Description
The Uu Relay RLC channel is a concept introduced in 3GPP Release 17 for Layer 2 (L2) UE-to-Network (U2N) relaying in 5G NR. It refers to the Radio Link Control (RLC) channel established between a relay UE and the gNB over the Uu air interface. This channel is used to carry packets that are relayed from a remote UE via the relay UE to the network, or vice versa. In the L2 relay architecture, the relay UE acts as a forwarding node at the RLC sublayer, meaning it does not terminate the PDCP or RRC protocols for the remote UE; instead, it forwards RLC PDUs between the PC5 link (remote UE to relay UE) and the Uu link (relay UE to gNB).
The Uu Relay RLC channel is configured by the gNB using RRC signaling (TS 38.331) and is managed by the relay UE's RRC entity. Each Uu Relay RLC channel is associated with a specific PC5 Relay RLC channel on the PC5 interface, creating an end-to-end RLC path for a remote UE's bearer. The mapping between PC5 and Uu RLC channels is controlled by the gNB and communicated to the relay UE. This channel supports the transport of user plane data and possibly control plane messages for the remote UE, depending on the relay configuration.
In Release 17, the definition specified the channel as between an L2 U2N Relay UE and gNB, used for L2 UE-to-Network Relay. In Release 18, the definition was updated to include Multi-Path (MP) Relay UE and to cover the indirect path in case of MP. This reflects the evolution of the relay architecture to support multi-path connectivity, where a remote UE can simultaneously communicate with the network via a direct path and an indirect path through a relay UE. The Uu Relay RLC channel thus becomes part of the indirect path for MP relay, enabling traffic steering and redundancy.
The channel operates at the RLC layer, which provides reliable data transfer using ARQ (Automatic Repeat Request) and segmentation/reassembly. The relay UE maintains separate RLC entities for each Uu Relay RLC channel, each with its own logical channel identity and configuration (e.g., RLC mode: AM, UM, or TM). The gNB schedules resources for these channels and manages QoS flows mapped to them. The Uu Relay RLC channel is transparent to the remote UE's PDCP and above, as the relay UE forwards RLC SDUs/PDUs without interpreting higher-layer protocols.
Key specifications for this term include TS 38.300 (NR overall description), TS 38.331 (RRC protocol), TS 38.470 (NG-RAN F1 general aspects), and TS 38.473 (F1AP). These specify the signaling and procedures for configuring and managing relay channels. The Uu Relay RLC channel is essential for enabling network coverage extension and capacity enhancement through UE relaying, particularly in scenarios like public safety, wearable devices, and indoor coverage.
Purpose & Motivation
The Uu Relay RLC channel exists to support Layer 2 UE-to-Network relaying in 5G NR, allowing a relay UE to forward traffic between a remote UE and the gNB at the RLC layer. This architecture extends network coverage and improves capacity without requiring additional infrastructure, which is particularly valuable in scenarios where deploying new gNBs is impractical or cost-prohibitive. By terminating the relay function at RLC, the relay UE remains transparent to the remote UE's higher-layer protocols, simplifying mobility and security management.
Prior to Release 17, UE relaying in 3GPP was primarily based on Layer 3 (IP-layer) relaying, where the relay UE acted as a router and terminated the IP layer. This approach had limitations in terms of QoS enforcement, bearer mapping, and integration with the 5G core network. The L2 relay architecture with the Uu Relay RLC channel addresses these by allowing the gNB to control the relay at the RLC sublayer, enabling more efficient resource allocation, better QoS handling, and seamless integration with the NR protocol stack.
The introduction of Multi-Path relay in Release 18 further motivated the enhancement of the Uu Relay RLC channel definition to cover MP Relay UEs and indirect paths. This allows a remote UE to maintain simultaneous connectivity via direct and indirect paths, improving reliability and throughput through path diversity. The Uu Relay RLC channel thus plays a central role in the evolution of 5G relay technology, supporting use cases such as enhanced mobile broadband, industrial IoT, and public safety.
What changed in its specifications
The latest release-to-release comparison of specifications that define Uu Relay RLC channel. Each summary describes the whole specification, not only this term.
Rel-19 adds multi-hop L2 UE-to-Network relay for NR sidelink as the largest item. It also adds low-power wake-up signal and receiver (LP-WUS/WUR) text, on-demand SSB and SIB1 for network energy savings, and sub-band full duplex for TDD carriers.
Full comparison in TS 38.300 →Rel-19 adds LTM cell-switch and MIMO Phase 5 identifiers to TS 38.331, plus multi-hop sidelink U2N relay clauses and IEs. It also adds OD-SIB1 and adaptive SSB for RRM, SIB27 for NTN, and SBFD identifiers.
Full comparison in TS 38.331 →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.
Studied in Rel-17, normative work from Rel-18.
Defining Specifications
3GPP specifications that define or reference Uu Relay RLC channel, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.331 vj40 | NR Radio Resource Control (RRC) | Rel-19 read |
| TS 38.470 vj20 | F1 Interface Specification for NG-RAN | Rel-19 read |
| TS 38.473 vj40 | F1 Application Protocol (F1AP) | Rel-19 read |