Description
Service Based Management Architecture (SBMA) is a management framework defined by 3GPP for the 5G System, which applies the service-based architecture (SBA) principles to network management operations. It replaces traditional, element-centric management approaches with a cloud-native, API-driven model where management services are exposed as standardized, reusable APIs. In SBMA, network functions and resources are managed through a set of management services, such as configuration management, performance management, fault management, and provisioning, which are consumed by management applications or orchestrators. These services are built on HTTP/2 and RESTful principles, using JSON or XML for data exchange, and are defined in OpenAPI specifications to ensure vendor interoperability. The architecture includes key components like the Management Function (MF), which provides management services, and the Management Service Consumer (MSC), which uses these services to perform management tasks.
SBMA works by decoupling management logic from the managed network functions, allowing for centralized or distributed management deployments. Management services are registered and discovered via a service registry, similar to the Network Repository Function (NRF) in the 5G Core, enabling dynamic service composition and scalability. For example, a performance management service can collect metrics from multiple network functions through standardized interfaces, aggregate the data, and provide it to an analytics engine. Fault management services can subscribe to alarms from various functions and trigger automated remediation actions. Configuration management services allow for the provisioning and updating of network function parameters in a consistent manner, supporting zero-touch provisioning and network automation. SBMA also integrates with broader management systems like the Network Slice Management Function (NSMF) and Network Slice Subnet Management Function (NSSMF) to manage the lifecycle of network slices, from creation to termination.
The role of SBMA in the network is to enable efficient, scalable, and automated management of 5G networks, which are characterized by their complexity, dynamic nature, and use of virtualization technologies. By using service-based interfaces, SBMA reduces the integration effort between different management systems and network functions, as all interactions follow a common pattern. It supports intent-based management, where high-level business goals (e.g., "ensure 99.9% reliability for slice X") are translated into low-level management actions through policy-driven automation. SBMA is essential for managing network slicing, as it provides the tools to monitor and adjust slice performance, allocate resources dynamically, and ensure isolation between slices. It also facilitates the integration of artificial intelligence and machine learning for predictive maintenance and optimization, by providing a standardized data collection and control plane.
Purpose & Motivation
SBMA was created to address the management challenges introduced by 5G networks, which are more complex, dynamic, and software-driven than previous generations. Traditional management architectures, such as those based on SNMP or proprietary interfaces, were designed for static, hardware-based networks and struggled to keep pace with the agility required for cloud-native deployments, network slicing, and edge computing. These legacy systems often involved manual configuration, siloed management domains, and high operational overhead, making it difficult to scale and automate network operations.
The primary motivation for SBMA was to align network management with the service-based architecture of the 5G Core, enabling a unified, API-driven approach that simplifies integration and automation. By adopting RESTful APIs and microservices principles, SBMA allows operators to manage network functions as software components that can be dynamically orchestrated. This is critical for supporting use cases like network slicing, where each slice may have unique management requirements that must be provisioned and monitored in real-time. SBMA also addresses the need for multi-vendor interoperability, as standardized interfaces reduce dependency on vendor-specific management tools.
Historically, SBMA evolved from earlier 3GPP management frameworks, such as the Telecommunications Management Network (TMN) and later the Management and Orchestration (MANO) concepts from ETSI NFV. It was formally introduced in 3GPP Release 16 as part of the 5G management specifications, building on the success of SBA in the control plane. By solving the problems of fragmentation and rigidity in network management, SBMA empowers operators to achieve higher operational efficiency, faster service deployment, and better resource utilization, which are essential for monetizing 5G investments and supporting innovative services.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-16, normative work from Rel-17.
In Release 17, the Service-Based Management Architecture (SBMA) was enhanced to support access control. This provides a framework for the Operation, Administration and Maintenance (OAM) system to securely expose collected network energy information, as defined in TS 28.
- Enhance SBMA to support access control TS 28.533CR0092
In Release 18, the Service-Based Management Architecture (SBMA) was formally introduced into the 3GPP management framework, as detailed in specification 32.300. The release provided new clarifications and updates, specifically in TS 28.533 Annex F, on the standardized usage of CRUD operations and NRM fragments to support management capabilities within SBMA.
- Overview of the usage of CRUD operations and NRM fragments in SBMA TS 28.533CR0122
- Rel-18 CR TS 28.533 Update Annex F Usage of CRUD operations and NRM fragments to support management capabilities in SBMA TS 28.533CR0124
- CR R18 Introduction of SBMA in 32.300 TS 32.300CR0034
- Rel-18 CR TS 28.533 Update Annex F Usage of CRUD operations and NRM fragments to support management capabilities in SBMA TS 28.533CR0129
In Release 19, the Service Based Management Architecture (SBMA) was enhanced with new definitions and the addition of an illustrative architecture reference model for management and orchestration. This provides a clearer framework for how OAM functions, such as the collection and exposure of network energy information, are structured and interact within the SBMA.
Explore further
Broader topics and technologies where SBMA plays a role.
Defining Specifications
3GPP specifications that define or reference SBMA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 26.942 vj00 | Study on Media Energy Consumption Exposure & Evaluation | Rel-19 |
| TS 28.111 vj30 | Fault Management Service Specification | Rel-19 |
| TS 28.533 vj30 | Management and orchestration; Architecture framework | Rel-19 |
| TR 28.834 vi01 | Technical Report | Rel-18 |
| TR 28.837 vi00 | Technical Report on Trace/MDT Management | Rel-18 |
| TS 28.871 vj00 | Study on Service Based Management Architecture enhancement phase 3 | Rel-19 |
| TS 28.873 vj10 | Study on Data Management, Subscriptions, and Reporting | Rel-19 |
| TR 28.925 vj00 | Enhancement of Service Based Management Architecture | Rel-19 |
| TS 32.300 vj00 | 3GPP Network Resource Naming Convention | Rel-19 |