Server Software Update Management via Vehicle Lifecycle Status
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge is to ensure timely software updates for electronic control units in vehicles throughout their life cycle, as existing over-the-air (OTA) technologies face difficulties in determining the vehicle's location and approval entity, leading to potential delays in software updates.
Innovation Solution
A server system that stores vehicle identification and life cycle status information, allowing it to determine if software updates are required and instructing on approval necessity based on the vehicle's status, enabling timely software updates by associating vehicle identification information with life cycle status to manage software updates efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If OTA technology is used for software updates, then software can be updated wirelessly throughout the vehicle lifecycle, but the system cannot determine vehicle location and approval entity, leading to delayed updates
Solution Approach 1:
The server performs preliminary actions by storing life cycle status information (yard, transport, dealership, owned) for each vehicle ID before update requests occur. This pre-established information allows the server to immediately determine the appropriate approval entity and update timing when a vehicle connects, eliminating delays caused by real-time location tracking and approval entity identification.
Solution Approach 2:
The system implements feedback by having the server compare the vehicle's current life cycle status against update criteria and provide appropriate responses. When the vehicle is in statuses requiring approval (dealership or owned), the server feedbacks approval requirements to the vehicle. When in statuses allowing automatic updates (yard or transport), the server feedbacks approval exemption, enabling timely updates based on lifecycle stage.
2Reliability
If approval is required for all software updates, then update security is improved, but update timing is delayed due to approval processing
Solution Approach 1:
The system applies local quality by differentiating approval requirements based on the specific life cycle status of each vehicle. Instead of uniformly requiring approval for all vehicles, the server selectively applies approval requirements only to vehicles in dealership or owned statuses, while exempting vehicles in yard or transport statuses. This localized approach maintains security where needed while enabling rapid updates where appropriate.
Solution Approach 2:
The system implements dynamics by making approval requirements flexible and adaptable to the vehicle's current life cycle stage. The server dynamically determines whether approval is needed based on the vehicle's status (yard, transport, dealership, or owned), allowing the update process to adapt its security level and speed according to the specific context, thereby optimizing both reliability and productivity.
3Measurement precision
If vehicle location and approval entity are manually determined, then update accuracy is improved, but system complexity increases
Solution Approach 1:
The server performs preliminary action by pre-storing life cycle status information for each vehicle ID in its database. This pre-established information infrastructure eliminates the need for complex real-time location tracking systems or manual approval entity determination processes. When a vehicle connects, the server simply retrieves the pre-stored status information, achieving accurate vehicle status identification with minimal system complexity.
Data Source
AI summary
A server includes: a storage unit that stores, for each of pieces of vehicle identification information that identifies a vehicle, life cycle status information indicating a distribution status of the vehicle after manufacturing, the life cycle status information being associated with the vehicle identification information; a communication unit that receives a confirmation request including the vehicle identification information from the vehicle; and a control unit that determines whether there is update data of software of the vehicle identified by the vehicle identification information included in the confirmation request when the communication unit receives the confirmation request. The control unit transmits, to the vehicle, instruction information instructing whether approval is required at a time of execution of a software update process in the vehicle, based on the life cycle status information, when determining that there is the update data of the software of the vehicle.