1 / 31

Next Generation 9-1-1 Project

Next Generation 9-1-1 Project. Jong Yul Kim, Wonsang Song, and Henning Schulzrinne. Overview. Project Introduction Architecture and implementation References Demo. Growth of VoIP Subscribers. Global Subscribers 16 million in 2005 62% year-over-year subscriber growth rate in 2005

gusty
Télécharger la présentation

Next Generation 9-1-1 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. Next Generation 9-1-1 Project Jong Yul Kim, Wonsang Song, and Henning Schulzrinne

  2. Overview • Project Introduction • Architecture and implementation • References • Demo

  3. Growth of VoIP Subscribers • Global Subscribers • 16 million in 2005 • 62% year-over-year subscriber growth rate in 2005 • 55 million by 2009 Numbers from instat.com Released on Jan. 31, 2006

  4. But there were problems… • VoIP service did not connect to 911; • VoIP service rang to the administrative line of the public safety answering point (PSAP), which is not often staffed after hours, and is usually not staffed by trained 911 operators; • VoIP service rang to the correct line of the PSAP, but did not automatically include the consumer’s phone number and/or location information. • Consumer must provide certain information (such as location information) in order for the VoIP provider to set up 911 service, but failed to do so • Consumer moved VoIP service to another location (the phone number can be used anywhere the customer has a broadband connection) but the VoIP service did not reflect the new address; • VoIP service did not work during a power outage; • VoIP service did not work when the broadband connection (cable modem or DSL) went down or was congested. Taken from http://www.fcc.gov/cgb/consumerfacts/voip911.html

  5. Three Fundamental Problems • Where is the caller? • To which PSAP should the call go to? • How to identify the emergency call? Problems 2 and 3 arise from problem 1.

  6. Project Goals • Develop a prototype system that routes emergency calls over SIP based VoIP networks. • Implement requirements for IP-based PSAP • Provide opportunities to enhance 911 system: • Multimedia (audio, video, text) • Data delivery (floor plan, medical information) • Delivering video (CPR how-to) • Load balancing and redundancy • Location delivery (location with forwarded, transferred calls)

  7. A Collaborative Effort • Funding • U.S. Department of Commerce • National Telecommunications and Information Administration (NTIA) • Requirements • National Emergency Number Association (NENA) • Software Development • Columbia University • Deployment and Testing • Texas A&M University • Standardization • IETF ECRIT, GEOPRIV WG • Contributions • States of Texas and Virginia 911 offices • Corporations like Cisco, Nortel, MapInfo, etc.

  8. The Big Picture from NENA

  9. Our Much Simpler Picture 

  10. Four Phases of Emergency Calls Phase 4 Phase 1 Phase 2 Phase 3

  11. System Components phase1 phase1 phase2 phase3 phase3 phase4

  12. Phase1: Determining Location • Purpose • To get emergency dial strings (Phase2) • To resolve the correct PSAP URL (Phase3) • To present the caller’s location on the call taker’s screen using mapping software (Phase4)

  13. Phase1: Determining Location (cont’d) • Problem • User can be stationary, nomadic or mobile • Solution • Apply different methods for different situations • DHCP, CDP (LLDP-MED), SkyHook (Wireless AP Location Database), GPS, and Manual Entry • The result is either civic address or geospatial coordinates. • Location will be included in the body of the INVITE request as PIDF-LO object.

  14. DHCPINFORM [MAC=00:11:20:9d:a0:03] request or response DHCPACK [option=0:US:1:NY:2:NEW YORK: 3:NEW YORK:6:AMSTERDAM:19:1214] DHCP Server DHCP for Location • Mainly for stationary users • We modified ISC’s dhcpd to generate location information • Use MAC address to get location information

  15. LLDP-MED for Location • Mainly for stationary and nomadic users • Link Layer Discovery Protocol – Media Endpoint Discovery(Layer2) • Switch broadcasts location data periodically. • A Switch covers a floor, a port leads to a jack in a room -> room-level accuracy

  16. SkyHook for Location • Mainly for nomadic, mobile users • Wireless device receives signals from Wi-Fi sites in range • Skyhook compares signals to its database of geographically known locations • Location data is used to direct safety services Taken from http://www.skyhookwireless.com

  17. Location Info inside a SIP message ------- =_ZGY1NTFlZDJkMDkxY2FkMTIxMWI2MzIzNjE1M2U0OTY= MIME-Version: 1.0 Content-Type: application/pidf+xml Content-Transfer-Encoding: 8bit <?xml version="1.0" encoding="ISO-8859-1"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:cl=" urn:ietf:params:xml:ns:pidf:geopriv10:civilLoc" xmlns:gml="urn:opengis:specification:gml:schema-xsd:feature:v3.0" entity="sip:calltaker_ny2@irt.cs.columbia.edu"> <tuple id="28185"> <status> <gp:geopriv> <gp:location-info> <cl:civilAddress> <cl:country>us</cl:country> <cl:A1>ny</cl:A1> <cl:A2>new york</cl:A2> <cl:A3>new york</cl:A3> <cl:A6>amsterdam</cl:A6> <cl:HNO>1214</cl:HNO> </cl:civilAddress> </gp:location-info> <gp:method>Manual</gp:method> </gp:geopriv> </status> <contact priority="0.8">sip:eddie@160.39.54.70:5060</contact> <timestamp>2005-09-26T15:57:34-04:00</timestamp> </tuple> </presence> ------- =_ZGY1NTFlZDJkMDkxY2FkMTIxMWI2MzIzNjE1M2U0OTY=-- INVITE urn:service:sos SIP/2.0 request line To: urn:service:sos Call-ID: 763782461@192.168.1.106 Via: SIP/2.0/TCP 192.168.1.106:4064;rport Content-Type: multipart/mixed; boundary From: sip:caller@irt.cs.columbia.edu Contact: <sip:eddie@160.39.54.70:5060> CSeq: 1 INVITE Content-Length: 1379 header fields ------ =_ZGY1NTFlZDJkMDkxY2FkMTIxMWI2MzIzNjE1M2U0OTY= MIME-Version: 1.0 content-Type: application/sdp Content-Transfer-Encoding: 8bit v=0 o=eddie 1127764654 1127764654 IN IP4 192.168.1.106 s=SIPC Call c=IN IP4 160.39.54.70 t=0 0 m=audio 10000 RTP/AVP 0 3 m=video 20000 RTP 31 SDP PIDF-LO

  18. Phase2: Identifying SOS • Purpose • For UA : To send caller’s location information • For Proxies: To handle the emergency call specially • Problem • Different emergency dial strings • different in countries (e.g., 911 for North America, 112 for Europe) • some countries uses separate numbers for ambulance/police/fire • Required to support both home and visited emergency dial strings • e.g., for an American traveler who is visiting Europe, both 911 and 112 should be recognized as emergency

  19. Phase2: Identifying SOS (cont’d) • Use Emergency Services URN(instead of emergency numbers) • Service URNidentifies a generic service, not a specific resource • Examples of emergency services URN: • urn:service:sos • urn:service:sos.ambulance • urn:service:sos.fire • urn:service:sos.police • Can be used in request URI and To header. • Will be resolved into PSAP URL in phase3

  20. Phase2: Identifying SOS (cont’d) • What if a user dials an emergency number? • User can set his/her home country through configuration. • In initial time, UA gets the home emergency dial strings using mapping protocols. • Whenever current location is changed, UA gets the visited emergency dial strings using mapping protocols. • UA keeps all emergency dial strings in the local dial plans e.g., [911 -> urn:service:sos]

  21. Caller’s location Service provider (PSAP URL) + Service identifier (urn:service:sos) Phase3: Routing to Correct PSAP • Which PSAP should the call go to? • Usually to the PSAP that covers the area • Sometimes to a backup PSAP • If no location, then ‘default’ PSAP • PSAP determination • mapping problem: • Work in progress for standardization of LoST ( LoST = A Location-to-Service Translation Protocol )

  22. LoST(Location-to-Service Translation) • Translates a service identifier and location information to {PSAP URL & emergency dial-string} • Supports both civic and geo location information • Uses web service (SOAP base) as underlying protocol <mapping> <response expires="2006-03-09T01:53:33.396Z"> <service>urn:service:sos</service> <displayName>New York City PSAP</displayName> <uri>sip:psap_ny@irt.cs.columbia.edu</uri> <civicMatch> <gp:location-info> <cl:civicAddress> <cl:country>US</cl:country> <cl:A1>NY</cl:A1> <cl:A3>New York</cl:A3> <cl:A6>Amsterdam</cl:A6> <cl:HNO>1214</cl:HNO> </cl:civicAddress> </gp:location-info> </civicMatch> <dialstring>911</dialstring> </response> </mapping> <mapping> <request> <operation>recurse</operation> <service>urn:service:sos</service> <gp:location-info> <cl:civicAddress> <cl:country>US</cl:country> <cl:A1>NY</cl:A1> <cl:A3>New York</cl:A3> <cl:A6>Amsterdam</cl:A6> <cl:HNO>1214</cl:HNO> </cl:civicAddress> </gp:location-info> </request> </mapping> request response LoST Server

  23. (8) join conference join conference (5) (6) REFER police to conference (7) INVITE to conference (4) INVITE to conference (3) select available call taker (2) create conference (1) psap@domain w/location Phase4: Call Presentation in PSAP

  24. Calltaker’s Screen • SIPc as SIP User Agent • Location Mapping software to display caller’s location • Geolynx • Google Maps

  25. Web Interface • Manage PSAP systems • Show call logs, details, incident information and statistics

  26. (2) Location + Service Identifier (1) Location (3) PSAP URL + emergencydial-string (4) INVITE PSAP URL To: urn:service:sos <Location> INVITE PSAP URL To: urn:service:sos <Location> (6) (5) dial emergency dial-string or push emergency button All Together Now LoST Server SOS caller SIP proxy call taker

  27. Related Websites ng911.tamu.edu www.nena.org www.ietf-ecrit.org Standards and Internet Drafts SIP: Session initiation protocol, RFC 3261 Requirements for Emergency Context Resolution with Internet Technologies, draft-ietf-ecrit-requirements-04 Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information, draft-ietf-geopriv-dhcp-civil-07 Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information, RFC 3825 A Presence-based GEOPRIV Location Object Format, RFC 4119 A Uniform Resource Name (URN) for Services, draft-ietf-ecrit-service-urn-01 LoST: A Location-to-Service Translation Protocol, draft-hardie-ecrit-lost-00 Best current practices for third party call control (3pcc) in the session initiation protocol (SIP), RFC 3725 References

  28. Thank you! Please join us for a demo of the prototype system

More Related