Ernst Langmantel Technical Director, Austrian Regulatory Authority for Broadcasting and Telecommunication (RTR GmbH) The opinions expressed in this presentation

Ernst LangmantelTechnical Director, Austrian Regulatory Authority for Broadcasting and Telecommunication (RTR GmbH)

The opinions expressed in this presentation are the personal views of the author and do not prejudge decisions of the Austrian regulatory authority

Internet / Next Generation Emergency Calls

ITU Workshop "Future of Voice", 15./16.01.2007, Geneva Seite 2

Contents

Basic Service Architecture Elements Legacy networks (PSTN/ISDN, GSM/UMTS)

Architecture – Outgoing Calls – Emergency Calls

Internet Architecture – Outgoing Calls – Emergency Calls

NGN (ITU/ETSI) Architecture – Outgoing Calls – Emergency Calls

IETF/Internet and ITU/ETSI NGN – Synergies ?


Basic Service Architecture Elements


Transport

Network Edge[Terminals, Application servers]Network of Networks

Service Connectivity,Signalling

Terminal

Terminal

Networks and Terminals


Transport



Terminal

Media Streams / User Data Path

Terminal


Transport



Terminal

Signalling

Terminal


Legacy networks (PSTN/ISDN, GSM/UMTS)Architecture – Outgoing Calls – Emergency Calls


Transport


PSTN /ISDN, GSM/UMTS – Architecture [simplified]

Without service interconnection (service interoperability)between networks the service area is restricted to area of individual networks

Service control andphysical routing pointscombined in “Telephone Exchanges”


g

Caller / Called in Home Network


HH

PSTN /ISDN, GSM/UMTS – Outgoing/ Emergency Call [simplified]

In case of emergency calls national emergency routing information is retrieved locally in the telephone exchange or from a national data base

Transport


HService Connectivity

VH

Caller in Visited Network

GSM/UMTS – Roaming Outgoing /Emergency Calls [simplified]

Call control in visited networkIn case of emergency calls national emergency routing information is retrieved locally in the telephone exchange or from a national data base

PSAP

Transport


Internet Architecture – Outgoing Calls – Emergency Calls


Transport(IP-Packets)


Internet Services - Architecture [simplified]

ONLY IP-Interoperability necessary for GLOBAL service area !

Service control (call control) at the network edge. NO CONTROL of network transport by service control



Internet VoIP - Outgoing Call [simplified]

Global service area without service interoperability between providers

“Home Position”

IP-interoperability between networks




Internet VoIP – Outgoing Call [simplified]

IP-Interoperability between networks

Different Service/Application ProvidersInteroperability between services/ applications of network edge, not relevant for networks




Internet VoIP - Emergency Call Solution (ECRIT) [simplified]

HH

LoST

fully distributed international emergency routing data

base

PSAP

Location &

type of emergency

PSAP UrI

Where do I get PSAP Url in visited

country?

Type of emergency

& location



LoST Functionality (Location-to-Service Translation Protocol)

Satisfies the requirements (draft-ietf-ecrit-requirements) for mapping protocols

Civic as well as geospatial queries civic address validation

Recursive and iterative resolution Fully distributed and hierarchical deployment

can be split by any geographic or civic boundary same civic region can span multiple LoST servers

Indicates errors in civic location data debugging but provides best-effort resolution

Supports overlapping service regions

Source: SDO Emergency Services Coordination Workshop (5./6.10.2006, Columbia University, New York), A Location-to-Service Translation Protocol (LoST)- Mapping Protocol Architecture, Ted Hardie, Andrew Newton, Henning Schulzrinne, Hannes Tschofenig


LoST Conclusions Mapping is core component of emergency calling problem LoST fully international and distributed

tries to avoid “who runs the root” problem optimized for efficient use in mobile end systems

Source: SDO Emergency Services Coordination Workshop (5./6.10.2006, Columbia University, New York), A Location-to-Service Translation Protocol (LoST)- Mapping Protocol Architecture, Ted Hardie, Andrew Newton, Henning Schulzrinne, Hannes Tschofenig


NGN (ITU/ETSI)Architecture – Outgoing Calls – Emergency Calls


Physical Transport (IP Packets)


NGN – Architecture [simplified]

Service control and physical routing in DIFFERENT network elements but fierce control of transport resources by service control within individual networks.

Without service interconnection (service interoperability) the service area is restricted to area of individual networks(same as in legacy circuit switched networks)


NGN (IMS) - Outgoing Call [simplified]

Roaming User (Exception for Emergency Calls!)

Physical Transport(IP-Packets)


VH

Call control for roaming user from “Home Position” (Internet-like) BUT via visited network

Caller in visited network



NGN (IMS) - Emergency Call NGN [simplified]

Roaming User


V

Home Position lacks knowledge of caller location and national emergency routing in visited country

PSAP





VH

In case of emergency calls also in NGN (like in GSM/UMTS) invocation of call control in visted network including access to national emergency routing information to PSAP.

PSAP

NGN (IMS) - Emergency Call NGN [simplified]

Roaming User



IETF/Internet and ITU/ETSI NGN – Synergies ?


One “Emergency (IP-)World” ? A lot of synergies regarding ITU/ETSI NGN and IETF Internet standards are

already in place because 3GPP standardisation is done in collaboration with IETF and NGN built on 3GPP specs.

Global routing database (LoST) is key element in IETF ECRIT concept. Global IETF emergency call routing database should also be able to serve 3GPP

and NGN needs. No basic change to current basic NGN architecture necessary if NGN reuses IETF

data base. NGN Location Retrieval Function (LRF) could access LoST.

The goal:

Only one place for the emergency organisations to put their routing requirements data!

“Single point of truth”

Can the two worlds come together ?


Further Information NGN

ETSI NGN, IMS emergency session standards ETSI TS 102 424 (2005-09) – Requirements for the NGN network to support emergency communication

from citizen to authority

Draft ETSI TS 182 009 (version 12.07.2006) – NGN Architecture to support emergency communication from citizen to authority

ETSI TS 102 164 (2006-09) – Emergency Location Protocols

G. Camarillo, M. A. Garcia-Martin, The 3G IP Multimedia Subssystem (IMS), Wiley 2006

IETF / ECRIT – Emergency Context Resolution using Internet Technologies

http://www.ietf.org/html.charters/ecrit-charter.html

A Wiki page that points to the most important documents:http://www.tschofenig.com/twiki/bin/view/EmergencyServices/EcritReviews(including link to SDO Emergency Services Coordination Workshop (ESW06))

IETF: http://edu.ietf.org/


Thank you very much for your attention !

Documents

Ernst Langmantel Technical Director, Austrian Regulatory Authority for Broadcasting and Telecommunication (RTR GmbH) The opinions expressed in this presentation