Streamlining Python Development: A Guide to a Modern Project Setup
EENA 2017 - eCall & Third Party Service eCall: update & remaining issues
1. eCall and Third-Party Service eCall:
update and remaining issues
Andy Rooke
Technical Implementing
Officer
I_HeERO
EENA Budapest 2017
2. Agenda
• Current Status of eCall
• What is missing to allow eCall
deployment
• Lessons Learned Recommendations
• Conclusions
3. Status of implementing eCall
• 28 Member States all active
BUT it is dependent on the
level of technical know how!
• Mobile Network Operators
(MNO)
– Larger MNO now upgrading.
– Smaller MNO resisting upgrade
4. Status of implementing eCall
• Rapid expansion of the TPS eCall
this will continue 2017-2018
• I_HeERO with EENA providing
practical assistance
• Vehicle Makers getting on with the
task
– BUT
• SIMs sourced from anywhere in the
world can your PSAP make
international calls?
5. Status of implementing eCall
• TPS eCall is growing fast
– European car makers will have a solution by 2017-
2018
– Do you want to be accepting data over the phone?
• Standards are there use them EN16102
– Call numbers will increase, make sure quality is
embedded in your arrangement
– Who makes the decision on eCall that you are not
sure about?
– Make sure the operation of TPS eCall at a PSAP is at
worst cost neutral REMEMBER this is a subscription
service.
6. What is still missing?
• True engagement?
– Member states, some are better than others
– MNO’s in particular
• Small MNOs’ REMEMBER eCall is a TS12 it is a 112 call
the MNO is obliged to handle it correctly!
– Emergency Service in some member states are quite
complacent
• eCall is a fundamental change in alerting!
• Digital Information
• Who decodes it?
• Who moves the data around?
7. What is still missing?
• The understanding of eCall, its digital
• How will your operating procedures change because of
eCall
• How are you going to move data between agencies?
• eCall is the start of Internet of Things are you ready?
– Faulty Units
• DDoS
• PSAP
– eCall Stress Test
– Deal with rogue units
– Malicious call
8. Lessons learnt and Recommendations
• Minimum Set of Data (MSD), do you know
all of the formats that are required
(Additional data)?
• MSD, vehicle details, how and who will you
get these?
• SIMS (TPS or 112 eCall), coming from US,
Malta, Korea, what does this mean?
– Control room restrictions on outgoing calls
9. Lessons learnt and Recommendations
• PSAP must be ready by 1st October 2017
– Conformity Assessment –
• limited expertise to carry this out
– Look for suppliers who have certified equipment.
• PSAP level 2 dispatches,
– How to transfer the call and the data?
– I_HeERO Activity 4 leader has the answer!
10. Lessons learnt and Recommendations
• What does eCall sound like for an operator?
• Is it a silent eCall or a real eCall?
• Who has the authority to cancel an eCall?
– is this any difference from any normal silent 112
call?
• Is it a manual or automatic eCall?
– Is there a difference why should I care?
11. Lessons learnt and Recommendations
• How to deal with Malicious calls
• How to deal Faulty In-Vehicle Units?
• A multi vehicle crash how will you cope
• Tip: Geo-Locate new car show rooms are?
• Liability for eCall - BEST ENDEVOUR
12. Conclusions.
• PSAP level 1 ready for TPS eCall what will you
accept?
– CEN Standards & TPS eCall Contract
– You do not have to accept TPS eCall,
– TPS eCall is a subscription service, PSAP operation
should at the very worst be cost neutral.
– Some TPS eCall providers may try and charge PSAP
to handle their calls be vigilant!
• Data Sharing services
• Premium Telephone lines
13. Conclusions.
• The three elements of eCall have to be aligned
– OEM
– MNO
– PSAP
• Emergency Services are you eCall ready?
– Controllers trained
– Operational teams briefed
– Transfer of Data is Key – How to move data