Next Meeting - 14 April 5:00pm CET
...
External Data Server Proof-Of-Concept - Work Breakdown Structure
Tuesday 7 April - 500pm CET
Participants
- Johan, Sachin, Magnus (JLR), Andrii, Piotr, Stefan, Alexander, Gunnar, Philippe, Stephen L
...
- Philippe: the AASIG VHAL workshop is scheduled on Wednesday 13 May at 3 to 6pm CET (best US Pacific friendly time we can propose)
- Philippe: asks Alex and Sachin whether they can be moderators, the workshop agenda preparation will be shared with the team in the upcoming weeks until the tech summit
- Alex: yes, possible for me
- Sachin: I will check whether I can participate, will provide feedback in a few days
Friday 27 March March - 200pm CET
Participants
- Alex, Stefan, Philippe
...
- Proper buildsystem support: Android.bp for future platform integration + gradle for development
- AIDL definition that is more developer friendly and can be easily kept as "compiled" .jar library for 3rd party development of Applications
- Functionality of Service will be the same as BWM kotlin implementation
- MPL 2.0 license
Tuesday 24 March - 500pm CET
Participants
- Alex, Stefan, Piotr, Johan, Nadim, Bartosz Cichosz, Stephen, Philippe
...
- Philippe: I may have to escalate the situation and report that AASIG VHAL team have difficulties to staff the poc
- (added offline): as in all collaborative projects, it would be good that each participant consider spending a little bit more time than attending the calls and reading the minutes, otherwise everyone gets the impression the work is stuck
- Stefan: point 13 of the WBS (Define GraphQL schema - what does it look like?) was actually done by Alex as he showed the schema today
- Alex: agreed, I have the schema but something is still missing
- Stefan: we need to have something to get started on the other work items
- Stefan: we need also to agree on the data format
- discussion follows on how to bootstrap the work
- Stefan: will work out some prototype code and show it at the next VHAL call
- Philippe: next week's call will be the AASIG All-Hands call on 31 March at 17:00 CET (watch out: there is a time change scheduled on 28-29 March in Europe)
- Philippe: next VHAL call will be scheduled on 7 April at 17:00 CET
Tuesday 17 March - 500pm CET
Participants
- Alex, Sachin, Stefan, Piotr, Johan, Stephen, Gunnar, Philippe
...
- Sachin: the people I contacted at Daimler acknowledged my demand for implementtersn, no positive feedback yet,, will continue to ping them
- then the participants resume the review of the work breakdown and discuss the candidate technologies to implement the components
External Data Server Proof-Of-Concept - Work Breakdown Structure updated on line by Gunnar, thanks !
- here is below some elements captured during this discussion
work item #7 - agree on PoC use cases for the implementation
Stefan: during the F2F meeting, we said we will use the battery voltage for an EV and also the tyre pressure and air conditioning information
All: an EV application is the right app to develop for a demo
we will show the battery status and battery consumption during a drive
- Stefan: Tieto evluated the GENIVI vehicle simulator available in github, this simulator can provide some of the data we needed like the property of speed during a drive
- Johan: opends used in W3C is also a candidate, link: https://opends.dfki.de/, configuration files are written in xml,
- Gunnar: one of these simulators would be the data provider box in the PoC block-diagram for the use case showing the vehicle speed or other vehicle signals like the tyre pressure and a simple simulation covering the EV signals (alternate data signal feeder) would be used for the demo use case showing the battery status and battery consumption
- Tieto is analysing the simulation aspects for the PoC
- work item #9 - Select and implement feeder input API → how feeder writes data into the "shared database"
Alex: do we take a database or in-memory hash values ?
Gunnar: the feeder is writing the values into the database, this work item is just the interface to the database, whatherver is coming from outside needs to be stored internally
work item #10 - VSS data server component - supporting technos
Alex: I will add a description on how to install graphql on ubuntu but what about using a virtual box where everything is installed ?
Gunnar: it would be ideal to package it that way
Stefan: we said we would run it on docker, this is another possible solution
Philippe: reminds the demo execution architecture, we will one laptop running the EDS on Linux and for the IVI unit either one laptop running the Android simulator or a target board like R-Car or NXP
discussion on the selection of docker vs virtual box
*decision* docher is the environment we will use
graphql and nodejs will run on docker
work item #11 - Implement the connection between the access protocol (GraphQL) and the fetching/writing of data into the database
discusison on VSS representation and graphql schema
Alex: I have something already and can possibly provide it although it needs some refactoring, I need to check with my management
Alex:I can show what I have done in the next call
work item #14
this is the graphql query, it corresponds to the implementation of the resolver function in graphql
work item #15
this work is included in workitem 14 but wiriting, a writing function in graphql is called a mutation function
- other work items
- discussion not captured, look at the WBS wiki page
- discussion on whether we add a column in the WBS table to capture the technologies used before capturing the volunteers' names
- decision: no change in the table for the time being
- /TODO/ all participants to review the work items and decide which one(s) they would take over
- work items descriptions are in the following wiki page External Data Server Proof-Of-Concept - Work Breakdown Structure
Tuesday 10 March - 500pm CET
Participants
- Roman (Harman, just observer), Andrii, Stefan, Piotr, Johan, Gunnar, Philippe
...
- Philippe: we do not whether the Spring AMM will be physical or virtual; decision will be made soon by the GENIVI board of directors
- Philippe: however we are planning actively the content of the sessions; there will 6 sets of sessions
- looking forward
- AASIG projects on VHAL & Audio HAL
- Cloud & Connected Services projects on Vehicle Data Model and Vehicle2Cloud Communication Infrastructure
- Cybersecurity
- In-vehicle payment
- Connected Vehicle Software Development
Adjourned: 5:20pm CET
Tuesday 3 March - 500pm CET
Participants
- Alexander, Sachin, Andrii, Stefan, Piotr, Johan, Stephen, Gunnar, Philippe
...
- Alex: we are using Apollo graphql server which needs an addition for web token management, and other stuff we are working on, I have discussed which contribution we could do with Markus
- BMW has the blue box on the right box (authentication) (look at the EDS architecture diagram)
- BMW has only the EDS implementation, not the Internal Data Server one
- Alex: the permissions are not yet what we need
- discussion on the work to do for the authentication and the access control groups
- Gunnar: we need to do a more formal description of things to be done for the authentication
- Alex: might be able to do some work in the next days, will try out my ideas on an actual implementation, as soon as I have something (next week possibly), I will generate some docs like ppt
- Alex: tooling is not clear for me yet, as soon as we agree on the way to specify things, we will talk about tooling and manifest generation
- discussion on the naming of artefacts
- Alex: we want to have a nodeJS graphql implementation running
- Alex: I can describe the nodeJS and graphql installation and the deployment of json files
- Gunnar: the wiki page for documenting tihs is AASIG: Implementation notes
- /TODO/ Alex to describe the nodeJS and graphql installation in the above wiki page
- Stefan: at Alex, since you have the authentication implementation under way, could you spent some time to describe what you have done so that we can identify the leftovers ?
- Alex: I can explain that, for instance we need a json web token implementation
- /TODO/ Alex & Stefan to clarify what could be the contribution of BMW & Tieto to the authentication mechanism implementation
...
- Alex: the scope of work depends on how much simulation we want
- discussion on how to implement the VSS data base in a limited manner for the purpose of demonstrating the concept
- Gunnar: for settting the values, would you suggest to use nodeJS code first ?
- Alex; yes, later we will use someip and so on
- Review of other work items for the VSS feeder
- todo finalize permissions layer concept (independent work item)
- Gunnar: we target a simpler mode of permissions, not a high priority
- todo create a layer concept for the Franca to VSS leaf mapping (model transformation)
- not a high priority
- todo check signal to service translation in Adaptive Autosar
- not a high priortiy
- todo agree on PoC use cases for the implementation
- Alex: this is important for the purpose of concept demonstration,
- Philippe: proposes to schedule this work item for next Sprint starting early April
- todo finalize permissions layer concept (independent work item)
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, Philippe (GENIVI)
- apologies: Sachin (Mercedes-Benz)
...
- 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
Participants
- Andrii (EPAM), Piotr, Stefan, Viet-Ahn (Tieto), Johan (melco), Suhasini (Analog Devices), Richard (Harman), Stephen (Renesas), Gunnar, Philippe
- apologies: Sachin, Alex
...
- Philippe proposes to have a weekly period for the Vehicle HAL call starting today
- Next call will be scheduled on Tuesday 18 February at 5pm CET
Vehicle HAL F2F Meeting 4-5 February
Tuesday 21 January - 5pm CET
Participants
- Andrey, Johan, Markku, Pontus Fuchs, Stefan K, Stefan W, Piotr, Stephen L, Patrick, Guru, Alexander, Gunnar, Philippe
- apologies: Sachin
...
- agenda updated on line, look here
Tuesday 14 January - 5pm CET
Participants
- Sachin, Stefan, Markku, Marcin, Gunnar, Johan, Alexander, Stephen L, Philippe
- apologies: Guru
...
- Philippe: proposes to have a 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
...
- 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
...
- 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,
...
- 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