Ethernet FEC Enablement via Link Training Channel Quality
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Ethernet network systems unnecessarily degrade performance and increase latency by enabling Forward Error Correction (FEC) protocols during auto-negotiation, as they are agnostic to channel quality, leading to inappropriate FEC enablement.
Innovation Solution
The network system configures FEC capability resolution during the link training period instead of auto-negotiation, allowing nodes to determine channel quality and enable FEC only when necessary, enabling asynchronous FEC mode enablement on a channel-by-channel basis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If FEC protocols are enabled during auto-negotiation period, then packet integrity is improved, but system performance degrades and latency increases
Solution Approach 1:
The patent applies preliminary action by measuring channel quality during the link training period (which occurs before FEC is actually needed for data transmission) and using this information to make an informed decision about whether to enable FEC during auto-negotiation. This preliminary measurement allows the system to avoid unnecessarily enabling FEC, thus maintaining high system performance while ensuring packet integrity when actually needed.
2Reliability
If FEC protocols are enabled during auto-negotiation period, then packet integrity is improved, but power demand increases
Solution Approach 1:
The patent applies preliminary action by measuring channel quality during the link training period (which occurs before FEC is actually needed for data transmission) and using this information to make an informed decision about whether to enable FEC during auto-negotiation. This preliminary measurement allows the system to avoid unnecessarily enabling FEC, thus maintaining high system performance while ensuring packet integrity when actually needed.
3Adaptability or versatility
If FEC is enabled based on auto-negotiation capabilities, then compatibility is improved, but appropriate FEC enablement deteriorates
Solution Approach 1:
The patent applies local quality by transitioning from a blanket FEC enablement approach to a channel-specific approach. Instead of enabling FEC uniformly based on capability exchange, the system measures actual channel quality metrics (such as signal-to-noise ratio, bit error rate, or other link quality parameters) for each individual channel and enables FEC only on channels that require it. This allows different channels to have different FEC configurations optimized for their specific quality characteristics.
Solution Approach 2:
The patent applies feedback by implementing a mechanism where channel quality measurements during link training are fed back to influence the FEC enablement decision during auto-negotiation. The system uses the actual measured channel quality information to adjust and refine the FEC configuration, creating a closed-loop system that continuously adapts FEC enablement based on real channel conditions rather than relying solely on pre-negotiated capabilities.
Data Source
AI summary
One embodiment provides a method for resolving a forward error correction (FEC) protocol. The method includes requesting, by a network node element during an auto-negotiation period between the node element and a link partner, to resolve at least one FEC mode during a link training period; wherein the auto-negotiation period and the link training period are defined by an Ethernet communications protocol and the auto-negotiation period occurs before the link training period; determining, by the network node element, at least one channel quality parameter of at least one channel of a communication link between the network node element and the link partner; and determining, by the network node element during the link training period, whether to enable at least one FEC mode for use by the network node element based on, at least in part, the at least one channel quality parameter.


