1、 ATIS-0300013 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part III, Installation, Testing and Maintenance Responsibilities for SS7 Links and Trunks Attachment B ISUP 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-0300013, NGIIF Reference Document, Part III, Installation and Maintenance
13、 Responsibilities for SS7 Links and Trunks, Attachment B, ISUP Compatibility Tests, Formerly NIIF 5008 The NGIIF Reference Document, Part III, Installation and Maintenance Responsibilities for SS7 Links and Trunks is an ATIS standard developed by the NGIIF. Published by Alliance for Telecommunicatio
14、ns 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 otherwise, without the prior written per
15、mission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. 3 ISUP Compatibility Tests Table of Contents 1 INTRODUCTION . 5 1.1 PURPOSE OF TESTS . 5 1.2 TEST METHOD 5 1.3 DESCRIPTION OF TESTS . 5 1.4 OTHER TESTING CONSIDERATION
16、S . 6 1.5 CIRCUIT VALIDATION TEST (CVT) . 8 1.6 CONTINUITY CHECK REQUEST (CCR) 9 1.7 CONTINUITY TEST - SUCCESSFUL . 10 1.8 2.4 CONTINUITY TEST - UNSUCCESSFUL . 11 1.9 CONTINUITY TEST - PREVIOUS CIRCUIT - IAM . 12 1.10 CONTINUITY TEST - SUCCESSFUL CRM . 13 1.11 CONTINUITY TEST - UNSUCCESSFUL - CRM .
17、14 1.12 SINGLE CIRCUIT BLOCK/UNBLOCK - BLO/UBL 15 1.13 SINGLE CIRCUIT BLOCK/RESET CIRCUIT/UNBLOCK - BLO/RSC/UBL . 16 1.14 BLOCK/UNBLOCK FROM CALL ORIGINATING END - BLO/BLU . 18 1.15 BLOCK/UNBLOCK FROM CALL RECEIVING END - BLO/UBL . 20 1.16 CIRCUIT GROUP BLOCKING/UNBLOCKING - CGB/CGU (BLOCK WITHOUT R
18、ELEASE) . 22 1.17 CIRCUIT GROUP BLOCKING/UNBLOCKING - CGB/CGU (BLOCK WITH IMMEDIATE RELEASE) 24 1.18 RESET CIRCUIT - DURING AN ESTABLISHED OUTGOING CALL - RSC 26 1.19 RESET CIRCUIT - DURING AN ESTABLISHED INCOMING CALL - RSC 27 1.20 DUAL SEIZURE 28 1.21 CALL TO IDLE TEST LINE 30 1.22 CALL TO BUSY TE
19、ST LINE 31 1.23 IAM WITH AN UNEQUIPPED CIRCUIT IDENTIFICATION CODE . 32 1.24 TONES AND ANNOUNCEMENTS - BUSY LINE 33 1.25 TONES AND ANNOUNCEMENTS - UNALLOCATED NUMBER . 34 1.26 TONE AND ANNOUNCEMENTS - NO CIRCUIT AVAILABLE . 35 1.27 RELEASE - ABANDONED CALL 36 1.28 RELEASE - CALLING PARTY 37 1.29 SUS
20、PEND, RESUME AND RELEASE - CASE 1 38 1.30 SUSPEND, RESUME AND RELEASE - CASE 2 40 1.31 UNSUCCESSFUL CALL - IAM - NO CPN, NO CHG, WITH OLI . 41 1.32 UNSUCCESSFUL CALL - IAM - WITH CPN, WITH CHG, NO OLI . 42 1.33 CALLING PARTY DISCONNECT BEFORE RECEIPT OF ACM . 43 1.34 SINGLE CIRCUIT BLOCK/RESET CIRCU
21、IT/UNBLOCK - BLO/RSC/UBL (ALSO SEE NGIIF TEST 2.9) 44 1.35 CIRCUIT GROUP BLOCKING/UNBLOCKING CGB/CGU (BLOCK WITHOUT RELEASE) (ALSO SEE NGIIF TEST 2.12) . 47 1.36 RESET CIRCUIT - DURING AN ESTABLISHED OUTGOING CALL - RSC (ALSO SEE NGIIF TEST 2.14) . 49 1.37 RESET CIRCUIT - DURING AN ESTABLISHED INCOM
22、ING CALL - RSC (ALSO SEE NGIIF TEST 2.15) 50 1.38 IAM RECEIVED ON A REMOTELY BLOCKED CIRCUIT . 51 1.39 CALL TO CIRCUIT BLOCKED AT BOTH ENDS 52 1.40 DUAL SEIZURE (ALSO SEE NGIIF TEST 2.16) . 53 1.41 TIMER TIAM TIME-OUT 55 1.42 IAM WITH AN UNEQUIPPED CIRCUIT (ALSO SEE NGIIF 2.19) 56 1.43 UNSUCCESSFUL
23、CALL - IAM NO CPN, NO CHG, WITH OLI (ALSO SEE NGIIF TEST 2.27) . 57 1.44 UNSUCCESSFUL CALL - IAM - WITH CPN, WITH CHG, NO OLI (ALSO SEE TEST 2.28) . 58 1.45 CALLING PARTY DISCONNECT BEFORE RECEIPT OF ACM (ALSO SEE NGIIF 2.29) 59 1.46 SIMULTANEOUS RELEASE MESSAGES . 60 1.47 BLO AFTER IAM RECEIVED AND
24、 BEFORE BACKWARD MESSAGE 61 1.48 SENDING IAM AND RECEIVING CGBS BEFORE ANY BACKWARD MESSAGES 62 1.49 SENDING IAM AND RECEIVING CGBS AFTER RECEIVING A BACKWARD MESSAGE 64 1.50 CIRCUIT GROUP RESET MESSAGES - GRS 66 1.51 CIRCUIT GROUP RESETS DURING AN ESTABLISHED CALL -GRS 67 1.52 RESET CIRCUIT AFTER I
25、AM BUT BEFORE BACKWARD MESSAGES - RSC . 68 1.53 IAM PRIORITY TEST FOR INTERCONNECTS . 69 4 1.54 IAM PRECEDENCE TEST FOR INTERCONNECTS . 72 1.55 SIP INVITE TO ISUP IAM MAPPINGS 74 1.56 ISUP IAM TO SIP INVITE MAPPINGS 79 5 1 INTRODUCTION These tests scripts were developed as a minimum set of tests to
26、be performed during interconnection of two networks. These tests presume that the interconnected network elements have been tested for conformance to applicable standards. Since no suite of conformance tests has been adopted, in the interest of the service, the interconnecting parties should exchang
27、e known specification non-compliances and discuss conformance testing that they have performed. Because of the current lack of conformance tests, interconnecting networks may agree on additional tests to be performed. NOTE: The test message sequence and expected test results described below are appl
28、icable to interconnecting trunk groups FG-D type interconnections and can also accommodate wireline to wireless, LEC to LEC interconnections. For all other types, it is expected that the call shall complete as per standards. The interconnecting parties should discuss all parameters and codings prior
29、 to testing taking place. 1.1 Purpose of Tests This document provides a recommended minimum set of script-driven tests and manually interactive tests that should be performed to test the compatibility of the network elements. 1.2 Test Method Tests should be generated via test scripts and manually by
30、 Access Service Provider End Office (ECEO), Access Service Provider Access Tandem (ECAT), and Access Service Customer (ASC) personnel per the “DESCRIPTION OF TESTS“ section of this document. The Access Service Provider (ASP) and the ASC should non-intrusively monitor the ISDN USER Part (ISDN-UP) mes
31、sages between the system under test. 1.3 Description of Tests This document provides the Trunk Maintenance, Call Set-Up, and Intrusive tests that should be performed. These tests are guidelines and each ASP/ASC may elect to add to these tests by mutual agreement. Some tests, as noted in the descript
32、ions, may not be able to be performed due to implementation constraints. NOTE: The test message sequence and expected test results described below are applicable to interconnecting trunk groups FG-D type interconnections and can also accommodate wireline to wireless, LEC to LEC interconnections. For
33、 all other types, it is expected that the call shall complete as per standards. The interconnecting parties should discuss all parameters and codings prior to taking place. In the “TEST SEQUENCE“ descriptions of the following tests - arrows, dashes, and the abbreviations “SS7“ and “MF“ are used to i
34、ndicate the directionality of messaging and type of circuit group(s) (Signaling System 7 and/or Multi-Frequency) i.e., ECEO(A)/ECAT ASC indicates that the test should be performed in both directions using an SS7 circuit group (four tests total). The “EXPECTED RESULT“ is included as a guide to aid in
35、 analysis. Detailed verification of the following items should be performed as applicable using the TR-TSV-000905 section(s) listed under “REFERENCE(S)“ for each test: Correct Termination of Calls Correct Message Sequences Between the Switches Correct Parameters in Messages 6 Correct Coding of Param
36、eters in Messages Correct Timer Functionality Correct Handling of Error and Abnormal Events Correct Circuit States Automatic Message Accounting (AMA) Billing Data Collected. 1.4 Other Testing Considerations 1.4.1 IAM Priority Level Testing In the event of a national emergency, the Government Emergen
37、cy Telecommunications Service (GETS) and Wireless Priority Service (WPS) provide priority call completion to authorized users during times of network stress or congestion. GETS was fielded on September 30, 1994 and includes the capability of coding the ISUP Calling Partys Category parameter with the
38、 NS/EP code point (11100010) and setting the IAM priority level to 1. Priority call handling features, such as call/trunk queuing and exemption from network management controls, are based on recognizing the NS/EP code point. The normal POTS priority setting of 0 must be maintained in accordance with
39、 ANSI T1.111 in order for the GETS and WPS calls to have a higher probability of completion during SS7 congestion. Annexes A and B in Chapter T1.111.5 specify priority assignments for ISUP messages transferred between U.S. SS7 networks and establish engineering principles for priority assignment. Ta
40、ble A1/T1.111.5 requires that all IAMs be assigned priority level 0 with the exception that “Message priority level 1 shall be limited to those network services or capabilities that have been approved in ANSI T1 standards to have an IAM message priority of 1 (e.g., High Probability of Completion, Mu
41、lti-level Precedence and Preemption, Emergency Calling Service).“ Interconnecting networks should exchange their respective IAM priority assignments in conformance with T1.111 such that the priority assignment for normal POTS (non-emergency) IAMs are set to 0. The interconnecting participants are re
42、sponsible for performing the appropriate tests to verify such conformance. See Test 2.92. 1.4.2 ISUP IAM Precedence Parameter Testing The Precedence parameter is defined as an optional parameter within the SS7 ISUP IAM. Technical Report 3GPP TR 22.952 V6.3.0 (2005-09), Table A.2, defines how a Mobil
43、e Switching Center (MSC) uses the ISUP Precedence parameter to send WPS information across the PSTN to a terminating MSC. The ISUP Precedence parameter encoding is specified in ANSI T1.111.5. This parameter ensures that a “precedence level 1” call originated at an MSC will receive the same “preceden
44、ce level 1” treatment at a terminating MSC (i.e., queuing and servicing before “precedence level 2” and lower precedence level calls). Without transmission of the Precedence parameter, all terminating WPS calls have the same default priority and treatment. All switches are required to pass optional
45、parameters and values that they do not understand, such as the Precedence parameter (according to ANSI T1.113-1995, “American National Standard for Telecommunication Signaling System No. 7 (SS7) Integrated Service Digital Network (ISDN) User Part”). Interconnecting networks should verify transit swi
46、tches pass the Precedence parameter and WPS terminating switches establish a call based on the IAM with the Precedence parameter. See Test 2.93. 1.4.3 IAM Priority Level Mapping to IP SIP Priority Level The Government Emergency Telecommunications Service (GETS) and Wireless Priority Service (WPS) pr
47、ovides priority call completion to authorized users during times of network stress or congestion. As networks migrate to Internet Protocol (IP) based signaling, proper mappings between TDM and IP networks are imperative to the GETS and WPS mission. GETS and WPS will make use of the Session Initiatio
48、n Protocol (SIP) Resource Priority Header (RPH) in the IP domain. SIP RPH is an IEEE standard (RFC 4412). The IP mappings found in this document are based on the ATIS document PTSC-SAC-2007-060R2 and are valid as of February 2007. Test 7 scripts should be derived on a carrier by carrier basis using
49、frameworks 2.94, SIP INVITE to ISUP IAM Mappings, and 2.95, ISUP IAM to SIP INVITE Mappings, in this document along with the PTSC-SAC-2007-060R2. 8 NGIIF Test #: ANSI T1.236 Test #: TR-905 Test # 1.5 Circuit Validation Test (CVT) I-1.1 Circuit Validation Test (CVT) REFERENCE: ANSI T1.113, chapter 3, tables 6D, 18; ANSI T1.113, chapter 4, annex C.3 TITLE: Circuit Validation Test (CVT) PURPOSE: To verify the correct response to a CVT message. PRE-TEST CONDITIONS: A stable MTP signaling relation and the circuit (under test) exist between SP B and SP A. CONFIGURATION: 1
