DAPS Fallback RLF Reporting for Handover Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current RLF frameworks in wireless communication systems fail to accurately distinguish between radio link failures occurring before and after a Dual Active Protocol Stack (DAPS) fallback, leading to ambiguity in optimizing handover configurations and potentially resulting in suboptimal network performance.
Innovation Solution
A method is introduced to enhance the RLF reporting mechanism by storing and transmitting specific failure information in the RLF report, including time stamps and flags, to differentiate between failures occurring during handovers and those occurring after DAPS fallback, allowing the network to unambiguously categorize and optimize handover configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the current RLF framework is used to report radio link failures, then the reporting process is simple, but the network cannot accurately distinguish between failures occurring before and after DAPS fallback, leading to ambiguous handover optimization
Solution Approach 1:
The RLF report is segmented into distinct fields: a first failure information section for handover failures and a second failure information section for RLF after fallback. This segmentation allows the network to clearly distinguish between failures occurring before and after DAPS fallback without creating excessive complexity, as each segment has a specific purpose and format.
Solution Approach 2:
The patent adds a temporal dimension to the RLF report by introducing time stamp fields (first time stamp for handover failure, second time stamp for RLF) and a fallback indication field. This dimensional enhancement allows the network to locate failures in time sequence, clearly distinguishing between pre-fallback and post-fallback failures while maintaining report structure.
2Reliability
If detailed failure information is stored and transmitted in the RLF report, then the network can accurately optimize handover configurations, but the information transmission overhead increases
Solution Approach 1:
The patent extracts only the most critical failure information elements needed for handover optimization: failure timing (time stamps), failure type identification (fallback indication), and basic failure context. By extracting and transmitting only these essential elements rather than complete failure logs, the patent reduces information overhead while maintaining sufficient detail for accurate network optimization.
Solution Approach 2:
The RLF report structure applies local quality by providing detailed information only where needed: the first failure information section contains detailed handover failure data, while the second section contains RLF after fallback data. Each section is tailored to its specific purpose, avoiding unnecessary information transmission while ensuring accurate optimization at each failure type.
3Productivity
If the network optimizes handover configurations based on accurate failure timing, then network performance improves, but the complexity of analyzing and processing RLF reports increases
Solution Approach 1:
The patent implements a feedback mechanism where the RLF report provides structured failure information back to the network, which then adjusts handover configurations accordingly. The clear segmentation and time-stamping in the report enable automated feedback loops where the network can systematically analyze failure patterns and optimize parameters without requiring complex manual analysis, thereby improving productivity while managing processing complexity.
Solution Approach 2:
The patent enables parameter changes for handover optimization by providing the network with specific failure timing data (time stamps) and failure type identification. The network uses this information to adjust handover parameters such as timing thresholds, trigger conditions, and DAPS configuration. The structured report format simplifies the parameter adjustment process compared to unstructured failure data.
Data Source
AI summary
A method performed by a wireless device for reporting failure information in a self-organizing network, SON, is provided. The method includes receiving, from a source cell (“cell”) while being connected to the cell, a handover command to attempt a handover to a target cell, one or more bearers associated with the handover to the target cell being configured with a dual active protocol stack, DAPS. The method includes experiencing a failure while attempting the handover. The method includes storing first failure information associated with the failure. The method includes performing a DAPS fallback to the cell based at least in part on experiencing the failure. The method includes experiencing a radio link failure, RLF, while being connected to the cell. The method includes storing second failure information associated with experiencing the RLF. The method includes transmitting the first or second failure information towards the SON.