JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
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. |
Note: Another planning page with restricted access exists at Internal planning page for COVESA AMM April 2023 - Technical
Session Proposals
| Proposed Topic/Session Title | Abstract | Requested Duration | Requested Day | Proposed By | Comments |
|---|---|---|---|---|---|
| BMW & MongoDB VSS-based Data Middleware PoC - Tiered Sync | 30 min | Arnaldo Vera | |||
| OTA updates with Realm | 30 min | ||||
| Workshop the creation and publishing of technical documentation that supports scaling and adoption of Covesa strategic vision. Be it design patterns, data architecture, cookbooks and howtos. | TBD | Design Pattern / Data Architecture documentation proposal | |||
| HIM and an interface using it | The Hierarchical Information Model (HIM) is an evolution of the COVESA Vehicle Signal Specification (VSS) that adds the ability to have multiple trees representing different domains, and representing different types of information. Besides the information type “resource data” that is what is represented by the VSS tree, HIM also supports “service data” where microservices represented by procedures with input and output parameters can be defined. Analogously to VSS, the HIM model does not specify an interface that exposes this information, it leaves this to separate interface specifications. One candidate for this is an evolution of the W3C Vehicle Interface Signal Specification version 2 (VISSv2), that in its current version uses VSS for modelling the data. It is the presenter’s view that this interface can with small modifications be extended to use HIM instead of VSS. This would provide a single interface that can be used to access both information types, that will possibly also be standardized in W3C. The presentation will give the presenter’s view on how this extension could look like. | 60 min | |||
Vehicle data server southbound architecture | An architecture is described where the southbound side of a vehicle data server utilizes a data store and a feeder to realize the interaction with the underlying vehicle subsystem. | 45-60 min | |||
Overview
Content Tools