230 likes | 526 Views
eCall implementation in Finland. eCall - what and why. eCall is an automatic in-vehicle emergency call service developed in the European Union The benefits of the eCall system are mainly based on the faster relaying of important accident information
E N D
eCall - what and why • eCall is an automatic in-vehicle emergency call service developed in the European Union • The benefits of the eCall system are mainly based on the faster relaying of important accident information • Precise location, time and type of the accident • The system itself will not reduce the number of accidents. • The main objective is to improve response times in the case of a traffic accident and save lives by faster help
eCall implementation in Finland Finland is at forefront of eCall deployment • 1st EU member state to sign eCall-MoU • PSAP infra ready within the next couple of years • national PSAP data system supports eCall-service since end of the year 2005 • Public eCall test service started in June 2005 • validating the functionality of eCall unit communications • 1st detailed accident study ready in November 2005 • Recommendations of the eCall Driving Group have been followed
Active eCall promoters and in Finland • ITS Finland • Initiator of the eCall-project • Ministry of Transport and Communications • Financier of r&d activities • Signer of eCall-MoU • Ministry of the Interior and Emergency Response Centre Administration • Realising of the eCall-service • VTT Technical Research Centre of Finland • Realising and maintaining of the test bench • Impact studies on eCall • Indagon Ltd. • Developer and manufacturer of the eCall terminal prototype
Impacts of eCall – Fatalities (1/2) • eCall could prevent 5 – 10% of the fatalities in Finland (VTT 2005) • Biggest effect expected on minor rural roads, at night time, in off-peak traffic (VTT 2005) • Benefit/cost ratio between 0,6-2,6; most likely more than 1 (VTT 2005) • A decrease of 5 – 15 % in fatalities on a pan-European level (EMERGE 2004)
Impacts of eCall – Fatalities (2/2) In addition to the 4.6%, a similar amount of the fatalities may have been prevented
eCall communications Test Bench • Test bench in use since June 2005, with registered users from 12 countries so far, including: • 3 car manufacturers • eCall-terminal developers • Simulated Emergency Centre • Simulated Service Centre • Simulated eCall vehicle terminal • Communications in real network • Trials with an eCall terminal prototype
eCall Testing activity • The test system can be contacted through eCall web pages for communications testing under the customer's own control • The service is targeted for everyone wanting to test the functionality of eCall terminals • Free of charge during 2005 - 06
eCall next steps (1) • Extension of the test environment to be a part of the pan-European certification procedure in co-operation with the European commission • also physical features, easiness of installation etc. • Language support • Cross-border data exchange • Other current recommendations of the eCall Driving Group
eCall next steps (2)eSafety Forum Implementation Road Map Working Group 18 October 2005
Finnish principles to reach the rapid implementation of pan-European eCall • Vehicle to PSAP communications are implemented utilising existing communications technologies, networks and standards • In future, the technology will be developed further following the standardisation work • Service centre to PSAP messaging is secure and, at the same time, enables free EU-wide competition of service centre business • EU-wide interoperability of terminals is ensured by creating a centralised EU-level terminal certification • EU member states agree on a rapid EU-wide and interoperable implementation of eCall at PSAPs • eCall terminal will be made mandatory in all vehicles in a rapid schedule
Further information - contacts • VTT Techinical Research Centre of Finland • Raine Hautala, raine.hautala@vtt.fi • Timo Laakko, timo.laakko@vtt.fi • Ministry of the Transportation and Communication • Anu Lamberg, anu.lamberg@mintc.fi • Ministry of the Interior • Mikko Jääskeläinen, mikko.jaaskelainen@intermin.fi
Messages • The minimum dataset (MDS) contains only the mandatory data items. • The full dataset (FDS) includes at least the mandatory data items. • FDS message is sent in XML format. XML schema is used to describe the XML structure and content of the message • MDS message is encoded very tightly to support the sending over voice connection using DTMF
MDS message format • MDS encoding (19 bytes => 38 DTMF signals): • DTMF codes: 0-9, A-D, #, *
eCall In-Vehicle Terminal • Testing of service centre and PSAP operation • Creating and sending MDS and FDS messages • Creating and editing accident data for testing different cases • Operation in error cases: • connection failed to service • response delays • server returns error code • Configurable • delays, retries, accident data, terminal preferences • Logging sent messages
Service centre • Testing of in-vehicle terminal and PSAP operation • Validating FDS messages • structure and content • Forwarding and completing FDS messages to the PSAP • creating additional information messages • Generation of error cases: • delayed response • returning error codes • Logging received and sent messages
PSAP • Receiving messages from In-Vehicle Terminal and Service Centre • Validating and encoding of incoming messages • Testing of terminal and service centre operation • Logging received messages and errors