1、 ATIS-0300065 LOCATION ROUTING NUMBER (LRN) ASSIGNMENT PRACTICES Reissued with the resolution of Issue 826 January 10, 2017 Copyright 2017 by the Alliance for Telecommunications Industry Solutions, Inc. All rights reserved. The Location Routing Number (LRN) Assignment Practices dated January 10, 201
2、7, is copyrighted, published and distributed by ATIS on behalf of the Industry Numbering Committee (INC). Except as expressly permitted, no part of this publication may be reproduced or distributed in any form, including electronic media or otherwise, without the prior express written permission of
3、ATIS. Participants in the INC and other parties are hereby authorized to reproduce this document and distribute it within their own business organizations for business purposes, provided that this notice continues to appear in the reproduced documentation. Resale is prohibited. For ordering informat
4、ion, please contact: ATIS 1200 G Street N.W., Suite 500 Washington, DC 20005 (202) 628-6380 incatis.org A complete listing of INC Documents is available on the ATIS Web Site at: http:/www.atis.org/inc/incguides.asp. As a leading technology and solutions development organization, the Alliance for Tel
5、ecommunications 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 serv
6、ices, 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 case
7、s, 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
8、initiative, 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. - The Industry Numbering Committee (INC) provides an open forum to address
9、and resolve industry-wide issues associated with planning, administration, allocation, assignment and use of North American Numbering Plan (NANP) numbering resources within the NANP area. This document is maintained under the direction of ATIS and the INC. Suggestions for improvement of this documen
10、t are welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, INC Staff, 1200 G Street NW, Suite 500, Washington, DC 20005. All changes to this document shall be made through the INC issue resolution process and adopted by the INC as set forth in the ATIS Operating Pr
11、ocedures. - Notice of Disclaimer & 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 engineering or other professional stan
12、dards 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 FURTHER, NO REPRESENTATION OR
13、WARRANTY IS MADE OFMERCHANTABILITY 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, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCID
14、ENTAL 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. NOTE - The users attention is called to the possibility that compliance with this standard may require use of an invention covered by
15、patent rights. By publication of this standard, no position is taken with respect to whether use of an invention covered by patent rights will be required, and if any such use is required no position is taken regarding the validity of this claim or any patent rights in connection therewith. Please r
16、efer to http:/www.atis.org/legal/patentinfo.asp to determine if any statement has been filed by a patent holder indicating a willingness to grant a license either without compensation or on reasonable and non-discriminatory terms and conditions to applicants desiring to obtain a license. LRN Assignm
17、ent Practices January 10, 2017 ATIS-0300065 1 Location Routing Number Assignment Practices These practices are intended to assist Service Providers1as to why Location Routing Numbers (LRNs) are necessary and how to select their own LRNs. The use of LRNs is covered in the ATIS Packet Technology Syste
18、ms Committee (formerly Committee T1S1) standards and the FCC North American Numbering Council Local Number Portability Administration Working Group (LNPA WG) best practices2and some of that direction is incorporated in these practices. An LRN is a 10-digit number, in the format NPA-NXX-XXXX, that un
19、iquely identifies a switch or point of interconnection (POI) per LATA. The NPA-NXX portion of the LRN is used to route calls to numbers that have been ported. The following LRN assignment criteria should be considered when a service provider selects and assigns an LRN: 1. A unique LRN will be provis
20、ioned to identify each recipient switch or POI in the number portability capable network3. LRNs are to be used for routing and not for rating/billing calls. Calls are rated and billed to an end-user based on the dialed digits and not on the LRN. There is, however an Automated Message Accounting feat
21、ure that records the LRN that a call is routed to in order to determine the appropriate provider serving that number for access billing purposes4. 2. A service provider will establish one (1) LRN per LATA from an assigned NXX for each recipient switch or POI in the number portability capable network
22、. Additional LRNs may be used for internal purposes. Further, additional LRNs are not required to identify US wireline rate centers. A unique LRN may be assigned to every LNP equipped switch or POI (and potentially to each CLLI5listed in the iconectiv LERG Routing Guide). Requesting an additional NX
23、X to establish an LRN in certain instances may be justified but precautions need to be taken to ensure number resource optimization. The following points should be considered prior to requesting a new NPA-NXX for the purpose of establishing an LRN: The requesting service provider uses an existing co
24、de already homed to the tandem where the LRN is needed for the POI. Once the NXX Code is assigned, the Code Holder must return any blocks not justified for retention in its inventory. When there are multiple tandems owned by different SPs in a single LATA, the requesting SP may obtain a new NXX in o
25、rder to establish an LRN for each subtending POI. Regulatory waivers granted to ILECs to carry local calls across a LATA boundary may exist. In such instances, SPs may be justified in establishing an additional LRN to properly route calls. 1The term “service provider” refers to a telecommunications
26、carrier or other entity that receives numbering resources from the NANPA, a Pooling Administrator or a telecommunications carrier for the purpose of providing or establishing telecommunications service. For the purposes of this part, the term “service provider” includes an interconnected VoIP servic
27、e provider (47 CFR 52.5 (e). 2See the LNPA WG pages at . 3ATIS PTSC Standard: ATIS-1000002, Number Portability for Switching Systems (documents available at the ATIS Document Center at www.atis.org may have an associated fee). 4See footnote 2. 5CLLI and LERG are trademarks of Telcordia Technologies,
28、 Inc. dba iconectiv. LRN Assignment Practices January 10, 2017 ATIS-0300065 2 3. Remote switches that have a unique, assigned NPA-NXX also may have a unique LRN assigned to the remote switches6. 4. The LRN must be selected and assigned from a valid NPA/NXX that has been uniquely assigned to the serv
29、ice provider by the Central Office Code Administrator and published in the LERG Routing Guide. An LRN should be selected and assigned with the following considerations: Do not select and assign the LRN from an NPA/NXX that is planned to be re-homed to another switch. Do not select and assign the LRN
30、 from an NPA/NXX that has a majority of the NXX numbers assigned to a single customer. Do not assign the LRN from an NPA/NXX that is assigned to the local choke network. Do not assign the same telephone number as both an LRN for a switch and a working number for a customer.7 Do not assign any TLDN o
31、r ESRD/ESRK wireless administrative number as an LRN. Do not select and assign the LRN from a block that otherwise may be eligible for donation to the thousands-block number pool.8 5. An LRN may have to be changed due to any of the following: switch replacements code moves or LERG reassignments NPA
32、Splits (as a result of an NPA-NXX split, a service provider may have to change their assigned LRN) Donation or return of the thousands-block containing the LRN 6. If a switch serves multiple NPA/NXXs, wherever possible, do not select and assign the LRN from an NPA that has been identified for area c
33、ode relief. 7. The LRN will be published in the LERG Routing Guide9. LERG Routing Guide LRN records are used by some SPs for trouble shooting and network engineering purposes. Within five business days of the assignment of an NXX that is to be used for LRN purposes, or when an LRN is assigned from a
34、n NXX already in an SPs inventory, the SP should forward a CO Code Part 2 Form 7 to its AOCN for input into Business Integrated Routing and Rating Database System (BIRRDS). 8. Service providers must maintain internal records of LRNs as a separate sub-category of “Administrative” in their TN inventor
35、ies (FCC 00-104 36 and 62, see also 47 CFR 52.15 (f) (1) (i). 9. Shared service provider NPA-NXXs should not be used for LRN assignments. 10. For thousands-block number pooling, the LRN shall only be selected and used by the Code Holder from its assigned/retained thousand block(s). 6See footnote 3.
36、7It should be recognized that there are some numbers that have been assigned as both a LRN and a working customer number, which is technically feasible. There is no requirement that those assignments be discontinued, including instances when the customer has ported the number to another service prov
37、ider. See ATIS-1000002, Number Portability Switching Systems. 8An SP can avoid the donation of blocks containing administrative numbers e.g., LRNs, Temporary Local Directory Numbers (TLDNs), Mobile Station Roaming Numbers (MSRN), by consolidating these numbers within blocks it intends to retain. The
38、 porting of an LRN can cause call delivery failures. 9At a minimum LRNs that are associated with ported and/or pooled records in the NPAC should be published in the LERG Routing Guide. Failure to publish LRNs in the LERG Routing Guide leads to confusion and more investigation time during the resolution process to determine to whom the LRN belongs.
