BellSouth E911 - Manual (Page 43)

CG-EWCG-001 Wireless E911 Guide
Issue 3, January 6, 2004 TN Database Updates
data records, the location data field may be used to define the cell site sector geographical service area.
Wireless Carriers should work with the E911 Customer and agree on the TN data record formats including
use of the LOCATION (LOC) data field.
There are four(4) levels of identifiers used for different types of information. Those identifiers are shown
as follows in the appropriate hierarchical level:
Level 1: BLDG, WNG, PIER
Level 2: FLR
Level 3: APT, RM, LOT, SLIP, SUIT, UNIT
Level 4: DES
These identifiers may be used uniquely or combined. The identifiers and associated data cannot exceed the
size limitation of the data field. Some examples are shown below:
EXAMPLE 1: APT 2-B
EXAMPLE 2: BLDG 6 APT 2-B
EXAMPLE 3: FLR 6 SUIT 2-B
EXAMPLE 4: DES NEXT TO POOL
EXAMPLE 5: .25 MI NE OF MAIN ST (wireless example)
5.9 Updating the TN Database
The Wireless Carrier must provide data records for the E911 database as described in this tab. Data
records are validated for proper format and to ensure the address information is defined in the MSAG
database. The TN data record includes a "Function of Change" data field to indicate the type of processing
that should be performed for this record. Processing rules for some of the "Function of Change" data
values are described below:
Function of Change
Data Value:
Processing Rules:
I Insert this data record into the database. There must not be another data
record with the same TN (pANI) or calling number in the database or the
insert will fail.
C Change the corresponding record in the database. A data record must
already exist in the database with the same TN (pANI) or calling number.
The entire database record is replaced by the new data record, therefore
the incoming record must have all appropriate data fields populated.
D Delete the corresponding record in the database. A data record must
already exist in the database with the same TN (pANI) or calling number.
E Delete the corresponding record in the Error File. No processing is
performed against the E911 database.
Page 33