ATIS 0300032-2015 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part X Interconnection Between LECS Operations Handbook C Local Interconnection Servic.pdf

《ATIS 0300032-2015 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part X Interconnection Between LECS Operations Handbook C Local Interconnection Servic.pdf》由会员分享，可在线阅读，更多相关《ATIS 0300032-2015 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part X Interconnection Between LECS Operations Handbook C Local Interconnection Servic.pdf（29页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0300032 ATIS Standard on - NEXT GENERATION INTERCONNECTION INTEROPERABILITY FORUM (NGIIF) REFERENCE DOCUMENT PART X, INTERCONNECTION BETWEEN LECS OPERATIONS HANDBOOK LOCAL INTERCONNECTION SERVICE ARRANGEMENT As a leading technology and solutions development organization, the Alliance for Telec

2、ommunications 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 servic

3、es, device 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,

4、 software 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 in

5、itiative, 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 of Disclaimer an exception is the provisioning of services assigned em

6、ergency 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 and restoration priority. When t

7、wo 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 with restoration priority of 2,

8、 3, 4, and 5. 10 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 priority and should be worked

9、 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 equipment are not available to

10、 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 priority level “E“ (Emerg

11、ency) or to provision an NS/EP service assigned a provisioning priority level “1“ through “5“. 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 circuits are available for publ

12、ic 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 the purpose of restoring t

13、he 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 suitable spare or non-N

14、S/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 who are preempting service

15、s 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. 11 4 NXX Code Openings1This section outlines the process and procedures for the testing of newly assigned Central Office NXX or NXX-X codes opened

16、for the first time. In addition, this section provides references for the user to ensure that they are 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

17、block that is opened in a NPA/NXX will follow the same rules as outlined in all NXX code opening procedures. 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

18、aspects contained in this section do not replace or supersede existing industry forum agreements or documents covering NXX or NXX-X Code opening processes. Listed below are specific documentation provided by the INC and NGIIF that provides guidance to Code Administrators, Service Providers and Servi

19、ce Customers when obtaining, activating, and testing NXX or NXX-X codes: Recommended Notification Procedures for Change in Access Network Architecture. Central Office Code (NXX) Assignment Guidelines, Industry Numbering Committee (INC) Document INC 97-0407-008. NGIIF Reference Document Part II, Inst

20、allation and Maintenance Responsibilities - Switched Access Services Feature Groups B, C, and D, and Part X, Interconnection Between LECs Operations Handbook - Local Interconnection Service Arrangement. ATIS-0300066, Thousands-Block Number (NXX-X) Pooling Administration Guidelines 4.1.1 NXX of NXX-X

21、 CO Code Activation Planning Service Providers requesting CO Code activation 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 ser

22、vice providers where the code is being opened to determine what types of interconnection 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 purpos

23、es. - Access Service Request (ASR) Form Preparation Guide (ATIS/OBF - ASR - 001) - Feature Group B, C, D (FG-B, C, D) Form Preparation Guide (ATIS/OBF - ASR - 004) - Translation Questionnaire (TQ) Form Preparation Guide (ATIS/OBF - ASR - 019) _ 1 Section 3 of ATIS-0300010, Part II, Installation and

24、Maintenance Responsibilities, Switched Access Services, Feature Group B, C, and D, of the NGIIF Reference Document, includes the same 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 Responsibil

25、ities, Switched Access Services, Feature Group B, C, and D, of the NGIIF Reference Document. 12 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: 4.2.1 BIRRDS Before a CO Code (NXX or NXX-X) can become ac

26、tive, 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 BIRRDS access for entry. 4.2.2 iconectiv LERG Routing Guide Dur

27、ing the process of entering the new CO Code (NXX or NXX-X) in the iconectiv LERG Routing Guide2, the code holder must identify the 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 p

28、urposes upon receipt of the CO Code and shall place the test number in the iconectiv LERG Routing Guide when entering the CO Code 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 i

29、n place shall contact the code holder and inform them that the routing of calls will not take place until the appropriate facility 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

30、 to ensure that the orders are completed 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 acce

31、pt full responsibility for placing such orders with the local exchange carrier (LEC) and schedule the Due Date for facilities testing. This will ensure that the facilities are in place prior to the date of the code opening identified in the iconectiv LERG Routing Guide. The LEC cannot be expected to

32、 meet the original effective date in the iconectiv LERG Routing Guide if all supporting information is not received in a timely manner. If interconnection already exists between service providers and a CO Code is being opened, the code holder shall provide appropriate routing information in the icon

33、ectiv LERG Routing Guide to inform other service providers with which they do not have direct interconnection. Where direct interconnection exists between service providers, it is presumed that all new CO Codes would be routed the same way as existing CO Codes, unless otherwise specified by the code

34、 holder in the ASR. _ 2LERG is a trademark of Telcordia Technologies dba iconectiv. 13 4.3 Translation Validation/Call through Testing The following process is outlined for the activation of new CO Codes (NXXs or NXX-Xs) to provide assurance that routing and billing translations are tested/validated

35、 appropriately by service providers and IXCs. The following information also includes activities for serving switch change or tandem rehome of switch serving CO Codes (NXXs or NXX-Xs) Upon receipt of notification (the iconectiv LERG Routing Guide) that a new CO Code is to be activated all service pr

36、oviders shall ensure the integrity of routing and billing by the effective date in the LERG. For established CO Codes where there is a change to the serving switch or a switch tandem rehome the service providers, not directly interconnected with the service provider making the changes, will ensure r

37、outing and billing changes on the LERG effective date. The service provider(s) directly interconnected and the service provider making the changes will negotiate a time as to when the translations changes will take place. The service provider assigned the new CO Code or implementing changes to the s

38、erving switch, or implementing a switch tandem rehome will provide a test number that terminates to a recorded announcement (preferable) or milliwatt (1004 Hz) to provide assurance to personnel performing call through tests that they have indeed reached the terminating (serving) office. Where billin

39、g is required, AMA validation shall take place by the service providers. 4.4 Intermediate Office(s) (Tandems/Access Tandems) Intermediate Office(s) are those in which InterLATA and IntraLATA calls are routed in an effort to reach someone in a newly opened CO Code (NXX or NXX-X). Intermediate Offices

40、 shall: Complete all translations work five (5) calendar days prior to the date identified in the iconectiv LERG Routing Guide as the effective date. Perform Call Through testing starting five (5) calendar days prior to the date identified in the iconectiv LERG Routing Guide as the effective date. I

41、dentify problems during call through testing, and resolve such problems prior to the effective date identified in the iconectiv LERG Routing Guide. For established CO Code(s) where there is a change to the serving switch or a switch tandem rehome, the service provider(s), not directly interconnected

42、 with the service provider making the changes, will ensure routing and billing changes are completed on the LERG effective date. The service provider(s) directly interconnected and the service provider making the changes will negotiate a time as to when the translations changes will take place. Test

43、ing will take place after the changes have been completed. 4.5 LEC Terminating Office (Serving Office) The LEC Terminating Office/serving office is the office where a call terminates. The LEC will: Validate that all translations work is complete five (5) calendar days prior to the date identified in

44、 the iconectiv LERG Routing Guide as the effective date. Perform Call Through tests to ensure that calls can be initiated from the newly opened CO Code (NXX or NXX-X) starting five (5) calendar days prior to the date identified in the iconectiv LERG Routing Guide as the effective date. An interLATA

45、or intraLATA call, and an intraoffice call to an existing CO Code, where applicable, should be performed within the serving office. Perform, where applicable, an intraoffice call from an existing CO Code within the serving office to the newly opened CO Code. Identify problems during call through tes

46、ting, and resolve such problems prior to the due date identified in the iconectiv LERG Routing Guide. 14 For established CO Code(s) where there is a change to the serving switch or a switch tandem rehome the service provider responsible for the terminating office will ensure routing and billing chan

47、ges are completed on the LERG effective date. The service provider responsible for the terminating office will negotiate with the interconnected service provider(s) as to the time when the translations changes will take place. NOTE: If the above functions are not performed, the originating office an

48、d intermediate office cannot perform their respective functions. 4.6 Originating Office LEC end offices with direct interconnection to, or located within the same NPA as the LEC with the newly opened CO Code (NXX or NXX-X), will: Validate that all translations work is complete five (5) calendar days

49、 prior to the date identified in the iconectiv LERG Routing Guide as the effective date. Initiate a call through test to the test number to ensure that the call routes correctly. Call through testing should start no earlier than five (5) calendar days prior to the date identified in the iconectiv LERG Routing Guide as the effective date. Identify problems during call through testing, and resolve such problems prior to the effective date identified in the iconectiv LERG Routing Guide. For established CO Code(s)