Minutes of Android Automotive SIG
Vehicle Data API / HAL Sub-Project
22 October 2019
Agenda
Agenda items (to be prioritarized at the beginning of the call)
1.	tech summit session preparation
2.	Software architectural task force : Vehicle Data architecture for Android - continuation of discussion
3.	Comparison of how vehicle properties are managed by Android 9 and 10 (Q) - further inputs
4.	question to address in the group: what do participating companies intend to do with the JAPI (Java API similar to CommonAPI for Android) ? this building block is currently missing
5.	AOB
Backlog
•	Some/IP and access management
•	Signal-to-Service translation
•	Vehicle properties: boot sequence

Attendees: 
Sachin Athanikar (Daimler), Alexander Domin (BMW), Johan Strand (Melco), Piotr Krawczyk (Tieto), Guru (Bosch), Gerald (Bosch), Stephen Lawrence (Renesas),  Gunnar (GENIVI), 8 participants
Apologies (vacation): Marc Bellanger (Renault), Philippe (GENIVI, Project Management Office Lead),

Software software architectural design 
Gunnar’s follow up after the call:
As Piotr noted during the call, it would not hurt to extend our diagrams with a bit more detail about how the software structure actually is (must be) within Android, and Piotr offered to put some work into that - thanks!
I'm referring also to the feedback received by Stefan previously.  For example what you wrote about clarifying what parts need to be changed as properties in .hal, and what parts are the application-facing services.  If that feedback can be described briefly in bullet-points, it would help.
Here is also for your consideration some new diagrams (see slide deck attached to the wiki) from Johan at Melco that make a clearer picture of what we have discussed.  Perhaps the last slide, number 4, shows the complete idea best.  It is not, in my opinion, set in stone that it is the VISS (v1) protocol that is preferred by all, but the architectural principle is clear here to have vehicle data server/service of some sort that can be queried with VSS identifiers using some protocol.
Johan also included on the side, a copy of the picture from the Android documentation but perhaps it would be better to redraw the complete picture as one ?  
@Piotr - you probably have a good idea of how to do this. Of course, feel free to also include additional slides containing text to explain anything you think is missing.
Looking forward to what you might add to this to clarify our intentions so far (or if you have any brand new ideas, of course those are welcome too). Anything you create will be added to the combined content and soon shared with the whole project group, of course.
Next call (5  November) agenda
Agenda items (to be prioritarized at the beginning of the call)
•	Software architectural task force : Vehicle Data architecture for Android - continuation of discussion
•	Comparison of how vehicle properties are managed by Android 9 and 10 (Q) - further inputs
•	question to address in the group: what do participating companies intend to do with the JAPI (Java API similar to CommonAPI for Android) ? this building block is currently missing
•	AOB