Cell Switching Mobility Using Group IDs for Inter-CU Handover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Intra-centralized unit (intra-CU) Layer 1/Layer 2 (L1/L2) triggered mobility (LTM) is only supported for mobility between cells within the same Next Generation Node B (gNB) or within the same CU, limiting its application opportunities.
Innovation Solution
A method and system for mobility management that enables inter-centralized unit (inter-CU) mobility by using group identifiers and signaling to determine whether intra-CU or inter-CU level configurations, such as security key updates, PDCP entity re-establishment, or RRC configurations, are needed during cell switching.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If intra-CU LTM is used for mobility between cells within the same CU, then mobility latency is improved, but the application scope is limited to intra-CU scenarios only
Solution Approach 1:
The patent segments the mobility management functionality by introducing a flag field that distinguishes between intra-CU and inter-CU scenarios. This allows the system to apply different configuration approaches (LTM for intra-CU, L3 for inter-CU) based on the specific scenario, thereby expanding the overall applicability while maintaining the low-latency benefits of LTM where applicable.
Solution Approach 2:
The patent adds a new dimension to the mobility management system by introducing a flag field that indicates whether the mobility is intra-CU or inter-CU. This dimensional addition allows the system to differentiate between scenarios and apply appropriate configuration methods, effectively expanding the application scope from only intra-CU to both intra-CU and inter-CU scenarios.
2Adaptability or versatility
If L3 based mobility is used for inter-CU scenarios, then the application scope is expanded, but mobility latency increases
Solution Approach 1:
The patent segments the mobility management approach based on the CU relationship, using LTM configuration for intra-CU scenarios (low latency) and L3 configuration for inter-CU scenarios (expanded scope). This segmentation allows each method to be applied in its most suitable context, optimizing both latency and applicability.
Solution Approach 2:
The patent introduces dynamic configuration where the mobility management approach (LTM or L3) is selected based on the specific scenario indicated by a flag field. This dynamic selection allows the system to adaptively choose the optimal method for each mobility event, balancing latency requirements with application scope needs.
3Adaptability or versatility
If inter-CU mobility is enabled with full L3 configuration, then mobility between different CUs is supported, but signaling overhead and complexity increase
Solution Approach 1:
The patent extracts only the essential elements needed for inter-CU mobility by using a flag field to indicate the mobility type. This extraction approach avoids the need for full L3 configuration in all scenarios, reducing signaling overhead and complexity while still enabling inter-CU mobility when required.
Solution Approach 2:
The patent applies partial configuration action by using a simplified flag-based mechanism instead of full L3 configuration for all mobility scenarios. This partial approach provides just enough configuration information to enable inter-CU mobility when needed, without the excessive complexity of complete L3 setup in every case.
Data Source
AI summary
A method of mobility management, a user equipment, and a base station are provided. The method includes receiving a network configuration, wherein the network configuration includes at least one candidate configuration, a serving cell's group identifier, and a group identifier for each of the at least one candidate configuration. Storing the serving cell's group identifier. Receiving a signaling for triggering a cell switching. The serving cell's group identifier is used by the UE to determine whether an inter-centralized unit (inter-CU) level configuration is needed or not upon the cell switching. The inter-CU level configuration includes at least one of the following: a security key update, a packet data convergence protocol (PDCP) entity re-establishment, or a radio resource control (RRC) configuration.