Vehicle ECU Update Control via Memory Structure Awareness
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current vehicle information communication systems face challenges in efficiently managing program data rewrites for electronic control units (ECUs) across diverse memory structures, particularly in ensuring safe and timely updates while the vehicle is in operation, and in handling rollbacks effectively.
Innovation Solution
A vehicle information communication system that includes a center device and a vehicle device, where the center device generates specification data based on memory structure information to control program data rewrites for ECUs, supporting Read While Write (RWW) operations and incorporating override information to restrict updates to when the vehicle is parked, and performs rollbacks accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If program data rewrites are performed for ECUs with diverse memory structures, then system adaptability is improved, but ensuring safe and timely updates while the vehicle is in operation becomes more difficult
Solution Approach 1:
The memory is segmented into multiple independent memory regions, allowing the system to perform read operations in one region while write operations occur in another region. This segmentation enables safe program data rewrites during vehicle operation by preventing conflicts between read and write operations.
Solution Approach 2:
The system dynamically adapts its update strategy based on the memory structure type. For ECUs with RWW-capable memory, updates can proceed during operation, while for ECUs with non-RWW memory, the system adjusts timing to ensure safety. This dynamic adaptation maintains reliability across diverse memory structures.
2Reliability
If program data rewrites are restricted to when the vehicle is parked, then reliability is improved, but productivity deteriorates due to delayed updates
Solution Approach 1:
The update timing policy is dynamically adjusted based on the ECU's memory structure characteristics. ECUs with RWW-capable memory can be updated during vehicle operation, while ECUs with non-RWW memory are updated when parked. This dynamic policy achieves both reliability and timeliness appropriately for each ECU type.
Solution Approach 2:
Different update strategies are applied to different ECUs based on their individual memory structure properties. Rather than applying a uniform restriction to all ECUs, the system tailors the update approach to each ECU's capabilities, allowing timely updates for RWW memory types while ensuring safety for non-RWW types.
3Productivity
If the system supports RWW operations for all ECUs, then productivity is improved, but device complexity increases due to additional memory structure requirements
Solution Approach 1:
The system maintains universality by supporting both RWW and non-RWW memory structures through a unified update management approach. The ECU information database stores memory structure information for different ECU types, and the system automatically selects the appropriate update strategy, eliminating the need for separate systems for different memory types.
Solution Approach 2:
The system changes the operational parameter (update timing) based on the memory structure parameter. Rather than requiring all ECUs to have identical RWW memory structures, the system adapts the update timing parameter to match each ECU's memory capabilities, achieving productivity without forcing hardware complexity.
4Ease of operation
If specification data including memory structure information is generated and transmitted, then ease of operation is improved, but loss of time occurs during data transmission
Solution Approach 1:
The system performs preliminary actions by storing memory structure information in the ECU information database in advance. When program data rewrites are needed, the controller can quickly retrieve this pre-stored information and generate appropriate specification data, reducing the time required during actual update operations.
Solution Approach 2:
The system creates and transmits specification data as a copy containing memory structure information, rather than requiring complex real-time analysis of each ECU's memory. This copying approach simplifies the control process and reduces transmission time by using standardized data formats.
Data Source
AI summary
A vehicle information communication system includes a vehicle device and a center device. The center device includes a storage unit, a center computer, and a center-device communication unit. The storage unit stores memory structure information for each of the ECUs. The memory structure information indicates whether a corresponding memory has a memory structure that supports Read While Write (RWW) operation defined as having a plurality of physically independent memory regions. The center computer is programmed to generate specification data including the memory structure information for each of the at least one target ECUs. The vehicle device includes a vehicle computer. The vehicle computer is programmed to perform the program data rewrites of the at least one target ECU according to the memory structure information included in the specification data.