1、- -_ CEPT T/A*07-02*E 8b 2326434 0002813 2 _- _ - - - Recommendation T/A 07-02 (Odense 1986) TEST PROCEDURES FOR TELETEX Recommendation proposed by Working Group T/WG 10 “Data communications” (CD) Text of the Recomrneiidation adopted by the “TelecommttticntioIts” Commission : “The Conference of Euro
2、pean Posts and Telecommunications Administrations, considering - that WG/TD has studied under the auspices of Question TDI: Specification for equipment to be installed in customers premises as part of a public data network in order to attain functional and equipment harmonisation, recommends - that
3、the attached specification of engineering requirements for Teletex Testing be taken into account by all CEPT Administrations.” Administrations are free to stipulate additional requirements and also which of the optional requirements, if any, are to be provided. Note: It should be noted that this Rec
4、ommendation may be revised from time to time. O Edition of November 30, 1987 TIA 07-02 E Page 2 Table of Contents 1. INTRODUCTION, . 2 1.1. Scope . 2 1.2. Use of standardised test procedures 2 2. TEST PROCEDURES . 3 2.2. Transport layer (T.70) 3 2.3. Session and Presentationlayer (T.62) . 3 2.4. Tel
5、etex Application Service Tesf Schedule . 3 r 1.3. Protocol description , . , , , , , , , , , , , , , , , , , . . , I ,_ , , , , , , , , , , , 2 2.1. Network dependent layers (for further study) 3. 4. INTERWORKING (for further study) PERFORMANCE TESTING (for further study) Annex 1. Test procedures fo
6、r Transport layer Annex 2. Test procedures for the Session layer Annex 3. Teletex Application service test schedule Annex 4. Teletex Test text 1. INTRODUCTION 1.1. Scope This Recommendation describes procedures (e.g. Test tables, test text) for testing Teletex implementations and proposes that they
7、be accepted as a basis for standardisation to achieve an adequate level of interna- tional compatibility between Teletex terminals. The end-to-end nature of the Teletex protocol, where, at least at the transport level and above, two terminals are in direct communication with one another, indicates t
8、he importance of such harmonisation of test procedures for the success of Teletex. It should be noted that some administrations have defined additional requirements that are not covered by these tests. 1.2. Use of Standardised Test Procedures The test procedures are specified in such a way that they
9、 can be used for a variety of purposes and by a number of different parties. Thus the test procedures may be applied to a Teletex implementation by any of the following: 1. First Party: the implementor or manufacturer. 2. Second Party: the purchaser or user of the Teletex implementation. 3. Third Pa
10、rty: someone other than first or second party, e.g. an independent body (Le. an administra- tion). The use of the test procedures by each party is called first party testing, second party testing and third party testing respectively. 1.3. Protocol description The Teletex network-independent control
11、procedures are laid down within CCITT-Recommendations T.60, T.62 and T.70 with a plain text description of each (including their interactions). Presently, these descrip- tions are open to different interpretations. Teletex is to be used in an open environment with different implementations able to c
12、ommunicate with each other - in order for this to occur each implementations ability to operate under certain conditions must be tested. Protocol conformance testing examines the conformance of an implementation to the protocol specification. This conformance testing is achieved by examining how the
13、 protocol implementation responds to certain events, However, the Protocol conformance testing is highly complex and therefore it is extremely difficult for it to be exhaustive. For comprehensive protocol conformance testing, rigorous and unambiguous protocol definitions are required. Such formal de
14、scriptions are partially provided by state tables and state diagrams. Edition of November 30, 1987 2. 2.1. 2.2. 2.3. 2.4. TIA 07-02 E Page 3 Generally, description techniques use the text descriptions including the state tables and state diagrams, and it is the translation of these descriptions whic
15、h lead to a basis for a hierarchical structure of systematic, measureable and repeatable tests. TEST PROCEDURES Owing to the compleqity of designing test sequences the technique of repeated refinement has been applied to establish a hierarchical structure of individually manageable tests. The rst di
16、vision or refinement was naturally the individual layer of the Teletex protocol (physical, link, network, transport, session presentation and application). The tests in each layer are organised according to the state tables of the protocol. The testing method thus falls into the main category of sta
17、te event exploration. For each accessible state of the protocol every identifiable event is tested at least one. The tests proposed in this Recommendation are mainly in the form of test tables, they cover static test of the peer-to-peer Teletex protocols, At the moment priority given to has been the
18、 Teletex service. Work is required to extend the tests to cover the interworking of the diflerent layers, and the negotiation of other services using parameters. Network dependent layers (For further study.) Transport layer (T.70) The test procedures for the transport layer (T.70) are contained in A
19、nnex 1. Annex 1 deines - the Valid and Invalid TPDUs List; - the basic test lists; - Extended Addressing Tests for T.70. Session and Presentation Layer (T.62) These test procedures are contained in Annex 2. Annex 2 describes the Teletex Test Schedule. Teletex Application Service Test Schedule These
20、test procedures are contained in Annex 3. Annex 3 denes - Teletex Application service tests under normal conditions; - Teletex Application service tests under exception conditions. Edition of November 30, 1987 CEPT T/A*07-02*E 8b 2326414 O002814 TIA 07-02 E Annex 1, Page 1 Annex 1 TEST PROCEDURES FO
21、R THE TRANSPORT LAYER Table of Contents 1. GENERAL . 1 2. LIST OF ABBREVIATIONS FOR TRANSPORT PROTOCOL . 2 3. VALID AND INVALID TPDUS LIST 3 4. BASIC TEST LISTS . 8 5. EXTENDED ADDRESSING TESTS FOR T.70 . 15 1. GENERAL This document contains: - a list of valid and invalid TPDUs; - basic test lists i
22、n tabular form; - extended addressing tests for T.70. 1.1. The Basic test Schedules There are two main categories of tests, those carried out when the terminal under test initiates a call and tests carried out when the terminal receives a call. Within each category there are tests for both normal an
23、d exception conditions. The test lists are displayed in tabular form. The tables describe tests which explore state transitions from a particular state. Tests for Multi-terminal configurations and terminals which use transport extended addressing are provided in Annex 1. 1.2. 1.2.1. Description of t
24、he test tables Test riirmber and Test Type The test type describes the test in terms of the TPDU type which is being transmitted or received by the terminal. Each test drives the implementation through at least one state transition. Carrying out all tests in the tables would drive an T.70 implementa
25、tion through all the state transitions except those involving a T-disc Request in states O and 1. Tester Action, Tester Detects These columns show the sequences of protocol blocks that are sent and received by the tester during a particular test. State diagram route ir1 the terwiirial This column sh
26、ows the sequence of state transitions in the terminal to be tested during the test. The service primitives in brackets, if any, indicate the second service action and events. TPDUs required foi n bnsic test These TPDUs are those that should be tested to provide a basic test of T.70. The TPDU numbers
27、 refer to TPDUs which are detailed in the TPDU lists (see 1.2. below). The TPDUs are designated as essential or optional. Essential TPDUs are those which are necessary to give a satisfactory level of condence that an T.70 implementation has been well tested. Optional TPDUs are those that a particula
28、r administration may wish to test in addition to the essential TPDUs. There are two lists for each type of protocol block, one for valid TPDUs and one for invalid TPDUs. The Test Document does not specify a particular sequence of tests. An efficient test sequence can only be created when such factor
29、s as the testing method, the type of test hardware and additional tests required by a testing authority are taken into account. I .2.2. 1.2.3. O 1.2.4. 1.2.5. TPDU lists 1.2.6. Test sequences Edition of November 30, 1987 CEPT T/A*07-02*E b 2326414 0002815 T TIA 07-02 E Annex 1, Page 2 1.2.7. Test Qu
30、ality The tests described here take account of the actual T.70 version which was agreed in the CCITT. This new T.70 version now also contains two annexes (A and B) in which detailed diagrams, tables and explanations (e.g. of “invalid TPDUs”) are given. Nevertheless no guarantee can be given that a t
31、erminal working correctly according to the described tests has no implementation errors at all. In spite of this fact it can be stated that this terminal has a high degree of compatibility and is able to communicate with another terminal tested using these tests. 2. ABBREVIATIONS LIST FOR TRANSPORT
32、PROTOCOL TSDU Transport Service Data Unit , TPDU Transport Protocol Data Unit TUT Terminal Under Test EAG Calling Extended Address EAD Called Extended Address PI Parameter Identifier LI Length Indicator PLI Parameter Length Indicator MUT Multi Terminal Configuration cc Cleaning Cause DR Destination
33、Reference SR Source Reference EM End Mark Bit X = D When TUT is Called Y = N Normal conditions Tests TCR (EAD) TCA (EAD) State XYMN X = G When TUT is Calling Y = E M = A TCR (Resp. TCA) block containing called extended Address I OS Exception conditions Tests For MUT additional Tests ,- Edition of No
34、vember 30, 1987 TIA 07-02 E Annex 1, Page 3 Without Parameter TDT Blocksize 128 TDT Blocksize 2048 With 1 EAD With Parameters block size, EAG, EAD Parameter in any order With EAD 3 digits Parameter with LI = O 3. VALID AND INVALID TPDUS LIST O EO0 13 O 6000240 O EO O 13 O CO O 9000240017 O EO O 13 O
35、 CO O 900024001B OE00 13 OCO3 900024021x 1 E O O 1 3 O C O O C O 3 3 3 3 C O 3 3 3 4 o o o 2 4 o o 18 14 xxxx2 3 xxx 1 EO0 130C03 3 3 3 COOCO3 3 3 4 O O O 2 4 O 14 XXXXO 18 2 3 XXX OE00 130CO 3 3 3 3 3 DO O O 2 4 O 2 5 XXXXX O EO O I3 O CO 800024000 Test level 4, TCR PROTOCOL With 1 EAG With 3 EAG W
36、ith 3 EAD Destination Reference Oandclass byte O and default class para- meter (Checks interworking with IS0 Transport Proto- cols) TYP/ No. ELEMENTS - VALID FOR RECEPTION ONLY O E O O 1 3 O C O 3 3 3 (IA5coding) B00024013XXX 1 EO0 130C03 CO3 3 CO3 3 3 200024011x12xx13xxx 1 EO0 13 OCO3 3 3 CO3 3 CO3
37、 2 o o o 2 4 o 2 3 xxx2 2 xx2 1 x OE130 GO01240 OEOOO 6000000 OE00 13 1 GO00241 O E O O 1 3 O C O c 9000240011 OE00130001 A000 240 5 2 O O O 1 3 C O O 9 F O O 2 4 2 7 1 O Tester Sending TCR Short Description Length indicator (LI) Block type Destination Reference (DD) Source Reference (SG) Extension
38、field X E O O X X O Parameters CO, C1, C2 in any order xo o o xxo Test Status VI. v2. v3. v4. v5. VG. v7. V8. v9. VIO. v11. v12. V13. V14. V15. V1G. V17. Edition of November 30, 1987 CEPT T/A*07-02*E 86 = 2326434 0002837 3 TIA 07-02 E Annex 1, Page 4 Test level 4, Invalid TCR Tester Sending TCR Type
39、/ No. Short Description Il. 12. LI Length First half of Octet 2 incorrect 13. 14. 15. 16. 17. LI Length LI 127 LI =Length PLI of TDT Block size 1 L1 sum of PLI + (2n + 6) n = number of parameters Test level 4, TCA Tester Sending TCA Type/ No. Short Description v1. v2. v3. v4. v5. V6. v7 * Length ind
40、icator (LI) Block type Destination Reference (DD) Source Reference (SG) Extension field X E O O X X O Parameters CO, C1, C2 in any order xo o o xx0 0000130 6001240 EOOOOO 7000000 OE0013 5000240 OE0013 500024 8 E O O 1 3 C 7 128, 128 / O O O O O EO O 13 O C A0002400289 1 EO O 13 O CO O CO 123 1000240
41、01813 - - - - i20 octets - Length indicator (LI) Block type Destination Reference (DR+ SG) Source Reference (SD) Extension field X D X X X X O Parameters CO, C1, C2 in any order xo xxxxo PROTOCOL ELEMENTS - VALID FOR TRANSMISSION AND RECEPTION Without Parameter O DXX1 3 O 6 O XX2 4 O TDT Blocksize 1
42、28 O DXXl 3 O CO O 9 o xx2 4 o o 17 EAD identicalto thatreceived X D X X 1 3 O C O 3 .,., in TCR xo xx2 4 o 2 xx EAD not identical to that re- X D X X 1 3 O C O 3 3 3. ceived in TCR xo xx2 4 o 2 xxxx EADidenticaltothatreceived X D X X 1 3 O C O 3 3 3 . C O O in TCR Blocksize = 128 xo xx2 4 o 2 xxxx
43、o 17 The order of the parameters is undefined EAD different from EAD in X D X X 1 3 O C O O C O 3 3 3. TCR Blocksize Length LI Length LI 127 LI =Length Destination Reference Source Reference of TCR Byte 7 O PLI of TDT block size 1 TDT blocksize blocksize requested in TCR TDT blocksize not known LI s
44、um of PLI + (2n + 6) n =number of parameters Length indicator (LI) Block type Destination Reference (DR+ SG) Source Reference (SD) Extension field X D X X X X O Parameters CO, C1, C2 in any order xo xxxxo oxx13 o 6 O XX2 4 O O DXXl 3 O 7 o xx2 4 o O DXXl 3 O 5 o xx2 4 o O DXXl 3 5 o xx2 4 8 D X X 1
45、3 C 7 ?, 128, 128 / O O 120 octets O Dml 3 O 6 O XX2 4 O O DXXl 3 6 O XX2 4 O O DXXl 3 O C O O AO XX2 4 O O 2 7 7 O DXXl 3 O CO x 9 oxx240 o 1 x O DXXl 3 O COE 90xx240011 1 DXXl 3 O CO O CO 123 1 o xx24 o o 17 13 - - - - - - Test Status E E O E E E E E E E E Test level test 4, TCC Type/ No. Tester S
46、ending TCC Short Description Length indicator (LI) Block type Destination Reference (DR+ SG) Source Reference (SD) Clearing cause (CC) Additional clearing information X8 XXXXO E xo xxxxxo Test Status v1. v2. v3. v4. v5. V6. v7. Edition of November 30, 1987 CEPT T/A*07-02*E b 232bY34 0002839 7 B TIA
47、07-02 E Annex 1, Page 6 Test level 4, Invalid TCC - Type/ No. II. 12. 13. 14. 15. - 16. - Tester Sending TCC Short Description Octet 2 incorrect cc o LI Length LI Length LI 127 DRSR of TCR Test level 4, TBR Type/ No. Tester Sending TBR Short Description Length indicator (LI) Block type Destination R
48、eference (DR+ SG) Source Reference (SD) Clearing cause (CC) Additional clearing information X8 XXXXO E xo xxxxxo ooxx130 6 O XX2 4 O o 8 xx13 o 7 o xx2 4 o o 8 xx13 o 5 o xx2 4 o o 8 xx13 5 o xx2 4 8 8 X X 1 3 O E 7 128, 128 / (IA5 coding) O O O O * - - - 120 octets 08xx130 6 O XX2 4 O Length indica
49、tor (LI) Block type Destination Reference (DR) Reject cause Reject block (PI) x7 xxo cx xo xxx1 x PROTOCOL ELEMENTS - VALID FOR TRANSMISSION AND RECEPTION V1. Normal V2. Parameter LI=O x7 xxo cxx . xo xxo 1 xx o 7 xxo CO 6 O XXO 1 O Test Status E Test Status E E Invalid TBR Il. 12. 13. 14. 15. Octet 2 incorrect LI Length LI Length LI PLI+6 (PLI incorrect) xo xxo cxx. xo xxo 1 xx O 7 XXO CO OF 9oxx11220 o 7 XXO CO OF 5 o xxo 12 2 o o 7 xxo 4 o xxo O 7 XXO CO O F 8 oxx113 20 - Edition of November 30, 1987 CEPT T/A*07-02*E b m 232b414 00
