ETSI TR 101 561-2011 IMS Network Testing (INT) Enhancement of Automated Interoperability Testing Framework in IMS core networks Test adapter And codec design suited for TTCN-3 intee.pdf

《ETSI TR 101 561-2011 IMS Network Testing (INT) Enhancement of Automated Interoperability Testing Framework in IMS core networks Test adapter And codec design suited for TTCN-3 intee.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 101 561-2011 IMS Network Testing (INT) Enhancement of Automated Interoperability Testing Framework in IMS core networks Test adapter And codec design suited for TTCN-3 intee.pdf（42页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 101 561 V1.1.1 (2011-06)Technical Report IMS Network Testing (INT);Enhancement of Automated Interoperability TestingFramework in IMS core networks:Test adapter And codec design suited forTTCN-3 interoperability testingfloppy3ETSI ETSI TR 101 561 V1.1.1 (2011-06) 2Reference DTR/INT-00035 Key

2、words adaption, codec, IMS, interoperability, IPv6, network 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 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are T

7、rade 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 Members and of the 3GPP Organizational Partner

8、s. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 101 561 V1.1.1 (2011-06) 3Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Abbreviations . 7g34 Overview 8g

9、35 Design proposals for receiving of traffic capture . 8g35.1 Design proposal for the codec 8g35.1.1 Principles 9g35.1.2 Encoder . 9g35.1.3 Decoder . 9g35.1.4 Discussion. 10g35.1.4.1 Rejected solutions . 10g35.1.4.1.1 External SIP application 10g35.1.4.1.2 Wireshark 10g35.1.4.1.3 Yacc parser 10g35.1

10、.4.2 Selected solution: T3DEVKIT 10g35.1.4.2.1 Encoder 11g35.1.4.2.2 Decoder . 11g35.2 Design proposals for receiving of traffic capture . 12g35.2.1 All traffic on single (mirrored) switch port . 12g35.2.2 Traffic on multiple switch ports (no mirroring) 13g35.2.3 Discussion. 13g36 Software design 13

11、g36.1 Codec design 13g36.1.1 Regular expression 14g36.1.2 Template generation . 14g36.1.2.1 Generation rules 14g36.1.2.2 Template generator design 14g36.2 Test adapter design . 15g36.2.1 Requirements 15g36.2.2 Software design 16g36.2.2.1 Test adapter interfaces . 17g36.2.2.2 Test adapter configurati

12、on . 18g36.2.2.3 Adapter configuration message encoding . 18g36.2.2.4 Traffic capture . 19g36.2.2.5 Merge of multiple trace files . 19g36.2.2.6 Possibilities for handling of equipment operation messages . 20g36.2.3 Discussion . 20g37 TTCN-3 message type definitions 20g37.1 TTCN-3 port description 20

13、g37.2 TTCN-3 messages description . 21g37.2.1 Record mode . 21g37.2.2 Merging of captured traffic files . 21g37.2.3 List of physical interfaces . 21g37.2.4 Example of setting general adapter configuration message values in TTCN-3 22g37.3 Setting of filter criteria . 23g37.4 Starting and stopping of

14、traffic capture 23g37.5 Equipment operation messages 24g3ETSI ETSI TR 101 561 V1.1.1 (2011-06) 48 Test case suite for Adapter regression tests 24g38.1 Description of TC_GeneralConfigurationMessageOffLineMode 24g38.2 Description of TC_GeneralConfigurationMessageLiveMode 24g38.3 Description of TC_Gene

15、ralConfigurationMessageMerge 24g38.4 Description of TC_TriggerUERegister 25g39 Deployment diagram of the test adapter . 25g310 Interaction of Adapter and PCAP traffic capture processes . 26g310.1 Interactions between TTCN-3 script and Adapter 26g310.2 Interaction between the Adapter and the traffic

16、capture process 27g311 Class diagram of the Adapter component 27g311.1 UpperTestAdapter class description . 28g311.2 Helpers classes description . 29g311.2.1 TTCN-3 messages decoding helpers. 29g311.2.2 Socket implementation . 29g311.2.3 Log framework . 29g311.2.4 BOOST framework . 29g311.2.5 Common

17、 development rules . 30g312 Implementation details . 30g312.1 TTCN-3 messages execution 30g312.1.1 Automate equipment operation . 30g312.1.2 Human friendly GUI . 30g312.2 Class diagrams 31g312.3 Human friendly GUI 31g312.4 TrafficCapture component 32g312.4.1 Usage 32g312.4.2 Architecture 33g312.4.3

18、Functional Specification . 34g312.4.3.1 UC 01: File Merging . 35g312.4.3.2 UC 02: Opening Device 35g312.4.3.3 UC 03: Setting Filter . 35g312.4.3.4 UC 04: Starting Capture 35g312.4.3.5 UC 05: Stopping Capture 36g312.4.4 Compilation 36g313 Test case suite for Codec: the torture tests . 36g313.1 Test S

19、ystem Architecture . 36g314 Testing of Test Adapter 37g315 SVN repositories 38g316 Development tools 38g317 RFCs covered by the codec 38g3History 42g3ETSI ETSI TR 101 561 V1.1.1 (2011-06) 5Intellectual Property Rights IPRs essential or potentially essential to the present document may have been decl

20、ared 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“, which

21、 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 given as to the existence of other IPRs not

22、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 Report (TR) has been produced by ETSI Technical Committee IMS Network Testing (INT). ETSI ETSI TR 101 561 V1.1.1 (2011-06) 61 Scope Th

23、e purpose of the present document is to present and describe issues and design choices made while developing a generic test adapter and codec suited for TTCN-3 interoperability testing within both STF370 and STF407. For further information, the reader is referred to EG 202 810 i.3 for global view of

24、 methodology and framework for automated interoperability testing and TR 102 788 i.4 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

25、 in C+ and TTCN-3 (ES 201 873-1 i.2) programming. Also good knowledge of the operation of ES 201 873-5 i.7 and ES 201 873-6 i.6 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

26、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.etsi.org/Reference. NOTE

27、: 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. Not applicable. 2.2 Informative references The f

28、ollowing 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 Official BOOST framework reference. NOTE: Available at: http:/www.boost.org/doc/libs/1_39_0/libs/libraries.htm. i.2 ETSI ES 201 873-1 (V3

29、.4.1): “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language“. i.3 ETSI EG 202 810: “Methods for Testing and Specification (MTS); Automated Interoperability Testing; Methodology and Framework “. i.4 ETSI TR 102 788: “Methods for T

30、esting and Specification (MTS); Automated Interoperability Testing; Specific Architectures“. i.5 Official t3devket framework reference. NOTE: Available at: http:/www.irisa.fr/tipi/wiki/doku.php/t3devkit. i.6 ETSI ES 201 873-6: “Methods for Testing and Specification (MTS); The Testing and Test Contro

31、l Notation version 3; Part 6: TTCN-3 Control Interface (TCI)“. i.7 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)“. ETSI ETSI TR 101 561 V1.1.1 (2011-06) 7i.8 IETF RFC 4475: “Session Initiation

32、Protocol (SIP) Torture Test Messages“. i.9 IETF RFC 3261: “Session Initiation Protocol (SIP )“. i.10 IETF RFC 3262: “Reliability of Provisional Responses in the Session Initiation Protocol (SIP)“. i.11 IETF RFC 3265: “Session Initiation Protocol (SIP)-Specific Event Notification“. i.12 IETF RFC 3313

33、: “Private Session Initiation Protocol (SIP) Extensions for Media Authorization“. i.13 IETF RFC 3323: “A Privacy Mechanism for the Session Initiation Protocol (SIP)“. i.14 IETF RFC 3325: “Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks“. i.15

34、 IETF RFC 3326: “The Reason Header Field for the Session Initiation Protocol (SIP)“. i.16 IETF RFC 3327: “Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts“. i.17 IETF RFC 3329: “Security Mechanism Agreement for the Session Initiation Protocol (SIP)“. i.1

35、8 IETF RFC 3455: “Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)“. i.19 IETF RFC 3515: “The Session Initiation Protocol (SIP) Refer Method“. i.20 IETF RFC 3608: “Session Initiation Protocol (SIP) Extension Header Field

36、for Service Route Discovery During Registration“. i.21 IETF RFC 3841: “Caller Preferences for the Session Initiation Protocol (SIP)“. i.22 IETF RFC 3891: “The Session Initiation Protocol (SIP) “Replaces“ Header“. i.23 IETF RFC 3892: “The Session Initiation Protocol (SIP) Referred-By Mechanism“. i.24

37、 IETF RFC 4028: “Session Timers in the Session Initiation Protocol (SIP)“. i.25 IETF RFC 4244: “An Extension to the Session Initiation Protocol (SIP) for Request History Information“. i.26 IETF RFC 5009: “Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization

38、of Early Media“. i.27 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“. i.28 IETF RFC 2617 HTTP: “Authentication: Basic and Digest Access Authentication“. 3 Abbreviations For the purposes of the present document, the following abbreviations apply: DNS Domain Name System (protocol) EUT Equipme

39、nt Under Test GUI Graphical User Interface HTTP Hypertext Transfer Protocol IP Internet Protocol IMS IP Multimedia Subsystem ISDN Integrated Service Digital Network OS Operating System PCAP Packet CaptureSIP Session Initiation Protocol SSH Secure Shell TCI TTCN-3 Control Interface ETSI ETSI TR 101 5

40、61 V1.1.1 (2011-06) 8TCP Transmission Control Protocol TRI TTCN-3 Runtime Interface TTCN-3 Testing and Test Control Notation 3 TE TTCN-3 Executable NOTE: As defined in ES 201 873-5 i.7 and ES 201 873-6 i.6. UE IMS User Equipment HTTPS Hypertext Transfer Protocol Secure IPv4 Internet Protocol version

41、 4 LR Leakage Ratio NNI Network to Network Interface POSIX Portable Operating System Interface SDP Service Delivery Platform SUT System Under Test TSI Time Slot Interchange UNIX Universal Network Information eXchange XML Extensible Markup Language 4 Overview The main purpose of the TTCN-3 interopera

42、bility test adapter is to implement the real test system interface as described in ES 201 873-1 i.2, ES 201 873-6 i.6 and ES 201 873-5 i.7 of the TTCN-3 IMS interoperability test system described in TR 102 788 i.4, i.e. the handling and transport of TTCN-3 messages send or received via abstract TTCN

43、-3 test system interface ports and different EUTs. Nevertheless it has been attempted to keep the adapter design completely independent on IMS specific testing. The adapter should be designed primarily to allow the use of the interoperability test system in the context of an interoperability event.

44、It should however also be possible to use it in the context of a test bed. Note that these usage scenarios come along with a different set of constraints. For example, in the context of an interoperability event it is not until the day of the event that you know which products and version of these p

45、roducts will participate whereas in a test bed that information is better known. Therefore automation of equipment operation is much easier to realize in a test bed than for an interoperability event. In addition interoperability events a restricted to a limited amount of times (usually a week) wher

46、eas time is not so much a constraint in the scenario of a test bed - giving much room for adaptation updates. The adapter conceptually splits into three parts: 1) an upper test adapter which provides an implementation of vendor specific operation of different EUTs involved in an interoperability tes

47、t; 2) a lower test adapter which captures traffic and isolates requested payloads based on filter criteria specified by an interoperability test suite and forwards them as raw data to the test suite; and 3) a TTCN-3 platform adapter implementing timers. 5 Design proposals for receiving of traffic ca

48、pture This clause evaluates different design proposals for integrating the TTCN-3 interoperability codec and test adapter with physical traffic capture. 5.1 Design proposal for the codec The following design considerations have been captured based on an analysis of the various protocols that need to

49、 be supported by the codec and the type definitions provided by TTCN-3 libraries. ETSI ETSI TR 101 561 V1.1.1 (2011-06) 95.1.1 Principles The codec should be extensible at low cost. SIP is still evolving and new headers and messages may be added to the protocol. Therefore it is essential to be able to add new types in the codec without having to fully redesign it. The codec should be as generic as possible and the chosen solution should not be operating system or hardware specific. Ideally, the