1. Freddie McBride, European Communications Office
eCall – Implementation challenges
Freddie McBride, European Communications Office
ETSI NTECH #18
Sophia Antipolis April 2017

2. eCall Workshop – 31 January 2017, ECO Copenhagen
Attended by stakeholders from all relevant groups (OEMs, Operators, PSAPs, SDOs and Regulators)
Presentations from stakeholders on market trends, implementation, interoperability, numbering and next-generation eCall
Good discussions but more questions than answers on implementation
NTECH should be aware of the implementation challenges and possible impacts on standards
ECC Recommendation – Numbering for eCall

3. About CEPT, ECC and ECO

4. What is eCall
eCall is a European initiative intended to bring rapid assistance to motorists involved in a collision anywhere in the European Union
Source: Wireless Design & Development
eCall is a 112 call. Requirements for citizen access to 112 and the provision of caller location information apply

5. eCall Legislative Requirements
Source: SBD/Vodafone

6. eCall Penetration
eCall regulation applies to ‘new type’ vehicles
Model cycle typically 4-6 years

7. eCall + value-added services
Source: Cubic Telecom

8. eCall only V. TPS eCall + VAS
Mandatory pan-European eCall a citizen protection policy initiative
There is no business opportunity in eCall alone.
“all vehicles should be equipped with the public 112-based eCall service, regardless of whether or not a vehicle owner opts for a TPS eCall service.”
- REGULATION (EU) 2015/758
Source: EENA

9. eCall Profile Characteristics
eCall-only profile
Dormant – no mobility management
Privacy by design
No subscription
eCall+VAS profile
Always connected
Subscription-based service
Privacy right waived in subscription agreement
Only one profile can be active at any given time!!

10. eCall numbering requirements
Why do we need numbers in the first place?
eCall is essentially a mobile service
eCall needs wide geographic coverage and the ability to roam between networks
Emergency calls from “simless” devices not supported in a lot of European Countries
For network authentication and registration (including roaming) each eCall in-vehicle system needs an International Mobile Subscriber Identity Number (IMSI)
Each eCall in-vehicle system needs an telephone number (or MS-ISDN or E.164 number) to be able to make a call and present a valid CLI.
A valid CLI is needed to facilitate callback/location update

11. Emergency Attach to Mobile Network
Each eCall device will have a subscription and an E.164 number
If the SIM is dormant, will it perform an “emergency attach” to make a call?
If it does, a temporary number is assigned and the original E.164 is irrelevant
How can callback be facilitated? Will the temporary number be sent in the CLI field?
How long will the temporary number remain assigned*?
CEN EN16072 standard says "minimum period of one hour after the eCall is terminated or until available power is exhausted" and 3GPP says 12 hours.
ETSI TS ( - Mobile Standards Group (MSG); Pan-European eCall end to end and in-band modem conformance testing; Prose test specification

12. PSAP Operator View (Lithuania 112)

13. What deployment might look like – embedded eUICC
This is my view on how eCall will be deployed.

14. What deployment will look like – cont’d

15. eCall technology – now and future
eCall as required by legislation uses circuit-switched technology on GSM/UMTS (CS eCall) (standardisation began in 2004)
eCall device has inband modem (voice and date carried on same channel)
PSAPs need to install inband modems to process MSD
Next Generation eCall (NG eCall) will be based on IMS (standardisation began in 2013)
Vehicles could be fitted soon with devices capable of supporting both technologies
At this point there is no option for PSAPs to future proof investments
Remember average age of a car on European Roads is around 18 years in some parts of Eastern Europe

16. Telephone (E.164) Numbers for eCall
How many numbers required?
270 million vehicles – approx 5% stock renewal each year (13.5 million)
New passenger car registrations in Europe (source: ACEA)
Demand for approximately 13,000,000 new mobile telephone numbers per annum when critical mass of new type vehicles reached (so not anytime soon!)
Numbering Options
National numbers (assigned by National authorities)
Dedicated M2M numbers
Mobile numbers
International numbering resources (Assigned by ITU-T)
+882, +883, +878 number ranges
Year
2012
2013
2014
2015
2016
5 yr average
New registrations
(000,000) 12
11,9
12,5
13,7
14.6
12,9

17. eCall Life Cycle Management
Link between VIN and SIM
Beginning: Deals between OEMS and MNOs
Deployment at car assembly plant
Middle Accidents & Testing (mandatory periodical inspections)
End Car written/off or reaches end of life naturally
Decommissioning of SIM
Recover of numbering resources

18. Standards – NG eCall NG eCall Standardization Status ETSI / 3GPP
TR recommends to use 3GPP and IETF for eCall – published in 2014
Emergency call requirements for IMS – stable
IMS eCall requirements and migration from CS eCall – stable
IETF
‘eCall’ RFC–publication – latest version dated February 2017
Focuses on next generation eCall specific needs for the EU
Carries data and metadata/control objects per ‘additional-data’ mechanism
Metadata/control (ack, retransmission, requests to vehicle, etc.)
additional-data' specification (RFC 7852) - published
Transmit any registered data block with emergency call
CEN
eCall over IMS (TC278 WG15, PT1506) – draft available, approval expected Q1 2017
eCall to other classes of user (PT1507) – started
eCall over a common telematics platform (PT1508) – started
Footer copy here

19. Areas where other standardisation work may be necessary
Over-the-air Provisioning of subscriber profiles
GSMA Specification
ETSI Standard (TC SCP)
Temporary assignment of MS-ISDNs (if eCall SIMs dormant)
Need for defining minimum period of time for which number remains assigned (days not hours according to PSAPs)
TPS eCall
Define a standard approach for conveying an emergency call from a TPS eCall centre to a PSAP
At ITU level
Raising awareness and encourage provisioning of global numbering resources on all networks

20. Thank you for your attention!
@CEPT_ECC