AT&T Clec Online

Local Number Portability (LNP) Database Access is a capability that utilizes Advanced Intelligent Network (AIN) or Intelligent Network (IN) technology to query a database to secure network routing instructions before completion of a call. The database contains information about end-users that have ported their service from the donor switch. At a minimum, the database contains the Location Routing Number (LRN) which identifies the Local Service Provider’s (LSP) switch serving each ported end user. The LRN is used to direct the call to the correct switch for completion to the end user.

N-1 wireline Competitive Local Exchange Carriers (CLECs) which have with their own facilities, have SS7 connectivity, and deployed LNP switching technology may arrange with Ameritech to query our database using their own Service Switching Points (SSPs) via the Common Channel Signaling System #7 (SS7) network.

As new carriers enter the local market and participate as CLECs, they may consider the option of consolidating their existing database services into Ameritech’s database services or simply using Ameritech’s database services. This arrangement would enable them to avoid the expense of building or maintaining their own databases.

1.0 Service Description

Terminating calls from N-1 Carriers to numbers in Ameritech’s network with NXX codes that have been designated as number portable may require a query to the LNP database to obtain the terminating telephone number’s Location Routing Number (LRN).

LNP Database Access:

N-1 Carriers terminating calls to the numbers in Ameritech’s network with NXX codes that have been designated as number portable may be responsible for making a query to a LNP database containing Location Routing Number (LRN) information necessary to route the call.

LNP Database Access allows carriers to query Ameritech’s database via Ameritech’s common channel signaling network. This service is for carriers who have their own facilities, have SS7 access to the Ameritech network, and want to perform their N-1 responsibility. Under this service, customers arrange in advance to query the database using their own Service Switching Points (SSPs), via the common channel signaling network. The carrier’s SS7 network or a hub provider’s network may be used to transport the query from the carrier’s SSP to the Ameritech STP and then to the Ameritech SCP. When the necessary routing information in the form of a LRN has been returned from the database to the switch that launched the query, call processing is resumed and the call is routed to the correct network switching element for completion to the called party. Information residing in Ameritech’s LNP database is protected from unauthorized access and may not be stored in a carrier’s database or elsewhere for any reason.

Carrier using Ameritech’s LNP Database must establish the processes needed to provision the LNP LRN triggers in their facilities, which will cause the queries to take place for routing calls to ported telephone numbers.

The following diagram identifies the network elements in the call flow for the LNP Database Access. The numbers on the diagram correspond to the description of the call flow as noted in the diagram.

LNP DATABASE ACCESS

IMAGE BEING REVISED

NOTE: Redundant SS7 components and links not shown

Basic LNP Data Base Query Call Sequence

The Carrier’s customer dials a number that has an NXX code that has been designated as number portable and the SSP office suspends the call and launches a query to the SCP. The query contains the Automatic Number Identification (ANI) type information and the called digits. The query transport path to the SCP will depend on the type of SSP interconnection.

The SCP’s service logic performs the necessary analysis of the ten digit called number, determines the appropriate routing instructions, and returns a response to the originating SSP. If the number has been ported, the Location Routing Number of the recipient switch that now serves the number is returned as well as the called number. The SCP’s contents are updated with downloads from the Local Service Management System (LSMS).

The Carrier uses the routing information to resume call progress and then completes the call over the appropriate facility, such as an Ameritech Tandem Switch.

1.1 Service Requirements

Interconnection to the Ameritech SS7 network is a prerequisite for this service. The information for this requirement is provided in the ‘Unbundled Access to the SS7 Network Product Guide’. Interconnection may be from the carrier’s Service Switching Points (SSP), STP, or via a hub provider’s SS7 network. (A hub provider is a third party providing SS7 transport between the telecommunication carrier and Ameritech.)

The carrier must have deployed LNP switching capability in their network. This is required before the carrier can launch LNP queries and use the LRN information returned from the database to route calls to portable numbers.

The carrier is responsible for the provisioning of the translations in the originating switches for the LNP NPA-NXX triggers that initiate the launch of the AIN or IN TCAP LNP query.

Called Party Address for queries to the Ameritech LNP Database shall include the Alias Destination Point Code provided by Ameritech, and subsystem number 0 with a translation type of 11 (AIN) or 201 (IN). Calling Party Address for the queries shall include the Point Code of the system sending the query, and it is suggested that a subsystem number of 248 is used. Such subsystem number and translation type values are necessary for Ameritech to properly process queries to its LNP Database.

1.2 Rate Structure

There are three major rate elements for the LNP Database Access. They are each described and then tabled below.

Ordering Charge - An administrative charge applies for each LNP Database Access service order .

Originating Point Code Charge - A charge is also applied to each Originating Point Code (OPC) established, as well as each OPC added or changed subsequent to the establishment of STP Access. (An OPC is considered an SS7 address that is assigned to each network element involved with the signaling process. These OPCs are assigned through Telecordia and are part of an SS7 interconnection.)

Global Title Address Translations Charge - A charge is also applied for Global Title Address (GTA) Translations each service or application that utilizes Transaction Capabilities Application Part (TCAP) messages. A GTA Translation charge also applies for each service added or changed subsequent to the initial establishment of STP Access. (GTA Translations are software instructions in the Signal Transfer Point (STP) that identify the signaling message destination.)

LNP Database Charge - A recurring charge will apply for each LNP Database query performed.

The following table defines the rate elements, the frequency of the charge and the USOCs where applicable.

Rate Element	Frequency	USOC
Ordering Charge per order	Non-Recurring	ORCMX
Originating Point Code (OPC) Charge per OPC, per service, added or changed, per STP Pair	Non-Recurring	CF3S3
Global Title Address (GTA) Translation Charge per OPC, per service, added or changed, per STP Pair	Non-Recurring	CF3S5
LNP Database Charge per query	Recurring Rates	-NA-
Note: SS7 TCAP Message Switching and Message Transport Charges are included in the LNP Database Charge.

1.3 Forecasting

LNP Database Access requires the carrier to submit in advance of placing the order for the service a forecast of the volume of LNP query transactions needed to the account manager. The forecast will include the following items:

The LATA and/or MSA in which the queries will be initiated

For each LATA and/or MSA, a Monthly Volume of LNP queries

For each LATA and/or MSA, the Busy Hour Volume of LNP queries

If the actual volumes of LNP queries exceed 120% of the forecasted volumes, the carrier is required to submit a new forecast to the account manager. A blank copy of the LNP Database Access Forecast can be found in the Forms and Exhibits section.

2.0 Pre-Ordering Requirements

Interconnection to the Ameritech SS7 network is a prerequisite. See the SS7 for complete details.

2.1 Customer Service Record (CSR)

An example of the information content and format of the Customer Service Record (CSR) for Ameritech LNP Database Access is shown in Attachment # 1.

2.2 Service Address Guide (SAG) Validation

Service Address Guide Validation is not applicable to the Ameritech LNP Database Access.

2.3 Central Office Feature Availability

Central Office Feature Availability is not applicable to the Ameritech LNP Database Access.

2.4 Telephone Number Selection

Telephone Number Selection is not applicable to the Ameritech LNP Database Access.

2.5 Due Date Negotiation/Intervals

All orders submitted to a Local Service Center prior to the fifth of the month will be completed by the first of the following month. The minimum ordering interval for access to Ameritech’s LNP Database is 15 business days from the date an error-free ASR is received. Firm Order Confirmation (FOC) of the due date for service completion will be provided to the CLEC within three business days. See section 3.3 for Firm Order Confirmation information.

3.0 Ordering Requirements

3.1 Ordering Method

Ameritech accepts orders for LNP Database Access from telecommunication carriers. See Forms section for ordering instructions.

The Local Service Center serves as a single point of contact for ordering and billing issues related to Local Number Portability (LNP) Database Access.

3.2 Order Types

The Ameritech LNP Database Access is ordered on the ASR Administrative and Trunking forms.

3.2.1 New Order

See SS7 for instructions for new STP Access. SS7 Interconnection is a prerequisite for ordering LNP Database Access service. LNP Database Access service should not be included with new SS7 service because special integration testing is required. See Section 3.2.2 Change Order for adding or removing LNP Database Access service.

3.2.2 Change Order

Follow the instructions for the ASR Administrative and Trunking forms found in the Forms section to add LNP Database Access service to SS7 links. CLECs interested in adding or removing Ameritech LNP Database Access service must supply the information at least fifteen business days in advance of the required due date.

3.2.3 Disconnect Order

See SS7 for instructions for disconnecting STP Access. See Section 3.2.2 Change Order for adding or removing LNP Database Access service.

3.3 Firm Order Confirmation (FOC)

After the CLEC has sent the completed ordering forms to the Lcoal Service Center, the Service Center will send a Firm Order Confirmation (FOC) back to the CLEC to confirm receipt of the order and indicate the expected due date. The FOC will be returned to the CLEC within three business days after receiving the completed initial order.

3.4 Design Layout Report (DLR)

The Design Layout Report (DLR) is not applicable to the Ameritech LNP Database Access.

4.0 Billing Procedures

4.1 Bill Type

The Carrier Access Billing System (CABS) is used to render bill invoices to any CLEC who purchases Ameritech LNP Database Access service. The bill will be generated once every month out of the CABS.

4.2 Bill Format

The bill format displays are consistent with the CABS Billing Output Specifications (BOS) for Switched Access. Ameritech may initially bill the customer in a manual format, until such time as the mechanized billing system for LNP Database Access queries is implemented.

4.3 Bill Inquires

The Local Service Center serves as a single point of contact for ordering and billing issues related to Local Number Portability (LNP) Database Access. See: Escalation Matrix.

5.0 Provisioning and Maintenance/Repair Procedures

The LOC is a single point of contact for all installation, status, and maintenance/repair reporting for LNP Database Access service.

To assist with the Provisioning and Maintenance/Repair Procedures, the following points of information are provided for clarification.

SS7 hub providers transporting queries into the Ameritech Network should coordinate all link troubles on behalf of their customer base.

Carriers reporting suspected AOS (Area of Service) provisioning problems should provide the following information.

Company Name

SSP Switch Location with LATA and NPA(s) served

Originating Point Code of SSP

Specific problems being encountered

SS7 Network interconnection arrangement

New: 7-5-01

5.1 Incorrect Caller ID Display

When an End User's telephone number (TN) displays incorrectly on Caller ID, CLECs should call the Local Operations Center (LOC) to report the problem at 800-730-8815. The LOC will first verify that the order is complete. If the order is held or incomplete, the LOC will refer the CLEC to the LSC.

If the order is complete, the LOC will verify that the TN is programmed correctly in the Caller ID Database. If Caller ID is programmed correctly in the Caller ID database, the LOC will open a trouble ticket and provide the CLEC with a trouble ticket number. After the trouble ticket has been opened, the CLEC should advise the EU to wait 48 hours and then make a test call. If, after the 48 hours have passed, the problem is still not corrected, the CLEC should call the LOC.

6.0 Attachments

6.1 Attachment #1 - Customer Service Record (CSR) Example

CUSTOMER SERVICE RECORD

(CSR) 312 G40-XXXX XXX

06/04/1998 PAGE 1

PCL PSN PROPRIETARY

ABC SERVICE CORP.

CLS SVC BILL DAY ACCT DATE FOR TELCO USE

BILLING INQUIRIES CALL XST 04TH 06-02-1998 ICSC OFC

(000) DMD-0000 BAI I, MM

---ACCOUNT IDENTIFICATION---

FOR TELCO USE ACNA ZZI LAT 358 TAR 0000 TAX A TYP SVC K

CCNA ZZI TYS IC

ZBU II, TIS

BILLED TO: ABC SERVICE CORP.

ATTN JOHN DOE

ONE N. MAIN

P O BOX XXX

ANYWHERE, IL 60606

CUSTOMER SERVICE ADDRESS: ONE N. MAIN, CHGO, IL

1 -ZZZZZZZZZZZ

---SERVICE AND FEATURES---

SVC ACTVTY

ESTBL :QTY :CODE: DESCRIPTION :TAX: AMOUNT :DATE

020398 ASG 1/OCL CHCGILWBDS0/PIU 100/SBE 021498

0002/LTYP A/OTID 720395D

720301T

MPB I, MM, X

020398 TSC LB012345/LTL ELGNILXDS0/APZ 060298*

ELGNIL0801W 77 ELGNILXDS0/NC

YNS-/NCI 04DS9.15/SLKC 00

/STPI 250-003-053/TGN 0000

/TRN 1000/TTC TY/TTD

MI-5SNAKD ZZI

020398 1 TAK9X 021798*

020398 1 CM6 021798*

INTERST/INTERLT 100%

X 1 X 14.2700 14.27

---SERVICE AND FEATURES---

SVC ACTVTY

ESTBL :QTY :CODE: DESCRIPTION :TAX: AMOUNT :DATE

020398 1 PT8SX /PIU 100 021798*

INTERST/INTERLT 100%

X 1 X 436.7500 436.75

020398 19 1L5XX /BIP 84/EC 0818 021498*

INTERST/INTERLT 100%

(.00 + (19 X 1.1100)) X 84% 17.72

INTERSTATE SUBTOTAL 468.74

ASG SUBTOTAL 468.74

020398 1 BHMOT /TSC AT039005 122397

INTERSTATE TOTAL 468.74

ACCOUNT TOTAL 468.74

---SUMMARY---

LAST COMPLETED ACTIVITY

R0000000000 XXXXXXXXXXXXXXXX 060298

ACTIVITY LEGEND

* - SERVICE ORDER ACTIVITY

R - RATE CHANGE

M - MISCELLANEOUS

P - JURISDICTIONAL FACTOR CHANGE

B - BIP CHANGE

Z - ZONE CHANGE

TAX LEGEND

APPLICABLE EXEMPT

TYPE CODE CODE

ALL EXEMPT X

FEDERAL X X

STATE X X

ACCESS LINK TRUNK INVENTORY

ASG OCL TSC PAGE

2 ELGNILXDS0 AT039006