1 / 5

NENA geopriv Requirements

Ensure the integrity and accuracy of location information used for emergency calls to prevent dispatching responders incorrectly. Address the challenges of multiple locations, resolve ambiguities, and establish guidelines for handling default and accurate locations. Introduce new fields for postal and legal communities, capture the date/time of location determination, enhance information on confidence and uncertainty, define additional "placetypes", and include relevant associated information. This document aims to recharter geopriv and propose accepted solutions for these issues.

grimshaw
Download Presentation

NENA geopriv Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NENA geopriv Requirements draft-rosen-nena-geopriv-requirements-00 Brian Rosen

  2. Integrity of Location Information • When location is forged, and used for an emergency calls, responders are dispatched incorrectly, which can cause harm • Location may go through multiple protocols and representations (e.g. DHCP, then SIP) • Need end to end signature over the location

  3. Multiple Locations • When multiple locations are given in a PIDF-LO, or multiple PIDF-LOs are transported in a message, what does that mean? • For emergency calls, we can’t have unresolvable ambiguity; we route on ONE location • BUT sometimes there is a default (more coarse grained) location, PLUS a more accurate one (tower location vs handset location). Need to deal with that. • Need rules/guidelines/fields to figure out how to do this

  4. Other changes needed • Need “Postal Community” and “Legal” Community fields • Need Date/Time location was determined (when PIDF-LO was created may be useful for integrity protection) • Confidence and Uncertainty is not enough information. Need more work • Need more “Placetypes” (?SIMPLE?) • Need other information associated with location (or caller)

  5. What do we want to do? • Recharter geopriv to deal with these issues • Turn this into one or more requirement/solution documents that get accepted as WG items

More Related