Vehicle ECU Reprogramming With Central Unit Function Substitution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing vehicle systems cannot perform reprogramming of electronic devices while they are in use, particularly during vehicle operation, leading to operational limitations.

Innovation Solution

A vehicle system is designed with a central unit that temporarily stores and executes applications from object units, allowing reprogramming by transferring applications to an evacuation storage area, enabling the central unit to substitute for the object units during the reprogramming process, thus maintaining functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If reprogramming is performed on electronic devices during vehicle operation, then system functionality is maintained, but data integrity and error reduction are improved

Engineering Contradiction:

Improvedata integrityVSAvoidsystem structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The memory system is divided into two distinct storage areas: a first storage area for storing the original application and a second storage area for temporarily storing updated application data. This segmentation allows the system to maintain the original application while receiving and processing updates, ensuring data integrity without requiring a complete system redesign.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The second storage area acts as an intermediary between the external update source and the original application in the first storage area. This intermediate storage enables the system to receive updated data during operation without directly modifying the running application, thereby maintaining reliability while managing complexity through a buffered update mechanism.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the application is disabled and updated in the first storage area, then updated functionality is achieved, but operational continuity is disrupted

Engineering Contradiction:

Improveupdate capabilityVSAvoidoperational continuity

Core Design Contradiction:

Adaptability or versatilityVSDuration of action of moving object

Solution Approach 1:

The system performs preliminary actions by storing the updated application data in the second storage area before activating it. This allows the update to be prepared and validated in advance, ensuring that the transition from the original application to the updated application is smooth and maintains operational continuity without disruption.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The updated application data is copied to the second storage area while the original application continues to run from the first storage area. This copying mechanism allows the system to maintain operational continuity by keeping the original application active during the update process, and only switches to the updated version after successful validation.

Inventive Principle:

Principle #26Copying

3Productivity

If reprogramming is performed while the vehicle is running, then operational limitations are removed, but the risk of errors during update increases

Engineering Contradiction:

Improvereprogramming efficiencyVSAvoidupdate safety

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system provides beforehand cushioning by maintaining the original application in the first storage area as a backup while the updated application is being prepared in the second storage area. This cushioning mechanism ensures that if the update process encounters errors or fails, the system can seamlessly continue using the original application, thereby maintaining update safety while enabling reprogramming during vehicle operation.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The system implements a discard and recover mechanism where the updated application in the second storage area can be discarded if validation fails, and the original application in the first storage area is recovered and continued to be used. This approach allows the system to attempt updates during operation while maintaining reliability through automatic fallback to the known-good original application.

Inventive Principle:

Principle #34Discarding and recovering

Data Source

PatentUS20250328336A1vehicle

Publication Date: 2025.10.23 SUBARU CORP

AI summary

A vehicle includes: an object unit including an object unit processor and an object unit memory coupled thereto; a communication unit including a communication unit processor and a communication unit memory coupled thereto; and a central unit including a central unit processor and a central unit memory coupled thereto. The object unit memory includes a first storage to store an application. The central unit memory includes a second storage to store part of the application. The communication unit processor performs a process including transferring update data to the object unit. The object unit processor performs a process including: storing the partial application in the second storage; disabling the partial application stored in the first storage; and performing an update process. The central unit processor causes part of a function of the object unit to operate by the application stored in the second storage at least during the update process.