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

Glossary term · Mobility

SHR

Successful Handover Report

Mobility →

SHR is a 5G data report from a target to a source base station providing detailed information on a completed handover for network optimization and troubleshooting.

Introduced
Rel-17
Where
Management
Specifications
5 specs
Also in
Radio Access Network
SHR Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Successful Handover Report (SHR) is a key enabler for advanced mobility management and Self-Organizing Network (SON) functionalities in 5G NR and evolved LTE networks. It is a structured message generated by the target node (gNB or eNB) upon the successful completion of a handover and sent back to the source node. Unlike basic handover completion signals, the SHR contains a rich set of contextual data about the radio conditions and configuration at the moment of handover execution. This report is defined within the context of the Xn Application Protocol (XnAP) and NG Application Protocol (NGAP) for inter-gNB and inter-system communication, as referenced in specifications like TS 38.423 and TS 38.413.

The report's content is comprehensive. It typically includes the Cell Radio Network Temporary Identifier (C-RNTI) assigned to the User Equipment (UE) in the target cell, detailed measurement results reported by the UE just before the handover (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ)), and the specific configuration of the radio bearers that were successfully established. Furthermore, it can contain timestamps and identifiers for the specific handover command. This granular data allows the source node to build a historical record of handover outcomes correlated with the radio conditions that triggered the handover decision.

Architecturally, the SHR flows over the Xn interface between gNBs or the NG interface between an eNB and a 5GC. Its generation and consumption are integral to Mobility Robustness Optimization (MRO) algorithms. By analyzing sequences of SHRs (and their counterpart, the Handover Failure Report), the network can detect issues like too-early, too-late, or handovers to wrong cells. The source node can then adjust its handover control parameters, such as hysteresis margins, time-to-trigger, or cell individual offsets, in an automated or semi-automated manner. This closed-loop optimization is vital for maintaining seamless mobility in dense, heterogeneous 5G deployments with complex interference scenarios.

Purpose & Motivation

The SHR was introduced to address the limitations of earlier mobility management systems, which often relied on simplistic success/failure indicators or required extensive drive testing and manual analysis to optimize handover parameters. In 4G LTE, SON features began automating optimization, but the data exchange was often less detailed. The advent of 5G, with its use of higher frequencies (mmWave), ultra-dense networks, and demanding use cases like ultra-reliable low-latency communication (URLLC), created a pressing need for more intelligent and data-driven mobility management.

The primary problem SHR solves is the lack of visibility for the source node into the *result* of its handover decision. Before SHR, a source node would command a handover and might receive an acknowledgment of completion, but not the detailed context of *why* it succeeded under those specific radio conditions. This made troubleshooting suboptimal handovers and fine-tuning algorithms inefficient. The SHR provides this crucial feedback, enabling the source node to learn from every handover event. Its creation was motivated by the desire to enhance SON capabilities, reduce operational expenditure (OPEX) by minimizing manual optimization, and fundamentally improve mobility robustness—a critical factor for user experience and network performance in advanced 5G systems.

What changed in its specifications

The latest release-to-release comparison of specifications that define SHR. 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 →

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 2 changes

Defining Specifications

3GPP specifications that define or reference SHR, 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 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read