Embed Size (px)
Citation preview
17 10 2014
EENA NG112 Long Term
Definition Document
A non-technical Tutorial
Wolfgang Kampichler EENA NG112 Technical Committee
17 10 2014
Outline
LTD Introduction
LTD Functional Elements
Step-by-step Emergency Calling
Contacting 112 from App
Contacting 112 from Mobile
Benefits & Risks
Further Reading
17 10 2014
Outline
Introduction
17 10 2014
Today (a possible scenario)
Contacting emergency services via audio (fixed or mobile phones)
Call routing via static configuration (incumbent provider)
Proprietary interface to location information (if ever)
Interconnected emergency centres (limited call routing)
17 10 2014
EENA - LTD
The purpose of the LTD is to define a long-term definition of an European emergency services architecture
The document has a profound impact on the operation of 112 services and PSAPs (new data formats, more rigid data structure requirements, new functions, …)
17 10 2014
History
Starting 2010:
Hannes became NG112 Technical Committee Co-Chair
service requirements developed by the Operations Committee
interworking with NENA (Detailed Functional and Interface Standards for the NENA i3 Solution – 08-003)
April 11th, 2012: NG112 LTD version 1 published
Latest version: http://www.eena.org/uploads/gallery/files/pdf/2013-03-15-eena_ng_longtermdefinitionupdated.pdf
17 10 2014
Overview
The document provides:
the definition of specific terminology used in the description of the NG112 architecture
a description of elements building the core concept of the NG112 architecture
the description of the state that has been reached after a migration from legacy to all IP-based systems with a corresponding Emergency Services IP network
There are some underlying assumptions (e.g.):
common signalling protocol for any call
calls entering provide (coarse) location for call routing
17 10 2014
Document Structure
Chapter 1 – 3: Introduction and terminology
Chapter 4: describes functional elements that are building the core concept of the NG112 architecture
Chapter 5: describes interfaces to a set of functional elements
Chapter 6: discusses security aspects
Chapter 7: introduces legacy interworking
Chapter 8 – 14: conclude the document
17 10 2014
Outline
Functional Elements
17 10 2014
ESInet
Emergency Service IP Network (LTD: 4.1)
Private and managed IP network, but not a walled garden
The ESInet is connected to the Internet
The term ESInet refers to the network (routers and links) but not to the services that run on it
The key to reliability is redundancy and security protection
17 10 2014
BCF
Border Control Function (LTD: 4.2)
External security border for ESInet (Internet)
Internal isolation border for PSAP
Has both, firewall and session border controller
Has functions to block specific call sources (suspicious levels)
Must withstand largest feasible attack (today ~ 10Gbit/s)
17 10 2014
ESRP
Emergency Service Routing Proxy (LTD: 4.3)
Call routing engine
Uses the ECRF to choose the nominal next hop
Applies route policy of the nominal next hop to determine actual next hop
Policy may take into account the state of a PSAP, time, …
Route decision can be: next ESRP, nominal/diversion PSAP, …
17 10 2014
ECRF
Emergency Call Routing Function (LTD: 4.4)
Routing database used for all calls
Queried using the IETF LoST protocol
send location in plus a ‘service urn‘ and get a URI of where to send the call out
conceptually geocode (civic and point in polygon)
Used to route to correct police, fire, ems, poison control, …
17 10 2014
PSAP
Public Safety Answering Point (LTD: 4.7)
Receives all calls with location via the ESInet
Can use ECRF/ESRP policies to route to queues of call takers
Multimedia capable: voice, video, real-time text, and messaging
Allows for virtual PSAPs
Services may reside in a data centre or at the PSAP
17 10 2014
LNG
Legacy Network Gateway (LTD: 7.1)
Element to interconnect with legacy origination networks
Bridge between existing origination network and ESInet
Interworks location towards ESInet
Forwards calls to ESRP
17 10 2014
LIS
Location Information Service (LTD: 4.10)
Stores location against some kind of key
Key can be a network address, phone number, URI …
An originating device queries the LIS when it boots, periodically when it moves and before an emergency call
Returns a PIDF/LO (civic address, geodetic) either by reference or by value
17 10 2014
Outline
Step-by-Step Emergency Call
CONTACTING 112 FROM APP
17 10 2014
Step-by-step Emergency Call
App gets (coarse) location from LIS (for call routing)
App uses location and type of service (ambulance, fire, police, …) to request next normal hop at the ECRF (external)
For more detailed information, please refer to: LTD section 4.4 ECRF and 4.10 LIS or IETF Standards
17 10 2014
Step-by-step Emergency Call
App starts calling the next hop (ESRP1) received from the ECRF
Signalling passes the BCF and hits ESRP1
For more detailed information, please refer to: LTD section 4.2 BCF, 4.3 ESRP and 5.2 SIP Call
17 10 2014
Step-by-step Emergency Call
ESRP gets more accurate location from LIS (for dispatching)
ESRP uses location and type of service (ambulance, fire, police, …) to request next normal hop at the ECRF (internal)
For more detailed information, please refer to: LTD section 4.3 ESRP, 4.4 ECRF and 4.10 LIS
17 10 2014
Step-by-step Emergency Call
ESRP1 operates on behalf of the emergency call and forwards to the next normal hop (ESRP2)
For more detailed information, please refer to: LTD section 4.3 ESRP
17 10 2014
Step-by-step Emergency Call
ESRP2 applies the route policy of the nominal next hop to determine actual next hop
ESRP2 forwards to the next hop (PSAP/Carol)
For more detailed information, please refer to: LTD section 4.3.1.2 Call Queuing and 5.4 Policy
17 10 2014
Step-by-step Emergency Call
Call set-up exchanges media capabilities
Bi-directional media stream between endpoints passes the BCF
For more detailed information, please refer to: LTD section 5.1.8 Media
17 10 2014
Step-by-step Emergency Call
Location updates for location URIs may be obtained by repeating the dereference or by a specific subscription (Presence Event) with a subsequent location update notification sent when a more accurate location is available
For more detailed information, please refer to: LTD section 4.7.3 LIS Interface
17 10 2014
Outline
Step-by-Step Emergency Call
CONTACTING 112 FROM MOBILE
17 10 2014
Step-by-step Emergency Call
Location enhanced emergency call service (M/493 EN)
Gateway (LNG) uses location and type of service (ambulance, fire, police, …) to request next normal hop at the ECRF (external)
For more detailed information, please refer to: 3GPP and LTD section 7.1.2.2 NIF Handling of Location Information
17 10 2014
Step-by-step Emergency Call
Gateway (LNG) starts calling the next hop (ESRP1) received from the ECRF
Signalling passes the BCF and hits ESRP1
For more detailed information, please refer to: LTD section 7.1.2.3 SIP Interface to the ESInet
17 10 2014
Step-by-step Emergency Call
ESRP gets more accurate location from LIS (for dispatching)
ESRP uses location and type of service (ambulance, fire, police, …) to request next normal hop at the ECRF (internal)
For more detailed information, please refer to: LTD section 4.3 ESRP, 4.4 ECRF and 4.10 LIS
17 10 2014
Step-by-step Emergency Call
ESRP1 operates on behalf of the emergency call and forwards to the next normal hop (ESRP2)
For more detailed information, please refer to: LTD section 4.3 ESRP
17 10 2014
Step-by-step Emergency Call
ESRP2 applies the route policy of the nominal next hop to determine actual next hop
ESRP2 forwards to the next hop (PSAP/Bob)
For more detailed information, please refer to: LTD section 4.3.1.2 Call Queuing and 5.4 Policy
17 10 2014
Step-by-step Emergency Call
Call set-up exchanges media capabilities
Bi-directional media stream between endpoints passes the BCF
For more detailed information, please refer to: LTD section 5.1.8 Media
17 10 2014
Step-by-step Emergency Call
Location updates for location URIs may be obtained by repeating the dereference or by a specific subscription (Presence Event) with a subsequent location update notification sent when a more accurate location is available
For more detailed information, please refer to: LTD section 7.1.3 Location Interwork Function (LIF)
17 10 2014
Tomorrow
Contacting emergency services via audio, video, text (any device)
Location based call routing (emergency service provider)
Standardized interface (IETF) to location information
Interconnected emergency centres (advanced call routing)
17 10 2014
Outline
Benefits & Risks
17 10 2014
Benefits & Risks
Location information received with the call
Single signalling and multimedia interface at PSAP
Location and policy based call routing
Simplifies networked services (cross border/cross vendor)
Reduced OPEX and improved response time (ref BE/SL)
Lack of regulation (public services)
an emergency service is as good as the accuracy of location
70% of all emergency calls are made from mobile devices
current capabilities of ES in Europe is inconsistent
LTD not well understood (might cause ambiguity in deployment)
17 10 2014
Outline
Further Reading
17 10 2014
Further Reading
Want to learn more?
Emergency Context Resolution with Internet Technologies
http://datatracker.ietf.org/wg/ecrit/charter/
ETSI EMTEL Status Report
http://portal.etsi.org/TBSiteMap/EMTEL/EMTELStatusReport.aspx
NEXT GENERATION 112 TRANSITION MODELS
http://www.eena.org/uploads/gallery/files/pdf/2013_12_19_ng112_models_v1_0_final.pdf
112 APPS EENA OPERATIONS DOCUMENT
http://www.eena.org/uploads/gallery/files/operations_documents/2014_02_25_112smartphoneapps.pdf
