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
  • Towards CVII pluggable components

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Tech Stack overview 

B) What, in your view, are acceptable choices (and preferred choices)
 for programming languages and runtimes:
  - In-cloud
  - In-vehicle

Today's ECUsNext-stage ECUs (domain controllers, central computers)Cloud (computers not in-vehicle)Development tools, code-generators, converters etc.

"Vehicle cloud computing"

(think about next-next gen)






Javascript / NodeJS


.NET, C#, ...

Haskell, Erlang, ...

C) In existing architecture pictures (e.g. CCS), and framework implementations (e.g. iot-event-analytics/vehicle-edge/KUKSA.val, AOS) which interfaces:

  - are documented ?
  - need to be documented ?
  - do NOT need to be documented (= internal / implementation detail) ?

Inspiration from these architecture pictures and other pages:

Completion of technology definition / implementation
Component NameProgramming language / runtimeRequired/consumed interfacesProvided Interfaces
Kuksa.VAL:PythonUses various bindings, socketCAN, ...
VISS-like interface also for writing data into KUKSA?
VISS protocol(?)
VSS Feeder (multiple)
= StateStorage db interfacedepends on input type (CAN, etc.)
State StorageSQLite database-SQL
OVDS Client (ccs client)
GoVISS protocol
OVDS Server
Go= StateStorage db interface

(CCS): LiveSim
GoData in OVDS Database format
WAII:Service ManagerGo(internal)(internal)
WAII:Server CoreGo(internal)(internal)
WAII:AGTGo-(internal)  HTTP?
WAII:ATGo-(internal)  HTTP?
WAII:MQTTGo(internal, VISS-like communication)-
WAII:WebSocketGo(internal, VISS-like communication)-
WAII:HTTPGo(internal, VISS-like communication)-
OVDS DatabaseSQLite.  Probably should be production-level time series database