ITU-T Q 786-1993 SIGNALLING SYSTEM No 7 SCCP TEST SPECIFICATION《7号信令系统-SCCP测试规程-NO 7信令系统的准则(第11研究组)53页》.pdf

《ITU-T Q 786-1993 SIGNALLING SYSTEM No 7 SCCP TEST SPECIFICATION《7号信令系统-SCCP测试规程-NO 7信令系统的准则(第11研究组)53页》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 786-1993 SIGNALLING SYSTEM No 7 SCCP TEST SPECIFICATION《7号信令系统-SCCP测试规程-NO 7信令系统的准则(第11研究组)53页》.pdf（53页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.786 (03/93) SIGNALLING SYSTEM No. 7 SCCP TEST SPECIFICATION ITU-T Recommendation Q.786 (Previously “CCITT Recommendation”) ITU-T RECMNrQ-786 93 M 48b2593 0584383 43

2、2 I FOREWORD The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecom- munication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunicatio

3、ns on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. ITU-T Recommendation 4.786 was revised by the ITU-T Study Gr

4、oup XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). NOTES 1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T)

5、was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms “CCITT, CCIR or IFRB” or t

6、heir associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. 2 telecommunication administration and a recognized operating agency. In this Recommendation, the expression “Administrati

7、on” is used for conciseness to indicate both a O ITU 1994 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. m 48b2591 0584182 379 m CO

8、NTENTS Page Introduction Objective of the test specification Scope of the test . General principles of tests Test environment 5.1 SCCP relation . 5.2 Configuration Test traffic SCCP test list Recommendation Q.786 (03/93) 1 1 1 2 2 2 2 3 3 1 ITU-T RECMN*Q.786 93 e 4862591 0584183 205 E Recommendation

9、 Q.786 SIGNALLING SYSTEM No. 7 SCCP TEST SPECIFICATION (Helsinki, 1993) 1 Introduction This Recommendation contains a detailed set of tests for the Signalling System No. 7 Signalling Connection Control Part (SCCP). These tests are intended to validate the protocol specified in Recommendations 4.711-

10、4.714. This Recom- mendation conforms to Recommendation 4.780, which describes the basic rules of the test specification. 2 Objective of the test specification The objective of the test specification is to provide: Validation - A level of confidence that a given implementation conforms to the Recomm

11、endations 4.71 1-Q.7 14 for SS No. 7 SCCP. Compatibility - A level of confidence that two implementations of SS No. 7 SCCP are able to interwork. In order to ensure that this test specification meets this objective, the following criteria are used: 1) 2) 3) The test specification is not intended to

12、provide exhaustive testing of all aspects of the SS No. 7 SCCP. All tests should be of a practical nature and implementable using the available technology. The test should concentrate on the testing of a normal signalling procedure. Testing of an abnormal signalling procedure will only be identified

13、 where this is regarded as particularly useful. The test list does not include any tests which are application specific (e.g. IN, mobile application, etc.). If such tests are required, they should be contained in application specific testing documentation. 4) 3 Scope of the test The test list is com

14、posed to validate routing/addressing and data transfer concerning connectionless SCCP procedures by monitoring and analysing SCCP messages and their contents. SCCP management, segmentation in connectionless SCCP test and connection-oriented procedures are for further study. Some tests in this Recomm

15、endation require generation of primitives, therefore when performing these tests, appropriate normal system action of the user will have to be chosen which results indicating primitives being generated. The testing of primitives is outside the scope of this Recommendation. Both messages and primitiv

16、es are shown in expected message sequence diagram as indicated below, but primitives are shown for ease of understanding only. . An internal routing of SCCP user data is implementation dependent, and therefore all tests related to internal routing may not be possible to execute. In addition, access

17、to various test interfaces may not be available in all implementations. Recommendation Q.786 (03/93) 1 ITU-T RECflN*Q.78b 73 = 4862571 0584184 141 b b SP C SP A 4 4 4 General principles of tests The tests are described as “Validation(VAT)” tests or “Validation” and “Compatibility(CPT)” tests. Each t

18、est description indicates in the field “type of test” whether the test is a “Validation” test or a “Validation” and “Compatibility” test. All questions and checks in the test description should be answered with positive acknowledgement for correct operations. Where particular failure conditions are

19、tested with or without the return option set, the test with the return option not set should use the same pre-test conditions and data, with the exception of the return option parameter as the corresponding test with the return option set. Some of the described validation tests may not be required t

20、o be executed, since the functionality they aim to test is not included in the Implementation Under Test (IUT). In such a case the non-execution of such a test should not be regarded as a non-conformance statement. For the test cases which result in returning N-NOTICE indication primitive or UDTS me

21、ssage, N-UNIDATA request primitive or UDT message should include the sufficient information to return the N-NOTICE indication primitive or UDTS message. SP B 5 Test environment 5.1 SCCP relation A signalling relation is required between “SP A” and “SP B” or among “SP A”, “SP B” and “SP C” in order t

22、o carry out effective tests. Tested MTPs should be used for compatibility tests. 5.2 Configuration Two configurations are required to perform these tests as shown in Figure 1 and Figure 2. I sp . (Under test) (Note) T1155400-93d01 NOTE - The arrows indicate an SCCP relation. FIGURE 114.786 Test conf

23、iguration for SCCP - Configuration 1 NOTES 1 2 The arrows indicate an SCCP relation. SP A is used as relay point. FIGURE 214.786 Test configuration for SCCP - Coiifiguration 2 2 Recommendation Q.786 (03/93) ITU-T RECMNMO.786 93 i 4862591 0584385 OB8 M The configurations shown above are functional re

24、presentations only, e.g. in Configuration 2, SP B and SP C could be the same or could belong to different MTP networks. 6 Test traffic The details for test traffic and its format are for further study. 7 SCCP test list * VAT & CFT 1 Connectionless procedure 1.1 SCCP Routing 1.1.1 Messages from SCCP

25、users 1.1.1.1 Route not on GT 1.1.1.1.1 1.1.1.1.1.1 GT and SSN included 1.1.1.1.1.2 1.1.1.1.2 1.1.1.1.3 1.1.1.1.4 1.1.1.1.5 1.1.1.1.6 Local DPC and SSN included, DPC and SSN available GT not included, SSN included Local DPC and SSN included, SSN unavailable - Return option set Local DPC and SSN incl

26、uded, SSN unavailable - Return option not set Remote DPC and SSN included, DPC and SSN available Remote DPC and SSN included, DPC and/or SSN unavailable - Return option set Remote DPC and SSN included, DPC and/or SSN unavailable - Return option not set 1.1.1.2 Route on GT 1.1.1.2.1 1.1.1.2.1.1 1.1.1

27、.2.1.2 1.1.1.2.2 1.1.1.2.3 1.1.1.2.4 1.1.1.2.4.1 1.1.1.2.4.2 1.1.1.2.5 1.1.1.2.6 1.1.1.2.7 1.1.1.2.8 1.1.1.2.9 GT translated to local DPC and SSN, and SSN available SSN and GT included SSN not included, GT included GT translated to local DPC and SSN, and SSN unavailable - Return option set GT transl

28、ated to local DPC and SSN, and SSN unavailable - Return option not set GT translated to remote DPC and SSN, and DPC and SSN available SSN and GT included SSN not included, GT included GT translated to remote DPC and SSN, and DPC and/or SSN unavailable - Return option set GT translated to remote DPC

29、and SSN, and DPC and/or SSN unavailable - Return option not set GT translated to DPC and new or as same GT, and DPC available GT translation failed - Return option set GT translation failed - Return option not set 1.1.2 Messages from MTP 1.1.2.1 Route on GT 1.1.2.1.1 1.1.2.1.2 1.1.2.1.3 1.1.2.1.4 1.

30、1.2.1.5 GT translated to ocal DPC and SSN, and SSN available GT translated to local DPC and SSN, and SSN unavailable - Return option set GT translated to local DPC and SSN, and SSN unavailable - Return option not set GT translated to remote DPC and SSN, and DPC and SSN available GT translated to rem

31、ote DPC and SSN, and DPC and/or SSN unavailable - Return option set Recommendation Q.786 (03193) 3 ITU-T RECMNaQ.78b 93 M 48b259L 0584L8b TL4 = * * * * * * * * * 4 1.1.2.1.6 GT translated to remote DPC and SSN, and DPC andor SSN unavailable - Return option not set GT translated to DPC and new or as

32、same GT, and DPC available GT translation failed - Return option set GT translation failed - Return option not set 1.1.2.1.7 1.1.2.1.8 1.1.2.1.9 1.1.2.2 Route not on GT 1.1.2.2.1 1.1.2.2.1.1 GT and SSN included 1.1.2.2.1.2 1.1.2.2.2 1.1.2.2.3 Local DPC and SSN, and SSN available GT not included, SSN

33、 included Local DPC and SSN unavailable - Return option set Local DPC and SSN unavailable - Return option not set 1.2 Data transfer 1.2.1 1.2.1.1 At originating node 1.2.1.2 At relay node 1.2.2 1.2.3 Message Return 1.2.3.1 UDTS deliverable Data transfer with sequential delivery capability Data trans

34、fer with syntax error 1.2.3.1.1 UDTS deliverable to SCCP user 1.2.3.1.2 UDTS deliverable to other SP 1.2.3.2 UDTS undeliverable 1.2.3.2.1 UDTS undeliverable to SCCP user 1.2.4 Segmentation Further Study 2 SCCP management Further Study 3 Connection-oriented procedure Further Study Recommendation 4.78

35、6 (03193) ITU-T RECNN*Q.786 93 4862593 054187 950 II SCCP TEST SPECIFICATION TEST NUMBER: 1.1.1.1.1.1 REFERENCE: 2.3.2 3) c)/Q.714 1 TITLE: Message from SCCP users, route not on GT. SUBTITLE: PURPOSE: Local DPC and SSN included, DPC and SSN available GT and SSN included. To verify that the user data

36、 can be delivered to the correct SCCP user at SP A when routing not on GT. PRE-TEST CONDITIONS: 1. Arrange the called address in N-UNITDATA request to contain: - DPC of SP A - SSN - GT 2. Arrange the SCCP routing control data as follows: - SSN at SP A available I CONFIGURATION: 1 I TYPE OF TEST: VAT

37、 I TYPEOFSP: SP 1 EXPECTED MESSAGE SEQUENCE: SP A SP B I TEST DESCRIPTION Arrange SP A to request delivery of user data to an SCCP user at SP A with a DPC and SSN of SP A in the request. Record the message sequence and parameters using a signai monitor. CHECK A: CONFIRM THAT NO MESSAGES WERE SENT BY

38、 SP A TO SP B. CHECK B: WAS THE DATA CORRECTLY DELIVERED TO THE SCCP USER AT SP A? Recommendation Q.786 (03/93) 5 ITU-T RECHN*d-786 93 W 4862593 0584388 897 W CONFIGURATION: 1 SCCP TEST SPECIFICATION TYPE OF TEST: VAT TYPEOFSP: SP TEST NUMBER: 1.1.1.1.1.2 1. 2. 3. 4. REFERENCE 2.3.2 3) c)/Q.714 TITL

39、E: Messages from SCCP users, route not on GT. SUBTITLE: Local DPC and SSN included, DPC and SSN available GT not included, SSN included. Arrange SP A to request delivery of user data to a SCCP user at SP A with a DPC and SSN of SP A in the request. Record the message sequence and parameters using a

40、signal monitor. CHECK A: CHECK B: CONFIRM THAT NO MESSAGES WERE SENT BY SPA TO SP B. WAS THE DATA CORRECTLY DELIVERED TO THE SCCP USER AT SP A? PURPOSE To verify that the user data can be delivered to the correct SCCP user at SP A when routing not on GT. EXPECTED MESSAGE SEQUENCE: SP A SP B 6 Recomm

41、endation Q.786 (03/93) ITU-T RECMN*Q.786 93 m 4862591 0584189 723 SCCP TEST SPECIFICATION TEST NUMBER: 1.1.1.1.2 REFERENCE: 2.3.2 3) b)/Q.714 TITLE: Messages from SCCP users, route not on GT. SUBTITLE: PURPOSE: Local DPC and SSN included, SSN unavailable - Return option set. To verify that data is r

42、eturned when routing not on GT and return option is set. PRE-TEST CONDITIONS : 1. Arrange the called address in N-UNITDATA request to contain: - DPCofSPA 2. Arrange return option in N-UNITDATA request to be set 3. Arrange the SCCP routing control data as follows: - SSN at SP A unavailable CONFIGURAT

43、ION: 1 TYPE OF TEST: VAT TYPEOFSP: SP - SSN EXPECTED MESSAGE SEQUENCE SP A SP B TEST DESCRIPTION Arrange SP A to request delivery of user data to an SCCP user at SP A with a DPC and SSN of SP A in the request. Record the message sequence and parameters using a signal monitor. CHECK A: CHECK B: CONFI

44、RM THAT NO MESSAGES WERE SENT BY SP A TO SP B. WAS THE SCCP USER ADVISED OF AN APPROPRIATE REASON FOR RETURN? Recommendation Q.786 (03/93) 7 ITU-T RECMN*Q#78b 93 48b2591, 0584390 445 CONFIGURATION: 1 SCCP TEST SPECIFICATION TYPE OF TEST: VAT TYPEOFSP: SP TESTNUMBER: 1.1.1.1.3 REFERENCE: 2.3.2 3) b)/

45、Q.714 1. 2. 3. 4. TITLE: Messages from SCCP users, route not on GT. Arrange SP A to request delivery of user data to an SCCP user at SP A with a DPC and SSN of SP A in the request. Record the message sequence and parameters using a signal monitor. CHECK A: CHECK B: CONFIRM THAT NO MESSAGES WERE SENT

46、 BY SPA TO SP B. CONFIRM THAT DATA WAS NOT RETURNED TO SCCP USER. SUBTITLE: Local DPC and SSN included, SSN unavailable - Return option not set. PURPOSE: To verify that data is not returned when routing not on GT and return option is not set. PRE-TEST CONDITIONS: 1. Arrange the called address in N-U

47、NITDATA request to contain: - SSN 2. Arrange return option in N-UNITDATA request not to be set 3. Arrange the SCCP routing control data as follows: - SSN at SP A unavailable - DPC Of SP A SP A SP B TEST DESCRIPTION 8 Recommendation Q.786 (03/93) ITU-T RECMN*d.786 93 4862591 0584191 381 CONFIGURATION

48、: 1 TYPE OF TEST: VAT & CPT SCCP TEST SPECIFICATION TYPEOFSP: SP TESTNUMBER: 1.1.1.1.4 REFERENCE: 2.3.2 3) a)/Q.714 TITLE: Messages from SCCP users, route not on GT. SUBTITLE: Remote DPC and SSN included, DPC and SSN available. EXPECTED MESSAGE SEQUENCE: SP A SP B TEST DESCRIPTION 1. 2. 3. 4. 5. 6.

49、Arrange SP A to request generating a UDT message to SP B with a remote DPC and SSN. Record the message sequence and parameters using a signal monitor. CHECK A: CHECK B: WAS THE UDT MESSAGE CORRECTLY GENERATED BY SP A TO SP B? WAS THE POINT CODE OF SP B CONTAINED IN THE MTP ROUTING LABEL OF THE UDT MESSAGE AND WAS THE SI0 CORRECT? WERE THE PARAMETER FIELDS SET CORRECTLY AS INDICATED IN THE CHECK TABLE BELOW? CHECK C: CHECK D: WAS THE MESSAGE SEQUENCE AS ABOVE? Recommendation 4.786 (03/93) 9 ITU-T RECMN*Q.786 93 4862591 0584192 218 0 TESTNUMBER: 1.1.1.1.4 (continued) CHECK