Vehicle Controller Update Approval With Battery-State Recheck
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle update management systems face challenges in reliably determining whether a vehicle controller update is executable, particularly for autonomous driving functions, leading to potential update failures after user approval.
Innovation Solution
An update management apparatus that determines the executability of vehicle controller updates based on the state of a low-voltage battery at predetermined intervals during driving, requests user approval during ignition-off, and re-evaluates executability before executing the update, using a cooperative controller to display approval windows and manage battery state calculations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the system requests user approval immediately before update execution, then the user can make an informed decision, but the update may fail if battery state changes between approval and execution
Solution Approach 1:
The system performs preliminary determination of update executability at multiple stages: first during vehicle driving to identify potential update opportunities, then again immediately before execution to confirm current battery state. This multi-stage preliminary action ensures the update can be executed reliably while giving users advance notice for informed approval decisions.
Solution Approach 2:
The system implements feedback loops where the first cooperative controller continuously monitors battery state and communicates with the management controller. The management controller receives determination results, requests user approval when conditions are favorable, and performs final verification before execution. This feedback mechanism ensures update reliability while maintaining timely execution.
2Reliability
If the system performs multiple determination checks, then update execution reliability improves, but the system complexity increases
Solution Approach 1:
The system divides the update management function into separate cooperative controllers: a first cooperative controller that performs initial determination during driving and a second cooperative controller that performs final determination before execution. This segmentation distributes the complexity across multiple specialized components rather than concentrating it in a single controller.
Solution Approach 2:
The management controller acts as an intermediary between the cooperative controllers and the user interface. It receives determination results from the first cooperative controller, manages the approval request process, coordinates with the second cooperative controller for final verification, and triggers update execution. This intermediary role simplifies the overall system architecture by centralizing coordination logic.
Data Source
AI summary
An update management apparatus for a vehicle includes: a first cooperative controller configured to first determine whether a vehicle controller is updatable based on a state of a low-voltage battery at a predetermined interval during vehicle driving; a management controller configured to receive a first determination result from the first cooperative controller, and when the vehicle controller is updatable, to request user approval during ignition-off of the vehicle, to update the vehicle controller; and a second cooperative controller configured to display an approval window for the user approval.