This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
This document was updated with contributions of the following EENA members:
Name Organisation
Bergonzi, Luca Beta80 Group
Bishop, Cathy OnStar
Lumbreras, Cristina EENA
Maher, Ann OnStar
Moseley, Russell Voltdelta
Novak, Gorazd Iskratel
Öörni , Risto VTT Finland
Rooke, Andy Ertico
Verlinden, Thom National Police, NL
Legal Disclaimer This document is authored by EENA staff members with contributions from individual members of EENA and represents the views of EENA. This document does not represent the views of individual members of EENA, or any other parties.
This document is published for information purposes only and it does not declare to be a statement or interpretation of EU law or the national law of EU Member States. This document is entirely without prejudice
to the views of relevant national statutory authorities and their legal functions and powers, whether under EU law or the national law of their Member State. Accordingly, under no circumstances may reliance be placed upon this document by any parties in compliance or otherwise with any applicable laws. Neither may reliance be placed upon this document in relation to the suitability or functionality of any technical specifications, or any other matters discussed in it. Legal advice, technical advice and other advice as relevant, may be sought
2.1 Background ......................................................................................................................... 5 2.2 EU Recommendation on eCall ................................................................................................ 5 2.3 eCall Legislation ................................................................................................................... 6 2.4 Chronology .......................................................................................................................... 7
3 Approaches to provide eCall ............................................................................................................ 7 4 Means to initiate an eCall ............................................................................................................... 8 5 eCall service stakeholders ............................................................................................................... 8 6 Minimum set of Data ...................................................................................................................... 9 7 Table of relevant applicable standards ............................................................................................ 10 8 Pan European eCall ...................................................................................................................... 11
8.7 PSAPs Conformance Testing ................................................................................................ 16 9 Third party services supported eCall .............................................................................................. 17
9.1 Overview ........................................................................................................................... 17 9.2 Operational procedures and agreements for communication between PSAP and TPSP ................. 19 9.3 Technical communication with PSAPs .................................................................................... 20
10 The Harmonised eCall European Pilot Project (HeERO) ................................................................... 21 10.1 Description ........................................................................................................................ 21 10.2 National implementations .................................................................................................... 22
10.3 HeERO Recommendations ................................................................................................... 28 11 NG eCall .................................................................................................................................. 31 12 Recommendation to stakeholders ............................................................................................... 33
12.1 Pan European eCall............................................................................................................. 33 12.2 Third Party Services supported eCall ..................................................................................... 33
Road safety is one of the major elements of the European Union’s transport policy. In 2011 around
30 000 people were killed and more than 1.5 million injured in about 1.1 million traffic accidents on
EU roads. In this context, eCall can significantly contribute to the reduction of road fatalities and
alleviation of severity of road injuries.
Therefore, the harmonised implementation of an interoperable EU-wide eCall service in the EU has
been in the agenda of the Commission since 2005.
Given the absence of any significant progress in the voluntary deployment of eCall by the end of
2009, the Commission decided to conduct an Impact Assessment in order to assess the most
appropriate policy option to implement the EU-wide eCall service in Europe.
2.2 EU Recommendation on eCall
The Commission unveiled on 8 September 2011 its strategy on regulatory measures for eCall,
together with the adoption of the first part of this strategy, which consisted of a Commission
Recommendation on support for an EU-wide eCall service in electronic communication networks for
the transmission of in-vehicle emergency calls based on 112 (eCall) 1.
In its non-legislative resolution report on eCall: a new 112 service for citizens adopted on 3 July
2012, the European Parliament stated that eCall should be a public EU-wide emergency call
system, embedded in the vehicle and based on 112 and on common pan-European standards. It
urged the Commission to submit a proposal within the framework of Directive 2007/46/EC2 in
order to ensure the mandatory deployment of a public, 112-based eCall system by 2015 in all new
type-approved cars and in all Member States.
On 26 November 2012, the Commission adopted the Delegated Regulation (EU) No 305/2013
supplementing Directive 2010/40/EU of the European Parliament and of the Council with regard to
the harmonised provision for an interoperable EU-wide eCall.
1 http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:303:0046:0048:EN:PDF 2 Full title: "Establishing a framework for the approval of motor vehicles and their trailers, and of
systems, components and separate technical units intended for such vehicles (Framework
Conformance testing of PSAPs is considered as an important part of the eCall deployment in
Europe. The delegated regulation 305/2012 of the European Commission8 states that the member
states have an obligation to designate the competent authorities for assessing the conformance of
PSAPs to the specifications of eCall:
“Conformity assessment Member States shall designate the authorities that are competent for
assessing the conformity of the operations of the eCall PSAPs with the requirements listed in Article
3 and shall notify them to the Commission. Conformity assessment shall be based on the part of
the standard ‘Intelligent transport systems — eSafety — eCall end to end conformance testing’ (EN
16454) that relates to PSAPs conformance to pan-European eCall.” (European Commission 2013,
Article 4)
The same regulation also states that the PSAPs must be able to demonstrate conformity with the
European standards. The first part of article 7 of the regulation states that the conformity
assessment must be based on the tests included in the related European standards EN16454 (see
section 7):
“Rules on liability
The eCall PSAPs must be able to demonstrate to the competent authorities that they meet all
specified conformance requirements of the eCall standards listed in Article 3(1) [EN16062 and
EN16072, author’s own note] in respect of the part(s) of the system under their design and/or
control. They shall be liable only for that part of the eCalls for which they are responsible, which
starts at the time the eCalls reach the eCall PSAP, in accordance with national procedures”.
At present, specifications of conformance tests for eCall are available as a CEN technical
specification (CEN TS16454) but not as a full EN standard. The EN standard on conformance
testing is currently under approval (CEN 2014), and it is expected to be available within a few
months.
It should be noted that also other testing than conformance assessment may be necessary to
achieve a functional and high-quality eCall service. For example, it may be necessary to test the
performance of the PSAP solution, its reliability and its correct operation in exceptional but possible
situations (e.g. a situation with a large number of simultaneous eCalls being received, support for
all defined MSD versions, presentation of MSDs with optional additional data, etc.).
8 European Commission. 2012. Commission delegated regulation (EU) No 305/2013 of 26 November 2012 supplementing Directive 2010/40/EU of the European Parliament and of the Council with regard to the harmonised provision for an interoperable EU-wide eCall. http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2013:091:0001:0004:EN:PDF
The experience gathered in the member states participating in HeERO was used to identify the
challenges and enablers for eCall deployment and to prepare recommendations for eCall
deployment in Europe.11 The way the recommendations were developed is presented in the
following figure. The recommendations were developed taking into account the barriers and
enablers for eCall identified in HeERO D6.2 (Öörni and Brizzolara 2014), the solutions to eCall
deployment barriers identified in HeERO D6.4 (Öörni et al. 2014) and the results of other work
packages of HeERO.
Development of recommendations for EC, member states and other stakeholders (Öörni et al.
2014).
The recommendations given by the HeERO project are aimed at EU member states, European
Commission, standardisation organisations and other stakeholders. The recommendations are
presented in the following tables.
The recommendations for member states intending to implement eCall are summarised in the first
table (Öörni 2014).
Recommendation
Id Description
MS1 Increase the awareness of stakeholders on member state level on impacts, benefits and costs of eCall and the implementation options available. Utilise the results of HeERO and HeERO2 projects, literature available on the subject and other
11 Öörni, R. 2014. Recommendations on implementation and operation of eCall. Deliverable D6.5 of HeERO project (Harmonized eCall
European pilot). http://www.heero-pilot.eu/ressource/static/files/heero_wp6_del_d6-5-recommendations-on-implementation-and-operation-
of-ecall_v0-5.pdf [accessed 7th July 2014]
Öörni, R. and Brizzolara, D. 2014. eCall Deployment enablers and opportunities and challenges: final report, Deliverable D6.2 of HeERO
available information sources such as iMobility effects database
MS2 Communicate the impacts and implementation options for eCall to the key stakeholders on member state level
MS3 Organise round table discussions and working groups on eCall on member state level
MS4 Identify a key stakeholder which monitors and possibly also coordinates the overall process towards eCall deployment and formally or informally takes responsibility for solving problems and for the whole process
MS5 Establish a national eCall platform
MS6 Analyse the architectural and deployment options available for eCall. Utilise the results of HeERO and HeERO2 projects, eCall standards and literature available on the topic
MS7 Develop and publish a national eCall implementation roadmap or an implementation plan. The
roadmap should describe - the actions necessary to achieve a functional eCall service chain - the roles of different stakeholders
- the schedule for eCall deployment including the various elements of the deployment process and eCall service chain (especially: eCall discriminator and PSAP upgrades)
MS8 Encourage and facilitate mutual cooperation and technical support between stakeholders within a
member state
MS9 Implement the eCall discriminator in mobile networks; cooperate with the mobile network operators and the national telecommunications regulator
MS10 Implement eCall reception and processing capabilities in PSAPs. Use the architectural solutions
defined in the national eCall implementation roadmap or implementation plan
MS11 Perform eCall end-to-end tests on member state level to ensure correct functioning and reliable operation of eCall. The tests should cover different mobile network operators, different PSAPs and different geographical areas.
MS12 Perform eCall interoperability tests. Integrate interoperability tests with the end-to-end tests.
MS13 Share and publish the results of the interoperability tests carried out after HeERO and HeERO2 – for example in the context of EeIP or in international conferences.
MS14 Monitor the status of retrofit IVE products and consider actions, if significant challenges or risks are encountered
MS15 Consider centralisation of reception and handling of eCalls to a few key PSAPs as an interim solution
if it is difficult to implement eCall reception or processing capabilities in all PSAPs at once.
MS16 Consider the use of specifications defined in EN16102 if TPS-eCall is integrated with PSAPs.
MS17 Analyse the impact of the network echo canceller disabling tone on the reliability of MSD transmission
and implement NEC disabling tone in PSAPs, if clear improvement can be observed
MS18 Analyse the reliability of eCall on member state level and the factors contributing to it. Implement necessary changes to the communication networks or to the PSAP (for example, changes to codecs used or transcoding between codecs along the call path from IVE to PSAP)
MS19 Monitor the service quality of E112 emergency calls; analyse the status of national regulations concerning the coverage of the mobile networks and handling of 112 calls, and implement changes if necessary
MS20 Provide training appropriate training for PSAP staff
MS21 Initiate a MSD retransmission when the first MSD transmission in the beginning of the connection fails.
MS22 Use the voice connection to communicate with vehicle occupants if the MSD transmission in the beginning of the connection fails.
MS23 Support development of certification scheme for eCall IVE and eCall in-band modem components.
MS24 eCall MSD transmission is not always successful. Take this into account when preparing national guidelines for operation of eCall (for example, guidelines for call handling or risk assessment in PSAPs)
MS25 Reduce the number of link layer acknowledgements (LL-ACKs) transmitted by the PSAP after a
successful MSD transmission or omit transmission of LL-ACK completely to reduce voice channel blocking time.
MS26 Take silent calls into account when developing national guidelines for operation of eCall (for example, guidelines for call handling and risk assessment)
MS27 Use the information available via voice connection such as background noise in case no one in the
MS28 Use the information included in the MSD in handling of silent calls and calls in languages not understood by the PSAP.
MS29 Validate the location of the caller using network based positioning available for all E112 calls. Use network based positioning in case where the position included in MSD cannot be trusted.
MS30 Educate car users on the operation and correct use of eCall with information campaigns.
MS31 If necessary, implement validation of incoming calls before connecting them to a PSAP operator.
MS32 Document the erroneous operation of mobile phone models affected by the problem and contact the equipment manufacturers.
MS33 Ensure that mobile networks support E.164 numbers with the length up to 15 digits as defined in GSM and 3G specifications. The problem can likely be solved with a software update of the mobile
network affected by the problem.
MS34 Encourage participation in eCall interoperability events.
MS35 Participate in international cooperation in the context of EeIP to exchange information and best
practises and to contribute to further development of eCall
MS36 Define appropriate call handling procedures for automatic and manual eCalls (for example, handling of silent calls and calls in languages other than the official languages of the member state)
MS37 Use HeERO training manuals when providing training to PSAP operators
Recommendations for the European Commission are summarised in the Recommendations Table 2 (Öörni 2014). Recommendation
Id Description
EC1 Complete European level regulation which mandates the implementation of eCall in PSAPs, communication networks and new type-approved vehicle models
EC2 Monitor the status of retrofit and OEM IVE products and consider regulatory actions if significant risks or challenges are encountered
EC3 Support the development of certification scheme for eCall IVE and in-band modem components (this work is currently being carried out in HeERO2)
EC4 Consider the need for development guidelines for retrofit IVE products; support the development of guidelines for example by European eCall implementation platform (EeIP)
EC5 Initiate and support further research and related road-mapping work on the long-term evolution of eCall including analysis of options available to manage the lifecycles of vehicles and wireless communication networks
EC6 Facilitate the cooperation of eCall stakeholders and further development of eCall specifications (such as specifications for PTI) in the context of EeIP
EC7 Continue support to standardisation and further research on eCall taking into account - the work carried out by ETSI STF 456 and IETF working group ECRIT on the future
development of eCall - the need to optimise the acknowledgement mechanism of eCall MSD transmission to reduce
voice channel blocking time - the need to ensure reliable operation of eCall such as the reliable operation of MSD
transmission (including retransmission, analysis of the correlation between outcomes of successive MSD transmissions during the same call is recommended)
- needs for recommendations on the service quality acceptable for eCall (such as the acceptable MSD success rate)
EC8 Support dissemination of information on eCall (examples of current activities performing eCall dissemination: iMobility Challenge, HeERO, iMobility Support and EeIP)
EC9 Support dissemination of information on impacts of eCall (examples of current activities performing eCall dissemination: iMobility Challenge, HeERO, iMobility Support and EeIP)
EC10 Continue monitoring the deployment of eCall as a part of monitoring related to the European ITS
directive
EC11 Encourage sharing and publication of the results of eCall interoperability tests to be carried out after
HeERO and HeERO2 projects, for example in the context of EeIP or international conferences
EC12 Analyse the availability and regulatory status of dormant SIM cards and decide on actions necessary
EC13 Support the member states in their efforts to communicate the functionality and correct use of eCall to citizens – for example by providing information material
EC14 When supporting national eCall pilots, encourage participation in eCall interoperability events
EC15 Consider the need to provide guidelines for automatic and manual triggering of eCall
EC16 Funding of eCall deployment in member states by DG MOVE and the TEN-T programme (note: the funding scheme has to be aligned with the needs of member states)
Recommendations for standardisation organisations are described in the third table of
recommendations(Öörni 2014):
Recommendation
Id Description
SDO1 Include references to CEN standards in the ETSI/3GPP standards when necessary. For example, - include clear references to timers mentioned in Annex A of EN16062 in ETSI TS 126 267
SDO2 Provide specifications for support of eCall functionalities in 4G (LTE) networks taking into account the
work carried out by ETSI STF 456 and IETF working group ECRIT
SDO3 Provide a long-term roadmap for the evolution of eCall taking into account the lifecycles of vehicles and wireless communication technologies and including the means available to maintain the compatibility of IVE with wireless networks and PSAPs over extended period of time
SDO4 Develop CEN TS 16454 into European standard
SDO5 Monitor the work being carried out on periodic technical inspection of eCall IVE and implement changes to standards if necessary; participate in the work of EeIP task force PTI if necessary
SDO6 Continue support for organising eCall interoperability events
SDO7 Clarify the role and use of the LL-ACK in CEN and ETSI standards: - provide guidelines on the numbers of LL-ACKs and HL-ACK - the fact that LL-ACK is not mandatory should be made clear to developers of IVSs and PSAPs
SDO8 Update the annex A of EN15722:2011 or add an errata to the standard (some values in the example presented in Annex A are not possible according to the ASN.1 specification presented in the
standard)
Finally, two recommendations were provided for other stakeholders such as system developers -
DEV2 Use dead-reckoning to support GNSS in determining the position of the vehicle. This is expected to improve IVE performance in case of short periods of unavailability of satellite signal (such as tunnels).
The recommendations presented in Tables were written in the beginning of 2014. In other words,
they are based on the results of the HeERO project and the information available at that time but
they do not take into account the results which have become available later such as the results of
HeERO2. The mapping between the challenges for eCall deployment and the recommendations
addressing the challenges is provided in (Öörni 2014).
11 NG eCall
The mobile network operators (MNOs) are shifting to Long Time Evolution (LTE) also referred to
as a 4G mobile technology. LTE networks are built on Packet Switched (PS) technologies,
where the normal modus operandi is transmitting packets of data instead of establishing a
National Government Establishing the model of eCall reception and handling
National Telecommunications regulatory authority (NTRA)
Checking that all legal requirements are complied, for example , Telecoms operator to provide the eCall flag
Mobile network operators Implement the eCall flag
Treat eCalls as 112 emergency calls (free of charge, priority, national roaming, etc.) Providing the right routing based on eCall flag following the instructions of the National Authorities Providing SIM cards for the IVE (based on commercial agreements)
Competent Authorities of
Emergency Services
Make sure that emergency services have the necessary means (including
budget) to adapt their systems to eCall Solve multi-languages cases
Emergency services and their providers (e.g. Software Provider)
Infrastructure set-up (e.g. integrate eCall into the PSAP systems) Verify that eCall information is correctly received Training of operational and technical staff
Establishment of operational protocols
Car Industry and their suppliers Equip vehicles with eCall following the relevant EU Regulations Ensure the functionality of the in-vehicle system Comply with EU Regulations on data protection and free consumer choice
12.2 Third Party Services supported eCall
Stakeholder Action
National Government Regulating the co-existence of TPSP based solutions, today present on the European market [this is not mandatory for Member States]
National
Telecommunications regulatory authority (NTRA)
Not involved in the TPSP eCall
Mobile network operators Providing SIM cards for the IVE (based on commercial agreements)
TPSP Provide appropriate number of call centres and trained operators available 24/7 Creation of a PSAP database Work with PSAPs to establish protocols to communicate with PSAPs Establishment of protocols to communicate with PSAPs (if the PSAPs agree) Establishment of a Multi-language system
Filtering of false alarms (Call Center based services) Development of an interface which offers a safe way to transmit detailed crash data to PSAPs (if PSAPs agree):
Clear and structured data transmission Exact and detailed location description (address, map, coordinates)
Vehicle information (car model, color, number plate) Sensors data visualisation (by automatic eCall)
Multiple languages
Competent Authorities of Emergency Services
No specific equipment needed. TPSP will adapt its equipment to the needs of PSAPs (if PSAPs agree)
Emergency services and their providers (e.g. Software Providers)
Establishment of operational protocols Training of operational and technical staff
Car Industry and their suppliers
Ensure the functionality of the in-vehicle system Comply with EU Regulations on data protection and free consumer choice