ETSI ES 201 873-7 V4.10.1 (2022-04)
Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 7: Using ASN.1 with TTCN-3
Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 7: Using ASN.1 with TTCN-3
RES/MTS-2018737v4101
Metode za preskušanje in specificiranje (MTS) - 3. različica zapisa preskušanja in krmiljenja preskusov - 7. del: Uporaba ASN.1 pri TTCN-3
V tem dokumentu je opredeljen normativni način uporabe ASN.1 pri TTCN-3, kot je opredeljeno v priporočilih ITU-T X.680 [2], X.681 [3], X.682 [4] in X.683 [5]. Ta dokument ne zajema harmonizacije ostalih jezikov z jezikom TTCN-3.
General Information
Standards Content (Sample)
Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
Part 7: Using ASN.1 with TTCN-3
2 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
Reference
RES/MTS-2018737v4101
Keywords
ASN.1, language, testing, TTCN, XML
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 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2022.
All rights reserved.
ETSI
3 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Introduction . 9
5 General . 10
5.1 Approach . 10
5.2 Conformance and compatibility . 10
6 Amendments to the core language . 11
7 Additional TTCN-3 types . 11
7.1 General . 11
7.2 The object identifier type . 11
7.2.0 The objid type . 11
7.2.1 Sub-typing of the objid type . 12
7.2.1.1 Subtrees of the objid type . 12
7.2.1.2 List subtypes . 12
7.2.1.3 Range subtypes . 13
7.2.1.4 Mixing list and range subtypings . 13
7.2.2 Object identifier values . 13
7.2.3 Using objid values to identify modules . 13
7.2.3.1 Identifying module definitions . 13
7.2.3.2 Identifying modules in import statements . 13
7.2.4 Object identifier templates . 13
7.2.4.0 General . 13
7.2.4.1 In-line templates . 14
7.2.4.2 Template matching mechanisms . 14
7.2.5 Using objid with operators . 15
7.2.5.1 List operator . 15
7.2.5.2 Relational operators . 15
7.2.6 Using objid with predefined functions . 16
7.2.6.1 Number of components of an objid value or template. 16
7.2.6.2 The Substring function . 16
7.2.6.3 The isvalue function . 16
7.2.7 Supporting objid in TCI . 16
7.2.7.0 General . 16
7.2.7.1 Adding objid to abstract data types and values . 17
7.2.7.2 Adding objid to Java language mapping . 18
7.2.7.3 Adding objid to ANSI C language mapping . 19
8 ASN.1 and TTCN-3 type equivalents . 23
8.1 General . 23
8.1.a Importing from ASN.1 modules . 24
8.1.a.1 Language specification strings . 24
8.1.a.2 Importing definitions from ASN.1 modules . 24
8.1.a.3 Importing import statements from ASN.1 modules . 24
ETSI
4 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
8.1.a.4 Import Visibility of ASN.1 definitions . 24
8.2 Identifiers . 25
9 ASN.1 data types and values . 25
9.1 Transformation rules for ASN.1 types and values . 25
9.2 Transformation rules for values . 35
9.3 Scope of ASN.1 identifiers . 35
10 Parameterization in ASN.1 . 35
11 Defining ASN.1 message templates . 35
11.1 General . 35
11.2 Receiving messages based on ASN.1 types . 36
11.3 Ordering of template fields . 36
12 Encoding information . 36
12.1 General . 36
12.2 ASN.1 encoding attributes . 37
12.3 ASN.1 variant attributes . 37
Annex A (normative): Additional BNF and static semantics . 39
A.0 General rules . 39
A.1 New productions for ASN.1 support . 39
A.2 Amended core language BNF productions and static semantics . 39
Annex B (normative): Additional Pre-defined TTCN-3 functions . 41
Annex C (informative): Additional information on object identifiers . 42
C.1 The top-level arcs of the OID tree . 42
C.2 Character patterns to match OID IRI-s . 44
Annex D (informative): Deprecated features . 46
Annex E (informative): Example patterns for ASN.1 time types . 47
E.0 General rules . 47
E.1 Patterns corresponding to unconstrained time types . 47
E.2 Constructing patterns corresponding to constrained time types . 60
Annex F (informative): Bibliography . 61
History . 62
ETSI
5 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given 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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This final draft ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and
Specification (MTS), and is now submitted for the ETSI standards Membership Approval Procedure.
The present document is part 7 of a multi-part deliverable. Full details of the entire series can be found in part 1 [1].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
6 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
1 Scope
The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered
by the present document.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[2] Recommendation ITU-T X.680 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Specification of basic notation".
[3] Recommendation ITU-T X.681 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Information object specification".
[4] Recommendation ITU-T X.682 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Constraint specification".
[5] Recommendation ITU-T X.683 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Parameterization of ASN.1 specifications".
[6] Recommendation ITU-T X.690 (02/2021): "Information technology - ASN.1 encoding rules:
Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)".
[7] Recommendation ITU-T X.691 (02/2021): "Information technology - ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)".
[8] Recommendation ITU-T X.693 (02/2021): "Information technology - ASN.1 encoding rules: XML
Encoding Rules (XER)".
[9] Recommendation ITU-T T.100 (1988): "International information exchange for interactive
Videotex".
[10] Recommendation ITU-T T.101 (1994): "International interworking for Videotex services".
[11] Recommendation ITU-T X.660 (2011): "Information technology - Procedures for the operation of
object identifier registration authorities: General procedures and top arcs of the international object
identifier tree".
[12] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 6: TTCN-3 Control Interface (TCI)".
ETSI
7 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
[13] Recommendation ITU-T X.696 (02/2021): "Information technology - ASN.1 encoding rules:
Specification of Octet Encoding Rules (OER)".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ISO 8601 (2004): "Data elements and interchange formats - Information interchange -
Representation of dates and times".
[i.2] ETSI ES 201 873-10: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 10: TTCN-3 Documentation Comment Specification".
[i.3] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions - Part 1:
Country codes".
[i.4] Recommendation ITU-T X.121: "Public data networks - Network aspects - International
numbering plan for public data networks".
NOTE: References to Recommendations ITU-T include the Recommendation and all Amendments and
Corrigenda published to the Recommendation except when specified otherwise in other parts of the
present document.
[i.5] Recommendation ITU-T X.208: "Specification of Abstract Syntax Notation One (ASN.1)" (Blue
Book).
[i.6] Recommendation ITU-T X.680 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.7] Recommendation ITU-T X.680 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.8] Recommendation ITU-T X.680 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.9] Recommendation ITU-T X.681 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Information object specification".
[i.10] Recommendation ITU-T X.681 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Information object specification".
[i.11] Recommendation ITU-T X.681 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Information object specification".
[i.12] Recommendation ITU-T X.682 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Constraint specification".
[i.13] Recommendation ITU-T X.682 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Constraint specification".
[i.14] Recommendation ITU-T X.682 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Constraint specification".
[i.15] Recommendation ITU-T X.683 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications".
ETSI
8 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
[i.16] Recommendation ITU-T X.683 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications".
[i.17] Recommendation ITU-T X.683 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications".
[i.18] Recommendation ITU-T X.690 (2002): "Information technology - ASN.1 encoding rules:
Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)".
[i.19] Recommendation ITU-T X.691 (2002): "Information technology - ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)".
[i.20] ETSI ES 202 781: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support".
[i.21] ETSI ES 202 782: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: TTCN-3 Performance and Real Time Testing".
[i.22] ETSI ES 202 784: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Advanced Parameterization".
[i.23] ETSI ES 202 785: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Behaviour Types".
[i.24] ETSI ES 202 786: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Support of interfaces with continuous signals".
[i.25] ETSI ES 202 789: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Extended TRI".
[i.26] CCITT Blue Book.
[i.27] ETSI ES 201 873-8: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 8: The IDL to TTCN-3 Mapping".
[i.28] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 9: Using XML schema with TTCN-3".
[i.29] ETSI ES 201 873-11: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 11: Using JSON with TTCN-3".
[i.30] ETSI ES 203 022: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language extension: Advanced Matching".
[i.31] ETSI ES 203 790: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Object-Oriented Features".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 201 873-1 [1],
Recommendation ITU-T X.660 [11] and the following apply:
associated TTCN-3 type: TTCN-3 type equivalent, obtained by transforming of the corresponding ASN.1 type
definition according to clause 9.1 of the present document
NOTE: Associated TTCN-3 types and values may not exist in a visible way; this term is used to identify the part
of the abstract information carried by the related ASN.1 type or value, which have significance from the
point of view of TTCN-3 (also called the TTCN-3 view).
ETSI
9 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
metatype "OPEN TYPE": used to explain the ASN.1 to TTCN-3 conversion process
NOTE: It does not exist in the input ASN.1 module or the output TTCN-3 module.
root type: Definition in ETSI ES 201 873-1 [1] applies with the following addition: in case of types based on imported
ASN.1 types, the root type is determined from the associated TTCN-3 type (see clause 8).
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI ES 201 873-1 [1] and the following apply:
ASN.1 Abstract Syntax Notation One
BER Basic Encoding Rules of ASN.1
CER Canonical Encoding Rules of ASN.1
OER Octet Encoding Rules of ASN.1
OID Object IDentifier
PER Packed Encoding Rules of ASN.1
XER XML Encoding Rules of ASN.1
4 Introduction
When using ASN.1 with TTCN-3 all features of TTCN-3 and statements given in clause 4 of ETSI ES 201 873-1 [1] do
apply. In addition, when supporting the present document, TTCN-3 becomes fully harmonized with ASN.1 which may
be used with TTCN-3 modules as an alternative data type and value syntax. The present document defines the
capabilities required in addition of those specified in ETSI ES 201 873-1 [1] when ASN.1 is supported. The approach
used to combine ASN.1 and TTCN-3 could be applied to support the use of other type and value systems with TTCN-3.
However, the details of this are not defined in the present document.
ETSI ES 201 873-1 [1] specifies the core capabilities of the TTCN-3 language. Other language mappings (see [i.27],
[i.28] and [i.29]) and TTCN-3 language packages as ETSI ES 202 781 [i.20], ETSI ES 202 782 [i.21], ETSI
ES 202 784 [i.22], ETSI ES 202 785 [i.23], ETSI ES 202 786 [i.24], ETSI ES 202 789 [i.25], ETSI ES 203 022 [i.30],
ETSI ES 203 790 [i.31] may specify extensions to the core language that may define additional rules for the ASN.1 to
TTCN-3 mapping. These additional rules are specified in the relevant other documents and need to be supported only if
the implementation claims to support the other document.
ETSI
10 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
Configuration Advanced OO
Advanced Behavior Performance Continuous TTCN-3
…
and deploy-
Matching Features
Parameteri- Types and Real signals Packages
ment support
zation Time Testing
ASN.1 types
and values
IDL types
TTCN-3
XML types
Core
TTCN-3 User
Language
JSON types
& values
The shaded boxes are not
defined in this document
Other types &
values
Figure 1: User's view of the core language and its packages
5 General
5.1 Approach
TTCN-3 provides a clean interface for using ASN.1 definitions (as specified in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5]) in TTCN-3 modules.
In general, there are two approaches to the integration of other languages with TTCN-3, which will be referred to as
implicit and explicit mapping. The implicit mapping makes use of the import mechanism of TTCN-3, denoted by the
keywords language and import, in which case the TTCN-3 tool shall produce an internal representation of the imported
objects, which representation shall retain all the structural and encoding information. This internal representation is not
accessible by the user. It facilitates the immediate use of the abstract data specified in the other language. Therefore, the
definition of a specific data interface for each of these languages is required.
The explicit mapping translates the definitions of the other language directly into appropriate TTCN-3 language
artefacts. This also means that all information needed for correct encoding and decoding shall be present in the TTCN-3
module(s) generated by this translation.
In case of the ASN.1 to TTCN-3 mapping no TTCN-3 encoding instructions are defined by the present document,
hence only the implicit mapping is specified.
5.2 Conformance and compatibility
For an implementation claiming to support the use of ASN.1 with TTCN-3, all features specified in the present
document will need to be implemented consistently with the requirements given in the present document and in ETSI
ES 201 873-1 [1].
The language mapping presented in the present document is compatible to:
• ETSI ES 201 873-1 [1], V4.9.1.
• ETSI ES 201 873-10 [i.2], V4.5.1.
NOTE: Only the informative annex E uses features from ETSI ES 201 873-10 [i.2].
If later versions of those parts are available and should be used instead, the compatibility of the language mapping
presented in the present document has to be checked individually.
ETSI
11 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
6 Amendments to the core language
Using ASN.1 with TTCN-3 is handled at the static type-value level. Though it mainly means additions described in the
subsequent clauses, some of the core language syntactical structures shall also be amended to support the use of ASN.1.
These are specified in clause A.2.
7 Additional TTCN-3 types
7.1 General
The TTCN-3 types summarized in table 1 shall be supported in addition to those specified in clause 6 of ETSI
ES 201 873-1 [1].
Table 1: Overview of TTCN-3 types
Class of type Keyword Sub-type
objid
Simple basic types list, range
7.2 The object identifier type
7.2.0 The objid type
The object identifier type shall be supported as follows:
• objid: a type whose distinguished values are the set of all syntactically correct object identifier values. The
value notations for the objid type shall conform to clause 31 of Recommendation ITU-T X.680 [2] with the
exception that hyphens are replaced with underscores.
NOTE 1: This definition also allows object identifier values outside the collection of values defined in
Recommendation ITU-T X.660 [11] (e.g. with a node beneath the root not defined in Recommendation
ITU-T X.660 [11]).
The name form of object identifier components shall be used only for components defined in Recommendation
ITU-T X.660 [11]. These predefined object identifier components are given in annex C for information. In case of any
conflict between Recommendation ITU-T X.660 [11] and annex C of the present document, the former shall take
precedence.
In cases when the identifier of a value referenced within an object identifier value notation is identical to any of the
predefined component names, i.e. independently of the position of the predefined component or the referenced value
inside the notation (considering name conversion rules in clause 8.2), the name of the referenced value shall be prefixed
with the name of the module in which it is defined (see definition of ASN.1 modules in clause 12 of Recommendation
ITU-T X.680 [2] and TTCN-3 modules in clause 8.1 of the core language standard ETSI ES 201 873-1 [1]). The prefix
and the identifier shall be separated by a dot (.). Predefined object identifier component names may also be prefixed
with the name "X660".
NOTE 2: To increase readability it is recommended to use the "X660" prefix also in object identifier values
referring to a value identifier that is clashing with any of the predefined component names.
NOTE 3: Rules to resolve name clashes caused by imports are defined in clause 8.2.3.1 of the core language
standard ETSI ES 201 873-1 [1].
ETSI
12 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
EXAMPLE:
objid{itu_t(0) identified_organization(4) etsi(0)}
// or alternatively
objid {itu_t identified_organization etsi(0)}
// or alternatively
objid { 0 4 0}
// or alternatively
const integer etsi := 0;
const objid itu_idOrg := objid{ itu_t identified_organization }
objid{ itu_idOrg etsi } // note, that both names are referencing value definitions
const integer x := 162;
objid{ itu_t recommendation x A.x } // it is mandatory to use the module name ('A')
// to prefix the ambiguous identifier
// or alternatively
objid{ itu_t recommendation X660.x A.x } // the module name shall be present even if
// the "X660" prefix is used
7.2.1 Sub-typing of the objid type
7.2.1.1 Subtrees of the objid type
The object identifier type is a collection of principally infinite set of unique identifier values, each containing a
sequence of components; each given sequence of arbitrary length compose an object identifier node as shown on
figure 2 (see also annex C). Thus, each node of the object identifier tree - except being a unique identifier itself - is the
root of a subtree, containing a potentially infinite number of unique identifiers. The first n components of all the
identifiers in the subtree are identical to the components of the node, being the root of the subtree, where n is the
number of components of that node. Hence, each object identifier node distinguishes also a unique subset (subtype) of
the objid type. Each member of this subtype (the subtree) is longer than the node identifying the subtree.
Root
itu-t (0) joint-iso-itu-t (2)
iso (1)
(0) (1) . (i) (0) (1) … (j) (0) (1) … (k)
(0) . (m)
Figure 2: The object identifier tree
Note that object identifiers may also be relative identifiers, i.e. when the given objid value contains only the additional
components related to a defined base node. However, the above remains true for relative object identifiers as well, as
they also do denote a unique node in the object identifier tree (the node defined by the base node + the relative
identifier). If a node is identified by a relative object identifier, all nodes in its subtree will have relative identifiers too.
7.2.1.2 List subtypes
In addition to the types listed in clause 6, table 3 of ETSI ES 201 873-1 [1], value list subtyping of the objid type
shall be supported. For value lists of the objid type the rules in this clause apply. The objid nodes in the list shall be
of objid type and shall be a true subset of the values defined by the objid type or the base type being restricted.
Clause 7.2.1.1 shall govern in determining if the nodes are a true subset. The subtype defined by this list restricts the
allowed values to the concrete nodes on the list and the subtrees identified by them.
ETSI
13 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
EXAMPLE:
//identifies the nodes {0 4 0 0}, {0 4 0 1} and all other nodes beneath them
type objid MyObjids (objid{0 4 0 0}, objid{0 4 0 1});
//Further restricting the base type MyObjids
type MyObjids MyNarrowerObjids (objid{0 4 0 0 1 0}, objid{0 4 1 1}, objid{0 4 1 3});
//invalid definition as the node {0 4 2} is not member of the type MyObjids
type MyObjids MyNarrowestObjids (objid{0 4 2 1});
7.2.1.3 Range subtypes
In addition to the types listed in clause 6, table 3 of ETSI ES 201 873-1 [1], range subtyping of the objid type shall be
supported. For range subtyping of the objid type the rules in this clause apply. The objid nodes determining the
lower and the upper bounds of the subtype shall be of objid type of equal length and shall be a true subset of the
values defined by the objid type or the base type being restricted. Clause 7.2.1.1 shall govern in determining if the
nodes are a true subset. The subtype defined by the range restricts the allowed values to the nodes between the lower
and the upper bounds inclusive and the subtrees identified by them.
EXAMPLE:
//identifies the nodes {0 4 0 0}, {0 4 0 1} … {0 4 0 5} and all other nodes beneath them
type objid MyObjidRange (objid{0 4 0 0} . objid{0 4 0 5});
7.2.1.4 Mixing list and range subtypings
It is allowed to mix the list and the range subtyping mechanisms for objid types. The nodes identified by the different
subtyping mechanisms shall not overlap.
7.2.2 Object identifier values
When defining objid values, rules in clauses 5.4.1.1, 8.2.1, 10 and 11.1 of ETSI ES 201 873-1 [1] and in this clause
shall apply. In case of inconsistency the present document takes precedence.
Each object identifier node is an object identifier value. In this case the value identifies the concrete node (i.e. with a
definite number of components) and does not denote the objid subtree beneath it (see clause 7.2.1.1).
7.2.3 Using objid values to identify modules
7.2.3.1 Identifying module definitions
When ASN.1 is supported, module names (of the form of a TTCN-3 identifier) may optionally be followed by an object
identifier, which shall be a valid value as defined in Recommendation ITU-T X.660 [11].
NOTE: Module names in a test suite 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 TTCN-3 identifiers
(see clause 8.2.3.1 of ETSI ES 201 873-1 [1]) is unable to resolve such kind of clashes.
7.2.3.2 Identifying modules in import statements
When ASN.1 is supported, in addition to the module names, their object identifiers may also be provided in TTCN-3
import statements. If an object identifier is used as part of the module identifier, this object identifier shall be used by
TTCN-3 test systems to identify the correct module.
7.2.4 Object identifier templates
7.2.4.0 General
When defining templates of objid types, rules in clause 15 and annex B of ETSI ES 201 873-1 [1] and in this clause
shall apply. In case of inconsistency the present document takes precedence.
ETSI
14 Final draft ETSI ES 201 873-7 V4.10.1 (2022-02)
7.2.4.1 In-line templates
The type of objid values can be identified from the value notation alone, hence in addition to the types listed in note 2
of clause 15.4 in ETSI ES 201 873-1 [1], the type specification may also be omitted in case of objid values.
7.2.4.2 Template matching mechanisms
Applicability of matching mechanisms to templates of objid types is defined in table 2.
Table 2: TTCN-3 Matching Mechanisms
Used with values of Value Instead of values Inside values Attributes
S O C V A A
R S S P A A P L I
p m o a n n a u u a n n e e f
e i m l y y n p b t y y r n P
c t
p u V V g e t t E E m g r
i V l e a a e r y e l l u t e
f a e L l l s p r e e t h s
i l m i u u e e n m m a R e
c u e s e e t e e t e n
V e n t (?) O n n i s t
a t r t t o t
l e N (?) s n r
u d o O
i
e L n r c
I e N t
s (*)
o i
t n o
e n
(*)
objid
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
(see (see (see
note) note) note)
NOTE: Can be assigned to templates, however when used, shall be applied to optional fields of record and set types
only (without restriction on the type of that field).
The matching mechanisms SpecificValue, OmitValue, AnyValue, AnyValueOrNone and IfPresent are applicable to
objid fields as well according to the rules defined in ETSI ES 201 873-1 [1].
The value list and complemented value list matching mechanisms can also be used for objid templates and template
fields. Rules in clauses B.1.2.1 and B.1.2.2 of ETSI ES 201 873-1 [1] also shall apply to objid templates.
NOTE: This also means that only the concrete node values on the list is to be considered but not the subtrees
identified by them. I.e. in case of a complemented list, a node within a given subtree will match even if
the node being the root of the subtree is on the list.
The value range matching mechanism, in addition to types listed in clause B.1.2.5 of ETSI ES 201 873-1 [1], can also
be used for objid templates. When applied to objids, the values matching the range shall be determined according
to clause 7.2.1.3 of the present document, with the exception, that subtrees are not considered.
The inside value matching mechanism AnyElement, in addition to types listed in clause B.1.3.1 of ETSI
ES 201 873-1 [1], can also be used within objid templates. When applied to objids, it replaces exactly one component.
The inside value matching mechanism AnyElementsOrNone, in addition to types listed in clause B.1.3.2 of ETSI
ES 201 873-1 [1], can also be used within objid templates. When applied to objids, it matches the longest sequence of
components possible, according to the pattern as specified by the components surrounding the "*".
The length restriction matching attribute, in addition to types listed in clause B.1.4.1 of ETSI ES 201 873-1 [1], can also
be used with objid templates. When applied to objids, it identifies the number of components within an objid v
...
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
Part 7: Using ASN.1 with TTCN-3
2 ETSI ES 201 873-7 V4.10.1 (2022-04)
Reference
RES/MTS-2018737v4101
Keywords
ASN.1, language, testing, TTCN, XML
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 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2022.
All rights reserved.
ETSI
3 ETSI ES 201 873-7 V4.10.1 (2022-04)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Introduction . 9
5 General . 10
5.1 Approach . 10
5.2 Conformance and compatibility . 10
6 Amendments to the core language . 10
7 Additional TTCN-3 types . 10
7.1 General . 10
7.2 The object identifier type . 11
7.2.0 The objid type . 11
7.2.1 Sub-typing of the objid type . 11
7.2.1.1 Subtrees of the objid type . 11
7.2.1.2 List subtypes . 12
7.2.1.3 Range subtypes . 12
7.2.1.4 Mixing list and range subtypings . 12
7.2.2 Object identifier values . 12
7.2.3 Using objid values to identify modules . 13
7.2.3.1 Identifying module definitions . 13
7.2.3.2 Identifying modules in import statements . 13
7.2.4 Object identifier templates . 13
7.2.4.0 General . 13
7.2.4.1 In-line templates . 13
7.2.4.2 Template matching mechanisms . 13
7.2.5 Using objid with operators . 14
7.2.5.1 List operator . 14
7.2.5.2 Relational operators . 14
7.2.6 Using objid with predefined functions . 15
7.2.6.1 Number of components of an objid value or template. 15
7.2.6.2 The Substring function . 15
7.2.6.3 The isvalue function . 16
7.2.7 Supporting objid in TCI . 16
7.2.7.0 General . 16
7.2.7.1 Adding objid to abstract data types and values . 16
7.2.7.2 Adding objid to Java language mapping . 17
7.2.7.3 Adding objid to ANSI C language mapping . 18
8 ASN.1 and TTCN-3 type equivalents . 22
8.1 General . 22
8.1.a Importing from ASN.1 modules . 23
8.1.a.1 Language specification strings . 23
8.1.a.2 Importing definitions from ASN.1 modules . 23
8.1.a.3 Importing import statements from ASN.1 modules . 24
ETSI
4 ETSI ES 201 873-7 V4.10.1 (2022-04)
8.1.a.4 Import Visibility of ASN.1 definitions . 24
8.2 Identifiers . 24
9 ASN.1 data types and values . 25
9.1 Transformation rules for ASN.1 types and values . 25
9.2 Transformation rules for values . 34
9.3 Scope of ASN.1 identifiers . 34
10 Parameterization in ASN.1 . 34
11 Defining ASN.1 message templates . 34
11.1 General . 34
11.2 Receiving messages based on ASN.1 types . 35
11.3 Ordering of template fields . 35
12 Encoding information . 35
12.1 General . 35
12.2 ASN.1 encoding attributes . 36
12.3 ASN.1 variant attributes . 36
Annex A (normative): Additional BNF and static semantics . 38
A.0 General rules . 38
A.1 New productions for ASN.1 support . 38
A.2 Amended core language BNF productions and static semantics . 38
Annex B (normative): Additional Pre-defined TTCN-3 functions . 40
Annex C (informative): Additional information on object identifiers . 41
C.1 The top-level arcs of the OID tree . 41
C.2 Character patterns to match OID IRI-s . 43
Annex D (informative): Deprecated features . 45
Annex E (informative): Example patterns for ASN.1 time types . 46
E.0 General rules . 46
E.1 Patterns corresponding to unconstrained time types . 46
E.2 Constructing patterns corresponding to constrained time types . 59
Annex F (informative): Bibliography . 60
History . 61
ETSI
5 ETSI ES 201 873-7 V4.10.1 (2022-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given 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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document is part 7 of a multi-part deliverable. Full details of the entire series can be found in part 1 [1].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
6 ETSI ES 201 873-7 V4.10.1 (2022-04)
1 Scope
The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered
by the present document.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[2] Recommendation ITU-T X.680 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Specification of basic notation".
[3] Recommendation ITU-T X.681 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Information object specification".
[4] Recommendation ITU-T X.682 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Constraint specification".
[5] Recommendation ITU-T X.683 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Parameterization of ASN.1 specifications".
[6] Recommendation ITU-T X.690 (02/2021): "Information technology - ASN.1 encoding rules:
Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)".
[7] Recommendation ITU-T X.691 (02/2021): "Information technology - ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)".
[8] Recommendation ITU-T X.693 (02/2021): "Information technology - ASN.1 encoding rules: XML
Encoding Rules (XER)".
[9] Recommendation ITU-T T.100 (1988): "International information exchange for interactive
Videotex".
[10] Recommendation ITU-T T.101 (1994): "International interworking for Videotex services".
[11] Recommendation ITU-T X.660 (2011): "Information technology - Procedures for the operation of
object identifier registration authorities: General procedures and top arcs of the international object
identifier tree".
[12] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 6: TTCN-3 Control Interface (TCI)".
[13] Recommendation ITU-T X.696 (02/2021): "Information technology - ASN.1 encoding rules:
Specification of Octet Encoding Rules (OER)".
ETSI
7 ETSI ES 201 873-7 V4.10.1 (2022-04)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ISO 8601 (2004): "Data elements and interchange formats - Information interchange -
Representation of dates and times".
[i.2] ETSI ES 201 873-10: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 10: TTCN-3 Documentation Comment Specification".
[i.3] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions - Part 1:
Country codes".
[i.4] Recommendation ITU-T X.121: "Public data networks - Network aspects - International
numbering plan for public data networks".
NOTE: References to Recommendations ITU-T include the Recommendation and all Amendments and
Corrigenda published to the Recommendation except when specified otherwise in other parts of the
present document.
[i.5] Recommendation ITU-T X.208: "Specification of Abstract Syntax Notation One (ASN.1)" (Blue
Book).
[i.6] Recommendation ITU-T X.680 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.7] Recommendation ITU-T X.680 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.8] Recommendation ITU-T X.680 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.9] Recommendation ITU-T X.681 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Information object specification".
[i.10] Recommendation ITU-T X.681 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Information object specification".
[i.11] Recommendation ITU-T X.681 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Information object specification".
[i.12] Recommendation ITU-T X.682 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Constraint specification".
[i.13] Recommendation ITU-T X.682 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Constraint specification".
[i.14] Recommendation ITU-T X.682 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Constraint specification".
[i.15] Recommendation ITU-T X.683 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications".
[i.16] Recommendation ITU-T X.683 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications".
[i.17] Recommendation ITU-T X.683 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications".
ETSI
8 ETSI ES 201 873-7 V4.10.1 (2022-04)
[i.18] Recommendation ITU-T X.690 (2002): "Information technology - ASN.1 encoding rules:
Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)".
[i.19] Recommendation ITU-T X.691 (2002): "Information technology - ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)".
[i.20] ETSI ES 202 781: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support".
[i.21] ETSI ES 202 782: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: TTCN-3 Performance and Real Time Testing".
[i.22] ETSI ES 202 784: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Advanced Parameterization".
[i.23] ETSI ES 202 785: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Behaviour Types".
[i.24] ETSI ES 202 786: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Support of interfaces with continuous signals".
[i.25] ETSI ES 202 789: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Extended TRI".
[i.26] CCITT Blue Book.
[i.27] ETSI ES 201 873-8: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 8: The IDL to TTCN-3 Mapping".
[i.28] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 9: Using XML schema with TTCN-3".
[i.29] ETSI ES 201 873-11: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 11: Using JSON with TTCN-3".
[i.30] ETSI ES 203 022: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language extension: Advanced Matching".
[i.31] ETSI ES 203 790: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Object-Oriented Features".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 201 873-1 [1], Recommendation ITU-T
X.660 [11] and the following apply:
associated TTCN-3 type: TTCN-3 type equivalent, obtained by transforming of the corresponding ASN.1 type
definition according to clause 9.1 of the present document
NOTE: Associated TTCN-3 types and values may not exist in a visible way; this term is used to identify the part
of the abstract information carried by the related ASN.1 type or value, which have significance from the
point of view of TTCN-3 (also called the TTCN-3 view).
metatype "OPEN TYPE": used to explain the ASN.1 to TTCN-3 conversion process
NOTE: It does not exist in the input ASN.1 module or the output TTCN-3 module.
root type: Definition in ETSI ES 201 873-1 [1] applies with the following addition: in case of types based on imported
ASN.1 types, the root type is determined from the associated TTCN-3 type (see clause 8).
ETSI
9 ETSI ES 201 873-7 V4.10.1 (2022-04)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI ES 201 873-1 [1] and the following apply:
ASN.1 Abstract Syntax Notation One
BER Basic Encoding Rules of ASN.1
CER Canonical Encoding Rules of ASN.1
OER Octet Encoding Rules of ASN.1
OID Object IDentifier
PER Packed Encoding Rules of ASN.1
XER XML Encoding Rules of ASN.1
4 Introduction
When using ASN.1 with TTCN-3 all features of TTCN-3 and statements given in clause 4 of ETSI ES 201 873-1 [1] do
apply. In addition, when supporting the present document, TTCN-3 becomes fully harmonized with ASN.1 which may
be used with TTCN-3 modules as an alternative data type and value syntax. The present document defines the
capabilities required in addition of those specified in ETSI ES 201 873-1 [1] when ASN.1 is supported. The approach
used to combine ASN.1 and TTCN-3 could be applied to support the use of other type and value systems with TTCN-3.
However, the details of this are not defined in the present document.
ETSI ES 201 873-1 [1] specifies the core capabilities of the TTCN-3 language. Other language mappings (see [i.27],
[i.28] and [i.29]) and TTCN-3 language packages as ETSI ES 202 781 [i.20], ETSI ES 202 782 [i.21], ETSI
ES 202 784 [i.22], ETSI ES 202 785 [i.23], ETSI ES 202 786 [i.24], ETSI ES 202 789 [i.25], ETSI ES 203 022 [i.30],
ETSI ES 203 790 [i.31] may specify extensions to the core language that may define additional rules for the ASN.1 to
TTCN-3 mapping. These additional rules are specified in the relevant other documents and need to be supported only if
the implementation claims to support the other document.
Advanced OO
Configuration Advanced Behavior Performance Continuous TTCN-3
…
and deploy- Matching Features
Parameteri- Types and Real signals Packages
ment support
zation Time Testing
ASN.1 types
and values
IDL types
TTCN-3
XML types
Core
TTCN-3 User
Language
JSON types
& values
The shaded boxes are not
defined in this document
Other types &
values
Figure 1: User's view of the core language and its packages
ETSI
10 ETSI ES 201 873-7 V4.10.1 (2022-04)
5 General
5.1 Approach
TTCN-3 provides a clean interface for using ASN.1 definitions (as specified in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5]) in TTCN-3 modules.
In general, there are two approaches to the integration of other languages with TTCN-3, which will be referred to as
implicit and explicit mapping. The implicit mapping makes use of the import mechanism of TTCN-3, denoted by the
keywords language and import, in which case the TTCN-3 tool shall produce an internal representation of the imported
objects, which representation shall retain all the structural and encoding information. This internal representation is not
accessible by the user. It facilitates the immediate use of the abstract data specified in the other language. Therefore, the
definition of a specific data interface for each of these languages is required.
The explicit mapping translates the definitions of the other language directly into appropriate TTCN-3 language
artefacts. This also means that all information needed for correct encoding and decoding shall be present in the TTCN-3
module(s) generated by this translation.
In case of the ASN.1 to TTCN-3 mapping no TTCN-3 encoding instructions are defined by the present document,
hence only the implicit mapping is specified.
5.2 Conformance and compatibility
For an implementation claiming to support the use of ASN.1 with TTCN-3, all features specified in the present
document will need to be implemented consistently with the requirements given in the present document and in ETSI
ES 201 873-1 [1].
The language mapping presented in the present document is compatible to:
• ETSI ES 201 873-1 [1], V4.9.1.
• ETSI ES 201 873-10 [i.2], V4.5.1.
NOTE: Only the informative annex E uses features from ETSI ES 201 873-10 [i.2].
If later versions of those parts are available and should be used instead, the compatibility of the language mapping
presented in the present document has to be checked individually.
6 Amendments to the core language
Using ASN.1 with TTCN-3 is handled at the static type-value level. Though it mainly means additions described in the
subsequent clauses, some of the core language syntactical structures shall also be amended to support the use of ASN.1.
These are specified in clause A.2.
7 Additional TTCN-3 types
7.1 General
The TTCN-3 types summarized in table 1 shall be supported in addition to those specified in clause 6 of ETSI
ES 201 873-1 [1].
Table 1: Overview of TTCN-3 types
Class of type Keyword Sub-type
objid
Simple basic types list, range
ETSI
11 ETSI ES 201 873-7 V4.10.1 (2022-04)
7.2 The object identifier type
7.2.0 The objid type
The object identifier type shall be supported as follows:
• objid: a type whose distinguished values are the set of all syntactically correct object identifier values. The
value notations for the objid type shall conform to clause 31 of Recommendation ITU-T X.680 [2] with the
exception that hyphens are replaced with underscores.
NOTE 1: This definition also allows object identifier values outside the collection of values defined in
Recommendation ITU-T X.660 [11] (e.g. with a node beneath the root not defined in Recommendation
ITU-T X.660 [11]).
The name form of object identifier components shall be used only for components defined in Recommendation ITU-T
X.660 [11]. These predefined object identifier components are given in annex C for information. In case of any conflict
between Recommendation ITU-T X.660 [11] and annex C of the present document, the former shall take precedence.
In cases when the identifier of a value referenced within an object identifier value notation is identical to any of the
predefined component names, i.e. independently of the position of the predefined component or the referenced value
inside the notation (considering name conversion rules in clause 8.2), the name of the referenced value shall be prefixed
with the name of the module in which it is defined (see definition of ASN.1 modules in clause 12 of Recommendation
ITU-T X.680 [2] and TTCN-3 modules in clause 8.1 of the core language standard ETSI ES 201 873-1 [1]). The prefix
and the identifier shall be separated by a dot (.). Predefined object identifier component names may also be prefixed
with the name "X660".
NOTE 2: To increase readability it is recommended to use the "X660" prefix also in object identifier values
referring to a value identifier that is clashing with any of the predefined component names.
NOTE 3: Rules to resolve name clashes caused by imports are defined in clause 8.2.3.1 of the core language
standard ETSI ES 201 873-1 [1].
EXAMPLE:
objid{itu_t(0) identified_organization(4) etsi(0)}
// or alternatively
objid {itu_t identified_organization etsi(0)}
// or alternatively
objid { 0 4 0}
// or alternatively
const integer etsi := 0;
const objid itu_idOrg := objid{ itu_t identified_organization }
objid{ itu_idOrg etsi } // note, that both names are referencing value definitions
const integer x := 162;
objid{ itu_t recommendation x A.x } // it is mandatory to use the module name ('A')
// to prefix the ambiguous identifier
// or alternatively
objid{ itu_t recommendation X660.x A.x } // the module name shall be present even if
// the "X660" prefix is used
7.2.1 Sub-typing of the objid type
7.2.1.1 Subtrees of the objid type
The object identifier type is a collection of principally infinite set of unique identifier values, each containing a
sequence of components; each given sequence of arbitrary length compose an object identifier node as shown on
figure 2 (see also annex C). Thus, each node of the object identifier tree - except being a unique identifier itself - is the
root of a subtree, containing a potentially infinite number of unique identifiers. The first n components of all the
identifiers in the subtree are identical to the components of the node, being the root of the subtree, where n is the
number of components of that node. Hence, each object identifier node distinguishes also a unique subset (subtype) of
the objid type. Each member of this subtype (the subtree) is longer than the node identifying the subtree.
ETSI
12 ETSI ES 201 873-7 V4.10.1 (2022-04)
Root
joint-iso-itu-t (2)
itu-t (0)
iso (1)
(0) (1) . (i) (0) (1) … (j) (0) (1) … (k)
(0) . (m)
Figure 2: The object identifier tree
Note that object identifiers may also be relative identifiers, i.e. when the given objid value contains only the additional
components related to a defined base node. However, the above remains true for relative object identifiers as well, as
they also do denote a unique node in the object identifier tree (the node defined by the base node + the relative
identifier). If a node is identified by a relative object identifier, all nodes in its subtree will have relative identifiers too.
7.2.1.2 List subtypes
In addition to the types listed in clause 6, table 3 of ETSI ES 201 873-1 [1], value list subtyping of the objid type
shall be supported. For value lists of the objid type the rules in this clause apply. The objid nodes in the list shall be
of objid type and shall be a true subset of the values defined by the objid type or the base type being restricted.
Clause 7.2.1.1 shall govern in determining if the nodes are a true subset. The subtype defined by this list restricts the
allowed values to the concrete nodes on the list and the subtrees identified by them.
EXAMPLE:
//identifies the nodes {0 4 0 0}, {0 4 0 1} and all other nodes beneath them
type objid MyObjids (objid{0 4 0 0}, objid{0 4 0 1});
//Further restricting the base type MyObjids
type MyObjids MyNarrowerObjids (objid{0 4 0 0 1 0}, objid{0 4 1 1}, objid{0 4 1 3});
//invalid definition as the node {0 4 2} is not member of the type MyObjids
type MyObjids MyNarrowestObjids (objid{0 4 2 1});
7.2.1.3 Range subtypes
In addition to the types listed in clause 6, table 3 of ETSI ES 201 873-1 [1], range subtyping of the objid type shall be
supported. For range subtyping of the objid type the rules in this clause apply. The objid nodes determining the
lower and the upper bounds of the subtype shall be of objid type of equal length and shall be a true subset of the
values defined by the objid type or the base type being restricted. Clause 7.2.1.1 shall govern in determining if the
nodes are a true subset. The subtype defined by the range restricts the allowed values to the nodes between the lower
and the upper bounds inclusive and the subtrees identified by them.
EXAMPLE:
//identifies the nodes {0 4 0 0}, {0 4 0 1} … {0 4 0 5} and all other nodes beneath them
type objid MyObjidRange (objid{0 4 0 0} . objid{0 4 0 5});
7.2.1.4 Mixing list and range subtypings
It is allowed to mix the list and the range subtyping mechanisms for objid types. The nodes identified by the different
subtyping mechanisms shall not overlap.
7.2.2 Object identifier values
When defining objid values, rules in clauses 5.4.1.1, 8.2.1, 10 and 11.1 of ETSI ES 201 873-1 [1] and in this clause
shall apply. In case of inconsistency the present document takes precedence.
Each object identifier node is an object identifier value. In this case the value identifies the concrete node (i.e. with a
definite number of components) and does not denote the objid subtree beneath it (see clause 7.2.1.1).
ETSI
13 ETSI ES 201 873-7 V4.10.1 (2022-04)
7.2.3 Using objid values to identify modules
7.2.3.1 Identifying module definitions
When ASN.1 is supported, module names (of the form of a TTCN-3 identifier) may optionally be followed by an object
identifier, which shall be a valid value as defined in Recommendation ITU-T X.660 [11].
NOTE: Module names in a test suite 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 TTCN-3 identifiers
(see clause 8.2.3.1 of ETSI ES 201 873-1 [1]) is unable to resolve such kind of clashes.
7.2.3.2 Identifying modules in import statements
When ASN.1 is supported, in addition to the module names, their object identifiers may also be provided in TTCN-3
import statements. If an object identifier is used as part of the module identifier, this object identifier shall be used by
TTCN-3 test systems to identify the correct module.
7.2.4 Object identifier templates
7.2.4.0 General
When defining templates of objid types, rules in clause 15 and annex B of ETSI ES 201 873-1 [1] and in this clause
shall apply. In case of inconsistency the present document takes precedence.
7.2.4.1 In-line templates
The type of objid values can be identified from the value notation alone, hence in addition to the types listed in note 2
of clause 15.4 in ETSI ES 201 873-1 [1], the type specification may also be omitted in case of objid values.
7.2.4.2 Template matching mechanisms
Applicability of matching mechanisms to templates of objid types is defined in table 2.
Table 2: TTCN-3 Matching Mechanisms
Used with values of Value Instead of values Inside values Attributes
S O C V A A R S S P A A P L I
p m o a n n
a u u a n n e e f
e i m l y y n p b t y y r n P
c t p u V V g e t t E E m g r
i V
l e a a e r y e l l u t e
f a e L l l s p r e e t h s
i l m i u u e e n m m a R
e
c u e s e e t e e t e n
V e n t (?) O n n i s t
a t r t t o t
l e N (?) s n r
u d o O i
e L n r
c
I e N t
s (*) o i
t
n o
e n
(*)
objid
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
(see (see (see
note) note) note)
NOTE: Can be assigned to templates, however when used, shall be applied to optional fields of record and set types
only (without restriction on the type of that field).
ETSI
14 ETSI ES 201 873-7 V4.10.1 (2022-04)
The matching mechanisms SpecificValue, OmitValue, AnyValue, AnyValueOrNone and IfPresent are applicable to
objid fields as well according to the rules defined in ETSI ES 201 873-1 [1].
The value list and complemented value list matching mechanisms can also be used for objid templates and template
fields. Rules in clauses B.1.2.1 and B.1.2.2 of ETSI ES 201 873-1 [1] also shall apply to objid templates.
NOTE: This also means that only the concrete node values on the list is to be considered but not the subtrees
identified by them. I.e. in case of a complemented list, a node within a given subtree will match even if
the node being the root of the subtree is on the list.
The value range matching mechanism, in addition to types listed in clause B.1.2.5 of ETSI ES 201 873-1 [1], can also
be used for objid templates. When applied to objids, the values matching the range shall be determined according
to clause 7.2.1.3 of the present document, with the exception, that subtrees are not considered.
The inside value matching mechanism AnyElement, in addition to types listed in clause B.1.3.1 of ETSI
ES 201 873-1 [1], can also be used within objid templates. When applied to objids, it replaces exactly one component.
The inside value matching mechanism AnyElementsOrNone, in addition to types listed in clause B.1.3.2 of ETSI
ES 201 873-1 [1], can also be used within objid templates. When applied to objids, it matches the longest sequence of
components possible, according to the pattern as specified by the components surrounding the "*".
The length restriction matching attribute, in addition to types listed in clause B.1.4.1 of ETSI ES 201 873-1 [1], can also
be used with objid templates. When applied to objids, it identifies the number of components within an objid value
matching the objid template.
7.2.5 Usi
...
SLOVENSKI STANDARD
01-julij-2022
Metode za preskušanje in specificiranje (MTS) - 3. različica zapisa preskušanja in
krmiljenja preskusov - 7. del: Uporaba ASN.1 pri TTCN-3
Methods for Testing and Specification (MTS) - The Testing and Test Control Notation
version 3 - Part 7: Using ASN.1 with TTCN-3
Ta slovenski standard je istoveten z: ETSI ES 201 873-7 V4.10.1 (2022-04)
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
35.060 Jeziki, ki se uporabljajo v Languages used in
informacijski tehniki in information technology
tehnologiji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
Part 7: Using ASN.1 with TTCN-3
2 ETSI ES 201 873-7 V4.10.1 (2022-04)
Reference
RES/MTS-2018737v4101
Keywords
ASN.1, language, testing, TTCN, XML
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 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2022.
All rights reserved.
ETSI
3 ETSI ES 201 873-7 V4.10.1 (2022-04)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Introduction . 9
5 General . 10
5.1 Approach . 10
5.2 Conformance and compatibility . 10
6 Amendments to the core language . 10
7 Additional TTCN-3 types . 10
7.1 General . 10
7.2 The object identifier type . 11
7.2.0 The objid type . 11
7.2.1 Sub-typing of the objid type . 11
7.2.1.1 Subtrees of the objid type . 11
7.2.1.2 List subtypes . 12
7.2.1.3 Range subtypes . 12
7.2.1.4 Mixing list and range subtypings . 12
7.2.2 Object identifier values . 12
7.2.3 Using objid values to identify modules . 13
7.2.3.1 Identifying module definitions . 13
7.2.3.2 Identifying modules in import statements . 13
7.2.4 Object identifier templates . 13
7.2.4.0 General . 13
7.2.4.1 In-line templates . 13
7.2.4.2 Template matching mechanisms . 13
7.2.5 Using objid with operators . 14
7.2.5.1 List operator . 14
7.2.5.2 Relational operators . 14
7.2.6 Using objid with predefined functions . 15
7.2.6.1 Number of components of an objid value or template. 15
7.2.6.2 The Substring function . 15
7.2.6.3 The isvalue function . 16
7.2.7 Supporting objid in TCI . 16
7.2.7.0 General . 16
7.2.7.1 Adding objid to abstract data types and values . 16
7.2.7.2 Adding objid to Java language mapping . 17
7.2.7.3 Adding objid to ANSI C language mapping . 18
8 ASN.1 and TTCN-3 type equivalents . 22
8.1 General . 22
8.1.a Importing from ASN.1 modules . 23
8.1.a.1 Language specification strings . 23
8.1.a.2 Importing definitions from ASN.1 modules . 23
8.1.a.3 Importing import statements from ASN.1 modules . 24
ETSI
4 ETSI ES 201 873-7 V4.10.1 (2022-04)
8.1.a.4 Import Visibility of ASN.1 definitions . 24
8.2 Identifiers . 24
9 ASN.1 data types and values . 25
9.1 Transformation rules for ASN.1 types and values . 25
9.2 Transformation rules for values . 34
9.3 Scope of ASN.1 identifiers . 34
10 Parameterization in ASN.1 . 34
11 Defining ASN.1 message templates . 34
11.1 General . 34
11.2 Receiving messages based on ASN.1 types . 35
11.3 Ordering of template fields . 35
12 Encoding information . 35
12.1 General . 35
12.2 ASN.1 encoding attributes . 36
12.3 ASN.1 variant attributes . 36
Annex A (normative): Additional BNF and static semantics . 38
A.0 General rules . 38
A.1 New productions for ASN.1 support . 38
A.2 Amended core language BNF productions and static semantics . 38
Annex B (normative): Additional Pre-defined TTCN-3 functions . 40
Annex C (informative): Additional information on object identifiers . 41
C.1 The top-level arcs of the OID tree . 41
C.2 Character patterns to match OID IRI-s . 43
Annex D (informative): Deprecated features . 45
Annex E (informative): Example patterns for ASN.1 time types . 46
E.0 General rules . 46
E.1 Patterns corresponding to unconstrained time types . 46
E.2 Constructing patterns corresponding to constrained time types . 59
Annex F (informative): Bibliography . 60
History . 61
ETSI
5 ETSI ES 201 873-7 V4.10.1 (2022-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given 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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document is part 7 of a multi-part deliverable. Full details of the entire series can be found in part 1 [1].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
6 ETSI ES 201 873-7 V4.10.1 (2022-04)
1 Scope
The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered
by the present document.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[2] Recommendation ITU-T X.680 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Specification of basic notation".
[3] Recommendation ITU-T X.681 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Information object specification".
[4] Recommendation ITU-T X.682 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Constraint specification".
[5] Recommendation ITU-T X.683 (02/2021): "Information technology - Abstract Syntax Notation
One (ASN.1): Parameterization of ASN.1 specifications".
[6] Recommendation ITU-T X.690 (02/2021): "Information technology - ASN.1 encoding rules:
Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)".
[7] Recommendation ITU-T X.691 (02/2021): "Information technology - ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)".
[8] Recommendation ITU-T X.693 (02/2021): "Information technology - ASN.1 encoding rules: XML
Encoding Rules (XER)".
[9] Recommendation ITU-T T.100 (1988): "International information exchange for interactive
Videotex".
[10] Recommendation ITU-T T.101 (1994): "International interworking for Videotex services".
[11] Recommendation ITU-T X.660 (2011): "Information technology - Procedures for the operation of
object identifier registration authorities: General procedures and top arcs of the international object
identifier tree".
[12] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 6: TTCN-3 Control Interface (TCI)".
[13] Recommendation ITU-T X.696 (02/2021): "Information technology - ASN.1 encoding rules:
Specification of Octet Encoding Rules (OER)".
ETSI
7 ETSI ES 201 873-7 V4.10.1 (2022-04)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ISO 8601 (2004): "Data elements and interchange formats - Information interchange -
Representation of dates and times".
[i.2] ETSI ES 201 873-10: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 10: TTCN-3 Documentation Comment Specification".
[i.3] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions - Part 1:
Country codes".
[i.4] Recommendation ITU-T X.121: "Public data networks - Network aspects - International
numbering plan for public data networks".
NOTE: References to Recommendations ITU-T include the Recommendation and all Amendments and
Corrigenda published to the Recommendation except when specified otherwise in other parts of the
present document.
[i.5] Recommendation ITU-T X.208: "Specification of Abstract Syntax Notation One (ASN.1)" (Blue
Book).
[i.6] Recommendation ITU-T X.680 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.7] Recommendation ITU-T X.680 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.8] Recommendation ITU-T X.680 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.9] Recommendation ITU-T X.681 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Information object specification".
[i.10] Recommendation ITU-T X.681 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Information object specification".
[i.11] Recommendation ITU-T X.681 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Information object specification".
[i.12] Recommendation ITU-T X.682 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Constraint specification".
[i.13] Recommendation ITU-T X.682 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Constraint specification".
[i.14] Recommendation ITU-T X.682 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Constraint specification".
[i.15] Recommendation ITU-T X.683 (1994): "Information technology - Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications".
[i.16] Recommendation ITU-T X.683 (1997): "Information technology - Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications".
[i.17] Recommendation ITU-T X.683 (2002): "Information technology - Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications".
ETSI
8 ETSI ES 201 873-7 V4.10.1 (2022-04)
[i.18] Recommendation ITU-T X.690 (2002): "Information technology - ASN.1 encoding rules:
Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)".
[i.19] Recommendation ITU-T X.691 (2002): "Information technology - ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)".
[i.20] ETSI ES 202 781: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support".
[i.21] ETSI ES 202 782: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: TTCN-3 Performance and Real Time Testing".
[i.22] ETSI ES 202 784: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Advanced Parameterization".
[i.23] ETSI ES 202 785: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Behaviour Types".
[i.24] ETSI ES 202 786: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Support of interfaces with continuous signals".
[i.25] ETSI ES 202 789: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Extended TRI".
[i.26] CCITT Blue Book.
[i.27] ETSI ES 201 873-8: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 8: The IDL to TTCN-3 Mapping".
[i.28] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 9: Using XML schema with TTCN-3".
[i.29] ETSI ES 201 873-11: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 11: Using JSON with TTCN-3".
[i.30] ETSI ES 203 022: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language extension: Advanced Matching".
[i.31] ETSI ES 203 790: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Object-Oriented Features".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 201 873-1 [1], Recommendation ITU-T
X.660 [11] and the following apply:
associated TTCN-3 type: TTCN-3 type equivalent, obtained by transforming of the corresponding ASN.1 type
definition according to clause 9.1 of the present document
NOTE: Associated TTCN-3 types and values may not exist in a visible way; this term is used to identify the part
of the abstract information carried by the related ASN.1 type or value, which have significance from the
point of view of TTCN-3 (also called the TTCN-3 view).
metatype "OPEN TYPE": used to explain the ASN.1 to TTCN-3 conversion process
NOTE: It does not exist in the input ASN.1 module or the output TTCN-3 module.
root type: Definition in ETSI ES 201 873-1 [1] applies with the following addition: in case of types based on imported
ASN.1 types, the root type is determined from the associated TTCN-3 type (see clause 8).
ETSI
9 ETSI ES 201 873-7 V4.10.1 (2022-04)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI ES 201 873-1 [1] and the following apply:
ASN.1 Abstract Syntax Notation One
BER Basic Encoding Rules of ASN.1
CER Canonical Encoding Rules of ASN.1
OER Octet Encoding Rules of ASN.1
OID Object IDentifier
PER Packed Encoding Rules of ASN.1
XER XML Encoding Rules of ASN.1
4 Introduction
When using ASN.1 with TTCN-3 all features of TTCN-3 and statements given in clause 4 of ETSI ES 201 873-1 [1] do
apply. In addition, when supporting the present document, TTCN-3 becomes fully harmonized with ASN.1 which may
be used with TTCN-3 modules as an alternative data type and value syntax. The present document defines the
capabilities required in addition of those specified in ETSI ES 201 873-1 [1] when ASN.1 is supported. The approach
used to combine ASN.1 and TTCN-3 could be applied to support the use of other type and value systems with TTCN-3.
However, the details of this are not defined in the present document.
ETSI ES 201 873-1 [1] specifies the core capabilities of the TTCN-3 language. Other language mappings (see [i.27],
[i.28] and [i.29]) and TTCN-3 language packages as ETSI ES 202 781 [i.20], ETSI ES 202 782 [i.21], ETSI
ES 202 784 [i.22], ETSI ES 202 785 [i.23], ETSI ES 202 786 [i.24], ETSI ES 202 789 [i.25], ETSI ES 203 022 [i.30],
ETSI ES 203 790 [i.31] may specify extensions to the core language that may define additional rules for the ASN.1 to
TTCN-3 mapping. These additional rules are specified in the relevant other documents and need to be supported only if
the implementation claims to support the other document.
Advanced OO
Configuration Advanced Behavior Performance Continuous TTCN-3
…
and deploy- Matching Features
Parameteri- Types and Real signals Packages
ment support
zation Time Testing
ASN.1 types
and values
IDL types
TTCN-3
XML types
Core
TTCN-3 User
Language
JSON types
& values
The shaded boxes are not
defined in this document
Other types &
values
Figure 1: User's view of the core language and its packages
ETSI
10 ETSI ES 201 873-7 V4.10.1 (2022-04)
5 General
5.1 Approach
TTCN-3 provides a clean interface for using ASN.1 definitions (as specified in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5]) in TTCN-3 modules.
In general, there are two approaches to the integration of other languages with TTCN-3, which will be referred to as
implicit and explicit mapping. The implicit mapping makes use of the import mechanism of TTCN-3, denoted by the
keywords language and import, in which case the TTCN-3 tool shall produce an internal representation of the imported
objects, which representation shall retain all the structural and encoding information. This internal representation is not
accessible by the user. It facilitates the immediate use of the abstract data specified in the other language. Therefore, the
definition of a specific data interface for each of these languages is required.
The explicit mapping translates the definitions of the other language directly into appropriate TTCN-3 language
artefacts. This also means that all information needed for correct encoding and decoding shall be present in the TTCN-3
module(s) generated by this translation.
In case of the ASN.1 to TTCN-3 mapping no TTCN-3 encoding instructions are defined by the present document,
hence only the implicit mapping is specified.
5.2 Conformance and compatibility
For an implementation claiming to support the use of ASN.1 with TTCN-3, all features specified in the present
document will need to be implemented consistently with the requirements given in the present document and in ETSI
ES 201 873-1 [1].
The language mapping presented in the present document is compatible to:
• ETSI ES 201 873-1 [1], V4.9.1.
• ETSI ES 201 873-10 [i.2], V4.5.1.
NOTE: Only the informative annex E uses features from ETSI ES 201 873-10 [i.2].
If later versions of those parts are available and should be used instead, the compatibility of the language mapping
presented in the present document has to be checked individually.
6 Amendments to the core language
Using ASN.1 with TTCN-3 is handled at the static type-value level. Though it mainly means additions described in the
subsequent clauses, some of the core language syntactical structures shall also be amended to support the use of ASN.1.
These are specified in clause A.2.
7 Additional TTCN-3 types
7.1 General
The TTCN-3 types summarized in table 1 shall be supported in addition to those specified in clause 6 of ETSI
ES 201 873-1 [1].
Table 1: Overview of TTCN-3 types
Class of type Keyword Sub-type
objid
Simple basic types list, range
ETSI
11 ETSI ES 201 873-7 V4.10.1 (2022-04)
7.2 The object identifier type
7.2.0 The objid type
The object identifier type shall be supported as follows:
• objid: a type whose distinguished values are the set of all syntactically correct object identifier values. The
value notations for the objid type shall conform to clause 31 of Recommendation ITU-T X.680 [2] with the
exception that hyphens are replaced with underscores.
NOTE 1: This definition also allows object identifier values outside the collection of values defined in
Recommendation ITU-T X.660 [11] (e.g. with a node beneath the root not defined in Recommendation
ITU-T X.660 [11]).
The name form of object identifier components shall be used only for components defined in Recommendation ITU-T
X.660 [11]. These predefined object identifier components are given in annex C for information. In case of any conflict
between Recommendation ITU-T X.660 [11] and annex C of the present document, the former shall take precedence.
In cases when the identifier of a value referenced within an object identifier value notation is identical to any of the
predefined component names, i.e. independently of the position of the predefined component or the referenced value
inside the notation (considering name conversion rules in clause 8.2), the name of the referenced value shall be prefixed
with the name of the module in which it is defined (see definition of ASN.1 modules in clause 12 of Recommendation
ITU-T X.680 [2] and TTCN-3 modules in clause 8.1 of the core language standard ETSI ES 201 873-1 [1]). The prefix
and the identifier shall be separated by a dot (.). Predefined object identifier component names may also be prefixed
with the name "X660".
NOTE 2: To increase readability it is recommended to use the "X660" prefix also in object identifier values
referring to a value identifier that is clashing with any of the predefined component names.
NOTE 3: Rules to resolve name clashes caused by imports are defined in clause 8.2.3.1 of the core language
standard ETSI ES 201 873-1 [1].
EXAMPLE:
objid{itu_t(0) identified_organization(4) etsi(0)}
// or alternatively
objid {itu_t identified_organization etsi(0)}
// or alternatively
objid { 0 4 0}
// or alternatively
const integer etsi := 0;
const objid itu_idOrg := objid{ itu_t identified_organization }
objid{ itu_idOrg etsi } // note, that both names are referencing value definitions
const integer x := 162;
objid{ itu_t recommendation x A.x } // it is mandatory to use the module name ('A')
// to prefix the ambiguous identifier
// or alternatively
objid{ itu_t recommendation X660.x A.x } // the module name shall be present even if
// the "X660" prefix is used
7.2.1 Sub-typing of the objid type
7.2.1.1 Subtrees of the objid type
The object identifier type is a collection of principally infinite set of unique identifier values, each containing a
sequence of components; each given sequence of arbitrary length compose an object identifier node as shown on
figure 2 (see also annex C). Thus, each node of the object identifier tree - except being a unique identifier itself - is the
root of a subtree, containing a potentially infinite number of unique identifiers. The first n components of all the
identifiers in the subtree are identical to the components of the node, being the root of the subtree, where n is the
number of components of that node. Hence, each object identifier node distinguishes also a unique subset (subtype) of
the objid type. Each member of this subtype (the subtree) is longer than the node identifying the subtree.
ETSI
12 ETSI ES 201 873-7 V4.10.1 (2022-04)
Root
joint-iso-itu-t (2)
itu-t (0)
iso (1)
(0) (1) . (i) (0) (1) … (j) (0) (1) … (k)
(0) . (m)
Figure 2: The object identifier tree
Note that object identifiers may also be relative identifiers, i.e. when the given objid value contains only the additional
components related to a defined base node. However, the above remains true for relative object identifiers as well, as
they also do denote a unique node in the object identifier tree (the node defined by the base node + the relative
identifier). If a node is identified by a relative object identifier, all nodes in its subtree will have relative identifiers too.
7.2.1.2 List subtypes
In addition to the types listed in clause 6, table 3 of ETSI ES 201 873-1 [1], value list subtyping of the objid type
shall be supported. For value lists of the objid type the rules in this clause apply. The objid nodes in the list shall be
of objid type and shall be a true subset of the values defined by the objid type or the base type being restricted.
Clause 7.2.1.1 shall govern in determining if the nodes are a true subset. The subtype defined by this list restricts the
allowed values to the concrete nodes on the list and the subtrees identified by them.
EXAMPLE:
//identifies the nodes {0 4 0 0}, {0 4 0 1} and all other nodes beneath them
type objid MyObjids (objid{0 4 0 0}, objid{0 4 0 1});
//Further restricting the base type MyObjids
type MyObjids MyNarrowerObjids (objid{0 4 0 0 1 0}, objid{0 4 1 1}, objid{0 4 1 3});
//invalid definition as the node {0 4 2} is not member of the type MyObjids
type MyObjids MyNarrowestObjids (objid{0 4 2 1});
7.2.1.3 Range subtypes
In addition to the types listed in clause 6, table 3 of ETSI ES 201 873-1 [1], range subtyping of the objid type shall be
supported. For range subtyping of the objid type the rules in this clause apply. The objid nodes determining the
lower and the upper bounds of the subtype shall be of objid type of equal length and shall be a true subset of the
values defined by the objid type or the base type being restricted. Clause 7.2.1.1 shall govern in determining if the
nodes are a true subset. The subtype defined by the range restricts the allowed values to the nodes between the lower
and the upper bounds inclusive and the subtrees identified by them.
EXAMPLE:
//identifies the nodes {0 4 0 0}, {0 4 0 1} … {0 4 0 5} and all other nodes beneath them
type objid MyObjidRange (objid{0 4 0 0} . objid{0 4 0 5});
7.2.1.4 Mixing list and range subtypings
It is allowed to mix the list and the range subtyping mechanisms for objid types. The nodes identified by the different
subtyping mechanisms shall not overlap.
7.2.2 Object identifier values
When defining objid values, rules in clauses 5.4.1.1, 8.2.1, 10 and 11.1 of ETSI ES 201 873-1 [1] and in this clause
shall apply. In case of inconsistency the present document takes precedence.
Each object identifier node is an object identifier value. In this case the value identifies the concrete node (i.e. with a
definite number of components) and does not denote the objid subtree beneath it (see clause 7.2.1.1).
ETSI
13 ETSI ES 201 873-7 V4.10.1 (2022-04)
7.2.3 Using objid values to identify modules
7.2.3.1 Identifying module definitions
When ASN.1 is supported, module names (of the form of a TTCN-3 identifier) may optionally be followed by an object
identifier, which shall be a valid value as defined in Recommendation ITU-T X.660 [11].
NOTE: Module names in a test suite 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 TTCN-3 identifiers
(see clause 8.2.3.1 of ETSI ES 201 873-1 [1]) is unable to resolve such kind of clashes.
7.2.3.2 Identifying modules in import statements
When ASN.1 is supported, in addition to the module names, their object identifiers may also be provided in TTCN-3
import statements. If an object identifier is used as part of the module identifier, this object identifier shall be used by
TTCN-3 test systems to identify the correct module.
7.2.4 Object identifier templates
7.2.4.0 General
When defining templates of objid types, rules in clause 15 and annex B of ETSI ES 201 873-1 [1] and in this clause
shall apply. In case of inconsistency the present document takes precedence.
7.2.4.1 In-line templates
The type of objid values can be identified from the value notation alone, hence in addition to the types listed in note 2
of clause 15.4 in ETSI ES 201 873-1 [1], the type specification may also be omitted in case of objid values.
7.2.4.2 Template matching mechanisms
Applicability of matching mechanisms to templates of objid types is defined in table 2.
Table 2: TTCN-3 Matching Mechanisms
Used with values of Value Instead of values Inside values Attributes
S O C V A A R S S P A A P L I
p m o a n n
a u u a n n e e f
e i m l y y n p b t y y r n P
c t p u V V g e t t E E m g r
i V
l e a a e r y e l l u t e
f a e L l l s p r e e t h s
i l m i u u e e n m m a R
e
c u e s e e t e e t e n
V e n t (?) O n n i s t
a t r t t o t
l e N (?) s n r
u d o O i
e L n r
c
I e N t
s (*) o i
t
n o
e n
(*)
objid
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
(see (see (see
note) note) note)
NOTE: Can be assigned to templates, however when used, shall be applied to optional fields of record and set types
only (without restriction on the type of that field).
ETSI
14 ETSI ES 201 873-7 V4.10.1 (2022-04)
The matching mechanisms SpecificValue, OmitValue, AnyValue, AnyValueOrNone and IfPresent are applicable to
objid fields as well according to the rules defined in ETSI ES 201 873-1 [1].
The value list and complemented value list matching mechanisms can also be used for objid templates and template
fields. Rules in clauses B.1.2.1 and B.1.2.2 of ETSI ES 201 873-1 [1] also shall apply to objid templates.
NOTE: This also means that only the concrete node values
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...