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.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Session Proposals

This is for Technical Session Presentation Proposals. 

Proposed Topic/Session Title

Abstract

Requested Duration

Requested Day

Proposed By

Comments

Extending VSS To Commercial Vehicles

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 special equipment like cranes and liftgates


Erik Jaegervall 

Possibly joint sesssion Ulf Bjorkengren  and Erik Jaegervall 

HIM or Overlays? depends

VSS in AGL

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




Sebastian Schildt 


Introduction to VSS

Are we doing this year?

I think we should, as still "newbies" are coming in. I can volunteer



Sebastian Schildt 


VSS Format and Tooling




Erik Jaegervall 

Parts of general VSS working session

VSS Collaboration/Competitor landscape




Erik Jaegervall 


COVESA repositories (i.e. not only VSS) as open source components

  • 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


Erik Jaegervall 


New features proposal for next version of VISSv2

New features are proposed for the development of the next version of VISSv2.30-45
Ulf Bjorkengren Interface Pillar
VISSv2 consent model explained and demoedThe newly added consent support in VISSv2 is explained, and a demo is jointly presented by Ford and Aiden Automotive Technologies.60

Ulf Bjorkengren

Aiden: Niclas/Sinan 

Architecture Pillar

Feeder domain conversion explained and demoed

The design and implementation of the mapping and scaling process of data transitioning between a northbound “VSS domain” and a southbound “Vehicle domain” is presented, together with a demo where it is used to actuate signals on a Ford vehicle.60

Ulf Bjorkengren 

Cem Mengi, Ford

Architecture Pillar
Introduction to the Central Data Service PlaygroundTo follow soon30-45

Stephen Lawrence on behalf of the Data Architecture group


Technical overview of the Central Data Service PlaygroundTo follow soon30-45

Stephen Lawrence on behalf of the Data Architecture group


Using the Central Data Service PlaygroundTo follow soon30-60

Stephen Lawrence on behalf of the Data Architecture group


CV PoCLimited, visualizeable PoC from CV use cases

Ted Guild Sven

Thomas Sprechley

Include Wally and RP1226?
CV coordination

RP1226, VDV, FMS

Cloud, in-vehicle port, in-vehicle API



Thomas Sprechley Ted Guild 
Android Infotainment quality analysis by end-user behavior modeling and vehicle data

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



Emil Dautovic Tero Aaltonen 


Android & VISS 

To be added



Emil Dautovic 

Presentation will also include OEM participation
Data Acquisition beyond VSS

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.

30–45

James Hunt 


Data Middleware enabling offline-first Telemetry Collection and real-time decision making with an in-car knowledge layer.

To be added

30-45

Christian Muehlbauer Arnaldo Vera Humza Akhtar 

Possibly joint sessionChristian Muehlbauer   and Arnaldo Vera 

In-vehicle data storage and data sharing in case of cloud disconnection.

To be added

30-45

Arnaldo Vera Humza Akhtar 


A Framework Approach to Standardizing Consent Management in Software-Defined Vehicles

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.

30

Philippe Le Berre, 360 of Me


In-Vehicle API (joining forces with AUTOSAR)

The in-vehicle API 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.



Dr. Henkel, Director in Systems Engineering & Technical Strategy Mobility  (BOSCH)


Wallet for in-car payment with self souvereign identities (SSI)

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.




Peter Busch,  Product Owner DLT Mobility


—

  • No labels

Privacy Policy | Cookie Policy