Virtual CAN Bus Publish-Subscribe for Selective ECU Data Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing vehicle communication systems, such as the CAN bus, suffer from inefficient message exchange and physical limitations, leading to unnecessary data distribution to all ECUs and difficulties in remote testing scenarios where not all ECUs are available or correctly installed.

Innovation Solution

A virtual bus architecture with a publish-subscribe framework that converts CAN frames into Ethernet messages for transmission over the Internet, allowing selective data delivery to subscribed ECUs and enabling dynamic configuration of ECU interactions across different CAN buses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional CAN bus architecture is used for ECU communication, then all ECUs receive all data frames, but this leads to inefficient message exchange and unnecessary data distribution

Engineering Contradiction:

Improvemessage exchange efficiencyVSAvoidunnecessary data distribution

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The patent extracts the data distribution function from the traditional broadcast architecture and implements selective subscription. ECUs can now subscribe only to the specific data frames they need, removing the unnecessary data distribution that occurs in traditional CAN bus where all ECUs receive all frames regardless of need.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The gateway acts as an intermediary between ECUs and the Ethernet network. It receives data frames from ECUs, determines subscription relationships, and selectively forwards only relevant frames to subscribed ECUs over Ethernet, thereby improving message exchange efficiency and reducing unnecessary data distribution.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If physical CAN bus connections are used, then ECUs can communicate directly, but this creates physical limitations and difficulties in remote testing scenarios

Engineering Contradiction:

Improveremote testing capabilityVSAvoidphysical connection requirements

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent replaces the mechanical/physical CAN bus connection system with an Ethernet-based network system. ECUs can communicate over Ethernet infrastructure instead of requiring direct physical CAN bus connections, enabling remote testing and eliminating the constraints of physical proximity and correct installation.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The gateway provides universal communication capability by supporting both traditional CAN bus interfaces and Ethernet network interfaces. This allows the system to function in both local and remote scenarios, accommodating different testing and deployment environments without requiring separate dedicated systems.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of operation

If all ECUs are connected to the same CAN bus, then communication is straightforward, but this prevents dynamic configuration and selective data delivery

Engineering Contradiction:

Improveselective data deliveryVSAvoidsubscription management framework

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements dynamic subscription management where ECUs can subscribe to data frames based on their specific needs. The subscription relationships are not fixed but can be configured and modified dynamically, allowing selective data delivery while maintaining ease of operation through the standardized subscription interface.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS20260012372A1Can bus with publish-subscribe architecture

Publication Date: 2026.01.08 TOYOTA MOTOR NORTH AMERICA INC

AI summary

An example operation includes one or more of receiving a request from a first ECU disposed on a virtual bus, wherein the request identifies data to be obtained from a second ECU, generating a subscription between the first ECU and the second ECU for the identified data via a framework of a virtual bus, receiving a data frame which is published by the second ECU, and forwarding the data frame published by the second ECU to the first ECU on the virtual bus based on the generated subscription.