Description
A Relay Node (RN) is a low-power base station that wirelessly connects to the core network via a donor cell (DeNB in LTE, gNB in 5G NR). It creates a new cell, visible to UEs as a normal serving cell, but its backhaul connection to the network is provided over the radio interface (the Un interface in LTE, NR-Uu in 5G) rather than a traditional wired fiber or microwave link. Architecturally, the RN contains a base station functionality (eNB/gNB part) towards the UE (Uu interface) and a UE-like functionality towards the donor base station.
The operation involves two distinct radio links: the backhaul link (between RN and Donor eNB/gNB) and the access link (between RN and UE). The RN demodulates and decodes the signal from the donor on the backhaul link, then re-encodes and re-modulates it for transmission on the access link (decode-and-forward relaying). This process improves signal quality compared to simple analog amplification. In-band relaying, where backhaul and access links share the same frequency, requires careful time-division multiplexing to avoid self-interference, often utilizing Almost Blank Subframes (ABS) in the donor cell.
Key protocols are extended to support RN functionality. S1 and X2 interfaces are proxied through the donor eNB. The donor eNB acts as an S1 and X2 proxy, meaning the RN appears as a normal eNB to the core network (MME/S-GW) and to other eNBs. For the UE, the RN is indistinguishable from a normal macro cell. Security is maintained via a secure connection between the RN and the donor eNB. Relay Nodes are categorized by their transparency to UEs (transparent vs. non-transparent) and their layer of operation (Layer 1 repeater, Layer 2 RN, Layer 3 RN). 3GPP primarily standardized Layer 3 RNs, which are full eNBs with wireless backhaul.
Purpose & Motivation
The Relay Node was introduced to address coverage and capacity challenges in a cost-effective manner. Deploying traditional macro cells with fiber backhaul is expensive and time-consuming, especially in rural areas, temporary event locations, or within buildings where coverage holes exist. RNs solve this by leveraging the existing macro network's radio resources to create new cells without the need for costly new backhaul infrastructure.
They specifically improve performance at cell edges and in shadowed regions where the signal from the macro cell is weak, leading to low data rates and poor service quality. By placing an RN closer to such UEs, the access link distance is shortened, enabling higher-order modulation and better throughput. Furthermore, RNs can increase overall network capacity by offloading traffic from the macro cell and enabling more efficient spatial reuse of spectrum. The motivation for their standardization in LTE-Advanced (Rel-10) was to meet IMT-Advanced requirements for enhanced coverage and spectral efficiency, providing a flexible deployment tool for network operators.
What changed in its specifications
The latest release-to-release comparison of specifications that define RN. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.
Full comparison in TS 23.401 →Technology family
Base stations and RAN nodes · Radio Access Network
- Phase 1 BSC, BSS, BTS
- R99 Node B, RNC, RNS
- Rel-8 eNB, HeNB, HNB, HNB-GW
- Rel-10 DeNB, HeNB-GW, RN
- Rel-15 en-gNB, gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, ng-eNB
- Rel-16 IAB-donor, IAB-DU, IAB-MT, IAB-node
- Rel-18 Mobile IAB-node
- RN used together with DeNB
“The RN terminates the S1, X2 and Un interfaces. The DeNB provides S1 and X2 proxy functionality between the RN and other network nodes” TS 36.300
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 3 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Relay Node gains identification and OAM addressing in TS 23.003, performance measurements in TS 32.425, and a security architecture annex in TS 33.401, all appearing for the first time in Rel-10.
- “23 Numbering, addressing and identification for the Relay Node OAM System” TS 23.003 v10.10.0
- “5 Measurements related to Relay Node” TS 32.425 v10.7.0
- “Annex D (normative): Security for Relay Node Architectures” TS 33.401 v10.7.0
Rel-11 management specs add Relay Node IOCs (RN functionality and externally controlled RN properties) and a list of candidate DeNB cells for RN attach.
- “This IOC represents Relay Node (RN) functionality. For more information about RN, see 3GPP TS 36.300 [11].” TS 28.658 v11.7.0
- “This IOC represents the properties of a Relay Node (RN) controlled by another IRPAgent.” TS 28.658 v11.7.0
- “A list of ECGIs of the candidates DeNB cells for the subject Relay Node in Attach for RN operation (phase 2)” TS 28.658 v11.7.0
User plane integrity activation now differs by node type: for an RN it is activated with RRC ciphering, while for a normal UE it is activated during the RRC Connection Reconfiguration procedure.
- “For normal UE, user plane integrity shall be activated during the RRC Connection Reconfiguration procedure” TS 33.401 v17.7.0
Defining Specifications
3GPP specifications that define or reference RN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.066 vj00 | Mobile Number Portability Technical Realization | Rel-19 read |
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 23.786 vg10 | Study on V2X architecture enhancements for EPS and 5GS | Rel-16 read |
| TS 28.658 vk00 | E-UTRAN NRM Information Service | Rel-20 read |
| TS 29.204 vj00 | SS7 Security Gateway Functional Description | Rel-19 read |
| TS 32.425 vj00 | E-UTRAN Performance Measurements | Rel-19 read |
| TS 32.762 vb70 | E-UTRAN NRM Information Service | Rel-11 read |
| TS 32.851 vc20 | Network Sharing OAM Requirements | Rel-12 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |
| TS 33.816 va00 | Security Analysis for LTE Relay Nodes | Rel-11 read |
| TS 36.201 vj00 | LTE Physical Layer General Description | Rel-19 read |
| TS 36.216 vj00 | LTE Relay Node Physical Layer | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.314 vj00 | E-UTRA Radio Measurements Specification | Rel-19 read |
| TS 36.321 vj30 | E-UTRA MAC Protocol Specification | Rel-19 read |
| 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 36.806 v900 | LTE-Advanced Relay Node Architectures | Rel-9 read |
| TR 44.901 vj00 | Extended NACC for External Cell Change | Rel-19 read |