ETSI TS 102 237-1-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4 Interoperability test methods and approaches Part 1 Generic approach _1.pdf

1、 ETSI TS 102 237-1 V4.1.1 (2003-12)Technical Specification Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON) Release 4;Interoperability test methods and approaches;Part 1: Generic approach to interoperability testingETSI ETSI TS 102 237-1 V4.1.1 (2003-12) 2 Reference DTS/T

2、IPHON-06025-1R4 Keywords H.323, interoperability, IP, SIP, telephony, testing, VoIP 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 Gr

3、asse (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 such versions, the

4、 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 subject to revision o

5、r 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, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by

6、written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON log

7、o are Trade Marks currently being registered by ETSI 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. ETSI ETSI TS 102 237-1 V4.1.1 (2003-12) 3 Contents Intellectual Property Rights6 Foreword.6 1 Scope 7

8、 2 References 7 3 Definitions and abbreviations.8 3.1 Definitions8 3.2 Abbreviations .8 4 Types of testing 9 4.1 Interoperability testing .9 4.2 Conformance testing.10 4.3 Combining interoperability testing and conformance testing.10 5 Interoperability testing process overview.12 6 Basic concepts12

9、6.1 Means of Testing13 6.2 Equipment Under Test (EUT) 13 6.3 Qualified Equipment (QE) .13 6.3.1 QEs and Devices.13 6.3.2 Designating the first QE .14 6.4 System Under Test (SUT) 14 6.5 Test interface 14 6.6 Test driver 14 6.7 Test coordinator15 6.8 Interoperability test cases .15 6.9 Means of Commun

10、ication 15 7 Generic interoperability test architectures15 7.1 Test architectures with a single QE 16 7.2 Test architectures with multiple QEs16 7.2.1 An example using 3 QEs 17 7.2.2 Testing IP hosts with multiple QEs 17 8 Developing interoperability tests18 8.1 Overview 18 8.2 Specify abstract arch

11、itecture.19 8.3 Prepare draft IFS Proforma 19 8.4 Specify Test Suite Structure .20 8.4.1 Identify test groups .20 8.4.2 Define test coverage within each test group .20 8.5 Write Test Purposes21 8.6 Write test cases.21 8.6.1 Pre-test conditions 21 8.6.2 Test steps and verdicts 21 8.6.2.1 Test steps.2

12、1 8.6.2.2 Verdicts .21 8.6.2.3 Specification of test steps and verdicts22 8.6.3 Example 22 8.6.4 Pre-amble and post-amble 23 8.6.4.1 Alternative test case presentation forms23 8.7 Validate test cases 28 8.8 Finalize IFS 28 9 Interoperability testing process 28 9.1 Overview 28 9.2 Prepare for testing

13、 29 ETSI ETSI TS 102 237-1 V4.1.1 (2003-12) 4 9.2.1 Test arrangement 29 9.2.2 Test planning 30 9.3 Testing30 9.3.1 Manual testing 30 9.3.2 Automated testing.31 9.4 Write test report31 Annex A (informative): Example IFS (TIPHON Profile of H.323, Release 3)32 A.1 Introduction 32 A.2 Instructions for c

14、ompleting the IFS proforma32 A.2.1 General structure of the IFS proforma32 A.2.2 Additional information.32 A.3 IFS proforma 33 A.3.1 Implementation identification 33 A.3.2 Protocol summary.33 A.4 H.323 entities .33 A.4.1 Roles.33 A.4.2 Terminal capabilities 34 A.4.2.1 Gatekeeper discovery34 A.4.2.2

15、Registration.34 A.4.2.3 Basic call.35 A.4.2.4 Supplementary services 35 A.4.3 Gatekeeper capabilities.35 A.4.3.1 Gatekeeper in the serving network .35 A.4.3.1.1 Overall capabilities35 A.4.3.1.2 Gatekeeper discovery35 A.4.3.1.3 Registration .36 A.4.3.1.4 Basic call.36 A.4.3.1.5 Supplementary services

16、.36 A.4.3.2 Gatekeeper in the intermediate network .36 A.4.3.2.1 Overall capabilities36 A.4.3.2.2 Gatekeeper discovery36 A.4.3.2.3 Registration .37 A.4.3.2.4 Basic call.37 A.4.3.2.5 Supplementary services.37 A.4.3.3 Gatekeeper in the home network 37 A.4.3.3.1 Overall capabilities37 A.4.3.3.2 Gatekee

17、per discovery37 A.4.3.3.3 Registration .38 A.4.3.3.4 Basic call.38 A.4.3.3.5 Supplementary services.38 A.4.4 Gateway capabilities.38 A.4.4.1 Overall capabilities .38 A.4.4.2 Basic call.39 A.4.4.3 Supplementary services 39 Annex B (informative): Example IFS (TIPHON Profile of SIP, Release 3)40 B.1 In

18、troduction 40 B.2 Instructions for completing the IFS proforma40 B.2.1 General structure of the IFS proforma40 B.2.2 Additional information.40 B.3 IFS proforma 41 B.3.1 Implementation identification 41 B.3.2 Protocol Summary, EN 301 xxx.41 B.4 SIP entities41 B.4.1 Roles.41 B.4.2 User Agent capabilit

19、ies 42 ETSI ETSI TS 102 237-1 V4.1.1 (2003-12) 5 B.4.2.1 Registration.42 B.4.2.2 Basic call.42 B.4.3 Registrar capabilities 43 B.4.3.1 Registration.43 B.4.4 Proxy capabilities .43 B.4.4.1 Proxy in the serving and intermediate network.43 B.4.4.1.1 Registration .43 B.4.4.1.2 Basic call.43 B.4.4.2 Prox

20、y in the home network.44 B.4.4.2.1 Registration .44 B.4.4.2.2 Basic call.44 B.4.5 Gateway capabilities.44 B.4.5.1 Basic call.44 Annex C (informative): Experimental testbed.45 C.1 Description of an experimental TIPHON H.323 - TIPHON SIP interoperability testbed .45 C.1.1 TIPHON H.323 - TIPHON SIP int

21、eroperability testing documentation 45 C.1.2 IP infrastructure46 C.1.3 Requirements for VoIP applications.47 C.1.4 Monitoring facilities .48 C.2 The experimental H.323-SIP testbed48 C.2.1 Components of the interoperability testbed48 C.2.1.1 Supporting companies.48 C.2.1.2 Open source software49 C.2.

22、2 Interoperability testing activities 49 C.2.3 Interoperability test specification documentation.49 C.2.4 Abstract architecture.50 C.2.5 Testing arrangements .50 C.2.5.1 BIT50 C.2.5.2 H.323 interoperability testing and SIP interoperability testing.51 C.2.5.3 H.323-SIP interoperability testing 52 C.2

23、.6 Logging 53 C.2.7 Example result matrices .53 C.2.8 Reporting54 Annex D (informative): Bibliography.55 History 56 ETSI ETSI TS 102 237-1 V4.1.1 (2003-12) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information p

24、ertaining 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 available from the ETSI Sec

25、retariat. 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 referenced in ETSI SR 000 314 (

26、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 Project Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON). The present document is part 1 of

27、 a multi-part deliverable covering Interoperability test methods and approaches, as identified below: Part 1: “Generic approach to interoperability testing“; Part 2: “H.323-SIP interoperability test scenarios to support multimedia communications in NGN environments“. ETSI ETSI TS 102 237-1 V4.1.1 (2

28、003-12) 7 1 Scope The present document, “A generic approach to interoperability testing“, gives general guidance on the specification and execution of interoperability tests for communication systems in Next Generation Networks (NGN). It provides a framework within which interoperability test specif

29、ications for a wide range of product types can be developed. The guidelines are expressed as recommendations rather than 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 accuratel

30、y reflect the requirements of the base standards and can be executed consistently across a range of configurations. Interoperability 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

31、not the detailed verification of protocol requirements specified in a conformance test suite, neither is it the less formal development testing often associated with plug-fest and interop events (frequently referred to as “bake-offs“). Although some consideration is given within the methodology to t

32、he operating and reporting aspects of interoperability testing, the primary focus of the present document is on the specification of interoperability testing architectures, test plans and test suites. 2 References The following documents contain provisions which, through reference in this text, cons

33、titute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced doc

34、uments which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ISO/IEC 9646 (parts 1 to 7): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework“. 2 IETF RFC 3261: “SIP: Session Initi

35、ation Protocol“. 3 ETSI EG 202 107: “Methods for Testing and Specification (MTS); Planning for validation and testing in the standards-making process“. 4 ETSI TS 102 237-2: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability Test Scenarios; Part

36、 2: H.323-SIP interoperability test scenarios to support multimedia communications in NGN environments“. 5 ITU-T Recommendation H.323: “Packet-based multimedia communications systems“. 6 ETSI TS 101 883: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Techno

37、logy Mapping; Implementation of TIPHON architecture using H.323“. 7 ETSI TS 101 884: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Technology Mapping; Implementation of TIPHON architecture using SIP“. ETSI ETSI TS 102 237-1 V4.1.1 (2003-12) 8 3 Definitions

38、 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 1 conformance testing: testing the extent to which an Implementation Under Test (IUT) satis

39、fies both static and dynamic conformance requirements ISO/IEC 9646 1 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 either alo

40、ne 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) interoperability: ability of two systems to int

41、eroperate using the same communication protocol interoperability 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 desig

42、ned to prove the ability of two (or more) systems 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

43、 shown, by rigorous and well-defined testing, to interoperate with other equipment NOTE: Once an EUT has been successfully tested against a QE, it may be considered to be a QE, itself. System Under Test (SUT): one or more QEs and an EUT 3.2 Abbreviations For the purposes of the present document, the

44、 following abbreviations apply: API Application Programming Interface BIT Basic Interconnection Tests EP End Point EUT Equipment Under Test GFT Graphical presentation Format for TTCN-3 GK GateKeeper ICS Implementation Conformance Statement IFS Interoperable Features Statement IUT Implementation Unde

45、r Test IWF InterWorking Function MMI Man-Machine Interface MoC Means of Communication MoT Means of Testing NDA Non-Disclosure Agreement NE Network Element NGN Next Generation Network PCO Point of Control and Observation PICS Protocol Implementation Conformance Statement QE Qualified Equipment ETSI E

46、TSI TS 102 237-1 V4.1.1 (2003-12) 9 SIP Session Initiation Protocol SUT System Under Test TE Terminal Element TP Test Purpose TSS Test Suite Structure 4 Types of testing Conformance testing establishes whether or not the implementation in question meets all of the requirements specified for the prot

47、ocol itself. For example, it will test protocol message contents and format as well as the permitted sequences of messages. Equipment implementing standardized protocols and services can be formally tested in two related but different ways. Individually, each of these test approaches has benefits an

48、d limitations. Conformance testing can show that a product correctly implements a particular standardized protocol while interoperability testing can demonstrate that it will work with other like products. Conformance testing prior to interoperability testing provides both the proof of conformance a

49、nd the guarantee of interoperation. Interoperability testing assesses the ability of the implementation to support the required trans-network functionality between itself and another, similar implementation to which it is connected. 4.1 Interoperability testing The term “interoperability testing“ is often used in relation to the semi-formal testing carried out at multi-vendor events as part of the product development process. While such events, often referred to as “plug-fest“, “interops“ and “bake-offs“, are valuable sources of information on the abilit