Source Edge Enabler Server

Description

The Source Edge Enabler Server (S-EES) is a core component of the 3GPP Edge Computing Enabler Layer (ECEL) architecture defined from Release 17. It functions as a service discovery and access gateway for application clients (ACs) seeking to utilize edge computing resources. The S-EES is typically deployed within the operator's network or a trusted third-party domain. Its primary role is to act as a trusted intermediary that an AC first contacts. The AC provides the S-EES with a service description or identifier for the edge application it wishes to consume. The S-EES then consults with other ECEL entities, primarily the Edge Configuration Server (ECS), to discover the appropriate Edge Application Server (EAS) instances that can fulfill the request. This discovery process considers factors like the client's location, network conditions, and EAS capabilities to select an optimal endpoint. Once a suitable EAS is identified, the S-EES provides the AC with the necessary information, such as an IP address or FQDN, and often a secure access token, to establish a direct or proxied connection to the EAS. This architecture abstracts the complexity of the edge deployment from the application, enabling dynamic service discovery and seamless mobility as clients move between different edge service areas. The S-EES also plays a crucial role in security, enforcing authentication and authorization policies for ACs before revealing EAS details, thereby protecting the edge infrastructure from unauthorized access. It interfaces with the ECS using the En-1 reference point and with ACs via the En-2 reference point, as specified in TS 23.558.

Purpose & Motivation

The S-EES was created to address the challenges of service discovery and access in distributed edge computing environments. Prior to its standardization, accessing edge applications often required static configuration or proprietary discovery mechanisms, which were not scalable, secure, or interoperable across different operators and vendors. The proliferation of latency-sensitive and bandwidth-intensive applications, such as augmented reality, industrial automation, and video analytics, necessitated a standardized way to dynamically find and connect to the closest or most suitable compute instance. The S-EES solves this by providing a centralized, trusted point of contact for clients. It decouples the client application from the physical and logical topology of the edge network, enabling operators to deploy, manage, and scale their edge resources independently. This standardization, initiated in Release 17, was motivated by the need to foster an ecosystem of interoperable edge services, reduce integration complexity for application providers, and ensure secure and efficient utilization of edge computing infrastructure as a key enabler for 5G and beyond networks.

Key Features

• Acts as the primary discovery and access endpoint for application clients in the ECEL architecture
• Interworks with the Edge Configuration Server (ECS) to resolve service identifiers to specific Edge Application Server (EAS) instances
• Provides application clients with EAS connection information and secure access tokens
• Enables client mobility support by facilitating re-discovery of optimal EAS instances as location changes
• Enforces initial authentication and authorization of application clients before service exposure
• Abstracts network and edge topology details from the application layer

Evolution Across Releases

Defining Specifications