Versions Compared

Old Version 187

changes.mady.by.user Philippe Robin

Saved on

compared with

New Version Current

changes.mady.by.user Gunnar Andersson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minutes

Current thread (from February 2021 on-wards): investigates this architecture

Previous thread (until January 2021) : External Data Server Proof-Of-Concept - Work Breakdown Structure

...

Zoom link
meeting ID  : 993 7365 2562
 password: Vhal!21
local dial-in numbers: https://zoom.us/u/aqC5ms8E7

Agenda

Backlog

...

Backlog


...

Tuesday December 7 – 5:00 PM CET
Participants

  • Kyrylo Skidanov (EPAM)
  • Stephen (Renesas)
  • Stefan Wysocki
  • Gunnar (COVESA)
  • Alexander Domin


Minutes

Kirill:  Procuring a development board.  Apparently graphics subsystem not starting on ARM64 (Google confirmed this...)  Being investigated.
  x86 emulation might be an option.  More disk space coming soon to prepare for builds.

Alexander: 

Further discussions about challenges of mapping VSS/different environments.
The Franca mapping file is very flexible - can map to Franca attribute (including subscription of changes, or to just a broadcast
or to an explicit getter function exposed on SOME/IP.  Similarly for writing, but it is defined independently => in theory different mappings for reading vs writing.

Stefan:  At the moment interested in Vehicle-Properties translation primarily, but it is interesting to see this other concept progress.
...Good to see that Microsoft's C++ implemented GraphQL is mature enough.  Apollo tried before which meant putting Java into the HAL layer, not ideal.

Compiling vspec2aaproperties code

Stefan: I tried also this but little progress (challenges with diferent computers, environment, disk space).







---


Tuesday November 30 – 5:00 PM CET
Participants

  • Kyrylo Skidanov (EPAM)
  • Johan (Melco)
  • Stephen (Renesas)
  • Manu (Bittium)
  • Philippe Robin (COVESA)
  • Gunnar (COVESA)
  • Alexander Domin (BMW)


Minutes

  • Updates on vspec2aaproperties code generator.  Generated code through compilation with minor changes.
    Need to add generation of getProperty... function for fetching dependent properties needed for complex calculation.  This function is currently not included by reference to the implementation. 
  • Manu: .... prefers generating these functions (variants depending on data type) according to if they are needed, which was done similarly with the type-conversion functions.
  • Discussion about setting up a repeatable build environment.  Apparently the standard way of building AOSP is "the whole system" (although rebuilding in the same directory structure is of course incremental and relatively fast).  How is AOSP builds normally set up for CI systems???  There ought to be a structured way to reuse a cache of already built artifacts.
  • Explanation from Alexander about the set of tooling (mentioned last week's minutes).  A demonstration of the technology planned for the next CVII Tech Stack meeting instead, since it is also more widely applicable beyond Android.


Tuesday November 23 – 5:00 PM CET

Participants

  • Kyrylo Skidanov (EPAM)
  • Johan (Melco)
  • Stephen (Renesas)
  • Manu (Bittium)
  • Philippe Robin (COVESA)
  • Gunnar (COVESA

Apologies:

  • Alexander Domin (BMW)

Minutes

  • Looking into the BMW code drops so far (Full end-to-end example of SOME/IP signal source to GraphQL server providing VSS data). 
  • AA properties code generator:
    • Manu: I would like to get feedback from the compilation tests before continuing.
    • Need Stefan (TietoEvry)'s input, with more details, e.g. Android version tested on, and how to set up repeatable test environment.
  • AASIG Dev Platform
    • EPAM is willing to bring it up to date.
    • Starting with Emulator as main target, and update to Android 12
    • Then look at hardware BSPs later - most are likely still on 11, (but that's OK - use git branches or just different handling in the scripts to handle version diff).
    • Is the AASIG components work not integrated?
      • Manifest repositories exist, pointing to some AASIG created software components but they are not integrated yet.



...

Tuesday 3 August – 5:00 PM CEST

  • Bittium and Tieto participants are back from vacation
  • Stefan delivers a recap on the plan for the demo for the upcoming AMM
  • then Stefan and Alex discuss the translation from vehicle properties from VSS
  • eventually Philippe asks Bittium people to consider a possible contribution to the demo or the tests of the demo, to be discussed further in the upcoming calls

Tuesday 6 July – 5:00 PM CEST

  • AMM dates are set for first week (4→8 October).  Location, likely Germany and virtual hybrid.
  • Tools.  Alignment process ongoing (which creates some open PRs and issues in VSS and vss-tools before that)

Last week we established these next actions on the property translation work.  Status updates below.

  • Feedback from VSS working group about general strategies for metadata (hierarchical?)  Gunnar Andersson

    • UPDATE: Question was raised (as a heads-up, future topic) last week's VSS.  Will check for more feedback this evening but it probably needs a bit of time to get all stakeholders involved (it's a fundamental question).

  • Start work on code generator in vss-tools/contrib, output according to chapter "How to describe the complex translations" above.

    • Question: Introduce templating language (JINJA2) in vss-tools?  It is used in vsc-tools and could be useful also for VSS for more complex code generation than we have today.
      • UPDATE: We still have no assigned programming resource to get this started
  • Stefan awaiting approval to publish "hard-coded" example code.
    • UPDATE: Approvals slow because of vacations.  Won't happen before Stefan's vacation.  (A few actions for Stefan to do, testing etc.)

Tuesday 29 June - 500pm CEST

Participants

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

Minutes

tool strategy

  • Alex: we are fixing some bugs and adapting to VSS 2.0 on our graphql tooling
  • Alex: we are also working on converting Franca files to VSS files and then to vehicle properties, however the open source publishing process was a major obstacle
  • Alex: BMW will reconnect the VHAL project in 2 weeks

vehicle properties

  • Gunnar shows the wiki page resulting from the import of the file sent by Stefan
  • Gunnar updates the next steps section of the wiki page on-line

TTuesday 22 June - 500pm CEST

Participants

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

Minutes

VSS to AOSP translation - WBS

Tuesday 15 June - 500pm CEST

Participants

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

Minutes

VSS to AOSP translation - WBS

Code Block
titleTyrePressure
conversionMap["Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Pressure"] = std::bind(convertFloat,
std::placeholders::_1, VehicleProperty::TIRE_PRESSURE, (int32_t) VehicleAreaWheel::LEFT_FRONT, 1.0f, 0.0f);
conversionMap["Vehicle.Chassis.Axle.Row1.Wheel.Right.Tire.Pressure"] = std::bind(convertFloat,
std::placeholders::_1, VehicleProperty::TIRE_PRESSURE, (int32_t) VehicleAreaWheel::RIGHT_FRONT, 1.0f, 0.0f);
conversionMap["Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure"] = std::bind(convertFloat,
std::placeholders::_1, VehicleProperty::TIRE_PRESSURE, (int32_t) VehicleAreaWheel::LEFT_REAR, 1.0f, 0.0f);
conversionMap["Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.Pressure"] = std::bind(convertFloat,
std::placeholders::_1, VehicleProperty::TIRE_PRESSURE, (int32_t) VehicleAreaWheel::RIGHT_REAR, 1.0f, 0.0f);
  • TODO Alex & Stefan to add the conclusion of the discussion

Tuesday 8 June - 500pm CEST

Participants

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

Minutes

too graphql generator

  • Gunnar gives an update on the graphql generator he has published
  • discussion about which implementation of the graphql generator to maintains
  • discussion on the type support in the generator
  • Alex will check when he and Stefan can deliver a presentation of the work done at BMW on this topic and on the open source code which is now in the publishing process

discussion on VSS to AOSP translation

AASIG development platform

  • Mannu reports on the building try out he made with the AASIG dev platform

...

Tuesday 1 June - 500pm CEST

Participants

  • Stefan, Johan, Mannu, Gunnar, Philippe

...

VSS to AOSP translation

reschedule of CVII workshop event

  • June CVII workshop moved one week later to Thu 1 July; 16:00 CEST (duration: 3h max)
  • this date is fine for Stefan and Johan, Mannu will be OOO

Tuesday 25 May - 500pm CEST

"Development platform"

Manu's feedback

...

  • Stefan created a writeup in Markdown → now posted as Wiki Page here.
  • Stefan will check about status of the translation code ("manually written example").

Tuesday 18 May - 500pm CET

Participants

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

...

Tuesday 11 May - 500pm CET

Participants

  • Stefan, Manu, Johan, Stephen, Gunnar, Philippe

...

  • TODO Stefan to update the VHAL project work breakdown structure to reflect the revised project scope which is now on the generation of Google vehicle properties from VSS

May 4-7 Virtual AMM - VHAL sessions

Tuesday 27 April - 500pm CET

Participants

  • Stefan, Johan, Chris, Gunnar, Philippe

...

  • review of AASIG VHAL short update report and slides for the AASIG VHAL tech workshop and topics for the next 6 months

  • TODO Stefan to split the current slide deck into 3 parts as listed above

Tuesday 20 April - 500pm CET

Participants

  • Stefan, Johan, Gunnar, Philippe

...

  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-122
    assigned to Gunnar Andersson that will add a final comment (reminder)
    • Gunnar: the work done on AASIG-122 draw the attention of the VSS team and might lead to some changes in VSS

Tuesday 13 April - 500pm CET

Participants

  • Stefan, Johan, Stephen, Gunnar, Philippe

...

  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-122
    assigned to Gunnar Andersson that will add a final comment
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-110
    the concept (using graphql)  was shown in a demo already,  Stefan Wysocki please add a comment and mark it as done, thanks !
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-44
    and subtasks will be revisited when we know better how Bosch code recently dropped fits into our work
  • sprint extended until 30 April

Tuesday 6 April - 500pm CET

Participants

  • Stefan, Johan, Chris, Philippe
  • apologies: Gunnar (Mobex webinar)

...

Tuesday 30 March - 500pm CET

Participants

  • Stefan, Stephen, Gunnar, Philippe
  • apologies: Johan

...

  • Stefan: manual translation of VSS to vehicle properties is done, an early implementation of the translator might be available at the time of AMM, possible, the demo will show how the generated code looks like
  • Stefan: will report the progress in
    Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-123

Tuesday 16 March - 500pm CET

Participants

  • Stefan, Johan, Stephen, Gunnar, Philippe

...

  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-37
    and sub-tasks thrown to backlog
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-54
    and sub-tasks thrown to backlog since the team stopped working on the External Data Server concept and status back to ToDo
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-44
    and sub-tasks thrown to backlog for the (same) reason above and status back to ToDo
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-38
    thrown to backlog

Tuesday 9 March - 500pm CET

Participants

  • Stefan, Johan, Philippe
  • apologies: Stephen Lawrence, Gunnar

...

  • TODO  Stefan Wysocki Stefan to check with the Tieto management about the preparation and resourcing for a VHAL demo to be shown at the upcoming virtual AMM

Tuesday 2 March - 500pm CET

Participants

  • Stefan, Johan, Stephen Lawrence, Gunnar & Philippe

...

  • TODOs Tieto (i.e. Piotr) to check the publishing status of the signal2service spec in the AUTOSAR set of standards
  • TODO  Tieto to check the status of the vsomeip implementation on Android (in github)

Tuesday 23 February - 500pm CET

Participants

  • Stefan, Piotr, Chris, Stephen Lawrence, Gunnar & Philippe

...

  • Next dissemination event will be the GENIVI virtual AMM scheduled on 4-7 May
  • Philippe: asks TietoEVRY whether it would be appropriate to show a VHAL connected to AUTOSAR demo, in 2-month time
  • discussion on interfacing with AUTOSAR using the signal2service mapping defined by AUTOSAR
  • TODO Tieto to check the publishing status of the signal2service spec in the AUTOSAR set of standards
  • TODO Gunnar and/or Tieto to check the status of the vsomeip implementation on Android (in github)

Tuesday 16 February - 500pm CET

Participants

  • Johan, Stefan, Stephen Lawrence, Gunnar & Philippe

...

  • we will switch to zoom instead of webex for next week call

Tuesday 9 February - 500pm CET

Participants

  • Johan, Stefan, Piotr (part-time) Stephen Lawrence, Gunnar & Philippe

...

  • browsing through this slidedeck and EAP diagram & discussion
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-122
    created and assigned to Johan

Tuesday 2 February - 500pm CET

Participants

  • Johan, Stefan, Chris, Stephen Lawrence, Gunnar & Philippe

...

  • Philippe: the second CVII workshop is scheduled on Thursday 18 February 16:00-20:00 CET, we have included a status report on existing projects in the schedule (see blog)
  • Gunnar: 15' will be allocated to the VHAL status report
  • Philippe: Stefan Wysocki can you deliver this ? this will likely reuse and update an existing VHAL project presentation
  • Stefan: yes, I can
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-121
    created for tracking

Tuesday 26 January - 500pm CET

Participants

  • Johan, Stefan, Stephen Lawrence, Gunnar & Philippe

...

Tuesday 19 January- 500pm CET

Participants

  • Johan, Piotr, Stefan, Stephen Lawrence
  • apologies: Gunnar & Philippe (in another call)

...

Tuesday 12 January- 500pm CET

Participants

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

...

Tuesday 15 December - 500pm CET

Participants

  • Chris, Gunnar, Johan, Piotr, Stefan, Stephen Lawrence, Philippe

...

  • no VHAL call next week, and the week after, and the 1st week of January
  • next VHAL call is scheduled on Tuesday 12 January

Tuesday 8 December - 500pm CET

Participants

  • Gunnar, Johan, Piotr, Stefan, Stephen Lawrence, Philippe
  • apologies: Chris

...

  • Stefan: we need to show the permission control promised by Alex, this is an important piece of code for the data server, it will allow us to validate the currently used EDS architecture, before digging into other architectures as suggested by Chris
  • Gunnar: I agreed we need access control
  • Gunnar: we will then have an opportunity to build other variants of the architecture and use a translation of VSS into vehicle properties, the initial work on translation can start now
  • Philippe: suggests to have a working session on the translation next week (instead of having an all hands report which can be done with a slide deck distribution)
  • all agree this is a good proposal
  • Gunnar, Stefan and al. will prepare the working session via the mailing list

Tuesday 1 December - 500pm CET

Participants

  • chris, gunnar, johan, piotr (20mn only), stefan (10mn only), stephen lawrence, philippe

...

Tuesday 10 November - 500pm CET

Participants

  • Alexander Domin, Johan Strand, Stephen Lawrence, Gunnar, Philippe
  • apologies: Stefan Wysocki

...

  • Alex: some ideas on my desktop, although not formalized as a set of specifications yet
  • the recording of Alex's pitch is here
  • some hints on the discussion are given below
  • in the web when using graphql,  there is a user login name and password to connect to the data
  • you need to authorize yourseld on the phone, the session is valid for a certain period of time, if you do things, the session will remain
  • the server knows you
  • before you can use a graphql application,  you need to register, there is a link between the graphql server and your role
  • let us switch in the car environment and let us deploy some kind of a server in the car
  • what we learned from the web, graphql needs a name and a password
  • the app which is installed in the vehicle environment shouf be identified and signed / qualified as coming from the BMW store or the OEM specific store
  • the app should be made trusted in the environment
  • Johan: I agree with the approach
  • Alex:  in the web we have roles & permissions stored in the server but not applicable to the vehicle environment
  • more on the token: in the web, we have a token enhancement, after we logged on to the server and run through the authentication process, we got a token enhancement
  • we can have the same in the vehicle environement
  • (not captured...)
  • access rights: each and every app should bring permission groups in the manifest file
  • let us assume the app is allowed to access 20 atrributes
  • let us assume the user driver needs to have more permissions that the user "baby"
  • how do we handle this ?
  • Johan: I understand the difference between the web and the car
  • (not captured...)
  • Alex: in the car we have an app where the user authorizes him once and then this app gives rights to all other apps that need it
  • discussion continues on the sw architecture
  • Gunnar: the key thing for me is that you can include the information that is to be exchanged in the token
  • discussion on the token structure
  • jira: AASIG-117 - Prepare use cases for the security token validation In Progress is in-progress

Tuesday 3 November  - 500pm CET

Participants

  • Alexander Domin, Johan Strand, Stefan Wysocki, Guru, Stephen Lawrence, Gunnar, Philippe

...

  • Gunnar: we need to finalize the building of the platform and the manifest
  • Alex: what about the validation of the security token approach ?
  • Gunnar: the GENIVI cybersecurity team can help reviewing the desing but will not implement anything
  • TODO Alex prepare the use cases for the security token validation for next week (10 November), jira:
    Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-117

Friday 26 October - 3pm-7pm CET - GENIVI AMM AASIG VHAL working session

GENIVI AMM AASIG VHAL working session:: slide deck and session recording are at GENIVI Virtual Member Meeting October 2020

Tuesday 6 October - 500pm CET

Participants

  • Alexander Domin, Johan Strand, Stefan Wysocki, Guru, Stephen Lawrence, Gunnar, Philippe

...

  • Philippe: proposes the team to update the work breakdown structure as the other teams did, this will help identifying the discussion topics for the working session

  • External Data Server Proof-Of-Concept - Work Breakdown Structure wiki page updated online with inputs from Gunnar, Alex and Stefan

  • relevant Jira tickets updated online
    • Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyAASIG-47
      ,
    • Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyAASIG-52
      ,
    • Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyAASIG-51
      ,
    • Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyAASIG-53
      updated on line
  • hint for the working session content: please have a look at CCS working session content which was derived also from the work breakdown structure update

Tuesday 22 September - 500pm CET

Participants

  • Alexander Domin, Johan Strand, Stefan Wysocki, Stephen Lawrence, Gunnar, Philippe

...

Tuesday 15 September - 500pm CET

Participants

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

...

  • Gunnar: openDS still not working on the test platform
  • Gunnar: I need to ask Daniel Wilms about the status of the graphql tooling
  • still waiting for the permission enforcement implementation

Tuesday 8 September - 500pm CET

Participants

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

...

  • 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 
    Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-58
    )
  • 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
    Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-116
    )

Tuesday 1 September - 500pm CET

Participants

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

...

  • Permission enforcement implementation

  • Outcome of call on OpenDS

  • Feature content for MS3 demo

  • jira review

Tuesday 18 August - 500pm CET

Participants

  • Piotr Krawczyk
  • Johan Strand
  • Stefan Wysocki

...

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

Participants

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

...

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

Participants

  • 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

Participants

  • Philippe
  • apologies: Stefan, Gunnar (vacation)

...

  • 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("http://192.168.56.101:4000/") // 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/IAuthenticationServiceImpl.java:41:            // TODO decide when handle this exception
    • service/src/main/java/org/genivi/vss/authenticationservice/IAuthenticationServiceImpl.java:44:        // TODO Make the key shared between the server and client or change the algo to asymmetric
    • service/src/main/java/org/genivi/vss/authenticationservice/IAuthenticationServiceImpl.java:61:                // TODO Filter out the non-genivi-vss permissions
    • vss-sdk-lib/src/main/java/org/genivi/vss/authenticationservice/VSS.java:12:    // TODO Make it autogenerated from VSS
    • vss-sdk-lib/src/main/java/org/genivi/vss/authenticationservice/VSS.java:17:    // 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: https://at.projects.genivi.org/jira/secure/ViewProfile.jspa?name=Stefan.Wysocki
  • "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

Participants

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

...

  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-38
    • 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
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-55
    • discussion on some code generation
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-56
    • discussion on the content of the java web token JWTK
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-47
    • Gunnar will contact Daniel Wilms about the VSS and tooling around, ticket assigned to Gunnar
  • demo readiness
    • need to review Stefan's pull request
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-57
    • 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

Participants

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

...

  • 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

Participants

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

...

Tuesday 9 June - 500pm CET

Participants

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

...

  • Piotr will put some effort this week, need to sync with SteFan on VHAL implementation tasks
  • Stefan: updated the tickets
    Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-43
    &
    Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-148
  • 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
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-55
    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
      Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyAASIG-42
      , 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 
      Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-149
    • Gunnar has started some analysis on the data generation but has not finalized an approach yet,

Tuesday 2 June - 500pm CET

Participants

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

...

  • Philippe: initiated a Jira tracker for the proof-of-concet implementation, look at
    Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-36

Tuesday 19 May - 500pm CET

Participants

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

...

  • 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
    Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyAASIG-62
  •  (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

Minutes

Tuesday 5 May - 500pm CET

Participants

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

...

  • 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

Participants

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

...

  • 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

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

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

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

Minutes&Participants

F2F meeting organization

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)

    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

VSS-to-SomeIP

28 August 2019

Minutes in Word

Vehicle_Properties_Architecture

VSS presentation (warning) 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

13 August 2019

Minutes in Word

30 July 2019 Project Kickoff Meeting

Minutes in Word