1 / 16

Rasmus Lindholm DG eCall eCall expert meeting 23 March, Budapest

Towards eCall implementation in Europe. Rasmus Lindholm DG eCall eCall expert meeting 23 March, Budapest. eCall as Public Service. Minimum Set of Data – DG eCall. eCall service chain. end2end Performance criteria. Suggested reliability for full eCall service chain 90% in 2010

gisela
Download Presentation

Rasmus Lindholm DG eCall eCall expert meeting 23 March, Budapest

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Towards eCall implementation in Europe Rasmus Lindholm DG eCall eCall expert meeting 23 March, Budapest

  2. eCall as Public Service Minimum Set of Data – DG eCall

  3. eCall service chain

  4. end2end Performance criteria Suggested reliability for full eCall service chain • 90% in 2010 • 95% in 2015 • 98% in 2020

  5. end2end Performance criteria Suggested performance criteria for timing in the eCall service chain

  6. Suggested performance criteria for deploying eCall service • Timing for triggering an eCall • A maximum of 10 seconds from the accident has occurred to the transfer of the eCall from the In-Vehicle System to the communication modem • Automatic triggering • Preventing false calls by triggering based on agreed sensor deployments and thresholds • Manual triggering • Preventing false calls through the HMI e.g. by • holding the eCall bottom down for three seconds • push it twice within 5 seconds • Location accuracy • Satellite based positioning performance – currently as a minimum: • ≤ 50 meters (in 50% of all cases) • ≤ 100 meters (in 95% of all cases)

  7. Performance criteria IVS - MNO - PSAP • Same as for 112 and E112 • The emergency call should be given the highest priority through the mobile network • Transmission time for voice and data should be no more than 4 sec - UK requirement for 112. Average today being 6 sec. • Transmit voice and data to the nearest PSAP • Reliability for transmission • 90% in 2010 • 95% in 2015 • 98% in 2020 • Full Roaming capabilities

  8. Performance criteria for PSAP • Map accuracy • 15 meters – measured against WGS84 • Road geometry – lowest local level • Road naming – Each road must have a name • Operational procedures • Answering incoming emergency calls • Evaluation of incoming calls • Routing calls to dispatching centres or direct dispatch of emergency unit • Timing • ≤ 10 Sec. for voice response • ≤ 10 Sec. for receiving the MSD and visualising location

  9. eCall from a PSAP perspective – What to expect • Instantaneous contact with the user through voice link • Detailed information via the MSD to: • Immediate detection of incident • reduce interview time • Visualise the precise location of the incident • Dispatch the right emergency service vehicle to optimise the emergency response • Obtain more information if needed via Service Provider to reduce “clean-up” time • Can use eCall to build additional applications that can help the emergency operators

  10. PSAP Requirements • Implement and operate 112 and E112 • data receiving capabilities, availability of digital map • Implement MSD decoder • Implement PSAP XML data viewer to visualise the information provided in the MSD • Ensure that both 112 Voice and MSD reach the same PSAP operator – could be a private body operating under the control of a emergency authority • Training of operators

  11. PSAP estimated yearly workload • Example OnStar US • 3.5 million users • 3.500 Automatic eCalls/year • 80.000 Manual eCalls/year • European Union • 170 million Cars • Automatic eCalls/year up to 170.000 (1%) • Manual eCalls/year up to 4 mill (3%) Incl. false calls?

  12. ExampleSpain • 98.243 accidents/Year (2004) - 17 PSAPs in Spain 1 call/accident=16 Automatic eCalls per day per PSAP • 24 Million vehicles in Spain – estimated that 1% will make a unprovoked/ automatic eCall per year = 39 automatic calls pr. day pr. PSAP • 24 Million vehicles in Spain – estimated that 3% will make a manual eCall per year either real or by mistake = 117 Manual eCalls per day per PSAP Average 172 eCalls per day per Spanish PSAP

  13. ExampleMadrid • Number of 112 calls in Madrid (one PSAP) in 2004 = 4 mill calls ~ 11000 calls per day • Average number of eCalls Madrid = 172 (probably higher due to the number of vehicles in Madrid) • Increase in number of calls for this PSAP ~ 1,6%

  14. Standardisation • Transport protocol – ETSI_MSG • In-band modem • USSD – Unstructured Supplementary Services Data • MSD Content • Timestamp • Location including direction of travel • Vehicle identification • Service provider identifier • eCall qualifier

  15. Next steps • Set up working group with the objective to define yearly amount of eCalls • Finalise papers from all sub-working groups • Draft eCall recommendations • Performance Criteria • Transport protocol • MSD Content • In-vehicle specifications • Business case – Input from different stakeholders • Circulate to DG eCall for final comments • Final DG eCall meeting 24-25 April, Brussels • Final eCall recommendations to the eSafety Forum end May 2006

  16. We need your data and help! Rasmus Lindholm r.lindholm@mail.ertico.com www.esafetysupport.org

More Related