Description
A managed alarm is a core concept in 3GPP network management, representing an alarm as a managed object within the Network Management (NM) domain. It is defined in specifications such as TS 32.111 (Fault Management) and TS 32.859 (Management and Orchestration). In the 3GPP management architecture, alarms are not simply raw events; they are structured information objects that describe a fault condition, its severity, its source, and its relationships to other managed objects. The managed alarm provides a standardized representation that can be exchanged between Element Managers (EMs) and Network Managers (NMs), enabling consistent fault supervision across multi-vendor networks.
The managed alarm typically includes attributes such as alarm type, probable cause, perceived severity (critical, major, minor, warning), alarm state (active or cleared), and timestamps for raising and clearing. It is associated with a managed object that represents the faulty resource, such as a cell, a bearer, or a network function. The alarm may also include correlation information, allowing the NM to group related alarms and suppress secondary alarms. In the NM domain, the managed alarm is often represented using the Alarm Information Object Class (IOC) defined in TS 32.111, which specifies the attributes and notifications for alarm reporting.
How it works: When a fault occurs in a network element, the element's fault management function detects the condition and generates an alarm notification. This notification is sent to the EM, which may filter, correlate, or enrich it before forwarding it to the NM as a managed alarm. The NM stores the managed alarm in its alarm list and may present it to operators via a graphical interface. The managed alarm remains active until the fault is cleared, at which point a clear notification is sent and the alarm state is updated. The NM can also acknowledge or comment on the alarm, and these actions are reflected in the managed alarm's attributes.
The managed alarm concept is essential for scalable and reliable network operations. It provides a common language for fault reporting across heterogeneous network elements and management systems, enabling operators to monitor large networks efficiently. It also supports automation, as management systems can use the structured alarm information to trigger corrective actions or to feed analytics engines. In the context of 5G and network slicing, managed alarms help ensure that service-level objectives are met by quickly identifying and resolving faults that affect specific slices or services.
In later releases, the managed alarm definition remained stable, reflecting the maturity of the fault management model. However, the surrounding management architecture evolved to support new technologies such as network function virtualization (NFV) and service-based management. The managed alarm remains a foundational building block for 3GPP fault management, and its standardized representation is key to interoperable and automated network operations.
Purpose & Motivation
The managed alarm exists to provide a standardized, structured representation of fault conditions in the Network Management domain. Before standardized alarm models, each network element vendor used proprietary alarm formats, making it difficult for operators to integrate multi-vendor networks and automate fault handling. The managed alarm solves this by defining a common information model for alarms, including attributes, states, and relationships, so that alarms from different sources can be processed uniformly.
Historically, 3GPP developed the managed alarm concept as part of its Fault Management specifications in the early 2000s, building on ITU-T recommendations such as X.733. The goal was to enable interoperable fault supervision across EMs and NMs, reducing integration costs and improving operational efficiency. As networks grew in complexity, the need for correlation and automation became more pressing, and the managed alarm provided the necessary structure for these advanced functions.
In modern networks, the managed alarm is even more important because of virtualization and network slicing. Faults can originate in virtualized network functions, cloud infrastructure, or transport networks, and the ability to represent and correlate these alarms in a consistent way is critical for maintaining service quality. The managed alarm thus remains a key enabler for automated, end-to-end fault management in 3GPP networks.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Managed alarm, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 32.111 vj00 | Fault Management Alarm IRP Solution Sets | Rel-19 read |
| TS 32.859 vc10 | Alarm Management Quality Improvement Study | Rel-12 read |