ETSI TS 186 018-3-2010 IMS Network Testing (INT) Malicious Communication Identification (MCID) Conformance Testing Part 3 Abstract Test Suite (ATS) and partial Protocol Implementat.pdf

1、 ETSI TS 186 018-3 V2.2.1 (2010-11)Technical Specification IMS Network Testing (INT);Malicious Communication Identification (MCID)Conformance Testing;Part 3: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT)proforma specificationfloppy3ETSI ETSI TS 18

2、6 018-3 V2.2.1 (2010-11)2Reference RTS/INT-00041-3 Keywords ATS, IMS, MCID, PIXIT, SIP, testing, 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 742 C Association but non lucratif enregistre la So

3、us-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 existing or perceived difference in contents between

4、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 sub

5、ject 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/ET

6、SI_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. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONT

7、M, 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 currently being registered for the benefit of its Memb

8、ers 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 018-3 V2.2.1 (2010-11)3Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative refer

9、ences 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Abstract Test Method (ATM) . 8g34.1 Network architecture 8g34.2 Protocol architecture. 9g34.3 Test architecture . 9g34.3.1 Test configuration . 9g34.3.1.1 Configuration using Gm interface . 9g34.3.1.2 Configura

10、tion using ISC interface . 10g34.3.1.3 Configuration using Mw and Ic interfaces 10g34.3.2 Test system architecture 11g34.3.2.1 General 11g34.3.2.2 Structure 11g34.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) 12g34.3.2.3.1 Sending and receiving SIP/IMS messages 12g34.3.2.3.2

11、Security and messages compression feature 13g34.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 requirements . 14g35 The ATS development process . 15g35.1

12、 Requirements and Test Purposes 15g35.2 ATS structure . 15g35.2.1 Test case grouping 15g35.2.2 Test case identifiers 15g35.3 ATS specification framework . 16g35.3.1 ATS Library 16g35.3.2 Use of TTCN-3 . 17g35.3.2.1 General 17g35.3.2.2 TTCN-3 naming conventions 17g35.3.2.3 Additional TTCN-3 IMS/SIP n

13、aming 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 . 20g3A.2.2 IMS-related PIXIT . 22g3Annex B (informa

14、tive): TTCN-3 library modules . 26g3B.1 Electronic annex, zip file with TTCN-3 code 26g3Annex C (informative): Bibliography . 27g3History 28 ETSI ETSI TS 186 018-3 V2.2.1 (2010-11)4Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to

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

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

17、ed 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 del

18、iverable covering Malicious Communication IDentification (MCID), as identified below: Part 1: “Protocol Implementation Conformance Statement (PICS)“; Part 2: “Test Suite Structure and Test Purposes (TSS Part 3: “Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Test

19、ing (PIXIT) proforma specification“. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11)51 Scope The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Test Suite Structure and Test Purposes defined in TS 186 0

20、18-2 3. The TSS the testing architecture; the test methods and port definitions; the test configurations; the design principles, assumptions, and used interfaces to the TTCN-3 tester (System Simulator); TTCN styles and conventions; the partial PIXIT proforma; the modules containing the TTCN-3 ATS. A

21、nnex 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 References are either specific (identified by date of publication and/or edition number or version numbe

22、r) 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 documents which are not found to be publicly available in the expected location might be found at http

23、:/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 necessary for the application of the present document. 1 ETSI TS 183 0

24、16: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol specification“. 2 ETSI TS 186 018-1: “Telecommunications and Internet converged Services and Protocols for Ad

25、vanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Part 1: Protocol Implementation Conformance Statement (PICS)“. 3 ETSI TS 186 018-2: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN

26、simulation services; Malicious Communication Identification (MCID); Part 2: Test Suite Structure and Test Purposes (TSS The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language“. 8 ETSI ES 201 873-2: “Methods for Testing and Specification (MTS); The Testing and Test Control Nota

27、tion version 3; Part 2: TTCN-3 Tabular presentation Format (TFT)“. 9 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)“. 10 ETSI ES 201 873-6: “Methods for Testing and Specification (MTS); The Test

28、ing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)“. 11 ETSI TS 102 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 Informati

29、on for Testing (PIXIT) proforma“. 12 ETSI TS 102 351 (V2.1.1): “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework“. 13 ETSI TS 186 005-2: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TIS

30、PAN); Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); 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; Anonymo

31、us Communication Rejection (ACR) and Communication Barring (CB); Part 2: Test Suite Structure and Test Purposes (TSS Internet Protocol Testing (IPT); Testing: Methodology and Framework“. i.2 ETSI TS 102 587-2: “ Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to-Peer Digital Pri

32、vate 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 functions has been implemented with the required mapping and unmapping statements (see table 3; module SS_Ims_TestConfi

33、guration), e.g. f_cf_1Ueup map one UE1 related port of the test system to the SUT. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11)13Figure 9 illustrates the interconnection of TS and SUT in terms of signalling message associations. TSas1port:sippport:sippport:AS1ue1port:UE1port:sippic1port:IC1port:MW_I1mwi1

34、SUTIMSport:UE2ue2port: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. 4.3.2.3.3 Additional SA constraints

35、 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 text-based protocol that all

36、ows 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 messages. This EDS is not part

37、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 like “=“ or “;“ that are us

38、ed to separate encoded values. LWS Linear White Spaces as defined in RFC 3261 4. Parameter name name of header parameters as defined in RFC 3261 4. ETSI ETSI TS 186 018-3 V2.2.1 (2010-11)14Parameter value the value of a parameter as defined in RFC 3261 4. Undefined method an undefined method is a me

39、thod other than: “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 4. Unexpected header an unexpected header is a header, which shall not be

40、present in a specific request message. This definition complies with the definition of NOT APPLICABLE in RFC 3261 4, 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.

41、Instead the information 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

42、 EDS: 1) Subsequent 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 followin

43、g decoding rules 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 clau

44、se 4.3.3 (“Logging conventions“). 2) In case an undefined header has been received the header field shall be decoded as UndefinedHeader field. RFC 3261 4 allows for multiple header field values of the same kind to either arrive in one or multiple occurrences of the corresponding header field. The SI

45、P 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 achieved by adding the value

46、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 4 when encoding structured values received from templates. This applies in particular to but it is

47、 not restricted to clause 7.3.1 of RFC 3261 4. 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 (cp. module LibSip_Steps): 1) rnd

48、Str() 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. ETSI ETSI TS 186 018-3 V2.2.1 (2

49、010-11)15calculateDigestResponse(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 Authentication: 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 calculateDig