1 / 19

Status and Development of VoIP based emergency calls

Status and Development of VoIP based emergency calls. Alexander Mayrhofer, nic.at GmbH The 1st European Security and Safety Summit Brussels, June 2007. Agenda. Motivation for a new emergency call services architecture IETF architecture overview

chanel
Download Presentation

Status and Development of VoIP based emergency calls

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. Status and Development of VoIP based emergency calls Alexander Mayrhofer, nic.at GmbH The 1st European Security and Safety Summit Brussels, June 2007

  2. Agenda • Motivation for a new emergency call services architecture • IETF architecture overview • nic.at/IPA emergency call services registry project in Austria

  3. About nic.at/IPA • IPA: Internet Foundation Austria • fostering the develoment of Internet in Austria • owner of nic.at – country code domain registry for .at • enum.at – ENUM registry for +43 • neutral provider critical, internet based registry infrastructure – emergency services registry • Alexander Mayrhofer: team leader research/development nic.at

  4. Motivation for a new emergency call architecture • Overview of current model • New communication means (eg VoIP) break this model • seperation of service and access • mobility (number <-> location relation) • no phone numbers at all • New "media" (video, chat, IM)

  5. call routing requirements • Routing the call to the right PSAP • caller location • local policy • Providing the PSAP with caller information • location • callback information (number)

  6. current call routing (Austria) • Routing to the right PSAP • number -> location -> PSAP contact • number -> area code -> PSAP contact • cell id -> PSAP contact • Providing PSAP with info • number: CLI display forced • location: number directory reverse lookup • or out of band location request

  7. "Conventional" communications • Closed, trusted network • trusted identities: numbers • Access and service provided by one party (or tightly integrated) • location retrieval relatively easy • Well known set of applications • mostly telephony

  8. VoIP mobility example ? +43 59966 112 VoIP SP Internet (various providers) Access provider Brussels Vienna, Austria Brussels Police Vienna Police

  9. "internet based" communications • Open, untrusted network • requires additional security/trust layers • Service and Access provided by different providers • location retrieval more difficult • Vast array of applications • even "VoIP" is not always the same

  10. internet emergency service issues • access network knows the location, service provider needs it • and they don't know of each other • service not limited to one access network • Numbers can't always be used as key for information • Most services don't use numbers at all • Trust relation, security, authenticity

  11. 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)

  12. IETF architecture overview I • Access network provides location to client • civic (street, number, postal code, city...) • geodetic (latitude, longitude, elevation) • By value / by reference

  13. Location configuration lat,lon .. LS VoIP SP Internet (various providers) Access provider Brussels Vienna, Austria Brussels Police Vienna Police

  14. IETF architecture overview II • Client queries for PSAP contacts • using location information received • uses "Location to Service Translation" (LoST) servers • either before the emergency call, or when client is started (if it is not moved) • Client knows PSAP contacts for services based on his location

  15. Location to Service Translation Q: sos.police for lat/lon? A: brussels.police@example.com LoST LS VoIP SP Internet (various providers) Access provider Vienna, Austria Brussels Police Vienna Police

  16. Current situation in Austria • Emergency numbers now officially assigned • Assignees are required to provide information about desired routing • (Telephony) Network Service Providers are required to provide information about implemented routing

  17. IPA/nic.at Emergency Services Project • Architecture requires a shared, up-to-date reference database of service areas and contact data for all short codes • Does currently not exist in Austria! • Motivation for nic.at: critical, registry based service to be provided by a neutral, trusted party – vast experience. • Important for the development of new communication means

  18. Scope of project • Practical application of those standards under development • provide a prototypic implementation of a next generation emergency call routing infrastructure • Location-enabling access networks • collecting and providing call routing data (registry) – LoST server • enabling PSAPs for new services

  19. Questions & contact info Questions? Alexander Mayrhofer nic.at GmbH Karlsplatz 1/2/9 A-1010 Wien mailto:alexander.mayrhofer@nic.at - +43 1 5056416 34

More Related