Excluding Non-Mobility Data from Mobility KPIs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In telecommunications systems, mobility robustness optimization (MRO) is impacted by mobility load balancing (MLB) actions, leading to inaccurate radio link failure and handover oscillation statistics, which can result in unfavorable performance indicators and incorrect adjustments in handover parameters.
Innovation Solution
A node in the telecommunications system is configured to exclude handover statistics and events caused by non-mobility factors, such as load balancing and cell maintenance, from the mobility robustness optimization statistics, using a non-mobility causation filter to differentiate between mobility-related and non-mobility-related issues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If mobility load balancing actions are included in mobility robustness optimization statistics, then network resource allocation is improved, but measurement precision of mobility-related failures deteriorates
Solution Approach 1:
The patent segments handover failures into two distinct categories: those caused by mobility issues (radio conditions, signal strength) and those caused by non-mobility issues (load balancing, cell maintenance, resource allocation). By separating these failure types into different statistical buckets, the system can accurately measure mobility-related failures while still benefiting from load balancing operations, thus resolving the contradiction between resource allocation efficiency and measurement precision.
2Adaptability or versatility
If all handover failures are used for mobility robustness optimization, then optimization coverage is improved, but adjustment accuracy deteriorates due to non-mobility causes
Solution Approach 1:
The patent extracts and removes handover failures caused by non-mobility factors (load balancing actions, cell maintenance activities, resource allocation issues) from the mobility robustness optimization statistic set. This extraction process ensures that only genuine mobility-related failures are used for adjusting handover parameters, thereby maintaining high adjustment accuracy while still providing comprehensive optimization coverage for actual mobility issues.
3Quantity of substance
If non-mobility causations are included in mobility statistics, then data completeness is improved, but data purity deteriorates
Solution Approach 1:
The patent applies local quality by creating different quality standards for different types of statistics data. Mobility-related failures are collected with high purity and accuracy for MRO purposes, while non-mobility failures are separately categorized and excluded from mobility statistics. This approach maintains data completeness across all failure types while ensuring that mobility-specific statistics maintain high purity and reliability for accurate performance evaluation.
Data Source
Figure 1~2
Figure 3A~3B
Figure 4~5
AI summary
Handover (HO) statistics and handover issue events which are due to non-mobility causes are not included in the statistics fed into mobility robustness optimization (MRO). The non-mobility causes may include, e.g., load balancing, retracting users to prepare for cell maintenance or restart/reconfiguration and cell outage including compensation means. Radio link failure (RLF), handover failure (HOF), and handover oscillations (HOosc) that are due to non-mobility cause are excluded from the statistics upon which mobility robustness optimization is based. Non-mobility causes are also differentiated from mobility causes when reporting key performance indicators to an operator.