Multi-Persona App QoS Differentiation via Traffic Type Indicators
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless networks face challenges in providing differentiated Quality of Service (QoS) to various traffic types within multi-persona applications without inspecting or analyzing the traffic content, which can lead to inefficient resource usage and privacy concerns.
Innovation Solution
The establishment of multiple communication sessions with distinct QoS parameters for different traffic types, such as voice call, content streaming, and file transfer, using network slices and resource allocation mechanisms within the Radio Access Network (RAN) and core network, allowing for granular QoS treatment without content inspection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traffic content inspection is performed to provide differentiated QoS treatment, then QoS differentiation accuracy is improved, but privacy protection deteriorates and processing complexity increases
Solution Approach 1:
The patent extracts only the essential traffic type identification information from the full traffic content, using application identifiers and traffic type indicators rather than inspecting actual data payloads. This extraction approach enables QoS differentiation while preserving user privacy by not analyzing sensitive traffic content.
Solution Approach 2:
The patent introduces an intermediary mechanism using application identifiers and traffic type indicators as mediators between the traffic flow and QoS treatment. Instead of directly inspecting traffic content, the system uses these intermediary identifiers to route traffic to appropriate QoS policies, thereby avoiding privacy intrusion while maintaining differentiation accuracy.
2Measurement precision
If multiple communication sessions are established for different traffic types, then QoS treatment precision is improved, but device complexity increases
Solution Approach 1:
The patent segments communication sessions by traffic type within multi-persona applications, creating distinct QoS flows for voice calls, content streaming, and file transfers. This segmentation enables precise QoS treatment for each traffic type while using standardized network slice resources to avoid excessive device complexity.
Solution Approach 2:
The patent implements a universal QoS handling mechanism that works across multiple application types and traffic categories. The same QoS policy framework and session management procedures are applied universally to different traffic types, reducing the need for application-specific complex handling logic while maintaining precise QoS differentiation.
3Productivity
If network resources are allocated for each traffic type, then network performance is improved, but resource usage efficiency deteriorates
Solution Approach 1:
The patent implements dynamic resource allocation where network slice resources are flexibly assigned to different traffic types based on actual demand. The system can dynamically adjust the number and capacity of communication sessions for voice calls, content streaming, and file transfers, ensuring high network performance when needed while conserving resources during low-demand periods.
Solution Approach 2:
The patent changes key QoS parameters such as packet loss rate, latency, and bandwidth allocation dynamically based on traffic type and network conditions. By adjusting these parameters rather than maintaining fixed resource allocations, the system achieves high network performance for critical traffic while optimizing overall resource usage efficiency across the network.
Data Source
AI summary
A system described herein may provide a technique for the differentiated Quality of Service (“QoS”) treatment of different traffic types associated with the same application (e.g., a “multi-persona” application) by a wireless network, without the exposure of an application identifier of the application to the wireless network. The application may provide a traffic type indication, based on which a User Equipment (“UE”) may establish one or more QoS flows or other types of communication sessions with the wireless network, where the QoS flows or other types of communication sessions are associated with a network slice that is associated with the traffic type. The communication sessions may include Data Radio Bearers (“DRBs”), backhaul links, protocol data unit (“PDU”) sessions, or other suitable types of communication sessions.


