Description
The MP relay UE (Multi-Path Relay User Equipment) is a 5G UE that serves as the intermediate node of an indirect communication path towards a Multi-Path remote UE. It was introduced in 3GPP Release 18 as part of the Multi-Path (MP) enhancement work in the NR sidelink and UE-to-Network (U2N) relay framework. In the overall architecture defined in TS 38.300 and TS 38.401, a remote UE may maintain simultaneously a direct Uu path to a gNB and one or more indirect paths through a relay UE. The MP relay UE is the entity that terminates the indirect path on the network side of the remote UE.
The MP relay UE is a dual-role device. On the one hand it maintains its own connection to the 5G network — either a Uu connection to a gNB (when relaying over PC5) or a Non-3GPP Connection (N3C) such as Wi-Fi to a Non-3GPP Interworking Function (N3IWF) or Trusted Non-3GPP Gateway (TNGF). On the other hand it provides connectivity to the MP remote UE. The nature of the remote-side link determines the relay role: when the indirect path is a PC5 unicast link (sidelink), the MP relay UE acts as an L2 UE-to-Network Relay UE, forwarding the remote UE's traffic at layer 2 using the PC5-S and PC5-RRC procedures and the adaptation layer defined for sidelink relay; when the indirect path is a Non-3GPP Connection, the MP relay UE acts as an N3C relay UE, i.e. it provides a non-3GPP access leg towards the core network on behalf of the remote UE.
In the L2 U2N relay case, the MP relay UE performs discovery (via PC5 discovery procedures defined in TS 38.331 and TS 23.304), establishes a PC5 unicast link with the remote UE, and then establishes or reuses a Uu connection to the gNB. The relay UE carries the remote UE's signalling and data in adaptation-layer PDUs over PC5, and the gNB (or the relay UE's serving cell) manages the remote UE's RRC context. The relay UE therefore needs to support the sidelink relay adaptation protocol, buffer management, and mapping between PC5 bearers and Uu bearers. In the N3C relay case, the relay UE provides IP-level forwarding between the remote UE and the non-3GPP access network, and the remote UE registers with the 5G core through the N3IWF/TNGF path.
The Multi-Path aspect is what distinguishes the MP relay UE from a conventional single-path relay. The remote UE can be configured with multiple paths (a direct path plus one or more indirect paths, or multiple indirect paths) and the network can steer traffic across them, for example to improve throughput, reliability, or coverage. The MP relay UE is therefore a candidate path endpoint that the network can select, add, or remove as part of multi-path configuration and traffic steering decisions. Control-plane signalling for path management is carried over RRC (TS 38.331) and, for the relay's own connection, over NGAP/F1AP (TS 38.401, 38.470, 38.473) when the relay is connected via a gNB.
The MP relay UE is relevant to both NR sidelink relay and non-3GPP access scenarios, and it is a key enabler for coverage extension, offloading, and resilience use cases such as public safety, wearables, and vehicle-to-everything communication. Its behaviour is specified across RAN2 (38.300, 38.331), RAN3 (38.401, 38.470, 38.473) and SA2 (23.304) specifications.
Purpose & Motivation
Before Release 18, UE-to-Network relaying in 3GPP was single-path: a remote UE either used a direct Uu link or an indirect link through a relay, but not both simultaneously in a coordinated manner. This limited the benefits of relaying to pure coverage extension and prevented the network from exploiting multiple simultaneous paths for throughput aggregation, reliability, or seamless mobility. The Multi-Path work in Release 18 was motivated by the need to support use cases where a UE has both a direct cellular link and a sidelink or non-3GPP path, and where the network should be able to steer traffic between them.
The MP relay UE exists to give the network a well-defined relay endpoint for these multi-path configurations. By defining the relay's role conditionally on the type of indirect path (L2 U2N relay for PC5, N3C relay for non-3GPP), 3GPP avoided creating separate, incompatible relay concepts and instead reused the existing sidelink relay and N3C architectures. This lets a single device serve as a relay in either access technology while the remote UE and network manage paths uniformly.
The concept also addresses the limitation that conventional relays were transparent to path selection: the network had no standard way to add or remove an indirect path while a direct path was active. With the MP relay UE, path management becomes an explicit, standardised procedure, enabling load balancing, coverage enhancement at cell edges, and improved session continuity.
What changed in its specifications
The latest release-to-release comparison of specifications that define MP 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 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
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 the MP relay UE concept as part of the Multi-Path enhancement to NR sidelink relay and non-3GPP access. The definition establishes the dual role: L2 U2N Relay UE for PC5 unicast indirect paths and N3C relay UE for Non-3GPP Connection indirect paths.
Defining Specifications
3GPP specifications that define or reference MP 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.331 vj40 | NR Radio Resource Control (RRC) | 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 |