Primer for
Local Number Portability

 

Issue 2

Download MSWORD copy of Document here

TABLE OF CONTENTS

I. Purpose of Document 3

II. Updates to Document 3

III. Introduction to LNP 3

IV. Deploying LRN in Wireline Networks 9

V. Wireless Networks 19

VI. Operator Services 21

VII. Pay Phones 24

VII. E911 25

IX. Inter-Exchange Carriers (IXCs) 26

X. Testing 27

XI. Technical Reference Documentation 29

XII. Glossary of Terms 32

 

 

Midwest Region Primer for Local Number Portability (LNP)

PURPOSE OF DOCUMENT

The purpose of this document is to provide a primer for new Local Service Providers (LSPs) intending to provide Local Number Portability (LNP) in the Midwest Region states of Illinois, Indiana, Michigan, Ohio, and Wisconsin. This document takes only a technical perspective to assist new LSPs in LNP planning. Neither regulatory or business issues are included in the subject matter although links to current regulatory documentation may be included as references.

UPDATES TO DOCUMENT

This primer document will not be updated. The user/reader should be aware that information contained within reference documents is dynamic in nature. Updates to technical specifications and new issues related to specific operations will evolve as new reference information is identified. The user/reader of these reference materials assumes responsibility for accessing the latest version of the documents.

Links to all of the documents referenced in this primer and new documents which may be developed to support LNP in the Midwest Region can be found at the following web site:

http://www.ported.com

INTRODUCTION TO LNP

This section introduces LNP to new LSPs and answers commonly asked questions from the various state LNP Workshops.

What Is LNP?

LNP is a circuit-switched network capability which allows an end-user to change Service Provider (SP), location, and/or service type without having to change their telephone number. The three types of LNP are:

  1. Service Provider Portability - allows an end-user to change SP while retaining his/her telephone number
  2. Location (Geographic) Portability - allows an end-user to change from one geographic area to another (the current Location Routing Number(LRN) model does allow limited location portability within the rate boundaries) while retaining his/her telephone number.
  3. Service Portability - allows an end-user to change service (e.g., CENTREX to POTS, etc.) while retaining his/her telephone number with the same Service Provider.

The first area of number portability to be addressed in the industry is service provider portability. Therefore, the focus of this document is service provider portability only. Service provider portability is made technically feasible by the Location Routing Number (LRN) method (as described later in this document). LRN capability will be deployed in the five state Midwest Region.

What Is LRN?

LRN depends on Intelligent Network (IN) or Advanced Intelligent Network (AIN) capabilities which must be deployed in participating Wireline LSPs networks. LRN is a 10-digit number used to uniquely identify a switch that has ported numbers. The LRN for a particular switch must be a native NPA-NXX assigned to the SP for that switch. Essentially, LRN assigns a unique 10-digit telephone number to each switch in a defined geographic area. The LRN serves as a network address. Carriers routing telephone calls to end-users that have transferred their telephone numbers from one carrier to another perform a database query to obtain the LRN that corresponds to the dialed telephone number. The database query is performed for all calls where the NPA-NXX of the called number has been marked in the switch as portable. The carrier then would route the call to the new carrier based on the LRN.

The graphic on the following page describes a typical LRN call flow.

 

Typical LRN Call Flow

Originating Switch LNP Processing Direct to Recipient Switch

Note: For additional call flows see the Generic Switching and Signaling Requirements for Number Portability document

Scenario: End-user A (708-224-1111) dials End-user B (708-713-2222). Assume that End-user B (708-713-2222).ports their number to a different LSP. End-user A’s LSP can be connected via a direct connection to End-user B’s LSP if this is an intra-LATA call. See the steps below for a detailed description of LNP LRN.

  1.  
  2. The Originating Switch performs digit analysis on the dialed digits to determine how to route the call. The Originating Switch determines that End-user B is in a portable NPA-NXX (708-713) and that End-user B does not reside on the Originating Switch.
  3.  
  4. The Originating Switch sends an AIN (Info_Analyzed) or IN (InstructionStart) query based on the dialed digits to the LNP SCP.
  5.  
  6. The LNP-SCP sends an AIN (Analyze_Route) or IN (ControlConnect) response containing the LRN (312-979-XXXX) of the Recipient Switch.
  7.  
  8. The Originating Switch receives the LNP SCP response and analyzes the data. The LRN is translated in the LNP Routing Tables and an Integrated Services User Part (ISUP) route from the Originating Switch to the Recipient Switch is determined. The LRN is stored in the Called Party (CdPN) parameter and the dialed digits are stored in the Generic Address Parameter (GAP) of the ISUP Initial Address Message (IAM). The Forward Call Indicator (FCI) Translated Called Number Indicator is set to indicate a query has been performed.
  9.  
  10. The call is routed from the Originating Switch to the Recipient Switch based on the LRN.
  11.  
  12. The Recipient Switch receives and processes the contents of the IAM message. The switch determines that an LRN is received and that it is its own LRN. The switch replaces the CdPN parameter's contents with the dialed digits stored in the GAP parameter. The switch does digit analysis on the dialed digits and finds the end-user on the switch.
  13.  
  14. The Recipient Switch completes the call from End-user A to End-user B.

 

How Does LNP Affect a New SP?

The Federal Communications Commission’s (FCC’s) First Report and Order on Telephone Number Portability (C.C. Docket No. 95-116, Document No. 96-286) Appendix B at 52.3(b) adopted June 27, 1996 requires the following of all LSPs operating within the Top 100 Metropolitan Statistical Areas (MSAs):

In addition, the FCC in its First Memorandum Opinion and Order for Reconsideration (Document No. 97-74) Appendix D at 25 further modified the LNP Implementation schedule to reflect a change in the time required to implement the Phase I and Phase II schedules.

On the following page is a copy of the FCC’s mandated Implementation Schedule taken from the First Memorandum Opinion and Order on Reconsideration Appendix E adopted March 6, 1997.

 

 

APPENDIX E - IMPLEMENTATION SCHEDULE

 

 Phase I – 10/1/97-3/31/98 Phase II – 1/1/98-5/15/98 Phase III – 4/1/98-6/30/98
Chicago, IL 3 Detroit, MI 6

Cleveland, OH 20

Indianapolis, IN 34

Milwaukee, WI 35

Columbus, OH 38

Philadelphia, PA 4 Washington, DC 5

Baltimore, MD 18

Pittsburgh, PA 19

Newark, NJ 25

Norfolk, VA 32

Atlanta, GA 8 Miami, FL 24

Fort Lauderdale, FL 39

Orlando, FL 40

New Orleans, LA 41

Charlotte, NC 43

Greensboro, NC 48

Nashville, TN 51

    Las Vegas, NV 50
  Cincinnati, OH 30  
  Tampa, FL 23  
New York, NY 2 Boston, MA 9 Nassau, NY 13

Buffalo, NY 44

Los Angeles, CA 1 Riverside, CA 10

San Diego, CA 14

Orange Co, CA 15

Oakland, CA 21

San Francisco, CA 29

    Rochester, NY 49
Houston, TX 7 Dallas, TX 11

St. Louis, MO 16

Kansas City, KS 28

Fort Worth, TX 33

    Hartford, CT 46
Minneapolis, MN 12 Phoenix, AZ 17

Seattle, WA 22

Denver, CO 26

Portland, OR 27

Note: Numeric values associated with city names indicate the Census Bureau ranking of the MSA.

 

 

 Phase IV -- 7/1/98-9/30/98 Phase V -- 10/1/98-12/31/98
Grand Rapids, MI 56

Dayton, OH 61

Akron, OH 73

Gary, IN 80

Toledo, OH 81

Youngstown, OH 85

Ann Arbor, MI 95

Fort Wayne, IN 100

Bergen, NJ 42

Middlesex, NJ 52

Monmouth, NJ 54

Richmond, VA 63

Scranton, PA 78

Allentown, PA 82

Harrisburg, PA 83

Jersey City, NJ 88

Wilmington, DE 89

Memphis, TN 53

Louisville, KY 57

Jacksonville, FL 58

Raleigh, NC 59

West Palm Beach, FL 62

Greenville, SC 66

Birmingham, AL 67

Knoxville, KY 79

Baton Rouge, LA 87

Charleston, SC 92

Sarasota, FL 93

Mobile, AL 96

Columbia, SC 98

   
   
Honolulu, HI 65 Tulsa, OK 70
Providence, RI 47

Albany, NY 64

Syracuse, NY 69

Springfield, MA 86

San Jose, CA 31

Sacramento, CA 36

Fresno, CA 68

Ventura, CA 72

Bakersfield, CA 84

Stockton, CA 94

Vallejo, CA 99

   
San Antonio, TX 37

Oklahoma City, OK 55

Austin, TX 60

El Paso, TX 74

Little Rock, AR 90

Wichita, KS 97

  New Haven, CT 91
Salt Lake City, UT 45

Tucson, AZ 71

Omaha, NE 75

Albuquerque, NM 76

Tacoma, WA 77

 

 

DEPLOYING LRN IN THE WIRELINE NETWORK

The following questions are typically asked by new LSPs deploying LRN in a Wireline network.

What Components Are Required in an LNP Capable Network?

The components for an LNP capable network include:

The minimum requirement for an LSP to provide LNP capability in its network is an SSP. While all component functionality is required to provide LNP capability, a new LSP may arrange component functionality from third-party sources.

All Incumbent Service Providers (ISPs) which have been selected by an New Service Provider (NSP) have the obligation to support end-users porting numbers out of their networks per the FCC Implementation Schedule. (It is assumed that NSPs will be LNP capable). Additionally, LSPs may make a business decision to support end-users porting numbers in from other LSP’s networks.

 

What Functional Capability is Required for LRN Implementation?

A new LSP deciding to deploy LNP for (porting numbers in and out) using the LRN method has several options when providing LNP-capability in their network. These options support a range of LNP capability deployment. The table below indicates the most common options.

Options for LSPs Deploying LNP Capability

Option

New LSP Components

3rd-Party Components

  1. New LSP routes traffic for portable NXXs to an equipped LNP LSP with whom the new LSP has established an agreement
  • Non-LNP Equipped SSP
  • SSP
  • STP
  • SCP
  • NPAC Connectivity
  1. New LSP performs the LNP query from its own SSP
  • LNP Equipped SSP
  • SOA (see note below)
  • STP
  • SCP
  • LSMS (see note below)
  1. New LSP performs the LNP query from its own SSP and STP
  • SSP
  • STP
  • SOA (see note below)
  • SCP
  • LSMS (see note below)
  1. New LSP performs LNP query from its own SSP to its own SCP via another LSP’s network and STP
  • SSP
  • SCP
  • SOA (see note below)
  • STP
  • LSMS (see note below)
  1. New LSP provides all LNP functions from its own components
  • SSP
  • STP
  • SCP
  • NPAC Connectivity
  • None

Note: Although LSMS and SOA can be provisioned independently, when provisioned jointly, this capability is referred to as Number Portability Administration Center (NPAC) connectivity.

The graphics on the following pages depict the functionality for each of the five LNP deployment options described in the table above.

 

Option

New LSP Components

3rd-Party Components

  1. New LSP routes traffic for portable NXXs to an equipped LNP LSP with whom the new LSP has established an agreement.
  • Non-LNP Equipped SSP
  • SSP
  • STP
  • SCP
  • NPAC Connectivity

Note: Although LSMS and SOA can be provisioned independently, when provisioned jointly, this capability is referred to as Number Portability Administration Center (NPAC) connectivity.

 

 

 

Option

New LSP Components

3rd-Party Components

  1. New LSP performs the LNP query from its own SSP
  • LNP Equipped SSP
  • SOA (see note below)
  • STP
  • SCP
  • LSMS (see note below)

Note: Although LSMS and SOA can be provisioned independently, when provisioned jointly, this capability is referred to as Number Portability Administration Center (NPAC) connectivity.

 

Option

New LSP Components

3rd-Party Components

  1. New LSP performs the LNP query from its own SSP and STP
  • SSP
  • STP
  • SOA (see note below)
  • SCP
  • LSMS (see note below)

Note: Although LSMS and SOA can be provisioned independently, when provisioned jointly, this capability is referred to as Number Portability Administration Center (NPAC) connectivity

.

Option

New LSP Components

3rd-Party Components

  1. New LSP performs LNP query from its own SSP to its own SCP via another LSPs network and STP
  • SSP
  • SCP
  • SOA (see note below)
  • STP
  • LSMS (see note below)

Note: Although LSMS and SOA can be provisioned independently, when provisioned jointly, this capability is referred to as Number Portability Administration Center (NPAC) connectivity

 

 

 

Option

New LSP Components

3rd-Party Components

  1. New LSP provides all LNP functions from its own components
  • SSP
  • STP
  • SCP
  • NPAC Connectivity
  • None

Note: Although LSMS and SOA can be provisioned independently, when provisioned jointly, this capability is referred to as Number Portability Administration Center (NPAC) connectivity

 

 

What Major Tasks Are Required for LRN Implementation?

The following model highlights the major tasks required for LNP implementation and testing.

 

 

 

 

 

 

 

 

 

 

 

The following is a high level list of tasks that must be accomplished to cutover LNP. (The tasks are not chronologically positioned and are not intended to list all relevant sub-order tasks).

  1. Load switch software.
  2. Develop internal company operations procedures for Service Order Administration (SOA)/Number Portability Administration Center (NPAC) interface
  1. Register, test, and certify SOA/NPAC physical interface.
  2. Develop internal company operations procedures for LSMS/NPAC interface
  1. Register, test, and certify LSMS/NPAC physical interface.
  2. Develop internal company operations procedures for LEC-to-LEC interfaces
  1. Develop and test Billing processes for both IXC access and LEC-to-LEC calls
  2. Test Operator Services
  3. Test E911/911
  4. Test interactions with LIDB and other features (e.g., CLASS)
  5. Internetwork testing
  1. Cutover

 

General Issues Associated with Implementation

Each participant in the implementation process needs to establish an individual schedule within each company. Those specific schedules depend upon the following items:

  1. Based upon the Illinois and other states’ requirements for the LRN feature, the major switch vendors have indicated the following feature General Availability (GA) dates. Software availability for the LRN feature for major switching systems follows:
Ericsson AXE10

6/30/97

GTD-5

10/1/97

Lucent 5ESS

3/28/97

Lucent 4ESS

5/1/97

Lucent 1AESS

Lucent OSPS

3/21/97

5/31/97

Nortel DMS100

6/30/97

Nortel DMS10

6/30/97

Nortel DMS100/200

6/30/97

Nortel TOPS

9/30/97

Siemens EWSD

3/31/97

Stromberg-DCO

7/1/97

  1. Development of LSMS/SCP implementation strategies. (Individual LECs may elect to own and maintain individual elements, or contract for that specific functionality.)

  1. The effort needed for all SPs to modify existing internal service order provisioning systems to support the 10-digit trigger as a "flow-through" provisioning process.
  2. Development and implementation of the various interfaces required could impact the deployment dates. These interfaces are as follows (see accompanying diagram):
  1. NPAC-to-SOA
  2. NPAC-to-LSMS
  3. LEC-to-LEC
  4. Other interfaces (not shown) include:
  5. LEC-to-911 Database
  6. LEC-to-Operator Services

 

LNP Operations

The Midwest Region Operations Sub-committee has developed a set of sequential functions and decision points that will allow for the provisioning and maintenance of end-users within an LNP environment. The interworking of these functions and decisions define processes that will allow two or more LECs to interwork on an operational level.

The Operations processes are represented in flow charts for these functional areas:

  1. Provisioning Processes
  1. Conflict Flow for the Service Creation provisioning Process
  2. Cancellation Flow for the Provisioning Process
  3. Cancellation Conflict Flow for the Provisioning Process
  4. Disconnect Process for Ported Telephone Numbers
  5. Audit Process
  6. Code Opening Processes
  7. Repair Process

Operational flow charts are based upon the work done in NANC, Illinois Operations Sub-committee, and other State LNP Workshops. In addition, the Operations Sub-committee has developed a narrative description to identify the relationships between the various process tasks and decisions, that when combined with the flow charts, will constitute the Inter-Company Provisioning and Repair Procedures. For Operations Flows and Procedures see:

http://www.ported.com

 

 

WIRELESS NETWORKS

The LNP capabilities which need to be supported by wireless networks depend on the MSA served and the date. For wireless SPs, the LNP capabilities that can (or must) be supported depend in large part on whether the MSA was designated by the FCC as one of the initial Top 100 MSAs. The schedule below, established by the FCC, defines different capabilities which must be supported by wireless SPs by specific dates.

FCC Mandated Wireless Schedule

Time Frame

TOP 100 MSA

OTHER MSA

Prior to 12/31/98 LNP routing optional

Not applicable

1/1/99 through 6/30/99 Cellular, broadband PCS, and covered SMR providers are required to have the capability to query the number portability databases nationwide, or arrange with other carriers to perform the queries, by December 31, 1998, in order to route calls from wireless customers to customers who have ported their numbers.

---------

Following 6/30/99 Service provider portability including the ability to support roaming. DN portability between SPs required on request.

Even if a wireless network is not supporting LNP, the wireless SP's methods and procedures should be updated to support troubleshooting for calls placed to ported wireline numbers.

The Cellular Telephone Industry Association (CTIA) has issued a "Report on Wireless Number Portability" to address technical methods to support number portability in wireless networks.

Top 100 MSAs, prior to 12/31/98

Once wireline networks have implemented LNP, wireless SPs serving the same MSA need to address wireless end-users making calls to portable wireline numbers. Wireless SPs are not required to support LNP routing during this period. Calls for wireless end-users to a ported wireline number will complete successfully through the donor network. However, wireless SPs should be prepared to support LNP troubleshooting (for calls to ported numbers).

 

Top 100 MSAs, as of 12/31/98

Following 12/31/98, Cellular, broadband PCS, and covered SMR providers are required to have the capability to query the number portability databases nationwide, or arrange with other carriers to perform the queries, by December 31,1998, in order to route calls from wireless customers to customers who have ported their numbers.Top 100 MSAs, as of 6/30/99

By June 30, 1999, all cellular, broadband PCS, and covered SMR

providers must povide a long-term database method for number portability

in switches for which another carrier has made a specific request (by

Sept. 30, 1998) for provision of number portability.

Non-Top 100 MSAs, prior to 1/1/99

A wireless SP may leave their networks unchanged prior to 12/31/98, if the SP serves an MSA which is not scheduled to support LNP.

Non-Top 100 MSAs, after 1/1/99

Wireline networks in a Non-Top 100 MSA will convert to LNP upon request. The 12/31/98 date for wireless applies.

Non-Top 100 MSAs, after 6/30/99

Wireless SPs must provide number portability to requesting SPs within 6 months after receiving a request or within six months after June 30, 1999,

 

 

OPERATOR SERVICES

Operator Service Providers (OSPs) may serve networks providing LNP capability, or may have to inter-work with networks providing LNP capability. OSPs should be aware that LNP may have various impacts on their operations.

LNP affects the way numbers are translated and outpulsed and it creates a requirement for additional information for numbers that are used in billing records. As a result, LNP particularly affects Alternate Billing Services (ABS) and Busy Line Verification (BLV). ABS calls (e.g. Collect, Person-to-Person, Third-Party Billed, Calling Card) are impacted because verifications are required on the alternative billing information and the additional information required for billing (e.g., service provider identity). BLV calls are impacted because of special routing requirements.

There are no required changes for signaling to, or from, Operator Services Systems supporting LNP. Calls which can be identified as requiring Operator Services Systems processing will not receive LNP processing prior to routing to the Operator Services Systems. An OSP may decide it is beneficial to upgrade its Operator Services Systems to support LNP capable SS7 signaling. LNP capable SS7 signaling allows the Operator Services Systems to receive and send portability information for calls it processes.

Timing for ABS queries may need to be modified. Most systems have "default timer" set at two seconds. Network responses for ABS queries are expected within two seconds even when affected by LNP, but longer timer values (e.g., three seconds) may be necessary to reduce "timeout" conditions.

Software for the SS7 addressing of ABS queries may be modified to 10-digit Global Title Address (GTA). Current systems place 6-digit values in the Signaling Control Connection Part (GTA) field, which is used for routing ABS queries through the SS7 network. In order to simplify ABS query routing when encountering an LNP trigger, industry signaling forums are considering recommendations to include all ten digits of the ABS directory number (DN) in the GTA field.

 

Busy Line Verification

 

PAY PHONES

No obvious impacts as a result of LNP (SP portability) have been identified for pay phone SPs. Pay phone SPs may have obligations or needs as a result of LNP if they are also providing operator services.

 

E911

An ad-hoc 911 team has been formed as a part of the Operations Sub-committee. New LSPs must be aware of 911 requirements prior to participation in LNP. Significant items of analysis are:

For the NENA recommended standards document and E911/911 Test Service Plan see:

http://www.ported.com

 

INTER-EXCHANGE CARRIERS (IXCs)

Inter-exchange carriers are not obligated by the FCC order to perform LNP processing. IXCs may elect to perform LNP processing in order to perform efficient routing and to avoid charges which might be incurred when delivering traffic to donor networks.

 

TESTING

FCC Field Test Background

The FCC directed the carrier members of the Illinois Local Number Portability Workshop to conduct a field test of LNP. The Chicago area was selected for the field test because the record indicates that the Illinois LNP Workshop was responsible for drafting requirements for switching software currently being developed by switch manufacturers. Because of the significant work which has been done on behalf of the Illinois LNP Workshop, the FCC determined the Chicago area was the best site within which to conduct a field test.

The Field Test encompasses both network capability; billing and ordering systems; as well as maintenance arrangements. It was further directed in the FCC’s First Report and Order on Telephone Number Portability at 79, that the carriers participating in the test jointly file with the Common Carrier Bureau (CCB) a report of their findings within 30 days following completion of the field test. The FCC also wrote:

As stated above, participation in the Illinois FCC Field Test will require LSPs to connect to the Lockheed-Martin administered Midwest NPAC. Participants are required to obtain new switch loads from their switch vendors that will allow their switch to function using the LRN LNP method. Participants are be required to develop their own LSMS and SOA system.

During the Field Test, in order to gain a comprehensive exposure to LRN functionality, LSPs are required to be both the recipient and the donor of ported telephone numbers. At a minimum, new LSPs are required to use their End Office (EO) and Tandem Switches, STPs, and associated Operations Support Systems (OSSs)/management systems, LSMSs and SOAs to support provisioning/call processing during the Field Test.

 

Ongoing Test Requirements for New LNP LSPs

Subsequent to the Field Test, and in order to meet the requirements listed in the previous paragraph, new LSPs are expected to do the following:

For additional information please refer to the Illinois FCC Field Test Plan at:

http://www.ported.com

 

TECHNICAL REFERENCE DOCUMENTATION DESCRIPTIONS

The following reference document descriptions have been provided for new LSPs to determine impact on their networks when upgrading to LNP. Existing documents are subject to change. Additionally, new documents may be added to support LNP in the Midwest Region. Interested LNP parties should check the http://www.ported.com for new documents and links as they become available.

911/E911 NENA Recommended Standards for SP LNP

The purpose of this document is to publish NENA recommended standards for all LSPs involved in providing dial tone to end-users and involved in SP LNP. This document may be obtained from:

http://www.ported.com

FCC Field Test Plan

Testing for number portability has several elements included in the evaluation criteria. The tests compiled in the FCC Field Test Plan have been developed by a team consisting of participant companies to provide those participating in the transition to an LRN based LNP environment adequate assurance that the porting endeavor using LRN and support processes is successful.

The FCC Field Test Plan should be considered a menu of tests. Each SP will select from this menu of tests those which their network arrangement will allow them to perform. Thus making this FCC Field Test Plan a universal collection of tests that SPs can use as a basis to develop their testing. This document may be obtained from:

http://www. ported.com

 

FCC Field Test Report

At the conclusion of the Illinois FCC Field Test a report will be compiled and submitted to the FCC. The Field Test Report is due to the FCC on December 17, 1997. Upon completion, this document may be obtained from:

http://www. ported.com

Generic Requirements for SCP Application and GTT Function for Number Portability Document

This document defines the requirements for an application residing on an SCP that performs LNP query processing (i.e., receives an LNP query from a switch and performs an LRN lookup in a database). It also defines the requirements for an LNP 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) in LNP networks. For links to this document see:

http://www.ported.com

Generic Operator Services Switching Requirements for Number Portability

This document defines the Operator Services switch requirements for the LRN method. It includes all switching-based LRN functionality, as well as:

For links to this document see:

http://www.ported.com

Generic Switching and Signaling Requirements for Number Portability

This document defines the switch requirements for the Number Portability - Location Routing Number (LRN) method. It includes the following switching requirements:

For links to this document see:

http://www.ported.com

Interconnection Logistics Plan

The necessary step to be conducted by the NPAC User to design, order, establish, and test connectivity are outlined in this document. It is required that the NPAC User has entered into a User Agreement prior to initiating the steps outlined within this procedure. For further information contact the Midwest NPAC on:

(800) NPAC-HELP.

 

Inter-operable Interface Specifications (IIS)

The NPAC/SMS Inter-operable Interface Specification contains the information model for the NPAC/SMS mechanized interfaces. Both SOA and LSMS interfaces to the NPAC/SMS are describes in this document. This document can be obtained from:

http://www.npac.com

Inter-SP LNP Operations Document

The following document provides inter-company process flows and verbiage to support the necessary inter-company Operational interactions which are necessary to support LNP. For Inter-SP LNP Operations Flows see:

http://www.ported.com

Midwest Region LLC Operating Agreement

The Midwest Region Limited Liability Corporation (LLC) is a corporation that determines enhancements to the NPAC/SMS for the Midwest Region.

Although NPAC connectivity is a requirement for deployment of LNP, LSPs are not required to join the LLC. For links to this document see:

http://www.ported.com

Midwest NPAC Methods and Procedures Document

This document describes the NPAC Support provided to SPs and methods and procedures for various processes (e.g., trouble reporting, NPA Splits) supporting LNP. For further information contact the Midwest NPAC on:

(800) NPAC-HELP

NPAC Functional Requirement Specifications (FRS)

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 Local Number Portability. For links to this document see:

http://www.ported.com

 

 

Glossary of Terms

ABS Alternate Billing Services
AIN Advanced Intelligent Network

Evolving, service-independent network architecture that provides important new capabilities for rapid creation of customized telecommunications services. AIN offers one way for a network element to query a central database to obtain local number portability routing information.

AIN 0.1 An AIN architecture that is a first step in realizing AIN Release 1.
AIN

Release 0

An AIN release defined by individual Bellcore Client Companies (BCCs) for initial deployment.
AIN

Release 1

An AIN release, intended for deployment in the 1990’s with a common functional architecture that support the delivery of circuit-switched voice and circuit-switched data services to network end-users.
ALI Automatic Location Identification

Name, address, and appropriate dispatching agencies of a 911 caller.

AMA Automatic Message Accounting

The automatic collection, recording, and processing of information relating to calls for billing purposes. (See CAMA also)

ANI Automatic Number Identification

ANI provides the billing number of the line or trunk that originated a call.

AT Access Tandem

A LEC switching system that provides a traffic concentration and distribution function for inter-LATA traffic originating/termination within a LATA. The access tandem provides the IC with access to more than one end office within the LATA. More than one access tandem may be required to provide access to all end offices within a LATA.

BLV Busy Line Verification
CAMA Centralized Automatic Message Accounting

An arrangement that provides for the recording of detailed billing information at a centralized location other than and end office, usually a tandem. CAMA equipment also may be associated with operator systems, etc.

CCB Common Carrier Bureau
CCS7 Common Channel Signaling # 7

A signaling method in which a single channel conveys, by means of labeled message, signaling information relating to a multiplicity of circuits or calls and other information, such as that used for network management.

CLEC Competitive Local Exchange Carrier

Considered to be a new entrant into a market where there is already an incumbent LEC providing local phone service.

CPN Calling Party Number

The acronym that identifies the originating telephone number field in an SS7 message.

CdPN Called Party Number

The acronym that identifies the terminating telephone number field in an SS7 message.

CENTREX Central Office Exchange

A telephone service offered by LSPs that provides the end-user with advanced features and services from the LSPs EO

CIC Carrier Identification Code

A 3-digit number that uniquely identifies each IC. A carrier identification code applies to an IC throughout the North American Number Plan area. Multiple carrier identification codes per carrier are not precluded.

CLASS Custom Local Area Signaling Services

Premium local service features, such as call forwarding or automatic callback.

CMRS Commercial Mobile Radio Service
CO Central office

An environmentally controlled space in which a telecommunications network switching system and other associated operating systems are installed.

CTIA Cellular Telephone Industry Association
DIPS Refers to database dips

Query by a local switching office or toll switching office to a remote database.

DN Directory Number

An end-user’s telephone number, also known as a TN. In its most restrictive definition, an end-user number which is listed in a directory or with directory assistance.

Donor Switch Switch/Office/Exchange

Refers to the local switch from which an end-user was served, prior to changing SPs.

DPC Destination Point Code

The part of a routing label that identifies where the CCS/SS7 signaling message should be sent.

EO End Office

A switching system used to provide local service for a local telephone company; also known as a central office. End offices are typically equipped with both line and trunk terminations.

FCI Forward Call Indicator

The acronym that identifies the field in an SS7 message which is set to indicate to participating networks involved in the processing of an LNP call when an LNP query has been performed.

FCC Federal Communications Commission

Congressional government entity endowed with the responsibility to direct the U.S. national telecommunications regulatory environment.

FOC Firm Order Confirmation

Verification/acknowledgment from one SP to another of receipt of a valid Service Request (SR)

FRS Functional Requirements Specifications for the NPAC/SMS
GAP Generic Address Parameter
GTT Global Title Translation
IAM Initial Address Message

A CCS/SS7 signaling message that contains the address and routing information required to establish a point-to-point telephone connection.

IC Inter-exchange carrier (see IXC)
IIS Inter-Operable Interface Specifications for the NPAC/SMS
ILEC Incumbent Local Exchange Carrier

Typically, the RBOC or independent who services all local end-users (prior to a market opening up to local competition)

IN Intelligent Network

Hardware and software platform used to provide enhanced voice, video and data services. IN offers one way for a network element to query a central database to obtain local number portability routing information.

ISP Incumbent Service Provider

The exchange carrier that has the NPA assign as a default. This would usually be the donor switch for the ported number.

ISUP Integrated Services User Part

The part of a CCS/SS7 signaling node that is used to develop and format signaling messages.

IXC Inter-Exchange Carrier

A carrier that provides connections between LATAs, between serving areas, and between LATAs and serving areas where the calling or called end-user is located in the United States.

JIP Jurisdiction Information Parameter
LEC Local Exchange Carrier

The company—most often a local Bell Operating Company—that provides local telephone service. LECs also include independent local telephone companies.

LERG Local Exchange Routing Guide

Bellcore administered Network Routing and V&H Coordinate information for U.S. Telecommunications Industry

LLC Limited Liability Corporation

The jointly-owned legal entity which is responsible for oversight and administration of the Midwest NPAC. While all certified LSPs can use the NPAC, only official members have a vote in its business decisions.

LM-IMS Lockheed-Martin IMS

The selected Midwest Region NPAC developer and neutral third-party administrator for the LNP database.

LNP Local Number Portability

The end-user's ability to retain his/her telephone number when switching to a competing local telephone SP.

LRN Location Routing Number

A 10-digit number used to uniquely identify a switch that has ported numbers. LRN utilizes AIN triggers, SS7 signaling, and unique 10-digit code for switch identification.

LSMS Local Service Management System

The LSP owned network database which holds down-loaded ported number information.

LSP Local Service Provider

A company that provides basic local telephone service.

MSA Metropolitan Statistical Area
N-1 N minus 1

The next to last network involved in a particular call. In the case of an inter-LATA call, for example, the next to last network is the inter-exchange carrier network.

NANC North American Numbering Council

FCC -mandated task force assigned to oversee NPAC and NANP administration for the U.S. telecommunications industry.

NANP North American Numbering Plan

A plan for the allocation of unique 10 digit address numbers. The numbers consist of a 3 digit area (numbering plan area) code, a 3 digit office code, and a 4 digit line number. The plan also extends to format variations (e.g., 3 digit and 7 digit address), prefixes (e.g., 1, 0, 01 and 011), and special code applications (e.g., Service Access Codes).

NENA National Emergency Number Association

National industry forum that includes police, fire, community administrators, and telecommunications vendors/ SPs with an involvement in emergency/911 services.

Non-Portable Number Non-portable numbers are those that have not been designated as ported exchanges or portable capabilities.
NPA Numbering Plan Area

A defined geographic area identified by a unique three digit code used in the North American Numbering Plan Area.

NPAC Number Portability Administration Center

A neutral third-party administrator of the regional LNP database.

NSP New Service Provider

Subscribers selection of exchange carrier that will be providing dial tone. This will usually be the exchange carrier that is not the default SP for the NPA. This would be the recipient switch for the porting of a number when the end-user is being ported. When the end-user is changing from ported to non-ported the NSP would be the donor switch.

NXX End Office Code

A three digit code used to identify a central office exchange. However, in a portable environment the last 4 digits or the 7-digit telephone number may not always reside in the central office exchange to which the NXX was natively assigned.

OSP Operator Service Provider

A SP of operator services. Typically associated with directory or alternate billing services.

PSAP Public Safety Answering Point

Police and/or fire agency that performs dispatching for emergency services.

Portable Number Portable numbers are those numbers within an exchange that have portable capabilities and are assigned to a designated portable exchange. These are the numbers that are assigned to the designated default switch and have not been ported to another LSP. These numbers are commonly identified as working on the "Donor" switch.

Portable numbers are all numbers in an NXX where portability is allowed. Numbers will be declared portable on an NXX basis.

Ported Number Ported numbers are those that have been assigned to other LSPs providing recipient switch access for Portable exchanges. This is commonly termed as the numbers assigned to the "Recipient" switches. The "Recipient" switch is not the default switch in the SCP.

Ported numbers are the subset of portable numbers that have actually been moved from the LERG based switch (donor) to another switch (recipient).

POTS Plain Old Telephone Service

Basic residence or business telephone service which provides users with simple telephone features or service.

PUC/PSC Public Utility (or Service) Commission

State regulatory body that exists in virtually every state and regulates intrastate services of utilities, including telephone companies providing intrastate services. Also called a Public Service Commission (PSC) in many states.

Query(ies) Refers to database queries/dips

Query by a local switching office or toll switching office to a remote database.

Recipient Switch Switch/Office/Exchange

Refers to local end office switch to which an end-user is served, after changing SPs.

SCP Service Control Point

Service control point; Transaction processor-based system that provides network interface to database services.

SMS Service Management System

Computer facility permitting access to records contained in the number portability database.

SOA Service Order Administration

Interface to the NPAC/SMS for provisioning ported end-user data.

SP Service Provider

A company that provides telephone service.

SSP Service Switching Point

Service switch point; a switching office that has the SSP features, enabling interactions with SCPs action with SCPs.

STP Signal Transfer Point

A signaling point with the function of transferring signaling messages from one signaling link to another and considered exclusively from the viewpoint of the transfer. A packet switch that transmits messages between switches and other network components. Also transmits messages between switches in the process of normal call set-up and routing.

Tandem Tandem Switch

An LSP switch that exclusively supports trunk terminations. The tandem allows an LSP to provide trunk connectivity between EOs within its own network, as well as providing trunk connectivity to other LSPs, OSPs, and IXCs. See access tandem.

TCAP Transaction Capabilities Application Part

TCAP is the application layer of the Transaction Capabilities protocol that is used for messages between end offices and remote databases.