Flag-Based RRC Reconfiguration Handling During Multi-Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-connectivity scenarios, user equipment (UE) may fail to comply with reconfiguration messages due to simultaneous execution of different RRC reconfiguration messages, leading to radio link failures and service interruptions.
Innovation Solution
Implementing a flag mechanism to determine whether to discard or execute subsequent RRC reconfiguration messages based on the status of ongoing reconfiguration processes, ensuring compatibility and reducing the need for connection re-establishment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the UE executes multiple RRC reconfiguration messages simultaneously during multi-connectivity, then the reconfiguration process completes faster, but the UE fails to comply with the messages leading to radio link failures
Solution Approach 1:
The patent introduces a preliminary check mechanism where the UE evaluates the compatibility of multiple pending RRC reconfiguration messages before execution. The UE determines whether simultaneous execution of multiple reconfiguration messages would lead to conflicts, and if so, prioritizes or sequences their execution accordingly. This preliminary assessment prevents radio link failures by ensuring that reconfiguration messages are executed in a safe order.
Solution Approach 2:
The patent implements dynamic prioritization of RRC reconfiguration messages based on their type and urgency. Different reconfiguration message types (e.g., mobility-related, bearer setup, SCG modification) are assigned different priorities. The UE dynamically adjusts the execution sequence based on the current radio conditions and the criticality of each reconfiguration task, rather than executing them in a fixed or simultaneous manner.
2Reliability
If the UE discards subsequent RRC reconfiguration messages during ongoing reconfiguration, then compliance conflicts are avoided, but service interruptions occur due to message discard
Solution Approach 1:
The patent changes the parameter of message handling from binary (execute/discard) to a multi-state system (execute, discard, store for later execution). The UE evaluates each incoming RRC reconfiguration message against the current execution context and determines the appropriate action. Compatible messages are executed, conflicting messages are stored with their execution conditions, and the UE continues service while awaiting appropriate execution时机.
Solution Approach 2:
The patent introduces an intermediary evaluation mechanism that mediates between incoming reconfiguration messages and the current execution state. This intermediary layer analyzes the compatibility of new messages with ongoing reconfigurations and determines the optimal execution strategy, preventing both conflicts and unnecessary discards that would cause service interruptions.
3Reliability
If the UE establishes strict execution order for RRC reconfiguration messages, then compliance conflicts are reduced, but the reconfiguration process takes longer
Solution Approach 1:
The patent segments the reconfiguration process into independent, manageable tasks that can be executed in parallel when compatible. Instead of treating all reconfiguration messages as a single sequential process, the UE identifies independent reconfiguration tasks (e.g., MCG reconfiguration, SCG reconfiguration, bearer setup) that can proceed simultaneously without interfering with each other, thus reducing overall execution time while maintaining compliance.
Solution Approach 2:
The patent changes the execution model from strictly sequential to conditional parallel execution. The UE monitors the compatibility of multiple reconfiguration tasks and allows parallel execution when no conflicts are detected. When conflicts are identified, the UE dynamically adjusts the execution schedule to resolve conflicts while minimizing delays, rather than always following a fixed sequential order.
Data Source
Figure 1~3
Figure 4~5
Figure 6
AI summary
A method comprising, during multi-connectivity: sending a reconfiguration message for execution by a user equipment; and sending a flag indicating an action to be taken by the user equipment during or after execution by the user equipment of an existing reconfiguration message, wherein the flag is configured to distinguish between at least two of the following actions: discarding the reconfiguration message; executing the reconfiguration message after executing an existing reconfiguration message; or prioritizing execution of the reconfiguration message over execution of an existing reconfiguration message.