Page History

...

• graphql schema example
• PoC design & implementation
• Webinar & virtual summit workshop content: gathering of topics
• projectization in jira
• AOB

Participants

• Kevin V, Ted, Ulf, Keith, Gunnar, Philippe

Minutes

Webinar & virtual summit workshop content: gathering of topics

...

graphql schema example

• Gunnar: Alex (BMW) is still waiting for a colleague to review his example before publishing it

• Kevin: shows the tool chain Gunnar and he proposed to go from VSS2 to graphql schema, look at the model transformation workflow attached to

  Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-96

  • grey boxes corresponds to the open source implementation of the neutral server components that High-Mobility will provide

• Kevin: explains the workflow and also a possible alternate workflow from VSS2 to 3rd party client (i.e. w/o going through the neutral server)

• Kevin: for the demonstrator we will focus on the EV charging datapoints in order to show attractive use cases

• discussion on the data packages and distance w.r.t. the data structures used by CVIM and Sensoris

  • CCS data packages (look at the high-level architecture diagram here) should be generic enough so that they can be mapped to any specific project data structures

• Ulf: this format does not fit very well with Gen2, IMHO this is not seen in the vehicle but rather in in the cloud

• Gunnar: this format might be used in the car but not for the transmission to the cloud, the format is not fixed yet, this format can be used inside the vehicle for storage purpose for instance, this still needs to be refined further

• Gunnar: the state storage does not need to use a SQL format in my opinion

• Kevin: I will document which format to put for which version of the proof-of-concept in the wiki

• /TODO/ Kevin V to document which format to put for which version of the proof-of-concept in the wiki

...

• Gunnar: shows the code repo structure in github, CCS-arch-demo repository
  • repo names correspond to the actual implementation used
  • please look at the various readme files

• Philippe: jira will be structured according to a list of generic components corresponding ro to the HL diagram>>>>>>>>>>>>>>>>>>>>>>>>>>> INSERTION
  shows the oeamdatabase implementaiton
  look at readme on github for the container dezcription

• Gunnar: explains how docker is used, e.g. CCS-arch-demo/tree/master/docker/sqlite repository

  • shows the OEM-database implementation using SQLite

  • shows the test files

  tests/test_files

  • will continue to

  pachage

  • package the components according

  to this approacj as

  • to  they become available

• Gunnar: the next step is to get the create table commend command for the datalake from Ulf (datalake

• Ulf: I started implementing the datalake using SQLite

• Ulf: I talked to Sanjeev and I will implement the a framework arounf around the datalage datalake and expose an API that the client will use to interfcace interface with Gen2Guna

• Gunnar: what will be the type of interface api API between the vehicle client and the datalake

• Ulf i : I am actually working on a server actually that thelcient both the client component and the reosurce management canusz fro mteh data lake
  resource management component can use for accessing the datalake, it it written in REST

• G. Gunnar: I am wonderinf whar wondering what we will get form from having the REST Api APIs between those componeents, I am wonderinf whete wondering whether there could be sometging something simplerULf

• Ulf: imgo IMHO this is simple enoughG.

• Gunnar: both Sanjeev and you are working in Go, aren't you ?

• discussion on how to mkae make interfacing simpler

• Ulf: we might reconsider tihs this later

• G. Gunnar: it seems to me as some extra frameworkwork, but we will see soon*

Webinar & virtual summit workshop content: gathering of topics

• Kevin: I will present how we came to the high-level diagram for the poc, @Gunnar : will you introduce VSS Gen 2 ?
• Gunnar: agreed
• Gunnar will be useful to give the full roadmap
• Philippe: proof-of-concept roadmap is as follows

  • milestone 1 - Spring virtual technical summit (12-14 May)

  • milestone 2 - internal milestone (early Q3 - July ?)

  • milestone 3 - Fall All Member Meeting, Leipzig, Germany (last week of October)

  • milestone 4 - CES 2021,  Las Vegas, USA  (early January 2021)

• Kevin: will show also an overview of the gap analysis
• Kevin: draft slide deck for the Webinar will be shared with Gunnar and Philippe to-morrow DONE

projectization in Jira

• Philippe:  Jira database will be structured with generic components corresponding to big boxes of the high level communication framework diagram

Monday,  April 20 - Vehicle Data

...