Wireless Number Portability Information Handbook

Transcription

1 Wireless Number Portability Information Handbook Phase 1, Version 1.0, 12 /99

2 Proprietary Information This document is the proprietary and confidential property of ILLUMINET, Inc. Information within this document is subject to change without notice. This document may not be copied, reproduced, used or disclosed, in whole or in part, without the express written consent of ILLUMINET. It is to be used only for the purpose for which it has been supplied. To the extent possible, the terms used in this document are the same as, and have the same meaning as, those contained in the Agreement(s) that this document pertains to. In the event that there is a difference or conflict in the terms or definitions between this document and the Agreement(s), the terms and definitions in the Agreement(s) shall prevail. Copyright 2001, ILLUMINET, Inc. All rights reserved.

3 d o c u m e n t r e v i s i o n h i s t o r y 12/22/99 Version 1.0 released 1/11/01 New logo updated throughout the guide.

4 t a b l e o f c o n t e n t s Chapter 1: Introduction to Wireless Number Portability Overview About this Guide What is Number Portability? What Is Wireless Number Portability? What is LRN ILLUMINET s WNP Service Bureau Solution Overall Product Architecture Communication Resources: On-line Documentation and Forms For more information Chapter 2: WNP Phases and Implementation Overview Number Portability Administration Mandated Implementation Timeframes Call Routing Responsibility N-1 Requirements Default Dipping and Blocked Calls Chapter 3: Functional Requirements and Agreements Components in a Wireless Number Portability-Capable Network Functional Requirements for LRN in Phase WNP Interconnection Agreeements NPAC User Agreements WNP Implementation Checklist Chapter 4: Provisioning Overview SP-to-SP Provisioning LSR/FOC Processes NPA Splits Number Pooling Code Opening Procedures Reserved TN Porting E911/ Operator Services Payphones

5 t a b l e o f c o n t e n t s Chapter 5: Test Requirements Overview Phase I: Internal Acceptance Testing Phase II: NPAC Certification Phase III: Intercompany Testing Chapter 6: ILLUMINET s Solution Overview Setting Up with ILLUMINET Services ILLUMINET s Responsibilities to You Appendix A: Acronyms Used in This Guide... A-1 Appendix B: WNP Industry and Regulatory Bodies... B-1 Appendix C: Industry WNP Documentation Resources... C-1

6 c h a p t e r 1 : i n t r o d u c t i o n t o w i r e le s s n u m b e r p o r t a b i l i t y

7 c h a p t e r 1 : i n t r o d u c t i o n t o W N P Overview Of all the changes in the telecommunications marketplace caused by the introduction of local competition, none is more complex than the development of Number Portability (NP). The 1996 Telecommunications Act requires all local exchange carriers (LECs) to provide Number Portability in accordance with requirements prescribed by the Federal Communications Commission (FCC). Further, we require all cellular, broadband, PCS and covered SMR providers to have the capability of delivering calls from their networks by June 30, FCC Ruling, July 2, 1996, (Docket 9-116). - NECA News Brief Supplement The tremendous opportunities provided by Number Portability (NP) distinguish it as one of the most exciting advances in the telecommunications industry since divestiture in the early 1980s. NP s transcendent effect upon the infrastructure of the industry - and the resulting benefits to consumers - is likely to distinguish it as one of the most significant advancements in telecommunications history. ILLUMINET has developed this Wireless Number Portability Information Handbook to help customers address significant issues and establish necessary elements when implementing this complex new technology. Contents of this guide incorporate information from major industry documents, NP knowledge gained from our experience to date and presents conclusions gleaned from discussions held with service providers nationwide. About this guide: Chapter 1 Introduction to Wireless Number Portability (WNP): Provides a general overview of NP, the technology that makes it possible and the processes being developed to facilitate its implementation nationwide. Chapter 2 WNP Phases and Implementation: Describes phases needed for a WNPcapable network to support Phase I of NP for Wireless Service Providers (WSPs). Chapter 3 Functional Requirements and Agreements: Describes the functional requirements and agreements necessary to implement WNP. Chapter 4 WNP Provisioning: Explains specific elements of WNP provisioning, including recommendations on how to address issues in each area. Chapter 5 Test Requirements: Provides a description of the testing requirements and activities for call delivery options in Phase I WNP. 1-1

8 Chapter 6 ILLUMINET s WNP Solution: Provides a high-level look at ILLUMINET s current WNP solution, a comprehensive description of Phase I opportunities, necessary steps for customer implementation of the service and ILLUMINET s responsibilities. Appendices: Lists of acronyms, industry organizations, web sites and documentation. What is Number Portability? Number portability (NP) is a circuit-switched network feature that provides consumers with the capability to move North American Numbering Plan (NANP) numbers from one serving switch in a network to another serving switch in another network while retaining the original NANP number. NP is automatic and transparent to consumers - this means that remote callers will automatically connect to ported subscribers without requiring any procedural changes for the consumer. Initially, consumers will have the option to change service providers within a defined area; future phases of portability will include moving physical locations and/or service types without having to change telephone numbers. The three types of NP are: Service Provider Portability: Allows an end-user to change SPs within a rate center while retaining the same telephone number. This is the only NP implementation currently being executed. Location (Geographic) Portability: Allows an end-user to change from one geographic area to another (e.g. New York to Ohio, etc.) while retaining the same telephone number. The current Location Routing Number (LRN) model does allow limited location portability within the rate boundaries. This is a future phase of NP implementation. Service Portability: Allows an end-user to change services (e.g., CENTREX to POTS, etc.) while retaining the same telephone number with the same service provider. This is a future phase of NP implementation. What is Wireless Number Portability? The initial rollout of NP in 1997 only affected wireline carriers in the top 100 MSAs - thereafter, implementation was by request. However, from the outset, the industry and the FCC recognized that wireless subscribers may call ported wireline subscribers and may eventually want to be able to change carriers while keeping their number. While the basic infrastructure for wireless and wireline NP are the same, there are many issues 1-2

9 unique to wireless providers. Some differences are technical (mobility and roaming support deployment, back office systems integration) while others are business concerns related to regulatory matters (local rate centers versus wireless market license areas). Still other issues are dependent on the integration of such differences. Service provider portability for both segments is made technically feasible by the Location Routing Number (LRN) method selected for so-called wireline number portability. What Is LRN? From its inception, several viable methods were considered for achieving NP; the United States and Canada have collectively opted for the Location Routing Number (LRN) method. The LRN is a 10-digit number in the format of NPA-NXX-XXXX that uniquely identifies a switch or point of interconnection (POI) that is capable of porting numbers in and out. LRNs utilize Intelligent Networking (IN), Advanced Intelligent Networking (AIN) or ANSI 41-D capabilities deployed in participating local service provider (LSP) networks. The LRN is activated in the switch by a software enhancement. The LRN for a particular switch must be an NPA-NXX, assigned to the service provider (SP) via the Local Exchange Routing Guide (LERG) for that switch or mobile switching center (MSC). The NPA-NXX portion of the LRN serves as the network address and is used to route calls to numbers that have been ported. Carriers routing telephone calls to end users who have ported their telephone numbers (TNs) from one carrier to another perform a database query to identify the corresponding LRN for the dialed number s switch. Carriers must perform queries for all calls where the dialed NPA-NXX has been marked as portable and at least one telephone number (TN) has been ported. The carrier then routes the call either to the new carrier - based on the LRN - or to the existing carrier via standard call routing. The LRN is obtained by querying a NP Database (NPDB) using a directory number as input. The LRN is then used to route the call to the recipient switch, with the directory number being used by that terminating switch to identify the specific subscriber. The LRN must identify the recipient switch because the response from a NPDB will continue to contain the dialed digits. For numbers that have not been ported, the original directory number is used both for routing and for identifying the subscriber, just as is done when NP is not implemented. The identity of a ported NPA-NXX in the switch and the delivery of the LRN by wireless service providers are the framework for WNP. 1-3

10 ILLUMINET s WNP Service Bureau Solution ILLUMINET s service bureau approach to WNP helps customers accomplish turnkey service without incurring the significant costs of deploying an independent WNP infrastructure. During Phase I of WNP deployment (see chapter 2 for more information on implementation phases for WNP) ILLUMINET s service bureau solution offers participants access to critical call routing information associated with ported numbers nationwide. In Phase II, ILLUMINET will facilitate number porting from wireless to wireless, wireline to wireless and wireless to wireline carriers. Our services extend nationwide, eliminating the need for SPs to work with multiple vendors, interfaces and potentially incompatible systems. It also facilitates communications with the seven Number Portability Administration Centers (NPACs) in the United States, and operational processing of the local service provider s information and maintenance of the portable number. ILLUMINET WNP customers can expect to: Save money and resources Minimize deployment time Control administrative costs Deliver WNP with efficiency Protect competitive position See chapter 6, ILLUMINET s Solution for more information regarding implementing WNP with ILLUMINET. Overall Product Architecture ILLUMINET s WNP service utilizes our well-established skills as a high-quality intelligent network services provider and our long time expertise in NP. We have offered our service commercially since 1997 when it became operational (per the FCC-mandated deadline). By providing secure access and reliable protocol support to the carrier s customer proprietary information, ILLUMINET can ensure a reliable, noncompetitive environment to its customers. The following components have been implemented for ILLUMINET s WNP Service: The Local Service Management System (LSMS): The interface between all of the NPACs that manages call routing information. ILLUMINET has the hardware and software database platform installed to interface with the NPACs and update the SCP for subsequent Local NP (LNP) LRN Data Access Service. The LNP SCP/STP: The network function that provides routing addresses for ported numbers during the query process. This service is available through ILLUMINET s LNP Data Access and Switch and Transport Services. For wireless carriers whose MSCs can support IN/AIN or NPREQ query types, ILLUMINET s LNP platform is available today. 1-4

11 Access is provided to routing information including: LRN: The Location Routing Number (LRN) identifies the carrier s switch where the call should be routed. GTT Data (DPC/SSN, routing indicator, etc.) by Service: Ten-digit Global Title Translations to allow for interoperability between LNP and other TCAP services such as LIDB, Custom Local Area Signaling Service (CLASS), Caller ID with Name (CNAM), Inter-Switch Voice Messaging (ISVM) and Short Message Service (SMS) (in Phase II). SOA (Service Order Administration): The second phase of WNP includes the implementation of the SOA, a high-speed interface between in-house processes and systems and the NPACs. It manages information as you initiate or receive service changes. The SOA functionality will be made available through ILLUMINET s WNP Data Administration Service. Service Orders SOA NPAC Service Management Layer LSMS Network Management Layer SCP MS Network Element Management Layer SCPs Network Element Layer STP STP SOA: Service Order Administration NPAC: Number Portability Administration Center LSMS: Local Service Management System SSPs/MSCs WNP Architecture 1-5

12 Communication Resources: On-line Documentation and Forms ILLUMINET s NP service team is committed to keeping customers apprised of changes and updates to services and procedures as they occur. To assure timely and efficient delivery of this vital information, we now utilize the convenience of ILLUMINET s home page on the world wide web. Customers are notified of service and procedure-affecting changes made to procedural guidelines via fax and/or as they occur and may download changes via the Number Portability section of the Documentation menu on ILLUMINET s web page at Passwords - available on request from Account Managers (AMs) and/or Customer Service Specialists (CSSs) are required to access ILLUMINET s on-line resources. Up-to-the minute copies of all NP forms are also available 24-hours-a-day via the web page. Please note: You must have Adobe Acrobat Reader a freeware application that can be downloaded free of charge through Adobe s web site ( to access bulletins via the ILLUMINET web page. A link to Adobe s Acrobat Reader download page is provided for your convenience at the top of the ILLUMINET documentation menu. For more information To learn more about ILLUMINET s WNP solution, contact your ILLUMINET AM. 1-6

13 c h a p t e r 2 : W N P p h a s e s a n d i m p l e m e n t a t i o n

14 c h a p t e r 2 : W N P p h a s e s a n d i m p l e m e n t a t i o n Overview Along with great opportunity, wireless service providers engaged in implementing NP are met with many unique challenges. Logistical issues surrounding the implementation of WNP are significant and far-reaching - impacting wireless service providers from the mobile switch-tofeature interaction, to billing, fraud and beyond. From the outset, ILLUMINET has been an industry leader in NP. This began with ILLUMINET s successful implementation of a solution for wireline NP customers in By dedicating the necessary resources and tapping our core competencies (database applications management and administration), ILLUMINET successfully met the Federal Communications Commission (FCC) mandated wireline local number portability (LNP) deadline of October 1, 1997, (FCC Number Portability Docket 96-98). That same dedication is now being applied to meeting WNP s implementation timeframes. Alaska Region #8 Canada Region #7 Northeast Region #1 Region #2 West Coast Western Region #3 Mid-West Region #5 Mid-Atlantic Hawaii Region #6 Southwest Region #4 Southeast Eight Regional NPACs U.S. Virgin Islands & Puerto Rico 2-1

15 Number Portability Administration In 1995, the North American Numbering Council (NANC) was selected by the FCC to oversee the administration of NP. The NANC recommended that to implement nationwide NP for wireline and wireless service providers as smoothly as possible and to ensure an even playing field for all service providers, the country should be subdivided into seven regions closely resembling the seven RBOC regions. An eighth region for Canada was then added. Under this structure, each region hosts a neutrally owned and operated Number Portability Administration Center (NPAC) that manages collection and distribution of ported number data for call routing. A single company oversees all eight NPACs (see map, Page 2-1). Mandated Implementation Timeframes The first mandate for WNP - to deliver wireless calls to ported, wireline TNs by December 31, was achieved. This was the first step in the current stage of WNP implementation, which is being referred to as Phase I. Wireless to wireline call routing is described in the following example: A business chooses to transfer its local telephone service from an Incumbent Local Exchange Carrier (ILEC) to a Competitive Local Exchange Carrier (CLEC) while keeping the same telephone number (TN). If a wireless subscriber dials the ported TN, the WSP is required to ensure that the call terminates to the correct landline subscriber. As we proceed through Phase I, issues continue to be addressed, including: Service provider portability within a rate center Roaming and the need to separate the Mobile Identification Number (MIN) and Mobile Directory Number (MDN) Business hours, days of operation, holidays Industry updates regarding progress in WNP implementation are posted regularly and are available on-line in the NANC LNPA-WG 2nd Report on Wireless and Wireline Integration, (dated June 30, 1999). Go to: Phase II will support the actual porting of TNs from wireless to wireless, wireline to wireless and wireless to wireline carriers. It is set for implementation by November, Please note: Wireless switches follow the same network interface (i.e, signaling the LRN) as wireline switches in accordance with the signaling standards defined in Call Completion to a Portable Number, reference ANSI T For requirements related to porting between wireless networks, see references TIA/EIA-756 TIA/EIA-41 D, ANSI T1.708,and TIA/EIA/IS

16 Call Routing Responsibility The FCC in their Second Report and Order in Docket CC accepted the NANC recommendation regarding who should be responsible for launching a query to determine the service provider of the called party. The solution is outlined in N-1 Requirements, below. N-1 Requirements The industry has proposed, and the FCC has endorsed, an N minus one (N-1) querying protocol. Under this protocol, the N-1 carrier will be responsible for the query, where N is the entity terminating the call to the end user, or a network provider contracted by the entity to provide tandem access. Therefore, the N-1 carrier (i.e. the last carrier before the terminating network) for a local call will usually be the calling customer s local service provider; the N-1 carrier for an interexchange call will usually be the calling customer s interexchange carrier (IXC). An N-1 carrier may perform its own querying, or it may arrange for other carriers or third parties to provide querying services on its behalf. The FCC has determined that if an N-1 carrier arranges with another entity to perform queries on its behalf, the other entity may charge the N-1 carrier in accordance with established requirements. If an N-1 carrier fails to ensure that a call is queried, the call might inadvertently be routed by default to the LEC that originally served the telephone number. If the number was ported, the LEC incurs costs in redirecting the call. This could happen, for example, if there is a technical failure in the N-1 carrier s ability to query, or if the N-1 carrier fails to ensure that its calls are queried, either through its own query capability or through an arrangement with another carrier or third-party. The FCC determined that if a LEC performs queries on default-routed calls, the LEC may charge the N-1 carrier. The FCC has determined further that it would allow LECs to block default-routed calls, but only in specific circumstances when failure to do so is likely to impair network reliability. The FCC also said that it would require LECs to apply this blocking standard to calls from all carriers on a nondiscriminatory basis. LSPs may query calls for other carriers by arrangement, or may receive unqueried, defaultrouted traffic when the N-1 carrier has not performed the query. Therefore, incumbent LECs are entitled to a federally tariffed query-service charge from N-1 carriers for their carrier-specific costs related to providing prearranged and default query services. The N-1 switch only has to perform a NP query when the destination directory number is in a Portable Block - a block of 10,000 numbers, also referred to as an NPA-NXX. This requires all switches in the local area, including wireless switches (which are not yet fully NP capable), to maintain tables that identify which local number blocks are portable and which are non-portable. To ensure correct routing, these tables must be updated based on the Local Exchange Routing Guide (LERG). 2-3

17 In order to avoid a LEC query charge, ILLUMINET offers this service to customers as a thirdparty provider, via our service bureau offering. Examples of N-1 call scenarios can be found in the Attachment A of the North American Numbering Council LNP Architecture & Administrative Plan, available at the NANC Federal Advisory Committee WNPA Working Group site at: Default Dipping and Blocked Calls As described earlier in this chapter, the FCC divided wireless NP implementation into two phases: Phase I mandated that all WSPs have the capability to deliver calls from their networks to ported numbers anywhere within the NPAC porting regions by December 31, Broadband Commercial Mobile Radio Service (CMRS) providers were also required to deliver telephone calls made from wireless phones to ported wireline customers on the same schedule. Both types of SPs met the December deadline. Phase II, the complete integration of wireline and wireless NP, has been pushed out to November, This deadline was established on February 8, 1999, when the FCC granted the cellular industry forbearance in the implementation of WNP in response to a petition filed by Cellular Telephone Industry Association (CTIA). With Phase II implementation delayed, mobile switch vendors are not yet required to provide NP software. Service Providers are, however, responsible to complete calls to ported numbers. Please note: It is possible (depending on the make and model of the MSC) that the LRN software may not be available at this time. Contact your vendor directly for a deployent schedule. WSPs who are seeing porting activity may currently be default routing to the Incumbent Local Exchange Carriers (ILECs). This automatic routing is referred to as default dipping - a service that provides the necessary information to correctly route calls while allowing the wireline carrier to charge the wireless carriers a tariffed charge (charges are assessed per region/ilec tariff). At this time, there is no cost recovery in place and wireless service providers are seeing charges ranging from a nominal amount to an invoice detailing the quantity of dips done and an explanation that the WSP will be back billed when cost recovery is determined. Wireless SP s may see blocked calls due to capacity constraints on the LEC network. An increase in number and type of individual contractual agreements with ILECs and administrative issues for nationwide providers are some of the reasons that wireless providers are recommended to push their vendors for early delivery of the NPREQ software feature in conjunction with using ILLUMINET for the NPDB function to avoid default dip charges. 2-4

18 c h a p t e r 3 : f u n c t i o n a l r e q u i r e m e n t s a n d a g r e e m e n t s

19 c h a p t e r 3 : f u n c t i o n a l r e q u i r e m e n t s a nd a g r e e m e n t s Components in a Wireless Number Portability-Capable Network To be WNP capable for Phase I, the SP must execute at least one of the following steps: A. Deploy or Upgrade and Utilize the required hardware and software components (see below) as part of your own network: Mobile Switching Center (MSC) w/lnp NPREQ capabilities Signal Transfer Point (STP) Service Control Point (SCP) Local Service Management System (LSMS) Appropriate SS7 Trunking B. Use ILLUMINET as your WNP data query Service Provider for: Signal Transfer Point (STP) Service Control Point (SCP) Local Service Management System (LSMS) C. Have access via another WNP capable network, or D. Default dip to the incumbent LEC Functional Requirements for LRN in Phase I The NPREQ Query Message - known as NumberPortabilityRequest (NPREQ) - has been defined in IS-756 by the TIA standards subcommittee TR The INVOKE for this message is sent from a wireless switch (MSC) to the NPDB and the response (known as RETURN RESULT ), either contains no parameters - indicating that the destination number is not ported - or an LRN (disguised as the routing digits parameter) if the destination number is ported. The NPREQ message is only used by wireless systems to query the NPDB. Landline switches use different query messages that are based on IN or AIN. The following is a basic scenario of a mobile subscriber calling a landline number that has been ported: 1. A mobile subscriber dials a landline number that is ported. The MSC queries an internal table of local number blocks that identifies the blocks (NPA-NXXs) that are identified as portable. 2. The MSC queries the NPDB using the IS-756 Number Portability Request INVOKE (NPREQ) message containing the directory number (DN), derived from the dialed digits. 3-1

20 3. If the dialed number is found in the NPDB (indicates that subscriber has ported), the LRN identifying the recipient switch is returned in the Number Portability Request RETURN RESULT. 4. The MSC selects a trunk group based on the LRN. If there are any intermediate switches, they will also route based on LRN. 5. The message that is used is the ISUP IAM (Initial Address Message). It contains the LRN, the DN, and an indication that an NP query has been performed in the forward call indicator (FCI), to minimize the probability of multiple query dipping. 6. The recipient switch then terminates to the subscriber based on the DN. WNP Interconnection Agreements In addition to network functionality, interconnection agreements demand immediate consideration. These agreements between WSPs and ILECs may include traffic forecasts for network sizing, query price per dip/per volume, additional recurring and nonrecurring charges and call completion as well as trouble reporting responsibility. While interconnection agreements are not mandated, many ILECs require them to assure proper network sizing. NPAC User Agreements In Phase I, if a SP is accepting downloads directly into an LSMS (not provided by a service bureau) a user agreement must be in place. As wireless service providers begin actively participating in porting customers between (Phase II) other carriers, they are required to sign a user agreement with each NPAC for the regions in which service is being offered even if you use a third-party provider for SOA services. You will need to obtain these user agreements and information surrounding the process directly from Neustar (formerly Lockheed Martin). WNP Implementation Checklist Use this high-level list of tasks to make sure that you have all elements for WNP implementation. (Items listed are not in chronological order and may not include all relevant suborder tasks.) Network must be SS7 capable. Load WNP switch software. Refer to TIA/EIA / IS-756-A, -B and -C for specifics on wireless network impacts of LNP. These documents define the WNP Database (NPDB) query and response protocol and procedures. Establish interconnection agreements as needed and/or required. 3-2

21 Define internal operational procedures for switch software implementation, maintenance and conflict resolution. Register, test and certify all physical interfaces, and sign Interconnection Agreements for all regions in which you will provide WNP service. Develop internal company operations procedures for LSMS/NPAC interface. These procedures should include repair, line provisioning and switch provisioning. Register, test and certify LSMS/NPAC physical interface. You may purchase and develop this interface yourself or use a third-party provider. Develop intercompany operations procedures for LEC-to-LEC interfaces. 3-3

22 c h a p t e r 4 : p ro v i s i o n i n g

23 c h a p t e r 4 : p r o v i s i o n i n g (P h a s e I I o f W N P) Overview This chapter summarizes several of the capabilities wireless SPs will be required to implement as part of Phase II of wireless NP, set for deployment by the FCC-mandated deadline of Nov. 24, Detailed procedures for provisioning will be provided in future versions of this document. SP-to-SP Provisioning NANC has developed a set of sequential functions and decision points for wireline SPs that have allowed for the provisioning and maintenance of end-users within an NP environment. The interworking of these functions and decisions define processes that will allow two or more LECs to interwork on an operational level. In a typical NP provisioning scenario, you could be the new or old service provider: New SP wins subscriber. Old and new SPs use the Local Service Request (LSR)/Firm Order Commitment (FOC) process to initiate porting. New SP notifies the NPAC of the change request via the SOA. Old SP uses SOA to concur with the port (optional). New SP coordinates any physical changes with the old SP. New SP adds central office (CO) switch translations for subscriber. New SP uses SOA to inform the NPAC to activate the port. NPAC downloads to all connected LSMSs to activate the subscription. LSMSs download updated routing information to the SCPs. Old SP removes CO switch translations for subscriber. Port is complete. The record for a transaction performed on a ported telephone number (TN) as it travels through the SOA is referred to as a subscription version. Subscription versions (SVs) involve porting a TN from one SP to another, as in the provisioning scenario above, or disconnecting a number that is no longer in use. You may also perform actions on subscription versions already in progress. These actions include canceling a request, placing the request in conflict (the two SPs don t concur on what action should be taken), and others. For more information on various wireline NP provisioning flows, see your regional NPAC documents accessible on the Internet at: 4-1

24 LSR/FOC Processes A large part of your intercompany processes will involve coordinating Local Service Requests (LSRs) between other service providers when porting numbers to your company. You will want to develop specific guidelines for completion of these LSRs. Some of the issues you will come across include: LRN=10 digit, but Ordering and Billing Forum (OBF) format is only six digits Specific edits given the 10-digit trigger Define location for old and new service provider Define which service provider is responsible for populating the fields in specific sections When a new SP issues an LSR, the old service provider will need to confirm the action by submitting a Firm Order Confirmation (FOC). You will want to establish guidelines for completing FOCs in the event another SP ports a number from your company. The regional flow scenarios at (noted in the section above) should help you approach LSR/FOC issues. NPA Splits The NANC Functional Requirement Specification (FRS) includes information on NPA-NXX splits. NPA-NXX flows continue to evolve as NP develops. It is the responsibility of each service provider to keep up to date with NPA-NXX changes. You can find the most recent information at and Number Pooling Industry mandates regarding number pooling currently affect wireline SPs only wireless SPs are exempt. Version requirements and download procedures for wireless SP participation in number pooling will be described in future versions of this document. 4-2

25 Code Opening Process As a service provider, required to deliver your subscribers calls to ported wireline TNs, you will need to ensure NPA-NXXs opened for porting are marked as portable in your MSC [as indicated in the Local Exchange Routing Guide (LERG)]. This code opening process must occur as soon as you prepare your MSC and begin accessing the NPDB. Failure to mark appropriate codes as portable in your MSC will result in defaulted dips and may result in additional charges from the ILEC. Keep in mind that NANC has defined generic process flows for opening NPA-NXXs for porting in an NP environment. As wireless porting begins (2002) you will need to be familiar with this process. Code Opening Processes currently affect wireline SPs only wireless SPs will implement this step in Phase II of implementation. Reserved TN Porting The process for porting reserved TNs essentially follows the same flows for porting regular numbers. It is important to note, however, that: All reserved TNs for the subscriber must be ported at the same time. The SP should make every effort to verify if a subscriber porting a number has reserved TNs. The subscriber will lose any reserved TNs that are not ported. When activating reserved TNs after porting, the subscriber must interface with the new SP. When a subscriber disconnects service, all numbers still reserved for the subscriber are returned to the original (donor) SP. 4-3

26 E911/911 Service Because implementation of number portability affects the routing of a call from emergency services to the callback number, wireless SPs need to be aware of the interaction of 911 service and number porting. While an MSC can connect to Emergency Service Providers (ESPs) in many ways the current arrangements typically do not automatically forward the mobile station call back number to the ESP. However, recent FCC rules dictate that an MSC must be capable of forwarding the correct call back along with information identifying the cell site of call origin. Therefore, the impact on the WNP-ready MSC is such that the MSC must be modified to forward the MDN and not the MSID. Further information on this issue should be obtained from your MSC software vendor or industry standards as they are published or by contacting the National Emergency Number Association (NENA) at: National Emergency Number Association 4789 Papermill Road Coshocton, OH Phone: (toll-free) (800) , Fax: (614) also, check: Operator Services Operator Service Providers (OSPs) may serve networks providing NP capability, or may interconnect with networks providing NP capability. Wireless SP switch [MSC] can connect to an operator tandem via several different ways in the traditional manner. There is no required change to this connection due to NP. However when a mobile station dials a call using 0+ or 0-, the call should route directly to the operator tandem where, if necessary the operator tandem will perform the query based on previously defined industry standards. Existing ANI information transfer and AMA recording at the operator tandem will be sufficient to support WNP. However, the MSC must be modified to forward the MDN and not the MSID as the ANI digits. Further information should be obtained from your appropriate OSP or industry guidelines as they are published. Payphones No obvious impacts as a result of NP have been identified for payphone SPs. Payphone SPs may have obligations or needs as a result of NP if they are also providing operator services. 4-4

27 c h a p t e r 5 : t e s t r e q u i r e m e n t s

28 c h a p t e r 5 : t e s t r e q u i r e m e n t s Overview Phase I testing for Wireless Number Portability, involves the following steps: 1. Internal switch testing of software load by Service Provider and Vendor 2. Query Launch and Response to and from the LNP database. Before offering commercial WNP service, you will want to test all elements to identify and resolve any technical problems. Testing will help ensure that you meet the FCC NP Commandments for minimum requirements which state that any long-term portability method may: 1) not result in unreasonable degradation in service quality or network reliability when implemented and, 2) not result in any degradation of service quality or network reliability when end-users switch carriers. The FCC ordered the Illinois Number Portability Workshop to conduct a field trial in the Chicago MSA to develop a test model for service providers across the country. The field trial encompassed network capability, billing and ordering systems, maintenance arrangements and data administration. In addition, all regions conducted test team forums to determine early participants, tools needed for testing and a test schedule. They also came together to ensure that testing in their areas followed the methods and standards initially established in the Illinois trial. It now becomes the responsibility of the wireless SPs to create a testing environment that will benefit all carriers as they prepare for porting. At this time the wireless industry has come together to expand the original test plan to include situations that are relevant to porting between all types of carriers. ILLUMINET strongly recommends that all wireless providers join in that effort. A test schedule timeline for wireless SPs is currently being drafted to assist in NP implementation. Details about this schedule will appear in a future version of this document. While the industry has guidelines for the three testing phases which are not all pertinent in Phase I implementation this document does provide an overview of all three phases of testing. Phase I: Internal acceptance testing Phase II: NPAC certification (SOA and LSMS) Phase III: Intracompany testing NOTE: If you choose ILLUMINET as your Service Bureau Provider we will assist with certain elements of Phase I and III testing as required by the customer. We have already performed Phase II testing for you. 5-1

29 Phase I: Internal Acceptance Testing All SPs must complete internal acceptance testing before entering into other testing phases. Phase I should cover all intranetwork elements including current systems that you have modified for WNP, and newly developed systems specifically designed for WNP support. All internal systems may require modification as Phase II is rolled out and will be thoroughly reviewed in the Phase II WNP Implementation Handbook. Testing should be performed with the same evaluation criteria that was used when initially installing equipment in a working network or lab environment. Testing must be conducted in a manner that does not affect any working services and does not impact the live network. In addition, testing must comply with existing test requirements, to adhere with all currently accepted network architectures and standards. Phase II: NPAC Certification The purpose of this phase is to verify that the interactions between a SP and the NPAC over the SOA and LSMS interfaces perform according to industry specifications. As a national service bureau, ILLUMINET is current with all certifications required for both these elements and we consistently meet the specifications for the interface as required by the industry for all new software releases or change management orders as directed by NANC. Phase III: Intercompany Testing For the SP using ILLUMINET, as the Data Access Provider, this phase of testing then becomes the most complex and cumbersome. It is very important that all carriers participate in this phase. As requirements are developed ILLUMINET will provide guidance in obtaining documents and will supply as much support as possible but the customer must dedicate resources to this effort. However, it is extremely important that wireless carriers participate in the actual requirements development and as much discussions surrounding this issue as possible. There will be more detailed information provided in the future. 5-2

30 c h a p t e r 6 : i l l u m i n e t s s o l u t i o n

31 c h a p t e r 6 : i l l u m i n e t s s o l u t i o n Overview ILLUMINET s WNP approach is national in scope, providing the ability to complete calls to ported wireline numbers as the FCC has mandated in Phase I and at the same time, setting the stage for Phase II of WNP and future NP enhancements for the industry (i.e., service type, location portability, number pooling). ILLUMINET s core competencies (database applications management, data administration, real-time call processing services through its SS7 and SCP network as well as its many wireless services), uniquely position ILLUMINET as a leading service bureau provider of NP. ILLUMINET delivers a turn-key solution for critical elements of WNP. Our solution for Phase I of WNP includes: Local Service Management System (LSMS): A system built to capture information from the NPACs and distribute it to network elements (i.e., our SCP/STP Platform, see below). Like our SOA, our LSMS is connected to all NPACs for time and cost savings and to provide you with uninterrupted and ubiquitous service. SCP/STP (Database) Platform A means of making information available to queries for call routing. ILLUMINET s database platform features an integrated design specifically developed for WNP, with the capacity to handle 20,000 transactions per second/per node. The platform minimizes delays that could occur if the SCP and STP functions were kept traditionally separate, as well as eliminating the need to initially purchase additional hardware and transmission links. The LSMS and database elements are available as part of ILLUMINET s Data Access service. The SOA is a separate service and will be available for Phase II. You may purchase just the components you need or a total package for complete WNP support. ILLUMINET will provide technical support for all testing and setup processes. Once implementation is complete, ILLUMINET customer support is available 24-hours-a-day, seven days a week. Setting Up With ILLUMINET Services 1. Execute and sign appropriate WNP contract(s) with ILLUMINET. 2. Identify points of contact at your company for WNP implementation (i.e., business, testing, customer service, etc.) 3. Complete an Operational Information Form and applicable setup forms for the services chosen, ( Attachment A Form for Data Access). These forms are available on-line. 6-1

32 4. Complete the ILLUMINET WNP Test Participation form, review test plans and coordinate schedules. This form is available from your ILLUMINET account manager 6. Contribute input for any customization requests, including test plans that you may require. 7. Identify significant dates, including switch-ready, test-ready and commercial service turn-up dates. 8. Negotiate interconnectivity agreements with other SPs. 9. Order, install and test SS7 facilities, if not already in place. 10. Install SSP hardware and software upgrades to support WNP. 11. Staff accordingly to support project. 12. Attend industry forums and regional committee meetings. 13. Investigate the pros and cons of joining the LLC. 14. Establish familiarity with industry documentation. ILLUMINET s Responsibilities to You 1. Ensure that LSMS connectivity to NPAC providers is ready for commercial service. 2. Staff to engineer, operate and maintain new WNP support infrastructure. 3. Provide SS7 network infrastructure for transport of queries to the LRN WNP database(s). 4. Continue visible presence at National/Regional meeting and monitor industry standard changes to keep current and provide timely service and information to our valued customers. 6-2

33 a p p e n d i c e s

34 a p p e n d i x a : a c r o n y m n s u s e d i n t h i s g u i d e ABS AIN ALI ALTS AM AMA ANI BLV CLASS CLEC CMRS CNAM CO CSS CTIA DA DN DPC EO ESP FCC FCI FOC FRS GSM GTA GTT IAM IIS ILEC IN INC INP ISUP ISVM IXC JIP LEC LERG LLC LNP LRN Alternate Billing Services Advanced Intelligent Network Automatic Location Indentifier Association for Local Telecommunications Services Account Manager (ILLUMINET) Automatic Message Accounting Automatic Number Identification Busy Line Verification Custom Local Area Signaling Services Competitive Local Exchange Carrier Commercial Mobile Radio Service Calling Name Delivery Central Office Customer Service Specialist (ILLUMINET) Cellular Telephone Industry Association Directory Assistance Directory Number Destination Point Code End Office Emergency Service Provider Federal Communications Commission Forward Call Indicator Firm Order Commitment Functional Requirements Specification Global System for Mobile (Communications) Global Title Address Global Title Translation Initial Address Message Interoperable Interface Specs Incumbent Local Exchange Carrier Intelligent Network Industry Numbering Committee Interim Number Portability Integrated Switched Digital Network - User Part Interswitch Voice Messaging Interexchange Carrier Jurisdiction Indicator Parameter Local Exchange Carrier Local Exchange Routing Guide Limited Liability Corporation Local Number Portability Location Routing Number A - 1

35 LSMS LSP MDN MIN MSC MSID NANC NANP NECA NENA NP NPAC NPDB NPREQ OI OBF OSP OSS SOA SCP SMR SMS SSN STP SV TN WNP WSP Local Service Management System Local Service Provider Mobile Directory Number Mobile Identification Number Mobile Switching Center Mobile Station Identifier North American Numbering Council North American Numbering Plan National Exchange Carrier Association National Emergency Number Association Number Portability Number Portability Administration Center Number Portability Database NumberPortabilityRequest Operational Information (ILLUMINET Form) Ordering and Billing Forum Operator Service Providers Operational Support System Service Order Administration Service Control Point Specialized Mobile Radio Service Management System SubSystem Number Signal Transfer Point Subscription Version Telephone Number Wireless Number Portability Wireless Service Provider A - 2

36 a p p e n d i x b : i n d u s t r y a n d r e g u l a t o r y b o d i e s Industry Numbering Committee (INC) ANSI T1S1 Signaling Protocols Congress and the Federal Communications Commission (FCC) State Utilities or Commerce Commissions North American Numbering Council (NANC) Number Portability Administration Centers (NPACs) NPAC Limited Liability Companies (NPAC LLCs) Ordering and Billing Forum (OBF) National Interoperability Industry Forum (NIIF) Wireless Number Portability Sub-Committee (WNPSC) Cellular Telephone Industry Association (CTIA) B - 1

37 a p p e n d i x c : i n d u s t r y d o c u m e n t a t i o n FCC Second Report and Order (97-289) re: FCC Docket No In the Matter of Telephone Number Portability; this document may be obtained on-line at: ATIS Standards - Technical Requirements for Number Portability - Switching Systems: This document defines the switch requirements for the Number Portability - Location Routing Number (LRN) method. It includes switching requirements for Switch Call Processing; Signaling and Protocol; Feature Interactions and Transparency; Switch Operations, Administration, and Provisioning; AMA Recording/Billing; and Maintenance and Test Call. This document may be obtained on-line at: ATIS Standards - Technical Requirements for Number Portability - Database and Global Title Translations: This document defines the requirements for an application residing on an SCP that performs NP query processing (i.e., receives a query from a switch and performs a LRN lookup in a database). It also defines the requirements for an Global Title Translation (GTT) function (also called a message relay function) that can be used to perform routing of SS7 messages for services (LIDB, CLASS, CNAM, ISVM) associated with a ported number. This document may be obtained on-line at: Interoperable Interface Specification for Number Portability Administration Center Service Management System [IIS-NPAC-SMS], from the North American Numbering Council (NANC): This document contains the information model for the NPAC/SMS mechanized interfaces. Both SOA and LSMS interfaces to the NPAC/SMS are described in this document. This document may be obtained on-line at: or, via links at: Functional Requirements Specifications for Number Portability Administration Center Service Management System [FRS-NPAC-SMS], from NANC: This document defines the functional requirements of a NPAC/SMS that is used to provide neutral, third party administration of the master routing information database used to support the operation of Number Portability. This document may be obtained on-line at: or links from North American Number Council Architecture and Administrative Plan for Local Number Portability from NANC-WNP Architecture Task Force, available at: gov/ccb/nanc WNPA Working Group section. NENA Recommended Standards for Service Provider Local Number Portability from the National Emergency Number Association (NENA): This document provides NENA recommended standards for all LSPs involved in providing dial tone to end-users and involved in SP NP. This document may be obtained on-line at: TIA/EIA INTERIM STANDARDS TIA/EIA-41-D Enhancements for Wireless Number Portability. Telecommunications Industry Association document provides recommendations for supporting wireless service portability. C - 1