# US 2025/0219951 A1 · Flow management based on stream classification service negotiations and policies

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

- Number: US 2025/0219951 A1
- Document ID: US20250219951A1
- Status: Published application
- Kind: A1
- Application number: 18/656,475
- Filed: 2024-05-06
- Published: 2025-07-03
- Earliest claimed: 2023-12-28
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Binita Gupta; Brian Hart; Malcolm Smith; Jerome Henry
- Web page: https://patentgrep.com/patent/US20250219951A1

## CPC

- H04L 47/2408: for supporting different services, e.g. a differentiated services [DiffServ] type of service
- H04L 47/12: Avoiding congestion; Recovering from congestion
- H04L 47/2441: relying on flow classification, e.g. using integrated services [IntServ]
- H04L 47/6215: {Individual queue per QOS, rate or priority}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In embodiments described herein, one or more stream classifications are incorporated into a plurality of flows within a network. These flows can have a number of characteristics associated with it, such as, but not limited to quality of service requirements that can dictate how the flow should be processed. A device associated with the flow can transmit a stream classification service (SCS) request. This SCS request can be received and processed to determine a scheduling behavior that should be adopted by various network device/nodes associated with the flow. The scheduling behavior can be transmitted to those network devices which can then modify the processing of the flow(s). In some cases, the network device can classify the packets associated with the flow(s) and prioritize them. In additional cases, the network device can generate one or more new queues that can be configured to best serve the requirements of the flow.

## Claims

### Claim 1

A device, comprising:
a processor;
at least one network interface controller configured to provide access to a network; and
a memory communicatively coupled to the processor, wherein the memory comprises a flow management logic that is configured to:
receive a stream classification service (SCS) request;
select a flow based on the SCS request;
identify a flow policy;
determine a scheduling behavior related to the flow policy; and
transmit the scheduling behavior to one or more network devices.

### Claim 2 (depends on 1)

The device of claim 1, wherein the SCS request is received from a client device.

### Claim 3 (depends on 1)

The device of claim 1, wherein determining a scheduling behavior is based on quality of service characteristics of the flow.

### Claim 4 (depends on 3)

The device of claim 3, wherein the quality of service is associated with at least one application.

### Claim 5 (depends on 1)

The device of claim 1, wherein the flow management logic is further configured to generate a classification based on at least the flow policy.

### Claim 6 (depends on 5)

The device of claim 5, wherein the classification is associated with an internet protocol header.

### Claim 7 (depends on 6)

The device of claim 6, wherein the classification is a differentiated services code point marking.

### Claim 8 (depends on 7)

The device of claim 7, wherein the marking is applied to an upstream flow.

### Claim 9 (depends on 1)

The device of claim 1, wherein the flow management logic is further configured to generate one or more queues in response to the scheduling behavior.

### Claim 10 (depends on 9)

The device of claim 9, wherein the one or more queues are generated in response to one or more quality of service characteristics of the flow.

### Claim 11

A device, comprising:
a processor;
at least one network interface controller configured to provide access to a network; and
a memory communicatively coupled to the processor, wherein the memory comprises a flow management logic that is configured to:
determine a flow for classification;
classify the flow;
receive a scheduling behavior for the flow; and
schedule the flow based on the scheduling behavior.

### Claim 12 (depends on 11)

The device of claim 11, wherein the flow management logic is further configured to analyze the scheduling behavior.

### Claim 13 (depends on 11)

The device of claim 11, wherein the flow management logic is further configured to prioritize the scheduling of the flow based on the analysis of the scheduling behavior.

### Claim 14

A method of managing flows, comprising:
establishing a connection to a network;
receiving a stream classification service (SCS) request from a network device on the network;
selecting a flow based on the SCS request;
identifying a flow policy based on the SCS request;
determining a scheduling behavior based on the flow policy; and
transmitting the scheduling behavior to the network device.

### Claim 15 (depends on 14)

The method of claim 14, wherein the method further includes forwarding the scheduling behavior to additional network devices on a network.

### Claim 16 (depends on 15)

The method of claim 15, wherein the additional network devices are not connected via a wireless connection.

### Claim 17 (depends on 16)

The method of claim 16, wherein the additional network devices are routing nodes.

### Claim 18 (depends on 14)

The method of claim 14, wherein the method further includes generating one or more classifications based on the scheduling behavior.

### Claim 19 (depends on 14)

The method of claim 14, wherein the method further includes generating one or more additional queues in response to the scheduling behavior.

### Claim 20 (depends on 19)

The method of claim 19, wherein the one or more additional queues are generated based on at least a quality of service characteristic associated with the SCS request.
