DAPS

Dual Active Protocol Stacks

Mobility →
Introduced in Rel-16 Also in: Core Network, Management

DAPS is a 5G handover enhancement that maintains two simultaneous protocol stacks to enable zero-interruption data transfer, eliminating packet loss for services like URLLC.

Category
Mobility
Introduced
Rel-16
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
28 specs
DAPS Description Purpose Related Detected Changes Specifications

Description

Dual Active Protocol Stacks (DAPS) is a sophisticated handover mechanism introduced in 5G to achieve make-before-break connectivity. Unlike traditional handovers where the User Equipment (UE) releases the connection to the source cell before establishing one with the target cell (break-before-make), DAPS allows the UE to maintain two fully active and independent protocol stacks simultaneously. This includes duplicate Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC) entities for the source and target cells. The core network establishes a split bearer where downlink data can be duplicated and sent to both the source and target gNBs. The UE receives this data from both cells, using mechanisms like PDCP duplication to ensure at least one copy is successfully delivered, thereby eliminating packet loss during the handover execution phase.

Architecturally, DAPS involves coordination between the source gNB, target gNB, and the core network's User Plane Function (UPF). The source gNB initiates the handover preparation by signaling the target gNB and the core network to establish a temporary dual connectivity-like path. The UPF is instructed to duplicate downlink packets and forward them to both gNBs. On the UE side, the protocol stack for the target cell is established and activated while the stack for the source cell remains fully operational. The UE continues to transmit uplink data exclusively to the source cell until a specific switch command is received, ensuring uplink continuity and order. This dual-reception window persists until the handover is finalized, at which point the source protocol stack is released.

The key operational principle is the decoupling of data reception from the handover execution command. The UE can receive downlink data from the target cell even before it has sent a handover confirmation message (e.g., RRCReconfigurationComplete) to that cell. This is a fundamental shift from legacy procedures. For uplink, the UE transmits data and control messages to the source cell until it receives an explicit 'UL Switch' indication within the RRC reconfiguration message, after which it switches uplink transmission to the target cell. This controlled switchover ensures no uplink packets are lost. DAPS handover is managed via enhanced RRC signaling (e.g., in NR) and Xn-AP procedures between gNBs, with support in the NG interface for core network coordination.

DAPS plays a pivotal role in the 5G radio access network by providing a foundation for ultra-reliable mobility. Its primary role is to guarantee service continuity for demanding applications like industrial automation, autonomous vehicles, and real-time remote control, where even milliseconds of interruption or a single lost packet can be catastrophic. By making the handover procedure virtually invisible to the application layer, DAPS is a key enabler for the 5G vision of supporting mission-critical communications and fulfilling the stringent requirements of URLLC service categories.

Purpose & Motivation

DAPS was created to solve the fundamental problem of data interruption and packet loss during handovers in cellular networks. Traditional LTE and early 5G handovers follow a break-before-make principle, where the radio link with the source cell is broken before a new link with the target cell is fully secured. This results in a handover interruption time, typically ranging from tens to hundreds of milliseconds, during which no data can be transmitted or received. This interruption, along with potential packet loss due to forwarding delays or failures, is unacceptable for emerging 5G use cases such as factory automation, tele-surgery, and vehicle-to-everything (V2X) communication, which demand 99.9999% reliability and sub-10ms latency.

The historical context stems from the limitations of existing enhancements like Packet Data Convergence Protocol (PDCP) status reporting and data forwarding between base stations, which mitigate but do not eliminate packet loss and latency spikes. Techniques like conditional handover improve reliability but do not address the core interruption time issue. DAPS was motivated by the need for a radical architectural change in the handover procedure to support Ultra-Reliable Low-Latency Communication (URLLC), a cornerstone of 5G Phase 2 (Release 16 and beyond). It directly addresses the limitation of having only one active radio link protocol stack at a time during mobility events.

By enabling a make-before-break paradigm, DAPS solves these problems by allowing the UE to prepare and activate the connection to the target cell while maintaining the active connection to the source cell. This ensures that data flow is never halted. The purpose is thus to provide true zero-millisecond interruption handovers, eliminate packet loss, and drastically reduce the latency impact of mobility, thereby unlocking the full potential of 5G for industrial and mission-critical IoT applications.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 63 changes

In Release 16, the DAPS (Dual Active Protocol Stacks) function was newly introduced to enable an S1-based handover procedure where data transmission can continue from the source base station for specific DRBs without interruption while the UE connects to the target. The procedure is initiated by the source eNodeB providing DAPS Information in the transparent container and requires explicit support from both the source and target MME and eNodeB, with the target responding with DAPS Response Information. This introduction included clarifications on various operational aspects, such as restrictions on using DAPS with Carrier Aggregation or Dual Connectivity and corrections for UE capabilities and RLF handling.

  • Alignment CR for DAPS HO TS 23.401CR3602
  • Introduction of DAPS handover TS 36.323CR0279
  • Introduction of DAPS handover TS 38.323CR0042
  • DAPS Handover information TS 29.518CR0376
  • DAPS handover corrections TS 36.300CR1302
  • Clarification on no support of CA or DC with DAPS TS 36.300CR1320

+ 57 more changes

Rel-17 12 changes

In Release 17, the enhancements for Dual Active Protocol Stacks (DAPS) included the introduction of performance measurements and Mobility Robustness Optimization (MRO) for DAPS handover, alongside specific corrections and clarifications to its procedures. The release added details for data transmission and volume calculation during handover, and provided technical clarifications for aspects like header compression for DAPS bearers. Furthermore, it specified support for DAPS over the F1 interface and addressed DAPS state transfer in scenarios involving a split gNB deployment.

  • NRM for DAPS handover TS 28.541CR0610
  • NRM for DAPS Stage 3 TS 28.541CR0611
  • DAPS handover Performance Measurements TS 28.552CR0336
  • MRO additions for CHO and DAPS handover TS 28.313CR0047
  • Correction performance measurements for CHO and DAPS MRO TS 28.313CR0061
  • Add one more trigger point to the number of failed DAPS handover preparations performance measurement TS 28.552CR0343

+ 6 more changes

Explore further

Broader topics and technologies where DAPS plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.401 vj50 Evolved Packet System (EPS) Stage 2 Description Rel-19
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 28.104 vj30 Management Data Analytics (MDA) Rel-19
TS 28.313 vk00 Management and orchestration; SON for 5G networks Rel-20
TS 28.541 vk00 5G Network Resource Model (NRM) Stage 2/3 Rel-20
TS 28.552 vk10 5G Performance Management Measurements Rel-20
TS 29.518 vj50 AMF Service Based Interface Protocol Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.321 vj00 E-UTRA MAC Protocol Specification Rel-19
TS 36.323 vj00 PDCP Protocol Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 36.413 vj10 S1 Application Protocol (S1AP) Rel-19
TS 36.423 vj10 X2 Application Protocol (X2AP) Specification Rel-19
TS 37.320 vj00 Minimization of Drive Tests (MDT) Overview Rel-19
TS 37.340 vj00 Multi-Connectivity Operation Overview Rel-19
TS 37.483 vj10 E1 Application Protocol (E1AP) Rel-19
TS 38.213 vj10 NR Physical Layer Control Procedures Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.306 vj00 NR UE Radio Access Capability Parameters Rel-19
TS 38.321 vj00 NR MAC Protocol Specification Rel-19
TS 38.323 vj00 Packet Data Convergence Protocol (PDCP) Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19
TS 38.413 vj10 NG Application Protocol (NGAP) Rel-19
TS 38.423 vj10 Xn Application Protocol (XnAP) specification Rel-19
TS 38.463 vj00 E1 Application Protocol (E1AP) Rel-19
TS 38.473 vj10 5G F1 Application Protocol (F1AP) Rel-19
TS 38.522 vj11 UE Conformance Test Applicability Statement Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.