ETSI ES 202 785 V1.10.1 (2025-09)
Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Behaviour Types
Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Behaviour Types
RES/MTS-202785v1.10.1
Metode za preskušanje in specificiranje (MTS) - 3. različica zapisa preskušanja in krmiljenja preskusov - Razširitev nabora jezikov TTCN-3: tipi obnašanja
General Information
Standards Content (Sample)
Final draft ETSI ES 202 785 V1.10.1 (2025-06)
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
TTCN-3 Language Extensions: Behaviour Types
2 Final draft ETSI ES 202 785 V1.10.1 (2025-06)
Reference
RES/MTS-202785v1.10.1
Keywords
conformance, testing, TTCN-3
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 the
ETSI Search & Browse Standards application.
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 on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
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 2025.
All rights reserved.
ETSI
3 Final draft ETSI ES 202 785 V1.10.1 (2025-06)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 6
4 Package conformance and compatibility . 6
5 Package concepts for the core language . 7
5.1 Extension to ETSI ES 201 873-1, clause 5 (Basic language elements) . 7
5.2 Extension to ETSI ES 201 873-1, clause 6 (Types and values). 8
5.3 Extension to ETSI ES 201 873-1, clause 7 (Expressions) . 14
5.4 Extension to ETSI ES 201 873-1, clause 8 (Modules) . 14
5.5 Extension to ETSI ES 201 873-1, clause 10 (Declaring constants) . 15
5.6 Extension to ETSI ES 201 873-1, clause 11 (Declaring variables) . 15
5.7 Extension to ETSI ES 201 873-1, clause 15 (Declaring templates) . 15
5.8 Extension to ETSI ES 201 873-1, clause 16 (Functions, altsteps and test cases) . 16
5.9 Extension to ETSI ES 201 873-1, clause 19 (Basic program statements) . 16
5.10 Extension to ETSI ES 201 873-1, clause 20 (Statement and operations for alternative behaviours) . 17
5.11 Extension to ETSI ES 201 873-1, clause 21 (Configuration Operations) . 17
5.12 Extension to ETSI ES 201 873-1, clause 26 (Module control) . 18
5.13 Extension to ETSI ES 201 873-1, annex A (BNF and static semantics) . 19
5.13.0 New keywords and TTCN-3 syntax BNF productions . 19
5.13.1 Changes to ETSI ES 201 873-1, clause A.1.6 (TTCN-3 syntax BNF productions) . 19
6 Package semantics . 20
6.1 Replacements . 20
6.2 Activate statement . 20
6.3 Replacements in Execute statement's operational semantics . 21
6.3.0 Execute statement . 21
6.3.1 Flow graph segment . 22
6.4 Replacements in Function call's operational semantics . 23
6.4.0 Function call . 23
6.4.1 Flow graph segment . 25
6.4.2 Flow graph segment . 25
6.5 Start component operation . 25
7 TRI extensions for the package . 28
8 TCI extensions for the package . 28
8.1 Extensions to ETSI ES 201 873-6, clause 7 (TTCN-3 control interface and operations). 28
8.2 Extensions to ETSI ES 201 873-6, clause 8 (Java language mapping) . 29
8.3 Extensions to ETSI ES 201 873-6, clause 9 (ANSI C language mapping) . 30
8.4 Extensions to ETSI ES 201 873-6, clause 10 (C++ language mapping) . 30
8.5 Extensions to ETSI ES 201 873-6, clause 11 (W3C XML mapping) . 32
9 Extensions to TTCN-3 documentation comment specification for the package . 42
9.1 Extensions to ETSI ES 201 873-10, annex A (where Tags can be used) . 42
History . 44
ETSI
4 Final draft ETSI ES 202 785 V1.10.1 (2025-06)
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 IPR online database.
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™, LTE™ and 5G™ logo 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 Membership Approval Procedure.
The use of underline (additional text) highlights the differences between base document and extended
documents.
The present document relates to the multi-part standard ETSI ES 201 873 covering the Testing and Test Control
Notation version 3, as identified in ETSI ES 201 873-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
5 Final draft ETSI ES 202 785 V1.10.1 (2025-06)
1 Scope
The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of
all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing
(including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of
APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including
interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer
protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines types for behaviour definitions in TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages and guidelines for this package in combination with other packages is
outside the s
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.