In-Vehicle Network Configuration for ECUs Missing Function Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing management devices struggle to generate configuration information for a new in-vehicle network when a newly added Electronic Control Unit (ECU) lacks the function of transmitting function unit information.

Innovation Solution

A management device that includes a detection unit to identify new function units, an acquisition unit to request missing information via notifications, and a generation unit to create network configuration based on acquired information, even when the new units cannot transmit their information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the management device relies on the new ECU to transmit its own function unit information, then the system maintains simplicity and automaticity, but the network configuration cannot be generated when the new ECU lacks this transmission function

Engineering Contradiction:
Improvenetwork configuration generation reliabilityVSAvoidinformation acquisition process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The management device acts as an intermediary by introducing a manual information input interface. When automatic information acquisition fails (new ECU cannot transmit its information), the system provides an alternative path where users can manually input the function unit information through a terminal device, ensuring the configuration generation process can proceed regardless of the ECU's capabilities

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary checks to determine whether the new ECU can transmit its function unit information before proceeding with configuration generation. Based on this preliminary assessment, the system prepares appropriate information acquisition methods in advance - either automatic acquisition from the ECU or manual input from users, ensuring the process can adapt to different ECU capabilities

Inventive Principle:
Principle #10Preliminary action

2Productivity

If the system waits for the new ECU to automatically provide information, then automation is maintained, but time is lost when the ECU cannot transmit information

Engineering Contradiction:
Improvenetwork configuration generation speedVSAvoidinformation acquisition time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The information acquisition method dynamically adapts based on the ECU's capabilities. The system first attempts automatic information acquisition, and when this fails, it transitions to manual information input. This dynamic adjustment optimizes the overall process speed by using the fastest available method for each specific situation

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements a feedback mechanism where the management device monitors whether function unit information was successfully acquired from the new ECU. Based on this feedback, the system determines the next appropriate action - either proceeding with automatic configuration generation or switching to manual information input mode, thereby eliminating unnecessary waiting time

Inventive Principle:
Principle #23Feedback

3Loss of information

If manual information input is always required, then complete information can be obtained, but the operation process becomes complex and time-consuming

Engineering Contradiction:
Improvefunction unit information completenessVSAvoidconfiguration process ease
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system applies partial action by requiring manual information input only when necessary - specifically when the new ECU cannot automatically transmit its function unit information. When the ECU can provide information automatically, the system uses this automatic acquisition method, thereby minimizing user involvement while ensuring information completeness

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20260039543A1Management device, vehicle communication management method, and vehicle communication management program
Publication Date: 2026.02.05 SUMITOMO ELECTRIC INDUSTRIES LTD
  • US20260039543A1 patent drawing
  • US20260039543A1 patent drawing
  • US20260039543A1 patent drawing

AI summary

A vehicle communication management device includes (i) a detection circuitry configured to detect addition of a function circuitry to a network including one or a plurality of in-vehicle function circuitries, (ii) an acquisition circuitry, and (iii) a generation circuitry. The acquisition circuitry is configured to acquire function circuitry information of each in-vehicle function circuitry, and if target information, which is function circuitry information of a new function circuitry that is the function circuitry the addition of which has been detected by the detection circuitry, cannot be acquired from the new function circuitry, acquire the target information by transmitting a lacking information notification for requesting a user to provide the target information. The generation circuitry is configured to, based on each function circuitry information acquired by the acquisition circuitry, generate configuration information of a new network which is the network further including the new function circuitry.