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

Glossary term · Mobility

Late Data Forwarding

Late Data Forwarding

Mobility →

Late Data Forwarding is a handover data forwarding scheme in NG-RAN where the source node begins forwarding user-plane data only after the UE successfully accesses the target node, reducing unnecessary forwarding and improving resource efficiency.

Introduced
Rel-16
Where
Radio Access Network › NG-RAN (5G)
Specifications
2 specs
Late Data Forwarding Description Purpose What changed Neighbours Specifications

Description

Late Data Forwarding (LDF) is a mobility enhancement introduced in 3GPP Release 16 for NG-RAN (5G NR and evolved LTE connected to 5GC) handover procedures, specified in TS 38.300 and TS 36.300. During an inter-node handover, user-plane data buffered at the source NG-RAN node may need to be delivered to the target node so that no packets are lost. Traditional (early) data forwarding starts as soon as the source decides to hand over the UE, i.e., before the target has confirmed that the UE has actually reached it. Late Data Forwarding instead defers the start of forwarding until the source node receives confirmation that the UE has successfully accessed the target NG-RAN node.

The procedure works as follows. The source node initiates handover via the Handover Request/Handover Request Acknowledge exchange over the Xn interface. In the Handover Request Acknowledge, the target provides forwarding tunnel information (e.g., downlink forwarding UPF/TNL addresses) as usual. However, with LDF the source does not immediately begin pushing buffered downlink data. Instead, it continues to buffer data locally while the UE performs random access and RRC reconfiguration towards the target. Only when the source receives an indication — typically via the Xn-U data forwarding control signalling or an explicit notification from the target — that the UE has successfully accessed the target cell does the source start forwarding the buffered packets over the forwarding tunnels.

This timing difference has several architectural benefits. Because forwarding only begins after successful access, the source avoids forwarding data for handovers that ultimately fail or are cancelled (e.g., the UE returns to the source cell or re-selects another cell). This reduces unnecessary load on the Xn transport and on the target node's buffers. It also allows the source to keep delivering data to the UE over the source radio link for as long as possible, which is particularly valuable for latency-sensitive and high-throughput traffic, since the UE can continue receiving data until the very moment it switches to the target.

LDF is closely related to the broader set of Rel-16 mobility enhancements such as DAPS (Dual Active Protocol Stack) handover and conditional handover, all of which aim to minimize interruption time and data loss. While DAPS keeps both source and target radio links active simultaneously, LDF is a lighter-weight optimization focused purely on the timing of the forwarding over Xn. It can be combined with other mechanisms depending on node capabilities and operator configuration. The source and target negotiate support for LDF during handover preparation, so it is a capability-dependent feature.

From an operational standpoint, LDF requires the source node to maintain sufficient buffering and to be able to react quickly to the access-success indication, and it requires the target to be prepared to receive forwarded data slightly later than in early forwarding. The feature is transparent to the UE and to the core network; it is purely an NG-RAN internal optimization. It has been carried forward unchanged through Rel-17, Rel-18 and Rel-19, reflecting its stability and its continued relevance in 5G-Advanced mobility scenarios.

Purpose & Motivation

Late Data Forwarding exists to solve the inefficiency of early data forwarding during handover. In early forwarding, the source NG-RAN node starts pushing buffered user-plane data to the target as soon as handover preparation completes, before knowing whether the UE will actually reach the target. If the handover fails, is cancelled, or the UE returns to the source, the forwarded data is wasted, consuming Xn transport resources and target buffer memory for nothing. In dense deployments with frequent handovers and high traffic volumes, this waste can be significant.

By deferring forwarding until the UE has successfully accessed the target, LDF eliminates forwarding for unsuccessful handovers and allows the source to keep serving the UE over the radio link for longer. This improves spectral efficiency at the cell edge, reduces transport load, and lowers the risk of packet loss and unnecessary duplication. It was introduced in Rel-16 as part of the broader 5G mobility enhancement workstream (alongside DAPS and conditional handover) that targeted reduced handover interruption and improved reliability for NR.

The feature is deliberately simple and UE-transparent, making it attractive for operators who want mobility robustness gains without the complexity of dual connectivity during handover. Its unchanged retention across Rel-17 through Rel-19 demonstrates that the mechanism has proven adequate for evolving 5G-Advanced networks.

What changed in its specifications

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

TS 36.300Rel-18 → Rel-19

Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.

Full comparison in TS 36.300 →
TS 38.300Rel-18 → Rel-19

Rel-19 adds multi-hop L2 UE-to-Network relay for NR sidelink as the largest item. It also adds low-power wake-up signal and receiver (LP-WUS/WUR) text, on-demand SSB and SIB1 for network energy savings, and sub-band full duplex for TDD carriers.

Full comparison in TS 38.300 →

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.

Rel-16 Initial

Introduced the concept of late data forwarding in NG-RAN handover: data forwarding is initiated after the source NG-RAN node knows that the UE has successfully accessed the target NG-RAN node, as specified in TS 38.300 and TS 36.300.

Definition carried over unchanged; the mechanism remains as specified in Rel-16.

Definition carried over unchanged; late data forwarding continues to apply within 5G-Advanced mobility procedures.

Definition carried over unchanged.

Defining Specifications

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

SpecificationTitleRelease
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read