1、 ATIS-0300032 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part X, Interconnection Between LECS Operations Handbook Local Interconnection Service Arrangement Version 13.0 i As a leading technology and solutions development organization, the Alliance for Telecommunicati
2、ons Industry Solutions (ATIS) brings together the top global ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently working to address the All-IP transition, network functions virtualization, big data analytics, cloud services, device
3、 solutions, emergency services, M2M, cyber security, network evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use cases, software
4、toolkits, open source solutions, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global initiative,
5、a member of and major U.S. contributor to the International Telecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. Notice This document was developed by the Alliance for Telecommunications Industry Solu
6、tions (ATIS) sponsored 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
7、architecture, disaster 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 emergi
8、ng technologies. All changes 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
9、 Bellcore. The last version 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 genera
10、lly accepted engineering 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 RUL
11、E OR REGULATION, AND FURTHER 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 A
12、NY CLAIM, AND IN NO EVENT 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. Trademark Acknowledgements iconectiv, Telcordia, and Com
13、mon Language are registered trademarks and CLCI, CLLI, LERG Routing Guide and TPM Data Source are trademarks and the Intellectual Property of Telcordia Technologies, Inc. dba as iconectiv. ATIS-0300032, NGIIF Reference Document, Part X, Interconnection Between LECS Operations Handbook Local Intercon
14、nection Service Arrangement, Formerly NIIF 5028 The NGIIF Reference Document, Part X, Interconnection Between LECS Operations Handbook Local Interconnection Service Arrangement, is an ATIS standard developed by the NGIIF. ii Published by Alliance for Telecommunications Industry Solutions 1200 G Stre
15、et, NW, Suite 500 Washington, DC 20005 Copyright 2018 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For infor
16、mation contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. iii Table of Contents 1 GENERAL .1 2 RESPONSIBILITIES .1 2.1 LOCAL SERVICE CUSTOMER (LSC) .1 2.2 LOCAL SERVICE PROVIDER (LSP) .2 3 TELECOMMUNICATION SERVICE PRIORITY (TSP) GUIDELINES .3 3.1 DOMESTIC NS/
17、EP SERVICES. .3 3.2 CONTROL SERVICES AND ORDERWIRES .3 3.3 OTHER SERVICES .4 3.3.1 TSP Code Identification 4 3.4 TSP INSTALLATION .5 3.5 TSP MAINTENANCE 5 3.5.1 Example 1 .5 3.5.2 Example 2 .6 3.6 COMPETITION FOR RESOURCES BETWEEN PROVISIONING AND RESTORATION PRIORITIES .6 3.7 TSP INSTALLATION PREEM
18、PTION 6 3.8 TSP MAINTENANCE PREEMPTION .7 3.8.1 To restore interrupted NS/EP services: 7 3.8.2 NS/EP services .7 4 NXX CODE OPENINGS 7 4.1.1 NXX of NXX-X CO Code Activation Planning .8 4.2 PRE-NXX OR NXX-X ACTIVATION .8 4.2.1 BIRRDS.8 4.2.2 iconectiv LERG Routing Guide .9 4.2.3 Facilities 9 4.2.4 Po
19、ints of Interconnection 9 4.3 TRANSLATION VALIDATION/CALL THROUGH TESTING 9 4.4 INTERMEDIATE OFFICE(S) (TANDEMS/ACCESS TANDEMS) 10 4.5 LEC TERMINATING OFFICE (SERVING OFFICE) . 10 4.6 ORIGINATING OFFICE . 11 4.7 MECHANIZED TESTING . 11 4.8 VERIFICATION OF NXX OR NXX-X CODE OPENINGS, SWITCH CHANGE/RE
20、HOME, OR SWITCH TANDEM REHOME PROCESS . 11 4.9 NXX OR NXX-X CODE OPENING, SWITCH CHANGE/REHOME, OR SWITCH TANDEM REHOME PROCESS IN JEOPARDY SITUATIONS . 11 5 TRUNK INSTALLATION . 12 5.1 PRE-SERVICE TESTING 12 5.2 ACCEPTANCE TESTING 12 5.3 ADDITIONAL COOPERATIVE ACCEPTANCE TESTING . 14 5.4 TRAFFIC RO
21、UTING AND BILLING ACCEPTANCE TESTING . 14 5.5 COMPLETION . 15 5.6 EXPEDITES 15 5.7 TRUNK DISCONNECTS 15 5.8 TRUNK REARRANGEMENTS 15 5.9 COORDINATED CONVERSION 15 6 TRUNK MAINTENANCE . 16 iv 6.1 TROUBLE DETECTION RESPONSIBILITIES 16 6.2 SECTIONALIZATION 17 6.3 TROUBLE REPORTING 17 6.4 REPAIR VERIFICA
22、TION 18 6.5 NON-TRUNK SPECIFIC TROUBLES 18 6.6 TROUBLE REPORT CLEARING INFORMATION 18 6.7 PRIORITY OF RESTORATION . 19 6.8 MAKE-BUSY PROCEDURES 19 6.9 RESTORATION . 19 6.10 HOLD AND TRACE TROUBLE ISOLATION 19 6.11 CALL TRACES 20 6.12 NETWORK MODIFICATION . 20 6.12.1 Network Modification Suspension P
23、eriods 21 6.13 LEC-LEC NON-TRUNK OPERATIONAL AGREEMENTS 21 6.13.1 Line Identification/Verification 21 7 EXCEPTIONS 22 7.1 LINE IDENTIFICATION/VERIFICATION 22 7.2 CALLING PARTY NUMBER (CPN), CALLING PARTY NAME (CNAM) . 22 7.2.1 Calling Party Number (CPN) 22 7.2.2 Linking CPN an exception is the provi
24、sioning of services assigned emergency priority, which should always be done before the restoration of services assigned restoration priorities “2“, “3“, “4“ or “5“. Restoration of any service assigned restoration priority “1“ takes precedence over any other service assigned any other provisioning a
25、nd restoration priority. When two or more TSP services are competing for resources, the priority sequence listed below will ensure proper handling of these circuits: Restore TSP services with restoration priority of “1” Provision TSP services with provisioning priority of “E” Restore TSP services wi
26、th restoration priority of 2, 3, 4, and 5 Provision TSP services with provisioning priority of 1, 2, 3, 4, and 5. Using the priority sequence listed above, the following are examples of two TSP services competing for the same resources at the same time. The underlined TSP service has the higher prio
27、rity and should be worked on first: TSP code 2-1 and E-2 both in trouble status 2-1 TSP code 2-1 in trouble and E-2 to be provisioned 2-1 TSP code 2-1 to be provisioned and E-2 in trouble E-2 TSP code 2-1 and E-2 to be provisioned E-2. 3.7 TSP Installation Preemption Where facilities and/or equipmen
28、t are not available to install a service assigned a TSP priority, preemption (interruption of an existing service) of a non-priority or lower priority circuit may be required. User consent is NOT required to preempt any users existing service to provision an NS/EP service assigned a provisioning pri
29、ority level “E“ (Emergency) or to provision an NS/EP service assigned a provisioning priority level “1“ through “5“. 7 3.8 TSP Maintenance Preemption Facilities of message circuits may be used for restoral of services assigned a TSP restoration priority after ensuring that sufficient message circuit
30、s are available for public switched network use. Where facilities and/or equipment are not available to restore a service assigned, a TSP restoration priority preemption (interruption of an active service) may be required. Interruption of a non-priority or lower priority circuit is authorized for th
31、e purpose of restoring the service assigned a TSP restoration priority. 3.8.1 To restore interrupted NS/EP services: User consent is not required to preempt any users existing service to restore any NS/EP service assigned a restoration priority lever from “1“ through “5“. 3.8.2 NS/EP services: If no
32、 suitable spare or non-NS/EP services are available, existing NS/EP services may be preempted to restore NS/EP services with higher priority level assignments. When this is necessary, NS/EP services will be selected for preemption in the inverse order of priority level assignment. Service vendors wh
33、o are preempting services will ensure their best effort to notify the service user of the preempted service and state the reason for, and estimated duration of, the preemption. 4 NXX Code Openings1 NOTE: For information related to NPA-NXX testing refer to ATIS-0300024, Next Generation Interconnectio
34、n Interoperability (NGIIF) Reference Document Part V, Test Line Guidelines. This section outlines the process and procedures for the testing of newly assigned Central Office NXX or NXX-X codes opened for the first time. In addition, this section provides references for the user to ensure that they a
35、re familiar with the obligations associated with obtaining codes and notifying the industry of the pending opening of CO NXX codes. In a Thousands Block Number Pooling environment the first thousands block that is opened in a NPA/NXX will follow the same rules as outlined in all NXX code opening pro
36、cedures. NPA/NXX and NPA/NXX-X are interchangeable in NXX code opening scenarios throughout the NGIIF documentation. In these cases the Code Holder is responsible for the testing. The non-operational aspects contained in this section do not replace or supersede existing industry forum agreements or
37、documents covering NXX or NXX-X Code opening processes. Listed below are specific documentation provided by the Industry Numbering Committee (INC) and NGIIF that provides guidance to Code Administrators, Service Providers and Service Customers when obtaining, activating, and testing NXX or NXX-X cod
38、es: ATIS-0300046, Recommended Notification Procedures to Industry for Changes in Access Network Architecture. _ 1 Section 3 of ATIS-0300010, Part II, Installation and Maintenance Responsibilities, Switched Access Services, Feature Group B, C, and D, of the NGIIF Reference Document, includes the same
39、 information on NXX Code Openings. Any changes to this section should also be reflected in Section 3 of ATIS-0300010, Part II, Installation and Maintenance Responsibilities, Switched Access Services, Feature Group B, C, and D, of the NGIIF Reference Document. 8 ATIS-0300051, Central Office Code (NXX
40、) Assignment Guidelines (COCAG) ATIS-0300010, Next Generation Interconnection Interoperability (NGIIF) Reference Document: Part II, Installation and Maintenance Responsibilities Switched Access Services Feature Group B, C, and D ATIS-0300032, Next Generation Interconnection Interoperability (NGIIF)
41、Reference Document: Part X, Interconnection Between LECS Operations Handbook Local Interconnection Service Arrangement ATIS-0300066, Thousands-Block Number (NXX-X) Pooling Administration Guidelines (TBPAG). 4.1.1 NXX of NXX-X CO Code Activation Planning Service Providers requesting CO Code activatio
42、n where the code involves the use of newly established switching facilities or additional interconnection trunking should perform the following prior to call through testing: Set up a planning session with the appropriate service providers where the code is being opened to determine what types of in
43、terconnection arrangements are required. Issue Service Orders (SO) to establish the appropriate facilities using the Access Service Request (ASR) and or translations using the Translation Questionnaire (TQ) for routing purposes.2 Access Service Request (ASR) Form Preparation Guide (ATIS/OBF - ASR -
44、001) Trunking Service Request Form Preparation Guide. (ATIS/OBF - ASR - 004) Translation Questionnaire (TQ) Form Preparation Guide (ATIS/OBF - ASR - 019). 4.2 Pre-NXX or NXX-X Activation The following reference is provided to aid in the performance of activation and testing of CO NXX or NXX-X Codes:
45、 4.2.1 BIRRDS Before a CO Code (NXX or NXX-X) can become active, the service provider requesting a new CO Code is responsible for either directly inputting the information in Part 2 of the CO Code Assignment Request form into BIRRDS, providing it to the Code Administrator, or another party with BIRR
46、DS access for entry. _ 2 Access Service Ordering Guidelines (ASOG), available at https:/www.atis.org/docstore/product.aspx?id=28359 9 4.2.2 iconectiv LERG Routing Guide During the process of entering the new CO Code (NXX or NXX-X) in the iconectiv LERG Routing Guide the code holder must identify the
47、 points of interconnection in the LATA where the CO Code resides. In addition, the code holder shall immediately assign a number to be utilized for call through testing purposes upon receipt of the CO Code and shall place the test number in the iconectiv LERG Routing Guide when entering the CO Code
48、into the iconectiv LERG Routing Guide. 4.2.3 Facilities Offices attempting to complete a call through test to the new CO Code (NXX or NXX-X) when the facilities are not in place shall contact the code holder and inform them that the routing of calls will not take place until the appropriate facility
49、 orders have been completed. In cases where orders have been placed with LECs for facilities, but have not been implemented, the LEC shall provide the appropriate support to ensure that the orders are complete and appropriate testing has been performed to meet the due date. 4.2.4 Points of Interconnection In cases where points of interconnection in the home NPA have not been identified and/or facilities have not been placed, the code holder (NXX or NXX-X) will accept full responsibility for placing such orders with th
