1、 ETSI TS 186 011-3 V4.1.3 (2012-05) IMS Network Testing (INT); IMS NNI Interoperability Test Specifications; Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) floppy3Technical Specification ETSI ETSI TS 186 011-3 V4.1.3 (2012-05)2Reference RT
2、S/INT-00061-3 Keywords ATS, IMS, interworking, NNI, testing 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Impo
3、rtant 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 th
4、e 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. Info
5、rmation 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 p
6、art 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 2012. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registere
7、d for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI 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 ETSI TS 186 011-3 V4.1.3 (2012-05)3Contents Intellectual
8、Property Rights 4g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Abbreviations . 6g34 Overview 7g34.1 Network architecture 7g34.1.1 Core IMS Nodes . 8g34.1.2 External IMS Nodes 8g34.1.2.1 UE . 8g34.1.2.2 AS . 8g35 Test configuration 8g36 Test
9、design 10g36.1 TTCN-3 naming convention. 10g36.2 TTCN-3 language version 11g36.3 Modularization . 12g36.4 SIP message template design 13g36.5 Function design 13g36.6 Handling of proprietary interfaces 14g36.7 Message skipping . 14g36.8 Documentation . 15g36.9 Mapping of test descriptions to test cas
10、es 16g37 Test system . 16g37.1 Test system architecture . 16g37.1.1 SUT adapter requirements 16g37.1.2 Adapter Configuration Primitives . 17g37.1.3 Upper Tester Primitives 17g37.1.4 TRI message encoding 18g37.2 Platform Adapter requirements 18g37.3 Codec requirements 19g37.3.1 Relevant RFCs 19g37.3.
11、2 SIP and SDP codec requirements . 20g37.3.2.1 Omission of the delimiters 20g37.3.2.2 Normalisation . 20g37.3.2.3 Other requirements . 21g38 Test execution 21g38.1 Live versus offline test execution . 21g38.2 Unavailable monitored interfaces . 22g38.3 Test case selection 22g38.4 PIXIT 22g38.4.1 LibI
12、ot_PIXITS 22g38.4.2 LibIms_UpperTester . 23g3Annex A (normative): Zip file with TTCN-3 code 24g3A.1 The ATS in TTCN-3 core (text) format . 24g3History 25g3ETSI ETSI TS 186 011-3 V4.1.3 (2012-05)4Intellectual Property Rights IPRs essential or potentially essential to the present document may have bee
13、n 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“,
14、 which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). 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
15、 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 ETSI Technical Committee IMS Network Testing (INT). The present document is part 3 of a multi-part deliv
16、erable covering the IMS NNI Interoperability Test Specifications, as identified below: Part 1: “Test Purposes for IMS NNI Interoperability“; Part 2: “Test descriptions for IMS NNI Interoperability“; Part 3: “Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
17、(PIXIT)“. ETSI ETSI TS 186 011-3 V4.1.3 (2012-05)51 Scope The present document describes the Abstract Test Suite (ATS) to test interoperability at IMS NNI for IP multimedia call control protocol based on TS 124 229 1. The ATS has been specified on the basis of the Test Descriptions for IMS NNI inter
18、operability testing presented in TS 186 011-2 3. It defines a TTCN-3 framework as well as codec and adapter requirements for analysing interoperability test execution traces generated from the manual or automatic execution of IMS interoperability tests. The scope of this ATS is not to cover all requ
19、irements specified in TS 124 229 1. It only assesses requirements that are observable at the NNI between two IMS core network implementations specified in TS 186 011-1 2. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-sp
20、ecific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.ets
21、i.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 necessary for the application of the present document. 1 ETSI TS 124 229 (V8.10.0)
22、: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 8.10.0 Release
23、8)“. 2 ETSI TS 186 011-1 (V4.1.2): “IMS Network Testing (INT); IMS NNI Interoperability Test Specifications; Part 1: Test Purposes for IMS NNI Interoperability“. 3 ETSI TS 186 011-2 (V4.1.2): “IMS Network Testing (INT); IMS NNI Interoperability Test Specifications; Part 2: Test Description for IMS N
24、NI Interoperability“. 4 ETSI ES 201 873-5: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)“. 5 ETSI ES 201 873-6: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part
25、6: TTCN-3 Control Interface (TCI)“. 6 ETSI ES 201 873-10: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 10: TTCN-3 Documentation Comment Specification“. 7 ETSI ES 201 873-1: “Methods for Testing and Specification (MTS); The Testing and Test Contr
26、ol Notation version 3; Part 1: TTCN-3 Core Language“. 2.2 Informative references The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI EG 202 568: “Methods for Testing and Specifica
27、tion (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework“. i.2 IETF RFC 3261: “SIP: Session Initiation Protocol“. ETSI ETSI TS 186 011-3 V4.1.3 (2012-05)6i.3 IETF RFC 3262: “Reliability of Provisional Responses in the Session Initiation Protocol (SIP)“. i.4 IETF RFC 3265: “Ses
28、sion Initiation Protocol (SIP)-Specific Event Notification“. i.5 IETF RFC 3313: “Private Session Initiation Protocol (SIP) Extensions for Media Authorization“. i.6 IETF RFC 3323: “A Privacy Mechanism for the Session Initiation Protocol (SIP)“. i.7 IETF RFC 3325: “Private Extensions to the Session In
29、itiation Protocol (SIP) for Asserted Identity within Trusted Networks“. i.8 IETF RFC 3326: “The Reason Header Field for the Session Initiation Protocol (SIP)“. i.9 IETF RFC 3327: “Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts“. i.10 IETF RFC 3329: “Se
30、curity Mechanism Agreement for the Session Initiation Protocol (SIP)“. i.11 IETF RFC 3455: “Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)“. i.12 IETF RFC 3515: “The Session Initiation Protocol (SIP) Refer Method“. i.13
31、 IETF RFC 3608: “Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration“. i.14 IETF RFC 3841: “Caller Preferences for the Session Initiation Protocol (SIP)“. i.15 IETF RFC 3891: “The Session Initiation Protocol (SIP) “Replaces“ Header“. i.16 IETF RFC
32、 3892: “The Session Initiation Protocol (SIP) Referred-By Mechanism“. i.17 IETF RFC 4028: “Session Timers in the Session Initiation Protocol (SIP)“. i.18 IETF RFC 4244: “An Extension to the Session Initiation Protocol (SIP) for Request History Information“. i.19 IETF RFC 5009: “Private Header (P-Hea
33、der) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media“. i.20 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“. i.21 IETF RFC 4566: “SDP: Session Description Protocol“. i.22 IETF RFC 1035: “Domain names - implementation and specification“. i.23 IETF RFC 2915:
34、 “The Naming Authority Pointer (NAPTR) DNS Resource Record“. i.24 IETF RFC 2617: “HTTP Authentication: Basic and Digest Access Authentication“. i.25 ETSI EG 202 810: “Methods for Testing and Specification (MTS); Automated Interoperability Testing; Methodology and Framework“. 3 Abbreviations For the
35、purposes of the present document, the following abbreviations apply: AS (IMS) Application Server AT Hayes commands ATS Abstract Test Suite CN Core Network CSCF Call Session Control Function DNS Directory Name Server EG ETSI Guide ES ETSI StandardETSI ETSI TS 186 011-3 V4.1.3 (2012-05)7EUT Equipment
36、Under test IBCF Interconnection Border Control Gateway I-CSCF Interrogating CSCF IMS IP Multimedia Subsystem IOT Interoperability TestingIP Internet ProtocolISC IMS service control interface MTC Main Test Component NNI Network to Network Interface PCAP Packet CAPture PCO Point of Control and Observa
37、tion P-CSCF Proxy CSCF PO Point of Observation PTC Parallel Test ComponentSA SUT Adapter S-CSCF Serving CSCFSDP Session Description Protocol SIP Session Initiation Protocol SUT System Under Test TC Test Cases TCI TTCN-3 Control Interface TD Test Description TE test ExecutionTP Test Purpose TRI TTCN-
38、3 Runtime Interface TSI Test System Interface TTCN-3 Testing and Test Control Notation 3 UE User Equipment URI Uniform Resource Identifier UTF UCS transformation format 4 Overview 4.1 Network architecture The ATS is defined to observe the SIP communication at the Gm, Mx, Ici and ISC interface of two
39、 IMS core networks for interoperability testing. Figure 1 shows a general architecture of two IMS core networks including the related interfaces. ETSI ETSI TS 186 011-3 V4.1.3 (2012-05)8Figure 1: Network Architecture 4.1.1 Core IMS Nodes The P-CSCF, S-CSCF, I-CSCF and the IBCF are considered to be w
40、ithin a “black box“ for testing purposes, i.e. the System Under Test (SUT). Interfaces within the IMS are considered internal and not observable for testing purposes except the Mx interface. The Mx and the Ici interface between two IMS core networks is used as point of observation (PO) for NNI inter
41、operability tests. 4.1.2 External IMS Nodes 4.1.2.1 UE The UE is considered to act as stimulus node in this test specification. The Gm interface between the P-CSCF and the UE is used as a Point of Control and Observation (PCO) for NNI interoperability tests. 4.1.2.2 AS The Application Server (AS) is
42、 considered to act as a stimulus node in this test specification. The ISC interface between the S-CSCF and the AS is used as Point of Control and Observation (PCO) for NNI interoperability tests. 5 Test configuration The test configuration is described in detail in TS 186 011-2 3. Test configuration
43、s have been defined in 3 by applying an interface based design approach. Here, each monitored IMS interface is paired with one dedicated Parallel Test Component (PTC) which receives all relevant message information from the TTCN-3 SUT Adapter (SA) via the abstract test system interface and checks it
44、s correctness according to the conformance criteria listed for a particular IMS test. An example test configuration is shown in figure 2. For detailed discussion of the abstract test system interface, the reader is referred to clause 6.2. IMS CN UE IMS CN AS AS IBCF IBCF UE GGMx MxIci ISC ISC SIP pr
45、otocolCore Network A Core Network B ETSI ETSI TS 186 011-3 V4.1.3 (2012-05)9Figure 2: Example IMS NNI interoperability test system configuration The test system configuration is based on the general TTCN-3 test system architecture specified in ES 201 873-5 4 and ES 201 873-6 5 as well as on the conc
46、epts stated in EG 202 810 i.25. Note that the figure 2 does not illustrate roaming and IMS/PSTN interworking aspects in a test configuration. In addition, it does not show the DNS server as an application support node for each IMS core network as well as its associated interface monitor component, w
47、hich are only required in a few tests. Note that TTCN-3 test components which are shown with dashed lines in figure 2 are only started for the execution of the test suite in live mode. The different types of TTCN-3 components used in this ATS are: Test Coordinator is a component type is dedicated to
48、 coordinate the behaviour of all other test components, which work on tasks independently of each other. It is in charge of controlling the overall execution, management of testing phases, conformance verdict and end-to-end interoperability verdict management, and synchronization. Equipment User is
49、a component type is dedicated to handle equipment operation, e.g. configure an IMS CN, make basic call or messaging from a UE, check for an incoming call notification on a UE, barring a user in a IMS CN, de-register a user forcefully from the IMS CN during a call. Interface Monitor is a component type that is dedicated to monitor one specific logical interface either between two EUTs or a EUT and an Application Support Node, e.g. IMS CN and a DNS server. UE_UE_AS_ AS_EUT_A IMS Gm Ici Gm I
