1、 International Telecommunication Union ITU-T Z.162TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2007) 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 tabular presentation format (TFT) ITU-T Recommendation Z.162 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 descripti
3、on techniques Z.110Z.119 Message Sequence Chart (MSC) Z.120Z.129 Extended Object Definition Language (eODL) Z.130Z.139 User Requirements Notation (URN) Z.150Z.159 Testing and Test Control Notation (TTCN) Z.160Z.199 PROGRAMMING LANGUAGES CHILL: The ITU-T high level language Z.200Z.209 MAN-MACHINE LAN
4、GUAGE General 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 telecommunic
5、ations networks 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 Processing environment architectures Z.600Z.609 For further details, please refer to the
6、 list of ITU-T Recommendations. ITU-T Rec. Z.162 (11/2007) i ITU-T Recommendation Z.162 Testing and Test Control Notation version 3: TTCN-3 tabular presentation format (TFT) Summary ITU-T Recommendation Z.162 defines TFT, the Tabular Format for TTCN-3. TFT is the tabular presentation format for TTCN
7、-3 (Testing and Test Control Notation 3) Core Language defined in ITU-T Z.161. It is similar in appearance and functionality to TTCN-2 defined in ITU-T Rec. X.292 for conformance testing. The tabular format provides an alternative way of displaying the core language as well as emphasizing those aspe
8、cts that are particular to the requirements of a standardized conformance test suite. While the core language may be used independently of the tabular presentation format, the tabular format cannot be used without the core language. Use and implementation of the tabular presentation format shall be
9、done on the basis of the core language. This Recommendation defines proformas, syntax mappings, additional static semantics, operational semantic restrictions, display and other attributes. Together, these characteristics form the tabular presentation format. TFT inherits all the essential propertie
10、s of the Core Language and is intended for specification of test suites that are independent of platforms, test methods, protocol layers and protocols. TTCN-3 can be used for specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are p
11、rotocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA-based platforms and APIs. The specification of test suites for physical layer protocols is outside the scope of this Recommendation. Source ITU-T Recommenda
12、tion Z.162 was approved on 13 November 2007 by ITU-T Study Group 17 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. Z.162 (11/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, informatio
13、n and communication technologies (ICTs). 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 telecommunications on a worldwid
14、e 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 procedure laid down in WTSA
15、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 telecommunication administra
16、tion 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 these mandatory provisions
17、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 draws attention to the
18、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 members or others outside of
19、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, implementers are cautioned that this may not represent the latest in
20、formation and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 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.162 (11/2007) iii CONTENTS Pa
21、ge 1 Scope 1 2 References. 1 3 Abbreviations 1 4 Introduction 1 5 Conventions 2 5.1 Syntactic metanotation . 2 5.2 Specification text 3 5.3 Proformas . 3 5.4 Core language. 3 5.5 General mapping rules 3 6 Proformas 4 6.1 Test Suite Control. 4 6.2 Test Suite Parameters . 6 6.3 Module Imports 7 6.4 Si
22、mple Types 9 6.5 Structured Types. 10 6.6 SequenceOf types . 11 6.7 Enumerated Type 12 6.8 Port Types. 14 6.9 Component Types. 15 6.10 Constants 17 6.11 Signature. 18 6.12 Simple Templates . 19 6.13 Structured Template . 20 6.14 Function 22 6.15 Altstep. 24 6.16 Testcase 26 7 BNF productions. 29 ITU
23、-T Rec. Z.162 (11/2007) 1 ITU-T Recommendation Z.162 Testing and Test Control Notation version 3: TTCN-3 tabular presentation format (TFT) 1 Scope This Recommendation defines the tabular presentation format of TTCN Version 3 (or TTCN-3). This Recommendation is based on the TTCN-3 core language defin
24、ed in ITU-T Z.161. The specification of other formats is outside the scope of 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,
25、 the editions 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 curre
26、ntly valid 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. ITU-T Z.161 ITU-T Recommendation Z.161 (2007), Testing and Test Control Notation version 3: TTCN-3 core languag
27、e. ITU-T Z.164 ITU-T Recommendation Z.164 (2007), Testing and Test Control Notation version 3: TTCN-3 operational semantics. 3 Abbreviations This Recommendation uses the following abbreviations and acronyms: ASN.1 Abstract Syntax Notation One ATS Abstract Test Suite BNF Backus-Nauer Form MTC Master
28、Test Component PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing TFT Tabular presentation Format for TTCN-3 TTCN Testing and Test Control Notation 4 Introduction The Tabular presentation Format for TTCN-3 (TFT) is a graphical format that i
29、s similar in appearance and functionality to earlier versions of TTCN, which are conformance testing oriented. The core language of TTCN-3 is defined in ITU-T Z.161 and provides a full text-based syntax, static semantics as well as defining the use of the language with ASN.1. The operational semanti
30、cs are defined in ITU-T Z.164. The tabular format provides an alternative way of displaying the core language as well as emphasizing those aspects that are particular to the requirements of a standardized conformance test suite. 2 ITU-T Rec. Z.162 (11/2007) Figure 1 Users view of the core language a
31、nd the various presentation formats The core language may be used independently of the tabular presentation format. However, the tabular format cannot be used without the core language. Use and implementation of the tabular presentation format shall be done on the basis of the core language. This Re
32、commendation defines the: a) proformas; b) syntax mappings; c) additional static semantics; d) operational semantic restrictions; e) display and other attributes. Together these characteristics form the tabular presentation format. 5 Conventions This clause defines the conventions, which have been u
33、sed when defining the TTCN proformas and the TTCN core language grammar. 5.1 Syntactic metanotation Table 1 defines the metanotation used to specify the extended BNF grammar for TTCN (henceforth called BNF). Table 1 The TTCN.MP syntactic metanotation := is defined to be abc xyz abc followed by xyz |
34、 alternative abc 0 or 1 instances of abc abc 0 or more instances of abc abc+ 1 or more instances of abc ( . ) textual grouping abc the non-terminal symbol abc abc a terminal symbol abc “abc“ a terminal symbol abc ITU-T Rec. Z.162 (11/2007) 3 The BNF productions are defined in Annex A of ITU-T Z.161.
35、 5.2 Specification text a) Bold text shall be used for references to proforma fields. b) Italics text shall be used for references to the TTCN-3 core language BNF productions. c) Bold courier new text shall be used for core language keywords. 5.3 Proformas a) Bold text shall appear verbatim in each
36、actual table in a TTCN-3 module. b) Italics text shall not appear verbatim in a TTCN-3 module. This font is used to indicate that actual text shall be substituted for the italicized symbol. Syntax requirements for the actual text can be found either following the definition of the proforma or in the
37、 TTCN-3 core language BNF. Square brackets before and after the Italics text indicates that inclusion of the text into the given field of the proforma is optional. 5.4 Core language a) Bold text of characters in quotes (e.g., ) is used for reserved keywords and terminals in the core language. b) Ita
38、lics text shall not appear verbatim in a TTCN-3 module. This font is used to indicate that actual text shall be substituted for the italicized symbol. Syntax requirements for the actual text can be found either following the definition of the proforma or in the TTCN-3 core language BNF. c) The “.“ n
39、otation is a place holder for any arbitrary contents that is not explicitly shown. 5.5 General mapping rules The mapping between the tabular presentation format and the TTCN-3 core language consists of a set of transformations. For every syntactical element within each proforma there is an associate
40、d transformation. The transformations make it also possible to transform any core language module into a tabular representation. These transformations fall into two classes. The first class directly converts between a tabular element and a core language construct with the same meaning. The second cl
41、ass converts between a tabular element and an associated core language construct, which has no meaning at the core language level. A typical example for the first class of transformations would be an identifier field. This field can be directly transformed from tabular to the core language and retai
42、ns its meaning i.e., identifying same language element. The second class of transformations is typically some form of comment or directive as to how a language element should be displayed in the presentation format. These elements have no direct meaning in the core language and are expressed using t
43、he WithStatement. The syntax and semantics specified in this Recommendation are specific to the ETSI tabular presentation format. In order to unambiguously identify within the core language which presentation format is being used the following special display statement shall be specified as the firs
44、t display statement associated with the TTCN-3 core language module: 4 ITU-T Rec. Z.162 (11/2007) 1: 2: 3: 4: 5: 6: 7: module TTCN3ModuleId “ . “ with “ display “ “presentation format“ “:=“ “ETSI Tabular version“ MajorVersion “.“ MinorVersion “ “;“ . “ NOTE All With Statements associated with a give
45、n proforma should be grouped together in a contiguous list. The Group fields in the proformas are never translated into WithStatements but are derived from the actual group structure of the module specification. 6 Proformas 6.1 Test Suite Control Test Suite Control Module Name TTCN3ModuleId Version
46、TabFreeText Date TabFreeText Base Standard Ref TabFreeText Test Standard Ref TabFreeText PICS Ref TabFreeText PIXIT Ref TabFreeText Test Method(s) TabFreeText Encoding TabFreeText Comments TabFreeText Local Def Name Type Initial Value Comments VarConstOrTimerIdentifier . ConstTypeOrTimer . Expressio
47、n . TabFreeText . Behaviour ModuleControlBody Detailed Comments TabFreeText Figure 2 Test Suite Control proforma 6.1.1 Mapping The Test Suite Control proforma is translated into three parts. The first part consists of the header fields and the Detailed Comments field, which are converted to display
48、attributes within the WithStatement associated with the overall TTCN-3 module. The Module Name field is mapped to the module identifier. The second part consists of local constants, variables and timers defined in the control part. These definitions can occur anywhere in the control part of the core
49、 language, but for the proforma they are separated from the rest of the module control body and displayed in a separate table. The order of the definitions shall be preserved, since the definitions can depend on each other. The Type column shall be set to the keyword timer for all timers and to the constant type preceded by the keyword const for all constants. The Comments fields of the local definitions table are converted to display attributes within the WithStatement associated with the control p
