โ† Telecom & Networking
5GNR / 5GC โ€” Deep Dive
View Details โ€” Coming Soon
2019NR5GCSBAAMFSMFUPFeMBBURLLCmMTCNSA/SA

5G / NR: From Broadband to Mission-Critical Connectivity

5G New Radio (NR) launched commercially in 2019 in South Korea and the US. Unlike previous generations defined by a single use case, 5G is designed for three fundamentally different scenarios: ultra-fast broadband (eMBB), ultra-low latency (URLLC), and massive machine connectivity (mMTC). Its service-based core architecture (5GC) and network slicing capability represent the most radical redesign of mobile core networks since GSM.

5G Architecture

Five Logical Layers โ€” UE, RAN, and 5GC

UE โ€” User Equipment

The UE (also referred to as the ME โ€” Mobile Equipment) is the device used by the subscriber: a smartphone, tablet, CPE, or IoT module. In Standalone (SA) mode the UE connects to a gNB over the NR Uu air interface. In Non-Standalone (NSA) mode, the UE maintains a simultaneous connection to both an eNB (LTE, LTE Uu) and a gNB โ€” the eNB anchors the control plane while the gNB adds 5G data capacity.

gNB โ€” gNodeB (5G NR Base Station)

The gNB is the 5G radio access node โ€” it transmits and receives NR signals and terminates the NR Uu interface toward the UE. Each gNB connects to the AMF via the N2 interface (control plane) and to the UPF via N3 (user plane). Adjacent gNBs communicate directly over the Xn interface for handover and coordination. In NSA mode, an eNB connects to a gNB via X2/Xn for dual-connectivity.

5GC Control Plane โ€” Service-Based Architecture

The 5G Core replaces the LTE EPC with a cloud-native, microservices-based design. All control-plane network functions (NFs) expose HTTP/2 REST APIs on a Service-Based Interface (SBI) and register with the NRF so other functions can discover them dynamically. Key functions visible in the architecture:

  • AMF โ€” Access and Mobility Management Function; the central control-plane anchor. Handles UE registration, NAS signalling, mobility management, and paging. The UE has a logical N1 interface to the AMF. The gNB connects to the AMF via N2. The AMF communicates with the SMF via N11.
  • SMF โ€” Session Management Function; manages all PDU sessions: allocates IP addresses, selects and controls the UPF, and enforces QoS policies. Communicates with the UPF over N4.
  • UDM โ€” Unified Data Management; stores subscriber profiles, authentication credentials, and authorised services. Backed by the UDR (Unified Data Repository) with a Front End (FE) separating application logic from storage.
  • AUSF โ€” Authentication Server Function; executes the 5G-AKA and EAP-AKA' authentication procedures on behalf of the AMF, interacting with the UDM for key material.
  • PCF โ€” Policy Control Function; provides unified policy rules for session management (QoS, charging) and access control, replacing the PGW-c/PCRF of LTE.
  • NSSF โ€” Network Slice Selection Function; selects the appropriate Network Slice Instance (NSI) and AMF set for a UE based on its NSSAI (slice identifier).
  • NEF โ€” Network Exposure Function; securely exposes 5G network capabilities and events to authorised third-party applications and AF.
  • NRF โ€” Network Repository Function; the service registry โ€” all NFs register here and discover each other via NRF queries.
  • AF โ€” Application Function; an application-layer entity (may be operator-owned or third-party) that interacts with the 5GC via NEF or directly with PCF/SMF for QoS influence.
UPF โ€” User Plane Function

The UPF is the sole user-plane forwarding node in the 5GC โ€” it carries all actual subscriber data packets. The gNB tunnels user-plane traffic to the UPF via N3 (GTP-U); the SMF controls the UPF via the N4 interface (PFCP protocol) to install packet detection, forwarding, and QoS enforcement rules. The UPF connects to the external Data Network (e.g., the internet or an enterprise network) via the N6 interface. UPFs can be deployed centrally (cost-efficient) or pushed to the network edge (low latency for URLLC and MEC).

NSA โ€” Non-Standalone Mode (eNB + EPC)

In NSA deployment, the LTE eNB continues to serve as the control-plane anchor โ€” it connects to the existing EPC via the S1 interface for mobility and signalling. A 5G gNB is added as a secondary node, connected to the eNB via X2/Xn. The gNB provides additional user-plane capacity (N3 to UPF or via the S-GW/PGW depending on option), but all registration, paging, and handover are still handled by the LTE/EPC path. NSA (Option 3x) was the first deployment mode used by most operators, allowing rapid 5G launch without replacing the LTE core.

The 5G architecture supports both SA (Standalone) and NSA (Non-Standalone) deployment modes, as shown in the diagram. SA mode uses the native 5GC with AMF, SMF, UPF and the full service-based interface mesh. NSA mode anchors the control plane on the LTE eNB and EPC while the gNB adds NR radio capacity. Interfaces N1, N2, N3, N4, N11, Xn, and the SBI (Namf, Nsmf, Nudm, Nausf, Npcf, Nnssf, Nnef, Nnrf, Naf) are all labelled in the figure.

5G Architecture Diagram

Abbreviations

AbbreviationFull FormAbbreviationFull Form
UEUser EquipmentMEMobile Equipment
gNBgNodeB (5G NR Base Station)eNBeNodeB (LTE Base Station)
NRNew RadioNR Uu5G Air Interface (UE โ†” gNB)
LTE UuLTE Air Interface (UE โ†” eNB)N1UE โ†” AMF (logical NAS)
N2gNB โ†” AMFN3gNB โ†” UPF (GTP-U tunnel)
N4SMF โ†” UPF (PFCP)N11AMF โ†” SMF
XngNB โ†” gNBX2eNB โ†” gNB (NSA dual-connectivity)
S1eNB โ†” EPC (NSA)N6UPF โ†” Data Network
AMFAccess and Mobility Management FunctionSMFSession Management Function
UPFUser Plane FunctionUDMUnified Data Management
UDRUnified Data RepositoryFEFront End (UDM application logic)
AUSFAuthentication Server FunctionPCFPolicy Control Function
NSSFNetwork Slice Selection FunctionNEFNetwork Exposure Function
NRFNetwork Repository FunctionAFApplication Function
5GC5G Core NetworkEPCEvolved Packet Core (LTE core)
SBAService-Based ArchitectureSBIService-Based Interface (HTTP/2)
PDUProtocol Data Unit (session type in 5G)PFCPPacket Forwarding Control Protocol
NSANon-Standalone (LTE anchor + 5G NR)SAStandalone (native 5GC)
MECMulti-access Edge ComputingNSINetwork Slice Instance
NSSAINetwork Slice Selection Assistance InformationGTP-UGPRS Tunnelling Protocol (User Plane)

Three Core Use Cases

eMBB โ€” Enhanced Mobile Broadband

Targets human-centric broadband applications: 4K/8K streaming, fixed wireless access (FWA), AR/VR, and dense stadium/event deployments. Peak theoretical downlink: 20 Gbps. Real-world mmWave deployments achieve 1โ€“4 Gbps; sub-6 GHz deployments typically 200โ€“1000 Mbps. Sub-6 GHz 5G covers wide areas; mmWave (24โ€“100 GHz) delivers extreme capacity at short range (100โ€“200 m).

URLLC โ€” Ultra-Reliable Low-Latency Communication

Targets machine-to-machine and mission-critical applications: factory automation, remote surgery, autonomous vehicles, and smart grid control. Target latency: <1 ms over-the-air; 99.999% reliability. Achieves this through mini-slots (as short as 0.125 ms), pre-emption of eMBB traffic, and redundant multi-path transmission.

mMTC โ€” Massive Machine-Type Communication

Targets low-power, wide-area IoT: smart meters, agriculture sensors, asset trackers, and city infrastructure. Target: 1 million devices per kmยฒ. 5G NR-Light (Rel-17 RedCap) addresses mid-tier IoT; LTE-based NB-IoT and LTE-M are the primary mMTC technologies in current 5G networks, operating as part of the 5G ecosystem.

5G New Radio โ€” The Air Interface

  • Flexible numerology โ€” 5G NR uses a configurable subcarrier spacing (SCS) called numerology ยต: 15 kHz (ยต=0, like LTE), 30 kHz (ยต=1), 60 kHz (ยต=2), 120 kHz (ยต=3), 240 kHz (ยต=4). Higher SCS reduces slot duration, enabling lower latency and supporting mmWave frequencies
  • FR1 (sub-6 GHz) and FR2 (mmWave) โ€” FR1 covers 410 MHzโ€“7.125 GHz (broad coverage, similar propagation to LTE); FR2 covers 24.25โ€“52.6 GHz (extreme capacity, very limited range and penetration, requires beamforming)
  • Channel bandwidth up to 400 MHz โ€” a single 5G NR carrier can be up to 100 MHz wide in FR1 and 400 MHz in FR2, compared to 20 MHz maximum in LTE
  • CP-OFDM downlink and DFTS-OFDM uplink โ€” same OFDM family as LTE but with flexible CP overhead; DFTS-OFDM on the uplink reduces PAPR when continuous coverage is needed

Massive MIMO and Beamforming

Massive MIMO (64T64R and beyond)

5G NR base stations (gNBs) routinely use 64 transmit and 64 receive antenna elements in the active antenna unit (AAU). More antennas enable more simultaneous spatial layers (MU-MIMO) โ€” a single gNB can serve 8โ€“16 UEs simultaneously on the same time-frequency resource, multiplying cell capacity without additional spectrum.

3D Beamforming

With a 2D antenna array, the gNB can steer beams in both horizontal and vertical directions (Full-Dimension MIMO). This allows the network to focus energy precisely at each UE's location, increase signal strength, reduce interference to neighbouring cells, and serve users on different floors of a building simultaneously โ€” critical for dense urban and indoor deployments.

Network Slicing

Network slicing is 5G's most transformative architectural feature โ€” it allows a single physical 5G network to be divided into multiple isolated logical networks, each customised for a specific use case or customer:

  • Each slice has dedicated resources โ€” separate AMF/SMF/UPF instances (or shared with isolation), radio resource quotas, and QoS policies; one slice's failure or overload cannot affect others
  • NSSAI โ€” Network Slice Selection Assistance Information โ€” a standardised identifier carried in NAS messages; the AMF uses it to route the UE to the correct slice at attach time
  • Example slices โ€” a public safety slice (guaranteed URLLC bandwidth), a consumer eMBB slice (best-effort broadband), and a private enterprise slice (isolated, dedicated capacity) can all run on the same infrastructure simultaneously
  • Requires end-to-end orchestration โ€” slices must be provisioned across RAN (via RAN slicing), transport, and core; this typically requires an NFVO/MANO system or a cloud orchestrator like Kubernetes with 5G-aware scheduling

NSA vs SA Deployment Modes

Non-Standalone (NSA) โ€” Option 3x

The initial deployment mode used by most operators. 5G NR provides the additional radio capacity (data plane) while LTE eNBs remain the control-plane anchor โ€” UE registration, mobility, and paging all use the existing LTE/EPC infrastructure. This allowed rapid nationwide 5G launch without replacing the LTE core network.

Standalone (SA) โ€” Option 2

The target architecture: 5G NR gNBs connect directly to the native 5GC (AMF, SMF, UPF). Unlocks all 5G features โ€” network slicing, URLLC, edge computing, and full control-plane independence. Requires deploying the new 5GC alongside gNBs, which is a larger investment. SA deployments are growing from 2022 onward.

5G's Significance

  • Industry 4.0 enabler โ€” URLLC and private 5G networks are enabling wireless factory automation, robot control, and real-time quality inspection at scales impossible with Wi-Fi or LTE
  • Fixed Wireless Access (FWA) โ€” 5G replaces DSL and cable broadband in underserved areas; home routers using 5G mmWave or sub-6 GHz deliver gigabit speeds without digging trenches
  • Cloud-native telecom โ€” the 5GC's containerised microservices model brings DevOps practices to telco infrastructure; operators can update individual functions independently and scale horizontally
  • Security improvements โ€” 5G added SUPI/SUCI (conceals IMSI over the air), subscription concealment via ECIES, and enhanced NAS integrity protection; IMSI catchers are significantly harder to execute
  • Platform for 6G research โ€” AI-native network management, integrated sensing, and reconfigurable intelligent surfaces (RIS) are being prototyped on 5G infrastructure as precursors to 6G