Matching Criteria Attributes

Description

Matching-Criteria-Attributes is a concept in 3GPP fault management that defines a set of attributes from ITU-T Recommendation X.733 used to determine whether two or more alarm notifications are related to the same network resource and the same alarmed condition. The attributes are: objectInstance, eventType, probableCause, and specificProblem (if present). When notifications carry identical values for these attributes, they are considered to be carrying alarm information about the same resource and condition. This mechanism is fundamental for alarm correlation, suppression, and root cause analysis in network management systems.

The attributes are defined as follows: objectInstance identifies the managed object instance that is the source of the alarm; eventType categorizes the type of event (e.g., communicationsAlarm, qualityOfServiceAlarm); probableCause provides a more specific reason for the alarm; and specificProblem further refines the cause. Together, they uniquely characterize an alarm condition on a specific resource. The matching criteria are used by management systems to group alarms, avoid duplicate notifications, and identify the root cause when multiple alarms are generated.

In 3GPP, these attributes are specified in TS 28.532 for management services and TS 32.111 for fault management. The integration of ITU-T X.733 attributes ensures alignment with international standards and enables interoperability between different vendors' management systems. The matching criteria are typically applied by the Element Manager (EM) or Network Manager (NM) when processing alarm notifications. For example, if a network element sends multiple alarm notifications with the same objectInstance, eventType, probableCause, and specificProblem, the management system can treat them as a single alarm condition and avoid flooding the operator with redundant alerts.

The concept supports advanced fault management functions such as alarm correlation, where alarms from different resources are analyzed to determine a common root cause. It also enables alarm suppression, where subordinate alarms are suppressed if a parent alarm is active. The matching criteria are essential for maintaining a clear and actionable alarm list, especially in large networks with thousands of network elements.

Since its introduction in Release 8, the definition of Matching-Criteria-Attributes has remained largely unchanged. The only notable change occurred in Release 17, where the wording was slightly reformatted, but the substance remained identical. This stability reflects the maturity and fundamental nature of the concept in fault management.

Purpose & Motivation

Matching-Criteria-Attributes exists to provide a standardized way to correlate alarm notifications in a multi-vendor, multi-technology network. Without such criteria, management systems would be overwhelmed by duplicate alarms for the same fault, making it difficult for operators to identify and resolve issues. The attributes allow alarms to be grouped based on the affected resource and the specific problem, enabling efficient fault management.

The concept was introduced in Release 8 as part of the 3GPP fault management framework, which adopted ITU-T X.733 for alarm reporting. Prior to this, alarm correlation was often vendor-specific and lacked interoperability. By defining a common set of matching attributes, 3GPP ensured that management systems from different vendors could consistently interpret and process alarms. This is particularly important in heterogeneous networks where equipment from multiple suppliers is deployed.

The matching criteria also support automated fault management processes, such as alarm suppression and root cause analysis, which reduce operational costs and improve network availability. As networks grow in complexity with the introduction of 5G and network slicing, the ability to correlate alarms across domains becomes even more critical, and Matching-Criteria-Attributes continues to play a vital role.