Page tree
Skip to end of metadata
Go to start of metadata

Main thread: External Data Server Proof-Of-Concept - Work Breakdown Structure

Next Meeting - VHAL / Vehicle Data APIs weekly call - every Tuesdays - 17:00-18:00 CET (except when replaced by the monthly All-Hands)

Webex link

Dial by your location: find your local number here


  • backlog review
  • AOB


 Click here to expand...


  • 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

Tuesday 8 September - 500pm CET


  • Maria Sciier
  • Piotr Krawczyk
  • Johan Strand
  • Stefan Wysocki
  • Stephen Lawrence
  • Guru
  • Gunnar
  • Philippe


  • Alexander Domin


  • Permission enforcement implementation
  • Outcome of call on OpenDS
  • Feature content for MS3 demo


Permission enforcement implementation

  • Alex is back from vacation and will do his contribution

Outcome of call with OpenDS

  • Gunnar: I have not succeeded to work with opends yet, I tried to build on ubuntu, no show stopper for the timebeing, nothing changed so far, on it

Feature content for MS3

  • Maria: will Android R11 be used for the demo

  • Stephen: There is R9 and R10 on R-Car. Android 11 would need to check more from Google agreement perspective.

  • Gunnar: We will use R10 for the demo

  • Philippe: invite Bosch to do some implementation tasks, e.g. on the application layer

  • Stefan: shows the block diagram in External Data Server Proof-Of-Concept - Work Breakdown Structure
  • Philippe: explains what the team has implemented, will implement for MS3 and which tasks are to be assigned (app development)
  • Stefan: explained which vehicle properties are available in the demo (look at  AASIG-58 - Getting issue details... STATUS )
  • Maria and his developer will look at it and provide feedback
  • Stefan indicates that Tieto has agreed to make their VHAL code available, it will be under MPL 2.0, look at AASIG-116 - Getting issue details... STATUS )

Tuesday 1 September - 500pm CET


  • Piotr Krawczyk
  • Johan Strand
  • Stefan Wysocki
  • Stephen Lawrence
  • Gunnar
  • Philippe


  • Alexander Domin

Feature content for MS3

  • the permission enforcement is something worth have on graphql side. Waiting for the status update from Alexander.
  • discussion on the feature content for the next milestone demo (MS 3, i.e. the virtual tech summit scheduled on 26-30 October) )
  • it would be good to implement the data access from VHAL in the HAL Layer to the Apollo Graphql (look at External Data Server Proof-Of-Concept - Work Breakdown Structure)
  • Stefan will look at it and confirm next week whether he can implement it, AASIG-113 - Getting issue details... STATUS created
  • Gunnar will continue the packaging of the demo AASIG-114 - Getting issue details... STATUS created
  • Gunnar would like get clarifications about the building of the demo using OpenDS, ad-hoc call scheduled on Wednesday 2 September with Stefan, Johan and Gunnar

Virtual tech summit preparation

  • the VHAL session is scheduled on Friday 30 October afternoon, please put a note in your agenda and schedule a timeslot from 15:00 until 19:00 CET AASIG-116 - Getting issue details... STATUS created

Next meeting agenda

  • Permission enforcement implementation

  • Outcome of call on OpenDS

  • Feature content for MS3 demo

  • jira review

Tuesday 18 August - 500pm CET


  • Piotr Krawczyk
  • Johan Strand
  • Stefan Wysocki


  • Alexander Domin
  • Stephen Lawrence

Stefan reports the status from last weeks to Johan with a highlight of new TODOs ready to be taken.

Piotr will continue his work on sqlite database between vssfeeder and graphql server.

All meeting members agreed, that the permission enforcement is something worth have on graphql side. Waiting for the status update from Alexander.

Tuesday 11 August - 500pm CET


  • Piotr, Stefan, Gunnar
  • Alexander is on vacation this week

The completion of the in-vehicle is held up by access-control implementation in GraphQL server – awaiting status update from Alexander.
Gunnar has tried to unpack OpenDS sources from the Windows-executable via wine but it did not work.  It requires "installing" Java (in the Windows environment) first, which did not work fully, and at least not so that the executable recognizes it as installed.  Have to retry this on a Windows machine probably.

Stefan confirms again that once the "installation" completes, the source code will be on disk and can be extracted to be run in any other Java-capable environment (e.g. Linux).

Tuesday 4 August - 500pm CET


  • Stefan / TietoEVRY
  • ...Piotr is on vacation
  • ...Alexander?


  • Sync up with Stefan. Will have more time next week for progress.
  • Discussed how to compile OpenDS from scratch.  The web site only provides version 5.0 only as a downloadable Windows executable! (sad) and no normal source code repository.
  • Stefan: There is an eclipse project file, but no command-line build project like maven.
  • Stefan explained how he compiled the Java sources manually.
  • Gunnar: OK I will try to unpack the sources from the .exe using WINE

Tuesday 21 July - 500pm CET


  • Philippe
  • apologies: Stefan, Gunnar (vacation)


  • demo status provided by Stefan offline (many thanks, kudos)
  • AOB


Stefan achieved the following activities

  • Described the concept of handling permission groups in  AASIG-38 - Getting issue details... STATUS   and reassigned to Alexander
  • Authentication service that generates token containing granted permissions + App using GraphQL plugin to retrieve the values from server (Fuel properties usecase):
  • TODOs from the code that can be taken:
    • ExampleAppJava/src/main/java/org/genivi/vss/authenticationservice/MainActivity.java43:       // TODO Move this connection boilerplate to VSS-SDK since this code will be shared across the clients
    • ExampleAppJava/src/main/java/org/genivi/vss/authenticationservice/MainActivity.java69:                .serverUrl("") // TODO make it configurable
    • ExampleAppJava/src/main/java/org/genivi/vss/authenticationservice/MainActivity.java84:        // TODO Pass the token to the query
    • ExampleAppJava/src/main/java/org/genivi/vss/authenticationservice/MainActivity.java88:                // TODO Do sanity check of the response and its content
    • service/src/main/java/org/genivi/vss/authenticationservice/            // TODO decide when handle this exception
    • service/src/main/java/org/genivi/vss/authenticationservice/        // TODO Make the key shared between the server and client or change the algo to asymmetric
    • service/src/main/java/org/genivi/vss/authenticationservice/                // TODO Filter out the non-genivi-vss permissions
    • vss-sdk-lib/src/main/java/org/genivi/vss/authenticationservice/    // TODO Make it autogenerated from VSS
    • vss-sdk-lib/src/main/java/org/genivi/vss/authenticationservice/    // TODO Make Manager class to hide this intent there (similar approach to other services running in the framework) see TODO in client implementation
  • Full setup has been recorded and is attached to this email and shows the following steps:
    1. Start of Apollo Graphql server with vss feeder, feeding the values from OpenDS
    2. Start Example application that is able to connect to Authentication Service and retrieve the token with permissions bundled
    3. Example application sends the query for retrieving Fuel data (capacity + current level).
    4. Indications that the values are the same as on server side
    5. JSON Web Token content
  •  Additionally, I have updated some of the Jira tickets. My actions (since 6 July) can be tracked via activity stream:
  • "I kindly ask participants for reviewing the code and contributing by fixing new TODOs."
  • Milestone 2 demo video is available there

Tuesday 6 July - 500pm CET


  • Alex, Piotr, Stefan, Gunnar, Stephen , Johan, Philippe


  • Jira  review
  • AOB


  • AASIG-38 - Getting issue details... STATUS
    • Stefan will document what is implemented in the proof-of-concept for milestone 2 (done with sequence diagrams added)
    • then other inputs from W3C, BMW, etc will be added
  • AASIG-55 - Getting issue details... STATUS
    • discussion on some code generation
  • AASIG-56 - Getting issue details... STATUS
    • discussion on the content of the java web token JWTK
  • AASIG-47 - Getting issue details... STATUS
    • Gunnar will contact Daniel Wilms about the VSS and tooling around, ticket assigned to Gunnar
  • demo readiness
    • need to review Stefan's pull request
  • AASIG-57 - Getting issue details... STATUS
    • Alex & Stefan will schedule a call on application layer on Thu 9 at 9:30am CET
    • agenda: token generation
    • invitees: Piotr, Stefan, Alex, Gunnar

Tuesday 23  June - 500pm CET


  • Stefan, Piotr, Philippe
  • apologies: Alex, Johan, Gunnar


  • outcome of discussion with Alex last Thursday & progress report
  • AOB


outcome of discussion with Alex last Thursday & progress report

  • Stefan: this was rather a free discussion, we made a walkthrough oF the code Alex developed a while ago
  • Pior: since last week,  we have an implementation based on SQL up &running
  • Jira tickets were updated
  • discussion on involving Johan into the review of pull requests,  this would be very helpful
  • Piot wiil start developing a small application this week, will look at the app skeleton prepared by Stefan and which is available in the authentication repo

Tuesday 16 June - 500pm CET


  • Stefan, Piotr, Johan, Alex, Andryii, Stephen, Gunnar, Philippe


  • allocation of work
  • AOB


allocation of work

  • Philippe: reminds the need to assign the work at application layer level in order to get a complete implementation "from top to bottom" and calls for volunteers
  • Alex: brings in information about the development guidelines fo Android app using Apollo graphql
  • Alex: for application developpent there is a helper in Apollo to work with graphgl

    • graphql schemas are exposed via http

    • the connection between the graphql server and the app can be easily developed

    • the rest can be done in Android studio

  • Stefan: there is already a skeleton in the genivi github repo, explains how he added to the skeleton the "hooks" to authentication services and permission management

  • Stefan: will introduce one dummy permission for poc purpose and then based on that, the real properties will be created

  • Johan: my company has no resources available

  • Piotr: I can jump in and crzate the next iteration of the authentication skeleton

  • Stefan: will also be able to do some work

  • Alex: wht I acan offer is some code I have developed sometime ago, we could have a walktrough session to review the code

  • decision  meeting with Stefan/Piotr/Alex/Johan scheduled on Thursday 18 June 9-11am CET

  • discussion on github repo organization between Stefan and Gunnar

    • TODO Stefan Wysocki to create a PR to move his own stuff from his private branch into the master branch

  • discussion on the data types to be exposed by the grapql server

  • Gunnar agrees with Alex proposal to have graphql expose types that are close to VSS types

  • if we do this, Alex will need to do something on the graphql server

  • discussion on type casting on 64-bit platform

  • Gunnar: we have obviously a type mapping problem, we need to express it more formailly

  • Alex: will start a short doc on type mapping between graphql and VSS in the wiki

    • TODO Alex to initiate a short doc on type mapping between graphql and VSS in the wiki AASIG-109 - Getting issue details... STATUS created

Jira update

Tuesday 9 June - 500pm CET


  • Stefan, Piotr, Gunnar, Philippe
  • apologies: Alex, Stephen


  • sprint review
  • AOB


sprint review

  • Piotr will put some effort this week, need to sync with SteFan on VHAL implementation tasks
  • Stefan: updated the tickets AASIG-43 - Getting issue details... STATUS & CCS-148 - Getting issue details... STATUS
  • Gunnar: my recommendation is to use use the full path name to access the signal
  • Stefan: will add a comment to AASIG-43 and close after I have done some benchmark
  • AASIG-55 - Getting issue details... STATUS in-progress
  • discussion for feature content for Milestone 2 (mid-July)
    • Stefan: one additional feature is to connect VSS feeder to talk to someip, look at AASIG-42 - Getting issue details... STATUS , ticket is to be assigned
    • review of the EDS PoC architecture block-diagram at ExternalDataServerPoC-lookatslide#7
    • TODO Gunnar to annotate the block-diagram with the status of components (like for instance Done (tick), in-progress (star), todo (red star)) and add the picture to the WBS wiki page
    • Stefan: we need to prioritarize the app development
    • Stefan/Piotr are capable of developing the app but it would be good that other developers get involved
    • Stefan: another next low hanging fruit is the VHAL implementation to retrieve the vehicle properties using a GraphQL query (see block-diagram), this can be done after implementing the data access in the app because it uses the same kind of query
    • TODO Stefan to create a Jira ticket for the VHAL implementation
    • discussion on the vehicle data generation, focus on  CCS-149 - Getting issue details... STATUS
    • Gunnar has started some analysis on the data generation but has not finalized an approach yet,

Tuesday 2 June - 500pm CET


  • Alex, Stefan, Piotr, Johan, Gunnar, Stephen, Philippe
  • apologies: JLR folks


  • sync with CCS project
  • AOB


sync with CCS project

  • outcome of the sync meeting with Ulf from the CCS project
  • Stephan: we could change the VSS database for SQLite and request for the properties on demand
  • Gunnar: there are 3 cases that can be considered
    • Do we consider relying not only on cached/stored/updated values in database updated periodically by vss feeder or foresee the need of “on demand” requesting the fresh data ? These 3 ways of accesses are not considered as VSS leaves definition, but might be specified using VSS Layers. Then VSS feeder/Data Server (discussion on the role) can act accordingly (use cached or request for fresh value).

  • TODO Gunnar to write prepare a block diagram describing the various cases
  • Alex :agrees with the 3 cases
  • Alex: do we really need a database which might be seen as an overkill for me ? some hash-map in memory might be enough
  • Alex: when the data are not changed at all, what do we do ?
  • Gunnar: do we need a database ? no, but there is an implementation that exists
  • Alex: are the feeder and the grapql in the same process ?
  • Gunnar: I think there are separate processes and we need IPC soemwhere unless we put everything in one process
  • Stefan:  but even if we use one processor we need some thread sync.
  • Piotr:  IMHO using hashmap and sync implementation would result in the same complerxity than using SQLite
  • Gunnar agreed
  • Gunnar:  debouncing ?
  • Gunnar: there might be some higher performance database, but basically we need only a key value store

VSS to Franca

  • VSS to Franca tool was updated by Gunnar to implement the someip connection
  • Gunnar will add this to the VSS tool repo

Jira tracking

  • Philippe: initiated a Jira tracker for the proof-of-concet implementation, look at AASIG-36 - Getting issue details... STATUS

Tuesday 19 May - 500pm CET


  • Stefan, Johan, Andrii, Gunnar, Stephen, Philippe
  • apologies: JLR folks


  • virtual summit outcome
  • backlog review
  • AOB


virtual summit outcome

  • Stefan, Johan: not a workshop but rather a walktrough

backlog review

  • Stefan - Alex: plan to implement the permissions model, next step is using the same data with graphql with the permissions model added
    • question: do we reuse what BMW is using or do we implement something in parallel ?
  • reusing the database from CCS to be more solid
  • Gunnar: it depends on what we want to store, depends on the use cases, simple key-value pair storing might be enough
  • Gunnar: for next milestone we will keep the values in memory
  • Gunnar: we do not need a very advanced data base
  • Philippe: how to identify a useful use case ?
  • Stefan: restrict the driver from accessing a given speed limit, zooming some control , average data, minimum & maximum value
  • Gunnar: displays the current values and some client side statistics, no need for a database
Gathered Todo's:
  • create a jira ticket for app development AASIG-62 - Getting issue details... STATUS
  • (Stefan ?) send an email to Alex to ask about the implementation of permissions model and graph resolver upgrade

Wednesday 13 May - 3pm-6pm CET - Virtual Technical Summit Workshop


Tuesday 5 May - 500pm CET


  • Alex, Johan, Piotr, Stefan, Sachin, Gunnar, Philippe
  • apologies: JLR folks


  • VSS feeder update: connecting the graphql schema
  • virtual meeting status report & workshop preparation
  • AOB


VSS feeder update: connecting the graphql schema

  • Stefan: was able to put the graphql at work , I have a problem with the docker setup and the simulator that runs outside the VM
    • demo can be shown as first milestone, i.e. at the virtual tech summit workshop
    • Stefan will contact gunnar after
  • Stefan: shows the set up of this demo and explains the problem he has with the nxtworking between the VM and the simulator that runs on windows
  • Philippe: why don't you the GVS (GENIVI Vehicle Simulator) that runs on linux ?
  • Stefan: we should use at a later stage a "better" database like SQL for instance
  • Gunnar: can you all take into account the packaging, like we did in other projects where we use a docker setup ?
  • Alex: I  am fine with the docker packaging
  • Gunnar: next step would be to integrate this into a dev kit and running an app on Android

virtual technical meeting - workshop preparation

  • Alex: I had a call with Stefan yesterday, I do not know how deep we need to address the topics, let us do a brief overwiew of the topics
  • topic #1 - VHAL implementation based on the graphQL implementation
    • Google requires OEMs to implement properties in the Google way
    • we want to deliver these properties outside the graphql server
    • I hope to have JLR working on the proof-of-concept implementation with us, then we need to identify which workpackages need to be implemented
    • Philippe: JLR people are shutdown for the month of May and will not show up again until next month, it is a good idea to prepare an updated work breakdown structure
  • topic #2 - permission group
    • Alex: this is about the concept introduced by Gunnar about the VSS layer concept; I would like to have a discussion on which concept we will follow in the future
    • Alex: in our architecture we have different players, player 1 is the app, player 2 is the authentication service that generates the token, player 3 is the dataserver
    • Alex: I intend to present my understanding of what I have learned about permission management
  • topic #3 - graphql schema
    • Alex: I generated the graphql scheima for the GENIVI VSS standard tree (on github)
    • there is a private area for each and every OEM has his own branch
    • do we need an additional layer to be  integrated into the graphql schema ? or do we create empty leaves in our schema ?
    • Gunnar:  we need both actually
    • Alex:  do we talk about the generation process at the workshop ?
    • Gunnar: I would like to invite you, Alex to partiicpate to W3C call on VSS call this evening

Tuesday 21 April - 500pm CET


  • Johan (Melco), Andrii (EPAM), Piotr (TietoEVRY), Stefan (TietoEVRY), Alexander (BMW), Gunnar (GENIVI), Philippe (GENIVI)
  • guests: Blake Lyman, Richard Isley, Robert Goldie (Jaguar Land Rover) (JLR)
  • apologies: Sachin (Mercedes Benz Research)


  • roundtable
  • introduction to External Data Server proof-of-concept
  • overview of architectural design options for the Vehicle Data Interface
  • VSS feeder proof-of-concept demo
  • graphql and nodeJS installation, graphql schema example
  • virtual tech summit : AASIG VHAL workshop preparation
  • AOB



  • quick introduction of each participants for JLR guests

introduction to External Data Server proof-of-concept

overview of architectural design options for the Vehicle Data Interface

  • (introduction added offline) Philippe:  the outcome of the February 4-5 F2F meeting is described in this slide deck
    • the team identified 4 options for the Vehicle Data Interface design (and 4 proof-of-concepts that could be implemented for experimenting and validating the design options)
    • the team has set up priorities for the proof-of-concepts implementation, the PoC priorities do not refer to which architecture should be deployed in production, they reflect rather the team preference for which PoC to start implementing first
  • Gunnar shows the following slide deck Vehicle HAL Architectural Design Concepts and explains the design options

VSS feeder proof-of-concept demo

  • Philippe: browses quickly through the slidedeck presented by Stefan two weeks ago
  • Stefan: will resume this week the work suspended because of the Easter break

graphql and nodeJS installation, graphql schema example

  • Alex: will finalize the upload of the graphql schema example and instructions for installing graphql and nodeJS this week after last week's Easter break

virtual tech summit : AASIG VHAL workshop preparation

  • Philippe: we need to start gathering the items for the agenda of the AASIG VHAL workshop and the AASIG VHAL project report at the upcoming virtual technical summit
  • Philippe: the abstract of the workshop is the following (published on the virtual tech summit registration page)
    • "The AASIG VHAL / Vehicle Data APIs project has detailed a delivery roadmap for its initial deliverables.  During a successful face-to-face meeting hosted at the beginning of February by BMW in Munich, the project team identified four proofs-of-concept (coding projects) corresponding to the various software architectural options that have been debated since last November’s GENIVI Technical Summit, held in Troy, Michigan.  The first proof-of-concept implementation is the External Data Server (EDS) proof-of-concept that investigates how to extend Android access to vehicle data. The rationale for this work is that the number of vehicle properties currently defined in standard Android is very limited as compared to the thousands of vehicle-related signals OEMs are considering for their connected vehicles. Although the project could propose to expand the standard vehicle property list in Android, the integration of Android into a complex electrical and connected vehicle architecture suggests a bigger picture to consider.  Standard data access methods should be applied in the entire vehicle and in cloud-connected services.  This EDS proof-of-concept intends to validate the concept of a data server accessing the vehicle dataset as described by VSS (Vehicle Signal Specification standard), which is used also in W3C Automotive Group, and enabling authenticated Android apps to access the vehicle data through a web socket protocol. The actual values of the vehicle signals will be queried/updated thanks to a VSS feeder that will connect to the rest of the vehicle using, for example, Some/IP.

       The AASIG VHAL / Vehicle Data APIs project team will present a status report of the EDS proof-of-concept implementation and explain the design choices made. The following next steps will be then comprehensively debated:

      • External Data Server proof-of-concept versioning w.r.t. roadmap milestones
      • Early assessment of implementation TRL (Technical Readiness Level)
      • Ensure project participants have opened, or are planning, a discussion to achieve synchronization of activities with Google's Android team
      • Other proof-of-concepts implementation"
  • Philippe: will contact Alex offline for the preparation of the sessions

Tuesday 7 April - 500pm CET


  • Johan, Sachin, Magnus (JLR), Andrii, Piotr, Stefan, Alexander, Gunnar, Philippe, Stephen L


  • VSS feeder proof-of-concept demo (Stefan)
  • graphql and nodeJS installation (Alex)
  • graphql schema example (Alex)
  • EDS PoC planning (skipped)
  • AOB
    • virtual tech summit VHAL workshop moderation


VSS feeder proof-of-concept demo

  • Stefan: shows this slidedeck presenting the analysis and experimentation he made on the VSS feeder of the EDS part of the proof-concept
  • first topic is about using opends as the vehicle simulator to feed the vss feeder
    • code written in nodejs
    • use a naive database written in json
  • Gunnar: the transformation of signals into VSS is done manually in your example, we could make a generic mapping on how to translate from one signal to the VSS tree
  • Stefan: agreed
  • second topic is about using the genivi-vehicle-simulator (GVS) - as the vehicle simulator to feed the vss feeder
    • Stefan: provides a short overview of the simulator
    • Gunnar: did you have trouble compiling the vehicle simulator code
    • Stefan: none
    • Philippe: asks question to Magnus about the simulation of EV vehicle signals in GVS
    • Magnus: will look at how to implement a small model for simulating EV signals in GVS
    • Philippe: explains as a side comment the reason why the GENIVI CCS project is introducing EV signals in the VSS tree: first this is to a state-of-the-art demo showing connected EV data rather connected ICE vehicle data and second this is also an attempt to trigger OEMs on providing inputs on EV data
  • Johan: we are using a different version of opends in W3C, we made some small changes

graphql schema example

  • Alex: shows the graphql schema he is using
  • Alex: reports the issues he had with some VSS descriptions
  • Magnus: we are currently looking at Daniel Wilms' work on include statement in yaml
  • /TODO/ Alex to submit the issues he encountered in the github VSS tracker
  • Magnus: we need to work on some sort of VSS validator to check the syntax
  • Alex and Gunnar will take offline the publishing of the example on the GENIVI github

graphql and nodeJS installation

  • Alex: I have a 1.3 Gbyte image for graphql and nodeJS installation ready
  • Gunnar: can you also provide the docker instructions for building the image ?
  • Alex: yes, Alex and Gunnar will take offline the publishing of these items on the GENIVI github

AOB - virtual tech summit - VHAL workshop moderation

  • 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


  • Alex, Stefan, Philippe


  • authentication service implementation (work sharing between BMW & TietoEVRY)
  • AOB


1. BMW has implemented the Service for Authentication:

  • Service written in Kotlin - conclusion: Android buildsystem does not support Kotlin yet - needs to be rewritten if integrated in platform
  • IPC between Service - App done manually - conclusion: can be rewritten to hide boilerplate via AIDL generators
  • JWT kept internally as string with payload: uid + permissions as a List<String>
  • Secretkey to sign JWT shared manually (i.e. no single point of encrypted storage) - Action to be put in the backlog: "Decide and configure storage of secret between Server and Clients")
  • Example permissions exposed in AndroidManifest

2. BWM has implemented the Client application to use Authentication Service:

  • JWT retrieved as bundle - can be reworked for AIDL object
  • Connection to GraphQL not analyzed, but not that relevant for the scope of Authentication Service

3. The code is not shared yet because of process of licensing and OSS check by BMW

4. We had a little session about finding similarities/improvements/possible reusage of

5. Based on conclusions from point 4, TietoEVRY proposed - since kotlin implementation needs to be rewritten eventually - to provide Java implementation containing:

  • 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


  • Alex, Stefan, Piotr, Johan, Nadim, Bartosz Cichosz, Stephen, Philippe


  • authentication implementation (work sharing between BMW & TietoEVRY)
  • graphql and nodeJS installation
  • staffing the EDS PoC (again !)
  • AOB


authentication implementation

  • Alex: I was preempted by internal projects again, although I did some work on graphql
  • Stefan: we need to schedule a meeting

  • Alex: we can have a meeting on Thursday at 10-11:30am CET

  • Stefan: will send an invitation DONE

graphql and nodeJS installation

  • Alex: I need to package what I have done in a container in order to make my work easy to reuse
  • Stefan: can you give us a snapshot of what you have done ?
  • Alex: yes, Alex shows the schema representing the vehicle data he is using for the testing of graphql together with some queries
  • Philippe: it would be good that team participants have a look at the Apollo GraphQL documentation to get more familiar with the approach:
  • /TODO/ all participants to look at the Apollo GraphQL documentation:

Next week's All Hands call preparation

  • 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


  • Alex, Sachin, Stefan, Piotr, Johan, Stephen, Gunnar, Philippe


  • authentication implementation (work sharing between BMW & TietoEVRY)
  • graphql and nodeJS installation
  • staffing the EDS PoC (again !)
  • AOB


authentication implementation

  • Stefan and Alex will clarify their mutual contribution to this topic this week

graphql and nodeJS installation

  • Alex: this is on my todo list for this week

staffing the EDS PoC (again !)

  • 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
  • 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:, 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


  • Roman (Harman, just observer), Andrii, Stefan, Piotr, Johan, Gunnar, Philippe


  • authentication implementation
  • graphql and nodeJS installation
  • call for volunteers
  • AOB
    • AMM preparation


authentication implementation

  • Stefan: was too busy to sync on work sharing between BMW & TietoEVRY with Alex,on my todo list for this week

graphql and nodeJS installation

  • skipped

call for volunteers

  • Philippe: reminds that the team priority should be now to volunteer for taking over some tasks on the EDS PoC work breakdown structure (link to the relevant wiki page is on the top)

AMM preparation

  • 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


  • Alexander, Sachin, Andrii, Stefan, Piotr, Johan, Stephen, Gunnar, Philippe


  • project plan update - filling workitem description and definition of done
  • proof-of-concept implementation resourcing
  • AOB


proof-of-concept implementation resourcing

  • Stephen: can provide support for the R-Car target board and Lava test farm
  • Gunnar: since we intend to use graphql technology for the VSS data server component, this is off-the-shelf
  • Sachin: it is difficult to get support from internal teams, I need to involve open source people at Daimler, I need two more weeks before providing feedback
  • Stefan: presents TietoEVRY proposed contribution
  • Stefan: we will use the Android emulator and AOSP 10.0 for this development
  • Gunnar: FYI Stefan's code was merged in the development branch
  • Stefan: this work was mostly related to a former approach than the External Data Server (EDS)
  • Alex joins


  • 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

VSS feeder

  • 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

Tuesday 18 February - 5:30pm CET


  • 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)


  • Roundtable
  • Recap on PoC architectural design
  • Call for participation
  • AOB


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 do you 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 ?

  • Alex: we have not considered it yet
  • Steven: how do you intend to go to Google ?
  • Gunnar: we had contact with Google Automotive team in the past, but people have changed, we intend to reach out to Google 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
  • Philippe: we need an updated version of Vehicle HAL Architectural Design Concepts presenting the various architectural design options

Call for participation to PoC activities

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


  • Andrii (EPAM), Piotr, Stefan, Viet-Ahn (Tieto), Johan (melco), Suhasini (Analog Devices), Richard (Harman), Stephen (Renesas), Gunnar, Philippe
  • apologies: Sachin, Alex


  • Overview of last week's F2F outcome
  • Call for participation
  • AOB


Overview of last week's F2F outcome

  • Philippe presents the outcome of the meeting using this slide deck
  • Meeting was productive and the team had a very good collaborative spirit
  • we were able to pass the milestone from the brainstorming stage to a proof-of-concept development stage
  • Gunnar delivers a short description of the  2 Audio HAL proof-of-concepts identified in the meeting (for information for this call participants)
  • Philippe presents the  4 Vehicle HAL pocs identified in the meeting
  • Gunnar delivers a description of the External Data Server concept architectural design
  • Philippe presents also the roadmap for the poc (note that the tech brief roadmap will be aligned to the same)
  • Philippe introduces the work breakdown structure for this poc. Work items will be introduced in Jira once a description and a definition of done is available for each of them.
  • Philippe presents also the intended execution platform for the poc
  • Minutes of the F2F meeting are here
  • Philippe asks participants for their feedback and comments in the wiki

Call for participation

  • Philippe calls for participation in the work items identified for the pocs and also for contributions to the tech briefs.
  • Expectation is to have feedback on AASIG participants commitment no later than the end of the month in order to start the poc asap and meet the first milestone of GENIVI AMM on 12 May.

Vehicle HAL call schedule

  • 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


F2F meeting organization

Tuesday 21 January - 5pm CET


  • Andrey, Johan, Markku, Pontus Fuchs, Stefan K, Stefan W, Piotr, Stephen L, Patrick, Guru, Alexander, Gunnar, Philippe
  • apologies: Sachin


  • VSS Layers concept vs. access control groups (Gunnar's presentation)
  • F2F agenda review and preparation organization


VSS Layers concept

  • Gunnar: shows the slide deck introducing the VSS layers concept
    • the concept was already presented to the GENIVI CCS project team and is being introduced on the W3C mailing list, positive feedback received
  • Alex: asked a question about the granularity of the access to the data, discussion on the relationship with VSS layers and access groups

  • Piotr: there is another method to access the data called "content provider", it would be good to check the access control with this approach as well

  • the concept will be discussed further at the upcoming F2F

F2F agenda review and preparation organization

  • agenda updated on line, look here

Tuesday 14 January - 5pm CET


  • Sachin, Stefan, Markku, Marcin, Gunnar, Johan, Alexander, Stephen L, Philippe
  • apologies: Guru


  • F2F meeting organization - logistics
  • F2F agenda topics - preparation readiness


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

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

  • Stefan shows this slidedeck,  sample code is there (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 it
  • Alex: very good presentation, thanks

Next call

  • 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


  • Jimhyuk, Patrick, Pontus, Stefan, Piotr, Gunnar, Guru, Johan, Alexander Stephen L, Philippe
  • apologies: Sachin, Pete


  • Next events: calls and F2F meeting organization - date planning - look here
  • F2F agenda: gathering of topics


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


  • Stefan, Piotr, Gunnar, Guru, Johan, Pete, Stephen L, Sachin, Viet-Ahn, Philippe, 10 participants
  • apologies: Alexander


  • 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


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.


  • 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


  • 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:
  • 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:
  • Assignment of work items (for the next meeting)

    1. how permission schemes are managed for custom properties, how access control is managed, vendor extension of the permission (assigned to: Stefan)
    2. 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)
    3. review of the Android Compatibility Definition Document (assigned to: Sachin)

22 October 2019

slide deck

Minutes in Word

8 October 2019

slide deck

Minutes in Word

25 September 2019

Minutes in Word

10 September 2019

Minutes in Word


28 August 2019

Minutes in Word


VSS presentation (warning) NOTE the current VSS is not at the link listed in this presentation.  It is now stored at

13 August 2019

Minutes in Word

30 July 2019 Project Kickoff Meeting

Minutes in Word

  • No labels