RTP Header Compression for Low-Rate Non-Terrestrial Links

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless communication systems over non-terrestrial networks face high transmission overhead due to the inclusion of real-time transport protocol (RTP) headers, which can reduce data transmission efficiency, especially in low-data-rate environments.

Innovation Solution

Implementing RTP header compression techniques to exclude or compress RTP header fields in RTP packets, generating new packets with only essential header fields to reduce transmission overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If RTP headers are included in packets for non-terrestrial network transmission, then packet integrity and protocol compliance are maintained, but transmission overhead increases and data transmission efficiency decreases

Engineering Contradiction:
Improvepacket integrityVSAvoiddata transmission efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts and removes unnecessary RTP header fields from packets transmitted over non-terrestrial networks. Specifically, it excludes fields such as contribution count, extension indication, and other optional headers that are not required for proper packet processing in satellite communications, thereby reducing overhead while maintaining essential packet integrity

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent modifies the RTP header structure by changing which fields are included or excluded based on the transmission medium. For non-terrestrial networks, the header is modified to include only essential fields (version, padding, extension, contribution count) while omitting optional fields, adapting the header parameters to the specific requirements of satellite communication environments

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If full RTP headers are transmitted, then protocol compatibility is maintained, but bandwidth consumption increases in low data rate environments

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidbandwidth consumption
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent applies different header compression strategies to different transmission contexts. For non-terrestrial networks with low data rates, it uses a simplified header format with only essential fields. For terrestrial networks or when full compatibility is required, it transmits complete headers. This local adaptation optimizes bandwidth usage while maintaining protocol compatibility where needed

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent transmits only the necessary portion of RTP headers (partial action) rather than always transmitting complete headers. By including only essential fields such as version, padding indication, extension indication, and contribution count, it reduces bandwidth consumption while providing sufficient information for proper packet processing in low data rate environments

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20260067345A1Real-time transport protocol header compression for transport over a non-terrestrial network
Publication Date: 2026.03.05 QUALCOMM INC
  • US20260067345A1 patent drawing
  • US20260067345A1 patent drawing
  • US20260067345A1 patent drawing

AI summary

Methods, systems, and devices for wireless communications are described. Techniques described provide for real-time transport protocol (RTP) header compression for transport over a non-terrestrial network (NTN). In some examples, a first network entity may receive, from a second network entity supported by the NTN, a first RTP packet comprising an audio payload associated with the second network entity, where the first RTP packet excludes one or more RTP header fields associated with an RTP packet generation protocol. The network entity may generate at least one RTP header field of the RTP header fields excluded from the first RTP packet. The first network entity may output, to a third network entity or to an upper layer RTP stack of the first network entity, a second RTP packet including the audio payload associated with the second network entity and the at least one RTP header field generated by the first network entity.