Suspended Notification

Description

A suspended notification is a management concept defined by 3GPP as a notification which would be sent under normal circumstances via Itf-N, but is not because a corresponding suspension request was previously received. Itf-N is the northbound interface between a 3GPP network management system (NMS) and an element manager (EM) or between an EM and a network element (NE). Suspended notifications are part of the fault management, configuration management, and performance management capabilities of 3GPP networks.

In 3GPP management architecture, notifications are used to inform management systems about events such as alarms, configuration changes, or performance threshold crossings. However, there are scenarios where a management system may want to temporarily suppress notifications to avoid flooding or to perform maintenance. A suspension request is sent to the notification producer (e.g., an EM or NE) to stop sending notifications for a specified period or until a resume request is received. During this suspension period, any notification that would have been sent is considered a suspended notification.

The concept is specified in 3GPP specifications 32.381, 32.382, 32.383, 32.386, and 32.387, which cover various aspects of management. These specifications define the procedures for suspending and resuming notifications, the format of suspension requests, and the handling of suspended notifications. The suspension request typically includes parameters such as the notification type, the scope of suspension (e.g., specific managed objects), and the duration. The notification producer must honor the suspension request and not send the corresponding notifications.

Suspended notifications are important for managing network operations efficiently. For example, during a software upgrade or a network reconfiguration, a large number of notifications might be generated, overwhelming the management system. By suspending notifications, the operator can perform maintenance without being flooded with alarms. After the maintenance is complete, the operator can resume notifications, and the management system can retrieve any missed notifications or simply continue from the current state.

The handling of suspended notifications may vary depending on the specific management function. In some cases, suspended notifications are discarded and not stored; in others, they may be logged or buffered for later delivery. The 3GPP specifications define the expected behavior to ensure interoperability between different vendors' management systems. The concept is part of the broader 3GPP management framework, which includes integration reference points (IRPs) and the Itf-N interface.

Purpose & Motivation

The suspended notification concept was introduced to provide a mechanism for controlling the flow of management notifications in 3GPP networks. Before this, management systems had no standardized way to temporarily stop notifications, which could lead to notification storms during network events such as mass configuration changes or failures. Such storms could overwhelm the management system, causing it to miss critical alarms or become unresponsive. The suspension mechanism allows operators to suppress notifications during planned activities, ensuring that the management system remains stable and responsive.

The concept solves the problem of notification overload and provides a way to coordinate maintenance activities. By allowing a management system to request suspension, it enables operators to perform tasks such as software upgrades, hardware replacements, or network optimization without being distracted by a flood of notifications. It also helps in scenarios where the management system itself is being upgraded or restarted. The suspension request can be scoped to specific managed objects or notification types, providing fine-grained control.

Historically, the suspended notification concept was introduced in Release 8 as part of the evolution of 3GPP management specifications. It addressed the growing complexity of networks and the need for more sophisticated management capabilities. The term has remained stable across releases, with the definition unchanged, reflecting its fundamental role in management systems. It is closely related to other management concepts such as notification filtering, alarm correlation, and heartbeat mechanisms.