Wireless Local Number Portability (LNP) -
V17.0
History
Log
Product
Description
Wireless Local Number Portability (LNP) is a procedure that is an interaction between Qwest and you in association with wireline to wireless LNP. It also addresses the call processing impacts for other telecommunications providers in a LNP environment.
Wireless LNP is defined by the Telecommunications Act of 1996 as: "the ability of users of telecommunications services to retain, at the same location, existing telecommunications numbers, without impairment of quality, reliability, or convenience when switching from one telecommunications carrier to another."
Local Number Portability (LNP) is also referred to as Service Provider Portability, because LNP enables end-users to retain the same Telephone Numbers (TNs) when the end-users change from one local service provider to another within a rate center. This also includes the ability for end-users to move from wireline service provider to a wireless service provider. The North American Numbering Council (NANC) recommended industry standards to the Federal Communications Commission (FCC) which adopted a further definition of Service Provider Portability allowing end-users to move within a Qwest® Rate Center and retain their TN.
Service Provider Portability differs from Location Portability, which is the ability to keep the same TN when moving to a new location outside the Qwest Rate Center. It also differs from Service Portability, which is the ability to keep the same TN when subscribing to new services, e.g., from Plain Old Telephone Service (POTS) to Integrated Services Digital Network (ISDN). Neither Location Portability nor Service Portability have been defined or deployed within the industry. LNP does sometimes allow end-users to subscribe to new services when they move from one local service provider to another or when their service is moved from one switch to another. LNP also allows geographic portability within a Qwest Rate Center. LNP fundamentally changes call processing in the public switched network and has been deployed in compliance with FCC and industry guidelines. LNP impacts all telecommunications providers, including Interexchange Carriers (IXCs) and wireless carriers as well as wireline local service providers.
Background
On February 9, 1999, the FCC granted the Cellular Telephone Industry Association's (CTIA) requested forbearance from Commercial Mobile Radio Service (CMRS) LNP requirements. The deadline for wireless LNP was November 24, 2003 for the top 100 MSA's. For all other areas the deadline was May 24, 2004. This does not relieve the CMRS carriers from the querying responsibilities that became effective on December 31, 1998.
Under the network architecture and the North American Numbering Plan (NANP) which was in effect before the implementation of LNP, a TN functioned like a switch address. Each TN was associated with the individual switch that was operated by a particular local telephone company in a specific geographical area. The area code, also referred to as the Numbering Plan Area (NPA), identified the general geographical area within which the switch provided service. The next 3-digits of the TN, referred to as Numeric Numbering Plan (NXX), also known as the Central Office Code identified the switch serving the end-user. The last 4-digits identified the specific telephone line serving the end-user's location.
Without number portability, if an end-user changed local telephone companies and received service from a different telephone company providing service from a different switch, the new provider typically assigned the end-user a new 7-digit TN. That new TN was directly associated with the new switch and the new telephone line. Without LNP technology, end-users were not able to retain their TNs when they changed local service providers.
Simple Port Request (SPR)
On November 8, 2007 the FCC expanded LNP to VoIP and in the Order, FCC 07-188, they further defined LNP to include SPR.
A Simple Port Request (SPR) is defined by the FCC in that order in footnote 153 as those Ports that:
- Involve a Single Line Account only
- Do not involve Unbundled Network Elements - (no Loop with Number Port);
- Do not include complex switch translations such as Centrex, DID Numbers, or AIN service
- Do not include Remote Call Forwarding numbers (for Qwest this includes Market Expansion Line (MEL) Service).
- Do not include multiple services on the Loop such as Broadband, or other Data services
- Do not include a line that has been Resold (RSID or ZCID)
The FCC's order established that a maximum of four fields can be used for validation. The fields that may be required for End User Validation are:
- Customer Account Number (includes 10 digit telephone number plus CUS Code as assigned by Qwest)
- Zip Code (not applicable (NA) for Qwest)
- Telephone Number to be Ported
- Pass Code (NA for Qwest)
LNP Network Architecture Overview
The industry solution for long-term number portability is a Location Routing Number (LRN) architecture. Under the LRN architecture, each switch is assigned a unique 10-digit LRN that identifies the location of that switch. The first 6-digits identify an NPA and NXX code that is assigned to that switch and the last 4-digits are in line number format. It is important to note that the LRN is not a TN; it is merely the identifier of the switch to which a TN is ported. The NPA and NXX identifies a particular switch, the 4-digit line number may be assigned as a working TN in that switch although it is not recommended.
Each ported end-user's TN is matched in a regional Number Portability Administration Center (NPAC) database with the LRN for the switch that currently serves that TN. If the TN is not ported, the TN does not appear in the Local Service Management System (LSMS) number portability database and the call is routed to the switch that was originally assigned the NPA-NXX.
In a LNP environment, it can no longer be assumed that the NPA-NXX code holder actually serves the end-user. During call setup, a LNP database in the Signaling System 7 (SS7) network is queried to determine which switch actually serves the dialed TN. If the TN is ported, the Called Party Number (CdPN) field is moved into the Generic Address Parameter (GAP) field, and the LRN information is overlaid in the CdPN field so the call can be routed to the proper terminating switch. The terminating switch then completes the call to the end-user based on the data contained in the GAP.
LRN Assignment
To assign a LRN, you must obtain an NPA-NXX from the North American Numbering Plan Administrator (NANPA) for each LNP capable switch.
The industry LRN Assignment Practices were developed by the Industry Numbering Committee (INC) and issued by the Alliance for Telecommunications Industry Solutions (ATIS) and Technical Requirements No. 2 prepared April, 1999 by the T1S1.6 Working Group on Number Portability and issued by ATIS.
Specifically, the INC practice states that an NXX will not be assigned to a service provider for the sole purpose of establishing an LRN unless that service provider's switch or Point of Interconnection (POI) does not yet have an LRN for the Local Access Transport Area (LATA) where they intend to provide service". The T1S1.6 technical requirement state: "only one NPA-NXX is needed for the first 6-digits of an LRN per LATA to identify the switch".
Qwest had previously recommended a LRN be assigned for each Qwest Rate Center that you intend to serve. All carriers, including Qwest, have concerns regarding TN conservation and in some cases assignment of new NPA-NXXs at a Qwest Rate Center level may not be necessary. To ensure conservation of numbering resources, and to comply with the INC practice, Qwest allows the ability to use one LRN to serve multiple Qwest Rate Center locations.
If you have already established a LRN for a particular Qwest Rate Center, you may continue to use that established LRN. If you do not need NPA-NXX codes that were assigned at a Qwest Rate Center level, you may notify Qwest to change from the LRN(s) assigned at a per Qwest Rate Center level to LRN(s) assigned at a per switch, per LATA level or for some lesser geographic area. Qwest will make appropriate network rearrangements to accommodate such change(s). You may return the unused NPA-NXX codes to the number administrator.
In those instances where you have not requested and have no need for an NPA-NXX for a particular Qwest Rate Center, you may notify Qwest of your desire to establish an LRN per LATA, or for some lesser geographic area. This notification must occur as soon as reasonably possible, but no later than at the time you first arrange for your POI, Local Interconnection Service (LIS) trunking, etc.
Single LRN per Switch, per LATA
Information on Single Location Routing Number can now be found at this web site:
LNP Query Services
Qwest provides Default Query Services whenever we receive unqueried calls from other telecommunications providers, including CLECs, Incumbent Local Exchange Carriers (ILECs), IXCs, or Wireless Service Providers (WSPs), which require a query in order to be terminated efficiently. Qwest also offers Direct Query access to the LNP database.
NPA/NXX Migration or Reassignment
When you plan to provide service for all assigned TNs in a particular NPA/NXX, you should request reassignment of that NPA/NXX in the Local Exchange Routing Guide (LERG) in lieu of porting. In this situation NPA/NXX migration supports network efficiency and is the preferred industry method. To arrange for a migration of an entire NPA/NXX, contact your Qwest Service Manager.
LNP Administration
There are seven regional databases that serve specific geographic areas. The Western Region database serves Qwest's 14-state local service area plus Alaska. A neutral third party, called the Local Number Portability Administrator (LNPA) administers these regional databases.
The FCC adopted the NANC recommendation that the administrative functions of the LNPA include all management tasks required to develop and administer the regional databases, called Number Portability Administration Centers (NPACs).
Number Portability Administration Centers (NPACs) responsibilities include:
- Management tasks required to run the NPAC
- Works with the users to update data tables required to route calls for ported local numbers or required for administration
- Responsible for NPAC SMS log on administration, user access, data security, user notifications, and management and is the primary contact for users who encounter problems with NPAC system features
- Provides the users with a central point of contact for reporting and resolution of NPAC problems
- Provide coordination/resolution of problems associated with system availability, communications and related capabilities
- Will provide reports to regulatory bodies as required
Number Portability Administration Centers (NPACs) hours of operation are 7:00 AM to 7:00 PM (CST/CDT), Monday through Friday. After hours are handled on a pager/call out basis.
Click here to refer to North American Numbering Council. http://www.fcc.gov/wcb/cpd/Nanc/
Managed Cuts
Managed Cuts are available for LNP in the following arrangements:
- Qwest Initiated Managed Cut
- WSP Initiated Managed Cut
When a Qwest Initiated Managed Cut or WSP Initiated Managed Cut is requested, Qwest will initiate a telephone call and/or arrange a meeting with you to discuss detailed information regarding the Managed Cut.
Qwest Initiated Managed Cut
Qwest will initiate a Managed Cut when the 10-digit unconditional trigger or Line Side Attribute (LSA) cannot be set or when the port request for an account exceeds 2000 TNs or 200 trunks. Qwest Initiated Managed Cuts are scheduled within the normal business hours, at no additional charge. If you request a Frame Due Time (FDT) that is outside the normal business hours, the terms, conditions and prices of the LNP Managed Cut offering will apply.
WSP Initiated Managed Cut
A WSP Initiated Managed Cut is available under the "LNP Managed Cut offering.
If the LNP Managed Cut offering is not included in your Wireless Interconnection Agreement, contact your Qwest Sales Manager to request a LNP Managed Cut amendment.
Availability
The FCC addressed specific requirements for providing number portability on an interim basis, known as Interim Number Portability (INP) as well as development and deployment of the long-term solution known as LNP. Qwest has deployed LNP in nearly every end office.
To determine LNP availability for Qwest wireline switches, refer to Network Disclosure.
Qwest has offered INP since 1996 utilizing Remote Call Forwarding (RCF), Direct Inward Dialing (DID®) service and Directory Number Route Indexing. INP is only offered in those few locations where LNP is not deployed. You may continue to request INP in a non-LNP capable switch.
If you want LNP capability in a switch where Qwest has not deployed LNP, submit a LNP Bona Fide Request (BFR) letter to Qwest at any time, at no charge. This LNP BFR process is separate from the BFR process for interconnect services..
Any certified WSP may submit a LNP BFR letter to request LNP capability in a switch where LNP has not yet been deployed. The request must include the 11-digit CLLI™ code of each Qwest switch being requested to become LNP capable.
The following outlines what will take place upon Qwest's receipt of the LNP BFR letter:
- Confirm received letter within 10 business days
- Deployment dates communicated no later than 45 calendar days
- The timeline for conversion is within 180 days
- Qwest switches selected through the LNP BFR process will be posted on the network disclosure web site
Contact your Qwest Service Manager to submit a LNP BFR letter.
Terms and Conditions
Wireless carriers are not required to enter into section 251 interconnection agreements with wireline carriers solely for the purpose of porting numbers.
Qwest will port numbers to wireless carriers where the requesting wireless carrier's "coverage area" overlaps the geographic location of the rate center in which the customer's wireline number is provisioned, provided that the porting-in carrier maintains the number's original rate center designation following the port. The wireless "coverage area" is the area in which wireless service can be received from the wireless carrier. In order to maintain the numbers original rate center designation following the port, the wireless carrier will be required to establish local trunking and define how and where to route calls to their serving switch.
Wireline subscribers that call wireless customers are bound by Rate Center and Local Calling Area (LCA) boundaries.
Service Restrictions
Local Number Portability (LNP) Triggers are not expected to be placed on Service Codes or Service Access Codes (911, 411, 800, 866, 877, 888, 900, 500) so queries will not be performed on these call types. In addition, queries will not be performed in the originating switch for 0+, 0-, or 1+ calls routed to an IXC.
The following service restrictions apply:
Telephone numbers may be ported only within the constraints placed on them by the FCC and specific state regulations.
- 555, 960 and 976 NXXs
- 500, 700, 800, 866, 877, 888, 900, 911 services
- Other N11 codes, e.g., 411, 511 etc.
- Qwest Public Coin or Semi-Public Coin
- Numbers used for mass calling events - Refer to North American Numbering Council (NANC). Once displayed, click on "LNPA Working Group then select "Documents". When this page is displayed, click on "High Volume Call in Networks Report, 5/7/98".
- Reserved Numbers
- Qwest's policy regarding the porting of reserved TNs is to allow porting if the reserved numbers are identified on the end-user service record.
- Porting service request will not be taken on unassigned, previously owned, disconnected, disconnected following suspension for non-payment, or vacant TNs.
- Numbers associated with Paging Services
Technical Publications
Technical characteristics are described in Technical Publication, Qwest Common Channel Signaling (CCS) Network Interface Specification, 77342.
Pricing
Rate Structure
Rate structure information can be found in your Interconnection Agreement.
Charges for the LNP Managed Cut Offering
LNP Managed Cut Rates are available in Exhibit A or the specific rate sheet in your Interconnection Agreement.
The charges you will incur for the LNP Managed Cut are dependent upon the Frame Due Time (FDT). The rates are based upon whether the request is within or outside Qwest's normal business hours.
Charges for LNP Managed Cuts will be based upon the actual hours worked in ½ hour increments multiplied by the number of Qwest personnel actively participating in the cut.
In those situations where Qwest determines a need to manage a cut, (e.g., the 10-digit unconditional trigger cannot be set) those LNP Managed Cuts would be scheduled during normal business hours and there would be no charge. The following matrix provides examples of when charges apply and when there is no charge.
| Managed Cut Activity |
(During Normal Business Hours) |
(Outside Normal Business Hours) |
| You request a LNP Managed Cut |
Charge |
Charge |
| Qwest requires a Managed Cut for DID in the DMS™10 switches |
No Charge |
Charge (you request the cut outside normal business
hours) |
| Qwest recommends a Managed Cut for more than 2000 Telephone
Numbers and/or more than 200 Trunks |
No Charge |
Charge (you request the cut outside normal business
hours) |
Qwest Customer Service Inquiry and Education (CSIE) hours of operations are described in Wholesale Customer Contacts.
Qwest will schedule the appropriate number of employees for
the cut, based upon information provided by you during the
coordination meeting. If such information changes and requires
modifications during the cut, and as a result, non-scheduled
employees are required, you will be charged a three-hour minimum
callout per each additional non-scheduled employee. If the
cut is either cancelled, or a supplemental service request is submitted
within 24 hours of the negotiated FDT to change the Due Date
(DD), you will be charged a three-hour minimum.
NOTE: Charges are rounded up. For example, if a LNP Managed
Cut requires 2 hours and 10 minutes, the rates will apply
for five 1/2 hour increments, per person.
Charges will be calculated based on actual 1/2 hours required for the cut, times the number of employees required for each 1/2 hour of the cut, multiplied by the appropriate rate based on the day and time of the cut. Managed Cuts during Qwest's normal business hours will be charged at a Standard rate. If the FDT is outside Qwest's normal business hours on Monday through Saturday (excluding holidays), the charge will be at an Overtime rate. If the FDT is on a Sunday or a Holiday, the charge will be at a Premium rate.
Example: You and Qwest preplan a 10:00 PM cut on a Monday
(outside normal business hours). The cut takes 1 1/2 hours, and
three Qwest employees participate. The applicable charges
are as follows:
Overtime rate times 3 (people) times 3 (1/2 hour increments) = manual cut charges.
Rates
Wholesale rates for this product or service, including tariff references and any applicable discounts, are provided in your current Interconnection, Resale, Commercial, or other governing agreement.
Tariffs, Regulations, and Policies
Tariffs, regulations and policies are located in the state specific Tariffs/Catalogs/Price Lists.
Qwest's LNP deployment and federal tariff filings are available in the FCC.
Features/Benefits
| Features |
Benefits |
| End-users can retain their present TN |
Easier to attract new end-users when they
do not have to change their TN |
| Qwest has widespread deployment of LNP
throughout its 14-state local service territory |
Widespread deployment gives you more efficient
market entry capabilities |
| Qwest's portability platform allows numbers
to move from switch to switch within a Qwest Rate Center |
Platform portability paves the way for
future number conservation through number pooling |
Applications
Contact your Account Team / Sales Executives and Service Managers for information.
Implementation
Porting Process Overview
When an end-user changes from one service provider to another and wants to retain their TNs, the WSP who "wins" the end-user will "port" the end-user's number from the former service provider. Coordinated service request activity by the previous and new local service providers removes the end-user's TN from one provider's records and establishes it in the records of the other, establishing the new LRN for call routing purposes. This service request activity is electronically transmitted (uploaded) communicating the new LRN to the administrator of the relevant regional database. This will pair the end-user's original TN with the LRN for the switch of the new WSP, allowing the end-user to retain the original TN. The regional database administrator (NPAC) will then electronically transmit (download) LRN updates to service provider-operated Local Service Management System (LSMS). Each service provider will distribute this information to Service Control Points (SCPs) or Signal Transfer Points (STPs) that the service provider uses to store and process data for routing calls to ported numbers.
Following is a diagram of the basic network elements that are required in a LNP environment:
LNP Call Routing Descriptions
To route an interswitch telephone call to a location where number portability is available, determine the LRN for the switch that serves the terminating TN of the call. When number portability is available for an NXX, "query" all interswitch calls to that NXX as appropriate, to determine whether the terminating end-user has ported TN. You will accomplish this by sending a signal over the SS7 network to retrieve from a SCP or STP the LRN associated with the called TN.
The FCC has endorsed an "N minus one" (N-1) querying protocol. Under this protocol, if you are the N-1 carrier, you 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. Thus the N-1 carrier (i.e. the last carrier before the terminating carrier) for a local call will usually be the billing owner of the call. The N-1 carrier for an interexchange call will usually be the calling end-user's IXC. If you are the N-1 carrier you may perform your own querying, or you may arrange for other carriers or third parties, or for Qwest to provide querying services on your behalf.
To better understand when queries are performed, download
LNP
Call Flow Diagram.
Following is a simplified trunking and SS7 diagram for connections
within a ported area:
Click here to refer
to NANC.
LRN Trunking, Signaling and Dialing Plans
A LRN looks just like a TN to a switch that is using the
LRN for call routing purposes. It is very important to understand
your signaling requirements and the result of the LERG inputs
to set up your networks appropriately for LNP.
An LRN definition was provided to the industry via the NANC
LNP Architecture and Administrative Plan (Issue 2, Revision
0, April 14, 1998):
"LRNs are 10-digit numbers that are assigned to
the network switching elements (Central Office - Host and
Remotes as required) for routing of calls in the network.
The first six digits of the LRN will be one of the assigned
NPA NXX of the switching element. The purpose and functionality
of the last four digits of the LRN have not yet been defined
but are passed across the network to the terminating switch."
This definition can potentially create some confusion regarding
whether a 7-digit or 10-digit LRN is to be transmitted between
Service Providers for LNP calls. A 7-digit or 10-digit LRN
transmit option will work based on how the participating Service
Providers have set up their trunking and signaling network.
It is vital that Service Providers on both ends of a Trunk
Group understand what is being sent and received. It is also
important to understand that the 7-digit or 10 digits are
counted from right to left.
Technically, an LRN in a signaling message looks just like a TN. The switch uses the LRN for routing purposes, and handles the LRN just like a called party TN. The switch determines where to route a call by the NPA NXX included in the LRN. This routing information provided in Section 4.6 of the LERG determines where and how (signaling) that the NPA NXX should be routed. The LERG input includes the number of digits signaled, whether SS7 or Multi-Frequency (MF), on trunk groups that are used by the complex translations routing group to complete the translations for a particular switch.
Timing and Coordination of Changes in the Local Exchange Routing Guide (LERG) and Switch
Changes that are entered into the LERG, intended for the network, have the potential to affect the end-user's telephone service. When signaling changes are required, it is critical that the timing considerations for LERG changes be fully understood and adhered to, including the Maintenance Window Policy.
Guidelines for timing requirements are described in Central Office Code Assignment Guidelines. You will be able to locate INC Document Number 95-0407-008, Title CO Code (NXX) Assignment Request & Confirmation Form, Part 3. Upon consideration of the timing guidelines, complete this form and submit your LERG changes,
Changes to LRNs also require this same type of planning and
coordination, as well as coordination with the NPAC to perform
routing changes and mass updates. Changes to LRNs may be caused
by various reasons, such as switch replacement, reassignment
of NPA-NXX codes from one service provider to another and/or
NPA splits.
For WSPs, the interfacing company's Service Manager must be notified of the LERG updates, including 7 to 10-digit, LRN or other types of changes so they can be scheduled and coordinated with the Routing Translations groups in both companies. As a result of this coordination and planning for the minimum elapsed time, as prescribed in the Industry Guidelines, the involved Service Providers will be able to make the necessary changes to their respective networks on the "EFF DTE" shown in the LERG without disruption of end-user telephone services.
Dialing Plans
The state utilities commission determines dialing plans. The individual service provider determines signaling plan. A signaling plan differs from a dialing plan for a local calling area. The information in the previous section addresses 7-digit or 10-digit LRN Trunk Signaling in the signaling network.
Signaling changes may be required as a result of state-ordered
dialing plan changes. Changes to a signaling network resulting
from dialing plan changes may require coordination between
CLECs, and this coordination is addressed in the ATIS Guideline
referenced above.
Click here to review Dialing
Plans within Qwest territory.
Following are examples of some specific Dialing Plans:
| Minneapolis, MN |
Seattle, WA |
Denver, CO |
- Multiple NPAs in the Minneapolis Metropolitan
Statistical Area (MSA); NPAs are geographically assigned
to a particular municipality and there may be multiple
NPAs within a Qwest Rate Center.
- Commission ordered TN porting cannot occur between NPAs.
- If dialing outside of your own NPA, 10-digit dialing
is mandatory but not necessarily a toll call. |
- Multiple NPAs, not overlaid.
- If dialing within your own NPA, 7 digit or 10-digit
dialing is permissive.
- If dialing outside of your own NPA, 10-digit dialing
is mandatory but not necessarily a toll call.
- Porting between the NPAs is not permitted. |
- Multiple NPAs; this is an overlay network.
- Porting between NPAs is permitted.
- 10-digit local dialing is mandatory in all cases. |
Product Prerequisites
If you are a new WSP and are ready to do business with Qwest, view Getting Started as a Facility-Based WSP. If you are an existing WSP wishing to amend your Interconnection Agreement or Customer Questionnaire, additional information is located in the Interconnection Agreement.
The following are actions that must be completed by you prior
to submitting a service request to port a TN:
- Provide after hours contact personnel, who will be responsible
for general problem resolution
- Provide a valid FAX number that is operational Monday-Friday,
5:00 AM to 10:00 PM, Central Time Zone
- Test LSMS and the Service Order Administration (SOA) functions
Establish Signaling System 7 (SS7) Requirements
Your SS7 network must adhere to the industry standards established
for LNP. There are impacts to the Line Information
Data Base (LIDB), Calling Name (CNAM), Custom Local Area Signaling
Service (CLASS™), and Inter-Switched Voice Messaging
services as a result of the industry standards. It is critical
that each company's SS7 technical experts review the requirements
and your specific deployment plans as related to SS7 message
queries. The use of an independent SS7 network and/or SS7
hub provider could introduce additional requirements. If there
is another provider of SS7 service involved, they should be
a part of the requirement review.
Establish E911 Requirements
All wireless providers must adhere to the National Emergency Number Association (NENA) requirements for wireless LNP.
Wireless E911 activities are described in Wireless E9-1-1 (W9-1-1) CellTrace™ and CellTrace Plus™
Determine Testing Requirements
If you wish to perform testing to ensure that your signaling,
switching, databases, systems and processes are functioning
properly prior to submitting LNP requests, you may want to
contact your Qwest Service Manager.
When contacting Qwest, provide information about your
testing requirements:
- The serving area you plan to test within
- The switch(es) involved in the testing
- How many test numbers you need Qwest to establish and
in what locations
- The timeframe you prefer to do the testing
Also, provide as much information as possible about
the type of testing you intend to perform. For example, are
you planning to:
- Perform call processing tests only, to ensure that your network and signaling databases are capable of delivering calls to ported and/or non-ported TNs? (This type of testing may be applicable to wireless carriers and IXCs as well as wireline Local Exchange Carriers (LECs.)
- Perform intra-company tests only, to ensure your switching,
signaling and databases meet the LNP operational requirements
and that you have the systems and processes in place to
accommodate the porting of TNs?
- Perform end-to-end, inter-company testing that includes
submitting service requests to port test TNs between Qwest and your
company?
Once you have provided your initial testing information to
Qwest, your Qwest Sales Executive or Service Manager will
establish a meeting with you to further define your testing
requirements, to identify the key personnel for conducting
the test, from both your company and from Qwest, and to establish
the testing timeline. Additional meetings may need to occur
prior to the testing, and may include identification of test
scripts, if appropriate.
Qwest will initiate service request to establish test accounts,
based on your testing requirements, and will provide information
about the test accounts, including the account name(s), TNs,
and DD of the new connect service request(s). If inter-company
testing is required, critical dates will be jointly established
and may include dates for:
- LSR exchange
- Firm Order Confirmation (FOC) exchange
- Porting of the TN(s)
- Disconnecting test account(s)
During inter-company testing, you will be responsible for:
- Ensuring the subscription is sent to the NPAC
- Verifying activity on subscriptions at the NPAC (i.e.
T1 and T2 timers)
- Completing the provisioning on your switch for the test
account(s)
- Sending the activation to the NPAC to port the TN(s) on
the requested DD
Upon completion of intra-company testing, you will notify
Qwest that the test accounts may be disconnected. For inter-company
testing, you will need to disconnect the Qwest TNs from your
switch and return them to Qwest, the original code holder.
If test TNs have also been ported from your switch to Qwest,
Qwest will need to disconnect the TNs and return them to you.
Pre Ordering
General pre-ordering activities are described in the Pre-Ordering Overview.
Requirements for pre-ordering are described in Local Service Ordering Guidelines (LSOG) Pre-Order.
Other activities to perform prior to submitting a service request to port a TN are:
- Review the end-users Customer Service Record (CSR) verifying all numbers to be ported. All services, including custom ring, when associated with ported TNs, will be disconnected. If you require rearrangement, prior to the port request activity, you and your end-user will contact the appropriate Qwest Department currently servicing the end-user customer to make these changes.
- A reserved number can be identified by the RTNF FID. (e.g. NDNRN/RTNF 111 555-5555)
- If the number you are porting is working a Centrex 21 see the Terms and Conditions section of Resale - Centrex 21.
Ordering
General ordering activities are described in the Ordering Overview.
Ordering standards are developed at the national Ordering
and Billing Forum (OBF).
Local Number Portability service requests are submitted using the following LSOG forms:
- Local Service Request (LSR)
- For Wireline to Wireless LNP, refer to the Number Portability Direction Indicator (NPDI) field for additional required entries
- End User (EU)
- Number Portability (NP) or
- Loop Service with Number Portability (LSNP)
Field entry requirements are described in the LSOG.
Service requests should be placed using Interconnect Mediated Access (IMA) Electronic Data Interchange (EDI), IMA Graphical User Interface (GUI), or faxed to (888) 796-9089.
Simple Port Request (SPR) service requests are submitted via IMA GUI or XML only using the SPR Form. Field entry requirements for a SPR are described in the LSOG.
When a Qwest account or an account owned by you has Qwest High Speed Internet (HSI) and you want to change the HSI to a Stand Alone HSI account with a new data TN at the time of port then you need to do the following:
- Populate the Manual indicator field with the letter "Y" and in the Remarks section add "Change HSI to a Stand Alone HSI". NOTE: the same Qwest Stand Alone HSI speed must be available.
If the number(s) you are porting are reserved numbers, the LSR must be issued manually & faxed to Qwest.
If you are requesting a number port for a telephone number that has an associated custom ring number, you must request the port of the custom ring number or it will be disconnected.
Wireless Type 1 service is a non-IMA product and is handled by the Wholesale Service Center. Wireless Type 1 to Wireline or Wireless LNP service requests should be faxed to 877 237-7149. The cover letter should indicate: Attn: Wireless Type 1 Group
When porting DID numbers associated with a VOIP service, this will not be treated as a simple port and you must mark the Manual Handling field of the LSR with a Y, and add a Remark indicating that the number(s) being Ported are "associated with a VOIP service".
In addition, either the AN or ATN field of the LSR must be populated with the Telephone Number or Account Number of the End User whose service is being ported.
Hours of Operation
Qwest Customer Service Inquiry and Education (CSIE) telephone numbers and hours of operations are described in Wholesale Customer Contacts.
Number Portability Administration Center (NPAC): has defined their standard hours of business for LNP
as 7:00 AM. to 7:00 PM, (CST/CDT), Monday through Friday.
Non-business hours/days are defined as 7:01 PM to 6:59 AM
Monday through Friday, and all day Saturday and Sunday. NPAC
holidays include New Years Day, Memorial Day, July 4th, Labor
Day, Thanksgiving Day, Christmas Eve Day and Christmas Day.
Normal hours of operation
for activating subscription DD and Frame Due Time (DD/FDT),
submitting service requests to the NPAC, error resolution, cancellation,
conflict setting, and resolution will be Monday through Friday
during the NPAC standard hours of business.
If you require any additional assistance, contact
your Qwest Service Manager directly.
Directory Listings
An ACT entry of "V" will discontinue listings associated with the port activity (all listings are removed). If the service request will port only a portion of an account, including the Qwest billing TN, the LSOG forms (LSR, EU, and NP) will be required from you.
Supplemental Input
To change the due date or cancel service request, issue a supplement to your service request.
Note: When a DD supplement or cancel cannot be submitted due to a system outage, verbal requests will be accepted through the escalation process. Following restoration of the system, submit a supplement for the DD change or cancel.
To determine the correct process for DD changes and/or cancels, follow the matrix below.
|
IF your supplement is submitted:
|
THEN:
|
| Before 8:00 PM Mountain Time, on the same day as the requested DD |
Submit a supplement to your service request via IMA or Fax |
| After 8:00 PM Mountain Time or before 12:00 PM Mountain Time the next business day after the service request DD |
Submit a supplement your service request via IMA or Fax.
(This is considered late notification.) |
| After 12:00 PM Mountain Time the next business
day after the requested DD |
Submit a supplement to your service request via IMA Fax
(This is considered late notification.) |
| Before 3:00 PM Mountain Time, two business days after the requested DD |
Submit a supplement to your service request via IMA Fax
Contact the CSIE Call Center Representative to initiate escalation. (This is considered late notification.) |
After 3:00 PM Mountain Time, two business days after
the requested DD
Note: See Failed Port Activities or End-User Out Of Service (OOS) for additional information. |
Contact the CSIE Call Center Representative to initiate an escalation ticket for the late notification.
Note: You may still be required to send in a supplement, the CSIE will advise you if you need a supplement or a new service request. |
Three or more days after the requested DD
Note: See Failed Port Activities or End-User Out of Service (OOS) for additional information |
Contact the CSIE Call Center Representative to initiate an escalation ticket for the late notification.
Note: You may still be required to send in a supplement to your service request, the CSIE will advise you if you need a supplement or a new service request. |
NOTE: You may contact the CSIE Call Center Representative at any time concerning your DD change or cancel request.
The following conditions do not apply to supplements, you must issue new service requests to:
- Add new TNs to port
- Change the New Service Provider (NSP) ID or the Old Network Service Provider (ONSP) ID
Managed Cuts
- LNP Managed Cut Scheduling
Up-front planning and coordination with Qwest is required
to establish the date and time for an LNP Managed Cut. All
requests will be processed on a first come, first served
basis and are subject to Qwest's ability to meet a reasonable
demand. Qwest will coordinate with you for an agreed upon
FDT and FOC
prior to issuing the FOC. Generally the FOC date will not
exceed the standard interval.
- LSR Entries for LNP Managed Cuts
You may request an LNP Managed Cut by submitting a service request
and designating the request as a "Managed Cut" in the Remarks
section of the LSR. Specifically, LNP Managed Cuts
require a notation in the Remarks and DFDT sections of the
LSR, e.g.:
Remarks = Managed Cut
DFDT = Anytime 24x7
When submitting a service request in the IMA GUI or EDI, you must
populate the Manual indicator field with the letter "Y".
All negotiated requests must be scheduled on the LNP
Operations schedule in 30-minute time slots.
- WSP Responsibilities
You will need to schedule the appropriate personnel for the negotiated FDT for the LNP Managed Cut. You are also responsible for NPAC coordination if a Managed Cut is scheduled outside the NPAC's normal business hours.
Provisioning and Installation
General Jeopardy Notification information is found in the Provisioning and Installation Overview.
General Reject Reasons are found in Ordering
Overview.
There are specific resolutions for Jeopardy after FOC conditions
that apply to LNP DDs. To view those resolutions, download
Jeopardy
after FOC Process.
Standard Intervals for LNP
Service interval guidelines are found in the Service Interval Guide (SIG).
Listed below is an example of the steps taken in the port
out process for 1-5 lines, simple, standard DD request. The
steps for six or more lines or complex services will be the
same, however the timing intervals will be based on standard
intervals for the specific product type.
| Step |
Process |
Result |
| 1 |
WSP completes sale to new end-user, validates CSR and
completes service request forms |
New Network Service Provider (NNSP) submits service request to Qwest (Day 0) |
| 2 |
Qwest receives and processes the service request. |
Qwest provides FOC to NNSP and submits request. Subscription is created at NPAC. (Day 1) |
| 3 |
WSP receives FOC and sends create message to NPAC to
match subscription activity |
Matching subscription activity shows concurrence.
NOTE: When a subscription is received at the NPAC from either the ONSP or NNSP, the t1 timer (9 business hours) begins. If the NNSP or the ONSP does not match the subscription before the t1 timer expires, then the t2 timer begins and runs 9 business hours.
If there is no matching subscription from the ONSP and the t1 and t2 timers have expired on the NNSPs subscription, the NNSP may activate the port on the DD without concurrence from the ONSP.
The subscription, if not activated, is cancelled by the
NPAC after 30 days. |
| 4 |
Qwest sets the 10-digit unconditional trigger no later
than 11:59 PM the day before the DD. (Day 2) |
10-digit trigger set (Day 2) |
| 5 |
NNSP sends activation to NPAC to port TN on DD/FDT.
NPAC broadcast sent to all Service Providers. (Day 3) |
Broadcast received, number is ported to NNSP. Qwest
service order is completed. (Day 3) |
| 6 |
Service Order completed |
Data transmitted to E911 in daily batch file after service
order completion |
| 7 |
Disconnect and removal of switch translations is completed
in Qwest switch no earlier than 11:59 PM the next business
day after the DD |
|
Customers with Disabilities | Servicio al Cliente en Español | Tariffs
