# US 2025/0219952 A1 · Systems and methods for quality of service treatment of network traffic for different user interface elements

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

- Number: US 2025/0219952 A1
- Document ID: US20250219952A1
- Status: Published application
- Kind: A1
- Application number: 18/401,878
- Filed: 2024-01-02
- Published: 2025-07-03
- Earliest claimed: 2024-01-02
- Assignees: Verizon Patent and Licensing Inc.
- Applicants: Verizon Patent and Licensing Inc.
- Inventors: Deepak Majjiga
- Web page: https://patentgrep.com/patent/US20250219952A1

## CPC

- H04L 47/2441: relying on flow classification, e.g. using integrated services [IntServ]
- G06F 3/0481: based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files}
- G06F 9/451: Execution arrangements for user interfaces
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L 67/50: Network services
- 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)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A device described herein may maintain a model associating sets of traffic attributes with respective sets of attributes of user interface (“UI”) elements; receive a request to associate a particular UI element with a particular set of Quality of Service (“QoS”) parameters; identify a first set of attributes of the particular UI element; identify that the first set of attributes, of the particular UI element, matches a second set of attributes of UI elements included in the model; and identify a particular set of traffic attributes indicated in the model as being associated with the second set of attributes of UI element attributes. The device may identify traffic associated with the particular set of traffic attributes; and may process the identified traffic in accordance with the particular set of QoS parameters indicated in the request, based on identifying that the traffic is associated with the particular set of traffic attributes.

## Claims

### Claim 1

A device, comprising:
one or more processors configured to:
maintain one or more models associating sets of traffic attributes with respective sets of attributes of user interface (“UI”) elements;
receive a request to associate a particular UI element of a UI, associated with an application executing at a User Equipment (“UE”), with a particular set of Quality of Service (“QoS”) parameters;
identify a first set of attributes of the particular UI element indicated in the request;
identify that the first set of attributes, of the particular UI element, matches a second set of attributes of UI elements included in the one or more models;
identify a particular set of traffic attributes indicated in the one or more models as being associated with the second set of attributes of UI element attributes;
identify traffic associated with the particular set of traffic attributes; and
process the identified traffic in accordance with the particular set of QoS parameters indicated in the request, based on identifying that the traffic is associated with the particular set of traffic attributes.

### Claim 2 (depends on 1)

The device of claim 1, wherein the traffic is first traffic, wherein the one or more processors are further configured to:
identify second traffic that is associated with different traffic attributes than the particular set of traffic attributes; and
process the second traffic in accordance with a different set of QoS parameters, based on identifying that the second traffic is associated with the different traffic attributes.

### Claim 3 (depends on 2)

The device of claim 2, wherein the first and second traffic are associated with a same application.

### Claim 4 (depends on 1)

The device of claim 1, wherein the traffic attributes include at least one of:
a Fully Qualified Domain Name (“FQDN”) associated with an endpoint with which the traffic is associated, or
a protocol associated with the traffic.

### Claim 5 (depends on 1)

The device of claim 1, wherein the sets of QoS parameters include at least one of:
one or more network slice identifiers, or
one or more UE Route Selection Policy (“URSP”) rule identifiers.

### Claim 6 (depends on 1)

The device of claim 1,
wherein receiving the request to associate the particular UI element with the particular set of QoS parameters includes an image depicting the particular UI element, and
wherein identifying the first set of attributes of the particular UI element includes utilizing one or more image recognition techniques to identify the first set of attributes of the particular UI element.

### Claim 7 (depends on 1)

The device of claim 1, wherein processing the identified traffic in accordance with the particular set of QoS parameters includes:
marking the traffic with one or more indicators of the particular set of QoS parameters; and
forwarding the marked traffic to a network, wherein the network further processes the marked traffic in accordance with the particular set of QoS parameters based on the marking.

### Claim 8

A non-transitory computer-readable medium, storing a plurality of processor-executable instructions to:
maintain one or more models associating sets of traffic attributes with respective sets of attributes of user interface (“UI”) elements;
receive a request to associate a particular UI element of a UI, associated with an application executing at a User Equipment (“UE”), with a particular set of Quality of Service (“QoS”) parameters;
identify a first set of attributes of the particular UI element indicated in the request;
identify that the first set of attributes, of the particular UI element, matches a second set of attributes of UI elements included in the one or more models;
identify a particular set of traffic attributes indicated in the one or more models as being associated with the second set of attributes of UI element attributes;
identify traffic associated with the particular set of traffic attributes; and
process the identified traffic in accordance with the particular set of QoS parameters indicated in the request, based on identifying that the traffic is associated with the particular set of traffic attributes.

### Claim 9 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the traffic is first traffic, wherein the plurality of processor-executable instructions further include processor-executable instructions to:
identify second traffic that is associated with different traffic attributes than the particular set of traffic attributes; and
process the second traffic in accordance with a different set of QoS parameters, based on identifying that the second traffic is associated with the different traffic attributes.

### Claim 10 (depends on 9)

The non-transitory computer-readable medium of claim 9, wherein the first and second traffic are associated with a same application.

### Claim 11 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the traffic attributes include at least one of:
a Fully Qualified Domain Name (“FQDN”) associated with an endpoint with which the traffic is associated, or
a protocol associated with the traffic.

### Claim 12 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the sets of QoS parameters include at least one of:
one or more network slice identifiers, or
one or more UE Route Selection Policy (“URSP”) rule identifiers.

### Claim 13 (depends on 8)

The non-transitory computer-readable medium of claim 8,
wherein receiving the request to associate the particular UI element with the particular set of QoS parameters includes an image depicting the particular UI element, and
wherein identifying the first set of attributes of the particular UI element includes utilizing one or more image recognition techniques to identify the first set of attributes of the particular UI element.

### Claim 14 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein processing the identified traffic in accordance with the particular set of QoS parameters includes:
marking the traffic with one or more indicators of the particular set of QoS parameters; and
forwarding the marked traffic to a network, wherein the network further processes the marked traffic in accordance with the particular set of QoS parameters based on the marking.

### Claim 15

A method, comprising:
maintaining one or more models associating sets of traffic attributes with respective sets of attributes of user interface (“UI”) elements;
receiving a request to associate a particular UI element of a UI, associated with an application executing at a User Equipment (“UE”), with a particular set of Quality of Service (“QoS”) parameters;
identifying a first set of attributes of the particular UI element indicated in the request;
identifying that the first set of attributes, of the particular UI element, matches a second set of attributes of UI elements included in the one or more models;
identifying a particular set of traffic attributes indicated in the one or more models as being associated with the second set of attributes of UI element attributes;
identifying traffic associated with the particular set of traffic attributes; and
processing the identified traffic in accordance with the particular set of QoS parameters indicated in the request, based on identifying that the traffic is associated with the particular set of traffic attributes.

### Claim 16 (depends on 15)

The method of claim 15, wherein the traffic is first traffic, the method further comprising:
identifying second traffic that is associated with different traffic attributes than the particular set of traffic attributes; and
processing the second traffic in accordance with a different set of QoS parameters, based on identifying that the second traffic is associated with the different traffic attributes.

### Claim 17 (depends on 16)

The method of claim 16, wherein the first and second traffic are associated with a same application.

### Claim 18 (depends on 15)

The method of claim 15,
wherein the traffic attributes include at least one of:
a Fully Qualified Domain Name (“FQDN”) associated with an endpoint with which the traffic is associated, or
a protocol associated with the traffic; and
wherein the sets of QoS parameters include at least one of:
one or more network slice identifiers, or
one or more UE Route Selection Policy (“URSP”) rule identifiers.

### Claim 19 (depends on 15)

The method of claim 15,
wherein receiving the request to associate the particular UI element with the particular set of QoS parameters includes an image depicting the particular UI element, and
wherein identifying the first set of attributes of the particular UI element includes utilizing one or more image recognition techniques to identify the first set of attributes of the particular UI element.

### Claim 20 (depends on 15)

The method of claim 15, wherein processing the identified traffic in accordance with the particular set of QoS parameters includes:
marking the traffic with one or more indicators of the particular set of QoS parameters; and
forwarding the marked traffic to a network, wherein the network further processes the marked traffic in accordance with the particular set of QoS parameters based on the marking.
