Service Based Architecture

Description

The Service Based Architecture (SBA) represents a paradigm shift in the design of the 3GPP Core Network, introduced with 5G System (5GS) in Release 15. Unlike the traditional point-to-point, reference-point-based architecture of previous generations (e.g., EPC), SBA models network functions as producers and consumers of services. Each Network Function (NF), such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), or Unified Data Management (UDM), exposes its capabilities as one or more services. These services are defined by a set of operations accessible via a standardized Application Programming Interface (API), primarily using HTTP/2 with JSON payloads, though other protocols can be specified.

The architecture relies on a few key enabling components. The Network Repository Function (NRF) acts as a service registry and discovery mechanism. When an NF service producer initializes, it registers its profile (including supported services and instance address) with the NRF. Consumer NFs can then query the NRF to discover available producer instances. This decouples service providers from consumers, enabling dynamic scaling, load balancing, and resilience. The Service Communication Proxy (SCP) can be deployed to provide indirect communication, offering features like message routing, security enforcement, and load balancing between NFs. The architecture mandates mutual authentication between NFs, typically using TLS, ensuring secure service-based interactions.

SBA fundamentally changes how network functions interact. Communication is no longer based on static, pre-configured links but on dynamic service discovery and consumption. This aligns perfectly with cloud-native principles such as microservices, stateless design (where applicable), and continuous integration/deployment. It allows operators to deploy, scale, and update individual NFs independently, drastically improving operational agility. Furthermore, SBA is essential for realizing advanced 5G concepts like network slicing, as it allows for the instantiation and composition of specific sets of NF services to form a logically isolated network slice tailored to a particular service type (e.g., enhanced Mobile Broadband, Massive IoT, Ultra-Reliable Low Latency Communications). The architecture's flexibility also future-proofs the network, making it easier to introduce new services and capabilities in subsequent releases.

Purpose & Motivation

The Service Based Architecture was created to address the limitations of the rigid, monolithic, and hardwired architecture of the Evolved Packet Core (EPC) in 4G. The EPC used defined reference points (e.g., S1, S5, S11) with proprietary or standardized protocols (e.g., GTP, Diameter) between specific pairs of network elements. This created tight coupling, making network upgrades, scaling, and the introduction of new functions slow, complex, and costly. It was ill-suited for the cloud era, which demands elasticity, automation, and rapid service innovation.

The primary motivation for SBA was to enable a cloud-native 5G Core that could leverage modern IT practices like DevOps and microservices. By breaking down monolithic NFs into sets of interoperable services, SBA allows operators to deploy software on commercial off-the-shelf hardware in data centers, leveraging virtualization and containerization. This solves the problem of vendor lock-in and hardware dependency, reducing CAPEX and OPEX. Furthermore, the dynamic service discovery and loose coupling inherent in SBA directly support the 5G vision of network slicing, where multiple logical networks with different characteristics must be created, managed, and scaled on a shared physical infrastructure. SBA provides the architectural foundation for this by allowing slice-specific instances of NFs to be dynamically composed and interconnected.