Versions Compared

Old Version 5

changes.mady.by.user Philippe Robin

Saved on

compared with

New Version Current

changes.mady.by.user Stephen Lawrence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Some initial collection of topics to cover, concerns and challenges, and how to structure the definition of the "big picture" Vehicle Data reference architecture.

Table of Contents

Big Picture

Warning
titleWARNING

Big Picture diagram below is out of date. See CCS PoC section for up to date version


look at this diagram

  • VSS2 is used for the description of the data content
  • it is proposed to re-use the container concept proposed by CVIM to encapsulate the data (the sample code in the box comes from CVIM)
  • both MQTT (currently used by various OEMs) and new options (like GraphQL, look at GENIVI AASIG work on the external data server) are used for the communication  between the in-vehicle part and the OEM cloud
  • both REST and WebSocket protocols are used for the communication between the OEM cloud, neutral server and 3rd party service


(star) From this outline below we have started defining example reference architectures and potential technologies.
Several of the later items however can be further analyzed.

0) Initial assumed technical  architecture ("block architecture")

...

  • Personalised vehicle data
    Personalised data is identifiable to a specific VIN and is needed for service offerings to individuals and fleets. It should be discussed how much of these use-cases should be supported by a technical solution:
    • Retrieval of the latest cached vehicle data from the OEM server on a request basis.
    • Allow 3rd party event subscriptions and send-out of notifications when new data is available.
    • Allow the retrieval of historical vehicle states, e.g. the data values of the last 12 hours.
    • Provide a socket type of streaming API with real-time data updates.
    • Allow the triggering of a vehicle status refresh by the 3rd party of an individual vehicle.
    • Allow data retrieval of a group of vehicles by a fleet owner instead of having to request data for each individual VIN.
  • Anonymised vehicle data
    Big Data that is distributed to 3rd parties at different update rates. Has to be enriched and analysed in order to provide insights e.g. for traffic information.


...

Initial ideas

Protocol for Vehicle -> OEM server
1) (W3C Gen 2)
2) Other?  MQTT, etc...
3) Are those proprietary protocols (i.e. unspecified in this project)?

...