Handover Failure Synchronization for Wireless Communication Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless communication systems face challenges in synchronizing continuous packet connectivity (CPC) configuration and other cell-controlled parameters between a mobile device and a serving cell after a handover failure, leading to potential interference and battery life issues.
Innovation Solution
A method and apparatus for synchronizing CPC configuration parameters between a user equipment (UE) and a Node B, involving failure recovery mechanisms that revert to default or last known configurations of DTX and DRX modes, ensuring seamless reconnection and minimizing interference.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a mobile device returns to the source cell upon handover failure, then communication continuity is restored, but synchronization of CPC configuration parameters between the device and serving cell becomes misaligned
Solution Approach 1:
The patent applies preliminary action by having the mobile device store the CPC configuration parameters from the source cell before initiating handover. When handover fails and the device returns to the source cell, it retrieves and re-applies the stored configuration parameters, ensuring synchronization is restored without requiring re-transmission from the network.
Solution Approach 2:
The patent implements feedback by having the mobile device monitor handover status and detect failures. Upon detecting handover failure, the device triggers a feedback mechanism that retrieves the stored CPC configuration and re-applies it, then confirms synchronization status. This closed-loop feedback ensures the configuration remains synchronized between the device and serving cell.
2Loss of information
If the mobile device continuously monitors and maintains CPC configuration synchronization after handover failure, then parameter alignment is improved, but device complexity and processing overhead increase
Solution Approach 1:
The patent reduces complexity by performing preliminary action during normal operation - the device stores CPC configuration parameters in memory before handover occurs. This pre-stored configuration is readily available for quick retrieval upon handover failure, eliminating the need for complex real-time synchronization protocols and reducing processing overhead.
Solution Approach 2:
The patent applies self-service by enabling the mobile device to autonomously detect handover failure, retrieve its stored CPC configuration parameters, and re-apply them without requiring complex network coordination or additional signaling. The device independently resolves the synchronization issue, reducing overall system complexity.
3Loss of time
If the mobile device re-applies CPC configuration parameters immediately upon returning to source cell, then synchronization is restored faster, but potential conflicts with updated network parameters may occur
Solution Approach 1:
The patent uses feedback to balance speed and reliability - the device re-applies stored CPC configuration parameters upon returning to the source cell, then monitors for any parameter conflicts or inconsistencies. If conflicts are detected, the device triggers a feedback loop to request updated parameters from the network, ensuring consistency while maintaining fast initial recovery.
Solution Approach 2:
The patent applies partial action by having the device re-apply only the critical CPC configuration parameters that are most likely to be out of sync, rather than completely resetting all parameters. This selective re-application restores synchronization faster while minimizing the risk of introducing conflicts, and allows incremental updates if needed.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems and methodologies are described herein that facilitate synchronization of Node B-ordered parameters, such as discontinuous transmission (DTX)/discontinuous reception (DRX) status, following a handover failure and/or other suitable triggering events. As described herein, upon failure of a handover from a source Node B to a target Node B, a mobile device can return to the source Node B and synchronize with the source Node B with respect to DTX/DRX status and/or other Node B-ordered parameters. DTX/DRX synchronization can be performed by setting DTX/DRX status to a default state, a last DTX/DRX state utilized prior to initiation of the failed handover, or the like. Identification of the last DTX/DRX state can be conducted as described herein according to an analysis of respective orders communicated by the source Node B in relation to respective time intervals following initiation of the failed handover.