Packet-Type Based WRED Protection Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing congestion control mechanisms in packet communication networks, such as RED and WRED, do not effectively differentiate between packet types, leading to unnecessary drops of low-priority packets that can impact Quality of Service (QoS) and system performance.
Innovation Solution
A network element with logic that classifies packets and selectively assigns lower drop probabilities to predefined low-priority packets, such as TCP-SYN, TCP-FIN, and non-congestion-causing flows, while using a Weighted Random Early Detection (WRED) process to avoid congestion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a Weighted Random Early Detection (WRED) process is used to randomly drop packets to avoid congestion, then congestion control is improved, but low-priority packets such as TCP-SYN and TCP-FIN packets are unnecessarily dropped, worsening Quality of Service
Solution Approach 1:
The patent applies local quality by differentiating packet drop probabilities based on packet type. Instead of uniformly dropping packets, the system assigns different drop probabilities to different packet classes: TCP-SYN and TCP-FIN packets are excluded from dropping (0% probability), while other packets follow standard WRED probability curves. This localized differentiation resolves the contradiction by protecting critical control packets while maintaining congestion control for regular data traffic.
Solution Approach 2:
The patent changes the drop probability parameter dynamically based on packet type identification. The logic detects packet types (TCP-SYN, TCP-FIN, regular data packets) and adjusts the drop probability parameter accordingly: setting it to 0 for control packets and applying weighted probabilities for data packets. This parameter adaptation resolves the contradiction between congestion control and QoS protection.
2Productivity
If standard RED or WRED algorithms are applied uniformly to all packet classes, then congestion avoidance is achieved, but Quality of Service for critical packets deteriorates due to indiscriminate dropping
Solution Approach 1:
The patent implements local quality by creating distinct drop probability profiles for different packet types. Critical packets (TCP-SYN, TCP-FIN) receive a local quality treatment of zero drop probability, while regular data packets receive standard WRED treatment. This localized differentiation ensures congestion avoidance for bulk traffic while protecting QoS for control traffic.
Solution Approach 2:
The patent segments the packet stream into different classes based on packet type identification. The logic separates TCP-SYN packets, TCP-FIN packets, and regular data packets into distinct categories, applying different WRED policies to each segment. This segmentation resolves the contradiction by allowing targeted congestion management for data packets while exempting control packets from dropping.
3Productivity
If packet dropping is increased to manage congestion more effectively, then network throughput is improved, but system performance and QoS deteriorate due to loss of critical control packets
Solution Approach 1:
The patent changes the drop probability parameter based on packet type detection. For TCP-SYN and TCP-FIN packets, the parameter is set to 0 (no dropping), while for regular data packets, standard WRED probability parameters are applied. This parameter adaptation allows aggressive congestion control for data traffic while protecting system performance by preserving control packet delivery.
Solution Approach 2:
The patent applies local quality by providing differential protection: critical control packets (TCP-SYN, TCP-FIN) receive zero drop probability treatment, while regular data packets receive full WRED treatment. This localized quality assurance resolves the contradiction by maximizing throughput control for data while ensuring system performance through control packet preservation.
Data Source
AI summary
A network element includes multiple ports and logic. The multiple ports are configured to serve as ingress ports and egress ports for receiving and transmitting packets from and to a network. The logic is configured to queue the packets received from the ingress ports, run a packet-dropping process that randomly drops one or more of the queued packets to avoid congestion, while detecting and excluding from the packet-dropping process, at least probabilistically, packets belonging to a predefined packet type, and forward the queued packets, which were not dropped, to the egress ports.