Page History

...

Value measurement formats

Wednesday,  April 8 - Communication Framework

Agenda:

• value measurement formats - review
• PoC design
  
  • formatting layer
  • authentication
• graphql schema example
• AOB

Participants

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

Minutes

value measurement formats - review

• 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

    , unanimous consent to reassign this ticket to Benjamin because on his former work on CVIM and Sensoris

formatting layer in the proof-of-concept

• Ulf: the formatting layer is not visible in the vehicle, if the Gen 2 client sits in the cloud,  this will sit on top of the client

• Ulf: Gen 2 is agnostic w.r.t. where the client is deployed, the client could be in the vehicle or the cloud, in the CCS PoC the client is in the cloud

• Ulf: I ambition this formatting layer to sit in the cloud in the CCS PoC

• Ulf: concerning jobs, there could be specific jobs where you have some particular logic to implement (TBC likely not captured accurately, Ulf Bjorkengren please check)

• Ted: I also see a gen2 client app residing on vehicle and *pushing* data samples to the cloud, I see more of push than a pull, this is an equally viable architecture

• Ulf: agreed, design choice might depend on the data (transmission) cost (TBC likely not captured accurately, Ulf Bjorkengren please check)

• Gunnar: for the push scenario, will that be using the set function ?

• Ted: I would rahter use the subscribe function (TBC likely not captured accurately, Gunnar Andersson please check)

• discussion on how to use Gen2

• Gunnar: I try to determine if we can solve the use case with the current Gen2 or with an extension of it, set might not be appropriate today

  • @Ulf: you are driving the strategy for feature growth in Gen2, would you propose the support of time series in Gen2 ?

  • Ulf: yes, I would, it is relevant but perhaps not as an integrated part of Gen2, my view is that it should be outside Gen2

• Ted: for the push scenario, look at https://www.w3.org/XML/EXI/,  this technique can work for both XML and JSON, this technique is used for the management of large data distribution (e.g. for a fleet of vehicles)

authentication in the proof-of-concept

• 
  

  
  

  Keith: I have a question about the authentication,  we did not discussed this yet

• Keith:  we need to discuss how to update the authentication info, I have in mind the use case of the service garage

• Gunnar: we need to check whether the proposed architecture should be enhanced to take into account the service garage use case

• Gunnar: this has to do actually with the role-based protocol discussed in W3C; in W3C it is assumed currently that the access to data is granted based on a role

• Gunnar: in W3C work, by transport protocol we think at something like TLS, you have a certificate checked in TLS to certify you are accessing a certified OEM cloud

• Keith: it might be worth documenting the assumptions

• /TODO/ Gunnar to update 

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

  accordingly, DONE

  
  

graphql schema example

• Kevin V: we are working on it
• Philippe: AASIG VHAL team is about to publish an example of a graphql schema

AOB

• WATCH OUT: next Monday 12 April is CANCELLED due to Easter break

Monday,  April 6 - Client Implementation, Vehicle Data

...