1、 ATIS-0300046 ATIS Standard on - NEXT GENERATION INTERCONNECTION INTEROPERABILITY FORUM RECOMMENDED NOTIFICATION PROCEDURES TO INDUSTRY FOR CHANGES IN ACCESS NETWORK ARCHITECTURE As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (A
2、TIS) 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 solutions, emergency ser
3、vices, 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 toolkits, open source sol
4、utions, 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, a member of and major U.S
5、. 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 Switch reconfigurations affecting rating or routing; New or changed NXX, including new and
6、existing NXXs designated as portable; New or changed NPA; Changes in rate centers. ATIS-0300046 1 Historical Reference ICCF 92-0726-004: Submitted by The Independent Telephone Company Network Reconfiguration Committee Accepted and Approved at ICCF16, March 1989 ICCF 92-0726-004 Revision 1: Submitted
7、 by The Data Integrity Group Accepted and Approved at ICCF22, March 1991 ICCF 92-0726-004 Revision 2: Accepted and Approved at the January 5, 1996, Emergency ICCF meeting in connection with resolution of ICCF Issue #284, “CO Code Activation Time Frame.” NIIF Issue #0092: The NIIF has taken ownership
8、 of ICCF 92-0726-004 due to the sunset of the ICCF. The document is being reissued as the resolution to NIIF Issue #0092: Updates to “Recommended Notification Procedures to Industry” document. NIIF Issue #0092 went to final closure on 8/19/98. NIIF Issue #0282 The document is being reissued as the r
9、esolution to NIIF Issue #0282, Update ATIS-0300046, Recommended Notification Procedures to Industry for Changes in Access Network Architecture. Trademark Information CLLI and LERG are trademarks of Telcordia Technologies dba iconectiv ATIS-0300046 2 Table of Contents 1 INTRODUCTION 3 2 BUSINESS RELA
10、TIONSHIPS . 3 3 LEC-I REQUEST TO LEC-A FOR INFORMATION 3 4 LEC-A RESPONSE TO LEC-I REQUEST FOR INFORMATION . 4 5 LEC-I PRELIMINARY NOTIFICATION TO ACCESS CUSTOMER 4 6 ACCESS CUSTOMER RESPONSE TO LEC-IS PRELIMINARY NOTIFICATION . 5 7 LEC-I FORMAL WRITTEN NOTIFICATION TO LEC-A AND ACCESS CUSTOMERS 5 8
11、 BIRRDS AND NECA TARIFF FCC NO. 4 UPDATE RESPONSIBILITY 6 9 RECEIPT OF FORMAL BIRRDS NOTIFICATION BY ACCESS CUSTOMERS 6 10 BLOCKING NOTIFICATION TO ACCESS CUSTOMERS 7 11 PROBLEM RESOLUTION . 7 12 IMPLEMENTATION OF ROUTING CHANGES . 8 ATTACHMENT A FLOW CHART 9 ATTACHMENT B 10 B.1 BIRRDS MINIMUM TIME
12、INTERVALS 10 ATIS-0300046 3 1 Introduction The following are recommended methodologies for all Local Exchange Carriers (LECs) to provide for timely notification to the Industry of changes in their access network architecture. These recommended methodologies should apply to any access network reconfi
13、guration that affects Access Customer routing or rating of calls such as: Tandem homing arrangements. Switch reconfigurations affecting rating or routing. New or changed NXX, including new and existing NXXs designated as portable. New or changed NPA Changes in rate centers. Attachment A is a flow ch
14、art of the recommended notification procedures to the Industry for changes in access network architecture. Each of the steps in the flow chart is explained in the paragraphs that follow. These procedures were prepared for the situation where any Local Exchange Carrier (LEC), initiates an access netw
15、ork reconfiguration that affects another Local Exchange Carrier(s). This document outlines the recommended notification procedures to the Industry for changes in access network architecture as established by the Network Generation Interconnection Interoperability Forum (NGIIF). It is intended to be
16、a living document to aid operations work forces. It does not replace nor supersede Tariffs, Contracts or any other legally binding documents. Key: LEC-I = LEC which initiates the change LEC-A = LEC which is affected by the change IC = Interexchange Carrier 2 Business Relationships a) All LECs are re
17、sponsible for their individual business relationship with Access Customers. b) The Company initiating the change (in this case, the LEC-I) is responsible for notification (as outlined herein) to the Industry of changes in its network architecture. 3 LEC-I Request to LEC-A for Information At the time
18、 a decision is made to make a change, the LEC-I initiating the change writes the LEC-A to: a) Preliminarily advise LEC-A of its planned changes. ATIS-0300046 4 b) Advise LEC-A of the estimated due date for each change, even though LEC-I may not have negotiated due dates with Access Customers. c) Det
19、ermine if LEC-A has any problems with completing the change in the time frames suggested by LEC-I. d) Request that LEC-A provide LEC-I with contact information for all Access Customers that deliver traffic to the affected LEC-A tandem when the request involves a tandem homing arrangement or other ch
20、anges that require Access Customer contact. LEC-I should not request a listing of Access Customers from their State PUC/PSC, for the purpose of notification, as this would leave out many non-IC Access Customers not shown on the PUC/PSC list. 4 LEC-A Response to LEC-I Request for Information In respo
21、nse to the LEC-Is request for information, LEC-A responds in writing to the LEC-I to: a) Provide the LEC-I with a list of Access Customers that deliver traffic to LEC-As affected tandem. Access Customers contact name and telephone number should be shared if available. b) Advise LEC-I if LEC-A has an
22、y problem with completing the changes in the time frame recommended by LEC-I, and suggest alternate dates if appropriate. 5 LEC-I Preliminary Notification to Access Customer LEC-I contacts in writing each affected Access Customer as soon as possible as indicated below. For cutover of an access or Fe
23、ature Group B tandem, it is recommended that preliminary notification occur twenty months in advance of the estimated effective date. Specific intervals for reflecting this information in the iconectiv Business Integrated Routing and Rating Database System (BIRRDS) that is maintained by iconectiv Te
24、lecom Administration (TRA) are contained in Attachment B. a) Preliminarily advise Access Customers of desired change. LEC-I can obtain Access Customer contact information through its normal relationship with the Access Customer, LEC-A and national or state telephone associations. b) Negotiate desire
25、d due date with Access Customers for access service changes. Minimum time intervals for entering information into BIRRDS associated with network changes are included in Attachment B. These intervals should be from the time the proposed changes would be entered into the iconectiv BIRRDS system. The d
26、ate recommended by an LEC-I should allow the minimum interval shown in Attachment B to be met. If all Access Customers, LEC-Is and LEC-A(s) affected by the change cannot agree on a change date, the individual Access Customers, LEC-I and LEC-A(s) may negotiate a different date. Additional information
27、 on such procedures is provided below in paragraph 10.c. LEC I may have an exceptional situation that does not allow the minimum activation interval to be met, which is 45 calendar days for Central Office Codes. For exceptions to this interval, please see Attachment B, paragraph 4 of this document.
28、ATIS-0300046 5 6 Access Customer Response to LEC-Is Preliminary Notification Access Customers advise LEC-I if they have any problem with completing the changes in the time frame suggested by LEC-I, and suggest alternate dates if appropriate. 7 LEC-I Formal Written Notification to LEC-A and Access Cu
29、stomers LEC-I reviews the information it has received from the LEC-A and Access Customers, and: a) Writes LEC-A to: 1) Formally advise LEC-A as to what is being changed, added or disconnected. 2) Provide the effective date and time for each change. 3) Authorize LEC-A to make the necessary changes. 4
30、) State that it has notified all affected Access Customers of the recommended effective date. LEC-Is letter should list: i) All affected Access Customers. ii) Effective date and time for each Access Customer. iii) Reasons for any Access Customer taking exception to the recommended effective date and
31、 time. iv) If applicable, date and time end office NXX blocking should occur at LEC-As affected tandem. v) If applicable, provide indication for permissive routing with end date and time. 5) Where appropriate, request LEC-A to enter the necessary information into BIRRDS to formally notify the Access
32、 Customers of the pending changes. (See paragraph 7.a following). 6) Provide LEC-Is contact name and telephone number for any questions. b) Writes Access Customers to: 1) Formally advise the FG B or D Access Customers as to what is being changed, added or disconnected, including NPA-NXXs, associated
33、 end office and old and new tandem CLLI Codes, new homing arrangements and any other information deemed necessary. 2) Provide the effective date and time for each change. 3) Where applicable, provide date and time when blocking should occur. 4) Where applicable, provide indication for permissive rou
34、ting with end date and time. 5) Provide LEC-Is contact name and telephone number for any questions. ATIS-0300046 6 The above should be communicated to the LEC-A(s) and Access Customers to allow sufficient time for planning and ordering of access services, construction, updating of BIRRDS, etc., to p
35、roceed on schedule. 8 BIRRDS and NECA Tariff FCC NO. 4 Update Responsibility a) Business Integrated Routing and Rating Database System (BIRRDS) LEC-I formally notifies all affected Access Customers of the pending changes. This notification is accomplished by LEC-I or LEC-A through updates to the ico
36、nectiv TRA BIRRDS database as follows: 1) LEC-I provides its own “on-line” access to BIRRDS (iconectiv will provide the necessary training to the LEC-I to accomplish this). A letter of release by LEC-A and a letter of acceptance by LEC-I are required by Telcordia TRA before “on-line” access will be
37、allowed. LEC-I is responsible for updating BIRRDS in sufficient time to meet the minimum intervals outlined in Attachment B, or 2) LEC-I channels its information to LEC-A, another LEC or other agent, where, if mutual agreement exists, the information is inputted into BIRRDS for LEC-I. If another LEC
38、 or agent is used, a letter as described above is required. LEC-I is responsible for providing the updates to LEC-A, other LEC or other agent in sufficient time to meet the minimum intervals outlined in Attachment B. The information required to be placed into BIRRDS is contained in ATIS-0300051, Cen
39、tral Office Code (NXX) Assignment Guidelines (COCAG). This information includes switch, switch homing, destination code, rate center and locality information. b) NECA TARIFF FCC NO. 4 LEC-I and LEC-A should update NECA Tariff FCC No. 4 to reflect changes in wire center and billing percentage informa
40、tion resulting from network rearrangements. The effective dates of changes made in the NECA Tariff FCC No. 4 should coincide as closely as possible with the effective dates input to BIRRDS, from which the iconectiv LERG Routing Guide1is generated. 9 Receipt of Formal BIRRDS Notification by Access Cu
41、stomers a) Network change information is available through access to BIRRDS or through BIRRDS output that is designed to identify such changes. BIRRDS output is available from Telcordia Technologies via: 1) On-line access to BIRRDS. 2) iconectiv LERG Routing Guide as issued monthly, distributed on C
42、D-ROM, available through web download, and via direct bulk data transfer. 3) A LERG daily download is also available from iconectiv TRA for subscribers to the monthly services listed in item 2 above. _ 1LERG is a trademark of Telcordia Technologies dba iconectiv. ATIS-0300046 7 b) Emergency Notifica
43、tions (ENs) are available through iconectiv for emergency situations where notification of any new code, rating change or hard to reach code must be made in less than 45 days. Emergency notifications are issued on an as needed (minimum weekly) basis, and distributed to all emergency notification sub
44、scribers via e-mail. c) 45 calendar days is the minimum activation interval for Central Office Codes. The 45 calendar day activation interval starts immediately after the NXX Central Office Code is entered into BIRRDS. For exceptions where an activation interval less than 45 calendar days is request
45、ed, see Attachment B, paragraph 4 of this document. 10 Blocking Notification to Access Customers Where blocking is to occur, LEC-A issues a blocking notification in writing to Access Customers. a) This notification should be an “All Users of Access” letter or a letter to individual Access Customers
46、and should provide the following information: 1) Tandem blocking date and time identified in paragraph 6.a.4 preceding. 2) NPA-NXXs involved. 3) A permissive routing notation indicating that traffic can continue to be routed through the losing tandem/end office for the annotated period. This allows
47、troubles encountered during cutover to be corrected. 4) LEC-As contact name and telephone number for any questions. b) Issuance of this blocking notification letter does not replace the requirement on LEC-I to formally notify Access Customers as indicated above in Section 6 and 7. 11 Problem Resolut
48、ion When problems that would delay the effective date for the proposed change (such as equipment changes, discrepancies between written notification and BIRRDS, or other actions) occur after the formal notification has been entered into BIRRDS, the following steps should be taken: a) The LEC-A(s) or
49、 Access Customer(s) experiencing the problem should first contact the LEC-I and discuss the problem. b) The LEC-I that initiated the network arrangement should coordinate with all involved Access Customers and affected LECs to resolve the issue. c) If a change in the effective date for the network rearrangement is necessary, the notification procedures described in the preceding paragraphs should be repeated as appropriate to institute a new effective date. This may include negotiating temporary alternate routing schemes on an individual case
