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

Glossary term · Mobility

MHI

Mobility History Information

Mobility →

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.

Introduced
Rel-17
Where
Management
Specifications
4 specs
MHI Description Purpose What changed Neighbours 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.

What changed in its specifications

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

TS 28.622Rel-18 → Rel-19

Rel-19 added external management data IOCs, discovery, notification retrieval, and single notifications. It added network slice lists in Area Scope, measurement conditions, and new data types for selecting instances via DNs, GeoAreas, or TAIs.

Full comparison in TS 28.622 →
TS 32.421Rel-18 → Rel-19

Rel-19 adds RRC report collection to TS 32.421 for NG-RAN, covering RLF, RCEF, RA, SHR, SPR and MHI reports. It also introduces new clauses, definitions and requirements for subscriber and equipment trace and QoE collection management.

Full comparison in TS 32.421 →

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.

Studied in Rel-17, normative work from Rel-19.

Rel-19 1 change
  • Correction on MHI for SCG active duration TS 38.306CR1482

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 vk40 Generic Network Resource Information Service Rel-20 read
TS 32.421 vj40 Subscriber & Equipment Trace Concepts & Requirements Rel-19 read
TS 32.422 vk30 Trace, MDT and UE Measurement Control Rel-20 read
TS 38.306 vj40 NR UE Radio Access Capability Parameters Rel-19 read