Management Information Model

Description

The Management Information Model (MIM) is a cornerstone of 3GPP's network management standardization, providing an abstract, information-centric view of all resources that need to be managed within a 3GPP system. It is not a software implementation but a conceptual schema that defines the structure of management information. The MIM specifies Managed Objects (MOs), which are representations of physical resources (like a base station), logical resources (like a software module), or service-related entities (like a subscriber profile). Each Managed Object is characterized by a set of attributes that hold data (e.g., operational state, administrative state, performance counters), notifications (alarms, state change reports) it can emit, and management operations (e.g., create, delete, set) that can be performed on it.

The architecture of the MIM is hierarchical and uses object-oriented principles. Managed Object Classes are defined, and specific instances of these classes represent actual managed entities in the network. Relationships between objects, such as containment (a Cell is contained within a Base Station) or dependency (a Service depends on a Network Slice), are also formally defined within the model. This structured approach allows management systems to navigate the network's inventory and understand the dependencies between components. The MIM is defined using a formal modeling language, typically based on guidelines from the ITU-T and ISO, which ensures precision and enables the generation of concrete implementation artifacts.

In operation, the MIM serves as the blueprint for the interface between Network Elements (NEs) and management systems like Element Managers (EMs), Network Management Systems (NMS), or Operations Support Systems (OSS). The actual management communication is carried out via protocols like CORBA, SNMP, or more recently, NETCONF/YANG, which carry data structured according to the MIM's definitions. For example, a fault management system receives notifications (alarms) defined as attributes of specific MOs, while a configuration management system manipulates attribute values to change the behavior of network resources. The MIM's role is to ensure that all parties in the management ecosystem—vendors implementing network elements and vendors building management systems—share a common understanding of what is being managed and how, enabling multi-vendor interoperability and simplified integration.

Purpose & Motivation

The MIM was created to solve the critical problem of interoperability and complexity in managing multi-vendor telecommunications networks. In the early days of mobile networks, each equipment vendor provided proprietary management interfaces and data models for their network elements. This made it extremely difficult for operators to integrate equipment from different vendors into a unified Operations Support System (OSS), leading to high operational costs, manual processes, and vendor lock-in. The purpose of the 3GPP MIM is to define a single, standardized, technology-agnostic information model that all vendors must adhere to for their managed products.

This standardization, initiated in earnest from 3GPP Release 4 onwards, was motivated by the operational demands of large-scale GSM and UMTS networks and became even more critical with the introduction of 3G and later technologies. It addresses the need for a common language for network management, allowing an operator's NMS to configure, monitor, and fault-manage a base station from Vendor A using the same logical model and operations as a base station from Vendor B. By abstracting the management view from the underlying implementation, the MIM enables automation, reduces integration time for new network elements, and forms the foundation for standardized Northbound Interfaces (NBIs) from EMS to NMS. Its creation was a fundamental step towards achieving the Telecom Management Network (TMN) layered architecture goals within the 3GPP context.

Key Features

• Defines Managed Object Classes representing physical/logical resources and services
• Specifies attributes, operations, notifications, and behaviors for each Managed Object
• Formally models relationships between objects (containment, dependency)
• Provides a technology-agnostic and vendor-neutral framework for management data
• Serves as the foundation for implementing standardized management interfaces (Itf-N, Itf-S)
• Enables multi-vendor interoperability for Fault, Configuration, Accounting, Performance, and Security (FCAPS) management

Evolution Across Releases

Defining Specifications