Philippe Robin welcomes everyone and hands over the mic to Kevin Valdek
slide deck for this workshop is here
## Project overview
Kevin: this is the presentation Gunnar and I delivered in the Automotive World webinar last week, recording is available
- slide #4: Project charter
- Even though cars are connected, they are limited to specific OEM/brands
- A lot of ideas and start ups introducing new services…
- We want to harmonize these activities… Define building blocks with flexibility for common solutions… Define data exchange and access
- slide #5: Vehicle data
- not limited to specific types but clustered by anonymity (personalised, pseudonymized, anonymized)
- slide #6: Services / Needs
- up-to-date data, typically telematic through a cloud server, but also bulk on big data
- Data Model
- slide #9: Common data model
- the industry needs this (different implemenations for each OEM… This is to avoid this situation)
- Gap analysis in the CCS project (CVIM, SensorIS, ISO20078, Android Automotive, VSS) in 2019
- slide #10: Vehicle Signal Specification (VSS)
- VSS is at the core of the CCS project
- slide #16: Value exchange formats
- proposed protocol to group and exchange VSS data
- slide #18: capture data in vehicles
- ECUs speaking VSS2 (SOME/IP, DDS, HTTP/REST) or current bus translation
- slide #19: cloud transfer & storage
- Transfer/Storage with the W3C defined protocol Gen2, "Gen2" is a vehicle API over HTTPS and WebSockets + data lake based possibly on object storage in a later stage
- Buffering (high frequency, poor connectivity…) to take into account
- slide #22: Neutral servers and data marketplaces opportunity included (in accordance to ISO20078) or simple 3rd party access
discussion on framework architecture
|6||## proof-of-concept demos|
Demo #1 - OEM cloud
- Ulf: shows a Cloud and Connected services demo involving 3 components:
- data server (W3C Gen2),
- data base (Open Vehicle Dataset Server a.k.a. OVDS)
- CCS vehicle client
- Data server can be accessed through multiple protocols (HTTP, WebSockets) with VSS(2) data (but open to use other compatible domains - with a service manager)
- Data base is a SQL database with a VSS-to-DB adapter
- CCS client sits in between and creates a list of all VSS leaf nodes and issues read/write requests to the Gen2/OVDS servers
Demo #2 - Vehicle data generation
- slide deck is here
- Stefan Vysocki (from the GENIVI AASIG Vehicle Data / VHAL project) shows a demo of a vehicle data feeder using a vehicle simulator and a GraphQL server
- simulator used in the demo is OpenDs, a frame example is given (could be VSS too)
- the demonstration iincludes the simulator interface and a GraphQL server to retrieve values from the simulator
- Kevin Valdek: Could we use a fleet instead ?
- Stefan: Yes, by configuring multiple ports
- Stephen Lawrence: Could you containerize the simulator and automate tests ?
- Stefan: It is partially containerized, no issues.
Demo #3 - GraphQL client on top of a VSS schema
slide deck is here, Kevin shows a demo
- How to have data anonymization ?
- there is consent here
- What about the identification?
- Here we could have many types of identifiers, such as what a brand allows you to access (a certain fleet for instance)
- What happens when the user removes consent (need to do something on the 3rd party side) ?
- These are great use cases, we should look into them.
- How do we categorize what is to be anonymized and what is not ?
- Since privacy is partially region-based, it might be better to have configuration outside of the VSS
Discussion on technology options
- Gunnar introduces the topic with this slide deck
- How to generate data
- Usefulness of an easy to run driving simulator
- it would be nice to use the simulator as a driving game and generate data
- Iyyaz: I go for it !
- Gunnar: which operating system would you use ?
- Iyyaz: ubuntu, linux or windows 10
- Christian: having vehicle data would be useful to test our APIs !
- Stephen Lawrence points out that CAN can-utils has the basic cansend to send can msgs, look at https://github.com/linux-can/can-utils, and https://manpages.debian.org/stretch-backports/can-utils/cansend.1.en.html
- How important is the sanity of the data ? Could we do statistical analysis on random data? What about randomly generating data ?
- Gunnar: Is that sending a random generated data you mean?
- Stephen: can-utils also has cangen for random data
- Stephen: it seems also that candevstudio may have some generation capability, look at CANdevStudio repository
- Alternative technologies
- Why not using MQTT between the vehicle and the cloud (rather than other than W3C Gen 2) ? with MQTT there is a need to define the payloads
- using maybe a NoSQL data base
- Abhijeet: mentions the use of a replica of the car like AWS Car Shadow and like the Ditto digital twin - Device as a service: Ditto project from Eclipse https://www.eclipse.org/ditto/
- How to do high-volume tests ?
- Evaluating the performances ?
- What about security ?