Page tree
Skip to end of metadata
Go to start of metadata

Implementation roadmap

  • milestone 1 - Spring GENIVI Virtual Tech Summit (12-14 May)
  • milestone 2 - internal milestone (early Q3 - 17 July)
  • milestone 3 - Fall All Member Meeting (Virtual) 26-30 October
  • milestone 4 - January 2021 – (originally planned for CES, now general milestone)

Communication framework architecture

This page lists the different components and tasks to be completed for the architecture discussed on the Vehicle data exchange protocols page. The table references to the following diagram, with components that are considered in scope for the PoC highlighted with green color.





StateStorage and VSSFeeder is expected to be combined into one component in the implementation.

SignalStoreIF : Done by reading/writing sqlite database transactions, and using the notification feature to notify components that update occurred.
StateStorage:   Essentially implemented by sqlite instance
SignalFeedIF:    This is an internal implementation detail now since StateStorage/VSSFeeder is essentially one program

                    OEM Cloud 

ValueStoreIF:   ?
ValueQueryIF:  ?

Interface details

(OEM Cloud) GraphQLDatabaseIF:   (Interface between VSS2-Database ↔ Resource Mgmt (GraphQL server)

The interface is expected to be accessing the database itself.  In order to give the GraphQL server full freedom to query data intelligently, it should connect directly to the SQL database.

Description of work

Apache License is more preferred by participants.

#ComponentPlan / ActivitiesStatus of chosen software components
(Implementation details of PoC)
Alt. SW components / Implementation for Production Systems
(star) (WIP, future)
State storage
(laptop simulator)
  • Custom code + in-memory database (+ persistence) + connection to feeder
  • Either locally cached during uptime of system or
  • Stored and indexed in a database to allow access to historical data
    • Selection of database
    • Implementation of database schema

CCS-106 - Getting issue details... STATUS

  • Custom control code (Python or C++)
  • + sqlite binding, OK for PoC

→ (tick) Implemented by a shared sqlite database file.  The "API" is simply interacting with the database using SQL statements and/or sqlite bindings.

Note: statestorage executable in a one-shot thing that sets up the database.  The gen2-server accesses the actual database directly using sqlite binding.

CCS-107 - Getting issue details... STATUS

  • Custom code

CCS-108 - Getting issue details... STATUS


CCS-109 - Getting issue details... STATUS



VSS2 translation (a.k.a. VSS feeder)
(laptop simulator)

  • Implementation of SOME/IP client?
  • or simple simulator
  • or Vehicle Driving Simulator (LG?  OpenDS? or GENIVI GitHub version?)
    • = set up simulator, make it drive around track, get list of available signals, write code to convert signals to VSS...
    • Signals are fed over DDS to AutoWare or Apollo autonomous driving stacks.
    • Sim needs a high-end graphics machine
  • Look if VSI or VSD should play a part
  • New: live_simulator which is feeding a real-time playback of existing timestamped data.

CCS-110 - Getting issue details... STATUS

  • (tick)  live-simulator implemented by Ulf feeds data taken from an existing "ovds" database and feeds it into statestorage.
  • Example ovds database to feed live simulator now exists.

Additional options:

  • Custom code, feeding simple simulated data
  • Then (future) run full vehicle driving simulator

→  continue driving-simulator track
and "playback" simulator in parallel.

CCS-111 - Getting issue details... STATUS

not assigned

CCS-112 - Getting issue details... STATUS



Data Package

  • Collecting VSS2 data into snapshots and bundles according to Value measurement formats
  • Presenting data packages to the Data server
  • Possibly closely related to the State storage schema

CCS-113 - Getting issue details... STATUS

Protocol defined within the CCS project.  Start with results of Apache NiFi track
to fulfil this need.
(error) No recent progress

CCS-114 - Getting issue details... STATUS

Future development. No support currently to transfer a Data Package in W3C Gen2

CCS-115 - Getting issue details... STATUS



Data server
(laptop simulator)

  • Data server implementation for W3C Gen2
    • Reference implementation exists in GitHub MEAE-GOT
    • Ulf can work together with someone how to connect to an existing API of "state storage"
    • (also talk to Kuksa project - VISS+REST server)

CCS-116 - Getting issue details... STATUS

Use server directory from W3C_VehicleSignalInterfaceImpl

CCS-117 - Getting issue details... STATUS

Gen2 implementation now uses ovds.db file. 
(tick) On-demand requests are fetched from database.
Timed subscriptions are also supported, i.e. send updates at regular intervals.

(warning) There is not yet implementation of a trigger to the gen 2 server from the database when a new value is written (SQLite supports trigger in theory).


CCS-154 - Getting issue details... STATUS


OEM Cloud

Vehicle client

  • W3C Gen2 protocol (VISS Websocket Pub/Sub)
  • Options:
    • Sanjeev involved in writing the client using Go-lang.
    • Curl script
    • Custom code + HTTP library (e.g. written in python) custom code + libcurl binding
    • Client directory from MEAE-GOT/W3C ?
    • No clear answer.  Depends on use-case.  What is the rate of data for example?
    • Sanjeev: It would make sense to write also client in Go.
  • This program shall also store the data into the data lake program (or directly into the database used as data lake)

CCS-118 - Getting issue details... STATUS

Written in Go, some similar code as in W3C Gen 2 reference server

CCS-119 - Getting issue details... STATUS

(tick)  Demo includes this function already..  In ccs-client repo.
Client reads data from data server in vehicle via the VISSv2 protocol, and writes it into the OVDS database.

(warning) Vehicle client current does get-requests on a timer (polling) but could in the future also exercize the subscription feature in the protocol.

CCS-120 - Getting issue details... STATUS


OEM Cloud

VSS2 database

  • Selection of libraries and database
    • Define database schema → Start with Ulf's proposal for DB schema

CCS-121 - Getting issue details... STATUS

Postgres was discussed.
Use SQLite first.

Currently the translation path to UUID is currently in a separate database, compared to the signal database.  A future possibility is two tables in a single database, making it possible to use SQL JOIN statements.

  • Custom control code (Python or C++) → implemented in Go.
  • + Sqlite binding, OK for PoC, or other database such as postgresql.

CCS-122 - Getting issue details... STATUS

(tick) Implemented in In ccs-client repo.
This is the OVDS server.
It exposes a REST protocol that is used by the client, which may be easier since it is a single operation and not having to look into both databases.  (See JOIN idea on the left for alternative).  
REST protocol can also deliver full time series.

(question) Should we split up the software into more logical repositories?

In production more likely to be an object store database instead of a RDBS.

Sanjeev looking at Apache ecosystem and Hortonworks/Cloudera platform capabilities.

CCS-124 - Getting issue details... STATUS


CCS-125 - Getting issue details... STATUS


OEM Cloud

Identity management

  • Implementation of end-user login and authentication using OpenID
    • Lots of candidates.  Responsible implementer should propose a good alternative.

CCS-126 - Getting issue details... STATUS

(error) TODO
Later. programming language preference could be influenced by the programmer


OEM Cloud

Access management

  • Implementation of authorization between end-user and 3rd party application or Neutral Server using OAuth2

CCS-127 - Getting issue details... STATUS

(error) TODO

Later. programming language preference could be influenced by the programmer


OEM Cloud

Resource Management
 = Data server API

  • Implementation of basic API management
  • Resource Mgmt is the ExVe naming.
  • Implementation of a GraphQL API using the VSS2 schema 
  • Interface to the client, is of course defined by GraphQL+schema.
  • Interface to database (GraphQLDatabaseIF) is described above

CCS-128 - Getting issue details... STATUS

GraphQL → Apache Apollo?

CCS-129 - Getting issue details... STATUS

Located in vss-graphql repo

  • (tick) Has one schema.
  • (error) Does not have tool to regenerate schema => (green star) Manually done for now by Kevin/High Mobility.
  • (tick) Has Apollo server in docker

    TODO(error) Needs to implement the connection from GraphQL (Apollo) to database.
    It could use the REST protocol of the OVDS server,
    or directly SQLite database.
  • ^^ Important to fix!!! ^^

(Alexander Domin)

CCS-130 - Getting issue details... STATUS

JIRA TODO:  Implement the connection between GraphQL and OVDS database.


Neutral Server

Data Marketplace

  • Separate instance that consumes the OEM Cloud OAuth2 and GraphQL APIs
    • We could implement a very simplistic neutral server using the published API of High Mobility, but an open implementation.
    • Security, consent and other complicates things.   Leave those details out.

CCS-131 - Getting issue details... STATUS

CCS-132 - Getting issue details... STATUS

In vss-graphql-client-swift repository

(tick) Has programming framework/example (in SWIFT) to access data via graphql.

  • This could show a way for 3rd party applications to access the OEM/GraphQL interface directly but possibly a more limited REST-API is more realistic for 3rd part app access

(blue star) TODO: Expose a neutral-server API to third party applications.

Nothing in particular to develop →  It would just be a proxy (for the GraphQL and/or REST) – same technologies as our current OEM connection would be used by the Neutral Server.

113rd Party Application
  • Example applications exist on High Mobility's GitHub
  • One instance that consumes the Neutral Server/Data Marketplace APIs
    • Use an example application from HM
    • For example an app that just shows the data (written in Node.js)
  • One instance that consumes the OEM Cloud OAuth2 and GraphQL APIs
    • Modify the application to use the OEM API directly

CCS-133 - Getting issue details... STATUS

CCS-134 - Getting issue details... STATUS

(tick)  New sample app
Connecting directly to OEM cloud for now, via GraphQL.

For connecting to Neutral server instead:

(blue star)  Example/standard API work needed. The example apps are using High Mobility's API.  → See above

(blue star) Need discussion/definition of what the open API should be.

The API would be quite transparent if VSS is exposed directly, but the Neutral Server API might expose different functions also. (question)

But enriched functions / anonymized aggregated data might be provided by Neutral Server.

→ See above

  • No labels