5G Core Network

Description

The 5G Core Network (5GCN) is the fundamental architectural framework for the core network in 5G systems, as standardized by 3GPP starting with Release 15. It represents a radical departure from previous Evolved Packet Core (EPC) architectures by adopting a fully cloud-native, service-based architecture (SBA). This means network functions are implemented as modular, reusable software services that communicate over standardized HTTP/2-based interfaces (e.g., N1, N2, N4). The architecture cleanly separates the user plane (UPF - User Plane Function) from the control plane, allowing for independent scaling, deployment, and optimization of data forwarding and signaling logic. This separation is a cornerstone for supporting diverse service requirements, from high-bandwidth video streaming to mission-critical industrial automation.

At its heart, the 5GCN operates by establishing and managing Protocol Data Unit (PDU) Sessions for user equipment (UE). The control plane, orchestrated by functions like the Access and Mobility Management Function (AMF) and Session Management Function (SMF), handles registration, authentication, mobility, and session establishment. The AMF is the single entry point for all UE control signaling, terminating the N1 and N2 interfaces. The SMF is responsible for session management, including IP address allocation, selection of the UPF, and configuring traffic steering and policy enforcement rules via the N4 interface to the UPF. The UPF then acts as the intelligent data router, performing packet routing and forwarding, packet inspection, QoS handling, and traffic usage reporting.

Key architectural components include the Network Repository Function (NRF), which enables service discovery, allowing network functions to find and communicate with each other dynamically. The Unified Data Management (UDM) function manages subscriber data and generates authentication credentials. The Policy Control Function (PCF) provides policy rules to control plane functions. The Authentication Server Function (AUSF) performs authentication with the UE. Together, these functions enable advanced capabilities like network slicing, where multiple logical, isolated networks are created on a common physical infrastructure, each tailored for specific service needs (e.g., a slice for enhanced mobile broadband, another for massive IoT). The 5GCN's role is to provide a flexible, scalable, and programmable foundation that can efficiently support the expansive set of 5G use cases defined by ITU-R IMT-2020.

Purpose & Motivation

The 5GCN was created to address the limitations of the 4G Evolved Packet Core (EPC), which was primarily designed for mobile broadband. The EPC's monolithic, node-based architecture struggled with the scalability, flexibility, and diverse performance requirements envisioned for 5G, such as ultra-low latency, massive device connectivity, and network slicing. The primary motivation was to build a core network that is inherently cloud-native, enabling operators to deploy network functions as software on commercial off-the-shelf hardware, leverage network function virtualization (NFV), and adopt modern DevOps practices for rapid service innovation and deployment.

Historically, each generation of mobile networks introduced a new core network (e.g., GSM's circuit-switched core, UMTS's core, 4G's EPC). The shift to 5G required a core that could be more than just a faster pipe for smartphones. It needed to be a versatile service platform capable of supporting vertical industries like automotive, manufacturing, and healthcare. The 5GCN solves this by its service-based architecture, which decouples software from hardware, and its clear separation of user and control planes, which allows the data plane to be deployed at the network edge to minimize latency. It directly addresses the problem of network rigidity by enabling network slicing, providing dedicated virtual networks with specific characteristics, and supporting a wider range of authentication methods and session types beyond simple IP connectivity.

Key Features

• Cloud-native, Service-Based Architecture (SBA) with HTTP/2 interfaces
• Control and User Plane Separation (CUPS) for independent scaling
• Native support for Network Slicing to create logical, isolated networks
• Unified policy framework for session and service quality management
• Support for concurrent access to local and central data networks
• Integration of common API framework for exposure to third-party applications

Evolution Across Releases

Defining Specifications