# US 2020/0404538 A1 · High bandwidth low latency cellular traffic awareness

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

- Number: US 2020/0404538 A1
- Document ID: US20200404538A1
- Status: Published application
- Kind: A1
- Application number: 16/900,249
- Filed: 2020-06-12
- Published: 2020-12-24
- Earliest claimed: 2019-06-19
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Xipeng ZHU; Prashanth Haridas HANDE; Gavin Bernard HORN; Thomas STOCKHAMMER
- Web page: https://patentgrep.com/patent/US20200404538A1

## 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)}
- H04W 28/065: {using assembly or disassembly of packets}
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/30: Profiles
- H04W 28/02: Traffic management, e.g. flow control or congestion control
- H04L 69/22: Parsing or analysis of headers
- H04L 2101/659: Internet protocol version 6 [IPv6] addresses
- H04W 80/06: Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless {(transmission control protocol/Internet protocol [TCP/IP] or user datagram protocol [UDP] H04L69/16)}
- 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

Disclosed are techniques for wireless communication. In an aspect, a network node configures a quality of service (QoS) profile comprising one or more file-level QoS parameters, wherein the QoS profile applies to one or more files associated with a service flow associated with a user equipment (UE), wherein each file of the one or more files comprises one or more protocol data units (PDUs), and wherein a header of each PDU of the one or more PDUs of the file includes a file identifier and a file type of the file, and enforces the QoS profile on the one or more files.

## Claims

### Claim 1

A method of wireless communication performed by a network node, comprising:
configuring a quality of service (QoS) profile comprising one or more file-level QoS parameters, wherein the QoS profile applies to one or more files associated with a service flow associated with a user equipment (UE), wherein each file of the one or more files comprises one or more protocol data units (PDUs), and wherein a header of each PDU of the one or more PDUs of the file includes a file identifier and a file type of the file; and
enforcing the QoS profile on the one or more files.

### Claim 2 (depends on 1)

The method of claim 1, wherein:
the network node comprises a network entity,
the configuring comprises receiving, from an application server, the one or more files associated with the service flow associated with the UE, and
the enforcing comprises:
encoding the file identifier and the file type in headers of each of one or more downlink PDUs; and
forwarding the one or more downlink PDUs to a radio access network (RAN) serving the UE.

### Claim 3 (depends on 2)

The method of claim 2, wherein the headers of the one or more PDUs comprise:
user datagram protocol (UDP) headers or transmission control protocol (TCP) headers, or
Internet protocol version 6 (IPv6) headers, and
wherein the headers of the one or more downlink PDUs comprise:
general packet radio service (GPRS) tunneling protocol (GTP) user plane (GTP-U) headers, or
one or more packet data convergence protocol (PDCP) headers, one or more radio link control (RLC) headers, one or more service data adaptation protocol (SDAP) headers, or any combination thereof.

### Claim 4 (depends on 2)

The method of claim 2, further comprising:
receiving, at the network entity, file detection information for the one or more files from a session management function (SMF) or an operations, administration, and maintenance (OAM) function.

### Claim 5 (depends on 2)

The method of claim 2, further comprising:
identifying an identifier of the service flow based on service flow detection rules; and
determining the file identifier and the file type from the headers of the one or more PDUs based on the service flow detection rules.

### Claim 6 (depends on 2)

The method of claim 2, further comprising:
receiving the QoS profile for the one or more files from a session management function (SMF).

### Claim 7 (depends on 2)

The method of claim 2, further comprising:
determining the file identifier and the file type from the headers of the one or more PDUs.

### Claim 8 (depends on 2)

The method of claim 2, wherein the network entity comprises a user plane function (UPF).

### Claim 9 (depends on 1)

The method of claim 1, wherein the one or more file-level QoS parameters include at least the file identifier, the file type, a file error rate (FER), a file delay budget (FDB), and a file discard timer for each type of file of the one or more files.

### Claim 10 (depends on 1)

The method of claim 1, wherein:
the network node comprises a base station serving the UE,
the configuring comprises receiving the QoS profile from an access and mobility management function (AMF)/session management function (SMF), and
the enforcing comprises transmitting the QoS profile to the UE.

### Claim 11 (depends on 10)

The method of claim 10, wherein the QoS profile is received from the AMF/SMF in a PDU session setup procedure or a PDU session modification procedure.

### Claim 12 (depends on 10)

The method of claim 10, further comprising:
receiving the one or more PDUs from a user plane function (UPF).

### Claim 13 (depends on 1)

The method of claim 1, wherein:
the network node comprises an application server,
the method further comprises transmitting, to a user plane function (UPF), the one or more files associated with the service flow associated with the UE, and
the configuring comprises:
determining the QoS profile for the one or more files; and
transmitting the QoS profile to a session management function (SMF).

### Claim 14 (depends on 13)

The method of claim 13, wherein the enforcing comprises:
the headers of the one or more PDUs comprising user datagram protocol (UDP) headers or transmission control protocol (TCP) headers,
the headers of the one or more PDUs comprising Internet protocol version 6 (IPv6) headers, or
the headers of the one or more PDUs comprising RTP headers.

### Claim 15 (depends on 13)

The method of claim 13, wherein the transmitting comprises transmitting the QoS profile to the SMF via a policy control function (PCF) or network exposure function (NEF).

### Claim 16 (depends on 1)

The method of claim 1, wherein:
the network node comprises the UE,
the configuring comprises receiving the QoS profile from an access and mobility management function (AMF)/session management function (SMF), and
the enforcing comprises:
receiving, from an application associated with the UE, the one or more files, the one or more files destined for an application server,
encoding the file identifier and the file type in headers of each of one or more uplink PDUs; and
forwarding the one or more uplink PDUs to a radio access network (RAN) serving the UE.

### Claim 17 (depends on 16)

The method of claim 16, further comprising:
determining the file identifier and the file type from the headers of the one or more PDUs.

### Claim 18 (depends on 16)

The method of claim 16, wherein the headers of the one or more PDUs comprise:
user datagram protocol (UDP) headers or transmission control protocol (TCP) headers, or
Internet protocol version 6 (IPv6) headers, and
wherein the one or more PDUs comprise:
one or more Internet protocol (IP) data packets, or
one or more real-time transport protocol (RTP) packets.

### Claim 19 (depends on 18)

The method of claim 18, wherein the file identifier and the file type are carried in fragmentation unit header options FU-A and FU-B of the one or more RTP packets.

### Claim 20 (depends on 16)

The method of claim 16, wherein the headers of the one or more uplink PDUs comprise one or more packet data convergence protocol (PDCP) headers, one or more radio link control (RLC) headers, one or more service data adaptation protocol (SDAP) headers, or any combination thereof.

### Claim 21 (depends on 16)

The method of claim 16, wherein the application is an extended reality (XR) application.

### Claim 22 (depends on 21)

The method of claim 21, wherein the XR application is running on an XR device separate from the UE.

### Claim 23 (depends on 22)

The method of claim 22, wherein the XR device comprises a virtual reality (VR) headset or augmented reality (AR) glasses.

### Claim 24 (depends on 21)

The method of claim 21, wherein the XR application is running on the UE.

### Claim 25 (depends on 24)

The method of claim 24, wherein the UE comprises a handheld touchscreen device.

### Claim 26

A network node, comprising:
a memory; and
at least one processor coupled to the memory, the memory and the at least one processor configured to:
configure a quality of service (QoS) profile comprising one or more file-level QoS parameters, wherein the QoS profile applies to one or more files associated with a service flow associated with a user equipment (UE), wherein each file of the one or more files comprises one or more protocol data units (PDUs), and wherein a header of each PDU of the one or more PDUs of the file includes a file identifier and a file type of the file; and
enforce the QoS profile on the one or more files.

### Claim 27 (depends on 26)

The network node of claim 26, wherein:
the network node comprises a base station serving the UE,
the memory and the at least one processor being configured to configure comprises the memory and the at least one processor being configured to receive the QoS profile from an access and mobility management function (AMF)/session management function (SMF), and
the memory and the at least one processor being configured to enforce comprises the memory and the at least one processor being configured to transmit the QoS profile to the UE.

### Claim 28 (depends on 26)

The network node of claim 26, wherein:
the network node comprises the UE,
the memory and the at least one processor being configured to configure comprises the memory and the at least one processor being configured to receive the QoS profile from an access and mobility management function (AMF)/session management function (SMF), and
the memory and the at least one processor being configured to enforce comprises the memory and the at least one processor being configured to:
receive, from an application associated with the UE, the one or more files, the one or more files destined for an application server,
encode the file identifier and the file type in headers of each of one or more uplink PDUs; and
forward the one or more uplink PDUs to a radio access network (RAN) serving the UE.

### Claim 29

A network node, comprising:
means for configuring a quality of service (QoS) profile comprising one or more file-level QoS parameters, wherein the QoS profile applies to one or more files associated with a service flow associated with a user equipment (UE), wherein each file of the one or more files comprises one or more protocol data units (PDUs), and wherein a header of each PDU of the one or more PDUs of the file includes a file identifier and a file type of the file; and
means for enforcing the QoS profile on the one or more files.

### Claim 30

A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable instructions comprising:
at least one instruction instructing a network node to configure a quality of service (QoS) profile comprising one or more file-level QoS parameters, wherein the QoS profile applies to one or more files associated with a service flow associated with a user equipment (UE), wherein each file of the one or more files comprises one or more protocol data units (PDUs), and wherein a header of each PDU of the one or more PDUs of the file includes a file identifier and a file type of the file; and
at least one instruction instructing the network node to enforce the QoS profile on the one or more files.
