Outline

• Intro
  • Why?
    • Covesa needs:
      • Repeated use of shared terminology, patterns and tools leads to quicker understanding in discussions, shared costs in development and can lead to quicker outcomes.
        • Jump from 'what is the box' to 'how are we using the box'
      • A neutral playground is needed to investigate internals of such services. In the context of data-centric architectures for example.
      • A neutral playground is needed to investigate, illustrate and disseminate combining such services with other parts of the vehicle.
    • Why Central Data Service?
      • Patterns such as view/controller, out of the box data servers, application stores etc are well known. It can in part be defined by what's not known. More clearly what is identified as open questions, in next-gen architectures such as data-centric architectures, that needs to be tackled down.
      • A repeating pattern of discussion in the Data Architecture pillar is the combination of VSS Data Server and VSS Data Store and their connection southbound to feeders/native data and northbound to clients and off-board. Hence Data Service.
      • VSS is a mechanism of abstraction. The logical architecture for the Data Expert Group and VSS places operation in the zonal ECUs and above. Discussion of next-gen and data-centric architectures suggests investigation into data services in zone, domain and HPC controller scenarios and the cooperation between them. Hence Central.
    • Why playground? Why not PoC?
      • A PoC is often a snapshot in time and often specific in scope.
      • Playground suggests greater flexibility. The central service, the lego, is intended to be flexible and evolving. Similarly with what it is combined with to illustrate Covesa concepts and technology.
  • What?
  • How?
  • Success factors
• Logical concepts
  • Central Data Service
    • 
       
  • Service in context
    • Zone/domain/HPC controller sync (system)
      • Logical architecture for VSS - zonal ECU and above:
      • Inter-controller sync/cooperation:
    • Southbound: feeders, Autosar etc.
    • Northbound: clients, mobile, cloud, in-vehicle Android/Apple, etc.
    • Logical: knowledge layer
• Implementation concepts
  • Initial idea/sketch
    • VISS Data Server with VSS Data Store backend
      • Add Apache IotDB (Apache eco-system, embedded and UDF) and Realm (embedded, sync) as backends