Page History

...

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

...

The were three main factors to introduce the ExVe ISO standard:

1. Increasing demand from 3rd parties to access vehicle data and functionality. The workaround to date has been installing additional hardware into the car, which has on one hand has limited scale but more importantly raises the question how security and safety is being handled.
2. OEMs have already equipped vehicles with telematics units and built up IT-infrastructure to handle data connectivity between vehicles and backend systems. To some extent OEMs have offered external parties to integrate with vehicle data using web services, this has been done however without any guidelines or requirements on the system design.
3. As there is active data sharing already, either through external hardware or individual OEM web services, there is a need to define a design and requirements to ensure that security, safety and data privacy is handled with best practices common methods.

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.

Licenses

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:

• ISO 20078-1 Road Vehicles – Extended Vehicle (ExVe) web services – Part 1: Content
• ISO 20078-2 Road Vehicles – Extended Vehicle (ExVe) web services – Part 2: Access
• ISO 20078-3 Road Vehicles – Extended Vehicle (ExVe) web services – Part 3: Security
• ISO/TR 20078-4 Road Vehicles – Extended Vehicle (ExVe) web services – Part 4: Control

CVIM (Unknown User (benjamin_klotz) )

...

• Need for shared data (model) description
• Tree hierarchy equivalence
• VSS specification structure and content
• Terms/nomenclature/definitions ("what is a data model, specification, ..." - reusing Daniel's infographic)
• Beyond: Deeper analysis of data characteristics - data ontologies
• (Open) Licensing
  • Common data model - can companies agree?
  • ...plus proprietary and function-specific extensions (still with common format and tooling)
• Car-network focus vs. generic usage
• VSS principle can be applied in network - ECU-internal, intra-ECU, and cloud connected services
• W3C protocol definition and usage of VSS
• Potential for VSS use in CCS.

SensorIS (Unknown User (gururaja.n) )

...

Extended Vehicle (ExVe) ISO standard  Unknown User (kevinval)

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 consumedTBA.

CVIM (Unknown User (benjamin_klotz) )

...

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

TBAThe 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.

CVIM (Unknown User (benjamin_klotz) )

...

Extended Vehicle (ExVe) ISO standard Unknown User (kevinval)

TBAThere 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.

Table comparison (if applicable)

...