External Data Server Proof-Of-Concept Work Breakdown Structure

0:10-12:15

Vehicle HAL / Vehicle Data Access Track

Work Breakdown Structure for the External Data Server Proof-Of-Concept

• The objective of this session is to develop an initial WBS for implementing the External Data Server.
• The TODOs listed below were added to the EA block-diagram, look at ExternalDataServerPoC-WBS.pptx
• After review and addition of a description of work and definition of done to each TODO, these TODOs will be entered into Jira.
  Vehicle HAL split meeting participants elaborated the WBS below
• TODO Develop an initial WBS for implementing an InternalDataServer (Priority 2) Proof-Of-Concept)

VSS feeder component

• todo finalize permissions layer concept (independent work item)
• todo create a layer concept for the Franca to VSS leaf mapping (model transformation)
• todo design and implement franca service (SomeIP)
• todo implement feeder as PoC
• todo check signal to service translation in Adaptive Autosar
• todo agree on PoC use cases for the implementation
• todo create PoC Someip simulation component to playback agreed use cases
  
  • note: we could consider using an Adaptive Autosar node like what we did for the FARACON demo
  • note: VSS data base could be merged into the VSS feeder
• todo select and implement VSS data storage (e.g. VISS, Geotab W3C PoC implementation)
  
  • look at W3C wiki page on VISS
  • https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=40403466 
  • look at melco: https://github.com/MEAE-GOT

VSS data server component

• todo APP implement authentication to access the data server (eg JWT), e.g. json Web token
  
  • relates to Vehicle Signal Authentication
• todo APP implement access for in-vehicle data, (e.g. App manifest permissions layer concept)
• todo APP implement request/response serialization
  
  • Gunnar: this relates to a communication protocol (so-called binary protocol)
• todo resolve requested data for the APP from the VSS data structure
• todo change/write data values for requested data leaves
  
  • look at https://github.com/w3c/automotive/issues/322
• todo handle the subscription for APPs
• todo write a generator which will handle permissions in the data server
  
  • look at on-going discussion in W3C on the dynamic registry https://www.w3.org/2019/11/W3C_Gen2_dynamic_registry.pdf (Geotab proposal)

Framework Layer / Authentication Service

• todo request APP permissions from package manager
• todo generate access token for the APP including the APP permissions

Application Layer

• todo Implement the APP permissions based on permissions defined/proposed in VSS layers
• todo implement access token request
• todo APP implement request/response serialization for the client
• todo implement the selected use cases