1 / 19

A Proposal for an Emergency Services Pilot Project

Transition from PSTN to IP-based networks for enhanced emergency communication. Benefits include better media, data transfer, and cost savings. The pilot project aims to build a demo VoIP emergency service architecture involving stakeholders from various sectors.

tsinger
Download Presentation

A Proposal for an Emergency Services Pilot Project

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. A Proposal for an Emergency Services Pilot Project Hannes Tschofenig

  2. Acknowledgements • This slide set is based on work done in the IETF ECRIT and IETF GEOPRIV working group. Slides by Prof. Henning Schulzrinne (Columbia University) are reused.

  3. Next Generation Emergency ServicesState-of-the-Art • Transition from PSTN emergency services infrastructure to IP-based networks and IP-based protocols • Citizen-to-Authority: ~20 SDOs working on this subject (including IETF ECRIT and IETF GEOPRIV) • Authority-to-Authority: Preferential Treatment of communication by some authorities (e.g., IETF IEPREP, ITU-T)Keywords: Multi-Level Precedence and Preemption (MLPP), Government Emergency Telecommunications Service (GETS) • Authority-to-Citizen: Tsunami warning, work in early stages (e.g., ITU-T, OGC -- GeoRSS)

  4. Next Generation Emergency Services Benefits • Enhanced media (voice, video, instant messaging, better codecs) • Device and access network independence • Ability to transfer data with emergency calls • Inherits a number of VoIP communication features • Lower cost • More flexibility regarding the access and distribution of location information • More robust architecture

  5. Location Routing PSTN Prototype Architecture

  6. Beyond Initial Emergency Services ArchitectureOutlook • Growth of sensor networks • Example: Shotspotter - to plot the location of the sounds of gunfire, CitySense – tracking weather and air pollution, sensors to track abnormal behavior at airports, personal sensors) • Ability to transfer call and data anywhere • Example: Coordination of first responders • Allow sharing of information • Information about hospitals, accidents and infrastructure • Examples: availability of hospital space (e.g., OASIS Common Alerting Protocol (CAP), EDXL Resource Messaging Standard (EDXL-RM)), building plans, CityGML – definition of city objects (www.citygml.org), TransXML – exchange of transportation data (http://www.transxml.org), street maps http://www.ist-highway.org/ • Identity management, Authorization & Privacy • To deal with secure sharing of information • Integration of all emergency service communication flavors

  7. Pilot Project • Build demo VoIP emergency service architecture by • Involving PSAP operators, network operators (universities, WLAN hotspots, etc.), government • Interact with governments of other countries (for roaming scenarios) • Stakeholders: • Users who summon for help • End Host Equipment: Open Source Software, Device Manufacturers • Network Operators: Provide location information • Government: Regulatory aspects, coordination between jurisdictions, make PSAP boundary data available; • PSAP Provider: Operate PSAP and LoST infrastructure • VoIP Provider: Offer SIP infrastructure and Customer Identity Info available • Use initial prototype as a starting point for further extensions

  8. References • SDO Emergency Services Workshop 2006 & 2007 • http://www.emergency-services-coordination.info/ • IETF ECRIT Working Group • http://www.ietf.org/html.charters/ecrit-charter.html • IETF GEOPRIV Working Group • http://www.ietf.org/html.charters/geopriv-charter.html

  9. Backup Slides

  10. Location is important! Caller in NY Caller in NJ

  11. Location Routing PSTN NG9-1-1 Call Routing

  12. Caller’s location Service provider (PSAP URL) + Service identifier (urn:service:sos) Routing Using LoST • LoST stands for Location-to-Service Translation • Work in progress at IETF ECRIT WG + Emergency Dial String

  13. Call Routing ? ? Location + Service ID NY PSAP

  14. Location Routing PSTN IP-based PSAP PSAP operator can communicate with caller using multimedia

  15. Example: Inviting NYPD into an on-going session CALL NYPD Caller ID & Location

  16. Example: Language-based Call Distribution ? ? ESPANOL

  17. Example: Callback INVITE

  18. Example: Call Queue BUSY BUSY Play Announcement

  19. Example: Call Overflow BUSY BUSY FULL Even the queue is full! Redirect call to a backup PSAP

More Related