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

Glossary term · Services

Application Context Relocation

Application Context Relocation

Services →

Application Context Relocation is an end-to-end service continuity procedure that transfers application context from source to target Edge Application Servers, ensuring seamless service when a UE moves or a better Edge Application Server is selected.

Introduced
Rel-17
Where
Services
Specifications
2 specs
Application Context Relocation Description Purpose What changed Neighbours Specifications

Description

Application Context Relocation (ACR) is a key procedure in 3GPP Edge Computing, introduced in Release 17 and specified in 3GPP TS 23.558. It refers to the end-to-end service continuity procedure described in clause 8.8 of that specification. ACR enables the transfer of the Application Context from a source Edge Application Server (EAS) to a target EAS, ensuring that an ongoing application session continues without interruption when a User Equipment (UE) moves or when network conditions necessitate a change of EAS.

The need for ACR arises from the mobile nature of UEs and the distributed deployment of edge servers. As a UE moves, the optimal EAS may change to maintain low latency and high quality of service. Without ACR, the application session would be disrupted, leading to a poor user experience. ACR addresses this by allowing the source EAS to transfer the application state—encapsulated in the Application Context—to the target EAS. This context includes all necessary information for the target EAS to resume the session, such as session identifiers, security keys, QoS parameters, and application-specific state.

The ACR procedure involves several functional entities. The Edge Enabler Server (EES) plays a central role by coordinating the relocation. The source EES detects the need for relocation (e.g., due to UE mobility or load balancing) and identifies a suitable target EES. It then initiates the context transfer, which may involve the source EAS sending the Application Context to the target EAS directly or via the EES. The Edge Enabler Client (EEC) on the UE side may also be involved, for example, to provide updated information or to assist in re-establishing the connection to the target EAS. The procedure includes steps for authentication, authorization, and secure transfer of the context to prevent unauthorized access.

ACR is designed to be transparent to the application client, minimizing service disruption. It supports various relocation scenarios, including UE mobility, EAS load balancing, and planned maintenance. The procedure can be triggered by the EES based on network events or by the EAS itself. The 3GPP specifications define the message flows and interfaces for ACR, ensuring interoperability between different vendors' equipment.

In summary, Application Context Relocation is a critical enabler for service continuity in edge computing. It allows applications to seamlessly migrate between edge servers, maintaining session state and QoS. As edge computing becomes more prevalent in 5G and beyond, ACR will be essential for delivering reliable and high-performance services to mobile users.

Purpose & Motivation

Application Context Relocation was developed to solve the problem of service interruption when a UE moves between different edge application servers. In edge computing, applications are hosted on servers close to the user to reduce latency. However, as users move, the optimal server may change, and without a standardized relocation procedure, the application session would be dropped and need to be re-established, causing delays and a poor user experience. ACR provides a standardized, end-to-end procedure for transferring the application context from one EAS to another, ensuring that the session continues seamlessly. This is particularly important for real-time and interactive applications such as online gaming, augmented reality, and autonomous driving, where even brief interruptions can be unacceptable. ACR also enables load balancing and maintenance operations without disrupting services. By defining the procedures and interfaces, 3GPP ensures that ACR can be implemented interoperably across different network deployments, facilitating the widespread adoption of edge computing.

What changed in its specifications

The latest release-to-release comparison of specifications that define Application Context Relocation. Each summary describes the whole specification, not only this term.

TS 23.558Rel-18 → Rel-19

Rel-19 adds common EAS removal and update procedures, ACR event subscription, bundle EAS discovery, and federation and roaming to TS 23.558. It also adds application group handling with group-level EAS discovery and ACR for UE groups, plus ADAE edge load analytics for EES selection.

Full comparison in TS 23.558 →

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-17 Initial

Initial definition introduced with the Edge Computing enablers. ACR was defined as the end-to-end service continuity procedure described in clause 8.8, establishing the framework for seamless application migration between edge servers.

Definition carried over unchanged from Rel-17. The procedure remained stable as edge computing specifications were refined.

Definition carried over unchanged from Rel-18. No changes to the definition text.

Definition carried over unchanged from Rel-19. The term continues to reference the procedure in clause 8.8 without modification.

Defining Specifications

3GPP specifications that define or reference Application Context Relocation, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.558 vk30 Enabling Edge Applications Rel-20 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read