Triggering Conditions Analysis and Use Case for Validation of ADAS/ADS Functions

TL;DR

This paper analyzes triggering conditions for ADAS/ADS safety validation, proposing a use case to identify potential hazardous scenarios using a mobile Hardware-in-Loop platform to enhance safety assessments.

Contribution

It introduces a novel use case for detecting triggering conditions of ADAS/ADS functions, focusing on collision avoidance safety validation with a custom HiL platform.

Findings

Identification of potential triggering conditions for ADAS/ADS functions

Application of the use case to a collision avoidance system

Enhanced understanding of scenarios leading to system failures

Abstract

Safety in the automotive domain is a well-known topic, which has been in constant development in the past years. The complexity of new systems that add more advanced components in each function has opened new trends that have to be covered from the safety perspective. In this case, not only specifications and requirements have to be covered but also scenarios, which cover all relevant information of the vehicle environment. Many of them are not yet still sufficient defined or considered. In this context, Safety of the Intended Functionality (SOTIF) appears to ensure the system when it might fail because of technological shortcomings or misuses by users. An identification of the plausibly insufficiencies of ADAS/ADS functions has to be done to discover the potential triggering conditions that can lead to these unknown scenarios, which might effect a hazardous behaviour. The main goal of this publication is the definition of an use case to identify these triggering conditions that have been applied to the collision avoidance function implemented in our self-developed mobile Hardware-in-Loop (HiL) platform.