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

Glossary term · Mobility

DAPS bearer

Dual Active Protocol Stack Bearer

Mobility →

DAPS bearer is a radio bearer whose protocol stacks remain active at both the source and target base stations during a DAPS handover, allowing data to flow through both nodes to minimize interruption.

Introduced
Rel-16
Where
Radio Access Network › NG-RAN (5G)
Specifications
4 specs
DAPS bearer Description Purpose What changed Neighbours Detected Changes Specifications

Description

A DAPS bearer is a radio bearer that, during a Dual Active Protocol Stack (DAPS) handover, maintains its radio protocol entities in both the source and the target base station simultaneously. In a conventional handover, the UE detaches from the source cell, reconfigures its radio link to the target cell, and only then resumes data transfer, producing a service interruption that can range from tens to hundreds of milliseconds. The DAPS bearer removes this interruption by keeping the source link active while the target link is established, so that user-plane data can be transmitted and received through either node during the transition.

The architecture of a DAPS bearer involves parallel protocol stacks. On the network side, the source eNB (or gNB) and the target eNB (or gNB) each host a full set of radio protocol entities — PDCP, RLC, MAC, and PHY — for the bearer. On the UE side, the UE maintains two corresponding stacks: one associated with the source cell and one with the target cell. The PDCP layer plays a central role: the UE's PDCP entity for the DAPS bearer is configured to handle both stacks, maintaining a single sequence-number space and reordering function so that packets delivered through either path are presented to upper layers in order and without duplication. During the handover, the source node continues to schedule uplink and downlink data on the source link while the target node begins scheduling on the target link once the random access procedure succeeds.

The handover procedure with DAPS bearers proceeds in stages. First, the source node decides to hand over the UE and sends a handover request to the target, which includes the DAPS bearer configuration. The target admits the UE and returns a handover request acknowledge containing the RRC configuration for the target cell. The source then sends an RRC reconfiguration message to the UE instructing it to perform a DAPS handover, including the target cell configuration. The UE does not release the source link at this point; instead, it establishes synchronization with the target cell while continuing to use the source link for data. Once the UE successfully accesses the target cell, it sends an RRC reconfiguration complete message to the target. The target then requests a path switch from the core network (MME or AMF), and after the path switch, the source node is informed that it can release the UE context. Throughout this period, the DAPS bearer carries data over both links, and the PDCP layer ensures in-order delivery.

DAPS bearers introduce several technical challenges that the specifications address. Because both links are active, the UE must handle uplink data transmission on two links simultaneously, and the network must manage duplicate packets and reordering. The PDCP layer uses sequence numbers and a reordering window to discard duplicates and deliver packets in order. Security is also affected: the UE must maintain separate security contexts for the source and target links during the transition, and the specifications define how ciphering and integrity protection keys are derived and applied for each stack. In addition, the UE must manage radio link monitoring and measurement for both cells, and the network must coordinate scheduling so that the source link can be released cleanly once the target link is fully operational.

DAPS was introduced in Release 16 for both LTE (TS 36.323, TS 36.331) and NR (TS 38.323, TS 38.331). It targets services that are sensitive to interruption, such as voice over IP, video conferencing, and industrial control applications, where even a short gap in connectivity can degrade quality. The feature is particularly valuable in deployments with overlapping cells and in mobility scenarios where the UE moves between cells of different radio access technologies or between a macro cell and a small cell. By keeping both protocol stacks active, the DAPS bearer provides a practical mechanism for achieving near-zero interruption handover without requiring a fully centralized architecture.

Purpose & Motivation

The DAPS bearer exists to address one of the most persistent quality-of-service problems in mobile networks: the interruption that occurs when a UE hands over from one cell to another. In conventional handover, the UE must break its connection to the source cell before establishing a connection to the target cell, and during this break user-plane data cannot be delivered. For best-effort data services, a short interruption is tolerable, but for real-time services such as voice, video, and industrial applications, it causes audible glitches, frozen frames, or control-loop instability.

Earlier approaches to reducing interruption included make-before-break handover in UTRAN and various dual-connectivity schemes, but these either did not apply to the single-connection handover case or required a more complex multi-connectivity architecture. The DAPS bearer was designed to provide a make-before-break capability within the standard handover framework, allowing the UE to maintain two active protocol stacks during the transition without requiring dual connectivity to be configured permanently.

The feature was introduced in Release 16 as part of the broader effort to improve mobility performance for latency-sensitive services in LTE and NR. It complements other Release 16 mobility enhancements, such as conditional handover and improved measurement reporting, and it supports the growing demand for seamless connectivity in applications such as cloud gaming, augmented reality, and industrial automation. By minimizing the data interruption during handover, the DAPS bearer helps operators meet the stringent reliability and latency requirements of these services.

What changed in its specifications

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

TS 36.323Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 36.323: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 36.323 →
TS 36.331Rel-18 → Rel-19

Rel-19 adds NTN-for-IoT Phase 3 and inter-RAT mobility from E-UTRAN to NR NTN, plus LTE-based 5G Broadcast Phase 2 changes. It also adds IMS disaster-roaming access barring, NTN-for-NR Phase 3 fields, and NR RRM Phase 5 items.

Full comparison in TS 36.331 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 1 change
  • Note to clarify UE handling of non-DAPS bearer TS 36.331CR4604
Rel-17 1 change
  • Clarification on headerCompression for DAPS bearer TS 38.331CR3417

Defining Specifications

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

SpecificationTitleRelease
TS 36.323 vj00 PDCP Protocol Specification Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 38.323 vj10 PDCP Protocol Specification Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read