Framework for traffic engineering in software defined networking
US-9225652-B2 · Dec 29, 2015 · US
US10498656B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10498656-B2 |
| Application number | US-201816028299-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 5, 2018 |
| Priority date | Feb 24, 2014 |
| Publication date | Dec 3, 2019 |
| Grant date | Dec 3, 2019 |
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.
A network device implementing the subject system for end to end flow control may include at least one processor circuit that may be configured to detect that congestion is being experienced by at least one queue of a port and identify another network device that is transmitting downstream traffic being queued at the at least one queue of the port that is at least partially causing the congestion. The at least one processor circuit may be further configured to generate an end to end flow control message that comprises an identifier of the port, the end to end flow control message indicating that the downstream traffic should be flow controlled at the another network device. The at least one processor circuit may be further configured to transmit, out-of-band and through at least one intermediary network device, the end to end flow control message to the another network device.
Opening claim text (preview).
What is claimed is: 1. A network device comprising: a first port communicatively coupled to another network device; a second port directly coupled to an end station device; and a processor configured to: receive upstream traffic from the end station device over the second port; forward the upstream traffic to the other network device over the first port; receive, from the other network device over the first port, an end to end flow control message that indicates that the upstream traffic should be flow controlled by the end station device, wherein the end to end flow control message is addressed to the network device, and the end to end flow control message comprises an identifier of the second port to which the end station device is directly coupled and a device identifier of the end station device; convert the end to end flow control message into a priority flow control message, the priority flow control message comprising a hop-by-hop flow control message corresponding to a link level flow control protocol; and transmit the priority flow control message to the end station device over the second port. 2. The network device of claim 1 , wherein the end to end flow control message further identifies at least one priority of traffic. 3. The network device of claim 2 , wherein the end station device is configured to, upon receipt of the priority flow control message, perform flow control on the upstream traffic associated with the at least one priority of traffic. 4. The network device of claim 2 , wherein the end station device is configured to pause or rate limit the upstream traffic associated with the at least one priority of traffic without pausing or rate limiting other upstream traffic not associated with the at least one priority of traffic. 5. The network device of claim 1 , wherein the other network device comprises a controlling bridge device. 6. The network device of claim 5 , wherein a source address field of the end to end flow control message comprises a first address of the controlling bridge device, and a destination address field of the end to end flow control message comprises a second address of the network device. 7. The network device of claim 6 , wherein the end to end flow control message is received from the controlling bridge device out-of-band via at least one intermediary device that forwards the end to end flow control message from the controlling bridge device to the network device without modifying the end to end flow control message. 8. The network device of claim 7 , wherein the at least one intermediary device comprises an aggregate port extender device in an extended bridge architecture, the network device comprises a port extender device in the extended bridge architecture, and the upstream traffic is received from the end station device by the port extender device over the second port, forwarded by the port extender device, without modifying the upstream traffic, to the aggregate port extender device over the first port, forwarded by the aggregate port extender device, without modifying the upstream traffic, to the controlling bridge device, and received by the controlling bridge device. 9. A non-transitory computer-readable storage medium storing code, the code comprising: code to receive, by a network device, upstream traffic from an end station device over a first port; code to forward the upstream traffic to another network device over a second port; code to receive, from the other network device over the second port, an end to end flow control message that indicates that the upstream traffic should be flow controlled by the end station device; code to convert the end to end flow control message into a priority flow control message the priority flow control message comprising a hop-by-hop flow control message in accordance with a particular flow control specification; and code to transmit the priority flow control message to the end station device over the first port, the end station device supporting the particular flow control specification. 10. The non-transitory computer-readable storage medium of claim 9 , wherein the end to end flow control message is addressed to the network device, and the end to end flow control message comprises an identifier of the second port to which the end station device is directly coupled and a device identifier of the end station device. 11. The non-transitory computer-readable storage medium of claim 10 , wherein the end to end flow control message further identifies at least one priority of traffic. 12. The non-transitory computer-readable storage medium of claim 11 , wherein the end station device is configured to, upon receipt of the priority flow control message, perform flow control on the upstream traffic associated with the at least one priority of traffic. 13. The non-transitory computer-readable storage medium of claim 12 , wherein the end station device is configured to pause or rate limit the upstream traffic associated with the at least one priority of traffic without pausing or rate limiting other upstream traffic not associated with the at least one priority of traffic. 14. The non-transitory computer-readable storage medium of claim 9 , wherein the other network device comprises a controlling bridge device. 15. The non-transitory computer-readable storage medium of claim 14 , wherein a source address field of the end to end flow control message comprises a first address of the controlling bridge device, and a destination address field of the end to end flow control message comprises a second address of the network device. 16. The non-transitory computer-readable storage medium of claim 15 , wherein the end to end flow control message is received from the controlling bridge device out-of-band via at least one intermediary device that forwards the end to end flow control message from the controlling bridge device to the network device without modifying the end to end flow control message. 17. The non-transitory computer-readable storage medium of claim 16 , wherein the at least one intermediary device comprises an aggregate port extender device in an extended bridge architecture, the network device comprises a port extender device in the extended bridge architecture, and the upstream traffic is received from the end station device by the port extender device over the second port, forwarded by the port extender device, without modifying the upstream traffic, to the aggregate port extender device over the first port, forwarded by the aggregate port extender device, without modifying the upstream traffic, to the controlling bridge device, and received by the controlling bridge device. 18. A method comprising: detecting that congestion is being experienced by at least one queue of a port of a network device; determining that the congestion is being caused at least in part by upstream traffic generated by an end station device that is coupled to another network device, the other network device being communicatively coupled to the network device; generating an end to end flow control message that indicates that the upstream traffic should be flow controlled by the end station device; and transmitting the end to end flow control message to the network device over the port, wherein, upon receipt of the end to end flow control message by the network device, the end to end flow control message is converted into a priority flow control message that is transmitted to the end station device, the priority flow control message comprising a hop-by-hop flow control message.
End to end · CPC title
Head of Line Blocking Avoidance · CPC title
by diverting traffic away from congested entities · CPC title
Backpressure · CPC title
Overload detection or protection within a single switching element · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.