ETSI ES 202 789-2015 Methods for Testing and Specification (MTS) The Testing and Test Control Notation version 3 TTCN-3 Language Extensions Extended TRI (V1 4 1)《测试方法和规格 (MTS) 试验和试_1.pdf

1、 ETSI ES 202 789 V1.4.1 (2015-06) Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Extended TRI ETSI STANDARD ETSI ETSI ES 202 789 V1.4.1 (2015-06) 2Reference RES/MTS-202789ed141 Keywords testing, TTCN-3 ETSI 650 Route des Luci

2、oles 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 can be downloaded from: http:/www.etsi.org/standa

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

4、 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 may be subject to revision or change of status. In

5、formation on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp 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 Copyright Notific

6、ation 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 an

7、d the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registere

8、d for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI ES 202 789 V1.4.1 (2015-06) 3Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References

9、 5g32.1 Normative references . 5g32.2 Informative references 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Package conformance and compatibility 7g35 Package concepts for the core language . 7g36 Package semantics 7g37 TRI extensions for the package 8g37.0 Intro

10、duction 8g37.1 Changes to clause 5.2 of ETSI ES 201 873-5, Error handling . 8g37.2 Changes to clause 5.5.2 of ETSI ES 201 873-5, Connection handling operations . 9g37.3 Changes to clause 5.5.3 of ETSI ES 201 873-5, Message based communication operations. 10g37.4 Addition to clause 5.5.3 of ETSI ES 2

11、01 873-5, Message based communication operations 12g37.5 Changes to clause 5.5.4 of ETSI ES 201 873-5, Procedure based communication operations 13g37.6 Changes to clause 5.6.3 of ETSI ES 201 873-5, Miscellaneous operations . 21g37.7 Changes to clause 6 of ETSI ES 201 873-5, Java language mapping 22g

12、37.8 Changes to clause 7 of ETSI ES 201 873-5, C language mapping . 24g37.9 Changes to clause 8 of ETSI ES 201 873-5, C+ language mapping 26g37.10 Changes to clause 9 of ETSI ES 201 873-5, C# language mapping . 29g38 TCI extensions for the package 31g3Annex A (informative): Bibliography . 32g3Histor

13、y 33g3ETSI ETSI ES 202 789 V1.4.1 (2015-06) 4Intellectual Property Rights 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 fou

14、nd 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 (http:/ipr.etsi.org). Pursuant to the ETSI IPR Poli

15、cy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI

16、 Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). The use of underline (additional text) and strike through (deleted text) highlights the differences between base document and extended documents. The present document relates to the multi-part s

17、tandard ETSI ES 201 873 covering the Testing and Test Control Notation version 3, as identified below: Part 1: “TTCN-3 Core Language“; Part 4: “TTCN-3 Operational Semantics“; Part 5: “TTCN-3 Runtime Interface (TRI)“; Part 6: “TTCN-3 Control Interface (TCI)“; Part 7: “Using ASN.1 with TTCN-3“; Part 8

18、: “The IDL to TTCN-3 Mapping“; Part 9: “Using XML schema with TTCN-3“; Part 10: “TTCN-3 Documentation Comment Specification“. 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

19、as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI ES 202 789 V1.4.1 (2015-06) 51 Scope The present document defines the Extended TRI package

20、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

21、 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

22、 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 dedicated applications and/or usages of TTCN-3.

23、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 serialized data can be passed directly between the SUT and the T

24、E. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document. 2 References 2.1 No

25、rmative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments)

26、 applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The follow

27、ing referenced documents are necessary for the application of the present document. 1 ETSI ES 201 873-1: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language“. 2 ETSI ES 201 873-4: “Methods for Testing and Specification (MTS); Th

28、e Testing and Test Control Notation version 3; Part 4: TTCN-3 Operational Semantics“. 3 ETSI ES 201 873-5: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)“. 4 ETSI ES 201 873-6: “Methods for Testing and Specificati

29、on (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)“. 5 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 IS

30、O/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. ETSI ETSI ES 202 789 V1.4.1 (2015-06) 62.2 Informative references References are either specific (identified by date of publication and/or edition number

31、or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI ca

32、nnot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 Void. i.2 Void. i.3 ETSI ES 201 873-7: “Methods for Testing and Specification (MTS); The Te

33、sting and Test Control Notation version 3; Part 7: Using ASN.1 with TTCN-3“. i.4 ETSI ES 201 873-8: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 8: The IDL to TTCN-3 Mapping“. i.5 ETSI ES 201 873-9: “Methods for Testing and Specification (MTS);

34、The Testing and Test Control Notation version 3; Part 9: Using XML schema with TTCN-3“. 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 Testi

35、ng 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 Notation version 3; TTCN-3 Language Extensions: Advanced Par

36、ameterization“. i.9 ETSI ES 202 785: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Behaviour Types“. i.10 ETSI ES 202 782: “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-

37、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: Support of interfaces with continuous signals“. 3 Definitions and abbreviations 3.1 Defin

38、itions For the purposes of the present document, the terms and definitions given in ETSI ES 201 873-1 1, ETSI ES 201 873-4 2, ETSI ES 201 873-5 3, ETSI ES 201 873-6 4 and Recommendation ITU-T X.290 5 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI E

39、S 201 873-1 1, ETSI ES 201 873-4 2, ETSI ES 201 873-5 3, ETSI ES 201 873-6 4, Recommendation ITU-T X.290 5 and the following apply: XTRI Extended TRI ETSI ETSI ES 202 789 V1.4.1 (2015-06) 74 Package conformance and compatibility The package has no package tag as the choice to use TRI and/or XTRI aff

40、ects the test adaptor only, but not the test specifications in TTCN-3. 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, ETSI ES 201 873-1 1 and ETSI

41、 ES 201 873-4 2. The package presented in the present document is compatible to: ETSI ES 201 873-1 1 (V4.5.1) ETSI ES 201 873-4 2 (V4.4.1) ETSI ES 201 873-6 4 (V4.5.1) ETSI ES 201 873-7 i.3 (V4.5.1) ETSI ES 201 873-8 i.4 (V4.5.1) ETSI ES 201 873-9 i.5 (V4.5.1) ETSI ES 201 873-10 i.6 (V4.5.1) If late

42、r versions of those parts are available and should be used instead, the compatibility of the package defined in the present document has to be checked individually. The package defined in the present document is also compatible to: ETSI ES 202 784 i.8 (V1.3.1) ETSI ES 202 781 i.7 (V1.2.1) ETSI ES 20

43、2 782 i.10 (V1.2.1) ETSI ES 202 785 i.9 (V1.3.1) ETSI ES 202 786 i.11 (V1.2.1) and can be used together with those packages. If later versions of those packages are available and should be used instead, the compatibility to the package defined in the present document has to be checked individually.

44、5 Package concepts for the core language Not applicable. 6 Package semantics Not applicable. ETSI ETSI ES 202 789 V1.4.1 (2015-06) 87 TRI extensions for the package 7.0 Introduction Historically, TTCN has been used to test communication protocols which typically use encoded messages. This has been r

45、eflected 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 structur

46、ed messages for which the bitstring encoding is not helpful. 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. 7.1 Changes to cla

47、use 5.2 of ETSI ES 201 873-5, Error handling The SA or PA can in addition provide notifications about unrecoverable error situations by use of the operations xtriSAErrorReq and xtriPAErrorReq, respectively. 5.2.1 triSAErrorReq barb2right xtriSAErrorReq Signature void xtriSAErrorReq(in string message

48、, in any cause) In Parameters message A string value, i.e. the error phrase describing the problem. cause (Optional) cause of the problem. Return Value void Constraint Shall be called whenever an error situation has occurred in the SA with the exception of errors occurring when processing SA calls i

49、nitiated by the TE. These errors are reported in the operation return. The optional cause parameter can be used to provide information in addition to the error phrase in message. Effect The TE will be notified about an unrecoverable error situation within the SA and may forward the error indication to the test management. 5.2.2 triPAErrorReq barb2right xtriPAErrorReq Signature void xtriPAErrorReq(in string message, in any cause) In Parameters message A string value, i.e. the error phrase desc