WO2001095572A2 - Procede, systeme et agent permettant de traiter une mise a jour d'avertissement de ressource reseau dans un reseau de gestion de telecommunication - Google Patents

Procede, systeme et agent permettant de traiter une mise a jour d'avertissement de ressource reseau dans un reseau de gestion de telecommunication Download PDF

Info

Publication number
WO2001095572A2
WO2001095572A2 PCT/SE2001/001270 SE0101270W WO0195572A2 WO 2001095572 A2 WO2001095572 A2 WO 2001095572A2 SE 0101270 W SE0101270 W SE 0101270W WO 0195572 A2 WO0195572 A2 WO 0195572A2
Authority
WO
WIPO (PCT)
Prior art keywords
alarm
agent
attribute
update
notification
Prior art date
Application number
PCT/SE2001/001270
Other languages
English (en)
Other versions
WO2001095572A3 (fr
Inventor
Edwin Tse
Nicolas Gosselin
André GODIN
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to AU2001262884A priority Critical patent/AU2001262884A1/en
Publication of WO2001095572A2 publication Critical patent/WO2001095572A2/fr
Publication of WO2001095572A3 publication Critical patent/WO2001095572A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor

Definitions

  • the present invention relates to Telecommunication Management Systems, and in particular to the processing of alarm updates by an agent of the Telecommunication Management System.
  • LANs Local Area Networks
  • WANs Wide Area Networks
  • PLMN Public Local Mobile Networks
  • EMS Telecommunication Management Network
  • the nodes of the monitored network typically issue event notifications for various events taking place in the network, such as for example call set-ups, radio cell selections, or hand-off failures in a PLMN.
  • the events are further collected by the EMS and processed in a manner defined by the network operator for providing indications of the level of service quality given by the monitored network.
  • the EMS may comprise one or more Agents that receives, processes and stores the incoming events, such as the alarm notification.
  • the Agent may receive the alarm notification from the monitored network, process it by assigning an alarm identifier to the received notification and store the identified alarm in an Active Alarm List (AAL).
  • AAL Active Alarm List
  • the agent can send a notification to one or more Managers, which is another type of entity of the EMS that may be dedicated to further processing the alarm notifications, such as for example by performing alarm correlation.
  • Managers may perform, for example, the actual management of the alarms, i.e. displaying the alarms to network administrators, thus allowing some remedial actions to be taken for dealing with the original problem that triggered the alarm notification.
  • the Agent is typically linked to a Manager and notifies the Manager upon receipt of an alarm notification, by sending the alarm information along with its identifier. If, for example, the severity level of the alarm subsequently changes, such as for example because it has been detected that the radio quality of the current call improved, an update of the alarm must be issued in order to reflect the change.
  • the International Telecommunication Union as suggested by the International Telecommunication Union -
  • the alarm update is performed in two separate steps. First, the alarmed resource that originally issued the alarm issues another alarm with the severity level set to CLEARED. Upon receipt of this notification, the Agent sets the alarm severity level to CLEARED in its Active Alarm
  • AAL Agent List
  • Manager which also sets the alarm severity level to CLEARED in its own alarm list.
  • the alarmed resource sends yet another alarm notification along with the new severity level to the Agent.
  • the Agent changes again the alarm severity level in its AAL, and notifies yet again the Manager of the new alarm severity.
  • a first update notification comprises a transitional attribute value, such as a cleared state
  • a second alarm update notification that comprises the actual new attribute value
  • the management system further notifies the user of the update information using a notifying interface corresponding to each user.
  • Inakoshi is limited to a method and system for notifying a user of an information change, and does not disclose, teach or suggest a method and system for simplifying the treatment of alarm update notification as proposed in the present invention.
  • an Event Management System a method for updating an alarm attribute of a particular alarm, the method comprising the steps of: receiving in an agent of the EMS a first update alarm notification comprising an alarm attribute value set to cleared, for the particular alarm; starting a timer set to expire after a pre-determined period of time upon receipt of said first update alarm notification in the agent; and if a second update alarm notification comprising a second alarm attribute value is received in the agent for the particular alarm before an expiry of the pre-determined period of time: discarding the first update alarm notification; and updating the alarm attribute of the particular alarm with the second alarm attribute value.
  • EMS Event Management System
  • EMS Event Management System
  • ANR Alarmed Network Resource
  • AAL Active Alarm List
  • the Agent sends a first update alarm notification comprising an alarm attribute value set to CLEARED to the agent, the notification being directed to update a particular alarm; upon receipt of the first update notification, the Agent starts a timer set to expire after a pre-determined period of time; and if a second update alarm notification directed to the particular alarm and comprising a second alarm attribute value is received in the agent before an expiry of the pre-determined period of time: the agent discards the first update alarm notification; and the agent updates the alarm attribute of the particular with the second alarm attribute value.
  • EMS Event Management System
  • AAL Active Alarm List
  • ANR Network Resource
  • an alarm processor connected to the timer for starting the timer upon receipt from the ANR of a first update alarm notification directed to a particular alarm and comprising an alarm attribute value set to CLEARED, and for determining if a second update alarm notification directed to the particular alarm and comprising a second alarm attribute value is received at the agent before an expiry of the pre-determined period of time; wherein, if the second update alarm notification is received in the agent before the expiry of the pre-determined period of time: the agent discards the first update alarm notification; and the agent updates the particular alarm with the second alarm attribute value.
  • ANR Network Resource
  • Figure 1 is a high-level block diagram of an Event Management System (EMS) and also includes a high-level flowchart diagram of the prior art method for treating an update alarm notification;
  • EMS Event Management System
  • Figure 2 is an exemplary high-level block diagram of an EMS network according to a preferred embodiment of the invention, and also includes a high-level flowchart diagram of the invented method for treating an alarm update;
  • Figure 3. a is an exemplary illustration of an alarm notification
  • Figure 3.b is an exemplary illustration of the severity attribute of an alarm notification
  • Figure 3.c is yet another exemplary illustration of a series of attributes of an alarm notification.
  • Figure 4 is an exemplary high-level block diagram of an EMS agent according to a preferred embodiment of the invention.
  • FIG. 1 a high-level block diagram of a known prior art Event Management System (EMS) 10 (also called hereinafter alarm management system or telecommunication management network) that monitors a network 12, such as for example a Public Local Mobile Network (PLMN) 12.
  • EMS Event Management System
  • PLMN Public Local Mobile Network
  • the monitored network 12 may appear as a set of components, or nodes, also having a series of sub-components. Every such node and/or sub-component may issue events and/or alarms.
  • the nodes and subcomponents are depicted as Alarmed Network Resources (ANR) 14 ; .
  • ANR Alarmed Network Resources
  • the monitored network 12 may be practically any kind of network, and that the ANRs 14 ; can be any kind of nodes, sub-components, or logical entities in communication or not with each other.
  • the monitored network 12 is linked with the EMS 10 by at least one connection 15, and the EMS 10 comprises at least one Agent 18 further connected to at least one Manager 32, such as for example through a network 34 that may be a Local Area network (LAN) or a Wide Area network (WAN).
  • the Agent 18 further comprises an internal or external Active Alarm List (AAL) 26 for storing the active alarms issued by at least some portions of the monitored network 12.
  • AAL Active Alarm List
  • action 20 assigns an identifier to the original alarm 16
  • action 22 and then stores the alarm along with the identifier, information 24, in its AAL 26, action 28.
  • the Agent 18 sends a notification 30, comprising information 24 (the alarm with its identifier) to the Manager 32 over the network 34, action 36, thus allowing the Manager 32 to be also informed of the receipt of the original alarm 16.
  • An alarm notification such as for example the original alarm 16 may include various alarm attributes (also called fields) having certain pre-defined values (also called states).
  • an alarm notification such as for example the alarm notification 16 typically includes certain alarm attributes (fields) 40 i5 each such attribute comprising an alarm attribute value 40 ; ' (the actual content, or state, of the attribute).
  • the alarm attribute 40 4 may be the "perceived severity attribute” and thus comprises the “perceived severity attribute value" 40 4 '.
  • the format of the alarm notification may vary from one communication protocol to another.
  • Figure 3.b illustrates an exemplary list of the possible values of an alarm attribute, such as for example of the alarm "perceived severity attribute" 40 4 of the alarm notification 16.
  • Figure 3.c depicts an exemplary list of alarm attributes 40j used in various ITU-
  • each alarm typically comprises an alarm identification which is used by the various EMS nodes for identifying, associating and correlating a particular alarm.
  • an attribute value of the original alarm may have to be changed for various reasons. For example, the state of an ANR that issued the original alarm may vary, and thus an alarm attribute such as for example the severity attribute of the original alarm 16 may change. This may require an update notification to be sent by the ANR 14 j to the Agent 18.
  • the ANR 14 sends a first update alarm notification with the severity attribute value set to CLEARED, message 50, to the Agent 18.
  • the updated alarm notification 50 comprises the same alarm information as the original alarm notification 16, i.e. the alarm identification and all attributes that did not change, with the exception of the alarm severity attribute that changed from a first attribute value to another attribute value set to CLEARED.
  • the Agent 18 receives the message 50, action 52, and sets the alarm severity attribute value 40 4 ' of the alarm listed in the
  • Agent 18 may use the alarm identification information for knowing which alarm from the AAL 26 the update alarm notification is addressed to.
  • the ANR 14 x After having sent the first update alarm notification 50 with the alarm severity attribute value set to CLEARED as described beforehand, according to the current standards, the ANR 14 x can send the new actual alarm severity attribute value. For this purpose, the ANR 14, sends yet another (second) update alarm notification, message
  • the Agent 18 receives the message 60, action 62, and stores in the AAL 26 the alarm information with the new severity level, action 63, by sending a message 65 comprising the alarm information with the new severity level. Thereafter, the manager
  • the prior art method for processing the alarm updates described in Figure 1 is laborious since it requires sending and processing a tandem update alarm notification comprising a first update alarm notification with an alarm attribute value set to CLEARED and a second update alarm notification having the actual (second) alarm severity attribute value.
  • the same two-step approach is also used in the prior art systems for updating not only the alarm severity attribute, but also other types of alarm attributes.
  • a modified EMS 11 monitors the monitored network 12.
  • the monitored network may be any kind of network, such as for example a Local Area Network (LAN), a Wide Area Network (WAN), a wired or wireless telephone network of any kind (GSM, ANSI-41 , GPRS,
  • the monitored network 12 is connected through at least one link 15, such as for example a wireline link, to one or more Agents 19, of the EMS 11.
  • the Agents 19 may be nodes and/or logical entities of the EMS 11 responsible for example of the intermediate treatment of the information ranging between the information acquisition from the monitored network 12 to the final display of the treated information on the network administrators display (not shown).
  • the tasks assigned to the Agents of an EMS include, but may not be limited to, information (events, alarms, etc) storage, primary information treatment such as some basic alarm correlation, basic information categorization, etc.
  • Agent 19 responsible for storing alarms issued by one or more Alarms Network Resources 14 for the alarm update processing and for forwarding the alarm-related information to the Manager 32'.
  • the Agent 19 receives the alarm 16, action 20, creates and assigns an identifier to the original alarm 16, action 22 and then stores the information 24, i.e. the alarm along with the identifier, in its AAL 26', action 28. Once the information 24 is stored in the AAL 26', the Agent 19 sends a notification message 30, comprising the information 24 (the alarm with its identifier) to the Manager 32' over the network 34, action 36, thus allowing the Manager to be also informed of the original alarm.
  • an alarm attribute value such as the value of the alarm severity attribute
  • alarm severity of a given alarm changes from a previous value of CRITICAL to a new value of MINOR
  • the ANR 14 may be set to issue a first alarm notification comprising the same alarm information as the original alarm notification 16, with the exception of the alarm attribute value now being set to CLEARED, message 50, and to send it to the Agent 19.
  • the invention proposes to receive a first update alarm notification having an attribute value set to cleared, hold this request for a pre-determined period of time without modifying the AAL entry of the given particular alarm, and without sending the further notification to the Manager.
  • the Agent updates the AAL alarm attribute by setting the given attribute value to CLEARED, and also informs the Managers that the given attribute value is set to CLEARED.
  • the Agent 19 receives the message 50, action 80, and first starts a Timer, action 82, for measuring a time interval between the receipt of message 50, comprising the given attribute value set to CLEARED, and the second update alarm notification, message 60, comprising the second (actual) alarm attribute value.
  • the Timer is set to expire at a pre-defined time period defined by a network administrator.
  • the period of time may bear a relation with the average amount of time separating the receipt of the first update alarm notification 50 and the receipt of the second update alarm notification 60 for the given particular alarm (see Figure 1). This relation can be for example that the pre-defined time period is set to be: i) sensibly greater than, or, ii) twice the average amount of time separating the receipt of the first and the second update alarm notifications at the Agent.
  • the Agent 19 does not actually perform the update of the given alarm attribute with the CLEARED state, as done in the prior art systems. Instead, the Agent monitors if a second update alarm notification message 60 (comprising a new alarm attribute value than the original alarm notification 16) is received before the expiration of the pre-determined time period, action 84. If yes, i.e. if the Agent 19 receives before the expiration of the pre-determined time period a second update alarm notification 60 with a new attribute value, the Agent 19 first discards the first alarm notification message 50, action 86, i.e.
  • the Agent does not update the AAL 26' with the alarm attribute value set to CLEARED, and does not update the Manager 32' with the alarm attribute value set to CLEARED. Instead, the Agent 19 updates the alarm attribute of the given alarm in the AAL 26' with the new alarm severity attribute received in message 60, action 87, by sending an alarm update request 88 to the AAL 26', and further informs the Manager 32' of the alarm update by sending an update alarm notification message 90 over the network 34, action 92.
  • the invention further comprises provisions for dealing with exception cases wherein the second update alarm notification 60 is not received during the pre-determined time period.
  • the timer monitors for receipt of the actual alarm update notification 60, action 84; if the timer expires and no such notification is received, then the Agent 19 updates the given attribute of the particular alarm in the AAL 26' with the CLEARED value, action 100, by sending an alarm attribute update request 102 to the AAL 26', and further updates the Manager 32', action 103, by sending an alarm attribute update request message 104 over the network 34.
  • the Agent 19 may update the AAL 26' with the new (second) alarm attribute and further update the Manager 32' as described beforehand for analogous actions (actions not shown).
  • the invention was exemplified hereinbefore especially with reference to the alarm severity attribute update, the invention is applicable and useful for updating various types of alarm attributes that according to certain standards require a first update with in intermediary value, such as the CLEARED value, and then only allow to proceed with the actual attribute update with an actual attribute value.
  • intermediary value such as the CLEARED value
  • the Agent 19 may comprise am input module 110, such as an I/O interface, for receiving the alarm notifications 16, 50, and 60 from the ANRs 14 i3 and possibly also for acknowledging receipt of the alarms (actions and acknowledging messages not shown).
  • the input module 110 may be connected to an alarm processor 112 wherein alarms are identified and treated as described hereinbefore with reference to Figure 3.
  • the alarm processor 112 is further connected to a Timer 114, which is responsible for measuring the time interval from the receipt of first update alarm notification with the attribute value set to CLEARED, message 50, to the receipt of the second update alarm notification 60 (see Figure 2).
  • the alarm identifier builder 113 that is responsible for creating and assigning an identifier for each newly received alarm (original alarm 16) as described in connection to Figure 2 and ii) the AAL 26' that stores the list of the active alarms.
  • the AAL 26' may be comprised in the Agent 19, as it is shown in Figure 4, or may be external to the Agent 19 but connected therewith, as shown in Figure 2.
  • the Agent 19 receives an original alarm notification 16 at the alarm input module 110, which forwards the notification 16 to the alarm processor 112.
  • the processor passes the original alarm notification 16 to the alarm identifier builder 113 that creates and assigns an identifier to the alarm 16.
  • the identifier builder 113 further transmits the alarm and its identifier, information 24 to the AAL 26'.
  • the Agent 19 may later receive a first update alarm notification 50 from the ANR 14,.
  • the notification 50 may be received in the same alarm input module 110 and further transmitted to the alarm processor 112. Since the first update alarm notification 50 contains the same alarm information as the notification 16, with the exception of the given attribute that must be updated which is set to the CLEARED value in the message 50, the alarm processor 112 detects that this is not an original alarm, but rather an update (CLEARED) for the original alarm given attribute. This action may be performed by the alarm processor 112 in collaboration with the AAL 26' that may be queried for detecting the presence of the original alarm 16 (with its identifier) in the AAL 26'.
  • the processor 112 detects that the message 50 is an update alarm notification following and corresponding to an original alarm notification 16, the processor 112 instructs the timer 114 to start and run until reaching a predetermined time value.
  • the timer 114 may send a timer expiry signal 115 to the alarm processor 112.
  • the alarm processor 112 updates the alarm attribute of the given particular alarm in the AAL 26' by setting it to the CLEARED value received in message 50.
  • the alarm processor 112 may identify the particular alarm the update 50 is directed to by using the alarm identification comprised in the message 50. Further, the alarm processor 112 notifies the Manager (not shown) of the new alarm attribute value set to CLEARED through message 104.
  • the alarm processor 112 first discards the first update alarm notification 50, (action 86 in Figure
  • the alarm processor 112 updates the alarm attribute if the given particular alarm in the AAL 26' by replacing the original alarm attribute value (received in the notification 16) by the second alarm attribute value (received in the second notification 60) as described in action 87 of Figure 2. Further, the alarm processor 112 notifies the Manager (not shown) of the alarm update through the message 90 (action 92 in Figure 2). In such a scenario, upon receipt of the second update alarm notification 60 comprising a new severity attribute, the alarm processor 112 may also instruct timer 114 to stop counting (action not shown) or simply ignore the time expiry signal received at the expiration of the pre-determined time period. Therefore, in the exemplary preferred embodiment described with reference to Figure 4, at least part of the intelligence of the Agent 19 is comprised in the alarm processor 112.
  • the functional modules 110 - 114 may preferably be software modules forming a global alarm processing application, or a portion thereof.
  • the functional modules 110 - 114 may be hardware modules, or a combination of software modules running over certain hardware devices.
  • the alarm processor 112 may be a code program functionality running over a hardware chip, while the AAL 26' may be a database management software application running over an operating system installed on a given server.
  • the invented method, system and Agent were described hereinbefore as being useful for dealing with a sequence comprising the receipt of an alarm update following the receipt of an original alarm 16 (see Figure 2)
  • the "original” alarm 16 may also be any kind of alarm notification, such as for example an update alarm notification. Therefore, the invention may also apply for processing not only a first alarm update for a given "original” alarm, but also further alarm updates of a given alarm, including a series of alarm updates (in that case the "original" alarm 16 becomes a "previous” alarm update). Therefore, the term "original” alarm notification as described hereinbefore should be interpreted in its larger sense, i.e. it represents an alarm that is received at the agent 19 previous to a subsequent alarm update.
  • the same principle and simplified processing scheme described with reference to Figures 2 and 4 may be used and applied not only for processing any type of alarm update wherein an alarm attribute changes, provided that the alarm identity remains unchanged.
  • the invention can therefore be applied to the processing any type of alarm attribute update that requires, according to a given standard (or other requirements), the transmission of an attribute set to a CLEARED state, or to an intermediate state, prior to the transmission of a new attribute indicating the actual update of that attribute.
  • alarm attributes may be used in accordance with the teachings of the present invention and as described hereinbefore, for simplifying the alarm update processing scheme: i ) the "correlated Notifications” alarm attribute that typically identifies a set of notifications to which the current notification is considered to be correlated; ii) the "trend Indication” alarm attribute that indicates if some observed condition is getting better, worse, or not changing. Legal values are "less severe”, “no change” and “more severe”; and iii) the "proposed Repair Actions” alarm attribute that indicates proposed repair actions.

Abstract

L'invention concerne un système de gestion événement (EMS) (11), dans lequel un procédé, un système et un agent (19) permettent de traiter la mise à jour de l'alarme. Un agent reçoit d'une ressource réseau alarmée (14i) une première notification (50) d'actualisation d'alarme avec un attribut alarme, tel qu'un attribut de gravité, réglé à EFFACE, suivie d'une deuxième notification (60) d'actualisation d'alarme contenant une nouvelle valeur d'attribut. A réception de la première notification d'actualisation (50), l'agent (19) lance une minuterie pour surveiller si la deuxième actualisation est reçue dans un laps de temps prédéterminé. Dans l'affirmative, l'agent supprime la première notification d'actualisation (50), actualise son alarme active avec les nouveaux attributs d'alarme puis informe un gestionnaire (32') du changement d'alarme. Dans le cas contraire, c'est-à-dire si le laps de temps prédéterminé expire ou si l'agent (19) ne reçoit pas de deuxième actualisation, l'agent (19) actualise son alarme initiale (16) dans sa liste d'alarmes actives avec l'attribut réglé à EFFACE puis informe le gestionnaire (32') de l'attribut mis à jour par l'état EFFACE.
PCT/SE2001/001270 2000-06-05 2001-06-05 Procede, systeme et agent permettant de traiter une mise a jour d'avertissement de ressource reseau dans un reseau de gestion de telecommunication WO2001095572A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001262884A AU2001262884A1 (en) 2000-06-05 2001-06-05 Method, system, and agent for processing a network resource alarm update in a telecommunication management network

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US20952100P 2000-06-05 2000-06-05
US60/209,521 2000-06-05
US63170100A 2000-08-03 2000-08-03
US09/631,701 2000-08-03

Publications (2)

Publication Number Publication Date
WO2001095572A2 true WO2001095572A2 (fr) 2001-12-13
WO2001095572A3 WO2001095572A3 (fr) 2002-03-28

Family

ID=26904242

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2001/001270 WO2001095572A2 (fr) 2000-06-05 2001-06-05 Procede, systeme et agent permettant de traiter une mise a jour d'avertissement de ressource reseau dans un reseau de gestion de telecommunication

Country Status (2)

Country Link
AU (1) AU2001262884A1 (fr)
WO (1) WO2001095572A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009151415A1 (fr) 2008-06-10 2009-12-17 Thomson Licensing Filtrage de message dans un système de surveillance de réseau

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19740738A1 (de) * 1997-09-16 1999-03-18 Siemens Ag Verfahren zum Wiederanordnen einer Liste der in einer untergeordneten Managementebene eines Kommunikationsnetzes aktiven Alarme
DE19740718A1 (de) * 1997-09-16 1999-09-23 Siemens Ag Realignment-Verfahren zwischen einem Betriebs- und Wartungszentrum und einem diesem übergeordneten Netzmanagementzentrum
WO2000039674A1 (fr) * 1998-12-31 2000-07-06 Computer Associates Think, Inc. Systeme et procede de correlation dynamique d'evenements
EP1079566A2 (fr) * 1999-08-23 2001-02-28 Motorola Ireland Limited Gestion de système dans un réseau de transmissions comportant des agents de SNMP et de CMIP

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19740738A1 (de) * 1997-09-16 1999-03-18 Siemens Ag Verfahren zum Wiederanordnen einer Liste der in einer untergeordneten Managementebene eines Kommunikationsnetzes aktiven Alarme
DE19740718A1 (de) * 1997-09-16 1999-09-23 Siemens Ag Realignment-Verfahren zwischen einem Betriebs- und Wartungszentrum und einem diesem übergeordneten Netzmanagementzentrum
WO2000039674A1 (fr) * 1998-12-31 2000-07-06 Computer Associates Think, Inc. Systeme et procede de correlation dynamique d'evenements
EP1079566A2 (fr) * 1999-08-23 2001-02-28 Motorola Ireland Limited Gestion de système dans un réseau de transmissions comportant des agents de SNMP et de CMIP

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009151415A1 (fr) 2008-06-10 2009-12-17 Thomson Licensing Filtrage de message dans un système de surveillance de réseau
CN102057624A (zh) * 2008-06-10 2011-05-11 汤姆森许可贸易公司 网络监控系统中的消息过滤

Also Published As

Publication number Publication date
WO2001095572A3 (fr) 2002-03-28
AU2001262884A1 (en) 2001-12-17

Similar Documents

Publication Publication Date Title
JP4945573B2 (ja) イベント通知相関のための方法および管理エージェント
JP5524410B2 (ja) Ｌｔｅ／ｅｐｃネットワークにおけるｍｍｅの障害を処理する方法
US20030069959A1 (en) Alarm lists synchronization in an alarm management system
KR100922040B1 (ko) 관리 네트워크에서 매니저와 에이전트 사이에 데이터를매칭하기 위한 방법 및 장치들
JP2006501717A (ja) 電気通信ネットワーク・エレメントの監視
US8737970B2 (en) Method and apparatus for processing release of connection resources
US20030110243A1 (en) Method, system and policy decision point (PDP) for policy-based test management
WO2001095572A2 (fr) Procede, systeme et agent permettant de traiter une mise a jour d'avertissement de ressource reseau dans un reseau de gestion de telecommunication
CN113824595B (zh) 链路切换控制方法、装置和网关设备
CN112437146B (zh) 一种设备状态同步方法、装置及系统
CN113259875B (zh) Cpnf与amf通信的方法及网络功能储存库功能实体
WO2000056097A1 (fr) Mise en correlation des evenements reseau et des identites d'abonne et d'equipement mobile
KR101146836B1 (ko) 매니저 고장시 관리 네트워크를 운영하기 위한 방법 및설비들
US7159148B2 (en) Method for performance and fault management in a telecommunication network
KR100279695B1 (ko) 브이엘알에서의 엠에이피 동작에 대한 신호점 상태 관리 방법
US6956856B2 (en) System and method for managing a plurality of calls
CN117675530A (zh) 一种容灾方法、第一网络存储功能网元及存储介质
KR19990058985A (ko) 이동통신시스템에서 메시지 과부하 감지방법
JP2002314684A (ja) 通信設備、監視装置、監視制御システムおよび通信設備の監視制御方法
JP2001169340A (ja) 加入者情報管理方法、加入者情報管理システム及び加入者情報管理装置
KR20010061326A (ko) 망 연동장치의 인터넷 링크 유지 보수 방법
JP2000049805A (ja) ネットワーク管理システムのヘルスチェック方法とシステム
KR20030055731A (ko) 무선 이동 단말의 기지국 운용 제어 방법
KR20020036095A (ko) 제어국 관리기와 전기통신 관리망 간의 통계데이터 처리방법
KR20000042943A (ko) 시스템 고장을 실시간으로 관리자에게 통보하는 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase in:

Ref country code: JP