Cross-channel object referencing with ASAM OSI and ASAM OpenLABEL

Cross-channel object referencing with ASAM OSI and ASAM OpenLABEL

Proposal Workshop

on: Thursday, Aug 27, 2026 | 10:00 am - 12:00 pm CEST

via: Microsoft Teams

The new MCAP-based multi-channel trace Is a description about how information is encoded and structured and given a specific syntax for storage in a computer file.File Format of ASAM 1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI offers the possibility to capture multiple streams of 1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI messages for various purposes, like re-Is the process of imitation of the behavior of a modeled real-world system over time.Simulation, The process of determining that a system performs and meets the needs for identified end users.Validation, etc. Due to its nature, the format also offers the possibility to store additional, non-1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI channels and meta-data alongside the 1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI channels.

This presents the opportunity to store labeling data alongside the ASAM 1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI raw data, which can be useful for The process of determining that a system performs and meets the needs for identified end users.Validation purposes, as well as searching and locating suitable traces for further processing.

ASAM OpenLABEL provides one potential way of storing labeling data, however currently there exist no conventions for storing this kind of data, nor are there clearly defined cross-referencing conventions, that would allow this kind of labeling to work.

The project proposes to address this situation with the following steps:

• Creation of a clear identification and location convention for ASAM OSI trace file data across channels.
• Creation of a clear convention of how labeling data channels can be stored alongside ASAM OSI data channels, how their relationship can be specified and how the identification convention is to be used to create the relevant cross-channel linking.
• Providing a proof-of-concept implementation of these mechanisms using a suitable metadata / labeling format - potentially based on ASAM OpenLABEL, or a relevant extension proposal - based on asam-osi-utilities and/or osi-python / osi-cpp.
• Providing a fully worked out example demonstrating the new capabilities in a best-practice style guidance.

As part of the project a look at the current capabilities of ASAM OpenLABEL to tag .1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI trace data will be taken, which can lead to improvement/extension proposals for a future ASAM OpenLABEL revision (currently ASAM OpenLABEL only supports scenario tagging and multi-sensor data stream labeling, neither of which are likely to fully fit the ASAM 1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI use case).

Register                            Project proposal