Non-Reactive Validation Environment for Automated Driving

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for validating automated driving functions and other automated technical systems struggle to detect rare events in real operation, requiring a large number of vehicles and extensive mileage, which is inefficient and resource-intensive.

Innovation Solution

A method for non-reactive validation of function applications involves executing the function in a host system within an encapsulated environment, using a unidirectional interface to send data for validation to a remote computing system, thereby isolating the function application from the control program and allowing for real-time testing without influencing the control program.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional system tests and endurance tests using a dedicated vehicle test fleet are used, then known situations can be detected and made safe, but a much higher number of vehicles and corresponding mileage are required to detect rare events in real operation

Engineering Contradiction:
Improvedetection of rare eventsVSAvoidnumber of vehicles and mileage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The validation system is segmented into multiple independent validation instances distributed across a fleet of vehicles. Each vehicle independently executes validation functions and reports results to a central validation server, allowing parallel collection of validation data from many sources simultaneously, thus detecting rare events without requiring a single dedicated test fleet

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The validation functions are designed to be universal and reusable across different vehicle types and operating conditions. The same validation functions can be deployed to validate control programs in various real-world scenarios, making the validation system adaptable to diverse situations without requiring specialized test vehicles

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If the function application is executed as part of the control program, then function data can influence control functions, but the function application may influence the control program and possibly lead to errors in the control of the device

Engineering Contradiction:
Improvefunction data influence on control functionsVSAvoidcontrol program stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The validation function is extracted from the control program and executed independently in a separate validation environment. The validation function receives input data through a unidirectional interface and outputs validation results without being able to modify or influence the control program, thus eliminating the risk of control program corruption while still allowing function data to be processed

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

A unidirectional interface acts as an intermediary between the validation function and the control program. This interface allows data to flow from the control program to the validation function but prevents any feedback or influence from the validation function back to the control program, ensuring control program stability while enabling functional validation

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If simulations are used for validation, then resource consumption is reduced, but a much larger number of situations can arise in real operation and be taken into account in the validation

Engineering Contradiction:
Improveresource consumptionVSAvoidnumber of situations tested
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The validation system utilizes the vehicle's own operational data and real-world operating conditions to perform validation, rather than requiring separate test facilities or extensive simulation resources. The validation function processes actual sensor data and control signals from the vehicle during normal operation, enabling comprehensive real-world validation without additional resource overhead

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The validation function is merged with the vehicle's existing operational systems and executes concurrently with normal vehicle operations. By combining validation activities with regular vehicle usage, the system achieves both simulation efficiency and real-world scenario coverage without requiring separate dedicated test resources

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20250036544A1Method for non-reactive validation of a function application
Publication Date: 2025.01.30 ROBERT BOSCH GMBH
  • US20250036544A1 patent drawing
  • US20250036544A1 patent drawing

AI summary

A method for non-reactive validation of a function application for a host system that has host system resources and is configured to execute a control program to implement control functions of a device. The method includes: providing an environment in the host system, to which are assigned certain environment resources of the host system resources that computer programs executed in the environment are permitted to have at most; sending data present in the host system outside the environment, into the environment via a unidirectional interface; executing the function application in the environment to determine validation function data based on the data sent into the environment; determining validation data including function data and/or data derived from function data; sending the validation data to a remote computing system via a data communication interface of the host system.