Minutes of Android Automotive SIG
Vehicle Data API / HAL Sub-Project
25 September 2019
Agenda
1.	Vehicle HAL update
2.	Feedback on previous call minutes
3.	Proposal for launching a task force on architecture
4.	AOB

Backlog
•	Some/IP and access management
•	Signal-to-Service translation
•	Vehicle properties: boot sequence

Attendees: 
Sachin Athanikar (Daimler), Markus Boje (BMW), Alexander Domin (BMW), Johan Strand (Melco), Stefan Wysocki (Tieto), Abhinit Sinha (Luxoft), Piotr Krawczyk (Tieto), Stephen Lawrence (Renesas), Philippe Robin (GENIVI, Project Management Office Lead), 9 participants
Apologies: Marc Bellanger & Eric Serre (Renault), Gunnar (GENIVI)

Introduction
Philippe: welcomes the participants and presents the agenda and reshuffles the items in the agenda
Apologies for the very concise minutes, there was a capturing issue 
Vehicle HAL update
•	Sachin: there was a change in the vehicle properties from Android 9 (P) to Android 10 (Q), vehicle.h was removed, I need to investigate into it, I intend to provide an update in the next call, I will keep the comparison of Android 9 and 10 generic 
•	Philippe: (side note added offline): https://source.android.com/setup/start/android-10-release
•	Stefan: is this relevant for the discussion we are having in this group ? IMHO the broad sense of properties in Android 9 & 10 is the same, differences are to me just implementation details
•	Sachin: we want to check whether the properties have to be changed and whether we have much rework to do, Android 10 is more automotive centric in our opinion
•	Stefan: are the changes backward compatible ?
•	Sachin: yes, it is backward compatible 

Feedback on previous call minutes
•	Johan: there was a quite interested topic discussed in the last call, so far we are discussing quite widely and there are various opinions about what we are trying to do, i.e. how can we use the Vehicle HAL with something standardized to communicate with ECUs
•	
The core questions seem to be:
o	The standardization of communications - could be Some/IP be one of the core techniques to use together with VSS as a first step ?
o	The security aspects (and Autosar comes into the picture then) as a second step
•	IMHO we need to limit our discussion to one point
•	Alexander : personally I see two tracks
o	VSS or not VSS for the standardization of the board.net communications
o	what do we bring as an automotive OEM ? Some/IP and/or IPC
•	Philippe: we need to address different kinds of system-level architecture like central computing nodes for which IPC is relevant and distributed computing architecture for which Some/IP (SOA) is more relevant

Proposal for launching a task force on architecture
•	Philippe: this call gives me an opportunity to propose the launching of a task force on the software architectural design to start structuring and pruning the different ways of designing and implementing the access to the vehicle data and their delivery to the Vehicle HAL
•	Sachin, Alexander, Johan are in, 
•	Gunnar, Giovanni and Pete will be asked to be in
•	All interested parties are welcome
•	Philippe: the task force needs to start now and provides first findings/proposals in two-week time at the next call on 9 October

Next call schedule
 Next call will be scheduled on Tuesday 8 October at 5pm CET. A calendar invite will be sent.
TODOs for next call
/TODO/ participants to software architectural design task force to reconvene via email and ad-hoc telcos until next call
/TODO/ interested parties to provide their views on the following two open questions
1.	Open question: Secure access control in Some/IP
2.	Open question: Signal-to-Service translation

/TODO/ all participants to provide their open questions
Agenda for next call (proposal)
1.	Comparison of how vehicle properties are managed by Android 9 and 10 (Q) (Sachin)
2.	Report of the software architectural task force ramp-up (TF participants)
3.	Secure access control in Some/IP (Giovanni ?, Pete ?)
4.	Signal to service translation (Pete ?)
5.	AOB
Adjourned: 17 :30 CET