Next Meeting - Tuesday 17 December - 5pm CET
Zoom dial-in
Dial by your location
Meeting ID: 499 263 988
Agenda (proposal)
Agenda items (to be prioritized at the beginning of the call)
- Android Compatibility Definition Document
- Software architectural task force : Vehicle Data architecture for Android
- F2F meeting organization - date planning - look here
- Backlog
- 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 3 December - 5pm CET
Participants
- Sachin, Gunnar, Gerald, Piotr, Pontus, Stefan, Viet-ahn, Guru, Alexander, Philippe
- Apologies: Johan, Pete,
Minutes
- Summ
Agenda items (to be prioritized at the beginning of the call)
- Permission schemes
- Android Compatibility Definition Document
- Software architectural task force : Vehicle Data architecture for Android
- F2F meeting organization - date planning - look here
- Backlog
- 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 19 November - 5pm CET
Participants
- Sachin, Gunnar, Gerald, Piotr, Pontus, Stefan, Viet-ahn, Guru, Alexander, Philippe
- Apologies: Johan, Pete,
Minutes
- Summary of Tech Summit and discussion about the latest architecture pictures.
Gunnar shows the update on the architecture made during last week's workshop in Detroit
- Pictures are included in the (commented) Tech Summit slide deck attached to this page.
- Proposal for organizing a second F2F meeting before EoY, meeting could possibly hosted by Tieto in Poland
- /TODO/ Gunnar create a duddle to gather the possible meeting dates and then send the date and other requirements for the meeting to Viet-Ahn
- /TODO/ Gunnar create a wiki page to gather the inputs and outcome of discussion on the architectural design
- Alex: we need to identify the building blocks in the architecture diagrams
- Alex: for instance we need to add the authorization / permission scheme stuff, one approach is to reuse Google permission scheme
- discussion on ServiceIds in Android
- Stefan: posts the following link: http://androidxref.com/9.0.0_r3/xref/packages/services/Car/service/src/com/android/car/hal/PropertyHalServiceIds.java
Sachin: I would recommend that we look for what we are violated from Google ? what contradicts the certification requirements of the CTS ? IMHO we need to have to look at the level of the standardized requirements that the CTS checks
- Stefan: IMHO we are not violating anything but a way to check it is to look at the Android Compatibility Definition Document: https://source.android.com/compatibility/cdd
Assignment of work items (for the next meeting)
- how permission schemes are managed for custom properties, how access control is managed, vendor extension of the permission (assigned to: Stefan)
- reviewing the someip identity and access management, GPRO has already reviewed this, they need to provide their review results to the Vehicle HAL project (assigned to: GPRO participants)
- review of the Android Compatibility Definition Document (assigned to: Sachin)
22 October 2019
8 October 2019
25 September 2019
10 September 2019
28 August 2019
Vehicle_Properties_Architecture
VSS presentation NOTE the current VSS is not at the link listed in this presentation. It is now stored at https://github.com/GENIVI/vehicle_signal_specification