Description
The MCG bearer is a radio bearer type defined in 3GPP TS 36.300, TS 36.875, and TS 37.340 for Multi-RAT Dual Connectivity (MR-DC) and earlier dual connectivity (DC) architectures. In MR-DC, a UE is connected simultaneously to a Master Node (MN) and a Secondary Node (SN), each providing one or more cell groups. The Master Cell Group (MCG) is the set of cells associated with the MN, and the Secondary Cell Group (SCG) is the set associated with the SN. A radio bearer is characterized by how its protocol layers are distributed across these nodes, and the MCG bearer is the simplest case: its RLC bearer or bearers are located only in the MCG.
In the user plane, a radio bearer consists of a PDCP entity and one or more RLC bearers beneath it. For an MCG bearer, the PDCP entity and the RLC bearer(s) are all hosted by the MN. The bearer therefore uses only MN radio resources. This contrasts with the SCG bearer, whose PDCP and RLC entities are hosted by the SN and which uses only SN resources, and with the split bearer, whose PDCP is hosted by one node while RLC bearers exist in both cell groups, allowing traffic to be split across MN and SN. The MCG bearer is thus the natural choice for traffic that should remain anchored at the master node, for example signaling-related data radio bearers or services for which the MN provides the most reliable coverage.
With the introduction of carrier aggregation (CA) packet duplication, the definition of the MCG bearer was refined to account for multiple RLC bearers. In an E-UTRAN cell group, CA packet duplication results in two RLC bearers; in an NR cell group, up to four RLC bearers may be configured for duplication. The MCG bearer definition was updated to explicitly permit these configurations while still requiring all RLC bearers to reside in the MCG. This reflects the evolution from LTE DC (where the definition spoke simply of radio protocols located in the MeNB) to the more general MR-DC framework covering EN-DC, NE-DC, NGEN-DC, and NR-DC.
From a protocol architecture perspective, the MCG bearer is configured by RRC signaling from the MN. The MN's RRC entity decides the bearer type and configures the PDCP and RLC entities accordingly. In EN-DC, for example, the MN is an LTE eNB and the MCG bearer uses LTE PDCP and LTE RLC. The bearer type selection is part of the overall bearer mapping performed by the MN, which considers factors such as traffic characteristics, load, and coverage. Because the MCG bearer does not use SN resources, it does not benefit from the additional throughput that dual connectivity offers, but it offers simplicity and robustness, particularly when SN coverage is spotty.
The MCG bearer is one of the fundamental building blocks for understanding dual connectivity bearer architecture. Together with the SCG bearer and the split bearer, it defines the complete set of options for distributing a UE's radio bearers across master and secondary nodes, and it underpins the design of data forwarding, bearer type change procedures, and mobility handling in MR-DC networks.
Purpose & Motivation
The MCG bearer exists to provide a well-defined bearer option in dual connectivity and MR-DC architectures where a UE's traffic is anchored entirely at the master node. When dual connectivity was introduced in Release 12, operators needed a way to aggregate radio resources from multiple eNBs while retaining a clear model of which node hosts which protocol layers. The MCG bearer solves the case where a bearer should use only master node resources, giving the network a simple, robust option that does not depend on secondary node availability.
Before dual connectivity, each bearer was served by a single eNB, and there was no need to distinguish bearer types by cell group. With DC, the protocol stack could be split in multiple ways, and without standardized bearer type definitions, interoperability between vendors would have been impossible. The MCG bearer, along with SCG and split bearers, provided the standardized vocabulary needed for multi-vendor DC deployments.
The evolution to MR-DC in Release 15 and the introduction of CA packet duplication in later releases required refining the definition to handle multiple RLC bearers. This ensured that the MCG bearer concept remained accurate as duplication mechanisms were added, preserving its role as the reference model for master-node-anchored bearers in 5G and beyond.
What changed in its specifications
The latest release-to-release comparison of specifications that define MCG 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 adds to TS 37.340 data collection for SON/MDT in NR standalone and MR-DC Phase 4. It covers conditional PSCell addition or change (CPAC/S-CPAC) failure detection and root cause analysis in MN and SN nodes.
Full comparison in TS 37.340 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 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 MCG 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.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 |