Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules (PER) — Part 2:

ISO/IEC 8825-2:2008 specifies a set of Packed Encoding Rules that can be used to derive a transfer syntax for values of types defined in ISO/IEC 8824-1. These Packed Encoding Rules can also be applied for decoding such a transfer syntax in order to identify the data values being transferred. The encoding rules specified in ISO/IEC 8825-2:2008: are used at the time of communication; are intended for use in circumstances where minimizing the size of the representation of values is the major concern in the choice of encoding rules; allow the extension of an abstract syntax by addition of extra values, preserving the encodings of the existing values, for all forms of extension described in ISO/IEC 8824-1; can be modified in accordance with the provisions of ISO/IEC 8825-6.

Technologies de l'information — Règles de codage ASN.1: Spécification des règles de codage compact (PER) — Partie 2:

General Information

Status
Withdrawn
Publication Date
14-Dec-2008
Withdrawal Date
14-Dec-2008
Current Stage
9599 - Withdrawal of International Standard
Completion Date
12-Nov-2015
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 8825-2:2008 - Information technology -- ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)
English language
64 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 8825-2
Fourth edition
2008-12-15


Information technology — ASN.1
encoding rules: Specification of Packed
Encoding Rules (PER)
Technologies de l'information — Règles de codage ASN.1:
Spécification des règles de codage compact (PER)




Reference number
ISO/IEC 8825-2:2008(E)
©
ISO/IEC 2008

---------------------- Page: 1 ----------------------
ISO/IEC 8825-2:2008(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's 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. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's 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 found 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 address given below.


COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2008
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 or
ISO's 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 copyright@iso.org
Web www.iso.org
Published by ISO in 2009
Published in Switzerland

ii © ISO/IEC 2008 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 8825-2:2008(E)

CONTENTS
Page
Foreword .vi

Introduction .vii
1 Scope. 1
2 Normative references . 1
2.1 Identical Recommendations | International Standards . 1
2.2 Additional references . 1
3 Definitions. 2
3.1 Specification of Basic Notation . 2
3.2 Information Object Specification. 2
3.3 Constraint Specification. 2
3.4 Parameterization of ASN.1 Specification .2
3.5 Basic Encoding Rules . 2
3.6 PER Encoding Instructions . 2
3.7 Additional definitions . 2
4 Abbreviations . 5
5 Notation. 5
6 Convention . 5
7 Encoding rules defined in this Recommendation | International Standard. 5
8 Conformance . 6
9 PER encoding instructions . 6
10 The approach to encoding used for PER. 7
10.1 Use of the type notation . 7
10.2 Use of tags to provide a canonical order. 7
10.3 PER-visible constraints . 7
10.4 Type and value model used for encoding .9
10.5 Structure of an encoding . 9
10.6 Types to be encoded. 10
11 Encoding procedures. 10
11.1 Production of the complete encoding. 10
11.2 Open type fields . 11
11.3 Encoding as a non-negative-binary-integer . 11
11.4 Encoding as a 2's-complement-binary-integer . 12
11.5 Encoding of a constrained whole number. 12
11.6 Encoding of a normally small non-negative whole number. 13
11.7 Encoding of a semi-constrained whole number . 13
11.8 Encoding of an unconstrained whole number. 14
11.9 General rules for encoding a length determinant . 14
12 Encoding the boolean type . 16
13 Encoding the integer type. 17
14 Encoding the enumerated type . 17
15 Encoding the real type. 18
16 Encoding the bitstring type. 18
17 Encoding the octetstring type. 19
18 Encoding the null type. 20
19 Encoding the sequence type . 20
20 Encoding the sequence-of type. 21
21 Encoding the set type . 21
© ISO/IEC 2008 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 8825-2:2008(E)
22 Encoding the set-of type. 22
23 Encoding the choice type . 22
24 Encoding the object identifier type . 23
25 Encoding the relative object identifier type. 23
26 Encoding the internationalized resource reference type. 23
27 Encoding the relative internationalized resource reference type.23
28 Encoding the embedded-pdv type . 23
29 Encoding of a value of the external type. 24
30 Encoding the restricted character string types. 25
31 Encoding the unrestricted character string type . 26
32 Encoding the time type, the useful time types, the defined time types and the additional time types. 27
32.1 General. 27
32.2 Encoding subtypes with the "Basic=Date" property setting . 31
32.3 Encoding subtypes with the "Basic=Time" property setting. 33
32.4 Encoding subtypes with the "Basic=Date-Time" property setting. 36
32.5 Encoding subtypes with the "Basic=Interval Interval-type=SE" property setting. 36
32.6 Encoding subtypes with the "Basic=Interval Interval-type=D" property setting. 37
32.7 Encoding subtypes with the "Basic=Interval Interval-type=SD" or
"Basic=Interval Interval-type=DE" property setting. 38
32.8 Encoding subtypes with the "Basic=Rec-Interval Interval-type=SE" property setting39
32.9 Encoding subtypes with the "Basic=Rec-Interval Interval-type=D" property setting39
32.10 Encoding subtypes with the "Basic=Rec-Interval Interval-type=SD" or
"Basic=Rec-Interval Interval-type=DE" property setting. 40
32.11 Encoding subtypes with mixed settings of the Basic property. 41
33 Object identifiers for transfer syntaxes . 43
Annex A Example of encodings. 44
A.1 Record that does not use subtype constraints. 44
A.1.1 ASN.1 description of the record structure. 44
A.1.2 ASN.1 description of a record value. 44
A.1.3 ALIGNED PER representation of this record value . 44
A.1.4 UNALIGNED PER representation of this record value . 45
A.2 Record that uses subtype constraints. 47
A.2.1 ASN.1 description of the record structure. 47
A.2.2 ASN.1 description of a record value. 47
A.2.3 ALIGNED PER representation of this record value . 47
A.2.4 UNALIGNED PER representation of this record value . 48
A.3 Record that uses extension markers . 49
A.3.1 ASN.1 description of the record structure. 49
A.3.2 ASN.1 description of a record value. 50
A.3.3 ALIGNED PER representation of this record value . 50
A.3.4 UNALIGNED PER representation of this record value . 52
A.4 Record that uses extension addition groups. 53
A.4.1 ASN.1 description of the record structure. 53
A.4.2 ASN.1 description of a record value. 54
A.4.3 ALIGNED PER representation of this record value . 54
A.4.4 UNALIGNED PER representation of this record value . 54
Annex B Combining PER-visible and non-PER-visible constraints . 56
B.1 General. 56
B.2 Extensibility and visibility of constraints in PER . 56
B.2.1 General. 56
B.2.2 PER-visibility of constraints . 57
B.2.3 Effective constraints. 58
B.3 Examples. 59
Annex C Support for the PER algorithms . 61
iv © ISO/IEC 2008 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 8825-2:2008(E)
Annex D Support for the ASN.1 rules of extensibility. 62

Annex E Tutorial annex on concatenation of PER encodings. 63

Annex F Identification of Encoding Rules . 64

© ISO/IEC 2008 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 8825-2:2008(E)
Foreword
ISO (the International 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 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 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 International
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 document 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 8825-2 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 6, Telecommunications and information exchange between systems, in collaboration with
ITU-T. The identical text is published as Rec. ITU-T X.691 (11/2008).
This fourth edition cancels and replaces the third edition (ISO/IEC 8825-2:2002), which has been technically
revised. It also incorporates the Amendments ISO/IEC 8825-2:2002/Amd.1:2004,
ISO/IEC 8825-2:2002/Amd.2:2007 and ISO/IEC 8825-2:2002/Amd.3:2008, and the Technical Corrigenda
ISO/IEC 8825-2:2002/Cor.1:2006 and ISO/IEC 8825-2:2002/Cor.2:2006.
ISO/IEC 8825 consists of the following parts, under the general title Information technology — ASN.1
encoding rules:
⎯ Part 1: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished
Encoding Rules (DER)
⎯ Part 2: Specification of Packed Encoding Rules (PER)
⎯ Part 3: Specification of Encoding Control Notation (ECN)
⎯ Part 4: XML Encoding Rules (XER)
⎯ Part 5: Mapping W3C XML schema definitions into ASN.1
⎯ Part 6: Registration and application of PER encoding instructions


vi © ISO/IEC 2008 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 8825-2:2008(E)
Introduction
The publications ITU-T Rec. X.680 | ISO/IEC 8824-1, ITU-T Rec. X.681 | ISO/IEC 8824-2, ITU-T Rec. X.682 |
ISO/IEC 8824-3, ITU-T Rec. X.683 | ISO/IEC 8824-4 together describe Abstract Syntax Notation One (ASN.1), a

notation for the definition of messages to be exchanged between peer applications.
This Recommendation | International Standard defines encoding rules that may be applied to values of types defined

using the notation specified in ITU-T Rec. X.680 | ISO/IEC 8824-1. Application of these encoding rules produces a

transfer syntax for such values. It is implicit in the specification of these encoding rules that they are also to be used for
decoding.
There are more than one set of encoding rules that can be applied to values of ASN.1 types. This Recommendation |
International Standard defines a set of Packed Encoding Rules (PER), so called because they achieve a much more
compact representation than that achieved by the Basic Encoding Rules (BER) and its derivatives described in ITU-T
Rec. X.690 | ISO/IEC 8825-1 which is referenced for some parts of the specification of these Packed Encoding Rules.

© ISO/IEC 2008 – All rights reserved vii

---------------------- Page: 7 ----------------------
ISO/IEC 8825-2:2008 (E)
INTERNATIONAL STANDARD
ISO/IEC 8825-2 : 1995 (E)
ITU-T Rec. X.691 (1995 E)
ITU-T RECOMMENDATION
Information technology –
ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)
1 Scope
This Recommendation | International Standard specifies a set of Packed Encoding Rules that may be used to derive a
transfer syntax for values of types defined in ITU-T Rec. X.680 | ISO/IEC 8824-1. These Packed Encoding Rules are
also to be applied for decoding such a transfer syntax in order to identify the data values being transferred.
The encoding rules specified in this Recommendation | International Standard:
– are used at the time of communication;
– are intended for use in circumstances where minimizing the size of the representation of values is the
major concern in the choice of encoding rules;
– allow the extension of an abstract syntax by addition of extra values, preserving the encodings
of the existing values, for all forms of extension described in ITU-T Rec. X.680 | ISO/IEC 8824-1;
– can be modified in accordance with the provisions of ITU-T Rec. X.695 | ISO/IEC 8825-6.
2 Normative references
The following 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, 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. 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 (2008) | ISO/IEC 8824-1:2008, Information technology – Abstract
Syntax Notation One (ASN.1): Specification of basic notation.
– ITU-T Recommendation X.681 (2008) | ISO/IEC 8824-2:2008, Information technology – Abstract
Syntax Notation One (ASN.1): Information object specification.
– ITU-T Recommendation X.682 (2008) | ISO/IEC 8824-3:2008, Information technology – Abstract
Syntax Notation One (ASN.1): Constraint specification.
– ITU-T Recommendation X.683 (2008) | ISO/IEC 8824-4:2008, Information technology – Abstract
Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications.
– ITU-T Recommendation X.690 (2008) | ISO/IEC 8825-1:2008, Information technology – ASN.1
encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER).
– ITU-T Recommendation X.695 (2008) | ISO/IEC 8825-6:2008, Information technology – ASN.1
encoding rules: Registration and application of PER encoding instructions.
2.2 Additional references
– ISO/IEC 646:1991, Information technology – ISO 7-bit coded character set for information interchange.
– ISO/IEC 2022:1994, Information technology – Character code structure and extension techniques.
– ISO/IEC 2375:2003, Information technology – Procedure for registration of escape sequences and
coded character sets.
  ITU-T Rec. X.691 (11/2008) 1

---------------------- Page: 8 ----------------------
ISO/IEC 8825-2:2008 (E)
– ISO 6093:1985, Information processing – Representation of numerical values in character strings for
information interchange.
– ISO International Register of Coded Character Sets to be Used with Escape Sequences.
– ISO/IEC 10646:2003, Information technology – Universal Multiple-Octet Coded Character Set (UCS).
3 Definitions
For the purposes of this Recommendation | International Standard, the following definitions apply.
3.1 Specification of Basic Notation
For the purposes of this Recommendation | International Standard, all the definitions in ITU-T Rec. X.680 |
ISO/IEC 8824-1 apply.
3.2 Information Object Specification
For the purposes of this Recommendation | International Standard, all the definitions in ITU-T Rec. X.681 |
ISO/IEC 8824-2 apply.
3.3 Constraint Specification
This Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.682 |
ISO/IEC 8824-3:
a) component relation constraint;
b) table constraint.
3.4 Parameterization of ASN.1 Specification
This Recommendation | International Standard makes use of the following term defined in ITU-T Rec. X.683 |
ISO/IEC 8824-4:
– variable constraint.
3.5 Basic Encoding Rules
This Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.690 |
ISO/IEC 8825-1:
a) dynamic conformance;
b) static conformance;
c) data value;
d) encoding (of a data value);
e) sender;
f) receiver.
3.6 PER Encoding Instructions
This Recommendation | International Standard makes use of the following term defined in ITU-T Rec. X.695 |
ISO/IEC 8825-6:
– identifying keyword.
3.7 Additional definitions
For the purposes of this Recommendation | International Standard, the following definitions apply.
3.7.1 2's-complement-binary-integer encoding: The encoding of a whole number into a bit-field (octet-aligned in
the ALIGNED variant) of a specified length, or into the minimum number of octets that will accommodate that whole
number encoded as a 2's-complement-integer, which provides representations for whole numbers that are equal to,
greater than, or less than zero, as specified in 11.4.
2 ITU-T Rec. X.691 (11/2008)

---------------------- Page: 9 ----------------------
ISO/IEC 8825-2:2008 (E)
NOTE 1 – The value of a two's complement binary number is derived by numbering the bits in the contents octets, starting with
bit 1 of the last octet as bit zero and ending the numbering with bit 8 of the first octet. Each bit is assigned a numerical value of
N
2 , where N is its position in the above numbering sequence. The value of the two's complement binary number is obtained by
summing the numerical values assigned to each bit for those bits which are set to one, excluding bit 8 of the first octet, and then
reducing this value by the numerical value assigned to bit 8 of the first octet if that bit is set to one.
NOTE 2 – Whole number is a synonym for the mathematical term integer. It is used here to avoid confusion with the ASN.1 type
integer.
3.7.2 abstract syntax value: A value of an abstract syntax (defined as the set of values of a single ASN.1 type),
which is to be encoded by PER, or which is to be generated by PER decoding.
NOTE – The single ASN.1 type associated with an abstract syntax is formally identified by an object of class
ABSTRACT-SYNTAX.
3.7.3 bit-field: The product of some part of the encoding mechanism that consists of an ordered set of bits that are
not necessarily a multiple of eight.
NOTE – If the use of this term is followed by "octet-aligned in the ALIGNED variant", this means that the bit-field is required to
begin on an octet boundary in the complete encoding for the aligned variant of PER.
3.7.4 canonical encoding: A complete encoding of an abstract syntax value obtained by the application of
encoding rules that have no implementation-dependent options; such rules result in the definition of a 1-1 mapping
between unambiguous and unique bitstrings in the transfer syntax and values in the abstract syntax.
3.7.5 composite type: A set, sequence, set-of, sequence-of, choice, embedded-pdv, external or unrestricted
character string type.
3.7.6 composite value: The value of a composite type.
3.7.7 constrained whole number: A whole number which is constrained by PER-visible constraints to lie within a
range from "lb" to "ub" with the value "lb" less than or equal to "ub", and the values of "lb" and "ub" as permitted
values.
NOTE – Constrained whole numbers occur in the encoding which identifies the chosen alternative of a choice type, the length of
character, octet and bit string types whose length has been restricted by PER-visible constraints to a maximum length, the count
of the number of components in a sequence-of or set-of type that has been restricted by PER-visible constraints to a maximum
number of components, the value of an integer type that has been constrained by PER-visible constraints to lie within finite
minimum and maximum values, and the value that denotes an enumeration in an enumerated type.
3.7.8 effective size constraint (for a constrained string type): A single finite size constraint that could be applied
to a built-in string type and whose effect would be to permit all and only those lengths that can be present in the
constrained string type.
NOTE 1 – For example, the following has an effective size constraint:
A ::= IA5String (SIZE(1.4) | SIZE(10.15))
since it can be rewritten with a single size constraint that applies to all values:
A ::= IA5String (SIZE(1.4 | 10.15))
whereas the following has no effective size constraint since the string can be arbitrarily long if it does not contain any characters
other than 'a', 'b' and 'c':
B ::= IA5String (SIZE(1.4) | FROM("abc"))
NOTE 2 – The effective size constraint is used only to determine the encoding of lengths.
3.7.9 effective permitted-alphabet constraint (for a constrained restricted character string type):
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.