Next Meeting -
...
3 March 5:
...
00pm CET
...
...
- project plan update - filling workitem description and definition of done
- discussion on proof-of-concept resourcing
- AOB
Backlog
Expand Backlog
- Android Compatibility Definition Document
- Software architectural task force : Vehicle Data architecture for Android
- 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
- Signal to service translation
- Secure access control in Some/IP
- AOB
Tuesday 18 February - 5:30pm CET
Participants
- Alex (BMW, software architecture team, connection to Android, finding the best solution to connect AA to BMW cars), Wassim (BMW), Steven Hartley (GM, infotainment connectivity architect, based in Montreal), Guru (Bosch), Andrii (EPAM), Stefan (Tieto), Johan (melco), Stephen (Renesas), Gunnar, Philipp
- apologies: Sachin (Mercedes-Benz)
Agenda
- Recap on PoC architectural design
- Call for participation
- AOB
Minutes
Recap on PoC architectural design
- Alex: presents the so-called External Data Server Proof-of-Concept architecture
- on the right side, this is the Android Automotive based infotainment unit
what we did: we tried to open our mind w.r.t. the abstraction to our bordnet interfaces
explains the rationale for the work done
point #1 is abstraction
point #2 is to bring this into the vehicle, this is where we use VISS (the implementation of VSS
Steven: this seems to me a way to solve the deployment of OEMs / Tiers 1 applications
Steven: how to solve the deployment of third party applications ? will this still use the vehicle HAL and the vehicle properties ?
Alex: explains we would like to go to Google with this proposal
Steven: will you put the vss server in the appstore ?
- Steven: how do you intend to go to Google ?
- Gunnar: through OEMs
Andrii: only the access to the data is external to the data server , there is some kind of confusion between internal & external data server architecture in my opinion
Stephen: we need to think about the safety domain in the vehicle EE architecture, we might have the data server running on the safety domain
Andrii: how do you manager the question of permissions for accessing data when the car stops vs the car moves
Alex: there are properties in the VSS and we will define groups with permissions that will be enhanced with the manifest files at application level, the management of these 2 set of datas will be probably handled at application level, but this is to confirm
- Philippe: shows the PoCs we identified and their priorities, the priorities do not refer to which architecture should be deployed in production, they reflect rather the team preference for which PoC to start first
- Philippe: we need an update version of the slide deck presenting the various architectural design options
Call for participation to PoC activities
- Philippe: reminds his request for ownership of the PoC activities
- WBS of PoC #1 is available at link, please review it and identify which activities your company could contribute to
Next events
- Tuesday 25 February 5pm CET - "all-hands" monthly call : recap of AASIG activities at management level
- Tuesday 3 March 5pm CET - next Vehicle HAL call
- calendar invites will be sent
Tuesday 11 February - 5pm CET
...