Description
The Remote UE is a key concept in 3GPP Proximity Services (ProSe) for public safety, defined in specifications such as TS 23.303, TS 23.468, TS 23.752, TS 33.833, and TS 36.300. It refers to a User Equipment (UE) that is enabled for ProSe and is used by public safety personnel, but is not directly served by the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). Instead, it communicates with a Packet Data Network (PDN) through a ProSe UE-to-Network Relay. This architecture allows devices that are out of network coverage to maintain connectivity by relaying their traffic through another UE that has network coverage.
The Remote UE operates in a direct communication mode with the ProSe UE-to-Network Relay, using the PC5 interface (sidelink). The relay UE acts as a Layer-3 router or a Layer-2 bridge, forwarding IP packets between the Remote UE and the PDN. The Remote UE may be a handheld device, a vehicle-mounted terminal, or any other public safety device. The key requirement is that it supports ProSe direct discovery and communication. The Remote UE can discover a suitable relay UE either through direct discovery procedures or by using a pre-configured relay association.
Architecturally, the Remote UE connects to the relay UE via the PC5 interface, and the relay UE connects to the network via the Uu interface (E-UTRAN). The relay UE may be served by the network directly or may itself be out of coverage but connected to another relay. The ProSe function in the core network manages authorization, authentication, and policy for the Remote UE and the relay. The Remote UE's traffic is encapsulated and forwarded by the relay, which may apply security (e.g., IPsec) to protect the communication. The Remote UE can access PDN services, including IP-based applications, as if it were directly connected to the network.
The Remote UE concept is particularly important for mission-critical push-to-talk (MCPTT) and other public safety applications, where reliable communication is essential even in areas with no network coverage. The relay functionality extends network coverage and improves resilience. The definition of Remote UE has evolved slightly: in Rel-13, it was defined as a ProSe-enabled Public Safety UE that is not served by E-UTRAN and communicates with a PDN via a ProSe UE-to-Network Relay. In Rel-14, the wording changed to remove the explicit 'not served by E-UTRAN' condition, reflecting that the Remote UE may be in coverage but still choose to communicate via a relay for other reasons (e.g., power saving, policy). This change broadened the applicability of the term.
The Remote UE is a fundamental element of the ProSe UE-to-Network Relay architecture, which is part of the broader 3GPP efforts to support public safety and mission-critical communications. It enables devices to communicate beyond network coverage, enhancing the capabilities of first responders. The term is closely related to ProSe UE-to-Network Relay, ProSe, PC5 interface, and public safety.
Purpose & Motivation
The Remote UE concept was created to address the need for public safety users to maintain communication even when they are outside network coverage. In disaster scenarios or remote areas, network infrastructure may be damaged or absent, but first responders still need to communicate with each other and with command centers. Traditional cellular communication requires direct connection to a base station, which is not always available. The ProSe UE-to-Network Relay architecture allows a UE that has network coverage (the relay UE) to extend connectivity to other UEs (the Remote UEs) that are out of coverage.
The Remote UE solves the problem of coverage holes by leveraging device-to-device (D2D) communication. It enables a group of public safety users to stay connected as long as at least one device in the group has network coverage. This is particularly useful for search and rescue operations, where teams may be spread out and some members may be in areas without direct cellular signal. The Remote UE can access the same PDN services as a directly connected UE, including IP-based applications, location services, and group communication.
Historically, the Remote UE was introduced in 3GPP Rel-13 as part of the initial ProSe specifications for public safety. The definition was refined in Rel-14 to remove the restriction that the Remote UE must not be served by E-UTRAN, acknowledging that a UE might still use a relay even when in coverage, for example to conserve battery or to use a more robust link. This evolution reflects the growing understanding of relay use cases and the flexibility required in public safety operations. The Remote UE remains a critical component of mission-critical communication systems, and its definition continues to be maintained in subsequent releases.
What changed in its specifications
The latest release-to-release comparison of specifications that define Remote UE. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 23.303: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.303 →Rel-19 brings only minor changes to TS 23.468: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.468 →Technology family
Sidelink, D2D and V2X · Services
- Rel-12 EPC-level ProSe Discovery, ProSe, ProSe Direct Communication, ProSe Direct Discovery, PSBCH, PSCCH, PSDCH, PSSCH, Sidelink
- Rel-13 PPPP, ProSe UE-to-Network Relay, Remote UE
- Rel-14 RSU
- Rel-15 PPPR
- Rel-16 NR sidelink communication, PC5 QoS Flow, PQI
- Rel-17 5G ProSe Direct Communication, 5G ProSe Direct Discovery, 5G ProSe Remote UE, 5G ProSe UE-to-Network Relay, NR sidelink discovery, SRAP
- Rel-18 5G ProSe UE-to-UE Relay, NR SL CA, Sidelink Positioning, SL-PRS, U2U Relay UE, U2U Remote UE
- Rel-19 5G ProSe Intermediate UE-to-Network Relay
- Remote UE counterpart in another generation: 5G ProSe Remote UE
“5G ProSe Remote UE: A 5G ProSe-enabled UE that communicates with a DN via zero or more 5G ProSe Intermediate UE-to-Network Relay(s) and a 5G ProSe UE-to-Network Relay.” TS 23.304
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Rel-13 clarified Remote UE behaviour in 23.303 (out-of-network, in-coverage, PLMN authorization provisioning) and added a Remote UE Report Notification in 29.274.
Rel-17 specifies 5G ProSe Layer-2 and Layer-3 Remote UE behaviour for the first time, covering relay discovery, PC5 security, QoS, IP addressing, and the Remote UE report procedure.
- “A UE is considered to be a 5G ProSe Layer-2 Remote UE if it has successfully established a PC5 link” TS 23.304 v17.8.0
- “the 5G ProSe Remote UE plays the role of the Monitoring UE and sends a Relay Discovery Key Request” TS 33.503 v17.10.0
- Introducing the Remote UE report procedure TS 24.501CR3426
Rel-18 extends Remote UE behaviour: emergency service access with PLMN selection and PC5 security, relay reselection path switching, multipath traffic handling, and PEI identification of Remote UE.
- “A Layer-2 Remote UE can select a PLMN different from the 5G ProSe Layer-2 UE-to-Network Relay's serving PLMN to access emergency and non-emergency services.” TS 23.304 v18.8.0
- “A 5G ProSe Remote UE can establish a PC5 security link for Emergency service with a network” TS 33.503 v18.6.0
- Remote UE identified by PEI TS 24.501CR5704
Remote UE behaviour was extended for multi-hop relaying: it determines and signals a Hop-Limit in discovery solicitation, uses hop count and accumulated QoS for relay selection, and reselects relays.
- “If the Hop-Limit is determined based on configuration associated with the RSC, the 5G ProSe Remote UE does not include the Hop-Limit in the Solicitation message.” TS 23.304 v19.6.0
- “The 5G ProSe Remote UE can also take the Accumulated QoS for PC5 link into account.” TS 23.304 v19.6.0
- Clarification on Relay reselection for 5G ProSe Remote UE with 5G ProSe Multi-hop UE-to-Network Relays TS 23.304CR0549
Rel-20 adds slice-based N3IWF selection for 5G ProSe Layer-3 Remote UE, with new Extended N3IWF identifier and Slice-specific N3IWF prefix configurations that take precedence over the existing N3IWF selection.
- “a 5G ProSe Layer-3 Remote UE is configured by HPLMN with Extended N3IWF identifier configuration and Slice-specific N3IWF prefix configuration” TS 23.304 v20.1.0
- “slice-based N3IWF selection procedure takes precedence over N3IWF selection procedure.” TS 23.304 v20.1.0
- Adding parameters required to support slice-based N3IWF selection for 5G ProSe Layer-3 Remote UE TS 31.102CR1108
Defining Specifications
3GPP specifications that define or reference Remote UE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.303 vj00 | Proximity Services (ProSe) Stage 2 | Rel-19 read |
| TS 23.468 vj00 | Group Communication System Enablers for LTE | Rel-19 read |
| TR 23.752 vh00 | 5G ProSe Enhancement Study | Rel-17 read |
| TS 33.833 vd00 | ProSe Security Study | Rel-13 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |