Today, vehicle users want to make use of the added value services on their smartphone and integrate them into their vehicles. Use cases from vehicle data exchange can increase comfort and convenience for customers, improve products and services, and contribute towards achieving societal goals. This includes improving road safety, reducing fuel consumption, and facilitating traffic management and parking.
This development has led to increasing demands to access and use in-vehicle data from third parties. Customers have used many of these use cases.
Regulations concerning the access to in-vehicle data should be based on a clear and accurate understanding of the functioning of a vehicle, how data is generated and how access is made available on a vehicle interface, regardless of the data level
Vehicle manufacturers have started to deploy the Extended Vehicle model and believe that the technology used for accessing data is based on the best practices in the industry.
This is underpinned by the key principles of driver safety and security. They regard that the ISO Extended Vehicle model satisfies the FRAND principle: fair, reasonable, and non-discriminatory access to in-vehicle data.
The Extended Vehicle makes it possible to access vehicle data through a number of interfaces that can be used depending on the type of access requested:
1. On-board Diagnostics (OBD) interface for regulated emissions control, diagnosis, repair and maintenance.
2. Ad hoc communication interface under the responsibility of the vehicle manufacturer (e.g., applications in the field of cooperative intelligent transport systems).
3. Web interface for all other third-party services (e.g., remote diagnostic support).
The customer chooses whether they want to share their personal data. Each vehicle manufacturer decides on the technology used to make that data available to third parties on a non-discriminatory basis.
The solution is based on AWS which offers all the building blocks neccesary to build custom applications tailored to the needs of any organization. Storm Reply's IoT approach enables customers to start fast and then evolve and adopt their IoT usage over time. Features are added in a function focused approach to enable fast and risk-free growth. This ensures that the IoT adoption goes beyond POCs or MVPs as they build on a framework that prioritises security, governance and usability.
Fast and provable Results
The fundamental core features of the Platform rely on a framework designed by Storm Reply. This enables a fast, yet secure and scalable start.
Secure and under the customer's control
Security and access controls are implemented by design. All data stays in the customers ownership, is encrypted and auditable.
The underlying services of the solution are billed per usage only. This granular pricing enables constant cost optimizations and minimizes investment costs.
Thanks to the modular approach the IoT platform is extremely adoptable and flexible. As the platform is embedded into the AWS eco-system future innovations are available by design.
The available data points differ depending on the vehicle manufacturer and the equipment level of each customer’s vehicle. Bearing this in mind, the following scheme describes the approaches to providing access to relevant data depending on the requests of the third party.
The vehicle’s data is available on the vehicle manufacturer’s backend (OEM) via the Extended Vehicle interface selected by the manufacturer.
Level B refers to data that can be made accessible via an Extended Vehicle interface but it has not yet been transferred to this interface.
This is data generated by applications and hosted in a vehicle’s electronic control unit (ECU). These applications can be used to aggregate and process data onboarding.
When a stakeholder wants to provide a service using vehicle data or resources over
the air, a clear process must be given for the provider to submit their request to the relevant vehicle manufacturer. To that end, ISO (TC22/SC31/WG 6 Extended Vehicle) is finalising a draft technical report entitled: ‘Road vehicle - Extended Vehicle – Upstream process to develop services’.
This technical report describes a process of initiating and facilitating the communication between service providers and vehicle manufacturers. By doing so, service providers express their requests to access data and resources from the Extended Vehicle interfaces for developing services.
A vehicle is not a smartphone on wheels, nor is it a personal computer that can be rebooted if a problem occurs while driving. Furthermore, it is not a software platform which primarily aims to generate, process, share and receive data. From a technical point of view, transferring additional data points requires deep modifications of the physical architecture and the software of the vehicle, which in turn will increase the computing power of the vehicle. Such measures have a significant impact on the resource’s optimisation and on the environment. .
Any policy initiative regarding access to vehicle data for third party services must take these limitations into consideration, and the consequences they may have on a customer’s ability to choose a vehicle which best suits their needs.
Within the Reply Group, Autonomous Reply is the specialist in the specification, development, integration and validation of autonomous and connected embedded systems. We offer a portfolio of services covering the entire value chain, from strategy definition to implementation and operational safety. Autonomous Reply's services include consulting, real-time systems engineering, software development and integration of autonomous solutions.