TDD Ethernet PHY for Asymmetric Automotive Data Rates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data communication protocols in automotive applications are limited by their inability to provide both symmetrical and asymmetrical data rates, which is crucial for balancing the high data flow from cameras and sensors to processors, and vice versa, while also being inflexible and power-intensive.
Innovation Solution
A physical layer Ethernet device utilizing time domain duplexing (TDD) with XGMII encoding, burst mapping, Reed Solomon FEC framing, and pulse amplitude mapping to enable flexible data rates ranging from 2 Gbps to 16 Gbps, supporting both symmetrical and asymmetrical communication modes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Ethernet protocol is used for automotive data communication, then Ethernet compatibility and established interface capability are provided, but the system is limited to symmetrical operation and cannot provide asymmetric data rates
Solution Approach 1:
The Ethernet protocol stack is segmented into distinct functional blocks: XGMII encoder for interface encoding, burst mapper for asymmetric rate adaptation, framer for Reed Solomon FEC framing, mapping module for pulse amplitude mapping, and PMA for physical transmission. Each block handles specific protocol functions independently, enabling asymmetric data rates while maintaining Ethernet compatibility.
Solution Approach 2:
A burst mapper is introduced as an intermediary component between the symmetric Ethernet protocol layer and the physical transmission layer. This mediator translates and adapts the Ethernet data stream into asymmetric burst patterns, allowing the system to achieve asymmetric data rates without modifying the core Ethernet protocol.
2Use of energy by moving object
If asymmetrical data rates are implemented to match camera-to-processor traffic patterns, then power consumption is reduced and flexibility is improved, but existing protocols cannot provide this capability
Solution Approach 1:
The system implements dynamic data rate configuration where the upstream and downstream data rates can be independently adjusted. The PMA supports variable data rates from 2 Gbps to 16 Gbps, and the burst mapper dynamically adapts the Ethernet stream to match the required asymmetric rates, enabling power optimization by matching actual traffic patterns.
Solution Approach 2:
The protocol allows independent configuration of upstream and downstream data rate parameters. By changing these parameters, the system can optimize power consumption - for example, using lower upstream rates for processor-to-camera traffic and higher downstream rates for camera-to-processor traffic, rather than being constrained to symmetric rates.
3Productivity
If higher data rates are used to accommodate increasing sensor data volumes, then communication capacity is improved, but signal-to-noise ratio and bit error rate are affected
Solution Approach 1:
Reed Solomon Forward Error Correction (FEC) framing is implemented in the framer block to provide error correction capability before data transmission. This beforehand cushioning allows the system to transmit at higher data rates while maintaining reliability, as the FEC codes can correct errors that occur at higher speeds without requiring retransmission.
Solution Approach 2:
The OAM (Operations, Administration, and Management) channels provide feedback mechanisms for monitoring and adjusting transmission parameters. This feedback enables the system to adapt to channel conditions and maintain optimal error rates even at higher data rates by adjusting transmission characteristics based on observed performance.
Data Source
AI summary
The proposed communication protocol enables both asymmetrical and symmetrical communication using TDD based allocation system, while having Ethernet PHY compatibility for interface with other systems. Ethernet physical layer device is configured to process data from a MAC to a desired line rate and is configured with a a XGMII interface configured to transport data from the MAC. An encoder is configured to perform encoding on the data received over the XGMII interface to create encoded data. A burst mapper is configured to append OAM or reserved bit allocation to the encoded data to create mapped data and a PCS device configured process the mapped data to data burst that include a header and one or phy blocks of data.