...

Introduction

The COVESA Logical Architecture shows the Data Expert Group scope as being the large ECUs and above.

Image Added

From the perspective of a DIKW Pyramid hierarchy we have:

1. Data Layer - native (raw) vehicle board-net data carried on vehicle buses such as CAN, LIN, FlexRay, Some/IP and DDS.
2. Information Layer - data in the VSS data-model abstracted from the data layer, along with data from other domains such as personal data.
3. Knowledge Layer - insights and wisdom derived from the Information Layer.

The Architecture and Infrastructure pillar is currently concentrating on data-centric architectures, with an emphasis on the needs of the Information and Knowledge layers in-vehicle, mobile devices and the cloud. For example, in the Information Layer that means technologies (software) providing data services for serving, storing and synchronizing data in VSS and other data-models, the group is any technologies (software) involved in the transfer and use of the Covesa standard data and services description models with the goal of making their adoption quicker and easier. That can be achieved through collaboration on specifications, design patterns, non-differentiating technology and PoCs to prove they work.

For more details see the The 2022 Autumn AMM Data Expert Group Introduction:

Building on earlier work

The Genivi Cloud & Connected Services (CCS) project investigated the requirements of open data capture in-vehicle and its connection to back-end systems in the cloud. One of the deliverables was this well known cloud reference architecture diagram:

Image Removed

Source: CCS Reference Architecture - Work Breakdown Structure

CCS was followed by the Common Vehicle Interface Initiative (CVII) Tech Stack project which investigated the software required to transfer and process the standard VSS data model. For that a mutual understanding of terms and common components were required. The latter resulted in this in-vehicle architecture diagram, which is intended to show the likely in-vehicle components and how they interact, rather than specify a specific monolithic architecture:

Image Removed

Image Added

Projects

Information on the current projects, such as the Central Data Service Playground, can be found in the project listThese two diagrams, the CCS Cloud reference architecture and the CVII Tech Stack in-vehicle architecture will be foundational building blocks for discussion of evolved versions in the Data Architecture and Infrastructure team.

Communication

To avoid multiple sources of information please refer to the Data Expert Group main page for details of the community calendar and communication channels.

...

In Slack we use the data expert group channel. Hope to see you there.

The current Data-Architecture pillar lead is Stephen Lawrence (Renesas).

Sub-pages

Related earlier work (Cloud and Connected Services, CVII Tech Stack)

The Genivi Cloud & Connected Services (CCS) project investigated the requirements of open data capture in-vehicle and its connection to back-end systems in the cloud. One of the deliverables was this well known cloud reference architecture diagram:

Image Added

Source: CCS Reference Architecture - Work Breakdown Structure

CCS was followed by the Common Vehicle Interface Initiative (CVII) Tech Stack project which investigated the software required to transfer and process the standard VSS data model. For that a mutual understanding of terms and common components were required. The latter resulted in this in-vehicle architecture diagram, which is intended to show the likely in-vehicle components and how they interact, rather than specify a specific monolithic architecture:

Image Added

These two diagrams, the CCS Cloud reference architecture and the CVII Tech Stack in-vehicle architecture will be foundational building blocks for discussion of evolved versions in the Data Architecture and Infrastructure team.