Mechanism for exchange of routing data between controllers
US-2015381479-A1 · Dec 31, 2015 · US
US9544239B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9544239-B2 |
| Application number | US-201313803144-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 14, 2013 |
| Priority date | Mar 14, 2013 |
| Publication date | Jan 10, 2017 |
| Grant date | Jan 10, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods and systems are disclosed for network congestion management. The methods and systems receive a first packet complying with a first network protocol comprising a first congestion indicator representative of a presence or absence of network congestion and further comprising a first set of data associated with a second network protocol, and provide an indication of the presence or absence of network congestion generated based, at least in part, on the first congestion indicator. The methods and systems also receive a first packet complying with a first network protocol comprising a first set of data associated with a second network protocol, and output a second packet complying with the first network protocol comprising a first congestion indicator representative of a presence of network congestion.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving, at a first component, a first packet complying with a first network protocol, the first packet comprising a first congestion indicator representative of a presence or absence of network congestion associated with a second component configured to output packets complying with the first network protocol, the first packet further comprising a first set of data associated with a second network protocol; decapsulating, based on the first network protocol, the first packet to obtain the first set of data; and outputting, based on the second network protocol and by the first component, a second packet complying with the second network protocol, the second packet including the first set of data and a second congestion indicator representative of the presence or absence of network congestion based, at least in part, on the first congestion indicator, wherein the second congestion indicator is different from the first congestion indicator. 2. The method of claim 1 , further comprising: determining the second congestion indicator representative of the presence or absence of network congestion may not be set; and dropping the first packet based, at least in part, on the determination. 3. The method of claim 1 , wherein the first network protocol is an InfiniBand protocol and the second network protocol is an Ethernet protocol or Internet protocol. 4. The method of claim 3 , wherein the first congestion indicator comprises a forward explicit congestion notification and the second congestion indicator comprises an explicit congestion notification. 5. The method of claim 1 , wherein the first component is an InfiniBand gateway and the second component is an InfiniBand switch. 6. The method of claim 1 , wherein the first packet is an IP over InfiniBand packet, and wherein the second packet is an IP packet. 7. The method of claim 1 , further comprising outputting a third packet complying with the first network protocol, the third packet including a third congestion indicator representative of the presence or absence of network congestion associated with the second component, wherein the first network protocol is an InfiniBand protocol, wherein the second network protocol is an Ethernet protocol or Internet protocol, and wherein the first congestion indicator comprises a forward explicit congestion notification and the third congestion indicator comprises a backward explicit congestion notification. 8. A method comprising: receiving, at a first component, a first packet complying with an InfiniBand protocol, wherein the first packet comprises a first set of data associated with an Ethernet protocol or an Internet protocol; and outputting, at the first component, a second packet complying with the InfiniBand protocol, wherein the second packet comprises an explicit congestion notification (ECN) or a quantized congestion notification (QCN) that is associated with the Ethernet protocol or the Internet protocol, the ECN or QCN is representative of a presence of network congestion associated with the first component. 9. The method of claim 8 , wherein the first component is an InfiniBand switch, the method further comprising: determining the presence of network congestion associated with the first component based, at least in part, on a determination that memory associated with the first component stores more than a predetermined number of packets. 10. The method of claim 8 , wherein the second packet further comprises a second set of data associated with the Ethernet protocol or the Internet protocol, wherein the second set of data comprises the ECN or QCN. 11. A method comprising: receiving, at a network gateway, an InfiniBand packet complying with an InfiniBand protocol, the InfiniBand packet comprising a backward explicit congestion notification (BECN) representative of a presence or absence of network congestion associated with a second component; and outputting, at the network gateway, an Ethernet packet complying with an Ethernet protocol or an Internet Protocol (IP) packet complying with an Internet protocol, the Ethernet packet or the IP packet comprising an explicit congestion notification (ECN) representative of the presence or absence of network congestion associated with the second component based, at least in part, on the BECN. 12. The method of claim 11 , further comprising reducing a rate of packets passing through the network gateway. 13. A system comprising: a receiver configured to: receive a first packet complying with a first network protocol, the first packet comprising a first congestion indicator representative of a presence or absence of network congestion associated with a first component configured to output packets complying with the first network protocol, the first packet further comprising a first set of data associated with a second network protocol; and decapsulate, based on the first network protocol, the first packet to obtain the first set of data; and a transmitter configured to output, based on the second network protocol, a second packet complying with the second network protocol, the second packet including a second congestion indicator representative of the presence or absence of network congestion based, at least in part, on the first congestion indicator, wherein the second congestion indicator is different from the first congestion indicator. 14. The system of claim 13 , wherein the transmitter is further configured to determine the second congestion indicator representative of the presence or absence of network congestion may not be set and drop the first packet based, at least in part, on the determination. 15. The system of claim 13 , wherein the first network protocol is an InfiniBand protocol and the second network protocol is an Ethernet protocol or Internet protocol. 16. The system of claim 15 , wherein the first congestion indicator comprises a forward explicit congestion notification and the second congestion indicator comprises an explicit congestion notification. 17. The system of claim 13 , wherein the first packet is an IP over InfiniBand packet, and wherein the second packet is an IP packet. 18. The system of claim 13 , wherein the transmitter is further configured to output a third packet complying with the first network protocol, the third packet including a third congestion indicator representative of the presence or absence of network congestion associated with the second component, wherein the first network protocol is an InfiniBand protocol, wherein the second network protocol is an Ethernet protocol or Internet protocol, and wherein the first congestion indicator comprises a forward explicit congestion notification and the third congestion indicator comprises a backward explicit congestion notification. 19. A system comprising: a receiver configured to receive a first packet complying with an InfiniBand protocol, wherein the first packet comprises a first set of data associated with an Ethernet protocol or an Internet protocol; and a transmitter configured to output a second packet complying with the InfiniBand protocol, wherein the second packet comprises an explicit congestion notification (ECN) or a quantized congestion notification (QCN) that is associated with the Ethernet protocol or the Internet protocol, the ECN or QCN is representative of a presence of network congestion. 20. The system of claim 19 , further comprising: a memory device; and a processing device configured to determine the presence of n
by embedding flow control information in regular packets, e.g. piggybacking · CPC title
Determining whether packet losses are due to overload or to deterioration of radio communication conditions · CPC title
by discarding or delaying data units, e.g. packets or frames · CPC title
detecting congestion or overload during communication (monitoring arrangements H04L43/00) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.