Center Device Program Update Phase Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing complexity of vehicle control systems and the need for frequent program updates in electronic control units (ECUs) pose challenges in efficiently managing and executing program updates, especially with the integration of Over The Air (OTA) technology for connected cars.
Innovation Solution
A center device that obtains program update campaign information and vehicle state, sets execution requirements, and notifies the vehicle master device to facilitate controlled phases of program updates, ensuring seamless data delivery and execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If program updates are performed frequently to improve system functionality, then system adaptability is improved, but the complexity of managing update phases increases
Solution Approach 1:
The program update process is divided into distinct phases (download phase, installation phase, activation phase), each with specific execution requirements and acceptance operations. This segmentation allows the system to manage complex updates systematically by controlling each phase independently, thereby resolving the contradiction between frequent updates and management complexity.
2Reliability
If user acceptance operations are required for each update phase, then update reliability is improved, but update productivity decreases due to delayed completion when users do not perform operations
Solution Approach 1:
The system performs preliminary actions by automatically advancing through update phases when execution requirements are met, without requiring explicit user acceptance operations for each phase. The center device determines whether to require acceptance operations based on the current phase and execution requirements, allowing the system to maintain reliability while improving productivity by reducing unnecessary waiting for user actions.
Solution Approach 2:
The requirement for user acceptance operations is made dynamic rather than static. The system adaptively determines whether to require acceptance operations based on the current update phase and execution requirements. In some phases, acceptance operations are required to ensure reliability; in other phases, the system automatically advances to maintain productivity, thus resolving the contradiction between reliability and productivity.
3Productivity
If the system automatically advances through update phases without user confirmation, then update productivity is improved, but the risk of abnormal completion increases
Solution Approach 1:
The system implements feedback mechanisms where the center device continuously monitors the update process, vehicle state, and execution requirements. Based on this feedback, the system dynamically determines whether to require user acceptance operations or automatically advance phases, ensuring that productivity improvements do not compromise update completion reliability.
Data Source
AI summary
A vehicle electronic control system includes a center device and a vehicle master device. The center device includes: a campaign information obtainer obtaining campaign information of a program update; a vehicle state obtainer obtaining a vehicle state of a target vehicle of the program update; an execution requirement setter setting an execution requirement of a phase in the program update based on the campaign information obtained by the campaign information obtainer and the vehicle state obtained by the vehicle information obtainer; an execution requirement notifier notifying the vehicle master device of the execution requirement set by the execution requirement setter; and an update data deliverer delivering the update data to the vehicle master device.