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

Glossary term · Services

EEC Context

Edge Enabler Client Context

Services →

EEC Context is a set of data about an Edge Enabler Client stored in the Edge Enabler Server, enabling stateful, personalized edge service provisioning and efficient reconnection.

Introduced
Rel-17
Where
Services
Specifications
2 specs
EEC Context Description Purpose What changed Neighbours Detected Changes Specifications

Description

EEC Context (Edge Enabler Client Context) is a data structure maintained by the Edge Enabler Server (EES) that contains information about a registered Edge Enabler Client (EEC). It is defined in TS 23.558 as part of the 3GPP Edge Computing architecture. The EEC Context is created when an EEC registers with an EES and is updated as the EEC's state or requirements change. It serves as the EES's memory of the client, enabling stateful interactions that go beyond simple request-response exchanges.

The EEC Context typically includes information such as the EEC's identity, the identity of the UE hosting the EEC, information about the Application Clients associated with the EEC, the services the EEC is interested in, and potentially location or mobility information. This data allows the EES to tailor its responses to service discovery requests, for example by prioritizing Edge Application Servers that are geographically close to the UE or that support the specific features required by the Application Client. The EEC Context may also include security credentials or tokens that authenticate the EEC and authorize it to access certain services.

One of the key roles of EEC Context is to support service continuity. When a UE moves and its EEC needs to connect to a different EES (for example, because it has moved to a new edge hosting environment), the new EES can obtain the EEC Context from the old EES (subject to authorization) to maintain continuity of service. This allows the EES to preserve information about the client's preferences and ongoing sessions, reducing the need for re-negotiation and improving the user experience. The EEC Context thus acts as a portable state object that can follow the client across edge environments.

The EEC Context is managed through the EDGE-1 reference point between the EEC and the EES. The EEC can register, update, and deregister its context. The EES may also update the context based on information it receives from other sources, such as network functions that provide UE location or mobility information. The context is stored securely and is subject to access control policies to prevent unauthorized disclosure or modification.

In summary, EEC Context is a fundamental concept in the 3GPP edge computing architecture. It enables the EES to provide personalized, stateful services to EECs, supports service continuity across edge hosting environments, and provides a foundation for advanced features such as context-aware service discovery and policy-based resource allocation. Its definition has remained stable across Rel-17 through Rel-20, reflecting its foundational role in the architecture.

Purpose & Motivation

EEC Context exists to solve the problem of statelessness in edge service provisioning. In a purely stateless model, each service discovery request from an EEC would be handled independently, with no memory of previous interactions. This would make it difficult for the EES to provide personalized services, to enforce policies based on the client's history, or to support service continuity when the client moves.

By maintaining EEC Context, the EES can remember information about the client across multiple interactions. This enables a range of valuable capabilities: the EES can prioritize services based on the client's past behavior or stated preferences; it can enforce quotas or access controls that depend on the client's identity and history; and it can support seamless handover of the client's session when the client moves to a new edge environment. This is particularly important for latency-sensitive and interactive applications, where re-establishing context from scratch could introduce unacceptable delays.

Furthermore, EEC Context provides a standardized way to represent client state, which is essential for interoperability between different vendors' EES implementations and for multi-operator edge deployments. Without a standardized context format, each EES would store client state in a proprietary way, making it difficult to transfer context between EESs or to build a consistent view of the client across the edge. The EEC Context definition in TS 23.558 provides this standardization, enabling a more open and interoperable edge ecosystem.

What changed in its specifications

The latest release-to-release comparison of specifications that define EEC 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

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (6 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 4 changes
  • EEC context relocation TS 23.558CR0008
  • Provide EES endpoint in ACR request to enable EEC context relocation during ACR TS 23.558CR0044
  • List of subscriptions to the CN in EEC context TS 23.558CR0054
  • Unique identification of the EEC context in ACR procedures TS 23.558CR0088
Rel-18 2 changes
  • Resolving EN about updating EEC Context with EDGE-3 subscriptions TS 23.558CR0394
  • Resolve the EN on EEC context handling procedure TS 23.558CR0461

Defining Specifications

3GPP specifications that define or reference EEC 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
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read