Some initial collection of topics to cover, concerns and challenges, and how to structure the definition of the "big picture" Vehicle Data reference architecture.
Big Picture
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
0) Initial assumed technical architecture ("block architecture")
...