SR-IOV (Single Root I/O Virtualisation) is a PCI-SIG specification that lets one physical PCIe device (typically a NIC or accelerator) expose multiple lightweight Virtual Functions (VFs) — each assignable directly to a VM or container — while a Physical Function (PF) remains for management and global configuration. VFs bypass much of the hypervisor’s software switching path, delivering lower latency, higher throughput, and more deterministic behaviour than paravirtualised virtio alone — properties valued in telco NFV (vEPC, vRAN CU/DU, firewall, DPI) and in cloud-native packet workloads on Kubernetes.
Precision Time Protocol (PTP), standardised as IEEE 1588, distributes a common reference time across packet networks so that distributed nodes share a clock with sub-microsecond to nanosecond accuracy — far beyond what NTP typically achieves over IP. PTP operates in a master–slave hierarchy: a Grandmaster Clock (GM) holds traceability to GNSS (GPS, Galileo, etc.) or a Primary Reference Time Clock (PRTC); Boundary Clocks (BC) terminate and regenerate timing on hops; Transparent Clocks (TC) correct residence time in switches without terminating the protocol. Messages (Sync, Follow_Up, Delay_Req/Resp, optional Announce) implement a delay request–response mechanism to estimate path asymmetry and offset each Ordinary Clock (OC) slave relative to the grandmaster.
Private 5G (also non-public 5G, dedicated 5G, or campus/industrial 5G) denotes 3GPP-conformant 5G systems operated for a defined organisation or site — factory, port, mine, hospital, stadium, or utility — rather than as a nationwide public mobile service. 3GPP Release 16+ formalised Non-Public Networks (NPN) with two principal models: Standalone NPN (SNPN) — an isolated PLMN (dedicated MCC/MNC or PLMN ID) with its own 5GC and NG-RAN; and Public Network Integrated NPN (PNI-NPN) — a slice or dedicated DNN on a public operator’s 5G with contractual isolation. Private 5G delivers URLLC-capable connectivity, local breakout (traffic stays on-site via local UPF), deterministic QoS, and control over upgrades and security policies — advantages over Wi-Fi 6/7 in mobility, scheduling, and industrial TSN integration scenarios, at higher cost and regulatory complexity.
The O-RAN Alliance is an operator-led global industry alliance, formed in February 2018 through the merger of the C-RAN Alliance and the xRAN Forum, whose mission is to reshape how radio access networks are designed, built, and operated. Where traditional RAN stacks are vertically integrated — baseband software, radio hardware, and management tools delivered as a single vendor bundle — O-RAN promotes disaggregation: separating the RAN into open, standardised functional blocks connected by published interfaces, so a mobile operator can mix DU, CU, RU, and management software from different suppliers. The alliance’s core objectives are multi-vendor interoperability, cloud-native and virtualised deployment, programmable RAN intelligence through the RIC (RAN Intelligent Controller), and operational automation at scale. These goals address vendor lock-in, slow innovation cycles, and the cost structure of legacy RAN, while aligning with 5G and beyond requirements for network slicing, edge deployment, and AI/ML-driven optimisation.
Edge computing in telecommunications places compute, storage, and application execution close to users and devices — at cell sites, regional points of presence, or on-prem enterprise locations — rather than only in distant hyperscale data centres. The goal is to reduce end-to-end latency, limit backhaul load, satisfy data residency, and enable real-time applications (AR/VR, industrial control, V2X, video analytics) that are impractical with 50–100 ms round trips to central clouds. In 5G, edge is tightly coupled to the user plane: a local UPF on N6 breakout forwards traffic to an edge data network (DN) hosting MEC applications without hairpinning through the operator’s core hub.
The Data Plane Development Kit (DPDK) is an open-source set of libraries and poll-mode drivers (PMDs) that move packet processing from the kernel to userspace, enabling telco and cloud applications to achieve millions of packets per second per core with predictable latency. DPDK bypasses the traditional socket stack: applications busy-poll NIC queues (or virtio/vhost rings), use hugepages to reduce TLB misses, and pin threads to NUMA-local cores — a model suited to UPF, vRouter, CG-NAT, load balancers, and 5G user-plane functions where per-packet syscall overhead is unacceptable.
Autonomous Networks (AN) describe an operator evolution path toward networks that configure, optimise, secure, and heal themselves with minimal manual intervention — expressed as closed loops (sense → analyse → decide → act) spanning RAN, transport, core, and cloud infrastructure. The concept is not a single product but a maturity model: TM Forum defines Autonomous Networks Levels (ANL 0–5), from fully manual operation (L0) through assisted and partial automation (L1–L3) to high and full autonomy (L4–L5) where intent (business or service goals) is translated into technical policies and executed with human oversight only for exceptions. GSMA and major operators (e.g. TM Forum AN Leadership Council participants) align roadmaps on high autonomy by ~2027–2030 for selected domains (energy saving, fault recovery, capacity management) rather than overnight “lights-out” operations.
The AI-RAN Alliance is a global industry consortium, launched at MWC Barcelona in February 2024 and governed by a Technical Steering Committee (TSC), whose mission is to accelerate the integration of artificial intelligence into Radio Access Networks and to define what an AI-native RAN looks like in practice for 5G Advanced and 6G. The alliance deliberately positions itself as neither a marketing organisation nor a demo factory: it pursues pioneering, pre-competitive work — reference architectures, blueprints, and credible benchmarking — without getting mired in formal standards processes or IP negotiations. Its work spans three complementary objectives — AI-for-RAN (using AI/ML to improve RAN performance and efficiency), AI-and-RAN (co-locating RAN and AI workloads on shared accelerated infrastructure), and AI-on-RAN (hosting tenant-facing AI applications at the network edge for differentiated, monetisable connectivity). Founding members include Ericsson, Nokia, NVIDIA, T-Mobile, SoftBank, Samsung, AWS, Microsoft, and Arm; membership grew from a handful at launch to 130+ organisations by MWC 2026, spanning operators, NEPs, hyperscalers, silicon vendors, universities, and government research bodies across more than 17 countries.
6G denotes the next generation of mobile cellular systems, framed internationally as IMT-2030 by ITU-R and studied in 3GPP from Release 18 (5G Advanced) onward with dedicated 6G work items accelerating in Release 19–21. Commercial deployment is widely targeted for around 2030, following the typical decade-long cycle after 5G (IMT-2020). Unlike incremental 5G releases, 6G research programmes emphasise a native integration of AI/ML in the air interface and the core (not only as an overlay analytics function), Integrated Sensing and Communication (ISAC) — using radio resources jointly for connectivity and environment sensing — and exploration of sub-terahertz and advanced MIMO for extreme capacity and sensing resolution. Energy efficiency, ubiquitous coverage (including NTN/satellite as a first-class component), and trustworthy / resilient network operation are recurring design goals across regional initiatives (Europe’s Hexa-X / Hexa-X-II, Korea’s 6G R&D, Japan’s Beyond 5G, and industry forums such as Next G Alliance in North America).
The 5G Core (5GC) is the packet core network architecture defined by 3GPP from Release 15 onward as the control and user-plane backbone of standalone 5G deployments. It replaces the Evolved Packet Core (EPC) of 4G LTE not through incremental evolution but through a deliberate architectural break: where the EPC was built around monolithic, hardware-bound network functions interconnected by point-to-point interfaces, the 5GC is designed from the ground up around a Service-Based Architecture (SBA) — every network function exposes its capabilities as a set of services over a common HTTP/2 bus (the Service-Based Interface, SBI), and any authorised consumer NF can discover and invoke those services through the NRF (Network Repository Function) without bilateral peering agreements or proprietary protocols. This shift reflects two structural requirements of 5G that EPC could not satisfy: network slicing — the ability to run logically independent end-to-end networks (each with its own QoS, isolation, and lifecycle) on shared physical infrastructure — and cloud-native deployment, where NFs run as containerised microservices on commodity compute, can be horizontally scaled, and are managed by standard Kubernetes-compatible orchestration rather than vendor-specific element managers. The 5GC also enforces a hard separation between Control Plane (CP) and User Plane (UP) — the CUPS principle inherited from 3GPP Release 14 and fully operationalised here — so that the UPF (User Plane Function) handling packet forwarding, QoS enforcement, and traffic anchoring can be distributed to the edge independently of the control logic, enabling ultra-low-latency and MEC scenarios without redesigning the control plane. The architecture is access-agnostic: the same 5GC serves NR (New Radio), eLTE, Wi-Fi (untrusted/trusted non-3GPP access), and fixed-wireless access through a unified N2/N3 reference point toward the access network and a common UE context model in the AMF.
