COVESA Getting Started

COVESA Community Calendar - Weekly Meeting Schedule

COVESA Communication Channels (Slack, Mailing Lists, Calendar)

COVESA Github Repository

Project Launch Process

Request Wiki Account


COVESA Briefing/Overview Deck


Data Expert Group
▶︎ Best Practices
     ▷ Governance
     ▷ Privacy and Identity
     ▷ Data Model Definition
     ▷ API First
▶︎ Data Models and Ontologies
     ▷ Vehicle Signal Specification (VSS)
     ▷ Vehicle Signal Specification Ontology (VSSo) - W3C Collaboration
▶︎ Architecture and Infrastructure
▶︎ Interface Definition
     ▷ Vehicle API
     ▷ Vehicle Service Catalog (VSC)
     ▷ Vehicle Information Service Specification (VISS) - W3C Collaboration
Data Expert Group Workshop 2023Q1

Electric Vehicle Charging Expert Group
▶︎ EV Charging Event Data Aggregation Project
▶︎ EV Optimization - Increase Travel Range for Fixed Battery

Android™ Automotive SIG
▶︎ Android Automotive White Label App Store

Security Team

Simulation and Tooling

Vehicle Experience and Content - Entertainment BoF
▶︎ In-vehicle Payment SIG


Common Vehicle Interface Initiative

Cloud & Connected Services Project

SDV Telemetry Project - On Hold


Industry Events

Industry Events 2023


October 2022 All Member Meeting

April 2022 All Member Meeting

October 2021 All Member Meeting

May 2021 All Member Meeting

October 2020 All Member Meeting

May 2020 Virtual Technical Summit

November 2019 Technical Summit

May 2019 All Member Meeting

Contact Us

Child pages
  • Collaboration Project: eSync

We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.

Skip to end of metadata
Go to start of metadata

COVESA has a liaison agreement with eSync Alliance to explore common interests.

eSync Alliance is an initiative to define Over The Air updates (OTA/SOTA) and Disgnostics.

A presentation LINK PENDING of the activities was made at the Automotive Linux Summit in Tokyo, December 2021.


eSync is interested in leveraging the use of their OTA protocol not only for software transfer (cloud to vehicle) but also data transfer (primarily vehicle to cloud). 
It was early on decided that the work within CVII to achieve an automotive industry-common data model, and use of VSS in particular, was desirable for such work.

Protocol Specification

eSync develops and publishes OTA protocol specifications among their members.  (Contact eSync for further details.)

Technical Prototype

The potential of a technical prototype has been discussed.  Outreach ongoing to companies that may be interested in implementing. 

Message Formats

Some of eSync technology leverages Apache frameworks and uses AVRO encoding  and therefore we envision trying that in the technical prototype.

Therefore a specification and implementation of AVRO encoding for VSS-signal data is one choice listed in the CVII Tech Stack components planning (in combination with protobuf, JSON and other choices).

A set of message definition schemas, and prototype code in python have been proposed on a separate branch of vss-tools named serialization, and it follows this generic proposal of data-protocol message types.

Smaller value-container messages can be bundled and there are definitions of such bundles (TimeSeries, etc.) and these definitions can thereby be a definition of a data bulk storage.

Prototype design

   <design diagram pending>

Components for development

  • (question) Convenience-library for data encoding.  (VSS values in, AVRO-encoded data messages out).  (C++)
  • eSync has in-vehicle components that the prototype might be aligned with (e.g. modify AVRO schema to fit VSS but the code gets reused).
  • Raw CAN-signals are often used.  CAN→VSS is a frequent topic, also listed in the planning/organization of CVII.

Hardware environment

  • Raspberry Pi is preferred for evaluation  (embedded system)

  • No labels