Conditional Handover Resource Reservation for Load Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current conditional handover (CHO) procedures in 5G networks face challenges in handling load variations, leading to potential PDU session drops due to resource unavailability at the target cell during handover execution, despite having free resources later, and inefficient resource reservation strategies.
Innovation Solution
Implementing a method where the target cell indicates a CONDITIONAL ACCEPT decision for PDU sessions during handover preparation, allowing the UE to attempt session establishment during handover execution, with the target cell making a final acceptance or rejection decision based on current load conditions, and using time-limited conditional acceptance to manage resource reservation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the target cell reserves resources during handover preparation, then service continuity is improved, but resource waste occurs when handover is not executed
Solution Approach 1:
The patent implements dynamic resource reservation where the target cell adjusts resource allocation based on handover execution status. Resources are reserved during preparation phase and automatically released if handover is not executed, converting static resource allocation to dynamic allocation that adapts to actual handover outcomes.
Solution Approach 2:
The patent extracts the resource reservation decision from the handover preparation phase and separates it from the handover execution phase. Resources are conditionally reserved only when needed, and the reservation is cancelled if handover conditions are not met, removing unnecessary resource occupation.
2Device complexity
If the target cell makes final handover decisions during preparation phase, then resource allocation is simplified, but adaptability to load variations is reduced
Solution Approach 1:
The patent implements preliminary resource reservation during handover preparation without making final binding decisions. The target cell prepares resource pools in advance and holds them temporarily, allowing later adjustment based on actual handover execution and load conditions, rather than committing resources prematurely.
Solution Approach 2:
The handover decision mechanism transitions from static pre-determination to dynamic post-preparation validation. The target cell validates handover decisions after preparation based on current load conditions, enabling adaptation to changing network states while maintaining resource allocation structure.
3Reliability
If resources are reserved for long duration in CHO scenarios, then service continuity is ensured, but resource utilization efficiency decreases
Solution Approach 1:
The patent implements periodic validation of handover decisions at the target cell after preparation. Instead of continuous long-term resource reservation, the system uses time-bounded resource holding with periodic checks whether handover execution has occurred, releasing resources if the validation period expires without execution.
Solution Approach 2:
The target cell receives feedback about handover execution status and adjusts resource reservation accordingly. When handover is executed, resources are confirmed; when not executed within expected timeframes, resources are released, creating a feedback-driven resource management system that balances continuity and efficiency.
Data Source
AI summary
Aspects of the present invention pertain to a method, comprising receiving a preparatory handover request pertaining to at least one or more physical resources, respectively associated to a particular communication service, preliminarily deciding on the feasibility of such preparatory handover request for each of said at least one or more physical resources associated to the particular communication service dependent on at least one feasibility criterion, and validating the preliminary decision on the feasibility of the preparatory handover request dependent on at least one validation criterion. Likewise, corresponding apparatus and computer program products are addressed, both from network entity perspective such as a gNB, as well as from a terminal's perspective, e.g. from a UE perspective.