Description
Standalone (SA) is a deployment architecture term in 3GPP, most prominently used for 5G, denoting a complete, independent system. In a 5G Standalone (5G SA) deployment, the Next Generation Radio Access Network (NG-RAN), which consists of gNBs transmitting the 5G New Radio (NR) air interface, is connected to the 5G Core network (5GC). This is a clean-slate architecture where both the RAN and the Core are based on the new 3GPP specifications defined from Release 15 onwards. The 5GC introduces fundamental architectural changes like a Service-Based Architecture (SBA) with network functions (NFs) such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), and User Plane Function (UPF). In SA mode, control plane signaling (e.g., registration, authentication, session establishment) and user plane data traffic are handled entirely through these new 5G network functions, without any reliance on the 4G Evolved Packet Core (EPC).
The operation in SA mode unlocks the full spectrum of 5G features. From a control plane perspective, procedures like initial registration, service request, and handover are executed natively between the UE, the gNB, and the 5GC NFs using new protocols like HTTP/2 for service-based interfaces. On the user plane, data flows directly between the UE and the UPF, enabling the ultra-low latency and high throughput promised by 5G. Key capabilities inherent to SA include Network Slicing, which allows the creation of multiple logical, isolated networks on a common physical infrastructure tailored for different service types (e.g., enhanced Mobile Broadband, Ultra-Reliable Low-Latency Communications, Massive IoT). It also fully supports advanced QoS models, edge computing integration via Local Area Data Networks (LADN), and native support for non-public networks.
Contrasting with SA is Non-Standalone (NSA) deployment, initially defined for 5G. In NSA mode (e.g., Option 3x), the 5G NR base station (gNB) is deployed as a secondary cell for data boost, while the 4G LTE base station (eNodeB) acts as the master node providing the control plane connection to the 4G EPC. SA eliminates this dependency, simplifying the network architecture and operations. The transition to SA is a significant step for operators, as it often requires a new core network build-out but is necessary to realize transformative 5G services beyond enhanced mobile broadband, such as mission-critical communications and large-scale IoT. The term 'Standalone' has also been used historically in other 3GPP contexts, such as Standalone GSM cells or Standalone Location Services, but in the modern 5G era, it predominantly refers to the 5G SA architecture.
Purpose & Motivation
The purpose of the Standalone architecture is to realize the complete vision and full capability set of a new generation of mobile technology, unencumbered by legacy system dependencies. For 5G, the motivation for defining SA was to enable services and features that were impossible or inefficient in the Non-Standalone (NSA) mode anchored to 4G. NSA was a pragmatic first step for early 5G deployment, allowing operators to launch 5G services rapidly by leveraging existing 4G core infrastructure, but it could not support core 5G innovations like end-to-end network slicing, ultra-reliable low latency communication (URLLC) with simplified user plane paths, or the service-based core architecture.
SA was created to solve these limitations. It addresses the need for a flexible, cloud-native core network (5GC) that can support diverse service requirements through network slicing—a key differentiator for 5G. It also solves the problem of control plane latency and complexity introduced by the dual-connectivity anchoring in NSA. By establishing a direct control plane connection between the UE and the 5GC via the gNB, procedures become more efficient. Historically, the concept of a 'standalone' mode exists to mark the point where a new technology generation becomes self-sufficient, no longer requiring the previous generation as a crutch. This allows for optimized performance, simplified network management, and the introduction of revolutionary services that define the new generation's value proposition, moving beyond mere incremental speed improvements.
What changed in its specifications
The latest release-to-release comparison of specifications that define SA. Each summary describes the whole specification, not only this term.
Rel-5 added applet management commands, minimum security level specification, and a security layer relation to Open Platform architecture.
Full comparison in TS 23.048 →Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference SA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.048 v590 | Secured Packets Structure for SMS and UICC Management | Rel-5 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TR 23.794 vh00 | Study on enhanced IMS to 5GC integration | Rel-17 read |
| TS 24.109 vj00 | HTTP Digest AKA & GAA Stage 3 | Rel-19 read |
| TS 24.193 vk10 | ATSSS Stage 3 Procedures | Rel-20 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.502 vk00 | Non-3GPP Access Network Discovery and Selection | Rel-20 read |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 read |
| TS 25.410 vj00 | Iu Interface Introduction for UTRAN | Rel-19 read |
| TS 25.414 vj00 | UTRAN Iu Interface User Plane Transport Protocols | Rel-19 read |
| TS 25.419 vj00 | Service Area Broadcast Protocol (SABP) | Rel-19 read |
| TS 25.703 vc00 | HNB Emergency Warning Area Study for UTRA | Rel-12 read |
| TS 26.346 vj30 | MBMS User Services Specification | Rel-19 read |
| TS 28.552 vk40 | 5G Network Performance Measurements | Rel-20 read |
| TS 29.273 vj20 | EPS AAA Reference Points and Procedures | Rel-19 read |
| TS 31.117 vj30 | USAT Tests for Non-Removable UICC | Rel-19 read |
| TS 31.127 vj00 | UE Application Behavioural Tests for Non-Removable UICC | Rel-19 read |
| TS 33.203 vk00 | IMS Security Features and Mechanisms | Rel-20 read |
| TS 33.204 vj00 | TCAP Security (TCAPsec) Stage 2 Specification | Rel-19 read |
| TS 33.210 vk00 | Network Domain Security for IP Networks | Rel-20 read |
| TS 33.223 vj00 | GBA Push Function Specification | Rel-19 read |
| TS 33.224 vj00 | Generic Push Layer (GPL) Specification | Rel-19 read |
| TS 33.320 vj00 | H(e)NB Subsystem Security Architecture | Rel-19 read |
| TS 33.402 vj00 | Security for non-3GPP access to EPS | Rel-19 read |
| TS 33.703 vk10 | Post-Quantum Cryptography for 3GPP Systems | Rel-20 read |
| TS 33.821 v900 | LTE/SAE Security Threat Analysis and Countermeasures | Rel-9 read |
| TS 33.938 vj30 | 5G Standalone Cryptographic Inventory | Rel-19 read |
| TS 37.718 | 3GPP TR 37.718 | Rel-4 read |
| TR 37.941 vj20 | RF Conformance Testing Background for Radiated BS Requirements | Rel-19 read |
| TR 37.985 vj00 | Overview of V2X features in LTE and NR | Rel-19 read |
| TS 38.106 vk00 | NR Repeaters: RF Requirements (TS 38.106) | Rel-20 read |
| TS 38.133 vk10 | NR Radio Resource Management Requirements | Rel-20 read |
| TS 38.719 vj10 | NR Inter-band CA/DC Configurations | Rel-19 read |
| TR 38.889 vg00 | NR-based access to unlicensed spectrum study | Rel-16 read |
| TR 38.913 vj00 | Next Gen Access Tech Scenarios & Requirements | Rel-19 read |
| TS 38.914 vk10 | 6G Radio Scenarios and Requirements | Rel-20 read |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 read |