Vehicle Software Update Cancellation With Split Error Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software update systems fail to properly cancel campaigns and notify users of the reason for cancellation due to various errors, leading to inefficiencies and increased management costs for servers.
Innovation Solution
A software management system that allows vehicles to cancel campaigns based on different error types, with the server handling first errors and the vehicle handling second errors, ensuring appropriate notification of cancellation reasons on display devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the server determines and notifies all cancellation reasons, then user notification completeness is improved, but server management cost and communication overhead increase
Solution Approach 1:
The patent segments cancellation reasons into two categories: server-side errors (first errors) and vehicle-side errors (second errors). The server handles notification for first errors, while the vehicle autonomously handles notification for second errors. This segmentation reduces server management cost by having the vehicle manage its own error notifications while ensuring complete user notification through dual-responsibility coverage.
2Reliability
If the server handles all error notifications, then notification reliability is improved, but communication overhead and server load increase
Solution Approach 1:
The patent implements self-service by enabling the vehicle to autonomously determine and notify users about second errors (vehicle-side errors) without server intervention. The vehicle checks its own error conditions and displays appropriate messages to users, reducing server processing power requirements while maintaining notification reliability through the vehicle's autonomous error handling capability.
3Device complexity
If the vehicle autonomously determines cancellation reasons, then server cost reduction is achieved, but notification accuracy may deteriorate
Solution Approach 1:
The patent segments error determination responsibilities based on error origin: the server determines first errors (server-side issues) while the vehicle determines second errors (vehicle-side issues). This segmentation ensures notification accuracy is maintained for each party's errors while reducing overall server management cost, as the vehicle independently manages its own error notifications without requiring server involvement.
4Stability of the object's composition
If wireless communication is required for error notification, then server coordination is improved, but system availability decreases in poor connectivity environments
Solution Approach 1:
The patent implements self-service error notification where the vehicle autonomously notifies users about second errors without requiring wireless communication with the server. This ensures system availability is maintained in poor connectivity environments, as the vehicle can independently determine and communicate vehicle-side errors to users through local display devices, while server coordination remains optional for first error notifications.
Data Source
AI summary
A software management system includes: a vehicle including a control device storing software and a display device; and a server including one or more processors that update the software by wireless communication. When a first error due to the server occurs, the one or more processors cancel software update and request the vehicle to display a description of the first error on the display device. When a second error different from the first error occurs, the vehicle cancels the software update, and displays a description of the second error on the display device without being requested by the one or more processors.


