ETSI ES 201 873-5-2017 Methods for Testing and Specification (MTS) The Testing and Test Control Notation version 3 Part 5 TTCN-3 Runtime Interface (TRI) (V4 8 1).pdf

《ETSI ES 201 873-5-2017 Methods for Testing and Specification (MTS) The Testing and Test Control Notation version 3 Part 5 TTCN-3 Runtime Interface (TRI) (V4 8 1).pdf》由会员分享，可在线阅读，更多相关《ETSI ES 201 873-5-2017 Methods for Testing and Specification (MTS) The Testing and Test Control Notation version 3 Part 5 TTCN-3 Runtime Interface (TRI) (V4 8 1).pdf（93页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI ES 201 873-5 V4.8.1 (2017-05) Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI) ETSI STANDARD ETSI ETSI ES 201 873-5 V4.8.1 (2017-05)2 Reference RES/MTS-201873-5 T3ed481TRI Keywords interface, methodology, runti

2、me, 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 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document c

3、an 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

4、any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document ma

5、y 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.e

6、tsi.org/People/CommiteeSupportStaff.aspx 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 w

7、ithout the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its

8、 Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI ES 201 873-5 V4.8.1

9、(2017-05)3 Contents Intellectual Property Rights 8g3Foreword . 8g3Modal verbs terminology 8g3Introduction 8g31 Scope 9g31.1 Scope of the present document . 9g31.2 Compliance. 9g32 References 9g32.1 Normative references . 9g32.2 Informative references 10g33 Definitions and abbreviations . 10g33.1 Def

10、initions 10g33.2 Abbreviations . 11g34 General Structure of a TTCN-3 Test System . 12g34.1 Entities in a TTCN-3 test system 12g34.1.0 Types of entities 12g34.1.1 Test Management and Control (TMC) 12g34.1.1.0 Test Management and Control Entities . 12g34.1.1.1 Test Management (TM) 13g34.1.1.2 Test Log

11、ging (TL) . 13g34.1.1.3 Coding and Decoding (CD) 13g34.1.1.4 Component Handling (CH) . 13g34.1.2 TTCN-3 Executable (TE) . 13g34.1.2.0 TTCN-3 Executable Entity . 13g34.1.2.1 Executable Test Suite (ETS) . 13g34.1.2.2 TTCN-3 RunTime System (T3RTS) . 13g34.1.2.3 Encoding/Decoding System (EDS) . 14g34.1.

12、2.4 Timers in the TTCN-3 Executable 14g34.1.3 SUT Adaptor (SA) 14g34.1.4 Platform Adaptor (PA) 14g34.2 Interfaces in a TTCN-3 Test System 15g34.3 Execution requirements for a TTCN-3 test system 15g35 TTCN-3 Runtime Interface and operations 15g35.1 Overview of the TRI. 15g35.1.0 Sub-interfaces . 15g3

13、5.1.1 The triCommunication Interface . 16g35.1.2 The triPlatform Interface 16g35.1.3 Correlation between TTCN-3 and TRI Operation Invocations . 16g35.2 Error handling 17g35.2.0 Basic rules . 17g35.2.1 triSAErrorReq (SA TE) . 18g35.2.2 triPAErrorReq (PA TE) . 18g35.3 Data interface . 18g35.3.0 Basic

14、rules . 18g35.3.1 Connection 18g35.3.2 Communication . 19g35.3.3 Timer 20g35.3.4 Miscellaneous . 20g35.4 Operation descriptions 20g35.5 Communication interface operations 21g35.5.1 triSAReset (TE SA) . 21g35.5.2 Connection handling operations . 21g35.5.2.1 triExecuteTestCase (TE SA) 21g3ETSI ETSI ES

15、 201 873-5 V4.8.1 (2017-05)4 5.5.2.2 triMap (TE SA) 21g35.5.2.3 triMapParam (TE SA) 22g35.5.2.4 triUnmap (TE SA) 22g35.5.2.5 triUnmapParam (TE SA) 23g35.5.2.6 triEndTestCase (TE SA) . 23g35.5.3 Message based communication operations . 24g35.5.3.1 triSend (TE SA) 24g35.5.3.2 triSendBC (TE SA) 24g35.5

16、.3.3 triSendMC (TE SA) . 25g35.5.3.4 triEnqueueMsg (SA TE) . 25g35.5.4 Procedure based communication operations . 26g35.5.4.1 triCall (TE SA) . 26g35.5.4.2 triCallBC (TE SA) 27g35.5.4.3 triCallMC (TE SA) . 28g35.5.4.4 triReply (TE SA) 29g35.5.4.5 triReplyBC (TE SA) . 30g35.5.4.6 triReplyMC (TE SA) 3

17、1g35.5.4.7 triRaise (TE SA) . 31g35.5.4.8 triRaiseBC (TE SA) . 32g35.5.4.9 triRaiseMC (TE SA) 32g35.5.4.10 triEnqueueCall (SA TE) . 33g35.5.4.11 triEnqueueReply (SA TE) 33g35.5.4.12 triEnqueueException (SA TE) . 34g35.5.5 Miscellaneous operations 34g35.5.5.1 triSUTactionInformal (TE SA) 34g35.6 Plat

18、form interface operations . 34g35.6.1 triPAReset (TE PA) . 34g35.6.2 Timer operations . 35g35.6.2.1 triStartTimer (TE PA) 35g35.6.2.2 triStopTimer (TE PA). 35g35.6.2.3 triReadTimer (TE PA) 35g35.6.2.4 triTimerRunning (TE PA) 36g35.6.2.5 triTimeout (PA TE) 36g35.6.3 Miscellaneous operations 37g35.6.3

19、.1 triExternalFunction (TE PA) 37g35.6.3.2 triSelf (PA TE) . 37g35.6.3.3 triRnd (PA TE) . 37g36 JavaTMlanguage mapping . 38g36.1 Introduction 38g36.2 Names and scopes 38g36.2.1 Names . 38g36.2.2 Scopes. 38g36.3 Type mapping . 38g36.3.1 Basic type mapping . 38g36.3.1.0 IDL type mapping . 38g36.3.1.1

20、Boolean . 39g36.3.1.2 String . 39g36.3.2 Structured type mapping . 39g36.3.2.0 Mapping rules . 39g36.3.2.1 TriPortIdType 39g36.3.2.2 TriPortIdListType . 40g36.3.2.3 TriComponentIdType 40g36.3.2.4 TriComponentIdListType . 41g36.3.2.5 TriMessageType 41g36.3.2.6 TriAddressType 42g36.3.2.7 TriAddressLis

21、tType 42g36.3.2.8 TriSignatureIdType. 43g36.3.2.9 TriParameterType . 43g36.3.2.10 TriParameterPassingModeType 44g3ETSI ETSI ES 201 873-5 V4.8.1 (2017-05)5 6.3.2.11 TriParameterListType . 44g36.3.2.12 TriExceptionType . 45g36.3.2.13 TriTimerIdType 45g36.3.2.14 TriTimerDurationType 45g36.3.2.15 TriFun

22、ctionIdType 46g36.3.2.16 TriTestCaseIdType 46g36.3.2.17 TriActionTemplateType 46g36.3.2.18 TriStatusType 47g36.4 Constants 47g36.5 Mapping of interfaces . 48g36.5.0 Basic rules . 48g36.5.1 Out and InOut Parameter Passing Mode . 48g36.5.2 triCommunication - Interface 48g36.5.2.0 Introduction . 48g36.

23、5.2.1 triCommunicationSA 48g36.5.2.2 triCommunicationTE. 49g36.5.3 triPlatform - Interface . 50g36.5.3.0 Introduction . 50g36.5.3.1 TriPlatformPA . 50g36.5.3.2 TriPlatformTE . 51g36.6 Optional parameters . 51g36.7 TRI initialization 51g37 ANSI C language mapping. 51g37.1 Introduction 51g37.2 Names a

24、nd scopes 51g37.2.0 Naming rules. 51g37.2.1 Abstract type mapping 52g37.2.2 ANSI C type definitions . 53g37.2.3 IDL type mapping . 53g37.2.4 TRI operation mapping . 53g37.3 Memory management . 56g38 C+ language mapping 56g38.1 Introduction 56g38.2 Names and scopes 56g38.3 Memory management . 56g38.4

25、 Void 56g38.5 Type mapping . 56g38.5.0 Basic rules . 56g38.5.1 Encapsulated C+ types 56g38.5.2 Abstract data types 57g38.5.2.1 QualifiedName 57g38.5.2.2 TriAddress . 57g38.5.2.3 TriAddressList 58g38.5.2.4 TriComponentId 59g38.5.2.5 TriComponentIdList 59g38.5.2.6 TriException 60g38.5.2.7 TriFunctionI

26、d 61g38.5.2.8 TriMessage 61g38.5.2.9 TriParameter 62g38.5.2.10 TriParameterList . 62g38.5.2.11 TriParameterPassingMode 63g38.5.2.12 TriPortId 63g38.5.2.13 TriPortIdList 64g38.5.2.14 TriSignatureId . 65g38.5.2.15 TriStatus 65g38.5.2.16 TriTestCaseId 65g38.5.2.17 TriTimerDuration 66g38.5.2.18 TriTimer

27、Id . 66g38.6 Mapping of interfaces . 67g38.6.1 TriCommunicationSA . 67g3ETSI ETSI ES 201 873-5 V4.8.1 (2017-05)6 8.6.2 TriCommunicationTE . 68g38.6.3 TriPlatformPA 69g38.6.4 TriPlatformTE . 69g39 C# language mapping . 70g39.1 Introduction 70g39.2 Names and scopes 70g39.2.1 Names . 70g39.2.2 Scopes.

28、70g39.3 Null value mapping 70g39.4 Type mapping . 70g39.4.1 Basic type mapping . 70g39.4.1.0 IDL type mapping . 70g39.4.1.1 Boolean . 71g39.4.1.2 String . 71g39.4.2 Structured type mapping . 71g39.4.2.0 Mapping rules . 71g39.4.2.1 IQualifiedName. 71g39.4.2.2 TriPortIdType 71g39.4.2.3 TriPortIdListTy

29、pe . 72g39.4.2.4 TriComponentIdType 72g39.4.2.5 TriComponentIdListType . 73g39.4.2.6 TriMessageType 73g39.4.2.7 TriAddressType 74g39.4.2.8 TriAddressListType 74g39.4.2.9 TriSignatureIdType. 75g39.4.2.10 TriParameterPassingModeType 75g39.4.2.11 TriParameterType . 75g39.4.2.12 TriParameterListType . 7

30、5g39.4.2.13 TriExceptionType . 76g39.4.2.14 TriTimerIdType 76g39.4.2.15 TriTimerDurationType 77g39.4.2.16 TriFunctionIdType 77g39.4.2.17 TriTestCaseIdType 77g39.4.2.18 TriStatusType 77g39.5 Mapping of interfaces . 77g39.5.0 Basic rules . 77g39.5.1 Out and inout parameter passing mode . 78g39.5.2 tri

31、Communication interface 78g39.5.2.0 Introduction . 78g39.5.2.1 ITriCommunicationSA 78g39.5.2.2 ITriCommunicationTE 79g39.5.2.3 ITriPlatformPA . 80g39.5.2.4 ITriPlatformTE 80g39.6 Optional parameters . 80g3Annex A (normative): IDL Summary 81g3Annex B (informative): Use scenarios 85g3B.0 Introduction

32、85g3B.1 First scenario 86g3B.1.0 Use case 86g3B.1.1 TTCN-3 fragment . 86g3B.1.2 Message sequence chart . 87g3B.2 Second scenario 88g3B.2.0 Use case 88g3B.2.1 TTCN-3 fragment . 88g3B.2.2 Message sequence chart . 89g3B.3 Third scenario . 90g3B.3.0 Use case 90g3ETSI ETSI ES 201 873-5 V4.8.1 (2017-05)7

33、B.3.1 TTCN-3 fragment . 90g3B.3.2 Message sequence chart . 91g3Annex C (informative): Bibliography . 92g3History 93g3ETSI ETSI ES 201 873-5 V4.8.1 (2017-05)8 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information p

34、ertaining 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 Sec

35、retariat. 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

36、 on the ETSI Web server) which are, or may be, or may become, essential to the present document. 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

37、 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 expressio

38、n 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

39、 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 interf

40、aces, is defined. The second part of the present document specifies the TTCN-3 Runtime Interface (TRI). The interface is defined in terms of operations, which are implemented as part of one entity and called by other entities of the test system. For each operation, the interface specification define

41、s associated data structures, the intended effect on the test system and any constraints on the usage of the operation. Note that this interface specification only defines interactions between the TSI and the SUT as well as timer operations. ETSI ETSI ES 201 873-5 V4.8.1 (2017-05)9 1 Scope 1.1 Scope

42、 of the present document 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 u

43、nder 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

44、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: JavaTMis the trade name of a programming language developed by Oracle Corp

45、oration. 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. 1.2 Compliance The requirement for

46、a TTCN-3 test system to be TRI compliant is to adhere to the interface specification stated in the present document as well as to one of the target language mappings included. EXAMPLE: If a vendor supports JavaTM, the TRI operation calls and implementations, which are part of the TTCN-3 executable,

47、have to comply with the IDL to JavaTMmapping specified in 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. F

48、or 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 cl

49、ause 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 Recommendation ITU-T X.290: “OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications - General concepts“. NOTE: The corresponding ISO/IEC standard is ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framewor