Edge Enabler Server Identification

Description

The Edge Enabler Server Identification (EESID) is a critical parameter within the 3GPP Edge Computing architecture that provides a globally or locally unique label for an instance of an Edge Enablement Server. It functions as a network address or name for the EES entity itself, distinct from the services it hosts. The EESID is used in various signaling messages and service operations to identify the source or target EES. For example, when an Edge Application Server (EAS) registers with an EES, the registration is associated with that EES's EESID. Similarly, when an Edge Configuration Server (ECS) provides configuration to a UE, it may include the EESID of the EES the UE should contact for service discovery.

The structure and format of the EESID are defined to ensure it can be routable within the edge ecosystem. It typically follows a hierarchical naming convention that may include domains to assist in resolution. In service discovery requests from an Edge Application Client (EAC), the EESID can be used to specify a preferred or pre-configured EES. The network, based on policies and the UE's location, may also select an appropriate EES and provide its EESID to the client. During mobility events, if a UE moves to an area served by a different EES, the new EESID might be provided to the UE to ensure continuity of edge service discovery.

From a protocol perspective, the EESID is carried in HTTP headers or within the JSON payloads of service-based interface messages (e.g., in the Ees_Service API defined in TS 29.558). Its presence allows for sophisticated network behaviors, such as EES selection based on load balancing, geographical affinity, or specific service-level agreements. It is a foundational element that enables the scalability of the edge architecture, allowing for the deployment of multiple EES instances without conflict and ensuring that service registrations and discoveries are correctly scoped.

Purpose & Motivation

The EESID was defined to solve the addressing and identification problem in a multi-vendor, multi-domain edge computing environment. As edge deployments scale, an operator or a federation of operators will deploy numerous EES instances. Without a standardized, unique identifier, it would be impossible to reliably direct an EAS registration to a specific EES or to guide a UE to the correct EES for service discovery. This identifier prevents ambiguity and ensures the integrity of the service registry.

It addresses limitations of using simple IP addresses or FQDNs alone by providing a logical identifier that is stable and can be mapped to different physical or network locations through resolution mechanisms. This is particularly important for mobility and redundancy; if an EES fails, its functions can be taken over by a backup instance with a different network address but potentially a related logical identity, and clients configured with an EESID can be redirected. The EESID also enables administrative and operational segregation, allowing different EESs (e.g., one for public edge services and one for a private enterprise edge) to be clearly distinguished within the same network.

In essence, the EESID provides the necessary handle for the network to manage the lifecycle and accessibility of the Edge Enablement Server, which is the central nervous system for edge service orchestration. It is a key component that makes the edge computing architecture robust, manageable, and scalable.

Key Features

• Globally or locally unique identifier for an EES instance
• Used for routing service registration and discovery requests
• Enables EES selection and load balancing by the network
• Supports UE mobility and EES re-selection procedures
• Carried in service-based interface (SBI) messages
• Facilitates multi-EES deployments and administrative domains

Evolution Across Releases

Defining Specifications