Always-On PDU Session Management for URLLC in 5G Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G wireless communication systems, existing technologies face challenges in managing PDU sessions for ultra-reliable low-latency communication (URLLC) services, particularly in maintaining high stability and low latency, as conventional PDU sessions may require activation/deactivation, leading to delays that are not suitable for URLLC's always-on requirements.
Innovation Solution
The proposed solution involves establishing and managing PDU sessions as 'always-on' sessions for URLLC services by transmitting specific messages between terminals and network nodes, determining the nature of PDU sessions, and modifying existing sessions to ensure continuous, low-latency data transmission without deactivation, using processor-configured transceivers and controllers in both terminal and network apparatuses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional PDU sessions are used for URLLC services, then resource management flexibility is improved, but service stability and latency performance deteriorate due to activation/deactivation cycles
Solution Approach 1:
The patent segments PDU session management into different types: always-on PDU sessions for URLLC services requiring high stability, and conventional PDU sessions for other services. This segmentation allows URLLC services to maintain continuous connectivity without activation/deactivation cycles, while other services can benefit from conventional resource management flexibility.
Solution Approach 2:
The patent applies different quality characteristics to different PDU sessions based on service requirements. URLLC services are assigned always-on PDU sessions with continuous availability, while other services use conventional PDU sessions. This local differentiation ensures that each service type receives the appropriate level of service stability and resource management flexibility.
2Reliability
If PDU sessions are established as always-on for URLLC, then service stability and latency are improved, but session management complexity increases
Solution Approach 1:
The patent introduces dynamic PDU session establishment where the network node determines whether to create an always-on PDU session based on real-time service requirements. The network node receives service requirements from the terminal, evaluates them against URLLC criteria, and dynamically decides on the session type. This dynamic approach manages complexity by automating the decision-making process rather than requiring manual configuration.
Solution Approach 2:
The terminal autonomously identifies its service requirements and requests appropriate PDU session types without requiring complex network-side configuration. The terminal self-evaluates whether URLLC services are needed and initiates the appropriate session establishment procedure, reducing the operational complexity burden on the network side.
3Device complexity
If conventional PDU sessions are used, then device complexity remains low, but latency performance deteriorates due to activation/deactivation delays
Solution Approach 1:
The patent implements preliminary establishment of always-on PDU sessions for URLLC services before actual data transmission begins. By pre-establishing these sessions with continuous availability, the system eliminates activation delays and ensures immediate data transmission capability when URLLC services need to be activated, significantly reducing latency while maintaining manageable complexity through automated session management.
Data Source
AI summary
The disclosure relates to a 5th generation (5G) or pre-5G communication system to support a higher data rate after a 4th generation (4G) communication system such as long term evolution (LTE). Various embodiments provide a method for operating a terminal in a wireless communication system, the method including: transmitting a PDU session establishment request message to a network node; receiving a PDU session establishment accept message from the network node; and determining a PDU session as an always-on PDU session for an URLLC service.