Cloud & Connected Services Project Minutes

• Mapping of CCS framework on popular cloud platforms

• CCS Proof-Of-Concept - Work Breakdown Structure

Earlier threads (back to backlog)

• Data serialization / value formats

• Access Control

All tickets query:

• Alignment discussion:

  • ODATA is an older model (developed by Microsoft, published OASIS standard) for business related data.
    Are there any reuse/adopt opportunities or does it not apply?   See also web site.

• We suggested to rework the overview picture into one part showing how components are stored in repository, and another for deployment

• LiveSim is not connected at both ends.  The diagram suggests there is a deployment where data is fed from livesim but also fed back into livesim, which doesn't make sense.  You either collect real data (from some kind of VSS Feeder writing into in-vehicle state storage) or you feed the system from the livesim.  It is true that Livesim consumes a OVDS database format, but it does not 

• Can we start using some kind of online editing tool or common format in the future? (anything that allows other people to change)

  • YEd?

  • Fallback is always PPTX file (works in MS Office and LibreOffice)

• Geotab data format to VSS conversion is possible.  About 50 signal translations have been defined.

  • Data sets can then be provided (in OVDS format) 

  • Position information likely coming (pending consent).

  • examples: position, speed, ignition, oil temp, turning indicators, seat belt

  • 5-10 vehicles, that type of range.

  • How can/shall we use this data?

• Stephen reminds about VSS-formated dataset that Access has defined before (available with a demo in GitHub).

• CCS demos have before focused on Vehicle→OEM cloud parts.  Development in the usage of data, cloud based applications, and deployment/automation as previously discussed.

• Curve logging implementation in VISS is new compared to last AMM.  It can be demonstrated.

• Android app - reads from VHAL sends signal to cloud.  Opportunity to use VSS and/or VISS?

Participants

• Florian Pinzel

• Nikhil Shirka

• Vishwajit Joshi

• Stephen Lawrence

• Gunnar Andersson

Minutes

• No updates on Tech Brief from Iyyaz this week.

• Two new participants from KPIT.  Introductions and quick project overview of CCS and CVII.

• Ongoing vacation season (in Europe).  There will be a break and some meetings will be cancelled in the next few weeks.  (Information coming via email)

US friendly time 16:00 CET

Participants

• Stephen, Florian, Gunnar, Philippe

• apologies: Kevin, Iyyaz, Ulf, Ted

Minutes

vacation plan

• discussion on vacation plan of the participants

ISO ExVe

• following the discussion on ISO ExVe in the CVII workshop, Philippe reports the Renault representative in this WG contacted him and confirmed he will organize a presentation of CVII to the vehicle data subgroup of the French PFA (French equivalent of German VDA) in September

• Gunnar and Philippe provide a short debrief to Florian on the outcome of the call with ISO WG6 participants on 23 June (ISO WG6 convenor, Stellantis representative, Audi representative, Gunnar, Ted, Philippe). Call went out well. A presentation of CVII to ISO WG6 is likely to be scheduled at the next meeting of ISO WG6 in late August / early September

• summary of discussion with ISO people is below

  • convenor: in ISO we are starting to work towards enabling third parties to get data and functions embedded in the car within the ExVe architecture, we realized it is difficult to get a similar set of signals from the different OEMs, this is why we decided to move only to an harmonization of the data description among the vehicle OEMs

  • Gunnar exposes the GENIVI/W3C vision

  • Stellantis : we do not want to harmonize the vehicle EE architecture among the OEMs, we do not want to have the same characteristics for the data we get

    • there is no direct access between the neutral server and the vehicle

    • the neutral server knocks at the door of each OEM cloud interface

  • Audi: there is no definition of accessible data, we do not define which data are provided, we are looking for a generic way to describe data

  • Gunnar: ISTM the ExVe interest is with the meta-model

  • convenor: we are discussing more about API catalog than data catalog; it will be something like a function catalog

  • Audi: in our specifications, we are describing the way and how the functions can be accessed (with security) and not the resources themselves

  • convenor: asks where we consider putting the layers implementing the CVII translation / conversion

  • Stellantis: you should talk to Bosch BSH, they have a similar block diagram for the home automation

  • convenor: shows one slide of the presentation he made to UNECE in Geneva a couple of months ago, the slide shows the different ways to access the vehicle data

US friendly time 16:00 CET

Participants

• Stephen, Ted, Gunnar, Philippe

• apologies: Kevin, Iyyaz, Ulf

Minutes

tech brief

• Iyyaz said via email that he will send the draft document on Wed/Thu this week

OPIN

• in the minutes of last Friday"s OPIN meeting, Steve and Philippe got an action item to provide a OEM oriented use case (Steve suggested a driver distraction use case) and a (truck) fleet management use case. Philippe suggested in the same call the use case related to the refrigeration of the cargo bay (monitoring of the cargo temperature)

• Gunnar: concerning trucks and their cargo, we have a signal in VSS indicated whether the trailer is hatched / not hatched

• Gunnar: concerning the OEM use case, we have in VSS signals that could be relevant for detecting the driver's behavior

• Gunnar: IMHO the technical architecture is in place and we should not be contemplating architectural changes due these additional use cases

• Philippe: asks whether Ted could find some help within Geotab to provide a truck fleet management scenario to share with OPIN

• Philippe: proposes to reach out to Kevin and ask whether High Mobility could provide a OEM use case (e.g. driver distraction)

• discussion follows on the coordination between Catena-x and VSS and OPIN and the structuring of vss signals

US friendly time 16:00 CET

Participants

• Ulf, Iyyaz, Stepahen, Ted, Gunnar, Philippe

• apologies: Kevin,

Minutes

tech brief on CCS mapping to cloud providers

• Iyyaz presents his workplan for drafting the first version of the tech brief which is expected to be available at the end of the month

• look at Tech Brief planning on CCS mapping to cloud providers

US friendly time 16:00 CET

Participants

• Ulf, Iyyaz, Stephen, Ted, Gunnar, Philippe

• apologies: Kevin

Minutes

tech brief on CCS mapping to cloud providers

• Brainstorm (document structure, headings, content, principles, goals...) for the tech brief

• look at Tech Brief planning on CCS mapping to cloud providers

• TODO all to consider taking ownership of the tech brief for the writing of the document,  remember that our practice is to have the contributors' name and company advertized in the tech brief

US friendly time 16:00 CET

Participants

• Ulf, kevin, Florian, Iyyaz, Stephen, Gunnar, Philippe

Minutes

quick roundtable to welcome Florian

discussion on the CCS work breakdown structure

• Gunnar : current CCS project focus is on the implementation of the CCS end-to-end architecture

• Gunnar explains the status of the implementation (using the diagram in CCS Reference Architecture - Work Breakdown Structure

• Florian welcomes favorably the CCS approach to promote the use of open source and off-the-shelf components for the implementation

• Gunnar focuses today's discussion on the identity and access management

• Iyyaz: Hydra/Okta challenging to set up. Okta seeems popular.  Hydra is the implementation.  See https://oauth.net/code/

• .....AWS, MS/Azure, etc. have their own offered services.

• ...Need ideas / definition of task to progress this within CCS PoC implementation.

• Gunnar: Self-hosted solutions?

• Iyyaz: They are all hosted services.  Some configurability regarding which servers to use.

• Signing up as a developer to Okta gives access to a limited account with a certain number of users  (quite many,~7000)

• Identity and access management is a moving target, important to track security updates, etc. which speaks to partnering with expert companies.

US friendly time 16:00 CET

Participants

• Ulf, Kevin, Gunnar, Philippe

Minutes

graphql generator

• Gunnar shows a demo of a graphql tool he developed during the last couple of weeks, it is written in python and derived from the tool available for generating protobuf

  • github: vss-tools/pull/64 repository

June CVII workshop

• Kevin will be OOO 23-24-25 June because of Summer celebration in Estonia

• Ulf will OOO this week of June

• decision  to move the workshop one week later on Thu 1 July, start time: 16:00 CET, duration 3 hours max.

ISO ExVe WG6 update

• Philippe delivers an update on the discussion Gunnar and he had two weeks ago

• discussion on the translation of OEM specific data format into a data market player specific  language like the one of High Mobility which is the current state of the art for the companies offering vehicle data access

no calls due to bank holiday in several countries (Denmark; Germany, France, etc.)

Asia friendy time 11:30 CET

Participants

• Sanjeev, Gunnar

• apologies: Philippe

Minutes

discussion on deployment of CCS communication framework components on Windows

• Error rendering macro 'jira' : null
  created

• Error rendering macro 'jira' : null
  created

US friendly time 16:00 CET

Participants

• Ulf, Iyyaz, Stephen, Gunnar, Philippe

• apologies: Kevin

Minutes

review of work breakdown structure

• CCS Proof-Of-Concept - Work Breakdown Structure updated on line

• entries modified

  • #2 - In-vehicle VSS2 translation:  Implement CAN + VSS translation support (e.g. reuse from Bosch code project) added as an additional activity and possible option for implementing the sw components

  • #3 - In-vehicle data package: VISS server role explained in the context of production-grade implementation

  • #5 - OEM Cloud vehicle client: vehicle client configuration options added

  • #6 - OEM Cloud VSS2 database: using path as ID

  • #8 - OEM Cloud access management: Iyyaz points to the following code

    • https://www.ory.sh/hydra/ taken from https://oauth.net/code/

  • #10 - Neutral server data marletplace: note added on neutral server API

• addition of AWS tools in the Cloud Infrastructure Tools section

• new sprint created (Sprint 17)

• Scope CCS project work (in relation to other CVII projects)

• Kevin: Worth building the implementation fully.  Cannot contribute (more) code at this time.

• Gunnar: Let's scope CCS for the "cloud" part of the architecture.  Strictly in-vehicle discussion perhaps a different CVII sub-project.

• Gunnar: Current CCS project scope is quite wide, and describes something similar to the first steps of CVII.  Let's try to narrow/clarify scope now.

• Philippe: Might need revising the ticket backlog to match.

• 5 May - technical update: recorded session (please go to CCS section), slides

• 6 May - technical workshop #1: Recorded Session, slides: Introduction to PaaS, IBM Cloud and more, Mapping CCS to AWS services

• 7 May - technical workshop #2: recorded session

US friendly time 16:00 CET

Agenda

Participants

• Ulf, Iyyaz, Kevin, Ted, Gunnar, Philippe

• apologies: Stephen

Minutes

CCS short update - slide review

• clarification on who does what for the upload of slide decks and the recordings, Kevin sorted out things with Karin during the call

• Ulf - Communication Framework - End-to-end Demonstration, moved to Friday

Workplan for the next 6 months (preparation of Friday 7 May CCS workshop)

• Kevin: what could be important for an OEM ?

• Ulf: important to show an end2end connection from the vehicle to the cloud, obd in the vehicle, we would need a better dataset from the obd, Geotab could be asked to provide a more comprehensive dataset, but to be really demonstrative, we would need someone working on the cloud side

• Gunnar: @Ted: what about the grapher project ?

• Ted: https://www.w3.org/auto/wg/wiki/Vss_data expose real-time data on to grapher (MIT, SRI, U.Memphis, Geotab are involved in a R&D project and asked for a grant)

• Mapping on MS Azure

PaaS

• review of slides prepared by Iyyaz for the AMM

US friendly time 16:00 CET

Agenda

• AMM preparation

• GAIA-X

• tech briefs

• AOB

Participants

• Ulf, Iyyaz, Kevin, Christian, Benjamin, Gunnar, Philippe

• apologies: Stephen

Minutes

AMM preparation

• Ulf: Geotab will deliver a talk on the mapping to Google Cloud, the name of the presenter will be given before the end of the week

• Kevin: cannot make it for the CCS session on Thursday 6 May

• decision  Kevin will pre-record his talk and prepare the Q&A with Gunnar (and others possibly) offline, no change in the AMM schedule

• Philippe: we need to prepare Friday 7 May session on the next step

• TODO all to think about the topics for the next 6 months, the review of these topics will be the main topic of the agenda of next week's call

• Error rendering macro 'jira' : null
  created, please add your topics there

GAIA-X

• Benjamin: this was a very high level presentation, a bit disappointing, the only use case I found relevant for automotive relates to the supplier chain

• Gunnar: we need to be proactive and reach out to them and tell the story that CVII will produce one of the items they need

• Philippe: the French "hub" of GAIA-X will gather on 7 May morning (CET); will joint it

• Philippe: we need also to continue reaching out to ISO ExVE

• TODO Benjamin to identify the VW representative at ISO ExVE

Tech briefs

• short discussion for finalizing the curve logic tech brief

• Philippe: suggests to plan the preparation of a tech brief on the mapping of CCS communication framework to the popular cloud infrastructures

• Error rendering macro 'jira' : null
  created

AOB

• Kevin: High-Mobility passed the German TISAX certification last week, look at for instance https://www.tuvsud.com/en/services/auditing-and-system-certification/tisax

US friendly time 16:00 CET

Agenda

• demo for AMM
  
  

• AMM talks
  
  

Participants

• Ulf, Iyyaz, Ted, Kevin, Stephen, Benjamin, Gunnar, Philippe

Minutes

demo for AMM

• Ulf: http-based demo done

• Ulf: MQTT-over-viss client is now implemented (separate executable), It is in the https://GENIVI/ccs-client repository

• Ulf: Old implementation verified that requests are found in the tree.

  • ...Now the paths are different.

  • ...I need for the demo some new populated OVDS, at least one database.

  • ...It is a bit tricky to keep the correct VSS version.

• Gunnar: Could we make this less tricky ?  It is often good to be able to catch errors on different levels of the stack.

• Ulf:  Another argument: OVDS server should be able to store data from different models etc.

  • ... anyway OVDS server has now removed this check so it accepts ANY path for the moment.

• Ulf:   I need a new populated OVDS from Geotab, working on it.

• Ulf:  The demonstration - I could run the demo natively but running on docker should be much better, who can fill up the docker structure with the new components

  • If container setup in CCS-arch-demo is not updated I will do the demo manually. But in that case I will do pre-recording of the demo.

  • Gunnar: Sometimes it's good to have a recording anyway, as a backup.

• Initial plan: 3 laptops in network.

AMM content

• deployment on google cloud talk still to be confirmed by Geotab

• TODO @Ulf Bjorkengren please check with Glenn the outcome of the internal meeting about this talk

• Iyyaz: Mostly working on terraform now.  Potential demo.  Slides were previewed on last CVII Tech Stack meeting.

  • ... discussion on technical level of presentation/discussion at workshops at AMM. 

  • Conclusion:  It's good to assume people are not experts in, say, terraform, but that they will pick it up quickly if there is a quick intro before moving into the details.

• Gunnar: we have the possibility to reuse the timeslot for google cloud and assign it to Iyyaz's talk and demo

Jira review

• Error rendering macro 'jira' : null
  Iyyaz looking for time of a colleague to work on deployment on Azure

• Error rendering macro 'jira' : null
  and subtask
  Error rendering macro 'jira' : null
  assigned to @Former user (Deleted)

• and subtask
  assigned to @Former user (Deleted)

• assigned to @Former user (Deleted)

• sprint extended until 30 April

tech brief (added offline)

• Philippe: I would suggest to start writing a tech brief on the deployment of CCS communication framework on cloud infrastructures, to be discussed further next week

US friendly time 16:00 CET

Agenda

• vehicle insurance use cases
  
  

• end2end demo for the upcoming AMM

• Jira review
  
  

Participants

• Glenn, Ulf, Iyyaz, Ted, Kevin, Stephen, Mike, Gunnar, Philippe

Minutes

vehicle insurance use cases

• Kevin: presents the data set used at HM in the context of the partnership with motion-s (see press release below)

  • https://motion-s.com/high-mobility-motion-s-partnership/https://motion-s.com/high-mobility-motion-s-partnership/

• Philippe: in the upcoming AMM agenda, we will have a talk/panel on vehicle data based insurance use cases, both OPIN and MS will participate, is HM willing to join the panelists ?

• Kevin: yes, we will join and present the use cases we have implemented

end2end demo at AMM

• Ulf explains the demo architecture, look at the picture https://at.projects.genivi.org/jira/secure/attachment/11702/mqtt_vissv2_arch.jpg

  • picture attached to

• Philippe: it would be good to have a complementary demo on the cloud side on the top of the (CCS) communiucation framework architecture and that we go one step further from what we demoed before

• Gunnar: I was thinking of possible extensions towards many (hundreds) of clients to look into the scaling

• discussion follows on bringing together Ulf's and Iyyaz's demos either on the paper or at implementation level

• Iyyaz: my intent is to show the use of terraform and how the deploymentcan be done on various cloud infrastructures, another possible approach for the deployment is to use containers

• TODO Iyyaz to provide a short slide deck (i.e. early overview) on how the deployment could be done

  • created

• then we will discuss on what we might end up with for the implementation in the AMM demo

• discussion on terms and definition of "edge"

  • Iyyaz: in the context of our discussion in CCS, my understanding is that vehicle = edge and we are talking of "edge-to-cloud"

  • Iyyaz: edge = everything that have a small compute capability, the edge needs to tell the cloud about the (vehicle) presence

  • TODO Iyyaz to provide our definition of "edge" as compared to what Bosch uses as a definition on "edge" in their recent code drop

    • created

Jira review

• • Gunnar:  I am almost done with the curve logic tech brief finalization

• • Gunnar: I am feeling an increased need to break this down to more details, we need a revised version of the CCS communication framework architecture picture taking into the Bosch code drop, etc. figuring out what are the different components we have

  • Kevin: I would recommend to use another tool to produce the end2end archi drawing

  • Gunnar: shows the Bosch vehicle edge and iot-event-analytics project

    • code https://github.com/GENIVI/vehicle-edge

    • wiki IoT-event-analytics and Vehicle-Edge projects

  • TODO Gunnar and Kevin to agree on how to share the existing architecture picture and update it

US friendly time 16:00 CET

Agenda

• virtual AMM preparation
  
  

• Jira ticket review
  
  

Participants

• Jim, Glenn, Ulf, Ted, Naresh, Kevin, Stephen, Gunnar, Philippe

• apologies: Kevin, Iyyaz

Minutes

quick roundtable

• Jim: Ford Motor Company, we are looking for opportunities to standardize our vehicle data as well as our connectivity solutions

Virtual AMM preparation

• Gunnar shares the (internal) wiki content planning

• Philippe: I would recommend CCS present the mapping of CCS communication framework on to cloud and related demos if any

• Example demos should be using AWS cloud and/or Google Cloud, IBM cloud, MS Azure so that people are aware we are not targeting a specific cloud infrastructure