RRC Connection Resume Without UE Context Relocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face inefficiencies in managing UE context relocation during state transitions, particularly in scenarios where UEs move frequently and resume connections without relocating the context, leading to network congestion and security challenges.
Innovation Solution
A mechanism that allows UEs to resume connections in new network nodes without relocating the UE context, ensuring security by maintaining context in the original node and using new security keys for communication, with the target node forwarding RRC responses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If UE context is relocated to target network node during state transitions, then connection resume speed is improved, but network congestion increases and security risks arise from exposing old security keys
Solution Approach 1:
The source network node acts as an intermediary that forwards RRC messages between the target network node and the UE. This allows the UE context to remain at the source node while enabling communication through the target node, thus avoiding context relocation and the associated security risks and network congestion.
Solution Approach 2:
The target network node receives a copy of the RRC response from the source network node via the forwarding mechanism. This copying approach allows the target node to participate in the communication without needing the actual UE context, thereby maintaining security while enabling fast connection resume.
2Reliability
If UE context is stored at source network node without relocation, then security is maintained by avoiding exposure of old security keys, but connection resume requires additional message forwarding
Solution Approach 1:
The source network node performs multiple functions: it maintains the UE context for security purposes and simultaneously acts as a message forwarder for RRC communications. This multi-functionality allows security to be maintained while enabling connection resume through the target node.
Solution Approach 2:
The source network node serves as an intermediary that relays RRC messages between the target network node and the UE. This intermediary role enables the UE to resume connection with the target node while the source node maintains security by keeping the context and using integrity protection with existing security keys.
3Productivity
If RRC messages are forwarded through source network node, then UE context relocation is avoided, but signaling overhead increases
Solution Approach 1:
The essential UE context information is extracted and retained at the source network node, while only the necessary RRC messages are forwarded through the source node. This extraction approach minimizes the amount of data that needs to be transmitted and stored at the target node, reducing signaling overhead while maintaining connection efficiency.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
According to certain embodiments, a target network node for communicating with a user equipment (UE) that was previously in communication with a source network node, comprises an interface operably coupled to processing circuitry. The interface is configured to receive a connection resume request from the user equipment, wherein the connection resume request comprises a resume identification associated with the source network node. The processing circuitry is configured to determine that the UE was previously in communication with the source network node. The interface is further configured to transmit the connection resume request to the source network node, receive a radio resource control (RRC) response from the source network node, and forward the RRC response to the UE.