Description
The Management Information Base (MIB) is a fundamental component in network management systems, defined as a virtual database that stores the management information of network entities. It is structured according to the Structure of Management Information (SMI), which uses a hierarchical tree format with object identifiers (OIDs) to uniquely name each managed object. These objects represent various aspects of a network device, such as configuration parameters, performance statistics, operational states, and fault conditions. The MIB does not store data itself but defines the schema—the types of data that can be accessed, their syntax, and access permissions (e.g., read-only or read-write). This schema is implemented in network management agents residing on devices like routers, switches, or base stations.
In operation, a network management system (NMS) interacts with the MIB through management protocols, primarily the Simple Network Management Protocol (SNMP). The NMS sends SNMP requests (e.g., GET, SET) to an agent on a managed device, specifying the OID of the desired object. The agent then accesses the corresponding data from the device's internal state and returns it in an SNMP response. For instance, a MIB might define objects for interface throughput, error counts, or CPU utilization, allowing the NMS to monitor network health. The MIB's role is to provide a standardized, vendor-neutral interface, ensuring that management data from different equipment can be interpreted consistently.
Key components of a MIB include managed objects, which are data variables representing network resources; notifications (or traps), which are asynchronous alerts sent by agents to report events like failures; and groups, which organize related objects for modularity. MIBs are defined in text files using ASN.1 notation and are compiled into a format usable by management software. In 3GPP networks, MIBs are crucial for managing elements across the Radio Access Network (RAN) and Core Network (CN), such as NodeBs, eNodeBs, gNBs, and MMEs. They enable fault management, performance monitoring, configuration, and security auditing, forming the backbone of operations, administration, and maintenance (OAM) systems.
The architecture of MIBs in 3GPP evolves across releases, with specifications detailing MIB modules for various network functions. For example, 3GPP TS 32.600 series defines MIBs for performance management, while TS 28.622 covers 5G network resource models. MIBs support scalability through modular design, allowing new objects to be added for emerging technologies like 5G NR or network slicing. They integrate with higher-level management frameworks, such as the Network Management (NM) and Element Management (EM) layers in the Telecommunications Management Network (TMN) model. By abstracting device-specific details into a common schema, MIBs reduce management complexity and facilitate automation, which is vital for large-scale, dynamic networks.
Purpose & Motivation
The MIB was created to address the challenges of managing heterogeneous, multi-vendor telecommunications networks. Before standardization, each equipment manufacturer used proprietary management interfaces, making it difficult for operators to integrate and monitor diverse network elements. This led to high operational costs, inconsistent data formats, and limited interoperability. The MIB, as part of the SNMP framework developed in the late 1980s, provided a universal language for network management, enabling centralized control and monitoring. In 3GPP, its adoption ensured that mobile networks could be managed efficiently as they grew in complexity from 2G to 5G.
The primary problem the MIB solves is the lack of a common data model for network management. By defining a structured hierarchy of managed objects, it allows network management systems to query and configure devices from different vendors using the same protocol (SNMP). This standardization reduces integration effort, improves fault detection, and supports automated operations. For 3GPP, MIBs are essential for meeting regulatory requirements, ensuring service quality, and enabling features like self-organizing networks (SON). They also facilitate the evolution to software-defined networking (SDN) and network function virtualization (NFV) by providing a consistent management interface.
Historically, the MIB concept originated from the Internet Engineering Task Force (IETF) and was incorporated into 3GPP standards to align with broader IT practices. Its motivation includes the need for real-time monitoring in dynamic mobile environments, where parameters like radio conditions or user load change rapidly. MIBs allow operators to track key performance indicators (KPIs), configure network slices, and manage security policies. As networks evolved, MIBs expanded to cover new technologies, such as LTE and NR, addressing limitations of earlier management approaches that were less flexible or scalable.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (105 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-15.
In Release 15, enhancements to the MIB function were focused on improving system information handling and provisioning, as indicated by corrections and clarifications on system information acquisition. Specific introductions included slicing assistance information and enhancements to avoid conflicts in System Information message scheduling. Furthermore, management functions were expanded with the addition of new network resource model fragments to support performance management.
- Running 36.300 CR to introduce assistance information for local cache TS 36.300CR1076
- Introduce assistance information for local cache 36.331 CR TS 36.331CR3178
- Addition of management functions and entities TS 32.101CR0067
- Introduction of Geofencing information in CMAS TS 36.331CR3523
- SI message scheduling enhancement to avoid conflicts between legacy and positioning System Information TS 36.331CR3596
- Add the missing NRM fragment supporting network performance management TS 28.622CR0027
+ 35 more changes
In Release 16, specific corrections were made to the MIB acquisition procedures, particularly addressing issues related to intra-frequency cell reselection during MIB and SIB1 acquisition failure. Furthermore, a direct correction was applied to the MIB's `subCarrierSpacingCommon` field to ensure accurate signaling. These updates refined the reliability of initial cell selection and system information acquisition for the User Equipment.
- Update generic NRM Information Service to support Managed NF Service Object TS 28.622CR0033
- CR TS 38.300 Remote Interference Management TS 38.300CR0184
- Introduction of cross link interference management TS 38.300CR0201
- Correct notification support table for ManagedElement and ManagementNode TS 28.622CR0097
- Correction regarding placement of cell specific SSB QCL information TS 36.331CR4393
- Miscellaneous corrections on overheating assistance information for NR SCG TS 36.331CR4489
+ 9 more changes
In Release 17, specific MIB-related enhancements included a correction on the MIB configuration for NR Non-Terrestrial Networks (NTN) and a specification change regarding the periodicity of the MIB, as detailed in the relevant 38.331 Change Request. These updates refined the broadcast system information parameters for improved operation in new deployment scenarios.
- Enhance NRM with geographical information supporting MDA TS 28.622CR0131
- Add stage2 definition for file management TS 28.622CR0147
- Add stage 2 for management data collection and discovery TS 28.622CR0166
- On introducing height information reporting in MDT reports [LTE-Height-MDT] TS 36.331CR4756
- Include already approved changes or enhancements of attribute properties for IOC ManagementDataCollectio TS 28.622CR0170
- Correction of UE History Information for CHO TS 38.300CR0607
+ 6 more changes
In Release 18, enhancements to the Management Information Base (MIB) function introduced new parameters for MDT Alignment Information and Available RAN Visible QoE Metrics. It also expanded ManagementDataCollection to support requests for management data per PLMN and added broadcast assistance information for GNSS LOS/NLOS positioning. Furthermore, corrections and clarifications were made for UE Location Information Reporting in IoT-NTN and for UE History Information.
- Definition of parameters MDT Alignment Information and Available RAN Visible QoE Metrics TS 28.622CR0206
- Rel-18 CR TS 28.622 Enhance the ManagementDataCollection to support request management data per PLMN TS 28.622CR0308
- GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] TS 36.331CR4931
- GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] TS 38.331CR4109
- Introduction of Enhancement on NR QoE management and optimizations for diverse services TS 38.331CR4446
- Correction on UE Location Information Reporting in IoT-NTN TS 36.300CR1410
+ 21 more changes
In Release 19, the MIB function was enhanced to support new management capabilities for data management and to introduce new information types for network management. These additions specifically included support for NB-IoT satellite information in E-UTRAN, reporting of Aerial UE Flight Information, and UE assistance information for cell DTX/DRX. Furthermore, clarifications were made regarding historical management data, and support was introduced for Continuous Management-based MDT and the provision of Store-and-Forward Mode Indication.
- Rel-19 CR TS 28.622 Add Enum values for the management capabilities related to data management TS 28.622CR0579
- Introduction of NB-IoT satellite information in E-UTRAN [EUTRAN-to-NBIoTNTN] TS 36.300CR1427
- Introduction of NB-IoT satellite information in E-UTRAN [EUTRAN-to-NBIoTNTN] TS 36.331CR5140
- Support Aerial UE Flight Information Reporting TS 38.300CR1031
- Introduction of UE assistance information for cell DTX/DRX [UAI_cellDTRX] TS 38.331CR5474
- Rel-19 CR TS 28.622 Clarification on historical management data TS 28.622CR0587
+ 3 more changes
In Release 20, the MIB function was updated to add new enumerated values for management capabilities that were missing from the previous Release 19 specification. This enhancement specifically addressed the need to define additional capability classes for network elements within the IRP Information Model. The update ensured the management information base could accurately represent the latest network equipment characteristics and their associated bearer services.
- Rel-20 CR TS 28.622 Add Enum values for missing R19 management capabilities TS 28.622CR0598
Explore further
Broader topics and technologies where MIB plays a role.
Defining Specifications
3GPP specifications that define or reference MIB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.851 v1600 | Network Sharing Architecture for 3G Systems | Rel-6 |
| TS 25.133 vj00 | UTRAN RRM Requirements for FDD | Rel-19 |
| TS 25.221 vj00 | UTRA TDD Physical Layer Specification | Rel-19 |
| TS 25.223 vj00 | UTRA Physical Layer TDD Spreading & Modulation | Rel-19 |
| TS 25.433 vj00 | Node B Application Part (NBAP) Protocol | Rel-19 |
| TS 28.622 vk20 | Telecommunication Management; Generic NRM Information Service | Rel-20 |
| TS 28.701 vj00 | Core Network NRM IRP Requirements | Rel-19 |
| TS 32.101 vj00 | Management principles and high-level requirements | Rel-19 |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 |
| TS 32.122 vj00 | Advanced Alarm Management IRP Information Service | Rel-19 |
| TS 32.123 v1900 | Advanced Alarm Management IRP CORBA Solution Set | Rel-9 |
| TS 32.125 v1930 | AAM IRP XML File Format Definition | Rel-9 |
| TS 32.126 vj00 | AAM IRP Solution Set Definitions | Rel-19 |
| TS 32.301 vj00 | Notification IRP Requirements | Rel-19 |
| TS 32.381 vj00 | Partial Suspension of Itf-N IRP Requirements | Rel-19 |
| TS 32.382 vj00 | Partial Suspension of Itf-N IRP Information Service | Rel-19 |
| TS 32.391 vj00 | Delta Synchronization IRP Requirements | Rel-19 |
| TS 32.600 vj00 | 3GPP Configuration Management Specification | Rel-19 |
| TS 32.601 vj00 | Basic Configuration Management IRP Requirements | Rel-19 |
| TS 32.602 vj00 | Basic Configuration Management IRP Information Service | Rel-19 |
| TS 32.611 vj00 | Bulk CM IRP Requirements | Rel-19 |
| TS 32.612 vj00 | Bulk Configuration Management IRP: Information Service | Rel-19 |
| TS 32.621 vb00 | Generic Network Resources IRP Requirements | Rel-11 |
| TS 32.622 vb10 | Generic Network Resources IRP NRM | Rel-11 |
| TS 32.631 vb00 | Core Network Resources IRP Requirements | Rel-11 |
| TS 32.652 vc00 | GERAN Network Resources NRM for Configuration Management | Rel-12 |
| TS 32.661 vj00 | Kernel Configuration Management IRP Requirements | Rel-19 |
| TS 32.662 vj00 | Configuration Management (CM); Kernel CM IRP | Rel-19 |
| TS 32.690 vj00 | Inventory Management IRP Requirements | Rel-19 |
| TS 32.691 vb00 | Inventory Management IRP Requirements | Rel-11 |
| TS 32.711 vb00 | TN Interface NRM IRP Requirements | Rel-11 |
| TS 32.741 vb00 | STN Interface NRM IRP Requirements | Rel-11 |
| TS 32.832 va00 | Alarm Correlation and Root Cause Analysis Study | Rel-10 |
| TS 32.833 vb00 | Converged OSS End-to-End Management Study | Rel-11 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TS 38.133 vj20 | 5G UE Radio Requirements for RRC_IDLE Mobility | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TR 38.802 ve20 | Study on New Radio Access Technology Physical Layer Aspects | Rel-14 |
| TR 38.912 vj00 | Study on New Radio Access Technology | Rel-19 |