SIST ES 201 873-5 V4.9.1:2022
(Main)Methods for Testing and Specification (MTS) - The Testing and Test Control Notation version 3 - Part 5: TTCN-3 Runtime Interface (TRI)
Methods for Testing and Specification (MTS) - The Testing and Test Control Notation version 3 - Part 5: TTCN-3 Runtime Interface (TRI)
The present document provides the specification of the runtime interface for TTCN-3 test system implementations. The
TTCN-3 Runtime Interface provides a standardized adaptation for timing and communication of a test system to a
particular processing platform and the system under test, respectively. The present document defines the interface as a
set of operations independent of target language.
The interface is defined to be compatible with the TTCN-3 standard (see ETSI ES 201 873-1 [2]). The present
document uses the CORBA Interface Definition Language (IDL) to specify the TRI completely. Clauses 6, 7 and 8
present language mappings for this abstract specification to the target languages JavaTM, ANSI C, and C++. A summary
of the IDL based interface specification is provided in annex A.
NOTE: JavaTM is the trade name of a programming language developed by Oracle Corporation. This information
is given for the convenience of users of the present document and does not constitute an endorsement by
ETSI of the programming language named. Equivalent programming languages may be used if they can
be shown to lead to the same results.
Metode za preskušanje in specificiranje (MTS) - 3. različica zapisa preskušanja in krmiljenja preskusov - 5. del: Vmesnik za čas izvajanja (TRI) TTCN-3
Ta dokument določa specificiranje vmesnika za čas izvajanja za preskusne izvedbe sistema TTCN-3. Vmesnik za čas izvajanja TTCN-3 zagotavlja standardizirano prilagoditev za časovni razpored in komunikacijo preskusnega sistema v povezavi z določeno obdelovalno platformo ter sistemom za preskušanje. V tem dokumentu je vmesnik opredeljen kot niz postopkov, neodvisnih od ciljnega jezika. Vmesnik je opredeljen kot združljiv s standardom TTCN-3 (glej ETSI ES 201 873-1 [2]). Za popolno določitev TRI je v tem dokumentu uporabljen jezik za definicijo vmesnikov (IDL) CORBA. V točkah 6, 7 in 8 so predstavljene jezikovne preslikave za to abstraktno specificiranje v ciljne jezike Java™, ANSI C in C++. Povzetek specifikacij vmesnikov na osnovi jezika IDL je podan v dodatku A.
OPOMBA: Java™ je tržno ime programskega jezika, ki ga je razvila družba Oracle Corporation. Te informacije so navedene za boljše razumevanje standarda s strani uporabnikov in ne pomenijo, da ETSI podpira imenovani programski jezik. Uporabljajo se lahko enakovredni programski jeziki, ki zagotavljajo enake rezultate.
General Information
Standards Content (Sample)
Final draft ETSI ES 201 873-5 V4.9.1 (2022-02)
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
Part 5: TTCN-3 Runtime Interface (TRI)
2 Final draft ETSI ES 201 873-5 V4.9.1 (2022-02)
Reference
RES/MTS-201873-5 T3ed491
Keywords
interface, methodology, runtime, testing, TRI,
TTCN-3
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2022.
All rights reserved.
ETSI
3 Final draft ETSI ES 201 873-5 V4.9.1 (2022-02)
Contents
Intellectual Property Rights . 8
Foreword . 8
Modal verbs terminology . 8
Introduction . 8
1 Scope . 10
1.1 Scope of the present document . 10
1.2 Compliance. 10
2 References . 10
2.1 Normative references . 10
2.2 Informative references . 11
3 Definition of terms, symbols and abbreviations . 11
3.1 Terms . 11
3.2 Symbols . 12
3.3 Abbreviations . 12
4 General Structure of a TTCN-3 Test System . 13
4.1 Entities in a TTCN-3 test system . 13
4.1.0 Types of entities . 13
4.1.1 Test Management and Control (TMC). 13
4.1.1.0 Test Management and Control Entities . 13
4.1.1.1 Test Management (TM) . 14
4.1.1.2 Test Logging (TL) . 14
4.1.1.3 Coding and Decoding (CD) . 14
4.1.1.4 Component Handling (CH) . 14
4.1.2 TTCN-3 Executable (TE) . 14
4.1.2.0 TTCN-3 Executable Entity . 14
4.1.2.1 Executable Test Suite (ETS) . 14
4.1.2.2 TTCN-3 RunTime System (T3RTS) . 14
4.1.2.3 Encoding/Decoding System (EDS) . 15
4.1.2.4 Timers in the TTCN-3 Executable . 15
4.1.3 SUT Adaptor (SA) . 15
4.1.4 Platform Adaptor (PA) . 15
4.2 Interfaces in a TTCN-3 Test System . 16
4.3 Execution requirements for a TTCN-3 test system . 16
5 TTCN-3 Runtime Interface and operations . 16
5.1 Overview of the TRI. 16
5.1.0 Sub-interfaces . 16
5.1.1 The triCommunication Interface . 17
5.1.2 The triPlatform Interface . 17
5.1.3 Correlation between TTCN-3 and TRI Operation Invocations . 17
5.2 Error handling . 18
5.2.0 Basic rules . 18
5.2.1 triSAErrorReq (SA → TE) . 19
5.2.2 triPAErrorReq (PA → TE) . 19
5.3 Data interface . 19
5.3.0 Basic rules . 19
5.3.1 Connection . 19
5.3.2 Communication . 20
5.3.3 Timer . 21
5.3.4 Miscellaneous . 21
5.4 Operation descriptions . 21
5.5 Communication interface operations . 21
5.5.1 triSAReset (TE → SA) . 21
ETSI
4 Final draft ETSI ES 201 873-5 V4.9.1 (2022-02)
5.5.2 Connection handling operations . 22
5.5.2.1 triExecuteTestCase (TE → SA) . 22
5.5.2.2 triMap (TE → SA) . 22
5.5.2.3 triMapParam (TE → SA) . 22
5.5.2.4 triUnmap (TE → SA) . 23
5.5.2.5 triUnmapParam (TE → SA) . 23
5.5.2.6 triEndTestCase (TE → SA) . 23
5.5.3 Message based communication operations . 24
5.5.3.1 triSend (TE → SA) . 24
5.5.3.2 triSendBC (TE → SA) . 24
5.5.3.3 triSendMC (TE → SA) . 25
5.5.3.4 triEnqueueMsg (SA → TE) . 25
5.5.4 Procedure based communication operations . 26
5.5.4.1 triCall (TE → SA) . 26
5.5.4.2 triCallBC (TE → SA) . 27
5.5.4.3 triCallMC (TE → SA) . 28
5.5.4.4 triReply (TE → SA) . 29
5.5.4.5 triReplyBC (TE → SA) . 30
5.5.4.6 triReplyMC (TE → SA) . 31
5.5.4.7 triRaise (TE → SA) . 31
5.5.4.8 triRaiseBC (TE → SA) . 32
5.5.4.9 triRaiseMC (TE → SA) . 32
5.5.4.10 triEnqueueCall (SA → TE) . 33
5.5.4.11 triEnqueueReply (SA → TE) . 33
5.5.4.12 triEnqueueException (SA → TE) . 34
5.5.5 Miscellaneous operations . 34
5.5.5.1 triSUTActionInformal (TE → SA) . 34
5.5.5.2 triSUTActionParam (TE → SA) . 34
5.6 Platform interface operations . 35
5.6.1 triPAReset (TE → PA) . 35
5.6.2 Timer operations . 35
5.6.2.1 triStartTimer (TE → PA) . 35
5.6.2.2 triStopTimer (TE → PA). 35
5.6.2.3 triReadTimer (TE → PA) . 36
5.6.2.4 triTimerRunning (TE → PA) . 36
5.6.2.5 triTimeout (PA → TE) . 36
5.6.3 Miscellaneous operations . 37
5.6.3.1 triExternalFunction (TE → PA) . 37
5.6.3.2 triSelf (PA → TE) . 37
5.6.3.3 triRnd (PA → TE) . 37
TM
6 Java language mapping . 38
6.1 Introduction . 38
6.2 Names and scopes . 38
6.2.1 Names . 38
6.2.2 Scopes . 38
6.3 Type mapping . 38
6.3.1 Basic type mapping . 38
6.3.1.0 IDL type mapping . 38
6.3.1.1 Boolean . 39
6.3.1.2 String . 39
6.3.2 Structured type mapping . 39
6.3.2.0 Mapping rules . 39
6.3.2.1 TriPortIdType . 39
6.3.2.2 TriPortIdListType . 40
6.3.2.3 TriComponentIdType . 40
6.3.2.4 TriComponentIdListType . 41
6.3.2.5 TriMessageType . 41
6.3.2.6 TriAddressType . 42
6.3.2.7 TriAddressListType . 42
ETSI
5 Final draft ETSI ES 201 873-5 V4.9.1 (2022-02)
6.3.2.8 TriSignatureIdType . 43
6.3.2.9 TriParameterType . 43
6.3.2.10 TriParameterPassingModeType . 44
6.3.2.11 TriParameterListType . 44
6.3.2.12 TriExceptionType . 45
6.3.2.13 TriTimerIdType . 45
6.3.2.14 TriTimerDurationType . 45
6.3.2.15 TriFunctionIdType . 46
6.3.2.16 TriTestCaseIdType . 46
6.3.2.17 TriActionTemplateType . 46
6.3.2.18 TriStatusType . 47
6.4 Constants . 47
6.5 Mapping of interfaces . 48
6.5.0 Basic rules . 48
6.5.1 Out and InOut Parameter Passing Mode . 48
6.5.2 triCommunication - Interface . 48
6.5.2.0 Introduction . 48
6.5.2.1 triCommunicationSA . 48
6.5.2.2 triCommunicationTE. 49
6.5.3 triPlatform - Interface . 50
6.5.3.0 Introduction . 50
6.5.3.1 TriPlatformPA . 50
6.5.3.2 TriPlatformTE . 51
6.6 Optional parameters . 51
6.7 TRI initialization . 51
7 ANSI C language mapping. 51
7.1 Introduction . 51
7.2 Names and scopes . 51
7.2.0 Naming rules . 51
7.2.1 Abstract type mapping . 52
7.2.2 ANSI C type definitions . 53
7.2.3 IDL type mapping . 53
7.2.4 TRI operation mapping . 53
7.3 Memory management . 56
8 C++ language mapping . 56
8.1 Introduction . 56
8.2 Names and scopes . 56
8.3 Memory management . 56
8.4 Void . 56
8.5 Type mapping . 56
8.5.0 Basic rules . 56
8.5.1 Encapsulated C++ types. 56
8.5.2 Abstract data types . 57
8.5.2.1 QualifiedName . 57
8.5.2.2 TriAddress . 57
8.5.2.3 TriAddressList . 58
8.5.2.4 TriComponentId . 59
8.5.2.5 TriComponentIdList . 59
8.5.2.6 TriException. 60
8.5.2.7 TriFunctionId . 61
8.5.2.8 TriMessage . 61
8.5.2.9 TriParameter. 62
8.5.2.10 TriParameterList . 62
8.5.2.11 TriParameterPassingMode . 63
8.5.2.12 TriPortId . 63
8.5.2.13 TriPortIdList. 64
8.5.2.14 TriSignatureId . 65
8.5.2.15 TriStatus . 65
8.5.2.16 TriTestCaseId . 65
8.5.2.17 TriTimerDuration . 66
ETSI
6 Final draft ETSI ES 201 873-5 V4.9.1 (2022-02)
8.5.2.18 TriTimerId . 66
8.6 Mapping of interfaces . 67
8.6.1 TriCommunicationSA . 67
8.6.2 TriCommunicationTE . 68
8.6.3 TriPlatformPA . 69
8.6.4 TriPlatformTE . 69
9 C# language mapping . 70
9.1 Introduction . 70
9.2 Names and scopes . 70
9.2.1 Names . 70
9.2.2 Scopes . 70
9.3 Null value mapping . 70
9.4 Type mapping . 70
9.4.1 Basic type mapping . 70
9.4.1.0 IDL type mapping . 70
9.4.1.1 Boolean . 71
9.4.1.2 String . 71
9.4.2 Structured type mapping . 71
9.4.2.0 Mapping rules . 71
9.4.2.1 IQualifiedName . 71
9.4.2.2 TriPortIdType . 71
9.4.2.3 TriPortIdListType . 72
9.4.2.4 TriComponentIdType . 72
9.4.2.5 TriComponentIdListType . 73
9.4.2.6 TriMessageType . 73
9.4.2.7 TriAddressType . 74
9.4.2.8 TriAddressListType . 74
9.4.2.9 TriSignatureIdType . 75
9.4.2.10 TriParameterPassingModeType . 75
9.4.2.11 TriParameterType . 75
9.4.2.12 TriParameterListType . 75
9.4.2.13 TriExceptionType . 76
9.4.2.14 TriTimerIdType . 76
9.4.2.15 TriTimerDurationType . 77
9.4.2.16 TriFunctionIdType . 77
9.4.2.17 TriTestCaseIdType . 77
9.4.2.18 TriStatusType . 77
9.5 Mapping of interfaces . 77
9.5.0 Basic rules . 77
9.5.1 Out and inout parameter passing mode . 78
9.5.2 triCommunication interface . 78
9.5.2.0 Introduction . 78
9.5.2.1 ITriCommunicationSA . 78
9.5.2.2 ITriCommunicationTE . 79
9.5.2.3 ITriPlatformPA . 80
9.5.2.4 ITriPlatformTE . 80
9.6 Optional parameters . 80
Annex A (normative): IDL Summary . 81
Annex B (informative): Use scenarios . 85
B.0 Introduction . 85
B.1 First scenario . 86
B.1.0 Use case . 86
B.1.1 TTCN-3 fragment . 86
B.1.2 Message sequence chart . 87
B.2 Second scenario . 88
B.2.0 Use case . 88
B.2.1 TTCN-3 fragment . 88
ETSI
7 Final draft ETSI ES 201 873-5 V4.9.1 (2022-02)
B.2.2 Message sequence chart . 89
B.3 Third scenario . 90
B.3.0 Use case . 90
B.3.1 TTCN-3 fragment . 90
B.3.2 Message sequence chart . 91
Annex C (informative): Bibliography . 92
History . 93
ETSI
8 Final draft ETSI ES 201 873-5 V4.9.1 (2022-02)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This final draft ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and
Specification (MTS), and is now submitted for the ETSI standards Membership Approval Procedure.
The present document is part 5 of a multi-part deliverable. Full details of the entire series can be found in part 1 [2].
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 present document consists of two distinct parts, the first part describing the structure of a TTCN-3 test system
implementation and the second part presenting the TTCN-3 Runtime Interface specification.
The first part introduces the decomposition of a TTCN-3 test system into four main entities: Test Management (TM),
TTCN-3 Executable (TE), SUT Adaptor (SA), and Platform Adaptor (PA). In addition, the interaction between these
entities, i.e. the corresponding interfaces, is defined.
ETSI
9 Final draft ETSI ES 201 873-5 V4.9.1 (2022-02)
...
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
Part 5: TTCN-3 Runtime Interface (TRI)
2 ETSI ES 201 873-5 V4.9.1 (2022-04)
Reference
RES/MTS-201873-5 T3ed491
Keywords
interface, methodology, runtime, testing, TRI,
TTCN-3
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2022.
All rights reserved.
ETSI
3 ETSI ES 201 873-5 V4.9.1 (2022-04)
Contents
Intellectual Property Rights . 8
Foreword . 8
Modal verbs terminology . 8
Introduction . 8
1 Scope . 9
1.1 Scope of the present document . 9
1.2 Compliance. 9
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 10
3 Definition of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 11
3.3 Abbreviations . 11
4 General Structure of a TTCN-3 Test System . 12
4.1 Entities in a TTCN-3 test syst em . 12
4.1.0 Types of entities . 12
4.1.1 Test Management and Control (TMC). 12
4.1.1.0 Test Management and Control Entities . 12
4.1.1.1 Test Management (TM) . 13
4.1.1.2 Test Logging (TL) . 13
4.1.1.3 Coding and Decoding (CD) . 13
4.1.1.4 Component Handling (CH) . 13
4.1.2 TTCN-3 Executable (TE) . 13
4.1.2.0 TTCN-3 Executable Entity . 13
4.1.2.1 Executable Test Suite (ETS) . 13
4.1.2.2 TTCN-3 RunTime System (T3RTS) . 13
4.1.2.3 Encoding/Decoding System (EDS) . 14
4.1.2.4 Timers in the TTCN-3 Executable . 14
4.1.3 SUT Adaptor (SA) . 14
4.1.4 Platform Adaptor (PA) . 14
4.2 Interfaces in a TTCN-3 Test System . 15
4.3 Execution requirements for a TTCN-3 test system . 15
5 TTCN-3 Runtime Interface and operations . 15
5.1 Overview of the TRI. 15
5.1.0 Sub-interfaces . 15
5.1.1 The triCommunication Interface . 16
5.1.2 The triPlatform Interface . 16
5.1.3 Correlation between TTCN-3 and TRI Operation Invocations . 16
5.2 Error handling . 17
5.2.0 Basic rules . 17
5.2.1 triSAErrorReq (SA → TE) . 18
5.2.2 triPAErrorReq (PA → TE) . 18
5.3 Data interface . 18
5.3.0 Basic rules . 18
5.3.1 Connection . 18
5.3.2 Communication . 19
5.3.3 Timer . 20
5.3.4 Miscellaneous . 20
5.4 Operation descriptions . 20
5.5 Communication interface operations . 21
5.5.1 triSAReset (TE → SA) . 21
5.5.2 Connection handling operations . 21
ETSI
4 ETSI ES 201 873-5 V4.9.1 (2022-04)
5.5.2.1 triExecuteTestCase (TE → SA) . 21
5.5.2.2 triMap (TE → SA) . 21
5.5.2.3 triMapParam (TE → SA) . 22
5.5.2.4 triUnmap (TE → SA) . 22
5.5.2.5 triUnmapParam (TE → SA) . 22
5.5.2.6 triEndTestCase (TE → SA) . 23
5.5.3 Message based communication operations . 23
5.5.3.1 triSend (TE → SA) . 23
5.5.3.2 triSendBC (TE → SA) . 23
5.5.3.3 triSendMC (TE → SA) . 24
5.5.3.4 triEnqueueMsg (SA → TE) . 24
5.5.4 Procedure based communication operations . 25
5.5.4.1 triCall (TE → SA) . 25
5.5.4.2 triCallBC (TE → SA) . 26
5.5.4.3 triCallMC (TE → SA) . 27
5.5.4.4 triReply (TE → SA) . 28
5.5.4.5 triReplyBC (TE → SA) . 29
5.5.4.6 triReplyMC (TE → SA) . 30
5.5.4.7 triRaise (TE → SA) . 30
5.5.4.8 triRaiseBC (TE → SA) . 31
5.5.4.9 triRaiseMC (TE → SA) . 31
5.5.4.10 triEnqueueCall (SA → TE) . 32
5.5.4.11 triEnqueueReply (SA → TE) . 32
5.5.4.12 triEnqueueException (SA → TE) . 33
5.5.5 Miscellaneous operations . 33
5.5.5.1 triSUTActionInformal (TE → SA) . 33
5.5.5.2 triSUTActionParam (TE → SA) . 33
5.6 Platform interface operations . 34
5.6.1 triPAReset (TE → PA) . 34
5.6.2 Timer operations . 34
5.6.2.1 triStartTimer (TE → PA) . 34
5.6.2.2 triStopTimer (TE → PA). 34
5.6.2.3 triReadTimer (TE → PA) . 35
5.6.2.4 triTimerRunning (TE → PA) . 35
5.6.2.5 triTimeout (PA → TE) . 35
5.6.3 Miscellaneous operations . 36
5.6.3.1 triExternalFunction (TE → PA) . 36
5.6.3.2 triSelf (PA → TE) . 36
5.6.3.3 triRnd (PA → TE) . 36
TM
6 Java language mapping . 37
6.1 Introduction . 37
6.2 Names and scopes . 37
6.2.1 Names . 37
6.2.2 Scopes . 37
6.3 Type mapping . 37
6.3.1 Basic type mapping . 37
6.3.1.0 IDL type mapping . 37
6.3.1.1 Boolean . 38
6.3.1.2 String . 38
6.3.2 Structured type mapping . 38
6.3.2.0 Mapping rules . 38
6.3.2.1 TriPortIdType . 38
6.3.2.2 TriPortIdListType . 39
6.3.2.3 TriComponentIdType . 39
6.3.2.4 TriComponentIdListType . 40
6.3.2.5 TriMessageType . 40
6.3.2.6 TriAddressType . 41
6.3.2.7 TriAddressListType . 41
6.3.2.8 TriSignatureIdType . 42
ETSI
5 ETSI ES 201 873-5 V4.9.1 (2022-04)
6.3.2.9 TriParameterType . 42
6.3.2.10 TriParameterPassingModeType . 43
6.3.2.11 TriParameterListType . 43
6.3.2.12 TriExceptionType . 44
6.3.2.13 TriTimerIdType . 44
6.3.2.14 TriTimerDurationType . 44
6.3.2.15 TriFunctionIdType . 45
6.3.2.16 TriTestCaseIdType . 45
6.3.2.17 TriActionTemplateType . 45
6.3.2.18 TriStatusType . 46
6.4 Constants . 46
6.5 Mapping of interfaces . 47
6.5.0 Basic rules . 47
6.5.1 Out and InOut Parameter Passing Mode . 47
6.5.2 triCommunication - Interface . 47
6.5.2.0 Introduction . 47
6.5.2.1 triCommunicationSA . 47
6.5.2.2 triCommunicationTE. 49
6.5.3 triPlatform - Interface . 49
6.5.3.0 Introduction . 49
6.5.3.1 TriPlatformPA . 49
6.5.3.2 TriPlatformTE . 50
6.6 Optional parameters . 50
6.7 TRI initialization . 50
7 ANSI C language mapping. 50
7.1 Introduction . 50
7.2 Names and scopes . 50
7.2.0 Naming rules . 50
7.2.1 Abstract type mapping . 51
7.2.2 ANSI C type definitions . 52
7.2.3 IDL type mapping . 52
7.2.4 TRI operation mapping . 52
7.3 Memory management . 55
8 C++ language mapping . 55
8.1 Introduction . 55
8.2 Names and scopes . 55
8.3 Memory management . 55
8.4 Void . 55
8.5 Type mapping . 55
8.5.0 Basic rules . 55
8.5.1 Encapsulated C++ types. 55
8.5.2 Abstract data types . 56
8.5.2.1 QualifiedName . 56
8.5.2.2 TriAddress . 56
8.5.2.3 TriAddressList . 57
8.5.2.4 TriComponentId . 58
8.5.2.5 TriComponentIdList . 58
8.5.2.6 TriException. 59
8.5.2.7 TriFunctionId . 60
8.5.2.8 TriMessage . 60
8.5.2.9 TriParameter. 61
8.5.2.10 TriParameterList . 61
8.5.2.11 TriParameterPassingMode . 62
8.5.2.12 TriPortId . 62
8.5.2.13 TriPortIdList. 63
8.5.2.14 TriSignatureId . 64
8.5.2.15 TriStatus . 64
8.5.2.16 TriTestCaseId . 64
8.5.2.17 TriTimerDuration . 65
8.5.2.18 TriTimerId . 65
ETSI
6 ETSI ES 201 873-5 V4.9.1 (2022-04)
8.6 Mapping of interfaces . 66
8.6.1 TriCommunicationSA . 66
8.6.2 TriCommunicationTE . 67
8.6.3 TriPlatformPA . 68
8.6.4 TriPlatformTE . 68
9 C# language mapping . 69
9.1 Introduction . 69
9.2 Names and scopes . 69
9.2.1 Names . 69
9.2.2 Scopes . 69
9.3 Null value mapping . 69
9.4 Type mapping . 69
9.4.1 Basic type mapping . 69
9.4.1.0 IDL type mapping . 69
9.4.1.1 Boolean . 70
9.4.1.2 String . 70
9.4.2 Structured type mapping . 70
9.4.2.0 Mapping rules . 70
9.4.2.1 IQualifiedName . 70
9.4.2.2 TriPortIdType . 70
9.4.2.3 TriPortIdListType . 71
9.4.2.4 TriComponentIdType . 71
9.4.2.5 TriComponentIdListType . 72
9.4.2.6 TriMessageType . 72
9.4.2.7 TriAddressType . 73
9.4.2.8 TriAddressListType . 73
9.4.2.9 TriSignatureIdType . 74
9.4.2.10 TriParameterPassingModeType . 74
9.4.2.11 TriParameterType . 74
9.4.2.12 TriParameterListType . 74
9.4.2.13 TriExceptionType . 75
9.4.2.14 TriTimerIdType . 75
9.4.2.15 TriTimerDurationType . 76
9.4.2.16 TriFunctionIdType . 76
9.4.2.17 TriTestCaseIdType . 76
9.4.2.18 TriStatusType . 76
9.5 Mapping of interfaces . 76
9.5.0 Basic rules . 76
9.5.1 Out and inout parameter passing mode . 77
9.5.2 triCommunication interface . 77
9.5.2.0 Introduction . 77
9.5.2.1 ITriCommunicationSA . 77
9.5.2.2 ITriCommunicationTE . 78
9.5.2.3 ITriPlatformPA . 79
9.5.2.4 ITriPlatformTE . 79
9.6 Optional parameters . 79
Annex A (normative): IDL Summary . 80
Annex B (informative): Use scenarios . 84
B.0 Introduction . 84
B.1 First scenario . 85
B.1.0 Use case . 85
B.1.1 TTCN-3 fragment . 85
B.1.2 Message sequence chart . 86
B.2 Second scenario . 87
B.2.0 Use case . 87
B.2.1 TTCN-3 fragment . 87
B.2.2 Message sequence chart . 88
ETSI
7 ETSI ES 201 873-5 V4.9.1 (2022-04)
B.3 Third scenario . 89
B.3.0 Use case . 89
B.3.1 TTCN-3 fragment . 89
B.3.2 Message sequence chart . 90
Annex C (informative): Bibliography . 91
History . 92
ETSI
8 ETSI ES 201 873-5 V4.9.1 (2022-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document is part 5 of a multi-part deliverable. Full details of the entire series can be found in part 1 [2].
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 present document consists of two distinct parts, the first part describing the structure of a TTCN-3 test system
implementation and the second part presenting the TTCN-3 Runtime Interface specification.
The first part introduces the decomposition of a TTCN-3 test system into four main entities: Test Management (TM),
TTCN-3 Executable (TE), SUT Adaptor (SA), and Platform Adaptor (PA). In addition, the interaction between these
entities, i.e. the corresponding interfaces, is defined.
The second part of the present document specifies the TTCN-3 Runtime Interface (TRI). T
...
SLOVENSKI STANDARD
01-julij-2022
Metode za preskušanje in specificiranje (MTS) - 3. različica zapisa preskušanja in
krmiljenja preskusov - 5. del: Vmesnik za čas izvajanja (TRI) TTCN-3
Methods for Testing and Specification (MTS) - The Testing and Test Control Notation
version 3 - Part 5: TTCN-3 Runtime Interface (TRI)
Ta slovenski standard je istoveten z: ETSI ES 201 873-5 V4.9.1 (2022-04)
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
Part 5: TTCN-3 Runtime Interface (TRI)
2 ETSI ES 201 873-5 V4.9.1 (2022-04)
Reference
RES/MTS-201873-5 T3ed491
Keywords
interface, methodology, runtime, testing, TRI,
TTCN-3
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2022.
All rights reserved.
ETSI
3 ETSI ES 201 873-5 V4.9.1 (2022-04)
Contents
Intellectual Property Rights . 8
Foreword . 8
Modal verbs terminology . 8
Introduction . 8
1 Scope . 9
1.1 Scope of the present document . 9
1.2 Compliance. 9
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 10
3 Definition of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 11
3.3 Abbreviations . 11
4 General Structure of a TTCN-3 Test System . 12
4.1 Entities in a TTCN-3 test syst em . 12
4.1.0 Types of entities . 12
4.1.1 Test Management and Control (TMC). 12
4.1.1.0 Test Management and Control Entities . 12
4.1.1.1 Test Management (TM) . 13
4.1.1.2 Test Logging (TL) . 13
4.1.1.3 Coding and Decoding (CD) . 13
4.1.1.4 Component Handling (CH) . 13
4.1.2 TTCN-3 Executable (TE) . 13
4.1.2.0 TTCN-3 Executable Entity . 13
4.1.2.1 Executable Test Suite (ETS) . 13
4.1.2.2 TTCN-3 RunTime System (T3RTS) . 13
4.1.2.3 Encoding/Decoding System (EDS) . 14
4.1.2.4 Timers in the TTCN-3 Executable . 14
4.1.3 SUT Adaptor (SA) . 14
4.1.4 Platform Adaptor (PA) . 14
4.2 Interfaces in a TTCN-3 Test System . 15
4.3 Execution requirements for a TTCN-3 test system . 15
5 TTCN-3 Runtime Interface and operations . 15
5.1 Overview of the TRI. 15
5.1.0 Sub-interfaces . 15
5.1.1 The triCommunication Interface . 16
5.1.2 The triPlatform Interface . 16
5.1.3 Correlation between TTCN-3 and TRI Operation Invocations . 16
5.2 Error handling . 17
5.2.0 Basic rules . 17
5.2.1 triSAErrorReq (SA → TE) . 18
5.2.2 triPAErrorReq (PA → TE) . 18
5.3 Data interface . 18
5.3.0 Basic rules . 18
5.3.1 Connection . 18
5.3.2 Communication . 19
5.3.3 Timer . 20
5.3.4 Miscellaneous . 20
5.4 Operation descriptions . 20
5.5 Communication interface operations . 21
5.5.1 triSAReset (TE → SA) . 21
5.5.2 Connection handling operations . 21
ETSI
4 ETSI ES 201 873-5 V4.9.1 (2022-04)
5.5.2.1 triExecuteTestCase (TE → SA) . 21
5.5.2.2 triMap (TE → SA) . 21
5.5.2.3 triMapParam (TE → SA) . 22
5.5.2.4 triUnmap (TE → SA) . 22
5.5.2.5 triUnmapParam (TE → SA) . 22
5.5.2.6 triEndTestCase (TE → SA) . 23
5.5.3 Message based communication operations . 23
5.5.3.1 triSend (TE → SA) . 23
5.5.3.2 triSendBC (TE → SA) . 23
5.5.3.3 triSendMC (TE → SA) . 24
5.5.3.4 triEnqueueMsg (SA → TE) . 24
5.5.4 Procedure based communication operations . 25
5.5.4.1 triCall (TE → SA) . 25
5.5.4.2 triCallBC (TE → SA) . 26
5.5.4.3 triCallMC (TE → SA) . 27
5.5.4.4 triReply (TE → SA) . 28
5.5.4.5 triReplyBC (TE → SA) . 29
5.5.4.6 triReplyMC (TE → SA) . 30
5.5.4.7 triRaise (TE → SA) . 30
5.5.4.8 triRaiseBC (TE → SA) . 31
5.5.4.9 triRaiseMC (TE → SA) . 31
5.5.4.10 triEnqueueCall (SA → TE) . 32
5.5.4.11 triEnqueueReply (SA → TE) . 32
5.5.4.12 triEnqueueException (SA → TE) . 33
5.5.5 Miscellaneous operations . 33
5.5.5.1 triSUTActionInformal (TE → SA) . 33
5.5.5.2 triSUTActionParam (TE → SA) . 33
5.6 Platform interface operations . 34
5.6.1 triPAReset (TE → PA) . 34
5.6.2 Timer operations . 34
5.6.2.1 triStartTimer (TE → PA) . 34
5.6.2.2 triStopTimer (TE → PA). 34
5.6.2.3 triReadTimer (TE → PA) . 35
5.6.2.4 triTimerRunning (TE → PA) . 35
5.6.2.5 triTimeout (PA → TE) . 35
5.6.3 Miscellaneous operations . 36
5.6.3.1 triExternalFunction (TE → PA) . 36
5.6.3.2 triSelf (PA → TE) . 36
5.6.3.3 triRnd (PA → TE) . 36
TM
6 Java language mapping . 37
6.1 Introduction . 37
6.2 Names and scopes . 37
6.2.1 Names . 37
6.2.2 Scopes . 37
6.3 Type mapping . 37
6.3.1 Basic type mapping . 37
6.3.1.0 IDL type mapping . 37
6.3.1.1 Boolean . 38
6.3.1.2 String . 38
6.3.2 Structured type mapping . 38
6.3.2.0 Mapping rules . 38
6.3.2.1 TriPortIdType . 38
6.3.2.2 TriPortIdListType . 39
6.3.2.3 TriComponentIdType . 39
6.3.2.4 TriComponentIdListType . 40
6.3.2.5 TriMessageType . 40
6.3.2.6 TriAddressType . 41
6.3.2.7 TriAddressListType . 41
6.3.2.8 TriSignatureIdType . 42
ETSI
5 ETSI ES 201 873-5 V4.9.1 (2022-04)
6.3.2.9 TriParameterType . 42
6.3.2.10 TriParameterPassingModeType . 43
6.3.2.11 TriParameterListType . 43
6.3.2.12 TriExceptionType . 44
6.3.2.13 TriTimerIdType . 44
6.3.2.14 TriTimerDurationType . 44
6.3.2.15 TriFunctionIdType . 45
6.3.2.16 TriTestCaseIdType . 45
6.3.2.17 TriActionTemplateType . 45
6.3.2.18 TriStatusType . 46
6.4 Constants . 46
6.5 Mapping of interfaces . 47
6.5.0 Basic rules . 47
6.5.1 Out and InOut Parameter Passing Mode . 47
6.5.2 triCommunication - Interface . 47
6.5.2.0 Introduction . 47
6.5.2.1 triCommunicationSA . 47
6.5.2.2 triCommunicationTE. 49
6.5.3 triPlatform - Interface . 49
6.5.3.0 Introduction . 49
6.5.3.1 TriPlatformPA . 49
6.5.3.2 TriPlatformTE . 50
6.6 Optional parameters . 50
6.7 TRI initialization . 50
7 ANSI C language mapping. 50
7.1 Introduction . 50
7.2 Names and scopes . 50
7.2.0 Naming rules . 50
7.2.1 Abstract type mapping . 51
7.2.2 ANSI C type definitions . 52
7.2.3 IDL type mapping . 52
7.2.4 TRI operation mapping . 52
7.3 Memory management . 55
8 C++ language mapping . 55
8.1 Introduction . 55
8.2 Names and scopes . 55
8.3 Memory management . 55
8.4 Void . 55
8.5 Type mapping . 55
8.5.0 Basic rules . 55
8.5.1 Encapsulated C++ types. 55
8.5.2 Abstract data types . 56
8.5.2.1 QualifiedName . 56
8.5.2.2 TriAddress . 56
8.5.2.3 TriAddressList . 57
8.5.2.4 TriComponentId . 58
8.5.2.5 TriComponentIdList . 58
8.5.2.6 TriException. 59
8.5.2.7 TriFunctionId . 60
8.5.2.8 TriMessage . 60
8.5.2.9 TriParameter. 61
8.5.2.10 TriParameterList . 61
8.5.2.11 TriParameterPassingMode . 62
8.5.2.12 TriPortId . 62
8.5.2.13 TriPortIdList. 63
8.5.2.14 TriSignatureId . 64
8.5.2.15 TriStatus . 64
8.5.2.16 TriTestCaseId . 64
8.5.2.17 TriTimerDuration . 65
8.5.2.18 TriTimerId . 65
ETSI
6 ETSI ES 201 873-5 V4.9.1 (2022-04)
8.6 Mapping of interfaces . 66
8.6.1 TriCommunicationSA . 66
8.6.2 TriCommunicationTE . 67
8.6.3 TriPlatformPA . 68
8.6.4 TriPlatformTE . 68
9 C# language mapping . 69
9.1 Introduction . 69
9.2 Names and scopes . 69
9.2.1 Names . 69
9.2.2 Scopes . 69
9.3 Null value mapping . 69
9.4 Type mapping . 69
9.4.1 Basic type mapping . 69
9.4.1.0 IDL type mapping . 69
9.4.1.1 Boolean . 70
9.4.1.2 String . 70
9.4.2 Structured type mapping . 70
9.4.2.0 Mapping rules . 70
9.4.2.1 IQualifiedName . 70
9.4.2.2 TriPortIdType . 70
9.4.2.3 TriPortIdListType . 71
9.4.2.4 TriComponentIdType . 71
9.4.2.5 TriComponentIdListType . 72
9.4.2.6 TriMessageType . 72
9.4.2.7 TriAddressType . 73
9.4.2.8 TriAddressListType . 73
9.4.2.9 TriSignatureIdType . 74
9.4.2.10 TriParameterPassingModeType . 74
9.4.2.11 TriParameterType . 74
9.4.2.12 TriParameterListType . 74
9.4.2.13 TriExceptionType . 75
9.4.2.14 TriTimerIdType . 75
9.4.2.15 TriTimerDurationType . 76
9.4.2.16 TriFunctionIdType . 76
9.4.2.17 TriTestCaseIdType . 76
9.4.2.18 TriStatusType . 76
9.5 Mapping of interfaces . 76
9.5.0 Basic rules . 76
9.5.1 Out and inout parameter passing mode . 77
9.5.2 triCommunication interface . 77
9.5.2.0 Introduction . 77
9.5.2.1 ITriCommunicationSA . 77
9.5.2.2 ITriCommunicationTE . 78
9.5.2.3 ITriPlatformPA . 79
9.5.2.4 ITriPlatformTE . 79
9.6 Optional parameters . 79
Annex A (normative): IDL Summary . 80
Annex B (informative): Use scenarios . 84
B.0 Introduction . 84
B.1 First scenario . 85
B.1.0 Use case . 85
B.1.1 TTCN-3 fragment . 85
B.1.2 Message sequence chart . 86
B.2 Second scenario . 87
B.2.0 Use case . 87
B.2.1 TTCN-3 fragment . 87
B.2.2 Message sequence chart . 88
ETSI
7 ETSI ES 201 873-5 V4.9.1 (2022-04)
B.3 Third scenario . 89
B.3.0 Use case . 89
B.3.1 TTCN-3 fragment . 89
B.3.2 Message sequence chart . 90
Annex C (informative): Bibliography . 91
History . 92
ETSI
8 ETSI ES 201 873-5 V4.9.1 (2022-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document is part 5 of
...
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...