Stale Failure Report Classification for Mobility Robustness
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cellular communication networks face challenges in efficiently handling mobility connection failures during handovers between different Radio Access Technologies (RATs), leading to stale failure reports that can result in incorrect mobility adjustments and slow convergence to stable mobility.
Innovation Solution
Implementing a system that classifies failure reports as stale or current based on timing data, where reports received after recent mobility adjustments are considered with reduced relevance or discarded, ensuring timely mobility optimization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all failure reports are processed for mobility optimization, then the network can capture all potential mobility issues, but stale reports cause incorrect adjustments and slow convergence
Solution Approach 1:
The system performs preliminary classification of failure reports as stale or current by comparing report timestamps with the timing of the most recent mobility adjustment. This preliminary action filters out stale reports before they can cause incorrect mobility adjustments, ensuring that only relevant reports influence optimization decisions and enabling faster convergence to stable mobility parameters.
2Productivity
If mobility parameters are adjusted frequently to respond to failure reports, then the network can quickly adapt to mobility issues, but adjustments based on stale reports lead to incorrect optimizations
Solution Approach 1:
The system implements feedback by classifying failure reports based on their temporal relationship to mobility adjustments. Reports are marked as stale if they predate the most recent adjustment, preventing feedback loops that would cause repeated or incorrect adjustments. This feedback mechanism ensures that mobility optimization responds only to current, relevant failure patterns rather than historical anomalies.
3Measurement precision
If the network waits for failure reports before making mobility adjustments, then adjustments can be data-driven, but stale reports delay the effectiveness of optimization
Solution Approach 1:
The system performs preliminary classification of failure reports as stale or current by comparing report timestamps with the timing of the most recent mobility adjustment. This preliminary action filters out stale reports before they can cause incorrect mobility adjustments, ensuring that only relevant reports influence optimization decisions and enabling faster convergence to stable mobility parameters.
Data Source
AI summary
The present disclosure relates to identifying stale failure reports in a cellular communications network. In one embodiment, a node in a cellular communications network receives a failure report associated with a connection failure for a user equipment and determines when the connection failure occurred with respect to a most recent mobility adjustment made by the node. If the connection failure occurred before the most recent mobility adjustment made by the node, the node classifies the failure report as a stale failure report. In one embodiment, if the failure report is classified as a stale failure report, the node discards the failure. In another embodiment, if the failure report is classified as a stale failure report, the node considers the failure report with reduced relevance for a next iteration of a process to determine whether new mobility adjustments are desired.