Vehicle Controller Software Update Clearance Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software updates for vehicle controllers can lead to errors, causing vehicles to become inoperable and requiring costly on-site or workshop repairs, resulting in immobilization.
Innovation Solution
A method to ascertain drive clearance after a software update by determining deviations in controller states using cryptographic hash values and controller classifications, allowing for limited drive clearance if necessary, thereby preventing immobilization and ensuring safety.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software updates are performed on vehicle controllers, then the vehicle can receive functional improvements and bug fixes, but the vehicle may become inoperable due to update errors
Solution Approach 1:
The system performs preliminary verification by comparing the actual software state against the target state before allowing vehicle operation. Hash values of the software are calculated and verified in advance to ensure integrity, preventing erroneous software from causing vehicle malfunction.
Solution Approach 2:
The system continuously monitors the software state of controllers and provides feedback by comparing actual hash values with target hash values. This feedback mechanism enables the system to detect deviations and respond appropriately by restricting or permitting vehicle operation based on software integrity.
2Reliability
If the vehicle is immobilized to ensure safety after software updates, then vehicle safety is improved, but the customer loses access to the vehicle requiring costly repairs
Solution Approach 1:
The system applies different operational permissions to different controllers based on their individual software verification results. Controllers with verified correct software allow normal operation, while controllers with erroneous software trigger specific restrictions. This localized approach allows the vehicle to remain partially operational rather than completely immobilized.
Solution Approach 2:
The system implements partial immobilization by restricting only the functions associated with controllers that have software errors, while allowing other functions to operate normally. This partial action approach maintains sufficient vehicle availability for safe operation while preventing damage from faulty controllers.
3Measurement precision
If comprehensive software verification is performed for all controllers, then software integrity is ensured, but the complexity of the verification system increases
Solution Approach 1:
The system uses cryptographic hash values as simplified copies or representations of the complete software state. Instead of verifying the entire software code directly, the system calculates and compares hash values, which are compact digital fingerprints that uniquely represent the software state, greatly simplifying the verification process.
Solution Approach 2:
The verification system is divided into independent modules that handle individual controllers separately. Each controller's software state is verified independently through its own hash calculation and comparison process. This segmentation allows the system to scale to multiple controllers without proportionally increasing overall system complexity.
Data Source
AI summary
A method ascertains a drive clearance after a software update for a set of controllers of a vehicle. The method includes determining a first deviation between the first target state and the first actual state of the software updated. If the first deviation indicates, then a second deviation between the second target state of the set of second target states and the second actual state of the set of second actual states for a first controller is determined. The first controller is linked to a class from a specified controller classification, and one or more properties of controllers are linked to each class of the specified controller classes. If a second deviation indicates, and if a property of the ascertained class of the first controller indicates that the first controller can be downgraded, then the first controller is downgraded after the software update.