Managed Object

Description

A Managed Object (MO) is a fundamental concept in 3GPP management architecture, defined in specifications such as TS 32.101, TS 32.102, and TS 32.150. It represents an entity used to convey information within a Solution Set. The MOs are the result of a mapping process from Information Objects defined in an Information Service (IS), taking into account engineering choices and technology specificity. In simpler terms, an MO is a logical representation of a network resource or service that can be managed, such as a cell, a carrier, a radio access technology, or a network slice. MOs are used in the context of the Integration Reference Point (IRP) framework, which defines how management systems interact with network elements.

The 3GPP management architecture is based on the Telecom Management Network (TMN) model, which separates management into layers: network element management layer, network management layer, service management layer, and business management layer. The IRP framework provides a set of specifications for interfaces between these layers. The Information Service (IS) defines the information model, which is technology-independent and describes the information objects and their relationships. The Solution Set (SS) defines how these information objects are mapped to specific technologies, such as CORBA, XML, or SOAP. The MOs are the technology-specific representations of the information objects in a Solution Set.

For example, an Information Object might represent a generic 'Cell' with attributes like cell identity, frequency, and transmit power. The mapping to a Managed Object would then specify how this Cell is represented in a specific technology, such as an XML schema or a CORBA interface. The MO includes details such as the object class, its attributes, operations, notifications, and relationships to other MOs. The Managed Object is typically defined in a Management Information Base (MIB) or a Management Object Model (MOM). In 3GPP, the MOs are often described using UML (Unified Modeling Language) and are published in TS 32.150 series specifications.

The management of MOs involves operations such as creation, deletion, modification, and retrieval of attributes. These operations are performed by a manager (e.g., an Element Manager or Network Manager) on an agent (e.g., a Network Element). The IRP framework defines the operations and notifications that can be performed on MOs. For instance, a manager can create a new MO to represent a newly deployed cell, or modify its attributes to change its configuration. Notifications are used to report events, such as a cell going down or a configuration change. The MOs also support bulk operations, such as bulk creation, to efficiently manage large numbers of objects.

The concept of MOs is crucial for interoperability and automation in network management. By standardizing the MO definitions, 3GPP ensures that management systems from different vendors can interoperate, reducing integration costs and enabling multi-vendor networks. MOs also facilitate the development of northbound interfaces, allowing operators to integrate their management systems with higher-level OSS/BSS systems. In the context of 5G, MOs are extended to support new features like network slicing, where a Network Slice is represented as a Managed Object with associated attributes and relationships.

In summary, a Managed Object is a technology-specific representation of a network resource or service that can be managed. It is derived from Information Objects through a mapping that considers engineering choices and technology specificity. MOs are essential for the standardized management of 3GPP networks, enabling interoperability, automation, and efficient operations.

Purpose & Motivation

The concept of Managed Objects was introduced to provide a standardized way to represent and manage network resources in a multi-vendor environment. In early networks, each vendor had its own proprietary management interfaces, leading to high integration costs and operational complexity for operators. The 3GPP management framework, based on IRPs, aimed to create open interfaces that allow management systems to manage network elements from different vendors uniformly. Managed Objects are the building blocks of this framework, providing a common language for describing network resources.

The mapping from Information Objects to Managed Objects allows for technology independence. The Information Service defines what information is needed to manage a resource, while the Solution Set defines how that information is represented in a specific technology. This separation enables the same information model to be reused across different technologies and releases. It also allows for evolution over time, as new technologies can be supported by defining new Solution Sets without changing the Information Service. This flexibility is crucial as networks evolve from 2G to 3G, 4G, and now 5G.

Furthermore, Managed Objects enable automation and programmability. With standardized MOs, management functions can be automated using scripts or orchestration tools. For example, a network slice can be instantiated by creating a set of MOs that represent the slice and its components. This is particularly important for 5G, where network slicing and automation are key requirements. The MO concept also supports the integration of management with SDN (Software-Defined Networking) and NFV (Network Function Virtualization), where virtualized resources are managed as MOs. Overall, Managed Objects are fundamental to achieving interoperable, efficient, and automated network management in 3GPP systems.