ATIS 0300065-2014 Location Routing Number (LRN) Assignment Practices (Reissued with the resolution of Issue 757).pdf

1、 ATIS-0300065 LOCATION ROUTING NUMBER (LRN) ASSIGNMENT PRACTICES Reissued with the resolution of Issue 757 September 5, 2014 Copyright 2014 by the Alliance for Telecommunications Industry Solutions, Inc. All rights reserved. The Location Routing Number (LRN) Assignment Practices dated September 5, 2

2、014 (former document number INC 98-0713-021) 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, withou

3、t the prior express written permission of 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. R

4、esale is prohibited. For ordering information, 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. ATIS is the leading technical planning and

5、 standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 250 companies actively formulate standards in ATIS 18 Committees, covering issues including: IPTV, Service Oriented Netw

6、orks, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, and Billing and Operational Support. In addition, numerous Incubators, Focus and Exploratory Groups address emerging industry priorities including “Green”, IP Downloadable Security, Next Generation Carrier Interconnect,

7、 IPv6 and Convergence. 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 a member of the Inter-American Telecommunicatio

8、n Commission (CITEL). For more information please visit . - The Industry Numbering Committee (INC) provides an open forum to address and resolve industry-wide issues associated with planning, administration, allocation, assignment and use of North American Numbering Plan (NANP) numbering resources w

9、ithin the NANP area. This document is maintained under the direction of ATIS and the INC. Suggestions for improvement of this document 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

10、 to this document shall be made through the INC issue resolution process and adopted by the INC as set forth in the ATIS Operating Procedures. - Notice of Disclaimer & Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degre

11、e of experience to understand and interpret its contents in accordance with generally 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

12、IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE 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

13、 AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT

14、 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 patent rights. By publication of this standard, no position is taken with respect to whether use of an invention covered by patent rights will

15、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. LRN Assignment Practices September 5, 2014 ATIS-0300065 1Location Routing Number Assignment Practices These practices are intended to assist Service Pr

16、oviders as 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 Systems Committee (formerly Committee T1S1) standards and the FCC North American Numbering Council Local Number Portability Administration Workin

17、g Group (LNPA WG) best practices1and some of that direction is incorporated in these practices. An LRN is a 10-digit number, in the format NPA-NXX-XXXX, that uniquely 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

18、 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 provisioned to identify each recipient switch or POI in the number portability capable network2. LRNs are to be used for routing and not for ratin

19、g/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 feature that records the LRN that a call is routed to in order to determine the appropriate provider serving that number for access billing purp

20、oses3. 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. Additional LRNs may be used for internal purposes. Further, additional LRNs are not required to identify US wireline rate centers. A uniqu

21、e LRN may be assigned to every LNP equipped switch or POI (and potentially to each CLLI4listed in the iconectiv LERG Routing Guide). Requesting an additional NXX to establish an LRN in certain instances may be justified but precautions need to be taken to ensure number resource optimization. The fol

22、lowing 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 code 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 no

23、t 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 order to establish an LRN for each subtending POI. Regulatory waivers granted to ILECs to carry local calls across a LATA boundary may exist.

24、 In such instances, SPs may be justified in establishing an additional LRN to properly route calls. 3. Remote switches that have a unique, assigned NPA-NXX also may have a unique LRN assigned to the remote switches5. 1See the LNPA WG pages at . 2ATIS PTSC Standard: Number Portability for Switching S

25、ystems ATIS-1000002, October, 2004 (documents available at the ATIS Document Center at www.atis.org may have an associated fee). 3See footnote 2. 4CLLI and LERG are trademarks of Telcordia Technologies, Inc. dba iconectiv. 5See footnote 2. LRN Assignment Practices September 5, 2014 ATIS-0300065 24.

26、The LRN must be selected and assigned from a valid NPA/NXX that has been uniquely assigned to the service 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

27、LRN from an NPA/NXX that is planned to be re-homed to another switch. Do not select and assign the LRN 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 telep

28、hone number as both an LRN for a switch and a working number for a customer. Do not assign any TLDN or 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.6 5. An LRN may have

29、 to be changed due to any of the following: switch replacements code moves or LERG reassignments NPA 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

30、, wherever possible, do not select and assign the LRN from an NPA that has been identified for area code relief. 7. The LRN will be published in the LERG Routing Guide7. LERG Routing Guide LRN records are used by some SPs for trouble shooting and network engineering purposes. Within five business da

31、ys of theassignment of an NXX that is to be used for LRN purposes, or when an LRN is assigned from an 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 m

32、aintain internal records of LRNs as a separate sub-category of “Administrative” in their TN inventories. (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 b

33、e selected and used by the Code Holder from its assigned/retained thousand block(s). 6An 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 i

34、t intends to retain. The porting of an LRN can cause call delivery failures. 7At 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.