Page History

...

• Philippe reports the outcome of the two calls he had with Automat project participants last weelweek
  • Renault participant on Wed 31 July
  • Automat cybersecurity WP lead (from Trialog) on Tue 30 July (A,ntonio)
• call wirh Renault

  • VW had the biggest budget share in the automat project (up to 25%)

  • the VW team involved was from the After Sales division (not from the R&D) and had a very short term vision of their needs

  • VW interest was on what happened in the vehicle before a failure using histograms, because they wanted to minimize the telecom costs for data transmission and therefore the quantity of data transmitted

  • there were actually two competing approaches for the vehicle data telemetry in the automat project: histograms for VW vs time series for Renault and Fiat (CRF Fiat R&D), the time series approach consisted in transmitting as many raw data as possible and processing them offline with big computers

  • At the beginning of the project, HERE proposed to use the Sensoris approach for gathering vehicle data but there was nothing like histograms in Sensoris and this approach was not investigated further

  • Renault did a proof-of-concept using a dongle to gather the data, VW and CRF decided to use existing ECUs (CRF used an existing TCU (communication box)

  • At the end of the project the OEMs decided not to continue.

• call with Trialog

  • Trialog pointed to the following position paper from BDVA (Big Data Value Association), Antonio was one of the main contributors to this paper based  on his work in the automat project with a particular focus on the privacy for big data

    • link: http://www.bdva.eu/sites/default/files/BDVA%20DataSharingSpace%20PositionPaper_April2019_V1.pdf

  • Antonio mentions also the SAREF work on data ontologies pushed by EU whose motivation is to define and promote a European standard

    • link: https://www.etsi.org/newsroom/press-releases/1620-2019-06-etsi-releases-3-new-ontology-specifications-for-smart-cities-industry-4-0-and-smart-agriculture

  • Antonio mentions W3C / Web of Things (WoT) work whose charter starts with a statement on the ecosystem fragmentation

    • link: https://www.w3.org/WoT/

  • data privacy / security in automat

    • the interesting feature of the automat cybersecurity work is that it relies on existing standards (at the time of the project execution timeline)

    • Antonio said it would be good to review and restructure and update the automat cybersecurity framework according to take into account recent US NIST work that takes into account the product lifecycle (to be shared witl the GENIVI security team)

• Conclusion on automat

  • Philippe's personal conclusion is that we have looked enough into Automat, unless we have an indication that Autosar will eventually use Automat CVIM as an input to their Cloud Services WG work, we in GENIVI should focus on Sensoris and VSS and ISO ExVe, we will also coordinate with Autosar on this

  • call participants agree

  • Guru: said he will look further into requirements for histograms as defined by automat anc check what was not supported in Sensoris

  • However the work done in automat on cybersecurity is good and relates to a big data architecture, Philippe recommends the GENIVI security team to review it and amend it w.r.t. US NIST work and extract possibly use cases to benchmark the MoRa tool

...

• Philippe: said he added P.Car (from AOSP) to the list of projects on Vehicle Data APIs we have to consider for the gap analysis
  • P.Car is investigated in the AASIG Vehicle Data APIs subproject which has started last week, look here
• Kevin: asked whether we will have one or several deliverables on gap analysis
• Philippe: said he is fine with both approaches, we need an executive summary to provide an overview of the results anyway, the format of the deliverables could possibly followed the one of the technical papers published earlier like GPRO white paper
• Philippe: we need to assign sections / deliverables to contributors and nominate a document owner, we will create the relevant Jira iickets in the new sprint that will start next Monday
  • Kevin: said he (and his team) can do a contribution
  • Guru: will check with Gerald whether Bosch can do a contribution

...

• VCS tracker https://at.projects.genivi.org/jira/browse/VCS

• Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-38

• VCS-45
•  commented and updated, subtask

  Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-47

  on how GENIVI could access ISO specs created and assigned to Steve

• Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-45

   closing remarks on automat project added

• Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-46

  table of content for gap analysis doc reviewed and agreed, closing remark added (see above), done

• Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key VCS-28

  we need to find an owner for the review of CCC specs
• we will close the sprint on next Monday 12 Augustto be updated

Monday, July 29

Participants

...