Multi-Slice PDU Sessions for Granular Wireless QoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless networks struggle to provide granular, differentiated Quality of Service (QoS) treatment to different traffic types associated with a single application, such as voice calls, video streaming, and text messaging, leading to suboptimal user experiences.
Innovation Solution
Implementing a single communication session, such as a Protocol Data Unit (PDU) session, that is associated with multiple network slices to manage and prioritize different traffic types based on their specific QoS requirements, using UE Route Selection Policy (URSP) rules and network slice selection mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single communication session is used for multiple traffic types, then device complexity and session management overhead are reduced, but granular QoS treatment for different traffic types becomes difficult to implement
Solution Approach 1:
The patent segments a single communication session into multiple network slices, where each slice can be independently configured with specific QoS parameters. This allows different traffic types within the same session to receive differentiated QoS treatment through slice-specific configurations, resolving the contradiction between session simplicity and QoS granularity.
Solution Approach 2:
The patent enables a single communication session to serve multiple functions by supporting multiple network slices simultaneously. Each slice can be tailored for different traffic types (e.g., voice, video, data), allowing the session to provide universal service while maintaining granular QoS control through slice-specific policies.
2Adaptability or versatility
If multiple communication sessions are established for different traffic types, then granular QoS treatment is achieved, but session management overhead and device complexity increase
Solution Approach 1:
The patent merges multiple communication sessions into a single unified session by introducing network slices as virtual subdivisions. This combining approach maintains the QoS differentiation benefits of multiple sessions while eliminating the management overhead, as the network and device only need to manage one session with multiple slice configurations.
Solution Approach 2:
The patent implements a nested structure where network slices are embedded within a single communication session. Each slice is contained within the session boundary but maintains independent QoS characteristics, creating a hierarchical organization that reduces complexity while preserving granular control capabilities.
3Productivity
If network slice selection is performed dynamically, then QoS optimization for different traffic types is improved, but processing time and decision-making complexity increase
Solution Approach 1:
The patent performs preliminary network slice selection during session establishment by using URSP rules to pre-determine appropriate slices for different traffic types. This advance configuration stores mapping relationships between traffic types and network slices, enabling rapid QoS optimization during operation without real-time decision delays.
Solution Approach 2:
The patent implements self-service mechanisms where the network automatically selects appropriate slices based on pre-configured URSP rules without requiring complex real-time processing. The system uses traffic type identification and rule-based matching to autonomously allocate resources, reducing processing overhead while maintaining optimization efficiency.
Data Source
AI summary
A system described herein may receive a request to associate a protocol data unit (“PDU”) session, between a particular User Equipment (“UE”) and a network, with multiple network slices. The system may provide the particular PDU session identifier to a first set of network devices that are associated with the first slice, and to a second set of network devices that are associated with the second slice. The network may route first traffic, received from the UE, to the first set of network devices based on the first traffic including the particular PDU session identifier and the identifier of the first network slice. The network may route second traffic, received from the UE, to the second set of network devices based on the second traffic including the particular PDU session identifier and the identifier of the second network slice.