The PanEuropean invehicle emergency call: eCall SIMBA2 Moscow, 221008

1
The Pan-European in-vehicle emergency call eCall
SIMBA2 Moscow, 22/10/08

• André Vits - Head of Unit
• European Commission
• DG Information Society and Media
• ICT for transport Unit

2
Presentation outline

• Whats eCall?
• Status of the eCall Initiative
• Next steps and conclusions

3
eCallPan-European In-vehicle Emergency Call
System
4
The pan-European eCall What is it?

• Triggered automatically by the in-vehicle device
  in case of serious accident or manually by
  vehicle occupants
• Builds on the single European Emergency number
  (112 and E112)
• Creates a voice link to the closest PSAP and
  sends data message (Minimum Set of Data MSD-)
• MSD includes
• Time stamp
• Accurate location (GNSS) and direction of driving
• Vehicle identification
• Information about the accident
• IP address of a private service provider (if any)

5
Why eCall? (1) Road Safety in Europe
Halving the number of road accident victims in
the EU by 2010 A shared responsibility

• Road Transport in EU27
• Road Accidents in 2007
• 42.500 fatalities
• 1.27 million accidents involving injury
• 1.7 million injuries

5
6
Why eCall ? (2)The potential of eCall

• Reduction of average response
• time to the accident
• 50 in Rural Areas
• 40 in Urban Areas
• Reduction of accidents severity
• 15 to less severe medical
• category
• Annual lives saving
• Estimated to be up to 2.500
• in EU 25
• Costs savings
  
• (exceeding many times needed investments)
• Up to 26 billion Euro in EU 25
• annually

7
Why eCall (3)The potential of eCall

• The potential for lives saved
• Estimated by the SEiSS1 Study, E-MERGE Project,
  U.S. data
• Confirmed by the Finnish Aino Study
• 4.7 lives saved on call delay only
• 2001 - 2003 when almost 100 penetration of
  mobile phones in Finland
• Further evidence being looked at
• eIMPACT Project (DG INFSO)
• Field Tests in the MS (e.g LAB)
• Field Operational Tests EC FP7 (starting 2008)
• Impact assessment study (Oct. 08)

1 Exploratory study on the potential
socio-economic benefits of the introduction of
Intelligent Safety Systems in Road Vehicles
8
The pan-European eCall (1) The Concept
FSD
FSD
E112
112
MSD
MSD
9
The pan-European eCall (2)Based on 112/E112
Public Telco
Fixed network

• 112

PSAP
CLI Call Line Identifier MSD Minimum Set of
Data FSD Full set of Data
(Voice)
ISDN
Operator
Fixed Telco Operator
Fixed network
PSAP

• E112

CLI (exact location)
ISDN
(Voice location)
CLI (best location)
Mobile Telco Operator

• eCall

Fixed network
PSAP
Voice (E-112)
GNSS
Voice (E112)
ISDN
CLI (best location)
MSD (accurate location)
MSD
(Voice MSD)
Voice
Service Provider (Optional added value services)
FSD
Additional Data
10
E112 and eCall (3) Summary

• 112
• 112 Operational both for fixed and mobile lines
  in all EU Member States
• Quality of 112 emergency calls handling varies
  strongly in (also at regional, local level)
• Only few countries have 112 as the single
  emergency number
• E112
• Location of fixed calls generally solved
• Location of mobile phones (push) only solved in
  some Member States. Some others have
  implementation plans to upgrade their
  infrastructure, while some have no plans
• eCall
• Benefits of pan-European service recognised by
  all Member States
• Different degree of implementation. Some have
  implementation plans envisaged and pilots
  planned, others not ready
• Need to progress and complete the standardisation
  which is blocking the implementation in Europe

11
E112 and eCall What is needed from the PSAPs?
PSAPs Needs of infrastructure upgrading

• 112 (Obligation under USD in EU)
• Appropriate answer (including multilingual)
• From 112 to E112 (Obligation under USD)
• Equipment GIS (Geographic Information System) in
  every operator post
• SW for processing location data and CLI
• Procedures Location data should arrive to
• the same operator answering the voice call
• Interface with MNO Agreement on protocols
• for provision of best location
• Training
• From E112 to eCall (In-band modem solution)
• Server with in-band modem to receive the Minimum
  Set of Data (MSD)
• SW for processing the MSD
• Procedures to deal with eCalls
• Training

12
eCall Which benefits for the PSAPs?

• The Emergency Response Services will benefit
  from
• Immediate contact with the vehicle occupants
  through the voice link
• Detailed information on the incident with the MSD
  allowing
• Immediate localisation of the incident
• Reduction of the conversation time
• Automatic Visualisation of the precise location
• Quick dispatching of the relevant emergency
  service(s) optimising the response to the
  emergency
• Moreover eCall can be used to design added value
  services useful to the emergency response centres

13
eCall Which benefits for the Road Operators?

• The Traffic Management Centres will benefit from
• Immediate reporting of traffic accidents
• More efficient traffic management thus reducing
  congestion
• Immediate accurate localisation of the incident
• Quick information to other road users
• Reduction of the time for clearing the way
• Protocols of co-operation PSAPs Traffic
  Management Centres for the transmission of the
  information needed.

14
The pan-European eCall(4)The Time-table

• 14 MS 3 Associated States have signed the
  MoU. 4 more will do it at short term
• Negotiation with the Automotive industry
  (ACEA, JAMA, KAMA) completed.
• Full-scale field tests to be started from the
  beginning of 2008
• All key Member States ready with upgrade of
  PSAPs September 2009
• Introduction of eCall as standard option in
  all vehicles type-approved
• from 1st September 2010 onward

15
Presentation outline

• Whats eCall?
• Status of the eCall Initiative
• Next steps and conclusions

16
Status of the eCall Initiative(1) eCall MoU
signature status
The eCall Memorandum of Understanding (MoU) aims
at parallel commitment of all stakeholders
towards full eCall Deployment

• 14 Member States and 3 Associated States have
  signed
• More countries have announced their signature
• 60 other organisations have signed as well,
  representing all the stakeholders involved

17
Status of the eCall Initiative (2)Moving forward
in Europe

• - Political Level
• Full support from the European Parliament
• New Commission Communication setting up actions
  for the eCall deployment
• - Member States and associated states
• Additional signatures to the MoU
• Pilots Germany Austria Italy, Czech
  Republic, Austria showed the feasibility of
  eCall. Field Operational Test planned
• - Standardisation
• ETSI MSG (transmission method in-band modem-,
  eCall Flag)
• CEN TC278 WG15 (MSD content, operational
  requirements, Third Parties supporting eCall)
• Consensus on MSD and eCall Flag achieved

18
Status of the eCall Initiative (3)Role of the
European Commission

• High-level Support via
• eSafety Forum Plenary Meetings
• Commission Communications
• Specific Sub-groups on eCall
• PSAPs expert group
• Service Providers Group
• Support to standardisation
• Liaison with art. 29 WP
• Awareness actions
• Liaison with all stakeholders
• - Automotive industry
• - Member States
• - Insurance, Telecom industries,
• Automotive clubs

19
Status of the eCall Initiative Commission actions

• Launched an updated impact assessment study on
  the introduction of eCall
• Launched a study to develop a VIN decoder
  available to the PSAPs
• Supporting Field Operational Tests on eCall
  (TELEFOT)
• Support to eCall standardisation activities
  through the 2008 ICT standardisation WP
• Negotiation with the automotive industry
  (ACEA-JAMA-KAMA) on the voluntary introduction of
  eCall in all new type-approved vehicles

20
The PSAP Expert Group

• Informal Group with PSAP experts, focusing on
  eCall issues
• Definition of operational requirements from PSAPs
  side
• Definition of the MSD
• Protocols to optimise the workload
• Exchange of Best Practices
• Opinion on the proposed solution for the TX of
  the MSD
• Last meeting 9th October
• Will hand over to EeIP
• All MS to send experts

21
Presentation outline

• Whats eCall?
• Status of the eCall Initiative
• Next steps and conclusions

22
Next Steps(1) European eCall Implementation
Platform (EeIP)

• Establish an European eCall Implementation
  Platform (EeIP) with MoU signatories plus
  interested MS and Association representatives
• Guidelines for implementation
• Follow-up of implementation at national-regional
  (cross border)-European level
• Exchange of best practices
• Contact Emilio DAVILA GONZALEZ
• emilio.davila-gonzalez_at_ec.europa.eu

23
Next Steps (2)

• Completion of the standardisation work It is
  important to participate in the standardisation
  fora and in the WGs. All stakeholders should
  support the process
• New eCall impact assessment study will provide
  updated figures
• Completion of the eCall VIN decoder for the PSAPs
• EeIP to solve implementation issues
• Setting up of national platforms and nomination
  of representatives
• Meeting Automotive MNO representatives to solve
  open issues
• FOTs and pilots to provide further evidence
• EC to report to Parliament and Council on the
  progress

24
Conclusions eCall The Opportunity

• An authoritative 2006 Eurobarometer study
  investigated Users' attitudes towards intelligent
  vehicle safety systems in Europe
• Over 70 of the respondents in the EU - 25 want
  to have eCall in their next car.
• The issue of data privacy for eCall does not seem
  to trouble the Europeans only 10 do not
  consider that benefits of eCall are more
  important.
• eCall as standard option in all cars is an
  opportunity for kick-starting telematics in
  Europe
• eCall can also spearhead the upgrading of
  Emergency Services in Europe
• eCall is about saving lives !

25
More Information

• Mail Box eSafety
• INFSO-eSafety_at_ec.europa.eu
• Unit Mailbox
• INFSO-G4_at_ec.europa.eu
• eSafety Website http//ec.europa.eu/information
  _society/ activities/esafety/index_en.htm
• eScope website (eCall Toolbox)
• www.eSafetySupport.org

SPASIBA THANK YOU
26

• Supporting slides

27
Standards related to eCall (1)
eCall Pan-European in-vehicle emergency call
A
Voice MSD on 112
Voice MSD on 112
E112

• Public service 112-based only
• As defined in the MoU
• Voice MSD to relevant PSAP
• 112-based, with or without intermediation
  platform under Public delegation

Private Service Provider
Intermediate Call centre
B
TPS-eCall
Stored Data
Incident Data
MSD
PSAP
Voice on specific number

• Private service reporting to PSAPs
• Voice on specific number
• Data through a private dedicated channel
• Intermediation platform (private call centre)

Incident Data
Voice connection with Vehicle occupants
28
Standards related to eCall (2)Pan-European eCall
A

• Public service 112-based only
• As defined in the MoU
• Voice MSD to relevant PSAP
• 112-based, with or without intermediation
  platform under Public delegation

WI 278220
Pan-European eCall Operating Requirements
(112-only)?
High Level Application Protocols
In-band modem trx
3GPP TS 26.267
eCall Data Transfer - General Description
3GPP TS 26.268
eCall Data Transfer. ANSI-C Reference Code
ETSI-MSG 3GPP. Chair F. Courau
3GPP TS 26.269
eCall Data Transfer. Conformance testing
CEN TC 278 WG 15. Chair Bob Williams
3GPP TS 26.969
Quality of Service Requirements for eCall and
Emergency Support Services
eCall Data Transfer. Characterisation Report
29
Standards related to eCall (3) Third Party
Services supporting eCall
B

• Private service reporting to PSAPs
• Voice on specific number
• Data through a private dedicated channel
• Intermediation platform (private call centre)

TPS-eCall Operational Requirements
Private Service Provider
Intermediate Call centre
Stored Data
Incident Data
MSD
15722
PSAP
Voice on specific number
Incident Data
Voice connection with Vehicle occupants
Quality of Service Requirements for eCall and
Emergency Support Services
Third Party Emergency Support Services
30
eCall Standardisation (1)Transmission of MSD

• From In-Vehicle System to PSAP through Mobile
  Network Operators
• ETSI MSG with 3GPP - Final TS Expected by end
  08
• Selected solution In-band Modem
• Status AT4 Wireless tested 3 candidates in-band
  modem solutions Airbiquity, RIM, Qualcomm. All
  the 3 complied with the requirements
• 3GPP SA4 has endorsed the leading candidate
  (Qualcomm) as proposed eCall solution

MNO
E112
112
MSD
MSD
31
eCall Standardisation (1)Transmission of MSD -2-

• Next Steps
• EC will request additional non-technical
  information to the candidates, and present their
  solutions to the PSAPs expert Group (9/10/2008)
• Final decision ETSI MSG meeting of
  30-31/10/2008. Open to relevant stakeholders
• 3GPP will complete the TS by December 2008 and
  the Conformance Testing on the 1st half 2009

MNO
E112
112
MSD
MSD
32
eCall Standardisation (2) eCall Discriminator
The eCall Flag will allow different structures
best suited to the different MS emergency
response infrastructures
(1) a
ECC
eCall
Direct reception The same PSAP receive all the
calls
ECC
PSAP
ECC
112
ECC
(1) b
Filtering organisation for eCalls Same treatment
for 112 calls
eCall
ECC
PSAPf
ECC
PSAP
ECC
ECC
112
33
eCall Standardisation (3) eCall Discriminator
Implemented in 3GPP TS24.008

• Table 10.5.135d Service Category information
  element
• Emergency Service Category Value (octet 3)
• The meaning of the Emergency Category Value is
  derived from the following settings (Please see
  3GPP TS 22.101 clause 10)
• Bit 1 Police
• Bit 2 Ambulance
• Bit 3 Fire Brigade
• Bit 4 Marine Guard
• Bit 5 Mountain Rescue
• Bit 6 eCall Manual
• Bit 7 eCall Automatic
• Bit 8 is spare and set to "0"
• Mobile station may set one or more bits to "1 in
  the call set-up
• If more than one bit is set to "1", routing to a
  combined Emergency centre (e.g. ambulance and
  fire brigade in Japan) is required. If the MSC
  can not match the received service category to
  any of the emergency centres, it shall route the
  call to an operator defined default emergency
  centre.
• If no bit is set to "1", the MSC shall route the
  Emergency call to an operator defined default
  emergency centre.
• eCall terminals shall set either bit 6 or
  bit 7 to 1 , all other bits shall be set to
  0. If either bit 6 or bit 7 is set to 1
  the network may route the manually or
  automatically initiated eCall to an operator
  defined emergency call centre.

eCall related items are underlined
34
CENDefinition of the MSD

• CEN TC 278 WG15
• Chair Bob William (bw_csi_at_fastmail.fm)
• Result MSD format ?
• Status - Approved
• CEN/TS 15722 was approved on January 08
• Revision made to include ASN.1 codes
• Will be sent into CD ballot for International
  European Standard
• (TC 278 Plenary 24/25 Sept)
• All National Committees to support it !

35
CENOperational Requirements

• Result Fixed Operational requirements
• Status - Draft Final version based on eCall DG
  recommendations agreed 16-17 September.
• Will be sent into CD ballot for International
  European Standard (TC 278 Plenary 24/25 Sept)
• Still some open issues to be solved before the
  comments resolution meeting
• All National Committees to support it !

36
CENTPS supporting eCall

• TPS-eCall Third parties supporting eCall service
  (private services)
• - Proposal for an interface between SP and
  PSAPs
• - Agreement on the scope of the work
• - Document at initial stage
• - Interaction with the PSAPs needed
• Editor Mr. B. Flury-Herard
• (Bernard.Flury-Herard_at_developpement-durable.gouv
  .fr)

37
Standardisation progress (7)High Level
Application Protocols

• CEN TC 278 WG15
• Result High Level Application Protocols
• Status - Project Team will elaborate them
  within 5 months period
• Proposal under negotiation with DG ENTR