Load Migration for LTE Control Domain Overload
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The 3GPP LTE system experiences increased communication delays due to overload in control domains, as network elements wait for idle controllers to process user requests, leading to inefficient resource utilization.
Innovation Solution
A load migration method that migrates user equipment (UE) from a source controller in an overloaded control domain to a destination controller in a less loaded control domain, updating resource information in the database server and external network elements to redirect user requests, thereby balancing load across domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the current control domain uses all controllers to process user requests, then resource utilization is maximized, but communication delay increases when the domain is overloaded
Solution Approach 1:
The patent extends load balancing from a single control domain to multiple control domains. When the source control domain is overloaded, the network element selector can redirect user requests to controllers in destination control domains, adding a spatial dimension (cross-domain) to the load distribution mechanism. This resolves the contradiction by providing additional processing capacity while maintaining efficient request routing.
Solution Approach 2:
The patent divides the network architecture into multiple independent control domains, each with its own controllers. This segmentation allows the system to distribute user requests across different domains, preventing any single domain from becoming a bottleneck. The network element selector segments the request routing decision by evaluating both intra-domain and inter-domain controller availability.
2Reliability
If the network element selector waits for an idle controller in the current control domain, then load balancing within the domain is maintained, but communication delay increases
Solution Approach 1:
The network element selector performs preliminary evaluation of controller availability across multiple control domains before routing user requests. By pre-assessing the load status of controllers in both the current and other control domains, the selector can proactively redirect requests to available controllers in destination domains, avoiding the delay of waiting for idle controllers in the overloaded source domain.
Solution Approach 2:
The network element selector acts as an intermediary that mediates between user requests and controllers across multiple control domains. It evaluates the load status of controllers and makes intelligent routing decisions, selecting either intra-domain or inter-domain controllers based on availability. This intermediary function enables the system to maintain load balancing while minimizing communication delay by redirecting requests through alternative domains when necessary.
3Loss of time
If load is distributed across multiple control domains, then communication delay is reduced, but system complexity increases
Solution Approach 1:
The network element selector is designed with multi-functionality, capable of performing both intra-domain load balancing and inter-domain request routing. It universally handles controller selection by evaluating load status across multiple control domains and adapting its routing strategy based on the current system state. This universal function reduces the need for separate specialized components, managing system complexity while enabling cross-domain load distribution.
Solution Approach 2:
The system implements feedback mechanisms where controllers report their load status to the network element selector, which uses this information to make routing decisions. The selector continuously monitors controller availability and adjusts its request distribution strategy accordingly. This feedback-driven approach enables dynamic load balancing across multiple domains without requiring complex centralized control, as each component adapts based on real-time system state information.
Data Source
AI summary
A load migration method, apparatus, and system. The method includes obtaining, by a first controller, in a process of migrating a user equipment (UE) to the first controller from a second controller, a first temporary user identifier of the UE, the first temporary user identifier comprising a second identifier of the second controller, allocating, by the first controller, a second temporary user identifier to the UE, the second temporary user identifier comprising a first identifier of the first controller, transmitting, by the first controller, the second temporary user identifier to a database server for updating the first temporary user identifier by the second temporary user identifier, and sending, by the first controller to an external network element, the first identifier of the first controller.