MHI

Mobility History Information

Mobility →
Introduced in Rel-17

MHI is a data record containing a UE's past mobility patterns, such as previous cell associations, which the network uses to predict future mobility for more efficient handover decisions and optimization.

Category
Mobility
Introduced
Rel-17
Where
Management
Specifications
4 specs
MHI Description Purpose Detected Changes Specifications

Description

Mobility History Information (MHI) is a structured data set generated and maintained by the User Equipment (UE) and/or the network, detailing the UE's historical mobility behavior. This information is primarily defined within the context of the Radio Resource Control (RRC) protocol in 5G New Radio (NR). The UE typically logs key mobility events, such as successful handovers, connection re-establishments, and cell reselections, along with associated parameters like the identities of source and target cells, timestamps, and radio conditions at the time of the event. This log forms the MHI record.

The network, specifically the Next Generation NodeB (gNB), can request this information from the UE via RRC signaling, such as during a UE Information Request procedure. Upon receiving the request, the UE provides the MHI report. The gNB's Radio Resource Management (RRM) functions then process this historical data. By analyzing patterns—such as frequent handovers between specific cells, typical movement trajectories, or failure-prone areas—the RRM algorithms can build a predictive model of the UE's mobility.

This predictive capability is central to MHI's operation. For instance, if a UE's history shows it consistently moves from Cell A to Cell B after a short dwell time in Cell A, the serving gNB can proactively prepare resources in Cell B or even initiate a conditional handover earlier and more reliably. This reduces handover failure rates and interruption time. Furthermore, MHI aids in network-centric optimizations. Network Management Systems (NMS) or the gNB itself can aggregate MHI reports from multiple UEs to identify systemic issues like cell coverage holes, persistent interference zones, or unbalanced traffic loads between neighboring cells, guiding corrective configuration changes.

The specifications governing MHI, such as 3GPP TS 38.306 (UE radio access capabilities) and the 28.622/32.42x series (management), define the information elements, reporting procedures, and management aspects. MHI enhances traditional, instantaneous-measurement-based mobility management by adding a temporal dimension, allowing the network to make decisions based on learned behavior rather than just a snapshot of current radio conditions.

Purpose & Motivation

MHI was introduced to address the challenges of mobility management in increasingly dense and heterogeneous 5G and beyond networks. Traditional handover decisions rely heavily on real-time measurement reports (e.g., Reference Signal Received Power - RSRP). While effective, this reactive approach can struggle with high-speed scenarios, ultra-dense deployments, and complex multi-beam environments, leading to late, failed, or unnecessary handovers (ping-pong effects). These failures degrade user experience and consume unnecessary signaling resources.

The core problem MHI solves is the lack of context in mobility decisions. By providing a history of the UE's movements, the network gains predictive insight. This allows for more proactive and intelligent resource management. For example, it enables predictive handovers where the target cell is prepared in advance based on the UE's trajectory, significantly reducing the risk of handover failure and data interruption. This is critical for supporting seamless mobility for use cases like vehicular communications (V2X) and high-speed trains.

Furthermore, MHI supports advanced network automation and Self-Organizing Network (SON) functions. By collecting mobility histories from a population of UEs, operators can perform data-driven optimization of cell boundaries (mobility robustness optimization), antenna tilts, and handover parameters. This moves network tuning from a reactive, manual process to a proactive, data-centric one, improving overall network efficiency and stability. Its specification across both radio access (38-series) and management (28/32-series) standards underscores its role as a key enabler for intelligent, automated 5G systems.

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 2 changes

In Release 16, the MHI (Mobility History Information) function was newly introduced within the generic NRM Information Service framework. This update specifically enabled support for a Managed NF Service Object as part of the management model. Furthermore, the associated class definitions were enhanced to include inheritance information, ensuring alignment with the overarching Federated Network Information Model (FNIM) concept.

  • Update generic NRM Information Service to support Managed NF Service Object TS 28.622CR0033
  • Update class definition with inheritance information TS 28.622CR0038
Rel-17 3 changes

In Release 17, the MHI (Mobility History Information) function was enhanced within the Network Resource Model (NRM) to include geographical information supporting MDA. This introduction of mobility-state-based cell reselection for NR HSDN was a key new procedure, alongside corrections to network assistance information for CRS-IM.

  • Enhance NRM with geographical information supporting MDA TS 28.622CR0131
  • Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN] TS 38.306CR0650
  • Corrections on CRS-IM network assistance information TS 38.306CR0803
Rel-18 3 changes

In Release 18, the MHI (Mobility History Information) function was enhanced with new parameters for MDT Alignment Information and Available RAN Visible QoE Metrics. Furthermore, clarifications were introduced for the UE capability on uplink traffic information. A correction was also made regarding the optionality of NR-U related information within the function.

  • Definition of parameters MDT Alignment Information and Available RAN Visible QoE Metrics TS 28.622CR0206
  • Clarification for UE capability on UL traffic information TS 38.306CR1182
  • Correction in the optionality of NR-U related information TS 38.306CR1221
Rel-19 3 changes

In Release 19, the MHI (Mobility History Information) function was enhanced to introduce UAV mobility information support and to incorporate UE assistance information for cell DTX/DRX procedures. Additionally, the speed state of a UE in RRC_CONNECTED was added as a new parameter within the mobility history reporting mechanism. These updates expanded the types of mobility-related data collected to support more advanced network optimization and mobility management for both traditional user equipment and new use cases like unmanned aerial vehicles.

  • Introduction of UAV mobility enhancements [UAV_Mobility] TS 38.306CR1319
  • Introduction of UE assistance information for cell DTX/DRX [UAI_cellDTRX] TS 38.306CR1352
  • Adding Mobility State in RRC_CONNECTED [SpeedStatePars] TS 38.306CR1395

Explore further

Broader topics and technologies where MHI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 28.622 vk20 Telecommunication Management; Generic NRM Information Service Rel-20
TS 32.421 vj30 Subscriber & Equipment Trace Concepts & Requirements Rel-19
TS 32.422 vk00 Telecom Management: Trace Control & Configuration Rel-20
TS 38.306 vj00 NR UE Radio Access Capability Parameters Rel-19