ITU-T X 291-1995 OSI Conformance Testing Methodology and Framework for Protocol Recommendations for ITU-T Applications - Abstract Test Suite Specification - Data Networks and Open nect.pdf

1、X.291 (04/95) INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS - OPEN SYSTEMS INTERCONNECTION - CONFORMANCE TESTING OS1 CONFORMANCE TESTING METHODOLOGY AND FRAMEWORK FOR PROTOCOL RECOMMENDATIONS TEST SUITE SPECIF

2、ICATION FOR ITU-T APPLICATIONS - ABSTRACT ITU-T Recommendation X.291 (Previously “CCIlT Recommendation“) ITU-T RECMN+X.291 95 M 48b2.591 Ob09287 T4L M FOREWORD The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The IT-T is re

3、sponsible for studying technical, operating and tariff questions and issuing Recommen- dations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study b

4、y the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. . The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). ITU-T Recommendation X.291 was revised by ITU-T Study Gro

5、up 7 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 10th of April 1995. NOTE In this Recommendation, the expression ?Administration? is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O ITU 1996 All rights res

6、erved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. KU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS (February 1994) ORGANIZ

7、ATION OF X-SERES RECOMMENDATIONS PUBLIC DATA NETWORKS Services and Facilities Subject area I Recommendation Series I X.1-X.19 Interfaces Transmission, Signalling and Switching Network Aspects X.20-X.49 X.50-X.89 X.90-X. 149 Administrative Arrangements OPEN SYSTEMS INTERCONNECTION Model and Notation

8、Service Definitions Connection-mode Protocol Specifications Connectionless-mode Protocol SDecifications X.180-X.199 x.200-x.209 X.2 10-X.2 19 X.220-X.229 X.230-X.239 PICS Proformas Protocol Identification Security Protocols X.240-X.259 X.260-X.269 X.270-X.279 Layer Managed Objects Conformance Testin

9、g INTERWORKING BETWEEN NETWORKS X.280-X.289 X.290-X.299 General I OS1 MANAGEMENT I x.700-x.799 I x.300-x.349 I SECURITY I X.800-X.849 I Mobile Data Transmission Systems Management MESSAGE HANDLING SYSTEMS DIRECTORY OS1 NETWORKING AND SYSTEM ASPECTS Networking X.350-X.369 X.370-X.399 X.400-X.499 x.50

10、0-x.599 X.600-X.649 Naming, Addressing and Registration Abstract Svntax Notation One (ASN. 1) X.650-X.679 X.680-X.699 OS1 APPLICATIONS Commitment, Concurrency and Recovery X.850-X.859 Transaction Processing Remote Owrations X.860-X. 879 X.880-X.899 OPEN DISTRIBUTED PROCESSING x.900-x.999 1 2 3 4 5 6

11、 7 8 9 10 11 12 13 14 15 CONTENTS Scope References Definitions Abbreviations . Compliance . Conformance requirements in OS1 base specifications . 6.2 General requirements 6.4 Multi-specification dependencies . 6.1 Introduction 6.3 Conformance clauses Requirements on ICs proformas Abstract Test Suite

12、 production process leading to conformance testing specifications . Conformance requirements and ICs proforma Test Suite Structure and Test Purposes (TSS b) testing by means of test methods which are specific to particular applications, protocols or systems, including testing by means other than PDU

13、 exchange. NOTE - This Recommendation applies fully to some but not all Physical layer protocols. Nevertheless, many of the concepts apply to ail protocols. 2 References The following Recommendations, and other references contain provisions which, through reference in this text, constitute provision

14、s of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendatio

15、ns and other references listed below. A list of currently valid ITU-T Recommendations is regularly published. ITU-T Recommendation X.200 (1994) I ISO/IEC 7498-1:1994, Informution technology - Open Systems Interconnection - Basic Reference Model: The Basic Model. ITU-T Recommendation X.210 (1993) I I

16、SODEC 10731:1994, Informution technology - Open Systems Interconnection - Conventions for the definition of OS1 services. - - *) Recommendation X.29 1 and ISO/iEC 9646-2, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract test sui

17、te specification, are technically aligned. Recommendation X.291 (04/95) 1 ITU-T RECMNtX=29L 95 486257L KILO9294 LB1 9 - CCITT Recommendation X.209 (1988), Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1). ISO/IEC 8825:1990, Information technology - Open Systems Intercon

18、nection - Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN. I). ITU-T Recommendation X.290 (19959, OS1 conformance testing methodology and framework for protocol Recommedtions for iTU-T applications - General concepts. ISO/IEC 9646-1 : 1994, Information technology - Open S

19、ystems Interconnection - Conformance testing methodology and framework - Part I: General concepts. CCITT Recommendation X.292 (1992), OS1 conformance testing methodology and framework for protocol Recommendations for CClT applications - The Tree and Tabular Combined Notation (WCN). ISO/IEC 9646-3: 1

20、992, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (WCN. ISO/IEC 9646-3: 1992 Amd 12), Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part

21、 3: The Tree and Tabular Combined Notation (lTCN) - Amendment I: TTCN extensions. ITU-T Recommendation X.293 (1995), OS1 conformance testing methodology and framework for protocol Recommendations for ITU-T applications - Test realization. ISO/IEC 9646-4: 1994, Information technology - Open Systems I

22、nterconnection - Conformance testing methodology and framework - Pari 4: Test realization. ITU-T Recommendation X.295 (1995), OS1 Conformance testing methodology and framework for protocol Recommendations for ITU-T applications - Protocol profile test specification. ISOhEC 9646-6: 1994, Information

23、technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification. ITU-T Recommendation X.29631, OS1 conformance testing methodology and framework for Protocol Recommendations for IT-T applications - Implementation conformance sta

24、tements. ISO/IEC 9646-7: 1995, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation conformance statement. - - - - - 3 Definitions For the purposes of this Recommendation, all the definitions given in Recommendation X.290 appl

25、y. 4 Abbreviations For the purposes of this Recommendation, the abbreviations given in Recommendation X.290 apply. The following abbreviations also apply to this Recommendation. ACSE Association Control Service Element ASE Application Service Element ASN. 1 ASP Abstract Service Primitive ATM Abstrac

26、t Test Method Abstract Syntax Notation One *) To be published. 3, Presently at the stage of draft. 2 Recommendation X.291 (04/95) ITU-T RECNN*X-2%1 95 4862591 Ob09295 018 ATS ICs IUT IXIT LT LTCF MPyT os1 PCO PCTR PDU RTS SAP SPyT SUT TCP TMP Abstract Test Suite Implementation Conformance Statement

27、Implementation under Test Implementation extra Information for Testing Lower Tester Lower Tester Control Function Multi-Party Testing Open Systems Interconnection Point of Control and Observation Protocol Conformance Test Report Protocol Data Unit Remote Transfer Service Service Access Point Single

28、Party Testing System under Test Test Coordination Procedures Test Management Protocol TSS shall be specified in a test notation standardized by ITU-T or ISO/IEC; shall satisfy all the requirements stated in clauses 9 to 15 inclusive; shall be within an IT-T or ISO/IEC published specification or, in

29、the absence of such a specification, shall be within a publicly available specification which is in the process of being standardized within ITU-T or ISO/IEC, which has the highest standardization status available, and which has the status of at least a Committee Draft or equivalent. NOTE - ATSs out

30、side the standardization process need to be submitted for international standardization before they can fully comply with this Recommendation, in order to ensure that they are subject to public scrutiny, correction and acceptance, internationally. 5.3 used, the ATS shall comply with Recommendation X

31、.292. It is recommended that the test notation used be the Tree and Tabular Combined Notation (TTCN). If TTCN is Recommendation X.291 (04/95) 3 ITU-T RECMNJX-291 95 9 4862593 Ob09296 T54 9 6 Conformance requirements in OS1 base specifications 6.1 Introduction The meaning of conformance in OS1 is dis

32、cussed in Recommendation X.290. It is necessary that there be an unambiguous and objective understanding of the conformance requirements of an OS1 base specification, as a prerequisite to the production of an ATS for that specification. Clauses 6 and 7 state the requirements on the relevant specifie

33、rs to ensure that there is such an understanding of the conformance requirements. Additional guidance is given in Appendix II. 6.2 General requirements 6.2.1 they should be stated separately from one another. 6.2.2 It shall be clear what conformance to the specification means, in the sense of what i

34、s required to be done (i.e. mandatory), what is permitted but not mandatory (Le. optional), and what is required not be done (i.e. prohibited), in order to conform to it. A clear distinction shall be made between static and dynamic conformance requirements. To avoid ambiguity, 6.2.3 For example, it

35、should be possible to look at a record of Protocol Data Unit (PDU) activity and decide whether or not it is valid with respect to the relevant specification. It shall always be decidable whether an instance of communication conforms dynamically or not. 6.3 Conformance clauses 6.3.1 object, shall inc

36、lude a conformance clause, which shall be expressed clearly and unambiguously. 6.3.2 Each base specification, which specifies an OS1 protocol, abstract syntax, encoding rules, or information Conformance clauses shall distinguish between the following categories of information: a) b) c) references to

37、 clauses which state dynamic conformance requirements; static conformance requirements concerning the implementation of the base specification itself; static conformance requirements concerning multi-specification dependencies (see 6.4). 6.3.3 proforma, shall be stated separately from the requiremen

38、ts on the implementation of the specification itself. The requirement to produce an Implementation Conformance Statement (ICs), in compliance with the ICs 6.3.4 The conformance clause of a protocol specification should also include a) the requirement to be able to accept all correct sequences of PDU

39、s received from peers, and respond with correct PDU sequences; the requirement to be able to respond correctly to all incorrect sequences of PDUs received; in connection oriented protocols, the option to support either the initiation of a connection or the acceptance of a connection, or both; in con

40、nectionless protocols, the option to support the transmission of a PDU, the receipt of a PDU, or both. b) c) d) 6.3.5 A checklist for what should be included or referenced in each conformance clause is given in Ii.5. 6.4 Multi-specification dependencies Multi-specification dependencies may be specif

41、ied by each base specification requiring the provision of non-mandatory features in one or more underlying base specifications. If multi-specification dependencies are to be included in an ICs proforma, the ICs proforma shall merely reflect the multi-specification dependencies specified in the confo

42、rmance clause of the corresponding base specification. 4 Recommendation X.291 (04195) ITU-T RECMN*X=291 95 tBb259L Ob09297 990 Multi-specification dependencies should usually be specified in terms of what elements of a given underlying service are required in order to support the given protocol or i

43、nformation object. In addition, each underlying protocol specification should specify which units of the protocol are required if a given element of service can be said to be supported. This refers to the functionality implied by the element of service, and does not in any way imply the existence of

44、 a service interface. NOTE -This is not conformance to service, but rather is an expression of the conditional requirements that result from the compliance of a protocol to its service definition. In cases where it is not possible to express dependencies through the underlying service, they can be s

45、pecified in terms of the units of the underlying protocol or other specification required to support the higher protocol (the referencing specification). Multi-specification dependencies should only be specified in a protocol specification if they are needed to preserve the integrity of that protoco

46、l. They should be avoided where they are really defining a profile. Multi-specification dependencies may also be specified in a similar way in information object specifications. 7 Requirements on ICs proformas 7.1 The specific requirements to be met by suppliers in respect of each ICs they are to pr

47、ovide, shall be stated in the relevant base specification. The specification of these requirements shall include an ICs proforma. The ICs proforma shall be in the form of a questionnaire to be completed by the supplier or implementor of an implementation of the relevant base specification. 7.2 The I

48、Cs proforma shall cover all major mandatory capabilities, all optional and conditional functions, elements of procedure, parameters, options, PDUs, timers, multi-specification dependencies and other capabilities identified in the base specification. 7.3 There shall be a well-defined mapping (by refe

49、rences) from the ICs proforma to the static conformance requirements. The expression of the static conformance requirements in the ICs proforma shall be consistent with the conformance clause of the base specification. 7.4 Recommendation X.296 provides requirements and guidance on the production of ICs proformas. 8 Abstract Test Suite production process leading to conformance testing specifications 8.1 In order to present the requirements and general guidance for specification of Abstract Test Suites (ATSs), it is useful to assume a normal form of the process of ATS productio