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

Glossary term · Services

Edge Application Server

Edge Application Server (EAS)

Services →

Edge Application Server is an application server resident in the Edge Hosting Environment, deployed close to users at the network edge to deliver low-latency, high-bandwidth services.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
4 specs
Edge Application Server Description Purpose What changed Neighbours Specifications

Description

The Edge Application Server (EAS) is an application server that resides in the Edge Hosting Environment — the compute and storage infrastructure deployed at the edge of the mobile network, close to the user plane access point. It is defined in the 3GPP edge computing specifications 23.548 (Edge Computing), 23.748 (Edge Computing – stage 2), 23.758 (Edge Computing – stage 3) and the security specification 33.739. The EAS is the actual application endpoint that user equipment (UE) connects to when using an edge service; it runs the application logic (e.g., video streaming, AR/VR rendering, gaming, industrial control) and is hosted in the Edge Data Network (EDN) operated by an Edge Computing Service Provider (ECSP).

In the 3GPP edge computing architecture, the EAS is discovered and selected through the Edge Enabler Layer. The Edge Configuration Server (ECS) provides the UE with information about available Edge Enabler Servers (EES), and the EES provides Edge Application Server discovery information — for example, the address or identifier of an EAS suitable for the UE's location and application. The UE's Edge Enabler Client (EEC) uses this information to connect to the selected EAS. The EAS itself is registered with the EES, which maintains information about the EAS's availability, capabilities and the service area (e.g., DNAI — Data Network Access Identifier) in which it is deployed.

The EAS is typically deployed in a data centre at the edge of the operator's network, connected via a local Data Network (DN) and reachable through a User Plane Function (UPF) located close to the radio access network. This placement reduces the round-trip latency between the UE and the application, offloads traffic from the core network, and can improve throughput. The EAS may be instantiated, migrated or terminated dynamically as the UE moves, a process known as Edge Application Server relocation/re-anchoring, coordinated by the EES and the network (e.g., via the SMF/UPF and the Edge Application Server Discovery Function, EASDF).

The EAS is distinct from the Edge Enabler Server (EES) and Edge Configuration Server (ECS): the EES and ECS provide the enabling functions (discovery, registration, configuration) for edge services, while the EAS is the application server itself. The EAS may be operated by the ECSP or by a third-party Application Service Provider (ASP). Security for the EAS, including authentication and authorization between the EEC and EAS, is addressed in 33.739.

The EAS concept is central to 5G edge computing: it is the concrete realization of the promise that applications can run close to users. Its lifecycle — deployment, discovery, selection, relocation and termination — is managed through the edge computing architecture, and its management can be orchestrated via the ECSP Management System. The term was introduced in Rel-17 and carried forward through Rel-20.

Purpose & Motivation

The Edge Application Server concept exists to make low-latency, high-bandwidth applications feasible over mobile networks. In a traditional centralized architecture, application servers sit in the internet or central data centres, so user traffic must traverse the core network and back, adding latency and consuming backhaul capacity. For latency-sensitive services (cloud gaming, AR/VR, V2X, industrial automation) and bandwidth-heavy services (video), this is a fundamental limitation.

By defining the EAS as an application server resident in the Edge Hosting Environment, 3GPP provides a standardized architectural anchor for applications deployed at the network edge. This allows application providers to place their servers close to the UPF and RAN, reducing latency and improving user experience, while the standardized edge computing architecture (ECS, EES, EEC) provides the discovery and selection mechanisms needed for UEs to find the right EAS as they move.

The EAS also enables new business models: ECSPs can host third-party applications at the edge, and ASPs can deploy their applications in operator edge environments using standardized interfaces. Introduced in Rel-17 as part of the 3GPP edge computing work, the EAS term provides the common vocabulary needed for multi-vendor, multi-operator edge ecosystems, and it continues to evolve through Rel-20.

What changed in its specifications

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

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

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

The Edge Application Server was introduced as part of the 3GPP edge computing architecture (23.548, 23.748, 23.758, 33.739), defined as an Application Server resident in the Edge Hosting Environment, with discovery and selection via the Edge Enabler Layer.

The definition text carried over unchanged from Rel-17; the EAS concept continued with the same scope in the edge computing specifications.

The definition text carried over unchanged from Rel-17; no revision to the EAS description in this release.

The definition text carried over unchanged from Rel-17; the EAS term remains stable as edge computing continues to evolve.

Defining Specifications

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

SpecificationTitleRelease
TS 23.548 vk00 5G Edge Computing Stage 2 Architecture Rel-20 read
TR 23.748 vh00 Edge Computing Enhancement Study for 5GC Rel-17 read
TR 23.758 vh00 Study on Edge Application Architecture Rel-17 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read