In this blog, we will delve into the advancements in the automotive industry, specifically focusing on the revolutionary OpenScenario 2.0 (OSC 2.0) framework. We will explore how the integration of Advanced Driver Assistance Systems (ADAS) can effectively prevent accidents at junctions. Additionally, we will emphasize the importance of coverage and Key Performance Indicators (KPIs) in this context, highlighting their role in ensuring safety and measuring the effectiveness of ADAS features. “I firmly believe that comprehensive coverage in ADAS testing is essential for creating a safer future on our roads.” – John Davis, CEO of Automotive Technologies Inc.

Understanding the Importance of Junction Testing with OSC 2.0

Junctions pose unique challenges due to their complex traffic patterns, multiple points of convergence, and varying right-of-way rules. These factors increase the potential for accidents and require ADAS systems to accurately detect and respond to vehicles, pedestrians, and potential hazards. ADAS features such as front collision warning(FCW), automatic emergency braking (AEB), and blind-spot detection (BSD) are crucial in improving safety at junctions. Testing these features with realistic scenarios is essential to ensure their effectiveness and minimize the risk of accidents. It is difficult and expensive to recreate all such scenarios for testing with a real vehicle. Simulating such scenarios and testing the junction control software features offers a more viable solution. The question then is, how does one reliably replicate real-life scenarios in a simulation? It turns out that OpenScenario 2.0 (OSC 2.0), a powerful open-source scenario creation language (ASAM standard), is the answer. OSC 2.0 provides a versatile platform to create complex junction scenarios, with support for various parameters such as vehicle behaviors, traffic patterns, weather conditions, etc. 

ASAM standards are a set of guidelines designed for automotive electronics, software, and data technologies, aiming to enable seamless communication and compatibility between different systems and tools utilized in the automotive sector.

Testing ADAS Features on Junctions with OSC 2.0, Cover,  and KPIs

In this scenario, an Autonomous vehicle(AV) and a Non-Participant vehicle(NPC) approach the junction in a straight direction. 

Both vehicles’ paths intersect at the junction, creating a potential collision risk. This scenario is ideal to test an ADAS feature like an Autonomous Emergency Braking system Straight Cross Path (AEB SCP). The feature detects approaching vehicles or objects in the AV’s path with sensors, such as cameras and radar.  If the system finds out that a collision is imminent and the driver does not respond or apply sufficient braking force, it automatically activates the emergency braking system. This helps to prevent or mitigate the impact of a potential collision by reducing the vehicle’s speed or bringing it to a complete stop. 

Creating such a scenario becomes very intuitive with OSC 2.0. The language, which is curated to represent ADAS scenarios, enables coding an abstract description of the scenario. This abstract description can then be parameterized to include all possible variables that might affect the performance of the AEB SCP feature. A test automation engine then reads the OSC 2.0 scenario description to create concrete parameter values and then orchestrates the simulation of the feature in a vehicle simulator. This enables closed-loop testing of the braking with various positions and speeds assumed for the NPC and the AV.

Leveraging Cover, and KPIs:

Cover and KPIs are crucial elements in evaluating the effectiveness of ADAS features. Cover assesses the coverage of critical situations and potential accident scenarios, while KPIs provide measurable metrics to evaluate the performance of ADAS systems. By integrating cover and KPIs into junction testing using OSC 2.0, engineers can ensure comprehensive evaluation and optimization of ADAS features.

Integration of Cover and KPIs:

Integrating cover, and KPIs into junction testing provides a comprehensive assessment of ADAS feature effectiveness. Cover, checks ensure that critical situations and potential accident scenarios are adequately covered, while KPIs provide quantifiable metrics to evaluate the performance of ADAS systems, such as the accuracy of detection, the time it takes to respond, and the ability to make decisions.

For example, here in the scenario, coverage and KPI can be as follows:

Coverages:

1. The relative distance in the longitudinal and lateral directions at the approaching junction
2. The relative distance in the longitudinal and lateral directions at the junction
3. The speed of AV and NPC at approaching junction
4. The speed of AV and NPC at the junction

KPIs:

AEB SCP Activation Scope: This refers to the range of conditions and scenarios in which the AEB SCP system is activated to prevent collisions. It includes specific criteria and triggers that initiate the system’s engagement.

1. AEB SCP Deceleration Range: This pertains to the behavior of the AEB SCP system in terms of deceleration. It encompasses the range of deceleration values that the system can apply and the conditions under which it adjusts the vehicle’s speed to avoid a collision.

2. AEB SCP Warning Criteria: This encompasses the warning behavior of the AEB SCP system. It specifies the specific conditions and scenarios in which the system provides warnings to the driver, alerting them of a potential collision and prompting them to take appropriate action.

3. AEB SCP Steering Intervention Scope: This refers to the range of steering inputs and behavior of the AEB SCP system. It outlines the conditions under which the system may intervene to adjust the vehicle’s steering to avoid a collision.

4. AEB SCP Collision Avoidance Capability: This encompasses the capabilities of the AEB SCP system in successfully avoiding collisions. It specifies the specific scenarios and conditions in which the system effectively prevents collisions, ensuring the safety of the vehicle and its occupants.

In conclusion, testing ADAS features on junctions using OpenScenario 2.0, cover, and KPIs is the key to unlocking enhanced safety and effectiveness in these systems. With the ability to simulate realistic scenarios and incorporate cover and KPIs, engineers can evaluate performance and optimize the functionality of ADAS features, preventing accidents at junctions. OSC 2.0 offers a robust platform for creating complex junction scenarios and analyzing ADAS performance, enabling targeted improvements and optimization. Through rigorous testing, ADAS systems can be refined to provide reliable, efficient, and life-saving functionality in real-world driving conditions. By harnessing the capabilities of OSC 2.0, automotive manufacturers and researchers can elevate ADAS safety, paving the way for safer roads for everyone. Stay tuned for the next blog, where we will delve into the art of writing coverage and KPIs in OSC 2.0. Prepare to uncover the secrets behind maximizing the potential of ADAS systems.