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

Glossary term · Services

Edge Enabler Layer

Edge Enabler Layer

Services →

Edge Enabler Layer is the collection of 3GPP-defined edge computing functions, EEC, EES, ECS, and CES, that enable applications to discover and use edge services in 5G networks.

Introduced
Rel-17
Where
Services
Specifications
2 specs
Edge Enabler Layer Description Purpose What changed Neighbours Specifications

Description

The Edge Enabler Layer (EEL) is a foundational concept in the 3GPP Edge Computing (formerly Edge Application) architecture defined in TS 23.558. It refers to the overall functionality provided by a set of functional entities that together enable edge applications to be discovered, instantiated, and consumed by User Equipment (UE) in a standardized way. The EEL sits between the underlying 5G network (including the 5G Core and Radio Access Network) and the edge applications themselves, acting as an enabling middleware that abstracts network complexity from application developers.

The primary entities comprising the Edge Enabler Layer are the Edge Enabler Client (EEC), which resides in the UE and provides edge support functions to the Application Client; the Edge Enabler Server (EES), which resides in the Edge Hosting Environment and provides services to Edge Application Servers and EECs; and the Edge Configuration Server (ECS), which provides configuration information to the EEC to enable it to connect to available EESs. In Rel-18, a fourth entity, the Cloud Enabler Server (CES), was added to the architecture, extending the layer to support cloud-edge continuum scenarios where edge services may be provided from cloud environments.

The EEL operates through a set of well-defined reference points and APIs. The EDGE-1 reference point connects the EEC to the EES, enabling service provisioning, registration, and discovery. The EDGE-4 reference point connects the EEC to the ECS for configuration. The EDGE-3 reference point connects the EES to Edge Application Servers, allowing them to register and expose their services. The EDGE-5 reference point connects the EEC to Application Clients in the UE. These APIs are specified as RESTful interfaces, typically using HTTP/JSON, making them accessible to a wide range of application developers.

A key function of the EEL is service discovery. When a UE application needs an edge service, the EEC queries the EES (or ECS) to discover available Edge Application Servers that can serve the request, taking into account factors such as the UE's location, the application's requirements, and the availability of edge resources. This enables dynamic, location-aware service selection that can significantly reduce latency and improve user experience compared to always routing traffic to a distant cloud data center.

The EEL also supports the concept of EEC Context, which is a set of data about the EEC that resides in the EES. This context allows the EES to maintain state about the UE's edge client, enabling personalized service provisioning and efficient reconnection when the UE moves between edge hosting environments. Security for the EEL is addressed in TS 33.739, which specifies authentication and authorization mechanisms between the EEL entities, ensuring that only authorized clients can access edge services and that service provisioning is protected against tampering and eavesdropping.

Purpose & Motivation

The Edge Enabler Layer exists to solve a fundamental problem in edge computing: how do applications running on a UE discover and connect to edge services in a standardized, interoperable way? Before 3GPP standardized edge computing in Rel-17, edge deployments were largely proprietary, with each operator or vendor implementing its own discovery and provisioning mechanisms. This created fragmentation, made it difficult for application developers to write portable edge applications, and limited the ability of UEs to roam between edge environments.

The EEL addresses this by defining a common set of functional entities and APIs that abstract the complexity of the underlying 5G network. Application developers no longer need to understand the details of 5G Core network functions, network exposure, or local breakout; they simply interact with the EEC and EES APIs. This separation of concerns accelerates edge application development and enables a vibrant ecosystem of edge services.

Furthermore, the EEL enables operators to expose edge capabilities in a controlled, secure manner. By centralizing service discovery and configuration in the ECS and EES, operators can apply policies, enforce security, and manage resource allocation. The addition of the Cloud Enabler Server in Rel-18 reflects the evolution toward a cloud-edge continuum, where the boundary between edge and cloud becomes fluid and applications can be served from the most appropriate location.

What changed in its specifications

The latest release-to-release comparison of specifications that define Edge Enabler Layer. 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 the Edge Enabler Layer as the functionality provided by the Edge Enabler Client, Edge Enabler Server, and Edge Configuration Server, establishing the foundational three-entity edge computing architecture.

The definition was revised to add the Cloud Enabler Server (CES) to the list of entities, extending the layer to support cloud-edge continuum scenarios.

Definition text carried over unchanged from Rel-18, retaining the four-entity architecture including the Cloud Enabler Server.

Definition text carried over unchanged from Rel-19, maintaining the same four-entity architecture.

Defining Specifications

3GPP specifications that define or reference Edge Enabler Layer, 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