VSS has historically focused on passenger cars. This session intends to discuss various options for extending VSS to better support commercial vehicles, including

• Adding new signals to standard VSS signal catalog
• Adding an "official" VSS overlay for commercil vehicles
• Private/OEM-specific overlays
• Using HIM to specify additional independent trees for for trucks, trailers, etc.
• Q & A

HIM or Overlays? depends

Need to discuss with Automotive Grade Linux  guys, but they did have a fancy VSS based demo and they have some tech information about that. They might come or give me slides.

The interesting thing is, that on the one hand it is a bit more of an end2end use case, but at the same time freely available

Taking the next steps with your understanding of VSS.  Learn from the pros as they walk through some how-tos.  Get your questions answered and learn how to get involved.

• Our current approach concerning governance, OSS scans, IP scans, headers/footers
• Our current approach concerning license (like MPL vs Apache)
• Discussion – what is needed to simplify inclusion/usage in downstream/proprietary projects. Implications of AI, CoPilot and so on
• I.e. is there any artifacts or files that members needs

RP1226, VDV, FMS

Cloud, in-vehicle port, in-vehicle API

How to find those tricky AOSP system issues as e.g. memory leaks during an infotainment project

-Developing an Open Standardized gRPC-enabled VISS API towards Android Automotive OS

-Enables securely sharing subset vehicle sensor data towards service providers

-Smartification/Smart sensing using VISS Curve logging

-RemotiveLabs virtual sensor platform as VSS data provider

VSS is a good starting for data collection, but that is only the start.  Flexible data collection requires much more.  The talk with outline additional areas of collaboration in COVESA to support vehicle-to-cloud dynamic data management.

This talk explores three aspects of automotive data architecture:

• To recap of bi-directional sync in the Porto and Detroit projects for seamless offline data exchange.
• To introduce uni-directional data collection's role in analytics and machine learning.
• To explain the in-car knowledge layer for real-time decision making, with practical industry examples.

Beyond traditional in-vehicle data transfer and storage, unique user experiences can be unlocked with a robust data middleware.
In this technical talk, we will explore the different architectural patterns, challenges and ways of implementing in-vehicle data transfer and storage with MongoDB's Edge Server. As well as how VSS is implemented and some peep into the future of embedded databases.

As the automotive industry evolves, the concept of the software-defined vehicle (SDV) has emerged as a pivotal innovation, offering unparalleled flexibility, customization, and new functionalities. However, this evolution introduces complex challenges in consent management. The requirement for accurate consented data, the complexity of user consent interfaces, and the need for interoperability among diverse systems and jurisdictions calls for a standardized framework to not only ensure privacy but also security. This presentation proposes an approach for developing a framework for consent management.

The in-vehicle API is based in the COVESA VSS and is linking the Open-Source-Software to the AUTOSAR-technology. The API is shown as standardized “OpenAPI.V3”-specification including error messages. A first implementation shows, how to create a REST-API with Swagger and to “read/write”-vehicle signals from the KUKSA-server.

Future Car2X services rely heavily on secure and efficient identity verification and data management. The Vehicle Signal Specification (VSS) may be used with payment options combined with Self Sovereign Identity (SSI) to configure the vehicle based on a driver ID stored in a digital vehicle wallet.

Topic/Abstract: 

• VSOMEIP and VSS

• Limits of VSS
• Previous attempts for expressivity
• An API-first approach to generically model data of vehicle properties
• Decoupling logical and physical layers.
• Integration of domains.

• A call for participation
• Using COVESA artifacts to enable a professional benchmark for the decision-making tasks on data streams. Including, but not limited to:
  • Data stream processing
  • Complex event processing
  • Stream Reasoning

The Accord released in 2023 is equipped with an AAOS-based IVI system.

Honda has implemented in-house software development for the first time with this model and will introduce a wide range of topics from the establishment of the organization to the customization points of AAOS.

45 min

(30min + Q&A)