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

Glossary term · Services

Edge Enabler Server

Edge Enabler Server

Services →

Edge Enabler Server is a functional entity in the Edge Hosting Environment that provides edge services to Edge Application Servers and Edge Enabler Clients, enabling standardized edge computing in 5G.

Introduced
Rel-17
Where
Services
Specifications
2 specs
Edge Enabler Server Description Purpose Neighbours Specifications

Description

The Edge Enabler Server (EES) is a core functional entity of the 3GPP Edge Computing architecture, defined in TS 23.558 (and referenced in TS 23.758 for related application layer support). It resides in the Edge Hosting Environment, which is typically a data center or compute node located at or near the network edge, such as a Multi-access Edge Computing (MEC) platform or a local 5G core deployment. The EES acts as the central point of control for edge services within its hosting environment, mediating between Edge Application Servers (which provide the actual application logic) and Edge Enabler Clients (which reside in UEs and represent applications).

The EES provides several key services. First, it supports registration of Edge Application Servers, allowing them to advertise their available services and capabilities. Second, it provides service discovery to Edge Enabler Clients, enabling UEs to find Edge Application Servers that can meet their requirements, taking into account factors such as the UE's location, the requested service characteristics, and the availability of resources. Third, the EES maintains EEC Context, which is a set of data about each registered Edge Enabler Client, enabling stateful interactions and personalized service provisioning.

The EES communicates with other entities through standardized reference points. The EDGE-1 reference point connects the EES to the EEC, carrying service provisioning, registration, and discovery messages. The EDGE-3 reference point connects the EES to Edge Application Servers, allowing them to register and expose their services. The EES may also interact with the Edge Configuration Server (ECS) to obtain configuration information and with underlying 5G network functions (such as the NEF or PCF) to obtain network information like UE location or QoS capabilities.

In terms of operation, when an EEC registers with an EES, it provides information about itself and its associated Application Clients. The EES stores this information as EEC Context and may use it to tailor service discovery results. When the EEC requests service discovery, the EES evaluates the request against the registered Edge Application Servers and returns a list of suitable candidates, potentially including information such as service endpoints, supported features, and proximity. The EES may also support service continuity when the UE moves between edge hosting environments, helping to maintain session continuity.

Security for the EES is addressed in TS 33.739, which specifies authentication and authorization mechanisms between the EES and other EEL entities. The EES must authenticate EECs before providing services and must ensure that only authorized Edge Application Servers can register. The EES is a critical component of the 3GPP edge computing architecture, as it is the primary point of interaction for UEs seeking edge services and the primary point of control for operators managing edge resources.

Purpose & Motivation

The Edge Enabler Server exists to provide a standardized, operator-controlled point of mediation between UE applications and edge application servers. In early edge computing deployments, applications had to be pre-configured with the addresses of edge servers, or rely on proprietary discovery mechanisms. This was inflexible, did not scale well, and made it difficult to support mobility, where a UE might move between different edge hosting environments.

The EES solves this by centralizing service discovery and provisioning within each edge hosting environment. Applications (via the EEC) query the EES to discover available services, and the EES can take into account dynamic factors such as the UE's current location, network conditions, and resource availability. This enables a much more dynamic and efficient use of edge resources. It also allows operators to apply policies, such as restricting certain services to certain UE types or locations, and to manage the lifecycle of edge applications.

Furthermore, the EES enables service continuity across edge hosting environments. By maintaining EEC Context and potentially coordinating with other EESs, the EES can help ensure that a UE's edge sessions are maintained as it moves, which is critical for latency-sensitive applications like augmented reality or connected vehicles. The EES thus plays a central role in making edge computing a viable, standardized part of the 5G ecosystem.

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 the Edge Enabler Server as a functional entity in the Edge Hosting Environment providing services for Edge Application Servers and Edge Enabler Clients, establishing its core role in the edge computing architecture.

Definition text carried over unchanged from Rel-17, with the EES continuing to serve as the central edge service mediation entity.

Defining Specifications

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

SpecificationTitleRelease
TR 23.758 vh00 Study on Edge Application Architecture Rel-17 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read