Managed Object

Description

A Managed Object (MO) is a concrete instance of a Managed Object Class (MOC) in the 3GPP management information model. It represents a network resource, function, service, or administrative entity that can be observed and controlled by a management system. In practice, an MO may correspond to a base station, a core network function, a radio bearer, a subscriber profile, a network slice instance, or another manageable element. The MO carries the actual values of attributes, participates in relationships with other MOs, and can emit notifications when events occur. Its standardized definition allows operations support systems (OSS), element managers (EM), and network management functions to interact with heterogeneous equipment without depending on vendor-specific data structures. Architecturally, MOs sit within a layered management model. The MOC defines the schema: attributes, data types, constraints, relationships, actions, and notifications. The MO is the instantiated object created when a network element is deployed or when a resource is allocated. Each MO is uniquely identifiable, typically through a Distinguished Name (DN) composed of Relative Distinguished Names (RDNs), so that management operations can target the correct object. In 3GPP systems, MOs are organized into trees or graphs: containment relationships express ownership or hierarchy, while association relationships express dependencies, such as a cell belonging to a node or a session being associated with a policy profile. This organization supports navigation, filtering, and correlation across network domains. How it works: A management client issues operations such as get, set, create, delete, invoke action, or subscribe to notifications. The target MO processes the operation by reading or modifying attribute values, updating internal state, or triggering a management action. Configuration parameters are stored as attributes; performance counters are collected from MOs; alarms and events are reported as notifications; and relationships allow the management system to understand impact. For example, changing a radio configuration attribute on a cell MO can propagate to the related base station MO, while a fault notification can be correlated with neighboring MOs to identify a root cause. In virtualized and cloud-native networks, MOs may represent software components, containerized functions, or slice instances, preserving the same abstraction across physical and logical resources. The role of MOs is to provide a common vocabulary for network management. Without this abstraction, each vendor would expose proprietary parameters, making integration expensive and automation fragile. Standardized MOs enable multi-vendor OSS interoperability, lifecycle management, service assurance, and closed-loop automation. They also support higher-level management concepts such as self-organizing networks, intent-based management, and network slicing, because the management system can reason about network state as a set of related objects rather than raw data streams. In 3GPP releases, the MO concept has remained central as networks evolve from circuit-switched and packet-switched domains to service-based 5G core architectures. MOs also support validation and consistency. Since each MO is an instance of a MOC, the model can enforce data types, allowed values, cardinality, and dependency rules. This prevents invalid configurations and helps management systems detect anomalies. For instance, an MO representing a security endpoint may require a certificate attribute and an association to an identity management MO. If required attributes are absent, the management function can reject the creation operation or raise an alarm. This object-oriented validation is especially important in large networks where manual configuration is impractical. Finally, MOs serve as anchors for analytics and automation. Performance measurements, fault events, and configuration changes can be associated with MOs, allowing management systems to build a coherent view of network behavior. This object-centric view is useful for root cause analysis, capacity planning, and service-level monitoring. As 3GPP management specifications evolve, MOs remain the fundamental unit through which network state is represented, manipulated, and correlated.

Purpose & Motivation

The Managed Object concept exists because telecommunications networks are composed of many independently managed resources, and operators need a uniform way to represent those resources to management systems. Early mobile networks relied on vendor-specific management interfaces and proprietary data models. While functional, those approaches made multi-vendor integration difficult, complicated service assurance, and limited automation. As networks grew more complex, especially with the introduction of UMTS, IMS, packet core functions, and later virtualized network functions, 3GPP needed a standardized abstraction that could describe network resources in a consistent, extensible manner. MOs solve this problem by turning network elements into manageable objects with defined attributes, relationships, actions, and notifications. A management system can create, modify, monitor, and delete MOs without knowing the internal implementation of the underlying equipment. This separation between the management view and the implementation view is the key motivation. It enables OSS/EM interoperability, supports lifecycle management, and allows performance, fault, and configuration management to operate on a common model. In modern networks, the same abstraction supports automation, analytics, and orchestration, because software and hardware resources can be represented consistently. The concept also addresses operational scale. In large networks, manual inspection of individual parameters is impractical. MOs provide a structured way to correlate resources, identify dependencies, and apply changes in a controlled manner. By standardizing the object abstraction, 3GPP allows management tools to build reusable workflows, validate configurations, and maintain a consistent view of network state across domains.