FOR REVIEW AND COMMENT
The following document is now ready for review andcomment. The feedback period is 30 days, beginning May 4, 1998 and continuing
until June 3, 1998.
Please send all comments to:
Bob Miller [email protected]
Executive Director 9-1-1
New Jersey State Police
Box 7068 – Bldg. 11 River Rd.
West Trenton, NJ 08628
Fax (609) 882-1463
Thank you in advance for your time and comments.
Please note: A lot of formatting was lostin the conversion of this file into a web page. If you want to download the Word 6.0file will all the correct formatting, click below.
NENA
Recommended Formats
For Data Exchange
TABLE OF CONTENTS
INTRODUCTION
1.1Purpose…………………………………………………………………………………2
- Copyright and Responsibility…………………………………………………….2
- Disclaimer……………………………………………………………………………..2
- Overview……………………………………………………………………………….2
- Reason for Reissue…………………………………………………………………..2
- Acronyms/Terms……………………………………………………………………..3
- Types of Formats……………………………………………………………………..4
- Reasons to Implement……………………………………………………………….5
- When to Implement………………………………………………………………….5
- Data Content Considerations……………………………………………………..5
- Acknowledgments……………………………………………………………………6
EXHIBITS
Version 1 Formats
1. Format for Data Exchange……………………………………………………….. 7
2. Format for MSAG Data Exchange…………………………………………….. 9
3. Header Format for Data Exchange…………………………………………….. 10
4. Trailer Format for Data Exchange…………………………………………….. 11
Version 2.1 Formats
5. Format for Data Exchange……………………………………………………….. 12
6. Format for MSAG Data Exchange…………………………………………….. 15
7. Header Format for Data Exchange…………………………………………….. 16
Trailer Format for Data Exchange……………………………………………..17
Version 3 Formats
9. Format for DataExchange……………………………………………………….. 18
10. Format for MSAG Data Exchange………………………………………………22
11. Header Format for DataExchange…………………………………………….. 24
- Trailer Format for Data Exchange………………………………………………25
- Format for Wireless Data Exchange…………………………………………….26
14. DataDictionary……………………………………………………………………….27
Prepared by:
National Emergency Number Association (NENA) Data Technical Committee
Published by:
National Emergency Number Association (NENA)
Printed in U.S.A.
INTRODUCTION
1.1 Purpose
This document sets forth NENA standard formats for Automatic Location Identification(ALI) data exchange between Service Providers and Data Base Management System Providers.
Movement of ALI data between Service Providers and/or Data Base Management SystemProviders is a necessary activity for the activation of E9-1-1 systems. Means of movingsuch data is varied and many.
1.2 Copyright and Responsibility
This practice was written by the NENA Data Technical Committee. The NENA Executive Board has not yet recommended this practice for industry acceptance and use.
1.3 Disclaimer
This document has been prepared solely for the voluntary use of Data Base ManagementSystem Providers , E9-1-1 equipment vendors, and participating Service Providers. By usingthis practice, the user agrees that the National Emergency Number Association (NENA) willhave no liability for any consequential, incidental, special, or punitive damages that mayresult.
Overview
The original version 1 document was created in June 1991 to provide established formatsfor exchange of 9-1-1 data between Service Providers and the Data Base Management SystemProviders. The format was created in a fixed format with 232 characters available withinthe record format for ALI data.
Version 2 Data Exchange Formats were added June 1993 to provide for exchange ofadditional data fields, expanding of specific fields to allow for increased characters anddata fields for X,Y,Z coordinates. Version 2 also expanded the length of the data exchangeformat to 512 characters to allow room for future expansion of the record.
Version three (3) has been established due to the difficulty in modifying Version 2standards. Version 3 has been created to reflect data formats utilizing a “TagData” concept, which creates a variable length record dependent upon the data fieldsbeing utilized between Service Providers and Data Base Management System Providers.Version 3 should support the data needs of 9-1-1 for many years.
1.5 Reason for Reissue
This standard has been reissued due to addition of a version 3 Data Exchange Format,utilizing a “Tagged Data with field labels” concept and includes additionalfields and has updated field names to better reflect industry trends.. Version 1 has beenchanged to reflect current terminology in format description fields. Version 2 has beenchanged to reflect new fields which reflect the “year 2000” date identificationand definition of the “Alt #” field for the “ALT#” associated withInterim Number Portability, to identify the Function Code indicators of “U”nlockand “M”igrate for Local Number Portability and to reflect current terminology informat description fields. The will be the last update to Version 2.
Acronyms/Terms
Acronyms and terms are those utilized within this document and also reside within theNENA Master Glossary of 9-1-1 Terminology NENA-01-002.
| Term | Definition |
| Enhanced 9-1-1 (E9-1-1) | An emergency telephone system which includes network switching, database and CPE elements capable of providing Selective routing, Selective Transfer, Fixed Transfer, ANI and ALI. |
| Automatic Location Identification (ALI) | The automatic display at the PSAP of the caller’s telephone number, the address/location of the telephone and supplementary emergency services information. |
| Data Base Management System (DBMS) | A system of manual procedures and computer programs used to create, store and update the data required to provide Selective Routing and/or Automatic Location Identification for 9-1-1 systems. |
| Data Base Management System Provider | Entity providing Selective Routing (SR) and/or Automatic Location Identification (ALI) data services. |
| Emergency Service Number (ESN)/Emergency Service Zone (ESZ) | An ESN is a three to five digit number representing a unique combination of emergency service agencies (Law Enforcement, Fire, and Emergency Medical Service) designated to serve a specific range of addresses within a particular geographical area, or Emergency Service Zones (ESZ). The ESN facilitates selective routing and selective transfer, if required, to the appropriate PSAP and the dispatching of the proper service agency(ies). |
| Emergency Service Routing Digit (ESRD) | (see Pseudo Automatic Number identification) (pANI)) |
| Enhanced 9-1-1 (E9-1-1) Control Office | The Central Office that provides the tandem switching of 9-1-1 calls. It controls delivery of the voice call with ANI to the PSAP and provides Selective Routing, Speed Calling, Selective Transfer, Fixed Transfer and certain maintenance functions for each PSAP. Also known as 9-1-1 Selective Routing Tandem or Selective Router. |
| Local Exchange Carrier (LEC) | A Telecommunications Carrier (TC) under the state/local Public Utilities Act that provide local exchange telecommunications services. Also known as Incumbent Local Exchange Carriers (ILECs), Alternate Local Exchange Carriers (ALECs), Competitive Local Exchange Carriers (CLECs), Competitive Assess Providers (CAPs), Certified Local Exchange Carriers (CLECs), and Local Service Providers (LSPs). |
| Local Number Portability (LNP) | A process by which a telephone number may be reassigned from one Local Exchange Carrier to another. |
| Master Street Address Guide (MSAG) | A data base of street names and house number ranges within their associated communities defining Emergency Service Zones (ESZs) and their associated Emergency Service Numbers (ESNs) to enable proper routing of 9-1-1 calls. |
| National Emergency Number Association (NENA) | The National Emergency Number Association is a not-for-profit corporation established in 1982 to further the goal of “one 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 systems. |
| Selective Routing (SR) | The routing of a 9-1-1 call to the proper PSAP based upon the location of the caller. Selective Routing is controlled by the ESN which is derived from the customer location. |
| Service Address | The physical location of a subscriber access line. Service Address is the recommended address for 9-1-1 use. (May be different from the listed address or the billing address). |
| Service Order | Local Exchange Carrier document used for additions, changes or removals of telephone service. |
| Service Provider | An entity providing one or more of the following 9-1-1 elements: network, CPE or database service. |
| Tag | A unique label that precedes the data for the data element associated with the tag. |
| Tag Data | A method of identifying data elements of varying lengths within a data record. |
| Tag Data Record | A record of varying length, comprised of pre-defined tag labels and their associated data elements. |
1.7 Types of Formats
All data exchange formats utilize ASCII characters. The NENA Data TechnicalCommittee has established 3 versions of standard data formats for use by Service Providersand Data Base Management System Providers when exchanging E9-1-1 data base information.Three (3)versions of standard format have been defined for each of the following:
– ALI data exchange
– MSAG data exchange
– Header and trailer records
Version 1 formats are the original NENA recommended formats utilizing the 240 characterformat for Data Exchange; 160 character format for MSAG Data Exchange and 160 characterformat for Header and Trailer records.
Version 2 formats recognize that the original formats needed to be expanded toaccommodate additional data fields critical to some data providers and also recognizingthat NENA must position the standard record for the future. Version 2 formats contain alldata fields resident in Version 1 formats utilizing a 512 character format for DataExchange; 200 character format for MSAG Data Exchange and 200 character formats for Headerand Trailer records.
Version 3 formats recognize that the previous formats were limiting distribution ofdata as technology evolved and the Data Technical Committee, after much discussion,arrived at the present NENA Version 3 format, included in this document. This format takesa “Tag Data” approach to information exchange for both wireline and wirelessdata distribution. Benefits include faster programming changes, more efficient datatransmission and smaller file sizes. It is strongly recommended that all Service Providersimplement the NENA 3 data exchange format by January 1, 2000 including the defined NENA 3Header and Trailer records.
The NENA Data Technical Committee requires that Service Providers maintain consistencyby utilizing formats consistent to one version. i.e., Header and Trailer records must bethe same version format as the Data or MSAG Exchange formats utilized.
1.8 Reasons to Implement
Industry adoption of the standard will:
– Minimize costs incurred in providing E9-1-1 data base services.
– Ensure timely activation of E9-1-1 data base systems.
– Ensure consistent provision of ALI data.
– Enable data compatibility for system integration of E9-1-1 products and services.
1.9 When to Implement
Since many Service Providers, Data Base Management System Providers and equipmentvendors are currently utilizing the original Version 1 and 2 data formats defined herein,it is strongly recommended that Version 3 formats be implemented to provide for futuredata needs. Service Providers and the respective Data Base Management System Provider mustjointly determine the data format most relevant to the system software being utilized.
A goal of January 1, 2000 is recommended as the date when Service Providers are capableof sending data utilizing the revised Version 2 format and Version 3 format to the DataBase Management System Providers and they be capable of receiving the revised Version 2and new Version 3 formats on January 1, 2000.
It is further understood that many in-service data flows may be unable to conform tothe NENA formats by the target date, but the Data Technical Committee strongly recommendsthat every effort be made to conform to at least one of the recommended formats by January1, 2000.
1.10 Data Content Considerations
Common Considerations:
All data exchange formats utilize ASCII characters.
Data Base Management System Providers should document how they utilize versions 1, 2and 3 and the fields that their software systems can utilize.
The “General Use” field may be used when exchange partners agree to exchangeinformation not defined
All data exchange formats utilize maximum numbers of characters for each field.
Header and Trailer records must be the same version format as the Data or MSAG Exchangeformats utilized.
Version 1 & 2 formats:
Standard field location.
Fixed record lengths.
Data exchange formats require that complete data records be exchanged.
All data fields are treated as “left-justified” with trailing spaces.
Unused fields are space-filled.
Version 3 data formats:
A tag data record is a record of varying length, comprised of pre-defined tag labelsand the associated data elements.
There is no particular sequence of the tag/data combinations within a Tag Data Record.
Each tag and its associated data is separated from all other tag/data combinations by apre-defined field separator.
Each Tag Data Record is followed by a pre-defined End of Record character.
The receiving Data Base Management System Provider will specify the minimum set oftag/data elements required by that system to uniquely identify and process the record.
If the field is not being used (I.E: “Street Suffix”, “PostDirectional”, “Customer Code”) then the label is not used.
Data Technical Committee authorized new tags may be added to the record withoutchanging the file format.
Header records will employ cycle counting to ensure a cycle of updates is not missed.
Trailer records will employ record counting to ensure a record within an update file isnot missed.
Tag Data Processing Logic: Action taken on a field in an existing databaserecord where incoming Version 3 record’s Function of Change (FOC) is change”C”.
| INCOMING VERSION 3 FIELD | ACTION TAKEN ON EXISTING ALI RECORD |
| Tag not sent | Field unchanged |
| Tag, no data | Field cleared |
| Tag, with data | Field changed |
1.11 Acknowledgments
Barb Thornburg Winstar Telecommunications (Chair)
Delaine Arnold GTE
Marcus Andronici SCC
Buddy Anthony GTE
Patty Bluhm HBF Group
Larry Ciesla Lucent
Judy Graham Time Warner Communications
Mike Guinta Bell Atlantic
Karen Hake Cincinnati Bell
Pat Harrison Ameritech
Beverly Hood Sprint
Pam Horne Southwestern Bell
Erica Kind State of Vermont E9-1-1 Board
Tom Lauden Bell Atlantic
Rich Lawton Bell Atlantic
Bill Marczak BellSouth
Bill McMurray Marin County, CA
Tom Muehleisen ALLTEL
Diane O’Brochta Southwestern Bell
Beth Ozanich SCC
Dixie Palmer Washington County, OR
Jackie Rigard Pacific Bell
Diane Wada Emergency Communications Consulting (ECC)
EXHIBIT 1
VERSION 1 FORMAT FOR DATA EXCHANGE
|
FIELD NAME |
POSITION |
BYTES |
TYPE |
DESCRIPTION |
| Function Code |
1 |
1 |
A |
Type of activity the record is being submitted for. Valid entries:
|
| NPA |
2-4 |
3 |
N |
Three digit area code of the Calling Number |
| Calling Number |
5-11 |
7 |
N |
Seven digit telephone number of the Calling Number |
| House Number |
12-21 |
10 |
AN |
House Number. The field should be space filled if no house number is available.
NOTE: Although the House Number field is ten characters, it is understood that telephone companies may only support up to 8 characters. |
| House Number Suffix |
22-25 |
4 |
AN |
House number extension (e.g. /2). The field should be spaced filled if no suffix applies. |
| Prefix Directional |
26-27 |
2 |
A |
Leading street direction prefix. The field should be space filled if no prefix applies. Valid entries:
|
| Street Name |
28-67 |
40 |
AN |
Valid service address of the Calling Number. |
| Street Suffix |
68-71 |
4 |
A |
Valid street abbreviation, as defined by the U.S. Postal Service Publication 28. (e.g. AVE) |
| Post Directional |
72-73 |
2 |
A |
Trailing street direction suffix. The field should be space filled if no suffix applies. Valid entries:
|
| Community Name |
74-105 |
32 |
A |
Valid service community of the street name/house number as designated by the MSAG. |
| State |
106-107 |
2 |
A |
Alpha state abbreviation (e.g. TX) |
| Location |
108-127 |
20 |
AN |
Additional address information (free formatted) describing the exact location of the Calling Number (e.g. Apt 718) |
| Customer Name |
128-159 |
32 |
AN |
Subscriber name associated with the Calling Number. |
| Class of Service |
160 |
1 |
AN |
Value of:
1=Residence 6=Coin 1 W out 2=Business 7=Coin 2 Way 3=Residence PBX 8=Mobile 4=Business PBX 9 = Residence OPX
5=Centrex 0=Residence OPX |
| Type of Service |
161 |
1 |
N |
Value of:
0=Not FX nor Non-Pub 1=FX in 911 serving area 2=FX outside 911 serving area 3=Non-Pub 4=Non-Pub FX in serving area
5=Non-Pub FX outside 911 serving area |
| Exchange |
162-165 |
4 |
AN |
Local Exchange Carrier exchange identifier for the serving telephone office of the customer. |
EXHIBIT 1
VERSION 1 FORMAT FOR DATA EXCHANGE
|
FIELD NAME |
POSITION |
BYTES |
TYPE |
DESCRIPTION |
| ESN |
166-170 |
5 |
AN |
Emergency Service Number associated with the House Number and Street Name.
NOTE: ESN field may be space filled when the Data Base Management System Provider is validating the address. The Service Provider providing the E9-1-1 Selective Routing will provide a list of ESN’s available for assignment. |
| Main NPA |
171-173 |
3 |
N |
Three digit area code of the Main Number associated with the Calling Number. |
| Main Number |
174-180 |
7 |
N |
Seven Digit telephone number of the Main Number associated with the Calling Number. |
| Order Number |
181-190 |
10 |
AN |
Service order number for the activity establishing this record. |
| Extract Date |
191-196 |
6 |
N |
Date on which the record was created in the format. MMDDYY |
| County ID |
197-200 |
4 |
AN |
County Identification code (usually the FIPS code)
NOTE: County Identification field is used to identify the county of call origination . The Subcommittee recommends use of the FIPS code assigned to each county by the U S Census Bureau. |
| Company ID |
201-205 |
5 |
AN |
NENA registered Company Identification code. |
| Source ID |
206 |
1 |
AN |
Code which indicates whether data is part of the initial database creation process or part of the daily update process.
Daily = Space, Initial Load = C |
| Zip Code |
207-211 |
5 |
AN |
Postal Zip Code |
| Zip + 4 |
212-215 |
4 |
AN |
Postal Zip Code Extension |
| General Use |
216-226 |
11 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
| Reserved |
227-239 |
13 |
AN |
This field is reserved for the Data Base Management Systems Provider’s use. |
| End of Record |
240 |
1 |
AN |
Always an asterisk (*). |
NOTE: All fields are left-justified, with trailing spaces.
The Service Provider providing E9-1-1 Selective Routing must provide the governmentalentity with a list of ESN’s available for assignment by MSAG development personnel.
EXHIBIT 2
VERSION 1 FORMAT FOR MSAG DATA EXCHANGE
|
NAME |
POSITION |
BYTES |
TYPE |
| Prefix Directional |
1-2 |
2 |
AN |
| Street Name |
3-42 |
40 |
AN |
| Street Suffix |
43-46 |
4 |
AN |
| Post Directional |
47-48 |
2 |
AN |
| Low Range |
49-58 |
10 |
AN |
| High Range |
59-68 |
10 |
AN |
| Community Name |
69-100 |
32 |
A |
| State |
101-102 |
2 |
A |
| Odd/Even |
103 |
1 |
O, E OR B |
| ESN |
104-108 |
5 |
AN |
| Extract Date |
109-114 |
6 |
MMDDYY |
| PSAP ID |
115-118 |
4 |
AN |
| County ID |
119-122 |
4 |
AN |
| Exchange |
123-126 |
4 |
AN |
| General Use |
127-146 |
20 |
AN |
| Reserved |
147-159 |
13 |
AN |
| End of Record |
160 |
1 |
Always “*” |
NOTE: All fields are left-justified, with trailing spaces.
EXHIBIT 3
VERSION 1 HEADER FORMAT FOR DATA EXCHANGE
|
NAME |
POSITION |
BYTES |
TYPE |
| Header Indicator |
1-5 |
5 |
“UHL” |
| Extract Date |
6-11 |
6 |
MMDDYY |
| Company Name |
12-61 |
50 |
AN |
| Cycle Counter |
62-67 |
6 |
N |
| County ID |
68-71 |
4 |
AN |
| State |
72-73 |
2 |
A |
| General Use |
74-93 |
20 |
AN |
| Reserved |
94-159 |
66 |
AN |
| End of Record |
160 |
1 |
Always “*” |
NOTE: All fields are left-justified, with trailing spaces, except theCycle Counter, this field will be right-justified with leading spaces.
Header records will employ cycle counting to ensure a cycle of updates is notmissed.
When used with an ALI data file, the Reserved field will be expanded to 145 bytes.
EXHIBIT 4
VERSION 1 TRAILER FORMAT FOR DATA EXCHANGE
|
NAME |
POSITION |
BYTES |
TYPE |
| Trailer Indicator |
1-5 |
5 |
“UTL” |
| Extract Date |
6-11 |
6 |
MMDDYY |
| Company Name |
12-61 |
50 |
AN |
| Record Count |
62-70 |
9 |
N |
| Reserved |
71-159 |
89 |
AN |
| End of Record |
160 |
1 |
Always “*” |
NOTE: All fields are left-justified, with trailing spaces, except for the Record Count,this field will be
right-justified with leading spaces.
Trailer records will employ record counting to ensure a record within an update file isnot missed.
When used with an ALI data file, the Reserved field will be expanded to 168 bytes.
EXHIBIT 5
VERSION 2.1 FORMAT FOR DATA EXCHANGE
|
FIELD NAME |
POSITION |
BYTES |
TYPE |
DESCRIPTION |
| Function Code |
1 |
1 |
A |
Type of activity the record is being submitted for. Valid entries:
|
| NPA |
2-4 |
3 |
N |
Three digit area code of the Calling Number. |
| Calling Number |
5-11 |
7 |
N |
Seven digit telephone number of the Calling Number. |
| House Number |
12-21 |
10 |
AN |
House number. The field should be space filled is no house number is available.
NOTE: Although the House Number field is ten characters, it is understood that telephone companies may only support up to 8 characters. |
| House Number Suffix |
22-25 |
4 |
AN |
House number extension (e.g. /2). The field should be space filled if no suffix applies. |
| Prefix Directional |
26-27 |
2 |
A |
Leading street direction prefix. The field should be space filled if no prefix applies. Valid entries:
|
| Street Name |
28-87 |
60 |
AN |
Valid service address of the Calling Number. |
| Street Suffix |
88-91 |
4 |
A |
Valid street abbreviation, as defined by the U. S. Postal Service Publication 28. (e.g. AVE) |
| Post Directional |
92-93 |
2 |
A |
Trailing street direction suffix. The field should be space filled if no suffix applies. Valid entries:
|
| Community Name |
94-125 |
32 |
A |
Valid service community of the street name/house number as designated by the MSAG. |
| State |
126-127 |
2 |
A |
Alpha state abbreviation (e.g. TX) |
| Location |
128-187 |
60 |
AN |
Additional address information (free formatted) describing the exact location of the Calling Number (e.g. Apt 718). |
| Customer Name |
188-219 |
32 |
AN |
Subscriber name associated with the Calling Number. |
| Class of Service |
220 |
1 |
AN |
Value of:
1=Residence 7=Coin 2 Way 2=Business 8=Mobile 3=Residence PBX 9=Residence OPX 4=Business PBX 0=Business OPX 5=Centrex A=Customer Owned Coin
6=Coin 1W out Telephone (COCT) |
EXHIBIT 5
VERSION 2.1 FORMAT FOR DATA EXCHANGE
|
FIELD NAME |
POSITION |
BYTES |
TYPE |
DESCRIPTION |
| Type of Service |
221 |
1 |
N |
Value of:
0=Not FX nor Non-Pub 1=FX in 911 serving area 2=FX outside 911 serving area 3=Non-Pub 4=Non-Pub FX in 911 serving are 5=Non-Pub outside 911 serving area 6=Local Ported Number (LNP)
7=Interim Ported Number |
| Exchange |
222-225 |
4 |
AN |
Local Exchange Carrier exchange identifier for the serving telephone office of the customer. |
| ESN |
226-230 |
5 |
AN |
Emergency Service Number associated with the House number and Street Name.
NOTE: ESN field may be space filled when the Data Base Management System Provider is validating the address. The Service Provider providing the E9-1-1 Selective Routing will provide a list of ESN’s available for assignment. |
| Main NPA |
231-233 |
3 |
N |
Three digit area code of the Main Number associated with the Calling Number. |
| Main Number |
234-240 |
7 |
N |
Seven Digit telephone number of the Main Number associated with the Calling Number. |
| Order Number |
241-250 |
10 |
AN |
Service order number for the activity establishing this record. |
| Extract Date |
251-256 |
6 |
N |
Date on which the record was created in the format MMDDYY |
| County ID |
257-260 |
4 |
AN |
County Identification Code (usually the FIPS code)
NOTE: County Identification field is used to identify the county of call origination . The Subcommittee recommends use of the FIPS code assigned to each county by the U S Census Bureau. |
| Company ID |
261-265 |
5 |
AN |
NENA registered Company Identification code |
| Source ID |
266 |
1 |
AN |
Code which indicates whether data is part of the initial database creation process or part of the daily update process.
Daily = Space, Initial Load = C |
| Zip Code |
267-271 |
5 |
AN |
Postal Zip Code |
| Zip + 4 |
272-275 |
4 |
AN |
Postal Zip Code Extension |
| General Use |
276-286 |
11 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
| Customer Code |
287-289 |
3 |
AN |
Code used to uniquely identify a customer. |
| Comments |
290-319 |
30 |
AN |
Optional notes, may be displayed at PSAP |
| X Coordinate |
320-328 |
9 |
AN |
Longitude/ X coordinate |
| Y Coordinate |
329-337 |
9 |
AN |
Latitude/ Y coordinate |
| Z Coordinate |
338-342 |
5 |
AN |
Structure elevation |
| Cell ID |
343-348 |
6 |
AN |
Identification number indicating a geographic region of cellular coverage. |
| Sector ID |
349 |
1 |
AN |
Sub set/section of a cell. |
| TAR Code |
350-355 |
6 |
AN |
Taxing Area Rate Code |
EXHIBIT 5
VERSION 2.1 FORMAT FOR DATA EXCHANGE
|
FIELD NAME |
POSITION |
BYTES |
TYPE |
DESCRIPTION |
| Reserved |
356-376 |
21 |
AN |
This field is reserved for the Data Base Management Systems Providers ’s use. |
| ALT # |
377-386 |
10 |
N |
Customer Number being remote call forwarded in Interim Number Portability service. |
| Expanded Extract Date |
387-394 |
8 |
N |
Date on which the record was created in the format YYYYMMDD |
| NENA Reserved |
395-480 |
86 |
AN |
This field is reserved for NENA Data Technical Committee Assignment |
| Reserved |
481-511 |
31 |
AN |
This field is reserved for the Data Base Management Systems Providers ’s use. |
| End of Record |
512 |
1 |
AN |
Always an asterisk (*). |
NOTE: All fields are left-justified, with trailing spaces.
The Service Provider providing E9-1-1 Selective Routing must provide the governmentalentity with a list of ESN’s available for assignment by MSAG development personnel.
EXHIBIT 6
VERSION 2.1 FORMAT FOR MSAG DATA EXCHANGE
|
NAME |
POSITION |
BYTES |
TYPE |
| Prefix Directional |
1-2 |
2 |
AN |
| Street name |
3-62 |
60 |
AN |
| Street Suffix |
63-66 |
4 |
AN |
| Post Directional |
67-68 |
2 |
AN |
| Low Range |
69-78 |
10 |
AN |
| High Range |
79-88 |
10 |
AN |
| Community Name |
89-120 |
32 |
A |
| State |
121-122 |
2 |
A |
| Odd/Even |
123 |
1 |
O, E or B |
| ESN |
124-128 |
5 |
AN |
| Extract Date |
129-134 |
6 |
MMDDYY |
| PSAP ID |
135-138 |
4 |
AN |
| County ID |
139-142 |
4 |
AN |
| Exchange |
143-146 |
4 |
AN |
| General Use |
147-166 |
20 |
AN |
| TAR Code |
167-172 |
6 |
AN |
| Reserved |
172-191 |
19 |
AN |
| Expanded Extract Date |
192-199 |
8 |
N |
| End of record |
200 |
1 |
Always “*” |
NOTE: All fields are left-justified, with trailing spaces.
EXHIBIT 7
VERSION 2.1 HEADER FORMAT FOR DATA EXCHANGE
|
NAME |
POSITION |
BYTES |
TYPE |
| Header Indicator |
1-5 |
5 |
“UHL” |
| Extract Date |
6-11 |
6 |
MMDDYY |
| Company Name |
12-61 |
50 |
AN |
| Cycle Counter |
62-67 |
6 |
N |
| County ID |
68-71 |
4 |
AN |
| State |
72-73 |
2 |
A |
| General Use |
74-93 |
20 |
AN |
| Release Number |
94-96 |
3 |
N |
| Format Version |
97 |
1 |
N |
| Expanded Extract Date |
98-105 |
8 |
N |
| Reserved |
106-199 |
94 |
AN |
| End of Record |
200 |
1 |
Always “*” |
NOTE: All fields are left-justified, with trailing spaces, except theCycle Counter, this field will be right-justified with leading spaces.
Header records will employ cycle counting to ensure a cycle of updates is not ismissed.
When used with an ALI data file, the Reserved field will be expanded to 414 bytes.
EXHIBIT 8
VERSION 2.1 TRAILER FORMAT FOR DATA EXCHANGE
|
NAME |
POSITION |
BYTES |
TYPE |
| Trailer Indicator |
1-5 |
5 |
“UTL |
| Extract Date |
6-11 |
6 |
MMDDYY |
| Company Name |
12-61 |
50 |
AN |
| Record Count |
62-70 |
9 |
N |
| Expanded Extract Date |
71-78 |
8 |
N |
| Reserved |
79-199 |
121 |
AN |
| End of Record |
200 |
1 |
Always “*” |
NOTE: All fields are left-justified, with trailing spaces, except forthe Record Count, this field will be right-justified with leading spaces.
Trailer records will employ record counting to ensure a record within an updatefile is not missed.
When used with an ALI data file, the Reserved field will be expanded to 441 bytes.
EXHIBIT 9
VERSION 3 FORMAT FOR DATA EXCHANGE
|
NAME |
LABEL |
MAX #
BYTES |
TYPE |
DESCRIPTION |
|
| Record Type |
DAT or
RTN |
0 |
Indicates start of data record (label only, no data follows). Valid labels:
|
||
| Status Indicator |
STI |
1 |
AN |
Record status indicator. Valid entries:
E = Error C = Completed P = Pending
U = Unprocessed Gateway received but not sent to processing, (future date) |
|
| Function Code |
FOC |
1 |
A |
Type of activity the record is being submitted for. Valid entries:
C = Change D = Delete I = Insert U = Unlock
M = Migrate |
|
| Calling Telephone Number |
CTN |
10 |
N |
Ten digit telephone number of the Calling Telephone Number. NPANXXXXXX | |
| House Number |
HNO |
10 |
AN |
House Number. Footnote | |
| House Number Suffix |
HNS |
4 |
AN |
House number extension (e.g. 1/2). Footnote 1,2 | |
| Prefix Directional |
PRD |
2 |
A |
Leading street direction prefix. Footnote 1,2 Valid Entries:
N S E W
NE NW SE SW |
|
| Street Name |
STN |
60 |
AN |
Valid service address of the Calling Telephone Number. Footnote 1,2 | |
| Street Suffix |
STS |
4 |
A |
Valid street abbreviation, as defined by the U S Postal Service Publication 28. (e.g. AVE) Footnote 1,2 | |
| Post Directional |
POD |
2 |
A |
Trailing street direction suffix. Footnote 1,2
Valid entries: N S E W
NE NW SE SW |
|
| MSAG Community Name |
MCN |
32 |
A |
Valid service community name as identified by the MSAG. Footnote 1,2 | |
| Postal Community Name |
PCN |
32 |
A |
Valid service community name as identified by the U S Postal Service. | |
| State |
STA |
2 |
A |
Alpha state abbreviation (e.g., TX) Footnote 1,2 | |
| Location |
LOC |
60 |
AN |
Additional address information (free formatted) describing the exact location of the Calling Telephone Number (e.g., Apt 718) Footnote 2 This information may be displayed at the PSAP | |
| Also Rings At Address |
ARA |
60 |
AN |
Secondary address for the Calling Telephone Number that rings at 2 locations. Not validated against the MSAG. This information may be displayed at the PSAP | |
| Customer Name |
NAM |
32 |
AN |
Subscriber name associated with the Calling Telephone Number. | |
EXHIBIT 9
VERSION 3 FORMAT FOR DATA EXCHANGE
|
NAME |
LABEL |
MAX #
BYTES |
TYPE |
DESCRIPTION |
|
| Class of Service |
CLS |
1 |
AN |
Value of:
1 = Residence 7 = Coin 2Way 2 = Business 8 = Mobile 3 = Residence PBX 9 = Residence OPX 4 = Business PBX 0 = Business OPX 5 = Centrex A = Customer Owned
6 = Coin 1W out Coin Telephone (COCT) |
|
| Type of Service |
TYS |
1 |
AN |
Value of:
0 = Not FX nor Non-Pub 1 = FX in 911 serving area 2 = FX outside 911 serving area 3 = Non-Pub 4 = Non-Pub FX in 911 serving area 5 = Non-Pub FX outside 911 serving area 6 = Local Ported Number (LNP)
7 = Interim Ported Number (INP) |
|
| Exchange |
EXC |
4 |
AN |
Switching entity which provides dial tone. | |
| Emergency Service Number (ESN) |
ESN |
5 |
AN |
Emergency Service Number associated with the House Number and Street Name and Community Name.
Note:. The Service Provider, providing the E9-1-1 Selective Routing will assign ESN’s. |
|
| Main Telephone Number |
MTN |
10 |
N |
Ten digit telephone number of the Main Billing Number associated with the Calling Telephone Number. NPANXXXXXX | |
| Order Number |
ORD |
10 |
AN |
Service order number for the activity associated with this record. | |
| Completion Date |
CPD |
8 |
N |
Service order completion date. YYYYMMDD | |
| County ID |
COI |
5 |
AN |
County Identification code (usually the FIPS code).
Note: County Identification field is used to identify the county of call origination. The Committee recommends use of the FIPS code assigned to each county by the U S Census Bureau. |
|
| Company ID 1 |
CPF |
5 |
AN |
NENA registered Company Identification code for Service Provider providing facilities for dial tone to the customer. | |
| Company ID 2 |
CPS |
5 |
AN |
NENA registered Company Identification code for Service Provider/Reseller/Private Switch supplying ALI record source information. | |
| Zip Code |
ZIP |
5 |
AN |
Postal Zip Code | |
| Zip + 4 |
ZP4 |
6 |
AN |
Postal Zip Code Extension | |
| Customer Code |
CUS |
3 |
AN |
Code used to uniquely identify a customer | |
| Comments |
CMT |
30 |
AN |
Optional notes, may be displayed at PSAP | |
| TAR Code |
TAR |
6 |
AN |
Taxing Area Rate Code | |
| Alternate Telephone Number |
ALT |
10 |
N |
Remote Call Forwarding number used during Interim Number Portability-NPANXXXXXX | |
EXHIBIT 9
VERSION 3 FORMAT FOR DATA EXCHANGE
|
NAME |
LABEL |
MAX #
BYTES |
TYPE |
DESCRIPTION |
|
| Return Code 1 |
RC1 |
3 |
N |
Code indicating specific processing error code or processing completed successfully. Valid entries:
Not present (or 000 if used) = processing completed successfully
XXX = Valid NENA Standard Error Code |
|
| Return Code 2 |
RC2 |
3 |
N |
Code indicating specific processing error code or processing completed successfully. Valid entries:
Not present (or 000 if used) = processing completed successfully XXX = Valid NENA Standard Error Code |
|
| Return Code 3 |
RC3 |
3 |
N |
Code indicating specific processing error code or processing completed successfully. Valid entries:
Not present (or 000 if used) = processing completed successfully XXX = Valid NENA Standard Error Code |
|
| Non Voice Indicator |
NVC |
1 |
AN |
Non-Voice type calls. Valid entries:
1 = TTY call |
|
| General Use 1 |
GU1 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. | |
| General Use 2 |
GU2 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. | |
| General Use 3 |
GU3 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. | |
| General Use 4 |
GU4 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. | |
| General Use 5 |
GU5 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. | |
| General Use 6 |
GU6 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. | |
| General Use 7 |
GU7 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. | |
| General Use 8 |
GU8 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. | |
EXHIBIT 9
VERSION 3 FORMAT FOR DATA EXCHANGE
|
NAME |
LABEL |
MAX #
BYTES |
TYPE |
DESCRIPTION |
|
| X Coordinate |
XCD |
11 |
AN |
Longitude/X coordinate. Right Justified: pad field with zeros to left of decimal degrees. +long: east of Greenwich; -long: west of Greenwich. Sample: +000.000000 | |
| Y Coordinate |
YCD |
11 |
AN |
Latitude/Y coordinate. Right Justified; pad field with zeros to left of decimal degrees. +lat: north of equator; -lat: south of equator. Sample: +000.###### | |
| Z Coordinate |
ZCD |
6 |
AN |
Altitude indicated as mean sea level, measured in feet. Blank record indicates data not available. Sample: ####.# | |
| Cell Site ID |
CEL |
6 |
AN |
Identification number indicating a geographic region of cellular coverage. | |
| Sector ID |
SEC |
1 |
AN |
Sub set/section of a cell. | |
The items below do not require a “Label” only the symbol shown
| Field Separator |
1 |
AN |
A “pipe” is to be utilized for the field separator
(ASCII HEX-7C) |
|
| End of record NL |
1 |
AN |
The NEW LINE character is a single character that identifies the end of record in all cases for all records.(ASCII HEX-0A) |
Data Record Format Example:
DAT|FOC.|CTN……….|HNO……….|PRD..|STN………………..|STS….|COM………………..|STA..|LOC………………………..|NAM…………………………………….|CLS.|TYS.|MTN……….|CPD……..|CPI…..|NL
NOTE: If the field is not being used (I.E: “Street Suffix”, “PostDirectional”, “Customer Code”) then the label is not used. It is also notnecessary for the labels to be in any particular order. Fields may be added to the recordwithout changing the file format.
The Service Provider, providing E9-1-1 Selective Routing must provide the governmentalentity with a list of ESN’s available for assignment by MSAG development personnel.
EXHIBIT 10
VERSION 3 FORMAT FOR MSAG DATA EXCHANGE
|
NAME |
LABEL |
MAX #
BYTES |
TYPE |
DESCRIPTION |
| Record Type |
MSG |
0 |
Indicates start of MSAG record (label only, no data follows) | |
| Function Code |
FOC |
1 |
A |
Type of activity the record is being submitted for. Valid entries:
C = Change D = Delete
I = Insert |
| Prefix Directional |
PRD |
2 |
AN |
Leading street direction prefix. Footnote 1,2 Valid Entries:
N S E W
NE NW SE SW |
| Street Name |
STN |
60 |
AN |
Valid service address of the Calling Telephone Number. Footnote 1,2 |
| Street Suffix |
STS |
4 |
AN |
Valid street abbreviation, as defined by the U S Postal Service Publication 28. (e.g. AVE) Footnote 1,2 |
| Post Directional |
POD |
2 |
AN |
Trailing street direction suffix. Footnote 1,2
Valid entries: N S E W
NE NW SE SW |
| Low Range |
LOR |
10 |
AN |
The lowest house number that is included in this ESN definition |
| High Range |
HIR |
10 |
AN |
The highest house number that is included in this ESN definition |
| MSAG Community Name |
MCN |
32 |
A |
Valid service community name as defined by the MSAG |
| Postal Community Name |
PCN |
32 |
A |
Valid service community name as defined by the U S Postal Service |
| State |
STA |
2 |
A |
Alpha state abbreviation (e.g., TX) Footnote 1,2 |
| Odd/Even |
OEN |
1 |
A |
Valid entries:
O = Odd numbering only E = Even numbering only
B = both odd and even numbering |
| Emergency Service Number (ESN) |
ESN |
5 |
AN |
Emergency Service Number associated with this House Number range, Street Name and Community Name. |
| Completion Date |
CPD |
8 |
N |
YYYYMMDD |
| PSAP ID |
PSI |
4 |
AN |
Code identifying the PSAP associated with the assigned ESN |
| County ID |
COI |
5 |
AN |
County Identification code (usually the FIPS code).
Note: County Identification field is used to identify the county of call origination. The Committee recommends use of the FIPS code assigned to each county by the U S Census Bureau. |
| Exchange |
EXC |
4 |
AN |
Switching entity which provides dial tone. |
EXHIBIT 10
VERSION 3 FORMAT FOR MSAG DATA EXCHANGE
|
AME |
LABEL |
MAX #
BYTES |
TYPE |
DESCRIPTION |
| TAR Code |
TAR |
6 |
AN |
Taxing Area Rate Code associated with this House Number range, Street Name and Community Name |
| E9-1-1 Control Office |
SRT |
11 |
AN |
9-1-1 Control Office CLLI as identified in the Bellcore LERG |
| General Use 1 |
GU1 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
| General Use 2 |
GU2 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
The items below do not require a “Label” only the symbol shown
| Field Separator |
| |
A “pipe” is to be utilized for the field separator (ASCII HEX-7C) | ||
| End of record |
NL |
A NEW LINE character is a single character that identifies the end of record in all cases for all records. (ASCII HEX-0A) |
MSAG Record Format Example:
MSG|FOC.|PRD..|STN…………………………………|STS….|LOR……….|HIR……….|MCN……………………………|PCN……………………………|STA..|OEN.|ESN…..|CPD……..|EXC….|SRT………..|GU1………………………………………………………………………….|NL
NOTE: If the field is not being used (I.E: General Use) then the label is not used. Itis also not necessary for the labels to be in any particular order. Fields may be added tothe record without changing the file format.
EXHIBIT 11
VERSION 3 HEADER FORMAT FOR DATA EXCHANGE
|
NAME |
LABEL |
MAX #
BYTES |
TYPE |
DATA DESCRIPTION |
| Record Type |
HDR |
0 |
Indicates start of header record (label only, no data follows) | |
| Extract Date |
EXD |
8 |
N |
Year, Month, Day the data was processed, YYYYMMDD |
| Company Name |
CON |
50 |
AN |
Name of Company forwarding file |
| Cycle Counter |
CYC |
9 |
N |
Sequential number, 1-999,999,999 |
| Record Count |
REC |
9 |
N |
Number of records by record type in file, does not include Header and Trailer records |
| General Use |
GEN |
20 |
AN |
Field to be utilized by sender/receiver company’s to provide additional information |
The items below do not require a “Label” only the symbol shown
| Field Separator |
1 |
AN |
A “pipe” is to be utilized for the field separator (ASCII HEX-7C) | |
| End of record NL |
1 |
AN |
The NEW LINE character is a single character that identifies the end of record In all cases for all records. (ASCII HEX-0A) |
Header Record Format Example:
HDR|EXDYYYYMMDD|CON…………………………………………..|CYC………|REC………|GEN………………..|NL
NOTE: If the field is not being used (I.E: General Use) then the label is not used. Itis also not necessary for the labels to be in any particular order, except for the RecordType indicator which must be first. Fields may be added to the record without changing thefile format.
Header records will employ cycle counting to ensure a cycle of updates is not missed.
EXHIBIT 12
VERSION 3 TRAILER FORMAT FOR DATA EXCHANGE
|
NAME |
LABEL |
MAX #
BYTES |
TYPE |
DATA DESCRIPTION |
| Record Type |
TLR |
0 |
Indicates start of Trailer record (label only, no data follows) | |
| Record Count |
REC |
9 |
N |
Number of records by record type in file, does not include Header and Trailer records |
The items below do not require a “Label” only the symbol shown
| Field Separator |
1 |
AN |
A “pipe” is to be utilized for the field separator (ASCII HEX-7C) | |
| End of record |
1 |
AN |
A NEW LINE character identifies the end of record value in all cases for all records. (ASCII HEX-0A) |
Trailer Record Format Example:
TLR|REC………|NL
NOTE: Fields may be added to the record without changing the file format, Because arecord consists of the data found between one new line and the next, labels need notfollow in sequence though checking for duplicate labels within a single record would beprudent.
Trailer records will employ record counting to ensure a record within an update file isnot missed.
EXHIBIT 13
VERSION 3 FORMAT FOR WIRELESS DATA EXCHANGE
|
NAME |
LABEL |
MAX # BYTES |
TYPE |
DESCRIPTION |
|
Call-Back Number |
CBN |
10 |
AN |
TN that can be dialed to reach a specific Wireless Calling party. Minimum 10 digits. |
|
MOBILE ID (MIN) |
MIN |
10 |
AN |
Mobile Identification number of the cellular wireless device. |
|
Roamer Port |
RPT |
10 |
AN |
Temporarily assigned “roamer” call back number. |
|
Channel |
RCC |
3 |
AN |
Channel signal received on. |
|
X Coordinate |
XCD |
11 |
N |
Longitude/X coordinate. Right Justified; pad field with zeros to left of decimal degrees. +long: east of Greenwich; -long: west of Greenwich. Sample: +000.###### |
|
Y Coordinate |
YCD |
11 |
N |
Latitude/Y coordinate. Right Justified; pad field with zeros to left of decimal degrees. +lat: north of equator; -lat: south of equator. Sample: +000.###### |
|
Z Coordinate |
ZCD |
6 |
N |
Altitude indicated as mean sea level, measured in feet. Blank record indicates data not available. Sample: ####.# |
|
P-ANI/Default |
PNI |
10 |
AN |
Pseudo ANI or locally specific code identifying the receiving antenna for the wireless 9-1-1 call for default routing purposes. |
|
Location Valid Flag |
LVD |
1 |
N |
Valid data indicator (1=OK;0=Invalid). |
|
Datum |
NDA |
2 |
AN |
A code consisting of two digits. The code 83 will be the default, identifying WGS84/NAD83; Other codes will be developed as additional datum become available through authorized entities. |
|
LDT Confidence |
COF |
4 |
N |
Sphere of confidence measured as a radius from the coordinate point generated by the LDT provider. The measurement in meters is to be calculated by LDT provider within the industry specified minimum standard. Also referred to as confidence interval. |
|
LDT Confidence % |
CO% |
2 |
N |
Degree of freedom within which the confidence interval falls. |
|
LDT Provider ID |
LDT |
8 |
AN |
LDT Provider Identification Code. Codes to be developed and held by NENA. |
|
LDT Technology |
LTY |
4 |
AN |
Location Determination Technology type used to determine specific point location. |
|
Time Stamp |
TME |
8 |
AN |
Universal Time Coordinate (UTC) indicating milliseconds into UTC day. |
|
Time Stamp (DAY) |
DAY |
7 |
N |
Year and Julian date. (UTC Date). Sample: 1996187 (YYYYDDD). |
|
Speed (in KPH) |
SPD |
3 |
N |
Speed of travel in kilometers per hour. |
|
Heading (in degrees) |
HDG |
3 |
N |
Direction of travel, decimal degrees from true north. Never higher than 359. |
Wireless Data Format Example:
CBN……….|MIN……….|RPT………..|RCC…|XCD………..|YCD………..|ZCD……|PNI……….|LVD.|NDA..|COF….|CO%..|LDT……..|LTY….|TME……..|DAY…….|SPD…|HDG…|NL
EXHIBIT 14
DATA DICTIONARY
|
LABEL |
NAME |
MAX# BYTES |
TYPE |
DESCRIPTION |
|
DAT HDR MSG RTN
TLR |
Record Type |
0 |
A |
Indicates the start of a data record (Label only, No Data follows): Valid Labels:
DAT = Data Record sent from the Service Provider to the Data Base Management System Provider HDR = Indicates start of Header Record MSG = Indicates start of MSAG Record RTN = Data Record returned from the Data Base Management System Provider to the Service Provider
TLR = Indicates start of Trailer Record |
|
ALT |
Alternate Telephone Number |
10 |
N |
Remote Call Forwarding number used during Interim Number Portability – NPANXXXXXX |
|
ARA |
Also Rings At Address |
60 |
AN |
Secondary address for the Calling Telephone Number that rings at 2 locations. Not validated against the MSAG. This information may be displayed at the PSAP |
|
CBN |
Call-Back Number |
10 |
V |
TN that can be dialed to reach a specific Wireless Calling party. Minimum 10 digits. |
|
CEL |
Cell Site ID |
6 |
AN |
Identification number indicating a geographic region of wireless coverage. |
|
CLS |
Class of Service |
1 |
AN |
Value of:
1 = Residence 7 = Coin 2 Way 2 = Business 8 = Wireless 3 = Residence PBX 9 = Residence OPX 4 = Business PBX 0 = Business OPX 5 = Centrex A = Customer owned Coin Telephone
6 = Coin 1W out (COCT) |
|
CMT |
Comments |
30 |
AN |
Optional notes; may be displayed at PSAP |
|
CO% |
LDT Confidence % |
2 |
N |
The degree of freedom within which the confidence interval fails. |
|
COF |
LDT Confidence |
4 |
N |
Sphere of confidence measured as a radius from the coordinate point generated by the LDT provider. The measurement in meters is to be calculated by LDT provider within the industry specified minimum standard. Also referred to as confidence interval. |
|
COI |
County ID |
4 |
AN |
County Identification Code – (Usually FIPS code. Note: County Identification field is used to identify the county of call origination. The committee recommends use of the FIPS code assigned to each county by the Census Bureau. |
|
CON |
Company Name |
50 |
AN |
Name of Company forwarding file. |
|
CPD |
Completion Date |
8 |
N |
Service Order Completion Date. YYYYMMDD |
|
CPF |
Company ID 1 |
5 |
AN |
NENA Registered Company Identification code for Service Provider providing facilities for dial tone to the customer. |
|
CPS |
Company ID 2 |
5 |
AN |
NENA Registered Company Identification Code for Service Provider/Reseller/Private Switch supplying ALI record source information. |
|
CTN |
Calling Telephone Number |
10 |
N |
Ten Digit telephone number of the Wireline Calling Telephone Number. NPA-NXX-XXXX |
|
CUS |
Customer Code |
3 |
AN |
Code used to uniquely identify a customer |
|
CYC |
Cycle Counter |
9 |
N |
Sequential Number, 1-999,999,999 |
EXHIBIT 14
DATA DICTIONARY
|
LABEL |
NAME |
MAX# BYTES |
TYPE |
DESCRIPTION |
|
DAY |
Time Stamp (DAY) |
7 |
N |
Year and Julian date. (UTC Date). Sample: 1996187 (YYYYDDD). |
|
ESN |
Emergency Service Number (ESN) |
5 |
AN |
Emergency Service Number associated with the House Number and Street Name.
Note: The Service Provider, providing the E9-1-1 Selective Routing will assign ESN’s. |
|
EXC |
Exchange |
4 |
AN |
Switching entity which provides dial tone. |
|
EXD |
Extract Date |
8 |
N |
Year, Month, Day the data was processed, YYYYMMDD |
|
FOC |
Function Code |
1 |
A |
Type of activity the record is being submitted for. Valid entries:
C = Change D = Delete I = Insert U = Unlock
M = Migrate |
|
GEN |
General Use |
20 |
AN |
Field to be utilized by sender/receiver companies to provide additional data |
|
GU1 |
General Use 1 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
|
GU2 |
General Use 2 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
|
GU3 |
General Use 3 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
|
GU4 |
General Use 4 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
|
GU5 |
General Use 5 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
|
GU6 |
General Use 6 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
|
GU7 |
General Use 7 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
|
GU8 |
General Use 8 |
60 |
AN |
This field will be mutually used by data exchange partners to pass information not defined in previous fields. |
|
HDG |
Heading (in degrees) |
3 |
N |
Direction of travel, decimal degrees from true north. Never higher than 359. |
|
HIR |
High Range |
10 |
AN |
The highest house number that is included in this ESN definition. |
|
HNO |
House Number |
10 |
AN |
House Number. |
|
HNS |
House Number Suffix |
4 |
AN |
House number extension (e.g. 1/2). Footnote 1,2 |
|
LDT |
LDT Provider ID |
8 |
AN |
LDT Provider Identification Code. Codes to be developed and held by NENA. |
|
LOC |
Location |
60 |
AN |
Additional address information (free formatted) describing the exact location of the Calling Telephone Number (e.g., Apt 718) Footnote 2. This information may be displayed at the PSAP. |
|
LOR |
Low Range |
10 |
AN |
The lowest house number that is included in this ESN definition. |
|
LTY |
LDT Technology |
4 |
AN |
Location Determination Technology type used to determine specific point location. |
EXHIBIT 14
DATA DICTIONARY
|
LABEL |
NAME |
MAX# BYTES |
TYPE |
DESCRIPTION |
|
|
LVD |
Location Valid Flag |
1 |
N |
Valid data indicator (1=OK;0=Invalid). | |
|
MCN |
MSAG Community Name |
32 |
A |
Valid service community name as identified by the MSAG. | |
|
MIN |
Mobile Identification Number |
10 |
AN |
Mobile Identification Number of the cellular wireless device. | |
|
MTN |
Main Telephone Number |
10 |
N |
Ten digit telephone number of the Main Billing Number associated with the Calling Telephone Number. NPANXXXXXX | |
|
NAM |
Customer Name |
32 |
AN |
Subscriber name associated with the Calling Telephone Number. | |
|
NDA |
Datum |
2 |
AN |
A code consisting of two digits. The code 83 will be the default, identifying WGS84/NAD83; Other codes will be developed as additional datum become available through authorized entities. | |
|
NVC |
Non Voice Indicator |
1 |
AN |
Non-Voice type calls. Valid entries:
1 = TTY call |
|
|
OEN |
Odd/Even |
1 |
A |
Valid entries:
O = odd numbering only E = even numbering only
B = both odd and even numbering |
|
|
ORD |
Order Number |
10 |
AN |
Service order number for the activity associated with this record. | |
|
PCN |
Postal Community Name |
32 |
A |
Valid service community name as identified by the U S Postal Service. | |
|
PNI |
P-ANI/Default |
10 |
AN |
Pseudo ANI or locally specific code identifying the receiving antenna for the wireless 9-1-1 call for default routing purposes. | |
|
POD |
Post Directional |
2 |
A |
Trailing street direction suffix. Footnote 1,2
Valid entries: N S E W
NE NW SE SW |
|
|
PRD |
Prefix Directional |
2 |
A |
Leading street direction prefix. Footnote 1,2 Valid Entries:
N S E W
NE NW SE SW |
|
|
PSI |
PSAP ID |
4 |
AN |
Code identifying the PSAP associated with the assigned ESN. | |
|
RC1 |
Return Code 1 |
3 |
N |
Code indicating specific processing error code or processing completed successfully. Valid entries:
Not present (or 000 if used) = processing completed successfully
XXX = specific processing error code |
|
|
RC2 |
Return Code 2 |
3 |
N |
Code indicating specific processing error code or processing completed successfully. Valid entries:
Not present (or 000 if used) = processing completed successfully
XXX = specific processing error code |
|
|
RC3 |
Return Code 3 |
3 |
N |
Code indicating specific processing error code or processing completed successfully. Valid entries:
Not present (or 000 if used) = processing completed successfully
XXX = specific processing error code |
|
|
RCC |
Channel |
3 |
AN |
Channel signal received on | |
EXHIBIT 14
DATA DICTIONARY
|
LABEL |
NAME |
MAX# BYTES |
TYPE |
DESCRIPTION |
||
|
REC |
Record Count |
9 |
N |
Number of records by record type in file, does not include Header and Trailer records | ||
|
RPT |
Roamer Port |
10 |
AN |
Temporarily assigned “roamer” call back number | ||
|
SEC |
Sector ID |
1 |
AN |
Sub set/section of a cell. | ||
|
SPD |
Speed (in KPH) |
3 |
N |
Speed of travel in kilometers per hour. | ||
|
SRT |
9-1-1 Control Office |
11 |
AN |
9-1-1 Control Office CLLI as identified in the Bellcore LERG | ||
|
STA |
State |
2 |
A |
Alpha state abbreviation (e.g., TX) Footnote 1,2 | ||
|
STI |
Status Indicator |
1 |
AN |
Record status indicator. Valid entries:
E = Error C = Completed P = Pending
U = Unprocessed Gateway received but not sent to processing, (future date) |
||
|
STN |
Street Name |
60 |
AN |
Valid service address of the Calling Telephone Number. Footnote 1,2 | ||
|
STS |
Street Suffix |
4 |
A |
Valid street abbreviation, as defined by the U S Postal Service Publication 28. (e.g. AVE) Footnote 1,2 | ||
|
TAR |
TAR Code |
6 |
AN |
Taxing Area Rate Code | ||
|
TME |
Time Stamp |
8 |
AN |
Universal Time Coordinate (UTC) indicating milliseconds into UTC day. | ||
|
TYS |
Type of Service |
1 |
AN |
Value of:
0 = Not FX nor Non-Pub 1 = FX in 911 serving area 2 = FX outside 911 serving area 3 = Non-Pub 4 = Non-Pub FX in 911 serving area 5 = Non-Pub FX outside 911 serving area 6 = Local Ported Number (LNP)
7 = Interim Ported Number (INP) |
||
|
XCD |
X Coordinate |
11 |
AN |
Longitude/X coordinate. Right Justified; pad field with zeros to left of decimal degrees. +long: east of Greenwich; -long: west of Greenwich. Sample: +000.###### | ||
|
YCD |
Y Coordinate |
11 |
AN |
Latitude/Y coordinate. Right Justified; pad field with zeros to left of decimal degrees. +lat: north of equator; -lat: south of equator. Sample: +000.###### | ||
|
ZCD |
Z Coordinate |
6 |
N |
Altitude indicated as mean sea level, measured in feet. Blank record indicates data not available. Sample: ####.# | ||
|
ZIP |
Zip Code |
5 |
AN |
Postal Zip Code | ||
|
ZP4 |
Zip + 4 |
6 |
AN |
Postal Zip Code Extension | ||
|
|
‘pipe” |
Field Separator |
1 |
AN |
A “pipe” is to be utilized for the field separator (ASCII HEX-7C) | ||
|
(nl)
new line |
End of record |
1 |
AN |
A NEW LINE character identifies the end of record value in all cases for all records. (ASCII HEX-0A) | ||