|
Frequently Asked Questions
Table of Contents General What information is available on this Web site?How do I port a number? Do Wireless Carriers have to port numbers? Who is the current Change Management Administrator (CMA)? Local Number Portability Administration Working Group (LNPA WG) What is the LNPA WG?How can I join the LNPA WG? When does the LNPA WG meet? Number Portability Administration Center (NPAC) What is the NPAC and how do I exchange porting information?How do I register as an NPAC SMS user? Do I have to be certified to use the NPAC SMS? NPAC SMS Change Management
How does the Change Management process work? What information is available on this Web site? The Local Number Portability web site contains information that supports the activities of the North American Numbering Council (NANC) Local Number Portability Administration Working Group (LNPA WG). Features Meetings Information.
* Documents
* LNPA WG Issue Creation Service Providers who wish to participate in LNP need to be able to communicate porting requests with the Old Service Provider (OSP) and they must be able to send and receive porting data with the regional NPAC. Prior to porting a customer, the New Service Provider (NSP) informs the OSP that the number will be ported. This is normally done through the Local Service Request (LSR) process. The OSP responds with the Local Service Confirmation (LSC), also known as a Firm Order Confirmation (FOC), agreeing to the port. After the LSR / LSC exchange, the NSP sends porting data to the NPAC. Service Providers are required to register with the NPAC prior to porting numbers. Registration information can be found at www.npac.com or by contacting the NPAC at 1-888 NPAC HELP. The NPAC Service Management System (SMS) is the central database and mediation point for all LNP activity. The NSP sends a porting request to the NPAC SMS. Porting requests can be sent to the NPAC SMS by using the NPAC SMS Low Tech Interface (LTI), by using a Service Order Administration (SOA) system that is interfaced to the NPAC SMS, or by contracting with a service bureau that has an interface to the NPAC SMS. Once the NSP sends a porting request to the NPAC SMS, a message is sent to the OSP by the NPAC for porting concurrence. When the porting due date is reached, the NSP sends a message to the NPAC SMS to activate the port. Upon receiving the activation message, the NPAC SMS sends the new network routing data to all Service Providers in the region. All Service Providers must be connected to the NPAC SMS to receive the new routing information. Routing information is sent to the Service Providers through a Local Service Management System (LSMS) interface to the NPAC SMS. The LSMS serves as the local LNP database. The Service Providers’ network queries the LSMS for proper routing information. In some cases the LSMS functionality is built into the Signal Transfer Point (STP). Service bureaus also provide LSMS functionality. Finally, all Service Providers then update their networks for proper routing of the ported number. A complete description of the operation flows is contained in the Inter-Service Provider LNP Operations Flows located on this Web site. A number of companies provide LNP Products and Services to help you operate in the LNP environment. Back to TopDo Wireless Carriers have to port numbers?The wireless industry was given an extension until November 2002 by the FCC to implement full Number Portability in the 100 largest MSAs. However, wireless providers are required to be able to complete calls to ported numbers in the 100 largest MSAs as of December 31, 1998. If the wireless carrier sends a call to the terminating carrier; in other words, the wireless carrier is the N-1 carrier, then the wireless carrier is responsible for doing the LNP database query. They can either perform the query themselves or default route the call to the original carrier (the NPA-NXX owner) to perform the query. Charges will be incurred if default routing is used. Issues pertaining to full Number Portability for wireless carriers are being addressed by the Wireless Number Portability Sub Committee (WNPSC) of the LNPA WG. Back to TopWho is the current Change Management Administrator (CMA)?The current Change Management Administrator function is handled by NeuStar. Send change requests to cma@neustar.biz. Back to TopLocal Number Portability Administration Working Group (LNPA WG)What is the LNPA WG?The Local Number Portability Administration Working Group (LNPA WG) is the body that makes the decisions and recommendations that form the basis of the regulatory orders issued by the FCC pertaining to LNP. The LNPA WG is also responsible for the business functionality of the national LNP system and how Service Providers inter-operate with it. Therefore, the activity of the LNPA WG has a direct bearing on the processes and systems that each Service Provider uses to participate in LNP. The LNPA WG was given the charter by the North American Number Council (NANC) for implementing Local Number Portability (LNP) on a national level. The LNPA WG is responsible for developing and maintaining the process that is followed by all Service Providers who participate in LNP. A complete description of the operation flows is contained in Inter-Service Provider LNP Operations Flows located on this Web site. These flows have been revised to include wireless carrier operations. The updated flows will be included in the second NANC report on Wireless Wireline Integration due out in the second quarter of 1999. The LNPA WG is also responsible for defining the requirements for the national Number Portability Administration Center (NPAC) Service Management System (SMS) and how it interfaces to each Service Provider’s local LNP system to enable LNP. The NPAC SMS is operated by NeuStar, which serves as the central mediation system and source database for all number portability data. The requirements are contained in the "NPAC SMS Functional Requirements Specification (FRS)" and the interface standards are contained in the "NPAC SMS Interoperable Interface Specification (IIS)". Both documents are available on the NPAC web page at www.npac.com under documents. The NPAC web site also has documentation about pending change orders that will change the functionality of both the NPAC SMS and the interface to it. The following are currently active sub committees of the LNPA WG: Wireless Wireline Integration Sub Committee (WWISC)– The WWISC was formed by the LNPA WG in June 1997 to address the issues of integrating wireless processes and systems into LNP. The first report on Wireless Wireline Integration was issued by NANC in May 1998. It addressed issues such as rate center differences between wireline and wireless carriers, modifications to the NPAC to support wireless carriers, changes required to wireless systems to support number porting, and inter-carrier communications required prior to porting a number. The second report from the WWISC will address among other things the shortening of porting intervals between wireline and wireless carriers to better support the wireless business model. This group no longer exist. It’s responsibility for reports is now under the LNPA Working Group, Number Pooling Sub Committee (NPSC) – The NPSC was formed by the LNPA WG in March 1998 to address the issues specific to the 847 area code trial in the Midwest Region, and later the National Number Pooling architecture. Number Pooling is a mechanism that allows an NPA-NXX owner (code holder) to donate unused 1K blocks to the Pooling Administrator, which are subsequently distributed to other Service Providers (block holders), for their use. This allocation mechanism lessens the distribution and opening of new NPA-NXXs for areas that are in jeopardy of available number exhaustion. The 847 trial has been operational since January 1999, and the National Number Pooling effort has a complete set of requirements, IIS flows, GDMO and ASN.1. The major feature in the National solution is Efficient Data Representation (EDR), where a 1K Block is represented by a single entity, versus 1000 individual TNs. Wireless Number Portability Sub Committee (WNPSC) The WNPSC was formed in September 1998 to address issues specific to wireless-to-wireless porting. Topics that are currently being discussed include the pre-port inter-carrier communications, E 911 issues, access to the NPAC for resellers, and both inter-carrier and NPAC certification testing. Slow Horse Sub Committee The Slow Horse sub committee was formed to address performance issues relating to high-volume ports. During high volume ports connectivity is lost between the NPAC SMS and SOA and LSMS systems. The LSMS outages are of concern because it results in routing information not being provisioned properly for the ported number. SOA outages, although not as critical as LSMS outages, also cause NPAC SMS performance degradation during recovery. Back to TopHow can I join the LNPA WG?The LNPA WG is an open forum sponsored by the North American Numbering Council (NANC) to facilitate the implementation of LNP. It is open to all wireline and wireless service providers, as well as all vendors. There are no requirements for joining, just show up and participate. Back to TopWhen does the LNPA WG meet?The LNPA WG and active subcommittees meet on a monthly basis at various locations throughout the country and in Canada. There are also regularly scheduled conference calls to discuss change management and operational issues. A complete schedule of meeting and conference calls can be found on the Meetings Page of this Web site. Minutes from the latest meetings can be found on the Documents Page of this Web site. Back to TopNumber Portability Administration Center (NPAC) What is the NPAC and how do I exchange porting information? The Number Portability Administration Center (NPAC) is operated by NeuStar, and serves as the central mediation center for all LNP activity. The NPAC Service Management System (SMS) is used by the NPAC personnel to facilitate the porting of numbers. There is a separate NPAC SMS for each of the seven traditional RBOC regions in the US and an eighth system for Canada. The systems are all physically located in Chicago, IL with a backup site in Tarrytown, NY. Every Service Provider that participates in LNP exchanges porting information with the NPAC SMS. Typically, subscription information is sent to the NPAC via the Low Tech Interface (LTI) or through the Service Provider’s Service Order Administration (SOA) system. Porting notifications are received from the NPAC via the same systems. When a ported number is activated, network downloads are received from the NPAC SMS through the Service Provider’s Local Service Management System (LSMS). The LTI is a Web-based screen that is accessed through the NPAC. A number of companies offer SOA and LSMS products. SOA products may be stand-alone or integrated with other parts of the OSS. LSMS products may be stand-alone or integrated with other network elements such as the STP. Service Providers can also contract with a service bureau for the SOA and LSMS functionality. How do I register as an NPAC SMS user? All Service Providers that wish to port numbers must register as an NPAC SMS user. The first step is to contact the NPAC and complete a Non-Disclosure Agreement and an NPAC User Agreement. The NPAC can be contacted via their Web site at www.npac.com or by calling 1-888-NPAC HELP. Do I have to be certified to use the NPAC SMS? Yes, NPAC certification is done by both the LNP product vendors and by the individual Service Providers. There are two types of NPAC certification tests, the Interoperability Test and the Turn-up Test. Interoperability Testing is done to certify that the SOA and LSMS CMIP interface conforms to the IIS. This test is performed by the SOA and LSMS vendor. The Turn-up Testing is performed by each Service Provider to test the SOA and LSMS application. The amount of testing varies according to the SOA or LSMS system used and whether or not the Service Provider has been certified to operate in another NPAC region. LTI users are issued a secure card and Logon ID and system setup instructions. Once the customer has set-up and configured the LTI system, they attend LTI system training. At the completion of training, customers then must complete LTI Testing with the NPAC. Customers can arrange all of the above by calling the NPAC support Help Desk at 1-888-NPAC-HELP. NPAC SMS Change Management How does the Change Management process work? The change management process starts with input from the LNPA Working Group, Vendors, or the LLC. Change orders are used to make changes to NPAC SMS functionality or to make clarifications to the FRS and IIS documents. The LNPA Working Group holds open discussions to determine if the Change Order should be implemented; both business and technical aspects are considered. Change Orders that are accepted are prioritized. Supporting requirements, business and technical flows, interface definitions, test cases, and methods and procedures are determined as required for each Change Order. After supporting documentation has been developed, Change Orders are grouped into recommended release packages. Negotiations between the LLCs and the NPAC vendor occur to refine the release package and to set implementation time frames. For detailed information reference the change management process documents located on this site. How do I submit a Change Order Request for the NPAC SMS? Change Order Request can be submitted to the CMA via e-mail at cma@neustar.biz. Change Order Requests can also be created as a group effort at the LNPA WG meetings. What changes will be in the next NPAC SMS release? The next release of the NPAC SMS is Release 3.0 which provides the functionality to support National Thousands Block Number Pooling as defined by the LNPA Working Group Number Pooling Subcommittee. It also introduces Efficient Data Representation (EDR) which provides a method of activating 1000 TNs as one record thus conserving NPAC, LSMS, and STP/SCP capacity. A detailed list of the Change Orders for this release is available in the Change Order Implemented List. What changes are being considered for implementation after the next release? The next major release, Release 4.0 provides functionality for various change orders as requested by the LNPA-Working Group in support of on-going Local Number Portability A detailed list of change orders is available under CMAS Report/R4 Change Orders under LNPAWG Documentation. Implementation dates have not yet been determined. When is the next NPAC SMS release scheduled? 6/30/00 Supplemental Test Plan Certification
Regression Testing is testing that is done to insure that existing NPAC SMS, LSMS, and SOA system functionality were not impacted by a new release of NPAC SMS software. Each Service Provider must perform regression testing for each new release of the NPAC SMS and each new release of their SOA or LSMS software. What is Interoperability Testing? Interoperability Testing insures that the SOA and LSMS vendor CMIP Interfaces comply with the functionality defined in the IIS. Vendor SOA and LSMS systems must be Interoperability Certified prior to starting Turn-up Testing with NeuStar. The Interoperable Interface Specification (IIS) is the document that defines the CMIP Interface used by the SOA and LSMS systems to communicate with the NPAC SMS. The CMA, under the direction of the LNPA WG, makes updates to this document. The latest revision of this document is available at www.npac.com The Functional Requirements Specification is the document that defines the business requirements for the NPAC SMS. The CMA, under the direction of the LNPA WG, makes updates to this document. The latest revision of this document is available at www.npac.com |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
