Workshop agenda for: GENIVI 20th All Member Meeting a Digital Experience
Here's the status report slide deck draft: GENIVI-AASIG-VHAL-status-1.1.pptx Here's the workshop content draft slide deck GENIVI-AASIG-VHAL-workshop-draft.pptx |
3:00 PM - 3:30 PM CET | AASIG - Vehicle HAL | Status report | Stefan | 3:00 PM - 3:20 PM |
Vehicle data model alignment - a short intro | Gunnar | 3:20 PM - 3:30 PM | ||
3:30 PM - 3:45 PM CET | Networking break | — | 15min | |
3:45 PM - 5:15 PM CET | Agenda and intro | Stefan | 3:45 PM - 3:50 PM | |
External Data Server Framework | PoC implementation | Stefan | 3:50 PM - 4:00 PM | |
Android-side (Head Unit) Components Status | Framework Layer: Authentication service HAL Layer : VHAL Application Layer: App | Stefan | 4:00 PM - 4:10 PM | |
Non-Android In-Vehicle Components Status | VSS feeder VSS database | Stefan, Alex | 4:10 PM - 4:20 PM | |
Demonstration, either video or live | Stefan | 4:20 PM - 4:30 PM | ||
Conclusions, future plans & repo structure | Stefan | 4:30 PM - 4:40 PM | ||
Q&A | 5min | |||
CVII workshop insights | Take-aways from CVII workshop and VHAL impact | Gunnar | 4:45 PM - 4:55 PM | |
Q&A | 5min | |||
Standards | AOSP 11 new features like customizable permissions for OEMs to enable better granularity, etc. | Stefan | 5:00 PM - 5:10 PM | |
Q&A | 5min | |||
5:15 PM - 5:30 PM CET | Networking break | — | 15min | |
5:30 PM - 7:00 PM CET | First session recap | Follow-up on questions on topics from the first block | Kevin | 5:30 PM - 5:35 PM |
GraphQL Concept | Open question to the participants: since there is no graphql libraries, it is the correct path to go ? do we revise the data access architecture ? | Stefan, Alex | 5:15 PM - 5:25 PM | |
Q&A | 5min | |||
Testing | Lava Test Farm satus | Stephen | 5:30 PM - 5:40 PM | |
Q&A | 5min | |||
Alternate architectures for vehicle data access | Internal Data Server | Stefan, Alex, Gunnar | 5:45 PM - 5:55 PM | |
Q&A | 5min | |||
Vehicle Data Access via Customized HAL - Google VHAL + OEM Extensions inside | Stefan, Alex, Gunnar | 6:00 PM - 6:10 PM | ||
Q&A | 5min | |||
Vehicle Data Access – via Some/IP Service - SomeIP stack inside the Framework | Stefan, Alex, Gunnar | 6:15 PM - 6:25 PM | ||
Q&A | 5min | |||
Data Models | Alignment of Android and non-Android data models | Gunnar | 6:30 PM - 6:40 PM | |
Q&A | 5min | |||
Outlook | Discussion and closing topics to plan next activities | All | 6:45 PM - 7:00 PM |
Times are in CET (= UTC + 1) (note, that is now "winter time", not daylight savings time)
Friday 30 October (one track) Afternoon Session | |||
---|---|---|---|
15:00-15:30 | Report | 30 | Android Automotive SIG #1 - Vehicle Data APIs / Vehicle HAL Presenter: Stefan Wysocki (Tieto) Abstract: Pre-recorded Status Report |
15:30-15:45 | Break | 15 | Sponsors' Videos |
15:45-17:15 | Working Session | 90 | Android Automotive SIG #1 - Vehicle Data APIs / Vehicle HAL Moderator: Alexander Domin (BMW) Abstract: During Q2, 2020, the Vehicle Data APIs / Vehicle HAL team has undertaken the design and implementation of the External Data Server (EDS) proof-of-concept demonstrator that investigates how to extend Android access to vehicle data. The rationale for this work is that the number of vehicle properties currently defined in standard Android is very limited as compared to the thousands of vehicle-related signals OEMs are considering for their connected vehicles. Although the project could propose to expand the standard vehicle property list in Android, the integration of Android into a complex electrical and connected vehicle architecture suggests a bigger picture to consider. Standard data access methods should be applied in the entire vehicle and in cloud-connected services. This EDS proof-of-concept intends to validate the concept of a data server accessing the vehicle dataset as described by VSS (Vehicle Signal Specification standard), which is used also in W3C Automotive Group, and enabling authenticated Android apps to access the vehicle data through a web socket protocol. The actual values of the vehicle signals will be queried/updated thanks to a VSS feeder that will connect to the rest of the vehicle using, for example, Some/IP. The AASIG VEHICLE HAL project team will present a status report of the proof-of-concept implementation and explain the design choices made. The following next steps will be then comprehensively debated:
|
17:15-17:30 | Break | 15 | Sponsors' Videos |
17:30-19:00 | Working Session | 90 | Android Automotive SIG #1 - Vehicle Data APIs / Vehicle HAL Moderator: Alexander Domin (BMW) Abstract: continuation of the working session |
Recommendations :
(Philippe +Stefan + Alex - draft)
Please fetch a template here. For the virtual tech summit 16:9 version is likely the best.
GENIVI Standard Presentation Documents (you may need to log in to the Wiki to view this page).
TODO
Reference work
(60mn) topics for discussion
interest of the graphql concept :
open question to the participants: since there is no graphql libraries, it is the correct path to go ?
other architectures are possible, rediscuss the other options, e.g. the internal data server
we should go through all of them again
there was some changes in aosp 11 to enable more customizable permissions for oems (permission granularity)
alignment of android and non android data models
Gunnar: from the discussion we are having on CVII, it seems that android will not drive the vehicle data model definition
(10m) Virtualization ( need to research more to get specific questions to drive discussion )
(10m) Containerization ( need to research more to get specific questions to drive discussion )
Ideas for detailed agenda: