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

Glossary term · Services

Application Context

Application Context

Services →

Application Context is a set of data about the Application Client that resides in the Edge Application Server, used to maintain service continuity in edge computing and enable the EAS to adapt to client-specific conditions and support seamless relocation.

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

Description

The Application Context is a concept introduced in 3GPP Release 17 within the framework of Edge Computing (EDGE) in 5G networks, as specified in 3GPP TS 23.558. It refers to a collection of data about an Application Client (AC) that is stored in the Edge Application Server (EAS). This data is essential for the EAS to provide services tailored to the specific needs and conditions of the Application Client, and it plays a critical role in enabling service continuity when the client moves or when the EAS needs to be relocated.

In the edge computing architecture, an Application Client runs on a User Equipment (UE) and communicates with an EAS that is typically deployed close to the network edge to minimize latency. The Application Context includes information such as the client's identity, session state, quality of service (QoS) requirements, location, and other application-specific parameters. This context is maintained by the EAS to ensure that the application service can be delivered consistently and with the required performance. For example, in a video streaming application, the Application Context might include the current playback position, buffering status, and preferred resolution, allowing the EAS to resume streaming seamlessly if the client switches to a different EAS.

The Application Context is particularly important for Application Context Relocation (ACR), a procedure that enables the transfer of the context from one EAS to another when the UE moves or when a more suitable EAS becomes available. During ACR, the source EAS transfers the Application Context to the target EAS, ensuring that the application session continues without interruption. This is crucial for maintaining end-to-end service continuity, especially for latency-sensitive and interactive applications.

The context is managed through the EDGEAPP (Edge Application) enablers, which include functions like the Edge Enabler Server (EES) and Edge Enabler Client (EEC). The EES provides registration and discovery services for EASs and ACs, and it facilitates the exchange of Application Context between EASs during relocation. The EEC on the UE side helps in establishing and maintaining the connection between the AC and the EAS, and it may assist in the context transfer by providing relevant information to the EES.

In summary, the Application Context is a vital element of the edge computing ecosystem, enabling personalized and continuous service delivery. It allows EASs to maintain state and adapt to client-specific conditions, and it is the key enabler for seamless service continuity through relocation. As edge computing evolves, the Application Context will continue to be refined to support new use cases and applications.

Purpose & Motivation

The Application Context was created to address the challenge of maintaining application state and service continuity in distributed edge computing environments. In traditional cloud computing, applications often rely on centralized servers, but edge computing brings services closer to the user, which introduces mobility challenges. When a user moves, the edge application server may need to change, and without a standardized way to transfer context, the application session could be disrupted. The Application Context provides a structured set of data that can be moved between edge servers, enabling seamless handover and ensuring that the user experience remains consistent. It also allows edge applications to be aware of client-specific conditions, such as device capabilities and network status, so they can optimize service delivery. This concept is essential for realizing the full potential of edge computing in 5G, particularly for latency-sensitive and interactive applications like augmented reality, gaming, and autonomous vehicles.

What changed in its specifications

The latest release-to-release comparison of specifications that define Application Context. 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. The Application Context was defined as a set of data about the Application Client residing in the Edge Application Server, establishing the foundation for service continuity in edge computing.

Definition carried over unchanged from Rel-17. The concept remained stable as edge computing specifications were further developed.

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

Wording changed to explicitly reference 3GPP TS 23.558 [3] within the definition: 'A set of data about the Application Client that resides in the Edge Application Server (as defined in 3GPP TS 23.558 [3]).' This adds a normative reference to the specification, clarifying the source and scope of the definition without altering the technical meaning.

Defining Specifications

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

SpecificationTitleRelease
TS 23.558 vk30 Enabling Edge Applications Rel-20 read
TS 23.947 vk10 Developer Guide to CAPIF, EDGEAPP and SEAL Rel-20 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read