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

Glossary term · Radio Access Network

SCG bearer

Secondary Cell Group Bearer

Radio Access Network →

SCG bearer is a radio bearer in MR-DC whose RLC bearer(s) reside only in the Secondary Cell Group, allowing the secondary node to carry user-plane traffic independently, improving throughput and offloading the master node.

Introduced
Rel-12
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
3 specs
SCG bearer Description Purpose What changed Neighbours Specifications

Description

An SCG bearer is a radio bearer type defined for multi-connectivity operation in 3GPP networks. In a dual connectivity or multi-radio dual connectivity (MR-DC) configuration, the UE is connected to a Master Node (MN) and a Secondary Node (SN) simultaneously. Radio bearers are classified according to where their user-plane and control-plane protocol entities are hosted: MCG bearers, SCG bearers, and split bearers. An SCG bearer is one whose Packet Data Convergence Protocol (PDCP) and Radio Link Control (RLCP) entities are located entirely in the Secondary Cell Group, meaning all of its traffic is carried over the SN's radio resources. The MN retains only the control-plane connection (RRC) toward the UE, while the SN handles the user-plane data path for that bearer.

Architecturally, the SCG bearer is realized through the SN's own PDCP and RLC/MAC layers. In the user plane, the SN terminates the PDCP entity and the associated RLC bearers, and the SN's MAC scheduler allocates physical resources in the SCG cells. In the control plane, the MN's RRC entity configures the bearer via the X2/Xn interface using SN Addition and SN Modification procedures, while the SN provides its radio configuration to the MN in a container that the MN forwards to the UE. The core network user plane (S-GW/UPF) may have a direct bearer to the SN (SCG bearer with a direct S1-U/NG-U path) or the traffic may be routed through the MN and forwarded over X2/Xn, depending on the architecture option and release.

A key characteristic of the SCG bearer is that it uses only SN resources for data transmission. This makes it attractive for offloading traffic from the MN to the SN, particularly when the SN provides additional capacity (e.g., a small cell or a high-capacity NR node). Because the bearer's RLC and MAC are entirely in the SN, the SN scheduler has full control over the radio resources for that bearer, enabling efficient link adaptation and HARQ operation within the SCG. However, the SCG bearer is more sensitive to SN radio link failure than a split bearer, since there is no MN leg to fall back on.

The definition of the SCG bearer has evolved with the introduction of carrier aggregation (CA) packet duplication. In Rel-15, the definition was generalized from "dual connectivity" to "MR-DC" and clarified that the bearer has an RLC bearer only in the SCG. In Rel-16, the definition was further refined to account for CA packet duplication: an SCG bearer may have two RLC bearers in the case of CA packet duplication in an E-UTRAN cell group, or up to four RLC bearers in the case of CA packet duplication in an NR cell group. This reflects the introduction of PDCP duplication over multiple carriers, where the same PDCP PDU is duplicated and transmitted over multiple RLC entities to improve reliability.

SCG bearers are used in EN-DC (E-UTRA-NR Dual Connectivity), NE-DC, NGEN-DC, and NR-DC deployments. They are particularly relevant for high-throughput scenarios where the SN has abundant spectrum, and for services requiring low latency where the SN's scheduler can act independently. The bearer type selection (MCG, SCG, or split) is a network decision based on traffic characteristics, radio conditions, and load balancing policies, and can be reconfigured dynamically via RRC signaling.

Purpose & Motivation

The SCG bearer exists to enable efficient use of secondary node resources in dual connectivity and MR-DC deployments. Before dual connectivity was introduced in Rel-12, a UE could only be served by a single eNB, meaning that traffic had to traverse the master node's radio link even when a secondary node had more favorable radio conditions or spare capacity. The SCG bearer solves this by allowing a bearer's entire user-plane protocol stack to reside in the secondary node, so that the SN's scheduler can directly allocate its radio resources to the UE without traversing the MN's radio interface. This improves throughput, reduces latency on the SN leg, and enables better load balancing between nodes.

The concept was motivated by the need to aggregate radio resources across nodes with different coverage and capacity characteristics—for example, a macro cell providing wide-area coverage and a small cell providing high-capacity hotspots. By hosting a bearer entirely in the small cell, the network can offload traffic from the macro layer and exploit the small cell's spectrum more efficiently. The SCG bearer also supports the architectural flexibility needed for inter-node coordination, where the MN controls RRC while the SN controls the data path for selected bearers.

Over time, the SCG bearer definition was extended to support carrier aggregation packet duplication, reflecting the need for ultra-reliable communication in later releases. The Rel-16 refinement to allow up to four RLC bearers in an NR cell group acknowledges that duplication can be configured across multiple carriers, improving reliability for URLLC and other mission-critical services. This evolution shows how a relatively simple bearer concept was adapted to support increasingly demanding reliability requirements in 5G networks.

What changed in its specifications

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

TS 36.300Rel-18 → Rel-19

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 →
TS 37.340Rel-18 → Rel-19

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

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-12 Initial

Initial definition introduced with dual connectivity: a bearer whose radio protocols are only located in the SeNB to use SeNB resources. This established the concept of hosting the entire user-plane stack in the secondary node for offloading.

Definition carried over unchanged from Rel-12; the dual connectivity SCG bearer concept remained stable.

Definition carried over unchanged from Rel-13; no textual revision to the SCG bearer definition.

Wording changed: the definition was generalized from 'dual connectivity' to 'MR-DC' and clarified that the bearer has an RLC bearer (or two RLC bearers in case of CA packet duplication) only in the SCG. This aligned the term with the broader MR-DC framework introduced for 5G.

Wording changed: the definition was refined to specify that CA packet duplication may involve two RLC bearers in an E-UTRAN cell group or up to four RLC bearers in an NR cell group, reflecting the extension of duplication to multiple carriers.

Definition carried over unchanged from Rel-16; the SCG bearer concept remained stable.

Definition carried over unchanged from Rel-17; no textual revision.

Definition carried over unchanged from Rel-18; no textual revision.

Defining Specifications

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

SpecificationTitleRelease
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