Ethernet Controller Flow Control Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional standalone Ethernet controllers lack an automatic flow control mechanism, leading to data packet loss when the buffer is full, requiring complex software to manage data flow and prevent buffer overflow.

Innovation Solution

Incorporating a data flow control unit with a packet counter, watermark registers, and comparator logic to automatically manage data flow by generating control signals when the packet counter reaches predefined watermark values, allowing for both automatic and manual flow control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If automatic flow control mechanism is added to Ethernet controller, then data packet loss is prevented and reliability is improved, but device complexity increases

Engineering Contradiction:
Improvedata packet loss preventionVSAvoidcontroller structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The Ethernet controller performs self-regulation of data flow through internal hardware mechanisms. The packet counter automatically tracks buffer occupancy, the comparator logic autonomously compares counter values against watermark thresholds, and the flow control unit independently generates pause frames without requiring external processor intervention. This self-service approach prevents data packet loss while minimizing the added complexity by using dedicated hardware blocks that operate autonomously.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements a closed-loop feedback mechanism where the packet counter continuously monitors buffer status, the comparator logic provides feedback signals based on watermark comparisons, and the flow control unit adjusts data transmission accordingly. This feedback loop ensures reliable operation by dynamically adapting to buffer occupancy levels, preventing both overflow and unnecessary pauses.

Inventive Principle:
Principle #23Feedback

2Reliability

If complex software is used to control data flow, then buffer overflow is prevented, but ease of operation deteriorates and external processor workload increases

Engineering Contradiction:
Improvebuffer overflow preventionVSAvoidexternal processor control complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent replaces complex software-based flow control mechanisms with dedicated hardware circuits. The packet counter, comparator logic, and flow control unit form a hardware system that automatically manages buffer overflow prevention without requiring the external processor to implement complex control algorithms. This substitution significantly reduces the operational burden on external processors while maintaining reliable buffer management.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The flow control functionality is extracted from the general-purpose external processor and implemented as dedicated hardware blocks within the Ethernet controller. By taking out the flow control logic from software and placing it in hardware, the system eliminates the need for complex processor software while maintaining effective buffer overflow prevention.

Inventive Principle:
Principle #2Taking out (Extraction)

3Device complexity

If manual flow control is used, then device complexity is reduced, but productivity decreases due to slower data transmission

Engineering Contradiction:
Improveflow control mechanism complexityVSAvoiddata transmission efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The flow control system dynamically adjusts its behavior based on real-time buffer status. The packet counter continuously monitors occupancy levels, and the comparator logic dynamically compares current levels against configurable watermark thresholds. This dynamic operation allows the system to automatically pause only when necessary (when buffer is nearly full) and resume transmission when buffer space becomes available, maintaining high productivity while using relatively simple hardware logic.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP2213057B1Ethernet controller
Publication Date: 2019.01.02 MICROCHIP TECHNOLOGY INC
  • EP2213057B1 patent drawingFigure 1
  • EP2213057B1 patent drawingFigure 2~3
  • EP2213057B1 patent drawingFigure 4

AI summary

An Ethernet controller has a buffer memory for receiving data packets, a data flow control unit for controlling the data flow to Ethernet controller, a packet counter, packet counter control logic for incrementing and decrementing the packet counter, a first register for storing a watermark, and a comparator logic coupled to the packet counter and the register for sending control signals to the data flow control unit.