1、 Reference numberISO/IEC 8824-4:2002(E)ISO/IEC 2002INTERNATIONAL STANDARD ISO/IEC8824-4Third edition2002-12-15Information technology Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specificationsTechnologies de linformation Notation de syntaxe abstraite numro un (ASN.1): Paramtrage d
2、es spcifications ASN.1 Adopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard.Date of ANSI Approval: 12/28/2004Published by American National Standards Institute,25 West 43rd Street, New York, New York 10036Copyright 2004 by Information Tech
3、nology Industry Council (ITI).All rights reserved.These materials are subject to copyright claims of International Standardization Organization (ISO), InternationalElectrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council(ITI). Not f
4、or resale. No part of this publication may be reproduced in any form, including an electronic retrieval system, withoutthe prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1250 Eye Street NW,Washington, DC 20005.Printed in the United States of Ame
5、ricaISO/IEC 8824-4:2002(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing.
6、 In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be foun
7、d in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the
8、address given below. ISO/IEC 2002 All rights reserved. Unless otherwise specified, 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 either ISO at the address below
9、 or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published by ISO in 2003 Published in Switzerland ii ISO/IEC 2002 All rights reservedISO/IEC 8824-4:2002(E
10、) ISO/IEC 2002 All rights reserved iiiCONTENTS Page Introduction . v 1 Scope 1 2 Normative references . 1 2.1 Identical Recommendations | International Standards 1 3 Definitions 1 3.1 Specification of basic notation 1 3.2 Information object specification 1 3.3 Constraint specification. 1 3.4 Additio
11、nal definitions 1 4 Abbreviations . 2 5 Convention . 2 6 Notation 2 6.1 Assignments 2 6.2 Parameterized definitions 2 6.3 Symbols. 3 7 ASN.1 lexical items 3 8 Parameterized assignments. 3 9 Referencing parameterized definitions. 5 10 Abstract syntax parameters. 8 Annex A Examples. 9 A.1 Example of t
12、he use of a parameterized type definition . 9 A.2 Example of use of parameterized definitions together with an information object class 9 A.3 Example of parameterized type definition that is finite 10 A.4 Example of a parameterized value definition 11 A.5 Example of a parameterized value set definit
13、ion. 11 A.6 Example of a parameterized class definition. 11 A.7 Example of a parameterized object set definition . 12 A.8 Example of a parameterized object set definition . 12 Annex B Summary of the notation . 13 ISO/IEC 8824-4:2002(E) iv ISO/IEC 2002 All rights reservedForeword ISO (the Internation
14、al Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by
15、 the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of
16、 information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft Inte
17、rnational Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this docume
18、nt may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 8824-4 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 6, Telecommunications and information exchange between syst
19、ems, in collaboration with ITU-T. The identical text is published as ITU-T Rec. X.683. This third edition cancels and replaces the second edition (ISO/IEC 8824-4:1998), which has been technically revised. It also incorporates the Amendment ISO/IEC 8824-4:1998/Amd.1:2000. ISO/IEC 8824 consists of the
20、 following parts, under the general title Information technology Abstract Syntax Notation One (ASN.1): Part 1: Specification of basic notation Part 2: Information object specification Part 3: Constraint specification Part 4: Parameterization of ASN.1 specifications ISO/IEC 8824-4:2002(E) ISO/IEC 200
21、2 All rights reserved vIntroduction Application designers need to write specifications in which certain aspects are left undefined. Those aspects will later be defined by one or more other groups (each in its own way), to produce a fully defined specification for use in the definition of an abstract
22、 syntax (one for each group). In some cases, aspects of the specification (for example, bounds) may be left undefined even at the time of abstract syntax definition, being completed by the specification of International Standardized Profiles or functional profiles from some other body. NOTE 1 It is
23、a requirement imposed by this Recommendation | International Standard that any aspect that is not solely concerned with the application of constraints has to be completed prior to the definition of an abstract syntax. In the extreme case, some aspects of the specification may be left for the impleme
24、ntor to complete, and would then be specified as part of the Protocol Implementation Conformance Statement. While the provisions of ITU-T Rec. X.681 | ISO/IEC 8824-2 and ITU-T Rec. X.682 | ISO/IEC 8824-3 provide a framework for the later completion of parts of a specification, they do not of themsel
25、ves solve the above requirements. Additionally, a single designer sometimes requires to define many types, or many information object classes, or many information object sets, or many information objects, or many values, which have the same outer level structure, but differ in the types, or informat
26、ion object classes, or information object sets, or information objects, or values, that are used at an inner level. Instead of writing out the outer level structure for every such occurrence, it is useful to be able to write it out once, with parts left to be defined later, then to refer to it and p
27、rovide the additional information. All these requirements are met by the provision for parameterized reference names and parameterized assignments by this Recommendation | International Standard. The syntactic form of a parameterized reference name is the same as that of the corresponding normal ref
28、erence name, but the following additional considerations apply: When it is assigned in a parameterized assignment statement, it is followed by a list of dummy reference names in braces, each possibly accompanied by a governor; these reference names have a scope which is the right-hand side of the as
29、signment statement, and the parameter list itself. NOTE 2 This is what causes it to be recognized as a parameterized reference name. When it is exported or imported, it is followed by a pair of empty braces to distinguish it as a parameterized reference name. When it is used in any construct, it is
30、followed by a list of syntactic constructions, one for each dummy reference name, that provide an assignment to the dummy reference name for the purposes of that use only. Dummy reference names have the same syntactic form as the corresponding normal reference name, and can be used anywhere on the r
31、ight-hand side of the assignment statement that the corresponding normal reference name could be used. All such usages are required to be consistent. ISO/IEC 8824-4:2003 (E) ITU-T Rec. X.683 (07/2002) 1 INTERNATIONAL STANDARD ISO/IEC 8824-4 : 1995 (E) ITU-T Rec. X.683 (1994 E) ITU-T RECOMMENDATION I
32、nformation technology Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications 1 Scope This Recommendation | International Standard is part of Abstract Syntax Notation One (ASN.1) and defines notation for parameterization of ASN.1 specifications. 2 Normative references The foll
33、owing Recommendations and International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated were valid. All Recommendations and Standards are subject to revision,
34、 and parties to agreements based on this Recommendation | International Standard are encouraged to investigate the possibility of applying the most recent edition of the Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently valid International Standards.
35、The Telecommunication Standardization Bureau of the ITU maintains a list of currently valid ITU-T Recommendations. 2.1 Identical Recommendations | International Standards ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-1:2002, Information technology Abstract Syntax Notation One (ASN.1): Specificati
36、on of basic notation. ITU-T Recommendation X.681 (2002) | ISO/IEC 8824-2:2002, Information technology Abstract Syntax Notation One (ASN.1): Information object specification. ITU-T Recommendation X.682 (2002) | ISO/IEC 8824-3:2002, Information technology Abstract Syntax Notation One (ASN.1): Constrai
37、nt specification. 3 Definitions For the purposes of this Recommendation | International Standard, the following definitions apply. 3.1 Specification of basic notation This Recommendation | International Standard uses the terms defined in ITU-T Rec. X.680 | ISO/IEC 8824-1. 3.2 Information object spec
38、ification This Recommendation | International Standard uses the terms defined in ITU-T Rec. X.681 | ISO/IEC 8824-2. 3.3 Constraint specification This Recommendation | International Standard uses the terms defined in ITU-T Rec. X.682 | ISO/IEC 8824-3. 3.4 Additional definitions 3.4.1 normal reference
39、 name: A reference name defined, without parameters, by means of an “Assignment“ other than a “ParameterizedAssignment“. Such a name references a complete definition and is not supplied with actual parameters when used. 3.4.2 parameterized reference name: A reference name defined using a parameteriz
40、ed assignment, which references an incomplete definition and which, therefore, must be supplied with actual parameters when used. ISO/IEC 8824-1:2002 (E)ISO/IEC 8824-4:2002 (E)ISO/IEC 8824-4:2003 (E) 2 ITU-T Rec. X.683 (07/2002) 3.4.3 parameterized type: A type defined using a parameterized type ass
41、ignment and thus whose components are incomplete definitions which must be supplied with actual parameters when the type is used. 3.4.4 parameterized value: A value defined using a parameterized value assignment and thus whose value is incompletely specified and must be supplied with actual paramete
42、rs when used. 3.4.5 parameterized value set: A value set defined using a parameterized value set assignment and thus whose values are incompletely specified and must be supplied with actual parameters when used. 3.4.6 parameterized object class: An information object class defined using a parameteri
43、zed object class assignment and thus whose field specifications are incompletely specified and must be supplied with actual parameters when used. 3.4.7 parameterized object: An information object defined using a parameterized object assignment and thus whose components are incompletely specified and
44、 must be supplied with actual parameters when used. 3.4.8 parameterized object set: An information object set defined using a parameterized object set assignment and thus whose objects are incompletely specified and must be supplied with actual parameters when used. 3.4.9 variable constraint: A cons
45、traint employed in specifying a parameterized abstract syntax, and which depends on some parameter of the abstract syntax. 4 Abbreviations For the purposes of this Recommendation | International Standard, the following abbreviation applies: ASN.1 Abstract Syntax Notation One 5 Convention This Recomm
46、endation | International Standard employs the notational convention defined in ITU-T Rec. X.680 | ISO/IEC 8824-1, clause 5. 6 Notation This clause summarizes the notation defined in this Recommendation | International Standard. 6.1 Assignments The following notation which can be used as an alternati
47、ve for “Assignment“ (see ITU-T Rec. X.680 | ISO/IEC 8824-1, clause 12) is defined in this Recommendation | International Standard: ParameterizedAssignment (see 8.1). 6.2 Parameterized definitions 6.2.1 The following notation which can be used as an alternative for “DefinedType“ (see ITU-T Rec. X.680
48、 | ISO/IEC 8824-1, 13.1) is defined in this Recommendation | International Standard: ParameterizedType (see 9.2). 6.2.2 The following notation which can be used as an alternative for “DefinedValue“ (see ITU-T Rec. X.680 | ISO/IEC 8824-1, 13.1) is defined in this Recommendation | International Standa
49、rd: ParameterizedValue (see 9.2). 6.2.3 The following notation which can be used as an alternative for “DefinedType“ (see ITU-T Rec. X.680 | ISO/IEC 8824-1, 13.1) is defined in this Recommendation | International Standard: ParameterizedValueSetType (see 9.2). 6.2.4 The following notation which can be used as an alternative for “ObjectClass“ (see ITU-T Rec. X.681 | ISO/IEC 8824-2, 9.2) is defined in this Recommendation | International Standard: ParameterizedObjectClass (see 9.2). ISO/IEC 8824-1:2002 (E)ISO/IE
