ECSP

Edge Computing Service Provider

Services →
Introduced in Rel-17 Also in: Management, Core Network

ECSP is an entity that provides edge computing capabilities and services within the 3GPP framework to enable low-latency applications by hosting them closer to the user.

Category
Services
Introduced
Rel-17
Where
Services
Also touches
2 segments
Specifications
14 specs
ECSP Description Purpose Detected Changes Specifications

Description

The Edge Computing Service Provider (ECSP) is a functional role defined within 3GPP's architecture for enabling edge computing. It operates the Edge Application Server (EAS) and the Edge Enabler Server (EES), which are key components in the Edge Computing (EC) architecture. The ECSP is responsible for deploying and managing applications at the network edge, providing the necessary compute, storage, and networking resources. It interfaces with the 3GPP network, specifically the 5G Core Network (5GC), to facilitate service discovery, traffic steering, and session continuity for edge-enabled User Equipment (UE). The ECSP's role is distinct from the Mobile Network Operator (MNO); it can be a third-party service provider leveraging the MNO's connectivity to offer enhanced, low-latency services.

The ECSP architecture is centered around the Edge Enabler Client (EEC) in the UE and the Edge Enabler Server (EES) in the network. The EES, managed by the ECSP, acts as a central point for edge service registration and discovery. When a UE requires an edge service, its EEC queries the EES (via the 3GPP network) to discover the appropriate Edge Application Server (EAS). The EAS, also hosted by the ECSP, is where the actual application logic resides. The 3GPP network, through mechanisms like Local Area Data Network (LADN) and User Plane Function (UPF) selection, ensures that the UE's data traffic is routed to the optimal EAS instance, minimizing latency and backhaul load.

Key protocols and interfaces for the ECSP are defined in specifications such as TS 23.558. The EC-3 (EEC-EES) and EC-5 (EES-EAS) reference points are crucial for service enablement. The ECSP interacts with the 5GC via the NEF (Network Exposure Function) for accessing network capabilities and with the PCF (Policy Control Function) for applying edge-specific policies. Security is paramount; the ECSP must authenticate and authorize UEs and ensure secure communication between all edge entities. The ECSP model supports multi-access edge computing (MEC) principles, allowing applications to leverage both 3GPP and non-3GPP access networks.

Purpose & Motivation

The ECSP concept was introduced to formalize and standardize the role of third-party edge service providers within the 5G ecosystem. Prior to its definition, edge computing deployments were often proprietary or tightly coupled with a single mobile operator, limiting innovation and service portability. The rise of latency-sensitive applications like autonomous vehicles, tactile internet, and immersive media created a demand for a standardized, interoperable edge framework that could decouple service provision from network connectivity.

The ECSP model addresses the problem of how to efficiently deploy and discover applications at the network edge in a multi-vendor, multi-stakeholder environment. It solves the challenge of enabling a UE to dynamically find and connect to the closest or most suitable instance of an application server, which is essential for maintaining low latency and efficient resource utilization. By defining clear functional roles and interfaces, 3GPP allows Mobile Network Operators (MNOs) to offer their network edge as a platform to external ECSPs, fostering a richer service ecosystem and new revenue streams beyond traditional connectivity.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 2 changes

In Release 17, the specification formally introduced the "Edge Computing Service Provider (ECSP)" terminology and its management system, enabling the provisioning of ECS configuration information per individual ECSP. This established the framework for partner ECSP relationships, allowing for service provisioning information retrieval between partner ECSs over the EDGE-10 interface. These enhancements support dynamic EAS instantiation triggering and service authorization between ECSPs, such as when a subscriber of one ECSP obtains edge services from a partner ECSP's ECS, EES, and EAS.

  • Support of provisioning ECS configuration info per ECSP TS 24.501CR4431
  • Add the terminologies for PLMN and ECSP management systems TS 28.538CR0004
Rel-18 6 changes

In Release 18, key enhancements for the Edge Computing Service Provider (ECSP) function included improved handling and authorization of a desired ECSP identifier, aligning the ECSP management system terminology with GSMA Operator Platform profiles. The release also introduced the capability for an ECS to provide a list of supported PLMNs with ECSP information within ECS address information, facilitating better service provisioning for partner ECSPs in roaming and federation scenarios.

  • Correct desired ECSP id handling TS 23.558CR0421
  • Update on Alignment of EDGEAPP and GSMA OP for ECSP Management System TS 23.958CR0002
  • Add list of supported PLMNs with ECSP information to the ECS address information TS 24.501CR6345
  • Handling of desired ECSP identifier(s) TS 24.558CR0066
  • EES is provided by ECSP and is not necessarily in PLMN domain. TS 23.558CR0407
  • Alignment of terminologies for the ECSP management system TS 23.558CR0408
Rel-19 7 changes

In Release 19, key enhancements for the Edge Computing Service Provider (ECSP) function introduced formalized support for service continuity in Edge Network Services via a leading ECSP and enabled the use of a common Edge Application Server (EAS) within a partner ECSP's environment. These changes build upon the existing service provisioning information retrieval procedure for obtaining a partner ECSP's Edge Data Network information and the mechanisms for ECSPs to authorize service usage. The updates also involved corrections and refinements to the encoding of parameters related to ECSP information exchanged over interfaces like EDGE-10.

  • Service continuity in ENS via leading ECSP TS 23.558CR0541
  • Common EAS in partner ECSP TS 23.558CR0528
  • Service continuity in ENS via leading ECSP TS 23.558CR0586
  • Service continuity in ENS via leading ECSP TS 23.558CR0610
  • Eecs_ECSServiceProvisioning – Common EAS in partner ECSP TS 29.558CR0218
  • Correction to Common EAS in partner ECSP TS 23.558CR0716

+ 1 more changes

Explore further

Broader topics and technologies where ECSP plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.558 vk00 Architecture for Edge Applications Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TR 23.758 vh00 Study on Edge Application Architecture Rel-17
TR 23.958 vj00 EDGEAPP alignment with ETSI MEC and GSMA OP Rel-19
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 24.558 vj50 Edge Enabler APIs Stage 3 Rel-19
TS 28.538 vj40 Edge Computing Management (ECM) Rel-19
TR 28.815 vh00 Charging Study for Edge Computing Rel-17
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18
TR 28.844 vi00 Technical Report on Charging Aspects of Satellite in 5GS Rel-18
TS 29.558 vj40 Enabling Edge Applications Rel-19
TS 32.257 vj00 Edge Computing Charging Management Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TR 33.739 vi10 Study on security enhancement of support for Rel-18
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.