ETSI EG 202 237-2010 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) Generic approach to interoperability testing (V1 2 1)《测试方法和规范(MTS) 互联网协议测试(IPT) 互用性_1.pdf

《ETSI EG 202 237-2010 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) Generic approach to interoperability testing (V1 2 1)《测试方法和规范(MTS) 互联网协议测试(IPT) 互用性_1.pdf》由会员分享，可在线阅读，更多相关《ETSI EG 202 237-2010 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) Generic approach to interoperability testing (V1 2 1)《测试方法和规范(MTS) 互联网协议测试(IPT) 互用性_1.pdf（41页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI EG 202 237 V1.2.1 (2010-08)ETSI Guide Methods for Testing and Specification (MTS);Internet Protocol Testing (IPT);Generic approach to interoperability testingETSI ETSI EG 202 237 V1.2.1 (2010-08)2Reference REG/MTS-00129-IOP-TSTAPPROACH Keywords interoperability, IP, telephony, testing ETSI 650

2、 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 Important notice Individual copies of the present document can be downlo

3、aded 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 the Portable Document Format (PDF). In case of dispute, the reference

4、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. Information on the current status of this and other ETSI documents is av

5、ailable 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 part may be reproduced except as authorized by written permission. Th

6、e copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2010. All rights 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

7、 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 Partners. GSM and the GSM logo are Trade Marks registered and owned by the

8、GSM Association. ETSI ETSI EG 202 237 V1.2.1 (2010-08)3Contents Intellectual Property Rights 6g3Foreword . 6g31 Scope 7g32 References 7g32.1 Normative references . 7g32.2 Informative references 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 9g34 Types of testing 9g34.

9、1 Interoperability testing . 9g34.2 Conformance testing. 10g34.3 Combining interoperability testing and conformance testing . 11g35 Interoperability testing process overview . 11g36 Basic concepts 12g36.1 Means of Testing 12g36.2 Equipment Under Test (EUT) 13g36.3 Qualified Equipment (QE) . 13g36.3.

10、1 QEs and Devices . 13g36.3.2 Designating the first QE . 13g36.4 System Under Test (SUT) 13g36.5 Test interface 14g36.6 Test driver 14g36.7 Test coordinator 14g36.8 Interoperability test cases . 14g36.9 Means of Communication 15g37 Generic interoperability test architectures 15g37.1 Test architectur

11、es with a single QE 15g37.2 Test architectures with multiple QEs 16g37.2.1 An example using 3 QEs 16g37.2.2 Testing IP hosts with multiple QEs 17g38 Developing interoperability tests 18g38.1 Overview 18g38.2 Specify abstract architecture. 19g38.3 Prepare draft IFS Proforma 19g38.4 Specify Test Suite

12、 Structure . 20g38.4.1 Identify test groups . 20g38.4.2 Define test coverage within each test group . 20g38.5 Write Test Purposes 21g38.6 Write test cases . 21g38.6.1 Pre-test conditions 21g38.6.2 Test steps and verdicts 22g38.6.2.1 Test steps . 22g38.6.2.2 Verdicts . 22g38.6.2.3 Specification of te

13、st steps and verdicts 22g38.6.3 Example 23g38.6.4 Pre-amble and post-amble 24g38.6.4.1 Alternative test case presentation forms 25g38.7 Validate test cases 26g38.8 Finalize IFS 26g39 Interoperability testing process 26g3ETSI ETSI EG 202 237 V1.2.1 (2010-08)49.1 Overview 26g39.2 Prepare for testing 2

14、7g39.2.1 Test arrangement 27g39.2.2 Test planning 28g39.3 Testing 29g39.3.1 Manual testing 29g39.3.2 Automated testing . 29g39.4 Write test report 29g3Annex A: Example IFS (Internet Key Exchange protocol, IKEv2) . 30g3A.1 Introduction 30g3A.2 Instructions for completing the IFS proforma 30g3A.2.1 Ge

15、neral structure of the IFS proforma 30g3A.2.2 Additional information . 30g3A.3 IFS proforma 31g3A.3.1 Implementation identification 31g3A.3.2 Protocol Summary, RFC 4306 . 31g3A.4 IKEv2 entities . 31g3A.4.1 Roles . 31g3A.4.2 IKEv2 Initiator functions 32g3A.4.2.1 IKE exchange types 32g3A.4.2.1.1 IKE S

16、A establishment functions . 32g3A.4.2.1.2 Child SA establishment functions . 32g3A.4.2.1.3 INFORMATIONAL exchange functions 33g3A.4.3 IKEv2 Responder functions . 33g3A.4.3.1 IKE exchange types 33g3A.4.3.1.1 IKE SA establishment functions . 33g3A.4.3.1.2 Child SA establishment functions . 34g3A.4.3.1

17、.3 INFORMATIONAL exchange functions 34g3Annex B: Example IFS (TIPHON Profile of SIP, Release 3) . 35g3B.1 Introduction 35g3B.2 Instructions for completing the IFS proforma 35g3B.2.1 General structure of the IFS proforma 35g3B.2.2 Additional information . 35g3B.3 IFS proforma 36g3B.3.1 Implementation

18、 identification 36g3B.3.2 Protocol Summary, EN 301 xxx . 36g3B.4 SIP entities 36g3B.4.1 Roles . 36g3B.4.2 User Agent capabilities 37g3B.4.2.1 Registration . 37g3B.4.2.2 Basic call . 37g3B.4.3 Registrar capabilities 38g3B.4.3.1 Registration . 38g3B.4.4 Proxy capabilities . 38g3B.4.4.1 Proxy in the se

19、rving and intermediate network. 38g3B.4.4.1.1 Registration . 38g3B.4.4.1.2 Basic call . 38g3B.4.4.2 Proxy in the home network . 39g3B.4.4.2.1 Registration . 39g3B.4.4.2.2 Basic call . 39g3B.4.5 Gateway capabilities. 39g3B.4.5.1 Basic call . 39g3ETSI ETSI EG 202 237 V1.2.1 (2010-08)5Annex C: Bibliogr

20、aphy 40g3History 41g3ETSI ETSI EG 202 237 V1.2.1 (2010-08)6Intellectual 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-members,

21、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:/webapp.etsi.org/IPR/home.asp).

22、 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 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 presen

23、t document. Foreword This ETSI Guide (EG) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). ETSI ETSI EG 202 237 V1.2.1 (2010-08)71 Scope The present document, “A generic approach to interoperability testing“, gives general guidance on the specification and e

24、xecution of interoperability tests for communication systems specifically in the context of product certification. It provides a framework within which interoperability test specifications for a wide range of product types can be developed. The guidelines are expressed as recommendations rather than

25、 strict rules and leave enough freedom to allow test specifiers to adopt and adapt processes to suit each particular project while still ensuring that test specifications accurately reflect the requirements of the base standards and can be executed consistently across a range of configurations. Inte

26、roperability testing is the structured and formal testing of functions supported remotely by two or more items of equipment communicating by means of standardized protocols. It is not the detailed verification of protocol requirements specified in a conformance test suite, neither is it the less for

27、mal development testing often associated with “plug-fest“ and “interop“ events (frequently referred to as “bake-offs“). A methodology for the latter type of testing is described in EG 202 810 i.8. Although some consideration is given within the methodology to the operating and reporting aspects of i

28、nteroperability testing, the primary focus of the present document is on the specification of interoperability testing architectures, test plans and test suites. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. F

29、or 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:/docbox.etsi.org/Ref

30、erence. 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. Not applicable. 2.2 Informative refe

31、rences The following 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 ETSI ES 201 873-1: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTC

32、N-3 Core Language“. i.2 Void. i.3 ETSI TS 101 884: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Technology Mapping; Implementation of TIPHON architecture using SIP“. i.4 ETSI EG 202 107: “Methods for Testing and Specification (MTS); Planning for validatio

33、n and testing in the standards-making process“. i.5 ISO/IEC 9646 (parts 1 to 7): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework“. i.6 IETF RFC 3261: “SIP: Session Initiation Protocol“. ETSI ETSI EG 202 237 V1.2.1 (2010-08)8i.7 IETF RFC 4306: “I

34、nternet Key Exchange (IKEv2) Protocol“. i.8 ETSI EG 202 810: “Methods for Testing and Specification (MTS); Automated Interoperability Testing; Methodology and Framework“. i.9 ETSI ES 202 553: “Methods for testing and Specification (MTS); TPLan: A notation for expressing test Purposes“. 3 Definitions

35、 and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: conformance: compliance with requirements specified in applicable standards ISO/IEC 9646 i.5 conformance testing: testing the extent to which an Implementation Under Test (IUT) sat

36、isfies both static and dynamic conformance requirements ISO/IEC 9646 i.5 NOTE: The purpose of conformance testing is to determine to what extent a single implementation of a particular standard conforms to the individual requirements of that standard. device: item of software or hardware which eithe

37、r alone or in combination with other devices implements the requirements of a standardized specification Equipment Under Test (EUT): grouping of one or more devices which has not been previously shown to interoperate with previously Qualified Equipment (QE) Implementation Under Test (IUT): an implem

38、entation of one or more Open Systems Interconnection (OSI) protocols in an adjacent user/provider relationship, being the part of a real open system which is to be studied by testing (ISO/IEC 9646-1 i.5) interoperability: ability of two systems to interoperate using the same communication protocol i

39、nteroperability testing: activity of proving that end-to-end functionality between (at least) two communicating systems is as required by the base standard(s) on which those systems are based interoperability test suite: collection of test cases designed to prove the ability of two (or more) systems

40、 to interoperate InterWorking Function (IWF): translation of one protocol into another one so that two systems using two different communication protocols are able to interoperate Qualified Equipment (QE): grouping of one or more devices that has been shown and certified, by rigorous and well-define

41、d testing, to interoperate with other equipment NOTE 1: Once an EUT has been successfully tested against a QE, it may be considered to be a QE, itself. NOTE 2: Once a QE is modified, it loses its status as QE and becomes again an EUT. System Under Test (SUT): one or more QEs and an EUT test case: sp

42、ecification of the actions required to achieve a specific test purpose, starting in a stable testing state, ending in a stable testing state and defined in either natural language for manual operation or in a machine-readable language (such as TTCN-3) for automatic execution test purpose: descriptio

43、n of a well-defined objective of testing, focussing on a single interoperability requirement or a set of related interoperability requirements ETSI ETSI EG 202 237 V1.2.1 (2010-08)93.2 Abbreviations For the purposes of the present document, the following abbreviations apply: API Application Programm

44、ing Interface EP End Point EUT Equipment Under Test GFT Graphical presentation Format for TTCN-3 IFS Interoperable Features Statement IUT Implementation Under Test IWF InterWorking Function MMI Man-Machine Interface MoC Means of Communication MoT Means of Testing OSI Open Systems Interconnection PIC

45、S Protocol Implementation Conformance Statement QE Qualified Equipment SIP Session Initiation Protocol SUT System Under Test TP Test Purpose TSS Test Suite Structure 4 Types of testing Equipment implementing standardized protocols and services can be formally tested in two related but different ways

46、, which each have benefits and limitations: conformance testing can show that a product correctly implements a particular standardized protocol: - establishes whether or not the implementation in question meets the requirements specified for the protocol itself. For example, it will test protocol me

47、ssage contents and format as well as the permitted sequences of messages. interoperability testing can demonstrate that a product will work with other like products: - assesses the ability of the implementation to support the required trans-network functionality between itself and another, similar i

48、mplementation to which it is connected. Conformance testing in conjunction with interoperability testing provides both the proof of conformance and the guarantee of interoperation. 4.1 Interoperability testing The term “interoperability testing“ is often used in relation to the semi-formal testing c

49、arried out at multi-vendor events as part of the product development process. While such events, often referred to as “plug-fests“, “interops“ and “bake-offs“, are valuable sources of information on the ability of similar products to communicate, they generally do not offer the structured and, therefore, repeatable, testing that is an essential part of a certification scheme. For a certification (or branding or logo) scheme to be meaningful, it is necessary that interoperability testing is carried out in accordance with a comprehensive and struct