Page History

...

For each link in data flow architecture
- (Specify actors involved)
- Identify data set (limitations, + non-functional requirements)
- Identify data protocol

4) Data needs

What: Define the different categories of 3rd party use-cases and the different technical needs for consuming the data.

• 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)?

...