ETSI TS 186 005-3-2010 IMS Network Testing (INT) Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) Conformance Testing Part 3 Abstract n.pdf

《ETSI TS 186 005-3-2010 IMS Network Testing (INT) Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) Conformance Testing Part 3 Abstract n.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 186 005-3-2010 IMS Network Testing (INT) Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) Conformance Testing Part 3 Abstract n.pdf（27页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 186 005-3 V2.2.1 (2010-10)Technical Specification IMS Network Testing (INT);Terminating Identification Presentation (TIP) andTerminating Identification Restriction (TIR)Conformance Testing;Part 3: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PI

2、XIT)proforma specificationfloppy3ETSI ETSI TS 186 005-3 V2.2.1 (2010-10)2Reference RTS/INT-00040-3 Keywords ATS, IMS, PIXIT, SIP, testing, TIP, TIR, TTCN 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

3、 742 C Association but non lucratif enregistre la Sous-Prfecture 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 e

4、xisting 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 d

5、ocument 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 f

6、ollowing 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 r

7、ights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM 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 cu

8、rrently 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 ETSI TS 186 005-3 V2.2.1 (2010-10)3Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 References 5g

9、32.1 Normative references . 5g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Abstract Test Method (ATM) . 8g34.1 Network architecture 8g34.2 Protocol architecture. 8g34.3 Test architecture . 9g34.3.1 Test configuration . 9g34.3.1.1 Con

10、figuration using Gm interface . 9g34.3.1.2 Configuration using ISC interface . 10g34.3.1.3 Configuration using Mw and Ic interfaces 10g34.3.2 Test system architecture 10g34.3.2.1 General 10g34.3.2.2 Structure 10g34.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) 11g34.3.2.3.1 S

11、ending and receiving SIP/IMS messages 11g34.3.2.3.2 Security and messages compression feature 12g34.3.2.3.3 Additional SA constraints 13g34.3.2.4 Encoding/Decoding requirements . 13g34.3.2.4.1 Encoding/Decoding System requirements for basic SIP messages/headers 13g34.3.2.5 Platform adaptation requir

12、ements . 14g35 The ATS development process . 14g35.1 Requirements and Test Purposes 14g35.2 ATS structure . 14g35.2.1 Test case grouping 14g35.2.2 Test case identifiers 15g35.3 ATS specification framework . 15g35.3.1 ATS Library 15g35.3.2 Use of TTCN-3 . 16g35.3.2.1 General 16g35.3.2.2 TTCN-3 naming

13、 conventions 17g35.3.2.3 Additional TTCN-3 IMS/SIP naming convention 18g35.3.2.4 Additional concepts and conventions 19g35.3.2.5 PICS information 19g35.3.2.6 Test Suite documentation 19g3Annex A (normative): Partial PIXIT proforma 20g3A.1 Introduction 20g3A.2 PIXIT items 20g3A.2.1 SIP-related PIXIT

14、. 20g3A.2.2 IMS-related PIXIT . 21g3Annex B (informative): TTCN-3 library modules . 25g3B.1 Electronic annex, zip file with TTCN-3 code 25g3Annex C (informative): Bibliography . 26g3History 27 ETSI ETSI TS 186 005-3 V2.2.1 (2010-10)4Intellectual Property Rights IPRs essential or potentially essentia

15、l 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

16、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

17、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 ETSI Technical Committee IMS Network Testing (INT)

18、. The present document is part 3 of a multi-part deliverable covering Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR), as identified below: Part 1: “Protocol Implementation Conformance Statement (PICS)“; Part 2: “Test Suite Structure and Test Purposes (

19、TSS Part 3: “Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification“. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10)51 Scope The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information

20、 for Testing (PIXIT) proforma based on the Test Suite Structure and Test Purposes defined in TS 186 005-2 2. The TSS the testing architecture; the test methods and port definitions; the test configurations; the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator

21、); TTCN styles and conventions; the partial PIXIT proforma; the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS. 2 References Refe

22、rences are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced do

23、cuments 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 follo

24、wing referenced documents are necessary for the application of the present document. 1 ETSI TS 183 008: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Iden

25、tification Restriction (TIR); Protocol specification“. 2 ETSI TS 186 005-2: “Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Part 2: Test Suite Structure

26、 and Test Purposes (TSS The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language“. 7 ETSI ES 201 873-2: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 2: TTCN-3 Tabular presentation Format (TFT)“. 8 ETSI ES 201 873-5: “Methods

27、 for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)“. 9 ETSI ES 201 873-6: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)“. 10 ETSI TS 102

28、027-3 (V3.1.1): “Methods for Testing and Specification (MTS); Conformance Test Specification for SIP (IETF RFC 3261); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma“. 11 ETSI TS 102 351 (V2.1.1): “Methods for Testing and Specifica

29、tion (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework“. 12 ETSI TS 186 017-2: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Anonymous Communication Rejection (ACR) and Communication Ba

30、rring (CB); Part 2: Test Suite Structure and Test Purposes (TSS PSTN/ISDN simulation services; Closed User Group (CUG); Part 2: Test Suite Structure and Test Purposes (TSS PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Part 2: Test Suite Structure and Test Purposes (TS

31、S Peer-to-Peer Digital Private Mobile Radio; Part 2: Conformance testing; Test Suite Structure and Test Purposes (TSS section LibIms). NOTE 2: For each test configuration listed above a TTCN-3 configuration function has been implemented with the required mapping and unmapping statements (see table 3

32、; module SS_Ims_TestConfiguration), e.g. f_cf_1Ueup map one UE1 related port of the test system to the SUT. Figure 9 illustrates the interconnection of TS and SUT in terms of signalling message associations. TSas1port:sipp port:sippport:AS1ue1port:UE1port:sippic1port:IC1port:MW_I1mwi1SUTIMSport:UE2u

33、e2port:UE3ue3SUTASSUTUEscscfport:SCSCFport:sipppcscfport:PCSCFport:sippFigure 9: Abstract port association 4.3.2.3.2 Security and messages compression feature Security transport layer, and signalling compression may be used transparently to the ATS. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10)134.3.2.3.3

34、 Additional SA constraints In order to execute this test suite the SA should support: communication channel handling (at least UDP and possibly also TCP); IPv4 transport. 4.3.2.4 Encoding/Decoding requirements 4.3.2.4.1 Encoding/Decoding System requirements for basic SIP messages/headers SIP is a te

35、xt-based protocol that allows different syntactical presentations of the same information. In general, an implementation of this ATS should use an EDS to parse received encoded messages into TTCN-3 type structures and values, and encode structured TTCN-3 type structures and values into encoded messa

36、ges. This EDS is not part of the ATS. Still all encoded messages, i.e. the messages as they are transmitted by the SA to or received by the SA from the SUT, shall be logged. The following terms shall be used for the conventions defined below: Syntactic delimiter syntactic delimiters are characters l

37、ike “=“ or “;“ that are used to separate encoded values. LWS linear white spaces as defined in RFC 3261 3. Parameter name name of header parameters as defined in RFC 3261 3. Parameter value the value of a parameter as defined in RFC 3261 3. Undefined method an undefined method is a method other than

38、: “INVITE“, “ACK“, “OPTIONS“, “BYE“, “CANCEL“ and “REGISTER“. Undefined header an undefined header is a header other than general-header, entity-header, request-header and response header as defined in RFC 3261 3. Unexpected header an unexpected header is a header, which shall not be present in a sp

39、ecific request message. This definition complies with the definition of NOT APPLICABLE in RFC 3261 3, clause 20 for request messages. Decoder requirements TTCN-3 fields should not contain syntactic delimiters like white space, semicolon, equal characters etc. in fully decoded fields. Instead the inf

40、ormation provided by a parser shall be used to build the decoded message in TTCN-3. Decoded messages shall use the TTCN-3 enumeration types where ever appropriate, e.g. for the method and the header field name. For charstring fields the following decoding rules shall be applied by the EDS: 1) Subseq

41、uent LWS shall compress to a single space character “ “. 2) Decoded parameter names shall use only lower case letters. 3) Parameter values containing an integer value shall be decoded to a TTCN-3 integer value where a TTCN-3 integer type is used for a SIP parameter value. The following decoding rule

42、s shall be applied by the EDS to each received message in the following order: 1) In case a request message indicating an undefined method is received by the test system, the message shall not be passed in the TE to the ETS. However the message is subject to logging as defined in clause 4.3.3 (“Logg

43、ing conventions“). 2) In case an undefined header has been received the header field shall be decoded as UndefinedHeader field. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10)14RFC 3261 3 allows for multiple header field values of the same kind to either arrive in one or multiple occurrences of the correspo

44、nding header field. The SIP ATS has been written assuming only the first format. Therefore, should the EDS receive multiple header fields of the same kind in a SIP message, e.g. of a Via header field, it shall convert them into the equivalent single header field with multiple values. This can be ach

45、ieved by adding the value of, e.g. the second received Via header field as the last value to the value(s) of the first Via header field. Encoder requirements Encoders shall follow all encoding rules that are defined in RFC 3261 3 when encoding structured values received from templates. This applies

46、in particular to but it is not restricted to clause 7.3.1 of RFC 3261 3. Values of type Raw shall be sent to the SUT without any modification. 4.3.2.5 Platform adaptation requirements For the execution of this test suite implementations of the following external functions have to be provided (see mo

47、dule LibSip_Steps): 1) rndStr() return charstring; returns a random charstring; 2) putInLowercase(charstring par_string) return charstring; returns the equivalent string in lower case; 3) getIpAddr(charstring host_name) return charstring; resolves a domain name to its equivalent IPv4 address; calcul

48、ateDigestResponse(charstring nonce, charstring cnonce, charstring user, charstring realm, charstring passwd, charstring alg, charstring nonceCount, charstring method, charstring qop, charstring URI, charstring HEntity) return charstring; generates a digest response according to RFC 2617 16 (HTTP Aut

49、hentication: Basic and Digest Access Authentication), and RFC 1321 17. The MD5 Message-Digest Algorithm. (See RFC 2617 16, clause 5 Sample implementation, for example usage, as the signature of calculateDigestResponse is according to the example given in the RFC.) 5 The ATS development process 5.1 Requirements and Test Purposes For each test purpose there is a table defined in clause 5 of TS 186 005-2 2. The requirements applicable to this TP are given by a reference to RFC 3261 3 (SIP), or TS 183 008 1. There ar