5G Core Network

Service-based architecture with network function virtualization.

1. Reimagining the Network's Brain: From 4G EPC to 5G Core

To understand the revolutionary nature of the 5G Core Network (5GC), we must first look back at its predecessor, the 4G Evolved Packet Core (EPC). The 4G EPC was a powerful system that successfully brought high-speed mobile broadband to the world. However, it was designed based on traditional telecommunication principles. It consisted of a series of large, specialized hardware boxes known as network nodes (like the MME, SGW, PGW), each with a specific, monolithic function. Communication between these nodes occurred over predefined, point-to-point interfaces, creating a relatively rigid, hierarchical structure.

This architecture was excellent for its intended purpose: delivering fast internet to smartphones. But the vision for 5G was far grander. It was not just about more speed (eMBB), but also about connecting billions of tiny devices (mMTC) and enabling mission-critical applications that demand near-instantaneous response times (URLLC). The rigid, hardware-centric model of the 4G EPC was not flexible, scalable, or programmable enough to support such diverse and demanding services simultaneously. A complete architectural rethink was required.

The 5G Core is that rethink. It is not an evolution; it is a revolution built from the ground up on the principles of modern IT, virtualization, and cloud computing. The 5GC replaces the physical boxes and rigid interfaces of the past with a flexible, software-driven framework known as the Service-Based Architecture (SBA). This fundamental shift is the single most important innovation in the 5G system, and it is the key that unlocks the full potential and transformative power of the fifth generation of mobile technology.

2. The Service-Based Architecture (SBA): The Heart of the 5G Core

The Service-Based Architecture is the core philosophical concept of the 5G network. It completely changes how the network is structured and how its different parts communicate. Instead of a network defined by physical equipment, the 5GC is a network defined by software services.

From Nodes and Interfaces to Functions and Services

In the 4G EPC, network functions were tightly coupled with their hardware nodes. For the MME to talk to the HSS, it used the standardized, point-to-point S6a interface. This created a complex web of interfaces that were difficult to manage and scale.

The SBA replaces this model with one inspired by modern web . The main building blocks of the 5G Core are not hardware boxes but software applications called Network Functions (NFs).

  • Network Functions as Services: Each NF (e.g., a function for session management, a function for authentication) is designed as a self-contained software module. Each NF acts as a "service producer," advertising its capabilities to the rest of the network through a standardized .
  • Service Consumption: Any other NF can act as a "service consumer." When it needs a specific capability, it does not need to know where that capability is physically located. It simply sends a service request over a common communication bus.

The Communication Bus and Service Discovery

All NFs are connected to a common message bus or service bus. This eliminates the rigid point-to-point links of the 4G EPC. But if all functions are just software talking on a common bus, how do they find each other?

This is the role of a critical new component: the NRF (Network Repository Function). The NRF acts as the network's service registry or "phone book."

  1. When a Network Function (for example, an instance of the AUSF for authentication) starts up, it registers its profile and the services it offers with the NRF.
  2. Later, when another NF (for example, the AMF) needs to authenticate a user, it sends a query to the NRF, asking, "Find me an available AUSF service."
  3. The NRF looks up its registry and returns the network address of one or more suitable AUSF instances to the AMF.
  4. The AMF can then directly communicate with the discovered AUSF to perform the authentication.

This dynamic service discovery mechanism makes the network incredibly agile. Operators can add new NF instances for scaling, perform software updates, or introduce entirely new services without reconfiguring a complex web of interfaces. Communication between NFs typically uses modern, lightweight web protocols like HTTP/2 over TCP and RESTful APIs, making the 5G core operate much more like a distributed cloud computing system than a traditional telecom network.

3. Embracing the Cloud: Key 5G Core Technologies

The Service-Based Architecture is enabled by a set of core technologies and design principles that are foundational to cloud computing.

Network Function Virtualization (NFV)

is the principle of separating network software from the underlying hardware. In the 5G Core, this means a Network Function is not a physical box. It is a piece of software (or a set of software components) that can be run on standard, generic server hardware, often referred to as Commercial-Off-The-Shelf (COTS) hardware.

This move to virtualization provides huge benefits for operators. Instead of being locked into buying expensive, proprietary hardware systems from specific telecom vendors, they can build their core network using the same type of servers found in modern IT data centers. This reduces capital expenditure, increases flexibility, and accelerates innovation. Furthermore, virtualized network functions can be deployed in software containers, orchestrated by platforms like Kubernetes, making them highly portable, scalable, and resilient.

Control and User Plane Separation (CUPS)

As discussed in the general 5G architecture, CUPS is a central design tenant of the 5GC. It ensures that the network's data-handling muscle (the User Plane Function or UPF) is completely decoupled from the network's brain (the control plane functions like AMF and SMF). This architectural separation enables one of 5G's most important capabilities: placing user plane functions strategically throughout the network. The UPF can be centralized in a large data center, or it can be pushed out to the edge of the network, very close to the radio towers. This distributed placement is the key to enabling edge computing and delivering the ultra-low latency required for URLLC services.

Stateless Functions and Unified Data Repository

A critical cloud-native design choice in the 5GC is that Network Functions are, wherever possible, stateless. This means the NF processing a user's request does not hold any long-term session information locally. For example, when an AMF processes a registration request, it does not permanently store the user's mobility state. Instead, it retrieves this information from a specialized, centralized data-storage function, processes the request, and then updates the information in that central repository.

This central data store is the UDR (Unified Data Repository). It is a robust database that holds session context, subscriber data, and policy information. This stateless approach makes the network incredibly resilient. If one software instance of an AMF fails, another one can instantly take over because it can retrieve the exact state of any user's session from the UDR and continue processing without interruption.

4. The Cast of Characters: Key 5G Core Network Functions

While there are many Network Functions defined in the 5G Core standard, a handful of them perform the most critical roles. They can be seen as the virtualized successors to the main nodes of the 4G EPC.

  • AMF (Access and Mobility Management Function): The AMF is the primary control point for device access to the network. It handles everything related to mobility and connection management, such as the initial registration of a device, authentication signaling, and tracking the device's location. It is the evolution of the mobility management aspects of the 4G MME.
  • SMF (Session Management Function): The SMF is responsible for managing the user's data sessions, known as PDU (Packet Data Unit) sessions. Its key tasks include allocating IP addresses for devices, selecting the User Plane Function (UPF) that will handle the traffic, and setting up the data bearers with the correct Quality of Service (QoS). It takes over the session management roles from the 4G MME, SGW-C, and PGW-C.
  • UPF (User Plane Function): The UPF is the data-plane workhorse of the 5GC. It is responsible for packet inspection, routing and forwarding traffic between the radio network and external data networks (like the internet), enforcing QoS policies, and collecting usage data for billing. It consolidates the user-plane roles of the 4G SGW and PGW into one more efficient and flexible function.
  • UDM (Unified Data Management): The UDM is the unified database for subscriber information, taking over the role of the 4G HSS. It holds subscriber profiles, generates authentication credentials, and manages user identifiers. It provides these services to other functions like the AMF and SMF.
  • AUSF (Authentication Server Function): This dedicated function manages the process of authenticating a device with the network, working closely with the UDM and AMF.
  • PCF (Policy Control Function): The PCF is the policy "brain" of the 5GC, evolving from the 4G PCRF. It creates and provides the policy rules that govern network behavior, QoS, and charging to the SMF and other functions.
  • NRF (Network Repository Function): The essential service discovery function that allows all the other NFs to find and communicate with each other in the Service-Based Architecture.
  • NSSF (Network Slice Selection Function): A new function specific to 5G that helps select the appropriate network slice for a user when they connect to the network, based on their subscription and the requested service.

5. Summary: A Foundation for the Future

The 5G Core Network represents a fundamental shift in how telecommunication networks are designed, built, and operated. By embracing principles from the cloud computing industry, it transforms the core network from a collection of rigid, specialized hardware into an agile, scalable, and programmable software platform.

Key architectural innovations include:

  • Service-Based Architecture (SBA): Decomposing the network into modular, reusable software services (Network Functions) that communicate via standard APIs.
  • Cloud-Native Design: Utilizing Network Function Virtualization (NFV) and stateless design principles to run network functions as software on common server hardware, enabling immense scalability and resilience.
  • Control and User Plane Separation (CUPS): Decoupling data forwarding from control signaling, which is the key enabler for flexible deployment and edge computing.
  • Dynamic Service Discovery: Using a Network Repository Function (NRF) to allow Network Functions to dynamically find and connect to each other, greatly simplifying network management and evolution.

This sophisticated and flexible architecture is what allows a single 5G network to simultaneously provide enhanced mobile broadband for consumers, ultra-reliable connections for industry and vehicles, and massive connectivity for the Internet of Things. It is not just the engine for 5G; it is the foundation upon which future decades of communication innovation will be built.

    5G Core Network | Teleinf Edu