1 / 27

The Next Generation 9-1-1 Proof-of-Concept System

Jong Yul Kim Wonsang Song Henning Schulzrinne. The Next Generation 9-1-1 Proof-of-Concept System. Talk Outline. Background why is emergency calling difficult for VoIP? numbers, call routing, … High level proof-of-concept architecture Location configuration Call routing Lessons learned.

flavia-dorsey
Download Presentation

The Next Generation 9-1-1 Proof-of-Concept System

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. Jong Yul Kim Wonsang Song Henning Schulzrinne The Next Generation 9-1-1 Proof-of-Concept System SIP 2009 (Paris, January 2009)

  2. Talk Outline • Background • why is emergency calling difficult for VoIP? • numbers, call routing, … • High level proof-of-concept architecture • Location configuration • Call routing • Lessons learned

  3. Modes of emergency communications emergency call information “I-am-alive” dispatch emergency alert (“inverse 911”) civic coordination

  4. Background on 9-1-1 • Established in Feb. 1968 • 1970s: selective call routing • late 1990s: 93% of population/96% of area covered by 9-1-1 • 95% of 9-1-1 is Enhanced 9-1-1 • US and Canada • Roughly 200 mio. calls a year (6 calls/second) • 1/3 wireless • 6146 PSAPs in 3135 counties • most are small (2-6 call takers) • 83.1% of population have some Phase II (April 2007) • “12-15 million households will be using VoIP as either primary or secondary line by end of 2008” (NENA) http://www.nena.org/

  5. Local Switch Automatic Number Identification Automatic Location Identification Collaboration between local phone providers and local public safety agencies

  6. What makes VoIP 112/911 hard?

  7. Emergency numbers • Each country and region has their own • subject to change • Want to enable • traveler to use familiar home number • good samaritan to pick up cell phone • Some 3/4-digit numbers are used for non-emergency purposes (e.g., directory assistance) Emergency number

  8. Service URN • Idea: Identifiers to denote emergency calls • and other generic (communication) services • Described in IETF ECRIT RFC 5031 • Emergency service identifiers: sos General emergency services sos.animal-control Animal control sos.fire Fire service sos.gas Gas leaks and gas emergencies sos.marine Maritime search and rescue sos.mountain Mountain rescue sos.physician Physician referral service sos.poison Poison control center sos.police Police, law enforcement

  9. “EMERGENCY HELP. Anytime, anywhere, any device.”™ National Emergency Number Association (NENA) IETF ECRIT Working Group IETF GEOPRIV Working Group NENA High level requirements Use of multimedia Data delivery and sharing Recording and incident details Call taker user interface Technical standards System architecture Behavior of components Format of location objects Technical standards IETF ECRIT Working Group IETF GEOPRIV Working Group The NG9-1-1 POC System

  10. The POC system is deployed in 5 real PSAPs and 3 labs across the USA. PSAP: Public Safety Answering Point (=Emergency call center) King County, WA Bozeman, MT St. Paul, MN Rochester, NY Columbia Univ. Lab Fort Wayne, IN BAH Lab TAMU Lab

  11. POC system is divided into two networks Emergency Services Network (ESN) 9-1-1 SIP-based network of PSAPs managed by the emergency authorities Access Network Network used by emergency caller to ask for help Examples: PSTN, Cellular, Residential VoIP Role 1. Determine location of caller 2. Route call to ESN

  12. ① ② • Why is location important? • Send help to the site of emergency • Route call to the correct destination • How do I send my location? • Sent along with SIP INVITE • Formatted as PIDF-LOXML object GPS LLDP-MED DHCP Cell Tower Manual Entry Skyhook Wireless

  13. Location determination options

  14. Caller’s location Service provider (PSAP URL) + Service identifier (urn:service:sos) LoST • LoST = Location-to-Service Translation • LoST lets you find a PSAP • RFC 5222 from IETF ECRIT WG + Emergency Dial String

  15. LoST: Location-to-URL Mapping VSP1 cluster serving VSP1 replicate root information cluster serves VSP2 123 Broad Ave Leonia Bergen County NJ US LoST root nodes NJ US NY US sip:psap@leonianj.gov search referral Bergen County NJ US Leonia NJ US

  16. LoST Architecture G tree guide G G G broadcast (gossip) T1: .us T2: .de G resolver T2 (.de) seeker 313 Westview Leonia, NJ US T3 (.dk) T1 (.us) Leonia, NJ  sip:psap@leonianj.gov

  17. LoST: Query example • Uses HTTP or HTTPS <findService xmlns="urn:…:lost1” recursive="true" serviceBoundary="value"> <location profile="basic-civic"> <civicAddress> <country>Germany</country> <A1>Bavaria</A1> <A3>Munich</A3> <A6>Neu Perlach</A6> <HNO>96</HNO> </civicAddress> </location> <service>urn:service:sos.police</service> </findService>

  18. LoST “Find Service” response/warning example <findServiceResponse xmlns="urn:ietf:params:xml:ns:lost1"> <mapping expires=“1990-12-31T23:59:60Z” lastUpdated=“2006-11-01T01:00:00Z”> <displayName xml:lang="de">München Polizei-Abteilung</displayName> <service>urn:service:sos.police</service> <serviceBoundary profile=”civic”> <civicAddress xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"> <country>Germany</country> <A1>Bavaria</A1><A3>Munich</A3><PC>81675</PC> </civicAddress> </serviceBoundary> <uri>sip:munich-police@example.com</uri> <serviceNumber>110</serviceNumber> </mapping> <path> <via source=“lost:esgw.uber-110.de.example”/> <via source=“lost:polizei.munchen.de.example”> </path> </findServiceResponse>

  19. Cellular LoST 9- 9-1- 9-1-1 9-1-1 SIP RTP Access Network

  20. SMS LoST 9- 9-1- 9-1-1 9-1-1 “Bank robbery!” SIP S Access Network

  21. Telematics LoST 9- 9-1- 9-1-1 9-1-1 SIP RTP Access Network Crash Data

  22. All Busy LoST 9- 9-1- 9-1-1 9-1-1 SIP RTP “All call takers are busy…” Access Network

  23. Calltaker screen • Columbia SIPc as SIP UA • Mapping software to display caller’s location • Geolynx • Google Maps

  24. NG911 trial: Lessons learned • Tested NG911 prototype in 3 PSAPs in TX and VA • Surprise: PSAP is really a conferencing system • LanguageLine, first responders, … • Surprise: no uniform incident description • every jurisdiction uses their own variation and level of detail • What is desirable behavior • rather than current behavior • e.g., for transfer, overflow • Need to integrate call taker management • presence (availability) • a specialized call center • Special requirements: partial mute • not typically supported on conference servers

  25. Challenges for NG911 • Technically, much simpler than E911 Phase II • hopefully, cheaper, too • but security challenges: location and identity verification • co-existence between E911 and NG911 • integrating external data (e.g., OnStar) -- from silo to NG911 SOA • Logistical challenges • deployment of new infrastructure • location and LoST servers • Legal and regulatory challenges • will ISPs give out location information to VSPs or customers? • liability for misrouted calls?

  26. mDNS? Final Comments • We are beginning to understand what an emergency response system should look like • Lots of interesting network problems in emergency communication systems • Geographic Location of network devices • “Call setup time (dialing of last digit to ring at the PSAP), under expected peak load shall be less than 2 seconds.” • Reliable communications in large scale disasters

More Related