Dedicated DNN Routing for Priority Traffic in 5G QoS Flows

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In advanced wireless networks like 5G SA, prioritizing data traffic for high-priority users can lead to unnecessary overuse of network resources and increased power consumption due to indiscriminate routing of both high-priority and non-high-priority data through high-QoS flows or sessions.

Innovation Solution

Implementing separate QoS flows or DNNs for high-priority and non-high-priority data traffic within the same PDU session, with distinct QoS parameters, to ensure high-priority traffic is only routed through dedicated high-QoS flows and non-high-priority traffic uses default, less resource-intensive flows or sessions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If high-priority user data traffic is routed through dedicated high-QoS flows or sessions, then service quality for priority users is improved, but network resource consumption and power usage increase unnecessarily for non-priority traffic

Engineering Contradiction:
Improveservice qualityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments data traffic into high-priority and non-high-priority categories, routing them through different QoS flows within the same PDU session. High-priority traffic uses dedicated high-QoS flows while non-priority traffic uses default flows, preventing unnecessary resource consumption for non-priority data while maintaining service quality for priority users.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different QoS characteristics to different portions of data traffic based on priority levels. Instead of applying high-QoS parameters uniformly to all traffic from priority users, the system applies high-QoS parameters only to high-priority data packets locally, while non-priority packets use standard QoS parameters, optimizing resource usage.

Inventive Principle:
Principle #3Local quality

2Productivity

If separate QoS flows are implemented for high-priority and non-high-priority traffic, then network resource efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvenetwork resource efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges multiple QoS flows (high-priority and non-high-priority) within a single PDU session. This allows the system to maintain separate QoS treatments for different traffic types while using a unified session framework, reducing the complexity that would arise from implementing completely separate sessions for each traffic type.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The PDU session is designed to serve multiple functions by accommodating both high-priority and non-high-priority QoS flows simultaneously. This multi-functional approach allows a single session to handle diverse traffic types with different QoS requirements, reducing overall system complexity compared to requiring separate sessions for each function.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20260059375A1Managing priority traffic in a wireless network using a dedicated data network name (DNN)
Publication Date: 2026.02.26 BOOST SUBSCRIBERCO LLC
  • US20260059375A1 patent drawing
  • US20260059375A1 patent drawing
  • US20260059375A1 patent drawing

AI summary

Technology that includes receiving, at a user equipment (UE), a first data packet to be communicated between the UE and a wireless network, and determining, based on one or more parameters associated with the first data packet and one or more configured rules, that the first data packet is associated with a first level of priority different from a second level of priority. In response, a determination is made to use—among (i) a first data network name (DNN) and (ii) a second DNN—the first DNN and an associated network slice to route the first data packet. The first DNN and a corresponding QoS flow is defined by a first set of quality-of-service (QoS) parameters different from a second set of QoS parameters associated with the second DNN. A first data communication session is established with the first DNN, and the first data packet is routed over the session.