Onboard Data Hub for Vehicle Software Update Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software update management systems for mobile and stationary assets face issues such as prolonged downtime, outdated update data, errors due to incorrect update sequences, and the burden of carrying update data, leading to potential malfunctions and incompatibilities.
Innovation Solution
A system and method where a data hub onboard the asset automatically receives and applies software updates from a remote location, using current and new configuration files and service programs to ensure accurate and efficient updates, reducing downtime and eliminating the need for manual data transport.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If software updates are performed using known systems, then software updates can be applied, but the updates take longer than desired and increase asset downtime
Solution Approach 1:
The system prepares and validates software update data before actual deployment by comparing configuration files (current vs. new) and verifying compatibility. This preliminary action ensures that updates are ready to be applied immediately, reducing both update time and asset downtime while maintaining update integrity.
2Reliability
If software update data is stored at service location, then updates can be performed locally, but update data may become outdated and incompatible with current software versions
Solution Approach 1:
The system implements a feedback mechanism where configuration files (current and new) are compared to verify update compatibility before application. The service entity receives feedback about the current software state and adjusts update deployment accordingly, ensuring update data remains synchronized with the actual software version and preventing outdated or incompatible updates.
3Ease of operation
If service entity determines update sequence and steps, then updates can be customized, but errors may occur causing software malfunction
Solution Approach 1:
The patent introduces an intermediary validation layer that mediates between the service entity's update decisions and the actual software application. This intermediary compares configuration files, verifies compatibility requirements, and validates update sequences before deployment, preventing errors while preserving the service entity's ability to customize update processes.
4Ease of manufacture
If operator uses local computer with update data, then updates can be performed offline, but operator burden increases and confusion may occur
Solution Approach 1:
The system extracts the complex update management functionality from the operator's local computer and relocates it to a centralized service entity. This extraction eliminates the need for operators to manually manage update data locally, reducing their workload and potential for confusion while maintaining offline update capability through automated data retrieval.
Data Source
AI summary
A method includes receiving, at a data hub onboard an asset, a new configuration file, a service program, and a software update of a software application of the asset from a remote location. The data hub includes a current configuration file that indicates a current configuration state of the software application. The new configuration file indicates an updated configuration state of the software application with the software update. The service program includes work instructions for applying the updated configuration state to the software application. The method includes displaying the current configuration file and the new configuration file onboard the asset using the data hub. The method also includes updating the software application with the updated configuration state according to the work instructions of the service program using the data hub.