EENA NG112 Committee Long Term Definition Document Conference call 1 of February 2012
Agenda 1. Next Generation Emergency Services Overview Background NG112 Scope meets EENA Operational Requirements 2. NG112 Long Term Definition Document Objectives Scope Entities and interfaces Gateways Document overview 3. Next Steps TBDs / Open Issues For NG112 LTD version 1 Long term next steps
NG Emergency Services Overview Background In March 2011 we published the Introduction to the European Next Generation 112 A requirements analysis for NG112 was conducted and matched against the service requirements developed by the operations committee. Mid 2011 we did a poll in the NG112 TC on the next steps for the work on the technical architecture. Group reinforced the desire to progress the work on the NG112 LTD document.
NG Emergency Services Overview NG112 Scope meets EENA Operational Requirements NG112 LTD Scope 1. Standards based approach 1. Geo-Location conveyance 2. PSAP interface 3. Call Routing 2. Multi-Media communications with citizens 3. Emergency Services Interoperability NG112: A standards-based SIP/IP Emergency Services Network (ESInet), with dynamic call routing of multi-media communications and advanced call processing functions
NG Emergency Services Overview NG112 Scope meets EENA Operational Requirements EENA Next Generation 112: Emergency services operational requirements survey Q13: Do you think that standards on NG112 are needed?: 98% yes Q8: Should location for the call always be available? 100% yes Q9: Do you require calls to be routed directly to the relevant local PSAPs? 72% yes Q4 : Do you believe it is appropriate to receive data (e.g, pictures, location information, contact data) from 112 applications from smartphones? 97% yes Link to Results for Next Generation 112: Emergency services operational requirements survey
NG112 Long Definition Document Document Objectives Define a long term architecture for European Emergency Services based on NENA i3 architecture Compatible with NENA i3 Compatible with European Emergency Services organisations very different organisational structure (See also recent EENA s PSAP in Europe publication)
NG112 Long Definition Document NG112 Scope
NG112 Long Definition Document NG112 Entities and Interfaces Emergency Services IP Network (ESINet) Border Control Functions at the ESINet to protect against attacks. Call Routing: Emergency Services Routing Proxy (ESRP) interacts with Emergency Call Routing Function (ECRF) Location Validation
NG112 Long Definition Document NG112 Entities and Interfaces (cont.) Many interfaces concern the PSAP itself Call establishment (using SIP) Media communication (audio, and multi-media support) Location for dispatching first responders Bridging and call forwarding IP-based vehicular emergency call support and integration with ecall
NG112 Long Definition Document NG112 Entities and Interfaces (cont.) Location conveyance: In-band in SIP message (via RFC 6442) Out-of-band delivery Out-of-band delivery makes use of two communication paradigms Request/Response using HTTP Asynchronous notification using SIP Re-uses already standardized protocols and data formats
NG112 Long Definition Document Interworking with Legacy Technology Legacy Gateways
NG112 Long Definition Document Interworking with Legacy Technology Legacy Gateways (cont.) Gateway related changes Interfaces Location Delivery Legacy Network GWY (LNG) SS7 as standard interface HELD, MLP Legacy PSAP GWY (LPG) SIP (LPG becomes part of legacy infrastructure) HELD, MLP Number plan ITU-T E.164 ITU-T E.164 (partially described, yet) Service Voice Voice
NG112 Long Definition Document Document Overview TABLE OF CONTENTS 1 Introduction 2 Terminology 3 Functional Elements 4 Interfaces 5 Security 6 Gateways 7 Data Associated with call/caller/location/psap 8 3rd Party Origination 9 Test Calls 10 Parameter Registries 11 References
Next Steps NG112 LTD Specification TBDs / Open Issues Create EENA registry service for protocol parameters Develop CA model (for security) Architectural deployment variants Instant Messaging Protocol Development PSAP callback More details about the database synchronization mechanisms Best current practice for access control Logging Update on additional data Legacy Gateway description for non-voice based media (e.g., ecall) More examples
Next Steps for NG112 LTD Version 1 Next steps First Comments and contributions Next conference call Comments and contributions Conference call Deadline 23 February 1 March 16.00 CET Time Deadline 15 March Publication April 2012 21 March 16.00 CET Time
Next Steps Long Term Next Steps Completion of Version 1 of the NG112 LTD specification (see previous slide) Cooperation with SDOs Cooperation with NENA on a harmonized, single version 2. Incorporate resolved open issues. Includes feedback from interoperability events Timeframe: Late 2012/Early 2013
Thank you!! Cristina Lumbreras: cl@eena.org Hannes Tschofenig: ht@eena.org