Scalable flow and congestion control with OpenFlow

• US 9,444,748 B2
• Filed: 03/15/2013
• Issued: 09/13/2016
• Est. Priority Date: 03/15/2013
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: DeCusatis, Casimer, Fabrizio, Petrini, Krishnamurthy, Rajaram B.
• Primary Examiner(s): Oh, Andrew
• Application Number:
  US13/833,952
• Publication Number:
  US 20140269320A1
• Time in Patent Office: 1,278 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/11 Identifying congestion
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/21 using leaky-bucket
• CPC Class Codes: H04L 47/215 using token-bucket
• CPC Class Codes: H04L 47/25 with rate being modified by the source upon detecting a change of network conditions
• CPC Class Codes: H04L 47/26 using explicit feedback to the source, e.g. choke packets

Abstract

A method of performing congestion management in a network is provided. The method includes monitoring a congestion status at a switch in the network. It is determined at the switch that the congestion status indicates that there is congestion at the switch. Based on the congestion being related to data received at the switch from a source at a first rate, a first message is transmitted from the switch to the source requesting the source to send the data at a second rate that is slower than the first rate. Based on the congestion being related to data requests received at the switch from a destination at third rate, a second message is transmitted from the switch to the destination requesting the destination to request the data at a fourth rate slower than the third rate.

Claims

1. A system for performing congestion management in a network, the system comprising:

a switch configured to connect to the network, the switch comprising;

a memory having computer readable computer instructions; and

a processor for executing the computer readable instructions, the instructions including;

monitoring both data packets and data requests received at the switch over one or more links in the network;

based on the monitoring, determining a congestion status at the switch;

determining that the congestion status indicates that there is congestion at the switch, the determining including examining a plurality of flags in a header field of an entry corresponding to a flow in a flow table at the switch, the plurality of flags including a forward congestion that when set indicates that a source of data for the data flow is sending data more quickly than the switch can process the data, and a backward congestion flag that when set indicates that a destination of data for the data flow is sending data requests more quickly than the switch can process the data requests;

based on the forward congestion flag being set and congestion being related to data packets received at the switch from the source at a first rate, transmitting a first message to the source requesting the source to send the data at a second rate that is slower than the first rate; and

based on the backward congestion flag being set and congestion being related to data requests received at the switch from the destination at a third rate, transmitting a second message to the destination requesting the destination to send the data requests at a fourth rate that is slower than the third rate.

2. The system of claim 1, wherein the instructions further include:

based on transmitting the first message;

monitoring the congestion status; and

based on determining that the congestion status indicates that there is no longer congestion at the switch related to data packets received at the switch from the source, transmitting a third message to the source requesting the source to send the data packets at a fifth rate that is faster than the second rate.

3. The system of claim 1, wherein the instructions further include:

based on transmitting the second message;

monitoring the congestion status; and

based on determining that the congestion status indicates that there is no longer congestion at the switch related to data requests received at the switch from the destination, transmitting a fourth message to the destination requesting the destination to send the data requests at a sixth rate that is faster than the fourth rate.

4. The system of claim 1, wherein the switch, source and destination are OpenFlow switches and the network is an OpenFlow network.

5. The system of claim 1, wherein the switch is an OpenFlow switch.

6. The apparatus of claim 5, wherein the forward congestion flag is set to indicate congestion at the switch related to data packets received at the switch based on a queue at the switch that stores the data packets exceeding a specified capacity.

7. The apparatus of claim 5, wherein the backward congestion flag is set to indicate congestion at the switch related to data requests received at the switch based on a queue at the switch that stores the data requests exceeding a specified capacity.