ETSI TS 102 351-2005 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) IPv6 Testing Methodology and Framework (V2 1 1 Includes Diskette)《测试方法和规范(MTS) 互联网协_1.pdf

《ETSI TS 102 351-2005 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) IPv6 Testing Methodology and Framework (V2 1 1 Includes Diskette)《测试方法和规范(MTS) 互联网协_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 351-2005 Methods for Testing and Specification (MTS) Internet Protocol Testing (IPT) IPv6 Testing Methodology and Framework (V2 1 1 Includes Diskette)《测试方法和规范(MTS) 互联网协_1.pdf（50页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 351 V2.1.1 (2005-08)Technical Specification Methods for Testing and Specification (MTS);Internet Protocol Testing (IPT);IPv6 Testing: Methodology and Frameworkfloppy3 ETSI ETSI TS 102 351 V2.1.1 (2005-08) 2 Reference RTS/MTS-IPT-001-IPV6-Fwk Keywords IP, interoperability, methodology, t

2、esting, 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 Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present d

3、ocument 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 the Portable Document Format (PDF). In case of di

4、spute, 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. Information on the current status of this and other

5、 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 part may be reproduced except as authorized by w

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

7、 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 351 V2.1.1 (2005-08) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2

8、References 6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 The TTCN-3 Framework8 5 The IPv6 test development process8 5.1 Conformance testing methodology.10 5.2 Interoperability testing methodology .10 6 The Requirements Catalogue .10 6.1 Entries in the Requirements Catal

9、ogue 10 6.2 Naming IPv6 requirements.11 7 Developing test specifications12 7.1 Conformance test specifications.12 7.1.1 Test configurations .12 7.1.1.1 Naming IPv6 conformance test configurations .12 7.1.1.2 Naming IPv6 test components.12 7.1.2 Test Suite Structure and Test Purposes.13 7.1.2.1 Test

10、Suite Structure.13 7.1.2.1.1 Naming IPv6 test groups .13 7.1.2.2 Test Purposes 13 7.1.2.2.1 Naming IPv6 TPs 13 7.1.2.2.2 Using the TP Language .14 7.1.3 Test Suite development in TTCN-315 7.1.3.1 Storage of TTCN-3 elements 15 7.1.3.2 Test Cases .16 7.1.3.2.1 Naming TCs 17 7.1.3.3 Test case functions

11、 17 7.1.3.3.1 Naming TC functions 18 7.1.3.4 TP functions 18 7.1.3.4.1 Naming of TP functions 19 7.1.3.5 Preambles and Postambles 19 7.1.3.5.1 Naming of Preambles and Postambles 19 7.1.3.6 Test case selection.19 7.1.3.7 Test suite parameterization20 7.2 Interoperability test specifications20 7.2.1 T

12、est configurations .20 7.2.1.1 Naming IPv6 interoperability test configurations .20 7.2.1.2 Naming IPv6 test components.21 7.2.2 Test Suite Structure and Test Purposes.21 7.2.2.1 Test Suite Structure.21 7.2.2.1.1 Naming IPv6 test groups .21 7.2.2.2 Test Purposes 21 7.2.2.2.1 Naming IPv6 TPs 21 7.2.2

13、.2.2 Using the TP Language .22 7.3 Test Description development23 7.3.1 Naming Test Descriptions 23 7.3.2 Presentation of TDs 23 ETSI ETSI TS 102 351 V2.1.1 (2005-08) 4 8 The TTCN-3 ATS Repository and Library 24 8.1 TTCN-3 Library structure overview.24 8.1.1 Data types and values modules.25 8.1.2 Te

14、mplates modules .25 8.1.3 Modules of TTCN-3 functions25 8.1.3.1 Verdict control modules25 8.1.3.2 Synchronization module26 8.1.3.3 IPv6 behaviour modules27 8.1.4 Adding modules to the TTCN-3 Library 27 8.1.5 ATS Repository structure overview27 9 TTCN-3 naming conventions.28 10 TTCN-3 comment tags.29

15、 11 Interaction between the test system and the SUT.31 11.1 The Simple Control and Observation Protocol (SCOP) .31 11.1.1 Upper Tester Server (UTS).32 11.2 The Upper Tester Client (UTC) .32 Annex A (normative): A formal notation for expressing test purposes 34 A.1 Introduction to TPLan 34 A.2 TSS He

16、ader 35 A.3 Grouping.35 A.4 TP Header.36 A.5 TP body 36 A.5.1 The with statement.37 A.5.2 The when statement .37 A.5.3 The then statement.37 A.5.4 Other behavioural statements .38 A.6 The TPLan Grammar38 Annex B (informative): TTCN-3 library modules.41 B.1 Electronic annex, zip file with TTCN-3 code

17、 41 Annex C (normative): SCOP type definitions and encodings 42 C.1 The Protocol Type Definition.42 C.2 Encoding of SCOP .43 Annex D (informative): The IPv6 requirements database46 History 50 ETSI ETSI TS 102 351 V2.1.1 (2005-08) 5 Intellectual Property Rights IPRs essential or potentially essential

18、 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, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified t

19、o 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 Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be g

20、iven 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 Technical Specification (TS) has been produced by ETSI Technical Committee Methods for Testing and Sp

21、ecification (MTS). ETSI ETSI TS 102 351 V2.1.1 (2005-08) 6 1 Scope The present document gives guidelines for the use of a common method for developing test specifications for IPv6. This method is applicable to all IPv6 categories including the core specification, mobility, security and transitioning

22、 to IPv6 from IPv4. The underlying method is based on the methodologies specified in ISO/IEC 9646-1 4 for conformance tests and TS 102 237-1 1 for interoperability tests. It provides guidance on the development and use of the following key elements of the method: - a Requirements Catalogue (RC); - a

23、 Test Suite Structure (TSS) and Test Purposes (TP); - Test Descriptions (TD) - interoperability; - a TTCN-3 library of data types and values, templates and functions; - an Abstract Test Suite (ATS) - conformance. The methodology also offers guidance on naming conventions and other style-related issu

24、es. Although the present document has been developed primarily for use in the testing of IPv6 standards, it could equally be used in other areas of protocol test specification. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the

25、 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 documents which are not fou

26、nd to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI TS 102 237-1 (V4.1.1): “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability test methods and approaches; Part 1: Generic approach to in

27、teroperability testing“. 2 ETSI EG 202 106 (V2.1.1): “Methods for Testing and Specification (MTS); Guidelines for the use of formal SDL as a descriptive tool“. 3 ETSI ES 201 873-6 (V3.1.1): “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3

28、Control Interface (TCI)“. 4 ISO/IEC 9646-1 (1992): “Information Technology - Open Systems Interconnection - Conformance Testing Methodology and Framework - Part 1: General concepts“. 5 IETF RFC 1035 (1997): “Domain names - implementation and specification“. ETSI ETSI TS 102 351 V2.1.1 (2005-08) 7 3

29、Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: behavioural function: TTCN-3 function which specifies actions which result in the sending of messages to one or more observed interface computational function: TTCN-3 fu

30、nction which specifies actions which modifies data values but does not result in the sending of messages to one or more observed interface Equipment Under Test (EUT): grouping of one or more devices which has not been previously shown to interoperate with previously Qualified Equipment (QE) TS 102 2

31、37-1 1 Qualified Equipment (QE): grouping of one or more devices that has been shown, by rigorous and well-defined testing, to interoperate with other equipment TS 102 237-1 1 NOTE: Once an EUT has been successfully tested against a QE, it may be considered to be a QE, itself. 3.2 Abbreviations For

32、the purposes of the present document, the following abbreviations apply: 3GPP 3rdGeneration mobile Partnership Project API Application Programming Interface ATS Abstract Test Suite EUT Equipment Under Test IETF Internet Engineering Task Force IFS Interoperable Functions Statement IPv4 Internet Proto

33、col version 4 IPv6 Internet Protocol version 6 IUT Implementation Under Test MTC Main Test Component NGN Next Generation Network PICS Protocol Implementation Conformance Statement PTC Parallel Test Component QE Qualified Equipment RC Requirements Catalogue RFC Request For Comments (IETF terminology

34、for a draft standard) RQ Requirement SCOP Simple Control and Observation Protocol SUT System Under Test TISPAN ETSI technical body with responsibility for NGN standardization TC Test Case TCI TTCN-3 Control Interface TD Test Description TE Test EquipmentTP Test Purpose TSS Test Suite Structure TTCN-

35、3 Testing and Test Control Notation edition 3 UDP User Datagram Protocol UT Upper Tester UTC Upper Tester Client UTS Upper Tester Server ETSI ETSI TS 102 351 V2.1.1 (2005-08) 8 4 The TTCN-3 Framework ETSI test specifications are usually developed for a single base protocol standard or for a coherent

36、 set of standards. As such, it is possible to follow the methodology specified for conformance test development in ISO/IEC 9646-1 4 without much difficulty. However, the requirements of IPv6 are distributed across a wide range of documents and an adaptation of the ISO/IEC 9646 approach to test devel

37、opment is necessary. Also, for readability, consistency and to ease reusability of TTCN-3 code it is necessary to apply some guidelines on the use of TTCN-3. It is this approach that is referred to as the “TTCN-3 Framework“. As its name implies, the framework is oriented towards the production of Ab

38、stract Test Suites (ATS) in the Testing and Test Control Notation edition 3 (TTCN-3). The TTCN-3 Framework comprises: a documentation structure: - catalogue of requirements; - Test Suite Structure (TSS); - Test Purposes (TP): square4 conformance; square4 interoperability; Abstract Test Suite (ATS):

39、- Test Cases (TC) in TTCN-3 for conformance tests; - Test Descriptions (TD) in tabulated English for interoperability tests; library of TTCN-3 building blocks: - data types and values; - templates; - general computational functions; - TP functions (see clause 7.1.3.3); a methodology linking the indi

40、vidual documentation, library and ATS elements together: - style guidelines and examples; - naming conventions; - guidelines on the use and extension of the TTCN-3 library; - a structured notation for TPs. The TTCN-3 Framework, particularly the methodology, draws heavily on the tried and tested ISO/

41、IEC 9646-1 4 but modifies it to suit the particular case of IPv6 testing. It also incorporates guidelines on interoperability testing taken from TS 102 237-1 1. 5 The IPv6 test development process The process to be followed when developing IPv6 test specifications is shown in figure 1. ETSI ETSI TS

42、102 351 V2.1.1 (2005-08) 9 Interoperability Test SuiteInteroperability Test SuiteInteroperability Test Suite1 or more TCs1 ATS1 or more TCs1 ATS1 TP Function Group1 Test CaseI Test Description1 Test Case1 TP1 TP Function Group1 TP1 TP Function Group1 Requirement1 or more TPsWrite TP FunctionsCollect

43、RequirementsWrite Test Purposes1 Requirement1 or more TPsRequirements CatalogueTSS existing test documentation from the IPv6 Forum and other established sources; specifications related to the use of IPv6 in 3rdGeneration mobile networks. The result of this analysis is the identification and classifi

44、cation of a full range of IPv6 requirements which is recorded in the Requirements Catalogue and used as the basis for both conformance and interoperability test specifications. 5.1 Conformance testing methodology Conformance test specifications should be produced following the methodology described

45、in ISO/IEC 9646-1 4. In summary, this methodology begins with the collation and categorization of the requirements to be tested into a tabular form which is normally referred to as the “Protocol Implementation Conformance Statement“ (PICS). Each PICS relates to a specific protocol standard. As the r

46、equirements of IPv6 are distributed across a large number of documents, there would be very little benefit in producing a PICS for each document. Consequently, the IPv6 requirements will be collected together and categorized in a single document, the Requirements Catalogue. For each requirement in t

47、he catalogue, one or more tests should be identified and classified into a number of groups which will provide a structure to the overall test suite (TSS). A brief Test Purpose (TP) should then be written for each identified test and this should make it clear what is to be tested but not how this sh

48、ould be done. Finally, a detailed Test Case (TC) is written for each TP. In the interests of test automation, TCs are usually combined into an Abstract Test Suite (ATS) using a specific testing language such as TTCN-3. 5.2 Interoperability testing methodology For a certification (or branding or logo

49、) scheme to be meaningful, it is necessary that interoperability testing is carried out in addition to conformance testing and that this is done in accordance with a comprehensive and structured suite of tests. In the context of the present document, it is this type of testing which is referred to as “Interoperability Testing“. The purpose of interoperability testing is to prove that the end-to-end functionality between (at least) two communicating systems is as required by the standard(s) on which those systems are based. A methodolo