11575609

Techniques for Congestion Management in a Network

PublishedFebruary 7, 2023
Assigneenot available in USPTO data we have
Technical Abstract

Patent Claims
17 claims

Legal claims defining the scope of protection, as filed with the USPTO.

2

2. The network device of claim 1, wherein the congestion message includes a number of times congestion was detected for the flow at the network device.

3

3. The network device of claim 1, wherein the circuitry is to determine a latency sensitivity of the flow and select a queue for the flow based on the latency sensitivity of the flow.

4

4. The network device of claim 3, wherein the latency sensitivity is based on an indication in an application programming interface (API) by an application associated with the flow.

5

5. The network device of claim 3, wherein the latency sensitivity is based on an indication in a header of a received packet, the indication comprising a traffic class (TC) associated with the flow.

6

6. The network device of claim 3, wherein the latency sensitivity is based on a receive rate of the flow, wherein the circuitry is to identify the flow as a mouse flow and latency sensitive if its receive rate is lower than a threshold or the circuitry is to identify the flow as an elephant flow and latency insensitive if its receive rate is higher than a second threshold.

7

7. The network device of claim 3, wherein the circuitry is to identify the flow as latency sensitive based on usage of accelerator devices for packet processing of packets in the flow.

8

8. The network device of claim 1, wherein the at least one payload that includes the congestion message comprises a requested reduction in transmit rate for the flow and an identification of encoding used to encode the identifier of the congestion causing flow.

9

9. The network device of claim 1, wherein to transmit the congestion message to the source transmitter of packets of the flow, the circuitry to transmit is to form at least one packet with at least one preamble and the at least one preamble includes the congestion message and wherein the preamble that includes the congestion message comprises an identification of the network device that detected congestion and a truncated identifier of the congestion causing flow.

10

10. The network device of claim 1, wherein the congestion message is to assist the source transmitter of packets of the flow to determine an action of whether to reduce a transmit rate of the flow, select another route for the flow to its destination endpoint, or not change a transmit rate or route of the flow and apply the determined action.

11

11. The network device of claim 1, wherein the congestion message is to identify a network device that detected congestion.

12

12. The network device of claim 1, wherein the congestion comprises one or more of: incast level being met or exceeded, packet drop rate being met or exceeded, bandwidth limit being met or exceeded, or queue depth level being met or exceeded.

13

13. The network device of claim 1, comprising a server, rack, or data center.

15

15. The computer-implemented method of claim 14, wherein determining a queue to allocate to one or more packets based on whether the flow is latency sensitive or latency insensitive comprises processing an indication in an application programming interface (API) by an application associated with the flow.

16

16. The computer-implemented method of claim 14, wherein determining a queue to allocate to one or more packets based on whether the flow is latency sensitive or latency insensitive comprises processing an indication in a header of a packet, the indication comprising a traffic class (TC) associated with the flow.

18

18. The computer-implemented method of claim 14, wherein determining a queue to allocate to one or more packets based on whether the flow is latency sensitive or latency insensitive comprises identifying the flow as latency sensitive based on usage of accelerator devices for packet processing of the flow.

21

21. The NIC of claim 20, wherein the at least one payload of the at least one Ethernet packet comprises one or more of: an encoded version of an identifier of the flow causing congestion at the second network device, an identification of encoding used to encode the identifier, or a requested reduction in transmit rate for the flow causing congestion at the second network device.

24

24. The network device of claim 1, wherein the indication of amount of congestion comprises high, medium, or low.

Patent Metadata

Filing Date

Unknown

Publication Date

February 7, 2023

Inventors

Arvind SRINIVASAN
Ramakrishna HUGGAHALLI
Parthasarathy SARANGAM
Sunil AHLUWALIA
Mrittika GANGULI
Malek MUSLEH

Want to explore more patents?

Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.

Citation & reuse

Analysis on this page is generated by Patentable — an AI-powered patent intelligence platform. AI-generated summaries, explanations, and analysis may be reused with attribution and a visible link back to the canonical URL below. Patent abstracts and claims are USPTO public domain.

Cite as: Patentable. “TECHNIQUES FOR CONGESTION MANAGEMENT IN A NETWORK” (11575609). https://patentable.app/patents/11575609

© 2026 Patentable. All rights reserved.

Patentable is a research and drafting-assistant tool, not a law firm, and does not provide legal advice. Documents we generate are drafts for review by a licensed patent attorney.