UE Connection Relocation via Core Network RRC Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current relocation procedures for User Equipment (UE) connections between source and target Radio Network Controllers (RNCs) in wireless communication networks face issues such as ping-pong effects and incompatible configurations, leading to degraded user experience and call drops, especially when RNCs belong to different vendors.
Innovation Solution
The method involves using a core network to trigger the relocation procedure and obtain a Radio Resource Control (RRC) configuration defined by the target RNC, enabling the UE to switch from the source RNC's configuration to the target RNC's configuration, even when an interface like IUR is available, thereby avoiding interface reliance and ensuring compatible configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the interface (IUR) between source RNC and target RNC is used for relocation, then the relocation procedure can be executed, but incompatible configurations and ping-pong effects occur leading to call drops
Solution Approach 1:
The patent extracts the harmful interface (IUR) from the relocation procedure. By removing the direct interface between RNCs and instead using the core network for relocation signaling, the patent eliminates the source of configuration incompatibility and ping-pong effects while maintaining relocation functionality through an alternative path.
2Ease of operation
If the interface (IUR) is available and used for relocation, then direct RNC communication is enabled, but configuration incompatibility between different vendor RNCs occurs
Solution Approach 1:
The patent introduces the core network as an intermediary between source and target RNCs for relocation procedures. This mediator translates and adapts configuration information, allowing RNCs from different vendors to communicate effectively during relocation without direct interface dependencies, thus resolving configuration incompatibility issues.
3Reliability
If hard handover is performed via core network when IUR is not available, then relocation can occur, but user experience degrades due to service interruption
Solution Approach 1:
The patent performs preliminary configuration preparation and resource allocation through the core network before the actual handover execution. By pre-establishing the target RNC configuration and preparing necessary resources in advance, the patent minimizes service interruption time during the actual handover while maintaining relocation capability.
Data Source
AI summary
Embodiments include methods performed by a target RAN controller for handling relocation of a UE connection from a source RAN controller during an ongoing wireless communication. Such methods include, when a distance between the UE and a border between source and target RAN controllers is below a threshold value, receiving from the source RAN controller an order to establish radio link(s) to be controlled by the target RAN controller for the ongoing wireless communication and establishing radio link(s) for the ongoing wireless communication accordingly. Such methods include, based on existence of certain conditions, receiving from the source RAN controller a request to initiate a procedure for relocating the UE connection from source to target RAN controller. Such methods include creating an RRC configuration to be used by the UE after the relocation to the target RAN controller and sending the created RRC configuration to the source RAN controller.