1、 International Telecommunication Union ITU-T Z.144TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2006) SERIES Z: LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS Formal description techniques (FDT) Testing and Test Control Notation (TTCN) Testing and Test Control Notation ve
2、rsion 3 (TTCN-3): Runtime interface (TRI) ITU-T Recommendation Z.144 ITU-T Z-SERIES RECOMMENDATIONS LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS FORMAL DESCRIPTION TECHNIQUES (FDT) Specification and Description Language (SDL) Z.100Z.109 Application of formal description techn
3、iques Z.110Z.119 Message Sequence Chart (MSC) Z.120Z.129 Extended Object Definition Language (eODL) Z.130Z.139 Testing and Test Control Notation (TTCN) Z.140Z.149 User Requirements Notation (URN) Z.150Z.159 PROGRAMMING LANGUAGES CHILL: The ITU-T high level language Z.200Z.209 MAN-MACHINE LANGUAGE Ge
4、neral principles Z.300Z.309 Basic syntax and dialogue procedures Z.310Z.319 Extended MML for visual display terminals Z.320Z.329 Specification of the man-machine interface Z.330Z.349 Data-oriented human-machine interfaces Z.350Z.359 Human-machine interfaces for the management of telecommunications n
5、etworks Z.360Z.379 QUALITY Quality of telecommunication software Z.400Z.409 Quality aspects of protocol-related Recommendations Z.450Z.459 METHODS Methods for validation and testing Z.500Z.519 MIDDLEWARE Distributed processing environment Z.600Z.609 For further details, please refer to the list of I
6、TU-T Recommendations. ITU-T Rec. Z.144 (03/2006) i ITU-T Recommendation Z.144 Testing and Test Control Notation version 3 (TTCN-3): Runtime interface (TRI) Summary This Recommendation provides the specification of the runtime interface for TTCN-3 (Testing and Test Control Notation 3) test system imp
7、lementations. The TTCN-3 Runtime Interface provides the recommended adaptation for timing and communication of a test system to a particular processing platform and the system under test, respectively. This Recommendation defines the interface as a set of operations independent of target language. T
8、he interface is defined to be compatible with ITU-T Rec. Z.140. This Recommendation uses the CORBA Interface Definition Language (IDL) to specify the TRI completely. Clauses 6 and 7 specify language mappings of the abstract specification to the target languages Java and ANSI-C. A summary of the IDL-
9、based interface specification is provided in Annex A. Source ITU-T Recommendation Z.144 was approved on 16 March 2006 by ITU-T Study Group 17 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. Z.144 (03/2006) FOREWORD The International Telecommunication Union (ITU) is the United
10、 Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommu
11、nications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the proce
12、dure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telec
13、ommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of thes
14、e mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU
15、draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU member
16、s or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not
17、represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2006 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Z.144 (03/2006) iii CONTENTS Page 1 Scop
18、e . 1 1.1 Compliance 1 2 References 1 3 Definitions and abbreviations 1 3.1 Definitions. 1 3.2 Abbreviations. 2 4 General structure of a TTCN-3 test system 3 4.1 Entities in a TTCN-3 test system 3 4.2 Interfaces in a TTCN-3 test system. 5 4.3 Execution requirements for a TTCN-3 test system . 6 5 TTC
19、N-3 Runtime Interface and operations 6 5.1 Overview of the TRI 6 5.2 Error handling 7 5.3 Data interface. 8 5.4 Operation descriptions . 9 5.5 Communication interface operations . 10 5.6 Platform interface operations. 20 6 Java language mapping 23 6.1 Introduction . 23 6.2 Names and scopes . 23 6.3
20、Type mapping 23 6.4 Constants. 30 6.5 Mapping of interfaces 31 6.6 Optional parameters. 33 6.7 TRI initialization. 34 6.8 Error handling 34 7 ANSI-C language mapping. 34 7.1 Introduction . 34 7.2 Names and scopes . 34 7.3 Memory management 38 7.4 Error handling 38 8 Use scenarios. 38 8.1 First scena
21、rio 39 8.2 Second scenario 41 8.3 Third scenario 43 Annex A (normative) IDL Summary . 45 BIBLIOGRAPHY 48 iv ITU-T Rec. Z.144 (03/2006) Introduction This Recommendation consists of two distinct parts, the first part describing the structure of a TTCN-3 test system implementation and the second part p
22、resenting 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 Adapter (SA); and Platform Adapter (PA). In addition, the interaction between these entities, i.e., the
23、 corresponding interfaces, is defined. The second part of this Recommendation 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
24、specification defines 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. ITU-T Rec. Z.144 (03/2006) 1 ITU-T Rec
25、ommendation Z.144 Testing and Test Control Notation version 3 (TTCN-3): Runtime interface (TRI) 1 Scope This Recommendation 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 commu
26、nication of a test system to a particular processing platform and the system under test, respectively. This Recommendation 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 reference below). This Recom
27、mendation uses the CORBA Interface Definition Language (IDL) to specify the TRI completely. Clauses 6 and 7 present language mappings for this abstract specification to the target languages Java and ANSI-C. A summary of the IDL-based interface specification is provided in Annex A. 1.1 Compliance The
28、 requirement for a TTCN-3 test system to be TRI compliant is to adhere to the interface specification stated in this Recommendation as well as to one of the target language mappings included. EXAMPLE: If a vendor supports Java, the TRI operation calls and implementations, which are part of the TTCN-
29、3 executable, must comply with the IDL to Java mapping specified in this Recommendation. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editi
30、ons indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid
31、 ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. 1 ITU-T Recommendation X.290 (1995), OSI conformance testing methodology and framework for protocol Recommendations for I
32、TU-T applications General concepts. ISO/IEC 9646-1:1994, Information technology Open Systems Interconnection Conformance testing methodology and framework Part 1: General concepts. 2 ITU-T Recommendation Z.140 (2006), Testing and Test Control Notation version 3 (TTCN-3): Core language. 3 ITU-T Recom
33、mendation X.292 (2002), OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications The Tree and Tabular Combined Notation (TTCN). ISO/IEC 9646-3:1998, Information technology Open Systems Interconnection Conformance testing methodology and framework Part 3:
34、The Tree and Tabular Combined Notation (TTCN). 4 ITU-T Recommendation Z.143 (2006), Testing and Test Control Notation version 3 (TTCN-3): Operational Semantics. 3 Definitions and abbreviations 3.1 Definitions For the purposes of this Recommendation, the terms and definitions given in ITU-T Rec. Z.14
35、0 2 and the following apply: 3.1.1 abstract test suite (ATS): See ITU-T Rec. X.290 1. 3.1.2 communication port: Abstract mechanism facilitating communication between test components. NOTE A communication port is modelled as a FIFO queue in the receiving direction. Ports can be message-based, procedu
36、re-based or a mixture of the two. 2 ITU-T Rec. Z.144 (03/2006) 3.1.3 executable test suite (ETS): See ITU-T Rec. X.290 1. 3.1.4 explicit timer: Timer that is declared in a TTCN-3 ATS and that can be accessed through TTCN-3 timer operations. 3.1.5 implementation extra information for testing (IXIT):
37、See ITU-T Rec. X.290 1. 3.1.6 implicit timer: System timer that is created by the TTCN-3 executable to guard a TTCN-3 call or execute operation. NOTE Implicit timers are not accessible to the TTCN-3 user. 3.1.7 platform adapter (PA): Entity that adapts the TTCN-3 executable to a particular execution
38、 platform. NOTE The Platform Adapter creates a single notion of time for a TTCN-3 test system, and implements external functions as well as explicit and implicit timers. 3.1.8 SUT adapter (SA): Entity that adapts the TTCN-3 communication operations with the SUT based on an abstract test system inter
39、face and implements the real test system interface. 3.1.9 system under test (SUT): See ITU-T Rec. X.290 1. NOTE All types are known at compile time, i.e., are statically bound. 3.1.10 test case: See ITU-T Rec. X.290 1. 3.1.11 test event: Either sent or received test data (message or procedure call)
40、on a communication port that is part of the test system interface. 3.1.12 test management (TM): Entity that provides a user interface and administers the TTCN-3 test system. 3.1.13 test system: See ITU-T Rec. X.290 1. 3.1.14 test system interface: Test component that provides a mapping of the ports
41、available in the (abstract) TTCN-3 test system to those offered by a real test system. 3.1.15 timer identification (TID): Unique identification for explicit or implicit timer instances that is generated by the TTCN-3 Executable. 3.1.16 TTCN-3 control interface (TCI): Currently a proprietary interfac
42、e that specifies the interaction between test management and TTCN-3 executable in a test system. 3.1.17 TTCN-3 executable (TE): Part of a test system that deals with interpretation or execution of a TTCN-3 ETS. 3.1.18 TTCN-3 runtime interface (TRI): Interface that defines the interaction of the TTCN
43、-3 executable with the SUT and platform adapter in a test system. 3.2 Abbreviations This Recommendation uses the following abbreviations: ATS Abstract Test Suite CH Component Handler ECD External CoDecs EDS Encoding/Decoding System ETS Executable Test Suite IDL Interface Definition Language IXIT Imp
44、lementation eXtra Information for Testing MSC Message Sequence Chart MTC Main Test Component OMG Object Management Group PA Platform Adapter SA SUT Adapter SUT System Under Test T3RTS TTCN-3 Runtime System TC Test Control TCI TTCN-3 Control Interface ITU-T Rec. Z.144 (03/2006) 3 TE TTCN-3 Executable
45、 TID Timer IDentification TL Test Logging TM Test Management TRI TTCN-3 Runtime Interface TSI Test System Interface TTCN Testing and Test Control Notation TTCN-3 Tree and Tabular Combined Notation version 3 4 General structure of a TTCN-3 test system A TTCN-3 test system can be thought of conceptual
46、ly as a set of interacting entities where each entity corresponds to a particular aspect of functionality in a test system implementation. These entities manage test execution, interpreting or executing compiled TTCN-3 code, realize proper communication with the SUT, implement external functions, an
47、d handle timer operations. (See Figure 1.) Figure 1/Z.144 General structure of a TTCN-3 test system 4.1 Entities in a TTCN-3 test system The structure of a TTCN-3 test system implementation is illustrated in Figure 1. It should be noted that the further refinement of TM into smaller entities, as sho
48、wn in Figure 1 and used in the following clauses of this Recommendation, is purely an aid to define TTCN-3 test system interfaces. The part of the test system that deals with interpretation and execution of TTCN-3 modules, i.e., the Executable Test Suite (ETS), is part of the TTCN-3 Executable (TE).
49、 This corresponds either to the executable code produced by a TTCN-3 compiler or a TTCN-3 interpreter in a test system implementation. It is assumed that a test system implementation includes the ETS as derived from a TTCN-3 ATS. The remaining part of the TTCN-3 test system, which deals with any aspects that cannot be concluded from information being present in the original ATS alone, can be decomposed into Test Management (TM), SUT Adapter (SA), and Platform Adapter (PA) entities. In general, these entities cover
