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

Glossary term · Services

EEC

Edge Enabler Client

Services →

EEC is a functional entity within a UE or application server that interacts with the Edge Enabler Server to access Edge Computing services, discover edge applications, provision necessary information, and facilitate communication with network edge applications.

Introduced
Rel-15
Where
Services › Codecs
Specifications
26 specs
Also in
Core Network, Security, Radio Access Network
EEC Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Edge Enabler Client (EEC) is a key component in the 3GPP Edge Computing architecture, defined within the Edge Application Server (EAS) discovery and service provisioning framework. It resides either within the User Equipment (UE) or within an application server in the data network. The primary role of the EEC is to act as a client-side agent that enables the UE or application to utilize edge computing resources. It interacts with its counterpart, the Edge Enabler Server (EES), which is located within the edge data network or the operator's network. This interaction is standardized via the EDGE-1 and EDGE-2 reference points.

The EEC performs several critical functions. First, it is responsible for Edge Application Server (EAS) discovery. Based on the UE's location, application requirements, or network conditions, the EEC queries the EES to discover suitable EAS instances that can provide the desired edge application service. Second, the EEC handles service provisioning and registration. It registers the UE's capabilities and context with the EES/EAS and may provision necessary configuration or security parameters required to access the edge service. Third, it facilitates the setup of communication sessions between the UE (or client application) and the selected EAS, often involving traffic steering or routing rules to ensure data flows to the optimal edge location.

Architecturally, the EEC is part of the broader 3GPP Edge Computing ecosystem defined in TS 23.558. It works in conjunction with other entities like the EES, EAS, and the Edge Configuration Server (ECS). The EEC may leverage network exposure functions (NEF) and the 5G Core Network (5GC) to obtain network and location information. Its operation is crucial for realizing low-latency, high-bandwidth applications such as augmented reality, industrial automation, and vehicle-to-everything (V2X) by ensuring that client requests are served from the nearest and most appropriate edge computing node.

Purpose & Motivation

The Edge Enabler Client was created to address the challenge of efficiently connecting end-users and applications to distributed edge computing resources in 5G and beyond networks. Traditional cloud computing models, with centralized data centers, introduce significant latency that is unacceptable for real-time applications. Edge Computing aims to bring computation and storage closer to the user. However, a standardized mechanism was needed for clients to dynamically discover and connect to these distributed edge resources.

The EEC solves this problem by providing a standardized client function that abstracts the complexity of edge resource discovery and access. Without an EEC, each application would need to implement its own proprietary method to find edge servers, leading to fragmentation and inefficiency. The EEC, in conjunction with the EES, provides a unified, operator-managed framework. This allows for optimal placement of application sessions based on real-time network conditions, UE location, and application requirements. It enables network operators to offer Edge Computing as a consistent service, supporting multi-vendor ecosystems and fostering innovation in low-latency services.

What changed in its specifications

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

TS 23.255Rel-18 → Rel-19

Rel-19 added real-time flight path reporting, QoS-based flight route selection, no-transmit zone management, and supporting APIs/procedures for UAS applications.

Full comparison in TS 23.255 →
TS 23.548Rel-18 → Rel-19

Rel-19 adds Edge Computing Phase 3 to TS 23.548, including a clause on Local Offloading Management procedures. The clause covers policy handling in which the PCF dynamically generates the policy and the SMF retrieves it.

Full comparison in TS 23.548 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 7 changes
  • Corrections for AC and EEC initiated ACR scenario TS 23.558CR0003
  • EEC context relocation TS 23.558CR0008
  • ACR preconditions for EEC TS 23.558CR0036
  • 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

+ 1 more changes

Rel-18 29 changes
  • EEC triggering service TS 23.558CR0138
  • New AC-EEC procedure to invoke UE ID request TS 23.558CR0155
  • Updating UE Identifier API procedure to enable EEC invoke UE ID request for NATed IP address TS 23.558CR0156
  • EEC sharing UE Mobility requirement TS 23.558CR0207
  • Explaining usage of EES’s capability exposure by EEC TS 23.558CR0230
  • EEC selected ACR scenario for EAS bundles TS 23.558CR0254

+ 23 more changes

Rel-19 7 changes
  • Remove EN on EEC triggering service parameter TS 23.558CR0607
  • AC and EEC interaction for ACR TS 23.558CR0630
  • Handling of EAS instantiation completion time at EEC TS 23.558CR0686
  • Sharing port information to receive the EEC triggers. TS 24.558CR0113
  • Functionalities of EEC update TS 23.558CR0604
  • EN on EEC-provided information verification and trustfulness TS 23.558CR0707

+ 1 more changes

Defining Specifications

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

SpecificationTitleRelease
TS 22.870 vk00 Study on 6G Use Cases and Service Requirements Rel-20 read
TS 23.255 vk10 UAS Application Enabler Architecture Rel-20 read
TS 23.548 vk00 5G Edge Computing Stage 2 Architecture Rel-20 read
TS 23.558 vk30 Enabling Edge Applications Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TR 23.758 vh00 Study on Edge Application Architecture Rel-17 read
TS 23.947 vk10 Developer Guide to CAPIF, EDGEAPP and SEAL Rel-20 read
TR 23.958 vj00 EDGEAPP alignment with ETSI MEC and GSMA OP Rel-19 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.558 vk00 Edge Application Enabler Server APIs Stage 3 Rel-20 read
TS 26.115 vj00 3GPP TS 26115: Echo Control Requirements Rel-19 read
TS 26.131 vj00 Terminal Acoustic Performance Requirements Rel-19 read
TS 26.132 vk00 Terminal Acoustic Test Methods for Telephony Rel-20 read
TS 26.506 vk00 5G Real-Time Media Communication Architecture Rel-20 read
TS 26.510 vj20 5G Media Streaming and Real-Time Communication APIs Rel-19 read
TR 26.803 vh00 5G Media Streaming Extensions for Edge Processing Rel-17 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TS 26.941 vk00 5GMS Network Slicing Study Rel-20 read
TS 28.879 vj10 OAM for Service Management Exposure Study Rel-19 read
TS 29.558 vk00 Edge Application Enablement APIs Rel-20 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read
TS 33.749 vj00 Study on security aspects of edge computing enhancement Rel-19 read
TR 33.839 vh10 Edge Computing Security Study for 5G Core Rel-17 read
TS 36.401 vj00 E-UTRAN Overall Architecture Description Rel-19 read
TS 43.050 vj00 GSM Transmission Planning for Speech Services Rel-19 read