xLoST Server

Selective IP 9-1-1 Routing at your fingertips

A Next Generation 9-1-1 Challenge

Providing NG9-1-1 call routing requires a location-to-service translation service that routes NG9-1-1 calls received with a PIDF-LO (civic or geodetic).

Challenges include:

• Relaying 9-1-1 communications from nomadic IP devices to the
  correct 9-1-1 jurisdiction
• Relaying a call at the PSAP on to the correct emergency service
  

Our Solution

microDATA’s xLoST (Location-to-ServiceTranslation) Server™ provides the query mechanism for multi-state, state or county public safety agencies to route 9-1-1 IP-based communications to the appropriate PSAP and emergency service. The xLoST™ web services perform a number of service requests centered on mapping locations and service Uniform Resource Names (URNs) to service Uniform Resource Locations (URLs).

xLoST Server™ meets NG9-1-1 challenges with these features:

• Ability to provide location information for NG9-1-1 call routing
• Identifies the correct ESZ from GIS map layers, so that the call may be routed to the appropriate emergency service agency
• Highly secure
• Validation of civic and geodetic locations
  

xLoST™ Server Features
Redundant web services support queries from any platform
Secure client authentication (Kerberos and username authentication)
Unlimited role-based queries (O-ESRP, I-ESRP, T-ESRP and PSAP)
Request for service results returned in milleseconds
Support for civic and geodetic profiles
Cached queries
Multi-processor and multi-threaded support
Load balancing supported
Queries supported: findService, listServicesByLocation, listServices, and getServiceBoundary
Recursion and iteration with other LoST servers on the ESInet
Support for ARC SDE, PGDB, Shapefile, and new file-based systems
Service boundaries returned by value or by reference
Runs on COTS equipment
Complies with IETF LoST standards
Support for errors, warnings, and redirects
HTTP underlying protocol transport (SOAP request)
Microsoft® Windows® Server 2003/2008, XP® SP2, and Vista®
IIS 6.0 or later
Microsoft® SQL Server™ 2005

Back to Top of page