NENA

Recommended Standards

For

Service Provider Local Number Portability


TABLE OF CONTENTS

INTRODUCTION

1.1 Purpose 2

1.2 Copyright and Responsibility 2

1.3 Disclaimer 2

1.4 Overview 2

1.5 Reason for Reissue 3

1.6 Acronyms/Terms 3

1.7 Reasons to Implement and Benefits 5

1.8 Implementation 5

1.9 Acknowledgments 6

STANDARDS

2.1 through 2.6 7

2.7 through 2.11 8




Prepared by:

National Emergency Number Association (NENA) Data Standards Technical Committee

Service Provider Local Number Portability Study Group

Published by:

National Emergency Number Association (NENA)

Printed in USA

INTRODUCTION

1.1 Purpose

This document sets forth National Emergency Number Association (NENA) standards for all Local Service Providers involved in providing dial tone to end users and involved in Service Provider Local Number Portability.

1.2 Copyright and Responsibility

This practice was written by the NENA Data Standards Technical Committee in conjunction with the Multiple Local Service Providers study group. The NENA Executive Board has recommended this practice for industry acceptance and use. For more information about this practice, contact:

National Emergency Number Association

47849 Papermill Road

Coshocton, OH 43812-9742

Phone: 800-332-3911

Fax: 614-622-2090

1.3 Disclaimer

This document has been prepared solely for the voluntary use of 9-1-1 service providers, 9-1-1 equipment vendors, and participating Local Service Providers.

By using this practice, the user agrees that NENA will have no liability for any consequential, incidental, special, or punitive damages that may result.

1.4 Overview

This document defines the recommendations for the exchange of telephone number data with a 9-1-1 Service Provider by companies participating in Service Provider Local Number Portability. It anticipates the protection of E9-1-1 data integrity, content, and call delivery regardless of dial tone provider. It is the goal of these standards to support current and future development consistent with the concept of "One Nation, One Number". It is assumed that Federal, State, or Local legislation will supersede these recommendations.

1.5 Reason for Reissue

NENA reserves the right to modify this technical reference. Whenever it is reissued, the reason(s) will be provided in this paragraph.

1.6 Acronyms/Terms

Acronym/Term Definition

Automatic Location An 9-1-1 Feature by which the name, address and responding

Identification (ALI) agencies associated with the number of the telephone used to dial 9-1-1 is displayed at the PSAP at the time the call is answered.

Automatic Number The telephone number associated with the calling party.

Identification (ANI)

Company Identifier A NENA approved 3-5 character identity chosen by the Local

(Company ID) Service Provider that distinguishes the entity providing the dial tone to the end user. The Company Identifier is maintained by NENA in a nationally accessible data base, and is an entry item in NENA 02-001, NENA Recommended Formats for Data Exchange.

Completion Date Applies to the service order process date that does the physical disconnection of dial tone by the donor company and the physical connection of dial tone by the recipient company to an end user.

Data Exchange The NENA Data Standards Subcommittee has established 2 versions of standard data formats for use by data exchange partners when exchanging E9-1-1 ALI data base information, referenced as NENA 02-001, NENA Recommended Formats for Data Exchange.

Donor Company The Local Service Provider responsible for the end user's telephone service and E9-1-1 data prior to the migration of the telephone number to the recipient company.

End User The 9-1-1 caller.

E9-1-1 Enhanced 9-1-1 (name, address, and telephone number displayed).

1.6 Acronyms/Terms cont'd

Acronym/Term Definition

Local Service Provider A term intended to encompass all companies providing dial tone

(LSP) to end users, including but not limited to Incumbent Local Exchange Carriers (ILEC), Alternative Local Exchange Carriers (ALEC) and Private Branch Exchange (PBX) providers.

Migration The term used to describe the inward transaction the recipient company submits to the 9-1-1 Service Provider that signifies movement of telephone service from a donor company.

National Emergency The National Emergency Number Association is a not-for-profit

Number Association corporation established in 1982 to further the goal of "One

(NENA) Nation-One Number." NENA is a networking source and promotes research, planning and training. NENA strives to educate, set standards and provide certification programs, legislative representation and technical assistance for implementing and managing 9-1-1 systems.

Ported In A Local Service Provider's term for the end user's telephone Telephone Number number migrated from a different Local Service Provider.

Ported Out A Local Service Provider's term for the end user's telephone

Telephone Number number migrated to a different Local Service Provider.

Recipient Company The new Local Service Provider responsible for the end user's telephone service and E9-1-1 data after the migration of the telephone number from a donor company.

Relock The recipient company will secure the record when the migration transaction replaces the customer details and Company ID of the donor company. Also allows the donor company to secure a telephone number record that has been unlocked pending a migration to a different Local Service Provider. (See Unlock)

Service Provider Allows the end user to retain their telephone number, providing

Local Number they remain within the same rate area or rate district (where

Portability (SPLNP) established), when changing from one service provider to another.

1.6 Acronyms/Terms cont'd

Acronym/Term Definition

Unlock The action required by a 9-1-1 Service Provider upon notification from a donor company that makes the end user's telephone number record available for the recipient company to replace the customer details and Company ID.

9-1-1 Service Provider The entity(ies) responsible for the ALI system data management (and/or retrieval), and/or Selective Routing management, e.g., a Telephone Company, Data base or Customer Provided Equipment (CPE) vendor, PSAP or County.

1.7 Reasons to Implement and Benefits

Industry adoption of the standard will:

-Ensure the consistent provision of ALI data

-Ensure reliable 9-1-1 call delivery

-Improve communications and remove barriers across entities

-Assist Local Service Providers toward compliance with the FCC order:

CC Docket 95-116, complying with Local Number Portability

1.8 Implementation

How: Use of the standards will provide the basis for agreements between the Local Service Provider and the 9-1-1 service provider.

When: Should be completed prior to the FCC mandated SPLNP conversion date schedule.

See also related standards document NENA 02-005, NENA Recommended Standards for Local Service Providers.

1.9 Acknowledgments

The standards have been created through the cooperative efforts of:

NENA Data Technical Committee - Judy Cortiana Chairperson

Local Number Providers Study Group

Judy Cortiana Pacific Bell Chairperson

Jacki Balto TCG

Terri Beager USWest

Anne Berman NYNEX

Bernard Brabant Bell Sygma

Marcia Broman Metro 9-1-1 Board

Sylvia Cadena Pacific Bell

Cher Cederquist ALLTEL

Stan Czolowski NYNEX

Nancy DeRoo Ameritech

Gary Ekwall Ameritech

Patti Fischer Pacific Bell

Karen Goldstein ICG

Joseph Gondek NYNEX

Judy Graham Time Warner Comm.

Anna Hastings Ameritech

Phil Hollar MCI

Beverly Hood Sprint

Pam Horne Southwestern Bell

Ron Huelsing Southwestern Bell

Rick Jones Illinois NENA

Linda Kerkam NYNEX

Doug Kroupa Lucent

Mark Lancaster AT&T

Jennifer Lynch SCC

Laurie Lyons Pacific Bell

Carolyn Maddox Sprint

Bill Marczak BellSouth

Kurt Mast ASCI

Enoch Morris ALLTEL

Maryellen Nee NYNEX

Dianne O'Brochta Southwestern Bell

David Pattillo BellSouth

John Schoppenhorst GTE

Greg Schiller NYNEX

Thom Selleck TCG

Mary Sharp SCC

Barb Thornburg Winstar Telecommunications, Chairperson

Larry Vasquez AT&T

Carol Wagner CCI

Randy West BellSouth

STANDARDS

  1. Allow any certified company to send end user telephone number records to a 911 Service Provider for any valid NPA-NXX that has access to 9-1-1.


  1. Adopt the use of the Company ID on all transactions and include on all embedded telephone number records in the 911 data base. The telephone number and Company ID relationship will remain the same until the record is unlocked and migrated or completely disconnected. (NENA does not recommend a data structure with one telephone number having more than one Company ID.)


  1. The 9-1-1 Service Provider and Local Service Provider must work together to modify the embedded telephone numbers to include the 3-5 character Company ID as referenced in the document "NENA Company ID Registration Service" available through the NENA National office. This should be completed prior to the FCC mandated SPLNP conversion date schedule.


  1. The ported out telephone numbers should remain in the 911 data base for ALI retrieval until the migration transaction from the new service provider successfully updates the record. This supports the expectation of uninterrupted 9-1-1 service.


  1. The new service provider will send a complete telephone number record to migrate the end user's service, not just the telephone number and Company ID


2.6 The following edits for the C and D function codes in the NENA-02-001, NENA Recommended Formats for Data Exchange for transactions are in addition to any existing edits:

C -create error condition if Company ID doesn't match between the embedded telephone number record in the 9-1-1 data base and the update transaction.

D -create error condition if Company ID doesn't match between the embedded telephone number record in the 9-1-1 data base and the delete transaction.

STANDARDS cont'd

2.7 Create 2 additional function codes for NENA-02-001, NENA Recommended Formats for Data Exchange to assure data integrity:

U -Unlock telephone record transaction sent by the donor company. This will make the telephone number available for the recipient company to overwrite the embedded telephone number record. The "U" function code requires a match of Company ID.

M -Inward migration transaction sent by the recipient company. This transaction requires an "unlocked" record in the 9-1-1 data base and will replace the customer information and the Company ID on the "unlocked" record. The "M" function code does not require a match of Company ID. If there is not a record with the same telephone number in the 9-1-1 data base the "M" transaction will be treated as an error with a unique error code.

2.8 The 9-1-1 Service Provider should make every effort where technically feasible to minimize error reporting to the recipient company when an "M" transaction is received before the corresponding "U" transaction. The 9-1-1 Service Provider must notify the recipient company whenever an "M" transaction is not successfully processed. This can be done as part of the normal reporting process.

The 9-1-1 Service Provider will reprocess all "M" transactions that did not successfully process against an unlocked record, a minimum of one additional time in one additional business day. "M" records to be reprocessed will be treated as a warning with identification of the donor company. If the final "M" attempt fails, the transaction will be treated as an error.

2.9 The service orders should be completed on the date (completion date) the porting activities occur. It is recommended that upon order completion, the "U" transaction will be sent by the donor company and the "M" transaction will be sent by the recipient company to the 9-1-1 Service Provider.

Create a unique informational message code if an "M" transaction is processed and the corresponding embedded data base record remains locked.

Create a unique error condition code identifying when an "M" transaction reprocessing fails in the attempt to update the 9-1-1 data base.

2.10 The 9-1-1 Service Provider must make an exception report(s) available to the donor company if the embedded telephone number record has been in an unlocked state for a period of time not less than 7 calendar days. Upon investigation, the donor company may relock the embedded record using an "M" function code.

2.11 It is expected that cooperative efforts occur between Local Service Providers to resolve all error conditions in a timely manner.