The number of users on a cell and the data usage of each of them can be modelled as **random variables** that differ depending on the date or time. This leads to **unequal load scenarios** for neighbouring cells. It may happen that, at a given time, **a cell is overloaded**, while its neighbour cell is underloaded. The quality of the service on the overloaded cell may not meet the QoS requirements while, on the underload cell, the resources are not being fully used. The **Mobility Load Balancing feature** is in charge of detecting the load imbalance and reassigning the users on all the available cells within a zone. This way, an efficient usage of the radio resources of the network is performed while granting the quality of service of the users. The Load balancing can be performed in two scenarios: - **Intra-LTE Load Balancing** - **Inter-RAT Load Balancing** In both scenarios, the eNodeBs need to have information about the load of the neighbour cells to take the appropriate action for the loading balance. On the IntraLTE scenario, the eNodeBs exchange load information through the X2 interface while on the Inter-RAT scenario, the information exchange is done through the S1 interface. These reports are also essential to avoid unnecessary handovers and inter-RAT ping-pong handovers. This use case is strongly tied to [[Mobility Robustness Optimisation]]. Use Case focuses on **reallocating the load of a zone** and, to do so, it is needed to tune handover parameters. This way, users on overloaded cells can be forced into underloaded neighbouring cells and, thus, re-distribute the load. #telco