Page History

Current threads

Earlier threads (back to backlog)

Info

Regular meeting times. For meeting links, please refer to the list on CVII Home Page or invitations that are sent out on the mailing lists.

Cloud and Connected Services (CCS): Mondays 1600 CE(S)T

Common Vehicle Interface Initiative (CVII) Technology Stack meeting: Wednesdays 1700 CE(S)T. Also vss-tools (discussed in VSS/VSSo meeting) could be relevant.

All tickets query:

Expand

Jira

server	JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project = CCS AND resolution = Unresolved ORDER BY priority DESC, updated DESC
serverId	121ddff2-c571-320f-9e4d-d5b9371533bd

Monday 2021-11-22

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.

Monday 2021-10-25

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)

Monday 2021-08-23

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?

Monday 2021-07-12

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)

Monday 2021-07-05

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

Monday 2021-06-28

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

Monday 2021-06-21

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

...

Monday 2021-06-14

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

Monday 2021-06-07

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.

Monday 2021-05-31

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

Monday 2021-05-24

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

Monday 2021-05-17

Asia friendy time 11:30 CET

Participants

Sanjeev, Gunnar
apologies: Philippe

Minutes

discussion on deployment of CCS communication framework components on Windows

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-203
created
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-204
created

US friendly time 16:00 CET

Participants

Ulf, Iyyaz, Stephen, Gunnar, Philippe
apologies: Kevin

Minutes

review of work breakdown structure

C CS 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)

May 10

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.

May 4-7 Virtual AMM - CCS sessions

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

Monday 2021-04-26

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

Monday 2021-04-19

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
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-202
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
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-201
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

Monday 2021-04-12

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

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-191
Iyyaz looking for time of a colleague to work on deployment on Azure
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-146
and subtask
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-149
assigned to Unknown User (naresh.nayak)
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-110
and subtask
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-111
assigned to Unknown User (naresh.nayak)
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-191
assigned to Unknown User (iyyaz.baber)
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

Monday 2021-03-29

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
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-196
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
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-199
  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
  - Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-200
    created

Jira review

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
- Gunnar: I am almost done with the curve logic tech brief finalization
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-7
- 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

Monday 2021-03-15

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

(CVII) CCS project update	75 min ?	Project update (15')
		+ Mapping to AWS Cloud (TBD) (20')	Kevin Valdek	Kevin agrees to deliver a presentation on the mapping to AWS
		+ Mapping to Google Cloud (Geotab) (20')	discussed today	Glenn: it is too early stage for the Geotab team, the team needs to build a biz case. Glenn/Ulf started a discussion with data analytics team in Geotab
		+ Mapping to IBM Cloud (Cobrasphere) (20')	to be determined on Monday 15	Iyyaz sent apologies for today's call, to be checked offline
		End-to-end demonstration similar to last virtual summit.	discussed today	Generic demonstration (not cloud specific?) Ulf can help on the OBD connection

quick intro to CVII work organization

Gunnar shows the Project organization in order to explain how the project is organized to Jim
Philippe: highlights the following boxes
- the bottom right box relates to CCS communication framework activities which currently focus on the mapping to the cloud
- the left box related to the data models and alignment of models among the industry, e.g. Sensoris (vehicle data and vehice environment data), Iso ExVe, etc.
Philippe: as part of the activities on data models, suggests to look at the Catena-X project in addition to the GAIA-X project
- useful link: https://internationaldataspaces.org/catena-x-with-gaia-x-will-data-space-be-the-word-of-2021/
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-198
  created for tracking and assigned to Benjamin

Jira ticket review

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-111
- Naresh: still waiting for inputs from colleagues on the VSS translator implemented in kuksa and the data simulator options, will report on this next week
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
- Gunnar: Draft of Tech Brief has been shared and I made some comments. Looking good - a bit of cosmetic cleanup and it should be OK. Can we share the draft with the CCS group for further review/comments?
- Glenn: yes

Monday 2021-03-08

US friendly time 16:00 CET

Agenda

sprint review and update

Participants

Ulf, Naresh, Stephen L, Gunnar, Philippe
apologies: Kevin, Iyyaz

Minutes

quick roundtable

Naresh works at Bosch, is a colleague of Sebastian S, he works on VSS and Kuksa, his knowledge is on the in-vehicle networking side of things

sprint review (new sprint)

Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
Ulf will remind Glenn about it
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-59
Gunnar: meeting with Cloudera will likely happen this week
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-196
Ulf: would like to know more about the timeslot duration for a demo, needs to secure resources for implementing the demo
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-123
Gunnar: IMHO using a time-series database would be more interesting, some explanation given to Naresh about this workitem
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-181
- Gunnar: for this one we need some one experienced with apache grapql and java script
- Gunnar: BMW has clearly some expertise there
- Philippe: this could be a topic for GSoC
- Gunnar: checks the GSoC timeline, too late for this year
- Gunnar: we need to find an implementer or to identify an existing implementation for the graphql server we could reuse
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-129
Gunnar: we proposed a graphql api as well, we are stuck for the same reason of having a graphql implementation available
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-149
- in the VHAL project, Stefan Wysocki implemented a signal feeder with the OpenDS simulator
- Gunnar: but there is outdated java code in the simulator code, runs on windows, not on linux
- Naresh: we have (in kuksa.VAL) a can feeder written in python that sends signals to can sockets
- Gunnar: shows OpenDS 5.0, there is a demo that can be done potentially using a windows machine and generate signals with OpenDS 5.0
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-111
- Naresh: in the work we did in kuksa project, the VSS data model is given to kuksa.VAL server
- Gunnar: underlines the comment of 7 December in the ticket
- Naresh: an implementation of VSS translation was done by kuksa
- TODO Naresh to check with colleagues and determine wheher they can contribute on the in-vehicle VSS translation

Monday 2021-03-01

US friendly time 16:00 CET

Agenda

alignment of Sensoris and VSS data model
review of tickets related to the deployment of CCS communication framework on cloud infrastructure
sprint review and update

Participants

Kevin, Ulf, Iyyaz, Irfan, Christian H, Ted, Stephen L, Gunnar, Philippe
apologies: Benjamin

Minutes

quick roundtable

Irfan is a new participant working for llts, Irfan is based in Bangalore, India, https://www.ltts.com/

alignment of Sensoris and VSS data model

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-195
Benjamin reported about the review he made prior to the call
- Benjamin reviewed the slide deck shown at the CVII workshop (slide deck is here)
- Some feedback on the slide deck shared:
  The overlap of signal categories is clear, Sensoris has both internal and external signals where VSS only has internal ones. What could complete this is that:
  - VSS only defines signals as things that your car senses/controls, not necessarily abstract information. For instance, the signal WindCondition does not exist in VSS but something equivalent could exist.
  - VSS orders signals by vehicle branch (part, component), while Sensoris has an approach based on use cases
  I believe these are the "notable differences" mentioned in slide 5.
  The proposals for collaboration are pretty clear and extensive. I would also include the possibility of organizing a workshop with developers of both community trying a set of use cases with a combination of both specs to find out where practical overlap/conflicts would happen. Another possibility is to have a spec importing the other (e.g. Sensoris using the VSS signal list like a catalog, translated into protobuf and Sensoris messages).
- TODO Gunnar to forward Benjamin's inputs to Stefan Werder who at Bosch is working on the alignment of Sensoris and VSS data models, ticket rassigned to Gunnar

review of tickets related to the deployment of CCS communication framework on cloud infrastructure

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-101
- Kevin: presents the analysis made by High Mobility on using terraform (please look at the comprehensive comment added to the ticket)
- Gunnar/Philippe: this sounds like a plan
- Gunnar: what would happen if we change the database (like to a pure sql database) ? some parts of the demo use REST interface, however some part of OBDII interface should be changed, Ulf agrees
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-189
- Iyyaz: at Cobrasphere, we tried to build CCS and we have not succeeded yet
- Iyyaz: it seems that ubuntu 10.x does not support some features
- Gunnar: that kind of things happen when you are not using ubuntu long term support
- Iyyaz: would it be ok to use Alpine Linux ?
- Gunnar: yes it is possible
- Ulf: I know that Magnus Gunnarsson at Melco (who works in W3C) uses the Alpine distro
- Iyyaz: we will try to rebuild then
- Gunnar: modifications should be made as pull requests
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-192
- Glenn: the challenge is to show the interopErability of the Geotab analytics tools with CCS
- Ulf: explains the update made in the vehicle client component, we have a solution for transporting VISS onto MQTT
- Ulf: we use moskito server for this purpose
- Stephen L: please note big picture is out of date in the wiki

sprint review and update

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-108
cancelled, won't fix, no need to go for a production-grade component
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-111
commented
- Gunnar: The principles for automatic/table-based translation can be seen in AASIG-122. The spreadsheet shows mapping between Android properties and VSS signals - and in one column you can see the intention is to define the type of conversion that is needed for each conversion (full equality, type conversions, or scaling through a linear transformation formula, or a more complex situation). Many input sources, such as CAN, would work similarly.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
commented
- Repository is now up. Draft tech brief is being developed currently. Official name will be: Curve Logging. Will soon be sent to Gunnar for review.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-59
commented
- Michael came back to ask to sync up FusionProject with the CCS and CVII work. Meeting pending probably to be booked this week.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-102
commented
- Discussion today about new potential parts:
  - AWS/cloud provider implementation ideas -> see CCS-101
  - New features in VISS communication could be part of next demo (subscription now also exists in client, VISS-over-MQTT). Also access control which was not demoed before.
  - Multi-client demo (using different transports)
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-83
commented
- Gunnar: Some more description of VSS-layers in GitHub pull request, but further discussions ongoing. The usage of VSS layers to define access control is still there (not further improved however).
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-123
commented
- One related idea proposed in CCS-101 was to use AWS RDS service,
- but also continue looking into a time-series database

Monday 2021-02-22

US friendly time 16:00 CET

Agenda

debriefing of CVII workshop and next event
CCS workplan
- CCS communication framework on cloud infrastructure

Participants

Kevin, Ulf, Iyyaz, Christian H, Ted, Benjamin, Stephen L, Gunnar, Philippe

Minutes

debriefing of CVII workshop and next event

workshop was a little bit too demanding (not enough breaks) but content was very good
Christian liked eSync presentation and Iyyaz's talk on the deployment of CCS communication framework on cloud services infrastructure
Iyyaz: woud have appreciated more time to explain the work and show demo
Philippe: next major dissemination event will be the All Member Meeting scheduled on May 4-7, 2021
Philippe: event will include a business track and technical tracks, there will be more time for discussion and demos
Christian H: forwards the link to the press release made by Bosch and Microsoft on Thu 18 February - https://www.bosch-presse.de/pressportal/de/en/bosch-teams-up-with-microsoft-to-develop-software-defined-vehicle-platform-for-seamless-integration-between-cars-and-cloud-224832.html
Philippe: we have been talking to Microsoft for quite some time and we have scheduled a call with them later this week to talk about the Digital Twin Consortium
Christian H: underlines that in his opinion the two companies also plan to use GitHub’s fully integrated enterprise platform and to open-source important parts of the new software platform on GitHub.com to encourage code re-use and best practice sharing across the industry.
Christian H: why don't we use github that belongs to MS as our CI & testing environment e.g. by using https://github.com/features/actions

CCS workplan

Philippe: shows the Jira tickets related to the deployment of CCS onto the cloud services infrastructures,
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-139
and its subtasks
Christian H: will speak to the Bosch team during our internal steering committee meeting on Thursday and underline the deployment of CCS on a cloud service infrastructure
Ulf: I will do the same for google and google cloud environment
Iyyaz: are you talking about the devops cycle ? Christian: yes
- discussion between Iyyaz/Christian on the development cycle and the release branching process
Kevin: supports the idea of using AWS, we should split the branches among AWS, IBM, Google, MS Azure if we do the deployment ourselves
HM is looking at Teraform (https://www.terraform.io/) and expects Teraform will facilitate the deploymnent on various cloud infrastructures
Philippe recaps the actions for participants as described in the following set of Jira tickets
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-101
  Kevin: I will check with HM team whether they can provide a feedback on using teraform
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-189
  Iyyaz: will look into it this week
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-191
  this is also assigned to Iyyaz, but it would be interesting that Gunnar and Philippe check how MS can help for the deployment on MS Azure
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-192
  Ulf: will check with Geotab team whether they can provide support for deployment CCS on Google cloud services

Monday 2021-02-15

US friendly time 16:00 CET

Agenda

preparation of CVII workshop
CCS communication framework on cloud infrastructure

Participants

Kevin, Ulf, Iyyaz, Christian H, Ted, Benjamin, Stephen L, Gunnar, Philippe

Minutes

preparation of CVII workshop

review of workshop agenda and allocation of slots to presenters
agenda is here

CCS communication framework on cloud infrastructure

short discussion on this deployment again
Stephen L: provides a link to AWS embedded demos - https://github.com/aws-samples/meta-aws-demos

Monday 2021-02-08

US friendly time 16:00 CET

Agenda

review of new sprint activities

Participants

Ulf, Glenn, Iyyaz, Ted, Benjamin, Stephen L, Gunnar, Philippe
apologies: Kevin

Minutes

review of new sprint activities

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-190
wip, Sanjeev is preempted by a high priority issue, he will be back on this topic from 22 Feb onwards; link added to
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-101
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-188
CCS presentation at Fosdem, there were up to 300-400 participants in the Embedded, Mobile and Automotive devroom
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-101
Stephen added a link to an AWS Team presentation at Open Source Summit Japan Autumn 2020: Scaling Automotive Telematics at the Edge and Cloud - Richard Elberger, Amazon Web Services - YouTube
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-191
Iyyaz: on my todo list, but not started yet
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-194
link https://www.okta.com/ added to the ticket
discussion on access control follows as declared in the following wiki page Data Access Control
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-139
it would be good to have some participants working on proof-of-concept deployment of CCS communication infrastructure on cloud services
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-183
need to remind Sebastian about this
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-174
ticket closed, no contact information on the project web site

Monday 2021-02-01

US friendly time 16:00 CET

Agenda

refocusing of CCS project activities
vehicle data model

Participants

Ulf, Kevin, Iyyaz, Stephen L, Benjamin, Christian H, Gunnar, Philippe

Minutes

rescoping of CCS project

Kevin: CVII call of last week was positive, Q. can we embed our CCS poc in the bigger CVII picture ?
quick look at CCS Reference Architecture - Work Breakdown Structure
Gunnar: there are 2 areas where it is still worth completing the implementation
- the graphql implementaion
- the access management
Iyyaz: concenring access management, are you looking for an implementation on the cloud side ?
@kevin: is it for the neutral server to authenticate or for 3rd parties ?
Kevin: this is for both
Gunnar: it does not replace the authentication on the pipe to the vehicle, VISS protocol does have a definition of access control
Gunnar: shows the vss-graphql repository
Christian H: why don't we collaborate with kuksa project on this, since they have implemented it
- https://github.com/eclipse/kuksa.val
Gunnar: is it aligned with OAuth ?
Christian H: this is to be checked with Sebastian Schidlt
discussion on the various approaches of authentication
Gunnar / Ulf: we use the same authentication mechanism but not the same authentication token on the cloud side and the vehicle side
Iyyaz: what are the actions resulting from this discussion ?
Gunnar: IMHO there is a need to review the kuksa code to check what can be reused
Gunnar: there is a need to cross-check whether kuksa project supports OAuth with Sebastian until next call
Gunnar: IMHO a deep knowledge of the OAuth2 specfication is necessary
Gunnar: we might be willing to explore which implementation exist in the open source
Iyyaz: I have been using the okta implementation of OAuth2, it is actually a service, but provides some code examples of how the service can be used
- https://developer.okta.com/docs/guides/
- okta supports jwt
- okta claims you do not have to bother about the updates of the various software components used
Christian H: the authenticator should be the code we are looking for
Iyyaz: points to https://medium.com/decentralized-identity/the-universal-resolver-infrastructure-395281d2b540
Christian H: points to https://dev.uniresolver.io/
TODO look into the kuksa code
- Christian: on Bosch side the developer is "wenwenchen", we should open a ticket in github to get in touch with the developer
- Christian: I will check with wenwen which material is available for explaining the authentication approach in kuksa
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-193
  created and assigned to Christian H
TODO Iyyaz to explain the rationale for using an external authentication service (like okta)
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-194
  created and assigned to Iyyaz
Philippe: I recommend that we use the mailing list for this because it gives more visibilty than comments in a Jira ticket
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-127
thrown into the current sprint

Vehicle data model

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-141
- Gunnar: presents the results of the review of autopilot project docs he made
- Gunnar: data files containing values measured in test trials, however we do not have a lot to learn for the development of VSS
- Philippe: a short comment, it might be worth checking whether those data files might used as inputs for testing in CCS poc
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-53
- Gunnar: IMHO we should ask Benjamin K to look further into it
- Philippe: IMHO we should go through Bosch to reactivate the liaison with Sensoris, Jira ticket commented
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-195
  created and assigned to Benjamin

Monday 2021-01-25

US friendly time 16:00 CET

Agenda

Geotab introduction to open source toolsuite

Participants

Ulf, Glenn, Rex (Saferide), Kevin, Iyyaz, Stephen L, Benjamin, Christian H, Gunnar, Philippe
Geotab presenters: Bob Bradley, Mike Branch, Nate Qu all based in Toronto, Canada

Minutes

Geotab introduction to open source toolsuite

Mike: list the various tools used by Geotab
Nate: we use java, scala and other programming languages but all on JVM
Kafka broker: we are closely working with the kafka community and we push performance improvements to the community
kubernetes: this is how we achieve the distributed platform, this techno is heavily used on google side, we use many aspects of the kubernetes techno
Bob bradley: his team does a lot of work with Google technos
Gunnar: what does CO mean ? (not captured)
Nate : in open source tools, we do find some issues, however the apache hosted projects are quite stable
Gunnar: have you looked at apache nifi ?
Nate: kafka seems to be more mature, nifi is on our watch list though
Gunnar: do you use other cloud technos ?
Nate: yes, we are trying out snowflake https://www.snowflake.com/
discussion between Mike and Rex on the data processing
Rex: are those technos only cloud based ?
Mike: yes, Rex will follow up with Mike
Gunnar: I can see overlap and complementarity of this work withthe CCS analysis on cloud technologies
Mike: we updated the table already filled in for AWS, IBM Cloud and CCS, updated table is there
Mike: our objective is to leverage what is available from the open source
Gunnar: homework for CCS participants until next week - TODO look over what we have learned, how to use those technos with VSS
Thanks @Geotab team for the open and very interesting experience sharing

Wednesday 2021-01-20

US friendly time 17:00 CET

Agenda

CCS introduction for a future participant in CVII technology stack project

Participants

Piotr (TietoEVRY), Ulf, Stephen L, Gunnar, Philippe, Ted
apologies: Kevin, Iyyaz

Minutes

CVII introduction

quick roundtable to welcome Piotr on-board, Pior was involved in AASIG VHAL project up to now
Gunnar: provides an intro to similarities and differences between VHAL and CCS
Ted: provides an intro to W3C projects
discussion on existing holes in the CCS framework architecture
discussion on which code (from CVII technology stack) could be reused for CCS implementation
quick look at ccs-w3c-client
recommended watching: https://www.youtube.com/watch?v=svqNfyGUHM8&t=2346

Monday 2021-01-18

US friendly time 16:00 CET

Agenda

sprint review
CVII ramp-up

Participants

Ulf, , Kevin, Iyyaz, Stephen L, Benjamin, Christian H, Gunnar, Philippe

Minutes

review of jira tickets

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-141
- Gunnar delivers a quick overview of autopilot project whose objective is to connect IoT to AD (Autonomous Driving)
- website of the autopilot project is back at work
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-174
assigned to Gunnar
- Ulf and Gunnar agree that SVI content seems a bit thin so far - published intentions, a few ideas, and several references to existing specifications.
- Next actions:
  - 1) Suggestion: Find a contact person and email them.
  - 2) Extract the ISO specifications that are security-related and ask the security team.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-139
status of current analysis on cloud platforms
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-101
  - Gunnar: This is a great first analysis. I would now draw a conclusion: Based on what we now know, and the experience of some participants it seems worthwhile to concretely try out some AWS features and/or do deeper evaluation. CCS-190 is new Story capturing this. We might want to use that Story ticket now to break down the work with further sub-tasks?
  - Sanjeev has exeprience with AWS and wants to dig into it and explore how AWS might fit in
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-192
  created
  - Ulf: Geotab will deliver an introduction of Google analytics tool suite on 25 January
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-191
  created
  - Gunnar: People who are familiar can make a similar analysis for Azure as we have done for other cloud providers. Further discussions with Microsoft Connected Car team might also support this activity.
- Christian: IMHO we should abstract our framework from the different cloud infrastructures
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
- Gunnar: I need to sync with Glenn on the tech brief

CVII ramp-up

Gunnar & Philippe: we want to repurpose the Wednesday CCS calls on CVII technology stack activities
Christian H is interested in starting the activity
Kevin: it is a good initiative to refresh the call
discussion on the scoping of CVII project on data-driven vehicle development
AASIG participant TietoEVRY is interested in the AUTOSAR connection which is very concrete, they will join the call

Monday 2021-01-18

Asia friendly time 11:30am CET

Agenda

sync with Sanjeev

Participants

Sanjeev, Gunnar, Philippe

Minutes

we looked at CCS framework architecture
Gunnar: resource management on top right is actually graphql server
Sanjeev: intends to work on AWS technology
discussion on the cost impact of using technos like AWS
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-190
created to follow Sanjeev's work
- workplan will explore different AWS services (like Kinesis, Firehose, Greengrass, etc), in the context of
  1. Architectural fit for CCS/VSS goals
  2. Use cases enabled.
  3. Cost-benefit analysis.
  4. Features provided.

Wednesday 2021-01-13

US friendly time 17:00 CET

Agenda

Fosdem talk readiness check

Participants

Kevin, Ulf, Stephen L, Gunnar, Philippe, Ted

Minutes

Fosdem talk readiness check

final tuning of the talk delivery, Ulf has produced his part of the video, Kevin will record his part and deliver the whole of it for Friday
useful link: https://fosdem.org/2021/schedule/event/open_communication_fw/

Monday 2021-01-11

US friendly time 16:00 CET

Agenda

sprint review

Participants

Ulf, , Kevin, Stephen L, Benjamin, Christian H, Gunnar, Philippe
apologies: Iyyaz

Minutes

review of jira tickets

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-87
- discussion on AUTOSAR protocols someip, ara.com, ara.rest; mqtt but not an AUTOSAR protocol
- Gunnar, shows FARACON tools
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-53
no feedback yet, will ping Sensoris people again next week
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-129
no pull request on github yet
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-59
email sent to Michael today
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
Gunnar: we discussed joint publication GENIVI/Geotab of a Tech Brief paper (one-pager) on Curve Logic. Here are examples of previous tech briefs to see what that would look like.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-20
title renamed to tell this will be for CES 2022
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-141
The web site is down, currently.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-140
Gunnar added a comment: The ideal outlook is for people who were active in SAREF to join the CVII work and incorporate what they developed into a common data model and be able to continue the work. In any case, the results published in the License project repository (link above) has a BSD 3-clause license, which enables derivative work, with attribution.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-183
Gunnar added a comment: I think
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-137
may have some ideas worth looking at, the idea of implementing a twin in the cloud, with cached data.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-182
Gunnar added a comment: Christian H /Gunnar: It would be useful to plan an entire meeting on this, with preparation
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-174
Philippe added a comment and assigned the ticket to Gunnar: did you forward info on this work to the security team ? they might be interested in the references on ISO work listed in this document

Wednesday 2021-01-06

US friendly time 17:00 CET

Agenda

comparison analysis between AWS and CCS framework
Fosdem

Participants

Kevin, Ulf, Stephen L, Gunnar, Philippe, Ted, Marty

Minutes

comparison analysis between AWS and CCS framework

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-101
discussion captured in V2 of the document attached to the Jira ticket
Ulf: Geotab proposes to do a similar comparison analysis for google, including google analytics and CCS framework

Monday 2021-01-04

US friendly time 16:00 CET

Agenda

Fosdem
IBM Cloud vs CCS

Participants

Ulf, Glenn, Kevin, Stephen L, Iyyaz Barber (Cobrasphere), Benjamin, Gunnar, Philippe
apologies: Benjamin, Ted (due to a VSSo call)

Minutes

fosdem

CCS talk was accepted
Kevin will start this week, slides will be discussed the slides on Wed next week (13 January)
recorded video is to be provided to Fosdem by Friday 15

ibm cloud

Iyyaz goes through the preliminary comparison analysis between IBM Cloud and CCS framework
the analysis is documented in
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-189
- there is no straight relationship to greengrass in IBMCloud
- discussion on the components related to data analysis
- discussion on whether we would try out one particular platform or several

next step

next step on Wed call is to revisit the CCS architecture and decide what we do next

Wednesday 2020-12-16

US friendly time 17:00 CET

Agenda

gap analysis between AWS and CCS framework
Fosdem

Participants

Kevin, Stephen L, Iyyaz Barber (Cobrasphere), Gunnar, Philippe, Ted

Minutes

comparison analysis between AWS and CCS framework

Kevin: redelivers the comparison analysis for Ted and Iyyaz
- look at
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-101
reaching AWS: Ted had a good call with Patrick Bartsch, needs to continue reaching him out, discussion on AWS strategy as known by Ted, AWS is a member of W3C but in different domains
Stephen: intitiates a discussion on the greengrass connectors
- look at https://docs.aws.amazon.com/greengrass/latest/developerguide/connectors.html
- discussion continues on greengrass scope of functionalities
- look at Stephen's comment in
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-101
- look also at: https://docs.aws.amazon.com/greengrass/latest/developerguide/what-is-gg.html
Iyyaz: I will look at what IBM is providing that would be in a similar way
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-189
  created, to be assigned to Iyyaz
Iyyaz: what would be the criteria for selecting one technology ?
Gunnar: criteria will mostly be the technical ones

Fosdem abstract

Kevin will finalize the abstract by the end of the week and publish in Fosdem CfP web site DONE. Abstract is here

Call plan for the period

no calls during next week and the week after
next CCS call will be on Monday 4th January at 4pm CET and Wednesday 6th January at 5pm CET

Monday 2020-12-14

US friendly time 16:00 CET

Agenda

welcome to new participant
CVII follow up
Fosdem
GAIA-X & EATA
sprint & backlog review (postponed because Jira is not available)

Participants

Ulf, Glenn, Kevin, Stephen L, Iyyaz Barber (Cobrasphere), Gunnar, Philippe
apologies: Benjamin, Ted (due to a VSSo call)

Minutes

welcome to new participant

Iyyaz Barber (Cobrasphere) joins for the first time, Iyyaz attended the GENIVI AMM
quick roundtable
Iyyaz: works on API connectivity, rather on the entreprise side, how to collect data from the edge, his expertise is with MS Azure, IBM cloud and other smaller provides, one of his colleagues is knowledgeable about AWS
discussion on CI infrastructure, discussion on containarization pros ans cons

CVII follow up

MS: Gunnar and Philippe and Ted (W3C) had a good call with MS MCVP team members last week, MS is very supportive of the CVII work, and wants to make sure the information about CVII is distributed in the MS organization, MS preferred language for describing data and data relationships is JSON-LD - JSON for Linking Data (which a W3C specification), url: json-ld.org, MS DTDL is based on JSON-LD
MS: Gunnar shows the slides about DTDL and various translation approaches he shared during the call with MS
Hyundai: Hyundai is working on a vehicle data model, but whether they want to help building a standard is still TBD
Sensoris: Gunnar has reached them out again in order to set up a coordination, this is work-in-progress on Sensoris side

Fosdem

Philippe: what's up with the abstract preparation ?
Kevin: having Geotab as a co-presenter would be good
Glenn: agrees that Ulf should be involved
Philippe: my proposal is to recycle the presentation delivered by Kevin at the GENIVI AMM and to show code in github
TODO Ulf and Kevin with Gunnar's support will prepare an abstract for Wednesday 16 December
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-188
commented

GAIA-X & EATA

Philippe browses through the GAIA-X project web site: https://www.data-infrastructure.eu/GAIAX/Navigation/EN/Home/home.html
in the technical concept section - How GAIA-X project works ? it is stated that one focus area will be an "easy access to the available providers, nodes and services. Data will be provided through federated catalogues"
in the BMW/AWS press release, it is also stated that "The BMW Group will contribute its expertise from these use cases to the recently announced Automotive Alliance, which will be based on GAIA-X standards. As founding member (BMW Group) and “Day 1 Member” (AWS) of GAIA-X, the two companies are striving to further develop the Cloud Data Hub towards the GAIA-X standards for sovereign, secure and innovative data spaces"
although the data spaces referred to there might be rather relevant to parts and manufacturing, it would be good to determine whether this work complements or supersedes CVII work
then Philippe browses through the EATA alliance web site: https://eata.be/, both BMW and Hyundai are members together with Toyota and Mazda (and also Iveco and MAN truck manufacturers), does EATA complements, overlaps or supersedes CVI work ?

gap analysis between AWS and CCS framework

it is proposed to go again through the analysis performed by Kevin during the Wed call if Ted and Benjamin can make it

sprint review

postponed due to Jira being not available

Wednesday 2020-12-9

US friendly time 17:00 CET

Agenda

gap analysis between AWS and CCS framework
Fosdem

Participants

Kevin, Ulf, Stephen, Philippe, Gunnar

gap analysis between AWS and CCS framework

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-101
Kevin: shows the analysis he made on AWS, this makes sense today because of the joint press release by BMW and AWS - look at https://telematicsnews.info/2020/12/08/aws-and-bmw-group-team-up-to-accelerate-data-driven-innovation/?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+telematicsnews+%28Telematics+News%29
Kevin: I initiated a gap analysis, i.e. an assessment of the mapping of AWS components on the CSS framework components, the initial results are captured in the Jira ticket
- for instance AWS greengrass would "override" Gen2 protocol implementation
- the name of Amazon timestream is mentioned : is this a time series database ?
Gunnar: do we identify some of these and try them out and integrate them ?
Kevin: 3rd party APIs to the data is not different for automotive than for other domains and might be reused, VSS2 might be a better fit because it was designed for automotive use only
Gunnar: CVII - do we convert from VSS to firehose or greengrass to use them ? for instance MS said they need everything to be translated to MS DTDL
Kevin: we do not know whether AWS have their own data model
Gunnar: Ted is in the process of organizing a meeting with Patrick Bleicher who is now with AWS
Stephen L: On the device side Greengrass Core, which has local AWS Lambda functions, msg broker etc, can be integrated into higher performance silicon components. There is also Greengrass for FreeRTOS focused on lower power MCU. It has things functionality like Greengrass discovery and MGTT agent.
Stephen L: AWS team maintains a Yocto layer to ease integration of Greengrass into Linux distributions in github https://github.com/aws/meta-aws
Stephen L: look also at https://github.com/aws-samples/meta-aws-demos. There was an integration of AWS into the AGL demo a couple of years ago, more to look at in this repo
Philippe: would like to put the topic of AWS in the agenda of next Monday's call, Unknown User (kevinval) would this be ok ?
Kevin : agreed

Fosdem

Philippe: presents the Fosdem CfP and the rationale for submitting and delivering a talk there, the CfP is there
discussion on the content of a talk to Fosdem (not captured because of audio issue on Philippe's side)
TODO Philippe to create a ticket for submitting a talk to Fosdem
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-188
created, assigned to Kevin and Ulf
Kevin and Ulf will check whether HM and Geotab can propose a joint talk at Fosdem, and report back on Monday CCS call next week

Monday 2020-12-7

US friendly time 16:00 CET

Agenda

sprint & backlog review
sync with Benjamin

Participants

Ulf, Glenn, Kevin, Benjamin, Stephen L, Gunnar, Philippe

Minutes

sprint review

review of tickets assigned
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-85
- Philippe: the original objective of this ticket was to remind The GENIVI security team which is US-centric to continue watching out what is coming from Europe which was the creator of the General Data Protection Regulation (GDPR)
- Gunnar: IMHO the team is aware of this and ticket can be closed now
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-59
- Gunnar: Michael (Cloudera) indicated to me he wanted to show the project (to some audience, do not know if it is CCS context or other). It would soon be ready – and then discuss the opportunities to tie it with CCS goals again. (Ref: Project presentation form AMM showcase)
- Philippe: why don't we ask for a presentation in early 2021 ?
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-111
- Philippe;: why about adding Geotab GoDevice as a possible source of vehicle data ?
- Ulf: Geotab works currently on a new tool that converts the Geotab "address space" to the VSS "address space".
- Gunnar: could it be open source code ?
- Ulf: yes, it might be open sourced, but it is intended for cloud use not for embedded use
- Gunnar: will add this comment to the ticket - Geotab signal input device collection to VSS translation is under development. This code might be more cloud than embedded-focused, but keeping a lookout for it as potentially reuse as a kind of vss-feeder.
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
- Gunnar: the Geotab code is coming out
- Glenn: engineering has completed the preparation of code and doc, code will reside on geotab github and genivi github will point to it, the code will be published under MPL2.0
- Gunnar: will help Geotab engineering team to finalize the publishing of the code to-morrow
- ticket to be commented and closed when code is uploaded on github
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-102
- Gunnar: discussion started with Bosch Christian K on whether we make a techno stack for VSS/CVII, this will be at the agenda of CCS call on Wednesday
- Jira
  server JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-150
  &
  Jira
  server JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-151
  - to be linked to this ticket, DONE
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-140
- Benjamin will check the status of SAREF deliverables again
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-182
&
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-183
- Gunnar: to be added to the list of topics for synchro with Bosch
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-160
- Gunnar: we should remove Sanjeev from these implementation tasks, Sanjeev is now working on grafana and inflexdb
- Gunnar: we need to sync with Cloudera on the usage of Apache / Nifi components
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-187
  created to track Sanjeev's work on grafana and inflexdb
- CCS-160 thrown back to the backlog
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-184
- Gunnar: we need to discuss with Bosch on waht they want to do
sprint extented until Friday 18 December

Sync with Benjamin

VW: is is still a W3C member although not active
discussion on how to reach out to VW
VSSo : eurecom has made a proposal for vsso, there is a need for a sync on vsso between Ted, Gunnar, and Benjamin
TODO GUnnar to set up a meeting with Ted and Benjamin on VSSo

Wednesday 2020-12-2

US friendly time 17:00 CET

Agenda

implementation review

Participants

Ulf, Christian K, Gunnar, Philippe

Minutes

implementation review: kuksa code walktrough
discussion with Christian on the code structure of https://github.com/eclipse/kuksa.val and a possible extension of the technology stack developed by bosch in kuksa.val
Gunnar; shows the activity matrix for cvii and bosch additions at the bottom of the page

Monday 2020-11-30

US friendly time 16:00 CET

Agenda

sprint & backlog review

Minutes

sprint & backlog review: the following tickets were reviewed

Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-53
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-185
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-129
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-181
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-101
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-183
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-184
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-68

Wednesday 2020-11-25

US friendly time 17:00 CET

Agenda

code implementation review

Participants

Ulf, Kevin, Gunnar, Ted, Stephen L, Philippe

Minutes

github browsing

Monday 2020-11-23

US friendly time 16:00 CET

Agenda

Autosar signal2service interface
sprint & backlog review

Participants

Christian H, Matthias Danzeisen, Glenn, Kevin, Stephen L, Ted, Gunnar, Philippe

Minutes

Autosar signal2service interface

Gunnar: with this mechanism, are we talking of CAN signals or something at a different level ?
Matthias: there is a specification / methodology defined to map signals to interfacesn like signals on a Can bus
Matthias: a possible implementation uses a signal2service daemon where you map udp signals to service
discussion captured in
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-87
comment section
Matthias: an explanation of the sensors interface mapping of the iso standards to signal2service is provided there
- https://www.autosar.org/fileadmin/user_upload/standards/adaptive/19-11/AUTOSAR_EXP_SensorInterfaces.pdf
- this document refers to the following reference documents
- SAE J3016 automation level 3-5
- ISO/DIS 23150 Road vehicles — Data communication between sensors and data fusion unit for automated driving functions — Logical interface

sprint & backlog review: the following tickets were reviewed

Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-88
- Philippe to ping Guru on CCS-88 and possibly close the ticket
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-87
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-101
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-135
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-152
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-184

Wednesday 2020-11-11

US friendly time 17:00 CET

Agenda

sprint & backlog review

Participants

Ulf, Kevin, Gunnar, Philippe, Ted

Minutes

sprint & backlog review (continuation of review started last week)

Jira

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

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-110
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-111
  - Gunnar will add a comment explaining his thougths concerning the use of driving simulators and "foreign tables"
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-112
  - Gunnar: this work item (which is done) relates actually to the so-called Technology Stack work identifed in the CVII activity matrix, we will talk to Bosch this week in a CVII workshop follow-up call and the question of candidate components for the technology stack will be addressed there
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-160
- Philippe: we need to talk with Sanjeev BA and determine the status of the various subtasks (suspended and put back in the backlog or in-progress), will schedule a call with Sanjeev next Monday
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-133
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-134
  - Kevin: the code is in github, ticket done

Jira

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

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-8
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-102
  - Philippe: I added two links to this ticket, one link relevant to the use of a production-grade database
    Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-123
    and one link to the investigation on which components from the KUKSA.VAL project could be reused for a demo
    Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-184
  - Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-184
    assigned to Ulf Bjorkengren, Ulf should be able to start looking at KUKSA.VAL in 2-week time
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-146
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-148
  - Gunnar: e should Unknown User (alexander.domin) for an update on the status of any work concerning this that could be in-progress on BMW side ? Thanks
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-149
  - Gunnar: I still have issues running the OpenDS simulator
  - Philippe: if we were meeting F2F, this would be solved in a peer programming session
  - Gunnar: let us schedule a conference call with Stefan Wysocki for hosting this peer programming session

Jira

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

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-139
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-101
  - Philippe
    Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-101
    in last Monday's call, Sebastian explained they are now working on the data collection use case where sets of data are pushed to AWS, IMHO we need to analyze how the AWS can be used to support parts of the CCS communication infrastructure
  - ticket assigned to Unknown User (kevinval)

AOB

Ford press release : Ford published a press release on 11 November about this collaboration and the usage of neutral servers: https://media.ford.com/content/fordmedia/feu/en/news/2020/11/11/drivers-to-benefit-from-smarter-insurance--maintenance-and-recov.html

Monday 2020-11-9

US friendly time 16:00 CET

Agenda

sprint & backlog review
AMM follow up - CVII

Participants

Sebastien, Gerald, Ulf, Glenn, Ted, Kevin, Benjamin, Stephen L, Gunnar, Philippe

Minutes

sprint & backlog review

review of tickets assigned to Benjamin & Sebastian & Gerald
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-109
- Sebastien: there is no vehicle state storage in kuksa, it is a digital twin within the car taking info from CAN and talking VSS to the cloud, the online use case with data streaming is implemented using MQTT (actually a subset of MQTT)
- Sebastien: we are now working on the data collection use case using the web socket interface for collecting a batch of data and upload it to Amazon
- Gunnar: reminds Sebastien about the mqtt paper produced by the CCS project a while ago, Sebastian Schildt please have a look at
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-143
  , paper is attached to this ticket
- Sebastian: the code of the demo by Bosch at the GENIVI AMM is available at https://github.com/eclipse/kuksa.val <-- Reuse THIS
- Philippe: it might be worth looking at what could be reused in the Bosch demonstrator for the next version of the demo, ticket
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-184
  created
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-171
,
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-173
- Benjamin: reviewed these documents while he prepared the slide deck on Sensoris/Jaspar/VSS (comparison of data models) for the AMM, look at TBD
- tickets can be closed
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-140
- Benjamin: will look at it again and check whether the SAREF automotive spec has been published
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-138
- Philippe: we need to sync with Bosch on the Digital Twin Description
- Sebastian: I fully agree with the fact we need to sync on digital twins
- Gunnar: IMHO the question is where do I search from the current correct values of the vehicle data (even if there is a disconnect iwth the car)
- Sebastian: there might a twin in the cloud and a twin in the car
- Sebastian: I can reach out people from Bosch involved in Ditto project and put them in contact with whoever in CCS team is willing to look at Ditto
- Philippe: CCS-138 to be closed because Bosch delivered a presentation on digital twins at the AMM, look at Bosch slide deck
- Philippe: I suggest to add a subtask to CCS-136 to determine which kind of digital twins is useful in the context of the CCS /CVII projects

AMM follow up - CVII

upcoming Webinar: Mobex scheduled a webinar on CVII on 19 November, this seminar is intended to disseminate further the W3C/GENIVI initiative on the Common Vehicle Interface
Gunnar: introduces and gives an overview of the wiki page he created whose purpose is to structure the CVII work, please look at Common Vehicle Interface Initiative - Activity Matrix
Philippe: it would be good that CCS participants review the page for next week Monday call
the follow up with Bosch, Renault, Ford, Hyundai, Volvo, VW etc. is in-progress
Gunnar: the objective is to have one-to-one discussions with each party to identify what they want to do with CVII
ticket
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-185
created for tracking the review results

Wednesday 2020-11-4

US friendly time 1700 CET

Agenda

sprint & backlog review

Participants

Ulf, Kevin, Gunnar, Philippe
apologies: Ted

Minutes

sprint & backlog review

review of epic
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-18
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-106
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-107
  - State storage is actually implemented using SQLite in the demo delivered at the AMM, ticket comm"nted and closed
  - TODO Philippe to poke Keith on the liaison with Autosar, there is a need for a translation from Autosar to VSS DONE waiting for feedback
  - Philippe: an alternative contact for Autosar might Christian H.
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-108
  - SQLite ias accepted and used in production already, do we have alternatives ?
  - Ulf: some years ago, JLR develop something called VSI (on genivi github) that relied on shared memory
  - Gunnar: in some sense it is a kind of library, relevant to state storage
  - links in github
    - vehicle_signal_interface repository
    - vehicle_signal_manager repository (might be worth having a look at this too)
  - TODO Ulf to have a quick look at VSI, ticket assigned to Ulf
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-109
  - there is a need to reactivate the discussion with Sebastian and Bosch in general
  - TODO Philippe to poke Sebastian, ticket commented
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-121
  - Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-123
    - Gunnar: it would be good to demonstrate with thousands of vehicles to show the performance
    - Ulf: agreed
    - ticket assigned to Gunnar, Ulf will help adapting the go code in the server (postgres)
    - note: postgres is an option, influx DB is another option
  - Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-168
    - need to poke Glenn about it ?
    - ulf: would rather cancel it
    - ticket closed ac CANCELLED
- review of backlog suspended at
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-128

review of workbreakdown structure

entry #1 - In-vehicle State storage : technonology choices for proof-of-concept and production-grade updated, see Jira tickets
entry #4 - In-vehicle Data server : technonology choice for proof-of-concept updated (Gen2 implementation now uses ovds.db file. On-demand requests are fetched from database. Timed subscriptions are also supported, i.e. send updates at regular intervals.
- There is not yet implementation of a trigger to the gen 2 server from the database when a new value is written (SQLite supports trigger in theory).
entry #8 - OEM cloud access management :
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-127
is a large piece of work
entry #9 - OEM cloud resource management: we still use the manually generated graphql schema
- Gunnar: the update of the graphql schema is still to do, will poke Daniel (BMW) on this
- a new ticket is to be created for tracking the connection between graphql and ovds,
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-181
  created
- entry #10 - neutral data server marketplace

AOB

CVII working session follow up
- Renault, Huyndai: Gunnar
- Ford, VW: Philippe
Gunnar proposes to update a table in the internal wilki we used when we prepared the AMM which is agreed

Monday 2020-11-2

US friendly time 16:00 CET

Agenda

AMM debriefing
sprint & backlog review

Participants

Ulf, Glenn, Ted, Kevin, Stephen L, Guru, Gunnar, Philippe

Minutes

AMM debriefing

Kevin: not too much of a discussion in the session, although I got some comments privately, no new work items were identified
Ulf: it was interesting to watch the demo
Glenn: we need to follow up the presentation on curve logic, the next step is to get the license agreement signed, we would like to discussion the various open source license options with Gunnar
- TODO Gunnar to send possible timeslots for a call with Geotab
Ted: my interest is with the follow up on CVII
Philippe: I will have a call with the ISO ExVe WG convenor this week and then we will schedule with him to determine how we can coordinate with ISO
slide decks and videos are available at GENIVI Virtual Member Meeting October 2020

Sprint & backlog review

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-87
assigned to Unknown User (christian.heissenberger)
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
as discussed above
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-11
closed
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-180
  a new one to be created (technology stack for CVII)
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-59
- we watched Cloudera project marketing pitch at the beginning og the AMM, to be discussed in this week's PMO call, Michael to be poked again
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-102
we need to identify the feature content for the next version of the demo in 2 or 3-month time (next milestone was CES at the beginning of Jan 2021)
- to be discussed in Wed call, we will update the WBS wiki page CCS Reference Architecture - Work Breakdown Structure
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-159
add link to Stefano's presentation, ticket is closed
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-71
Kevin will finalize this ticket
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-83
- Gunnar: we had a significant discussion on last Friday's VHAL working session
- discussion on access control policy
- Philippe: it would be good to create a wiki page to capture the inputs for creating an example
- Ulf: will populate the wiki page Data Access Control
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-105
the follow up with the various stakeholders of CVII will be discussed in this week's PMO call

Monday 2020-10-19

US friendly time 16:00 CET

Agenda

upcoming AMM - CCS demo & work session preparation readiness check

Participants

Ulf, Glenn, Ted, Kevin, Stephen L, Gunnar, Philippe

Minutes

demo readiness check

Gunnar: had a talk with Sanjeev roday about his work on Grafana, Sanjeev might deliver some code this week
Gunnar: the demo system is up & running
- discussion on initialisation of processes with Ulf, issue fixed
Ulf: tested the OBD live data provided by his colleagues in Toronto, these data cannot be shared yet, but a sharable data set is expected shortly, these data were recorded using the curve logic algorithm, we might have some inconsistencies when displaying them (to checked)
- the data set is the following

Code Block

title	OBD II data set

Vehicle/Cabin/Infotainment/Navigation/CurrentLocation/Longitude

Vehicle/Cabin/Infotainment/Navigation/CurrentLocation/Latitude

Vehicle/Drivetrain/Transmission/Speed

Vehicle/Acceleration/Longitudinal

Vehicle/Acceleration/Lateral

VehicleAcceleration/Vertical

Vehicle/Drivetrain/FuelSystem/Level

Vehicle/TravelledDistance

Vehicle/ADAS/ABS/IsEngaged

Vehicle/Drivetrain/InternalCombustionEngine/RPM

Vehicle/Drivetrain/Transmission/Speed

Vehicle/Cabin/Infotainment/Navigation/CurrentLocation/Altitude

Vehicle/OBD/CoolantTemperature

Ulf: will share the sharable OBD data set with Gunnar as soon as I get it

status report and working session readiness check

Kevin: I still need a slide on CVII from Gunnar and I am still missing other topics for discussion in the workshop
Philippe: Unknown User (glenn.atkinson) can Geotab provide a topic ?
discussion on curve logic algorithm that could be a good candidate for discussion
Glenn and Ted will work on the preparation of the curve logic topic, to be checked on Wednesday call
Philippe: we expect some slides to introduce each topic discussed during the working session
topic added to wiki page 2020 October Tech Summit — CCS working session

Wednesday 2020-10-14

US friendly time 17:00 CET

Agenda

eSync Alliance / GENIVI joint presentation
AOB

Participants

to be updated

Minutes

eSync Alliance slide deck (not uploaded yet)
GENIVI slide deck (not uploaded yet)

Monday 2020-10-12

US friendly time 16:00 CET

Agenda

upcoming AMM - CCS work session content
sprint review

Participants

Ulf, Benjamin, Kevin, Christian H, Stephen L, Gunnar, Philippe

Minutes

CCS work session content

wiki page for preparing the session is at 2020 October Tech Summit — CCS working session, the link to the updated agenda is there
the wiki page identifies also the expected contributors to each section of the working session
TODO all participants to add topics for discussion during the working session in the table at the bottom of the wiki page

sprint review

Augment Vehicle Data Model
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-170
Benjamin presents his findings
- vehicle motion interface specs mostly describe ADAS systems, a lot of stuff we are not interesred in (physical laws), describe some sensors and actuators, raw signals and intermediate signals, some systems are pretty simple, please look at Benjamin's comment in Jira
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-173
Benjmain presents his findings
- this work is much closer to what W3C is doing (REST interface, json payload on http), it is a top down hierarchy, with metadata, containers and subcontainers, there are some common elements with VSS sections, e.g. start time, end time, etc, iso description of map section ids
- the message structure is pretty interesting, some links to ISO standards for time and location and good practices, this looks similar to we need in VSS to contextualize the vehicle data we define
- please look at Benjamin's comment in Jira
Benjamin: it would be good to get an example of a json payload defined by Jaspar
- Philippe: there are two more documents to review, assigned to Unknown User (benjamin_klotz) tentatively, please confirm you can have a quick look at them
  - Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-172
  - Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-171
Philippe: IMHO it would good to add a topic on gap analysis between Jaspar and VSS in the CCS working session, the rationale is that Toyota said they will identify someone for the CVII session at the upcoming AMM, we should also invite this person to the CCS working session
Gunnar: this is a good proposal, we have work to do to identify overlap and gap both for VSS vs. Sensoris and VSS vs. Jaspar, I will update the working session content accordingly

AOB

presentation of eSync Alliance : it will be scheduled during the regular Wednesday CCS call, invite sent

Wednesday 2020-10-07

US friendly time 17:00 CET

Agenda

demo implementation status
AOB

Participants

Ulf, Kevin, Ted, Stephen, Gunnar, Philippe

Minutes

demo implementation status

Ulf: Geotab team might be able to provide by Monday next week a set of vehicle data recorded during a real trip in the Toronto area
Gunnar: shows the demo repo and explains to Ulf the build issues he has
followed by a short sync on the building of the iOS app between Gunnar and Kevin

AOB

Kevin will have a v2 of the working session content by Monday 12 October

Monday 2020-10-05

US friendly time 16:00 CET

Agenda

upcoming AMM - CCS work session content

Participants

Glenn, Kevin, Stephen L, Gunnar, Philippe

Minutes

CCS work session content

agenda updated online
addition of 2 placeholders for the list of relevant standards including security, and the liaison with CVII
discussion on a placeholder for a demo video in the status report
discussion on the demo look

AOB

presentation of eSync Alliance scheduled on Wednesday, October 14th at 17:00 CET / 8:00am PT

Wednesday 2020-09-30

US friendly time 17:00 CET

Agenda

tech summit working session agenda preparation
MS3 (tech summit) demonstrator implementation

Participants

Ulf, Kevin, Stephen, Gunnar, Philippe

Minutes

working session agenda preparation

work breakdown structure update is done
Kevin: first content for the working session agenda by next week

MS3 (tech summit) demonstrator implementation

Gunnar explains to Ulf the trouble he experienced with building with go

AOB

we will have an opportunity to sync with the eSync Alliance (https://esyncalliance.org/) in the coming weeks (likely on Wednesday 14 October during the CCS call)

Monday 2020-09-28

First call - Asia friendly time 11:30am CET cancelled due to Sanjeev's busy elsewhere

Second call only - US friendly time 16:00 CET

Agenda

work breakdown structure review
CVII update

Participants

Ulf, Glenn, Kevin, Stephen L, Gunnar, Philippe

Minutes

work breakdown structure review

objective is to update the wiki page and align the page content with the actual status of the implementation work
after the update is done, Kevin will start preparing the agenda for the working session at the upcoming virtual tech summit
wiki page updated online C CS Proof-Of-Concept - Work Breakdown Structure
discussion starts with the review of the updated block-diagram at the top of the page
review will continue during this week's Wednesday call

CVII

Gunnar browses through the slide deck shown during the 2nd OEM roundtable that happened last Thursday
- slide deck is here

Wednesday 2020-09-23

US friendly time 17:00 CET

Agenda

MS3 (tech summit) demonstrator implementation review
work breakdown structure update

Participants

Ulf, Kevin, Gunnar, Philippe

Minutes

application level

High-Mobility reports their progress on the implementation of the app
- https://github.com/highmobility/vss-graphql/tree/electric_powertrain
- https://github.com/highmobility/ios-vss-graphql-client-demo
application runs on Apple IOS
the data used are the EV data in VSS branch
Ulf: discussion on OBD data that are available at Geotab, they could be used for a second demonstrator, will investigate what can be done in the given timeframe until the virtual tech summit (26-30 October)

work breakdown structure

the objective is to start preparing the tech summit
TODO Kevin update the names and chosen technologies in the wiki page & block diagram
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-178
&
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-179
created (attached to epic dissemination)

Monday 2020-09-21

First call - Asia friendly time 11:30am CET cancelled due to Sanjeev's busy elsewhere

Second call only - US friendly time 16:00 CET

Agenda

sprint & backlog review - CCS

Participants

Ted, Glenn, Kevin, Stephen L, Gunnar, Philippe

Minutes

sprint & backlog review - CCS

Jira updated online, in particular
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-123
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-80
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-59
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-87
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-134
changed to in-progress

Wednesday 2020-09-16

US friendly time 17:00 CET

Agenda

MS3 (tech summit) demonstrator implementation review

Participants

Ulf, Kevin, Gunnar, Philippe

Minutes

demonstrator implementation review

Gunnar: shows the status of the demo packaging wih the containers
Ulf: demo almost working, json related issue will be investigated by Ulf
Ulf; there is a proposal being elaborated by Geotab for a OBD-II populated database that could be used for feeding the vehicle data
Kevin: High Mobility is working on the application level as expected

Monday 2020-09-14

First call - Asia friendly time 11:30am CET cancelled due to Sanjeev's busy elsewhere

Second call only - US friendly time 16:00 CET

Agenda

sprint & backlog review - CCS
CVII
tech summit preparation

Participants

Ted, Glenn, Kevin, Stephen L, Gunnar, Philippe

Minutes

sprint & backlog review - CCS

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-5
assigned to Kevin
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-168
- Gunnar: it seems Geotab have an opinion on the distance between their platform and the CCS communication framework
- Glenn: Geotab sdk is open and interfaces are public, Geotab will provide their vision of the so-called distance
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-169
closed as duplicate on CCS-168
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-101
- Gunnar: would it be interesting to use some of the AWS services ? deploying using AWS lambda is worth looking at after the tech summit
- Gunnar: is it a topic for the agenda of the working session ? who can bring the knowledge ? who has contact as AWS automotive ?
- Kevin: at HM we work rather with OEMs directly, we swork on safety KPIs son top of ISO 27017
- Kevin: https://docs.aws.amazon.com/solutions/latest/connected-vehicle-solution/architecture.html
- Stephen L: AWS are both in the cloud and in the vehicle, it is worth looking at greengrass that overlaps our solution, IMHO this is not competitive, rather complementary
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-141
- Gunnar has not reported the work he did on it, still needs to look at this
- please push it later to the following sprint after the tech summit
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-53
the call with Sensoris plenary meeting is scheduled on Thursday morning this week

CVII

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-105
- Gunnar will produce a slide deck from the scoping document he wrote for the 2nd OEM RT
- in the 2nd rountable, we expect to have a sort of vote about the OEM commitment
- we did a sync up between GENIVI and W3C about our OEM contacts

tech summit preparation - abstract for the working session

the proposed abstract text is below
it is expected that the agenda for the CCS working session will be derived from the text below and augmented with whatever topic needs to be addressed
"The current GENIVI work on data-driven connected vehicle software architecture is an important step towards achieving the seamless coupling of the in-vehicle and back-end architectures and delivering an end-to-end vehicle computing platform. This end-to-end platform leverages existing standards and solutions, but some gaps exist and overall interoperability is still far from achieved. We are convinced the GENIVI work will help the automotive industry take a big step toward the future when the in-vehicle software, E/E architecture and the back-end architecture will be moving closer together.
The Cloud & Connected Services (CCS) project team has undertaken during Q2, 2020 the implementation of an end-to-end vehicle-to-cloud communication framework proof-of-concept demonstrator. This framework incorporates technology components identified by various collaborative projects such as W3C Gen 2 protocol built on VSS2, GraphQL, ISO Extended Vehicle Neutral Server. It clarifies connections to in-car technologies such as AUTOSAR-defined SOME/IP and several others.
The CCS project team will present a status report of the CCS proof-of-concept implementation and explain the design choices made. The following topics will be also comprehensively debated:
- how to augment the vehicle data model, collaboration with the Sensoris project (www.sensoris.org)
- discussion on which APIs and components on the proposed architecture are candidates for standardization, the objective is to enable an open market for the software components of the communication framework (components are either in-vehicle or in the cloud)
- discussion on how the CCS project will contrbute to the newly laucnhed work on a Common Vehicle Interface (CVII)."

Monday 2020-09-06

First call - Asia friendly time 11:30am CET - shifted to Tuesday 7 September

Agenda

contact with Cloudera
sprint & backlog review

Participants

Sanjeev, Gunnar, Philippe

Nifi

Sanjeev is willing to move away from the Nifi implementation (
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-160
), we need to find another develop for this
Gunnar introduces the grafana tool (https://grafana.com/) which raises Sanjeev's interest, Sanjeev will do some experiment with Grafana

Jira ticket

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-162
updated
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-161
updated
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-176
created
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-177
created

Second call only - US friendly time 16:00 CET

Agenda

Geotab presentation

Participants

Stefano Peduzzi (Geotab), Benjamin K, Chrsitian Heissenberger, Glenn (Geotab), Ulf (Geotab), Guru, Kevin, Stephen L, Gunnar, Philippe

Minutes

Geotab presentation

Stefano's presentation identifies the business cases for Geotab, in particular the CVaaS (Connected Vehicle as a Service) is the one that is supported by the CCS communication framework end-to-end architecture
presentation is here
Philippe: IMHO this presentation matches well what was expected from the tasks in
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-5
, this is to be consolidated further when the presentation is published

Wednesday 2020-09-02

Recap of implementation plan and status.

The plan/status table in CCS Reference Architecture - Work Breakdown Structure is a bit outdated (wrong(?) responsibles, wrong plan).
It still needs a bit of an update. For now taking the notes here.

In Vehicle Server : still W3C_VehicleSignalInterfaceImpl

State Storage : Implemented by statestorage dir in ccs-w3c-client
Connection vehiclesever to statestorage is in ovds client / server in same repo

Demo Goal

Vehicle/OEM cloudside

- Data collection into state storage by driving the simulator around
- Gen2 server support get/set and subscription
- (Subscription using timer should work, but is not change triggered yet)
- OEM Cloud: Vehicle client can be set to send requests on a timer. Using a file to list signals.
- Stores data with timestamps into database
- Aim for signals that can be graphed
- How to visualize? Grafana. First approach integrate with sqlite according to current schema.

Neutral-Cloud-side
- Swift app with GraphQL client (mostly exists)
- Fetches data from GraphQL server in OEM cloud (server not yet started)
- Shown in a iOS application
- Easiest to go directly to OEM cloud for this demo

Remaining work:

Integration OpenDS to statestorage (Gunnar)
- Define the signals that we expect to have (from OpenDS) --> Swift App can use
!! GraphQL to OEM database integration (?)
Grafana investigation and integration (Gunnar?)
+ "Fake" data feeder for Electrical Vehicle related signals
- list of signals need to match OpenDS is delivering
packaging/testing, preparation
(Optional) Subscription hook on new value / change - make server aware

Side tracks:

Consider using influxdb instead in cloud (database optimized for time series data)

Monday 2020-08-31

First call - Asia friendly time 11:30am CET cancelled due to Sanjeev's busy elsewhere

Second call only - US friendly time 16:00 CET

Agenda

sprint & backlog review

Participants

Ulf, Glenn, Kevin, Guru, Gerald Gunnar, Philippe

Minutes

Review of Jira tickets on data model in particular

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-174
Guru has performed review worl on SVI, i.e. the Secure Vehicle Interface (SVI), there is a need to determine how this fits with the CCS work
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-138
assigned to Gerald in order to get info from internal Bosch projects on DTDL
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-80
- Gunnar: we made progress on our understanding of DTDL, we need now to write the VSS to DTDL translator
- TODO: Philippe to get back to MS to discuss this
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-153
- Georg will moderate a panel at the upcoming virtual tech summit
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
- Glenn: the paperwork about licensing is done
- Glenn: will send the proposed text to Steve, Gunnar and Philippe for review
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-152
- Sync with W3C on contacts with Renault done on Thu 3 September (context: CVII)
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-169
- Glenn: Geotab proposes to deliver a presentation on Geotab platform during next Monday's call
- Philippe: agreed, meeting invite sent
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-53
- call with Sensoris Lead Architect from Bosch scheduled on Wed 2 September
- Lead architect proposed the Sensoris steering committee to coordinate with GENIVI the next day, the proposal was accepted
- a presentation of GENIVI VSS and CCS work is scheduled at the next Sensoris plenary meeting in September, Gunnar will deliver the presentation

Monday, July 27 - Vehicle Data Model, Common Vehicle Interface Initiative

First call - Asia friendly time 11:30am CET cancelled due to Sanjeev's busy elsewhere

Second call only - US friendly time 16:00 CET

Agenda

Jaspar data models & APIs
sprint & backlog review
next calls

Participants

Benjamin, Kevin, Stephen L, Philippe
apologies: Ulf

Minutes

Jaspar data models & APIs

Philippe: presents shortly the work done by Jaspar (the Japanese sister organization of Autosar) on the Autonomous Driving / ADAS Vehicle Motion Control Interface
- (ST-AVI-1) AD/ADAS Vehicle Motion Control Interface Specification
Stephen: points out that Jaspar has published additional documents on the vehicle interface that might be relevant for the VSS / VSC work
Benjamin will have a look at these documents and report whether they complement or overlap with VSS
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-170
created and assigned to Benjamin
the list of Jaspar documents to review in addition to ST-AVI-1 above is at https://www.jaspar.jp/news/498
- (ST-VI-1）Dynamic Vehicle Information Sharing API Specifications Ver.1.0
- (ST-VI-2）Dynamic Vehicle Information Sharing Concept Specifications Ver.1.0
- (ST-VI-3）Common Vehicle Information and Data Set Specifications Ver.1.0
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-173
created and assigned to Unknown User (benjamin_klotz) ,
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-171
,
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-172
created

sprint & backlog review - review of tickets assigned to Kevin and Benjamin

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-71
reminder for Kevin
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-136
next call with Microsoft is likely to be scheduled during the 2nd half of August, it would be good to Kevin's inputs before mid-August
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-133
added to the new sprint
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-140
reminder for Benjamin to sync with Gunnar
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-24
is it time to look again at the data categories ?

next call

Wednesday 29 July call is cancelled because it is better to wait for Gunnar to be back to discuss again the packaging of the demo and any other implementation topic
Monday 3 August call is cancelled, any progress on the data model related documents is to be reported in the Jira tickets
next CCS call will be on Wednesday 5 August

Wednesday, July 22 - Vehicle Data & Communication Framework

Agenda:

AASIG VHAL demo
sync with W3C
AOB

Participants

Ulf, Ted, Philippe

Minutes

AASIG VHAL demo

Stefan Wysocki has published a demo for the VHAL project proof-of-concept, that uses graphql and the OpenDS simulator
to learn about the demo code and video, please look at the minutes of the 21 July weekly meeting at https://at.projects.genivi.org/wiki/x/HYVoAg
Ulf will have a quick look at the demo

sync with W3C

Philippe: asks Ted about W3C contacts at Renault, W3C and GENIVI have different contacts, this will be taken in an offline call between GENIVI & W3C to discuss coordination of our activities w.r.t. the Common Vehicle Interface Initiative

AOB

heads up on the upcoming GENIVI AMM / technical summit
- Content planning has started
- Dates: 26-30 October
  - Day 1: thought leadership and market trends
  - Day 2-5: project working sessions

Monday, July 20 - Vehicle Data Model, Common Vehicle Interface Initiative

First call - Asia friendly time 11:30am CET cancelled due to Sanjeev's busy elsewhere

Second call only - US friendly time 16:00 CET

Agenda

CVII
sprint & backlog review
next calls

Participants

Gunnar, Ted, Glenn, Philippe
apologies: Ulf

Minutes

CVII

OEM roundtable was hold on Thursday 16 July
the roundtable received a positive feedback from all OEM participants
Ted: Ford was an advocate
next step will be a workshop to discuss the "how" that will be scheduled in the coming weeks

sprint & backlog review

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-144
- Gunnar: explains the work he did on the containerization of components in order to build a demo putting together all the system, he needs to inform Ulf of the work done, but not likely before the 1st week of August
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-125
- ticket is closed
- two new tickets are created to track the assessment of the impact of CCS work and VSS on the Geotab SDK
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-168
- and on the Geotab platform architecture
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-169
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
- conditions of access to the Geotab curve logic algorithm are closerto be pubished by Geotab
- this is followed by a short discussion on Gen2 protocol specfication wich works with time intervals and is not intereoperable with curve logic based sampling, one approach would that the Gen2 protocol detect the sampling method that is used and decide on the protocol then
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-143
- Gunnar will upload the updated tech note and close the ticket
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-80
- Philippe: will remind MS about the next agreed call whose topics are Digital Twin Description Language (DTDL) and VSS vs. AUTOSAR ARXML
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-152
- GENIVI and W3C will sync on their contacts with Renault in an ad-hoc call
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-135
- Philippe: will follow up with Christian on the scheduling of a call with SensorIS

Next calls

Philippe will set up and moderate the call on
- Wednesday 22 July at 17:00 CET
- Monday 27 July 11:30am CET and 16:00 CET
- Wednesday 29 July at 17:00 CET
no call on Monday 3 August
Gunnar will set up and moderate the call on
- Wednesday 5 August at 17:00 CET
- Monday 10 August at 11:30am CET and 16:00 CET
- Wednesday 12 August at 17:00 CET
calendar invites will be sent accordingly

Wednesday, July 15 - Communication Framework

Agenda:

Jira review
AOB

Participants

Ulf, Gunnar, Kevin, Stephen

Minutes

Jira review (tickets updated online)

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-30
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-137
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-141
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-111
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-85
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-53

Monday, July 13 - Communication Framework, Vehicle Data Model, Common Vehicle Interface Initiative

First call - Asia friendly time 11:30am CET cancelled due to Sanjeev's busy elsewhere

Second call - US friendly time 16:00 CET cancelled due to agenda collision with the GENIVI Board virtual meeting

Wednesday, July 8 - Communication Framework

Agenda:

Jira review
AOB

Participants

Ulf, Gunnar, Kevin, Stephen, Benjamin, Christian, Ted, Philippe

Minutes

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-107
- Ulf: work was done some weeks ago
- Keith is supposed to do a mapping with Autosar
- Ulf: before my vacation i updated the Gen 2 server so that it is possible to configure the dataserver so that it looks for data in a state storage database
- therefore it is possible to have a mapping from AUTOSAR or any non-AUTOSAR data for the data feeder
- Gunnar shows the code in the repo
- Ulf provides clarifications on how to launch what, either the dummy server or the server accessing the state storage database
- ovds - open vehicle data server
  - how can it be used ?
  - Ulf: by having a client requesting service from the ovds server
  - Ulf will provide info on how to launch a client
  - Ulf: will look why the obds server does not start
  - Gunnar will update the ticket accordingly
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-149
- driving simulator: Gunnar put somr work into it
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-110
- discussion on CAN representation of signals
- we would add another mapping from CAN representation to vehicle signals
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-151
- Stephen L will provide inputs when it is time to implement, ticket assigned to Stephen

Monday, July 6 - Communication Framework, Vehicle Data Model, Common Vehicle Interface Initiative

First call - Asia friendly time 11:30am CET cancelled due to Sanjeev's busy elsewhere

Second call only - US friendly time 16:00 CET

Agenda

sprint & backlog review (on data modeling related tickets)
CVIM

Participants

Gunnar, Stephen, Christian K, Benjamin, Glenn, Kevin, Keith, Philippe

Minutes

sprint & backlog review (on data modeling related tickets)

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-167
,
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-143
- discussion on Benjamin's review comments (look at file attached to the ticket)
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-53
- Gunnar: shows the addition made to Data serialization / value formats wiki page, i.e. a geospatial record in addition to the timestamp record
- Christian: are we safe w.r.t. possible changes of Sensoris in the future ?
- Gunnar: Sensoris always includes the position because of its orientation on sensing the vehicle environment, Sensoris data set complements VSS
- Christian: we should talk to Sensoris
- Gunnar: yes, we will do, we want do discuss the license
- Christian: Sensoris is open to discuss the licensing
- TODO Christian to organize a meeting with Sensoris, i.e. Bosch representative in Sensoris + others, ticket will be assigned to Christian

CVIM

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-105
- Philippe: we have made progress towards the organization of an OEM roundtable about CVIM, member and non-member OEM will gather next week, we will have 3 champions to present their views w.r.t. CVIM
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-80
- Philippe: browses through the MCVP slidedeck shown by MS during our last call of 22 June and highlights the slides describing the strategic collaboration with RNM Alliance and VW
- Philippe: gives an overview of the technical discussion with MS, look here
- discussion follows on ARXML and what is the best source of Autosar data description
- Keith thinks the Autosar UML model is the best source
- Gunnar: will contact Itemis (Klaus Birken) to know about the latest Autosar UML model and which version is available in Artop

VSS feeder

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-110
- Keith has some issues with the execution of the vehicle simular, under investigation

Monday, June 29 - Communication Framework, Vehicle Data Model, Common Vehicle Interface Initiative

First call - Asia friendly time 11:30am CET cancelled due to Sanjeev's busy elsewhere

Second call only - US friendly time 16:00 CET

Agenda

sprint & backlog review (on data modeling related tickets)

Participants

Ulf, Ted, Kevin, Keith, Gunnar

Minutes

sprint & backlog review (on data modeling related tickets)

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-53
- Possible follow-up with companies who are active in Sensoris, or more official Sensoris-representative to confirm our conclusions, and progress the data-catalog question.
- Gunnar: I'm considering extending https://at.projects.genivi.org/wiki/display/DIRO/Value+measurement+formats with the idea of values tied to a GPS position, similarly to timestamp.
- The data items that are transferred, this still ties to the question of merging data catalogs into a single one (into VSS tree format) – still open question of sorts.
- The definition of their Envelope, Message format, is useful for the particular position-oriented model and hard to reuse generally.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-156
- Glenn gives an update on discussions on licenses. Detailed paperwork coming so that we can review.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-125
- Glenn answers during meeting:
  - Standard APIs - primarily VSS would help, but also the programming interface (Geotab SDK provided to companies/users of the platform) would likely benefit from being a more standard interface to achieve better interoperability in the industry.
  - Comparing architectures, would like to review it a bit further internally first.
  - In-vehicle to cloud, efficiency is key (cellular costs). Transformation to shared formats can be done in the cloud, once the data has reached that point.
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-80
- MCVP presentation attached to the ticket

Wednesday, June 24- Communication Framework

Agenda:

Jira review
AOB

Participants

Ulf, Gunnar, Philippe
apologies: Keith, Kevin,

Minutes

Jira review

IMPLEMENTATION
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-129
- todo Gunnar to add a comment about the implementation options
- we are blocked by the regeneration of the graphql schema for EV data set
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-111
- Ulf: it would be good to write timestamps together with value
- Gunnar: I think it is ok
- Ulf: will forward it to Keith
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-111
was commented by Kevin
ANALYSIS
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-143
- Gunnar: this is completed to the right level of analysis, next step would take a few days, we need a reviewer for this
- Ulf: will look at it
- Philippe: will add Benjamin to the reviewer list,
- 2 tickets created for tracking the review
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-167
  &
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-166
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-137
- Philippe: AWS device shadow would be a good selling point to show a different implementation path
- Gunnar: yes it is possible, having a local cache in the vehicle
- Philippe: we should try to demo this for CES and ask Amazon to support it
- todo Gunnar add a comment to this ticket on how to fetch values

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-53
assigned to Gunnar for reviewing the HERE materials
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-148
- Ulf: looks very similar to the state storage
- Ulf: implementation maps Gen2 server interface
- we do not know for graphql yet
- Ulf: we should ask Piot to look at the state storage we have in github
- comment added by Gunnar

Ulf on holiday for next week

Monday, June 22 - Communication Framework, Vehicle Data Model, Common Vehicle Interface Initiative

First call - Asia friendly time 11:30am CET

Agenda

contact with Cloudera
sprint & backlog review

Participants

Sanjeev, Gunnar, Philippe

Minutes

Cloudera

Gunnar and Philippe had a phone discussion with Michael Ger last week
Michael understood we are making progress with VSS
Michael presented the Edge Computing to AI project they are working on with NXP, Windriver, Teraki (a specialist in video and data compression)
we explained Michaek we are working with Sanjeev
we gonna have another call with those companies above, then we expect to set up a call between Cloudera engineering team and Sanjeev

sprint and backlog review

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-161
- Sanjeev shows the repo nifi-nar-bundles he is working on, it is about the infrastructure plugins
- a good example is the transformation nifi-jolf-transform-json-ui
- Sanjeev is currently looking at the transformation from VSS to java, he needs to work on the following packages: ProcessorResource.java, ProcessWebUtils.java
- the test harness is in place, it can be reused as such to show how VSS works
- Sanjeev should be able to spend 4-6 hours per week, will have something by the end of the week
- Sanjeev will follow the development model nifi project is using to facilitate further upstreaming
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-124
changed to done

AOB

Sanjeev: in W3C repo, I saw no git update anymore, is there any further progress ?
Gunnar: not so many changes of the implementation in https://github.com/MEAE-GOT/W3C_VehicleSignalInterfaceImpl
Gunnar: Ulf was given some other tasks on the database, etc. Ulf thinks the server is complete now, waiting for further changes in the specs

Second call only - US friendly time 16:00 CET

Agenda

CVII
sprint & backlog review (on data modeling related tickets)

Participants

Ulf, Ted, Kevin, Keith, Gunnar, Philippe

Minutes

CVII

Philippe: OEM outreach was discussed during lats week's GENIVI board of directors call, next step is to organize an OEM roundtable bringing together member and non-member OEMs and raise their attention on CVII, the roundtable will be scheduled in early July, another roundtable iwth non OEMs will be scheduled later
Gunnar: the work on service catalog is making progress in parallel on github, this will increase our readiness level when we know more about OEM interest for CVII

sprint and backlog review

ANALYSIS epic
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-1
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-23
  Keith: no progress yet
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-159
  Ulf is waiting for Glenn (Geotab) to provide inputs
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-71
  commented
  - discussion on data points listed in the Data Categories wiki page
  - Ted: mentions an article about EU expectation w.r.t. datapoints
    - https://otonomo.io/blog/extended-vehicles-a-new-eu-regulation-based-framework-for-car-data-access/
  - Gunnar: it starts from the service stations which are not limited to OEM certified stations
  - Gunnar: I do not think it will change our framework design
  - Ted: there are two drivers regulators and business
  - OEMs will not allow 3rd parties in, but EU (and US) said this is anti competitive
  - Kevin: this requirement is covered by Extended Vehicle for the maintenance use case of data categories
  - Kevin: if there is no business behind a data point the regulator will not pushed it
  - TODO Kevin to write down the drivers
  - Kevin assigned , no urgent (targeted timeline is likely for the Fall AMM)
- Jira
  server JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-140
  - Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-78
    wip
  - clarification made on autopilot project url
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-30
  commented by Gunnar who reviewed the project materials
DISSEMINATION epic
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-41
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-7
  wip

CVIM epic
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-104
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-80
  - discussion with Microsoft last week was on the mapping from VSS to DTDL a.k.a. Digital Twin Description Language
  - Gunnar: IMHO DTDL is not so far from ARXML
  - Gunnar: Unknown User (keith.derrick) we should look for some semantics equivalence between VSS and ARXML
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-135
  Phiilippe will check how to sync with Bosch other than on Mondays

AOB

Keith: has trouble with running Ulf proof-of-concept code written in go
Ulf explains how to do "go run", usually Ulf does a "go build" first before running it
Keith: tries this out, issue solved

Wednesday, June 17 - Communication Framework

Agenda:

Jira review
AOB

Participants

Ulf, Ted, Kevin V, Stephen L, Gunnar, Philippe
apologies: Keith

Minutes

work breakdown structure review

Jira review

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-107
commented
- Ulf: I had a conversation with Keith and sent to him the ideas Gunnar and I had together on a SQL based solution
- Ulf: I started to implement the solution on my own, 80% is implemented in go in my own branch at https://github.com/UlfBj/ccs-w3c-client
- Ulf has already set up a statestorage-manager that will create the database, tables and will document how to use the SQLite database with example queries
- Ulf explains the details of his implementation
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-160
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-161
  Sanjeev posted acomment about the workplan he came out with
  - Fork nifi repo (https://github.com/apache/nifi)
  - Build an nifi-nar-bundle
    - Nar bundles seem to be more protocol/domain specific
  - Within the bundle, the implementation of
    - getters/setters
    - transform vss to JSON, CSV
    - configuration params for W3C servers
  - Add sample test file for HTML interface
  - Apache test suite
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-165
created and assigned to Keith
- Gunnar: have we tried the latest version of the LGE driving simulator? (–> this means OpenDS ?)
- We are wondering if it has any EV-related signal support.
- Maybe there is some internal state-of-the art development? Keith, could you investigate the state and development of this inside LGE and ask if there are relevant EV signals that can be extracted from the simulator?
- Please see the linked issue ~~AASIG-58~~ for details on what has been tried so far using the OpenDS simulator, as well as the "GENIVI Vehicle Simulator" which is an alternative.

Monday, June 15 - Communication Framework, Common Vehicle Interface Initiative

First call - Asia friendly time 11:30am CET

Call cancelled due to unavailabilty of participant

progress report will be provided for CCS call of Wedneday 17 June

Second call only - US friendly time 16:00 CET

Agenda

CVII
sprint & backlog review (on data modeling related tickets)

Participants

Ulf, Glenn, Kevin, Gunnar, Philippe, Gerald
apologies: Keith

Minutes

CVII

Philippe: OEM outreach was discussed during lats week's GENIVI board of directors call, next step is to organize an OEM roundtable bringing together member and non-member OEMs and raise their attention on CVII, the roundtable will be scheduled in early July, another roundtable iwth non OEMs will be scheduled later
Gunnar: the work on service catalog is making progress in parallel on github, this will increase our readiness level when we know more about OEM interest for CVII

sprint and backlog review

CVIM epic
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-104
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-136
  & subtasks
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-137
  &
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-138
  assigned to Kevin V, will look at them in the coming weeks
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-105
  Philppe will ping Bosch people about their participation to the CCS Monday calls, a new call with Microsoft is scheduled on Thursday 18 June
DESIGN epic
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-10
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-156
  - Gunnar asks Glenn for clarification because this algorithm is patented, could we have an offline discussion about this ?
  - Glenn: I could arrange an offline talk with the authorizing people at Geotab
  - Glenn: benefit from Geotab is that the algorithm enables to bring to the cloud only the data that are important and discard the less important ones
  - short discussion on what geotab and genivi could achieve together
  - Gunnar: we would need a statement of intention from Geotab about the usage of the algorithm
  - ticket assigned to Glenn
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-157
  - Glenn underlines the main input to review is Omniair - association formed to test interoperability of Tier 1 suppliers of V2V and V2X system being implemented into some current (high end) and future vehicles. https://omniair.org/tag/v2v/
  - Gunnar will contact the omniair project lead and asks for info
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-98
  ticket is done
ANALYSIS epic
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-1
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-159
  reminder for Ulf to look at elements of story telling to explain the biz value of the W3C graph project to the OEMs and other stakeholders
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-140
  Benjamin will contact the SAREF project lead and asks about the availability of the final deliverables
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-141
  Gunnar will review the materials from autopilot in connection to the review of omniair project materials, link to
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-157
  added
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-30
  Gunnar check Homeiot work and possibly closes the ticket
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-31
  Philippe will ask Sanjeev about the status of OCF automotive and possibly close the ticket
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-53
  - Gunnar: we still need to better understand the sensoris work status in particular on the measurement
  - Philippe: we should work out a short agenda for a new sync call with Sensoris
  - Gunnar: joint members of GENIVI and Sensoris (like Bosch) could help
  - Philippe: there is a HERE SDK that implements the results of Sensoris project, look at https://www.here.com/vision/sensoris
  - ticket assigned to Kevin

Wednesday, June 10 - Communication Framework

Agenda:

Jira review
AOB

Participants

Ulf, Kevin V, Keith, Gunnar, Philippe

Minutes

work breakdown structure review

Jira review

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-111
and
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-110
assigned to Keith in particular

Monday, June 8 - Communication Framework, COmmon Vehicle Interface Initiative

First call - Asia friendly time 11:30am CET

Agenda

weekly sync with Sanjeev : review of workplan on other technology options for implementing the framework

Participants

Sanjeev, Gunnar, Philippe

Minutes

review of workplan

review of slide deck attached to
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-124
Milestone content (slide #2)
- checking of the milestones content
- TODO Philippe to projectize slide #2 DONE
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-160
  created with subtasks
Edge Computing (slide #5)
- Samsung is working on the smart phone aspects of edge computing
- link https://docs.edgexfoundry.org/1.2/microservices/device/sdk/Ch-DeviceSDK/
- TODO TBD to look a little deeper in edgexdoundry for a demo poc
  - Jira
    server JIRA
    serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
    key CCS-163
    unassigned for the time being
Apache Spark (slide #4)
- Gunnar: it is not only a database
VSS on Eclipse Paho (slide #6)
- Gunnar: mentions the ticket about mapping VSS to MQTT (specification only)
- Sanjeev: Eclipse Paho is just a tooling
- Sanjeev: it comes with a simulator which is quite attractive
- Gunnar: VSS on MQTT - maybe we need to work on this earlier than December; someone else can perhaps look at it

Cloudera

Gunnar: Cloudera contacted, no feedback from them yet
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-59
commented

Second call only - US friendly time 16:00 CET

Agenda

CVII

Participants

Keith, Ted, Ulf, Glenn, Steve, Kevin, Gunnar, Philippe

Minutes

CVII

Gunnar: makes a recap on CVIM discussion, Gunnar Andersson please update the slide you showed, thanks
Keith: who is the OEM active in W3C ?
Ted: JLR
Keith: what is the service catalog about ? VSS is about the data acquisition
Ted: JLR is proposing something to GENIVI & W3C for the command side (service catalog)
Ted: please have a look at https://www.w3.org/2020/03/26-auto-minutes.html#item05
Keith: I heard quite a few OEMs would not get on-board a command API, their concerns is that if you have an API, here are also the parameters on the command, and it gives your IP away from this knowledge, I have been pushed back
Keith: OEMs even described which functions they do not want to be visible
discussion on proprietary vs. non-proprietary model items
Keith: Autosar define their own internal stanfards (for application component APIs) but the architects of the vehicle projects did not use them because they consider it is too much effort
Keith: OEMs love standards for off-the-shelf ECUs and sensors but not for internal work
Gunnar: there is an ability to have private branches in VSS, they could be positioned as VSS Extensions
Gunnar: currently we name everything as VSS, it might be worth thinking about differentiating the naming of the data model and the tooling and the spec langage
Kevin V: IMHO it is a little bit tricky to make a common service API
Gunnar: shows an example of a service catalog from the github repo, we use same words and features as Franca
discussion with Kevin on the service API, for instance the function turnonheater
Kevin V: approach has changed in order to make no assumption on how an OEM intends to implement the control of a function, a signal group is used then for this purpose
Ulf likes the structured way we used

learning about production platforms for connected vehicle services

Philippe: reminds Glenn about
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-125
, our expectation was added as a comment there

Wednesday, June 3 - Communication Framework

Agenda:

Jira review
AOB

Participants

Ulf, Kevin V, Gunnar, Philippe
apologies: Keith,

Minutes

Jira review

Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-72
changed to done
- Glenn has provided the link to the video presenting the Geotab algorithm
- Ulf: the functionality for this algotrithm will be in Gen2
- Gunnar: I will look at this video, I am not sure whether the compression algorithm should be part of Gen2, other statistics like an average could be implemented in a "node", this must be discussed with W3C people
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-156
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-74
changed to done
- Glenn has provided the link to the NTHSA paper on V2X and an additional paper
- Gunnar: will look at it as well
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-157
  created
- note: this ticket is rather a topic for a Monday call
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-4
- Gunnar: the wiki page Data serialization / value formats is now finalized, all subtasks are done, changed to done
- The overall analysis feels quite done now. If the idea of edge-processed / statistical values becomes more refined then there might be a few more subclasses to define those different types of calculations, but we can leave that for later.
- If we want to cover MQTT just for good measure, then this needs a concrete data encoding and that's covered in CCS-143
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-96
&
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-97
- Kevin will add concluding comments to both tickets and close them
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-97
- Ulf added a concluding comment on Daniel Wilms' vision of the data lake design
- Daniel Willms view is that the graphql server should directly access the SQL database, instead of via the HTTP interface that the OVDS server exposes.
- That makes possible more complex queries on the data set than what is possible through the OVDS server interface. I see no problem with exposing both, and let a client choose which to use.
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-158
  created and assigned to Ulf
Jira
server JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-59
changed to in-progress
- Gunnar sent an email to Cloudera
- link added to Sanjeev's work
  Jira
  server JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-124
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-102
comment added
- Gunnar: production in my mind means actual deployment in the industry, in order to manage millions of vehicles, our work is not going to reach production, I tried to capture in this column of the work breakdown structure (and this ticket) which technogoies need to be changed to go to that kind of scale
- Gunnar: we should not talk about a reference version term and use v1,v2,v3,v4 to label the maturity of the implementation
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-70
- Ted: refers to an email sent by Arnand, who is not sure whether we need to look at specific use cases, we should rather be looking at the data points (as required by the European Union for instance)
- looking for business cases is not relevant anymore, ticket changed to done
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-71
- Philippe: will do this review, ticket reassigned
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-159
created
- Philippe: we need to create a ticket to bring elements for a story telling about the use cases
- Ted: next week I will meet with John from Ford and they will talk about the group John is forming within Ford
- Ulf: about the biz cases in the graph project, at Geotab we believe we have to change the solution because we think that OEMs will not agree to share vehicle data in the same repo , Geotab thinks the model has to be revised
- Ulf: we will come back with a proposal on how to explain the biz value of the graph project to the OEMs and other stakeholders in two-week time likely
  - ticket assigned to Ulf for tracking the presentation of this proposal
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-85
- Gunnar: no feedback from the security team although some of them might be aware of this EU work
- Philippe: the list of reviewers who provided comments on the EU document is available here . 3 OEMs did it (VW, Volvo Cars, Tesla and ACEA which represents the European OEMs)
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-125
commented
- Gunnar/Philippe; the same question can be asked both Geotab and High Mobility
- Kevin: it is difficult to relate our CCS work to a commercial platform, this is about how the CCS work could be integrated with a commercial platform
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-129
commented
- Kevin: will descrive the oem cloud resource management
- "In the communication framework we have a distinction between different interfaces from the OEM cloud:
  - Consent Management
  - Authentication Management
  - Resource Management (data access)
  This has been done as a best practice and to follow the Extended Vehicle architecture. However for the PoC it makes to simpify. What is needed is an API component that exposes the GraphQL server externally to Neutral Servers and 3rd parties. This component has to take care of querying the requested data from the OEM cloud database as well."

Monday, June 1 - Communication Framework

First call - Asia friendly time 11:30am CET

Agenda

weekly sync with Sanjeev : other technology option for implementing the framework

Participants

Sanjeev, Gunnar, Philippe

Minutes

Sanjeev has digged into open source componennts like Apache NiFi components and others for implementing the framework using technology options different than the ones currently used for the first version of the proof-of-concept (a.k.a. Gen2). Some of these technologies were used by Cloudera in a demo in an earlier GENIVI AMM in Korea.
Sanjeev's proposal is described in a slide deck attached to
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-124
Gunnar / Philippe: propose Sanjeev to continue in this parallel track while Gunnar will contact Cloudera to see whether some collaboration might be set up with them, look at :
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-59

Monday, May 25 - Communication Framework

Second call only - US friendly time 16:00 CET

Agenda

sync between CCS and AASIG VHAL projects
GraphQL server implementation

Participants

Gerald, Kevin, Gunnar, Philippe
apologies: Ulf

Minutes

Vehicle data simulation

Stefan W and Gunnar had a sync meeting on the vehicle data simulation earlier today, this simulation approach could be used jointly bu the CCS and AASIG projects
Stefan's raw notes
- "Learning from Ulf input: VSS to DB Adapter is “flattening” the vss tree structure to be easly stored in the database. The code is available https://github.com/GENIVI/ccs-w3c-client
- For usecase: querying min, max, avg value of the property – not in scope for graphql queries for Data Server Historical values not needed that is why we do not need to have complex database, unlike CCS more relies on data storage.
- Topic to discuss for tomorrow AASIG call ?: Do we consider relying not only on cached/stored/updated values in database updated periodically by vss feeder or foresee the need of “on demand” requesting the fresh data.
- This 3 ways of accesses are not considered as vss leaves def, but might be specified using VSS Layers. Then VSS feeder/Data Server (discuss on the role) can act accordingly (use cached or request for fresh value).
- To reuse VSS Feeder across CCS and AASIG PoC demos agreed the following: Temporarily descope “on demand request of the fresh data from sensor/ecu): Use sqlite as database for storing vehicle properties, then all three parties could write/read from it in common way (w3cgen2 + Apollo grapqhl + vss-feeder).
- Flat the structure of VSS tree to a unique key in the database (like using a string containing full tree path to leaf as a key).
- Tasks to be added to the backlog: Rework current vss-feeder and Apollo grapqhl resolver to use sqllite to retrieve/store data
- Ulf Bjorkengren I guess similar task needs to be performed on w3cgen2 side as well"

GraphQL generation

Below comments are extracted from
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-96
updated by Kevin
- Client with example queries have been created in Swift: https://github.com/highmobility/vss-graphql-client-swift. Based on this we should see if the VSS GraphQL schema should be modified to simplify 3rd party usage.
- High-Mobility is now waiting for VSS pull request related to Electric Vehicle signals to be reviewed and merged. Then the GraphQL schema can be generated and used for the EV use-case 3rd party service.
Gunnar : it is good to have anoter component to be added to the set of components

NiFi

Sanjeev will look at other ways to transmit data from the cars to the OEM cloud, we have no idea whether it impacts the architecture we have yet

MQTT

Gunnar: MQTT handles only the way you describe the topics and the subscription to those topics , but the payload content is not defined, it is not a major work to do in my opinion
Gunnar: MQTT is popular, should on the list of TODOs for the future
Gunnar: I will write a mapping doc from VSS to MQTT, please add this to the backlog

Monday, May 18 - Client Implementation, Vehicle Data

First call - Asia friendly time 11:30am CET

Agenda

weekly sync with Sanjeev on the client implementation

Participants

Sanjeev, Gunnar, Philippe

Minutes

review of work breakdown structure
Gunnar: Ulf showed his wor at the summit, but we still need a command line implementation
Sanjeev: in my opinion showing 3 different terminals in the demo shown by Ulf is good for the time being, but it was difficult to understand which terminal was showing which component, I want to improve
the user experience
Sanjeev: are you working with Cloudera ?
Gunnar: we talked to Cloudera, it is now time to start discussing with them again
Gunnar: it might be interesting to work with Apache NiFi and al. components
Sanjeev: one proposal could be to connect the CCS demo and OBD II signals retrieved from the Hortonworks demo shown at the GENIVI AMM in Korea
TODO Sanjeev to move forward with this parallel implementation
Sanjeev: I would like also to showcase a server less configuration and Alexa-based queries
Gunnar: I recently identified cool projects to help with the deployment of services (with SSO)
Sanjeev:. Iwill do some planning and propose a workplan until next milestone in July

Second call - US friendly time 16:00 CET

Agenda

virtual tech summit debrief
code sync between Ulf and Gunnar

Participants

Keith, Guru, Ulf, Stephen, Gunnar, Philippe
apologies: Kevin

Minutes

Philippe delivers a short debrief of the virtual tech summit execution
Then Ulf and Gunnar dig into github for a code sync

Thursday, May 14 - Virtual Technical Summit Workshop

minutes are here

Monday, May 11 - Client Implementation & VTS CCS Project Report Review

First call - Asia friendly time 11:30am CET

Agenda

weekly sync with Sanjeev on the client implementation

Participants

Sanjeev reported his progress offline

Minutes

Sanjeev: fixed the crash issue (was related to Gen2 server log implementation) and cleaned up scripts. CLI based test works uninterrupted. Ulf informed him that he will do the demo during the virtual session on Thursday.

Virtual Technical Summit - CCS Project Report Review

Participants

405 attendees registered to the summit

Minutes

CCS project report is here

Wednesday, May 6 - Communication Framework

Agenda:

proof-of-concept implementation status
virtual tech summit - workshop preparation
Jira review
AOB

Participants

Ulf, Gunnar, Philippe
apologies: Keith, Kevin V

Minutes

proof-of-concept implementation status

Ulf: Gen2 crash is solved, it is possible to run the entire VSS tree into Gen2 server and populate the datalake

virtual tech summit - topics for the CCS workshop

each topic will be introduced with a short slidedeck to fuel the discussion
topic #1 - Generation of vehicle data
- Ulf: in the demo, we transport data from the gen2 server to the data lake, but we transport only dummy values, how to integrate something underneath : vehicle simulator or real vehicle data
- Gunnar: one possiiblity is to download a vehicle simulator and "drive a car around" to generate data, how to get people signing for this ?
- intro slide deck owner: Philippe
topic #2 - Technology options for bringing vehicle data into the system
- Gunnar: IMHO we need to investigate other technologies than Gen 2 for bringing vehicle data into the system
- Gunnar: we should think about some use cases and produce some criteria for future decisions
- Gunnar: we will need to scale up the system and measuring its performance, example of options: Web style protocols, coding optimization
- intro slide deck owner: Gunnar
topic #3 - Interface between the datalake and the neutral server and the third parties app
- Ulf: one could discuss what needs to be done above the datalake from "the datalake to the upper left side" of the high-level diagram
- Philippe: we need to realize that this interface is perhaps the easiest to start with analyze for a possible standardization, because the righ side of the high-level diagram (from the vehicle to the OEM cloud) is currently largely based on proprietary solutions
- intro slide deck owner: Kevin V ?
topic #4 - privacy expectations
- Ulf: got some feedback on the terminology like data lake, in a privacy context, data lake has a negative vibe
- Gunnar/Philippe: agreed in particular because we claim we are ISO Extended Vehicle compliant meaning we have "privacy-by-design"
- intro slide deck owner: Gunnar
topic #5: data exchange formats
- Gunnar: since we will likely have attendees that do not follow the day2day work, it is important to disseminate some of the results of our work
- one key opic is the data exchange formats
- slide deck owner: Gunnar

Jira review

Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-79
&
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-80
moved to a new epic
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-104
created
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-105
created
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-83
this work item is related to and needs to sync with the work on W3C Gen2, comment added
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-85
Gunnar sent out the link to European Union privacy guidelines to the GENIVI security team for review, comment added
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-98
is now WIP, Ulf sent an email to Adnan and Daniel

Monday, May 4 - Client Implementation, Vehicle Data

First call - Asia friendly time 11:30am CET

Agenda

weekly sync with Sanjeev on the client implementation

Participants

Sanjeev, Benjamin, Gerald, Gunnar, Philippe
apologies: Ulf

Minutes

Sanjeev: client was committed on github, I have one issue with the Gen2 server that crashes when (too) many requests are sent
Sanjeev: I have other thoughts about the technologies (e.g. NiFi) we could use for implementing the clients, when should I start looking into these ?
Gunnar: we need to get the current implementation you made running first
Gunnar: I do not have root access to the Gen2 server, so I cannot help for the debugging, I would be good to package this component according to the approach used in CCS-arch-demo repository
Sanjeev: I agree it makes sense, I will package everything in a docker container once the crash issue is solved
Sanjeev: explains what he can show as a demo for the upcoming Virtual Tech Summit

Second call - US friendly time 16:00 CET

Agenda

AW webinar

Participants

many attendees (close to 200)

Minutes

Kevin Valdek and Gunnar delivered a Webinar of the CCS project hosted by Automotive World
- presentation is here
- a lof of good questions were asked

Wednesday, April 29 - Communication Framework

Agenda:

proof-of-concept implementation status
AOB

Participants

Ted, Ulf, Keith, Gunnar, Philippe
apologies: Keith, Kevin V

Minutes

proof-of-concept implementation status

Ulf: I helped Sanjeev to install the go build system today
Gunnar: I also had some trouble with the go building
Ulf: next week I should be able to run the client and do a demo
Gunnar: will there be a command line client ?
Ulf: no the client will go through the complete VSS tree and check for changes, it will work as an infinite loop asking for more data from the data lake
Gunnar: IMHO it might be useful to have a command line interface as well
Gunnar: I tried to build the data server and has some issues with the dependencies
discussion with Ulf on how to set up the datalake and populate the database content
we need to double check the MIT licence since we are modifying code for implementing the ccs-w3c-client DONE MIT license is fine

Jira tickets review

browsing through the Sprint board, tickets updated on line

Monday, April 27 - Client Implementation, Vehicle Data

First call - Asia friendly time 11:30am CET

Agenda

weekly sync with Sanjeev on the client implementation

Participants

Sanjeev, Ulf, Gunnar, Philippe

Minutes

discussion on Hortonworks demo on fleet management: which radio stations are best used among a fleet of vehicles ? Sanjeev said it is an impressive demo
discussion on implementation of gen2 server
Gunnar shows the code quality guidelines
update of PoC WBS online

Second call - US friendly time 16:00 CET

Agenda

AW webinar slide deck review

Participants

Ulf, Keith, Kevin Valdek, Guru, Gunnar, Philippe

Minutes

AW webinar slide deck review

Kevin V shares the draft slide deck for the webinar
in-vehicle OS slide (look at the block diagram on top of this page)
- discussion on in-vehicle protocols
- Keith: DDS is also a protocol adopted by AUTOSAR, DDS is an ARA::COM binding as well as SomeIP is, to be added
- ROS is build on top of DDS, ROS and DDS have "topics" and "fields" inside topics
  - look for instance at https://istkb.adlinktech.com/article/overview-dds/
  - other link: https://index.ros.org/doc/ros2/Tutorials/Topics/Understanding-ROS2-Topics/
- discussion on ROS2 (look at https://index.ros.org/doc/ros2/) and open source project autoware (https://www.autoware.org/)
  - autoware is based on ROS
  - look also at https://gitlab.com/autowarefoundation/autoware.ai
  - there is no ROS2 integration in AUTOSAR
  - Apex.ai has joined AUTOSAR as an associate member
    - look at https://www.apex.ai/apex-os
    - apex-os is a rewrite of ROS2 in particular to comply with ISO-26262
utilization of VSS for vehicle data modeling
- Keith: IMHO VSS is a "target" format
- Keith: autoware has its own message definition
  - look at https://gitlab.com/autowarefoundation/autoware.ai/messages/-/tree/master/autoware_msgs/msg
- Keith: since you are promoting VSS as the data modeling language, you have to be prepared to answer a question like how VSS compares to or builds on autoware messages or whatever
slide deck review will continue in an ad-hoc call on Wednesday 29 morning

Wednesday, April 22 - Communication Framework

Agenda:

graphql schema example
PoC design & implementation
Webinar & virtual summit workshop content
projectization in jira
AOB

Participants

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

Minutes

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 Gen2 protocol transfer, but rather in the OEM cloud
Gunnar: The picture does not show it used for the transmission to the cloud but in the vehicle only. The format might be used in the car, or not... but I think it is OK to indicate the idea of this would be there (to support historical values). The format is not fixed yet, it needs to be refined further
Gunnar: the in-vehicle state storage could use SQL but might also not need it (it is a simple key-value if not multiple time stamps are stored).
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

PoC design & implementation

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 to the HL diagram
Gunnar: explains how docker could be used to package each part (SW components) for development help, or maybe for production, e.g. CCS-arch-demo/tree/master/docker/sqlite repository
- shows the OEM-database implementation using SQLite
- shows the test files
- will continue to package the components according to they become available
Gunnar: the next step is to program the create table command for the datalake from Ulf
Ulf: I started implementing the datalake using SQLite
Ulf: I talked to Sanjeev and I will implement a framework around the datalake and expose an API that the client will use to interface with Gen2
Gunnar: what will be the type of API between the vehicle client and the datalake
Ulf: I am actually working on a server that both the client component and the resource management component can use for accessing the datalake, it it written in REST
Gunnar: I am wondering what we will get from having REST APIs between those components, I am wondering whether there could be something simpler
Ulf: IMHO this is simple enough
Gunnar: both Sanjeev and you are working in Go, aren't you ? If one part was done in a typical web language like node.js I could see how a REST interface might be easier to consume. But especially with the same language other communication methods likely exist.
discussion on how to make interfacing simpler
Ulf: we might reconsider this later
Gunnar: it seems to me as some extra work, but we will see it soon then if it is almost done now anyway.

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

Important threads (currently)

C CS Proof-Of-Concept - Work Breakdown Structure

...

Monday, April 20 - Vehicle Data

...

Gunnar: goes through the latest modifications he made and through Ulf's comment at the end of the page
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-91
Gerald: it is a side topic maybe, can we discuss in the future the anonymization of the vehicle ID ? in C2C they provide temporary IDs and change it every 5mn
Gunnar: update the "vehicle identity" definition in the wiki page online
Philippe: what is the status of
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-93
?
Gunnar: in the value measurement formats we have similar concepts as in CVIM and Sensoris, we need to check what maps to what
Ted: Sensoris is part of the Geospace consortium (OGC.3c work), AFAIK Sensoris is not technically aligned (tbc)
Gunnar: Unknown User (benjamin_klotz) can you help us do the mapping between the value measurement formats and the Sensoris spec ? ideally we should share the same names and perhaps the same content
Benjamin: I can do that both for Sensoris and CVIM as well
CCS-93 commented and changed to in-progress
discussion on Gen 2
Gunnar: I am not sure Gen2 needs to integrate the value measurement formats
Ulf: IMHO most of these should be outside of gen2
Gunnar: shows the "Protocol does not (yet) cover all variations of data exchange" bullet point of the section "Relationship to Protocols" of the wiki page
Ulf: however some data structures shown in the value measurement formats should be added to a gen2 client if the client needs historical data (Ulf Bjorkengren please review here and below)
Ulf: my proposal was that if a node supports historical data you can have metadata in the tree
Ulf: we need to discuss this in the Gen2 group
Ted: how does an application register and sign up to use data (this is related in my opinion to the best practice work in W3C ) ?

...

PoC design & implementation - please refer to C CS Proof-Of-Concept - Work Breakdown Structure

Gunnar: suggests Ulf translates the slides he presented last week into a set of SQL instructions
Philippe: IMHO we need to change to a implement and build mindset now
Philippe: we need to think about the minimal demo we will show in one-month time at the virtual tech summit mid-May
Ulf: it would be good to connect the data lake, the vehicle client and the data server (look at the proof-of-concept block diagram)
Philippe: invites Ulf to join the Monday call with Sanjeev
Gunnar: shows the vehicle client implementation VehicleSignalInterfaceImpl he tried out
discussion on the feature set for the mid-May demo
Gunnar: timestamp is enough (please refer to the wiki page Value measurement Data serialization / value formats)
Kevin: do the language or platform we use for the PoC implementation matter ?
Gunnar: my proposal at this stage is that this does not matter, it is easier to do that way

...

Kevin V : explains the comments he made to the wiki page (look at the bottom of the page)
Kevin V: we need such a protocol to be defined, the content of the wiki page is very advanced
Kevin V: sensitivity level - an example of such an attribute is driver's fatigue (high) vs. engine oil level (low)
Gunnar: thanks for your very good feedback
Gunnar: the container is some kind of top level messaging format
Gunnar: I tried to work out a type hierarchy with subtypes
Gunnar: we should think that the content of the wiki page comes down to a generic protocol definition that could be instantiated into several actual protocol specifications
Gunnar: the W3C Gen 2 protocol might not take over all the facets of the generic procotol as it is defined there, but if we can align on some definitions and naming with W3C it would be good
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-81
done
Philippe: did you have a look at the description of formats ?
Ulf: not yet, however since I am very Gen2 centric, I would say the formatting layer lies on top of Gen 2, using Gen 2 as the transport mechanism
discussion continues of the position of the formatting layer in the CCS PoC
quick check on the sprint & backlog
- Philippe: the cross-checking w.r.t. CVIM and Sensoris is to be performed next
- Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-4
  , subtask
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-93
  unanimous consent to reassign this ticket to Benjamin because of his former work on CVIM and Sensoris

...

Gunnar; presents the refinement made on the component interface last week, in CCS Proof-Of-Concept - Reference Architecture - Work Breakdown Structure
Gunnar: we are now collecting proposals for graphql schemas
discussion on impact on Sanjeev's workitems
Sanjeev: in my opinion, we might need someting like an object store for the data lake
Gunnar: Ulf is likely to propose a relational data base
Philippe: Ulf will make a presentation on the data lake in this afternoon CCS call
Sanjeev: is there any reason to use a relational database ? I saw the data coming as a continuous data stream, unless there is a need of classification of data, I am wondering why we should use a database
Gunnar: understood, in the long run, the name data lake means there could be very diverse data and it could make more sense to look into an object oriented database for instance
Sanjeev: I stumbled in similar problems in the IoT domain
Gunnar: we might go to Hadoop in a later version of the proof-of-concept

...

Gunnar: shows the modifications of Value measurement Data serialization / value formats wiki page he made since last Monday call
Keith: remark on VIN number vs MAC address
Gunnar: I use here the VSS defined VIN
Gunnar: details the record types and subtypes
Ulf: do you envision this to be on top of Gen2 ?
Gunnar: this should be on top of every single protocol we want to use
Ulf: agreed, Gen2 is one protocol (the only one for the time being)
Ulf: IMHO this translates partially into subscribe requests on Gen2
Gunnar: yes, the subscribe request is close to what I explained here
Gunnar: my expectation is that all participants this wiki page and check whether the naming of the various items described is appropriate
Ulf: I will look into this,
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-91
created
Kevin: likes it a lot, it is a very comprehensive set of definitions, are these definitions independent of the data models ?
Gunnar: yes
Kevin: CVIM & Sensoris touched this a little bit, job and streams are a litthe bit independent from the other definitions
Ulf: Kevin pointed out a very crucial thing, how do we structure the storage in the cloud VSS tree, we need to complement the values with time dimension & VIN dimension ?
Ulf: it is quite complicated to come up with the best solution
Gunnar: agreed, this is not trivial
Kevin: it is good to define various layers like time series, etc.
Gunnar: we need to analyse how this work can influence the definition of the database schema
Gunnar: any volunteer for the review of this ?
Kevin: I will look at it,
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-92
created
Gunnar: I will look into Sensoris and CVIM afterwards
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-90
created for tracking the update of Value measurement Data serialization / value formats wiki page

communication framework

...

continuation of the review of CCS Proof-Of-Concept Reference Architecture - Work Breakdown Structure, wiki page updated online
component #1 - in-vehicle storage
- the selection of database is perhaps to be shared with AASIG VHAL project
component #2 - in-vehicle VSS2 translation (a.k.a. VSS feeder)
- we need to set up a call asap with Bosch to determine what could be reused from Kuksa project and to discuss the model transformation tools (VSS-to-Franca and Franca-to-ARXML)
- /TODO/ Philippe to contact Bosch (Sebastian and Christian) for setting up the call asap
discussion on the simulator that might be used to feed simulated data in the poc
- Keith: presents shortly the LGE simulator
  - the simulator is based on unify and can be run using ROS and be interfaced with AutoWare (https://www.autoware.org/) and Apollo (https://github.com/ApolloAuto/apollo)
  - the simulator provides driving itineraries corresponding to big chunks of San Francisco
  - the simulator needs to run on a very powerful desktop, it might be appropriate for a CES kind of demo
- Philippe: the LGE simulator could be an option for the milestone #4 of the CCS PoC (demo at CES 2021)
- Gunnar: what do you mean by interfacing Apollo ?
- Keith: you can run Autoware or Apollo to enable the execution of open source ADAS stacks
component #4 - OEM cloud - vehicle client
- there are several options for this implementation
- curl scripts proposed by Gunnar are only a plan C or higher for the implementation, other options are to be analyzed first
short discussion on open source licence
- Keith: would prefer Apache 2.0, MPL 2.0 copyleft is much too strong for the automotive industry (e.g. vsomeip used by Adaptive Autosar demonstrator)
- Gunnar: currently, we are doing our shopping list for the poc based on existing components
- Gunnar: it is only if new components are developed and hosted by GENIVI that the question of the open source licence needs to be analyzed, anyway GENIVI has a list of "green" licences and is not limited to MPL 2.0 if necessary
component #8 - OEM Cloud (Resource Management =) Data server API
- Gunnar emailed Adnan (BMW) and Daniel (BMW) to get some clarity on their GraphQL work
- Philippe: Alex (BMW) showed the work on GraphQL he did for the AASIG EDS PoC yesterday, his work might also help with this

...

Philippe: we need to start thinking about the identification of APIs that could be standardized
Gunnar: we are at a very early stage, i.e. first iteration of the PoC, the identification of APIs will take time and several PoC iterations
Gunnar: I would propose to start a design justification wiki page for the poc where we can capture the rationale for selecting the components (currently the number one criterion is that the component exists)
Philippe: reminds about the following wiki pages Big Picture & Design concerns that might contain some useful inputs
Gunnar: there is this wiki page Vehicle data exchange protocols
Gunnar: I have also created the following wiki page Value measurement Data serialization / value formats, the content was reviewed with Unknown User (benjamin_klotz) during Monday's vehicle data call and then augmented, it would be good you read it
/TODO/ CCS participants to review the wiki page Value measurement Data serialization / value formats
Philippe: next week we need to go through Jira and do a sprint review and we need to kick-start the implementation work

...

discussion starts on the EV data access requirements
- /TODO/ TBD (Benjamin ?) to compare Geotab doc on EV data requirements and the content of the data bundles wiki page
- Philippe: brings clarification on his expectation concerning data categories vs EV data requirements sent by Geotab
discussion continues on the definition of data bundles as described in the wiki page previously named Data Bundles
- Both Gunnar and Benjamin agree to rename the page as Data Categories
Gunnar: in his opinion, it is now important to start looking into the format for message values
Gunnar shows the wiki page Value measurement Data serialization / value formats he drafted
- review of the definition section of this proposal
- Benjamin: agrees with the definition of a signal
- Benjamin: for the record item, he would rather use observation or measurement
- discussion of examples for a record, with timestamp attached and possible additional information
- there is the special use case of streaming where you have a continuous connection: look at the stream item
discussion continues on data format requirements for the different types of signals
wiki page updated online by Gunnar, look at Value measurement Data serialization / value formats

Second call

/TODO/ all CCS participants to review the Geotab document on EV data access requirements
- Philippe reminds this TODO to participants, Kevin will look at Geotab document this week
/TODO/ Rex to review the Adaptive Autosar signal-to-service specifications
- Philippe asks Keith (who knows well the Adaptive Autosar stack) whether he could provide an overview of the signal-to-service specifications to the CCS team
- Keith: will do,
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key CCS-88
  Jira ticket created for tracking
sync on the communication framework
- Keith was able to join today after a long period of overlapping between CCS call and other calls that prevented him from joining
- Kevin: for the sake of synchronizing Keith with the CCS current status of work, Kevin presents the CCS PoC as described in CCS Proof-Of-Concept Reference Architecture - Work Breakdown Structure
- Keith: asks how we can get the gps position of a fleet of cars using the communication infrastructure proposed in the poc
- Kevin V / Philippe: we might have different variants of the poc depending on whether we simulate the vehicle data or we use existing devices like the Geotab Go device if we want to connect to actual cars
- Philippe: for the vehicle simulation, two options have been discussed in the GENIVI AASIG project which is also working on a poc : either using the vehicle simulator published by JLR on GENIVI gitub (genivi-vehicle-simulator repository) or using opends
- Keith: indicates that LGE Labs in the Silicon Valley have also a vehicle simulator
- Philippe: although we will start with laptops as execution targets for the poc, we might switch to automotive boards for the in-vehicle segment of the poc in the future, FYI Renesas has set up a lava-based test farm (with R-Car boards) to build and run the GENIVI CI process, we could use the test farm to simulate the vehicle segment
- Keith: FYI Adaptive Autosar has decommissionned their test farm and runs the CI process on qemu only
- Philippe: invites Keith to the second call of the week which is dedicated to the communication infrastructure

...

Philippe: reminds that it is now time for the team need to pick up some of work items for the CCS PoC implementation,
- link: CCS Proof-Of-Concept Reference Architecture - Work Breakdown Structure
- wiki page updated online by Gunnar. Thanks !
Ulf: I can take over the data server, and its connection to the state storage in the in-vehicle OS box, I am also interested in the data lake
Kevin: we can provide sample applications for the 3rd party service and neutral server marketplace boxes, i.e. entities that will consume graphql apis
Philippe: what about the OEM cloud box ?
Gunnar: we need to determine the signals and the use cases we want to show
Kevin V: we should show different data categories including big data chunks
Kevin V: showing anonymized data is not really possible because this requires a lot of data, it would be better to show different categories
short discussion on the demo use cases
Philippe: explains the use cases selected by the AASIG for the PoC demo (EV data, speed & tyre monitoring and air conditioning
need to add the use cases definition work item
Gerald: I might be able to pull in someone in the in-vehicle OS box , I will ask Sebastian and Christian whether they could recycle something from the kuksa project for the state storage
Gunnar: we need to agree on the format for storing values, e.g. time stamps and values of different types
Gunnar: I would like to get an example of a query for getting multiple snapshots of vehicle data in order to make graphql shine a little bit
Kevin V: if you look at the state of the vehicle, you have a benefit of using a graphql query (get multiple data in one query)
Kevin V: it should also possible to push data with graphql
discussion on the protocols between boxes
Gunnar: I am still waiting for an actual schema for using graphql from someone
Philippe: what about Geotab / Canada ?
Kevin S: I am still chasing what GENIVI is doing, I see myself in a support role rather
review and update of the owner column in the WBS table
Ulf: someone else has to take over the vehicle simulation
Philippe: execution targets will be laptops for the initial implementation
Vehicle client
- vehicle client: Sanjeev's work does not seem to be directly reusable
- Ulf: the client would be repsonsible for stoting the data into the data lake
Data lake
- Gunnar: concenring the data lake, do we have a database person in the call ?
- KevinV not on my side
- Ulf: this is where we should try to get BMW in, it won't be a good idea to invent our own database structure
- Ted: their solution is based on VSS/VSSo too, trying to get Adnan to present what he showed at last W3C F2F
- Gunnar: I talked to Adnan yesterda
OEM cloud
- Gunnar: what the resource management is all about in this box ?
- Kevin V: resource management comes from the extended vehicle ISO standard
- Gunnar: can we replace this naming by "data server apis" in the OEM cloud
- Kevin V: agreed
Neutral Server market
- Kevin V: it is important that we consume data coming the OEM cloud (server) api
Miscellaneous
- Gunnar: I could likely take over the vehicle client and the graphql and data base
Test farm
- Stephen: I checked the use of lava farm for running the CCS poc, do you want to use a RTOS in the in-vehicle OS box or linux ?
- Gunnar: we can plan for this at a later time, The PoC will be linux-based including the in-vehicle OS box
- Philippe: however Renesas could an Adaptive Autosar demonstrator stack in the in-vehicle OS box, this would be good for the demo, it will still be linux-based because the Adaptive Autosar demonstrator is based in RT Linuw

...

communication framework

Gunnar: shows the CCS PoC WBS
Gunnar: aks Sanjeev for clarification on the work he is doing on the so-called clients
Sanjeev: I limited the scope of my work to the W3C demo shceduled un a couple of weeks time
Sanjeev: I implemented http and websocket connections for the Tizen watch, we have now the vehicle dashboard on the watch, the java scripts used in this implementation are quite straitghforward but need to be rewritten for better clarity
Sanjeev the watch code is in the app store, but I intenf to publish the code as well, the web interface is avauable is the daemon folder, the watch interface is pretty much a html interface
Ted: Magnus from Melco set up the Gen2 server instance on MIT cloud host, the app could point to that
Ted: has set up a Gen2 server instance for demo purposes
Ulf: this data server is up and running, it is available but the link to it has not been released yet
Ted: link is https://www.w3.org/auto/wg/wiki/Vss_data
Sanjeev: back to the clients I am developing, I want to separate the library interfaces from the UX
Gunnar: we need to figure out an idea of the demo we want to do, we need to major progress on this actually
Kevin V: there is a lot of different use cases, that could be used to demonstrate the PoC
Gunnar: we can work with simple queries, but it owuld be good to have simple queries moving a lot of data in odrer to learn abour possible bottlenecks in our communication framework proposal
Benjamin: we could reuse what we have introduced in the data bundles
Rex: do you have at Geotab a document listing all the telematics data ?
Glenn: I am not aware of it
/TODO/ TBD (Benjamin ?) to compare Geotab doc on EV data requirements and the content of the data bundles wiki page
Ulf: asks whether Gunnar can present the CCS PoC block diagram in next week's W3C virtual meeting
Gunnar: will do

...

Ulf: informed Ted (W3C) about the work we are planning to do on the CCS PoC and invited him to join the call
Gunnar: introduces briefly the 2 main thrads of activities in the CCS project: vehicle data model and communication infrastructure, then presents the CCS PoC wiki page CCS Proof-Of-Concept Reference Architecture - Work Breakdown Structure
Ted: are you in contact with Graham Smethurs at BMW ?
Philippe: Yes, there is an action item to talk to him
Ted: are the CCS PoC aligned with BMW ?
Gunnar: yes; we are very much aligned on the data server between GENIVI CCS and AASIG projects , and BMW is active in AASIG and promotes graphql there
short discussion about Sanjeev who completed the Gen2 clients on Tizen (for the Samsung watch), Linux, and Android, Sanjeev seems to be looking at graphql as well (TBC)
Philippe: I have an action item to contact Sanjeev that we happen to know very well due to former collaboration on demonstrators
Ted: I talked to John S at Ford recently, Ford is still in the process of making plans concerning the vehicle data APIs
Philippe: @Ted John delivered a talk in the CCS project track at the GENIVI tech summit of Nov 2019 in Troy, USA, slide deck is here
Gunnar & Philippe invite Ted to join the CCS weekly calls
Ted will be added to the CCS mailing list

...

Kevin presents the wiki page containing the WBS
/TODO/ all participants to review the WBS and identify which work item could be taken over
Gunnar shows
Jira
server JIRA
serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
key CCS-11
where he added the list of technogolies that could be used for the PoC
Ulf: regarding the client implementation Sanjeev is doing, Sanjeev will present his work as part of the remote F2F W3C will have at the end of the month, Sanjeev is working on different platforms including an Android app
OEM cloud: Kevin is fine with Hadoop
Glenn: we need to remap the data from different OEMs to a common standard, go back to the data guys and talk to them about the pinpoints
/TODO/ Glenn provide feedback on a possible common standard for next week
/TODO/ Philippe set up a call with Sanjeev and invite him to follow / join the CCS project
Rex: IMHO we could set an Adaptive Autosar stack in the cloud
Philippe: possibly but in my opinion this is for the future, the architecture of the current PoC adresses a mid-term vehicle EE architecture (like the one depicted on slide #4 and marked as "today" of the VAP presentation by Bosch), having an Autosar stack in the cloud corresponfs rather to a future vehicle EE architecture like the one depicted on slide #4 and marked as "smart infrastructure" of the VAP presentation by Bosch

...

Connected Services project charter
- Philippe asks participants to review the project charter and provide comments by next week
- Philippe: asks participants for their inputs on what should be the project deliverables; he suggests a combination of paper work (likely EA (UML) models, text-based specifications) and code (prototype implementation, proof-of-concept), reminds that Gerald presented the list of outputs of the various sprints identified in the workplan he presented at the last AMM (look here)
- Kevin: the text is good, the charter will be useful for sharing with the HM team
- /TODO/ all review the project charter and send comments to Philippe by email by next week
ISO Extended Vehicle update
- Gerald provides a couple of links he got from Bosch After Market colleagues
- link: https://www.figiefa.eu/new-economic-study-vehicles-manufacturers-external-backend-data-access-models-risk-major-cost-burden-to-consumers-and-independent-stakeholders-reaching-e65-billion-in-2030/
- link: https://www.figiefa.eu/wp-content/uploads/Knobloch-Gr%C3%B6hn-OEM-3rd-Party-Telematics-General-Analysis-Report.pdf
  - this link presents the results of an evaluation made by a consulting company about how the data access around ExVe is implemented
- link: https://www.caruso-dataplace.com/wp-content/uploads/2019/06/137%C2%A9THOMAS_BITTERA_CARUSO_HAL2_05062019-copy-2.jpg
- link: https://www.neutralvehicle.com/ (yet another start-up company)
- /TODO/ all review these materials, we will put this at the agenda of next week's call,
  Jira
  server JIRA
  serverId 121ddff2-c571-320f-9e4d-d5b9371533bd
  key VCS-38
  added to the backlog and current sprint
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

...

JOIN/SIGN UP

GET INVOLVED

COLLABORATIVE PROJECTS

HISTORICAL

Events

Industry Events

COVESA Events

Contact Us

Child pages

Page History

Versions Compared

Old Version 170

New Version Current

Key

Current threads

Monday 2021-11-22

Monday 2021-10-25

Monday 2021-08-23

Monday 2021-07-12

Monday 2021-07-05

Monday 2021-06-28

Monday 2021-06-21

Monday 2021-06-14

Monday 2021-06-07

Monday 2021-05-31

Monday 2021-05-24

Monday 2021-05-17

May 10

May 4-7 Virtual AMM - CCS sessions

Monday 2021-04-26

Monday 2021-04-19

Monday 2021-04-12

Monday 2021-03-29

Monday 2021-03-15

Monday 2021-03-08

Monday 2021-03-01

Monday 2021-02-22

Monday 2021-02-15

Monday 2021-02-08

Monday 2021-02-01

Monday 2021-01-25

Wednesday 2021-01-20

Monday 2021-01-18

Monday 2021-01-18

Wednesday 2021-01-13

Monday 2021-01-11

Wednesday 2021-01-06

Monday 2021-01-04

Wednesday 2020-12-16

Monday 2020-12-14

Wednesday 2020-12-9

Monday 2020-12-7

Wednesday 2020-12-2

Monday 2020-11-30

Wednesday 2020-11-25

Monday 2020-11-23

Wednesday 2020-11-11

Monday 2020-11-9

Wednesday 2020-11-4

Monday 2020-11-2

Monday 2020-10-19

Wednesday 2020-10-14

Monday 2020-10-12

Wednesday 2020-10-07

Monday 2020-10-05

Wednesday 2020-09-30

Monday 2020-09-28

Wednesday 2020-09-23

Monday 2020-09-21

Wednesday 2020-09-16

Monday 2020-09-14

Monday 2020-09-06

Wednesday 2020-09-02

Demo Goal

Monday 2020-08-31

Monday, July 27 - Vehicle Data Model, Common Vehicle Interface Initiative

Wednesday, July 22 - Vehicle Data & Communication Framework

Monday, July 20 - Vehicle Data Model, Common Vehicle Interface Initiative

Wednesday, July 15 - Communication Framework

Monday, July 13 - Communication Framework, Vehicle Data Model, Common Vehicle Interface Initiative