Description
The Secondary eNB (SeNB) is a fundamental architectural entity introduced in 3GPP Release 12 as part of the Dual Connectivity (DC) feature for LTE. In a dual connectivity configuration, a UE maintains simultaneous connections to two distinct eNBs: the Master eNB (MeNB) and the Secondary eNB (SeNB). The MeNB is responsible for anchoring the control plane (RRC) and typically handles the primary cell group (MCG), while the SeNB provides additional user-plane radio resources through a secondary cell group (SCG). This split allows the network to aggregate radio resources from two geographically separated or differently configured nodes, thereby increasing per-user throughput and improving mobility robustness at cell edges.
Architecturally, the SeNB connects to the core network (EPC) through the S1-U interface for user-plane traffic, while the S1-MME control interface remains anchored at the MeNB. The two eNBs communicate over the X2 interface, which carries the X2-C (control) and X2-U (user) planes. The X2-C is used for inter-node coordination procedures such as SeNB Addition, SeNB Modification, SeNB Release, and Secondary Node Change, as specified in 3GPP TS 36.423. The X2-U carries forwarded user-plane packets, particularly for split bearers where the MeNB routes a portion of the PDCP PDUs to the SeNB for transmission. TS 36.425 defines the X2 user-plane protocol for data forwarding in dual connectivity.
There are several bearer architecture options for dual connectivity. In the MCG bearer, all radio resources reside in the MeNB. In the SCG bearer, the bearer is served entirely by the SeNB, with the S1-U path terminating at the SeNB. In the split bearer, the bearer is anchored at the MeNB's PDCP entity, and PDCP PDUs are routed over X2-U to the SeNB's RLC entity for transmission on the SCG. These options allow operators to balance load, optimize backhaul usage, and tailor the configuration to deployment constraints.
The SeNB also plays a role in mobility. When a UE moves, the network may perform an SeNB Change, where the SCG is moved from one SeNB to another while the MeNB remains unchanged, minimizing interruption. The SeNB is configured with its own set of secondary cells (SCells) that form the SCG, and the UE monitors PDCCH on these cells according to the configured scheduling. Radio resource management requirements for dual connectivity, including measurement and mobility procedures involving the SeNB, are captured in TS 36.133.
The SeNB concept was later generalized in 5G NR as the Secondary gNB (SgNB) within Multi-RAT Dual Connectivity (MR-DC), where the same architectural principles—control-plane anchoring at the master node and user-plane aggregation at the secondary node—were extended to NR and inter-RAT scenarios. The SeNB thus represents an important evolutionary step toward the flexible, multi-node radio access architectures that underpin modern 5G deployments.
Purpose & Motivation
The Secondary eNB was created to address a fundamental limitation of single-node LTE deployments: a UE could only be served by one eNB at a time, meaning that user throughput was bounded by the radio resources of a single cell and mobility at cell edges was fragile. With the explosion of mobile data demand in the early 2010s, operators needed a way to aggregate radio resources from multiple nodes without requiring a full core-network redesign or a new radio access technology.
Dual connectivity with an SeNB solves this by allowing the UE to simultaneously utilize radio resources from two eNBs. This is particularly valuable in heterogeneous network deployments where macro cells provide coverage and small cells provide capacity. Rather than forcing all traffic through the macro eNB, the SeNB can offload user-plane data, improving spectral efficiency and user experience. It also improves mobility robustness because the MeNB can maintain the control-plane connection while the SCG is added, modified, or released, reducing the risk of radio link failure during handover.
The SeNB concept also motivated the development of flexible bearer split architectures (MCG, SCG, and split bearers) that allow operators to optimize backhaul usage and core-network anchoring. These architectural patterns directly influenced the design of 5G MR-DC, where the Secondary gNB plays an analogous role. Thus, the SeNB was a foundational step toward the multi-connectivity paradigm that is now central to 5G and beyond.
What changed in its specifications
The latest release-to-release comparison of specifications that define Secondary eNB. Each summary describes the whole specification, not only this term.
Rel-19 adds enhanced NR NTN and IoT NTN requirements and test methods to TS 36.133. It also removes many clauses, mainly SCell delay, RSRP accuracy, NB-IoT and LTE-M measurement and test sections, plus multi-layer gap monitoring and CGI identification clauses.
Full comparison in TS 36.133 →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 →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.
Dual connectivity was introduced with the SeNB as the node providing additional radio resources. The initial architecture defined MCG, SCG, and split bearer options, X2-C/X2-U signaling for SeNB Addition/Modification/Release, and SCG configuration procedures.
Defining Specifications
3GPP specifications that define or reference Secondary eNB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 28.802 vf00 | Management Study for 5G Network Architecture | Rel-15 read |
| TS 36.133 vj60 | LTE Radio Resource Management Requirements | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.423 vj10 | X2 Application Protocol (X2AP) Specification | Rel-19 read |
| TS 36.425 vj00 | X2 User Plane Protocol for Dual Connectivity | Rel-19 read |
| TS 36.842 vc00 | Small Cell Enhancements for LTE Higher Layers | Rel-12 read |
| TS 36.875 vd10 | Dual Connectivity Extension Requirements | Rel-13 read |