MAC Address Table Updates Under Switch Congestion Back Pressure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing media access control (MAC) address table updating technologies face issues with table lookup errors and unexpected forwarding behaviors due to incorrect table contents, leading to missed updates and synchronization failures in switch devices, especially in high-traffic or congested network environments.
Innovation Solution
A media access control address table updating device comprising a learning controller, packet generator, and traffic manager, which employs mechanisms like self-defined packet control, event suppression, back pressure, bypass CPU egress port rate, and end-to-end congestion control to manage update events and prevent table update failures by adjusting operations based on congestion and traffic conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the switch device continuously updates the MAC address table to maintain real-time network topology, then the synchronization accuracy between processor and hardware is improved, but the network congestion and packet loss increase during high-traffic periods
Solution Approach 1:
The patent implements preliminary action by using the event suppression mechanism to anticipate and prevent congestion before it occurs. The system monitors queue depths and determines whether to suppress notification packets in advance, before the processor can become overwhelmed. This proactive approach prevents packet loss while maintaining synchronization accuracy during high-traffic periods.
Solution Approach 2:
The patent employs feedback mechanisms through the traffic manager that continuously monitors queue depths and congestion status, then adjusts the generation of notification packets accordingly. When queues are full or congestion is detected, the system reduces notification packet generation to prevent further congestion, creating a dynamic feedback loop that balances synchronization accuracy with network load.
2Loss of information
If the traffic manager generates notification packets for every MAC address table update event, then the processor receives complete update information, but the processor workload and queue congestion increase
Solution Approach 1:
The patent extracts only the essential update information that the processor needs, rather than transmitting every single MAC address table change event. The event suppression mechanism filters out redundant or non-critical updates, extracting only the most important synchronization information. This reduces processor workload while maintaining the completeness of critical update data.
Solution Approach 2:
The patent applies partial action by selectively generating notification packets only when necessary, rather than for every update event. The traffic manager determines whether to suppress notifications based on queue depth and congestion status, performing partial updates rather than complete updates in all cases. This balances information completeness with processor efficiency.
3Manufacturing precision
If the switch device updates the MAC address table frequently to maintain network topology accuracy, then the forwarding precision is improved, but the data transmission time and network burden increase
Solution Approach 1:
The patent implements periodic action through the congestion-based suppression mechanism that adjusts notification packet generation in periodic intervals based on network conditions. Rather than continuous updates, the system periodically evaluates queue depth and congestion status to determine whether to suppress notifications. This reduces data transmission time and network burden while maintaining forwarding precision when needed.
Data Source
AI summary
A media access control address table updating device is provided. The device includes a processor, a storage, a learning controller, a packet generator, and a traffic manager. The traffic manager determines whether to generate a first back pressure signal based on a current traffic corresponding to a plurality of queues. In response to determining that the first back-pressure signal is generated, the traffic manager transmits the first back-pressure signal to the packet generator. In response to receiving the first back pressure signal from the traffic manager, the packet generator stops generating a notification packet corresponding to a notification event.