Page History

...

Value measurement formats

Wednesday,  June 3 - Communication Framework

Agenda:

• Jira review
• AOB

Participants

• Ulf, Kevin V, Gunnar, Philippe

• apologies: Keith, Kevin V

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

  • Gunnar: will analyze to put the Geotab algorithm at work, we need to analyze the way we design and implement the in-vehicle data processing

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

    created

• 
  

  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 Value measurement 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

...