Description
The Intermediate U2N Relay UE is a new node type introduced in Rel-19 for multi-hop Layer-2 (L2) UE-to-Network (U2N) relay communication. In a single-hop U2N relay deployment, a U2N Relay UE connects to the network over the Uu interface and provides a PC5 sidelink connection to a U2N Remote UE, which has no direct network connection. The intermediate relay extends this by chaining relays: it has a PC5 connection to a parent UE (which may itself be a relay or the network-connected relay) and a PC5 connection to a child UE or a U2N Remote UE. In this way, traffic from a remote UE can traverse multiple relay hops before reaching the network.
Architecturally, the intermediate relay operates at Layer 2, meaning it forwards packets at the adaptation layer rather than terminating the full protocol stack for the remote UE. The remote UE's traffic is carried over PC5 to the intermediate relay, which forwards it over another PC5 link to its parent, and so on until a relay with a Uu connection delivers it to the gNB. The 3GPP specifications 38.300, 38.304, 38.331, 38.351, 38.401, 38.470, and 38.473 define the overall architecture, idle-mode and cell selection aspects, RRC procedures, sidelink relay procedures, NG-RAN architecture, and the F1AP/E1AP-related signalling needed to support this multi-hop topology.
A key procedural detail in Rel-19 is that an intermediate U2N Relay UE must first establish a connection to the network as a U2N Remote UE before it begins relaying traffic for connected U2N Remote UEs. In other words, the intermediate relay bootstraps itself into the network through the same relay mechanism it will later use to serve others. This ensures that the intermediate relay has a valid network path and context before it accepts child UEs, avoiding orphaned or unauthenticated relay chains. Once connected, it can accept child UEs and forward their traffic.
Key components include the PC5 interface (sidelink) with its PC5-S and PC5-RRC signalling, the L2 adaptation layer that carries the remote UE's PDUs across hops, the relay discovery and selection procedures, and the RRC and NAS signalling that establish and maintain the relay path. The intermediate relay must manage its own mobility and radio link monitoring while also forwarding traffic for child UEs, and it must handle the case where its parent link changes (for example, due to handover or relay reselection).
The intermediate relay matters because it extends coverage beyond what a single relay hop can reach. In scenarios such as disaster recovery, industrial campuses, or remote areas, a chain of relays can connect UEs that are far from any gNB. It also improves robustness by allowing relay paths to be extended incrementally. The Rel-19 introduction of multi-hop L2 U2N relay, with the intermediate relay as the central new node, represents a significant step beyond the single-hop relay model of earlier releases.
Purpose & Motivation
The Intermediate U2N Relay UE exists to extend the reach of UE-to-Network relay communication beyond a single hop. In earlier releases, U2N relay was limited to one relay UE between the remote UE and the network. This constrained coverage to roughly twice the radio range (remote-to-relay plus relay-to-gNB) and made it impossible to serve UEs that were beyond the range of any single relay with a good network connection. Multi-hop relay addresses this by allowing relay chains, with the intermediate relay as the node that bridges two PC5 links.
The motivation is both coverage and resilience. In public safety, disaster recovery, and remote industrial deployments, network infrastructure may be sparse or damaged, and UEs may be scattered over a wide area. A chain of relays can connect them back to the nearest surviving gNB. Multi-hop relay also allows incremental extension: as more relay-capable UEs become available, the chain can grow without requiring new infrastructure.
The Rel-19 design choice that an intermediate relay must first connect to the network as a U2N Remote UE reflects a security and correctness concern. It ensures that every relay in the chain has an authenticated path to the network and a valid context before it forwards traffic for others, preventing rogue or misconfigured relays from injecting traffic into the network. This bootstrap procedure is a defining characteristic of the Rel-19 intermediate relay.
What changed in its specifications
The latest release-to-release comparison of specifications that define Intermediate U2N Relay UE. 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 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 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial introduction of the Intermediate U2N Relay UE for multi-hop L2 U2N relay communication, including the requirement that it first establish a network connection as a U2N Remote UE before relaying traffic for connected remote UEs.
Defining Specifications
3GPP specifications that define or reference Intermediate U2N Relay UE, 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.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.351 vj10 | Sidelink Relay Adaptation Protocol (SRAP) | Rel-19 read |
| TS 38.401 vj30 | NG-RAN Architecture Description | 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 |