JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project - On Hold |
We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies. |
This is a draft outline with placeholder texts to serve as a starting point for a project deliverable.
following above list of analysis criteria
TBA.
TBA.
The were three main factors to introduce the ExVe ISO standard:
The scope of the ISO standard is web services only, which means data offered by OEM backends. It assumes that OEMs have vehicle data available in their backend and applies no requirements on how the data collection is done.
A large part of the standard focuses on authorisation, in other words how user consent should be obtained and maintained. There are several categories of vehicle data; personalised (identifiable to a specific vehicle with a VIN), pseudonymised and anonymised. If we consider a vehicle data point as a resource, in each of these data categories the resource owner depends on the nature of the data and has specific authorisation requirements. All of the data categories are considered in this standard.
Apart from data retrieval the standard also provides requirements and methods for handling modification to the vehicle state through functions.
The documentation is provided by the ISO standardisation under a commercial license. The license can be obtained from www.iso.org for the following documents:
TBA.
TBA.
Content outline:
SensorIS (Unknown User (gururaja.n) )
TBA.
The ExVe ISO standard does not introduce a data model. In this aspect any data model analysed in this document would fit as a data model in the implementation of a ExVe compatible web service. No ExVe compatible interface that has been introduced to the market today uses any standardised data model.
The standard does however define requirements on the web service interface that is provided to 3rd parties. It has to be RESTful and use the JSON or XML schema. Furthermore the standard includes requirements on several aspects: URI definition, error handling, naming and interaction patterns. All of these are aimed to make the implementation for 3rd parties similar no matter what OEM web service is being consumed.
TBA.
TBA.
TBA.
TBA.
The contents consist purely of specification documents. These include detailed descriptions along with visual diagrams and logical workflow diagrams of how a ExVe web service should be defined. This also covers the system design on an architectural level, meaning how certain logic should be decoupled in different components to ensure a secure implementation of the authorisation process, resources and data access.
TBA.
TBA.
TBA.
TBA.
There is good support for the ExVe standard which is demonstrated by market launch of ExVe compatible web services by several European OEMs already. European OEMs agreed to adopt the ExVe concept in 2016 which was followed by the finalisation and publication of the ISO standard in Q1, 2019.
TBA.
TBA.
TBA.
TBA.
TBA.
TBA.
TBA.
TBA.
TBA.