Courier Device for Vehicular Software Update Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Vehicular computing devices face challenges in reliable network connectivity due to their mobile nature, and updates can be disruptive to both the devices and the vehicles they are installed in.
Innovation Solution
The use of an intermediary courier device that can access networks not directly available to vehicular computing devices, combined with methods to minimize disruption during updates, such as scheduling installations based on vehicle state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If vehicular computing devices directly connect to networks for updates, then network access is straightforward, but connection reliability deteriorates due to mobile nature
Solution Approach 1:
The patent introduces a courier device as an intermediary between the update server and vehicular computing devices. The courier device receives updates from the server and stores them locally, then transfers them to vehicles when connected. This mediator approach resolves the contradiction by providing reliable update delivery without requiring direct network connection from the mobile vehicle, thus improving reliability while maintaining manageable system complexity.
2Productivity
If software updates are applied immediately, then system functionality is updated promptly, but vehicle operation is disrupted
Solution Approach 1:
The patent implements preliminary action by having the courier device receive and store update packages in advance before they are installed in the vehicle. The update is prepared and staged in the courier device's storage, then transferred to the vehicle when appropriate conditions are met. This allows the update to be ready but not immediately applied, thus maintaining update speed capability while avoiding disruption to ongoing vehicle operations.
Solution Approach 2:
The patent applies dynamics by making the update installation process conditional and adaptive. The system determines whether to install updates based on vehicle state (e.g., parked vs. moving, engine on vs. off). This dynamic approach allows rapid update deployment when conditions permit while automatically preventing disruption when the vehicle is in operation, thus resolving the contradiction between update speed and operational continuity.
3Adaptability or versatility
If updates are transferred directly from server to vehicle, then transfer process is simple, but network accessibility is limited for mobile vehicles
Solution Approach 1:
The courier device serves as an intermediary that bridges the network and the vehicle. It downloads updates from the server when network access is available, stores them in its memory, and then transfers them to the vehicle. This approach enhances adaptability by allowing the system to update vehicles even when they are mobile and cannot directly access the network, while the pre-stored updates in the courier device eliminate transfer time delays.
4Loss of time
If update installation is performed without scheduling, then update process is quick, but vehicle disruption increases
Solution Approach 1:
The patent implements dynamic scheduling of update installation based on real-time vehicle state monitoring. The system checks conditions such as whether the vehicle is parked, engine status, and operational mode before initiating update installation. This dynamic approach allows the update to be installed quickly when conditions are favorable (minimizing time loss) while automatically preventing installation during active operation (reducing disruption), thus resolving the contradiction between installation speed and disruption avoidance.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
The present disclosure is generally directed to systems and methods for updating functionality of vehicular computing devices. An update package, received from client device, comprises at least one update along with parameters for scheduling installation for a time when the operation state of the vehicle or of vehicular computing devices is compatible with installation of the update package, and along with instructions for installation. Current software is backed-up before installation of update. After installation of update it is determined whether installation was successful, and update is committed if successful. Updates may be associated with severity levels and prioritised accordingly. Updates may be verified or validated. Recovery or roll-back may be performed from backup, if installation was not successful. An error message may be transmitted. A flag may be set indicating success or error.