NPIF

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Notice:

Effective August 1, 2017 the role of Change Management Administrator (CMA) of the Local Number Portability Administration Working Group (LNPAWG) for all US Regions was transferred to Telcordia Technologies, Inc., d/b/a iconectiv.

To contact the iconectiv CMA or to be added/removed from the LNPAWG distribution list please email cma@iconectiv.numberportability.com.

Please note that on or about September 30, 2017 the collection and history of industry documents will be transferred to https://numberportability.com/. Stay tuned for further updates at upcoming LNPAWG meetings and conference calls.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

NANC LNP Process Flows

The following pages include the textual and graphical descriptions of the Inter-Service Provider Local Number Portability (LNP) Operations Flows.

Legend

Local Service Provider (LSP) = Any provider (e.g., voice provider, data provider) that administers and bills local exchange and related services for the end user. The following terms identify LSPs with specific roles during the porting process:

New Local Service Provider (NLSP) - The local provider of record following the completion of the porting process.
Old Local Service Provider (OLSP) - The local provider of record prior to the porting process.

Network Service Provider (NSP) = Carrier that provides the facilities and switch/equipment components needed to make up an end user’s local telecommunications service. The following terms identify NSPs with specific roles during the porting process:

New Network Service Provider (NNSP) - The network provider of record following the completion of the porting process.
Old Network Service Provider (ONSP) - The network provider of record prior to the porting process.

CSR = Customer Service Record

DSL = Digital Subscriber Loop

FOC = Firm Order Confirmation

FRS = Functional Requirements Specification

ICP = Inter-carrier Communication Process

IIS = Interoperability Interface Specifications

LSMS = Local Service Management System

LSR = Local Service Request

NPAC = Number Portability Administration Center

PSTN = Public Switched Telephone Network

SOA = Service Order Activation

SP = Service Provider

SV = Subscription Version

TN = Telephone Number

“via the SOA interface” = generic description for one of the following: the SOA CMIP association,

LTI, or contacting NPAC personnel

WPR = Wireless Port Request

WPRR = Wireless Port Request Response

Notes

Note 1

Pursuant to FCC Order 07-188, released on November 8, 2007, and FCC Order 09-41, released on May 13, 2009, Local Number Portability (LNP) obligations are extended to interconnected Voice over Internet Protocol (VoIP) providers. In paragraph 8 of FCC Order 09-41, the FCC ruled the following:

“Thus, we require all entities subject to our LNP rules, including interconnected VoIP providers and their numbering partners, to complete port requests for simple wireline-to-wireline and simple intermodal ports within one Business Day, unless a longer period is requested by the new provider or the customer elects otherwise.”

The North American Numbering Council (NANC) identifies three classes of interconnected VoIP providers, defined as follows:

Class 1: An interconnected VoIP provider that obtains numbering resources directly from the North American Numbering Plan Administrator (NANPA) and the Pooling Administrator (PA). Class 1 interconnected VoIP providers must follow the appropriate Wireline-Wireline/Intermodal Flows (Simple or Non-Simple, whichever is applicable) for the LNP provisioning process, serving as the New Network Service Provider (NNSP) or Old Network Service Provider (ONSP), whichever is applicable.
Class 2: An interconnected VoIP provider that partners with a facilities-based Public Switched Telephone Network (PSTN) Service Providers to obtain numbering resources and connectivity to the PSTN via the Service Provider partner’s switch. A Class 2 interconnected VoIP provider is not considered a reseller in the context of the FCC definition of a Simple Port (refer to FCC Order 07-188 and FCC Order 09-41 for Simple Port definition). Class 2 interconnected VoIP providers must follow the appropriate Wireline-Wireline/Intermodal Flows (Simple or Non-Simple, whichever is applicable) for the LNP provisioning process, serving as the New Local Service Provider (NLSP) or Old Local Service Provider (OLSP), whichever is applicable.
Class 3: A non-facilities-based reseller of interconnected VoIP services that utilizes the numbering resources and facilities of another interconnected VoIP provider (analogous to the “traditional” PSTN reseller). A Class 3 interconnected VoIP provider is not considered a reseller in the context of the FCC definition of a Simple Port (refer to FCC Order 07-188 and FCC Order 09-41for Simple Port definition). Class 3 interconnected VoIP providers must follow the appropriate Wireline-Wireline/Intermodal Flows (Simple or Non-Simple, whichever is applicable) for the LNP provisioning process, serving as the New Local Service Provider (NLSP) or Old Local Service Provider (OLSP), whichever is applicable.

Note 2

The FCC has allowed that One Business Day porting must be implemented either within 9 months of the NANC report to the FCC, or for carriers which qualify, implemented within 15 months (FCC 09-41, para 12). The Local Number Portability Administration Working Group (LNPA WG) provisioning flows and One Business Day definition require reciprocal implementation where carriers must only port-in at the interval which that carrier also ports-out.

Note 3

Service Providers are not precluded from exceeding the requirements set forth in the NANC LNP Provisioning Flows. For example, no provider is required to allow activation on a non-Business Day (Saturday, Sunday or Old Service Provider Company-Defined Holiday). However, a non-Business Day activation may be performed as long as both Service Providers agree and any Service Provider activating a port on a non-Business Day understands the porting out Service Provider may not have, and is not required to have, operational support available on days not defined as Business Days. In agreeing to non-Business Day activations, the Old (porting out) Service Provider may require that the Local Service Request (LSR)/Firm Order Confirmation (FOC) and the New (porting in) Service Provider NPAC Create message be due-dated for the appropriate normal Business Day in order to ensure that the end user's service is maintained.