EP1668822B1 - Method for synchronizing alarms in a management system of a communications network - Google Patents

Abstract

The invention relates to a method for handling alarms via a management network of a communications system, whereby the management network comprises at least two management centers (NMC, OMC) in different management levels. At least one of the at least two management centers functions as an element manager (OMC) and at least one of the at least two management centers functions as a network manager (NMC) that is assigned to and of a higher ranking than the element manager (OMC) in its function as agent. According to the invention: an alarm is mapped onto a functional object class in the element manager (OMC) while taking an object model into consideration at the interface (NM-EM) between the network manager (NMC) and element manager (OMC); the alarm is relayed from the element manager (OMC) to the network manager (NMC); the alarm is handled in the network manager (NMC), and a synchronization of the alarm status between the network manager (NMC) and the element manager (OMC) ensues in the element manager (OMC) using an operation that is the uniform for the interface (NM-EM) between the network manager (NMC) and the element manager (OMC) in the communications system.

Description

The invention relates to a method for the treatment of alarms in a management system of a communication network according to the preamble of claim 1.

The invention further relates to an element manager of a management system of a communication network for the treatment of alarms according to the preamble of claim 8.

Finally, the invention relates to a communication system for the treatment of alarms by a management network according to the preamble of claim 12.

The principles of telecommunication network management, also referred to as TMN (Telecommunications Management Network) principles, define several management layers for the management of the telecommunications network - for example, a mobile communication network - with each layer except the top and bottom lowest layer has a double function. In the managing system, each level except the bottom one performs a manager function for the level below. In the managed system, each layer except the top one has an agent function for the next higher layer.

Individual devices or elements of the telecommunications network (network resources) exercise the role of an agent in a TMN hierarchy. Agents must recognize relevant events (so-called events, eg alarms) in the network as quickly as possible, generate corresponding messages - so-called notifications - and send these event reports ( event reports ) Transfer managers to enable efficient network management.

The management network of a communication network usually comprises at least two management devices in different management levels, wherein at least one of the at least two management devices act as an element manager and at least one of the at least two management devices as a manager of the parent network manager.

Element managers act as managers at a lower level and act as agents with regard to the next level of management of the network managers.

A manager starts so-called operations ( requests that are executed in agents) for network monitoring and control and receives corresponding responses. An agent detects relevant network events ( events, eg alarms), generates notifications (so-called notifications ) and transmits these as event reports to the manager to enable efficient network management.

Such a management network for an agent-manager relationship mobile communication network includes, for example, operation and maintenance centers (OMC) and multiple network management centers (NMC). In addition, for example, a management level of the management network including the network element level with multiple base station systems may be provided. For example, at the network element management level, operations and maintenance centers may each provide the vendor-specific management functionality for, for example, individual base stations of the base station system. At the network management level, network management centers each implement an integrated, as a rule manufacturer-independent management functionality. In this case, several network management centers may have access to the same network device of the next lower management level, the network element management level, for example the network management centers to at least one operating and maintenance center of the next lower management level.

Between the network devices of different management levels conventionally defined interfaces are provided for the information transmission in the manager-agent communication, so-called management interfaces, in an object-oriented environment by a communication protocol (eg CMIP (Common Management Information Protocol according to ITU-T X.711) or CORBA (Common Object Request Broker Architecture)) and an object model. Such interfaces exist, for example, between Network Element Management and Network Element level (eg OMC-BSS (BSS Base Station Subsystem) in a GSM mobile radio network) or between Network Management and Network Element Management level (eg NMC-OMC ).

The optimal management of a telecommunications network requires that only the relevant event messages from the subordinate agents are forwarded as quickly as possible to manager systems. Under normal conditions, ie when communication between agents and managers work, this occurs over a present in Agent filter mechanism (for example in a CMIP-based management interface with the aid of Event Forwarding discriminator, EFD's so-called ITU-T X.734 " Systems Management: Event Report Management Function " ) .

The task of these filters is to forward by appropriate tests only those notifications to the manager, which meet certain criteria. A manager is able to set up or delete such filters in the agent and the Specify filter criteria. This allows each manager to control the flow of information according to his individual requirements at all times.

The management network considered below in particular comprises at least two management devices in different management levels, wherein at least one of the at least two management devices functions as an element manager and at least one of the at least two management devices functions as an agent and superordinate network manager as the element manager in its function as agent.

The document DE 198 01 785 A1 describes a method for the treatment of alarms in a communication system. A manager sends a message requesting an alert reconciliation to an agent. The message contains a parameter by which the alarm data synchronization is controlled. The alarm data synchronization takes place when the communication between manager and agent is restored after the connection has been interrupted. Upon receiving the request, the agent successively sends the requested alarms to the manager.

The document US 2003/0162537 A1 describes a management system which as a manager comprises a manufacturer-independent device. An agent receives vendor-dependent information that is transmitted to the vendor-independent manager in a vendor-independent format.

The ITU-T (International Telecommunications Union - Telecommunication standardization sector) Series X. 73x defines various system management functions for the management of telecommunications networks, which are used by application processes in a centralized or decentralized management environment can. The fault management (fault management) and the handling of alarms (alarm handling) as one of the The most important network monitoring and control functions take place with the help of management systems (management systems). The management facilities may be located in particular at the Network Element Management level (eg OMC, Element Manager) or Network Management level (eg NMC, Network Manager).

In a telecommunications network, there are usually a large number of network resources that can be modeled as so-called object instances (MOI Management Object Instance ) and generate alerts. Each alarm is thus generated due to at least one event in at least one network resource of the communication network. There are different types of relationships between different network resources such that, for example, an event in a network resource has a number of other events in the network resource same and / or may result in other network resources of a network entity.

• Die "Network Element Management"-Ebene (EM-Ebene), deren Funktionalität von (regionalen) Element Managers (üblicherweise OMCs genannt) realisiert wird, die in der Regel vom gleichen Hersteller wie die dazugehörigen Netzeinrichtungen bzw. Netzelemente (Network Elements, NE) geliefert werden. Die OMCs müssen alle hersteller-spezifischen Eigenschaften der Netzelemente (d.h. auch die entsprechenden Hardware-Merkmale) berücksichtigen.
• Die "Network Management"-Ebene (NM-Ebene), deren Funktionalität von einem Netzwerk Manager (üblicherweise NMC genannt) realisiert wird, der auch von einem Dritt-Hersteller geliefert werden kann. Um eine funktionale Integration hersteller-spezifischen Netzregionen unter einem einheitlichen NMC zu ermöglichen, muss die Schnittstelle zwischen NMC und den (regionalen) OMCs hersteller-unabhängig sein.

From an operational point of view, two management levels are of great importance for the management of an entire telecommunications network:

• The "Network Element Management" level (EM level), the functionality of which is realized by (regional) element managers (usually called OMCs), usually from the same manufacturer as the associated network devices ( Network Elements, NE) to be delivered. The OMCs must take into account all manufacturer-specific properties of the network elements (ie also the corresponding hardware features).
• The "Network Management " level (NM level), the functionality of which is realized by a network manager (usually called NMC), which can also be supplied by a third party manufacturer. In order to enable functional integration of manufacturer-specific network regions under a single NMC, the interface between NMC and the (regional) OMCs must be manufacturer-independent.

The manufacturer independence of the OMC NMC interface can be ensured in an object-oriented management environment by the exclusive use of so-called function-related object classes (MOC (Management Object Class)). The functional objects model the network resources of a telecommunications network from a functional, vendor-independent point of view.
In contrast, the manufacturer-specific interface between OMC and the network elements (eg BSS (Base Station System) and SSS (Switching Sub-System) in a GSM network ) also knows so-called hardware-related object classes ( equipment-related MOC), which varies from manufacturer to manufacturer are. In this management hierarchy, each vendor-specific OMC plays a dual role: managers for the NEs and agent for the parent NMC.

• Auf der EM-Ebene, d.h. an einem hersteller-spezifischen OMC-System (das jeweils für eine Netzregion zuständig ist) üblicherweise an den Werktagen. Die Statusänderung eines Alarms wird in diesem Fall üblicherweise automatisch über eine entsprechende Ereignismeldung dem NMC mitgeteilt.
• Auf der NM-Ebene, d.h. an einem NMC-System, üblicherweise während der Zeit, wenn die OMCs umbesetzt sind, z. B. nachts oder an den Wochenenden. Wird hier der Status eines Alarms durch den Operator verändert, muss der untergeordnete Element Manager automatisch synchronisiert werden, damit alle Management-Systeme den gleichen Informationsstand erhalten. Für eine solche Synchronisierung definieren die jetzigen 3GPP Standards der TS 32.xxx-Reihe unterschiedliche Operationen, in denen die betroffenen Alarme einzeln spezifiziert werden müssen.
  Für eine größere Anzahl von behandelten Alarmen ist diese Art von Synchronisierung weder für die NM-EM Schnittstelle noch für die OMCs effizient.

The treatment of alarms can basically be done at both management levels:

• At the EM level, ie a manufacturer-specific OMC system (each responsible for a network region) usually on working days. In this case, the status change of an alarm is usually communicated automatically to the NMC via a corresponding event message.
• At the NM level, ie at a NMC system, usually during the time when the OMCs are relocated, e.g. At night or at weekends. If the status of an alarm is changed by the operator here, the subordinate element manager must be synchronized automatically so that all management systems receive the same level of information. For such synchronization, the current 3GPP standards of the TS 32.xxx series define different operations in which the affected alarms must be individually specified.
  For a larger number of handled alarms, this type of synchronization is not efficient for either the NM-EM interface or the OMCs.

• Für jede Art von Alarmbehandlung (Bestätigung (acknowledgement), Rücknahme der Bestätigung (unacknowledgement), Deaktivierung (clearing), Zuweisung von Alarmhinweisen (set comments)) wird eine andere Operation (mit jeweils anderer Syntax) definiert.
• Jeder zu synchronisierende Alarm muss in der Operation durch eine eindeutige Kennung identifiziert werden.

Synchronizing alarms at the EM level after changing the alarm status at the NM level is specified in the 3GPP standards of the TS 32.xxx series as follows:

• For each type of alarm treatment ( acknowledgment ), unacknowledgement , clearing, set comments ) becomes another Operation (each with a different syntax).
• Each alarm to be synchronized must be identified in the operation by a unique identifier.

Thus, in particular, a synchronization of a larger number of treated alarms designed as consuming.

The invention has for its object to provide a method, an element manager and a communication system of the type mentioned, by which the synchronization can be simplified and in particular it is possible that a simultaneous synchronization of several, treated at the NM level alarms with the OMC systems can be done.

This object is achieved according to the invention in terms of the method by the features of claim 1, with respect to the element manager by the features of claim 8 and in terms of the communication system by the features of claim 12. Further developments and refinements of the invention are to be taken in particular from the dependent claims.

• im Element Manager (OMC) unter Berücksichtigung eines Objektmodells an der Schnittstelle zwischen Netzwerk Manager und Element Manager ein Alarm auf eine funktionale Objektklasse abgebildet,
• der Alarm vom Element Manager zum Netzwerk Manager weitergeleitet,
  im Netzwerk Manager der Alarm behandelt
  und
• es erfolgt eine Synchronisierung des Alarmstatus zwischen Netzwerk Manager und Element Manager im Element Manager anhand einer für die Schnittstelle zwischen Netzwerk Manager und Element Manager im Kommunikationssystem einheitlichen Operation.

According to the invention

• in the Element Manager (OMC), taking into account an object model at the interface between Network Manager and Element Manager, an alarm is mapped to a functional object class,
• the alarm is passed from the Element Manager to the Network Manager,
  treated in the network manager the alarm
  and
• There is a synchronization of the alarm status between the Network Manager and the Element Manager in the Element Manager by means of an interface between Network Manager and Element Manager in the communication system unified operation.

This approach allows for improved handling of alerts with respect to synchronization by providing a generic, vendor-independent mechanism not only for GSM (Global System for Mobile communication) and UMTS (Universal Mobile Telecommunication System) mobile radio Networks, but also for the management of any telecommunications networks can be used. The invention allows for handling alarms on the management systems that perform functions of various levels of management, such as network element management or network management. Typically, there are a variety of network element managers (e.g., OMCs) and a variety of network managers (e.g., NMCs).

The inventive method is basically used for all telecommunications networks. This explicitly includes straight non-wired telecommunications networks. Especially mobile networks require effective error management.

In the element manager in its logical function part according to the management functionality, network element managers receive incoming alarms from a network element and pass them to the logical function part according to the management functionality as agent to the network manager before forwarding to the network manager. Information about the alarm can be stored in both logical functional parts. The forwarding of the alarm from the Element Manager is not mandatory for all alarms, but usually for those alarms relevant to the Network Manager. These are mapped to a functional object class in the Element Manager before being forwarded to the Netwerk Manager. Sending to the network Manager preferably takes place substantially in real time, ie without too much delay. As a rule, the alarm is forwarded to the network manager via a filter device (eg EFD). The transmission to the network manager can take place by means of adjustable and / or variable filter devices. In particular, for example, the effect of the filter devices can be made adjustable and / or variable, especially with regard to the management system. As a filter device within the scope of the invention, a so-called Event Forwarding Discriminator (EFD ) can preferably be used. The task of the filter device in this functionality (event reporting according to ITU-T X. 734) is to route only those messages (event reports) to the manager which satisfy certain filter criteria. The manager is able to set up or delete such EFDs in the agent and set the filter criteria (via the discriminatorConstruct attribute). This allows each manager to control the flow of information according to his individual needs at all times. The filtering facility in the Element Manager can usually be set up, deleted, and / or set by the network manager for its job content by the network manager.

In an advantageous embodiment of the invention, the element manager at least temporarily stores information concerning the content of the incoming at the element manager and / or of the imaged taking into account the object model at the interface between the network manager and element manager on a functional object class alarm. Preferably, use is made of both options. This includes, with regard to the second possibility, that advantageously in the element manager (eg OMC) as event messages incoming alarms to the corresponding functional object class according to the information model of the interface between Element Manager (in the Function as agent) and network manager (eg NMC in the function as manager).

In particular, the at least temporarily stored information may comprise an alarm list of alarms arriving in the element manager and an alarm list of alarms mapped to a functional object class taking into account the object model at the interface between the network manager and the element manager.

Preferably, the information stored in the element manager concerning the content of the element manager incoming and / or of the object model at the interface between the network manager and element manager mapped to a functional object class alarm is used at least partially in the synchronization by means of the unitary operation.

In a development of the invention, an object instance as the reference entity for the functional object class, to which the alarm was mapped taking into account the object model at the interface between the network manager and element manager, is transmitted from the network manager to the element manager for synchronization by means of the uniform operation becomes. In particular, the incoming alarms in the Element Manager are converted to the corresponding functional object class according to the information model of the interface between Element Manager and Network Manager.

This method can be further developed by taking into account the information stored in the Element Manager regarding the content of the incoming in the Element Manager and / or of the object model at the interface between Network Manager and Element Manager on a functional object class mapped alarm synchronization a regression to one Object instance of the object model is done at the interface between element manager and network element.

In particular, it can be provided that during the synchronization also one, several or all object instances, which in the object tree of the object model at the interface between element manager and network element below the reference instance according to the object model at the interface between the network manager and element manager corresponding object instance the object model at the interface between Element Manager and Network Element.

• Das Verfahren definiert einen einheitlichen, optimierten Mechanismus für die Synchronisierung von mehreren Alarmen auf EM-Ebene nach deren unterschiedlichen Bearbeitung auf NM-Ebene. Sowohl die Verarbeitungsleistung im Agenten (OMC) als auch der Durchsatz der NM-EM Management-Schnittstelle wird deutlich verbessert.
• Als Grundlage des Verfahrens dient eine für beide Kommunikationsrichtungen (d.h. vom Element Manager zum Netzwerk Manager und in umgekehrter Richtung vom Netzwerk Manager zum Element Manager) verwendbare Bearbeitung (kann als "Mapping function" bezeichnet werden) von Alarmen unter Berücksichtigung unterschiedlicher Objektmodelle in einer Management-Hierarchie.

The method according to the invention has the following advantages in particular:

• The method defines a uniform, optimized mechanism for synchronizing multiple alarms at the EM level after their different processing at the NM level. Both the processing power in the agent (OMC) and the throughput of the NM-EM management interface are significantly improved.
• The basis of the method is a processing that can be used for both communication directions (ie from the element manager to the network manager and vice versa from the network manager to the element manager) (can be referred to as a "mapping function" ) of alarms taking into account different object models in a management system. Hierarchy.

• Mittel zum Abbilden eines Alarm auf eine funktionale Objektklasse unter Berücksichtigung eines Objektmodells an der Schnittstelle zwischen Netzwerk Manager und Element Manager,
• Mittel zum Weiterleiten des Alarms vom Element Manager zum Netzwerk Manager und
• Mittel zum Synchronisieren des Alarmstatus zwischen Netzwerk Manager und Element Manager im Element Manager anhand einer für die Schnittstelle zwischen Netzwerk Manager und Element Manager im Kommunikationssystem einheitlichen Operation nach einer Behandlung des Alarms im Netzwerk Manager

vorhanden.The element manager of a management system of a communication network for handling alarms in the management system of the communication network as one of at least two management devices of the management network in different management levels is adapted to associate with the element manager in its function as agent a network manager. In element manager are according to the invention

• Means for mapping an alarm to a functional object class taking into account an object model at the interface between the Network Manager and Element Manager,
• Means for forwarding the alarm from the Element Manager to the Network Manager and
• Means for synchronizing the alarm status between the Network Manager and Element Manager in the Element Manager using a common operation for the interface between Network Manager and Element Manager in the communication system after handling the alarm in the Network Manager

available.

Furthermore, means may be provided for at least temporary storage of information concerning the content of the incoming in the element manager and / or of the displayed on the basis of the object model at the interface between Network Manager and Element Manager on a functional object class alarm.

The Element Manager may also include means for sending alarms received in the Element Manager to the Network Manager.

In particular, the element manager may have adjustable and / or variable filter devices in its operation.

Finally, the element manager may receive means for receiving an object instance as a reference instance for the functional object class mapped to the network object manager interface manager and element manager interface, the network manager interlocked synchronization synchronization message from Network Manager included.

The element manager may be provided with further means for performing the methods described above.

The communication system according to the invention for the treatment of alarms by a management network with at least two management devices in different management levels is designed such that at least one of the at least two management devices as element manager and at least one of the at least two management devices as the element manager in its function as an agent and parent network manager. It may comprise means for carrying out the methods described above. In particular, it may contain an element manager as explained above.

The invention will be explained in more detail by means of embodiments with reference to figures.

Fig. 1

ein Blockschaltbild eines Managementnetzes für ein Kommunikationssystem mit Agent-Manager-Beziehung zwischen Netzelementen, Betriebs- und Wartungszentren und einem Netzwerkmanagementzentrum,

Fig. 2

eine schematische Darstellung eines Managementnetzauschnittes für ein Kommunikationssystem mit Agent-Manager-Beziehung zwischen einem Netzelement, einem Betriebs- und Wartungszentrum und einem Netzwerkmanagementzentrum mit Alarmumsetzung zwischen der Schnittstelle zwischen Element Manager und Netzelement und der Schnittstelle zwischen Netzwerk Manager und Element Manager,

Fig. 3

ein Beispiel eines Ablauf-Schemas einer erfindungsgemäßen einer für die Schnittstelle zwischen Netzwerk Manager und Element Manager im Kommunikationssystem einheitlichen Operation,

Fig. 4

ein Beispiel einer hierarchischen Objektbaumstruktur und

Fig 5

eine schematische Darstellung eines Managementnetzauschnittes für ein Kommunikationssystem mit Agent-Manager-Beziehung zwischen einem Netzelement, einem Betriebs- und Wartungszentrum und einem Netzwerkmanagementzentrum mit Synchronisierung von Alarmen nach deren Behandlung im Netzwerk Manager.

Show it:

Fig. 1

a block diagram of a management system for a communication system with agent-manager relationship between network elements, operation and maintenance centers and a network management center,

Fig. 2

a schematic representation of a management network excerpt for an agent-manager relationship communication system between a network element, an operations and maintenance center and a network management center with alarm conversion between the element manager and network element interface and the interface between the network manager and element manager;

Fig. 3

an example of a flow scheme of an inventive one for the interface between Network Manager and Element Manager in the communication system single operation,

Fig. 4

an example of a hierarchical object tree and

Fig. 5

a schematic representation of a management network excerpt for a communication system with agent-manager relationship between a network element, an operation and maintenance center and a network management center with synchronization of alarms after their treatment in the network manager.

FIG. 1 is a block diagram of a management network for a mobile communication system having an agent-manager relationship between, on the one hand, operation and maintenance centers OMC ₁ , OMC ₂ to OMC _N (OMC Operation and Maintenance Center) and network elements NE (Network Elements) and, on the other hand a network management center NMC (Network Management Center) and the operation and maintenance centers OMC ₁ , OMC ₂ to OMC _N (Operation and Maintenance Center). FIG. 1 shows a representation with three management levels NM LEVEL, EM LEVEL and NE LEVEL.

The management level EM LEVEL identifies the network element management level, in the operation and maintenance centers OMC ₁ , OMC ₂ to OMC _N respectively the manufacturer-specific management functionality for, for example, in the management level NE LEVEL in Figure 1 base station systems (eg BSS ₁ to BSS _P with Base Station systems in a number from 1 to P).

The NM LEVEL management level identifies the network management level, in which the NMC network management center implements integrated, vendor-independent management functionality. In principle, several network management centers NMC can be present at the management level NM LEVEL. Between the elements Different management levels are defined interfaces for information transmission provided.

The network management center NMC is connected via a (eg real-time) interface NM-EM operation and maintenance centers OMC ₁ , OMC ₂ to OMC _N. Logically, the network management center NMC is connected to the NMC agents of the operation and maintenance centers OMC ₁ , OMC ₂ to OMC _N. Each of the operation and maintenance centers OMC ₁ , OMC ₂ to OMC _N also logically has a NE manager (not shown in FIG. 1 but shown in FIG. 2) for the interface EM-NE to the network elements NE. As shown in FIG. 1, filtering devices for the transmission of the alarm messages to the operating and maintenance centers OMC ₁ , OMC ₂ to OMC _{N can be} provided in the network elements NE.

The alarm conversion between the interface EM-NE and the interface NM-EM and FIG. 2 will be explained below with reference to the method according to the invention on the basis of a concrete example.

Alarm surveillance is one of the most important network monitoring and control functions at the network management level (at NM level eg in the NMC network management center), mainly based on the alarm list. First, in the logical part NE manager of the operation and maintenance center OMC, alarm information is stored in an alarm list "Original alarm list" (insert original alarm ). Taking into account the object model at the NM-EM interface, each operation and maintenance center OMC has to implement a mapping function Mapping function , which converts all alarms relevant to the network management center NMC from the network elements ("original" alarm) to the corresponding functional object instance. Detailed information from the original alarm received in the OMC Operations and Maintenance Center ("original" alarm), especially regarding the original failed network resource, are written by the operation mapping function as additional information in the mapped alarm list shown or derived (for example, in one of the standardized alarm parameters additionalText or additionalInformation), wherein the storing of the mapped alarm into the alarm list Mapped alarm list of the NMC agent by the operation insert mapped alarm is indicated in Figure 2. Advantageously, it can be provided that from a mapping table mapping table details for the object model at the interface NM-EM with regard to the mapping by means of the mapping function mapping function can be removed or stored.

Since the interface between NMC and the regional operation and maintenance center OMC must be manufacturer-independent, the information model of this management interface NM-EM contains only functional object classes (MOC Management Object Class) as follows: On the one hand it concerns so-called logical object classes, which model the functions of the telecommunications network. Examples of such logical MOCs in a GSM mobile radio network are BSC, BtsSiteManager or transcoder. On the other hand, an optimal network management requires that the network management center NMC also information such as alarms on the hardware operational readiness of the network units to be present. This information is intended to allow the NMC operator to correctly estimate the significance of hardware failures for the functionality of an entire network entity to initiate appropriate on-site repair operations. This is especially true if the OMC ₁ , OMC ₂ to OMC _N operations and maintenance centers are unoccupied and the mobile network is only monitored by the NMC network management center.

In order to enable network monitoring at a higher-level network management center NMC (above all during the time with unoccupied operation and maintenance centers OMC ₁ , OMC ₂ to OMC _N , eg at night or at weekends), as above Each manufacturer-specific operating and maintenance centers OMC contain a mapping function Mapping function , all the event reports relevant to the network management center NMC such as alarms from the network elements NE to the corresponding functional object class according to the information model (information model) of the OMC -NMC interface NM-EM converts. Exact information from the original, in the network element NE generated alarm message (eg information about manufacturer-specific data such as board type, board number, etc.) are as additional information (eg in the standardized parameter additionalText or additionalInformation ) in the displayed alarm message (which also can be referred to as a "mediated" alarm message).

The mapped or converted alarm messages are then routed to the NMC's own filter device EFD in the logical part NMC agent of the operation and maintenance center OMC.

This is illustrated in a schematic representation of the management network section for a communication system with agent-manager relationship between network elements NE, an operation and maintenance center OMC and a network management center NMC in FIG. The original alarm message from the network elements NE ("original" alarm) is stored, for example in the operation and maintenance center OMC as Element Manager, converted with the mapping function mapping function into functional object classes and the network management center NMC as a mapped alarm under Use of adjustable in their activity and / or variable filter device EFD sent. In the network management center, the stored alarm is stored in an alarm list Mapped alarm list of the network management center NMC by the operation insert mapped alarm.

The different object trees (containment trees) indicated in FIG. 2 in their differing structure at the interfaces EM-NE and NM-EM form the basis for the conversion of alarms by the mapping function Mapping function. Since the modeling of network resources naturally has to be more detailed at the EM-NE interface (in this case, additional manufacturer-specific resources are managed), the object tree of the EM-NE interface contains many more object classes than at the NM-EM interface. In most cases, the implementation of alarms therefore takes place via a n greater (or equal) 1 relationship, ie alarm messages from several object classes subordinate in the EM-NE object tree hierarchy can be converted into alarms of a single object class at the NM-EM interface ,

• Der Alarm wird bestätigt (alarm acknowledgement), d.h. der Alarm wurde zur Kenntnis genommen und Reparaturmaßnahmen wurden gegebenenfalls eingeleitet. Eine versehentlich erfolgte Alarmbestätigung kann dabei vom gleichen NMC-Operator zurückgenommen werden (alarm unacknowledgement).
• Der Alarm wird vom Operator manuell deaktiviert (alarm clearing), beispielsweise wenn die Ursache eines Alarms behoben wurde, ohne dass eine entsprechende Ereignismeldung vom Netzelement NE generiert werden konnte.
• Erläuterungen (alarm comments) werden einem Alarm zugewiesen, z.B. um eine bessere Koordinierung zwischen Operatoren zu ermöglichen.

At the network management level (NM LEVEL of Figure 1), the mapped alarms of NMC operators may undergo various treatments, for example as follows:

• The alarm is acknowledged ( alarm acknowledgment ) , ie the alarm has been acknowledged and repair measures have been initiated as appropriate. An accidental alarm confirmation can be withdrawn by the same NMC operator (a larm unacknowledgement ).
• The alarm is manually deactivated by the operator (a larm clearing ), for example if the cause of an alarm has been corrected without the corresponding event message being generated by the network element NE.
• Explanations (alarm comments) are assigned to an alarm, eg to allow a better coordination between operators.

The status of alarms handled at the NM level (NM LEVEL) must then be synchronized at the EM (EM LEVEL) level. This automatic synchronization is particularly important when changing the shift of OMC operators (for example, every morning when the OMC Operations and Maintenance Centers are reoccupied) so that the OMC operators can get a correct picture of the alarm situation in the network.

The method according to the invention and described in more detail in the exemplary embodiment is basically applicable to all manager-agent interfaces. It is explained below by way of example with explanations of a CMIP-based NMC-OMC interface NM-EM. However, the method is equally usable when using other interface protocols (e.g., SNMP or CORBA) in accordance with adapted form.

In the following, the synchronization of alarms with multiple object selection is considered by way of example and FIG. 3 is explained.

For the synchronization of alarm statuses of different object instances, a uniform operation alignAlarmsStatus (for example in a CMIP-based management interface with the aid of the M-ACTION service according to ITU-T X.710 standard) is realized at the interface NM-EM.

This uniform operation, shown in its flow in FIG. 3, comprises at least two communication parts , namely an operation request of the operation alignAlarmsStatus from the network management center NMC to the operation and maintenance center OMC and an operation response part of the operation alignAlarmsStatus of the operation center. and maintenance center OMC to the network management center NMC.

• ➢ operation Type:
  Dieser Parameter definiert die Art der erforderlichen Alarmsynchronisierung am Betriebs- und Wartungszentrum OMC (ack, unack, clear, comment).
• ➢ baseMOI: Dieser Parameter identifiziert eine Referenzinstanz als Ausgangspunkt im Objektbaum der Schnittstelle NM-EM für die Synchronisierung der Alarmzustände. Alle gesuchten Alarme beziehen sich auf diese Referenzinstanz und gegebenenfalls - abhängig von Wert des folgenden Parameters choice - auf weitere, im Objektbaum der Referenzinstanz untergeordnete Instanzen.
• ➢ choice: Dieser Parameter spezifiziert, ausgehend von der oben genannten Referenzinstanz, für welche, im Objektbaum der Schnittstelle NM-EM untergeordnete Netzressourcen die Alarmzustände im OMC synchronisiert werden sollen. Der Parameter kann folgende Werte annehmen:
  • einen Wert wholeSubtree:
    Die von der Referenzinstanz und allen dieser Instanz im Objektbaum untergeordneten Objekten stammenden Alarme werden berücksichtigt.
  • einen Wert levelNumber:
    Es werden nur diejenigen Alarme berücksichtigt, die von den der Referenzinstanz auf dem Level n untergeordneten Objekten generiert wurden (Anmerkung: die Referenz-Objektinstanz wird beispielsweise als Level 0 definiert und jeder im Objektbaum vorhandene Level mit untergeordneten Objekten erhält entsprechend seinem Level eine natürliche Zahl n). Dieser Wert kann nur dann verwendet werden, wenn äquivalente Objektklassen auf Level n gemäß dem Wert des Parameters levelNumber in beiden Objektbäumen an den Schnittstellen NM-EM und EM-NE vorhanden sind.
• ➢ commentText: Dieser optionale (dies ist durch die eckigen Klammern in Figur 3 verdeutlicht) Parameter wird nur verwendet, wenn der oben genannte Parameter operationType den Wert comment hat und spezifiziert einen Operatorhinweis, der den ausgewählten Alarmen zugewiesen werden soll.

The operation request of the uniform operation alignAlarmsStatus is advantageously determined by the following parameters:

• ➢ Operation Type:
  This parameter defines the type of alarm synchronization required at the Operations and Maintenance Center OMC ( ack, unack, clear, comment ).
• ➢ baseMOI : This parameter identifies a reference instance as the starting point in the object tree of the NM-EM interface for synchronizing the alarm states. All searched alarms refer to this reference instance and - depending on the value of the following parameter choice - to additional subordinate instances in the object tree of the reference instance.
• ➢ choice: Based on the reference instance mentioned above, this parameter specifies for which network resources subordinate in the object tree of the NM-EM interface the alarm states in the OMC are to be synchronized. The parameter can take the following values:
  • a value wholeSubtree :
    The alarms originating from the reference instance and all of this instance in the object tree are taken into account.
  • a value levelNumber :
    Only those alarms that were generated by the reference instance at the level n subordinate objects are taken into account (note: the reference object instance, for example, becomes defined as level 0, and each level in the object tree with subordinate objects receives a natural number n) according to its level. This value can only be used if there are equivalent object classes at level n according to the value of the levelNumber parameter in both object trees at the NM-EM and EM-NE interfaces.
• ➢ commentText : This optional (this is indicated by the square brackets in Figure 3) Parameter is only used if the above parameter operationType has the value comment and specifies an operator hint to be assigned to the selected alarms.

• ➢ status: Dieser Parameter enthält das Ergebnis der Ausführung der Alarmsynchronisierung am Betriebs- und Wartungszentrum OMC.

The operation response of the uniform operation alignAlarmsStatus is advantageously determined by the following parameter:

• ➢ status : This parameter contains the result of the execution of the alarm synchronization at the operation and maintenance center OMC.

The choice parameter of the operation request (operation re quest ) of the uniform operation alignAlarmsStatus can take the values wholeSubtree and levelNumber . For this purpose, Figure 4 provides an example, wherein a valid at both interfaces NM-EM and EM-NE hierarchy of an object tree is displayed. Basically, the object tree is contained at the interface NM-EM in the object tree at the interface EM-NE with the same hierarchy.

• > bssFunction (BSS-Funktions-Instanz)
• > bsc (BSC-Instanz)
• > btsSiteManager (BTS-SiteManager-Instanz)
• > bts (BTS-Instanz)
• > transceiver (Transceiver-Instanz).

In the example shown in FIG. 4, the hierarchy is given with the following descending hierarchical levels:

• > bssFunction (BSS function instance)
• > bsc (BSC instance)
• > btsSiteManager (BTS SiteManager instance)
• > bts (BTS instance)
• > transceiver (transceiver instance).

Assuming that the parameter baseMOI = btsSiteManager: 3 (ie the BTS SiteManager instance with number 3) and the parameter choice = levelNumber (2) (ie only those alarms are taken into account by the reference instance at the level 2 subordinate objects were generated), this means for the illustrated embodiment that the alarms of all in the object tree below the instance btsSiteManager: 3 (BTS SiteManager instance number 3) existing transceiver instances are taken into account in this example.

• ack: Alle Alarme werden automatisch in den Zustand "bestätigt" gesetzt,
• unack: Alle Alarme werden automatisch in den Zustand "nicht bestätigt" zurückgesetzt,
• clear: Alle Alarme werden automatisch "cleared". Diejenigen Alarme, die schon bestätigt waren, werden aus den Alarmlisten entfernt.
• comment: Jedem Alarm wird ein Operatorhinweis zugewiesen.

Upon receipt of the operation request request of the unitary operation alignAlarmsStatus , in the operations and maintenance center OMC, the status of all alarms selected at the network management center NMC is displayed both in the NMC agent mapped alarm list alarm list and in the alarm list. Original alarm list "of the NE manager synchronized according to the parameter value operationType , whereby in detail means:

• ack : All alarms are automatically set to "confirmed",
• unack : All alarms are automatically reset to the "not confirmed" state,
• clear: All alarms are automatically cleared. Those alarms that have already been confirmed will be removed from the alarm lists.
• comment: Each alarm is assigned an operator hint.

The agent then sends to the Manager (NMC) a response (Operation Response) containing the result of the execution.

In connection with FIG. 5, an application example for an alarm synchronization with alarm acknowledgment in the OMC is described below, which synchronizes the status of the alarm acknowledgment ("acknowledgment state").

It is assumed that a base station system (eg, BSS Function Instance # 17, bssFunction: 17 ') is serviced, thereby indicating a larger number of associated alarms at the network management center NMC. The NMC operator (which knows the reason for the occurrence of these alarms) has selected and acknowledged all alarms originating from this BSS network element .

• operationType = ack
• baseMOI = bssFunction:17
• choice = wholeSubtree

The NMC then sends to the base station monitoring operation and maintenance center OMC an operation request of the unitary operation alignAlarmsStatus with the following parameter values:

• operationType = ack
• baseMOI = bssFunction: 17
• choice = wholeSubtree

The optional parameter commentText is not used in this example case.

1. a) In der Alarmliste "Mapped alarm list" werden diejenigen Alarme gesucht, deren Objektinstanz (Parameter MOI) die Komponente (so genannten "relative distinguished name") bssFunction:17 enthält. In jedem gefundenen abgebildeten Alarm ("Mapped" alarm) wird aus dem Parameter additionalText (oder additionalInformation) die Objektinstanz des ursprünglichen ("original") BSS-Alarms (orig-MOI_k) ermittelt.
2. b) Alle in der Alarmliste "Mapped alarm list" des NMC-Agenten gefundenen Alarme werden automatisch bestätigt (acknowledged). Ist ein jetzt bestätigter Alarm nicht mehr aktiv, dann wird dieser aus der Alarmliste "Mapped alarm list" des NMC-Agenten automatisch entfernt.
3. c) Nachdem alle ursprünglichen ("original") Objektinstanzen des Alarms gefunden wurden, sendet der NMC-Agent an den NE-Manager im Betriebs- und Wartungszentrum OMC ein internes Kommando scopedAlarmsHandling mit folgenden Parameterwerten:
   • operationType: ack
   • objectlnstanceList:
     Dieser Parameter spezifiziert eine Sequenz von Objektinstanzen an der Schnittstelle EM-NE, deren Alarme bestätigt werden sollen (origMOI₁ , ..., origMOI_n).
   (Es könnte ferner optional ein Parameter comment zur Kommentierung vorgesehen sein.)

At the OMC Operations and Maintenance Center, the NMC Agent performs the following steps:

1. a) In the alarm list "Mapped alarm list" those alarms are searched whose object instance (parameter MOI) contains the component (so-called "relative distinguished name") bssFunction: 17 . In each mapped alarm found, the parameter additionalText (or additionalInformation ) determines the object instance of the original ("original") BSS alarm (orig-MOI _k ).
2. b) All alarms found in the "Mapped alarm list" alarm list of the NMC Agent are automatically acknowledged. If a now confirmed alarm is no longer active, it will be automatically removed from the alarm list "Mapped alarm list" of the NMC agent.
3. c) After all original ("original") instances of the alarm have been found, the NMC agent sends an internal scopedAlarmsHandling command to the NE manager in the OMC operation and maintenance center with the following parameter values:
   • operationType: ack
   • objectlnstanceList :
     This parameter specifies a sequence of object instances at the EM-NE interface whose alarms are to be acknowledged (origMOI ₁ , ..., origMOI _n ).
   (Optionally, a parameter comment for commenting could also be provided.)

1. a) Für jede Objektinstanz origMOIk (k = l...n): alle Alarme in der Alarmliste "Original alarm list" des NE-Managers", deren Objektinstanz (Parameter MOI) den "relative distinguished name"-Wert der Objektinstanz origMOIk enthält, werden automatisch bestätigt. Dies bedeutet folgenden Vorteil: Damit werden auch Alarme von der Objektinstanz origMOI_k bestätigt, die durch den NMC-eigenen Filter (z.B. weil diese Alarme für den NMC-Operator weniger relevant sind) absichtlich ausgefiltert worden waren.
2. b) Ist ein bestätigter Alarm nicht mehr aktiv, dann wird dieser aus der Alarmliste "Original alarm list" des NE-Managers automatisch entfernt.

After receiving the scopedAlarmsHandling command, the NE manager of the OMC Operations and Maintenance Center carries out the following steps:

1. a) For each object instance origMOIk (k = l ... n): all alarms in the alarm list "Original alarm list" of the NE manager "whose object instance (parameter MOI) contains the" relative distinguished name "value of the object instance origMOIk , are automatically confirmed, which means the following advantage: This also confirms alarms from the object instance origMOI _k , which are filtered by the NMC's own filter (eg because these alarms less relevant to the NMC operator) were deliberately filtered out.
2. b) If a confirmed alarm is no longer active, it is automatically removed from the alarm list "Original alarm list" of the NE manager.

By way of example, an alarm acknowledgment has been explained above by the NMC operator. For other types of treatment of multiple alarms at the network management center NMC, the procedure applies mutatis mutandis.

Claims (13)

1. A method for handling alarms by means of a management network of a communication system,
   wherein the management network comprises at least two management entities (NMC, OMC₁, OMC₂, OMC_N; OMC) at different management levels,
   wherein at least one of the at least two management entities functions as an element manager (OMC₁, OMC₂, OMC_N; OMC) which is hierarchically higher than network elements (NE), and at least one of the at least two management entities functions as a network manager (NMC) which is hierarchically higher than and allocated to the element manager (OMC₁, OMC₂, OMC_N; OMC) in its function as an agent,
   characterised in that

   - an alarm is mapped onto a functional object class in the element manager (OMC₁, OMC₂, OMC_N; OMC) with reference to an object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC),

   - the alarm is forwarded from the element manager (OMC₁, OMC₂, OMC_N; OMC) to the network manager (NMC),

   - the alarm is handled in the network manager (NMC),

   - a synchronisation of the alarm status of the alarm,

   which alarm status is set by the network manager (NMC), between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC) takes place in the element manager (OMC₁, OMC₂, OMC_N; OMC) on the basis of a standardised operation (alignAlarmStatus) for the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC) in the communication system.
2. The method as claimed in claim 1, characterised in that provision is made for storing within the element manager (OMC₁, OMC₂, OMC_N; OMC), at least occasionally, information relating to the content of the alarm which arrives at the element manager (OMC₁, OMC₂, OMC_N; OMC) and/or of the alarm which is mapped onto a functional object class with reference to the object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC).
3. The method as claimed in claim 2, characterised in that the information which is at least occasionally stored includes an alarm list (original alarm list) for incoming alarms in the element manager (OMC₁, OMC₂, OMC_N; OMC) and an alarm list (mapped alarm list) for alarms which are mapped onto a functional object class with reference to the object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC) .
4. The method as claimed in claim 2 or 3,
   characterised in that the information that is stored in the element manager (OMC₁, OMC₂, OMC_N; OMC), and relates to the content of the alarm which arrives at the element manager (OMC₁, OMC₂, OMC_N; OMC) and/or of the alarm which is mapped onto a functional object class with reference to the object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC), is used at least to some extent during the synchronisation by means of the standardised operation (alignAlarmStatus).
5. The method as claimed in one of the claims 2, 3 or 4, characterised in that for the purpose of synchronisation by means of the standardised operation (alignAlarmStatus) in the element manager (OMC₁, OMC₂, OMC_N; OMC), an object instance is transferred from the network manager (NMC) to the element manager (OMC₁, OMC₂, OMC_N; OMC) as a reference instance for the functional object class onto which the alarm was mapped with reference to the object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC).
6. The method as claimed in claim 5, characterised in that with reference to the information that is stored in the element manager (OMC₁, OMC₂, OMC_N; OMC), and relates to the content of the alarm which arrives at the element manager (OMC₁, OMC₂, OMC_N; OMC) and/or of the alarm which is mapped onto a functional object class with reference to the object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC), a reverse mapping takes place onto an object instance of the object model at the interface (EM-NE) between element manager (OMC₁, OMC₂, OMC_N; OMC) and network element (NE) during the synchronisation.
7. The method as claimed in claim 6, characterised in that during the synchronisation, consideration is also given to one, a plurality or all object instances which are in the object tree of the object model at the interface (EM-NE) between element manager (OMC₁, OMC₂, OMC_N; OMC) and network element (NE) and are below that object instance as per the object model at the interface (EM-NE) between element manager (OMC₁, OMC₂, OMC_N; OMC) and network element (NE) which corresponds to the reference instance as per the object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC).
8. An element manager (OMC₁, OMC₂, OMC_N; OMC) of a management system of a communication network for handling alarms in the management system of the communication network, as one of at least two management entities (NMC, OMC₁, OMC₂, OMC_N; OMC) of the management network on different management levels,
   wherein a network manager (NMC) can be assigned to the element manager (OMC₁, OMC₂, OMC_N; OMC) in its function as agent,
   characterised in that

   - means (mapping function) are present for mapping an alarm onto a functional object class with reference to an object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC),

   - means (EFD) are provided for forwarding the alarm from the element manager (OMC₁, OMC₂, OMC_N; OMC) to the network manager (NMC), and

   - means (mapping function) for synchronising the alarm status of the alarm, which alarm status is set by the network manager (NMC), between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC) in the element manager (OMC₁, OMC₂, OMC_N; OMC) on the basis of a standardised operation (alignAlarmStatus) for the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC) in the communication system, after handling of the alarm in the network manager (NMC).
9. The element manager (OMC₁, OMC₂, OMC_N; OMC) as claimed in claim 8, characterised in that means (original alarm list, mapped alarm list) are provided for at least occasionally storing information relating to the content of the alarm which arrives at the element manager (OMC₁, OMC₂, OMC_N; OMC) and/or of the alarm which is mapped onto a functional object class with reference to the object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC).
10. The element manager (OMC₁, OMC₂, OMC_N; OMC) as claimed in claim 8, characterised in that means (original alarm list, mapped alarm list) are provided for receiving an object instance as a reference instance for the functional object class, onto which the alarm was mapped with reference to the object model at the interface (NM-EM) between network manager (NMC) and element manager (OMC₁, OMC₂, OMC_N; OMC), of the alarm which was handled in the network manager (NMC) for synchronisation by means of the standardised operation (alignAlarmStatus) from the network manager (NMC).
11. The element manager (OMC₁, OMC₂, OMC_N; OMC) as claimed in claim 8 or 9, characterised in that the element manager (OMC₁, OMC₂, OMC_N; OMC) comprises means for carrying out the method in accordance one of the claims 3, 4, 6 and 7.
12. A communication system for handling alarms by means of a management network including at least two management entities (NMC, OMC₁, OMC₂, OMC_N; OMC) on different management levels,
    wherein at least one of the at least two management entities functions as an element manager (OMC₁, OMC₂, OMC_N; OMC) and at least one of the at least two management entities functions as a network manager (NMC) which is hierarchically above and allocated to the element manager (OMC₁, OMC₂, OMC_N; OMC) in its function as an agent,
    characterised in that means are provided for carrying out the method as claimed in one of the claims 1 to 7.
13. The communication system as claimed in claim 12,
    characterised in that it includes an element manager (OMC₁, OMC₂, OMC_N; OMC) as claimed in claim 8, 9, 10 or 11.

Images