Mapping Multiple QoS Flows to Single PDU Session
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies do not provide a mechanism for setting up a network slice that supports multiple QoS flows, which is necessary for efficiently handling diverse data types such as pose information and high-resolution moving image content in 5G wireless communication systems.
Innovation Solution
A terminal device, base station device, and processing device that enable the mapping of multiple QoS flows to one network slice associated with a PDU session, allowing for the allocation of S-NSSAI and QoS profile configuration for each flow, and dynamically setting up a network slice to support multiple QoS flows based on subscription information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If multiple QoS flows are handled separately through multiple PDU sessions, then QoS control precision is improved, but device complexity and network overhead increase
Solution Approach 1:
The patent combines multiple QoS flows into a single PDU session by introducing a QoS flow identifier field in the PDU session establishment request message. This allows the network to distinguish and control different QoS flows (e.g., sensor data and video content) within one session, maintaining precise QoS control while reducing the number of PDU sessions and associated complexity.
Solution Approach 2:
The PDU session is enhanced to serve multiple functions by incorporating support for multiple QoS flows. The session can simultaneously handle different types of traffic (sensor data, video content) with different QoS requirements through the extended message structure that includes QoS flow identifiers, making a single session universal for diverse data types.
2Ease of operation
If a single PDU session is used for all data types, then network configuration simplicity is improved, but QoS control capability deteriorates
Solution Approach 1:
The patent applies local quality by introducing differentiated QoS flow identifiers within the unified PDU session. Each data type (sensor data, video content) is tagged with specific QoS flow identifiers, allowing the network to apply localized QoS control policies to specific flows while maintaining the overall simplicity of a single session configuration.
3Reliability
If network slices are set up for each QoS flow, then QoS isolation is improved, but network resource overhead increases
Solution Approach 1:
The patent merges multiple QoS flows into a single network slice (PDU session) by using QoS flow identifiers to distinguish different traffic types within the same slice. This reduces the number of network slices required while maintaining QoS isolation through the identifier-based differentiation mechanism.
Data Source
AI summary
A UE 10 transmits a request for mapping a plurality of Qos flows to one network slice associated with one PDU session, receives S-NSSAI allocated to one network slice to which the plurality of Qos flows is mapped, and establishes one PDU session associated with one network slice to which the plurality of Qos flows is mapped. The UE 10 allocates S-NSSAI as identification information for each of the plurality of QoS flows, and maps data transmitted and received on one PDU session to any one of the plurality of QOS flows on the basis of the identification information.