# US 2026/0089200 A1 · Communicating data burst traffic characteristics in an rtp header extension for an rtp media communication session

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

- Number: US 2026/0089200 A1
- Document ID: US20260089200A1
- Status: Published application
- Kind: A1
- Application number: 19/330,308
- Filed: 2025-09-16
- Published: 2026-03-26
- Earliest claimed: 2024-09-20
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Liangping Ma; Imed Bouazizi
- Web page: https://patentgrep.com/patent/US20260089200A1

## CPC

- H04L 65/70: Media network packetisation
- H04L 65/1069: Session establishment or de-establishment
- H04L 65/65: Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An example device for communicating data via a network includes a memory configured to store data, and a processing system implemented in circuitry and configured to: send or receive a first protocol data unit (PDU) of a data burst, the first PDU including data representing a predicted burst size (BSSize) value for the data burst; and send or receive a second PDU of the data burst after having sent or received the first PDU, the second PDU including data for updating the predicted BSSize value for the data burst to an actual BSSize value for the data burst. A sending device may send the data for updating the predicted BSSize value when the sending device sends the first PDU before all PDUs of the data burst have been formed. A receiving device may use the actual BSSize value to, e.g., perform resource allocation.

## Claims

### Claim 1

A method of communicating data via a network, the method comprising:
receiving a first protocol data unit (PDU) of a data burst, the first PDU including data representing a predicted burst size (BSSize) value for the data burst;
receiving a second PDU of the data burst after having received the first PDU, the second PDU including data for updating the predicted BSSize value for the data burst to an actual BSSize value for the data burst;
updating the predicted BSSize value to the actual BSSize value based on the data of the second PDU; and
using the actual BSSize value to receive one or more subsequent PDUs of the data burst.

### Claim 2 (depends on 1)

The method of claim 1, wherein the data for updating the predicted BSSize value is included in a real-time transport protocol (RTP) header extension of an RTP header encapsulating the second PDU.

### Claim 3 (depends on 2)

The method of claim 2, further comprising sending data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

### Claim 4 (depends on 3)

The method of claim 3, wherein sending the data representing the support for burst size updates comprises sending session description protocol (SDP) data.

### Claim 5 (depends on 4)

The method of claim 4, wherein the SDP data conforms to an augmented Backus-Naur format of:
extensionname=“urn:3gpp:sa4:5grtp: dynamic-traffic-characteristics-rel19”;
extensionattributes=[format SP][BSSize-update].

### Claim 6 (depends on 1)

The method of claim 1, wherein the data for updating the predicted BSSize value is included in a QUIC header encapsulating the second PDU.

### Claim 7 (depends on 6)

The method of claim 6, further comprising sending data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

### Claim 8 (depends on 7)

The method of claim 7, wherein sending the data representing the support for burst size updates comprises sending the data in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet.

### Claim 9 (depends on 7)

The method of claim 7, wherein sending the data representing the support for burst size updates comprises sending a transport parameter indicating the support for data burst size updates for the data bursts of the communication session.

### Claim 10 (depends on 1)

The method of claim 1, wherein using the actual BSSize value to receive the one or more subsequent PDUs of the data burst comprises:
in response to the predicted BSSize value, performing a first resource allocation based on the predicted BSSize value to allocate first resources to receive data having a first size corresponding to the predicted BSSize value; and
in response to updating the predicted BSSize value to the actual BSSize value, performing a second resource allocation based on the actual BSSize value to allocate second resources to receive data having a second size corresponding to the actual BSSize value.

### Claim 11 (depends on 1)

The method of claim 1, wherein using the actual BSSize value to receive the one or more subsequent PDUs of the data burst comprises:
in response to the predicted BSSize value, scheduling reception circuitry to stop receiving data after having received a first amount of data corresponding to the predicted BSSize value; and
in response to the actual BSSize value, rescheduling the reception circuitry to stop receiving data after having received a second amount of data corresponding to the actual BSSize value.

### Claim 12 (depends on 1)

The method of claim 1, wherein the data for updating the predicted BSSize value comprises a size of remaining PDUs of the data burst, and wherein updating the predicted BSSize value comprises adding the size of the remaining PDUs to the predicted BSSize value to form the actual BSSize value.

### Claim 13 (depends on 1)

The method of claim 1, wherein the data for updating the predicted BSSize value comprises a size of all PDUs of the data burst, and wherein updating the predicted BSSize value comprises replacing the predicted BSSize value with the size of all PDUs of the data burst to form the actual BSSize value.

### Claim 14 (depends on 1)

The method of claim 1, further comprising receiving a Real-time Transport Protocol (RTP) header extension including data representing a time to next data burst (TNDB) value relative to an ordinal last PDU of the data burst.

### Claim 15

A device for communicating data via a network, the device comprising:
a memory configured to store data; and
a processing system implemented in circuitry and configured to:
receive a first protocol data unit (PDU) of a data burst, the first PDU including data representing a predicted burst size (BSSize) value for the data burst;
receive a second PDU after having received the first PDU, the second PDU including data for updating the predicted BSSize value for the data burst to an actual BSSize value for the data burst;
update the predicted BSSize value to the actual BSSize value based on the data of the second PDU; and
use the actual BSSize value to receive one or more subsequent PDUs of the data burst.

### Claim 16 (depends on 15)

The device of claim 15, wherein the data for updating the predicted BSSize value is included in a real-time transport protocol (RTP) header extension of an RTP header encapsulating the second PDU.

### Claim 17 (depends on 15)

The device of claim 15, wherein the data for updating the predicted BSSize value is included in a QUIC header encapsulating the second PDU.

### Claim 18

A method of communicating data via a network, the method comprising:
predicting a predicted burst size (BSSize) for a data burst, the data burst including a plurality of protocol data units (PDUs);
sending a first PDU of the data burst, the first PDU including data representing the predicted BSSize for the data burst, wherein sending the first PDU comprises sending the first PDU before an ordinal last PDU of the plurality of PDUs has been formed;
after forming one or more additional PDUs of the plurality of PDUs, determining an actual BSSize value for the data burst; and
sending a second PDU of the data burst, the second PDU including data for updating the predicted BSSize value for the data burst to the actual BSSize value for the data burst.

### Claim 19 (depends on 18)

The method of claim 18, wherein the data for updating the predicted BSSize value is included in a real-time transport protocol (RTP) header extension of an RTP header encapsulating the second PDU.

### Claim 20 (depends on 19)

The method of claim 19, further comprising receiving data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

### Claim 21 (depends on 20)

The method of claim 20, wherein receiving the data representing the support for burst size updates comprises receiving session description protocol (SDP) data.

### Claim 22 (depends on 21)

The method of claim 21, wherein the SDP data conforms to an augmented Backus-Naur format of:
extensionname=“urn:3gpp:sa4:5grtp: dynamic-traffic-characteristics-rel19”;
extensionattributes=[format SP][BSSize-update].

### Claim 23 (depends on 18)

The method of claim 18, wherein the data for updating the predicted BSSize value is included in a QUIC header encapsulating the second PDU.

### Claim 24 (depends on 23)

The method of claim 23, further comprising receiving data representing support for burst size updates for data bursts during session establishment for a communication session including the data burst.

### Claim 25 (depends on 24)

The method of claim 24, wherein receiving the data representing the support for burst size updates comprises receiving the data in one or more of a QUIC Initial packet, a QUIC handshake packet, or a QUIC 1-RTT packet.

### Claim 26 (depends on 24)

The method of claim 24, wherein receiving the data representing the support for burst size updates comprises receiving a transport parameter indicating the support for data burst size updates for the data bursts of the communication session.

### Claim 27 (depends on 18)

The method of claim 18, wherein the data for updating the predicted BSSize value comprises a size of remaining PDUs of the data burst.

### Claim 28 (depends on 18)

The method of claim 18, wherein the data for updating the predicted BSSize value comprises a size of all PDUs of the data burst.

### Claim 29 (depends on 18)

The method of claim 18, further comprising sending a Real-time Transport Protocol (RTP) header extension including data representing a time to next data burst (TNDB) value relative to the ordinal last PDU of the data burst.

### Claim 30

A device for communicating data via a network, the device comprising:
a memory configured to store data; and
a processing system implemented in circuitry and configured to:
predict a predicted burst size (BSSize) for a data burst, the data burst including a plurality of protocol data units (PDUs);
send a first PDU of the data burst, the first PDU including data representing the predicted BSSize for the data burst, wherein sending the first PDU comprises sending the first PDU before an ordinal last PDU of the plurality of PDUs has been formed;
after forming one or more additional PDUs of the plurality of PDUs, determine an actual BSSize value for the data burst; and
send a second PDU of the data burst, the second PDU including data for updating the predicted BSSize value for the data burst to the actual BSSize value for the data burst.
