JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project - On Hold |
We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies. |
Participants
Planned agenda
Minutes
Kevin moderates the call. Thanks.
1- Update on automat project
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.
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
Antonio mentions also the SAREF work on data ontologies pushed by EU whose motivation is to define and promote a European standard
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)
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
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
2- Gap analysis deliverable: document owner and contributors, table of content update
3- Scrum review
Participants
Apologies
Planned agenda
Minutes
Kevin moderates the call. Thanks.
Gap analysis deliverable proposal
Extended Vehicle ISO 20078 summary
Participants
Apologies
Planned agenda
Minutes
Gap analysis CVIM vs VSS
Sprint review
VCS: Kevin has a login and should be to update the wiki eventually
current sprint review
- VCS-25Getting issue details... STATUS survey sensoris spec is done
gap analysis between sensoris and cvim is the next step
Guru will add a comment and close the ticket
- VCS-37Getting issue details... STATUS review CS project charter
Daniel & Petar will review it
Kevin approved it a couple of weeks ago
Philippe: deliverables will be added to the charter later
- VCS-43Getting issue details... STATUS Check OADF forum results
philippe will add the link to oadf and add some comments on what is relevant,
assigned to philippe
The link to the minutes is: https://login.openautodrive.org/downloads/presentations/20190612oadfminutesv10pdf,
For accessing the minutes, you need to ask for credentials on the OADF web page at: http://www.openautodrive.org/
relevant sections of the minutes in my opinion are
- VCS-34Getting issue details... STATUS Gap analysis between Sensoris and CVIM
gunnar: we do not need to compare sensoris and cvim data models, we need rather to compare project scope
benjamin: sensoris is more about surroundings, cvim is more about the vehicle
- VCS-39Getting issue details... STATUS Provide an update on Kuksa project
philippe will ping sebastian schidlt
/TODO/ contact ted to know about the background of the story
gunnar and philippe will need to sync on this
Participants
Apologies
Planned agenda
- review of OADF workshop minutes
- discussion on gap analysis deliverable content
- feedback on project charter
- AOB
- JIRA kanban is here (Note, Kanban requires login. This browse project seems to currently work for viewing without login. Please request login if you are active participant....
Minutes
* please find links to material from the corresponding ticket in the JIRA project if not provided here.
Over time the material ought also be summarized as results of the project on the parent Wiki page.
Discussion:
Participants:
apologies:
Agenda:
Minutes
review of Jira tickets, Sprint 1 done, Sprint 2 started
VCS-2 | Analyze data and signal specifications
| Philippe Robin | VCS Sprint 2, VCS Sprint 1 (i.e. carried over from Sprint 1 to Sprint 2) |
VCS-42 | Contact OCF Automotive and check for status | Philippe Robin | added to VCS Sprint 2 |
VCS-41 | Dissemination of connected services projet results (i.e. deliverables, charter, etc.)
| ||
VCS-33 | Perform gap analysis of VSS vs. CVIM
| Benjamin Klotz | added to VCS Sprint 2 |
VCS-40 | Publish AutoMat cybersecurity overview | Petar Vorotnikov | added to VCS Sprint 2 |
VCS-39 | Provide an update on Kuksa project | Sebastian Schildt | added to VCS Sprint 2 |
VCS-37 | Review CS project charter
| Philippe Robin | VCS Sprint 2, VCS Sprint 1 |
VCS-26 | Survey AUTOMAT specifications (Common Vehicle Information Model - CVIM)
| Kevin Valdek | VCS Sprint 2, VCS Sprint 1 |
VCS-38 | Survey ISO Extended Vehicle | Gerald Spreitz | VCS Sprint 2, VCS Sprint 1 |
VCS-34 | Perform gap analysis of Sensoris vs CVIM | Gerald Spreitz | VCS Sprint 2, VCS Sprint 1 |
VCS-25 | Survey SENSORIS specifications
| Gururaja | VCS Sprint 2, VCS Sprint 1 |
VCS-28 | Survey CCC specifications and check for relevance
| Unassigned | VCS Sprint 2 |
Participants:
apologies: Petar (Visteon)
Agenda:
Minutes
Philippe asks participants to review the project charter and provide comments by next week
link: https://www.neutralvehicle.com/ (yet another start-up company)
Participants:
Minutes
automat project security framework:
Petar shows a comprehensive and informative slide deck detailing his findings during his review of the cybersecurity framework, look here
For early July the public release of version 1.0.0 under the CC-BY-ND license is planned.
Public license: Copyright (c) 2017, 2019 SENSORIS Innovation Platform hosted by ERTICO - ITS Europe
This program and the accompanying materials are made available under the terms of the Creative Commons Attribution-NoDerivatives 4.0 International license which accompanies this distribution, and is available at https://creativecommons.org/licenses/by-nd/4.0/legalcode.
Also the Version 1.1.0 will be released for members only. This Version includes the specification of "Job Requests".
Participants:
Minutes
news
project charter
Philippe is preparing a project charter for advertizing our work, we foresee to breakdown the project into 2 stages
Stage 1 focusing on data, i.e. what we are initiating now with an objective to decrease the fragmentation of the ecosystem with several different approaches to describe the vehicle data and the communication framework to access them
Stage 2 focusing on compute, initial though is to look into cloud computing platform to support mobility and vehicle autonomy
the model describes big data for connected cars, it is quite different from VSS, it goes very deep in data harmonization and proposes several layers like signals + measurement layer + data package layer
Gunnar: how is it compared to W3C
Kevin: I have not seen the same information than in W3C
Benjamin: we have a metadata Task Force in W3C, it is part of what next generation will do, we will have different kind of meta data, I would recommend to use the best practice, no competition now from W3C because there is no spec on this topic yet
sensoris va automat ==> Gerald / Kevin (due date: 3-week time
vss vs sensoris ==> not assigned yet
vss vs automat ==> Benjamin (after submitting his thesis at the end of the month) , Gunnar
(This call was not intended/schedule and therefore had no official invite. Therefore only had 3 participants, but we still made progress in discussing the needed steps and plans which will benefit the group for next time)
Participants: Kevin, Petar, Gunnar
Using a Etherpad at Mozilla we captured:
Security guidelines
1. Collect and write down Security guidelines
Idea to produce general security guidelines for different parts of the data-oriented parchitecture.
E.g.
- For this API type you should apply this type of security...
- For this data link ....
- Web services and Mobile App requirements are different
- High Mobility has input to give here
- GENIVI Security group could review, if we have something written down
(We discussed to prepare a draft result first since the Sec Team does not benefit from an undefined "open question" at this point)
Data categories
2. Analyze What type of data is needed for different data users?
- Recognize that fine-grained filtering is needed, and mechanisms for it
but here we rather mean:
- Define names of groups of data, and describe them.
...Service classes that need different refresh rates
- Define groups and needs
Data contracts
- Quick intro to discussion in W3C before. It came up because it relates to the definition of the needs of each party. These needs eventually get formalized into contracts and that is the link.
- Grab-bag of tools/questions/terms to define business contracts or more technical contracts
- A kind of checklist...
- Purpose: Simplify business contracts on data, and make sure details are not lost
Tech constraints, technology choices
What are the Technical constraints that are imposed by the used technology?
- Communication paradigm and protocols (pub/sub, req/res, REST, MQTT)
- Middleware and components standing in the data path - caching layer, service layer, service bus
Surveying existing initiatives
- SENSORIS -> await this week's meeting and announcements, and see the outcome before defining actions
- Automat - Data formats and types and similar things are in their specs. Read and consider alignment.
https://automat-project.eu/content/open-cvim-specification
- W3C protocol content (being worked on with participation in group - but summarizing and presenting to the group is useful). Also Webinar tomorrow.
- CCC - have we confirmed there is nothing to reuse or relate to or is this still active? Reconfirm with PR and GS.
- ... follow up with the rest of the list
Question: SENSORIS - which companies can lead the investigation and alignment?
Answer:
- not Visteon - Petar did not reach anyone working with it
- not HM -
- Bosch? ... figure out this list
Terms/names/definitions
Steps:
- Review existing specs, do they include a Glossary
- ... and/or just start writing it down
Collecting Information in Wiki to complete the picture
- Action for all: Populate the Wiki with useful links
- Example of things to link to:
Other Projects
Specifications
Presentations & Videos
Implementations of basic technologies (open source projects)
Do this on the Connected Services home page: https://at.projects.genivi.org/wiki/x/PIAVAg
Steps/Actions (current and future to be assigned)
- AI(all): First get projects.genivi.org Wiki account if you don't have it (signup link is this one - it is part of JIRA)
- Read AUTOMAT CVIM specification
Future:
- Look at other AUTOMAT docs - are any other important to read?
Participants:
Minutes
roundtable
Participants:
Minutes
Slide #3-4:
Gunnar: needs to identify what are the higher level protocols we use on top of radio links
discussion on the roles to play by various organizations for the definition of data containers, many organizations are currently competing on this
Gerald: where is the most interested area for the genivi group ?
Benjamin: I have multiple perspectives on those topics (slide 3), this is a highly fragmented ecosystem
Petar: IoT style communications are more interesting to me, having a connected vehicle does not mean a vehicle is always connected in my opinion
slide 6 - ISO ExVehicle
BMW: does not know who from BMW is involved
/TODO/ each participant find who in their company is involved in ISO work ExVehicle
/TODO/ Philippe contact Kevin to check whether high-mobility is implementing an alpha version of the ExVehicle concept and ask him to join the call
Gunnar: does everyone has the same understanding of what a neutral server is ?
Gunnar: as genivi we need to work on the interfaces between the various parts of the architecture
Christian: agreed, we need to define the interfaces and *do it first*
slide 6 - Sensoris
Gerald: they have something like a neutral server
/TODO/ each participatant attend or get information on the OADF/Sensoris workshop scheduled in June
discussion on how CCC and W3C sync on those topics
Gunnar: in his opinion, this should not be not a constraint for our work
/TODO/ each participant find who in their company is involved in CCC work
slide 8
automat: it is likely a good idea to check this project because there are 2 OEMs involved (VW, Renault) and also there seems to be a comprehensive work on security and privacy
Philippe: IoT - FYI genivi has a liaison agreement with OCF
/TODO/ Petar look into OCF work
Petar: kuksa project is quite comprehensive
Autosar: cloud services - Benjamin discussed this with Sebastianat the AMM
/TODO/ Philippe contact Sebastian (Bosch) about the Autosar cloud services
slide 11
Gerald: thinks we need to pre-integrate some parts of the reference architecture
/TODO/ Philippe ask Daniel (BMW) why he has a concern about abstract layers and invite him to join the call
Participants:
Minutes