- Twitter 06Apr
Why do we need Vehicle Data Hubs? https://t.co/Cldkirblgx #connectedcar #vdh ...
- Twitter 30Mar
RT @PTOLEMUS: What is a Vehicle Data Hub (VDH)? The only way to scale the use of connected car data #cardata ...
- Twitter 29Mar
RT @IoTwatcher: @PTOLEMUS: 'What is a Vehicle Data Hub (VDH)? The only way to scale the use of connected car ...
- Twitter 29Mar
RT @dwnews: Why is Germany's #coronavirus death rate so low compared to other countries? As @c_drosten — one of the country's ...
- Twitter 28Mar
What is a Vehicle Data Hub (VDH)? The only way to scale the use of connected car data #cardata #connectedcar ...
We just published a free eCall Briefing – you can download here
PTOLEMUS eCall Briefing
eCall is becoming a standard feature of connected services provision.
OEMs, telematics service providers, insurance companies and roadside assistance companies increasingly use eCall as a gateway to other connected services. But due to regulations and complex procedures, implementing eCall is different and more complex than any other connected service.
Before the 2018 EU-wide eCall mandate, obligating all OEMs to equip new type-approved vehicles in Europe with an embedded eCall device, the car manufacturers were already offering Private eCall via third-party service providers such as Bosch, IMA, Allianz and OnStar.
In most cases, the same third-party service provider also provides other connected services to the OEM such as bCall, SVT/R and concierge services. The OEMs often bundle these services in the connected service packages.
By establishing relationships with PSAPs (Public Safety Answering Point) such as 112 emergency call centres, police and emergency medical service centres and appropriate local authorities, the B2B2C providers have developed necessary competences and geographic coverage to supply the OEMs worldwide.
After the eCall mandate, TPSPs face new requirements to be compliant not only to the EN standards but also to local PSAP’s requirements. Only in this way can they work directly with PSAPs and provide compliant TPS eCall across Europe. OEMs are currently actively looking for such compliant TPSPs to provide TPS eCall as well as a wider range of connected services at a European level.
However, the task to create and implement TPS eCall Europe-wide is challenging, as PSAPs often have different service requirements and country-specific emergency service protocols with different technical standards and design. In most countries, the process for TPSPs to set up their service is not standardised and requirements are not defined, many still rely on negotiation. In countries where PSAP structure is decentralised or fragmented, the process is even more time-consuming and complicated.
This briefing explains the regulatory requirements for public and TPS eCall, summarises the current deployment of TPS eCall in Europe and analyses issues and opportunities for TPS eCall.