1、 ATIS-0300014 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part III, Installation, Testing and Maintenance Responsibilities for SS7 Links and Trunks Attachment C SCCP Compatibility Tests Version 12.0 ATIS is the leading technical planning and standards development orga
2、nization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 200 companies actively formulate standards in ATIS Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wir
3、eless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle,
4、 IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and
5、 a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For more information, please visit www.atis.org. Notice This document was developed by the Alliance for Telecommunications Industry Solutions (ATIS) sponsored
6、 Next Generation Interconnection Interoperability Forum (NGIIF). The NGIIF addresses next-generation network interconnection and interoperability issues associated with emerging technologies. Specifically, it develops operational procedures which involve the network aspects of architecture, disaster
7、 preparedness, installation, maintenance, management, reliability, routing, security, and testing between network operators. In addition, the NGIIF addresses issues which impact the interconnection of existing and next generation networks and facilitate the transition to emerging technologies. All c
8、hanges to this document shall be made through the NGIIF issue resolution process. Note Regarding Previous Versions The NIIF Reference Document was formerly known as the Network Operations Forum (NOF) Reference Document. The NOF Reference Document was published and maintained by Bellcore. The last ve
9、rsion of the NOF Reference Document is Issue 13. Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineeri
10、ng or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND F
11、URTHER NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EV
12、ENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES THAT ANY AND ALL USE OF OR RELIANCE UPON THE INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0300014, NGIIF Reference Document, Part III, Installation and Maintenance
13、 Responsibilities for SS7 Links and Trunks, Attachment C, SCCP Compatibility Tests, Formerly NIIF 5009 The NGIIF Reference Document, Part III, Installation and Maintenance Responsibilities for SS7 Links and Trunks, Attachment C, SCCP Compatibility Tests is an ATIS standard developed by the NGIIF. Pu
14、blished by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2011 by Alliance for Telecommunications Industry Solutions All rights reserved. 2 No part of this publication may be reproduced in any form, in an electronic retrieval system or
15、otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. 3 SCCP Compatibility Tests Table of Contents 1 INTRODUCTION AND TESTING ENVIRONMENT 4 1.1 SCCP PROTOCOL CLASS 0 COMPATIBILITY T
16、ESTING . 4 1.2 TESTING ENVIRONMENT . 4 1.3 DESCRIPTION OF THE SCCP PROTOCOL CLASS 0 COMPATIBILITY TESTS . 4 2 SCCP COMPATIBILITY TESTS . 5 3 TEST SCRIPTS . 5 3.1 SUCCESSFUL UDT QUERIES/RESPONSES - FGTT IN THE TERMINATING NETWORK 6 3.2 FAILURE - UNASSIGNED CODES . 8 3.3 FAILURE - INVALID ADDRESS INDI
17、CATOR IN THE CALLED PARTY ADDRESS 9 3.4 FAILURE GTT (TRANSLATION TYPE AND GT DIGITS) . 10 3.5 FAILURE - GTT (NO ENTRIES FOR THE GT IN TRANSLATION TABLES) . 12 3.6 FAILURE - MTP NETWORK ROUTING AT AN STP WITH GTT FUNCTIONS 13 3.7 FAILURE - OF THE SIGNALING END POINT (SEP), E.G., SERVICE-SPECIFIC DATA
18、BASE, IN THE TERMINATING NETWORK; STP PERFORMING FGTT HAS SCCP MANAGEMENT (SCMG) FUNCTIONS 14 3.8 FAILURE- OF THE SIGNALING END POINT (SEP), E.G., SERVICE SPECIFIC DATABASE, IN THE TERMINATING NETWORK 16 3.9 SUCCESSFUL UDT QUERIES/RESPONSES - FGTT IN THE ORIGINATING NETWORK 17 3.10 SSP AND SST MESSA
19、GES DURING SUBSYSTEM FAILURE AND SSA MESSAGE(S) AFTER SUBSYSTEM RECOVERY - FGTT IN THE ORIGINATING NETWORK 18 3.11 SST AND SSA MESSAGES DURING SUBSYSTEM NORMAL OPERATION - FGTT IN THE ORIGINATING NETWORK . 20 4 1 INTRODUCTION AND TESTING ENVIRONMENT The following tests were developed by the NGIIF/SS
20、7 Ad hoc Committee to verify the compatibility of networks during interconnection. These tests are intended to be used as a set of minimum tests of the SCCP protocol portion of the network service part for connectionless services only (Class 0). It is assumed that the interconnecting networks may ha
21、ve some additional tests they may wish to perform during interconnection. In that case, these tests will be part of the bilateral agreements developed for SS7 network interconnection. Schematics included with the test scripts indicate a minimum network configuration. The actual test network may incl
22、ude intermediate STPs. 1.1 SCCP Protocol Class 0 Compatibility Testing Compatibility testing checks for the correct interworking of SCCP Protocol Class 0 Compatibility Testing implementations. The tests are written for the interconnecting of two (2) given implementations. These tests should be perfo
23、rmed on new signaling points as well as between already connected signaling points. The full tests suite should be run for any interconnection configuration between the interconnecting companies, unless previously tested. The configuration is defined by manufacturer model and software load of the in
24、terconnecting signaling network elements and the application being supported. Subsequent interconnections, using configurations previously tested by the interconnecting companies, may be tested at their discretion. 1.2 Testing Environment The following test scripts provide the ability to test interc
25、onnected networks. Test scripts that have the potential to impact service are so noted. Some test scripts indicate an insertion point for test equipment that will be used to stimulate test conditions. The test environment may be configured differently if network conditions require, provided the desi
26、red test objectives are met. Exact message format and codings are not discussed in these tests. Bilateral discussions and pre-test agreements are required prior to executing any of the tests, in particular, the contents of the Called Party Address field to produce the desired result; either successf
27、ul message translation or message failure simulation. In addition, the content of screening tables shall be discussed so that the test messages are not discarded. Message content should be discussed individually for each of the tests to be conducted. 1.3 Description of the SCCP Protocol Class 0 Comp
28、atibility Tests The following table summarizes the set of SCCP Protocol Class 0 compatibility tests. 5 2 SCCP Compatibility Tests Test # Test Title 3.1 Successful UDT queries/responses - FGTT in the terminating network 3.2 Failure - unassigned codes 3.3 Failure - invalid Address Indicator in the cal
29、led party address 3.4 Failure - GTT (Translation Type and GT digits) 3.5 Failure - GTT (no entries for the GT in translation tables) 3.6 Failure - MTP network routing at an STP with GTT functions 3.7 Failure - of the signaling end point, e.g., service-specific database, in the terminating network. S
30、TP performing FGTT has SCMG functions. 3.8 Failure - of the signaling end point, e.g., service-specific database, in the terminating network. 3.9 Successful UDT queries/responses - FGTT in the originating network 3.10 SSP and SST messages during subsystem failure and SSA message(s) after subsystem r
31、ecovery - FGTT in the originating network 3.11 SST and SSA messages during subsystem normal operation FGTT in the originating network 3 Test Scripts Test scripts for the above tests follow. 6 NGIIF Test #: ANSI T1.235 Test #: TR-905 Test # 3.1 Successful UDT queries/responses - FGTT in the terminati
32、ng network S-1.1 No corresponding test REFERENCE: ANSI T1.112, chapter 4, clause 2 TITLE: 3.1 Successful UDT Queries/Responses - FGTT (Final Global Title Translation) in the terminating network PURPOSE: To verify that: 1.) the global title translation functions at the STPs are performed correctly; 2
33、.) the UDT query message is routed correctly to the destination; and 3.) the UDT response message is properly returned to the query originator. PRE-TEST CONDITIONS: Global title translation tables are populated at the appropriate STPs. CONFIGURATION: MESSAGE SEQUENCE: SPC SP A-A SP B-B SP D Q1 Q2 Q3
34、 R1 1.4 SP A 1.3 SP A 1.2 SP B 1.1 SP B SPC SPD 7 TEST DESCRIPTION 1. Send a UDT test query message, Q1 from SP C. 2. Intermediate global title translation (IGTT) is performed at SP A (or SP A) of Network 1. UDT query message, Q2, should be routed to SP B (or SP B). 3. Final global title translation
35、 (FGTT) is performed at SP B (or SP B) of Network 2. UDT query message, Q3, should be routed to the destination SP D. 4. Verify that the UDT response message, R1, is sent from SP D and received in the correct format SP C. 8 NGIIF Test #: ANSI T1.235 Test #: TR-905 Test # 3.2 Failure - unassigned cod
36、es S-2.1 No corresponding test REFERENCE: ANSI T1.112, chapter 4, clause 4.3 TITLE: 3.2 Failure - unassigned codes PURPOSE: To verify that the UDT message with unassigned codes of Message Type, Protocol Class, or Return Option will be discarded. PRE-TEST CONDITIONS: Connect the test unit SP B to SP
37、A. CONFIGURATION: MESSAGE SEQUENCE: SP B SP AQ1 TEST DESCRIPTION: 1. Send a UDT test message, Q1, from the test unit SP B to SP A. Consider testing the cases where Q1 has: unassigned message type code unassigned protocol class code unassigned return option code. 2. Verify that in each case, the mess
38、age Q1 is discarded at SP A, and no UDTS is returned. Note: Alternatively, the test unit can be located on the A-link side of an STP, and the UDT message may be MTP routed to SP A. SP-B SP-A9 NGIIF Test #: ANSI T1.235 Test #: TR-905 Test # 3.3 Failure - invalid Address Indicator in the called party
39、address S-2.2 No corresponding test REFERENCE: ANSI T1.112, chapter 3, subclause 3.4.1 and ANSI T1.112, chapter 4, subclause 4.2 TITLE: 3.3 Failure - invalid Address Indicator in the called party address PURPOSE: To verify that the UDTS message will be returned if the information in the Address Indi
40、cator of the called party address of the sent UDT message is invalid, and the “return message on error“ option is set in the sent UDT message. PRE-TEST CONDITIONS: Insert the test unit SP E between SP A and SP B. CONFIGURATION: MESSAGE SEQUENCE: SP C SP A-A SP E SP B-B SP D Q1 UDTS TEST DESCRIPTION:
41、 1. Send UDT test messages, Q1, from SP E to SP B, with the “return message on error“ option set. Simulate Q1 as if it were the query message from SP C via SP A. 2. Test the following separate cases - invalid Address Indicators in Called Party Address (CdPA) of Q1: natl/intl indicator = 0 (intl) rou
42、ting indicator = 0 and global title indicator =0 routing indicator = 0 and global title indicator = nor-applicable value (other than zero) routing indicator = 1 and SSN indicator = 0 3. Verify that in all four cases, a UDTS is returned from SP B addressed to SPC with Return Cause set to “no translat
43、ion of an address of such nature.“ Notes: Alternatively, SP E can be located on the A-link side of SP A and the UDT message may be MTP routed to SP B. SP-C SP-A SP-A SP-B SP-B SP-D SP-E 10 NGIIF Test #: ANSI T1.235 Test #: TR-905 Test # 3.4 Failure GTT (Translation Type and GT digits) S-3.1 No corre
44、sponding test REFERENCE: ANSI T1.112, chapter 3, subclauses 3.4.2, 3.12 and ANSI T1.112, chapter 4, subclauses 2.3, 2.4, 4.2 TITLE: 3.4 Failure GTT (Translation Type and GT digits) PURPOSE: To verify that the UDTS message will be returned if the information in the address of the Called Party Address
45、 of the received UDT message is invalid, i.e., invalid translation type or GT digits are outside of the applicable range, and the “return message on error“ is set in the received UDT message. PRE-TEST CONDITIONS: Insert the test unit SP E between SP A and SP B. GTT tables are populated at the approp
46、riate STPs. CONFIGURATION: MESSAGE SEQUENCE: SP C SP A-A SP E SP B-B SP D Q1 UDTS TEST DESCRIPTION: 1. Send UDT test messages, Q1, from SP E to SP B, with the “return message on error“ option set. Simulate Q1 as if it were the query message from SP C via SP A. 2. Test the following separate cases. i
47、nvalid translation type GT digits outside of the applicable range (correct number of digits) GT digits outside of the applicable range (incorrect number of digits) 3. Verify that in all cases, a UDTS is returned from SP B addressed to SP C with Return Cause set to “no translation for this specific a
48、ddress“. Case i may fail screening, and may not return UDTS. SP-C SP-A SP-A SP-B SP-B SP-D SP-E 11 Note 1: Alternatively, SP E can be located on the A-link side of SP A and the UDT message may be MTP routed to SP B. Note 2: For IGTT, SP B (SP B) belongs to an intermediate network. For FGTT, SP B (SP
49、 B) belongs to an intermediate or terminating network. 12 NGIIF Test #: ANSI T1.235 Test #: TR-905 Test # 3.5 Failure - GTT (no entries for the GT in translation tables) S-3.2 No corresponding test REFERENCE: ANSI T1.112, chapter 3, subclause 3.12 and ANSI T1.112, chapter 4, subclauses 2.3, 2.4, 4.2 TITLE: 3.5 Failure - GTT (no entries for the GT in translation tables) PURPOSE: To verify that a UDTS message will be returned if GTT fails due to no entries for the GT, and the “return message on error“ option is set in
