ATIS 1000083-2018 Technical Report on Assessment of Nationwide Number Portability.pdf

1、 TECHNICAL REPORT ATIS-1000083 Technical Report on Assessment of Nationwide Number Portability 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 pres

2、sing business priorities. ATIS nearly 200 member companies are currently 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 suppo

3、rt, 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 solutions, and interoperability testing. ATIS is accredited by the American Nationa

4、l 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 the International Telecommunication Union (ITU), as well as a member of the Inter-American Te

5、lecommunication Commission (CITEL). For more information, visit www.atis.org. Notice of Disclaimer National LRN and Non-Geographic LRN 7 5.1 National LRN Solution . 7 5.1.1 Overview 7 5.1.2 Impacts . 8 5.2 Non-Geographic Location Routing Number (NGLRN) Solution . 10 5.2.1 NGLRN Solution Description

6、. 10 5.2.2 Impacts . 10 5.3 Summary and Comparison of National LRN National LRN and Non-Geographic LRN This clause provides the analysis of the near-term NNP solutions; National LRN and Non-Geographic LRN. NNP breaks down the association between TNs and geography. In light of NNP, the FCC6is conside

7、ring changing policies regarding N-1 query processing and interLATA call processing for NNP TNs. Regardless of the technical solution, full deployment of NNP will necessitate that the FCC first expand its number portability requirements beyond rate center and LATA boundaries and lift all restriction

8、s that could prevent the porting of any telephone number to or from anywhere in the nation. 5.1 National LRN Solution 5.1.1 Overview The National LRN NNP solution allows Location Routing Numbers (LRNs) to be used outside of the current LATA boundaries, thereby allowing TNs to be “ported” nationally.

9、 This NNP solution assumes that Service Providers will be permitted to have an LRN in multiple regional NPACs to identify the customers current location. However, this solution takes a straightforward approach, leveraging todays infrastructure as it utilizes existing call routing functionality witho

10、ut the “costs” of additional administrative overhead. 6In the Matter of National Number Portability, WC Docket No 17-244. ATIS-1000083 8 5.1.2 Impacts 5.1.2.1 SS7 Signaling The National LRN NNP Solution requires no changes to the SS7 signaling used to support NP queries or call setup. 5.1.2.2 Call P

11、rocessing there are no block assignments. The area code (3-digits) is an indication to PSTN networks to route to an IP network. Once on the IP network, the full 10-digits will be used to determine an Internet address, such as a Uniform Resource Identifier (URI). The NGLRN administration system will

12、provide the 10-digit NGLRN-to-URI mapping. 5.2.2.5 Accounting/Billing Accounting/billing changes to the end user are up to each carrier. This applies to all proposed NNP solutions. Carriers that bill on a minute basis will not need to change billing. The NGLRN solution does not propose a method of p

13、roviding the customers geographic location to originating networks. This means that this solution does not support distance-based billing, nor does it consider the questions surrounding intercarrier compensation. 5.2.2.6 PSTN/IP Interworking There is no industry consensus on where the PSTN/IP interw

14、orking is required to take place between TDM networks and IP networks. This must be addressed through the terms of an interconnection or traffic exchange agreement. The NGLRN solution provides the ability to interwork the TDM/SS7-based PSTN with a post-transition IP-based PSTN and the ability to tra

15、nsition customers and the network from TDM/SS7 to IP. The NGLRN solution assumes the availability of an all-IP network of switches (i.e., the NGGWs) that interconnect with the TDM/SS7 PSTN as a result of routing calls based on an NGLRN. TDM/SS7 switches would route calls based on the NGLRN area code

16、 to a transport network (the carriers own or a third partys) that can route calls to the terminating network via the NGLRN. ATIS-1000083 12 5.2.2.7 Regulatory Related Services There is no new functionality required for the NGLRN solution to enable regulatory related services. However, this option po

17、ses no requisite for interconnection otherwise provided by existing Tariff or Interconnection Agreements applicable to the PSTN. 5.2.2.7.1 Emergency Services Calls to 9-1-1 initiated by wireless and VoIP customers that have ported their TNs using an NNP solution would use the pANI-based solutions th

18、at are currently deployed. Calls to 9-1-1 initiated by wireline customers that have ported their TNs under NNP will be subject to the same considerations as described in clause 4.1.2.7.1. The impacts identified in clause 4.1.2.7.1 are independent of the use of NGLRNs to support NNP. 5.2.2.7.2 NS/EP

19、The general impacts identified in clause 4.1.2.7.2 are also applicable for the NGLRN approach. In addition, there will be a need to ensure that the network of NGGWs (IP network) is capable of recognizing and providing priority to NS/EP calls/sessions including any query/response to NPDBs. Also, ther

20、e will be a need to make sure that any third-party arrangement as described for the NGLRN option has the necessary capabilities to provide priority treatment and handling of NS/EP calls/sessions (i.e., if the third party is not a GETS Service Provider). 5.2.2.8 Policy The only policy change specific

21、 to the NGLRN solution is requiring carriers to have the ability to route to NGLRNs. Carriers may choose to have agreements with transport providers who can route to NGLRNs rather than do it themselves. As described in clause 5.2.1, this solution does not require carriers to offer NNP service to the

22、ir customers, connect directly to NGGWs, nor interface with administrative systems or processes necessary to enable the solution. Regardless of the technical solution, full deployment of NNP will necessitate that the FCC first expand its number portability requirements beyond rate center and LATA bo

23、undaries and lift all restrictions that could prevent the porting of any telephone number to or from anywhere in the nation. NNP further breaks down the association between TNs and geography. In light of NNP, the FCC7is considering changing policies regarding N-1 query processing and interLATA call

24、processing for NNP TNs. 5.2.2.9 Summary The NGLRN approach handles porting numbers outside of the LATA by associating them to non-geographic LRNs formed from a special non-geographic NPA. Calls to NNP-ported numbers would be routed based on NGLRNs to special gateways so that the calls can be complet

25、ed over an IP network where transport would be provided from the originating LATA to the terminating carrier. The jurisdictional issues identified above for the national LRN approach would also need to be addressed for the NGLRN approach. An originating LNP query for all calls would be helpful, but

26、not required, in the context of the NGLRN solution (as it would be for the national LRN solution) to avoid routing what might turn out to be a local call to an IXC. The implementation of an NGLRN approach also requires carriers to consider potential billing and settlement impacts of numbers ported o

27、utside the LATA, including what modifications might be required to ensure that jurisdiction-related factors (such as taxes) will be properly handled. It should be noted that the following challenges exist: A new non-geographic area code to be used for LRNs (NGLRNs) for call routing to NNP TNs. o Adm

28、inistrative processes for managing the new numbering space. 7In the Matter of National Number Portability, WC Docket No 17-244. ATIS-1000083 13 o Association between NGLRN and routing and service provider information. A network of IP switches (non-geographic gateways, or NGGWs) to host the NGLRNs. o

29、 Similar to todays LATA tandems. Service providers must route calls to NGGWs on an IP network to complete to NGGWs/NGLRNs for delivery to the terminating network based on the NGLRN. o Service providers can route to the IP network either using their own network or a partner network. Service providers

30、 have built their operational support systems and network processes around the existing number allocation and porting systems and processes. Implementing the NGLRN approach likely require network related changes. These may include reconfiguration of the legacy TDM network to facilitate routing, a ch

31、ange that would require further investment in the legacy networks 5.3 Summary and Comparison of National LRN & Non-Geographic LRN Solutions Table 5.1 - Summary of National & Non-Geographic LRN Impacts Impact Analysis Summary National LRN Non-Geographic LRN SS7 Signaling None. None. Call Processing M

32、ay appear to be Out of LATA but now local. Suppression of LNP query by some carriers. May appear to be Out of LATA but now local. Suppression of LNP query by some carriers. Restrict NNP port-ins to wireless and VoIP carriers. Network Routing Query at point of origination vs N-1. Query at point of or

33、igination vs N-1. Process to provision and distribute new NGLRNs, Arrangement with a carrier for calls to NNP TNs, new network element. Number Administration Porting TNs out-of-state raises regulatory questions. New NPA, select Adm., allocate to NGGW providers. Porting TNs out-of-state raises regula

34、tory questions. NPAC Connect to multiple regional DBs. New NGLRN added to all seven regional databases. Needs new data element so not to conflict with existing LRNs. Accounting/Billing Yes- Ported out of LATA calls could be local or toll. Yes - Ported out of LATA calls could be local or toll. Does n

35、ot support distance-based billing does not convey geographic location to originating network. PSTN/IP Interworking None. Impact is dependent upon Interconnection options and obligations of providing interworking function. Emergency Services No solution-specific impact. No solution-specific impact. N

36、S/EP No solution-specific impact identified. No solution-specific impact identified. ATIS-1000083 14 Impact Analysis Summary National LRN Non-Geographic LRN Policy Dialing Plan consistency, N-1 requirement, changes to intercarrier compensation. Dialing Plan consistency, N-1 requirement, changes to i

37、ntercarrier compensation. Facilitating a national LRN, or NGLRN approach would require that carriers examine changes that may be necessary to their systems, processes, and equipment. Implementation of the National LRN or NGLRN approach may necessitate updates to the existing Industry Numbering Guide

38、lines and/or the development of new guidelines and would require a more detailed analysis and possibly testing. These options have common set of impacts Service providers would need to conduct an assessment to determine the network impacts of either performing all queries at the point of origination

39、 or maintaining the N-1 call completion scenario with the understanding that those TNs porting outside the LATA require additional routing in the case of National LRN or further specification of how the call is routed to the Non-Geographic LRN. o The capability to query on calls to NPA-NXXs outside

40、the LATA may not be uniformly supported. o It is not clear how the existing six-digit query triggers can accommodate the number of foreign NPA-NXX ports. There may be too many potential NPA-NXXs for the normal six-digit (NPA-NXX) triggers to be employed for NNP, due to switch table limitations. Howe

41、ver, a three-digit trigger may suffice. o Even assuming a successful query, the switch must be able to override the normal requirement that the type of route (local or IXC) be selected based on analysis of dialed number before query rather than on the LRN. o The fact that LRNs are assigned on a per-

42、switch, per-LATA basis also has important implications. When a foreign number ports into a LATA, neither the dialed number nor the LRN will allow determination of whether a call to the number from within the ported-to LATA is local, EAS, or IntraLATA toll. To the extent these distinctions remain imp

43、ortant for routing, end user billing, or intercarrier settlements, implementation of NNP via a national LRN or NGLRN approach will require changes in policy Numbering resources are state managed. Porting TNs out-of-state raises questions of regulatory and service provider responsibilities, liabiliti

44、es, and numbering resource management. From a consumer point of view there could be some confusion if local/toll plans are involved, as there would be calls to the same NPA-NXX that are sometimes local and sometimes toll. The NGLRN approach does not support distance-based billing. From an NPAC persp

45、ective: o NGLRNs will have to be added to the NPAC as valid LRNs, as is done today for geographic LRNs. The main difference is that the same NGLRN will be able to be duplicated across multiple NPAC regions. Operationally, this is not done today. o From a National LRN perspective current NPAC system

46、processes require the LRN and TN NPA-NXX components to be associated to the same LATA. Changes to support this proposal would require existing edits to be modified. Also, currently local systems connect to the regional NPAC SMS database based on numbers being broadcasted to the region where the NPA-

47、NXX is allocated. Local systems would need to connect to all regions that numbers may port from to receive the network routing information in support of the NPDB used for call routing Dialing plan consistency (e.g., national 1+10-digit dialing) may be needed. For example, variations exist across the

48、 country with how calls can/should be dialed, i.e., 1+10-digits, 10-digits, and/or 7-digits. These are often related to intelligence in the dialed number relative to routing. For example, local calls originating and terminating within the same NPA, if only one NPA today serves the area, are usually

49、dialed on a seven-digit basis. Areas where NPA overlays have occurred are dialed as 1+10-digits or only 10-digits depending on the dial plan approved by the state. NNP impacts on the varying dialing plans need to be assessed ATIS-1000083 15 This NGLRN option has not only administrative impacts associated with identifying and administering a new, as yet undefined non-geographic numbering resourse, but also network impacts including the development and deployment of yet undeveloped network elements, e.g., NGGW, and changes in how routing is currently performed,