Skip to main content
  1. Index/

Edge Computing

Table of Contents

Edge computing in telecommunications places compute, storage, and application execution close to users and devices — at cell sites, regional points of presence, or on-prem enterprise locations — rather than only in distant hyperscale data centres. The goal is to reduce end-to-end latency, limit backhaul load, satisfy data residency, and enable real-time applications (AR/VR, industrial control, V2X, video analytics) that are impractical with 50–100 ms round trips to central clouds. In 5G, edge is tightly coupled to the user plane: a local UPF on N6 breakout forwards traffic to an edge data network (DN) hosting MEC applications without hairpinning through the operator’s core hub.

ETSI Multi-access Edge Computing (MEC) defines a reference architecture: MEC platform (virtualisation, app lifecycle), MEC orchestrator, MEC app APIs (MxP), and exposure of RAN information (radio conditions, location) to applications via standardised services. 3GPP complements this with NEF exposure, LADN (Local Area Data Network), and ULCL / multi-homed PDU sessions for selective traffic steering. Hyperscalers (AWS Wavelength, Azure Edge Zones, Google Distributed Cloud Edge) and telco edge (Ericsson Edge, Nokia MX Industrial Edge, Vapor IO, etc.) offer Kubernetes or VM footprints at the edge, often co-located with vRAN or UPF on M-CORD / O-RAN-style infrastructure.

LayerRole
Device / UEGenerates traffic; may run light edge (e.g. AI on device)
RAN + local UPFAnchors session; steers flows to local DN
MEC platformHosts apps, provides RAN exposure APIs
Central cloudTraining, orchestration, non-latency-sensitive workloads

Private 5G, Open RAN, and cloud-native 5GC accelerate edge adoption by making UPF and CU/DU cloud-packaged and geographically distributable. Operational challenges include fragmented footprints (many small sites), application portability, security zoning between tenant workloads, and consistent observability across edge and core. Edge is not universally required — many 5G services still use centralised UPF — but it is essential for advertised ultra-low latency and on-site industrial scenarios.

Additional Information
#

Related

5G Core (5GC)

The 5G Core (5GC) is the packet core network architecture defined by 3GPP from Release 15 onward as the control and user-plane backbone of standalone 5G deployments. It replaces the Evolved Packet Core (EPC) of 4G LTE not through incremental evolution but through a deliberate architectural break: where the EPC was built around monolithic, hardware-bound network functions interconnected by point-to-point interfaces, the 5GC is designed from the ground up around a Service-Based Architecture (SBA) — every network function exposes its capabilities as a set of services over a common HTTP/2 bus (the Service-Based Interface, SBI), and any authorised consumer NF can discover and invoke those services through the NRF (Network Repository Function) without bilateral peering agreements or proprietary protocols. This shift reflects two structural requirements of 5G that EPC could not satisfy: network slicing — the ability to run logically independent end-to-end networks (each with its own QoS, isolation, and lifecycle) on shared physical infrastructure — and cloud-native deployment, where NFs run as containerised microservices on commodity compute, can be horizontally scaled, and are managed by standard Kubernetes-compatible orchestration rather than vendor-specific element managers. The 5GC also enforces a hard separation between Control Plane (CP) and User Plane (UP) — the CUPS principle inherited from 3GPP Release 14 and fully operationalised here — so that the UPF (User Plane Function) handling packet forwarding, QoS enforcement, and traffic anchoring can be distributed to the edge independently of the control logic, enabling ultra-low-latency and MEC scenarios without redesigning the control plane. The architecture is access-agnostic: the same 5GC serves NR (New Radio), eLTE, Wi-Fi (untrusted/trusted non-3GPP access), and fixed-wireless access through a unified N2/N3 reference point toward the access network and a common UE context model in the AMF.

Private 5G

Private 5G (also non-public 5G, dedicated 5G, or campus/industrial 5G) denotes 3GPP-conformant 5G systems operated for a defined organisation or site — factory, port, mine, hospital, stadium, or utility — rather than as a nationwide public mobile service. 3GPP Release 16+ formalised Non-Public Networks (NPN) with two principal models: Standalone NPN (SNPN) — an isolated PLMN (dedicated MCC/MNC or PLMN ID) with its own 5GC and NG-RAN; and Public Network Integrated NPN (PNI-NPN) — a slice or dedicated DNN on a public operator’s 5G with contractual isolation. Private 5G delivers URLLC-capable connectivity, local breakout (traffic stays on-site via local UPF), deterministic QoS, and control over upgrades and security policies — advantages over Wi-Fi 6/7 in mobility, scheduling, and industrial TSN integration scenarios, at higher cost and regulatory complexity.

AI-RAN Alliance

The AI-RAN Alliance is a global industry consortium, launched at MWC Barcelona in February 2024 and governed by a Technical Steering Committee (TSC), whose mission is to accelerate the integration of artificial intelligence into Radio Access Networks and to define what an AI-native RAN looks like in practice for 5G Advanced and 6G. The alliance deliberately positions itself as neither a marketing organisation nor a demo factory: it pursues pioneering, pre-competitive work — reference architectures, blueprints, and credible benchmarking — without getting mired in formal standards processes or IP negotiations. Its work spans three complementary objectives — AI-for-RAN (using AI/ML to improve RAN performance and efficiency), AI-and-RAN (co-locating RAN and AI workloads on shared accelerated infrastructure), and AI-on-RAN (hosting tenant-facing AI applications at the network edge for differentiated, monetisable connectivity). Founding members include Ericsson, Nokia, NVIDIA, T-Mobile, SoftBank, Samsung, AWS, Microsoft, and Arm; membership grew from a handful at launch to 130+ organisations by MWC 2026, spanning operators, NEPs, hyperscalers, silicon vendors, universities, and government research bodies across more than 17 countries.