Vehicle Application Testing via External Simulation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for testing updated vehicle applications, especially safety-critical ones, face challenges due to the unavailability of test vehicles or lengthy conventional test series, which can lead to unforeseen malfunctions and increased development costs, particularly when updates need to be implemented quickly or wirelessly.

Innovation Solution

A method where input and output data from vehicles running the current application version are collected via a wireless link and used to simulate and test the updated application on a vehicle-external computing system, allowing for real-time or parallel execution and comparison with the current version's output data to evaluate and adapt the update according to predefined criteria.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional test vehicles or test benches are used for testing updated applications, then testing can be performed, but test vehicles are not available or not in sufficient quantity, and test series take too long

Engineering Contradiction:
Improvetesting reliabilityVSAvoidtest duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates virtual copies of test vehicles through simulation models that replicate the behavior and characteristics of physical test vehicles. These virtual models allow testing to proceed without requiring actual test vehicles, thus resolving the availability constraint while maintaining testing reliability.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent replaces the mechanical physical testing system with a computational simulation system. By substituting physical test vehicles and manual test series with automated simulation models executed on computing systems, the method eliminates the time-consuming nature of conventional testing while preserving reliability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If thorough testing is performed on test benches or test vehicles, then application behavior can be verified, but a great amount of time and high development costs are necessary

Engineering Contradiction:
Improveapplication behavior verificationVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary testing actions by executing simulation models before actual deployment. The simulation models are prepared in advance and can be executed repeatedly with different input scenarios, allowing thorough verification of application behavior without incurring the time and cost penalties of physical testing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

By creating virtual replicas of the application environment through simulation models, the patent enables comprehensive behavior verification at a fraction of the time and cost required for physical testing. These copies allow exhaustive testing scenarios to be explored without real-world constraints.

Inventive Principle:
Principle #26Copying

3Reliability

If conventional test series are conducted, then safety-critical updates can be tested, but unknown errors may have a fatal effect and updates cannot be released in time

Engineering Contradiction:
Improvesafety-critical update reliabilityVSAvoidupdate release speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent replaces slow conventional testing mechanisms with high-speed computational simulations. This substitution maintains safety-critical verification capabilities while enabling rapid iteration and faster release cycles, as simulations can be executed and evaluated much quicker than physical testing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The simulation models perform preliminary safety verification before deployment, identifying potential errors early in the development process. This preliminary action prevents fatal errors from reaching production while maintaining rapid update capabilities.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If test vehicles are used for updating applications, then testing can be performed, but test vehicles are not available or not in sufficient quantity

Engineering Contradiction:
Improvetesting capabilityVSAvoidtesting availability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The simulation models serve multiple testing functions simultaneously, replacing the need for dedicated test vehicles. A single simulation infrastructure can test multiple applications and scenarios, providing universal testing capability that is not constrained by the limited availability of physical test vehicles.

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

Solution Approach 2:

By creating virtual copies of testing environments, the patent makes testing capability universally available without being limited by physical vehicle availability. These digital replicas can be instantiated and executed on demand, providing unlimited testing access.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11853747B2Method for testing an application for vehicles
Publication Date: 2023.12.26 ROBERT BOSCH GMBH
  • US11853747B2 patent drawing
  • US11853747B2 patent drawing

AI summary

A method for testing an updated version of an application for vehicles. In the method, input data for the application, which are used for a present version of the application on at least one vehicle, and output data of the present version of the application are received by a vehicle-external computing system, from the at least one vehicle via a wireless data link. The updated version of the application is executed on the vehicle-external computing system using the received input data. Output data of the updated version of the application are compared with the received output data of the present version of the application. An evaluation of the updated version of the application being carried out, based on the comparison.