Notes

Performance improvements

1. Encoding (Protobuf, Flatbuffer)
2. Configurable selection of data to include in OSI messages
3. Ensure data modeling takes account of performance
4. Separate static and dynamic information from groundTruth. Maybe even discuss "delta encoding" (only send the data that has changed)

Encoding (Protobuf, Flatbuffer)

Performance sufficient for the initial "A public specification, which has been developed by experts in a defined consensus-driven development process and was released by officials that represent a significant share of the industry for which it is targeted, giving the specification the necessary legitimacy to be called a 'Standard'.Standard" use case, i.e. object based modeling

Increased Is the process of imitation of the behavior of a modeled real-world system over time.Simulation complexity will place significantly increased performance requirements on 1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI. This will be due to e.g.: * Quantity or complexity of sensors in Is the process of imitation of the behavior of a modeled real-world system over time.Simulation * Increased resolution of environment model * Increasing additions to the 1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI Is an abstract model that organizes data and how they relate to one another via formal description elements such as entities, attributes, relations and tables.Data Model

Protobuf has problems with encoding/decoding large data quantities and is thus a performance bottleneck. An alternative is Flatbuffer, which is significantly faster for encoding and does not even require decoding in all cases. Its focus is more on efficiency, thus programming complexity is greater. Could be directly supported in addition to Protobuf

Deliverable

This group shall provide a usage guide for the use cases detailed in the project proposal

• encoding recommendations (Protobuf, Flatbuffer, etc.)
• performance pitfalls & recommendations
• interaction between data & transport layer (OSI vs. packaging)
• (content from WP traffic): guidelines on formatting and structuring of messages to support use case 3 (measurement file)

The group should also discuss packaging concepts and provide a recommendation for the next steps (e.g. in a further project)

1) Open Simulation Interface (ASAM Standard); 2) Open Systems InterconnectionOSI should not be a bottleneck in any of the project use cases, each use case thus needs to be evaluated

Tasks

1. Configurable selection of data to include in OSI messages
2. Ensure data modeling takes account of performance
3. Separate static and dynamic information from groundTruth. Maybe even discuss "delta encoding" (only send the data that has changed) (T.Nader)

WP1: Sensor Modeling

WP2: Traffic Participants & Infrastructure

WP 4: Harmonization with OpenX
 

Back to ASAM OSI Project Page