SIST ES 203 119-8 V1.3.1:2025
(Main)Methods for Testing and Specification (MTS) - The Test Description Language (TDL) - Part 8: Textual Syntax
Methods for Testing and Specification (MTS) - The Test Description Language (TDL) - Part 8: Textual Syntax
The present document specifies the concrete textual syntax of the Test Description Language (TDL). The intended use of the present document is to serve as the basis for the development of textual TDL tools and TDL specifications. The meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
NOTE: OMG®, UML ® and OCL™ are the trademarks of Object Management Group (OMG). Xtext™ is
trademark of the Eclipse ® Foundation. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of the products named.
Metode za preskušanje in specificiranje (MTS) - Jezik za opis preskusa (TDL) - 8. del: Besedilna sintaksa
Ta dokument določa konkretno besedilno skladnjo jezika za opis preskusa (TDL). Ta dokument se predvidoma uporablja kot osnova za razvoj orodij besedilnega jezika za opis preskusa in specifikacij jezika za opis preskusa. Metamodel jezika za opis preskusa in pomeni metarazredov so opisani v standardu ETSI ES 203 119-1 [1]. OPOMBA: OMG®, UML® OCL™ so blagovne znamke skupine Object Management Group (OMG). Xtext™ je blagovna znamka neprofitne organizacije Eclipse ® Foundation. Te informacije so navedene za boljše razumevanje standarda s strani uporabnikov in ne pomenijo, da ETSI podpira imenovane izdelke.
General Information
Standards Content (Sample)
Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Part 8: Textual Syntax
2 Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
Reference
RES/MTS-203119-8v1.3.1
Keywords
language, MBT, methodology, testing, TSS&TP,
TTCN-3, UML
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 203 119-8 V1.3.1 (2025-05)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Basic principles . 9
4.1 Introduction . 9
4.2 Document Structure . 9
4.3 Grammar Language . 9
4.3.1 Overview . 9
4.3.2 Operators . 10
4.3.3 Terminal rules and keywords . 10
4.3.4 Production rules . 10
4.4 Conformance . 11
5 General rules . 11
5.1 Identities and references . 11
5.2 Models and importing . 11
5.3 Linking . 12
5.4 Alternative syntaxes . 12
5.5 Terminals . 12
5.6 File format . 14
6 Production Rules . 14
6.1 Foundation . 14
6.1.1 Element . 14
6.1.2 NamedElement . 15
6.1.3 ElementImport . 15
6.1.4 Package . 16
6.1.5 PackageableElement . 16
6.1.6 Comment . 17
6.1.7 Annotation . 17
6.1.8 AnnotationType . 18
6.1.9 TestObjective . 18
6.1.10 Extension . 19
6.1.11 ConstraintType . 19
6.1.12 Constraint . 19
6.2 Data . 20
6.2.1 DataResourceMapping . 20
6.2.2 DataElementMapping . 20
6.2.3 ParameterMapping . 20
6.2.4 DataType . 21
6.2.5 SimpleDataType . 21
6.2.6 SimpleDataInstance . 21
6.2.7 StructuredDataType . 22
6.2.8 Member . 22
6.2.9 StructuredDataInstance . 23
6.2.10 MemberAssignment . 23
6.2.11 CollectionDataType . 23
ETSI
4 Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
6.2.12 CollectionDataInstance . 24
6.2.13 ProcedureSignature . 24
6.2.14 ProcedureParameter . 24
6.2.15 ParameterKind . 25
6.2.16 Parameter . 25
6.2.17 FormalParameter . 25
6.2.18 Variable . 26
6.2.19 Action . 26
6.2.20 Function . 26
6.2.21 UnassignedMemberTreatment . 27
6.2.22 PredefinedFunction . 27
6.2.23 EnumDataType . 28
6.2.24 DataUse . 28
6.2.25 ParameterBinding . 29
6.2.26 MemberReference . 29
6.2.27 StaticDataUse . 30
6.2.28 DataInstanceUse . 30
6.2.29 SpecialValueUse . 31
6.2.30 AnyValue . 31
6.2.31 AnyValueOrOmit . 31
6.2.32 OmitValue. 32
6.2.33 LiteralValueUse . 32
6.2.34 DynamicDataUse . 32
6.2.35 FunctionCall . 33
6.2.36 FormalParameterUse . 33
6.2.37 VariableUse . 33
6.2.38 PredefinedFunctionCall . 34
6.2.39 DataElementUse . 34
6.2.40 CastDataUse . 35
6.3 Time . 35
6.3.1 Time . 35
6.3.2 TimeLabel . 36
6.3.3 TimeLabelUse . 36
6.3.4 TimeLabelUseKind . 36
6.3.5 TimeConstraint . 37
6.3.6 Timer . 37
6.3.7 TimeOperation . 37
6.3.8 Wait . 37
6.3.9 Quiescence . 38
6.3.10 TimerOperation . 38
6.3.11 TimerStart . 38
6.3.12 TimerStop . 39
6.3.13 TimeOut . 39
6.4 Test Configuration . 39
6.4.1 GateType . 39
6.4.2 GateTypeKind . 40
6.4.3 GateInstance . 40
6.4.4 ComponentType . 40
6.4.5 ComponentInstance . 41
6.4.6 ComponentInstanceRole . 41
6.4.7 GateReference . 41
6.4.8 Connection . 42
6.4.9 TestConfiguration . 42
6.5 Test Behaviour . 43
6.5.1 TestDescription . 43
6.5.2 BehaviourDescription . 43
6.5.3 Behaviour . 44
6.5.4 Block . 44
6.5.5 LocalExpression . 44
6.5.6 CombinedBehaviour . 45
6.5.7 SingleCombinedBehaviour . 45
6.5.8 CompoundBehaviour . 46
ETSI
5 Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
6.5.9 BoundedLoopBehaviour . 46
6.5.10 UnboundedLoopBehaviour . 46
6.5.11 OptionalBehaviour . 47
6.5.12 MultipleCombinedBehaviour . 47
6.5.13 ConditionalBehaviour . 47
6.5.14 AlternativeBehaviour . 48
6.5.15 ParallelBehaviour . 49
6.5.16 ExceptionalBehaviour . 49
6.5.17 DefaultBehaviour . 49
6.5.18 InterruptBehaviour . 50
6.5.19 PeriodicBehaviour . 50
6.5.20 AtomicBehaviour . 51
6.5.21 Break . 52
6.5.22 Stop . 52
6.5.23 VerdictAssignment . 52
6.5.24 Assertion . 53
6.5.25 Interaction . 53
6.5.26 Message . 53
6.5.27 Target . 54
6.5.28 ValueAssignment . 54
6.5.29 ProcedureCall . 55
6.5.30 TestDescriptionReference . 55
6.5.31 ComponentInstanceBinding . 56
6.5.32 ActionBehaviour . 56
6.5.33 ActionReference . 57
6.5.34 InlineAction . 57
6.5.35 Assignment . 57
Annex A (informative): Technical Representation of the Complete Textual Syntax . 58
Annex B (informative): Examples . 59
B.0 Overview . 59
B.1 Illustration of Data Use . 59
B.2 Interface Testing . 61
B.3 Interoperability Testing . 64
History . 67
ETSI
6 Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
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 (MAP).
The present document is part 8 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
7 Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
1 Scope
The present document specifies the concrete textual syntax of the Test Description Language (TDL). The intended use
of the present document is to serve as the basis for the development of textual TDL tools and TDL specifications. The
meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
® ®
NOTE: OMG , UML and OCL™ are the trademarks of Object Management Group (OMG). Xtext™ is ®
trademark of the Eclipse Foundation. This information is given for the convenience of users of the
present document and does not constitute an endorsement by ETSI of the products named.
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 in the
ETSI docbox.
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 203 119-1: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 1: Abstract Syntax and Associated Semantics".
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 may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document. ®
[i.1] Eclipse Foundation: "Xtext - The Grammar Language Website".
[i.2] ETSI TS 136 523-1 (V10.2.0): "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification (3GPP TS 36.523-1 version 10.2.0 Release 10)".
[i.3] ETSI TS 186 011-2: "Core Network and Interoperability Testing (INT); IMS NNI Interoperability
Test Specifications (3GPP Release 10); Part 2: Test descriptions for IMS NNI Interoperability".
[i.4] ETSI: "TDL Open Source Project".
[i.5] ETSI ES 203 119-4: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 4: Structured Test Objective Specification (Extension)".
[i.6] ETSI ES 203 119-7: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 7: Extended Test Configurations".
ETSI
8 Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
[i.7] ETSI TS 129 165: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; Inter-IMS Network to Network Interface
(NNI) (3GPP TS 29.165)".
[i.8] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; IP multimedia call control protocol based
on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP
TS 24.229)".
[i.9] ETSI TS 136 213: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures (3GPP TS 36.213)".
[i.10] ETSI TS 136 508: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing
(3GPP TS 36.508)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 203 119-1 [1] and the following apply:
derivation: construction of an abstract syntactical structure, such as a model instance conforming to a meta-model,
from a textual representation by applying the structural rules of a grammar, and potential mappings to the underlying
meta-model
(formal) grammar: set of structural rules that define how to form valid strings from a language's alphabet that obey the
syntax of the language
non-terminal symbol: placeholder for (groups of) other symbols that describe elements in a specified language
(production) rule: definition of a structured rule for the derivation of a non-terminal symbol based on other
non-terminal symbols and terminal symbols
terminal symbol: symbols that appear explicitly in a specified language, such as a keyword, an identifier or other
tokens
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
EBNF Extended Backus-Naur Form
IMS IP Multimedia Subsystem
OCL Object Constraint Language™ ®
OMG Object Management Group
SUT System Under Test
TDL Test Description Language
TTCN-3 Testing and Test Control Notation version 3 ®
UML Unified Modelling Language
URI Uniform Record Identifier
ETSI
9 Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
4 Basic principles
4.1 Introduction
The meta-model of the Test Description Language (TDL) is specified in ETSI ES 203 119-1 [1]. The presentation
format of the meta-model can be different according to the needs of the users or the requirements of the domain, where
the TDL is applied. These presentation formats can either be text-oriented or graphic-oriented and may cover all the
functionalities of the TDL meta-model or just a part of it, which is relevant to satisfy the needs of a specific application
domain.
The present document specifies a concrete textual syntax that provides a textual representation for the commonly used
functionality of the TDL meta-model. In the current version of the present document, certain parts, such as 'Comment's
and 'Annotation's in 'DataUse' elements, are syntactically excluded. Syntactic specifications for these may be added in
future versions of the present document as needed.
The present document specifies the TDL textual file format, where the textual representations of the instances of the
TDL meta-classes may be placed. A textual representation may contain keywords, delimiters, and textual labels within a
defined structure. The rules, how these structures shall be interpreted, are described by means of Extended Backus-Naur
Form (EBNF)-like expressions. In particular, in addition to the syntactical structure, the EBNF-like expressions also
indicate how the textual labels and structures are mapped to the TDL meta-model.
4.2 Document Structure
The present document specifies the concrete textual syntax of the Test Description Language (TDL).
Clause 5 specifies general rules for the specification and use of the TDL textual file format.
Clause 6 specifies the concrete production rules defined for the TDL meta-classes (the meta-model of TDL and the
meanings of the meta-classes are described in ETSI ES 203 119-1 [1]):
• Foundation (clause 6.1)
• Data (clause 6.2)
• Time (clause 6.3)
• Test Configuration (clause 6.4)
• Test Behaviour (clause 6.5)
At the end of the present document several examples illustrating the features of the TDL Textual Syntax can be found.
4.3 Grammar Language
4.3.1 Overview
The rules that define the textual syntax of the TDL are described in present document using the grammar language of
the Xtext framework. In addition to defining the lexical structure of the TDL syntax the grammar language also
provides means for mapping those textual constructs to the TDL meta-model. Additional rules such as identity
resolution and linking are described where applicable to provide complete mapping of textual TDL to the TDL model.
The grammar of textual TDL is composed of a number of grammar rules organized in a tree. The grammar structure
follows the logical structure of the TDL meta-model and the root of the grammar is the 'Package' production rule.
Production rules are used to construct model objects and assign values to the properties of those objects. Production
rules consist of keywords (character literals) and calls to production rules, data type rules and terminal rules (which
correspond to tokens of text).
The following clauses describe the syntax of the grammar language. See Xtext documentation for further details [i.1].
ETSI
10 Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
4.3.2 Operators
Various operators are used in grammar rule definitions to specify the order and cardinality of keywords and rule calls.
Terminal rule specific operators are used to express various textual constructs. Production rule specific operators are
used to define assignments and cross-references.
Following operators are used in all rule definitions:
• '?' indicates that preceding construct shall occur 0 or 1 time;
• '*' indicates that preceding construct shall occur 0 or more times;
• '+' indicates that preceding construct shall occur 1 or more times;
• '|' is used between alternative constructs; and
• '(' and ')' are used to group constructs defined in between.
Following operators are used in terminal rule definitions:
• '!' is used to negate a construct;
• '->' is used to indicate that everything is ignored until the following construct is detected;
• '.' is used between characters to define a range; and
• '.' denotes any character.
Following operators are used in production rule definitions:
• '=' is used to define a simple assignment of a right hand construct to a property on the left;
• '+=' is used for assigning (adding to) multi-valued property;
• '?=' is used for assigning the value 'true' to a Boolean property on the condition that the right hand side
construct is present; and
• '[', '|' and ']' are used to define a cross-reference.
Various special symbols are included in the grammar definitions of production rules that are included solely as
implementation detail (to help the generation of a parser for textual TDL) and do not alter the definition of the syntax.
Such symbols include '->' and '=>'.
4.3.3 Terminal rules and keywords
Lexical tokens in the TDL grammar are either keywords of character sequences that are matched and consumed by
terminal rules during parsing. In the grammar definition, keywords are placed between apostrophes (').
Terminal rule declarations start with the keyword 'terminal' followed by the rule name (in upper-case letters by
convention). The rule name is followed by 'returns' keyword and the reference to a data type that is used for creating a
value using the consumed token.
The definition of the rule starts with a colon (':') and ends with a semi-colon (';'). Terminal rule definitions consist of
terminal rule calls (indicated by rule name), characters and operators.
EXAMPLE: Terminal INT returns EInt: ('0'.'9')+;
Some terminal rules (such as comments and whitespace) are defined as hidden in TDL grammar and corresponding text
shall be allowed anywhere in textual TDL (outside of tokens).
4.3.4 Production rules
Production rules are used to create model objects or data values. The rules that return a data type instead of a meta-class
are known as data type rules.
ETSI
11 Final draft ETSI ES 203 119-8 V1.3.1 (2025-05)
Production rule declarations start with the rule name followed by 'returns' keyword and the reference to the meta-class
that defines the object that is produced by the rule. The definition of the rule starts with a colon (':') and ends with a
semi-colon (';'). Production rule definitions consist of rule calls, keywords and operators.
EXAMPLE 1: Comment returns tdl::Comment:
'Note:' body=EString
;
An assignment is defined as a property name followed by an assignment operator (see clause 4.3.2) followed by a rule
call (name of production or data type rule) or a cross-reference. A cross-reference is defined as a meta-class reference
followed by '|' and a terminal rule call that defines the format for the identifier. The cross-reference definition is placed
between square brackets ('[' and ']').
EXAMPLE 2: Annotation returns tdl::Annotation:
'@' key=[tdl::AnnotationType|Identifier]
(':' value=EString)?
;
Production rule calls may also be used without assignment. In that case the model object that is returned from the
calling rule is the one that is created in the called rule.
Production rules may be created as fragments by prefixing the declaration with the 'fragment' keyword. In that case the
rule does not produce an object by itself but rather assigns to properties of the object that is created in the calling rule.
Fragment rules are always unassigned.
4.4 Conformance
For an implementation claiming to conform to this version of the TDL Concrete Textual Syntax, all features specified in
the present document and in ETSI ES 203 119-1 [1] shall be implemented consistently with the requirements given in
the present document and ETSI ES 203 119-1 [1].
5 General rules
5.1 Identities and references
In TDL models, references between objects are based on unique identifiers that are generated by the modelling
framework and stored in model files. Such identifiers are generally hidden from the user. In textual TDL, all attributes
shall be part of the text document and the use of such identifiers is not feasible.
In textual TDL,
...
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Part 8: Textual Syntax
2 ETSI ES 203 119-8 V1.3.1 (2025-07)
Reference
RES/MTS-203119-8v1.3.1
Keywords
language, MBT, methodology, testing, TSS&TP,
TTCN-3, UML
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 ETSI ES 203 119-8 V1.3.1 (2025-07)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Basic principles . 9
4.1 Introduction . 9
4.2 Document Structure . 9
4.3 Grammar Language . 9
4.3.1 Overview . 9
4.3.2 Operators . 10
4.3.3 Terminal rules and keywords . 10
4.3.4 Production rules . 10
4.4 Conformance . 11
5 General rules . 11
5.1 Identities and references . 11
5.2 Models and importing . 11
5.3 Linking . 12
5.4 Alternative syntaxes . 12
5.5 Terminals . 12
5.6 File format . 14
6 Production Rules . 14
6.1 Foundation . 14
6.1.1 Element . 14
6.1.2 NamedElement . 15
6.1.3 ElementImport . 15
6.1.4 Package . 16
6.1.5 PackageableElement . 16
6.1.6 Comment . 17
6.1.7 Annotation . 17
6.1.8 AnnotationType . 18
6.1.9 TestObjective . 18
6.1.10 Extension . 19
6.1.11 ConstraintType . 19
6.1.12 Constraint . 19
6.2 Data . 20
6.2.1 DataResourceMapping . 20
6.2.2 DataElementMapping . 20
6.2.3 ParameterMapping . 20
6.2.4 DataType . 21
6.2.5 SimpleDataType . 21
6.2.6 SimpleDataInstance . 21
6.2.7 StructuredDataType . 22
6.2.8 Member . 22
6.2.9 StructuredDataInstance . 23
6.2.10 MemberAssignment . 23
6.2.11 CollectionDataType . 23
ETSI
4 ETSI ES 203 119-8 V1.3.1 (2025-07)
6.2.12 CollectionDataInstance . 24
6.2.13 ProcedureSignature . 24
6.2.14 ProcedureParameter . 24
6.2.15 ParameterKind . 25
6.2.16 Parameter . 25
6.2.17 FormalParameter . 25
6.2.18 Variable . 26
6.2.19 Action . 26
6.2.20 Function . 26
6.2.21 UnassignedMemberTreatment . 27
6.2.22 PredefinedFunction . 27
6.2.23 EnumDataType . 28
6.2.24 DataUse . 28
6.2.25 ParameterBinding . 29
6.2.26 MemberReference . 29
6.2.27 StaticDataUse . 30
6.2.28 DataInstanceUse . 30
6.2.29 SpecialValueUse . 31
6.2.30 AnyValue . 31
6.2.31 AnyValueOrOmit . 31
6.2.32 OmitValue. 32
6.2.33 LiteralValueUse . 32
6.2.34 DynamicDataUse . 32
6.2.35 FunctionCall . 33
6.2.36 FormalParameterUse . 33
6.2.37 VariableUse . 33
6.2.38 PredefinedFunctionCall . 34
6.2.39 DataElementUse . 34
6.2.40 CastDataUse . 35
6.3 Time . 35
6.3.1 Time . 35
6.3.2 TimeLabel . 36
6.3.3 TimeLabelUse . 36
6.3.4 TimeLabelUseKind . 36
6.3.5 TimeConstraint . 37
6.3.6 Timer . 37
6.3.7 TimeOperation . 37
6.3.8 Wait . 37
6.3.9 Quiescence . 38
6.3.10 TimerOperation . 38
6.3.11 TimerStart . 38
6.3.12 TimerStop . 39
6.3.13 TimeOut . 39
6.4 Test Configuration . 39
6.4.1 GateType . 39
6.4.2 GateTypeKind . 40
6.4.3 GateInstance . 40
6.4.4 ComponentType . 40
6.4.5 ComponentInstance . 41
6.4.6 ComponentInstanceRole . 41
6.4.7 GateReference . 41
6.4.8 Connection . 42
6.4.9 TestConfiguration . 42
6.5 Test Behaviour . 43
6.5.1 TestDescription . 43
6.5.2 BehaviourDescription . 43
6.5.3 Behaviour . 44
6.5.4 Block . 44
6.5.5 LocalExpression . 44
6.5.6 CombinedBehaviour . 45
6.5.7 SingleCombinedBehaviour . 45
6.5.8 CompoundBehaviour . 46
ETSI
5 ETSI ES 203 119-8 V1.3.1 (2025-07)
6.5.9 BoundedLoopBehaviour . 46
6.5.10 UnboundedLoopBehaviour . 46
6.5.11 OptionalBehaviour . 47
6.5.12 MultipleCombinedBehaviour . 47
6.5.13 ConditionalBehaviour . 47
6.5.14 AlternativeBehaviour . 48
6.5.15 ParallelBehaviour . 49
6.5.16 ExceptionalBehaviour . 49
6.5.17 DefaultBehaviour . 49
6.5.18 InterruptBehaviour . 50
6.5.19 PeriodicBehaviour . 50
6.5.20 AtomicBehaviour . 51
6.5.21 Break . 52
6.5.22 Stop . 52
6.5.23 VerdictAssignment . 52
6.5.24 Assertion . 53
6.5.25 Interaction . 53
6.5.26 Message . 53
6.5.27 Target . 54
6.5.28 ValueAssignment . 54
6.5.29 ProcedureCall . 55
6.5.30 TestDescriptionReference . 55
6.5.31 ComponentInstanceBinding . 56
6.5.32 ActionBehaviour . 56
6.5.33 ActionReference . 57
6.5.34 InlineAction . 57
6.5.35 Assignment . 57
Annex A (informative): Technical Representation of the Complete Textual Syntax . 58
Annex B (informative): Examples . 59
B.0 Overview . 59
B.1 Illustration of Data Use . 59
B.2 Interface Testing . 61
B.3 Interoperability Testing . 64
History . 67
ETSI
6 ETSI ES 203 119-8 V1.3.1 (2025-07)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document is part 8 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
7 ETSI ES 203 119-8 V1.3.1 (2025-07)
1 Scope
The present document specifies the concrete textual syntax of the Test Description Language (TDL). The intended use
of the present document is to serve as the basis for the development of textual TDL tools and TDL specifications. The
meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
® ®
NOTE: OMG , UML and OCL™ are the trademarks of Object Management Group (OMG). Xtext™ is ®
trademark of the Eclipse Foundation. This information is given for the convenience of users of the
present document and does not constitute an endorsement by ETSI of the products named.
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 in the
ETSI docbox.
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 203 119-1: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 1: Abstract Syntax and Associated Semantics".
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 may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document. ®
[i.1] Eclipse Foundation: "Xtext - The Grammar Language Website".
[i.2] ETSI TS 136 523-1 (V10.2.0): "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification (3GPP TS 36.523-1 version 10.2.0 Release 10)".
[i.3] ETSI TS 186 011-2: "Core Network and Interoperability Testing (INT); IMS NNI Interoperability
Test Specifications (3GPP Release 10); Part 2: Test descriptions for IMS NNI Interoperability".
[i.4] ETSI: "TDL Open Source Project".
[i.5] ETSI ES 203 119-4: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 4: Structured Test Objective Specification (Extension)".
[i.6] ETSI ES 203 119-7: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 7: Extended Test Configurations".
ETSI
8 ETSI ES 203 119-8 V1.3.1 (2025-07)
[i.7] ETSI TS 129 165: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; Inter-IMS Network to Network Interface
(NNI) (3GPP TS 29.165)".
[i.8] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; IP multimedia call control protocol based
on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP
TS 24.229)".
[i.9] ETSI TS 136 213: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures (3GPP TS 36.213)".
[i.10] ETSI TS 136 508: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing
(3GPP TS 36.508)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 203 119-1 [1] and the following apply:
derivation: construction of an abstract syntactical structure, such as a model instance conforming to a meta-model,
from a textual representation by applying the structural rules of a grammar, and potential mappings to the underlying
meta-model
(formal) grammar: set of structural rules that define how to form valid strings from a language's alphabet that obey the
syntax of the language
non-terminal symbol: placeholder for (groups of) other symbols that describe elements in a specified language
(production) rule: definition of a structured rule for the derivation of a non-terminal symbol based on other
non-terminal symbols and terminal symbols
terminal symbol: symbols that appear explicitly in a specified language, such as a keyword, an identifier or other
tokens
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
EBNF Extended Backus-Naur Form
IMS IP Multimedia Subsystem
OCL Object Constraint Language™ ®
OMG Object Management Group
SUT System Under Test
TDL Test Description Language
TTCN-3 Testing and Test Control Notation version 3 ®
UML Unified Modelling Language
URI Uniform Record Identifier
ETSI
9 ETSI ES 203 119-8 V1.3.1 (2025-07)
4 Basic principles
4.1 Introduction
The meta-model of the Test Description Language (TDL) is specified in ETSI ES 203 119-1 [1]. The presentation
format of the meta-model can be different according to the needs of the users or the requirements of the domain, where
the TDL is applied. These presentation formats can either be text-oriented or graphic-oriented and may cover all the
functionalities of the TDL meta-model or just a part of it, which is relevant to satisfy the needs of a specific application
domain.
The present document specifies a concrete textual syntax that provides a textual representation for the commonly used
functionality of the TDL meta-model. In the current version of the present document, certain parts, such as 'Comment's
and 'Annotation's in 'DataUse' elements, are syntactically excluded. Syntactic specifications for these may be added in
future versions of the present document as needed.
The present document specifies the TDL textual file format, where the textual representations of the instances of the
TDL meta-classes may be placed. A textual representation may contain keywords, delimiters, and textual labels within a
defined structure. The rules, how these structures shall be interpreted, are described by means of Extended Backus-Naur
Form (EBNF)-like expressions. In particular, in addition to the syntactical structure, the EBNF-like expressions also
indicate how the textual labels and structures are mapped to the TDL meta-model.
4.2 Document Structure
The present document specifies the concrete textual syntax of the Test Description Language (TDL).
Clause 5 specifies general rules for the specification and use of the TDL textual file format.
Clause 6 specifies the concrete production rules defined for the TDL meta-classes (the meta-model of TDL and the
meanings of the meta-classes are described in ETSI ES 203 119-1 [1]):
• Foundation (clause 6.1)
• Data (clause 6.2)
• Time (clause 6.3)
• Test Configuration (clause 6.4)
• Test Behaviour (clause 6.5)
At the end of the present document several examples illustrating the features of the TDL Textual Syntax can be found.
4.3 Grammar Language
4.3.1 Overview
The rules that define the textual syntax of the TDL are described in present document using the grammar language of
the Xtext framework. In addition to defining the lexical structure of the TDL syntax the grammar language also
provides means for mapping those textual constructs to the TDL meta-model. Additional rules such as identity
resolution and linking are described where applicable to provide complete mapping of textual TDL to the TDL model.
The grammar of textual TDL is composed of a number of grammar rules organized in a tree. The grammar structure
follows the logical structure of the TDL meta-model and the root of the grammar is the 'Package' production rule.
Production rules are used to construct model objects and assign values to the properties of those objects. Production
rules consist of keywords (character literals) and calls to production rules, data type rules and terminal rules (which
correspond to tokens of text).
The following clauses describe the syntax of the grammar language. See Xtext documentation for further details [i.1].
ETSI
10 ETSI ES 203 119-8 V1.3.1 (2025-07)
4.3.2 Operators
Various operators are used in grammar rule definitions to specify the order and cardinality of keywords and rule calls.
Terminal rule specific operators are used to express various textual constructs. Production rule specific operators are
used to define assignments and cross-references.
Following operators are used in all rule definitions:
• '?' indicates that preceding construct shall occur 0 or 1 time;
• '*' indicates that preceding construct shall occur 0 or more times;
• '+' indicates that preceding construct shall occur 1 or more times;
• '|' is used between alternative constructs; and
• '(' and ')' are used to group constructs defined in between.
Following operators are used in terminal rule definitions:
• '!' is used to negate a construct;
• '->' is used to indicate that everything is ignored until the following construct is detected;
• '.' is used between characters to define a range; and
• '.' denotes any character.
Following operators are used in production rule definitions:
• '=' is used to define a simple assignment of a right hand construct to a property on the left;
• '+=' is used for assigning (adding to) multi-valued property;
• '?=' is used for assigning the value 'true' to a Boolean property on the condition that the right hand side
construct is present; and
• '[', '|' and ']' are used to define a cross-reference.
Various special symbols are included in the grammar definitions of production rules that are included solely as
implementation detail (to help the generation of a parser for textual TDL) and do not alter the definition of the syntax.
Such symbols include '->' and '=>'.
4.3.3 Terminal rules and keywords
Lexical tokens in the TDL grammar are either keywords of character sequences that are matched and consumed by
terminal rules during parsing. In the grammar definition, keywords are placed between apostrophes (').
Terminal rule declarations start with the keyword 'terminal' followed by the rule name (in upper-case letters by
convention). The rule name is followed by 'returns' keyword and the reference to a data type that is used for creating a
value using the consumed token.
The definition of the rule starts with a colon (':') and ends with a semi-colon (';'). Terminal rule definitions consist of
terminal rule calls (indicated by rule name), characters and operators.
EXAMPLE: Terminal INT returns EInt: ('0'.'9')+;
Some terminal rules (such as comments and whitespace) are defined as hidden in TDL grammar and corresponding text
shall be allowed anywhere in textual TDL (outside of tokens).
4.3.4 Production rules
Production rules are used to create model objects or data values. The rules that return a data type instead of a meta-class
are known as data type rules.
ETSI
11 ETSI ES 203 119-8 V1.3.1 (2025-07)
Production rule declarations start with the rule name followed by 'returns' keyword and the reference to the meta-class
that defines the object that is produced by the rule. The definition of the rule starts with a colon (':') and ends with a
semi-colon (';'). Production rule definitions consist of rule calls, keywords and operators.
EXAMPLE 1: Comment returns tdl::Comment:
'Note:' body=EString
;
An assignment is defined as a property name followed by an assignment operator (see clause 4.3.2) followed by a rule
call (name of production or data type rule) or a cross-reference. A cross-reference is defined as a meta-class reference
followed by '|' and a terminal rule call that defines the format for the identifier. The cross-reference definition is placed
between square brackets ('[' and ']').
EXAMPLE 2: Annotation returns tdl::Annotation:
'@' key=[tdl::AnnotationType|Identifier]
(':' value=EString)?
;
Production rule calls may also be used without assignment. In that case the model object that is returned from the
calling rule is the one that is created in the called rule.
Production rules may be created as fragments by prefixing the declaration with the 'fragment' keyword. In that case the
rule does not produce an object by itself but rather assigns to properties of the object that is created in the calling rule.
Fragment rules are always unassigned.
4.4 Conformance
For an implementation claiming to conform to this version of the TDL Concrete Textual Syntax, all features specified in
the present document and in ETSI ES 203 119-1 [1] shall be implemented consistently with the requirements given in
the present document and ETSI ES 203 119-1 [1].
5 General rules
5.1 Identities and references
In TDL models, references between objects are based on unique identifiers that are generated by the modelling
framework and stored in model files. Such identifiers are generally hidden from the user. In textual TDL, all attributes
shall be part of the text document and the use of such identifiers is not feasible.
In textual TDL, objects are identified by 'name' or 'qualifiedName' property. The allowed values for the 'name' property
are restricted by the terminal rule 'ID' (see clause 5.5). The exception to this rule is made for objects that are pred
...
SLOVENSKI STANDARD
01-september-2025
Metode za preskušanje in specificiranje (MTS) - Jezik za opis preskusa (TDL) - 8.
del: Besedilna skladnja
Methods for Testing and Specification (MTS) - The Test Description Language (TDL) -
Part 8: Textual Syntax
Ta slovenski standard je istoveten z: ETSI ES 203 119-8 V1.3.1 (2025-07)
ICS:
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 Test Description Language (TDL);
Part 8: Textual Syntax
2 ETSI ES 203 119-8 V1.3.1 (2025-07)
Reference
RES/MTS-203119-8v1.3.1
Keywords
language, MBT, methodology, testing, TSS&TP,
TTCN-3, UML
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 ETSI ES 203 119-8 V1.3.1 (2025-07)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Basic principles . 9
4.1 Introduction . 9
4.2 Document Structure . 9
4.3 Grammar Language . 9
4.3.1 Overview . 9
4.3.2 Operators . 10
4.3.3 Terminal rules and keywords . 10
4.3.4 Production rules . 10
4.4 Conformance . 11
5 General rules . 11
5.1 Identities and references . 11
5.2 Models and importing . 11
5.3 Linking . 12
5.4 Alternative syntaxes . 12
5.5 Terminals . 12
5.6 File format . 14
6 Production Rules . 14
6.1 Foundation . 14
6.1.1 Element . 14
6.1.2 NamedElement . 15
6.1.3 ElementImport . 15
6.1.4 Package . 16
6.1.5 PackageableElement . 16
6.1.6 Comment . 17
6.1.7 Annotation . 17
6.1.8 AnnotationType . 18
6.1.9 TestObjective . 18
6.1.10 Extension . 19
6.1.11 ConstraintType . 19
6.1.12 Constraint . 19
6.2 Data . 20
6.2.1 DataResourceMapping . 20
6.2.2 DataElementMapping . 20
6.2.3 ParameterMapping . 20
6.2.4 DataType . 21
6.2.5 SimpleDataType . 21
6.2.6 SimpleDataInstance . 21
6.2.7 StructuredDataType . 22
6.2.8 Member . 22
6.2.9 StructuredDataInstance . 23
6.2.10 MemberAssignment . 23
6.2.11 CollectionDataType . 23
ETSI
4 ETSI ES 203 119-8 V1.3.1 (2025-07)
6.2.12 CollectionDataInstance . 24
6.2.13 ProcedureSignature . 24
6.2.14 ProcedureParameter . 24
6.2.15 ParameterKind . 25
6.2.16 Parameter . 25
6.2.17 FormalParameter . 25
6.2.18 Variable . 26
6.2.19 Action . 26
6.2.20 Function . 26
6.2.21 UnassignedMemberTreatment . 27
6.2.22 PredefinedFunction . 27
6.2.23 EnumDataType . 28
6.2.24 DataUse . 28
6.2.25 ParameterBinding . 29
6.2.26 MemberReference . 29
6.2.27 StaticDataUse . 30
6.2.28 DataInstanceUse . 30
6.2.29 SpecialValueUse . 31
6.2.30 AnyValue . 31
6.2.31 AnyValueOrOmit . 31
6.2.32 OmitValue. 32
6.2.33 LiteralValueUse . 32
6.2.34 DynamicDataUse . 32
6.2.35 FunctionCall . 33
6.2.36 FormalParameterUse . 33
6.2.37 VariableUse . 33
6.2.38 PredefinedFunctionCall . 34
6.2.39 DataElementUse . 34
6.2.40 CastDataUse . 35
6.3 Time . 35
6.3.1 Time . 35
6.3.2 TimeLabel . 36
6.3.3 TimeLabelUse . 36
6.3.4 TimeLabelUseKind . 36
6.3.5 TimeConstraint . 37
6.3.6 Timer . 37
6.3.7 TimeOperation . 37
6.3.8 Wait . 37
6.3.9 Quiescence . 38
6.3.10 TimerOperation . 38
6.3.11 TimerStart . 38
6.3.12 TimerStop . 39
6.3.13 TimeOut . 39
6.4 Test Configuration . 39
6.4.1 GateType . 39
6.4.2 GateTypeKind . 40
6.4.3 GateInstance . 40
6.4.4 ComponentType . 40
6.4.5 ComponentInstance . 41
6.4.6 ComponentInstanceRole . 41
6.4.7 GateReference . 41
6.4.8 Connection . 42
6.4.9 TestConfiguration . 42
6.5 Test Behaviour . 43
6.5.1 TestDescription . 43
6.5.2 BehaviourDescription . 43
6.5.3 Behaviour . 44
6.5.4 Block . 44
6.5.5 LocalExpression . 44
6.5.6 CombinedBehaviour . 45
6.5.7 SingleCombinedBehaviour . 45
6.5.8 CompoundBehaviour . 46
ETSI
5 ETSI ES 203 119-8 V1.3.1 (2025-07)
6.5.9 BoundedLoopBehaviour . 46
6.5.10 UnboundedLoopBehaviour . 46
6.5.11 OptionalBehaviour . 47
6.5.12 MultipleCombinedBehaviour . 47
6.5.13 ConditionalBehaviour . 47
6.5.14 AlternativeBehaviour . 48
6.5.15 ParallelBehaviour . 49
6.5.16 ExceptionalBehaviour . 49
6.5.17 DefaultBehaviour . 49
6.5.18 InterruptBehaviour . 50
6.5.19 PeriodicBehaviour . 50
6.5.20 AtomicBehaviour . 51
6.5.21 Break . 52
6.5.22 Stop . 52
6.5.23 VerdictAssignment . 52
6.5.24 Assertion . 53
6.5.25 Interaction . 53
6.5.26 Message . 53
6.5.27 Target . 54
6.5.28 ValueAssignment . 54
6.5.29 ProcedureCall . 55
6.5.30 TestDescriptionReference . 55
6.5.31 ComponentInstanceBinding . 56
6.5.32 ActionBehaviour . 56
6.5.33 ActionReference . 57
6.5.34 InlineAction . 57
6.5.35 Assignment . 57
Annex A (informative): Technical Representation of the Complete Textual Syntax . 58
Annex B (informative): Examples . 59
B.0 Overview . 59
B.1 Illustration of Data Use . 59
B.2 Interface Testing . 61
B.3 Interoperability Testing . 64
History . 67
ETSI
6 ETSI ES 203 119-8 V1.3.1 (2025-07)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document is part 8 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
7 ETSI ES 203 119-8 V1.3.1 (2025-07)
1 Scope
The present document specifies the concrete textual syntax of the Test Description Language (TDL). The intended use
of the present document is to serve as the basis for the development of textual TDL tools and TDL specifications. The
meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
® ®
NOTE: OMG , UML and OCL™ are the trademarks of Object Management Group (OMG). Xtext™ is ®
trademark of the Eclipse Foundation. This information is given for the convenience of users of the
present document and does not constitute an endorsement by ETSI of the products named.
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 in the
ETSI docbox.
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 203 119-1: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 1: Abstract Syntax and Associated Semantics".
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 may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document. ®
[i.1] Eclipse Foundation: "Xtext - The Grammar Language Website".
[i.2] ETSI TS 136 523-1 (V10.2.0): "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification (3GPP TS 36.523-1 version 10.2.0 Release 10)".
[i.3] ETSI TS 186 011-2: "Core Network and Interoperability Testing (INT); IMS NNI Interoperability
Test Specifications (3GPP Release 10); Part 2: Test descriptions for IMS NNI Interoperability".
[i.4] ETSI: "TDL Open Source Project".
[i.5] ETSI ES 203 119-4: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 4: Structured Test Objective Specification (Extension)".
[i.6] ETSI ES 203 119-7: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 7: Extended Test Configurations".
ETSI
8 ETSI ES 203 119-8 V1.3.1 (2025-07)
[i.7] ETSI TS 129 165: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; Inter-IMS Network to Network Interface
(NNI) (3GPP TS 29.165)".
[i.8] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; IP multimedia call control protocol based
on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP
TS 24.229)".
[i.9] ETSI TS 136 213: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures (3GPP TS 36.213)".
[i.10] ETSI TS 136 508: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing
(3GPP TS 36.508)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 203 119-1 [1] and the following apply:
derivation: construction of an abstract syntactical structure, such as a model instance conforming to a meta-model,
from a textual representation by applying the structural rules of a grammar, and potential mappings to the underlying
meta-model
(formal) grammar: set of structural rules that define how to form valid strings from a language's alphabet that obey the
syntax of the language
non-terminal symbol: placeholder for (groups of) other symbols that describe elements in a specified language
(production) rule: definition of a structured rule for the derivation of a non-terminal symbol based on other
non-terminal symbols and terminal symbols
terminal symbol: symbols that appear explicitly in a specified language, such as a keyword, an identifier or other
tokens
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
EBNF Extended Backus-Naur Form
IMS IP Multimedia Subsystem
OCL Object Constraint Language™ ®
OMG Object Management Group
SUT System Under Test
TDL Test Description Language
TTCN-3 Testing and Test Control Notation version 3 ®
UML Unified Modelling Language
URI Uniform Record Identifier
ETSI
9 ETSI ES 203 119-8 V1.3.1 (2025-07)
4 Basic principles
4.1 Introduction
The meta-model of the Test Description Language (TDL) is specified in ETSI ES 203 119-1 [1]. The presentation
format of the meta-model can be different according to the needs of the users or the requirements of the domain, where
the TDL is applied. These presentation formats can either be text-oriented or graphic-oriented and may cover all the
functionalities of the TDL meta-model or just a part of it, which is relevant to satisfy the needs of a specific application
domain.
The present document specifies a concrete textual syntax that provides a textual representation for the commonly used
functionality of the TDL meta-model. In the current version of the present document, certain parts, such as 'Comment's
and 'Annotation's in 'DataUse' elements, are syntactically excluded. Syntactic specifications for these may be added in
future versions of the present document as needed.
The present document specifies the TDL textual file format, where the textual representations of the instances of the
TDL meta-classes may be placed. A textual representation may contain keywords, delimiters, and textual labels within a
defined structure. The rules, how these structures shall be interpreted, are described by means of Extended Backus-Naur
Form (EBNF)-like expressions. In particular, in addition to the syntactical structure, the EBNF-like expressions also
indicate how the textual labels and structures are mapped to the TDL meta-model.
4.2 Document Structure
The present document specifies the concrete textual syntax of the Test Description Language (TDL).
Clause 5 specifies general rules for the specification and use of the TDL textual file format.
Clause 6 specifies the concrete production rules defined for the TDL meta-classes (the meta-model of TDL and the
meanings of the meta-classes are described in ETSI ES 203 119-1 [1]):
• Foundation (clause 6.1)
• Data (clause 6.2)
• Time (clause 6.3)
• Test Configuration (clause 6.4)
• Test Behaviour (clause 6.5)
At the end of the present document several examples illustrating the features of the TDL Textual Syntax can be found.
4.3 Grammar Language
4.3.1 Overview
The rules that define the textual syntax of the TDL are described in present document using the grammar language of
the Xtext framework. In addition to defining the lexical structure of the TDL syntax the grammar language also
provides means for mapping those textual constructs to the TDL meta-model. Additional rules such as identity
resolution and linking are described where applicable to provide complete mapping of textual TDL to the TDL model.
The grammar of textual TDL is composed of a number of grammar rules organized in a tree. The grammar structure
follows the logical structure of the TDL meta-model and the root of the grammar is the 'Package' production rule.
Production rules are used to construct model objects and assign values to the properties of those objects. Production
rules consist of keywords (character literals) and calls to production rules, data type rules and terminal rules (which
correspond to tokens of text).
The following clauses describe the syntax of the grammar language. See Xtext documentation for further details [i.1].
ETSI
10 ETSI ES 203 119-8 V1.3.1 (2025-07)
4.3.2 Operators
Various operators are used in grammar rule definitions to specify the order and cardinality of keywords and rule calls.
Terminal rule specific operators are used to express various textual constructs. Production rule specific operators are
used to define assignments and cross-references.
Following operators are used in all rule definitions:
• '?' indicates that preceding construct shall occur 0 or 1 time;
• '*' indicates that preceding construct shall occur 0 or more times;
• '+' indicates that preceding construct shall occur 1 or more times;
• '|' is used between alternative constructs; and
• '(' and ')' are used to group constructs defined in between.
Following operators are used in terminal rule definitions:
• '!' is used to negate a construct;
• '->' is used to indicate that everything is ignored until the following construct is detected;
• '.' is used between characters to define a range; and
• '.' denotes any character.
Following operators are used in production rule definitions:
• '=' is used to define a simple assignment of a right hand construct to a property on the left;
• '+=' is used for assigning (adding to) multi-valued property;
• '?=' is used for assigning the value 'true' to a Boolean property on the condition that the right hand side
construct is present; and
• '[', '|' and ']' are used to define a cross-reference.
Various special symbols are included in the grammar definitions of production rules that are included solely as
implementation detail (to help the generation of a parser for textual TDL) and do not alter the definition of the syntax.
Such symbols include '->' and '=>'.
4.3.3 Terminal rules and keywords
Lexical tokens in the TDL grammar are either keywords of character sequences that are matched and consumed by
terminal rules during parsing. In the grammar definition, keywords are placed between apostrophes (').
Terminal rule declarations start with the keyword 'terminal' followed by the rule name (in upper-case letters by
convention). The rule name is followed by 'returns' keyword and the reference to a data type that is used for creating a
value using the consumed token.
The definition of the rule starts with a colon (':') and ends with a semi-colon (';'). Terminal rule definitions consist of
terminal rule calls (indicated by rule name), characters and operators.
EXAMPLE: Terminal INT returns EInt: ('0'.'9')+;
Some terminal rules (such as comments and whitespace) are defined as hidden in TDL grammar and corresponding text
shall be allowed anywhere in textual TDL (outside of tokens).
4.3.4 Production rules
Production rules are used to create model objects or data values. The rules that return a data type instead of a meta-class
are known as data type rules.
ETSI
11 ETSI ES 203 119-8 V1.3.1 (2025-07)
Production rule declarations start with the rule name followed by 'returns' keyword and the reference to the meta-class
that defines the object that is produced by the rule. The definition of the rule starts with a colon (':') and ends with a
semi-colon (';'). Production rule definitions consist of rule calls, keywords and operators.
EXAMPLE 1: Comment returns tdl::Comment:
'Note:' body=EString
;
An assignment is defined as a property name followed by an assignment operator (see clause 4.3.2) followed by a rule
call (name of production or data type rule) or a cross-reference. A cross-reference is defined as a meta-class reference
followed by '|' and a terminal rule call that defines the format for the identifier. The cross-reference definition is placed
between square brackets ('[' and ']').
EXAMPLE 2: Annotation returns tdl::Annotation:
'@' key=[tdl::AnnotationType|Identifier]
(':' value=EString)?
;
Production rule calls may also be used without assignment. In that case the model object that is returned from the
calling rule is the one that is created in the called rule.
Production rules may be created as fragments by prefixing the declaration with the
...
SLOVENSKI STANDARD
01-september-2025
Metode za preskušanje in specificiranje (MTS) - Jezik za opis preskusa (TDL) - 8.
del: Besedilna sintaksa
Methods for Testing and Specification (MTS) - The Test Description Language (TDL) -
Part 8: Textual Syntax
Ta slovenski standard je istoveten z: ETSI ES 203 119-8 V1.3.1 (2025-07)
ICS:
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 Test Description Language (TDL);
Part 8: Textual Syntax
2 ETSI ES 203 119-8 V1.3.1 (2025-07)
Reference
RES/MTS-203119-8v1.3.1
Keywords
language, MBT, methodology, testing, TSS&TP,
TTCN-3, UML
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 ETSI ES 203 119-8 V1.3.1 (2025-07)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Basic principles . 9
4.1 Introduction . 9
4.2 Document Structure . 9
4.3 Grammar Language . 9
4.3.1 Overview . 9
4.3.2 Operators . 10
4.3.3 Terminal rules and keywords . 10
4.3.4 Production rules . 10
4.4 Conformance . 11
5 General rules . 11
5.1 Identities and references . 11
5.2 Models and importing . 11
5.3 Linking . 12
5.4 Alternative syntaxes . 12
5.5 Terminals . 12
5.6 File format . 14
6 Production Rules . 14
6.1 Foundation . 14
6.1.1 Element . 14
6.1.2 NamedElement . 15
6.1.3 ElementImport . 15
6.1.4 Package . 16
6.1.5 PackageableElement . 16
6.1.6 Comment . 17
6.1.7 Annotation . 17
6.1.8 AnnotationType . 18
6.1.9 TestObjective . 18
6.1.10 Extension . 19
6.1.11 ConstraintType . 19
6.1.12 Constraint . 19
6.2 Data . 20
6.2.1 DataResourceMapping . 20
6.2.2 DataElementMapping . 20
6.2.3 ParameterMapping . 20
6.2.4 DataType . 21
6.2.5 SimpleDataType . 21
6.2.6 SimpleDataInstance . 21
6.2.7 StructuredDataType . 22
6.2.8 Member . 22
6.2.9 StructuredDataInstance . 23
6.2.10 MemberAssignment . 23
6.2.11 CollectionDataType . 23
ETSI
4 ETSI ES 203 119-8 V1.3.1 (2025-07)
6.2.12 CollectionDataInstance . 24
6.2.13 ProcedureSignature . 24
6.2.14 ProcedureParameter . 24
6.2.15 ParameterKind . 25
6.2.16 Parameter . 25
6.2.17 FormalParameter . 25
6.2.18 Variable . 26
6.2.19 Action . 26
6.2.20 Function . 26
6.2.21 UnassignedMemberTreatment . 27
6.2.22 PredefinedFunction . 27
6.2.23 EnumDataType . 28
6.2.24 DataUse . 28
6.2.25 ParameterBinding . 29
6.2.26 MemberReference . 29
6.2.27 StaticDataUse . 30
6.2.28 DataInstanceUse . 30
6.2.29 SpecialValueUse . 31
6.2.30 AnyValue . 31
6.2.31 AnyValueOrOmit . 31
6.2.32 OmitValue. 32
6.2.33 LiteralValueUse . 32
6.2.34 DynamicDataUse . 32
6.2.35 FunctionCall . 33
6.2.36 FormalParameterUse . 33
6.2.37 VariableUse . 33
6.2.38 PredefinedFunctionCall . 34
6.2.39 DataElementUse . 34
6.2.40 CastDataUse . 35
6.3 Time . 35
6.3.1 Time . 35
6.3.2 TimeLabel . 36
6.3.3 TimeLabelUse . 36
6.3.4 TimeLabelUseKind . 36
6.3.5 TimeConstraint . 37
6.3.6 Timer . 37
6.3.7 TimeOperation . 37
6.3.8 Wait . 37
6.3.9 Quiescence . 38
6.3.10 TimerOperation . 38
6.3.11 TimerStart . 38
6.3.12 TimerStop . 39
6.3.13 TimeOut . 39
6.4 Test Configuration . 39
6.4.1 GateType . 39
6.4.2 GateTypeKind . 40
6.4.3 GateInstance . 40
6.4.4 ComponentType . 40
6.4.5 ComponentInstance . 41
6.4.6 ComponentInstanceRole . 41
6.4.7 GateReference . 41
6.4.8 Connection . 42
6.4.9 TestConfiguration . 42
6.5 Test Behaviour . 43
6.5.1 TestDescription . 43
6.5.2 BehaviourDescription . 43
6.5.3 Behaviour . 44
6.5.4 Block . 44
6.5.5 LocalExpression . 44
6.5.6 CombinedBehaviour . 45
6.5.7 SingleCombinedBehaviour . 45
6.5.8 CompoundBehaviour . 46
ETSI
5 ETSI ES 203 119-8 V1.3.1 (2025-07)
6.5.9 BoundedLoopBehaviour . 46
6.5.10 UnboundedLoopBehaviour . 46
6.5.11 OptionalBehaviour . 47
6.5.12 MultipleCombinedBehaviour . 47
6.5.13 ConditionalBehaviour . 47
6.5.14 AlternativeBehaviour . 48
6.5.15 ParallelBehaviour . 49
6.5.16 ExceptionalBehaviour . 49
6.5.17 DefaultBehaviour . 49
6.5.18 InterruptBehaviour . 50
6.5.19 PeriodicBehaviour . 50
6.5.20 AtomicBehaviour . 51
6.5.21 Break . 52
6.5.22 Stop . 52
6.5.23 VerdictAssignment . 52
6.5.24 Assertion . 53
6.5.25 Interaction . 53
6.5.26 Message . 53
6.5.27 Target . 54
6.5.28 ValueAssignment . 54
6.5.29 ProcedureCall . 55
6.5.30 TestDescriptionReference . 55
6.5.31 ComponentInstanceBinding . 56
6.5.32 ActionBehaviour . 56
6.5.33 ActionReference . 57
6.5.34 InlineAction . 57
6.5.35 Assignment . 57
Annex A (informative): Technical Representation of the Complete Textual Syntax . 58
Annex B (informative): Examples . 59
B.0 Overview . 59
B.1 Illustration of Data Use . 59
B.2 Interface Testing . 61
B.3 Interoperability Testing . 64
History . 67
ETSI
6 ETSI ES 203 119-8 V1.3.1 (2025-07)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document is part 8 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
7 ETSI ES 203 119-8 V1.3.1 (2025-07)
1 Scope
The present document specifies the concrete textual syntax of the Test Description Language (TDL). The intended use
of the present document is to serve as the basis for the development of textual TDL tools and TDL specifications. The
meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
® ®
NOTE: OMG , UML and OCL™ are the trademarks of Object Management Group (OMG). Xtext™ is ®
trademark of the Eclipse Foundation. This information is given for the convenience of users of the
present document and does not constitute an endorsement by ETSI of the products named.
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 in the
ETSI docbox.
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 203 119-1: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 1: Abstract Syntax and Associated Semantics".
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 may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document. ®
[i.1] Eclipse Foundation: "Xtext - The Grammar Language Website".
[i.2] ETSI TS 136 523-1 (V10.2.0): "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification (3GPP TS 36.523-1 version 10.2.0 Release 10)".
[i.3] ETSI TS 186 011-2: "Core Network and Interoperability Testing (INT); IMS NNI Interoperability
Test Specifications (3GPP Release 10); Part 2: Test descriptions for IMS NNI Interoperability".
[i.4] ETSI: "TDL Open Source Project".
[i.5] ETSI ES 203 119-4: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 4: Structured Test Objective Specification (Extension)".
[i.6] ETSI ES 203 119-7: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 7: Extended Test Configurations".
ETSI
8 ETSI ES 203 119-8 V1.3.1 (2025-07)
[i.7] ETSI TS 129 165: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; Inter-IMS Network to Network Interface
(NNI) (3GPP TS 29.165)".
[i.8] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; IP multimedia call control protocol based
on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP
TS 24.229)".
[i.9] ETSI TS 136 213: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures (3GPP TS 36.213)".
[i.10] ETSI TS 136 508: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing
(3GPP TS 36.508)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 203 119-1 [1] and the following apply:
derivation: construction of an abstract syntactical structure, such as a model instance conforming to a meta-model,
from a textual representation by applying the structural rules of a grammar, and potential mappings to the underlying
meta-model
(formal) grammar: set of structural rules that define how to form valid strings from a language's alphabet that obey the
syntax of the language
non-terminal symbol: placeholder for (groups of) other symbols that describe elements in a specified language
(production) rule: definition of a structured rule for the derivation of a non-terminal symbol based on other
non-terminal symbols and terminal symbols
terminal symbol: symbols that appear explicitly in a specified language, such as a keyword, an identifier or other
tokens
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
EBNF Extended Backus-Naur Form
IMS IP Multimedia Subsystem
OCL Object Constraint Language™ ®
OMG Object Management Group
SUT System Under Test
TDL Test Description Language
TTCN-3 Testing and Test Control Notation version 3 ®
UML Unified Modelling Language
URI Uniform Record Identifier
ETSI
9 ETSI ES 203 119-8 V1.3.1 (2025-07)
4 Basic principles
4.1 Introduction
The meta-model of the Test Description Language (TDL) is specified in ETSI ES 203 119-1 [1]. The presentation
format of the meta-model can be different according to the needs of the users or the requirements of the domain, where
the TDL is applied. These presentation formats can either be text-oriented or graphic-oriented and may cover all the
functionalities of the TDL meta-model or just a part of it, which is relevant to satisfy the needs of a specific application
domain.
The present document specifies a concrete textual syntax that provides a textual representation for the commonly used
functionality of the TDL meta-model. In the current version of the present document, certain parts, such as 'Comment's
and 'Annotation's in 'DataUse' elements, are syntactically excluded. Syntactic specifications for these may be added in
future versions of the present document as needed.
The present document specifies the TDL textual file format, where the textual representations of the instances of the
TDL meta-classes may be placed. A textual representation may contain keywords, delimiters, and textual labels within a
defined structure. The rules, how these structures shall be interpreted, are described by means of Extended Backus-Naur
Form (EBNF)-like expressions. In particular, in addition to the syntactical structure, the EBNF-like expressions also
indicate how the textual labels and structures are mapped to the TDL meta-model.
4.2 Document Structure
The present document specifies the concrete textual syntax of the Test Description Language (TDL).
Clause 5 specifies general rules for the specification and use of the TDL textual file format.
Clause 6 specifies the concrete production rules defined for the TDL meta-classes (the meta-model of TDL and the
meanings of the meta-classes are described in ETSI ES 203 119-1 [1]):
• Foundation (clause 6.1)
• Data (clause 6.2)
• Time (clause 6.3)
• Test Configuration (clause 6.4)
• Test Behaviour (clause 6.5)
At the end of the present document several examples illustrating the features of the TDL Textual Syntax can be found.
4.3 Grammar Language
4.3.1 Overview
The rules that define the textual syntax of the TDL are described in present document using the grammar language of
the Xtext framework. In addition to defining the lexical structure of the TDL syntax the grammar language also
provides means for mapping those textual constructs to the TDL meta-model. Additional rules such as identity
resolution and linking are described where applicable to provide complete mapping of textual TDL to the TDL model.
The grammar of textual TDL is composed of a number of grammar rules organized in a tree. The grammar structure
follows the logical structure of the TDL meta-model and the root of the grammar is the 'Package' production rule.
Production rules are used to construct model objects and assign values to the properties of those objects. Production
rules consist of keywords (character literals) and calls to production rules, data type rules and terminal rules (which
correspond to tokens of text).
The following clauses describe the syntax of the grammar language. See Xtext documentation for further details [i.1].
ETSI
10 ETSI ES 203 119-8 V1.3.1 (2025-07)
4.3.2 Operators
Various operators are used in grammar rule definitions to specify the order and cardinality of keywords and rule calls.
Terminal rule specific operators are used to express various textual constructs. Production rule specific operators are
used to define assignments and cross-references.
Following operators are used in all rule definitions:
• '?' indicates that preceding construct shall occur 0 or 1 time;
• '*' indicates that preceding construct shall occur 0 or more times;
• '+' indicates that preceding construct shall occur 1 or more times;
• '|' is used between alternative constructs; and
• '(' and ')' are used to group constructs defined in between.
Following operators are used in terminal rule definitions:
• '!' is used to negate a construct;
• '->' is used to indicate that everything is ignored until the following construct is detected;
• '.' is used between characters to define a range; and
• '.' denotes any character.
Following operators are used in production rule definitions:
• '=' is used to define a simple assignment of a right hand construct to a property on the left;
• '+=' is used for assigning (adding to) multi-valued property;
• '?=' is used for assigning the value 'true' to a Boolean property on the condition that the right hand side
construct is present; and
• '[', '|' and ']' are used to define a cross-reference.
Various special symbols are included in the grammar definitions of production rules that are included solely as
implementation detail (to help the generation of a parser for textual TDL) and do not alter the definition of the syntax.
Such symbols include '->' and '=>'.
4.3.3 Terminal rules and keywords
Lexical tokens in the TDL grammar are either keywords of character sequences that are matched and consumed by
terminal rules during parsing. In the grammar definition, keywords are placed between apostrophes (').
Terminal rule declarations start with the keyword 'terminal' followed by the rule name (in upper-case letters by
convention). The rule name is followed by 'returns' keyword and the reference to a data type that is used for creating a
value using the consumed token.
The definition of the rule starts with a colon (':') and ends with a semi-colon (';'). Terminal rule definitions consist of
terminal rule calls (indicated by rule name), characters and operators.
EXAMPLE: Terminal INT returns EInt: ('0'.'9')+;
Some terminal rules (such as comments and whitespace) are defined as hidden in TDL grammar and corresponding text
shall be allowed anywhere in textual TDL (outside of tokens).
4.3.4 Production rules
Production rules are used to create model objects or data values. The rules that return a data type instead of a meta-class
are known as data type rules.
ETSI
11 ETSI ES 203 119-8 V1.3.1 (2025-07)
Production rule declarations start with the rule name followed by 'returns' keyword and the reference to the meta-class
that defines the object that is produced by the rule. The definition of the rule starts with a colon (':') and ends with a
semi-colon (';'). Production rule definitions consist of rule calls, keywords and operators.
EXAMPLE 1: Comment returns tdl::Comment:
'Note:' body=EString
;
An assignment is defined as a property name followed by an assignment operator (see clause 4.3.2) followed by a rule
call (name of production or data type rule) or a cross-reference. A cross-reference is defined as a meta-class reference
followed by '|' and a terminal rule call that defines the format for the identifier. The cross-reference definition is placed
between square brackets ('[' and ']').
EXAMPLE 2: Annotation returns tdl::Annotation:
'@' key=[tdl::AnnotationType|Identifier]
(':' value=EString)?
;
Production rule calls may also be used without assignment. In that case the model object that is returned from the
calling rule is the one that is created in the called rule.
Production rules may be created as fragments by prefixing the declaration with the
...
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...