Redundant Vehicle Software Validation Using Parallel Status Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The constant development of safety-critical software for automated vehicle systems results in high costs and effort for securing and testing new software, as access to old data and records is restricted in closed-loop systems, leading to inefficient validation processes.
Innovation Solution
A method that compares old and new software statuses in parallel using multiple software paths, allowing for detection and storage of deviations during inactive system states, enabling quick reconfiguration to production series status and reducing costs by utilizing existing hardware for online validation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If new software is tested on vehicles with closed-loop systems, then software validation can be performed, but access to old data and records is restricted and costs increase
Solution Approach 1:
The system performs preliminary actions by recording and storing output data from the closed-loop system before software updates are implemented. This creates a repository of historical data that can be reused for validating new software versions, eliminating the need to collect new data each time and ensuring unrestricted access to old data and records for future validation cycles.
2Reliability
If new software is tested on vehicles, then software validation can be performed, but costs and effort increase enormously
Solution Approach 1:
The system merges the validation process with normal system operations by automatically recording output data during regular vehicle operation. This combines data collection, storage, and future validation activities into a unified process, eliminating separate validation trips and reducing the overall costs and effort required for software validation.
Solution Approach 2:
The system creates copies of output data from vehicle operations and stores them for later use. These data copies can be reused multiple times for validating different software versions, eliminating the need to repeatedly collect new data and significantly reducing validation costs across multiple software update cycles.
3Adaptability or versatility
If software is updated in closed-loop systems, then new functionalities can be implemented, but access to historical data is restricted
Solution Approach 1:
The system performs preliminary data preservation by automatically recording and archiving output data before software updates are deployed. This ensures that historical data remains accessible for comparing against new software performance, enabling unrestricted access to historical data even as software functionalities are updated and evolved.
Data Source
AI summary
A method for validating a software status of a vehicle in a system involves testing the software in the vehicle in the system. The system controls the vehicle according to input data and subsequently records output data of the vehicle. In an inactive state of the system, an in each case non-productive, old and new software status are compared in parallel, and by activating the system to an active state, a change to the productive software status takes place.