RNC Cluster Decision Logic for UE Movement Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the UMTS network, when User Equipment (UE) moves between Radio Network Controllers (RNCs), there are inconsistencies in identifying RNC IDs, leading to incorrect message routing, which can result in call drops due to misidentification of RNC types and incorrect processing of messages, affecting service continuity.
Innovation Solution
A method and device for UE movement that involve determining whether the target RNC Cluster is the same as the current RNC Cluster by analyzing the RNC ID, and if not, routing messages accordingly through internal processing within the RNC Cluster or to the target RNC Cluster, using a decision rule based on the RNC Cluster ID and message IDs like U-RNTI and S-RNTI, ensuring correct message processing and routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the DRNC resolves the target RNC ID according to the general RNC ID format, then messages can be correctly routed for general RNC IDs, but messages will be incorrectly routed when the target actually uses an extended RNC ID
Solution Approach 1:
The patent segments the RNC ID resolution process into two distinct paths: one for general RNC IDs (12 bits) and another for extended RNC IDs (16 bits). The DRNC first determines whether the target RNC uses the general or extended format, then applies the appropriate resolution method. This segmentation allows the system to handle both formats correctly without confusion, resolving the contradiction between routing accuracy for general IDs and compatibility with extended IDs.
Solution Approach 2:
The patent changes the parameter of RNC ID length recognition dynamically. Instead of fixed at 12 bits, the system adjusts the recognized RNC ID length based on the actual format being used. When an extended RNC ID is detected, the system switches to 16-bit resolution mode; when a general RNC ID is used, it maintains 12-bit mode. This parameter adaptation resolves the contradiction by making the system flexible to handle both formats accurately.
2Reliability
If the DRNC resolves the target RNC ID according to the extended RNC ID format, then messages can be correctly routed for extended RNC IDs, but messages will be incorrectly routed when the target actually uses a general RNC ID
Solution Approach 1:
The patent segments the RNC ID resolution process into two distinct paths: one for general RNC IDs (12 bits) and another for extended RNC IDs (16 bits). The DRNC first determines whether the target RNC uses the general or extended format, then applies the appropriate resolution method. This segmentation allows the system to handle both formats correctly without confusion, resolving the contradiction between routing accuracy for general IDs and compatibility with extended IDs.
Solution Approach 2:
The patent changes the parameter of RNC ID length recognition dynamically. Instead of fixed at 12 bits, the system adjusts the recognized RNC ID length based on the actual format being used. When an extended RNC ID is detected, the system switches to 16-bit resolution mode; when a general RNC ID is used, it maintains 12-bit mode. This parameter adaptation resolves the contradiction by making the system flexible to handle both formats accurately.
3Reliability
If the RNC sends messages for internal processing within the RNC Cluster, then service continuity is maintained during UE movement, but incorrect internal processing may occur if the target RNC is actually outside the cluster
Solution Approach 1:
The patent implements a feedback mechanism where the DRNC verifies whether the resolved target RNC actually belongs to the source RNC's cluster before sending internal processing messages. The system receives feedback information indicating cluster membership, and based on this feedback, decides whether to send messages for internal cluster processing or external routing. This feedback loop ensures accurate cluster identification and prevents incorrect internal processing, resolving the contradiction between service continuity and identification accuracy.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Provided is a method and device for moving a User Equipment (UE). The method includes that: a Radio Network Controller (RNC) receives a first message; according to a decision rule, the RNC decides whether a target RNC Cluster corresponding to the first message is the RNC Cluster where the RNC is located, wherein the RNC Cluster is composed of one or more RNCs; if the decision result is yes, the RNC sends a second message to perform internal processing of the RNC Cluster; or, if the decision result is no, the RNC sends the second message to the target RNC Cluster. The disclosure can avoid call drop when the UE moves between the RNCs, thereby guaranteeing the continuous reception of a service.