CAN Message Delivery Ethernet Frame for Vehicle Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional vehicle communication systems face delays and increased software costs due to the large header size of Ethernet frames when transmitting CAN messages, which affects real-time transmission performance in Advanced Driver Assistance Systems and autonomous driving.
Innovation Solution
A vehicle heterogeneous communication system that uses a CAN message delivery Ethernet frame with a shortened size by omitting MAC, IP, and UDP stacks, and adding an SSD4 symbol, allowing for efficient processing and transmission between Ethernet and CAN controllers, including a microcontroller unit and a physical layer module to recognize and process the CAN message delivery frame.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a general Ethernet frame structure is used to transmit CAN messages, then the transmission can be performed using standard Ethernet protocols, but the frame size becomes excessively large due to the ancillary header (MAC/IP/UDP stacks) and processing time is delayed
Solution Approach 1:
The patent extracts and removes the unnecessary MAC/IP/UDP header stacks from the Ethernet frame structure when transmitting CAN messages. By taking out only the essential components needed for CAN message transmission and eliminating the redundant protocol headers, the frame size is reduced from 113 bytes to a much smaller size, thereby reducing processing time while maintaining Ethernet transmission capability
Solution Approach 2:
The patent segments the Ethernet frame into two distinct parts: a simplified header portion containing only essential transmission information and a payload portion containing the CAN message. This segmentation allows the system to use a lightweight custom header instead of the full MAC/IP/UDP stack, achieving faster processing while maintaining protocol compatibility
2Adaptability or versatility
If a general Ethernet frame with full MAC/IP/UDP stacks is used, then comprehensive protocol support is provided, but software costs increase and processing efficiency decreases
Solution Approach 1:
The patent extracts only the necessary protocol elements required for CAN message transmission over Ethernet, removing the redundant MAC/IP/UDP stack components. This extraction reduces software complexity and development costs while maintaining the essential functionality of Ethernet-based CAN message transmission
Solution Approach 2:
Instead of using the conventional approach of embedding CAN messages in full Ethernet frames with complete protocol stacks, the patent inverts the approach by creating a simplified custom frame structure that embeds CAN messages with minimal overhead, thereby reducing software complexity while achieving the same communication goal
3Ease of operation
If the Ethernet frame includes complete MAC/IP/UDP headers, then standard Ethernet processing can be used, but the frame size is excessively larger than the valid data
Solution Approach 1:
The patent removes the excessive header overhead (MAC/IP/UDP stacks) from the Ethernet frame, extracting only the minimal necessary information for CAN message transmission. This reduces the frame size from 113 bytes to a compact size where the valid CAN message data constitutes the majority of the frame, thereby improving transmission efficiency
Solution Approach 2:
The patent segments the frame into a minimal custom header and the CAN message payload, separating the essential transmission control information from the data payload. This segmentation eliminates the need for bulky standard protocol headers while maintaining the ability to process Ethernet frames
Data Source
AI summary
A vehicle heterogeneous communication system for efficient CAN message transmission between heterogeneous communication controllers in a vehicle includes: a first transceiving controller transmitting a CAN message delivery Ethernet frame to which an SSD4 symbol added by changing an SSD size compared with a general Ethernet frame; and a second transceiving controller recognizing the received Ethernet frame as the CAN message delivery Ethernet frame when there is the SSD4 symbol by checking the SSD of Ethernet frame received from the first transceiving controller, and performing CAN message delivery Ethernet frame processing in which a media access control (MAC), Internet protocol (IP), and user datagram protocol (UDP) analysis step in the general Ethernet frame processing process is omitted.


