|
Technical Specification
Technical Committee for IMS Network Testing (INT);
Originating Identification Presentation (OIP)
and Originating Identification Restriction (OIR)
Part 2: Test Suite Structure and Test Purposes (TSS&TP)
---------------------- Page: 1 ----------------------
2 ETSI TS 102 722-2 V2.1.1 (2010-03)
Reference
DTS/INT-00001-2
Keywords
testing, TSS&TP, OIP, OIR
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2010.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI TS 102 722-2 V2.1.1 (2010-03)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 8
4 Test Suite Structure (TSS) . 8
4.1 Configuration . 8
5 Test Purposes (TP) . 10
5.1 Introduction . 10
5.1.1 TP naming convention . 10
5.1.2 Test strategy . 10
5.2 User TPs for OIP . 11
5.2.1 Calling user . 11
5.2.1.1 Valid behaviour . 11
5.2.1.1.1 Syntax requirements at the originating user . 11
5.2.1.1.2 Actions at the originating user . 14
5.2.1.1.3 Actions at the destination user . 15
5.2.2 Requirements on the originating network side. 16
5.2.2.1 Actions at the originating P-CSCF . 16
5.2.2.2 Actions at the S-CSCF serving the originating UE . 18
5.2.2.3 Actions at the AS serving the originating user . 18
5.2.2.4 Interactions with not trusted network SIP based networks. 23
5.2.2.5 Actions at the AS serving the terminating UE . 24
6 Compliance . 24
Annex A (informative): Bibliography . 25
History . 26
ETSI
---------------------- Page: 3 ----------------------
4 ETSI TS 102 722-2 V2.1.1 (2010-03)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by IMS Network Testing (INT).
The present document is part 2 of a multi-part deliverable covering Originating Identification Presentation (OIP) and
Originating Identification Restriction (OIR) as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 3: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification".
The present version updates the references to the basic call specifications.
NOTE: Some new parts will be developed in the future.
ETSI
---------------------- Page: 4 ----------------------
5 ETSI TS 102 722-2 V2.1.1 (2010-03)
1 Scope
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the Originating Identification
Presentation (OIP) and Originating Identification Restriction (OIR) NGN Basic Service, TS 124 407 [1].
A further part of this multi-part deliverable specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on the present document.
Within the TISPAN NGN Release 2, 3GPP release 8 Next Generation Network (NGN) the stage 3 description is
specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session
Description Protocol (SDP).
The OIP service provides the terminating party with the possibility to receive a trusted (network-provided) identity of
the originating party, and is applicable to all session-based services of the NGN.
The OIR service enables the originating party to prevent presentation of any network-provided identity to the
terminating party, and is applicable to all session-based services of the NGN.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TS 124 407: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services;
Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR);
Protocol specification (3GPP TS 24.407 Release 8)".
[2] ETSI TS 102 722-1: "Technical Committee for IMS Network Testing (INT); Originating
Identification Presentation (OIP) and Originating Identification Restriction (OIR) conformance
testing; Part 1: Protocol Implementation Conformance Statement (PICS)".
[3] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
[4] IETF RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax".
[5] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
ETSI
---------------------- Page: 5 ----------------------
6 ETSI TS 102 722-2 V2.1.1 (2010-03)
[6] IETF RFC 2806: "URLs for Telephone Calls".
[7] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[8] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[9] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite specification".
[10] ITU-T Recommendation Q.1912.5: "Interworking between Session Initiation Protocol (SIP) and
Bearer Independent Call Control protocol or ISDN User Part".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] IETF RFC 3261: "SIP: Session Initiation Protocol".
[i.2] ITU-T Recommendation I.210: "Principles of telecommunication services supported by an ISDN
and the means to describe them".
[i.3] ETSI TS 183 007: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); PSTN/ISDN simulation services; Originating Identification
Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
abstract test case: Refer to ISO/IEC 9646-1 [7].
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [7].
address identity: See ITU Recommendation E.164 [5] or/and RFC 2806 [6].
dialog: Refer to RFC 3261 [i.1].
final response: Refer to RFC 3261 [i.1].
header: Refer to RFC 3261 [i.1].
header field: Refer to RFC 3261 [i.1].
dentity information: includes all the information identfying a user, including trusted (network generated) and/or
untrusted (user generated) addresses
NOTE: See RFC 2806 [6], RFC 2396 [4]and ITU-T Recommendation E.164 [5].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [7].
implicit send event: Refer to ISO/IEC 9646-3 [8].
lower tester: Refer to ISO/IEC 9646-1 [7].
method: Refer to RFC 3261 [i.1].
ETSI
---------------------- Page: 6 ----------------------
7 ETSI TS 102 722-2 V2.1.1 (2010-03)
option-tag: Refer to RFC 3261 [i.1].
originating user: the sender of a SIP request intended to initiate either a dialog (e.g. INVITE, SUBSCRIBE), or a
standalone transaction (e.g. OPTIONS, MESSAGE)
outgoing (call): call outgoing from the user side of the interface
PICS proforma: Refer to ISO/IEC 9646-1 [7].
PIXIT proforma: Refer to ISO/IEC 9646-1 [7].
point of control and observation: Refer to ISO/IEC 9646-1 [7].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [7].
Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [7].
provisional response: Refer to RFC 3261 [i.1].
proxy, proxy server: Refer to RFC 3261 [i.1].
request: Refer to RFC 3261 [i.1].
response: Refer to RFC 3261 [i.1].
session: Refer to RFC 3261 [i.1].
SIP transaction: Refer to RFC 3261 [i.1].
standalone transaction: SIP transaction that is not part of a dialog and does not initiate a dialog
NOTE: An OPTIONS or a MESSAGE request sent outside of a SIP dialog would be considered to be part of a
standalone transaction.
supplementary service: See ITU-T Recommendation I.210 [i.2], clause 2.4
system under test: Refer to ISO/IEC 9646-1 [7].
tag: Refer to RFC 3261 [i.1].
test equipment: combination of equipment and procedures that can perform: the derivation of test cases, the selection
of test cases, the parameterization of test cases, the execution of test cases; and the production of a conformance log
Test Purpose (TP): Refer to ISO/IEC 9646-1 [7].
terminating user: recipient of a SIP request intended either to initiate a dialog or to initiate either a dialog or a
standalone transaction
trusted identity: network generated user address information
untrusted identity: user generated user address information
user equipment: allows a user access to network services
NOTE: For the purpose of 3GPP specifications the interface between the UE and the network is the radio
interface. A User Equipment can be subdivided into a number of domains, the domains being separated
by reference points. Currently the User Equipment is subdivided into the UICC domain and the ME
Domain. The ME Domain can further be subdivided into one or more Mobile Termination (MT) and
Terminal Equipment (TE) components showing the connectivity between multiple functional groups.
voice session: existing voice connection between two terminal equipments
EXAMPLE: Via RTP.
ETSI
---------------------- Page: 7 ----------------------
8 ETSI TS 102 722-2 V2.1.1 (2010-03)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AS Application Server
ATM Abstract Test Method
CLIP Calling Line Identification Presentation
CLIR Calling Line Identification Restriction
CN Core Network
CS Circuit Switched
CSCF Call Session Control Function
IBCF Interconnection Border Control Function
IM IP Multimedia
IP Internet Protocol
ISDN Integrated Service Data Network
MGCF Media Gateway Control Function
MT Mobile Termination
n/a not applicable
NGN Next Generation Network
NNI Network-Network Interface
OIP Originating Identification Presentation
OIR Originating Identification Restriction
P-CSCF Proxy - CSCF
PSTN Public Switch Telephone Network
S-CSCF Serving CSCF
SDP Session Description Protocol
SIP Session Initiation Protocol
TE Terminal Equipment
TP Test Purpose
TSS Test Suite Structure
UA User Agent
UE User Equipment
URI Universal Resource Identifier
4 Test Suite Structure (TSS)
OriginatingUser
CallingUser SyntaxReq OIP_U01_xxx
OrigUser OIP_U02_xxx
DestUser OIP_U03_xxx
Originating_Netw
OrigP-CSCF OIP_N01_xxx
OrigS-CSCF OIP_N02_xxx
AS_OrigUser OIP_N03_xxx
NotTrusNetw OIP_N04_xxx
AS_TermUser OIP_N05_xxx
Figure 1: Test suite structure
4.1 Configuration
The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as
described in [1]. The stage 3 description respects the requirements to several network entities and also to requirements
regarding to end devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different
entities.
ETSI
---------------------- Page: 8 ----------------------
9 ETSI TS 102 722-2 V2.1.1 (2010-03)
Therefore to test the appropriate entities the configurations below are applicable:
Testing of the Application Server: This entity is responsible to perform the service. Hence the ISC interface is the
appropriate access point. Figure 1 points to this.
Figure 1: Applicable interface to test AS functionalities
If the ISC interface is not accessible it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx)
interface (consider figure 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware
that the verification of several requirements is impeded.
Mw, Mg, Mx
Mw, Mg, Mx
CSCF
Test (and/or AS) Test
System System
Implementation
under Test
Figure 2: Applicable interfaces to test using the (generic) NNI interface
Figure 3 illustrates the usage of any NNI interface.
Testing of User Equipment: There are several requirements regarding to the end devices. Therefore a special
configuration appears.
Gm
User Equipment
Test
System Implementation
under Test
Figure 3: Applicable configuration to test the User Equipment
Testing of the IBCF functionality: The IBCF is the division between the trusted and the untraced networks.
ETSI
---------------------- Page: 9 ----------------------
10 ETSI TS 102 722-2 V2.1.1 (2010-03)
Figure 4: Applicable configuration to test the IBCF
If the Mx interface is not accessible it is also applicable to perform the test of the IBCF using any NNI (Mw, Mg, Mx)
interface (consider figure 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware
that the verification of several requirements is impeded.
5 Test Purposes (TP)
5.1 Introduction
For each test requirement a TP is defined.
The references applicable in the test Purposes are with respect to the OIP/OIR specification [1], except where explicitly
stated otherwise.
5.1.1 TP naming convention
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite and whether it applies to the network or the user (see table 1).
Table 1: TP identifier naming convention scheme
Identifier: __
= supplementary service: e.g. "OIP"
= type of IUT: U User - equipment
N Network
= group 2 digit field representing group reference according to TSS
= sequential number (001 to 999)
5.1.2 Test strategy
As the base standard TS 124 407 [1] TS 183 007 [i.3] contains no explicit requirements for testing, the TPs were
generated as a result of an analysis of the base standard and the PICS specification TS 102 722-1 [2]. The criteria
applied include the following:
• whether or not a test case can be built from the TP is not considered.
ETSI
---------------------- Page: 10 ----------------------
11 ETSI TS 102 722-2 V2.1.1 (2010-03)
5.2 User TPs for OIP
All PICS items referred to in this clause are as specified in TS 102 722-1 [2] unless indicated otherwise by another
numbered reference.
5.2.1 Calling user
5.2.1.1 Valid behaviour
5.2.1.1.1 Syntax requirements at the originating user
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_001 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in local number format
Ensure that the IUT in order to present a complete calling user identity contained in the P-Preferred Identity header,
sends an INVITE message containing a valid 'tel' URI in the local number format e.g. tel: local number.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_002 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in international number format: global number
Ensure that the IUT in order to present a complete calling user identity contained in the P-Preferred Identity header,
sends an INVITE message containing a valid 'tel' URI in the international number format e.g. tel: global number.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_003 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in local number format: phone-context=particular phone prefix
Ensure that the IUT in order to present a complete calling user identity contained in the P-Preferred Identity header,
sends an INVITE message containing a valid 'tel' URI in the format: tel: local number ; phone-context= particular phone
prefix.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_004 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in local number format: phone-context=domain name
Ensure that the IUT in order to present a complete calling user identity contained in the P-Preferred Identity header
sends an INVITE message containing a valid 'tel' URI in the format: tel: local number ; phone-context=domain name
e.g. tel: 4711; phone-context=example.com.
Comments:
User Equipment Test Equipment
INVITE
ETSI
---------------------- Page: 11 ----------------------
12 ETSI TS 102 722-2 V2.1.1 (2010-03)
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_005 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the global number format: isub=isdn sub address
Ensure that the IUT in order to present a complete calling user identity contained in the P-Preferred Identity header,
sends an INVITE message containing a valid 'tel' URI in the format:
tel: global number; isub= ISDN Subadress.
Comments:
UA C SUT UA S
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_006 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the local number format: isub=isdn sub address
Ensure that the IUT in order to present a complete calling user identity contained in the P-Preferred Identity header,
sends an INVITE message containing a valid 'tel' URI in the format tel: local number ; isub= ISDN Subadress.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_007 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the local number format: isub=isdn sub address, phone-context=particular phone
prefix
Ensure that the IUT in order to present a complete calling user identity contained in the P-Preferred Identity header,
sends an INVITE message containing a valid 'tel' URI in the format tel: local number; isub= ISDN Subadress ;
phone-context= particular phone prefix.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_008 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the local number format: phone context=domain name, isub=isdn sub address
Ensure that the IUT in order to present a complete calling user identity contained in the P-Preferred Identity header,
sends an INVITE message containing a valid 'tel' URI in the format: tel: local number ; phone-context= domaniname
e.g. tel: 4711 isub= ISDN Subadress; phone-context=example.com.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_009 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the From header in the local number format
Ensure that the IUT in order to present a complete calling user identity contained in the From header field,
sends an INVITE message containing a valid 'tel' URI in the local number format e.g. tel: local number.
Comments:
User Equipment Test Equipment
INVITE
ETSI
---------------------- Page: 12 ----------------------
13 ETSI TS 102 722-2 V2.1.1 (2010-03)
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_010 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the From header in the international number format
Ensure that the IUT in order to present a complete calling user identity contained in the From header field,
sends an INVITE message containing a valid 'tel' URI in the international number format e.g. tel: global number.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_011 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the From header in the local number format; phone-context=particular phone
prefix
Ensure that the IUT in order to present a complete calling user identity contained in the From header field,
sends an INVITE message containing a valid 'tel' URI in the format: tel: local number ; phone-context= particular phone
prefix.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_012 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the From header field; local number format, phone-context=domain name
Ensure that the IUT in order to present a complete calling user identity contained in the From header field,
sends an INVITE message containing a valid 'tel' URI in the format: tel: local number; phone-context= domain name
e.g. tel: 4711; phone-context=example.com.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_013 clause 4.5 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the From header field; global number format, isub=isdn sub address
Ensure that the IUT in order to present a complete calling user identity contained in the From header field,
sends an INVITE message containing a valid 'tel' URI in the format: tel: global number ; isub= ISDN Subadress.
Comments:
User Equipment Test Equipment
INVITE
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_014 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the From header field; local number format, isub=isdn sub address
Ensure that the IUT in order to present a complete calling user identity contained in the From header field,
sends an INVITE message containing a valid 'tel' URI in the format: tel: local number; isub= ISDN Subadress.
Comments:
User Equipment Test Equipment
INVITE
ETSI
---------------------- Page: 13 ----------------------
14 ETSI TS 102 722-2 V2.1.1 (2010-03)
TSS TP OIP reference Selection expression
Originating_user/Calling_user/SyntaxReq OIP_U01_015 clause 4.4 PICS 1/1
Test purpose:
The originating UE sends a Tel URI in the From header field ;local number format, isub=isdn sub address,
phone-context=particular phone context
Ensure that the IUT in order to present a complete calling user identity
...