# US 2022/0045972 A1 · Flow-based management of shared buffer resources

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0045972 A1
- Document ID: US20220045972A1
- Status: Published application
- Kind: A1
- Application number: 16/988,800
- Filed: 2020-08-10
- Published: 2022-02-10
- Earliest claimed: 2020-08-10
- Assignees: Mellanox Technologies Tlv Ltd.
- Applicants: Mellanox Technologies Tlv Ltd.
- Inventors: Niv Aibester; Aviv Kfir; Gil Levy; Liron Mula; Barak Gafni
- Web page: https://patentgrep.com/patent/US20220045972A1

## CPC

- H04L 47/30: in combination with information about buffer occupancy at either end or at transit nodes
- H04L 47/10: Flow control; Congestion control
- H04L 47/2441: relying on flow classification, e.g. using integrated services [IntServ]
- H04L 47/521: {Static queue service slot or fixed bandwidth allocation}
- H04L 47/54: {Loss aware scheduling}
- H04L 49/90: Buffering arrangements
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An apparatus for controlling a Shared Buffer (SB), the apparatus including an interface and a SB controller. The interface is configured to access flow-based data counts and admission states. The SB controller is configured to perform flow-based accounting of packets received by a network device coupled to a communication network, for producing flow-based data counts, each flow-based data count associated with one or more respective flows, and to generate admission states based at least on the flow-based data counts, each admission state being generated from one or more respective flow-based data counts.

## Claims

### Claim 1

Apparatus for controlling a Shared Buffer (SB), the apparatus comprising:
an interface configured to access flow-based data counts and admission states; and
a SB controller configured to:
perform flow-based accounting of packets received by a network device coupled to a communication network for producing flow-based data counts, each flow-based data count associated with one or more respective flows; and
generate admission states based at least on the flow-based data counts, each admission state being generated from one or more respective flow-based data counts.

### Claim 2 (depends on 1)

The apparatus according to claim 1, wherein the SB is comprised in a memory accessible to the SB controller, the memory being external to the apparatus.

### Claim 3 (depends on 1)

The apparatus according to claim 1, wherein the apparatus further comprises a memory, and the SB is comprised in the memory.

### Claim 4 (depends on 1)

The apparatus according to claim 1, further comprising:
multiple ports including an ingress port, configured to connect to the communication network; and
data-plane logic, configured to:
receive a packet from the ingress port;
classify the packet into a respective flow; and
based on one or more admission states that were generated based on the flow-based data counts, decide whether to admit the packet into the SB or drop the packet.

### Claim 5 (depends on 1)

The apparatus according to claim 1, wherein the SB controller is configured to produce an aggregated data count for packets belonging to multiple different flows, and to generate an admission state for the packets of the multiple different flows based on the aggregated data count.

### Claim 6 (depends on 1)

The apparatus according to claim 1, wherein the SB controller configured to produce first and second flow-based data counts for packets belonging to respective first and second different flows, and to generate an admission state for the packets of the first and second flows based on both the first and the second flow-based data counts.

### Claim 7 (depends on 4)

The apparatus according to claim 4, wherein the SB controller is configured to generate multiple admission states based on multiple selected flows, and the data-plane logic is configured to decide whether to admit a packet belonging to one of the selected flows into the SB or drop the packet, based on the multiple admission states.

### Claim 8 (depends on 4)

The apparatus according to claim 4, wherein the data-plane logic is configured to determine for received packets respective egress ports among the multiple ports, ingress priorities and egress priorities, and wherein the SB controller is configured to perform occupancy accounting for (i) Rx data counts associated with respective ingress ports and. ingress priorities, and (ii) Tx data counts associated with respective egress ports and egress priorities, and to generate the admission states based on the flow-based data counts and on at least one of the Rx data counts and the Tx data counts.

### Claim 9 (depends on 8)

The apparatus according to claim 8, wherein the SB controller is configured to perform the flow-based accounting and the occupancy accounting in parallel.

### Claim 10 (depends on 1)

The apparatus according to claim 1, wherein the SB controller is configured to identify for a received packet a corresponding flow-based data count by applying a hash function to one or more fields in a header of the received packet, or (ii) processing the packet using an Access Control mist (ACL).

### Claim 11 (depends on 1)

The apparatus according to claim 1, wherein the SB controller is configured to identify for a received packet a corresponding flow-based data count based on flow-based binding used in a protocol selected from a list of protocols comprising: a tenant protocol, a bridging protocol, a routing protocol and a tunneling protocol.

### Claim 12 (depends on 1)

The apparatus, according to claim 1, wherein the SB controller ls configured to locally monitor selected flow-based data counts, to evaluate performance level of the network device based on the monitored flow-bases data counts, and based on a reporting criterion, to report information indicative of the performance level.

### Claim 13 (depends on 1)

The apparatus according to claim 1, wherein the SB controller is configured to calculate a drop probability based at least on a flow-based data count associated with one or more selected flows, and to generate an admission state for the one or more flows based on the flow-based data count and on the drop probability.

### Claim 14

A method for controlling a Shared Buffer (SB), the method comprising:
in an apparatus comprising a SB controller, accessing flow-based data counts and admission states;
performing flow-based accounting of packets received by a network device coupled to a communication network for producing flow-based data counts, each flow-based data count associated with one or more respective flows; and
generating admission states based at least on the flow-based data counts, each admission state being generated from one or more respective flow-based data counts.

### Claim 15 (depends on 14)

The method according to claim 14, wherein the SB is comprised in a memory accessible to the SB controller, the memory being external to the apparatus.

### Claim 16 (depends on 14)

The method according to claim 14, wherein the apparatus further comprises a memory, and the SB is comprised in the memory.

### Claim 17 (depends on 14)

The method according to claim 14, and comprising:
connecting via multiple ports including an ingress port to the communication network;
receiving a packet from the ingress port;
classifying the packet into a respective flow; and
based on one or more admission states that were generated based on the flow-based data counts, deciding whether to admit the packet into the SB or drop the packet.

### Claim 18 (depends on 14)

The method according to claim 14, wherein performing the flow-based accounting comprises producing an aggregated data count for packets belonging to multiple different flows, and wherein generating the admission states comprises generating an admission state for the packets of the multiple different flows based on the aggregated data count.

### Claim 19 (depends on 14)

The method according to claim 14, wherein performing the flow-based accounting comprises producing first and second flow-based data counts for packets belonging to respective first and second different flows, and wherein generating the admission states comprises generating an admission state for the packets of the first and second flows based on both the first and the second flow-based data counts.

### Claim 20 (depends on 14)

The method according to claim 14, wherein generating the admission states comprises generating multiple admission states based on multiple selected flows, and wherein deciding whether to admit a packet belonging to one of the selected flows into the SB or drop the packet, comprises deciding whether to admit the packet based on the multiple admission states.

### Claim 21 (depends on 14)

The method according to claim 14, and comprising determining for received packets respective egress ports among the multiple ports, ingress priorities and egress priorities, and performing occupancy accounting for (i) Rx data counts associated with respective ingress ports and ingress priorities, and (ii) Tx data counts associated with respective egress ports and egress priorities, and wherein generating the admission states comprises generating the admission states based on the flow-based data counts and on at least one of the Rx data counts and the Tx data counts.

### Claim 22 (depends on 21)

The method according to claim 21, wherein performing the occupancy accounting comprises performing the flow-based accounting and the occupancy accounting in parallel.

### Claim 23 (depends on 14)

The method according to claim 14, and comprising identifying for a received packet a corresponding flow-based data count by (i) applying a hash function to one or more fields in a header of the received packet, or (ii) processing the packet using an Access Control List (ACL).

### Claim 24 (depends on 14)

The method according to claim 14, and comprising identifying for a received packet a corresponding flow-based data count based on flow-based binding used in a protocol selected from a list of protocols comprising: a tenant protocol, a bridging protocol, a routing protocol and a tunneling protocol.

### Claim 25 (depends on 14)

The method according to claim 14, and comprising locally monitoring selected flow-based data counts, evaluating performance level of the network element based on the monitored flow-bases data counts, and based on a reporting criterion, reporting information indicative of the performance level.

### Claim 26 (depends on 14)

The method according to claim 14, and comprising calculating a drop probability based at least on a flow-based data count associated with one or more selected flows, and wherein generating the admission states comprises generating an admission state for the one or more flows, based on the flow-based data count and on the drop probability.
