SIST ES 203 119-9 V1.1.1:2025

• Abstract:

  The present document specifies the architecture for the execution environment of TDL test descriptions and functional requirements for the components in the form of function declarations that will be provided by an implementation of the components and data types used as input and output parameters of the functions. The test executor component will interpret the elements of test descriptions according to operational semantics specified in [1]. The present document will be used for developing a code generator or interpreter for mapping abstract TDL constructs to code and the required test environment components that are specific to a chosen test execution platform.

• Status: Published
• Publication Date: 20-Aug-2025
• ICS: 35.060 - Languages used in information technology
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 18-Jul-2025
• Due Date: 22-Sep-2025
• Completion Date: 21-Aug-2025
• Ref Project: ETSI ES 203 119-9 V1.1.1 (2025-07) - Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 9: Test Runtime Interfaces

Overview

SIST ES 203 119-9 V1.1.1:2025 - "Methods for Testing and Specification (MTS) - The Test Description Language (TDL) - Part 9: Test Runtime Interfaces" specifies the architecture and functional requirements for the execution environment that runs TDL-based test descriptions. This standard, developed by SIST and aligned with ETSI ES 203 119-9, defines the Test Runtime Interfaces (TRI) that enable mapping abstract TDL constructs to actionable code in specific testing environments.

The document targets organizations and developers creating code generators or interpreters for the TDL language, ensuring that test descriptions remain executable across various platforms through clearly defined runtime components and interfaces.

Key Topics

• Test Execution Architecture: The standard outlines a modular architecture for TDL test execution environments, centering on the test executor, which interprets test descriptions in line with formal operational semantics.
• Test Runtime Interfaces (TRI): It defines the essential interfaces required for a compliant execution environment:
  • System Adapter: Manages all interactions between the test executor and the System Under Test (SUT).
  • Validator: Provides data matching and validation capabilities.
  • Test Reporter: Handles test logging and reporting.
  • Predefined Functions: Exposes TDL-specific functions required for execution.
• Mapping Abstractions to Implementations: Specifies methods for mapping TDL meta-classes (e.g., DataType, DataInstance) to objects and functions within a target platform, ensuring seamless integration.
• Component Requirements: Function declarations and expected input/output data types for each interface are provided, enabling predictable interaction between components and platform-specific implementations.
• Data Handling and Immutability: Emphasizes data isolation by mandating that all data modifications occur prior to passing parameters, adhering to TDL’s immutability principles.

Applications

• Testing Tool Development: Tool vendors and engineers can implement TDL code generators, test interpreters, or test execution harnesses that conform to this runtime interface standard, guaranteeing interoperability and consistency across test environments.
• Test Automation: Facilitates automation of conformance and interoperability tests in sectors where TDL is adopted, such as telecommunications and IT.
• Integration with Test Management Systems: The standardized interfaces enhance integration into broader test management frameworks, supporting comprehensive test logging, verdict sharing, and test orchestration.
• Platform Independence: By defining the TRI, tests authored in TDL can be reliably executed on various platforms supporting compatible adapters without rewriting test logic for each new system.

Related Standards

• ETSI ES 203 119-1: "Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 1: Abstract Syntax and Associated Semantics" - foundational document for TDL syntax and semantics.
• Other Parts of SIST/ETSI ES 203 119 Series: Covering aspects such as modeling, data mapping, and test configuration for comprehensive TDL application.
• ICS 35.060: Standards for languages used in information technology, which underpin the broader context of TDL runtime use.

---

This standard is essential for any stakeholder developing TDL-compatible test frameworks, integration solutions, or automated testing platforms. Its robust, modular approach to test execution architecture promotes efficient, portable, and maintainable implementation of TDL across the evolving landscape of interoperable systems. For current and future test automation initiatives, adherence to SIST ES 203 119-9 V1.1.1 provides a clear pathway toward standardized, reliable test execution.

Final draft ETSI ES 203 119-9 V1.1.1 (2025-05)

ETSI STANDARD
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Part 9: Test Runtime Interfaces

2 Final draft ETSI ES 203 119-9 V1.1.1 (2025-05)

Reference
DES/MTS-203119-9v1.1.1
Keywords
interface, runtime, TDL, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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-9 V1.1.1 (2025-05)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols, abbreviations and conventions . 6
3.1 Terms . 6
3.2 Symbols . 7
3.3 Abbreviations . 7
3.4 Conventions . 7
4 Test Execution Environment . 7
4.1 Architecture . 7
4.2 Mappings . 8
4.3 Data Values . 8
5 Test Runtime Interfaces. 9
5.1 Notational Conventions . 9
5.2 Basic Principles . 9
5.3 Overview . 10
5.4 Types . 10
5.4.1 Element . 10
5.4.2 ElementAnnotation . 10
5.4.3 NamedElement . 11
5.4.4 Data . 11
5.4.5 Argument . 11
5.4.6 Procedure . 12
5.4.7 Parameter . 12
5.4.8 Type . 12
5.4.9 Value . 13
5.4.10 SpecialValue . 14
5.4.11 Mapping . 14
5.4.12 GateReference . 14
5.4.13 GateTypeKind . 15
5.4.14 ComponentInstanceRole . 15
5.4.15 Connection . 15
5.4.16 Verdict . 16
5.4.17 StopException . 16
5.4.18 ValidationFailedException . 16
5.5 System Adapter . 17
5.5.1 Overview . 17
5.5.2 Configure connections . 17
5.5.3 Send message . 17
5.5.4 Receive message . 17
5.5.5 Call procedure . 18
5.5.6 Receive procedure call . 18
5.5.7 Reply to procedure call . 18
5.6 Validator . 19
5.6.1 Overview . 19
5.6.2 Match data . 19
5.6.3 Set verdict . 19
5.6.4 Get verdict . 19
ETSI
4 Final draft ETSI ES 203 119-9 V1.1.1 (2025-05)
5.7 Test Reporter . 19
5.7.1 Overview . 19
5.7.2 Comment . 20
5.7.3 Test objective reached . 20
5.7.4 Behaviour started . 20
5.7.5 Behaviour completed . 20
5.7.6 Runtime error . 20
5.8 Predefined Functions . 21
Annex A (informative): Technical Representation of the Runtime Interfaces . 22
History . 23

ETSI
5 Final draft ETSI ES 203 119-9 V1.1.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 9 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.
Introduction
The TDL language has been designed from the start with executability in mind. However, some of the constructs of
TDL are abstract and adaptation to concrete implementation is required.
The present document provides a specification for an architecture of a test execution environment for TDL test
descriptions and interfaces between the components. It provides a mapping of abstract TDL constructs to concrete
implementation artifacts that are a prerequisite to produce executable TDL test descriptions. The described approach
follows the commonly used 'separation of concerns' principle.

ETSI
6 Final draft ETSI ES 203 119-9 V1.1.1 (2025-05)
1 Scope
The present document specifies the architecture for the execution environment of TDL test descriptions and functional
requirements for the components in the form of function declarations that will be provided by an implementation of the
components and data types used as input and output parameters of the functions. The test executor component will
interpret the elements of test descriptions according to operational semantics specified in [1].
The present document will be used for developing a code generator or interpreter for mapping abstract TDL constructs
to code and the required test environment components that are specific to a chosen test execution platform.
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] ETSI: "TDL Open Source Project".
3 Definition of terms, symbols, abbreviations and
conventions
3.1 Terms
For the purposes of the present document, the terms given in [1] and the following apply:
system adapter: entity that adapts the test executor communication operations with the SUT
test executor: application that carries out test behaviour
ETSI
7 Final draft ETSI ES 203 119-9 V1.1.1 (2025-05)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in [1] and the following apply:
SUT System Under Test
TRI Test Runtime Interfaces
3.4 Conventions
For the purposes of the present document, the following conventions apply:
Meta-classes and predefined instances from the TDL meta-model [1] are typed in italic, e.g. DataType.
4 Test Execution Environment
4.1 Architecture
The execution environment for TDL test descriptions shall have modular architecture as shown on Figure 4.1.
System adapter Test executor Test reporter
Predefined
Validator
functions
Figure 4.1: Architecture
The central component of the environment shall be the test executor. The test executor shall execute the behaviour of
the elements in a test description according to the operational semantics specified in [1].
The test executor shall only execute the behaviours that occur on component instances of type 'Tester'. The execution of
the behaviour of each component shall be independent of other components. This implies that the implementations of
the runtime components shall be thread-safe in case the execution language supports multi-threading.
Additional requirements for the test executor are defined in clauses 4.2 and 4.3.
The specifics of the realization of the test executor and the mechanism for resolving the implementations of runtime
interface components are outside the scope of the present document.
NOTE: It is a good practice to use a dependency injection mechanism for providing specific implementation for
required interfaces.
The interfaces that should be realized and made available to the test executor are collectively called Test Runtime
Interfaces (TRI). The following interfaces shall be implemented:
• 'System adapter' manages interactions between the test executor and the SUT;
• 'Validator' provides data matching functionality;
ETSI
8 Final draft ETSI ES 203 119-9 V1.1.1 (2025-05)
• 'Test reporter' implements test logging; and
• 'Predefined functions' provides implementation of TDL predefined functions.
Interface function declarations and implementation requirements are specified in clause 5.
4.2 Mappings
TDL model elements of the meta-classes DataType and DataInstance (and their sub-classes) may be mapped to specific
objects or type definitions in the execution platform via DataElementMapping elements. The realization of the TDL test
executor shall support two mechanisms for resolving the mappings.
In the first instance, the mappings shall refer to specific objects or type definitions in the execution platform
programming language. The test executor shall resolve those mappings using language specific means and pass
references to those objects to the runtime interface components.
In the second case, the mapping information shall be encapsulated in instances of 'Mapping' and the associated
DataType or DataInstance shall be encapsulated in instances of 'Type' or 'Value' respectively.
<>
Data
getValue()
getType()
<> <>
Value Type
getMapping() getMapping()
<>
Mapping
Figure 4.2: Encapsulated Data and Type
The choice of the mechanism shall be made by the concrete realization of the test executor based on the MappingName
annotation applied to the mappings.
TDL model elements of the meta-classes Action, Function and PredefinedFunction shall be mapped to functions
implemented in the execution language. The MappingName annotation shall be used to identify the appropriate
mapping for the language.
4.3 Data Values
The test executor shall perform all data modifications (as specified by MemberAssignment and ParameterBinding
elements) before passing the values to other components. Before parameter bindings are applied, the value instances
shall be copied using language-specific means to adhere to the immutability principle of TDL data.
ETSI
9 Final draft ETSI ES 203 119-9 V1.1.1 (2025-05)
5 Test Runtime Interfaces
5.1 Notational Conventions
References to t
...

ETSI STANDARD
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Part 9: Test Runtime Interfaces

2 ETSI ES 203 119-9 V1.1.1 (2025-07)

Reference
DES/MTS-203119-9v1.1.1
Keywords
interface, runtime, TDL, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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-9 V1.1.1 (2025-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols, abbreviations and conventions . 6
3.1 Terms . 6
3.2 Symbols . 7
3.3 Abbreviations . 7
3.4 Conventions . 7
4 Test Execution Environment . 7
4.1 Architecture . 7
4.2 Mappings . 8
4.3 Data Values . 8
5 Test Runtime Interfaces. 9
5.1 Notational Conventions . 9
5.2 Basic Principles . 9
5.3 Overview . 10
5.4 Types . 10
5.4.1 Element . 10
5.4.2 ElementAnnotation . 10
5.4.3 NamedElement . 11
5.4.4 Data . 11
5.4.5 Argument . 11
5.4.6 Procedure . 12
5.4.7 Parameter . 12
5.4.8 Type . 12
5.4.9 Value . 13
5.4.10 SpecialValue . 14
5.4.11 Mapping . 14
5.4.12 GateReference . 14
5.4.13 GateTypeKind . 15
5.4.14 ComponentInstanceRole . 15
5.4.15 Connection . 15
5.4.16 Verdict . 16
5.4.17 StopException . 16
5.4.18 ValidationFailedException . 16
5.5 System Adapter . 17
5.5.1 Overview . 17
5.5.2 Configure connections . 17
5.5.3 Send message . 17
5.5.4 Receive message . 17
5.5.5 Call procedure . 18
5.5.6 Receive procedure call . 18
5.5.7 Reply to procedure call . 18
5.6 Validator . 19
5.6.1 Overview . 19
5.6.2 Match data . 19
5.6.3 Set verdict . 19
5.6.4 Get verdict . 19
ETSI
4 ETSI ES 203 119-9 V1.1.1 (2025-07)
5.7 Test Reporter . 19
5.7.1 Overview . 19
5.7.2 Comment . 20
5.7.3 Test objective reached . 20
5.7.4 Behaviour started . 20
5.7.5 Behaviour completed . 20
5.7.6 Runtime error . 20
5.8 Predefined Functions . 21
Annex A (informative): Technical Representation of the Runtime Interfaces . 22
History . 23

ETSI
5 ETSI ES 203 119-9 V1.1.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 9 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.
Introduction
The TDL language has been designed from the start with executability in mind. However, some of the constructs of
TDL are abstract and adaptation to concrete implementation is required.
The present document provides a specification for an architecture of a test execution environment for TDL test
descriptions and interfaces between the components. It provides a mapping of abstract TDL constructs to concrete
implementation artifacts that are a prerequisite to produce executable TDL test descriptions. The described approach
follows the commonly used 'separation of concerns' principle.

ETSI
6 ETSI ES 203 119-9 V1.1.1 (2025-07)
1 Scope
The present document specifies the architecture for the execution environment of TDL test descriptions and functional
requirements for the components in the form of function declarations that will be provided by an implementation of the
components and data types used as input and output parameters of the functions. The test executor component will
interpret the elements of test descriptions according to operational semantics specified in [1].
The present document will be used for developing a code generator or interpreter for mapping abstract TDL constructs
to code and the required test environment components that are specific to a chosen test execution platform.
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] ETSI: "TDL Open Source Project".
3 Definition of terms, symbols, abbreviations and
conventions
3.1 Terms
For the purposes of the present document, the terms given in [1] and the following apply:
system adapter: entity that adapts the test executor communication operations with the SUT
test executor: application that carries out test behaviour
ETSI
7 ETSI ES 203 119-9 V1.1.1 (2025-07)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in [1] and the following apply:
SUT System Under Test
TRI Test Runtime Interfaces
3.4 Conventions
For the purposes of the present document, the following conventions apply:
Meta-classes and predefined instances from the TDL meta-model [1] are typed in italic, e.g. DataType.
4 Test Execution Environment
4.1 Architecture
The execution environment for TDL test descriptions shall have modular architecture as shown on Figure 4.1.
System adapter Test executor Test reporter
Predefined
Validator
functions
Figure 4.1: Architecture
The central component of the environment shall be the test executor. The test executor shall execute the behaviour of
the elements in a test description according to the operational semantics specified in [1].
The test executor shall only execute the behaviours that occur on component instances of type 'Tester'. The execution of
the behaviour of each component shall be independent of other components. This implies that the implementations of
the runtime components shall be thread-safe in case the execution language supports multi-threading.
Additional requirements for the test executor are defined in clauses 4.2 and 4.3.
The specifics of the realization of the test executor and the mechanism for resolving the implementations of runtime
interface components are outside the scope of the present document.
NOTE: It is a good practice to use a dependency injection mechanism for providing specific implementation for
required interfaces.
The interfaces that should be realized and made available to the test executor are collectively called Test Runtime
Interfaces (TRI). The following interfaces shall be implemented:
• 'System adapter' manages interactions between the test executor and the SUT;
• 'Validator' provides data matching functionality;
ETSI
8 ETSI ES 203 119-9 V1.1.1 (2025-07)
• 'Test reporter' implements test logging; and
• 'Predefined functions' provides implementation of TDL predefined functions.
Interface function declarations and implementation requirements are specified in clause 5.
4.2 Mappings
TDL model elements of the meta-classes DataType and DataInstance (and their sub-classes) may be mapped to specific
objects or type definitions in the execution platform via DataElementMapping elements. The realization of the TDL test
executor shall support two mechanisms for resolving the mappings.
In the first instance, the mappings shall refer to specific objects or type definitions in the execution platform
programming language. The test executor shall resolve those mappings using language specific means and pass
references to those objects to the runtime interface components.
In the second case, the mapping information shall be encapsulated in instances of 'Mapping' and the associated
DataType or DataInstance shall be encapsulated in instances of 'Type' or 'Value' respectively.
<>
Data
getValue()
getType()
<> <>
Value Type
getMapping() getMapping()
<>
Mapping
Figure 4.2: Encapsulated Data and Type
The choice of the mechanism shall be made by the concrete realization of the test executor based on the MappingName
annotation applied to the mappings.
TDL model elements of the meta-classes Action, Function and PredefinedFunction shall be mapped to functions
implemented in the execution language. The MappingName annotation shall be used to identify the appropriate
mapping for the language.
4.3 Data Values
The test executor shall perform all data modifications (as specified by MemberAssignment and ParameterBinding
elements) before passing the values to other components. Before parameter bindings are applied, the value instances
shall be copied using language-specific means to adhere to the immutability principle of TDL data.
ETSI
9 ETSI ES 203 119-9 V1.1.1 (2025-07)
5 Test Runtime Interfaces
5.1 Notational Conventions
References to types and interfaces de
...

SLOVENSKI STANDARD
01-september-2025
Metode za preskušanje in specificiranje (MTS) - Jezik za opis preskusa (TDL) - 9.
del: Preskusni vmesniki za izvajanje
Methods for Testing and Specification (MTS) - The Test Description Language (TDL) -
Part 9: Test Runtime Interfaces
Ta slovenski standard je istoveten z: ETSI ES 203 119-9 V1.1.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 9: Test Runtime Interfaces

2 ETSI ES 203 119-9 V1.1.1 (2025-07)

Reference
DES/MTS-203119-9v1.1.1
Keywords
interface, runtime, TDL, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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-9 V1.1.1 (2025-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols, abbreviations and conventions . 6
3.1 Terms . 6
3.2 Symbols . 7
3.3 Abbreviations . 7
3.4 Conventions . 7
4 Test Execution Environment . 7
4.1 Architecture . 7
4.2 Mappings . 8
4.3 Data Values . 8
5 Test Runtime Interfaces. 9
5.1 Notational Conventions . 9
5.2 Basic Principles . 9
5.3 Overview . 10
5.4 Types . 10
5.4.1 Element . 10
5.4.2 ElementAnnotation . 10
5.4.3 NamedElement . 11
5.4.4 Data . 11
5.4.5 Argument . 11
5.4.6 Procedure . 12
5.4.7 Parameter . 12
5.4.8 Type . 12
5.4.9 Value . 13
5.4.10 SpecialValue . 14
5.4.11 Mapping . 14
5.4.12 GateReference . 14
5.4.13 GateTypeKind . 15
5.4.14 ComponentInstanceRole . 15
5.4.15 Connection . 15
5.4.16 Verdict . 16
5.4.17 StopException . 16
5.4.18 ValidationFailedException . 16
5.5 System Adapter . 17
5.5.1 Overview . 17
5.5.2 Configure connections . 17
5.5.3 Send message . 17
5.5.4 Receive message . 17
5.5.5 Call procedure . 18
5.5.6 Receive procedure call . 18
5.5.7 Reply to procedure call . 18
5.6 Validator . 19
5.6.1 Overview . 19
5.6.2 Match data . 19
5.6.3 Set verdict . 19
5.6.4 Get verdict . 19
ETSI
4 ETSI ES 203 119-9 V1.1.1 (2025-07)
5.7 Test Reporter . 19
5.7.1 Overview . 19
5.7.2 Comment . 20
5.7.3 Test objective reached . 20
5.7.4 Behaviour started . 20
5.7.5 Behaviour completed . 20
5.7.6 Runtime error . 20
5.8 Predefined Functions . 21
Annex A (informative): Technical Representation of the Runtime Interfaces . 22
History . 23

ETSI
5 ETSI ES 203 119-9 V1.1.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 9 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.
Introduction
The TDL language has been designed from the start with executability in mind. However, some of the constructs of
TDL are abstract and adaptation to concrete implementation is required.
The present document provides a specification for an architecture of a test execution environment for TDL test
descriptions and interfaces between the components. It provides a mapping of abstract TDL constructs to concrete
implementation artifacts that are a prerequisite to produce executable TDL test descriptions. The described approach
follows the commonly used 'separation of concerns' principle.

ETSI
6 ETSI ES 203 119-9 V1.1.1 (2025-07)
1 Scope
The present document specifies the architecture for the execution environment of TDL test descriptions and functional
requirements for the components in the form of function declarations that will be provided by an implementation of the
components and data types used as input and output parameters of the functions. The test executor component will
interpret the elements of test descriptions according to operational semantics specified in [1].
The present document will be used for developing a code generator or interpreter for mapping abstract TDL constructs
to code and the required test environment components that are specific to a chosen test execution platform.
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] ETSI: "TDL Open Source Project".
3 Definition of terms, symbols, abbreviations and
conventions
3.1 Terms
For the purposes of the present document, the terms given in [1] and the following apply:
system adapter: entity that adapts the test executor communication operations with the SUT
test executor: application that carries out test behaviour
ETSI
7 ETSI ES 203 119-9 V1.1.1 (2025-07)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in [1] and the following apply:
SUT System Under Test
TRI Test Runtime Interfaces
3.4 Conventions
For the purposes of the present document, the following conventions apply:
Meta-classes and predefined instances from the TDL meta-model [1] are typed in italic, e.g. DataType.
4 Test Execution Environment
4.1 Architecture
The execution environment for TDL test descriptions shall have modular architecture as shown on Figure 4.1.
System adapter Test executor Test reporter
Predefined
Validator
functions
Figure 4.1: Architecture
The central component of the environment shall be the test executor. The test executor shall execute the behaviour of
the elements in a test description according to the operational semantics specified in [1].
The test executor shall only execute the behaviours that occur on component instances of type 'Tester'. The execution of
the behaviour of each component shall be independent of other components. This implies that the implementations of
the runtime components shall be thread-safe in case the execution language supports multi-threading.
Additional requirements for the test executor are defined in clauses 4.2 and 4.3.
The specifics of the realization of the test executor and the mechanism for resolving the implementations of runtime
interface components are outside the scope of the present document.
NOTE: It is a good practice to use a dependency injection mechanism for providing specific implementation for
required interfaces.
The interfaces that should be realized and made available to the test executor are collectively called Test Runtime
Interfaces (TRI). The following interfaces shall be implemented:
• 'System adapter' manages interactions between the test executor and the SUT;
• 'Validator' provides data matching functionality;
ETSI
8 ETSI ES 203 119-9 V1.1.1 (2025-07)
• 'Test reporter' implements test logging; and
• 'Predefined functions' provides implementation of TDL predefined functions.
Interface function declarations and implementation requirements are specified in clause 5.
4.2 Mappings
TDL model elements of the meta-classes DataType and DataInstance (and their sub-classes) may be mapped to specific
objects or type definitions in the execution platform via DataElementMapping elements. The realization of the TDL test
executor shall support two mechanisms for resolving the mappings.
In the first instance, the mappings shall refer to specific objects or type definitions in the execution platform
programming language. The test executor shall resolve those mappings using language specific means and pass
references to those objects to the runtime interface components.
In the second case, the mapping information shall be encapsulated in instances of 'Mapping' and the associated
DataType or DataInstance shall be encapsulated in instances of 'Type' or 'Value' respectively.
<>
Data
getValue()
getType()
<> <>
Value Type
getMapping() getMapping()
<>
Mapping
Figure 4.2: Encapsulated Data and Type
The choice of the mechanism shall be made by the concrete realization of the test executor based on the MappingName
annotation applied to the mappings.
TDL model elements of the meta-classes Action, Function and PredefinedFunction shall be mapped to functions
implemented in the execution language. The MappingName annotation shall be used to identify the appropriate
mapping for the language.
4.3 Data Values
The test executor shall perform all data modifications (as specified by MemberAssignment and ParameterBinding
elements) before passing the values to other components. Before parameter bindings are applied, the value instances
shall be copie
...