Next Generation 9-1-1 Project

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
  consumers 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 AM 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
phase4
phase3
12
Phase1 Determining Location

• Purpose
• To get emergency dial strings (Phase2)
• To resolve the correct PSAP URL (Phase3)
• To present the callers location on the call
  takers screen using mapping software (Phase4)

13
Phase1 Determining Location (contd)

• 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
DHCP for Location

• Mainly for stationary users
• We modified ISCs dhcpd to generate location
  information
• Use MAC address to get location information

15
CDP for Location

• Mainly for stationary and nomadic users
• Cisco Discovery Protocol (Layer2)
• Cisco switches broadcast switch/port ID
  periodically.
• A Switch covers a floor, a port leads to a jack
  in a room
• -gt 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
------- _ZGY1NTFlZDJkMDkxY2FkMTIxMWI2MzIzNjE1M2U0
OTY MIME-Version 1.0 Content-Type
application/pidfxml Content-Transfer-Encoding
8bit lt?xml version"1.0" encoding"ISO-8859-1"?gt
ltpresence xmlns"urnietfparamsxmlnspidf"
xmlnsgp"urnietfparamsxmlnspidfgeopriv10"
xmlnscl" urnietfparamsxmlnspidfgeopriv1
0civilLoc" xmlnsgml"urnopengisspecificati
ongmlschema-xsdfeaturev3.0"
entity"sipcalltaker_ny2_at_irt.cs.columbia.edu"gt
lttuple id"28185"gt ltstatusgt ltgpgeoprivgt
ltgplocation-infogt ltclcivilAddressgt
ltclcountrygtuslt/clcountrygt
ltclA1gtnylt/clA1gt ltclA2gtnew
yorklt/clA2gt ltclA3gtnew yorklt/clA3gt
ltclA6gtamsterdamlt/clA6gt
ltclHNOgt1214lt/clHNOgt lt/clcivilAddressgt
lt/gplocation-infogt ltgpmethodgtManuallt/gp
methodgt lt/gpgeoprivgt lt/statusgt
ltcontact priority"0.8"gtsipeddie_at_160.39.54.70506
0lt/contactgt lttimestampgt2005-09-26T155734-040
0lt/timestampgt lt/tuplegt lt/presencegt -------
_ZGY1NTFlZDJkMDkxY2FkMTIxMWI2MzIzNjE1M2U0OTY--
INVITE urnservicesos SIP/2.0
request line
To urnservicesos Call-ID 763782461_at_192.168.1.1
06 Via SIP/2.0/TCP 192.168.1.1064064rport Conte
nt-Type multipart/mixed boundary From
sipcaller_at_irt.cs.columbia.edu Contact
ltsipeddie_at_160.39.54.705060gt CSeq 1
INVITE Content-Length 1379
header fields
------ _ZGY1NTFlZDJkMDkxY2FkMTIxMWI2MzIzNjE1M2U0O
TY MIME-Version 1.0 content-Type
application/sdp Content-Transfer-Encoding
8bit v0 oeddie 1127764654 1127764654 IN IP4
192.168.1.106 sSIPC Call cIN IP4
160.39.54.70 t0 0 maudio 10000 RTP/AVP 0
3 mvideo 20000 RTP 31
SDP
PIDF-LO
18
Phase2 Identifying SOS

• Purpose
• For UA To send callers 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 (contd)

• Use Emergency Services URN(instead of emergency
  numbers)
• Service URN identifies a generic service, not a
  specific resource
• Examples of emergency services URN
• urnservicesos
• urnservicesos.ambulance
• urnservicesos.fire
• urnservicesos.police
• Can be used in request URI and To header.
• Will be resolved into PSAP URL in phase 3

20
Phase2 Identifying SOS (contd)

• 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 -gt urnservicesos

21
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

ltmappinggt ltresponse expires"2006-03-09T01
5333.396Z"gt ltservicegturnservicesoslt/s
ervicegt ltdisplayNamegtNew York City
PSAPlt/displayNamegt lturigtsippsap_ny_at_irt.c
s.columbia.edult/urigt ltcivicMatchgt
ltgplocation-infogt
ltclcivicAddressgt
ltclcountrygtUSlt/clcountrygt
ltclA1gtNYlt/clA1gt ltclA3gtNew
Yorklt/clA3gt ltclA6gtAmsterdamlt/clA
6gt ltclHNOgt1214lt/clHNOgt
lt/clcivicAddressgt
lt/gplocation-infogt lt/civicMatchgt
ltdialstringgt911lt/dialstringgt
lt/responsegt lt/mappinggt
ltmappinggt ltrequestgt
ltoperationgtrecurselt/operationgt
ltservicegturnservicesoslt/servicegt
ltgplocation-infogt ltclcivicAddressgt
ltclcountrygtUSlt/clcountrygt
ltclA1gtNYlt/clA1gt ltclA3gtNew
Yorklt/clA3gt ltclA6gtAmsterdamlt/clA6gt
ltclHNOgt1214lt/clHNOgt
lt/clcivicAddressgt lt/gplocation-infogt
lt/requestgt lt/mappinggt
request
response
LoST Server
23
Phase4 Call Presentation in PSAP
24
Calltakers Screen

• SIPc as SIP User Agent
• Location Mapping software to display callers
  location
• Geolynx
• Google Maps

25
Web Interface

• Manage PSAP systems
• Show call logs, details, incident information and
  statistics

26
All Together Now
LoST Server
SOS caller
SIP proxy
call taker
27
References

• 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-requi
  rements-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

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