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

Glossary term · Management

LB

Load Balancing

Management →

LB is a network management function that distributes traffic, users, or sessions across multiple resources to optimize utilization, prevent congestion, and enhance capacity and reliability.

Introduced
Rel-8
Where
Management
Specifications
13 specs
Also in
Radio Access Network, Testing
LB Description Purpose What changed Neighbours Specifications

Description

Load Balancing (LB) in 3GPP systems is a comprehensive set of algorithms and procedures designed to evenly distribute network load across available resources. This load can refer to user equipment (UE) connections, radio resource usage, computational load on network functions, or data traffic. The primary goal is to prevent individual cells, carriers, or network elements from becoming overloaded while others are underutilized, thereby maximizing overall network capacity and efficiency. LB operates across multiple domains: radio access network (RAN) between cells, between carriers (frequency layers), between Radio Access Technologies (RATs), and within the core network between instances of virtualized network functions.

In the RAN, Load Balancing is typically managed by the eNodeB in LTE or the gNodeB in NR, often with coordination from a central entity like the Operation, Administration, and Maintenance (OAM) system or a RAN Intelligent Controller (RIC) in more advanced architectures. The process involves continuous monitoring of Key Performance Indicators (KPIs) such as resource block utilization, number of connected UEs, PRB usage, and hardware load. When a load imbalance is detected—for instance, one cell is above a high-utilization threshold while a neighboring cell is below a low-utilization threshold—the LB algorithm triggers actions. The most common action is handover-based load balancing, where the network initiates handovers for selected UEs from the overloaded cell to the underloaded neighbor. This is known as Mobility Load Balancing (MLB).

LB mechanisms are sophisticated and consider multiple factors to avoid ping-pong effects and service degradation. Algorithms use hysteresis, thresholds, and filtering to ensure stability. They also consider UE capability, radio channel conditions, and QoS requirements of active bearers to select suitable UEs for handover. For example, a UE with a non-GBR bearer at the cell edge might be prioritized for load-balancing handover over a UE with a GBR bearer in good conditions. In carrier aggregation scenarios, LB can also involve adjusting the secondary cell group (SCell) addition/removal policies. Furthermore, in multi-RAT environments (e.g., LTE-NR dual connectivity, LTE-WiFi), Inter-RAT Load Balancing can steer traffic or idle-mode UEs to the most appropriate RAT based on load and capability.

In the core network, especially with cloud-native 5G Core (5GC), Load Balancing is crucial for stateless and scalable network functions (NFs). The Network Repository Function (NRF) facilitates service discovery and load balancing among multiple instances of a given NF type (e.g., multiple AMF instances). When a UE registers or an NF requires a service, the consumer NF queries the NRF, which can return a list of producer NF instances filtered and prioritized based on their current load, capacity, and locality. This ensures no single NF instance becomes a bottleneck. Overall, Load Balancing is a dynamic, multi-layered optimization process that is fundamental to the automated, efficient, and resilient operation of modern 3GPP networks.

Purpose & Motivation

Load Balancing was introduced to solve the inherent inefficiency and performance degradation caused by uneven traffic distribution in cellular networks. Early cellular systems often experienced 'hotspot' cells in dense urban areas or during events, leading to congestion, high blocking rates, and poor user experience, while neighboring cells remained underused. This imbalance arose from non-uniform user distribution, geographical factors, and varying cell configurations. Without LB, network capacity is effectively limited by the most congested cell, wasting capital investment in underutilized infrastructure.

The primary purpose of LB is to maximize the utilization of all deployed network resources, thereby increasing total system capacity and throughput. By proactively moving users from congested areas to less busy ones, LB alleviates congestion, reduces call drops and access failures, and improves the overall Quality of Service (QoS) and Quality of Experience (QoE) for all users. It transforms a collection of individual cells into a coordinated, elastic resource pool. This is especially critical with the advent of heterogeneous networks (HetNets) featuring macro cells, small cells, and different frequency bands, where manual optimization of traffic distribution is impractical.

Furthermore, LB enhances network robustness and reliability. It acts as a preventive measure against node failures by avoiding extreme overload conditions that could lead to software or hardware failures. In the context of network slicing, LB ensures that resources are fairly allocated among slices according to their SLAs. With the move to cloud-native, software-based 5G core networks, LB is essential for auto-scaling and elasticity. It allows the network to dynamically adjust to traffic patterns, enabling efficient use of cloud resources and supporting the on-demand nature of 5G services. In summary, Load Balancing is a key enabler for the high-capacity, self-optimizing, and reliable networks required for modern mobile broadband and critical communications.

What changed in its specifications

The latest release-to-release comparison of specifications that define LB. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 28.628Rel-14 → Rel-15

Added SON for AAS management clauses, new attributes for AAS switches/load rates, and performance measurement support.

Full comparison in TS 28.628 →

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-8 Initial

Introduced basic Mobility Load Balancing (MLB) for LTE as a self-organizing network (SON) function. Initial capabilities focused on intra-LTE load balancing between eNodeBs using the X2 interface, based on simple metrics like Radio Resource Utilization. It allowed eNodeBs to exchange load information and trigger handovers to alleviate congestion.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19 read
TS 28.627 vj00 SON Policy NRM IRP: Requirements Rel-19 read
TS 28.628 vj00 SON Policy NRM IRP Information Service Rel-19 read
TS 28.861 vg00 SON for 5G Networks Management Rel-16 read
TS 32.521 vb10 SON Policy NRM IRP Requirements Rel-11 read
TS 32.522 vb70 SON Policy NRM IRP Information Service Rel-11 read
TS 34.109 vj00 UE Conformance Test Functions for UMTS Rel-19 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.509 vi00 UE Conformance Test Loop Functions Rel-18 read
TS 37.852 vc00 RAN Enhancements for UMTS/HSPA and LTE Interworking Rel-12 read
TS 38.509 vj00 5GS UE Special Conformance Test Functions Rel-19 read