|
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
TTCN-3 Language Extensions:
Configuration and Deployment Support
---------------------- Page: 1 ----------------------
2 ETSI ES 202 781 V1.7.1 (2019-04)
Reference
RES/MTS-202781ConfDeplv171
Keywords
protocol, testing, TTCN-3
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
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 2019.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI ES 202 781 V1.7.1 (2019-04)
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 Package conformance and compatibility . 8
5 Package Concepts for the Core Language . 9
5.0 General . 9
5.1 Static configurations . 10
5.1.1 The special configuration type: configuration . 10
5.1.2 The configuration function . 11
5.1.3 Starting a static test configuration . 12
5.1.4 Destruction of static test configurations . 12
5.1.5 Creation of static test components . 13
5.1.6 Establishment of static connections and static mappings. 14
5.1.7 Test case definitions for static test configuratio n . 14
5.1.8 Executing test cases on static test configurations . 15
5.1.9 Further restrictions . 17
5.1.10 Logging the status of static configurations . 17
5.2 Ports with translation capability . 17
5.2.0 General . 17
5.2.1 Translation capability in port type declaration. 19
5.2.2 Mapping and connecting ports . 20
5.2.3 Translation functions . 20
5.2.4 Translation state . 21
5.2.5 Sending . 23
5.2.6 Receiving . 23
5.2.7 Address . 25
5.2.8 Clear, start, stop and halt operation . 25
5.2.9 The outer port reference . 26
6 Package Semantics . 27
6.0 General . 27
6.1 Replacement of short forms. 29
6.2 Order of replacement steps . 29
6.3 Flow graph representation of TTCN-3 behaviour . 30
6.4 Flow graph construction procedure . 30
6.5 Flow graph representation of configuration functions . 31
6.6 Retrieval of start nodes of flow graphs . 32
6.7 Module state . 32
6.8 Accessing the module state . 33
6.9 Configuration state . 33
6.10 Accessing the configuration state . 33
6.11 Entity states . 34
6.12 Accessing entity states . 36
6.13 Handling of connections among ports . 37
6.14 Handling of port states . 37
6.15 Void . 39
ETSI
---------------------- Page: 3 ----------------------
4 ETSI ES 202 781 V1.7.1 (2019-04)
6.16 Evaluation phases, general . 39
6.17 Phase I: Initialization . 39
6.18 Phase II: Update . 40
6.19 Phase III: Selection . 40
6.20 Phase IV: Execution . 41
6.21 Global functions . 41
6.22 Clear port operation . 41
6.23 Configuration function call. 42
6.24 Connect operation. 43
6.25 Create operation . 44
6.26 Flow graph segment . 46
6.27 Flow graph segment . 47
6.28 Flow graph segment . 48
6.29 Flow graph segment . 48
6.30 Execute statement . 49
6.31 Flow graph segment . 50
6.32 Flow graph segment . 50
6.33 Flow graph segment . 50
6.34 Flow graph segment . 51
6.35 Flow graph segment . 53
6.36 Halt port operation. 54
6.37 Kill component operation . 55
6.38 Flow graph segment . 57
6.39 Flow graph segment . 57
6.40 Kill execution statement . 59
6.41 Kill configuration operation . 60
6.42 Map operation . 60
6.43 Start port operation . 61
6.44 Stop component operation . 62
6.45 Flow graph segment . 64
6.46 Flow graph segment . 65
6.47 Flow graph segment . 66
6.48 Stop port operation . 67
6.49 Flow graph segment . 68
6.50 Flow graph segment . 69
6.51 Flow graph segment . 70
7 TRI Extensions for the Package . 70
7.1 Changes and extensions to clause 5.5.2 of ETSI ES 201 873-5 [3] Connection handling operations . 70
TM
7.2 Extensions to clause 6 of ETSI ES 201 873-5 [3] Java language mapping . 72
7.3 Extensions to clause 7 of ETSI ES 201 873-5 [3] ANSI C language mapping . 72
7.4 Extensions to clause 8 of ETSI ES 201 873-5 [3] C++ language mapping . 72
7.5 Extensions to clause 9 of ETSI ES 201 873-5 [3] C# language mapping . 73
8 TCI Extensions for the Package . 73
8.1 Extensions to clause 7.2.1.1 of ETSI ES 201 873-6 [4] Management . 73
8.2 Extensions to clause 7.3.1.1 of ETSI ES 201 873-6 [4] TCI-TM required . 73
8.3 Extensions to clause 7.3.1.2 of ETSI ES 201 873-6 [4] TCI-TM provided. 75
8.4 Extensions to clause 7.3.3.1 of ETSI ES 201 873-6 [4] TCI-CH required . 75
8.5 Extensions to clause 7.3.3.2 of ETSI ES 201 873-6 [4] TCI CH provided . 76
8.6 Extensions to clause 7.3.4 of ETSI ES 201 873-6 [4] TCI-TL provided . 77
TM
8.7 Extensions to clause 8 of ETSI ES 201 873-6 [4] Java language mapping . 79
8.8 Extensions to clause 9 of ETSI ES 201 873-6 [4] ANSI C language mapping . 81
8.9 Extensions to clause 10 of ETSI ES 201 873-6 [4] C++ language mapping . 83
8.10 Extensions to clause 11 of ETSI ES 201 873-6 [4] W3C XML mapping . 85
8.11 Extensions to clause 12 of ETSI ES 201 873-6 [4] C# language mapping . 88
Annex A (normative): BNF and static semantics . 90
A.1 Additional TTCN-3 terminals . 90
A.2 Modified TTCN-3 syntax BNF productions . 90
A.3 Additional TTCN-3 syntax BNF productions . 91
ETSI
---------------------- Page: 4 ----------------------
5 ETSI ES 202 781 V1.7.1 (2019-04)
Annex B (informative): Library of useful types . 93
B.1 Limitations . 93
B.2 Useful TTCN-3 types . 93
B.2.1 Status values for port states . 93
History . 94
ETSI
---------------------- Page: 5 ----------------------
6 ETSI ES 202 781 V1.7.1 (2019-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, 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.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The use of underline (additional text) and strike through (deleted text) highlights the differences between base
document and extended documents.
The present document relates to the multi-part series ETSI ES 201 873 covering the Testing and Test Control Notation
version 3, as identified below:
Part 1: "TTCN-3 Core Language";
Part 4: "TTCN-3 Operational Semantics";
Part 5: "TTCN-3 Runtime Interface (TRI)";
Part 6: "TTCN-3 Control Interface (TCI)";
Part 7: "Using ASN.1 with TTCN-3";
Part 8: "The IDL to TTCN-3 Mapping";
Part 9: "Using XML schema with TTCN-3";
Part 10: "TTCN-3 Documentation Comment Specification";
Part 11: "Using JSON with TTCN-3".
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
---------------------- Page: 6 ----------------------
7 ETSI ES 202 781 V1.7.1 (2019-04)
1 Scope
The present document defines the Configuration and Deployment Support package of TTCN-3. TTCN-3 can be used
for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of
application are protocol testing (including mobile and Internet protocols), service testing (including supplementary
services), module testing, testing of APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for
many other kinds of testing including interoperability, robustness, regression, system and integration testing. The
specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines the TTCN-3 support for static test configurations.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[2] ETSI ES 201 873-4: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 4: TTCN-3 Operational Semantics".
[3] ETSI ES 201 873-5: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)".
[4] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 6: TTCN-3 Control Interface (TCI)".
[5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -Conformance testing
methodology and framework; Part 1: General concepts".
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.
ETSI
---------------------- Page: 7 ----------------------
8 ETSI ES 202 781 V1.7.1 (2019-04)
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI ES 201 873-7: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 7: Using ASN.1 with TTCN-3".
[i.2] ETSI ES 201 873-8: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 8: The IDL to TTCN-3 Mapping".
[i.3] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 9: Using XML schema with TTCN-3".
[i.4] ETSI ES 201 873-10: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 10: TTCN-3 Documentation Comment Specification".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 201 873-1 [1], ETSI ES 201 873-4 [2], ETSI
ES 201 873-5 [3], ETSI ES 201 873-6 [4] and ISO/IEC 9646-1 [5] apply.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI ES 201 873-1 [1], ETSI ES 201 873-4 [2],
ETSI ES 201 873-5 [3], ETSI ES 201 873-6 [4], ISO/IEC 9646-1 [5] and the following apply:
MTC Main Test Component
PTC Parallel Test Component
4 Package conformance and compatibility
The package presented in the present document is identified by the package tag:
"TTCN-3:2009 Static Test Configurations" - to be used with modules complying with the present
document.
For an implementation claiming to conform to this package version, all features specified in the present document shall
be implemented consistently with the requirements given in the present document, in ETSI ES 201 873-1 [1] and in
ETSI ES 201 873-4 [2].
The package presented in the present document is compatible to:
• ETSI ES 201 873-1 [1] version 4.9.1;
• ETSI ES 201 873-4 [2] version 4.6.1;
• ETSI ES 201 873-5 [3] version 4.8.1;
• ETSI ES 201 873-6 [4] version 4.9.1;
• ETSI ES 201 873-7 [i.1];
• ETSI ES 201 873-8 [i.2];
ETSI
---------------------- Page: 8 ----------------------
9 ETSI ES 202 781 V1.7.1 (2019-04)
• ETSI ES 201 873-9 [i.3];
• ETSI ES 201 873-10 [i.4].
If later versions of those parts are available and should be used instead, the compatibility to the package presented in the
present document has to be checked individually.
5 Package Concepts for the Core Language
5.0 General
This package defines the TTCN-3 means to define static test configurations. A static test configuration is a test
configuration with a lifetime that is not bound to a single test case. The test components of a static test configuration
may be used by several test cases. This package realizes the following concepts:
• A special configuration function is introduced which can only be called in the control part of a TTCN-3
module to create static test configurations. The configuration function returns a handle of the predefined type
conf
...