Versions Compared

Old Version 342

changes.mady.by.user Gunnar Andersson

Saved on

compared with

New Version 343

changes.mady.by.user Gunnar Andersson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

...

  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-167
    ,
    Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-143
    • discussion on Benjamin's review comments (look at file attached to the ticket)

  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-53

    • Gunnar: shows the addition made to Value measurement 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

...

  • Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-156
       

  • Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-157
      created

    • note: this ticket is rather a topic for a Monday call

  • Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-4

    • Gunnar: the wiki page Value measurement 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
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-96
     &
    Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-97

    • Kevin will add concluding comments to both tickets and close them

  • Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-158
      created and assigned to Ulf
  • Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-59
    changed to in-progress
    • Gunnar sent an email to Cloudera
    • link added to Sanjeev's work
      Jira
      serverJIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-124
  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-71

    • Philippe: will do this review, ticket reassigned

  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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."

...

  • Gunnar: goes through the latest modifications he made and through Ulf's comment at the end of the page
    • Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-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
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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 ) ?

...

  • 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
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-4
      , subtask
      Jira
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-93
      unanimous consent to reassign this ticket to Benjamin because of his former work on CVIM and Sensoris (smile)

...

  • 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
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-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
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-92
    created

  • Gunnar: I will look into Sensoris and CVIM afterwards

  • Jira
    serverJIRA
    serverId121ddff2-c571-320f-9e4d-d5b9371533bd
    keyCCS-90
    created for tracking the update of Value measurement Data serialization / value formats wiki page

communication framework

...

  • 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

  • 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
      serverJIRA
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyCCS-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 - 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

...

  • 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
  • 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
        serverJIRA
        serverId121ddff2-c571-320f-9e4d-d5b9371533bd
        keyVCS-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

...