# US 2026/0089552 A1 · Ran aware proactive multi-packet link adaptation

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

- Number: US 2026/0089552 A1
- Document ID: US20260089552A1
- Status: Published application
- Kind: A1
- Application number: 19/314,487
- Filed: 2025-08-29
- Published: 2026-03-26
- Earliest claimed: 2024-09-26
- Assignees: Apple Inc.
- Applicants: Apple Inc.
- Inventors: Onur Sahin; Arnab Roy; Oner Orhan; Norman Goris; Ahmed M. Soliman; Ayman F. Naguib; Ping-Heng Kuo; Ralf Rossbach
- Web page: https://patentgrep.com/patent/US20260089552A1

## CPC

- H04W 28/0278: {using buffer status reports (dynamic wireless traffic scheduling definition H04W72/12)}
- H04L 1/1812: Hybrid protocols; Hybrid automatic repeat request [HARQ]
- H04W 28/06: Optimizing {the usage of the radio link}, e.g. header compression, information sizing {, discarding information (system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365)}
- 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

Embodiments herein include a UE that receives one or more packets of a downlink packet set from a network node. The UE may identify a remaining delay budget and a remaining packet error budget for remaining packets of the downlink packet set based on Key Performance Indicator (KPI) requirements. The UE may perform a packet error prediction for the remaining packets, and perform a link adaptation operation based on the prediction and the remaining delay budget. A network node may perform similar actions on an uplink packet set.

## Claims

### Claim 1

A method performed by a UE, the method comprising:
receiving one or more packets of a downlink packet set from a network node;
identifying a remaining delay budget and a remaining packet error budget for remaining packets of the downlink packet set based on Key Performance Indicator (KPI) requirements of the downlink packet set and the one or more packets received;
performing a packet error prediction for the downlink packet set to determine a likelihood value of unsuccessful reception of a number of the remaining packets exceeding the remaining packet error budget based on current conditions; and
performing a link adaptation operation based on the likelihood value and the remaining delay budget.

### Claim 2 (depends on 1)

The method of claim 1, wherein the current conditions include one or more of successful reception statistics of the one or more packets received in the packet set, packet set size, packet set delay budget, packet identifier, Application Layer (AL) packet error rate (PER), Channel Quality Indicator (CQI), Hybrid Automatic Repeat Request (HARQ) acknowledgment or negative-acknowledgment, Packet Data Convergence Protocol (PDCP), PDCP discard statistics, or Radio Link Control (RLC) acknowledgment or negative-acknowledgment statistics.

### Claim 3 (depends on 1)

The method of claim 1, wherein performing the link adaptation operation comprises generating retransmission or redundancy framework reconfiguration feedback, and sending the retransmission or redundancy framework reconfiguration feedback to the network node.

### Claim 4 (depends on 3)

The method of claim 3, wherein the retransmission or redundancy framework reconfiguration feedback comprises a configuration of PDCP duplication parameters including linear packet level coding for duplicated packets.

### Claim 5 (depends on 3)

The method of claim 3, wherein the retransmission or redundancy framework reconfiguration feedback comprises activation or de-activation Radio Link Control (RLC) Acknowledged Mode, Unacknowledged Mode, or Transparent Mode, and configuration of RLC Acknowledged Mode including linear packet coding for packet re-transmission.

### Claim 6 (depends on 3)

The method of claim 3, wherein the retransmission or redundancy framework reconfiguration feedback comprises activation or de-activation Medium Access Control (MAC) or Physical Layer (PHY) Hybrid Automatic Repeat Request (HARQ), and configuration of the MAC or PHY HARQ including Forward Error Correction (FEC) selection and configuration.

### Claim 7 (depends on 1)

The method of claim 1, wherein performing the link adaptation operation comprises discarding all remaining packets in the packet set when the KPI requirements will not be met.

### Claim 8 (depends on 1)

The method of claim 1, further comprising sending an outcome of the packet error prediction to the network node.

### Claim 9 (depends on 1)

The method of claim 1, further comprising sending UE capability information to the network node to indicate application layer forward error correction capabilities or linear predictive coding capabilities, and predictive link adaptation capabilities.

### Claim 10

A method performed by a network node, the method comprising:
receiving one or more packets of an uplink packet set from a user equipment (UE);
identifying a remaining delay budget and a remaining packet error budget for remaining packets of the uplink packet set based on Key Performance Indicator (KPI) requirements of the uplink packet set and the one or more packets received;
performing a packet error prediction for the uplink packet set to determine a likelihood value of unsuccessful reception of a number of the remaining packets exceeding the remaining packet error budget based on current conditions; and
performing a link adaptation operation based on the likelihood value and the remaining delay budget.

### Claim 11 (depends on 10)

The method of claim 10, wherein performing the link adaptation operation comprises generating retransmission or redundancy framework reconfiguration feedback, and sending the retransmission or redundancy framework reconfiguration feedback to the UE.

### Claim 12 (depends on 11)

The method of claim 11, wherein the retransmission or redundancy framework reconfiguration feedback comprises a configuration of Packet Data Convergence Protocol (PDCP) duplication parameters including linear packet level coding for duplicated packets.

### Claim 13 (depends on 11)

The method of claim 11, wherein the retransmission or redundancy framework reconfiguration feedback comprises activation or de-activation Radio Link Control (RLC) Acknowledged Mode, Unacknowledged Mode, or Transparent Mode, and configuration of RLC Acknowledged Mode including linear packet coding for packet re-transmission.

### Claim 14 (depends on 11)

The method of claim 11, wherein the retransmission or redundancy framework reconfiguration feedback comprises activation or de-activation Medium Access Control (MAC) or Physical Layer (PHY) Hybrid Automatic Repeat Request (HARQ), and a configuration of the MAC or PHY HARQ including Forward Error Correction (FEC) selection and configuration.

### Claim 15 (depends on 10)

The method of claim 10, wherein performing the link adaptation operation comprises discarding all remaining packets in the packet set when the KPI requirements will not be met.

### Claim 16 (depends on 10)

The method of claim 10, further comprising determining source encoder setting options and sending the source encoder setting options to the UE such that the UE can autonomously select a particular setting option based on information from the network node.

### Claim 17

A method performed by a user equipment (UE) the method comprising:
sending one or more packets of an uplink packet set to a network node;
receiving link adaptation feedback based on a remaining delay budget and a packet error prediction for remaining packets of the uplink packet set;
adjusting an application source encoder configuration based on the link adaptation feedback; and
adjusting a transmission configuration based on the application source encoder configuration.

### Claim 18 (depends on 17)

The method of claim 17, wherein adjusting the transmission configuration comprises continuing to transmit encoded packets belonging to the packet set until a threshold number of packets are lost.

### Claim 19 (depends on 17)

The method of claim 17, further comprising adjusting a Hybrid Automatic Repeat Request (HARQ) policy or retransmission policy based on the application source encoder configuration.

### Claim 20 (depends on 17)

The method of claim 17, further comprising receiving, from the network node, source encoder setting options and autonomously selecting a particular setting option based on information from the network node.
