Description
The Edge Application Server Discovery Function (EASDF) is a specialized network function introduced in 3GPP Release 17 to enhance edge computing in 5G systems. Its primary role is to facilitate the discovery and selection of Edge Application Servers (EAS) by User Equipment (UE) or other network functions. The EASDF acts as a DNS (Domain Name System) server or proxy that is aware of the network topology, UE location, and EAS deployment locations. When a UE attempts to access an edge application via a domain name, the EASDF intercepts the DNS query and returns the IP address of the most suitable EAS instance, typically the one closest to the UE to minimize latency.
Architecturally, the EASDF is part of the 5G core network's user plane or can be deployed as a separate function interacting with the control plane. It integrates with the Policy Control Function (PCF) and the Network Exposure Function (NEF) to obtain policies and contextual information that influence EAS selection. Key components include the DNS resolution logic, a database or interface to EAS availability and location information, and policy enforcement mechanisms. The EASDF works by receiving a DNS query from the UE (often routed to it via UE Route Selection Policy (URSP) or local breakout configurations). It then applies selection criteria such as UE current location, EAS load, network conditions, and subscriber profiles to choose the optimal EAS. The resolved IP address is returned to the UE, which then establishes a direct connection to the selected EAS for application data transfer.
How it operates involves close coordination with other 5G systems. The EASDF may be provisioned with EAS information via management systems or dynamically through interfaces with the Network Repository Function (NRF). In operation, it enables dynamic and efficient traffic steering to edge resources. For example, for a latency-sensitive gaming application, the EASDF ensures the UE connects to a game server in a nearby edge data center rather than a distant central cloud. Its role is critical in multi-edge environments where multiple EAS instances are deployed across different geographical points of presence, as it provides the intelligence to direct users to the best instance based on real-time network and service conditions.
Purpose & Motivation
The EASDF was created to solve the challenge of efficiently discovering and connecting to the most appropriate Edge Application Server in a distributed edge computing environment. Before its introduction, edge discovery mechanisms were often proprietary, lacked standardization, or relied on basic DNS which is not network-aware. This led to suboptimal routing where a UE might be directed to a distant EAS despite a closer one being available, negating the latency benefits of edge computing. The proliferation of edge deployments in 5G, driven by applications like autonomous vehicles, industrial IoT, and augmented reality, necessitated a standardized, network-integrated discovery solution.
The primary problem EASDF addresses is the intelligent, policy-driven selection of edge resources. It ensures that edge computing delivers on its promise of low latency and high bandwidth by dynamically directing users to the optimal EAS based on current network conditions. This is especially important for mobile users, as their location changes and the best EAS selection may change accordingly. EASDF also solves the issue of scalability and management in large-scale edge deployments, providing a centralized discovery point that can be updated with new EAS instances and their capabilities.
Historically, the motivation stems from 3GPP's work on edge computing architecture (EDGEAPP) in earlier releases, which defined the EAS but lacked a standardized discovery mechanism. EASDF fills this gap, completing the edge computing framework by adding a crucial control element. It enables operators to offer edge computing as a seamless service, where applications can be deployed at the edge without requiring end-users or application providers to manage complex connectivity details. This standardization encourages ecosystem growth, allowing application developers to rely on a consistent method for edge service discovery across different operator networks.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (21 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the EASDF was formally introduced with key functional clarifications and procedural updates. These included the definition of the N88a reference point to the SMF, detailed procedures for EAS discovery with dynamic PSA distribution, and specific rules for DNS message handling. The release also explicitly clarified deployment constraints, such as stating that a NAT between the EASDF and a PSA UPF is not supported.
- Correction related to uniqueness of Update related to a buffered DNS message in EASDF TS 23.548CR0001
- Not all EC scenarios requires EASDF TS 23.548CR0005
- Updates on EAS Discovery Procedure with EASDF TS 23.548CR0017
- Alignment of EASDF functional description TS 23.548CR0039
- Update of EAS discovery procedure and BaselineDNSPattern management in EASDF TS 23.548CR0047
- On NAT between PSA UPF and EASDF TS 23.548CR0048
+ 2 more changes
In Release 18, the EASDF was enhanced to support the Home Routed SBO (HR-SBO) roaming scenario, introducing a specific EAS discovery procedure using an IP replacement mechanism with the V-EASDF. The updates also defined N6 tunneling between the V-UPF and V-EASDF to handle PDU sessions with overlapping IP addresses, and clarified DNS traffic routing between the UE and V-EASDF for networks with identical IP address ranges. Furthermore, the release included security provisions and functional description updates for the EAS discovery procedure via the (V-)EASDF.
- EAS Re-discovery Procedure with EASDF in HR roaming scenario TS 23.548CR0073
- The EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO TS 23.548CR0088
- EASDF functional description update TS 23.548CR0105
- EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO TS 29.244CR0823
- N6 tunneling between V-UPF and V-EASDF for HR-SBO PDU sessions with overlapping IP addresses TS 29.244CR0847
- DNS traffic routing between UE and V-EASDF where multiple DNN networks with the same IP address range are deployed TS 29.556CR0030
+ 6 more changes
In Release 19, the key addition for the EASDF was the formal introduction of the N88a reference point between the I-SMF and the EASDF to support the Local Offloading Management scenario. This new interface enables the I-SMF, which is inserted into a PDU Session with UL-CL/BP, to select and configure the EASDF. This enhancement facilitates procedures like EAS discovery with Dynamic PSA distribution, where the EASDF can influence DNS queries to trigger PDU Session re-anchoring to a more optimal edge location.
- N88a reference point between I-SMF and EASDF TS 29.556CR0048
Explore further
Broader topics and technologies where EASDF plays a role.
Defining Specifications
3GPP specifications that define or reference EASDF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.548 vj50 | 5G System Edge Computing Enhancements | Rel-19 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TR 26.803 vh00 | 5G Media Streaming Extensions for Edge Processing | Rel-17 |
| TS 29.244 vj40 | PFCP Specification for Control/User Plane Separation | Rel-19 |
| TS 29.556 vj40 | EASDF Service Based Interface Protocol | Rel-19 |
| TR 33.739 vi10 | Study on security enhancement of support for | Rel-18 |