Monday 17 June weekly call
Participants:
- Petar (Visteon)
- Kevin (High Mobility)
- Benjamin (BMW)
- Gerald (Bosch)
- Ilios (Obigo) new participant
- Gunnar
- Philippe
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
- 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 Progress 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
- 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)
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
- AUTOMAT Security document looks useful to read in addition to CVIM spec.
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 -- 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
Minutes
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
Minutes
- 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
Minutes
- roundtable
- Petar: works with Visteon Connected Car team, he is a colleague of Giovanni (GPRO project), he is also based in Sofia, Bulgaria
- Petar is the solution architect of the team responsible for the overall architecture of the Visteon platform for connected services
- Petar has 12 year experience in connected services, for the entire stack from infrastructure to Web content end-to-end and for standard compliance
- Petar is currently more on R&D and prototyping than production
- Slidedeck
- Gerald went through the slide deck he presented at the AMM
- Gerald: session went out very well, better than expected, a lot of experience people attended, Melco (Mitsubishi Electric) which is quite involved in W3C was there and showed a lot of interest
- next steps following AMM workshop
- organization of weekly calls (instead of every other week): agreed
- /TODO/ Philippe send out an invite for the calls (starting next Monday) to the genivi-projects mailing list and the list of interested participants gathered at the AMM
- /TODO/ Philippe initiate a wiki page for the project
- feedback from today's call participants
- Petar: workplan is quite interesting, told us he identified interesting work on IoT protocol standardization, the Homie protocol specification that he came across a couple of months ago. Although it is suggested to be home IoT-oriented, it is generic enough to provide structured data interface for IoT communication, which falls in the scope of Car to Cloud.
- link: https://homieiot.github.io/
- Petar: has a question on the authorization work, is it also on the cloud side ?
- Gerald: yes, you are right, something is needed on the cloud side
- Gerald: Daniel Wilms (BMW) expressed his concern about piling up abstraction layers
- Philippe: this has been a recurrent concern from BMW for a couple of years
- Gunnar: thinks this is a no brainer