Nemergent Blog.

First release of Nemergent NG112 Location Information Server

Location information is crucial in the event of an emergency. NG112 architecture includes a Location Information Server (LIS) to manage this information. In view of this necessity, the Nemergent team has already made an open-source LIS available in our repository.

According to EENA NG112 Long-Term Definition, a LIS supplies the location of the users who call the emergency services. This location can be sent in the form of a PIDF-LO (location by value) or a location URI (location by reference). The LIS also provides a “dereference” service for a location URI. Other elements in the network can make use of this service to obtain the location value as a PIDF-LO. A LIS may be a database, or may be a protocol interworking function to an access network specific protocol. The following picture depicts the integration of the LIS node in the NG112 architecture.

NG112-LIS

The Nemergent LIS is built upon SIP/HTTP capable multi-purpose Kamailio server, which is in fact responsible for providing both interfaces and presence+location information. Kamailio builtin MySQL backend will be used for permanent data storage.

More information about the Nemergent NG112 LIS available here.

Please, visit our repository to access the source code of the NG112 LIS Server.

Reference standards:

  • EENA Next Generation 112 Long-Term Defnition (NG112 LTD)
  • RFC 5491: GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations.
  • RFC 5985: HTTP-Enabled Location Delivery (HELD)
  • RFC 6155: Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
  • RFC 6753: A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)
  • RFC 3856: Presence Event Package for the Session Initiation Protocol (SIP)
  • RFC 6447: Filtering Location Notifications in the Session Initiation Protocol (SIP)
  • RFC 6446: Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control
  • RFC 6915: Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)
  • RFC 5139: Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)
  • RFC 4119: A Presence-Based GEOPRIV Location Object Format

June 29th, 2016

NEW: Interested in commercial MCPTT products and services? check Nemergent Solutions