Description
SNMP/SMI is a comprehensive management framework adopted by 3GPP for the Operation, Administration, and Maintenance (OAM) of network elements. It is based on the IETF standards for SNMP (Simple Network Management Protocol) and its associated SMI (Structure of Management Information). The architecture is client-server based, where a central Network Management System (NMS) acts as the manager (client) and the managed network elements, such as NodeBs, eNodeBs, gNBs, or core network functions, act as agents (servers). The manager communicates with agents using SNMP messages (GET, SET, TRAP, etc.) over UDP/IP to retrieve or modify management information.
The core of the framework is the Management Information Base (MIB), which is a virtual database that describes the managed objects within a device. The SMI defines the rules for how these managed objects are named, typed, and structured within the MIB. It uses an Abstract Syntax Notation (ASN.1) subset to define object types and employs a hierarchical tree structure for object identifiers (OIDs). This allows for a standardized, vendor-neutral way to represent parameters like radio link counters, hardware status, software versions, and alarm conditions.
In a 3GPP context, specifications like 3GPP TS 32.101 define the requirements and framework for using SNMP/SMI, often specifying 3GPP-specific MIB modules. The manager polls agents periodically to collect performance data (PM) and receives asynchronous TRAP or INFORM messages for fault management (alarms). This data is crucial for network monitoring, capacity planning, and troubleshooting. The framework's role is to provide a unified, interoperable interface for element management, which is a foundational layer in the Telecommunications Management Network (TMN) model used by operators.
Purpose & Motivation
SNMP/SMI was introduced to address the critical need for standardized, interoperable network management in increasingly complex and multi-vendor 3GPP networks. Prior to its formal adoption, proprietary management interfaces were common, leading to high integration costs, operational inefficiencies, and vendor lock-in for network operators. The framework solves the problem of how to uniformly monitor and control diverse network equipment from different manufacturers.
Its creation was motivated by the success of SNMP in the IP world (IETF). 3GPP recognized the value of a mature, widely understood protocol for managing the IP-based transport and increasingly IP-centric aspects of mobile networks. SNMP/SMI provides a lightweight, flexible mechanism for real-time and periodic management data exchange, which is essential for ensuring network availability, performance, and security. It established a common language (through MIBs) for describing manageable resources, which is a prerequisite for automated OAM systems.
Key Features
- Standardized protocol (SNMPv1, SNMPv2c, SNMPv3) for manager-agent communication
- Structure of Management Information (SMI) for defining managed object syntax and semantics
- Hierarchical Management Information Base (MIB) with unique Object Identifiers (OIDs)
- Support for polling (GET, GETNEXT) and asynchronous event notification (TRAP, INFORM)
- Integration into the 3GPP OAM architecture for Fault, Configuration, Accounting, Performance, and Security (FCAPS) management
- Definition of 3GPP-specific MIB modules for managing radio and core network parameters
Evolution Across Releases
Introduced the SNMP/SMI framework as a standardized management interface within the 3GPP OAM architecture, primarily for managing LTE network elements. It established the use of IETF-based SNMP and SMI standards, with 3GPP TS 32.101 defining the overall requirements and framework for its application in Evolved Packet Core (EPC) and E-UTRAN management.
Defining Specifications
| Specification | Title |
|---|---|
| TS 32.101 | 3GPP TR 32.101 |