...

The logical architecture for VSS and the Data Expert Group is places the typical scope as Zonal ECUs and above as shown in the following diagram:

...

The service will integrate southbound to connections to data fSouthbound: connections to feeders, lower parts of the vehicle and its native data, through data feeders and connectors. This will include making connections to other systems such as Autosar etc.

Northbound

...

connections will be made to clients, mobile, cloud

...

and major in-vehicle domains such as IVI running Android/Apple

...

etc.

...

Connections may also be made to other logical data domains. For example, to provide data layer services to the knowledge generating concepts as suggested in the knowledge layer proposal made in the Data Architecture Group.

Implementation Concepts

• Address two high level implementation needs, keeping in mind a path towards production where possible:
  1. Easy to develop: make it easy to build, modify and trial by providing an instance running on a host, e.g. using Docker container(s).
  2. Closer to production: the same base code should be deployable on automotive hardware (or its simulation), e.g. Yocto, container orchestration, SOA etc.
• Initial idea/sketch for base building block
  
  • Generic code: VISS Data Server with VSS Data Store backend
    • Data Architecture requirements: Add Apache IotDB (Apache eco-system, embedded and UDF) and Realm (embedded, sync) as backends to enable research.
  • Deployment 1 (assumed first target): x86 host Docker containers
  • Deployment 2 (assumed second target): ARM64 using common automotive deployment, e.g. Yocto Linux.
• Investigation sketches:
  • Data Architecture and Infrastructure pillar
    
    • Sync
      • Multi-instance of deployment 1/2
    • Logical
      • knowledge layer proposal
        • e.g. sync up/down between knowledge generator and data layer
    • Data Service Internals (e.g. server, store connections)
      
      • Latency
      • Medium and high speed data
      • etc.
  • Touchpoints, common deployment scenarios, scenarios created by other Covesa groups etc.