Core Network Node Load Sharing via Dynamic Target Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In radiocommunication systems, load sharing between core network nodes is inefficient when not all nodes support the 'Flex' feature, leading to potential overload and service disruptions due to manual configuration errors and lack of dynamic load balancing.
Innovation Solution
A method for managing communications that allows a radio network controller change request to be forwarded to a target core network node selected based on predetermined criteria, enabling dynamic load balancing and ensuring service continuity even when a core network node fails or has high traffic variations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual configuration is used to determine target CN nodes for load sharing, then configuration simplicity is maintained, but load sharing effectiveness deteriorates and human error increases
Solution Approach 1:
The source CN node automatically selects the target CN node based on its own load capacity and the pool area configuration, without requiring manual intervention. The system self-configures the load sharing relationship dynamically, eliminating human error while maintaining operational simplicity.
Solution Approach 2:
The target CN node selection is made dynamic based on the source CN node's load capacity. Instead of static manual configuration, the system adaptively determines which CN node should receive the RNC change request, enabling effective load sharing that responds to changing network conditions.
2Device complexity
If a source CN node always selects the same target CN node, then configuration complexity is reduced, but target CN node overload risk increases
Solution Approach 1:
The selection of the target CN node becomes dynamic and adapts to the load capacity of the source CN node. A source CN node with high load capacity will select different target nodes compared to one with low load capacity, distributing traffic more evenly and preventing any single target node from becoming overloaded.
Solution Approach 2:
The selection criteria for the target CN node changes based on the load capacity parameter of the source CN node. This parameter-driven selection ensures that the target node chosen is appropriate for the source's current state, balancing the load across the pool area while maintaining simple configuration.
3Ease of operation
If a single target CN node is configured in the source CN node, then configuration simplicity is maintained, but service continuity deteriorates when the target node fails
Solution Approach 1:
The source CN node is configured with the ability to select from multiple potential target CN nodes based on pool area information. Instead of being limited to a single predetermined target, the system can universally adapt to select any suitable target node from the pool, ensuring service continuity even when the originally intended target is unavailable.
Solution Approach 2:
The target CN node selection is dynamic and can change based on the availability of target nodes. If the initially selected target node fails or becomes unavailable, the source CN node can dynamically select an alternative target node from the pool area, maintaining service continuity without requiring manual reconfiguration.
4Reliability
If Flex feature is implemented for load sharing, then load distribution improves, but device complexity and configuration difficulty increase for CN nodes not supporting Flex
Solution Approach 1:
The source CN node acts as an intermediary that translates the Flex load sharing mechanism into actions compatible with CN nodes that do not natively support Flex. By using the pool area configuration and load capacity-based selection, the source CN node mediates between the Flex capability and the limitations of non-Flex nodes, enabling load sharing without requiring all nodes to support the full Flex feature set.
Data Source
AI summary
A first group of core network (CN) nodes are arranged for transmitting a change request from a source to a target radio network controller (RNC), to a CN node selected from the set of CN nodes to which the target RNC is connected. Relating to a communication in progress with a first RNC (11) and a first CN node (13), for which a change from the first to a second RNC (12) is requested: the change request is transmitted from the first CN node to a second CN node (14) of the first group, and is forwarded from the second to a third CN node (15) selected, according to predetermined criteria, from the set of CN nodes to which the second RNC is connected.