ITU-T Z 146-2006 Testing and Test Control Notation version 3 (TTCN-3) Using ASN 1 with TTCN-3 (Study Group 17)《测试和测试控制符号版本3 国际应急首选方案的支持(第17研究组)》.pdf

《ITU-T Z 146-2006 Testing and Test Control Notation version 3 (TTCN-3) Using ASN 1 with TTCN-3 (Study Group 17)《测试和测试控制符号版本3 国际应急首选方案的支持(第17研究组)》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Z 146-2006 Testing and Test Control Notation version 3 (TTCN-3) Using ASN 1 with TTCN-3 (Study Group 17)《测试和测试控制符号版本3 国际应急首选方案的支持(第17研究组)》.pdf（26页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Z.146TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2006) SERIES Z: LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS Formal description techniques (FDT) Testing and Test Control Notation (TTCN) Testing and Test Control Notation ve

2、rsion 3 (TTCN-3): Using ASN.1 with TTCN-3 ITU-T Recommendation Z.146 ITU-T Z-SERIES RECOMMENDATIONS LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS FORMAL DESCRIPTION TECHNIQUES (FDT) Specification and Description Language (SDL) Z.100Z.109 Application of formal description techn

3、iques Z.110Z.119 Message Sequence Chart (MSC) Z.120Z.129 Extended Object Definition Language (eODL) Z.130Z.139 Testing and Test Control Notation (TTCN) Z.140Z.149 User Requirements Notation (URN) Z.150Z.159 PROGRAMMING LANGUAGES CHILL: The ITU-T high level language Z.200Z.209 MAN-MACHINE LANGUAGE Ge

4、neral principles Z.300Z.309 Basic syntax and dialogue procedures Z.310Z.319 Extended MML for visual display terminals Z.320Z.329 Specification of the man-machine interface Z.330Z.349 Data-oriented human-machine interfaces Z.350Z.359 Human-machine interfaces for the management of telecommunications n

5、etworks Z.360Z.379 QUALITY Quality of telecommunication software Z.400Z.409 Quality aspects of protocol-related Recommendations Z.450Z.459 METHODS Methods for validation and testing Z.500Z.519 MIDDLEWARE Distributed processing environment Z.600Z.609 For further details, please refer to the list of I

6、TU-T Recommendations. ITU-T Rec. Z.146 (03/2006) i ITU-T Recommendation Z.146 Testing and Test Control Notation version 3 (TTCN-3): Using ASN.1 with TTCN-3 Summary This Recommendation defines the way of using ASN.1 as defined in ITU-T Recs X.680, X.681, X.682 and X.683 with TTCN-3 (Testing and Test

7、Control Notation 3) as defined in ITU-T Rec. Z.140. Content of this Recommendation has been moved into this separate Recommendation from ITU-T Rec. Z.140 (04/2003). Since then, corrections and editorial changes have been made and included in this Recommendation. Source ITU-T Recommendation Z.146 was

8、 approved on 16 March 2006 by ITU-T Study Group 17 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. Z.146 (03/2006) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication S

9、tandardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA)

10、, which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall wit

11、hin ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recomme

12、ndation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as

13、 “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendati

14、on may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval o

15、f this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent

16、 database. ITU 2006 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Z.146 (03/2006) iii CONTENTS Page 1 Scope . 1 2 References 1 3 Definitions and abbreviations 1 3.1 Definitions. 1 3.2 Abbreviations

17、. 1 4 Introduction. 2 5 General. 2 6 Amendments in the core language 2 7 Additional TTCN-3 types. 5 7.1 General . 5 7.2 Additional simple basic types and values . 5 7.3 Sub-typing of additional types . 6 8 ASN.1 and TTCN-3 type equivalents . 6 8.1 General . 6 8.2 Identifiers 7 9 ASN.1 data types and

18、 values. 7 9.1 General . 7 9.2 Scope of ASN.1 identifiers 12 10 Parameterization in ASN.1 . 12 11 Defining ASN.1 message templates 13 11.1 General . 13 11.2 ASN.1 receive messages using the TTCN-3 template syntax 13 11.3 Ordering of template fields 14 12 Encoding information 14 12.1 General . 14 12.

19、2 ASN.1 encoding attributes 14 12.3 ASN.1 variant attributes . 15 Annex A Additional BNF and static semantics 16 A.1 ASN.1 support 16 Annex B Pre-defined TTCN-3 functions 16 B.1 The Decompose function 16 Annex C Predefined object identifier components 17 BIBLIOGRAPHY 18 ITU-T Rec. Z.146 (03/2006) 1

20、ITU-T Recommendation Z.146 Testing and Test Control Notation version 3 (TTCN-3): Using ASN.1 with TTCN-3 1 Scope This Recommendation defines a normative way of using of ASN.1 as defined in ITU-T Recs X.680 2, X.681 3, X.682 4 and X.683 5 with TTCN-3. The harmonization of other languages with TTCN-3

21、is not covered by this Recommendation. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and

22、other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The

23、 reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. 1 ITU-T Recommendation Z.140 (2006), Testing and Test Control Notation version 3 (TTCN-3): Core language. 2 ITU-T Recommendation X.680 (2002), Information technology Abstr

24、act Syntax Notation One (ASN.1): Specification of basic notation. 3 ITU-T Recommendation X.681 (2002), Information technology Abstract Syntax Notation One (ASN.1): Information object specification. 4 ITU-T Recommendation X.682 (2002), Information technology Abstract Syntax Notation One (ASN.1): Cons

25、traint specification. 5 ITU-T Recommendation X.683 (2002), Information technology Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications. 6 ITU-T Recommendation X.690 (2002), Information technology ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical E

26、ncoding Rules (CER) and Distinguished Encoding Rules (DER). 7 ITU-T Recommendation X.691 (2002), Information technology ASN.1 encoding rules: Specification of Packed Encoding Rules (PER). 8 ITU-T Recommendation X.693 (2001), Information technology ASN.1 encoding rules: XML Encoding Rules (XER). 9 Vo

27、id. 10 ITU-T Recommendation T.100 (1988), International information exchange for interactive Videotex. 11 ITU-T Recommendation T.101 (1994), International interworking for Videotex services. 12 ITU-T Recommendation X.660 (2004), Information technology Open Systems Interconnection Procedures for the

28、operation of OSI registration authorities: General procedures and top arcs of the ASN.1 Object Identifier tree. 3 Definitions and abbreviations 3.1 Definitions For the purposes of this Recommendation, the terms and definitions given in ITU-T Rec. Z.140 1 apply. 3.2 Abbreviations For the purposes of

29、this Recommendation, the abbreviations given in ITU-T Rec. Z.140 1 and the following apply: ASN.1 Abstract Syntax Notation One 2 ITU-T Rec. Z.146 (03/2006) 4 Introduction When using ASN.1 with TTCN-3 all features of TTCN-3 and statements given in clause 4/Z.140 1 still apply. In addition, when suppo

30、rting this Recommendation, TTCN-3 becomes fully harmonized with ASN.1 which may be used with TTCN-3 modules as an alternative data type and value syntax. This Recommendation defines the use of ASN.1 in TTCN-3 modules. The approach used to combine ASN.1 and TTCN-3 could be applied to support the use

31、of other type and value systems with TTCN-3. However, the details of this are not defined in this Recommendation. TTCN-3 core language TTCN-3 User ASN.1 types “ASN.1:1997“ for ASN.1 version 1997; “ASN.1:1994“ for ASN.1 version 1994; “ASN.1:1988“ for Blue Book version of ASN.1. NOTE 1 Language identi

32、fiers “ASN.1:1997“, “ASN.1:1994“ and “ASN.1:1988“ refer to versions of ASN.1 based on superseded ITU-T Recommendations (including the base document and all published Amendments and Technical Corrigenda published so far amending the base document). The only purpose to include them into this Recommend

33、ation is to allocate unique identifiers if protocol modules based on these ASN.1 versions are used with TTCN-3. When ASN.1 version 1997 is supported, the support of Amendment 3 to ITU-T Rec. X.680 2 is not considered. NOTE 2 When “ASN.1:1988“ is supported, the ASN.1 items shall be imported from such

34、 modules according to the syntactical and semantical rules of ITU-T Rec. X.208 (Blue Book) When ASN.1 is used with TTCN-3, the keywords listed in 11.18/X.680 2 shall not be used as identifiers in a TTCN-3 module. ASN.1 keywords shall follow the requirements of ITU-T Rec. X.680 2. 6 Amendments in the

35、 core language When using ASN.1 definitions in TTCN-3 the amendments given in this clause to the TTCN-3 core language as defined in ITU-T Rec. Z.140 1 shall also apply. Clause numbers below refer to those in ITU-T Rec. Z.140 1. Clause 3.1 Definitions Change the definition “known types“: with the fol

36、lowing one: known types: set of defined types, imported ASN.1 types and other imported external types. Insert the following note after the definition “root type“: NOTE In case of types based on imported ASN.1 types, the root type is determined from the associated TTCN-3 type (see clause 8). ITU-T Re

37、c. Z.146 (03/2006) 3 Clause 3.2 Abbreviations Add the following abbreviation: ASN.1 Abstract Syntax Notation One Clause 7.1 Naming of modules Append to the end of the 1st sentence of the 1st paragraph: optionally followed by an object identifier. Add the following new note after NOTE 1: NOTE 2 Modul

38、e names may differ in the object identifier part only. However, in this case, due precaution has to be exercised at import to avoid name clash as prefixing of identifiers (see 7.5.8) is unable to resolve such kind of clashes. Clause 7.5.0 General Add the following new paragraph after the 2nd paragra

39、ph: If the object identifier is provided as part of the module name (from which the definitions are imported) in the import statement, this object identifier shall be used to identify the correct module. Clause 7.5.8 Add the following note after the 1st paragraph: NOTE 1 The rule to resolve name cla

40、shes within object identifier values is given in 6.1.0 item d). Clause 14.3 Template matching mechanisms Append objid to the list of types in the note to the 3rd paragraph: NOTE The following types may be omitted: . Clause 15.3 Relational operators Add objid to the list of types in the 1st paragraph

41、 for which relational operators are allowed (All other relational operators shall have only operands of type integer (including derivatives of integer), float (including derivations of float), objid .) Add a new paragraph after the 2nd paragraph: Two objid values are equal, if they have equal number

42、 of components and the numerical values at all positions are the same. The less than (), greater than or equal to (=) and less than or equal to ( c_etsiIN / returns true as c_etsiINNet has more components v_etsiInIso NULL , where is the ASN.1 Type reference converted according to 7.2. 22) Replace al

43、l references to open types with the metatype “OPEN TYPE“. 23) Replace ASN.1 types with their equivalents according to Table 2 and ASN.1 values with equivalent TTCN-3 values based on the associated types. Missing (i.e., implicitly omitted) optional fields in structured ASN.1 values of the types (SET,

44、 SEQUENCE, etc.) shall be explicitly omitted in the resulted structured TTCN-3 values (see Note 9). The metatype “OPEN TYPE“ has to be replaced by anytype. NOTE 1 Associated types alone do not contain all information needed for the correct encoding of values based on ASN.1 types. The way of handling

45、 the extra information needed by the system to provide correct encoding is implementation dependent and remains hidden for the user; its knowledge is not required to make valid TTCN-3 declarations or assignments involving imported ASN.1 types and values. NOTE 2 When importing ENUMERATED types, integ

46、er numbers assigned by the user to enumerations are also imported. NOTE 3 The data-value field of the EXTERNAL type may be encoded as a single-ASN.1-type, octet-aligned or arbitrary (see 8.18.1/X.690 6) at the discretion of the encoder; if the user wants to enforce one given form of encoding or want

47、s to allow only one specific encoding form at matching, it shall use the appropriate encoding attribute for the type or the given constant, variable, template or template field (see 11.3). NOTE 4 Inner subtyping shall be taken into account by the user when defining TTCN-3 values or templates based o

48、n an ASN.1 type constrained by inner subtyping. NOTE 5 Equivalence with the objid type is limited to the syntax to be used for value notations only. When encoding/decoding an objid value retrieved from an ASN.1 RELATIVE-OID value using an ASN.1 encoding rule, the encoding/decoding shall occur accord

49、ing to rules specified for the RELATIVE-OID type. NOTE 6 VisibleString, IA5String and UniversalString have their equivalent TTCN-3 types and are replaced directly. NOTE 7 Relational constraints shall be taken into account by the user when declaring values and templates (also may be handled by tools implicitly). NOTE 8 This replacement do not effect constraints applied to the “notation for the object class field type“ itself. NOTE 9 Missing optional fields in