# US 2025/0031090 A1 · Support for application data unit based quality of service

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

- Number: US 2025/0031090 A1
- Document ID: US20250031090A1
- Status: Published application
- Kind: A1
- Application number: 18/710,589
- Filed: 2022-08-15
- Published: 2025-01-23
- Earliest claimed: 2022-01-28
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Dario Serafino TONESI; Miguel GRIOT; Prashanth Haridas HANDE; Haris ZISIMOPOULOS; Mickael MONDET; Yih-Hao LIN
- Web page: https://patentgrep.com/patent/US20250031090A1

## CPC

- 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 47/2475: for supporting traffic characterised by the type of applications
- H04W 28/0252: {per individual bearer or channel (dynamic wireless traffic scheduling H04W72/12)}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Aspects relate to core network entities that: establish a session including at least one of: application data unit (ADU) detection rules, or ADU handling rules related to a detection of ADUs in a user plane, and determine, for one or more quality of service (QOS) flows, whether ADU awareness applies based on an application of the ADU detection rules, or the ADU handling rules; and transmit a request to create a session that supports ADU-based QoS flows, negotiate at least one of: ADU-based QoS policies, or ADU QoS rules applicable to the session, and receive an acknowledgment of creation of the session in response to completing the negotiating. A radio access network entity conveys, during a session, one or more ADUs to a user equipment via a user plane in compliance with ADU-based QoS policies associated with at least one ADU aware QoS flow.

## Claims

### Claim 1

A core network entity for wireless communication, comprising:
a memory; and
a processor coupled to the memory, the processor and the memory being configured to:
establish a session that includes at least one of: application data unit (ADU) detection rules, or ADU handling rules related to a detection of ADUs in a user plane; and
determine, for one or more quality of service (QOS) flows, whether ADU awareness applies based on an application of the at least one of: the ADU detection rules, or the ADU handling rules.

### Claim 2 (depends on 1)

The core network entity of claim 1, wherein the processor and the memory are further configured to:
assign, in response to determining that ADU awareness applies, at least one ADU 5G QoS flow identifier (A5QI) to at least one ADU aware QoS flow; and
configure a radio access network (RAN) entity with the at least one A5QI and the at least one ADU aware QoS flow.

### Claim 3 (depends on 2)

The core network entity of claim 2, wherein the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters are included in at least one of: a table of standardized 5G QoS flow Identifier (5Q1) related QoS parameters, or a table of standardized A5QI related QoS parameters.

### Claim 4 (depends on 2)

The core network entity of claim 2, wherein the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters include at least one of: a maximum ADU size, a maximum number of packet data units (PDUs) per ADU, an ADU delay budget, an ADU maximum data burst volume, or an ADU error rate.

### Claim 5 (depends on 2)

The core network entity of claim 2, wherein parameters related to the at least one ADU aware QoS flow are provided in at least one of:
a dedicated ADU QoS profile that includes QoS flow parameters exclusively related to the at least one A5QI, or
a QoS profile that includes QoS flow parameters related to a 5G QoS flow identifier (5Q1) and the at least one A5QI.

### Claim 6 (depends on 1)

The core network entity of claim 1, wherein the processor and the memory are further configured to:
configure a user plane function (UPF) with at least one of: ADU aware filters, or the ADU detection rules.

### Claim 7 (depends on 1)

The core network entity of claim 1, wherein the core network entity is a session management function (SMF), and the session is established with a user plane function (UPF) over an interface between the SMF and the UPF.

### Claim 8 (depends on 1)

The core network entity of claim 1, wherein an ADU is comprised of a set of Internet Protocol (IP) packets or Ethernet frames jointly processed by at least one of: an application function, or an application server.

### Claim 9 (depends on 1)

The core network entity of claim 1, wherein one or more ADUs, each comprising a plurality of PDUs, are:
generated by an application server at substantially a same time; and
grouped in at least one burst.

### Claim 10 (depends on 1)

The core network entity of claim 1, wherein the processor and the memory are further configured to:
configure ADU aware uplink filters to a user equipment during at least one of: packet data unit (PDU) session establishment, or PDU session modification.

### Claim 11 (depends on 1)

The core network entity of claim 1, wherein the processor and the memory are further configured to:
obtain policy rules related to ADU-based QoS policies from at least one of:
a policy control function (PCF), or
a local configuration.

### Claim 12 (depends on 1)

The core network entity of claim 1, wherein the processor and the memory are further configured to:
obtain an identity of a user plane function that supports ADU-based QoS policies from a policy control function (PCF).

### Claim 13

A method at a core network entity, comprising:
establishing a session that includes at least one of: application data unit (ADU) detection rules, or ADU handling rules related to a detection of ADUs in a user plane; and
determining, for one or more quality of service (QOS) flows, whether ADU awareness applies based on an application of the at least one of: the ADU detection rules, or the ADU handling rules.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
assigning, in response to determining that ADU awareness applies, at least one ADU 5G QoS flow identifier (A5QI) to at least one ADU aware QoS flow; and
configuring a radio access network (RAN) entity with the at least one A5QI and the at least one ADU aware QoS flow.

### Claim 15 (depends on 14)

The method of claim 14, wherein the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters are included in at least one of: a table of standardized 5G QoS flow Identifier (5Q1) related QoS parameters, or a table of standardized A5QI related QoS parameters.

### Claim 16 (depends on 14)

The method of claim 14, wherein the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters include at least one of: a maximum ADU size, a maximum number of packet data units (PDUs) per ADU, an ADU delay budget, an ADU maximum data burst volume, or an ADU error rate.

### Claim 17 (depends on 14)

The method of claim 14, wherein parameters related to the at least one ADU aware QoS flow are provided in at least one of:
a dedicated ADU QoS profile that includes QoS flow parameters exclusively related to the at least one A5QI, or
a QoS profile that includes QoS flow parameters related to a 5G QoS flow identifier (5Q1) and the at least one A5QI.

### Claim 18 (depends on 13)

The method of claim 13, further comprising:
configuring a user plane function (UPF) with at least one of: ADU aware filters, or the ADU detection rules.

### Claim 19 (depends on 13)

The method of claim 13, wherein the core network entity is a session management function (SMF), and the session is established with a user plane function (UPF) over an interface between the SMF and the UPF.

### Claim 20 (depends on 13)

The method of claim 13, wherein an ADU is comprised of a set of Internet Protocol (IP) packets or Ethernet frames jointly processed by at least one of: an application function, or an application server.

### Claim 21 (depends on 13)

The method of claim 13, wherein one or more ADUs, each comprising a plurality of PDUs, are:
generated by an application server at substantially a same time; and
grouped in at least one burst.

### Claim 22 (depends on 13)

The method of claim 13, further comprising:
configuring ADU aware uplink filters to a user equipment during at least one of: packet data unit (PDU) session establishment, or PDU session modification.

### Claim 23 (depends on 13)

The method of claim 13, further comprising:
obtaining policy rules related to ADU-based QoS policies from at least one of:
a policy control function (PCF), or
a local configuration.

### Claim 24 (depends on 13)

The method of claim 13, further comprising:
obtaining an identity of a user plane function that supports ADU-based QoS policies from a policy control function (PCF).

### Claim 25

A core network entity for wireless communication, comprising:
a memory; and
a processor coupled to the memory, the processor and the memory being configured to:
transmit a request to create a session that supports application data unit (ADU) based quality of service (QOS) flows,
negotiate at least one of: ADU-based QoS policies, or ADU QoS rules applicable to the session, and
receive an acknowledgment of creation of the session in response to completing the negotiating.

### Claim 26 (depends on 25)

The core network entity of claim 25, wherein the core network entity is an application function (AF), and the session is an AF session.

### Claim 27 (depends on 25)

The core network entity of claim 25, wherein the request to create the session is transmitted to a network exposure function (NEF) and the acknowledgment is received from the NEF if the core network entity is not a trusted core network entity, or the request to create the session is transmitted to a policy control function (PCF) and the acknowledgment is received from the PCF if the core network entity is a trusted core network entity.

### Claim 28

A method at a core network entity, comprising:
transmitting a request to create a session that supports application data unit (ADU) based quality of service (QOS) flows;
negotiating at least one of: ADU-based QoS policies, or ADU QOS rules applicable to the session; and
receiving an acknowledgment of creation of the session in response to completing the negotiating.

### Claim 29 (depends on 28)

The method of claim 28, wherein the core network entity is an application function (AF), and the session is an AF session.

### Claim 30 (depends on 28)

The method of claim 28, wherein the request to create the session is transmitted to a network exposure function (NEF) and the acknowledgment is received from the NEF if the core network entity is not a trusted core network entity, or the request to create the session is transmitted to a policy control function (PCF) and the acknowledgment is received from the PCF if the core network entity is a trusted core network entity.
