Congestion management scheme

• US 5,822,300 A
• Filed: 04/02/1996
• Issued: 10/13/1998
• Est. Priority Date: 04/02/1996
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Compaq Computer Corporation (HP Inc.)
• Inventors: Johnson, Brian W., Hoang, Hieu M.
• Primary Examiner(s): Chin, Wellington
• Assistant Examiner(s): VU, HUY DUY
• Application Number:
  US08/627,692
• Time in Patent Office: 924 Days
• Field of Search: 370/229, 370/230, 370/231, 370/235, 370/236, 370/239, 370/240, 370/252, 370/400, 370/401, 370/402, 370/403, 370/404, 370/405, 370/410, 370/412, 370/413, 370/414, 370/415, 370/416, 370/417, 370/418, 370/428, 370/474, 370/476, 370/422, 370/423, 370/424, 370/425, 370/420, 370/421, 370/426, 370/407, 395/200.13, 395/877, 395/879, 395/849, 395/200.05, 395/200.02, 395/250
• US Class Current: 370/229
• CPC Class Codes: H04L 2012/445 with switching in a hub, e.g. ETHERNET switch
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/30 in combination with information about buffer occupancy at either end or at transit nodes

Abstract

A congestion management scheme for managing traffic in a data communication system having a plurality of port blocks at least one of which may be connected to a communication medium, the congestion management scheme including a structure for determining whether a sender is congested, a structure for determining whether a receiver is congested, and a structure for determining whether a RX FIFO is congested and a structure for determining a memory buffer, associated with at least one of the sender and the receiver, is congested. The congestion scheme further includes a structure for handling traffic by taking one of the preferred actions depending upon the congestion indicators.

Claims

1. A system for managing congestion within a data communication system, said data communication system including a sender and a receiver between which traffic may be transmitted, said system for managing congestion comprising:

(a) a structure for determining whether said sender is congested;

(b) a structure for determining whether said receiver is congested; and

(c) a structure for handling said traffic based upon whether said sender is congested and whether said receiver is congested, wherein said structure for handling handles said traffic as follows;

(i) if said sender is congested and said receiver is not congested, then transmitting said traffic;

(ii) if said sender is not congested and said receiver is not congested, then transmitting said traffic;

(iii) if said sender is not congested and said receiver is congested, then holding said traffic; and

(iv) if said sender is congested and if said receiver is congested, then dropping said traffic.

2. The system as recited in claim 1, and further comprising:

(a) a first-in first-out (FIFO) structure;

(b) a structure for determining whether said FIFO structure is congested; and

wherein said structure for handling said traffic transmits said traffic if said sender is congested and said receiver is not congested and said FIFO structure is not congested.

3. The system as recited in claim 2, wherein said traffic may be priority traffic, and further wherein if said sender is congested, said receiver is not congested and said FIFO structure is congested:

(a) said structure for handling traffic holds said traffic if said traffic is priority traffic; and

otherwise

(b) said structure for handling said traffic discards said traffic.

4. The system as recited in claim 3, wherein if said sender is congested, said receiver is congested and said FIFO structure is congested:

(a) said structure for handling traffic holds said traffic if said traffic is priority traffic; and

otherwise

(b) said structure for handling said traffic discards said traffic.

5. The system as recited in claim 4, wherein if said sender is congested, said receiver is congested and said FIFO structure is not congested:

(a) said structure for handling traffic transmits said traffic if said traffic is priority traffic; and

otherwise

(b) said structure for handling said traffic discards said traffic.

6. The system as recited in claim 5, wherein said structure for handling traffic transmits said traffic if said sender is not congested, said receiver is not congested and said FIFO structure is not congested.

7. The system as recited in claim 6, wherein said structure for handling traffic holds said traffic if said sender is not congested, said receiver is not congested and said FIFO structure is congested.

8. The system as recited in claim 7, wherein said structure for handling traffic holds said traffic if said sender is not congested, said receiver is congested and said FIFO structure is congested.

9. The system as recited in claim 8, wherein if said sender is not congested, said receiver is congested and said FIFO structure is not congested:

(a) said structure for handling traffic transmits said traffic if said traffic is priority traffic; and

otherwise

(b) said structure for handling said traffic holds said traffic.

10. The system as recited in claim 1, wherein said traffic comprises at least one cell, said at least one cell for holding data information and management information, and said system further comprising a bus, said bus for transporting said traffic.

11. The system as recited in claim 1, wherein said sender further comprises at least one ring data structure, said at least one ring data structure for facilitating out-going transmission of said traffic.

12. The system as recited in claim 1, wherein said receiver further comprises at least one ring data structure, said at least one ring data structure for facilitating in-coming reception of said traffic.

13. The system as recited in claim 1, wherein said sender is operably connected to a communication medium.

14. The system as recited in claim 13, wherein said receiver is operably connected to said communication medium.

15. The system as recited in claim 14, wherein said communication medium comprises an Ethernet medium.

16. The system as recited in claim 14, wherein said communication medium comprises a fiber distributed data interface medium.

17. The system as recited in claim 1, wherein said structure for determining whether said sender is congested comprises a sender-congestion-indicator.

18. The system as recited in claim 1, wherein said structure for determining whether said receiver is congested comprises a receiver-congestion-indicator.

19. The system as recited in claim 2, wherein said structure for determining whether said FIFO structure is congested comprises a FIFO-congestion-indicator.

20. The system as recited in claim 1, and further comprising:

(a) a first-in first-out (FIFO) structure; and

(b) a structure for determining whether said FIFO structure is congested, wherein if said sender is congested, said receiver is not congested and said FIFO structure is congested, said structure for handling traffic holds said traffic if said traffic is priority traffic, and otherwise said structure for handling said traffic discards said traffic.

21. The system as recited in claim 1, and further comprising:

(a) a first-in first-out (FIFO) structure;

(b) a structure for determining whether said FIFO structure is congested, wherein if said sender is congested, said receiver is congested and said FIFO structure is congested, said structure for handling traffic holds said traffic if said traffic is priority traffic, and otherwise said structure for handling said traffic discards said traffic.

22. A method for managing congestion within a data communication system, said data communication system including a sender and a receiver between which traffic may be transmitted, said method for managing congestion comprising the steps of:

(a) determining whether said sender is congested;

(b) determining whether said receiver is congested; and

(c) handling said traffic based upon whether said sender is congested and whether said receiver is congested, wherein;

(i) if said sender is congested and said receiver is not congested, then transmitting said traffic;

(ii) if said sender is not congested and said receiver is not congested, then transmitting said traffic;

(iii) if said sender is not congested and said receiver is congested, then holding said traffic; and

(iv) if said sender is congested and if said receiver is congested, then dropping said traffic.