Managed Object Referring to Test

Description

The Managed Object Referring to Test (MORT) is a fundamental component of the 3GPP's Telecommunications Management Network (TMN) and Network Management (NM) architecture, detailed in the 32-series specifications. It is a specific type of Managed Object (MO) that acts as a logical representation of a test resource within the management information tree. As an MO, it is defined by its attributes, notifications, and operations, which are standardized to ensure interoperability between different Network Elements (NEs) and Element Management Systems (EMSs) or Network Management Systems (NMSs). The MORT provides a standardized interface for the NMS to initiate, configure, control, and retrieve results from various tests performed on the network, such as connectivity checks, performance measurements, or fault diagnostics.

Architecturally, MORTs reside within the Management Information Base (MIB) of a managed network element or a dedicated test system. They are accessed and manipulated via standardized management protocols, primarily the Common Management Information Service/Protocol (CMIS/CMIP) or its successors, using interfaces like the Itf-N. Each MORT instance is uniquely identified and contains attributes that define the test type (e.g., loopback, bit error rate), its current state (idle, in progress, completed), configuration parameters (target address, test pattern, duration), and the results (success/failure, measured values, timestamps). The management system can perform CRUD (Create, Read, Update, Delete) operations on these objects to orchestrate testing workflows.

Its role is critical for automated fault management, performance management, and service assurance. By abstracting physical test procedures into software-managed objects, MORTs enable operators to integrate testing seamlessly into larger OAM workflows, such as automated root cause analysis or service quality validation. For example, when a service degradation alarm is received, the NMS can automatically create and activate a MORT on the suspected network element to run a diagnostic test, parse the results stored in the MORT's attributes, and use that data to pinpoint the fault. This model-driven approach decouples the management logic from the vendor-specific implementation of the test hardware or software, promoting multi-vendor interoperability and streamlined operations.

Purpose & Motivation

MORT was created to address the challenge of non-standardized, vendor-proprietary methods for managing and executing tests in telecommunications networks. Prior to its standardization, network operators relied on ad-hoc, manual procedures or vendor-specific tools to conduct diagnostics and performance tests. This led to operational inefficiencies, increased complexity in multi-vendor environments, and an inability to automate end-to-end testing workflows within a unified management system. The TMN framework aimed to bring order to network management, and MORTs were introduced as a specific solution within the Fault Management and Testing functional areas.

The core problem MORT solves is providing a consistent, object-oriented model for representing any test entity. This allows a generic NMS to command and receive results from tests on equipment from different suppliers without needing custom integrations for each test type or vendor. It formalizes the lifecycle of a test—from creation and configuration to execution and result retrieval—into a standardized management interface. This capability is fundamental for achieving the TMN goals of automated, efficient, and reliable network operations and maintenance (OAM), which directly impacts service availability and quality.

Key Features

• Standardized object model for representing test resources and configurations
• Defined attributes for test type, state, parameters, and results
• Support for management operations: Create, Retrieve, Update, Delete, and actions like Start/Stop test
• Integration into the broader TMN hierarchical management architecture (NMS-EMS-NE)
• Enables automated test invocation and result collection as part of OAM workflows
• Promotes multi-vendor interoperability for network testing and diagnostics

Evolution Across Releases

Defining Specifications