Guidelines for the Definition of Managed Objects

Description

Guidelines for the Definition of Managed Objects (GDMO) is a formal specification language standardized by ITU-T in recommendation X.722 and adopted within 3GPP specifications for network management. It provides the foundational methodology for defining managed objects, which are abstract representations of physical or logical network resources such as network elements, software modules, or connections. A managed object is characterized by its attributes, which hold state information; its operations, which are actions that can be performed on it (like GET, SET, or notifications); and its behaviors, which define how the object responds to operations and internal events. GDMO uses an object-oriented approach, allowing for inheritance, where new object classes can be defined as extensions of existing ones, promoting reusability and a hierarchical management information structure.

The architecture of a GDMO-based Management Information Base (MIB) is central to network management systems like the Telecommunications Management Network (TMN) framework. The definitions created using GDMO are compiled into an Abstract Syntax Notation One (ASN.1) representation, which serves as the machine-readable schema for the managed objects. These objects are then accessed via management protocols, primarily the Common Management Information Protocol (CMIP), although adaptations for SNMP exist. The key components of a GDMO definition include the object class template, which names the class and specifies its superclasses; the attribute templates, which define the properties; the action and notification templates for operations; and the parameter templates for data structures.

In a 3GPP network, GDMO is used extensively to define the managed objects for Network Elements (NEs) across various domains, including the Network Management (NM), Domain Management (DM), and Element Management (EM) layers. For instance, specifications like 3GPP TS 32.102 (Telecommunication management architecture) and TS 32.150 (Integration Reference Point (IRP) concept and definitions) rely on GDMO principles to ensure that management data from a Base Station or a Core Network function is modeled consistently. This consistency allows Operations Support Systems (OSS) to manage heterogeneous equipment from different vendors through a unified interface, abstracting the vendor-specific implementations behind a standardized object model. The role of GDMO is therefore to provide the semantic and syntactic rigor necessary for interoperable, scalable, and automated fault, configuration, accounting, performance, and security (FCAPS) management in complex 3GPP networks.

Purpose & Motivation

GDMO was created to address the critical challenge of multi-vendor interoperability in large-scale telecommunications networks. Prior to its standardization, network management was often proprietary, with each equipment vendor providing unique management interfaces and data models. This made it extremely difficult and costly for network operators to integrate systems from different suppliers into a cohesive Operations Support System (OSS), leading to operational inefficiencies, higher integration costs, and vendor lock-in. The ITU-T's TMN framework, conceived in the 1980s, envisioned a layered, standardized approach to management, and GDMO emerged as the essential modeling language to realize this vision by providing a common way to describe any manageable resource.

The historical context lies in the evolution from simple, protocol-centric management (like SNMP's simple variable bindings) towards a more robust, object-oriented, and transaction-oriented model required for complex telecom equipment. SNMP's MIB structure, defined using SMI, was found lacking for the sophisticated behaviors and rich relationships needed in telecom networks. GDMO, coupled with CMIP, offered a more powerful alternative, supporting complex operations, scoping, filtering, and confirmed event reporting. Its adoption by 3GPP, particularly for the management of 3G UMTS and subsequent networks, was driven by the need for a rigorous, future-proof foundation for defining all management information, from physical hardware inventory to software performance counters and service-level parameters.

While newer management paradigms like NETCONF/YANG have gained prominence for web-based and data-model-driven management, GDMO's purpose in establishing a formal, object-oriented foundation remains historically significant. It solved the fundamental problem of how to unambiguously define what can be managed in a network, separating the information model from the communication protocol. This enabled the creation of standardized Integration Reference Points (IRPs) in 3GPP, allowing management systems to interact with network elements in a predictable, vendor-neutral manner, which is a cornerstone of modern automated network operations.

Key Features

• Object-oriented modeling for network resources using formal class definitions
• Support for inheritance, allowing new managed object classes to extend existing ones
• Definition of attributes, actions, notifications, and behaviors within standardized templates
• Tight integration with ASN.1 for precise data type and encoding specification
• Protocol-neutral information model, primarily designed for use with CMIP
• Enables the creation of a standardized, hierarchical Management Information Base (MIB)

Evolution Across Releases

Defining Specifications