Conditional Cell Group Change With Persistent Node Configurations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communications systems, the release of configurations during conditional primary secondary cell group change (CPAC) and conditional handover (CHO) procedures leads to inefficiencies, increased latency, and failed transmissions, as the user equipment (UE) loses configurations after performing the change, necessitating reconfiguration and measurement reports.
Innovation Solution
The described techniques involve the network entity providing UE with node configurations that include execution commands, allowing the UE to maintain configurations during CPAC and CHO without triggering conditions, using reduced handover commands or layer 1/layer 2 signaling for dynamic node addition/change, thereby maintaining configurations post-update.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UE releases configurations during CPAC and CHO procedures, then the system follows standard handover protocols, but this leads to increased latency and failed transmissions due to loss of configurations
Solution Approach 1:
The network entity provides the UE with node configurations for multiple target nodes in advance, before the actual handover is triggered. This preliminary provisioning of configurations ensures that when handover is needed, the UE already has the necessary configuration data ready, eliminating the time loss associated with configuration release and re-acquisition during the handover process.
Solution Approach 2:
The patent changes the state of configuration parameters from 'temporary/conditional' to 'maintained/persistent' during CPAC and CHO procedures. By modifying the parameter lifecycle of node configurations, the system prevents configuration loss while still allowing handover to proceed, thereby maintaining transmission reliability without incurring latency penalties.
2Reliability
If the UE maintains multiple node configurations, then transmission reliability improves, but device complexity and memory requirements increase
Solution Approach 1:
The patent extracts only the essential node configurations needed for potential handover targets, rather than maintaining all possible configurations. The network entity provides configurations for multiple target nodes, but the UE selectively maintains only those relevant to its current context and mobility patterns, reducing memory and processing requirements while preserving transmission reliability.
Solution Approach 2:
The system provides configurations for multiple target nodes (excessive action), but the UE maintains only a subset of these configurations (partial action) based on current needs. This approach ensures reliability by having backup configurations available while avoiding the full complexity burden of maintaining all possible configurations simultaneously.
3Reliability
If the network provides configurations for multiple target nodes, then handover robustness improves in rapidly degrading conditions, but signaling overhead increases
Solution Approach 1:
The network entity performs preliminary configuration provisioning for multiple target nodes before handover is actually triggered. By preparing these configurations in advance during periods of stable connection, the network reduces the signaling burden during critical handover moments, as the configurations are already established and ready for immediate use if needed.
Data Source
AI summary
Methods, systems, and devices for wireless communications are described. The method includes a user equipment (UE) receiving signaling from a network entity that indicates a set of multiple node configurations for a set of multiple target nodes, receiving a command from the network entity to perform a node update procedure associated with the set of multiple node configurations, performing the node update procedure based on receiving the command, maintaining at least one of the set of multiple node configurations after performing the node update procedure, and communicating based on results of the node update procedure.