You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »


Implementation details are collected here  ← @alexander.domin start here.


Filling instructions

Please add your name in the "Owner" column for the task(s) you would like to take over and add comments in the last colum if any.

For the task(s) you selected, please add a short description and a definition of done

Thanks for your cooperation in making the PoC happen

1

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

  • The TODOs listed below were added to the EA block-diagram, look at ExternalDataServerPoC-WBS.pptx
  • After addition of a description of work and definition of done to each TODO, these TODOs will be entered into Jira.
OwnerComment
2

VSS feeder component

  • todo finalize permissions layer concept (independent work item)
    • description TBD
    • definition of done TBD
Stefan WysockiSee vss-feeder repository
3
  • todo create a layer concept for the Franca to VSS leaf mapping (model transformation)


4
  • todo design and implement franca service (SomeIP)


5
  • todo implement feeder as PoC


6
  • todo check signal to service translation in Adaptive Autosar


7
  • todo agree on PoC use cases for the implementation


8
  • 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


9
  • Select and implement feeder input API → how feeder writes data into the "shared database"
  • Either it is writing directly into the database (shared with the VSS data server component) or writing into an API provided by the VSS data server. 


10

VSS data server component



11
  • Implement the connection between the access protocol (GraphQL) and the fetching/writing of data into the database.


12
  • APP implement request/response serialization
    • Gunnar: this is probably defined by the communication protocol (defined by GraphQL)


13Define GraphQL schema - what does it look like?  – Alexander Domin will deliverAlex.See vss-graphql repository
14
  • todo resolve requested data for the APP from the VSS data structure
  • ==> This means:  Implement the resolvers function in GraphQL
    Depends on choosing the database implementation first.


15
  • todo change/write data values for requested data leaves
    • ==> Same as implementation of 14, but for writing.
    • This means:  Implement Mutation functions in GraphQL


16
  • todo handle the subscription for APPs
  • => Implement Subscriptions (according to GraphQL)


17

18

Define the "signal groups" that make up each permission and give each permission a name.

  • Example permission group created by Alexander (in .md file), similar to the layers discussion.  Alexander found it easiest to do Signal→Group mapping
    (this fits the VSS layer principle exactly.) but also to have the opposite view (Group→ Signals) generated by tooling (for human readability)
  • vss.permission.xxx (as proposed in VSS layers) was a nice convention, but let's confirm that we are aligned with Google standards on permission names.


19

Framework Layer / Authentication Service

  • todo request APP permissions from package manager
    • description TBD
    • definition of done TBD

Stefan Wysocki
(TietoEVRY)

Will update the description and DoD for this component
20
  • todo generate access token for the APP including the APP permissions

Stefan Wysocki
(TietoEVRY)

Implementation of the module deployed on the platform. Buildable by Android buildystem (Android.bp)
21

Application Layer

  1. Implement EV charging status App in Android, with a graphical UI
  2. Implement Position/speed/make/model/ any other info, as received from driving simulator (could be simple UI, maybe text).


22TODO:  Define what signals we can get from simulator, and try the simulator (Tieto)Tieto?
23
  • Implement the APP permissions based on permissions defined/proposed in VSS layers
    • description TBD
    • definition of done TBD


24
  • Implement authentication as required by the concept 
    including access token request, etc.

Stefan Wysocki
(TietoEVRY)

Will be provided as a part of "Authentication Service" to showcase the exposed API
25
  • APP implement request/response serialization for the client
    As above, this is likely defined by GraphQL.  Refer to the result of line 12


26
  • implement the selected use cases



Support / Infrastructure

  1. Testing
    1. Stephen Lawrence I can contribute to the effort to integrate the PoC into the Genivi LAVA Automated testing if the group decides to use it.
  2. Integration
    1. Stephen Lawrence : I would be happy to provide best effort support for integration on R-Car h/w where needed.
  • No labels