MRO

Mobility Robustness Optimisation

Management →
Introduced in Rel-10 Also in: Management

MRO is a Self-Organizing Network function that automatically detects and corrects handover parameter problems to minimize connection failures and unnecessary handovers by analyzing UE reports and failure events.

Category
Management
Introduced
Rel-10
Where
Radio Access Network › E-UTRAN (LTE)
Also touches
1 segments
Specifications
8 specs
MRO Description Purpose Related Classification Detected Changes Specifications

Description

Mobility Robustness Optimisation (MRO) is a core Self-Organizing Network (SON) function defined in 3GPP for LTE (E-UTRAN) and subsequent radio access technologies. Its primary objective is to automate the tuning of handover control parameters to optimize mobility performance. MRO operates by collecting and analyzing specific performance measurements and failure reports from the network. Key data sources include: Radio Link Failure (RLF) reports sent by UEs after reconnection, Handover Failure (HOF) reports, and regular measurement reports from UEs (e.g., Reference Signal Received Power - RSRP, Reference Signal Received Quality - RSRQ). The function runs within the Operation, Administration, and Maintenance (OAM) system or distributedly in base stations (eNBs/gNBs), depending on the SON architecture (Centralized, Distributed, or Hybrid).

The MRO algorithm identifies specific mobility failure patterns. The three main problems it detects are: 1) **Too Late Handover**: The handover is triggered after the radio link to the source cell has already degraded significantly, often leading to an RLF before or during the handover procedure. 2) **Too Early Handover**: The handover is executed successfully to a target cell, but the UE quickly suffers an RLF in the target cell and reconnects back to the source cell or a different cell. 3) **Handover to Wrong Cell**: The handover succeeds, but an RLF occurs shortly after in the target cell, and the UE reconnects to a third cell that was not the source or target. For each detected pattern, MRO correlates the failure with the specific cells involved and the handover parameter settings (primarily handover hysteresis, time-to-trigger, and cell individual offsets) that were active at the time.

Based on this analysis, MRO generates optimization actions. These are typically recommendations or automatic adjustments to the handover control parameters for the relevant cell pairs (neighbor relations). For a "Too Late Handover" from Cell A to Cell B, MRO might suggest decreasing the handover threshold or hysteresis for that direction. For a "Too Early Handover," it might suggest increasing the threshold or time-to-trigger. The adjustments are applied cautiously, often in small steps, and their impact is monitored to ensure stability and avoid oscillating parameters. MRO works continuously, adapting to changes in the radio environment, user distribution, and network topology, thereby maintaining optimal mobility performance with minimal manual intervention.

Purpose & Motivation

MRO was created to address a major operational challenge in cellular networks: the manual, time-consuming, and error-prone process of optimizing handover parameters. Before SON, network engineers had to manually analyze drive test data and Key Performance Indicators (KPIs) like handover success rate, then trial-and-error adjust parameters for thousands of cell neighbor relationships. This process was static, could not react quickly to daily or seasonal changes in traffic and propagation, and often led to suboptimal settings that caused dropped calls, poor user experience, and inefficient resource usage.

The drive for SON and MRO specifically was motivated by the increasing complexity of networks (more cells, heterogeneous deployments) and the need to reduce operational expenditure (OPEX). MRO automates this optimization loop. It solves the problems of late/early handovers which are primary causes of call drops and poor service continuity. By minimizing Radio Link Failures and unnecessary handovers (ping-pong), MRO directly improves end-user perceived quality, increases network reliability, and reduces signaling load on the network. Its introduction in LTE Release 10 was a foundational step towards fully autonomous networks, enabling efficient operation of dense and complex future RAN deployments like those with small cells.

Classification

Part ofSON
Related approachesANRPCI

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 1 change

In Release 16, the MRO function was enhanced with a correction to the Radio Link Failure (RLF) reporting procedure for inter-RAT scenarios involving NR. The specification also introduced explicit configuration parameters for the function, such as a parameter to enable or disable probing and the "minimumTimeBetweenHoTriggerChange" parameter to control the rate of handover trigger adjustments.

  • Correction on RLF Report for Inter-RAT MRO NR TS 36.306CR1778

Explore further

Broader topics and technologies where MRO plays a role.

Defining Specifications

3GPP specifications that define or reference MRO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 28.628 vj00 SON Policy NRM IRP Information Service Rel-19
TS 28.861 vg00 SON for 5G Networks Management Rel-16
TS 32.522 vb70 SON Policy NRM IRP Information Service Rel-11
TS 36.306 vj00 E-UTRA UE Radio Access Capability Parameters Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 36.887 vc00 Energy Saving Enhancement for E-UTRAN Study Rel-12
TS 37.816 vg00 RAN-centric Data Collection & Utilization Study Rel-16
TS 37.822 vc10 SON Enhancements for UE Types and Active Antennas Rel-12
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.