1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU SERIES Q: SWITCHING AND SIGNALLING Specifications of Signalling System No. 7 - Test specification Q.787 (09/97) Transaction Capabilities (TC) test specification ITU-T Recommendation Q.787 (Previously CCITT Re
2、commendation) STD=ITU-T RECMN Q.787-ENGL 1997 48b259; 0647257 022 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN CLAUSES APPLICABLE TO I
3、TU-T STANDARD SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM RI SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q.1-Q.3 Q.4-Q . 59 Q.60-Q.99 Q.100-Q.119 Q.120-Q.249 Q .250-Q . 309 Q. 3 I 0-Q.399 Q.400-Q.499 DIGITAL EX
4、CHANGES INTERWORKING OF SIGNALLING SYSTEMS I/ Q .500-Q. 599 Q.600-Q.699 1) SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q. 700-Q.849 General Message transfer part (MTP) Signalling connection control part (SCCP) Telephone user part (TUP) ISDN supplementary services Data user part Signalling System No. 7
5、 management ISDN user part Q.700 Q.701-Q.709 Q.711-Q.719 Q.720-Q.729 Q. 730-Q. 739 Q. 740-Q. 749 Q.750-Q.759 Q. 760-Q. 769 Transaction capabilities application part Q.770-Q.779 Q3 interface Q.800-Q.849 Q ,850-Q . 999 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK Q.1000-Q.1099
6、 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q. 1 1 OO-Q. 1 199 INTELLIGENT NETWORK Q. 1200-Q. 1999 BROADBAND ISDN Q.2000-Q.2999 For further details, please refer to ITU-T List of Recommendations. STDDITU-T RECMN Q-7B7-ENGL 1997 9 4862591 Ob47258 Tb9 9 ITU-T RECOMMENDATION Q.787 TRANSACTION CAPABILIT
7、IES (TC) TEST SPECIFICATION Summary This revised Recommendation Q.787 contains the test scripts for the SS No. 7 Transaction Capabilities. This revised Recommendation now covers the test descriptions for the Dialogue Portion of the White Book (1 993) Recommendations Q.771 to Q.774 (Transaction capab
8、ilities application P* Source ITU-T Recommendation Q.787 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997. FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the fiel
9、d of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
10、 The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the IT-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedu
11、re laid down in WTSC Resolution No. 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a tel
12、ecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the e
13、vidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents,
14、which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 1998 All rights reserved. No part of this publication may be reproduced or utilize
15、d in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. Recommendation 4.787 (09/97) 11 1 2 3 4 5 5.1 5.2 6 7 7.1 7.2 CONTENTS Page Introduction Objectives of the test specification . Scope General pnnciples of test T
16、est environment Signalling relation Configuration Background traffic Test list . TC Transaction sublayer (TSL) test specification 7.1.2 Transaction sublayer tests . 7.1.1 Guidance on performing transaction sublayer tests TC Component Sublayer (CSL) test specification . 7.2.1 Guidance on performing c
17、omponent sublayer tests 7.2.2 Component sublayer test list . Recommendation Q.787 (09/97) 1 2 2 2 2 2 2 3 114 114 114 . 111 Recommendation 4.787 TRANSACTION CAPABILITIES (TC) TEST SPECIFICATION (revised in 1997) 1 Introduction This Recommendation contains a detailed set of tests for the SS No. 7 Tra
18、nsaction Capabilities (TC). These tests are intended to validate the protocol specified in Recommendations Q.771 to Q.774. This Recommendation conforms to white Book (1993) which describes the basic rules for a test specification, as specified in Recommendation Q.780. 2 Objectives of the test specif
19、ication The objective of the test specification is to provide: Validation-A level of confidence that a given implementation conforms to the white Book (1993) Recommendations 4.771 to 4.774 for SS No. 7 TC. Compatibility - A level of confidence that two implementations of SS No. 7 TC are able to inte
20、rwork. The following criteria have been used in the generation of this test specification: 1) 2) 3) 4) the test specification does not provide exhaustive testing of all aspects of the SS No. 7 TC; all tests are of a practical nature and implementable using the available technology; the test list con
21、centrates on the testing of normal signalling procedures. Testing of abnormal signalling procedures are only identified where this is regarded as particularly useful; the test list does not include any tests which are application specific. These tests should be contained in application specific test
22、ing documentation and are outside the scope of this test specification. 3 Scope The test scripts are divided into two subclauses: 7.1, TC Transaction Sublayer (TSL) test specification and 7.2, TC Component Sublayer (CSL) test specification. Most TSL and CSL functions are dependent on each other and
23、will need to be performed together. The division between TSL and CSL is for clarification and understanding only and does not imply an implementation. This test specification is designed to veri the TCAP functionality by testing TCAP messages and their contents. Performance aspects such as the limit
24、s of numbers of transactions IDS are not taken into account in this test specification. Some tests in this Recommendation require the generation of primitives; therefore, when performing these tests, appropriate normal system actions of the TCAP user will have to be chosen which result in the indica
25、ted primitive being generated. The testing of primitives is outside the scope of this Recommendation. Both messages and primitives are shown in the expected message sequence diagrams as indicated below, but primitives are shown for ease of understanding only. PHMITIVE: =-=E= MESSAGE: - The test desc
26、ription provides a guide for the correct interpretation and implementation of the test, but it does not constrain its realisation. In particular, any reference to the internal structure of the Recommendation Q.787 (09/97) 1 Implementation Under Test (IUT), such as confirmation of internal states of
27、the TC state machines, is given for clarification only and its practical realisation can be application dependent or vary from one test to another. All questions and checks in the test description should be answered “YES“ for correct operation. Throughout the test specification, mention is made of “
28、state machines“. This specification conceptual model is used in Recommendation Q.774 to aid understanding. It does not imply an implementation, even when the test script asks for the state to be confirmed at the end of some tests. Possible methods of ensuring that the software has returned to the re
29、quired state are enumerated in the 7.1.1 and 7.2.1, Guidance on performing component sublayer tests. The test specification is independent of any specific application, or implementation. 4 General principles of test The tests are described as “Validation“ or “Validation and Compatibility“ tests. Eac
30、h test script indicates in the “Type of Test“ field, whether the test is “VAT“ (Validation) or “VAT and CPT“ (Validation and Compatibility). 5 Test environment 5.1 Signalling relation A stable signalling relation is required between “SP A“ and “SP B“ in order to test TCAP effectively. A tested netwo
31、rk service layer, e.g. MTP and SCCP signalling relation, should be used for compatibility tests. 5.2 Configuration Only one configuration is required to perform the tests given in the proposed test list, Figure 1: as shown in TI 18531 0-97 IUT NOTE -The arrows indicate a signalling relation. Figure
32、1/Q.787 - Configuration: 1 6 Background traffic These tests do not take into account any level of background traffic. 7 Test list The test list categories are given in the following subclauses. 7.1 7.1.1 For each test, the expected message sequence, a test description and a check table for Informati
33、on Elements (IE) within messages are given. TC Transaction sublayer (TSL) test specification Guidance on performing transaction sublayer tests 2 Recommendation Q.787 (09/97) In the expected message sequence, primitives are shown at SP A Implementation Under Test (IUT) side only. The function of the
34、check table is to provide the contents of both the initiating message and the expected results in order to perform the checks in the test descriptions. The check table for IE within messages does not include information on the Component Portion or the User Abort Information IE contents, which are de
35、pendent on a specific application. In the check tables, messages from the IUT are described using the short form for any IE length, except for 1.1.3.1.1 which tests the length variations. However different forms complying with 3.3iQ.773 may be used in any test. In order to test for pre and post test
36、 results such as the state machines being in the idle state, the following procedure is suggested: - NOTE 7.1.2 NDA FFS * Send a Continue to the IUT with the identical destination transaction ID (of a transaction that should be idle) and expect an Abort with unrecognized transaction ID cause value.
37、If another message is received as a response, then this means that the transaction is not in the idle state. - The details of these confirmation tests are implementation dependant. Transaction sublayer tests No Details Available For Further Study Validation and Compatibility * * * All other tests ar
38、e Validation Only. 1 Transaction sublayer 1.1 Valid function 1.1.1 Unstructured dialogue * 1.1.1.1 Tested side sending * 1.1.1.2 Tested side receiving 1.1.2 Structured dialogue 1.1.2.1 Clearing before subsequent Message 1.1.2.1.1 Valid clearing from initiating side * 1) Prearranged ending * 2) Abort
39、 by the TR-User 1.1.2.1.2 Valid clearing from responding side 1.1.2.1.2.1 IUT sending * 1) Basic ending * 2) Prearranged ending * 3) Abort by the TR-User * 1) Abort by the TR-User * 3) Basic ending 1.1.2.1.2.2 IUT receiving 2) Abort by transaction sublayer 1.1.2.2 Clearing after Continue Message 1.1
40、.2.2.1 Valid clearing from initiating side 1.1.2.2.1.1 IUT sending i) Basic ending 2) Prearranged ending 3) Abort by the TR-User 1) Basic ending 2) Abort by the transaction 1.1.2.2.1.2 IUT receiving sublayer * Recommendation 4.787 (09197) 3 - - - STD=ITU-T RECMN Q-787-ENGL 1997 = 4862593 Ob472b4 2b2
41、 = * * * * * * * * * 3) Abort by the TR-User 1.1.2.2.2 Valid clearing from responding side 1.1.2.2.2.1 IUT sending 1) Basic ending 2) Prearranged ending 3) Abort by the TR-User 1) Basic ending 2) Abort by the transaction 3) Abort by the TR-User 1.1.2.2.2.2 IUT receiving sublayer 1.1.2.3 Clearing aft
42、er Continue Message (component portion not present) 1.1.2.3.1 Basic ending IUT sending 1.1.2.3.2 Basic ending IUT receiving 1.1.2.4 Message exchange after transaction established 1.1.2.4.1 IUT initiating 1.1.2.4.2 IUT receiving 1.1.2.5.1 Register address change 1.1.2.5 TC Addressing 1.1.3 Encoding a
43、nd value variations 1.1.3.1 Encoding variations 1.1.3.1.1 Length variations 1.1.3.1.1.1 Definite short 1) 2) Component portion length in definite short form embedded in short form Component portion length in definite short form embedded in long form Component portion length in definite long form emb
44、edded in long form Component portion length in indefinite form embedded in indefinite form 1.1.3.1.1.2 Definite long 1) 1.1.3.1.1.3 Indefinite form 1) 1,1.3.2 Value variations 1.1.3.2.1 Transaction ID 1) Length is one octet 2) Length is four octets 1.2 Syntactically Invalid Behaviour 1.2.1 Invalid v
45、alues for information elements 1.2.1.1 Begin Message type 1) OTID length = O 2) 1.2.1.2 First Continue Message 1) DTID length = O 1.2.1.3 Subsequent Continue Message 1) Component portion length incorrect 1.2.1.4 End Message 1) OTID length four octets DTID length four octets 4 Recommendation Q.787 (0
46、9/97) - STD-ITU-T RECMN Q.787-ENGL It997 4862591 0647265 1T9 1.2.1.5 Abort Message 1) Invalid P-Abort cause value 2) P-Abort cause length incorrect 1.2.2 1.nvalid structure 1.2.2.1 Unidirectional Message type 1) Unknown information element present 1.2.2.2 Begin Message type 1) OTID absent 2) Unknown
47、 information element present 1) OTID absent 2) DTID absent 3) OTID duplicated 4) DTID duplicated 5) Unknown information element present 1.2.2.4 Subsequent Continue Message 1) OTID absent 2) Unknown information element present 1) DTID absent 1) DTID absent 1) OTID not included 2) 3) 1.2.2.3 First Con
48、tinue Message 1.2.2.5 End Message 1.2.2.6 Abort Message 1.2.2.7 Unknown Message OTID included and DTID not included OTID included and DTID included 1.2.3 Invalid encoding (Le. Rec. X.209 BER violation) 1.2.3.1 Begin Message type 1.2.3.2 Continue Message type 1) Invalid tag 1) Invalid tag 1.3 Inoppor
49、tune Messages 1) 1) 1) 1.3.1 Continue Message type 1.3.2 End Message type 1.3.3 Abort Message type 1.4 Multiple Transaction Encoding Receipt of Continue Message in Idle state with unassigned DTID Receipt of End message in Idle state Receipt of Abort message in Idle state 1.4.1 1.4.2 Valid Transaction Encoding 1) 2) Inopportune Messages 1) 2) New transaction request during transaction establishment New transaction request after transaction establishment Message with unassigned DTID during transaction establishment Message with unassigned DTID after transac
