1、 ATIS-0300089 P-ANI Administration Guidelines Reissued with the resolution of Issue 847. March 2, 2018 2 Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2018 by Alliance for Telecommunications Industry Solutions All rights r
2、eserved. 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 information contact ATIS at 202.628.6380. ATIS is online at . Participants in the INC and other parties are hereby authorized
3、 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. A complete listing of INC Documents is available on the ATIS Web Site at: http:/www.atis.o
4、rg/inc/incguides.asp. 3 As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (ATIS) brings together the top global ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currentl
5、y working to address the All-IP transition, 5G, network functions virtualization, big data analytics, cloud services, device solutions, emergency services, M2M, cyber security, network evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track dev
6、elopment lifecycle from design and innovation through standards, specifications, requirements, business use cases, software toolkits, open source solutions, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Or
7、ganizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global 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 m
8、ore information, visit www.atis.org. - 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 within the NANP area.
9、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 to this document sha
10、ll be made through the INC issue resolution process and adopted by the INC as set forth in the ATIS Operating Procedures. The INC wishes to acknowledge the cooperation of the ATIS Emergency Services Interconnection Forum (ATIS ESIF) in the development of these Guidelines. - Notice of Disclaimer Sep.
11、 8, 2006; http:/ 3Only those users with a valid profile will be permitted to submit applications or changes on behalf of an Eligible User. 4The INC shall not designate the central office code “911” for use as a p-ANI resource because NPA-911-XXXX may continue to be used to represent a problem condit
12、ion at the PSAP. 6 Safety Answering Point (PSAP). While the ultimate delivery of any call to a PSAP must be based upon the geographic location of the caller, by necessity the association of the geographical location of the callers telephone number and the p-ANI is typically made using the Selective
13、Routing Data Base (SRDB). In instituting these guidelines, all entities formerly assigning p-ANI resources will discontinue such practices and transition administration and control of formerly assigned non-dialable p-ANIs to the RNA in accordance with schedules and deadlines mutually set between the
14、 affected entities and the RNA. These guidelines do not supersede appropriate North American Numbering Plan (NANP) area governmental or regulatory principles, procedures, and requirements. For interpretation of these guidelines, see Section 9.0. 2.0 Assumptions and Constraints The development of the
15、se non-dialable p-ANI administration guidelines is based on the following assumptions and constraints: 2.1 P-ANI resources covered in these guidelines are collectively managed by the telecommunications industry with oversight by the appropriate governmental agency in areas served by the NANP. 2.2 Th
16、e RNA will obtain the necessary Eligible User documentation to establish and administer the p-ANI resources. 2.3 The p-ANI resources are considered a public resource and are not owned by the p-ANI Assignees or the RNA. Consequently, the resources cannot be sold, brokered, bartered, or leased by the
17、p-ANI Assignee for a fee or other consideration. If a resource is sold, brokered, bartered, or leased for a fee, the resource is subject to reclamation (See Section 8.0). 2.4 These guidelines apply only to the assignment of p-ANI resources to Eligible Users for use in 9-1-1 selective routing systems
18、 and/or for E9-1-1 display purposes. 2.5 P-ANI resources shall be assigned to facilitate the most effective and efficient use of a finite numbering resource in order to prevent premature exhaust of p-ANI resources. 2.6 Each individual NPA is considered a separate pool of p-ANI numbers even in cases
19、where an NPA overlay situation exists because of technical limitations (e.g. many selective routers can only support a maximum of four NPAs). 2.7 A p-ANI Applicant requesting resources from the p-ANI inventory: 7 a) shall provide, as part of its application for p-ANIs, evidence demonstrating that th
20、e p-ANI Applicant is an Eligible User of p-ANI resources. An Eligible User is defined as an entity that: 1) Demonstrates that it is permitted under applicable law to access p-ANI resources in the area for which the p-ANI resources are sought; A wireless service provider applicant shall provide the R
21、NA a copy of its FCC license, showing that it is authorized to provide service in the area in which it is seeking resources. In the case that the name on the license does not match the SPs name on the application, the applicant shall provide documentation linking the name on the application with the
22、 name on the license. If a wireless service provider provides a non-exclusive 3650-3700 MHz Radio Service nationwide license, it shall also provide a 3650-3700 MHz Service Registration Acceptance Letter from the FCC to establish both that it has registered fixed sites and base stations, and the loca
23、tion of those sites. Any entity that requires p-ANIs to comply with any state or federal order and that has been certified as a CLEC by a state shall provide the RNA a copy of its state certification showing that it is authorized to provide service in the area in which it is seeking resources.5In th
24、e case that the name on the CPCN does not match the SPs name on the application, the applicant shall provide documentation linking the name on the application with the name on the CPCN. An interconnected VoIP service provider applicant shall provide the RNA with a copy of its FCC nationwide authoriz
25、ation6. A VPC provider applicant shall provide documentation from the state or the states general counsel in the form of7: 1. An order of the commission denying certification, with the reason for the denial being that the state does not certify VPC providers, or 2. A statement from the state commiss
26、ion or its general counsel that it does not certify VPC providers. The RNA will then retain this information in its records for that VPC providers future requests for that specific state. 2) Has received approval from the 9-1-1 governing authority to route E9-1-1 traffic for termination to a Public
27、Safety Answering Point (PSAP)8; _ 5See Implementation of the NET 911 Improvement Act of 2008, FCC 08-249, at Footnote 66: citing 47 CFR 52.15(g)(2); see also Footnote 84. 6FCC 15-70, 14 and 47 CFR 52.15(g)(3). 747 CFR 52.15(g)(2). 8December 14, 2010, letter from the Wireline Competition Bureau Chief
28、 to the NANC Chair and the Director of Number Pooling Services. 8 3) Has been assigned a valid Operating Company Number (OCN)9. The OCN must be associated with a NECA Company Code (OCN) Category Type that has been determined to be appropriate for the direct assignment of numbering resources. The fol
29、lowing is the list of permitted Company Code Category Types for numbering resources: Incumbent Local Exchange Carrier ILEC Regional Bell Operating Company RBOC Competitive Local Exchange Carrier CLEC Personal Communications Service PCS Unbundled Local Exchange Carrier ULEC Wireless Carriers WIRE Int
30、ernet Provider Enabled Services IPES (only interconnected VoIP) The RNA will deny all numbering applications from SPs with an OCN category that is not permissible for numbering assignments. 4) Has been assigned a valid NENA Company Identifier (ID) 1 by the National Emergency Number Association (NENA
31、)10; and 5) Self-certifies that it will provide the technical and functional capability to route traffic or provide routing instructions to enable emergency call delivery to a PSAP. b) shall establish internal policies and practices that provide for the efficient use and assignment of p-ANIs. 2.8 Th
32、e schedule of holidays recognized by the RNA will affect the administration of these guidelines. Holidays posted on the RNA website will not be considered a “business day” as a part of any timing of p-ANI allocation(s) in association with these guidelines. 2.9 P-ANI Assignees and the RNA are respons
33、ible for managing p-ANI resources in accordance with these guidelines and the orders of the appropriate governmental agency. Both p-ANI Assignees and the RNA are subject to audits. 2.10 Audits of the RNA and p-ANI Assignees may be performed by the appropriate bureau(s) within the FCC or other approp
34、riate governmental agency, or other designated agents to: a) ensure uniformity in application of these guidelines by the RNA to all p-ANI requests received by the RNA; b) ensure compliance with these guidelines by p-ANI Assignees and the RNA; and _ 9See Glossary. 10See Glossary. 9 c) ensure the effi
35、cient and effective use of p-ANIs by p-ANI Assignees and efficient and effective management of p-ANI resources by the RNA. 3.0 P-ANI Assignment Principles The following assignment principles apply to all aspects of these guidelines: 3.1 The RNA will assign individual p-ANIs or p-ANI ranges from the
36、established p-ANI inventory. P-ANIs will be available for assignment from both the 211 central office code (or “NXX”) and 511 NXX initially. For purposes of this provision, a p-ANI is “not available for assignment,” if it is classified as: a) Aging b) Assigned c) Unavailable as defined in the Glossa
37、ry. 3.2 P-ANIs are assigned uniquely to individual Eligible Users in contiguous ranges (where possible). However, the RNA cannot guarantee that all p-ANIs will be assigned in contiguous ranges. 3.3 P-ANI resources in the p-ANI inventory shall be available and allocated to Eligible Users in a fair an
38、d non-discriminatory manner (i.e., on a first come, first served basis). 3.4 Information that is submitted by p-ANI Applicants in support of a p-ANI assignment shall be kept to a minimum, be uniform for all applicants, and be treated as proprietary and adequately safeguarded by the RNA, pursuant to
39、FCC confidentiality rules.113.5 P-ANIs are assigned for use by a selective routing system for which the Eligible User has approval to route E9-1-1 traffic for termination to a PSAP. 3.6 NPA-211-XXXX and NPA-511-XXXX formats will be used for p-ANI assignment. The NPA of the p-ANI shall coincide with
40、an NPA valid for the serving selective routing system. P-ANIs shall be considered non-dialable in the Public Switched Telephone Network (PSTN). 3.7 Any Eligible User that is denied the assignment of one or more p-ANIs under these guidelines has the right to appeal that decision, per Section 9.0. 3.8
41、 The RNA shall accept and fulfill requests for specific p-ANIs if they are currently available for assignment from the p-ANI inventory, subject to the criteria identified in Section 7.0. 3.9 P-ANI Assignees may not trade p-ANIs between themselves. _ 1147 CFR, 52.13 (c) (7). 10 3.10 P-ANIs may be tra
42、nsferred between Eligible Users, via the RNA, if the p-ANI is In Use and one or more of the following conditions is met: a) merger or acquisition; b) both entities involved mutually agree to the transfer of the p-ANI and coordinate through the RNA (see Section 7.4); c) authorization or directive rec
43、eived from the appropriate governmental agency. All p-ANI transfers must be mutually agreed to by both the relinquishing and receiving parties. 3.11 A p-ANI returned in error to the RNA is retrievable by the p-ANI Assignee, provided the p-ANI is Aging. This is accomplished via e-mail between the p-A
44、NI Assignee and the RNA in order to establish an audit trail. 3.12 The 211-9950 through 211-9999 p-ANI ranges in every NPA12shall be Unavailable for assignment to Eligible Users because they are used for Next Generation 9-1-1 Legacy Selective Router Gateway (LSRG) purposes.13These ranges shall be ma
45、de Unavailable for assignment in any new NPA added to RNAS as well. 4.0 Eligible User Responsibilities Eligible Users have several responsibilities in a p-ANI environment. These responsibilities vary depending on whether the Eligible User is a p-ANI Applicant or a p-ANI Assignee. These responsibilit
46、ies are outlined below: 4.1 P-ANI Applicant Responsibilities A p-ANI Applicant is responsible for obtaining a current copy of the P-ANI Administration Guidelines14. A p-ANI Applicant requesting resources from the p-ANI inventory shall: a) meet the definition of an Eligible User as defined in Section
47、 2.7 a; b) complete the Part 1 P-ANI Application Form (Attachment 1) per these guidelines; c) have a current P-ANI Forecast Report (Appendix 1) on file with the RNA . A p-ANI Applicant making its first request in an NPA shall provide a P-ANI Forecast Report _ 12In NPAs 281, 405, 806, 870, and 903, t
48、he Unavailable p-ANI ranges for these purposes are 511-8950 through 511-8999. 13In 2015, the NENA i3 Architecture Working Group requested that these ranges be allocated for this purpose and the FCC subsequently approved it on May 5, 2015, via email to the RNA. 14p-ANI Applicants can obtain a current copy of the p-ANI Administration Guidelines at http:/www.atis.org/inc/docs.asp. 11 (Appendix 1) of p-ANI resource needs to the RNA prior to submitting the p-ANI request for the requested NPA; d) provide a detailed expla
