Edge Data Network

Description

The Edge Data Network (EDN) is a core architectural concept in 5G systems, defined by 3GPP, that refers to a local data network located at the edge of the mobile operator's network, in close proximity to the User Equipment (UE). It is not merely a physical location but a logical and service-based architecture that hosts application functions, cloud resources, and content caches. The EDN is typically collocated with or adjacent to the 5G Radio Access Network (RAN) nodes, such as the gNB, or with the User Plane Function (UPF) that provides the breakout point for local data traffic. This proximity drastically reduces the physical distance data must travel, minimizing latency and backhaul load.

Architecturally, the EDN is integrated into the 5G Core (5GC) via the Local Area Data Network (LADN) feature and the UPF. A key component is the Data Network (DN) in 5GC terminology, which represents any network providing data services (e.g., the internet, an IMS, or a private corporate network). An EDN is a specific type of DN that is 'local' or 'edge'. The UPF is configured to steer specific user data flows, identified by Data Network Name (DNN) and Network Slice Selection Assistance Information (NSSAI), to the EDN instead of routing them through the central core network to a distant DN. The EDN itself hosts Application Functions (AFs) that can interact with the 5GC via the Network Exposure Function (NEF) or directly with the Policy Control Function (PCF) to influence traffic routing and QoS policies.

How it works involves session establishment and traffic steering. When a UE requests a connection to an edge service (e.g., a factory robot control server), it uses a DNN associated with the EDN. The 5GC's Session Management Function (SMF) selects a UPF that is topologically close to the UE's location and has connectivity to the requested EDN. The UPF then becomes the anchor point, routing the UE's IP packets directly to the application servers within the EDN. This enables real-time interaction. Furthermore, the EDN can leverage network exposure for advanced capabilities like receiving notifications about UE mobility events (e.g., entering an edge service area) via the NEF, allowing applications to dynamically migrate or adapt their state.

Purpose & Motivation

The EDN was created to solve the fundamental limitations of centralized cloud computing for latency-sensitive and bandwidth-intensive applications. In traditional mobile networks, all data traffic traversed the RAN, backhaul, and core network to reach distant data centers, introducing significant latency (often 50-100ms). This is unacceptable for applications like autonomous vehicles, tactile internet, augmented reality, and real-time industrial control, which require latencies below 10ms. The EDN moves computation and storage to the network edge, directly addressing this latency bottleneck.

It also solves critical problems of network congestion and backhaul cost. By processing and storing content locally (e.g., caching popular video), the EDN reduces the volume of repetitive traffic that must be transported over long distances to the central core and the internet. This improves overall network efficiency and user experience, especially in crowded venues like stadiums. The motivation is deeply tied to the 5G vision of enabling vertical industries (e.g., manufacturing, healthcare) which require guaranteed low latency, high reliability, and data locality for privacy or regulatory reasons.

Historically, EDN concepts evolved from Cloud Radio Access Network (C-RAN) and Mobile Edge Computing (MEC), which were initially more RAN-centric. 3GPP's formalization of the EDN in Release 17 integrated these concepts natively into the 5G service-based architecture. It provides a standardized framework for operators to offer edge computing as a seamless network service, creating new revenue streams and enabling the ecosystem of ultra-reliable low-latency communication (URLLC) and enhanced mobile broadband (eMBB) applications that define 5G's transformative potential.

Key Features

• Hosts application servers and cloud resources in proximity to the user (at the RAN edge)
• Integrated with 5GC via UPF local breakout and LADN features
• Enables ultra-low latency (single-digit milliseconds) and high bandwidth for applications
• Supports traffic steering based on DNN and network slice
• Allows Application Functions (AFs) to interact with 5GC for QoS and policy control
• Reduces backhaul traffic and core network load through localized data processing and caching

Evolution Across Releases

Defining Specifications