Location Database (LDB)

 

Although some vendors suggest an E9-1-1 ALI database can be utilized in a NG9-1-1 environment, this approach is not recommended because ALI information is not regularly synchronized with GIS data and response times for ALI queries can potentially delay call deliveries. To overcome potential issues, NENA recommends the use of a Location Database (LDB) to ensure address information is pre-validated against the LVF and eliminate the need to query the ALI database to correctly route an emergency call. 

 

Because DDTI converts legacy content into the appropriate NG9-1-1 formats automatically, there is no need for service providers to alter their data or modify their SOI provisioning process. Our secure web interface provides insight into location records and facilitates data discrepancies resulting from failed LVF validations.

​

ECRF/LVF

​

The Emergency Call Routing Function (ECRF) and Location Validation Function (LVF) provide call routing and address verification capabilities in NG9-1-1 deployments.

 

DDTI's ECRF is a scalable, NENA and IETF-compliant LoST (Location-to-Service Translation) server that accepts LoST queries (containing a civic address or geodetic information, as well as the desired emergency service) and returns the appropriate PSAP call routing information based on stored GIS data.

 

As the ALI was validated against the MSAG in E9-1-1, the LVF validates that a civic address stored in the LDB can be uniquely located in the GIS database, can be properly associated with the correct PSAP and can provide first responders with a “dispatchable” location.

 

Because the ECRF and LVF play critical roles in the location-based routing of emergency calls, authoritative GIS data is consistently updated within DDTI’s DataManager product. DataManager ensures GIS data in the ECRF and LVF is current and accurate. GIS updates are validated and published within minutes of submission.

​

DataManager

 

To properly function, the ECRF/LVF requires up-to-date GIS data that defines emergency service area boundaries and civic location addresses. This information is typically maintained by local jurisdictions and provisioned to the DataManager product which makes this authoritative GIS data available to NG9-1-1 functional elements (ECRF/LVF, map displays, CAD, etc.).

 

DDTI’s DataManager fulfills this role by providing the following functionality:

​

• A quality control process that runs continuously and evaluates updates as they are incorporated into the core database. Detailed reporting is available for QC errors and historical data.

• A data publishing function that transforms, formats, and exports the data from the core database into the ECRF or other databases based on the client’s needs.

• A secure web interface for enabling administrators to configure quality control and data publishing rules, control users, permissions, and display options.

​

MSAG Conversion Service (MCS)

 

In the transition to NG9-1-1, there may be PSAPs that will continue to use legacy customer premise equipment (CPE) requiring MSAG formatted addresses. DDTI’s MSAG Conversion Service (MCS) protects the investment in legacy CPE by enabling it to function in an i3 environment without modification.

 

The MCS is a web service that bidirectionally converts between PIDF-LO civic locations and MSAG addresses in a NENA compliant XML format. The MCS is provisioned and maintained using the same mechanism used for the ECRF/LVF.