In-Vehicle Management Data Rewrite via ECU Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for updating in-vehicle software face challenges in efficiently and accurately rewriting management data related to multiple electronic control units, particularly due to complex processing requirements and the need to handle changes in legal numbers associated with software updates.
Innovation Solution
A management data rewrite system comprising a first electronic control unit with a non-volatile memory for holding management data and a second electronic control unit that updates in-vehicle software. The second ECU receives the entire management data, rewrites the relevant data portions, and transmits the updated data back to the first ECU, simplifying the rewrite process and reducing the processing load on the first ECU.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the first ECU (CGW) performs all processing for rewriting management data during software updates, then the update control can be centralized, but the processing load on the first ECU becomes excessive and the complexity increases
Solution Approach 1:
The patent divides the management data rewriting task into two segments: the first ECU (CGW) handles data transmission and coordination, while the second ECU (target of update) performs the actual rewriting of management data. This segmentation reduces the processing load and complexity on the first ECU while maintaining centralized update control reliability.
Solution Approach 2:
The second ECU (target of update) performs the management data rewriting operation itself based on update information from the first ECU. This self-service approach eliminates the need for the first ECU to directly manipulate management data, reducing its processing complexity while ensuring reliable update control through coordinated operation.
2Adaptability or versatility
If the first ECU stores and manages all management data for multiple ECUs, then centralized management is achieved, but the processing load on the first ECU increases during updates
Solution Approach 1:
The patent extracts the management data rewriting operation from the first ECU and assigns it to the second ECU (target of update). The first ECU retains only the function of transmitting update information and receiving rewritten data, thereby reducing its processing load while maintaining centralized management adaptability across multiple ECUs.
Solution Approach 2:
The first ECU acts as an intermediary that coordinates the update process by transmitting update information to the second ECU and receiving the rewritten management data back. This intermediary role reduces the processing load on the first ECU compared to directly performing all rewriting operations, while preserving centralized management capability.
3Manufacturing precision
If management data is rewritten during software updates, then licensing data accuracy is maintained, but the update process becomes more complex and time-consuming
Solution Approach 1:
The patent performs management data rewriting as part of the software update process itself, rather than as a separate subsequent operation. The second ECU rewrites management data using update information received during the update, ensuring licensing data accuracy is maintained while integrating the rewriting operation into the existing update timeline, thus not adding extra time.
Data Source
AI summary
A management data rewrite system is provided that includes first and second electronic control units. The first electronic control unit includes a non-volatile memory configured to hold management data regarding multiple electronic control units. In the second electronic control unit, an update of in-vehicle software is made. The second electronic control unit is coupled to the first electronic control unit and configured to carry out transmission and reception of data to and from the first electronic control unit through an in-vehicle network. The second electronic control unit receives an entirety of the management data from the non-volatile memory, rewrites a data portion related to the update of the in-vehicle software in the management data, into new data, and transmits an entirety of the post-rewrite management data to the first electronic control unit, to allow the non-volatile memory to hold the entirety of the post-rewrite management data.