Page History

Data Expert Group Update 

Erik Jaegervall

VSS with OpenAPI

Adnan Bekan 

Title:  Alternative to Push Notifications  Working Session

The AOSP App Framework Standardization Expert Group Statuswill continue their assessment of alternatives to Push Notifications including UnifiedPush. 

@Jose Freitas Melina Mascolo Richard Fernandes Camille GhibaudoMelina Mascolo  Camille Ghibaudo Richard Fernandes 

EV Charging Event Data Aggregation Project Workshop

360 Degree Overview of EV Alliances and Initiatives (US+EU)- How it fits together.  Why Vehicle Signal Specification Matters.

Matus Banyay

DDS and Data-Centric Communications

Overview of DDS (Data Distribution Service), its applicability to VSS, and how data-centric communications can enable interoperable ecosystems of tools and components with vast scalability; an opportunity for COVESA

Neil Puthuff 

Integrate VSS with Automotive Systems: Aligning Data Collection with Business Requirements

VSS provides a good basis for modeling and naming sensor and actuator data in a vehicle.  The work to standardize CAN signal descriptions and integrating AUTOSAR signals into VSS is quite useful.  AUTOSAR could even benefit from the VSS naming scheme.   On the other Hand, VSS does not cover how data should be transmitted or which data should be collected when.  These are not data modeling tasks and should be handled separately.  In fact, data acquisition should be dynamically changeable to address changing business goals.  The talk will present how this could be done and what would be advantageous for future COVESA activities.

James Hunt 

Commercial Vehicle Birds of a Feather 

Ted Guild Unknown User (tom.spreckley)

EV Power Optimization Prototype Walkthrough

Umang Sharma Unknown User (dirk.slama@bosch.com) Chris Cheng Pradeep Kumar 

OTA Updates with Realm

Arnaldo Vera 

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.

Ulf Bjorkengren