Description
Immediate Handover is a mobility concept introduced in 3GPP Release 16 in the context of Conditional Handover (CHO). In a conventional (non-conditional) handover, the network sends a Handover Command (RRCReconfiguration with a reconfigurationWithSync for NR, or RRCConnectionReconfiguration with mobilityControlInfo for LTE) and the UE is expected to execute the handover as soon as it receives and processes that command. This is what 3GPP refers to as an Immediate Handover: the execution is not gated by any additional condition evaluated by the UE; the reception of the command itself is the trigger.
The term became necessary when CHO was standardized. In CHO, the network prepares one or more candidate target cells in advance and provides the UE with a CHO configuration containing execution conditions (for example, a measurement-based threshold on a candidate cell). The UE stores this configuration and only executes the handover when the associated condition is satisfied. To describe the contrast between this deferred, condition-based execution and the classical behaviour, 3GPP introduced the notion of Immediate Handover. In other words, Immediate Handover is not a new procedure but a label for the legacy handover execution model viewed from within the CHO framework.
Architecturally, Immediate Handover involves the same nodes as any inter-node handover: the source gNB/eNB decides to hand over the UE, performs handover preparation over the Xn (38.423) or X2 (36.423) interface with the target node, and sends the Handover Command to the UE. The UE then detaches from the source cell, synchronizes to the target cell, and completes the random access and RRC reconfiguration procedure. The key differentiator is purely the timing of execution: there is no intermediate condition evaluation phase and no need for the UE to keep a prepared configuration pending.
In the specifications, the term appears in the stage-3 inter-node signalling documents 36.423 (E-UTRAN X2 Application Protocol) and 38.423 (NG-RAN Xn Application Protocol), where it is used to describe handover behaviour and to distinguish immediate execution from conditional execution in the information elements and procedures related to mobility. The concept helps implementers and test engineers reason about UE behaviour: in Immediate Handover, the UE must act on the command without delay, whereas in CHO it must monitor conditions and may never execute a given prepared candidate.
From a deployment perspective, Immediate Handover remains the dominant mobility mechanism in live networks. CHO is an enhancement that improves robustness at cell edges by preparing multiple candidates, but the baseline immediate model is still used for the majority of handovers, especially where radio conditions are stable and the source cell can make a reliable decision. Understanding the distinction is therefore essential for anyone analysing handover performance, mobility robustness optimisation (MRO), or the interaction between legacy mobility and CHO features.
Purpose & Motivation
The concept exists to provide precise terminology for the timing of handover execution. Before CHO, all handovers were effectively immediate, so no special term was needed. With the introduction of Conditional Handover in Release 16, the standard needed a way to refer to the classical behaviour—execute as soon as the command is received—without ambiguity. Immediate Handover fills that terminological gap.
It solves the problem of describing and specifying UE behaviour in a mixed environment where some handovers are conditional and some are not. Network implementations, test specifications, and inter-node signalling all need to distinguish between a UE that must act immediately and one that must wait for a condition. By naming the immediate case, 3GPP enables clearer procedure descriptions and more precise conformance requirements.
The motivation is rooted in mobility robustness. Classical immediate handover can fail if the Handover Command is lost or arrives too late as radio conditions deteriorate. CHO addresses this by preparing candidates early, but it does not replace immediate handover; it complements it. Immediate Handover therefore remains the reference behaviour against which CHO gains are measured, and the term helps engineers understand which execution model applies in a given scenario.
What changed in its specifications
The latest release-to-release comparison of specifications that define Immediate Handover. Each summary describes the whole specification, not only this term.
Rel-13 added enhanced signalling for inter-eNB CoMP with CSI reporting to RESOURCE STATUS procedures, SON for AAS with relative narrowband transmit power reporting and cell coverage modification, and multicarrier load distribution with X2 removal, coverage state, cell replacement, and band priority signalling.
Full comparison in TS 36.423 →Rel-19 adds OD-SIB1 configuration provision messages and TA Information Transfer, LTM Cancel and CSI-RS Coordination procedures to TS 38.423. It also adds SON/MDT data collection with CLI Indication and SCG Failure Indication, XR IEs for ECN marking and PDU Set QoS, and RedCap LP-WUS paging IEs.
Full comparison in TS 38.423 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial introduction of the term in the context of Conditional Handover, defining an Immediate Handover as one executed immediately after the UE receives the Handover Command. This established the terminological distinction between classical and conditional handover execution.
Defining Specifications
3GPP specifications that define or reference Immediate Handover, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.423 vj10 | X2 Application Protocol (X2AP) Specification | Rel-19 read |
| TS 38.423 vj40 | NG-RAN Xn Application Protocol | Rel-19 read |