SIST ES 202 784 V1.7.1:2020

SLOVENSKI STANDARD
SIST ES 202 784 V1.7.1:2020
01-julij-2020

Metode za preskušanje in specificiranje (MTS) - 3. različica zapisa preskušanja in

Methods for Testing and Specification (MTS) - The Testing and Test Control Notation

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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:

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying

The content of the PDF version shall not be modified without the written authorization of ETSI.

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

oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and

Intellectual Property Rights ................................................................................................................................ 4

Foreword ............................................................................................................................................................. 4

Modal verbs terminology .................................................................................................................................... 4

1 Scope ........................................................................................................................................................ 5

2 References ................................................................................................................................................ 5

2.1 Normative references ......................................................................................................................................... 5

2.2 Informative references ........................................................................................................................................ 6

3 Definition of terms, symbols and abbreviations ....................................................................................... 6

3.1 Terms .................................................................................................................................................................. 6

3.2 Symbols .............................................................................................................................................................. 6

3.3 Abbreviations ..................................................................................................................................................... 6

4 Package conformance and compatibility .................................................................................................. 7

5 Package concepts for the core language ................................................................................................... 7

5.1 Extension to ETSI ES 201 873-1, clause 4 (Introduction) ................................................................................. 7

5.2 Extension to ETSI ES 201 873-1, clause 5 (Basic language elements) .............................................................. 7

5.3 Extension to ETSI ES 201 873-1, clause 6 (Types and values)........................................................................ 11

5.4 Extension to ETSI ES 201 873-1, clause 8 (Modules) ..................................................................................... 12

5.5 Extension to ETSI ES 201 873-1, annex A (BNF and static semantics) .......................................................... 13

5.6 Extension to ETSI ES 203 790, clause 5.1 (Classes and Objects) .................................................................... 14

5.7 Extension to ETSI ES 203 790, clause A.3 (Additional TTCN-3 syntax BNF productions) ........................... 15

6 Package semantics .................................................................................................................................. 15

6.0 General ............................................................................................................................................................. 15

6.1 Extension to ETSI ES 201 873-4, clause 6 (Restrictions) ................................................................................ 15

7 TRI and Extended TRI extensions for the package ................................................................................ 15

7.1 Extension to ETSI ES 201 873-5 ...................................................................................................................... 15

7.2 Extension to ETSI ES 202 789, clause 7 (TRI extensions for the package) ..................................................... 16

8 TCI extensions for the package .............................................................................................................. 16

8.1 Extension to ETSI ES 201 873-6, clause 7 (TTCN 3 control interface and operations) .................................. 16

8.2 Extension to ETSI ES 201 873-6, clause 8 (Java™ language mapping) .......................................................... 18

8.3 Extension to ETSI ES 201 873-6, clause 9 (ANSI C language mapping) ........................................................ 20

8.4 Extension to ETSI ES 201 873-6, clause 10 (C++ language mapping) ............................................................ 21

8.5 Extension to ETSI ES 201 873-6, annex A (IDL Specification of TCI) .......................................................... 22

9 Package Extensions for the use of ASN.1 with TTCN-3 ....................................................................... 22

9.1 Extension to ETSI ES 201 873-7, clause 10 (Parameterization in ASN.1) ...................................................... 22

10 Documentation extensions for the package ............................................................................................ 26

10.1 Extension to ETSI ES 201 873-10, clause 6 (Tagged paragraphs) ................................................................... 26

10.2 Extension to ETSI ES 201 873-10, annex A (where Tags can be used) ........................................................... 27

History .............................................................................................................................................................. 28

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

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

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.

This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification

The use of underline (additional text) and strike through (deleted text) highlights the differences between base

The present document relates to the multi-part standard ETSI ES 201 873 covering the Testing and Test Control

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

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

The present document defines the Advanced Parameterization 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 CORBA based platforms, 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

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

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 documents which are not found to be publicly available in the expected location might be found at

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee

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

[2] ETSI ES 201 873-4: "Methods for Testing and Specification (MTS); The Testing and Test Control

[3] ETSI ES 201 873-5: "Methods for Testing and Specification (MTS); The Testing and Test Control

[4] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control

[5] ETSI ES 201 873-7: "Methods for Testing and Specification (MTS); The Testing and Test Control

[6] 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".

[7] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing

[8] ETSI ES 201 873-8: "Methods for Testing and Specification (MTS); The Testing and Test Control

[9] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control

[10] Recommendation ITU-T X.683: "Information technology - Abstract Syntax Notation One

[11] ETSI ES 202 789: "Methods for Testing and Specification (MTS); The Testing and Test Control

[12] ETSI ES 203 790: "Methods for Testing and Specification (MTS); The Testing and Test Control

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

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee

The following referenced documents are not necessary for the application of the present document but they assist the

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], ETSI ES 201 873-7 [5], ETSI ES 201 873-10 [6], ISO/IEC 9646-1 [7] and

subtype compatibility: type "A" has a subtype compatibility to another type "B" if all of the values of type A are type

NOTE: All subtypes defined via subtype definition are subtype compatible with their supertype.

type parameterization: ability to pass a type as an actual parameter into a parameterized object via a type parameter

NOTE: This actual type parameter is added to the specification of that object and may complete it.

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], ETSI ES 201 873-7 [5], ETSI ES 201 873-10 [6] and

• "TTCN-3:2014 Advanced Parameterization" - to be used with modules complying with the present

NOTE: This version of the package only extends the previous versions, identified with the package tag

"TTCN-3:2009 Advanced Parameterization", with the option of parameterizing objects - in

addition to types - also with signatures. For this reason, modules not containing a formal or actual

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

If later versions of those parts are available and should be used instead, the compatibility to the package presented in the

Additionally, formal type parameters can be used as types of formal value parameters, return values, runs on and

Replace table 2 "Overview of parameterizable TTCN-3 objects" with the following table.

Keyword Allowed kind of Allowed form of non- Allowed types in formal non-type parameter lists

module Value parameterization Static at start of run-time all basic types, all user-defined types and address

type Value parameterization, Static at compile-time all basic types, all user-defined types and address

template Value and template Dynamic at run-time all basic types, all user-defined types, address type,

function Value, template, port and Dynamic at run-time all basic types, all user-defined types, address type,

(note 1) timer parameterization, component type, port type, default, template and

altstep Value, template, port and Dynamic at run-time all basic types, all user-defined types, address type,

(note 1) timer parameterization, component type, port type, default, template and

testcase Value, template, port and Dynamic at run-time all basic types and of all user-defined types, address

signature Value and template Dynamic at run-time all basic types, all user-defined types and address

NOTE 2: Only port and component types are parameterizable with signature formal parameters.

In addition to the existing rules, TTCN-3 supports value parameterizations as follows:

a) Language elements which cannot be parameterized are: const, var, timer, control, record of, set of,

e) The expression of formal parameter's default value has to be compatible with the type of the parameter. The

expression may be any expression that is well-defined at the beginning of the scope of the parameterized

entity, but shall not refer to other parameters of the same or any following parameter list.

d) The default template instance has to be compatible with the type of the parameter. The template instance may

be any template expression that is well-defined at the beginning of the scope of the parameterized entity, but

Type, template and behaviour definitions in TTCN-3 can have parameters of kind type.

[ in ] [ TypeIdentifier | type | signature ] TypeParIdentifier [ ":=" ( Type | Signature ) ]

Types and signatures passed into a parameterized object can be used inside the definition of that object. This includes

the usage as type of value, template, and port parameters, as type of return values and within runs on and system

Type and signature parameters shall be written in a separate parameter list, enclosed in angle brackets.

Parameters of type kind may have a default type, which is given by a type assigned to the parameter. Similarly,

parameters of signature kind may own a default signature, which is identified by assigning a signature to the parameter.

The actual parameters of a type parameter can be required to be subtype compatible with a specific type. This is

indicated by referring to a specific type in the formal parameter list instead of using the keyword type.

a) Formal type and signature parameters shall be in parameters, which can optionally be indicated by the optional

b) When a TypeIdentifier is used to specify the kind of the formal parameter, the default types shall be subtype

compatible with the type of the parameter. For type compatibility see ETSI ES 201 873-1 [1] TTCN-3 Core

Language, clause 6.3. The default type shall not refer to other type parameters in the same parameter list.

function isElement (in MyList list, in T elem) return boolean { … }

e) The expression of the default value has to be compatible with the type of the parameter. The expression shall

not refer to elements of the component type of the optional runs on clause. The expression shall not refer to

other parameters of the same parameter list. The expression shall not contain the invocation of functions with a

e) The type of a value parameter with a default value shall not be a type parameter.

a) Only function, testcase, altstep and template definitions may have formal template parameters.

a) The type of a template parameter with a default template shall not be a type parameter.

Types can be passed into parameterized TTCN-3 objects as actual type parameters. Signatures can be passed into

parameterized TTCN-3 objects as actual signature parameters. Actual type and signature parameters can be provided

both as a list in the same order as the formal parameters as well as in an assignment notation, explicitly using the

associated formal parameter names. They can also be provided in mixed form, starting with actual parameters in list

Actual type parameters that are passed to formal type parameters shall be types or formal type parameters or nested type

definitions. Actual signature parameters that are passed to formal signature parameters shall be signatures or formal

signature parameters. Any compatible type/signature can be passed as actual parameter, i.e. actual parameters are not

limited to those types/signatures only known in the module containing the parameterized definition itself. Formal type

and signature parameters passed as parameters are those from the enclosing scope unit.

An empty type/signature parameter list can be omitted in both the declaration and usage of that object.

a) When using list notation, the order of elements in the actual parameter list shall be the same as their order in

the corresponding formal parameter list. For each formal parameter without a default type/signature there

shall be an actual parameter. If a formal parameter with a default is followed by a formal parameter without a

default, the actual parameter can be skipped by using dash "-" as actual parameter. If a formal parameter with

a default is not followed by a parameter without a default, then the actual parameter can simply be omitted.

b) When using assignment notation, each formal parameter shall be assigned an actual parameter at most once.

For each formal parameter without default type or signature, there shall be an actual parameter. To use the

default type or signature of a formal parameter, no assignment for this specific parameter shall be provided.

c) If a formal parameter was defined using a specific component type, then the actual parameter shall be

compatible with the type of the formal parameter. For type compatibility of component types see ETSI

d) Instantiating formal type or signature parameters with actual types/signatures shall result in valid TTCN-3.