Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Mobility

MLB

Mobility Load Balancing

Mobility →

MLB is a self-organizing network function that redistributes traffic across neighboring cells by adjusting mobility parameters to relieve congestion and improve resource utilization.

Introduced
Rel-12
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
3 specs
MLB Description Purpose Neighbours Specifications

Description

Mobility Load Balancing (MLB) is a Self-Organizing Network (SON) use case that automatically balances the traffic load across cells in a radio access network. When one cell becomes congested while neighbouring cells have spare capacity, MLB adjusts mobility parameters—such as handover thresholds, cell individual offsets, and cell reselection parameters—to encourage UEs at the cell edge to move to less loaded cells, or to redistribute load through handover decisions. The goal is to maximize overall network utilization and user experience without manual intervention.

MLB operates through a control loop involving the Operations, Administration and Maintenance (OAM) system and the eNodeB/gNodeB. The OAM system configures policies and thresholds, while the base station monitors load indicators such as physical resource block utilization, number of active UEs, and hardware load. When a load imbalance is detected, the base station exchanges information with neighbouring cells over the X2 interface (in LTE) or Xn interface (in NR) using load indication messages. These messages convey resource status and load levels, enabling coordinated decisions.

The function distinguishes between intra-RAT and inter-RAT load balancing. Intra-RAT MLB adjusts handover and reselection parameters between cells of the same technology, while inter-RAT MLB manages load between, for example, LTE and NR or between different frequency layers. MLB also interacts with Mobility Robustness Optimization (MRO), which handles handover failures and unnecessary handovers; the two functions must be coordinated to avoid conflicting parameter adjustments.

Key mechanisms include load reporting, handover parameter tuning, and cell reselection offset adjustment. MLB can also trigger handovers for load reasons even when radio conditions would not normally require them, provided that the target cell can accept the UE and that service continuity is maintained. The function must respect constraints such as avoiding ping-pong handovers and ensuring that offloaded UEs still receive adequate coverage and quality.

In 5G, MLB continues as part of the NG-RAN SON framework, with load information exchanged over Xn and coordination across centralized and distributed RAN architectures. The specifications in 32.860 (SON management), 36.856 (E-UTRAN SON), and 37.816 (NG-RAN SON) define the procedures, measurements, and policies that enable standardized, multi-vendor MLB operation.

Purpose & Motivation

MLB exists to solve the problem of uneven traffic distribution in cellular networks. In real deployments, user demand is rarely uniform: some cells become hotspots while adjacent cells are underutilized. Without automated load balancing, operators would need to manually tune handover and reselection parameters, a slow and error-prone process that cannot keep up with dynamic traffic patterns. MLB automates this tuning, improving capacity utilization and reducing congestion.

Historically, network optimization was a manual, drive-test-driven activity. The introduction of SON in 3GPP Release 8 and its expansion in later releases aimed to reduce operational expenditure and improve network performance through self-configuration and self-optimization. MLB was formalized as a SON use case to address load imbalances that degrade user experience, such as reduced throughput in congested cells.

MLB also supports energy efficiency and multi-layer coordination, allowing operators to shift traffic away from lightly loaded cells that could be powered down or reconfigured. By standardizing load information exchange and parameter adjustment procedures, 3GPP enables multi-vendor interoperability and consistent behaviour across network elements.

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-12 Initial

Initial formalization of MLB as a SON use case with standardized load reporting, handover parameter tuning, and OAM coordination procedures for E-UTRAN.

The term carried over unchanged; no revision to the MLB definition text is indicated in the available wording.

The term carried over unchanged; no revision to the MLB definition text is indicated in the available wording.

Defining Specifications

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

SpecificationTitleRelease
TS 32.860 ve00 D-SON MLB OAM Enhancement Study Rel-14 read
TS 36.856 vc00 RAN Sharing Enhancements for LTE Study Rel-12 read
TS 37.816 vg00 RAN-centric Data Collection & Utilization Study Rel-16 read