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

Glossary term · Radio Access Network

PC5 Relay RLC channel

PC5 Relay Radio Link Control Channel

Radio Access Network →

PC5 Relay RLC channel is an RLC channel established over the PC5 sidelink interface between relay and remote UEs to transport packets for Layer-2 UE-to-Network or UE-to-UE relay communication.

Introduced
Rel-17
Where
Radio Access Network › NG-RAN (5G)
Specifications
5 specs
PC5 Relay RLC channel Description Purpose What changed Detected Changes Specifications

Description

The PC5 Relay RLC channel is a radio link control (RLC) layer channel that operates over the PC5 sidelink interface in 3GPP proximity-based services (ProSe) and sidelink relay architectures. It is established between a Layer-2 (L2) UE-to-Network (U2N) Remote UE and an L2 U2N Relay UE, or between L2 U2N Relay UEs in multi-hop configurations, or between an L2 UE-to-UE (U2U) Remote UE and an L2 U2U Relay UE. The channel serves as the transport bearer for packets that need to traverse the PC5 link as part of a relay path, enabling a remote UE to reach a network (via a relay UE) or another UE without a direct cellular connection.

Architecturally, the PC5 Relay RLC channel sits within the sidelink protocol stack. In the L2 relay model, the relay UE forwards packets at the RLC sublayer, meaning that the RLC channel is configured per end-to-end bearer or per hop. The channel is mapped to a sidelink logical channel and then to a sidelink transport channel (SL-SCH) and physical channel (PSSCH). The RLC entity can operate in acknowledged mode (AM), unacknowledged mode (UM), or transparent mode (TM), depending on the required reliability and latency. For L2 U2N relay, the PC5 Relay RLC channel carries the adaptation layer PDUs that include the remote UE's identity, allowing the relay to route packets to the correct remote UE and the network to distinguish traffic from different remote UEs.

The configuration of the PC5 Relay RLC channel is controlled by the network (e.g., gNB) via RRC signaling. The gNB provides the relay UE with the necessary RLC configuration (e.g., logical channel identity, priority, RLC mode, and parameters) through system information or dedicated RRC messages. The remote UE obtains its PC5 RLC configuration either from the network (if in coverage) or via pre-configuration. In multi-hop scenarios (Rel-19), the channel can be established between relay UEs to extend coverage further, requiring a chain of RLC channels. The PC5 Relay RLC channel is distinct from the Uu RLC channel used on the cellular link; it is specifically for sidelink relay traffic.

Key procedures associated with the PC5 Relay RLC channel include establishment, modification, and release. When a remote UE initiates a relay connection, the relay UE sets up the PC5 RLC channel based on the configuration received from the network. The channel is then used to carry user plane data (e.g., IP packets) and control plane signaling (e.g., RRC messages for the remote UE). The relay UE performs RLC-level functions such as segmentation, reassembly, and ARQ retransmissions on this channel. In the L2 U2N relay architecture, the PC5 Relay RLC channel is paired with a Uu RLC channel on the relay UE's network side, and the relay performs routing between them based on the adaptation layer.

The PC5 Relay RLC channel is essential for enabling coverage extension and service continuity for UEs outside network coverage or in challenging radio conditions. It allows a remote UE to access network services through a nearby relay UE, effectively extending the cell's reach. It also supports UE-to-UE relay for direct communication between devices without network involvement. The channel's configuration and management are tightly integrated with the overall sidelink resource allocation and QoS framework, ensuring that relay traffic receives appropriate treatment. As relay technologies evolve, the PC5 Relay RLC channel continues to be a fundamental building block for sidelink relay communication in 5G and beyond.

Purpose & Motivation

The PC5 Relay RLC channel was created to support Layer-2 UE-to-Network and UE-to-UE relay communication over the PC5 sidelink interface. Prior to its introduction, sidelink communication was primarily direct between UEs, and relay functionality was limited to higher-layer (IP) relay or proprietary solutions. The need for a standardized RLC-level channel arose from the desire to efficiently multiplex and route traffic for multiple remote UEs through a single relay UE, while maintaining QoS and enabling network control. This channel provides a reliable, configurable transport for relayed packets, allowing the network to manage resources and ensure service continuity.

The introduction of the PC5 Relay RLC channel in Release 17 addressed the limitations of earlier relay approaches, which either operated at the IP layer (e.g., using NAT) or lacked standardized RLC configuration. By defining an RLC channel specifically for relay, 3GPP enabled a unified architecture where the relay UE can forward packets at Layer 2, reducing latency and overhead. This is particularly important for mission-critical services, public safety, and IoT devices that require extended coverage. The channel also facilitates multi-hop relay (added in Rel-19) by allowing relay UEs to interconnect, further extending coverage.

Overall, the PC5 Relay RLC channel solves the problem of how to transport packets over PC5 in a relay context with network-controlled QoS and resource allocation. It provides a standardized, interoperable mechanism that supports both UE-to-Network and UE-to-UE relay, and it is a key enabler for 5G sidelink relay features.

What changed in its specifications

The latest release-to-release comparison of specifications that define PC5 Relay RLC channel. Each summary describes the whole specification, not only this term.

TS 38.300Rel-18 → Rel-19

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

Rel-19 adds TS 38.304 definitions for multi-hop L2 UE-to-Network sidelink relay roles, including child, parent, intermediate, first and last relay UEs. It also adds paging and system information handling for relays, and NTN IoT Phase 3 text on PLMN access technology restrictions and cell categories.

Full comparison in TS 38.304 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (3 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-19.

Rel-19 3 changes
  • Correction on PC5 Relay RLC channel configuration TS 38.331CR5510
  • Correction on PC5 Relay RLC channel addition TS 38.331CR5787
  • Correction on PC5 Relay RLC channel addition/modification TS 38.331CR5794

Defining Specifications

3GPP specifications that define or reference PC5 Relay RLC channel, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures 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