EENA 2016 - Standards Update (1/3)
•
0 likes•279 views
There is considerable development work going on regarding emergency Applications and in this session attendees were informed about the most recent updates and heard first hand where the latest thinking will take us. They were also informed about standards discussed and produced by international Standards Developing Organisations (SDOs) and that will impact emergency calls handling organisations.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (17)
Similar to EENA 2016 - Standards Update (1/3)
Similar to EENA 2016 - Standards Update (1/3) (20)
More from EENA (European Emergency Number Association)
More from EENA (European Emergency Number Association) (20)
Recently uploaded
Recently uploaded (20)
EENA 2016 - Standards Update (1/3)
- 1. Pan-European Mobile Emergency Application (PEMEA) EENA Conference Prague 2016 Presenters James Winterbottom (EENA Technical Committee Vice Chair) Cristina Lumbreras (EENA Technical Director) 07/04/2016
- 2. EENA Conference Prague 2016 Objectives 2 1. What is the EENA Apps architecture 2. What the Public Authorities/PSAPS need to do to access Apps 3. What are the next steps?
- 3. EENA Conference Prague 2016 Emergency Apps There are many “emergency” Apps on the market, made by Public Authorities, PSAPs, Commercial companies. Lack of accurate location information (and other reasons) has fueled the growth of Apps with device-provided location information being generated. Apps are powerful tool for bi-directional communication (A2C) and (C2A) and use location techniques such as GNSS, WiFi and Cell-ID. Apps features also include video calling, supplementary health information, basic first aid tips But there are issues with Apps; namely they only work within the local or national boundaries, consumers/citizens don’t download them in large numbers, often forgotten about in an emergency situation etc. 3
- 4. EENA Conference Prague 2016 EENA Apps Strategy 4 ✔ In progress In progress ✔
- 5. EENA Conference Prague 2016 The General Situation Today 5 Application Provider PSAP Service Provider App PSAP Application Provider connects to PSAP Service Provider to give extra information to the PSAP May be more than one region but not scalable to all of Europe
- 6. EENA Conference Prague 2016 Basic PEMEA Architecture Application Provider PSAP Service Provider Aggregating Service Provider Pa Ps Pp Pr App PSAP Application Provider PSAP Service Provider Pa Ps Pp App PSAP Pr 6 If want to roam then we need a way to interconnect
- 7. EENA Conference Prague 2016 Quick Overview:- Calling from Home Application Provider PSAP Service Provider Aggregating Service Provider Pa Ps Pp Pr App PSAP Application Provider PSAP Service Provider Pa Ps Pp App PSAP Pr MNO Voice Home Region or Country 7 For the local PSAP
- 8. EENA Conference Prague 2016 Quick Overview:- Calling Abroad PSAP Service Provider Aggregating Service Provider Pp Pr PSAP Application Provider PSAP Service Provider Pa Ps Pp App PSAP Pr Visited Region or Country MNO Voice 8 Not for this PSAP. now an origination PSP YES for this PSAP. now a terminating PSP Cool! Now I can help you better
- 9. EENA Conference Prague 2016 PEMEA Message Flow 9 Application Provider Originating PSAP Service Provider emergencyDataSend(ttl, route:AP, Loc++) Aggregating Service Provider Determine Destination emergencyDataReceived(route:AP+oPSP, delivery) Determine Destination emergencyDataSend(ttl-1, route:AP+oPSP, Loc++) emergencyDataReceived(route:AP+oPSP+ASP, delivery) Terminating PSAP Service Provider emergencyDataSend(ttl-2, route:AP+oPSP+ASP, Loc++) emergencyDataReceived(route:+oPSP+ASP+tPSP, delivery) PSAP DATA
- 10. EENA Conference Prague 2016 emergencyDataSend 10 ttl (time to live) onErrorPost route callerIds apMoreInformation accessData emergencyDataSend How many nodes the message may traverse before being dropped Unique sequence identifier from first hop The hop number in the list of hops The URI of the sending node URI or token providing the contact details The service to which the Id applies The URI to the information The type of information the URI yields apMoreInformation information information information protocol value typeOfInfo Application protocol associated with the URI mcc mnc network Mobile Country Code Mobile Network Code position timeStamp hop node typeOfId value callerId callerId callerId callerIds accessData wifi network or msgSeq hops hop hop route serving bssid wifi tuple entity status geopriv location-info usage-rules method provided-by ProviderInfo DeviceInfo SubscriberData PIDF-LO EmergencyCallDataValue timestamp EmergencyCallDataReference SubscriberData pidfLo URI at the AP to post any errors to
- 11. EENA Conference Prague 2016 emergencyDataRecieved timeStamp route delivery emergencyDataRecieved The time and date that the message was sent in UTC Unique sequence identifier from first hop The hop number in the list of hops The URI of the sending node URI or token identifying the node the EDS was sent to The node that the EDS was sent to position timeStamp hop node destType value delivery msgSeq hops hop hop route 11
- 12. EENA Conference Prague 2016 PEMEA Error timeStamp reason message error The time and date that the message was sent in UTC Unique sequence identifier from first hop The hop number in the list of hops The URI of the sending node Free text message describing the error The language the message is written in position timeStamp hop node language value message msgSeq hops hop hop route route Token identifying the type of error 12
- 13. EENA Conference Prague 2016 EENA’s next steps Complete review and publication of “PEMEA Protocols and Procedures” document Complete the “PEMEA Operations Guidelines” document Identify a protocol reference implementation to test against. Bridge with ETSI EMTEL towards a standardised approach Identify early-PEMEA adopters to assist in improvements 13