ETSI ES 202 789 V1.2.1 (2013-04)

SLOVENSKI STANDARD
SIST ES 202 789 V1.2.1:2014
01-julij-2014

0HWRGH]DSUHVNXãDQMHLQVSHFLILFLUDQMH076UD]OLþLFD]DSLVDSUHVNXãDQMDLQ

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 more than one electronic version or in print. In any case of existing or

perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).

In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive

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:

DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.

3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and

GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.

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

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

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

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

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

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

3 Definitions and abbreviations ................................................................................................................... 6

3.1 Definitions .......................................................................................................................................................... 6

3.2 Abbreviations ..................................................................................................................................................... 6

4 Package conformance and compatibility .................................................................................................. 6

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

6 Package semantics .................................................................................................................................... 7

7 TRI extensions for the package ................................................................................................................ 7

7.1 Changes to clause 5.2 of ES 201 873-5, Error handling ..................................................................................... 8

7.2 Changes to clause 5.5.2 Connection handling operations .................................................................................. 8

7.3 Changes to clause 5.5.3 Message based communication operations .................................................................. 9

7.4 Addition to clause 5.5.3 Message based communication operations ................................................................ 11

7.5 Changes to clause 5.5.4 Procedure based communication operations .............................................................. 12

7.6 Changes to clause 5.6.3 Miscellaneous operations ........................................................................................... 20

7.7 Changes to clause 6 Java language mapping .................................................................................................... 21

7.8 Changes to clause 7 C language mapping ........................................................................................................ 23

7.9 Changes to clause 8 C++ language mapping .................................................................................................... 25

7.10 Changes to clause 9 C# language mapping ...................................................................................................... 27

8 TCI extensions for the package .............................................................................................................. 29

History .............................................................................................................................................................. 30

IPRs essential or potentially essential to the present document 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

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

The present document relates to the multi-part standard covering the Testing and Test Control Notation version 3, as

ES 202 781 [i.7]: "TTCN-3 Language Extensions: Configuration and Deployment Support";

ES 202 782 [i.10]: "TTCN-3 Language Extensions: Performance and Real-Time Testing Concepts";

The present document defines the Extended TRI 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 or in its interfaces TRI and TCI, but which are optional as part of a package which is suited for

This package defines a more efficient handling of software values by a version of TRI, that does not use binary encoded

messages for the communication with the SUT, but uses the values as they are; meaning e.g. that software objects 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] Recommendation ITU-T X.290: "OSI conformance testing methodology and framework for

NOTE: The corresponding ISO/IEC standard is ISO/IEC 9646-1: "Information technology -- Open Systems

Interconnection -- Conformance testing methodology and framework -- Part 1: General concepts".

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

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

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

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

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

[i.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".

[i.7] ETSI ES 202 781: "Methods for Testing and Specification (MTS); The Testing and Test Control

Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support".

[i.8] ETSI ES 202 784: "Methods for Testing and Specification (MTS); The Testing and Test Control

[i.9] ETSI ES 202 785: "Methods for Testing and Specification (MTS); The Testing and Test Control

[i.10] ETSI ES 202 782: "Methods for Testing and Specification (MTS); The Testing and Test Control

Notation version 3; TTCN-3 Language Extensions: TTCN-3 Performance and Real Time Testing".

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

Notation version 3; TTCN-3 Language Extensions: TTCN-3 Continuous Signal Support".

For the purposes of the present document, the terms and definitions given in ES 201 873-1 [1], ES 201 873-4 [2],

For the purposes of the present document, the abbreviations given in ES 201 873-1 [1], ES 201 873-4 [2],

ES 201 873-5 [3], ES 201 873-6 [4], Recommendation ITU-T X.290 [5] and the following apply:

The package has no package tag as the choice to use TRI and/or XTRI affects the test adaptor only, but not the test

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, ES 201 873-1 [1] and

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

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

Historically, TTCN has been used to test communication protocols which typically use encoded messages. This has

been reflected in the TRI SA and TCI CD design of TTCN-3 by encoding and decoding messages to and from

bitstrings. However, TTCN-3 also supports signature-based communication for which the transformation of objects into

bitstrings and vice versa is cumbersome. Furthermore, some protocols use also structured messages for which the

Therefore, an alternative API is being defined in this extension package of TTCN-3 along which TTCN-3 values can be

directly passed to/from the SUT. It is defined by redefining the operations in TRI SA and PA as follows.

The SA or PA can in addition provide notifications about unrecoverable error situations by use of the operations

Shall be called whenever an error situation has occurred in the SA with the exception of errors

occurring when processing SA calls initiated by the TE. These errors are reported in the

operation return. The optional cause parameter can be used to provide information in addition

Effect The TE will be notified about an unrecoverable error situation within the SA and may forward

In Parameters message A string value, i.e. the error phrase describing the problem.

Constraint Shall be called whenever an error situation has occurred in the PA with the exception of errors

occurring when processing PA calls initiated by the TE. These errors are reported in the

operation return. The optional cause parameter can be used to provide information in addition

Effect The TE will be notified about an unrecoverable error situation within the PA and may forward

The return status of the triMap operation. The return status indicates the local success (TRI_OK)

Constraints This operation is called by the TE when it executes a TTCN-3 map operation.

Effect The SA can establish a dynamic connection to the SUT for the referenced TSI port.

The triMap operation returns TRI_Error in case a connection could not be established

successfully, TRI_OK otherwise. The operation should return TRI_OK in case no dynamic

The return status of the triUnmap operation. The return status indicates the local success (TRI_OK)

Effect The SA shall close a dynamic connection to the SUT for the referenced TSI port.

The triUnmap operation returns TRI_Error in case a connection could not be closed successfully or

no such connection has been established previously, TRI_OK otherwise. The operation should return

tsiPortId identifier of the test system interface port via which the message is sent to the SUT

Return Value The return status of the triSend operation. The return status indicates the local success (TRI_OK)

Constraints This operation is called by the TE when it executes a TTCN-3 unicast send operation on a component

port, which has been mapped to a TSI port. This operation is called by the TE for all TTCN-3 send

operations if no system component has been specified for a test case, i.e. only a MTC test component

The encoding of sendMessage has to be done in the TE prior to this TRI operation call.

The triSend operation returns TRI_OK in case it has been completed successfully. Otherwise

TRI_Error shall be returned. Notice that the return value TRI_OK does not imply that the SUT has

tsiPortId identifier of the test system interface port via which the message is sent to the SUT

Return Value The return status of the triSendBC operation. The return status indicates the local success

Constraints This operation is called by the TE when it executes a TTCN-3 broadcast send operation on a

component port, which has been mapped to a TSI port. This operation is called by the TE for all

TTCN-3 send operations if no system component has been specified for a test case, i.e. only a MTC

The triSendBC operation returns TRI_OK in case it has been completed successfully. Otherwise

TRI_Error shall be returned. Notice that the return value TRI_OK does not imply that the SUT has

tsiPortId identifier of the test system interface port via which the message is sent to the

The return status of the triSendMC operation. The return status indicates the local success

This operation is called by the TE when it executes a TTCN-3 multicast send operation on a

component port, which has been mapped to a TSI port. This operation is called by the TE for all

TTCN-3 send operations if no system component has been specified for a test case, i.e. only a MTC

The encoding of sendMessage has to be done in the TE prior to this TRI operation call.

The triSendMC operation returns TRI_OK in case it has been completed successfully. Otherwise

TRI_Error shall be returned. Notice that the return value TRI_OK does not imply that the SUT has

In Parameters tsiPortId identifier of the test system interface port via which the message is enqueued

Constraints This operation is called by the SA after it has received a message from the SUT. It can only be used

when tsiPortId has been either previously mapped to a port of componentId or has been referenced in

In the invocation of a triEnqueueMsg operation receivedMessage shall contain an encoded

Effect This operation shall pass the message to the TE indicating the component componentId to which the

In order to interpret unknown values along a type hypothesis, an additional xtriConvert operation is defined. It can be

used in all cases where the type of the incoming value is not known. Please note that typically the value type is known

Return Value Returns the converted value, if the value is of a compatible type as the typeHypothesis, else the

Constraints This operation shall be called whenever the TE has to convert a value. The TE might convert

immediately after reception of the value, or might for performance considerations postpone the

Effect This operation converts a value and returns a value according to the type hypothesis if it matches.

The typeHypothesis determines whether the value can be converted. If not, the distinct null value

In Parameters componentId identifier of the test component issuing the procedure call

tsiPortId identifier of the test system interface port via which the procedure call is sent

parameterList a list of encoded parameters which are part of the indicated signature. The

Return Value The return status of the triCall operation. The return status indicates the local success (TRI_OK)

Constraints This operation is called by the TE when it executes a TTCN-3 unicast call operation on a component

port, which has been mapped to a TSI port. This operation is called by the TE for all TTCN-3 call

operations if no system component has been specified for a test case, i.e. only a MTC test

The procedure parameters are the parameters specified in the TTCN-3 signature template. Their

Effect On invocation of this operation the SA can initiate the procedure call corresponding to the signature

The triCall operation shall return without waiting for the return of the issued procedure call (see

note). This TRI operation returns TRI_OK on successful initiation of the procedure call, TRI_Error

otherwise. No error shall be indicated by the SA in case the value of any out parameter is non-null.

Notice that the return value of this TRI operation does not make any statement about the success or