In-Vehicle Network Configuration Verification for Software Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software updates for in-vehicle devices may fail due to configuration abnormalities in the in-vehicle network, leading to unapplied updates without the user being aware of the issue.
Innovation Solution
A distribution system where a distribution server determines the normal configuration of the in-vehicle network by comparing acquired configuration information from vehicles with stored normal configuration information, and notifies users when the configuration is abnormal, preventing unnecessary software updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If software updates are distributed to vehicles without checking in-vehicle network configuration, then update distribution speed is improved, but update reliability deteriorates due to configuration abnormalities causing update failures
Solution Approach 1:
The distribution server performs preliminary configuration verification by comparing the vehicle's in-vehicle network configuration against stored normal configuration information before distributing update data. This preliminary check ensures that updates are only sent to vehicles with compatible configurations, preventing update failures while maintaining efficient distribution processes.
2Reliability
If configuration verification is performed before software updates, then update reliability is improved, but system complexity increases due to additional verification processes
Solution Approach 1:
The distribution server stores copies of normal configuration information templates that represent valid in-vehicle network configurations. Instead of implementing complex real-time validation logic, the server simply compares the vehicle's configuration against these pre-stored templates, significantly reducing system complexity while maintaining high update reliability.
Solution Approach 2:
The patent introduces configuration information as an intermediary element between the update distribution system and the vehicle's in-vehicle network. This intermediary layer abstracts the complexity of configuration validation, allowing the distribution server to verify compatibility without directly interfacing with complex network protocols or device configurations.
3Productivity
If update data is sent to vehicles with abnormal configurations, then distribution efficiency is improved, but loss of time increases due to failed updates requiring re-attempts
Solution Approach 1:
The system implements a feedback mechanism where the distribution server receives configuration information from vehicles, verifies compatibility against stored templates, and uses this feedback to determine whether to proceed with update distribution. This feedback loop prevents wasted time on incompatible vehicles by filtering them out before update attempts, thereby maintaining high distribution efficiency while minimizing time loss.
Data Source
AI summary
A distribution system includes a vehicle that includes an in-vehicle network configured by in-vehicle devices, and a distribution server that distributes update data of software for the in-vehicle devices to the vehicle. Updating the software with the update data is performed on a condition that a configuration of the in-vehicle network is normal. The distribution server includes a processor and a storage unit that stores normal configuration information that indicates a normal configuration of the in-vehicle network. The vehicle transmits configuration information on the in-vehicle network to the distribution server. The processor notifies, when the configuration of the in-vehicle network is determined not to be normal, a user of the vehicle that the configuration of the in-vehicle network is not normal.