Cellular Traffic Awareness Through File-Level QoS Headers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless communication systems struggle to provide the necessary quality of service (QoS) for high bandwidth and low latency applications, such as extended reality (XR), due to the lack of file-level awareness in cellular data networks, leading to inefficient QoS policy application.

Innovation Solution

Implementing a file-level quality of service (QoS) profile that includes file identifiers and types in protocol data units (PDUs) to enable the cellular data network to apply appropriate QoS requirements to data flows, allowing the core network to determine and enforce file-level QoS policies based on traffic identifiers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If file-level QoS parameters are implemented in cellular networks, then QoS management precision for high bandwidth low latency applications is improved, but device complexity and network complexity increase due to additional header fields and processing requirements

Engineering Contradiction:
ImproveQoS management precisionVSAvoidnetwork complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The QoS parameters are segmented into file-level attributes that can be independently identified and managed. Each file is assigned specific QoS parameters (bandwidth, latency, packet error rate) that are embedded in the data structure, allowing the network to segment and manage different file types with different QoS requirements separately rather than treating all traffic uniformly.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a new dimension to packet structure by incorporating file-level QoS parameters into the data flow. This dimensional expansion allows the network to identify and manage files based on their specific QoS requirements, transforming the network's ability to handle traffic from a single-dimension approach to a multi-dimensional QoS-aware approach.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Loss of information

If file identifiers and types are included in PDU headers, then traffic awareness and QoS policy application are improved, but data transmission overhead increases

Engineering Contradiction:
Improvetraffic awarenessVSAvoiddata transmission overhead
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent implements partial action by including QoS parameters only where necessary - specifically in file-level identifiers and types within PDU headers. Rather than adding comprehensive metadata to every packet, the solution selectively adds only the essential file-level information needed for QoS management, balancing awareness requirements with overhead constraints.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If file-level QoS policies are enforced in the core network, then service quality for XR applications is improved, but processing time and network latency increase

Engineering Contradiction:
Improveservice qualityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring QoS policies and parameters before data transmission begins. File-level QoS requirements are established and embedded in the data structure in advance, allowing the network to enforce pre-determined policies rather than making real-time decisions during packet processing, thus reducing processing time while maintaining service quality.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12382341B2High bandwidth low latency cellular traffic awareness
Publication Date: 2025.08.05 QUALCOMM INC
  • US12382341B2 patent drawing
  • US12382341B2 patent drawing
  • US12382341B2 patent drawing

AI summary

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.