1、 ETSI TS 102 722-2 V2.1.1 (2010-03)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 Essential, or potentially Essential, IPRs noti
2、fied 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 ca
3、n 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 docume
4、nt 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 Part 3: “Abstract
5、 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 ETSI TS 102 722-2 V2.1.1 (2010-03)51 Scope The
6、present document specifies the Test Suite Structure and Test Purposes (TSS - 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 we
7、re 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
8、 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 Originat
9、ing 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 Impl
10、ementation 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 ETSI TS 1
11、02 722-2 V2.1.1 (2010-03)66 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 - Conf
12、ormance 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:
13、 “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 ar
14、ea. 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.
15、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 abbreviatio
16、ns 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
17、.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 4and IT
18、U-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 ETSI TS 102 722-2 V2.1.1 (2010-03)7option-tag: Refer to RFC 3261 i.1. originating user:
19、 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. poin
20、t 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
21、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 out
22、side 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: t
23、he 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 ini
24、tiate 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 U
25、E 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 T
26、ermination (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 ETSI TS 102 722-2 V2.1.1 (2010-03)83.2 Abbreviations For the purposes of the present doc
27、ument, 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 SwitchedCSCF Call Session Control Function IBCF Interconnection Border Control Function IM IP
28、 Multimedia IP Internet ProtocolISDN 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 Pr
29、oxy - 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) Originati
30、ngUser CallingUser SyntaxReq OIP_U01_xxx OrigUser OIP_U02_xxxDestUser OIP_U03_xxxOriginating_Netw OrigP-CSCF OIP_N01_xxx gS-CSCF OIP_N02_xxxAS_OrigUser OIP_N03_xxxNotTrusNetw OIP_N04_xxxAS_TermUser OIP_N05_xxx Figure 1: Test suite structure 4.1 Configuration The scope of the present document is to t
31、est 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
32、of the different entities. ETSI ETSI TS 102 722-2 V2.1.1 (2010-03)9Therefore 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
33、 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
34、 this case, be aware that the verification of several requirements is impeded. CSCF(and/or AS)Implementation under TestTest SystemTest SystemMw, Mg, MxMw, Mg, MxFigure 2: Applicable interfaces to test using the (generic) NNI interface Figure 3 illustrates the usage of any NNI interface. Testing of U
35、ser Equipment: There are several requirements regarding to the end devices. Therefore a special configuration appears. User EquipmentImplementation under TestTest SystemGmFigure 3: Applicable configuration to test the User Equipment Testing of the IBCF functionality: The IBCF is the division between
36、 the trusted and the untraced networks. ETSI ETSI TS 102 722-2 V2.1.1 (2010-03)10Figure 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
37、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 spec
38、ification 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
39、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
40、 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. ET
41、SI ETSI TS 102 722-2 V2.1.1 (2010-03)115.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 Orig
42、inating_user/Calling_user/SyntaxReq TP OIP_U01_001 OIP reference clause 4.4 Selection expression 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, sen
43、ds an INVITE message containing a valid tel URI in the local number format e.g. tel: local number. Comments: User Equipment Test Equipment barb4right INVITE TSS Originating_user/Calling_user/SyntaxReq TP OIP_U01_002 OIP reference clause 4.4 Selection expression PICS 1/1 Test purpose: The originating
44、 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. Comm
45、ents: User Equipment Test Equipment barb4right INVITE TSS Originating_user/Calling_user/SyntaxReq TP OIP_U01_003 OIP reference clause 4.4 Selection expression 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 i
46、n 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 barb4right INVITE TSS Originating_us
47、er/Calling_user/SyntaxReq TP OIP_U01_004 OIP reference clause 4.4 Selection expression 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 Ide
48、ntity 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=. Comments: User Equipment Test Equipment barb4right INVITE ETSI ETSI TS 102 722-2 V2.1.1 (2010-03)12TSS Originating_user/Calling_user/SyntaxReq
49、TP OIP_U01_005 OIP reference clause 4.4 Selection expression 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 barb4right INVITE TSS O
