1、 ETSI TS 186 017-3 V2.2.1 (2010-10)Technical Specification Technical Committee for IMS Network Testing (INT);Anonymous Communication Rejection (ACR) andCommunication Barring (CB) conformance testing;Part 3: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (P
2、IXIT)proforma specificationfloppy3ETSI ETSI TS 186 017-3 V2.2.1 (2010-10)2Reference RTS/INT-00038-3 Keywords ATS, IMS, 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 Associati
3、on 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 existing or perce
4、ived 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 b
5、e 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 service
6、s: 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.
7、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 currently being re
8、gistered 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 017-3 V2.2.1 (2010-10)3Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative r
9、eferences . 6g32.2 Informative references 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Abstract Test Method (ATM) . 9g34.1 Network architecture 9g34.2 Protocol architecture. 10g34.3 Test architecture . 10g34.3.1 Test configuration . 10g34.3.1.1 Configuration us
10、ing Gm interface . 10g34.3.1.2 Configuration using ISC interface . 11g34.3.1.3 Configuration using Mw and Ic interfaces 11g34.3.2 Test system architecture 12g34.3.2.1 General 12g34.3.2.2 Structure 12g34.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) 12g34.3.2.3.1 Sending and r
11、eceiving SIP/IMS messages 12g34.3.2.3.2 Security 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
12、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
13、Technical Specification (TS) has been produced by ETSI Technical Committee IMS Network Testing (INT). The present document is part 3 of a multi-part deliverable covering Anonymous Communication Rejection (ACR) and Communication Barring (CB), as identified below: Part 1: “Protocol Implementation Conf
14、ormance Statement (PICS)“; Part 2: “Test Suite Structure and Test Purposes (TSS Part 3: “Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification“. ETSI ETSI TS 186 017-3 V2.2.1 (2010-10)61 Scope The present document specifies the Abs
15、tract 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 017-2 3. The TSS the testing architecture; the test methods and port definitions; the test configurations; the design princi
16、ples, assumptions and used interfaces to the TTCN3 tester (System Simulator); 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 Te
17、sting 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 number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version
18、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.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI ca
19、nnot 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 011: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation
20、services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification“. 2 ETSI TS 186 017-1: “Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) a
21、nd Communication Barring (CB); Part 1: Protocol Implementation Conformance Statement (PICS)“. ETSI ETSI TS 186 017-3 V2.2.1 (2010-10)73 ETSI TS 186 017-2: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Anonymous Comm
22、unication Rejection (ACR) and Communication Barring (CB); 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 Notation versi
23、on 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 Testing and Te
24、st 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 Information for Tes
25、ting (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 (TISPAN); Term
26、inating 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; Malicious Communi
27、cation Identification (MCID); 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 Private Mobile Radio; Part 2: Conforman
28、ce 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_TestConfiguration), e.g. f_cf_1Ueup map one U
29、E1 related port of the test system to the SUT. ETSI ETSI TS 186 017-3 V2.2.1 (2010-10)14Figure 9 illustrates the interconnection of TS and SUT in terms of signalling message associations. TSas1port:sippport:sippport:AS1ue1port:UE1port:sippic1port:IC1port:MW_I1mwi1SUTIMSport:UE2ue2port:UE3ue3SUTASSUT
30、UEscscfport:SCSCFport:sipppcscfport:PCSCFport:sippFigure 9: Abstract port association 4.3.2.3.2 Security 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 allows different syntactica
31、l 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 of the ATS. Still all enc
32、oded 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 used to separate encoded va
33、lues. 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 017-3 V2.2.1 (2010-10)15Parameter value the value of a parameter as defined in RFC 3261 4. Undefined method an undefined method is a method other than: “INVITE“
34、, “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 present in a specific req
35、uest 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. Instead the information p
36、rovided 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) Subsequent LWS s
37、hall 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 rules shall be
38、 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 (“Logging conven
39、tions“). 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 SIP ATS has been written as
40、suming 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 of, e.g. the second recei
41、ved 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 not restricted to clause
42、 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 (see module LibSip_Steps): 1) rndStr() return charstring;
43、returns a random charstring; 2) putInLowercase(charstring par_string) return charstring; returns the equivalent string in lower case; ETSI ETSI TS 186 017-3 V2.2.1 (2010-10)163) getIpAddr(charstring host_name) return charstring; resolves a domain name to its equivalent IPv4 address; calculateDigestR
44、esponse(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 Authenticatio
45、n: 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 2617 16.) 5 The ATS development process 5.1 Req
46、uirements and Test Purposes For each test purpose there is a table defined in clause 5 of TS 186 017-2 3. The requirements applicable to this TP are given by a reference to RFC 3261 4 (SIP), or TS 183 011 1. There are no explicit formulations of requirements. 5.2 ATS structure 5.2.1 Test case groupi
47、ng The ATS structure defined in table 2 is based on the structuring of Test Purposes in clause 4 of TS 186 017-2 3. The group names in column 2 of table 2 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 186 017-2 3, but use the naming conventions defined for the
48、 ATS (see clause 5.3.2.2). Table 2: ATS structure ACR-CB ACR_terminating_AS ACR-CB_N01_xxx OBC_originating_AS ACR-CB_N02_xxxIBC_terminating_AS ACR-CB_N03_xxxinteraction_OIP ACR-CB_N04_xxx interaction_CDIV ACR-CB_N05_xxx5.2.2 Test case identifiers The test case names are built up according to the fol
49、lowing scheme: “_“_“ where: a) double quotes (“) are used to enclose literal strings; b) is the group index in column 4 of table 2 (which uniquely identifies the path of groups/subgroups); c) is a running 3-digit decimal number, starting in each subgroup path with “001“. EXAMPLE: TC_ACR_CB_N01_001: i) the identifier has Group index “ACR_CB_N01“, i.e. it is in the subgroup having complete path: SupplementaryService_ACR/SS_ACR_CB_SIPSIP/ ACR_terminating_AS; ii) the identifier is the first test case of this
