Description
The Last U2N Relay UE is a concept introduced in 3GPP Release 19 for Layer 2 (L2) UE-to-Network (U2N) relay communication. In L2 U2N relaying, a remote UE connects to the network through one or more relay UEs. The Last U2N Relay UE is the relay UE that is closest to the remote UE in the relay chain—i.e., the relay UE that has a PC5 connection to the remote UE (or to a child UE that eventually connects to the remote UE) and a Uu connection to the network. In single-hop L2 U2N relay communication, the Last U2N Relay UE is the only relay UE, and its child UE is the remote UE itself.
Architecturally, L2 U2N relaying allows a remote UE to access the network via a relay UE that acts as a Layer 2 forwarder. The relay UE establishes a Uu connection to the gNB and a PC5 connection (sidelink) to the remote UE. The gNB manages the remote UE's context and radio bearers, while the relay UE forwards packets between the Uu and PC5 links. In multi-hop scenarios, multiple relay UEs may be chained, and the Last U2N Relay UE is the one at the edge of the chain adjacent to the remote UE. The term 'child UE' refers to the UE downstream of a relay UE; for the Last U2N Relay UE in single-hop, the child UE is the remote UE.
The Last U2N Relay UE is responsible for forwarding user plane and control plane traffic between the remote UE and the network. It maintains the PC5 link to the child UE and the Uu link to the gNB, and it may perform header compression, routing, and bearer mapping. The gNB is aware of the relay chain and manages the remote UE's radio bearers accordingly. The Last U2N Relay UE may also assist in mobility procedures, such as handover of the remote UE, by forwarding messages between the remote UE and the gNB.
The concept is specified across multiple TS 38.300-series documents: TS 38.300 (NR overall description), TS 38.304 (UE procedures in idle and inactive mode), TS 38.331 (RRC protocol), TS 38.351 (L2 U2N relay), TS 38.401 (NG-RAN architecture), TS 38.470 (F1 general principles), and TS 38.473 (F1AP). These specifications define how the Last U2N Relay UE is identified, how it establishes and maintains connections, and how it interacts with the gNB and the remote UE. The term was introduced in Release 19 to support enhanced L2 U2N relaying, including multi-hop scenarios and improved mobility.
The Last U2N Relay UE enables network coverage extension and improved reliability for remote UEs that cannot directly connect to the network, such as devices in coverage holes or with limited transmit power. By defining the last relay in the chain, 3GPP provides a clear architectural anchor for procedures such as bearer setup, mobility, and security, ensuring that the remote UE's traffic is correctly forwarded and managed.
Purpose & Motivation
The Last U2N Relay UE concept exists to clarify the architecture of L2 UE-to-Network relaying in 3GPP networks, particularly for multi-hop and single-hop scenarios. Before Release 19, L2 U2N relaying was defined primarily for single-hop scenarios, and the terminology did not explicitly distinguish the relay UE closest to the remote UE. As relaying evolved to support more complex topologies, a precise term was needed to identify the relay UE that terminates the PC5 link to the remote UE (or its child UE) and the Uu link to the network.
The term solves ambiguity in procedures such as bearer establishment, mobility, and security, where the gNB and relay UEs must coordinate. By defining the Last U2N Relay UE, 3GPP enables standardized handling of multi-hop relay chains, where the last relay is responsible for forwarding traffic to the remote UE. This is essential for coverage extension in scenarios such as wearables, IoT devices, and public safety communications, where remote UEs may not have direct network connectivity.
Historically, relay architectures in 3GPP (e.g., ProSe relay in LTE) used different terminology and were often limited to single-hop. The Release 19 work on L2 U2N relaying introduced multi-hop support and refined the architecture, making the Last U2N Relay UE a key identifier for the relay UE at the edge of the chain. This enables more flexible deployments and improves interoperability between relay UEs and the network.
What changed in its specifications
The latest release-to-release comparison of specifications that define Last 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.
Introduced as part of the Release 19 L2 U2N relay enhancements. The definition establishes the Last U2N Relay UE as the relay UE with both Uu and PC5 connections to a child UE, clarifying its role in single-hop and multi-hop relay chains.
Defining Specifications
3GPP specifications that define or reference Last 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 |