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.

1. Bob Williams
Convenor CEN TC278 WG15 eSafety
Editor EN 15722; EN16072; EN16062; EN16454; TS16405
eCall Standards and
Future Standards
EENA 2016eCall Standards and Future Standards Slide 112 April 2016

2. ETSI / 3GPP GSM/UMTS Standards.
There are more than 200 TS and Standards that
support GSM/UMTS. They are generally not eCall
specific but support e112
Release 8 or later
Introduces and specifies the eCall Flag
GSM/UMTS are circuit switched mobile networks
Status
EENA 2016 : eCall Standards and Future
Standards
Slide 2Sept 2015 Berlin

3. Following the issuing of the text of the eCall Regulations, the
key 112eCall Standards were updated to ensure consistency
EN 16072: 2015 eCall Operating
Requirements
This European Standard specifies the general operating
requirements and intrinsic procedures for in-vehicle
emergency call (eCall) services in order to transfer an
emergency message from a vehicle to a Public Safety
Answering Point (PSAP) in the event of a crash or
emergency, via an eCall communication session and to
establish a voice channel between the in-vehicle equipment
and the PSAP.
Status
EENA 2016 : eCall Standards and Future
Standards
Slide 3Sept 2015 Berlin

4. EN 15722:2015 eCall –Minimum Set of
data
Specifies the data that is sent to the PSAP –location
direction of travel, identification of vehicle etc.
Status
EENA 2016 : eCall Standards and Future
Standards
Slide 4Sept 2015 Berlin

5. EN 16062:2015 eCall High level
application protocols for GSM/UMTS
Defines the high level application protocols,
procedures and processes required to provide the
eCall service using a TS12 emergency call over a
mobile communications network.
NOTE HLAP requirements for third party services
supporting eCall can be found in EN 16102,. This
deliverable makes reference to those provisions but
does not duplicate them.
Status
EENA 2016 : eCall Standards and Future Standards Slide 5
Sept 2015 Berlin

6. EN 16454:2015 eCall End-to-End Conformance Tests
This European Standard defines the key actors in the eCall chain of service provision as:
In-Vehicle System (IVS)/vehicle,
Mobile network Operator (MNO),
Public safety assistance point [provider](PSAP),
in some circumstances may also involve:
Third Party Service Provider (TPSP),
and to provide conformance tests for actor groups 1) – 4).
NOTE Conformance tests are not appropriate nor required for vehicle occupants, although
they are the recipient of the service.
This European Standard covers conformance testing (and approval) of new engineering
developments, products and systems, and does not imply testing associated with individual
installations in vehicles or locations.
Status
EENA 2016 : eCall Standards and Future
Standards
Slide 6Sept 2015 Berlin

7. EN 16102:2012 - Intelligent transport systems — eCall —
Operating requirements for third party support
The objective of implementing a 'Third Party' emergency call is to provide
emergency assistance and an automated notification of a traffic accident, using
'Third Party Services' packages where such services are supported between the
vehicle and a Third Party Service Provider in countries where such notification of
an emergency are supported by PSAPs.
The first objective of this TPS-eCall is to transfer an emergency message from a
vehicle to a Third Party Service Provider (TPSP) in the event of a crash or an
emergency, and to establish a voice channel between the in-vehicle equipment
and the TPSP.
The second objective of this TPS-eCall is, in case of an emergency likely to
require assistance from the emergency services, for the TPSP to transfer an
emergency message including the data of the Minimum Set of Data (MSD) (as
defined in EN 15722) from the TPSP to the most appropriate PSAP and to make
best efforts to establish a direct voice contact between that PSAP and the
occupants of the vehicle if required by the PSAP.
This European Standard specifies the general operating requirements and
intrinsic procedures for an in- vehicle eCall via the services of a Third Party
Service Provider (TPSP).
This European Standard also provides definition of the service(s) provided to the
PSAP and the method and form of service delivery.
Status
EENA 2016 : eCall Standards and Future
Standards
Slide 7Sept 2015 Berlin

8. CEN TS 16405:2014 eCall Additional
optional dataset for commercial vehicles
This Technical Specification defines an additional data concept that may
be transferred as an ‘optional additional data concept’ as defined in CEN
15722 eCall MSD, that may be transferred from a goods vehicle to a
PSAP in the event of a crash or emergency via an eCall communication
session.
Two variants are provided, one (schema A) for use where information
about the goods (ADR classified or not) is known in the eCall device; the
second variant (schema B) is for use where such information must be
fetched from elsewhere.
This document should be seen as an addendum to EN 15722; it contains
as little redundancy as possible.
Status
EENA 2016 : eCall Standards and Future Standards Slide 8Sept 2015 Berlin

9. 00278400
ProForma agreements
Between PSAPs and TPSPs .
First draft circulated and discussed 3rd draft being
finalised. Will go to TS ballot shortly
Development of proforma agreements/
heads of agreement
between Public Safety Answering Point operators and
eCall Third Party Assistance Providers (TPSP)
Active Work items
EENA 2016 : eCall Standards and Future
Standards
Slide 9Sept 2015 Berlin

10. 00278401
Interoperability and user choice in 112
eCall aftermarket and third party eCall
services . Initial draft under development
To provide a standardized option between
consenting organisations who wished to work in an
environment where users could change service
provider. Part of the investigation is to consider
whether the target output should be a TR/TS or EN
Active Work items
EENA 2016 : eCall Standards and Future
Standards
Slide 10Sept 2015 Berlin

11. SA/CEN/ENTR/EFTA/000/2014-04 High Level
Application Protocols for eCall using E-
UTRAN
As 16062 for packet switched networks
CEN PT Project recently approved by EC
EENA 2016 : eCall Standards and Future Standards Slide 11Sept 2015 Berlin

12. SA/CEN/ENTR/EFTA/000/2014-06 ECall via a
shared vehicle telematics platform (ITS-
station)
As cars become equipped for cooperative ITS and
have built-in ITS-stations (multi-use communication
platforms) to provide the means to send eCall via
ITS-stations
CEN PT Projects awaiting approval by EC
EENA 2016 : eCall Standards and Future
Standards
Slide 12Sept 2015 Berlin

13. SA/CEN/ENTR/EFTA/000/2014-05 Enabling
eCall for additional classes of user
HGV
ADR
P2WV
Busses and Coaches
?cycles
?Disadvantaged road users
CEN PT Projects awaiting approval by EC
EENA 2016 : eCall Standards and Future
Standards
Slide 13
Sept 2015 Berlin

14. Aftermarket eCall
Via TPSP not a major concern,but
Direct 112 eCalls: A major concern
– could overwhelm PSAPs
Aftermarket 112 eCall / Aftermarket TPS eCall
IVS requirements
System/PSAP requirements
Certification
Maybe a new EC Project (sAFE) next year
Area of New investigations
EENA 2016 : eCall Standards and Future Standards Slide 14Sept 2015 Berlin

15. A silent call is a successful eCall, but when the PSAP
tries to talk to the occupants of the vehicle he gets no
response
This means one of three things
A)The occupants are unconscious/unable to talk
B) The equipment is damaged
C) The occupants have left the vehicle to go and stand in a place of
safety(behind crash barrier etc.)
This is a conundrum for the PSAP
French experience with private emergency services
indicate that nearly 90% of silent calls are (c)
Silent Calls
WG # report to CEN/TC 278 Slide 1512 April 2016

16. In todays vehicle, when the regular user enters his/her
vehicle his smartphone automatically connects to the
vehicle via Bluetooth
The vehicle therefore knows if this number (or one of
several numbers) is present in the vehicle
With the phone owners prior consent, This number can be
added to the MSD in the event of a crash as an “Optional
Additional Data concept”
The meta-data for this data concept can be quickly added to
the esafetydata website
But, because of privacy issues, we need to control the way
this is done and therefore are considering a Technical
Specification
Silent Calls (2)
WG # report to CEN/TC 278 Slide 1612 April 2016

17. Certification for PSAPS
Also
Practical testing, implementation and management
and specifications for subjects of CEN PTs (E-Utran
and ITS station eCall )
Further considerations of new classes of user
ADR aspects (Dangerous Goods)
Testing out of 16405 (optional additional data for
commercial vehicles)
Standardisation related support hoped for from
I_HeERO
EENA 2016 : eCall Standards and Future Standards Slide 17Sept 2015 Berlin

18. www.esafetydata.com
Data Registry Available for PSAPs, OEMs
and Aftermarket
EENA 2016 : eCall Standards and Future Standards Slide 18Sept 2015 Berlin

19. WG # report to CEN/TC 278 Slide 1912 April 2016

20. Representation at European eCall Implementaiton
Platform
GLONASS (Russian eCall) representation in WG15
Direct liaison /involvement with I-HeERO
Relevant WG15 Liaison Activities
EENA 2016 : eCall Standards and Future Standards Slide 20
Sept 2015 Berlin

21. Planned WG meeting(s)
21 September 2016, Berlin (adjacent to eCall Days)
Email Bob Williams if you would like to attend
Next Meetings
EENA 2016 : eCall Standards and Future
Standards
Slide 21
Sept 2015 Berlin

22. Bob Williams bw_csi@fastmail.fm
www.2-csi.com
Questions
EENA 2016 : eCall Standards and Future
Standards
Slide 22
September 2015
Berlin