Description
A split bearer is a fundamental concept in 3GPP dual connectivity (DC) architectures, introduced in Release 12 for LTE. In a dual connectivity configuration, a user equipment (UE) maintains simultaneous connections to two radio access nodes: a Master eNodeB (MeNB) and a Secondary eNodeB (SeNB). The split bearer allows a single Evolved Packet System (EPS) bearer to have its radio protocol layers distributed across both nodes, thereby aggregating the radio resources of both base stations to serve the UE. This is in contrast to a Master Cell Group (MCG) bearer, whose radio protocols reside solely in the MeNB, and a Secondary Cell Group (SCG) bearer, whose protocols reside solely in the SeNB.
The architecture of a split bearer is defined in 3GPP TS 36.300 for LTE and TS 37.340 for multi-connectivity. The Packet Data Convergence Protocol (PDCP) entity for the split bearer is located in the MeNB, while the Radio Link Control (RLC) and Medium Access Control (MAC) entities are located in both the MeNB and the SeNB. The PDCP layer is responsible for header compression, ciphering, and integrity protection, and it also handles the splitting of PDCP Protocol Data Units (PDUs) between the two RLC entities. This split is performed based on factors such as the available radio resources, backhaul capacity, and quality of service requirements. The PDCP PDUs are then transmitted over the respective RLC/MAC layers of the MeNB and SeNB, and are reassembled at the UE's PDCP layer.
The split bearer operation relies on the X2 interface between the MeNB and SeNB for the forwarding of user plane data. The MeNB receives the EPS bearer data from the Serving Gateway (S-GW) and forwards a portion of the PDCP PDUs to the SeNB via the X2-U interface. The SeNB then transmits these PDUs to the UE using its own radio resources. The UE's PDCP layer must support reordering of PDCP PDUs received from both nodes, as the two paths may have different latencies. This reordering function ensures in-sequence delivery to upper layers. The split bearer thus enables throughput aggregation and load balancing across the two nodes, improving user experience and network efficiency.
In 5G New Radio (NR) and Multi-RAT Dual Connectivity (MR-DC), the split bearer concept has been extended and refined. For example, in EN-DC (E-UTRA-NR Dual Connectivity), a split bearer can be configured with the PDCP entity in the Master Node (MN) and the RLC entities in both the MN and the Secondary Node (SN). The split bearer is also applicable in NR-NR dual connectivity (NR-DC) and in multi-connectivity scenarios. The 3GPP specifications TS 37.340 and TS 38.323 define the PDCP and bearer architecture for these scenarios. The split bearer remains a key enabler for achieving high data rates and robust mobility in dual connectivity deployments.
The split bearer is closely related to other dual connectivity concepts such as the split SRB (Signalling Radio Bearer) for control plane, and the overall dual connectivity framework. It is a critical feature for operators seeking to leverage heterogeneous network deployments, where macro and small cells are combined to provide enhanced capacity and coverage. The split bearer's ability to dynamically distribute traffic across multiple nodes makes it a cornerstone of 3GPP's multi-connectivity strategy.
Purpose & Motivation
The split bearer was created to address the need for higher user throughput and improved resource utilization in heterogeneous networks. Prior to dual connectivity, a UE could only connect to a single base station, limiting the achievable data rates to the resources of that cell. With the proliferation of small cells and the need to aggregate spectrum across different nodes, 3GPP introduced dual connectivity in Release 12. The split bearer solves the problem of how to utilize the radio resources of both the MeNB and SeNB for a single bearer, thereby increasing peak data rates and providing load balancing. It also enables seamless mobility and robust connectivity by allowing the UE to maintain connections to two nodes simultaneously.
The split bearer addresses the limitations of carrier aggregation (CA), which requires tight synchronization and coordination between cells, typically within the same base station. Dual connectivity, and specifically the split bearer, allows aggregation across non-co-located nodes with potentially non-ideal backhaul, making it more flexible for deployment scenarios involving macro and small cells. This is particularly important for operators who cannot deploy fiber to all sites and need to leverage existing backhaul. The split bearer also provides a mechanism for offloading traffic from the macro cell to small cells, improving overall network capacity and user experience.
Over time, the split bearer concept has evolved to support 5G NR and multi-RAT dual connectivity, ensuring that the benefits of resource aggregation are available in the 5G era. The fundamental motivation remains: to provide higher data rates, better coverage, and efficient load balancing by utilizing multiple radio access nodes simultaneously.
What changed in its specifications
The latest release-to-release comparison of specifications that define Split bearer. Each summary describes the whole specification, not only this term.
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 →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 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference Split bearer, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.323 vj00 | PDCP Protocol Specification | Rel-19 read |
| TS 36.425 vj00 | X2 User Plane Protocol for Dual Connectivity | Rel-19 read |
| TS 36.875 vd10 | Dual Connectivity Extension Requirements | Rel-13 read |
| TS 37.340 vj30 | Overview of Multi-Connectivity Operation using E-UTRA and NR | Rel-19 read |
| TS 38.323 vj10 | PDCP Protocol Specification | Rel-19 read |