ETSI TS 101 586-2012 IMS Network Testing (INT) User Documentation and IMS Codec and Adapter layer software for IPv6 and 3GPP Release 9 (V1 1 1)《IMS网络测试(INT) IPv6和3GPP(第9次发布)的用户文件和I.pdf

1、 ETSI TS 101 586 V1.1.1 (2012-04) IMS Network Testing (INT); User Documentation and IMS Codec and Adapter layer software for IPv6 and 3GPP Release 9 Technical Specification ETSI ETSI TS 101 586 V1.1.1 (2012-04)2Reference DTS/INT-00060 Keywords IMS, testing ETSI 650 Route des Lucioles F-06921 Sophia

2、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 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The p

3、resent 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 the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI print

4、ers 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. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb

5、/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 part may be reproduced except as authorized by written permission. The copyright and the foregoing restr

6、iction 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 registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of

7、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 101 586 V1.1.1 (2012-04)3Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative

8、 references 5g33 Abbreviations . 6g34 Abstract Test Method (ATM) . 6g34.1 Introduction 6g34.2 Impact on the Test Adapter 7g34.3 Impact on the Codec . 7g35 Supporting IPv6 on the lower tester part 7g36 Supporting IPv6 on the codec 7g37 Untestable Test Purposes 7g38 ATS conventions 8g39 Abstract Test

9、Suite (ATS) 9g3History 10g3ETSI ETSI TS 101 586 V1.1.1 (2012-04)4Intellectual Property Rights IPRs essential or potentially essential 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-mem

10、bers, 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 available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). Pursuant

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

12、. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee IMS Network Testing (INT). ETSI ETSI TS 101 586 V1.1.1 (2012-04)51 Scope The purpose of the present document is to present and describe issues and design choices made to support IPv6 into the generic test adap

13、ter and codec suited for TTCN-3 interoperability testing within STF370, STF407 and STF435. NOTE: Both client and server were concerned by supporting of IPv6. For further information, the reader is referred to EG 202 810 i.2 for global view of methodology and framework for automated interoperability

14、testing and TR 102 788 i.3 for an overall view of the IMS interoperability test architecture which has served as the main source for design requirements. The present document has been written with the assumption that the reader is well versed in C+ and TTCN-3 (ES 201 873-1 i.1) programming. Also goo

15、d knowledge of the operation of ES 201 873-5 i.7 and ES 201 873-6 i.8 standards is assumed. 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-specifi

16、c references, the latest version of the referenced 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

17、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 IETF RFC 4291: “IP Version 6 Addressing Architecture“. 2.2 Informative references The following referen

18、ced 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 ES 201 873-1 (V3.4.1): “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language“.

19、 i.2 ETSI EG 202 810: “Methods for Testing and Specification (MTS); Automated Interoperability Testing; Methodology and Framework“. i.3 ETSI TR 102 788: “Methods for Testing and Specification (MTS); Automated Interoperability Testing; Specific Architectures“. i.4 ETSI TR 101 561 (V1.1.1): “IMS Netwo

20、rk Testing (INT); Enhancement of Automated Interoperability Testing Framework in IMS core networks: Test adapter And codec design suited for TTCN-3 interoperability testing“. i.5 ETSI EG 202 568: “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and

21、Framework“. i.6 ETSI TS 186 011-3: “IMS Network Testing (INT); IMS NNI Interoperability Test Specifications; Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)“. ETSI ETSI TS 101 586 V1.1.1 (2012-04)6i.7 ETSI ES 201 873-5: “Methods for Testing

22、 and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)“. i.8 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)“. i.9 ETSI ES 201 873-2: “M

23、ethods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 2: TTCN-3 Tabular presentation Format (TFT)“. 3 Abbreviations For the purposes of the present document, the abbreviations given in 1, i.1, i.2, i.3, i.4, i.5, i.6, i.7, i.8, i.9 and the following apply:

24、 ATM Abstract Test Method IPv6 Internet Protocol version 6 MSRP Message Session Relay Protocol PCAP Packet CAPtureSIP Session Internet Protocol SDP Session Description Protocol TTCN-3 Testing and Test Control Notation 3 4 Abstract Test Method (ATM) This clause describes the impact supporting IPv6 in

25、to the generic test adapter and codec. 4.1 Introduction The test adapter software architecture is described figure 1. g3g100g286g400g410g3g18g381g374g410g381g367g3g894g100g18g895g3 g100g286g400g410g3g62g381g336g336g349g374g336g3g894g100g62g895g3g94g455g400g410g286g373g3g4g282g258g393g410g286g396g3g8

26、94g94g4g895g3 g87g367g258g410g296g381g396g373g3g4g282g258g393g410g286g396g3g894g87g4g895g3g18g381g374g410g396g381g367g3 g17g286g346g258g448g349g381g396g3 g18g381g373g393g381g374g286g374g410g400g3g100g455g393g286g400g853g3g24g258g410g258g3 g87g381g396g410g400g3 g100g349g373g286g396g3g18g381g373g393g3

27、81g374g286g374g410g3g44g258g374g282g367g349g374g336g18g381g282g286g272g3g100g18g47g3g100g90g47g3g100g286g400g410g3g94g455g400g410g286g373g3g104g400g286g396g3g94g455g400g410g286g373g3g104g374g282g286g396g3g100g286g400g410g3g894g94g104g100g895g3Figure 1: Abstract Test System Architecture The main comp

28、onents are: A Lower Test Adapter which provides traffic capture processing functionality which includes handling both IPv4 and IPv6 and TCP fragmentation, isolation of protocol messages, etc. ETSI ETSI TS 101 586 V1.1.1 (2012-04)7 A PCAP capture process which interacts with the Lower Test Adapter. A

29、n Upper Test Adapter which converts TTCN-3 equipment operation messages into EUT operator instructions and can process their feedback based on a terminal window. TRI implementation. Codecs for decoding of configuration message request and encoding responses in the adapter. NOTE: Refer to TR 101 561

30、i.4 for more details. 4.2 Impact on the Test Adapter The adapter conceptually splits into three parts: a) an upper test adapter which provides an implementation of vendor specific operation of different EUTs involved in an interoperability test; b) a lower test adapter which captures traffic and iso

31、lates requested payloads based on filter criteria specified by an interoperability test suite and forwards them as raw data to the test suite; and c) a TTCN-3 platform adapter implementing timers. Only the lower tester is impacted by supporting IPv6. NOTE: As the PCAP library already support IPv6 pr

32、otocol, the PCAP Traffic Capture process (refer to TR 101 561 i.4, clause 6.1) is not concerned by supporting IPv6. 4.3 Impact on the Codec SIP, SDP and MSRP stacks are concerned by changes involved supporting IPv6. 5 Supporting IPv6 on the lower tester part The lower test adapter provides traffic c

33、apture processing functionality which includes handling of IPv4/IPv6 and TCP fragmentation, isolation of protocol messages, etc., (i.4, clause 6.2.2). 6 Supporting IPv6 on the codec Only addressing and versioning parts of SIP/SDP/MSRP stacks are concerned by supporting IPv6. As described in TR 101 5

34、61 i.4, clause 6.1, the codec is based on regular expression. In consequence, the impact of supporting IPv6 is reduced. The regular expression assertions were enhanced to include IPv6 formalism 1. / IPv6 #define SIPREG_HEX4 “ SIPCHARS_HEXA “1,4“ #define SIPREG_HEXSEQ SIPREG_HEX4 “(:“ SIPREG_HEX4 “)*

35、“ #define SIPREG_HEXPART “(“ SIPREG_HEXSEQ “)?:2(“ SIPREG_HEXSEQ “)?)|(“ SIPREG_HEXSEQ “)“ #define SIPREG_IP6 “ SIPREG_HEXPART “(:“ SIPREG_IP4 “)?“ / host #define SIPREG_HOST “(“ SIPREG_HOSTNAME “)|(“ SIPREG_IP4 “)|(“ SIPREG_IP6 “)“ #define SIPREG_ABSOLUTE_URI “(“ SIPCHARS_UNRESERVED “/;?: the names

36、 of TTCN-3 objects being associated with standardized data types (e.g. in the base protocols) should reflect the names of these data types as close as possible (of course not conflicting with syntactical requirements or other conventions being explicitly stated); the subfield names of TTCN-3 objects

37、 being associated with standardized data type should also be similar to corresponding element names in the base standards (be recognizable in the local context); in most other cases, identifiers should be prefixed with a short alphabetic string specified in table 1 (as described by EG 202 568 i.5, c

38、lause 8) indicating the type of TTCN-3 element it represents; prefixes should be separated from the body of the identifier with an underscore (“_“); only test case names, module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the

39、 identifier following the prefix) should begin with a lower-case letter. Table 1 specifies the naming guidelines for each construct of the TTCN-3 language indicating the recommended prefix and capitalization. Table 1: Naming Conventions Language element Naming convention Prefix Example Notes Module

40、Upper-case initial letter none LibSip_TypesAndValues Group Lower-case initial letter none messageGroup Data type Upper-case initial letter none SetupContents Message template Lower-case initial letter m_ m_response Note 1 Message template with wildcard or matching expression Lower-case initial lette

41、r mw_ mw_response Note 2 Modifying message template Lower-case initial letter md_ md_response Note 1 Modifying message template with wildcard or matching expression Lower-case initial letter mdw_ mdw_reponse Note 2 Port instance Lower-case initial letter none configPort Test component reference Lowe

42、r-case initial letter none userTerminal Constant Lower-case initial letter c_ c_maxRetransmission Constant (defined within component type) Lower-case initial letter cc_ cc_maxRetransmission External constant Lower-case initial letter cx_ cx_macId Function Lower-case initial letter f_ f_authenticatio

43、n() External function Lower-case initial letter fx_ fx_calculateLength() Altstep (incl. Default) Lower-case initial letter a_ a_receiveSetup() Test case All upper-case letters TC_ TC_IMS_MESS_0001 Variable (defined locally) Lower-case initial letter v_ v_macId Note 3 Variable (defined within compone

44、nt type) Lower-case initial letter vc_ vc_systemName ETSI ETSI TS 101 586 V1.1.1 (2012-04)9Language element Naming convention Prefix Example Notes Timer (defined locally) Lower-case initial letter t_ t_wait Timer (defined within component type) Lower-case initial letter tc_ tc_authMin Module paramet

45、er All upper-case letters none PX_MAC_ID Parameterization Lower-case initial letter p_ p_macId Enumerated Value Lower-case initial letter e_ e_syncOk NOTE 1: This prefix should be used for all template definitions which do not assign or refer to templates with wildcards or matching expressions, e.g.

46、 templates specifying a constant value, parameterized templates without matching expressions, etc. NOTE 2: This prefix should be used in identifiers for templates which either assign a wildcard or matching expression (e.g. ?, *, value list, ifpresent, pattern, etc.) or reference another template whi

47、ch assigns a wildcard or matching expression. NOTE 3: In this case it is acceptable to use underscore within an identifier. NOTE: Naming conventions have been enforced only in the TTCN-3 code written within this project for this ATS. There may be some minor deviations from these conventions in code

48、that has been reused from other ETSI projects. In addition to the above naming conventions, TTCN-3 functions which specify behaviour that is to execute on the main test component should use a “f_mtc_“ prefix to distinguish it from functions which can run on PTCs which have no prefix extension. For f

49、urther information on function design the reader is referred to i.6. 9 Abstract Test Suite (ATS) This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ES 201 873-2 i.9. ETSI ETSI TS 101 586 V1.1.1 (2012-04)10History Document history V1.1.1 April 2012 Publication