Description
Proximity-based work task offloading is a novel service concept introduced in 3GPP Release 19. It leverages direct device-to-device (D2D) communication to enable a relay UE to perform computational tasks on behalf of a remote UE. The remote UE, which may have limited processing capabilities or energy constraints, sends data to a nearby relay UE via a direct connection (e.g., sidelink PC5). The relay UE then executes the required calculations and can forward the results to a network server, such as an application server or edge computing node. This offloading mechanism is initiated based on a request from a third party, which could be an application service provider or the remote UE itself.
The architecture for this feature builds upon the existing ProSe (Proximity Services) framework, utilizing the direct communication capabilities between UEs. The relay UE acts as a compute node, effectively extending the computational resources available to the remote UE. The direct connection ensures low latency and high bandwidth, which are critical for time-sensitive tasks. The network server may be involved in coordinating the offloading, providing task descriptions, or receiving results. The 3GPP specifications 22.261 (Service requirements for the 5G system) and 22.876 (Study on proximity-based services) provide the requirements and study the feasibility of this feature.
The operation of proximity-based work task offloading involves several steps. First, a third party (e.g., an application server) requests the offloading of a specific work task for a remote UE. The request may include task details, required resources, and the identity of the remote UE. The network then identifies a suitable relay UE in proximity of the remote UE, considering factors such as computational capability, battery level, and link quality. The remote UE sends the task data to the relay UE via a direct connection. The relay UE performs the calculation, which could range from simple data processing to complex computations like AI inference. Finally, the relay UE may send the results back to the remote UE or directly to the network server, depending on the task requirements.
Key technical considerations include the discovery of suitable relay UEs, the establishment and maintenance of the direct link, security and privacy of the offloaded data, and the management of computational resources. The relay UE must have sufficient resources to perform the task without compromising its own operations. The network may assist in relay selection and provide policies for offloading. The feature also raises questions about trust and incentive mechanisms, as the relay UE may be owned by a different user. 3GPP is studying these aspects to ensure a robust and secure service.
This feature is part of the broader trend towards edge computing and distributed intelligence in 5G and beyond. By enabling UEs to collaborate, it can improve energy efficiency, reduce latency, and enable new applications such as augmented reality, real-time translation, and collaborative sensing. It aligns with the 5G vision of ubiquitous connectivity and intelligent services.
Purpose & Motivation
Proximity-based work task offloading was created to address the growing demand for computational resources at the edge of the network, particularly for devices with limited processing power or battery life. Many IoT devices, wearables, and smartphones generate data that requires processing, but performing all computations locally may be inefficient or impossible. Offloading tasks to nearby devices with more resources can improve performance, reduce energy consumption, and enable new applications.
Traditional cloud offloading involves sending data to a remote server, which introduces latency and depends on network availability. Proximity-based offloading leverages direct device-to-device communication to keep data local, reducing latency and backhaul usage. It also enables offloading in scenarios where network coverage is poor or congested, such as in disaster relief or remote areas. The feature is motivated by the need for low-latency, high-reliability communication in 5G and beyond, as well as the proliferation of smart devices that can act as compute nodes.
The concept was standardized in Release 19 as part of the ongoing evolution of ProSe. It builds on earlier work on D2D communication and edge computing, integrating them into a cohesive service. By allowing third parties to request offloading, it opens up new business models and use cases, such as crowdsourced computing and collaborative applications.
What changed in its specifications
The latest release-to-release comparison of specifications that define proximity-based work task offloading. Each summary describes the whole specification, not only this term.
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 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced: based on a third party's request, a relay UE receives data from a remote UE via direct device connection and performs calculation of a work task for the remote UE, with results potentially sent to a network server. This established the concept of proximity-based work task offloading.
Defining Specifications
3GPP specifications that define or reference proximity-based work task offloading, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.261 vk81 | 5G Service and Operational Requirements | Rel-20 read |
| TR 22.876 vj10 | AI/ML Model Transfer Phase 2 Study | Rel-19 read |