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.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (186 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, DAPS (Dual Active Protocol Stacks) was newly introduced to enable a handover procedure without data interruption. This function allows the UE to maintain two active protocol stacks simultaneously, one for the source and one for the target cell, facilitating seamless user data forwarding. It involves specific enhancements to the user plane protocol stacks and their associated tunneling, particularly leveraging the GTP-U protocol across interfaces like S1-U.
- Fixes for CP protocol stack TS 23.501CR0083
- 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI TS 23.501CR0087
- Correction on Control Plane protocol stacks TS 23.501CR0240
- Corrections to N4 and UP tunnel protocol descriptions TS 23.501CR0584
- Clarification on GTP-u protocol TS 23.501CR1012
- RRC corrections for URLLC TS 36.331CR3751
+ 8 more changes
In Release 16, the DAPS (Dual Active Protocol Stacks) handover was introduced as a new function. This feature enables a UE to maintain dual protocol stack connections to both source and target cells during a handover procedure, which is designed to support enhanced reliability and reduced interruption for services like URLLC. The technical implementation involves the S1-U reference point based on the GTP-U protocol for user plane tunnelling during this active handover state.
- Alignment CR for DAPS HO TS 23.401CR3602
- New clause for URLLC supporting TS 23.501CR0810
- Protocol stack for W-5GAN support TS 23.501CR0961
- Corrections to MICO mode with Active Time TS 23.501CR1250
- Introduction of QoS Monitoring to assist URLLC Service TS 23.501CR0990
- Add Number of Active UEs measurements TS 28.552CR0187
+ 94 more changes
In Release 17, the DAPS (Dual Active Protocol Stacks) function was enhanced with new performance measurements and mobility robustness optimization (MRO) additions specific to DAPS handover. The release also introduced new NRM (Network Resource Model) capabilities for DAPS handover and Stage 3 specifications. Furthermore, corrections were made to the performance measurements for DAPS MRO and a trigger point was added to the measurement for failed DAPS handover preparations.
- Adding the usage of Redundant Transmission Experience analytics for URLLC service TS 23.501CR2581
- NRM for DAPS handover TS 28.541CR0610
- NRM for DAPS Stage 3 TS 28.541CR0611
- Add PLMN granularity for number of active UEs measurements TS 28.552CR0284
- DAPS handover Performance Measurements TS 28.552CR0336
- Introduction of IIoT/URLLC enhancements in NR TS 38.213CR0272
+ 35 more changes
In Release 18, enhancements for Dual Active Protocol Stacks (DAPS) were introduced as part of broader Timing Resiliency and Ultra-Reliable Low Latency Communication (URLLC) improvements. The release included specific protocol corrections and clarifications, such as updates to the XnAP protocol for these features. Furthermore, it involved corrections and testing updates related to UE capabilities for URLLC, ensuring the function's reliability during procedures like handover.
- Rel-18 CR TS 28.552 Add missing Mean and Max number of Active UEs per cell TS 28.552CR0546
- Protocol support for MBS Session in MOCN TS 29.518CR0836
- Introduction of Timing Resiliency and URLLC enhancements TS 38.300CR0730
- Introduction of URLLC and Timing Resiliency TS 38.331CR4258
- Introduction of 5G Timing Resiliency and URLLC enhancements TS 38.401CR0309
- Introduction of 5G Timing Resiliency and URLLC enhancements TS 38.413CR0972
+ 15 more changes
In Release 19, the DAPS function was enhanced with clarifications and corrections for protocol-specific parameters and procedures related to N6 interface delay measurements. The release also introduced the capability to convey slice information for an active PDU session during an inter-PLMN handover. Furthermore, updates were made to the general protocol description and the control plane and user plane protocol stacks involving the MWAB node.
- Control Plane and User Plane Protocol stacks involving the MWAB node TS 23.501CR5561
- General description of relaying media related information over N6 using an encapsulation protocol TS 23.501CR5711
- Rel-19 CR TS28.552 Enhance Number of Active UEs related measurements for RedCap UEs TS 28.552CR0686
- Rel-19 CR TS 28.552 Update number of active UEs related measurements TS 28.552CR0706
- Introduction of NR Femto Architecture and Protocol Aspects TS 38.300CR1035
- Clarifications on other protocols used for N6 delay measurements TS 23.501CR6331
+ 4 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.
| Specification | Title | Release |
|---|---|---|
| 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 |