IP Library Granted Patent US 7,383,349
Granted Patent B2
US 7,383,349 · App. 10/199,238 · Granted Jun 3, 2008

Controlling the flow of packets within a network node utilizing random early detection

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,383,349
App. No.
10/199,238
Granted
Jun 3, 2008
Kind
B2
Abstract

A method and system for controlling the flow of packets within a network node is disclosed. The method comprises receiving packets that are intended for a queue, classifying each of packets into at least one of a plurality of traffic classes and applying class-specific random early detection to each of said packets. The system comprises a classification engine configured to classify packets into one of a plurality of traffic classes, class-specific random early detection (RED) logic configured to apply class-specific RED to each of said packets that have been classified by said classification engine; and a queue for queuing any of said packets that are not dropped in response to application of said class-specific RED.

Claims (44)

1. A method for controlling the flow of packets within a network node comprising:

receiving packets that are intended for a main queue;

classifying each of said packets into at least one of a plurality of traffic classes, wherein the main queue is utilized to physically queue the plurality of traffic classes;

tracking lengths of a plurality of class-specific logical queues within the main queue, each of the class-specific logical queues corresponding to one of the traffic classes;

applying class-specific random early detection (RED) to each of said packets, wherein the class-specific RED is based at least in part on distinct transmission requirements of each of the plurality of traffic classes and the lengths of the class-specific logical queues; wherein applying class-specific RED further comprises: establishing the plurality of class-specific logical queues establishing queue-specific minimum and maximum thresholds and a maximum drop probability for each of said class-specific logical queues; and utilizing said queue-specific minimum and maximum thresholds and said maximum drop probability that are established for said class-specific logical queues in applying class-specific RED.

2. The method of claim 1 wherein applying class-specific RED includes calculating class-specific drop probabilities for said packets.

3. The method of claim 2 wherein applying class-specific RED includes determining whether or not to drop packets in response to each packet's associated class-specific drop probability.

4. The method of claim 3 further comprising queuing, in said main queue, packets that are not dropped in response to application of said class-specific RED.

5. The method of claim 4 wherein said packets are formatted according to the Transmission Control Protocol (TCP).

6. The method of claim 1 further comprising queuing, in said main queue, packets that are not dropped in response to application of said class-specific RED.

7. The method of claim 1 further comprising queuing, in said class-specific logical queues, packets that are not dropped in response to application of said class-specific RED.

8. The method of claim 1 wherein applying class-specific RED further comprises establishing class-specific drop probability weights for each of said plurality of traffic classes.

9. The method of claim 8 wherein applying class-specific RED further comprises:

identifying a corresponding class-specific drop probability weight for one of said received packets; and

utilizing said corresponding class-specific drop probability weight to calculate a class specific drop probability for said one received packet.

10. The method of claim 9 wherein said class-specific drop probability weights represent the relative priorities of said traffic classes.

11. The method of claim 10 wherein a traffic class having a high relative priority has a lower class-specific drop probability weight than a traffic class having a low relative priority.

12. A system for controlling the flow of packets within a network node comprising:

a classification engine configured to classify packets into at least one of a plurality of traffic classes;

class-specific random early detection (RED) logic configured to apply class-specific RED to each of said packets that have been classified by said classification engine;

a main queue for physically queuing any of said packets that are not dropped in response to application of said class-specific RED, wherein the main queue is utilized to queue the plurality of traffic classes;

a plurality of class-specific logical queues to track lengths corresponding to packets of each of the traffic classes in the main queue, wherein the class-specific RED is based at least in part on distinct transmission requirements of each of the plurality of traffic classes and the lengths of the class-specific logical queues; wherein applying class-specific RED further comprises: establishing the plurality of class-specific logical queues establishing queue-specific minimum and maximum thresholds and a maximum drop probability for each of said class-specific logical queues; and utilizing said queue-specific minimum and maximum thresholds and said maximum drop probability that are established for said class-specific logical queues in applying class-specific RED.

13. The system of claim 12 wherein said class-specific RED logic includes logic for calculating class-specific drop probabilities for said packets.

14. The system of claim 13 wherein said class-specific RED logic includes logic for determining whether or not to drop packets in response to each packet's associated class-specific drop probability.

15. The system of claim 14 wherein packets that are not dropped in response to application of said class-specific RED are queued in said main queue.

16. The system of claim 15 wherein said packets are formatted according to the Transmission Control Protocol (TCP).

17. The system of claim 12 wherein packets that are not dropped in response to application of said class-specific RED are queued in said main queue.

18. The system of claim 17 wherein packets that are not dropped in response to application of said class-specific RED are queued in said class-specific logical queues.

19. The system of claim 12 wherein said class-specific RED logic includes logic for maintaining class-specific drop probability weights for each of said plurality of traffic classes.

20. The system of claim 19 wherein said class-specific RED logic includes logic for:

identifying a corresponding class-specific drop probability weight for one of said received packets; and

utilizing said corresponding class-specific drop probability weight to calculate a class specific drop probability for said one received packet.

21. The system of claim 20 wherein said class-specific drop probability weights represent the relative priorities of said traffic classes.

22. The system of claim 21 wherein a traffic class having a high relative priority has a lower class-specific drop probability weight than a traffic class having a low relative priority.

23. A computer readable storage medium containing program instructions for controlling the flow of packets within a network node, the program instructions comprising:

receiving packets that are intended for a main queue;

classifying each of said packets into at least one of a plurality of traffic classes, wherein the main queue is utilized to physically queue the plurality of traffic classes;

tracking lengths of a plurality of class-specific logical queues within the main queue, each of the class-specific logical queues corresponding to one of the traffic classes;

applying class-specific random early detection (RED) to each of said packets, wherein the class-specific RED is based at least in part on distinct transmission requirements of each of the plurality of traffic classes and the lengths of the class-specific logical queues; wherein applying class-specific RED further comprises: establishing the plurality of class-specific logical queues establishing queue-specific minimum and maximum thresholds and a maximum drop probability for each of said class-specific logical queues; and utilizing said queue-specific minimum and maximum thresholds and said maximum drop probability that are established for said class-specific logical queues in applying class-specific RED.

24. The computer readable storage medium of claim 23 wherein applying class-specific RED further comprises establishing class-specific drop probability weights for each of said plurality of traffic classes.

25. The computer readable storage medium of claim 24 wherein applying class-specific RED further comprises:

identifying a corresponding class-specific drop probability weight for one of said received packets; and

utilizing said corresponding class-specific drop probability weight to calculate a class specific drop probability for said one received packet.

26. The computer readable storage medium of claim 25 wherein said class-specific drop probability weights represent the relative priorities of said traffic classes.

Assignments (4)
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033950/0261 →
SECURITY INTEREST Recorded Mar 7, 2013
From: ALCATEL-LUCENT USA INC.
To: CREDIT SUISSE AG
Reel/Frame 030510/0627 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2008
From: RIVERSTONE NETWORKS, INC.
To: LUCENT TECHNOLOGIES INC.
Reel/Frame 020634/0697 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 20, 2002
From: LODHA, SANDEEP
To: RIVERSTONE NETWORKS, INC.
Reel/Frame 013212/0057 →