Local Number Portability (LNP) is defined by the Federal Communications Commission (FCC) as "the ability of users of telecommunications services to retain, at the same location, existing telecommunication number(s), without impairment of quality, reliability or convenience when switching from one local telecommunications carrier to another". Detailed information is described in Local Number Portability (LNP).
This PCAT addresses Port In activity using LNP. Port In is defined as the ability of End-Users to retain the same telephone number(s) when changing from one local service provider to another within a Rate Center. Either a new or existing Qwest end-user customer has requested that TN(s) currently provided by a different Network Service Provider to be ported into the Qwest network. These TN(s) may be established as POTS, DID TNs with trunks or other types of services.
"Port In" is where a Resale, commercial local exchange services products, e.g. Qwest Local Service Platform™ (QLSP™) or Public Access Line (PAL) provider request their newly acquired end-user's Telephone Numbers (TNs) be ported from a Competitive Local Exchange Carrier (CLEC) switch into a Resale, Resale CTX, Qwest commercial local exchange service or PAL provider service to be served by a Qwest switch.
The Port In process is offered on the following products or services:
To determine LNP availability, refer to Network Disclosure 414.
Service Restrictions
The following service restriction applies:
Local number portability (LNP) is confined to Service Provider Portability, either within the area serviced by the same central office or between areas serviced by different central offices within the same rate center.
In addition, the porting of certain TN(s) will not be provided on all porting activity when the following circumstances or services exist:
Technical characteristics, including Network Channel /Network Channel Interface (NC/NCI™) codes, are described in Technical Publication, Qwest Common Channel Signaling (CCS) Network Interface Specification, 77342.
Recurring and nonrecurring charges do not apply to Port In, charges are based on products and services ordered.
Rates Section does not apply to the Port In process.
Refer to Terms and Conditions of this PCAT for Regulations and Policies.
If you are a new CLEC and are ready to do business with Qwest, view Getting Started as a Facility-Based CLEC or Getting Started as a Reseller. If you are an existing CLEC wishing to amend your Interconnection Agreement or New Customer Questionnaire, additional information is located in the Interconnection Agreement.
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.
General ordering activities are described in the Ordering Overview.
Port In service requests are submitted using the following Local Service Ordering Guidelines (LSOG) forms, as applicable:
Field entry requirements are described in the LSOG.
Service requests should be placed using Interconnect Mediated Access (IMA) Extensible Markup Language (XML), IMA Graphical User Interface (GUI), or faxed to (888) 796-9089.
The Port In service request must include the following:
LSR
If the product requested does not require appointment access, DFDT may be anytime between 7:00AM - 7:00 PM MTN (e.g. DID telephone numbers).
RS, CRS, PS and DRS
RS, CRS and PS
To ensure a successful Port In, all facilities and/or trunks must be installed and tested prior to the Port In due date. If facilities and/or trunks are not existing, they must be requested on a separate service request.
Subsequent Service Requests
A subsequent service request is required when ordering Design Services (e.g. Integrated Services Digital Network (ISDN) and Off Premise Extensions (OPX). For Design Services request the Port In order must be completed prior to submitting any subsequent service requests.
Features (i.e. High Speed Internet (HSI) and hunting) can be ordered on New Connect service requests. However, if you do need to submit other subsequent service requests for Non-Design it is recommended to allow the Port In order to complete.
Old Local Service Provider (OLSP) Firm Order Confirmation (FOC) Requirements
Loop Reclamation
You may request loop reclamation on port in activity in the Remarks section on the LSR.
For the Qwest policy on Loop Reclamation, refer to Migrations and Conversions Overview.
Qwest will attempt to reclaim facilities whenever the Number Portability Indicator (NPI) field is populated with a C, D, or Z. You may provide additional information for the loop reclamation on port in activity in the Remarks section on the LSR.
When possible, Qwest will reclaim an Unbundled Local Loop associated with migration activity:
Qwest will reclaim the Unbundled Local Loop associated with a telephone number being Ported-In to Qwest, for like services. Qwest will send the service request, EU and NP forms for straight number portability and will use the following REQ TYP entries depending upon whether Qwest is reclaiming an Unbundled Local Loop.
REQ TYP "CB" = Qwest is not reclaiming an Unbundled Local Loop
REQ TYP "BB" = Qwest is reclaiming an Unbundled Local Loop
Qwest will advise the OLSP in the service request remark field whether or not the Unbundled Local Loop(s) is being reclaimed. If the Unbundled Local Loop(s) is being reclaimed, Qwest will also include the Exchange Company Circuit ID (ECCKT) in the service request remarks field or in the "ECCKT" field on the NP form preceding the associated "PORTED NBR" field.
Loss reports and Completion reports will identify the loop disconnect date for billing termination.
Qwest will not reclaim an Unbundled Local Loop associated with a telephone number being Ported-In to Qwest, if the end-user is changing address and Qwest is not aware of the loop at the old address or if the loop circuit ID cannot be identified. Qwest will identify this situation by entering the following remark on the service request , "End-user moving to new location, not reclaiming loop".
Qwest does NOT provide information on the re-use of facilities for the NLSP , Qwest provides the FOC stating that their request has been processed. Use of facilities to provision the service request to the end user customer is reserved by the NSP. The reclaiming of the facilities and the termination of billing is between the OLSP and the NSP.
Pre-Completion Call Process
Qwest offers a Port In pre-completion call process per your service request. This process provides advanced notice to you when the Qwest Technician is dispatched on the order.
Requests must include the following additional entries:
service request entries include:
Qwest will place the call notification upon dispatch to the premise.
Port In Ordering Activities Examples
The following examples describe different types of Port In ordering activities:
Process #1: Same Location End-User Not Moving
Process #2: Same Location End-User Not Moving, with addition of new Line(s) with non Ported Number(s)
***Note*** In the case where the Port is unable to happen on the requested due date, the entire request will be put into jeopardy status, including the new non ported telephone numbers on the request.
Process #3: New Location End-User Moving
Process #4: End-User Moving to New Location Served by Existing Provider
Qwest DSS must be established prior to porting in DID TNs. On new requests, Qwest will order the trunks with a DID test number belonging to Qwest. This will enable Qwest to test the trunks before the end-users TNs are ported in. The DSS DS1 and trunk orders must follow established service order intervals. In addition, the order porting in the DID TNs must be due at least one business day after the trunk order. Qwest commercial local exchange service orders are processed through IMA, Resale DSS orders are processed through a manual fax.
Process #6: New DSS with Port In DID TNs
Process #7: Port In DID TNs to Existing DSS when CSR does not Exist
Process #8: Port In DID TNs to Existing DSS when CSR Exists
Refer to the following Table Matrix Overview for the LNP Port In Process:
| Table Matrix Overview: LNP Port In Process to Qwest Resale /Qwest commercial local exchange service | |||
| Intervals: Simple Service, 1FR/1FB 1-50 lines ported, 6-Business Day minimum Complex Service, (PBX, Trunks, ISDN, Centrex) 1-25 lines or trunks ported, 6-Business Day minimum Simple Service, 1FR/1FB service, 51+ lines ported, 10-Business Day minimum Complex Service (PBX, Trunks, ISDN, Centrex) 26 = lines or trunks ported, 10-Business Day minimum Note: Minimum days apply, however, Due Dates are still based on Product specific guidelines, and availability in Appointment Scheduler and the FOC returned fromthe Old Local Service Provider (OLSP). |
|||
| Day | CLEC, New Local Service Provider (NLSP) | Qwest, Network Service Provider (NSP) | CLEC, Old Local Service Provider (OLSP) |
| 0 | (6 & 10 Business Day Process)
|
|
|
| 0-1 | (6 & 10 Business Day Process) |
|
|
| 1-3 | 6 & 10 Business Day Process
|
|
|
| 4 | (6 & 10 Business Day Process)
|
|
|
| 5 | (6 Business Day Process) |
|
|
| 6 | (6 Business Day Process)
|
|
|
| 6-9 | (10 Business Day Process)
|
|
|
| 9 | (10 Business Day Process)
|
|
|
| 10 | (10 Business Day Process)
|
|
|
Options for NLSP if Port In request is rejected for lack of concurrence from OLSP
Qwest will provide the following information on the rejected LSR:
The PON/LSR number we used when submitting the port request to the OLSP
The date when the request was submitted to the OLSP
The method in which the request was submitted (i.e. email, online, fax)
List of follow up dates and name(s) of the person(s) we attempted to contacted at the OLSP
If the LSR was rejected due to wrong end user information provided to Qwest, Qwest will indicate that the LSR data does not match OLSP CSR data.
The NSLP has the following options:
Re-submit the request with a different due date to re-try the process
Contact the OLSP and make reference to the PON/LSR which was sent on their behalf
Escalate to the OLSP using the same contact Qwest used or additional contacts they have obtained. If successful with different contact, re-submit request and identify contacts in the remarks section of the LSR to Qwest
Obtain a current CSR from the OLSP and re-submit the corrected LSR to Qwest
The following matrix is an overview for Port In Supplemental DD Changes or Cancels:
| Processing of Supplemental DD Changes or Cancels | ||
| NLSP will: | Qwest NSP will: | OLSP will: |
|
|
|
General provisioning and installation activities are described in the Provisioning and Installation Overview.
General maintenance and repair activities are described in the Maintenance and Repair Overview.
Billing section does not apply to the Port In process.
Local Qwest 101 "Doing Business With Qwest"
View additional Qwest course by clicking on Course Catalog.
Qwest contact information is located in Wholesale Customer Contacts.
1. What is the purpose of the DFDT?
DFDT is needed to submit the subscription to the NPAC for automated port completion as well as the automated necessary switch programming work.
2. Is the port in process the same if the NPA NXX was originally a Qwest TN not native to the Central Office the customer is moving to?
The Port in Process downloads are applicable to all ported TNs, whether they are native or non-native Qwest TNs or non-native CLEC TNs, as long as they are considered to be portable.
3. When a CLEC is porting a number into a Qwest WC, how does the CLEC determine if the TN can be ported into a particular switch in a multiple switch CO when the number is not the native LSO NPA/NXX?
Porting in to a Qwest switch is restricted by rate center boundaries. The pre-order address validation function in IMA will validate the end user's address and wire center. The CLEC should validate the TN NPA NXX with their own access to the LERG to determine if the rate center and wire center meet the rate center boundary guidelines for port in. Central offices may have multiple switches assigned to serve the rate center and wire center. Address validation in conjunction with NPA/NXX rate center validation is the only way to ensure portability. Designation of a particular switch is not required by the CLEC, only validation and rate center boundary rules are required to meet your port in request.
4. How does switch capacity effect porting into a Qwest switch?
If a switch has reached capacity, Qwest's process is to review the network for possible solutions. The provisioning process would port into whatever switch was available to serve the address, with no effect on the end-user's TN. Should an out of capacity situation occur in which there was no relief, the order would go held and you would be notified through the jeopardy notification process.
5. Is there ever a situation where a CLEC would have to request a Port In and a Port Within?
Qwest does not have a process for ordering a Port In and Port Within through one service request function. Port In indicates that the TN in question does not currently reside in a Qwest switch and must be ported in from another CLEC's network. A Port Within is when the TN is already in a Qwest WC either through traditional installation or through the port in process and is moved within the Qwest network to a different WC within the same Rate Center. However, it is also possible to Port In directly to a new address different from where the end-user's TN resided previously in the old CLEC's network within the same Rate Center.
6. When Porting In/Within DID numbers, can I request a change to the trunks, account number and/or STN on the same LSR and due the same day?
No. A change to the trunks, account number and/or STN would be considered a Design Service, which must be requested on a subsequent service request with standard intervals applying. See Subsequent Service Request section above.
Last Update: May 8, 2009
Qwest Local Services Platform™ (QLSP™) is a trademark of Qwest Communications International Inc.
