Internet based Emergency calls

9 downloads 120 Views 209KB Size Report
Internet Emergency Calling – RIPE 55. Agenda. ▫ How "legacy" Emergency Calling works. ▫ Issues with IP-based emergency calls. ▫ IETF architecture ...
Internet based Emergency calls Alexander Mayrhofer, nic.at GmbH RIPE 55 Oct 2007, Amsterdam

Agenda „ How

"legacy" Emergency Calling works „ Issues with IP-based emergency calls „ IETF architecture overview „ Who needs to do what? „ Regulation „ nic.at IP-based emergency calling projects

Internet Emergency Calling – RIPE 55

Emergency calls: "hello, world" Police 112: +43 1 YYY

112

112!! +43 1 XXX (Karlsplatz 1, Vienna)

„ „ „

+43 1 YYY

telephony telephony network network

"Phone "Phone book" book" +43 1 XXX: Karlsplatz 1

Detect emergency call Route to "best" Public Service Access Point PSAP: Answer call, figure location, send help

Internet Emergency Calling – RIPE 55

Mobile: It gets trickier Police 112: +43 1 YYY

112

112!! +43 699 XXX (whereever)

+43 1 YYY

mobile mobile telephony telephony network network

MSC MSC +43 699 XXX: Karlsplatz 1

„ „

+43 699: mobile

"Phone "Phone book" book"

call destination depends on handset location handset location not in the "phone book": requires cooperation of PSAP and operator

Internet Emergency Calling – RIPE 55

Like real estate: "It's all about location" „ caller

location required to find correct (best/closest/non-busy) PSAP „ caller location needed to send help „ "Plain"

telephony uses phone number / "phonebook" as key to location „ Mobile telephony uses access network element to access location info. „ (mobile) VoIP uses ? Internet Emergency Calling – RIPE 55

VoIP & emergency calls: OMG! sip:[email protected]

112 Amsterdam

local local ISP ISP

transit transit providers providers

VoIP VoIP SP SP Vienna

Ams Police

„ „

Vienna Police

VoIP SP needs location to properly route the call, but doesn't know it Access ISP does not notice the call, but knows the user's location

Internet Emergency Calling – RIPE 55

Problem: Seperation of Service and Access „ Classical

telephony is integrated

z Service

and Access from same provider z Easy to acquire location (even mobile) „ VoIP

(usually) seperates roles

z Access

is completely independent from

service z And they don't even know each other z They only have one thing in common: .... the user! Internet Emergency Calling – RIPE 55

"Other" problems „ World

wide mobility of (some) services

z requires

„ Services

worldwide standards

without phone numbers

z number

cannot be used as a lookup key z PSAP can't "call back" based on number „ It

might be more than just voice

z Instant

Messaging, Video, email z PSAPs usually don't even handle SMS z "VoIP" is not always "VoIP" (think Skype) Internet Emergency Calling – RIPE 55

IETF emergency services work „ Working

groups: ECRIT, GEOPRIV „ Location delivery (LCP) „ Service identification (service URN) „ Service discovery (LoST) „ Privacy, security (location by reference, location signing, location hiding) „ Introduction: z draft-ietf-ecrit-framework z draft-ietf-ecrit-phone-bcp

Internet Emergency Calling – RIPE 55

IETF architecture (ECRIT, GEOPRIV) „ client

acquires location from access net

z DHCP z LLDP z HELD

„ client

(HTTP Enabled Location Discovery)

(or service provider) uses LoST

z "Location

to Service Translation" – think of a pizza delivery service directory. z returns available services, PSAP contacts, dial strings „ emergency

call contains location

Internet Emergency Calling – RIPE 55

Step 1: Location Discovery Location

LS LS

Amsterdam

local local ISP ISP

transit transit providers providers

VoIP VoIP SP SP Vienna

Ams Police

„ Access

Vienna Police

network provides client with

location Internet Emergency Calling – RIPE 55

Step 1: Location Configuration „ Spatial

/ Civic

z "Karlsplatz

„ By

1, Vienna" vs. "48°N 16°E"

value / by reference

„ DHCP

– (RFC3825, RFC4776) „ LLDP-MED – ANSI/TIA 1057 z (LLDP:

"CDP reloaded")

„ HELD

(HTTP Enabled Location Delivery)

Internet Emergency Calling – RIPE 55

Step 2: Service Discovery dial: 112; urn:service:sos.police sip:[email protected]; tel:+31 xxx

LoST LoST

LS LS

Amsterdam

local local ISP ISP

X

Location transit

transit providers providers

VoIP VoIP SP SP Vienna

Ams Police

„ Client

Vienna Police

uses LoST to discover dialstring, contact addresses

Internet Emergency Calling – RIPE 55

Step 2: Location to Service „ „

Input data: Location Output data: z z z

„ „

available services (sos.police...) contact URIs (sip, tel, ...) service boundary (geographic object)

XML/HTTP based, query/response expected to have similar query rate and importance as DNS z

think of clients in cars, planes with frequent location updates

Internet Emergency Calling – RIPE 55

Step 3: Actual Emergency call dial: 112; urn:service:sos.police sip:[email protected]; tel:+31 xxx

Amsterdam

LoST LoST

LS LS

112!!

local local ISP ISP

X

transit transit Location providers providers

VoIP VoIP SP SP Vienna

Location

Ams Police

„ Client

Vienna Police

can place emergency call to best PSAP (directly, or via VoIP SP)

Internet Emergency Calling – RIPE 55

Regulation & Motivation „ „ „

Most EU countries require emergency calling for telephony services Depends on classification of VoIP service (PSTN interopability) Weak execution, though. ("... in the best way technically feasable") z

„

But – that might change (Sunday's news: "4 kittens die because Internet emergency call fails")

Standardization is progressing rapidly – industry is barely watching z z

did someone mumble "IPv6" or "DNSSEC"? changes cost money – government funding?

Internet Emergency Calling – RIPE 55

Who needs to do what? „

Access networks z z

„

VoIP SPs z z

„

Add emergency support to VoIP client software

PSAPs z z

„

Recognize, route, prioritize emergency calls trust relations (location info, LoST server)

Software Vendors z

„

location-enable their access lines much effort, low incentive ($$$, privacy)

publish their service coverage expand service beyond PSTN-based telephony

Someone (?) z z z

run authoritative LoST servers for a region define mapping of address elements to IETF standards coordinate between PSAPs, government, access providers

Internet Emergency Calling – RIPE 55

nic.at emergency services work „ Investigating

practical application of

standards z "location-enabled

access network in a box" (OpenWRT extension) z mapping Austrian address data to PIDF-LO (upcoming internet draft) z VoIP-enabling PSAPs „ Consulting z PSAPs,

ISPs, VoIP SPs

Internet Emergency Calling – RIPE 55

nic.at emergency services work „ Participating

in Austrian Emergency Services Forum z regulator,

telcos, PSAPs, government – very few ISPs and VoIP SPs! z PSAP service area data collection „ LoST

server prototype

z similar

to DNS in availability and performance reqs. – central function of local internet infrastructure z Funding? Internet Emergency Calling – RIPE 55

conclusions „ „ „

Standards are progressing quickly Implementation means effort Regulators are looking away z

„

„

„

how long? Until standards finished?

Suggestion to ISPs: Watch closely, and prepare. Audit systems from the perspective of customer location provisioning. Suggestion to VoIP SPs: Expect nice letters from the regulator if you don't route emergency calls properly. Watch related consultations. Location information is a big business. There might be added value to monetize.

Internet Emergency Calling – RIPE 55

Thank you! Alexander Mayrhofer nic.at GmbH [email protected] +43 1 5056416 34 Internet Emergency Calling – RIPE 55