NTN Buffer Sizing Using RLC RTT and Data Rate

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless communication systems struggle with efficient buffer management for non-terrestrial networks (NTNs) due to longer radio link control (RLC) round trip times (RTTs), leading to potential memory overflow and increased latency.

Innovation Solution

The UE calculates a buffer size specific to NTNs using the maximum data rate and RLC RTT specific to NTNs, preventing memory overflow and reducing latency by ensuring a sufficient buffer size for NTN communications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a buffer size calculated using terrestrial network RLC RTT is used for NTN communications, then memory overflow is prevented, but buffering capacity is insufficient leading to data loss

Engineering Contradiction:
Improvebuffering capacityVSAvoidbuffer size
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies parameter changes by transitioning from terrestrial network RLC RTT values to NTN-specific RLC RTT values in the buffer size calculation formula. This parameter substitution ensures the buffer size reflects the actual longer round trip times experienced in satellite or aerial network communications, thereby providing adequate buffering capacity without causing memory overflow.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If a larger buffer size is allocated for NTN communications, then memory overflow is prevented, but latency increases due to larger buffer processing time

Engineering Contradiction:
Improvememory overflow preventionVSAvoidprocessing latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial action by calculating the buffer size using a specific portion of the RLC RTT value rather than using excessive buffer allocation. The buffer size is precisely calculated as buffer size = maximum data rate × RLC RTT, which provides just sufficient buffering capacity to prevent overflow without allocating excessive memory that would increase processing latency unnecessarily.

Inventive Principle:
Principle #16Partial or excessive action

3Device complexity

If standard terrestrial network buffering techniques are used for NTN, then device complexity is maintained, but communication efficiency deteriorates due to mismatched buffer parameters

Engineering Contradiction:
Improvebuffering implementationVSAvoidcommunication efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent maintains device complexity by using the same buffer size calculation formula (buffer size = maximum data rate × RLC RTT) but changes the critical parameter from terrestrial RLC RTT to NTN-specific RLC RTT. This parameter change adapts the buffering mechanism to NTN characteristics without requiring fundamental redesign of the buffering architecture, thereby maintaining implementation simplicity while improving communication efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12621706B2Buffering techniques for non-terrestrial networks
Publication Date: 2026.05.05 QUALCOMM INC
  • US12621706B2 patent drawing
  • US12621706B2 patent drawing
  • US12621706B2 patent drawing

AI summary

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may be configured to buffer communications with a network node. A buffer size of a buffer used to buffer the communications may be specific to a non-terrestrial network (NTN) via which the UE communicates with the network node. For example, the UE may calculate the buffer size based on a maximum data rate of a connection with the network node via the NTN and a radio link control (RLC) round trip time (RTT). The RLC RTT may be specific to NTNs. The UE may use a buffer having the calculated buffer size to buffer the communications between the UE and the network node over the connection.