Next Meeting - Tuesday 21 January - 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)
- VSS Layers concept vs. access control groups (Gunnar's presentation)
- F2F agenda review and prepation readiness
Backlog
- AOB
Tuesday 14 January - 5pm CET
Participants
- Sachin, Stefan, Markku, Marcin, Gunnar, Johan, Alexander, Stephen L, Philippe
- apologies: Guru
Agenda
- F2F meeting organization - logistics
- F2F agenda topics - preparation readiness
Minutes
F2F meeting organization - logistics
- Alexander: added the address of the BMW office where the meeting will be hosted ("the 4-cylinder building" near the Olympic park) and the list of recommended hotels to the wiki, look here
- review of the participation list
- who is interested in the Audio HAL in addition to the Vehicle HAL ?
- Sachin: could spend half-a-day on Day 2 on the audio HAL
- Piotr: interested in both topics
- Patrick (Mobis) interested in both topics, will join remotely
- Nassim (Mobis) interested in Audio HAL, will attend physically
- Markku
- Andrey: Philippe will reach him out to check he can join remotely
- Philippe: will check the participation of the Audio HAL team members this week
- who is interested in the Audio HAL in addition to the Vehicle HAL ?
F2F agenda topics - preparation readiness
- review of TODOs from agenda draft (there) put together during last call
- TODOs were on the security design
- Android permission model
- Stefan has prepared a slide deck on connecting VSS and Android permissions model
- External service approach
- /TODO/ Alexander will contact Giovanni about the Adaptive Autosar Identify and Access Management model
- The VSS Layers concept could be used to put signals into access control groups
- Gunnar said that some basic ideas are in a presentation he made to the CCS project
- /TODO/ Gunnar deliver this presentation at the next call Vehicle HAL call (on Tuesday 21 January)
- Android permission model
Android permission model
- Stefan shows this slidedeck, sample code is there (both not uploaded yet)
Alex: what is the granularity of the properties ? one application can access to 5 leaves (of the VSS tree) and another to 20 leaves of the VSS tree, how to hande it ?
Stefan; this is possible
Gunnar: who owns the signing key ?
- Stefan: the OEM owns (TBC)
- Alex: very good presentation, thanks
Next call
- Philippe: proposes to have another Vehicle HAL call next Tuesday at 5pm CET (because Tuesday 28 January slot will be occupied by the AASIG All Hands call
- all agreed
Tuesday 17 December - 5pm CET
Participants
- Jimhyuk, Patrick, Pontus, Stefan, Piotr, Gunnar, Guru, Johan, Alexander Stephen L, Philippe
- apologies: Sachin, Pete
Agenda
- Next events: calls and F2F meeting organization - date planning - look here
- F2F agenda: gathering of topics
Minutes
Next events
- F2F meeting organization - date planning - look here
- decision F2F will happen on 4-5 February 2020, location: BMW, Munich, Germany
- for those who have not filled their participation info yet, please fill the table
- next calls: 14 January and 28 January 2020 at 5pm CET
F2F agenda
- list of topics and assignment of preparation work is provided there
Tuesday 3 December - 5pm CET
Participants
- Stefan, Piotr, Gunnar, Guru, Johan, Pete, Stephen L, Sachin, Viet-Ahn, Philippe, 10 participants
- apologies: Alexander
Agenda
- Permission schemes
- Android Compatibility Definition Document (skipped to next call)
- Software architectural task force : Vehicle Data architecture for Android
- Next events: calls and F2F meeting organization - date planning - look here
- Backlog
- 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
Minutes
Permission schemes
- Stefan presents this deck
.Sachin: I understood that the properties are not stable yet, do we still need to investigate properties further ?
Stefan: there is only one way to customize the permission via the CAR_VENDOR_EXTENSION, we need to understand this comprehensively
discussion follows followed by discussion on implementation
Vehicle Data architecture for Android
Philippe: how to relate this to the architectural concepts identified already ? can someone do some work before EoY ?answer seems to be everyone busy with CES.
Backlog
- Gunnar introduces shorlty the topic of developing jointly a component implementing Java APIs for Androif
Next events
- next calls are scheduled on Tuesday 17 December a,d Tuesday 14 January
- F2F meeting: participation table is here. Please fill it on
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