In-Vehicle ECU Cluster Rewriting for Flexible Network Activation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing in-vehicle network systems face challenges in flexibly responding to changes in startup conditions of ECUs due to fixed relationships between ECUs, leading to potential inappropriate changes and failures in vehicle functions.

Innovation Solution

An in-vehicle network system with cluster information management, where each control device determines the validity of rewrite requests based on the attribute of the request source, allowing flexible and controlled changes within a defined rewritable range.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If fixed relationships between ECUs are maintained, then system stability is preserved, but flexibility to respond to ECU startup condition changes deteriorates

Engineering Contradiction:

Improveflexibility to respond to ECU startup condition changesVSAvoidsystem stability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic cluster information that can be rewritten based on startup conditions. The ECU determines whether to rewrite cluster information based on comparison between current startup conditions and stored startup conditions, allowing the system to adapt dynamically while maintaining stability through controlled rewrite operations.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of cluster information from fixed to rewritable based on startup conditions. By allowing cluster information to be updated when startup conditions change, the system achieves flexibility while maintaining reliability through the structured rewrite determination process that compares current and stored conditions.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If cluster information is made rewritable, then adaptability to startup condition changes improves, but risk of inappropriate modifications increases

Engineering Contradiction:

Improveadaptability to startup condition changesVSAvoidinappropriate modifications

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements a feedback mechanism where the ECU stores startup conditions and cluster information, then determines whether to rewrite cluster information by comparing current startup conditions with stored ones. This feedback loop prevents inappropriate modifications by ensuring rewrites only occur when actual condition changes are detected.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent performs preliminary storage of startup conditions and cluster information before any rewrite operation. By storing the original state and comparing it with current conditions, the system prepares for potential rewrites while preventing inappropriate modifications through the comparison check.

Inventive Principle:

Principle #10Preliminary action

3Productivity

If cluster information is rewritten without validation, then responsiveness to condition changes improves, but system reliability deteriorates

Engineering Contradiction:

Improveresponsiveness to condition changesVSAvoidsystem reliability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent implements validation feedback by determining whether rewrite requests are valid before executing rewrites. The ECU compares current startup conditions with stored conditions and only rewrites cluster information when the rewrite request is determined to be valid, ensuring both responsiveness and reliability.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent implements dynamic validation that adapts rewrite permissions based on current startup conditions. Rather than fixed rewrite rules, the system dynamically determines validity by comparing current and stored conditions, achieving both responsiveness to changes and maintenance of reliability.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS20260056835A1In-vehicle network system and management method of in-vehicle network system

Publication Date: 2026.02.26 DENSO CORP

AI summary

An in-vehicle network system is equipped to a vehicle, which includes multiple control devices communicating with one another via a communication bus. Each control device has cluster information indicating a cluster to which ego device belongs, and switches to an activated state or maintains the activated in response to receiving of network management message, which includes activation cluster information indicating a target cluster to be activated is same as the cluster of ego device. The in-vehicle network system is configured to: determine, when a rewrite request for rewriting the cluster information is received in at least one of the multiple control devices, that the rewrite request is a valid rewrite request under a condition that the rewrite request is within a rewritable range of the cluster information, and then rewrite the cluster information according to the valid rewrite request.