Common Management Information Service

Description

The Common Management Information Service (CMIS) is a cornerstone of the 3GPP Telecommunications Management Network (TMN) framework, providing the standardized application-layer service definitions for network management. It is based on the ITU-T X.700 series recommendations and the OSI Systems Management model. CMIS defines a set of generic services, such as M-GET, M-SET, M-ACTION, M-CREATE, M-DELETE, and M-EVENT-REPORT, which are used to manipulate and observe managed objects. These managed objects are abstract representations of physical or logical network resources (e.g., a port, a software process, a performance counter) defined in a Management Information Base (MIB). The services operate over the Common Management Information Protocol (CMIP), which provides the reliable transfer of management requests and notifications.

Architecturally, CMIS operates in a manager-agent model. The managing system (the manager) invokes CMIS operations on a managed system (the agent), which contains the managed objects. The agent performs the requested operation on the local MIB and returns a response. For example, a manager can use M-GET to retrieve a performance measurement or M-SET to modify a configuration parameter. Event reporting is asynchronous, where an agent uses M-EVENT-REPORT to notify the manager of significant occurrences like faults or threshold crossings. This decouples the management logic from the underlying communication details.

CMIS's role is to provide a rich, object-oriented, and semantically powerful interface for management. Its strength lies in its scoping and filtering capabilities, which allow a single operation to act upon multiple managed objects that match specific criteria, reducing network traffic compared to simplistic request-response protocols. It supports confirmed and non-confirmed service modes, offering flexibility for different management scenarios. While CMIP/CMIS is often associated with the OSI protocol stack, in 3GPP contexts, these services can be mapped to different underlying transports, and the information model is crucial for defining how network elements are managed in a standardized way across the 3GPP system.

Purpose & Motivation

CMIS was created to address the critical need for multi-vendor interoperability and efficient, standardized management of complex telecommunications networks. Prior to its adoption, network management was often proprietary, with each equipment vendor providing unique interfaces and protocols. This made integrating management systems for networks built with equipment from multiple suppliers extremely difficult, costly, and error-prone, leading to operational inefficiencies and high lifecycle costs.

The purpose of CMIS, as part of the broader TMN framework, is to provide a unified, technology-neutral service layer for all management activities. It solves the problem of semantic disparity by defining a common language and set of operations (the services) that all compliant network elements must support. This allows a single network management system (NMS) to configure, monitor, and receive alarms from diverse network elements—such as base stations, switches, and routers—using the same consistent methodology. Its creation was motivated by the move towards open systems and the operational demands of large-scale public networks where reliability and manageability are paramount.

By abstracting resources as managed objects with defined attributes, actions, and notifications, CMIS enables powerful and automated management workflows. It supports the comprehensive FCAPS (Fault, Configuration, Accounting, Performance, Security) management model, which is essential for maintaining service quality and operational health. Although newer management technologies like SNMP and NETCONF/YANG have gained popularity in certain domains due to their simplicity, the CMIS service definitions and their underlying object-oriented information modeling principles remain influential in the design of 3GPP management interfaces, ensuring a robust foundation for managing the complex relationships and behaviors in mobile networks.

Key Features

• Standardized object-oriented management service primitives (M-GET, M-SET, M-ACTION, etc.)
• Powerful scoping and filtering to perform operations on multiple managed objects simultaneously
• Support for both confirmed and non-confirmed service modes for flexible interaction
• Asynchronous event reporting (M-EVENT-REPORT) for alarms and notifications
• Integration with the 3GPP Telecommunications Management Network (TMN) framework and architecture
• Foundation for defining managed objects and behaviors in 3GPP Management Information Bases (MIBs)

Evolution Across Releases

Defining Specifications