Monday, July 22
Participants
- Benjamin Klotz (BMW)
- Daniel Wilms (BMW)
- Gururaja N (Bosch)
- Kevin Valdek (High Mobility)
- Petar Vorotnikov (Visteon)
- Gunnar Andersson (GENIVI)
...
Gap analysis CVIM vs VSS
Benjamin: there is a lot of overlap between cvim & vss, it would be good to have someone from the automat project in the call
/TODO/ Philippe contact automat project manager & renault (since Renault is one of the project participants)
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | VCS-45 |
---|
|
created
Sprint review
Monday, July 15
Participants
- Gerald Spreitz (Bosch)
- Michael Ger (Cloudera)
- Benjamin Klotz (BMW)
- Daniel Wilms (BMW)
- Ilios Galil (Obigo)
- Gururaja N (Bosch)
- Kevin Valdek (High Mobility)
- Petar Vorotnikov (Visteon)
- Gunnar Andersson (GENIVI)
...
- Michael Ger asked for login. Gunnar answered via email.
- Gunnar asked every presenter to update their corresponding JIRA ticket. If anyone is still having issues with login, email Gunnar and/or Philippe (on vacation this week).
- Benjamin's presentation was a little short on time. Decided to follow up next week on more detailed discussion on comparing the data models.
- Gunnar will create a ticket for "gap analysis" accordingly.
Monday, July 8
Participants:
- Benjamin (BMW)
- Gerald (Bosch)
- Guru (Bosch)
- Daniel (BMW)
- Petar (Visteon)
- Magnus (Melco)
- Ilios (Obigo)
- Gunnar
- Philippe
...
review of Jira tickets, Sprint 1 done, Sprint 2 started
VCS-2 | Analyze data and signal specifications - We need to start defining the content and format of the deliverables for those analysis activities
| 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.) - new epics created for tracking the publishing of results
|
|
|
VCS-33 | Perform gap analysis of VSS vs. CVIM - summary change : comparison changed to gap analysis
| 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 - the charter is attached to the Jira ticket
- /TODO/ all review the charter and provide comments in Jira
| Philippe Robin | VCS Sprint 2, VCS Sprint 1 |
VCS-26 | Survey AUTOMAT specifications (Common Vehicle Information Model - CVIM) - findings should be presented shortly at the next call and then published to VCS-2 recommendation
| 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 - Guru will start looking at the Sensoris specifications now (i.e. before the specifications are published which should happen anytime soon) since as Bosch he has access to it
| Gururaja | VCS Sprint 2, VCS Sprint 1 |
VCS-28 | Survey CCC specifications and check for relevance - we need someone to take this work item
| Unassigned | VCS Sprint 2 |
Monday, July 1
Participants:
- Benjamin (BMW)
- Gerald (Bosch)
- Guru (Bosch)
- Daniel (BMW)
- Kevin (High_Mobility)
- Gunnar
- Philippe
...
- Connected Services project charter
- ISO Extended Vehicle update
- W3C work status
- Gunnar presents the content of the following wiki page Connected Services: W3C VISS/VSI specification status
- discussion on proff-of-concept implementation of the VISS/VSI
- Kevin: is there a general plan/timeline for VSS Gen2 ?
- Benjamin: things will be delayed until the data models for transportation workshop has happened (scheduled on 12-13 September 2019)(look here)
- current WG charter started on May 2018 and will end on June 2020,
Jira |
---|
server | JIRA |
---|
serverId | 121ddff2-c571-320f-9e4d-d5b9371533bd |
---|
key | VCS-27 |
---|
|
commented
- Sensoris
- Gerald shows a slide deck (link TO BE ADDED) from Bosch describing the status of Sensoris work
- Version 1.0.0 of the Sensoris specification will be released in the next days under CC-ND license
- data provided by Sensoris are not only about the vehicles but about the environment
- Version 1.1.0 will introduce the concept of "jobs"
- jobs = login jobs running for a certain period of time for a certain fleet of vehicles
- Gunnar: it would be good to identify how much overlap we have, shows the interest of different domain taxonomies
- Gerald: it would be good also to set up a call with the sensoris project once we have reviewed the Sensoris specification that will be published soon
- AOB
- telco schedule
- DECISION we will start scheduling the weekly call on Monday afternoons at 4pm CET next week (8 July)
- (added offline) cloudera and autonomic.ai which are based on US Pacific coast have been invited to join
Monday 24 June weekly call
Participants:
- Petar (Visteon)
- Gerald (Bosch)
- Daniel (BMW)
- Gunnar
- Philippe
...
automat project security framework:
- W3C
- Gunnar introduces the wiki page he prepared for describing the status of W3C work, he will present the status in the next call
- Sensoris
- Gerald contacted his Bosch colleague who attended the Open Auto Drive Forum (OADF) two weeks ago, however his colleague is rather interested in HD maps and not so much by the vehicle sensor data which is Sensoris project focus
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".
- added offline: Philippe spotted a one-year old presentation of the Sensoris project web site, link, reading this presentation is recommended, the presentation shown at the OADF event two weeks was much less informative
- AOB
- schedule of weekly calls
- Philippe: we got a request to shift the call later in the afternoon in order to allow US participants to join. There seems to be possible participants from US Pacific timezone as well
- quick poll: Daniel 4-5pm CET is the latest possible timeslot, Petar 4-5pm or 5-6pm CET is fine, Gerald 4-5pm or 5-6pm CET
- this time is ok for US Central/Eastern but is anyway too early for US Pacific, we will likely end up with a second US Pacific friendly call
- time for the Monday weekly call will be confirmed later this week
Monday 17 June weekly call
Participants:
- Petar (Visteon)
- Kevin (High Mobility)
- Benjamin (BMW)
- Gerald (Bosch)
- Ilios (Obigo) new participant
- Gunnar
- Philippe
...
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
- this charter will be shared with this project participants
- project tracker
- new participant
- Ilios introduced himself, he works for Obigo (Korea) and is their representative in Europe, he is based in Portugal-based representative attended the weekly call, he will be an observer for the time being, we had a discussion on the GENIVI Korea REG
- Gerald: asked Iliol whether there are public funded projects related to vehicle data in Korea
- project status
- we use the Jira tickets of the active sprint
- Kevin (High-Mobility) has reviewed the automat project Commoin Vehicle Information Model and presented his findings
VCS-26 - Survey AUTOMAT specifications (Common Vehicle Information Model - CVIM) In Progressthe 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
- Kevin will summarize his findings in the wiki
- Petar (Visteon) is reviewing the automat project security model
VCS-32 - Read AUTOMAT security document In Progress - Gerald (Bosch) will spot the colleague within Bosch who attended the OADF conference, objective is to learn about the Sensoris specifications status
VCS-25 - Survey SENSORIS specifications To Do - Gerald: we need to make a comparison between the various data and protocol specifications
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
- Jira tickets created in VCS
Wednesday 12 June
Webinar on W3C Auto WG & GENIVI collaboration, VSS and Vehicle Data definition future steps
Wednesday, June 12, 1300 CEST
recording
Monday 10 June - informal call
(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)
...
- 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 -- AI: Kevin -- read and summarize, present next week
- AUTOMAT Security document -- AI: Petar -- read and summarize, present next week
Future:
- Look at other AUTOMAT docs - are any other important to read?
Monday 3 June weekly call
Participants:
- Petar (Visteon)
- Christian (BMW) (partially)
- Kevin (High Mobility)
- Rafael (xapix)
- Stephen L
- Gunnar
- Philippe
- apologies: Sebastian (Bosch) vacation
...
roundtable
- Rafael: xapix is a German company based in Berlin trying to create an api automotive platform www.xapix.io
- takeaway from AMM
- Kevin: liked to talk about the standardization of car data, VSS, VSS 2
- high mobility has a different perspective, establishing the framework between high mobility, the car and the cloud
- a lot of different protocols, not only VSS 2 but also several others
- discussion on the various protocols
- Gunnar: at AMM we got a presentation by cloudera on the way data are managed in an automotive api framework (big data architecture)
- Discussion followed on capturing all the different players/users of the architecture. Third-party "app" development API, is that a programming API or "only" the W3C REST-based architecture?
- High level vision on the project scope
- Gunnar: shows this slide deck
- Petar: agrees totally with slides 3&4
- one question on how to describe a behavior/service, need to represent different data types, and how to represent data that is made up of combining data from several sources.
- Gunnar: When it comes to combining signals into more refined data, the VSM project is investigating exactly that. It provides currently a python implementation. This can be useful to run on powerful IT systems, and/or be further refined to a optimized compiled code through code-generation for example.
- look at: GitHub/GENIVI/vehicle_signal_manager
- Kevin: I have a more organisational level, question, is VSS 2 more based on REST ?
- clarification brought by Gunnar on the various topics wip at W3C: VISS, VSS 2, etc.
- Clarifying VSS (Data Model @GENIVI GitHub), VISS v1 (W3C specification, which does also refer to VSS as the (minimum) data that shall be provided. VISS v2 (ongoing, in combination of augmenting VSS v2 to the needs). VISS v2 primarily focuses on adding HTTP/REST but some augmentations of the underlying features and data models happen in combination with this.
- Clarifying differences of work in data definition:
- data-model description (Exemplified by VSS - shared among implementors)
- actual data names and descriptions (Also exemplified by VSS - shared among data providers/users)
- actual data names and descriptions (E.g. proprietary extended VSS additional, e.g. OEM private)
- Notice that VSS provides two different roles - defining HOW to define data, and also WHAT data, but these can be treated separately!
- There is some talk of "other data models" in W3C, not clear if this is just other proprietary data, described in VSS-like format, or if it is described in some other format. Also not clear what those other formats might be. VSS is generally adapted to match the needs that come up.
- The fact that some companies are worried to agree that all data names/descriptions are shared tend to block the discussion. We all understand that some data definitions are unique and private and VSS v1 already described private extensions. We understand that we benefit first from a shared way to describe it, and shared tooling, second that we also can benefit from some data being shared and defined (e.g. any "developer API" *requires* that to be defined at some point), and we also agree that companies may have some own unique and private data. Key point: No part should block progress on any other part.
- Kevin asked about if W3C VISS service covers security access control features. Gunnar answered that it is specified weakly on VISS v1 (but that still allows for implementors to add it), and that in v2 we will see what makes it into the formal specification (timing, progress), but there are some discussions.
- homework
- review the draft workplan and Gunnar's slidedeck
- back to the project naming ==> homework for next week- coin other project names
- AOB
- participation to OADF open conference next week in Munich ==> check whether some of your colleagues are attending it
Monday 27 May weekly call
Participants:
- Petar (Visteon)
- Gerald (Bosch)
- Christian (BMW)
- Benjamin (BMW)
- Gunnar
- Philippe
...
- roundtable
- discussion on the project name, consensus on "connected services"
- Slidedeck
- Gerald went again through the slide deck he presented at the AMM
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
- slide 7
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
- Gunnar will prepare a slidedeck delivering his vision of what we should work on (in reference to the 5-level ladder shown in the panel on future vehicle electrical architectures at the AMM, look at slide #3 of future EE architectures)
Monday 20 May weekly call
Participants:
- Petar (Visteon) new participant
- Gerald (Bosch)
- Guru (Bosch)
- Gunnar
- Philippe
...