Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

ProSe UE-to-UE Relay

Proximity Services User Equipment-to-User Equipment Relay

Services →

ProSe UE-to-UE Relay is a Public Safety ProSe-enabled UE that relays ProSe E-UTRA communication between two other ProSe-enabled UEs, extending direct device-to-device coverage when the endpoints cannot communicate directly.

Introduced
Rel-12
Where
Services
Specifications
4 specs
ProSe UE-to-UE Relay Description Purpose What changed Neighbours Specifications

Description

ProSe UE-to-UE Relay is a relaying function defined within the 3GPP Proximity Services (ProSe) framework, originally specified for public safety use cases. In this architecture, a Public Safety ProSe-enabled UE — typically one that has direct connectivity to both endpoints — acts as an intermediate node forwarding ProSe E-UTRA Communication between two other Public Safety ProSe-enabled UEs. The relay operates at the UE level rather than through the network infrastructure, meaning the two communicating UEs do not need a direct PC5 link to each other; instead, each maintains a PC5 link to the relay, and the relay forwards traffic between them. This is conceptually distinct from UE-to-Network Relay, where a remote UE reaches the network through a relay UE that has a Uu connection.

The relay is discovered and selected through ProSe Discovery procedures. A UE that can serve as a relay announces its relay capability via ProSe Discovery messages, and remote UEs that need relaying discover candidate relays and select one based on criteria such as signal quality, relay load, and operator policy. Once selected, the relay establishes sidelink connections to both endpoints and forwards user-plane traffic between them. Because the relay is a UE, it is subject to the same authorization and security framework as other ProSe UEs: it must be provisioned with ProSe authorization, and the relayed communication must satisfy the security requirements defined for ProSe direct communication, including the protection of the PC5 links and the handling of identity and key material.

The primary motivation for UE-to-UE Relay is coverage extension in public safety scenarios. First responders operating in environments without network coverage — inside buildings, tunnels, or remote areas — may be able to reach a relay UE even when they cannot reach each other directly. The relay bridges that gap, allowing the two endpoints to communicate over two shorter sidelink hops rather than one unattainable long hop. This improves the robustness of mission-critical push-to-talk and group communication, which are central to public safety operations.

From a standards perspective, the concept appears across ProSe requirements and security specifications. TS 22.278 defines the service requirements for ProSe, including relay operation, while TS 22.803 captures the original feasibility study that established the ProSe architecture and use cases. TS 22.261 places ProSe relay in the broader 5G service requirements context, and TS 33.833 addresses security aspects of ProSe, including the security of relayed communication. The term has been carried forward across Releases 12 through 19 with essentially stable meaning, and in Release 20 the definition was reworded for editorial clarity without changing the underlying concept.

In practice, UE-to-UE Relay is closely tied to the PC5 sidelink interface and to the ProSe Discovery and Communication procedures. It complements UE-to-Network Relay: the former extends reachability between devices, the latter extends reachability to the network. Together they form the relay toolkit that public safety operators use to maintain communication continuity when infrastructure is unavailable or degraded.

Purpose & Motivation

ProSe UE-to-UE Relay exists to solve a specific and safety-critical problem: two public safety users need to communicate directly, but the radio conditions between them do not permit a single sidelink hop. Before relay was introduced, ProSe direct communication assumed that the two endpoints could establish a PC5 link with each other. In real deployments — urban canyons, building interiors, underground facilities, and disaster scenes — that assumption frequently fails, even when each user is within range of some third device. Relay turns that third device into a bridge, converting one impossible link into two feasible links.

The concept was introduced in Release 12 as part of the original ProSe work, which was driven primarily by public safety requirements following the momentum of LTE-based mission-critical communications. Public safety agencies needed device-to-device communication that worked without network coverage, and relay extended the useful range of that capability. The alternative — relying solely on direct links or on network infrastructure — was inadequate because infrastructure may be destroyed or absent, and direct links are range-limited.

By keeping the relay function in a UE rather than in the network, 3GPP preserved the infrastructure-independent nature of ProSe communication. The relay can be any authorized public safety device, including one carried by a first responder, which makes the capability deployable without dedicated relay infrastructure. The trade-off is that relayed paths consume relay resources and add latency, so relay selection and authorization procedures exist to ensure relays are used appropriately and securely.

What changed in its specifications

The latest release-to-release comparison of specifications that define ProSe UE-to-UE Relay. Each summary describes the whole specification, not only this term.

TS 22.261Rel-18 → Rel-19

Rel-19 adds to TS 22.261 Indirect Network Sharing, 5G satellite access Phase 3 requirements, a 5G wireless sensing service clause, signalling traffic monitoring, SNPN interconnection clauses, and Localized Mobile Metaverse Services. It also extends disaster roaming to 5G-only UEs and adds Ambient IoT device clauses.

Full comparison in TS 22.261 →
TS 22.278Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 22.278: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 22.278 →

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.

Rel-12 Initial

Initial definition introduced with the ProSe framework: a Public Safety ProSe-enabled UE acts as a ProSe E-UTRA Communication relay between two other Public Safety ProSe-enabled UEs, establishing the UE-to-UE relay concept for coverage extension in public safety scenarios.

Definition carried over unchanged from Release 12; the relay concept remained stable while ProSe requirements continued to mature.

Definition carried over unchanged; no textual revision to the relay definition in this release.

Definition carried over unchanged; the term retained its Release 12 wording.

Definition carried over unchanged; no revision to the relay definition text.

Definition carried over unchanged; the relay concept continued to be referenced with the same wording.

Definition carried over unchanged; no textual change to the definition.

Definition carried over unchanged; the term remained stable through Release 19.

Wording revised for editorial clarity: the definition was rephrased from 'is a form of relay in which a Public Safety ProSe-enabled UE acts as a ProSe E-UTRA Communication relay between two other Public Safety ProSe-enabled UEs' to 'a Public Safety ProSe-enabled UE that acts as a relay between two other Public Safety ProSe-enabled UEs.' The change is stylistic — it removes the 'form of relay' framing and the 'E-UTRA Communication' qualifier from the core sentence — while the underlying concept of a UE relaying between two other UEs is preserved.

Defining Specifications

3GPP specifications that define or reference ProSe UE-to-UE Relay, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.261 vk81 5G Service and Operational Requirements Rel-20 read
TS 22.278 vj00 Evolved Packet System Service Requirements Rel-19 read
TS 22.803 vc20 Proximity Services Use Cases and Requirements Rel-12 read
TS 33.833 vd00 ProSe Security Study Rel-13 read