In-Vehicle SOTA Update Range Selection for Verified Module Combinations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software update technologies face challenges in efficiently updating software modules in vehicles while ensuring operational consistency and avoiding interference with vehicle control systems, particularly with increasing software module versions and combinations.
Innovation Solution
An information processing device that determines the update range of software modules based on verified operation combinations and vehicle control considerations, allowing selective or bulk updates to ensure operational integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the software module is activated before the update to resolve version inconsistency, then the version inconsistency is resolved, but the vulnerability in the software module before update is not eliminated and operation after update cannot be guaranteed
Solution Approach 1:
The system performs preliminary actions by creating a backup of the current software module before activation, and pre-verifying the update target software module's compatibility with other software modules. This allows the system to safely activate the module before update while ensuring operation guarantee through the backup and verification processes.
Solution Approach 2:
The system provides a safety cushion by maintaining a backup of the current software module and verifying update compatibility in advance. This cushioning mechanism ensures that even if the update target has vulnerabilities, the system can revert to the backup and guarantees operation consistency through pre-verification of software combinations.
2Reliability
If operation verification is performed on all combinations with other software modules after updating, then operation after update is guaranteed, but the verification time becomes excessively long especially as the number of versions increases
Solution Approach 1:
Instead of performing exhaustive verification on all possible software module combinations, the system performs partial verification only on the update target software module's compatibility with other software modules. This selective verification approach maintains operation guarantee for critical combinations while significantly reducing verification time.
Solution Approach 2:
The verification process is segmented into two parts: (1) comprehensive verification of the update target software module with other software modules, and (2) reliance on previously performed verification for other software modules that haven't changed. This segmentation reduces the verification scope while maintaining reliability.
3Adaptability or versatility
If all software modules are updated to latest versions, then the system has the latest software, but the combination of software modules may not have been verified and operation cannot be guaranteed
Solution Approach 1:
Before updating software modules to latest versions, the system performs preliminary verification to check if the combination of the update target software module and other software modules has been verified. This preliminary action ensures that only verified combinations are updated, maintaining operation guarantee while allowing software currency.
Solution Approach 2:
The system uses feedback from verification results to determine whether to proceed with the update. If the combination has been verified, the update proceeds; if not, the update is postponed. This feedback mechanism balances software currency with operation guarantee.
Data Source
AI summary
An object is to efficiently update some software modules provided in an in-vehicle device by SOTA while guaranteeing an operation of the software modules after the update. An information processing device 100 of an update system 1 is a device for updating an update target software module which is a part of a plurality of software modules provided in an in-vehicle device 110. The information processing device 100 includes a determination unit 101 that determines an update range of a software module in the plurality of software modules. The determination unit 101 determines the update range on the basis of whether or not the combination of the update target software module and other software modules after the update of the update target software module is a combination in which the operation of each software module has been verified.