# US 2025/0219955 A1 · Signaling to identify a stream classification service (scs) flow using a fully qualified domain name/uniform resource locator or an application identifier

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

- Number: US 2025/0219955 A1
- Document ID: US20250219955A1
- Status: Published application
- Kind: A1
- Application number: 18/786,385
- Filed: 2024-07-26
- Published: 2025-07-03
- Earliest claimed: 2023-12-30
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Binita Gupta; Brian D. Hart; Malcolm M. Smith
- Web page: https://patentgrep.com/patent/US20250219955A1

## CPC

- H04L 47/2483: involving identification of individual flows
- H04L 47/2475: for supporting traffic characterised by the type of applications
- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04W 48/16: Discovering, processing access restriction or access information
- H04L 61/4511: using domain name system [DNS]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Signaling to identify a Stream Classification Service (SCS) flow using a Fully Qualified Domain Name (FQDN)/Uniform Resource Locator (URL) or an application Identifier (ID) may be provided. An Access Point (AP) may receive a SCS request from a station for a SCS flow. The SCS request may include a flow identifier for the SCS flow. The flow identifier may include a FDQN or an application ID for identifying the SCS flow. The AP may verify a network policy associated with the flow identifier for the SCS flow. The AP may process the SCS request for the SCS flow based on the network policy.

## Claims

### Claim 1

A method comprising:
receiving, by an Access Point (AP), a Stream Classification Service (SCS) request from a station for a SCS flow, the SCS request comprising a flow identifier for the SCS flow, wherein the flow identifier comprises a Fully Qualified Domain Name (FDQN) or an application Identifier (ID) for identifying the SCS flow;
verifying, by the AP, a network policy associated with the flow identifier for the SCS flow; and
processing, by the AP, the SCS request for the SCS flow based on the network policy.

### Claim 2 (depends on 1)

The method of claim 1, wherein processing the SCS request comprises determining a quality of service characteristics associated with the flow identifier received in the SCS request.

### Claim 3 (depends on 1)

The method of claim 1, wherein the FDQN or the application ID is provided in a sub-element of a SCS descriptor element of the SCS request.

### Claim 4 (depends on 1)

The method of claim 1, wherein the FDQN or the application ID is provided in a public identifier FQDN sub-element in a SCS descriptor element of the SCS request.

### Claim 5 (depends on 1)

The method of claim 1, wherein the FDQN or the application ID is provided in a classifier type 10 field of a traffic classifier element of the SCS request.

### Claim 6 (depends on 1)

The method of claim 1, wherein verifying the network policy associated with the flow identifier for the SCS flow comprises:
determining the network policy associated with the flow identifier; and
verifying that the network policy associated with the flow identifier allows the SCS flow.

### Claim 7 (depends on 1)

The method of claim 1, wherein processing the SCS request for the SCS flow comprises determining that the AP can support QoS resources requested for the SCS flow.

### Claim 8 (depends on 1)

The method of claim 1, wherein the application ID comprises an operating system assigned application ID and an operating system type.

### Claim 9

A method comprising:
receiving, by an Access Point (AP), a first Stream Classification Service (SCS) request for a first SCS flow, the first SCS request comprising a first resource allocation and retention priority and a Quality of Service (QOS) resources for the first SCS flow;
determining, by the AP, that there is a conflict for the QoS resources between the first SCS flow and a second SCS flow, wherein the second SCS flow is associated with a second resource allocation and retention priority; and
prioritizing, by the AP, allocation of the QoS resources for the first SCS flow and the second SCS flow based on the first resource allocation and retention priority and the second resource allocation and retention priority.

### Claim 10 (depends on 9)

The method of claim 9, wherein each of the first resource allocation and retention priority and the second resource allocation and retention priority is assigned based on a service level agreement associated with the first SCS flow and the second SCS flow respectively.

### Claim 11 (depends on 9)

The method of claim 9, wherein each of the first resource allocation and retention priority and the second resource allocation and retention priority is assigned based on a priority of an application or a device associated with the first SCS flow and the second SCS flow respectively.

### Claim 12 (depends on 9)

The method of claim 9, wherein the first SCS request further comprises a first resource preemption capability parameter, wherein the first resource preemption capability parameter defines whether the first SCS flow has a capability to preempt other QoS resources from other SCS flows.

### Claim 13 (depends on 12)

The method of claim 12, wherein the first resource preemption capability parameter is either enabled or disabled, and wherein when enabled, the first SCS flow has the capability to preempt the other QoS resources from a lower priority SCS flow.

### Claim 14 (depends on 9)

The method of claim 9, wherein the first SCS request further comprises a first resource preemption vulnerability parameter, wherein the first resource preemption vulnerability parameter defines whether the first SCS flow is subject to loosing already assigned QoS resources to higher priority SCS flows.

### Claim 15 (depends on 14)

The method of claim 14, wherein the first resource preemption vulnerability parameter is enabled for SCS flows with no associated service level agreement.

### Claim 16

A method comprising:
receiving, by an Access Point (AP), a Stream Classification Service (SCS) request from a station for an uplink stream;
determining, by the AP, that the SCS request does not include a traffic classifier information for the uplink stream; and
sending, by the AP, a SCS response comprising a status code to the station in response to determining that the SCS request does not comprise the traffic classifier information for the uplink stream, the status code comprising one of:
a first status code indicating to the station that the SCS request is being rejected for lack of the traffic classifier information, and
a second status code indicating to the station that the SCS request is being accepted along with assigned quality of service characteristics.

### Claim 17 (depends on 16)

The method of claim 16, wherein sending, by the AP, the SCS response comprising the status code in response to determining that the SCS request does not include the traffic classifier information for the uplink stream comprises:
sending, by the AP, the SCS response comprising the first status code in response to determining that:
the SCS request does not include the traffic classifier information for the uplink stream, and
a network policy requires the traffic classifier information to accept the SCS request.

### Claim 18 (depends on 16)

The method of claim 16, wherein sending, by the AP, the SCS response comprising the status code in response to determining that the SCS request does not include the traffic classifier information for the uplink stream comprises:
sending, by the AP, the SCS response comprising the second status code in response to determining that:
the SCS request does not include the traffic classifier information for the uplink stream, and
a network policy does not require the traffic classifier information to accept the SCS request.

### Claim 19 (depends on 16)

The method of claim 16, further comprising sending, by the AP, the SCS response comprising a third status code to the station in response to determining that the SCS request does not comprise a differentiated service code point value in the SCS request.

### Claim 20 (depends on 16)

The method of claim 16, wherein the assigned quality of service characteristics is a default quality of service characteristics defined for SCS requests with no quality of service characteristics.
