Page History

Next Meeting -

...

24 March 5:00pm CET

https://zoom.us/j/453590365

...

Agenda (proposal)

Agenda items (to be prioritized at the beginning of the call)

• authentication implementation (work sharing between BMW & TietoEVRY)
• graphql and nodeJS installation
• staffing the EDS PoC (again !)PoC
• PoC planning
• 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

External Data Server Proof-Of-Concept - Work Breakdown Structure

Tuesday 17 March - 500pm CET

Participants

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

Agenda

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

Minutes

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

  • 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

...

• 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

...