5G SA vs 5G NSA: Key Differences, Use Cases, and What Changes in Your Core Network

5G NSA (Non-Standalone) uses an existing 4G core alongside new 5G radio — faster to deploy, limited to enhanced mobile broadband. 5G SA (Standalone) builds a cloud-native 5G core from scratch — enabling network slicing, ultra-reliable low-latency communications (URLLC), and advanced monetisation. The choice of SA over NSA is not only a radio decision; it changes the operator’s requirements for Authentication, Authorization, and Accounting (AAA), policy control, subscriber data management, and Business Support Systems (BSS).

For mobile network operators (MNOs), the question is no longer whether to move to 5G SA. It is when, and how to stage the changes to the core network that come with it.

What Is 5G SA Architecture and What Does It Enable?

5G Standalone (SA) is a complete, end-to-end 5G architecture defined by 3GPP. It introduces a new radio plus a new 5G Core (5GC) built on Service-Based Architecture (SBA) and cloud-native principles, replacing the Evolved Packet Core (EPC) entirely. In a Standalone deployment, the 5G radio talks directly to the 5G core — control signalling does not depend on the 4G network at any point.

Architecturally, the 5G SA core consists of network functions communicating over service-based interfaces — Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Unified Data Management (UDM), Authentication Server Function (AUSF), and the Network Repository Function (NRF), among others. Each is independently deployable, scalable, and upgradeable.

This is what 5G SA enables that NSA cannot:

• Network slicing. End-to-end logical networks tailored per use case — enhanced Mobile Broadband (eMBB) for consumer data, Ultra-Reliable Low-Latency Communications (URLLC) for industrial and automotive, massive Machine-Type Communications (mMTC) for Internet of Things (IoT) at scale, and dedicated slices for vehicle-to-everything (V2X), private enterprise 5G, and aerial UE (drones).

• URLLC use cases. Latency targets in single-digit milliseconds with reliability guarantees — remote control of critical infrastructure, autonomous driving, advanced industrial automation, robotics, and drone coordination.

• mMTC at scale. Massive IoT device density with power-efficient device support.

• B2B2X monetisation. Per-slice charging, enterprise SLAs, and wholesale models that depend on the 5G core’s policy and charging architecture.

• Edge-native services. SBA makes it practical to deploy network functions at the edge for low-latency services.

What Is 5G NSA Architecture and When Does It Make Sense?

5G Non-Standalone (NSA) is the migration architecture most operators used to launch 5G first. It pairs new 5G radio with the existing 4G EPC. The 5G radio handles the user plane and high data rates; the 4G core handles control signalling, mobility, and most network functions.

Architecturally, NSA includes a new 5G New Radio (NR) deployed alongside the existing 4G LTE radio, supported by the existing 4G Core or EPC. This is a Dual Connectivity model — devices connect to both the 4G anchor and the 5G NR simultaneously, with the 4G network providing the control plane and the 5G radio adding data-plane capacity.

NSA makes sense when:

• The operator wants to launch 5G eMBB quickly and capture marketing benefit without rebuilding the core.

• Existing 4G capital investment must be amortised before committing to a 5G core programme.

• The operator’s near-term use cases are consumer broadband-led — video streaming, augmented reality (AR), virtual reality (VR), immersive media — which NSA delivers well.

• Enterprise 5G, network slicing, and URLLC are not yet on the near-term roadmap.

What NSA cannot do: network slicing, URLLC, true mMTC scale, or B2B2X monetisation models that depend on the 5G core. NSA’s higher broadband speeds are real, but the architectural capabilities that 5G is famous for live in the 5G core that NSA does not have.

Technical Differences Between 5G SA and 5G NSA

The main difference is structural. In NSA, control signalling for 5G runs through the 4G base station and the 4G core. In SA, the 5G base station connects directly to the 5G core and control signalling does not touch the 4G network. NSA is a 5G layer added to a 4G foundation. SA is 5G end-to-end.

The practical consequences:

NSA is like adding a faster engine to an existing chassis. SA is a new vehicle.

How Do 5G Usage Scenarios Differ Between NSA and SA?

3GPP and GSMA define three major usage scenarios for 5G, but only one of them is fully accessible on NSA.

• Enhanced Mobile Broadband (eMBB). Supported on both NSA and SA. Higher data rates, better capacity, and improved spectral efficiency. This is the workhorse consumer use case 5G was launched with.

• Ultra-Reliable Low-Latency Communications (URLLC). Supported on SA only. Single-digit millisecond latency and reliability guarantees suited to industrial automation, autonomous vehicles, remote surgery, and mission-critical control.

• Massive Machine-Type Communications (mMTC). Supported on SA only at full scale. Massive IoT device density with power-efficient operation.

An operator on NSA can compete on consumer 5G speed. An operator on SA can compete on consumer speed and sell URLLC, mMTC, network slicing, and enterprise-grade differentiated connectivity.

What Changes in Your Core Network When You Move to 5G SA?

The 5G SA transition is not only a radio decision — it reshapes four critical layers of the operator’s core network. Each layer comes with new 3GPP interfaces, new network functions, and new vendor decisions.

1. Authentication and Authorization (AAA). In a 5G SA network, RADIUS-based 4G authentication patterns and legacy HSS interfaces give way to Diameter-based subscriber authentication using interfaces such as S6b, SWx, and SWm, integrated with the UDM and the AUSF. Operators need an AAA that natively supports the full 3GPP Diameter suite and integrates with the 5G Session Management Function (SMF). Alepo AAA is built for 5G SA networks — one enterprise-class platform handling RADIUS, Diameter, and TACACS+ on a single stack, with the EAP family and AI-driven security and operations built in.

2. Policy Control. In 4G, policy decisions are made by the Policy and Charging Rules Function (PCRF). In 5G SA, the PCRF is replaced by the Policy Control Function (PCF), which operates over service-based interfaces and supports per-slice policy enforcement. Operators running both 4G and 5G need a converged policy platform that can manage PCRF and PCF on one stack rather than running two separate policy engines. Alepo’s 5G policy control function (PCF) covers both 4G and 5G policy needs on a single platform.

3. Subscriber Data Management. The 4G Home Subscriber Server (HSS) is replaced in 5G SA by a combination of the Unified Data Management (UDM) function and the Unified Data Repository (UDR), with the Authentication Server Function (AUSF) handling 5G-AKA authentication. Operators staging a 4G-to-5G transition benefit from a converged data layer that supports HSS, UDM, AUSF, and UDR on one platform rather than three separate vendor stacks. See subscriber data management in 5G SA for the converged data layer that supports 4G, 5G NSA, and 5G SA on one stack.

4. Business Support Systems (BSS). 5G SA enables network slicing and B2B2X charging models that legacy BSS platforms were not designed for. Per-slice rating, slice-aware product catalogues, enterprise SLAs, and partner settlement for B2B2X models all require a modern, convergent BSS with a real-time charging engine that can rate per slice and per subscriber simultaneously. Alepo Digital BSS is a convergent, AI-native BSS built for operators monetising 5G use cases beyond flat-rate broadband.

The core-network impact is the part of the 5G SA decision that often surprises operators. Choosing SA over NSA is not just a network architecture upgrade — it is a refresh of AAA, policy, subscriber data, and BSS together. Operators who plan this as one coordinated programme avoid the multi-vendor integration sprawl that derails most 5G SA launches.

What Is the Current State of 5G SA Deployments in 2026?

Five years after the first NSA-led 5G launches, the SA picture looks very different from how it did in 2020. Multiple Tier-1 operators across North America, Europe, Asia-Pacific, and the Middle East have moved to 5G SA in production. As of September 2025, 78 operators had launched 5G SA commercially across 42 countries, with a further 96 having expressed intent to deploy — bringing the total pipeline to 174 operators across 72 countries, according to GSMA Intelligence. Leading SA deployments include operators in the US (T-Mobile), Europe (Deutsche Telekom), and pioneer markets across the GCC and Asia Pacific.. Devices have caught up — most current-generation 5G handsets support both NSA and SA modes.

What has changed is the framing of the question. In 2020, the question was “should an operator commit to SA?” In 2026, the question is “how should an operator stage the SA transition without breaking existing services?” The answer for most operators is a hybrid path — keep NSA running for consumer eMBB while building the 5G core for enterprise, private 5G, network slicing, and new revenue streams. Over time, consumer traffic also migrates to SA as the core matures and VoNR replaces fallback to VoLTE.

The convergence of NSA and SA is the migration story that matters now. Operators that planned their core refresh — AAA, policy, subscriber data, BSS — alongside the SA build are launching enterprise 5G and network slicing on schedule. Operators that treated SA as only a radio decision are discovering integration debt mid-programme.

FAQ: 5G SA vs 5G NSA

Q1: What is the difference between 5G SA and 5G NSA?

5G NSA (Non-Standalone) pairs new 5G radio with the existing 4G core; control signalling runs through the 4G network. 5G SA (Standalone) introduces a new, cloud-native 5G core (5GC) built on Service-Based Architecture, with the 5G radio connecting directly to it. NSA is faster to deploy and limited to enhanced Mobile Broadband. SA enables network slicing, URLLC, mMTC, and advanced enterprise monetisation models that NSA cannot support.

Q3: Can operators upgrade NSA to SA without replacing everything?

Yes, but the path needs planning. The 5G radio investment from an NSA deployment carries forward to SA. What changes is the core network — the 4G EPC has to be paired with or replaced by a 5G core. Modern subscriber data management and policy platforms support 4G, 5G NSA, and 5G SA on one stack, allowing a phased migration. A converged BSS, AAA, and policy refresh is usually the bigger programme than the radio refresh itself.

Q5: What happens to AAA and subscriber authentication when moving to 5G SA?

Authentication moves from 4G’s HSS-based model to a 5G SA model built around the AUSF and UDM. The AUSF handles 5G-AKA authentication. The UDM provides subscriber data and authentication management. AAA platforms supporting 5G SA networks need full 3GPP Diameter coverage (S6b, SWx, SWm, and related interfaces) and native integration with the 5G SMF and UDM. Alepo AAA for 5G Standalone networks is built for this — one platform handling RADIUS, Diameter, and TACACS+ at carrier scale, with the full EAP family and AI-driven security and operations.

Q6: What replaces PCRF in 5G Standalone?

The 5G Policy Control Function (PCF) replaces the 4G Policy and Charging Rules Function (PCRF). The PCF operates over service-based interfaces (Npcf) and supports per-slice policy enforcement, Quality of Service (QoS) control, and access and mobility policies in 5G SA networks. Operators running both 4G and 5G typically deploy a converged policy platform that handles PCRF and PCF on a single stack rather than maintaining two separate engines.

Closing

5G SA versus 5G NSA used to be a question about the radio. In 2026, it is a question about the full core network — AAA, policy, subscriber data, BSS — and how to stage the transition so the operator launches enterprise 5G, network slicing, and new monetisation models without breaking the services that already work.

Alepo’s portfolio is built for that transition: AAA, Converged Policy Control, Subscriber Data Management, and Digital BSS as a coordinated platform for operators moving from 4G to 5G SA. To Explore Alepo’s 5G SA-ready AAA, Policy Control, and BSS to see how each layer fits into the 5G core transition, Book a Demo