Common Management Information Protocol

Description

The Common Management Information Protocol (CMIP) is an OSI (Open Systems Interconnection) protocol standardized for telecommunications and network management. It operates within the OSI management framework, defining a client-server model where a manager (client) interacts with agents (servers) residing on managed network elements. CMIP uses a connection-oriented transport service, typically over the OSI protocol stack, to ensure reliable delivery of management operations and notifications. The protocol's core strength lies in its sophisticated information model, which is based on managed objects defined using the Guidelines for the Definition of Managed Objects (GDMO). Each managed object represents a resource within the network element, such as a port, circuit, or software process, and possesses attributes, actions it can perform, and notifications it can emit.

Communication in CMIP is facilitated through a set of service primitives. The manager can invoke operations like M-GET to retrieve attribute values, M-SET to modify them, M-ACTION to request an object to perform a specific function, M-CREATE to instantiate new managed objects, and M-DELETE to remove them. The agent, upon detecting significant events like failures or threshold crossings, can asynchronously send notifications (M-EVENT-REPORT) to the manager. These interactions are scoped and filtered, allowing a single request to target multiple managed objects based on complex criteria, which reduces network traffic compared to simpler protocols that require individual queries per attribute.

CMIP's architecture is highly structured and object-oriented, promoting interoperability between multi-vendor management systems and network elements. Its comprehensive service set supports all aspects of the FCAPS (Fault, Configuration, Accounting, Performance, Security) management model. While powerful, CMIP is also complex, requiring significant processing resources and a fully implemented OSI stack. In 3GPP contexts, it was historically specified for certain management interfaces, particularly in early releases for the management of network elements, before a broader industry shift towards Internet-based management protocols like SNMP and NETCONF/YANG for many applications.

Purpose & Motivation

CMIP was created to address the need for a standardized, robust, and comprehensive protocol for managing complex telecommunications networks, which were increasingly multi-vendor and required interoperability. Prior to its development, proprietary management systems were the norm, leading to vendor lock-in, high integration costs, and operational inefficiencies. The OSI management framework, with CMIP as its protocol, aimed to provide a universal solution based on open international standards, enabling seamless management across different types of network equipment from various manufacturers.

The protocol was designed to solve the limitations of simpler management tools, which lacked the granularity, reliability, and sophisticated data modeling required for large-scale, mission-critical telecom networks. CMIP's connection-oriented nature ensured reliable delivery of critical management commands and alarms. Its powerful scoping and filtering capabilities allowed for efficient bulk operations, reducing the management overhead on the network. The object-oriented information model (GDMO) provided a formal, extensible way to represent any network resource, making the system future-proof and capable of managing new technologies as they emerged.

Within the 3GPP ecosystem, CMIP was adopted to fulfill requirements for standardized Operations, Administration, and Maintenance (OAM) interfaces, particularly in the early releases for managing core network and radio access network elements. It provided the necessary rigor and structure for the complex management tasks in 2G and 3G mobile networks, supporting detailed performance monitoring, fault management, and configuration control as defined in 3GPP's specifications for network management.

Key Features

• Object-oriented management model using GDMO for defining managed objects
• Connection-oriented protocol ensuring reliable management communication
• Comprehensive operation set: M-GET, M-SET, M-ACTION, M-CREATE, M-DELETE
• Asynchronous event reporting (M-EVENT-REPORT) for alarms and notifications
• Powerful scoping and filtering to perform operations on multiple objects with a single request
• Full support for the FCAPS (Fault, Configuration, Accounting, Performance, Security) management model

Evolution Across Releases

Defining Specifications