Shared I2C Packet Encoding for Multi-Device TDD Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing need for high-speed communication between in-vehicle devices, particularly in automated driving systems, leads to a requirement for multiple encoders and decoders, which increases the memory capacity and scale of the Root device, making it inefficient and costly.
Innovation Solution
A communication device and system that utilize a shared encoder and decoder for multiple communication partner devices, employing a Time Division Duplex (TDD) communication scheme to transmit and receive Header Packet Data and I2C Packet Data, with a memory space optimized to store target IDs and I2C Packet Data, allowing efficient communication without increasing memory capacity or the number of encoders/decoders.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple encoders and decoders are provided for each Leaf device, then communication capability with multiple I2C communication instruments is improved, but device complexity and memory capacity requirements increase
Solution Approach 1:
The patent implements a universal encoder and decoder that can handle multiple I2C communication instruments through software configuration. The encoder generates packets with target device identification information, allowing a single encoder to communicate with different Leaf devices by changing the target ID in the packet header, eliminating the need for dedicated encoders for each device.
Solution Approach 2:
The patent segments the communication protocol into two parts: a common packet structure that is the same for all devices, and device-specific identification information (target ID) that is changed according to the communication partner. This segmentation allows the same encoder/decoder to serve multiple devices by only changing the identification portion.
2Adaptability or versatility
If multiple encoders and decoders are provided for each Leaf device, then communication capability with multiple I2C communication instruments is improved, but memory capacity requirements increase
Solution Approach 1:
The patent implements a universal encoder and decoder that can handle multiple I2C communication instruments through software configuration. The encoder generates packets with target device identification information, allowing a single encoder to communicate with different Leaf devices by changing the target ID in the packet header, eliminating the need for dedicated encoders for each device.
Solution Approach 2:
The patent changes the parameter of target device identification in the packet header to differentiate between communication partners. Instead of having separate encoders for each device, the system changes the target ID parameter in the packet data to identify different Leaf devices, thereby reducing hardware requirements and memory capacity needs.
3Adaptability or versatility
If the number of connected Leaf devices increases, then communication versatility is improved, but the scale of the Root device increases
Solution Approach 1:
The patent implements a universal encoder and decoder that can handle multiple I2C communication instruments through software configuration. The encoder generates packets with target device identification information, allowing a single encoder to communicate with different Leaf devices by changing the target ID in the packet header, eliminating the need for dedicated encoders for each device.
Data Source
AI summary
The memory capacity for storing address information etc. of an I2C communication instrument, as well as the number of encoders and decoders can be reduced.A communication device to establish communication between a first I2C communication instrument and a second I2C communication instrument connected to a communication partner device, includes: an encoder that generates Header Packet Data including a target ID of the communication partner device and I2C Packet Data including a slave address and an offset address of the second I2C communication instrument; a communication unit that transmits a transmission packet including the Header Packet Data and the I2C Packet Data generated by the encoder to the communication partner device by a TDD communication scheme and receives a reception packet from the communication partner device by the TDD communication scheme; and a decoder that generates the I2C Packet Data from the reception packet.


