Description
The MP remote UE (Multi-Path Remote User Equipment) is a 5G UE that is configured with Multi-path connectivity, i.e. it can maintain a direct path to the network (typically a Uu link to a gNB) together with one or more indirect paths through relay UEs. It was introduced in Release 18 alongside the MP relay UE as part of the Multi-Path enhancement to the NR sidelink relay and non-3GPP access frameworks. The concept is defined in TS 38.300 and referenced in RRC (38.331), NG-RAN architecture (38.401), and F1AP/XnAP specifications (38.470, 38.473).
The MP remote UE is characterised by its configuration rather than by a fixed role: it is a UE for which the network has configured multi-path operation. The indirect path may be realised in two ways. When the indirect path is a PC5 unicast link to a relay UE, the MP remote UE acts as an L2 UE-to-Network Remote UE: it performs PC5 discovery, establishes a PC5 unicast link with the MP relay UE, and exchanges adaptation-layer PDUs carrying its own signalling and user data. In this mode the remote UE's RRC connection is anchored at the gNB serving the relay, and the remote UE uses the sidelink relay procedures of TS 38.331. When the indirect path is a Non-3GPP Connection, the MP remote UE acts as an N3C remote UE: it connects through a relay UE that provides non-3GPP access towards an N3IWF or TNGF, and its NAS signalling reaches the 5G core over that non-3GPP path.
Multi-path operation means the remote UE can have simultaneous direct and indirect paths, and the network can steer traffic between them. This requires the remote UE to support path selection and path management signalling, to maintain the necessary contexts for each path, and to handle potential reordering or duplication when traffic is split across paths. The remote UE may also support measurement reporting on candidate relay UEs and candidate paths so that the network can decide when to add, modify, or release an indirect path.
The MP remote UE is a key enabler for use cases such as coverage extension at cell edge, throughput aggregation by combining direct and relay paths, reliability through path redundancy, and offloading of traffic onto sidelink or non-3GPP access. Because the remote UE can be served by both a direct and an indirect path, it benefits from improved robustness against link failure and from the ability of the network to balance load across paths.
In terms of protocol architecture, the MP remote UE interacts with the MP relay UE over PC5 (when the indirect path is sidelink) and with the gNB over Uu for the direct path. The network side coordinates the paths through RRC configuration and, where applicable, through NG-RAN interfaces. The remote UE's behaviour is specified primarily in TS 38.300 (stage 2) and TS 38.331 (RRC), with architecture aspects in TS 38.401 and F1AP in TS 38.470/38.473.
Purpose & Motivation
Prior to Release 18, a remote UE in the 3GPP relay framework was associated with a single path: either a direct Uu connection or an indirect connection through a relay UE. There was no standard mechanism for a UE to use both a direct and an indirect path at the same time under network control. This restricted relaying to coverage-extension scenarios and prevented operators from exploiting the combined capacity of multiple links.
The MP remote UE was created to formalise the endpoint of multi-path connectivity on the UE side. By defining the remote UE's role conditionally on the type of indirect path — L2 U2N Remote UE for PC5 unicast links and N3C remote UE for Non-3GPP Connections — 3GPP reused the existing sidelink relay and non-3GPP access architectures rather than inventing a new one. This ensures that a UE supporting multi-path can interoperate with existing relay and N3IWF/TNGF deployments.
The concept solves the problem of path rigidity: with multi-path, the network can add or remove an indirect path while a direct path remains active, improving coverage, throughput, and reliability without interrupting the session. It also enables operators to offload traffic to sidelink or Wi-Fi paths when beneficial, and to provide resilience when one path degrades.
What changed in its specifications
The latest release-to-release comparison of specifications that define MP remote 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.
Defining Specifications
3GPP specifications that define or reference MP remote 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 |