[go: up one dir, main page]

WO2003047167A2 - Procede, systeme et agent permettant de connecter des consommateurs d'evenements a des producteurs d'evenements dans un systeme de gestion d'evenement reparti - Google Patents

Procede, systeme et agent permettant de connecter des consommateurs d'evenements a des producteurs d'evenements dans un systeme de gestion d'evenement reparti Download PDF

Info

Publication number
WO2003047167A2
WO2003047167A2 PCT/CA2002/001800 CA0201800W WO03047167A2 WO 2003047167 A2 WO2003047167 A2 WO 2003047167A2 CA 0201800 W CA0201800 W CA 0201800W WO 03047167 A2 WO03047167 A2 WO 03047167A2
Authority
WO
WIPO (PCT)
Prior art keywords
event
consumer
producer
agent
notifications
Prior art date
Application number
PCT/CA2002/001800
Other languages
English (en)
Other versions
WO2003047167A3 (fr
Inventor
Edwin Tse
David Mcaleer
Andre Godin
Nicolas Gosselin
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 AU2002350301A priority Critical patent/AU2002350301A1/en
Publication of WO2003047167A2 publication Critical patent/WO2003047167A2/fr
Publication of WO2003047167A3 publication Critical patent/WO2003047167A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; 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/06—Management of faults, events, alarms or notifications
    • H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
    • H04L41/0613—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time based on the type or category of the network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/564—Enhancement of application control based on intercepted application data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention relates to network management, and in particular to a method, system and agent for dynamically connecting event consumers to event producers in a distributed event management system.
  • Event Channel Networks also called herein event management systems, or simply management systems, are network of nodes whose function is to acquire event notifications from event producers, process, and relay the event notifications to event consumers.
  • Event Producers EPs
  • Event Consumers are those nodes of the ECN that "consume" event notifications, i.e. for example, event consumers acquire event notifications from other nodes, such as for example from EPs, and process or further relay the event notifications.
  • Multiple levels of event consumers may also exist, so that for example a first event consumer may acquire event notifications from event producers, and in turn further relay some event notifications to yet another event consumer.
  • the ECN is a distributed system so that its nodes can be deployed on multiple hosts that are physically distributed into a wide geographical area.
  • An example of ECN implementation is a distributed fault management system that monitors abnormal conditions of telecommunication networks, fleet management networks, building security systems, and computing systems.
  • event notifications are generated by event producers (the managed nodes), may carry alarm information and are relayed through the store-and-forward capabilities of the ECN nodes until they reach the appropriate event consumer(s).
  • Fig. 1 Prior Art
  • Fig. 1 Prior Art
  • the managed network 12 may comprise one or more types of event producers 14;, such as for example the PC 14 ⁇ , the server 14 2 , the door access device 14 , etc.
  • event producers 14i may issue alarm notifications 16, which are collected by the ECN 10 and relayed to one or more event consumers, such as for example the network management terminal 18, wherein the alarm information from alarms 16 can be displayed, thus allowing, for example, a network administrator to take corrective action for the original abnormal condition that generated the alarms.
  • the network management terminal 18 is generally understood to be part of the ECN 10, although in Fig. 1 it is illustrated outside the ECN 10 for clarity purposes.
  • Fig. 2 (Prior Art), there is shown a generic illustration of a monitored network 12, comprising a plurality of event producers 14i, connected to the ECN 10, and relaying to the ECN event notifications 16.
  • the event notifications are generated within event producers 14j that are normally of the same type (telecommunications nodes, PCs, fleet vehicles, etc) and relayed to the event consumers 22i ofthe ECN 10.
  • Fig. 3 (Prior Art) wherein there is shown one exemplary configuration for connecting an event producer (EP1) 20 to an ECN's one or more event consumers (EC1, EC2, EC3) 22;.
  • the ECN may also comprise a plurality of intermediate nodes (Nl, N2, N3) 24; through which the event notifications 16 are passed before reaching the event consumers 22;.
  • event producer EP1 20 may generate event notifications of a certain type in which the consumers 22 ⁇ - 22 3 are interested, and for which they have subscribed their interest to ECN. Therefore, that type of event notifications 16 are sent by the event producer EP1 20 to the node Nl 24 1 , and further forwarded to the intermediate nodes N2 and N3, 24 2 and 24 3 , which again push the event notifications to event consumers EC1 and EC2, 22 ⁇ and 22 2 .
  • Node 24 ⁇ also forwards the alarm 16 directly to event consumer EC3 22 3 .
  • the communication links connecting the event producers to the event consumers are static links, i.e. their configuration is established during the set-up the ECN network and cannot be dynamically changed during operation.
  • the event producer EP1 20 can only send event notifications to the event consumer EC1 22 1 via nodes Nl 24 1 and N2 24 2 , although in certain circumstances it would be preferable to send the event notifications 16 directly to the event consumer EC1 22 ⁇ , without any intermediate step.
  • the store and forward nature of the ECN nodes often introduces event propagation delays in the transmission of the event notifications from event producers to event consumers. It also reduces the event throughput in the cases wherein the ECN guarantees event integrity (e.g. no event notification loss).
  • Johnson teaches a system and method that separate the order in which event handlers register, from the order in which the event handlers are notified of events.
  • the notification order is determined by event producers, and therefore may be reversed without re-registering the event handlers.
  • the events may be broadcast, may carry data between event handlers, and may be consumed to prevent further notifications.
  • Szymanski US Patent 5,566,337 issued to Szymanski et al (hereinafter called Szymanski) teaches a method and apparatus for distributing events in an operating system.
  • an event producer generates events and detects that an event has occurred in the computer, and that an event consumer needs to be informed.
  • the system for distributing events includes a store for storing a specific set of events of which the given event is part, and an event manager control unit for receiving the events from the event producer. The system compares the received event to the stored set of events, and distributes an appropriate event to an appropriate event consumer.
  • the issue of the connection between event producers and event consumers is not specifically addressed since both event consumers and even producers are part of the same computer system.
  • All the above-described management systems utilize static communications links between event producers and event consumers for the transmission of event notifications. This consists in a major drawback of the existing systems, since a given path may be preferable in some transmission scenarios, while being inconvenient in others. Moreover, in cases wherein a plurality of intermediate nodes are used for relaying a given type of event notifications, major delays may be engendered in the transmission of the event notifications, thus causing delays in the repair of the their cause. This unduly prolongs an abnormal condition in the managed network.
  • the present invention provides such as solution.
  • the present invention is a method for dynamically connecting an event consumer to at least an event producer, the method comprising the steps of: i) transmitting a first Subscription Request message from a first event consumer to an agent, the first Subscription Request message comprising an indication of a type of event notifications the first event consumer requests for receiving; ii) upon receipt of the first Subscription Request message, detecting in the agent if an event producer generates event notifications of the type requested by the first event consumer; iii) if an event producer generates event notifications of the type indicated by the event consumer, dynamically connecting the event producer to the first event consumer; and iv) sending event notifications of the type indicated by the event consumer from the event producer to the first event consumer.
  • the present invention is a management system comprising: a first event consumer transmitting a first Subscription Request message, the first Subscription Request message comprising an indication of a type of event notifications the first event consumer requests for receiving; one or more event producers; an agent receiving the first Subscription request from the first event consumer and, upon receipt of the first Subscription Request message, detecting if an event producer of the one or more event producers generates event notifications of the type requested by the first event consumer; wherein if an event producer generates event notifications of the type indicated by the event consumer, the agent dynamically connects the event producer to the first event consumer so that the event notifications of the type indicated by the event consumer are sent from the event producer to the first event consumer.
  • the present invention is an agent of a management system, comprising: an event producer table comprising information related to event producers managed by the agent, the information related to event producers managed by the agent comprising a type of event notifications generated by the event producers; an event consumer table comprising information related to event consumers managed by the agent, the information related to event consumers managed by the agent comprising a type of event notifications requested by the event consumers; and a processor for detecting a match between the type of event notifications generated by a first event producer from the event consumers managed by the agent, and the type of event notifications requested by a first event consumer from the event consumers managed by the agent; wherein when the match is detected, the processor dynamically connects the first event producer to the first event consumer; whereby the event notifications of the matched type are transmitted from the first event producer to the first event consumer.
  • Figure 1 is a high-level network diagram of representative of an
  • Event Channel Network responsible for supervising a managed network
  • Figure 2 (Prior Art) is a generic illustration of a monitored network connected to an ECN;
  • Figure 3 is an exemplary configuration for connecting an event producer to one or more event consumers
  • Figure ,4.a is the first part of an exemplary nodal operation and signal flow diagram of the preferred embodiment of the invention.
  • Figure 4.b is the second part of the exemplary nodal operation and signal flow diagram of the preferred embodiment of the invention
  • Figure 4.c is the third part of the exemplary nodal operation and signal flow diagram of the preferred embodiment of the invention.
  • Figure 5 is an exemplary high-level block diagram of an agent according to the preferred embodiment of the invention.
  • Figure 6 is an exemplary list of parameters that may be used by an event consumer for subscribing with the ECN for a certain type of event notifications, according to the preferred embodiment of the invention
  • Figure 7.a is an exemplary relational table of preferred connection paths between an event producer and multiple event consumers, according to a first variant of the preferred embodiment of the present invention
  • Figure 7.b is another exemplary illustration of yet another method for detecting an optimal connection path according to a second variant of the preferred embodiment of the present invention.
  • Fig. 4.a depicted therein is a first part of a nodal operation and signal flow diagram illustrating the preferred embodiment of the present invention related to the dynamic configuration of a transmission path between an event producer and one or more event consumers.
  • a management system 100 comprising one or more event producers, such as for example event producers 102 and 104, each having a respective egress port 103 and 105 for sending event notifications.
  • the management system 100 further comprises at least one event consumer such as for example event consumers 106 and 108, each having an ingress port 107 and 109, respectively, for receiving event notifications.
  • the management system 100 further comprises at least one agent 110, which is responsible for managing the connections and communications between the event producers 102-104 and the event consumers 106- 108.
  • the management system 100 may further comprise one or more intermediate nodes, such as for example node 112 responsible in some cases for relaying event notifications from the event producers toward the event consumers, and a dummy event consumer 114 that discards every event notification received on its ingress port 115.
  • the dummy event consumer 114 is used when none of the event consumers is interested in receiving certain event notifications, and acts to discards those event notifications.
  • an event producer such as for example event producer 104 transmits an event notification advertisement message 120 to the agent 110 and for specifying which categories 122 of event notifications, the event producer 104 can generate.
  • the agent 110 detects in action 124 that no event consumer of the management system 100 is so far interested in receiving this type of event notifications, and therefore connects the egress port 105 of the event producer 104 to the ingress port 115 of the dummy event consumer 114, action 126.
  • all the event notifications of the event notification category 122 generated by the event producer 104 are received, action 128, and discarded, action 130, by the dummy consumer 114.
  • Fig. 5 illustrates a high-level block diagram of the agent 110 according to the preferred embodiment of the invention.
  • the agent 110 which comprises an event producer table (or list) 200 having the event notification categories 202 and 204 that each one of the event producer generates, as well as the respective egress port identity 206 and 208 that each such event producer use for sending event notifications.
  • the event producers table 200 only comprises one line directed to the event producer EP 1 104.
  • the agent 110 also comprises an event consumer list 210 having each event consumer managed by the agent 110.
  • the list 210 only comprises one line directed to the dummy event consumer (DC) 114, with the identity of the ingress port 212 that the dummy event consumer uses for receiving event notifications. Therefore, based on the information contained in the event producer table 200 and the event consumers table 210, a processor 213 of the agent 110 is capable of detecting in action 124 of Fig.
  • an event consumer of the management system 100 such as for example event consumer 106 may manifest an interest in receiving a certain type of event notifications.
  • the event consumer 106 sends a subscription request message 132 to the agent 110, subscription request message 132 comprising at least one type parameter 134 indicative of which event notifications the event customer 106 is interested in receiving.
  • Fig. 4.a there is shown an exemplary illustration of a list of parameters that may be used by an event consumer like the event consumer 106 for subscribing with the agent 110 for a certain type of event notifications, according to the preferred embodiment of the invention.
  • the at least one parameter 134 of message 132 preferably includes at least one of the parameters 134 ⁇ to 134 3 as shown in Fig. 6.
  • the agent 110 upon receipt of the subscription request message 132 from the event customer 106, the agent 110 first updates the event consumers list 210, action 136, by including the parameters 134; received in message 132 into a record of the list 210 corresponding to the event consumer EC1 106.
  • a record of table 210 shown in Fig. 5 may be updated to comprise information related to the type of event notifications the event consumer 106 is interested in receiving, the information comprising at least one of the parameters 134 ⁇ to 134 3 .
  • the processor 213 of the agent 110 detects a match between the type of event notifications output by event producer 104 and the type of event notifications the event consumer 106 has subscribed for, action 138. For example, such a match may be detected when the notification category parameter 134 3 recorded in table 210 for the event consumer 106 is the same with the notification category parameter 202 recorded in the event producer table 200 for the event producer 104.
  • the agent 110 may optionally send a Suspend message 139 to instruct the event producer 104 to stop sending events, so that no event is lost during the drop of the old connection and the setup of the new one. In such an instance, the event producer 104 suspends its transmission of events at step 141.
  • the agent 110 further disconnects the egress port 105 of event producer 104 from the ingress port 115 of the dummy consumer 114, action 140, and because the only actual event consumer interested in the event notifications of event producer 104 is now the event consumer 106, the agent establishes a new connection between the egress port 105 of the event producer 104 and the ingress port of the event consumer 106, action 142.
  • the agent 110 sends a Resume message 143 to instruct event producer 104 to resume sending event notifications, action 143.
  • event notifications produced by the event producer 104 that are compliant with the type of event notifications the event consumer 106 is interested in receiving, are sent from the egress port 105 of event producer 104 to the egress port 107 of event consumer 106, action 144.
  • yet another event consumer of the management system 100 such as for example event consumer 108 may manifest an interest in receiving a similar type of event notifications.
  • the event consumer 108 proceeds in a similar manner as the one described hereinabove, and sends a subscription request 146 to the agent 110, the subscription request message 146 comprising at least one type parameter 134 indicative of which event notifications the event consumer 108 is interested in receiving.
  • the type parameter of message 146 is assumed to be the same as the type parameter 134 of the previous message 132 and indicates an interest of event consumer 108 for the same event notifications as event consumer 106 is interested in.
  • the agent 110 Upon receipt of the subscription request message 146 from the event consumer 108, the agent 110 first updates the event consumers lists 210, action 148, by including the parameters 134 ⁇ of message 146 in a record of the list 210 directed to the event consumer EC2 108, as shown in Fig. 5.
  • the record of table 210 may be updated as to comprise information related to the type of event notifications the event consumer 108 is interested in receiving, this information comprising the at least one of the parameters 134 ⁇ to 134 3 .
  • the agent 110 detects a match between the type of event notifications output by event producer EP1 104 and the type of event notifications the event consumers ECI 106 and EC2 108 have subscribed for, action 150.
  • the agent 110 has knowledge that two (2) event consumers (event customer 106 and event consumer 108) are both interested in event notifications generated by the event producer 104. Therefore, in action 152, the agent 110 detects the optimal duplication node for duplicating the event notifications information generated by the event producer 104 in view of its transmission to both event consumers 106 and 108.
  • Figure 4.b is the second part of the exemplary nodal operation and signal flow diagram of Fig. 4.a. Thereafter, the agent 110 may optionally send a Suspend message 153 to instruct the event producer 104 to stop sending events, so that no event is lost during the drop of the old connection and the set-up of the new one.
  • the agent 110 terminates the existing connection between the egress port 105 of the event producer EP1 104 and the ingress port 107 of the event customer ECI 106, and in action 156 connects the egress port 105 of the event producer 104 to the ingress port 111 of the intermediate node 112 detected as being the optimal duplication node in action 152.
  • the agent 110 further connects the egress port 113 of the node 112 with the ingress port 107 of the event customer 106, action 158, and also connects the egress port
  • the agent 110 may send a Resume message 161 to instruct the event producer 104 to resume sending event notifications.
  • subsequent event notifications produced by the event producer EP1 104 are sent from the event producer 104 to the intermediate node 112 where they are split and further sent to both event consumers 106 and 108, as shown in action 162.
  • the method described in Fig. 4 may further continue and provide support for the transmission of event notifications generated by event producers to other event consumers (not shown) that subscribe with agent 110, in a manner similar to the one described hereinbefore.
  • the agent 110 may detect in actions similar to action 152, the optimal connection path between one or more event producer(s) and the one or more event consumers interested in that or those event producer(s)' event notifications, and then establish a connection according to the preferred connection path.
  • the match detection between the type of event notification produced by one or more given event producers and the type of event notification requested by one or more event producers may be preformed responsive to either i) an advertisement message like message 120 or ii) as already described, a subscription request message like message 132.
  • the agent 110 may further receive an advertisement message 206 from another event producer, e.g. event producer 103 that registers with the agent 110 its type 208 of event notifications it produces.
  • event producer 103 e.g. event producer 103 that registers with the agent 110 its type 208 of event notifications it produces.
  • the agent 110 registers in its event producers table the type of event notifications 218, action 210, and detect a match between the type of event notifications produced, on one side, by the event producers 102 and 104, and the type of event notifications requested, on the other side, by the event consumers 106 and 108, action 212.
  • action 214 the agent 110 detects the optimal intermediate node for relaying the event notifications to the event consumers.
  • the agent 110 sends a Suspend message for instructing the event producer 104 to suspend the transmission of event notifications during the set-up of the new connection, which the event producer does in action 217. Then, in action 218 the agent 110 terminates the existing connections between the event producer 104 and the intermediate node Nl 112, and between the intermediate node Nl 112 and the event consumers 106 and 108.
  • the agent 110 dynamically establishes new connections between the event producer 104 and the intermediate node N2 200, detected as being the optimal duplication node, and between the intermediate node N2 200 and the event consumers 106 and 108. Likewise, the agent 110 also establishes new connections between the event producer 102 and the intermediate node N2 200, and between the intermediate node N2 200 and the event consumers 106 and 108. The agent 110 may further optionally send a Resume message 222 to instruct event producer 104 to resume sending event notifications, and a Start message 224 to instruct event producer 102 to start sending event notifications.
  • subsequent event notifications produced by the event producer EP1 104 are sent from the egress port 105 of the event producer 104 to the ingress port 202 of the intermediate node N2 200, where they are split, and further sent to the ingress ports 107 and 109 of respective event consumers 106 and 108, as shown in action 226, while subsequent event notifications produced by the event producer EP2 102 are sent from the egress port 103 of the event producer 102 to the ingress port 202 of the intermediate node N2 200, . where they are split, and further sent to the ingress ports 107 and 109 of respective event consumers 106 and 108, as shown in action 228.
  • the detection of the optimal connection path may be performed in various manners, depending upon the preference of the network operator, and based upon various factors.
  • Figure 7.a is an exemplary relational table of preferred, connection paths according to a first variant of the preferred embodiment of the present invention.
  • table 300 may comprise pre-determined connection paths 302; between one event producer, such as one of event producers EP1 102 and EP2 104, and a corresponding group 304; of event consumers.
  • table 300 may be stored in agent 110 and include indications of the preferred path given one or more event producers that are to be coimected to one or more vent consumers.
  • these indications may comprise information stating that: i) in the case wherein event consumers of group 304j (event consumers ECI
  • the optimal connection path is through the intermediate node Nl 112; ii) in the case wherein event consumers of group 304 2 (event consumers 106,
  • the optimal connection path is through the intermediate node Nl 112 that duplicates the event notifications before relaying them to both event consumers ECI 106 and EC2 108, and through the intermediate node N2 119 that relays the vent notifications to the event consumer EC3 117 (not shown in Fig. 4.a and Fig. 4.b); iii) in the case wherein event consumers EP1 104 and EP2 106 are to be connected to event consumers ECI 106 and EC2 108, the preferred connection path is the duplication node N2 200.
  • Figure 7.b is another exemplary illustration of yet another method for detecting an optimal connection path according to a second variant of the preferred embodiment of the present invention.
  • the method for selecting the optimal connection path starts by detecting if more than two (2) event consumers are to be connected for receiving the same event notifications generated by a given event consumer, action 400. If not, then the optimal intermediate node for duplicating the event notifications is the intermediate node closest to the event consumers, action 402.
  • the method selects i) a first intermediate node closest to the event consumers for duplicating the event notifications for sending them to the first two event consumers and ii) a second intermediate node as close as possible to the event consumers for duplicating the event notifications and for sending them to the next event consumers. The pattern is repeated until all event consumers are assigned paths for receiving the requested event notifications.
  • the present invention provides an advantageous solution, which offers dynamic set up of connections between event consumers interested in receiving event notifications from certain event producers.
  • the system, method, and agent described in the present invention may function according to the specification of the "3 rd Generation Partnership Project (3GPP)'s Technical Specification Group Services and System Aspect, Telecommunication Management, Part II: Notification Integration Reference Point: Information Service Version 1 (Release 1999) - 3GPP TS 32.106-2", herein included by reference.
  • 3GPP 3 rd Generation Partnership Project
  • 3GPP TS 32.106-2 3 rd Generation Partnership Project
  • the processor 213 shown in the agent 110 of Fig. 5 may be any kind of hardware or software (or a combination thereof) processing functionality.
  • the tables (lists) 200 and 210 of Fig. 3 may also be implemented using any kind of memory functionality, such as for example but not limited to, a table, a chip memory, a database, a list, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Environmental & Geological Engineering (AREA)
  • Computer And Data Communications (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un procédé, un système et un agent permettant de connecter de manière dynamique des producteurs d'événements à des consommateurs d'événements lorsque le type de notifications d'événement demandé par un ou des consommateurs d'événements correspond au type de notifications d'événement émis par un ou des producteurs d'événements. L'agent reçoit une annonce ou une demande d'abonnement en provenance de producteurs et de consommateurs d'événements, et il détecte une correspondance entre le type de notifications d'événement créé par des producteurs d'événements et demandés par des consommateurs d'événements. A ce moment, l'agent connecte de manière dynamique le port de sortie du producteur d'événements au port d'entrée du consommateur d'événements. Lorsque l'agent reçoit une autre demande d'abonnement d'un autre consommateur d'événement pour le même type de notifications d'événement, il détecte le noeud optimal de façon à dupliquer ces notifications d'événement avant de les envoyer aux deux consommateurs d'événements. L'agent comprend un processeur, un tableau de producteur d'événements et un tableau de consommateur d'événements stockant les types de notifications d'événement de chaque noeud.
PCT/CA2002/001800 2001-11-30 2002-11-29 Procede, systeme et agent permettant de connecter des consommateurs d'evenements a des producteurs d'evenements dans un systeme de gestion d'evenement reparti WO2003047167A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2002350301A AU2002350301A1 (en) 2001-11-30 2002-11-29 Method, system and agent for connecting event consumers to event producers in a distributed event management system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/999,084 US20030105801A1 (en) 2001-11-30 2001-11-30 Method, system and agent for connecting event consumers to event producers in a distributed event management system
US09/999,084 2001-11-30

Publications (2)

Publication Number Publication Date
WO2003047167A2 true WO2003047167A2 (fr) 2003-06-05
WO2003047167A3 WO2003047167A3 (fr) 2003-12-04

Family

ID=25545877

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2002/001800 WO2003047167A2 (fr) 2001-11-30 2002-11-29 Procede, systeme et agent permettant de connecter des consommateurs d'evenements a des producteurs d'evenements dans un systeme de gestion d'evenement reparti

Country Status (3)

Country Link
US (1) US20030105801A1 (fr)
AU (1) AU2002350301A1 (fr)
WO (1) WO2003047167A2 (fr)

Families Citing this family (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7143417B2 (en) * 2002-01-10 2006-11-28 International Business Machines Corporation Notification services within a unified communications service
CA2416337A1 (fr) * 2003-01-14 2004-07-14 Cognos Incorporated Forage transversal contextuel dans un systeme de gestion d'evenements
US20040139444A1 (en) * 2003-01-14 2004-07-15 Hope Clifford C. Notification service in an event management system
CA2416359A1 (fr) * 2003-01-14 2004-07-14 Cognos Incorporated Detection de tendance dans un systeme de gestion d'evenements
US20040139448A1 (en) * 2003-01-14 2004-07-15 Hope Clifford C. Interative escalation in an event management system
CA2416352A1 (fr) * 2003-01-14 2004-07-14 Cognos Incorporated Modification de comportement autonome dynamique d'un systeme de gestion d'evenements
US8230445B2 (en) 2003-01-14 2012-07-24 International Business Machines Corporation Event management method and system
CA2416400A1 (fr) * 2003-01-14 2004-07-14 Cognos Incorporated Systeme et methode de gestion d'evenements
CA2416357A1 (fr) * 2003-01-14 2004-07-14 Cognos Incorporated Suppression de messages dans un systeme de gestion d'evenements
US20040139452A1 (en) * 2003-01-14 2004-07-15 Hope Clifford C. Dynamic recipients in an event management system
JP2005322016A (ja) * 2004-05-10 2005-11-17 Yokogawa Electric Corp サーバ装置および情報配信方法
US8448182B2 (en) * 2005-09-27 2013-05-21 Oracle International Corporation System and method for pause and resume message operations on destinations
US8069452B2 (en) 2005-12-01 2011-11-29 Telefonaktiebolaget L M Ericsson (Publ) Method and management agent for event notifications correlation
US20070153828A1 (en) * 2006-01-04 2007-07-05 Cisco Technology, Inc. System and method to negotiate the addition or deletion of a PPP link without data loss
US8146100B2 (en) * 2006-03-21 2012-03-27 Sap Ag System and method for event-based information flow in software development processes
US8087032B2 (en) * 2008-03-31 2011-12-27 International Business Machines Corporation Automated recovery process initiation for data consumers of a common information model (CIM) managed component
US20120066694A1 (en) 2010-09-10 2012-03-15 International Business Machines Corporation Event overflow handling by coalescing and updating previously-queued event notification
US8694625B2 (en) * 2010-09-10 2014-04-08 International Business Machines Corporation Selective registration for remote event notifications in processing node clusters
US8984119B2 (en) * 2010-11-05 2015-03-17 International Business Machines Corporation Changing an event identifier of a transient event in an event notification system
US8667126B2 (en) 2010-12-03 2014-03-04 International Business Machines Corporation Dynamic rate heartbeating for inter-node status updating
US8433760B2 (en) 2010-12-03 2013-04-30 International Business Machines Corporation Inter-node communication scheme for node status sharing
US8634328B2 (en) 2010-12-03 2014-01-21 International Business Machines Corporation Endpoint-to-endpoint communications status monitoring
US8634330B2 (en) 2011-04-04 2014-01-21 International Business Machines Corporation Inter-cluster communications technique for event and health status communications
US11949700B2 (en) 2017-05-15 2024-04-02 Forcepoint Llc Using content stored in an entity behavior catalog in combination with an entity risk score
US11632382B2 (en) 2017-05-15 2023-04-18 Forcepoint Llc Anomaly detection using endpoint counters
US10999296B2 (en) 2017-05-15 2021-05-04 Forcepoint, LLC Generating adaptive trust profiles using information derived from similarly situated organizations
US10318729B2 (en) 2017-07-26 2019-06-11 Forcepoint, LLC Privacy protection during insider threat monitoring
US10999324B2 (en) 2017-08-01 2021-05-04 Forcepoint, LLC Direct-connect web endpoint
US11509728B2 (en) * 2018-06-29 2022-11-22 Nokia Solutions And Networks Oy Methods and apparatuses for discovering a network function acting as network function service consumer
US10885186B2 (en) 2018-11-13 2021-01-05 Forcepoint, LLC System and method for operating a protected endpoint device
US11754419B2 (en) * 2019-12-05 2023-09-12 Aclara Technologies Llc Auto-detection of communication module protocol in utility metering systems
US20230070455A1 (en) * 2020-02-10 2023-03-09 Nokia Technologies Oy Devices, methods, apparatus and computer readable storage media for service management in a communication system
CN113573282B (zh) * 2020-04-29 2022-09-16 中国电信股份有限公司 订阅数据的提供/获取方法、提供/获取装置和交互系统
US11838275B2 (en) 2021-03-12 2023-12-05 Forcepoint Llc Web endpoint device having automatic switching between proxied and non-proxied communication modes

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0759591A1 (fr) * 1995-08-18 1997-02-26 International Business Machines Corporation Service de gestion d'événements
WO2001071976A2 (fr) * 2000-03-20 2001-09-27 Telefonaktiebolaget Lm Ericsson (Publ) Equilibrage de la charge de traitement par le filtrage de canaux de notification
WO2001086439A2 (fr) * 2000-05-09 2001-11-15 Sun Microsystems, Inc. Points d'extremite de message d'evenement dans un environnement informatique reparti (environnement dce)

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3357956B2 (ja) * 1992-08-06 2002-12-16 日本電気エンジニアリング株式会社 判定帰還形等化器
US5566337A (en) * 1994-05-13 1996-10-15 Apple Computer, Inc. Method and apparatus for distributing events in an operating system
US5713045A (en) * 1995-06-29 1998-01-27 Object Technology Licensing Corporation System for processing user events with input device entity associated with event producer which further links communication from event consumer to the event producer
US6477585B1 (en) * 1995-08-18 2002-11-05 International Business Machines Corporation Filter mechanism for an event management service
US5925108A (en) * 1995-11-03 1999-07-20 Novell, Inc. Event notification in a computer system
US5721825A (en) * 1996-03-15 1998-02-24 Netvision, Inc. System and method for global event notification and delivery in a distributed computing environment
FR2762950B1 (fr) * 1997-05-02 2000-08-04 Alsthom Cge Alcatel Procede de transmission d'une notification dans un reseau a applications distribuees comportant plusieurs services de notifications et reseau pour sa mise en oeuvre
US6782541B1 (en) * 1999-05-28 2004-08-24 Avaya Technology Corp. System and method of exchanging information between software modules
US6671742B1 (en) * 1999-06-15 2003-12-30 At&T Corp. Method and apparatus for unifield control and data event exchange in a software system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0759591A1 (fr) * 1995-08-18 1997-02-26 International Business Machines Corporation Service de gestion d'événements
WO2001071976A2 (fr) * 2000-03-20 2001-09-27 Telefonaktiebolaget Lm Ericsson (Publ) Equilibrage de la charge de traitement par le filtrage de canaux de notification
WO2001086439A2 (fr) * 2000-05-09 2001-11-15 Sun Microsystems, Inc. Points d'extremite de message d'evenement dans un environnement informatique reparti (environnement dce)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CISCO SYSTEMS: "Multicast Deployment Made Easy - IP Multicast Planning and Deployment Guide" DESIGN IMPLEMENTATION GUIDE, [Online] 1999, pages 1-20, XP002255585 Retrieved from the Internet: <URL:http://www.cisco.com/warp/public/cc/t echno/tity/ipmu/tech/ipcas_dg.pdf> [retrieved on 2003-09-24] *

Also Published As

Publication number Publication date
WO2003047167A3 (fr) 2003-12-04
US20030105801A1 (en) 2003-06-05
AU2002350301A1 (en) 2003-06-10
AU2002350301A8 (en) 2003-06-10

Similar Documents

Publication Publication Date Title
US20030105801A1 (en) Method, system and agent for connecting event consumers to event producers in a distributed event management system
US6484200B1 (en) Distinguished name scoping system for event filtering
US8149725B2 (en) Methods, systems, and computer program products for a hierarchical, redundant OAM&amp;P architecture for use in an IP multimedia subsystem (IMS) network
JP4756188B2 (ja) メッセージングアプリケーションルータ
US10749735B2 (en) Method and management agent for event notifications correlation
US6665262B1 (en) Distributed fault management architecture
US20100228843A1 (en) Element management system in wireless communication network
US9237077B2 (en) Monitoring persistent client connection status in a distributed server environment
US20040139179A1 (en) Method and system for router misconfiguration autodetection
EP1947806A1 (fr) Procede, systeme et terminal de trace de service, element reseau
WO2009050184A1 (fr) Commande de services de pousser
MXPA04006830A (es) Deteccion remota de estados de suministro de energia.
US20030084147A1 (en) Maintenance of third party service&#39;s subscription information
US7010795B2 (en) Process for sending a notification in a data processing network with distributed applications
CN113824595B (zh) 链路切换控制方法、装置和网关设备
CN113259185B (zh) 网管代理以及网元管理平台
EP1766943A2 (fr) Systeme et procede de suivi de communications de bout en bout
JPH11340991A (ja) マルチキャストを用いたネットワ−ク監視方式
US7330437B1 (en) Checking connectivity for point-to-multipoint connections
CN112437146A (zh) 一种设备状态同步方法、装置及系统
JP3794348B2 (ja) 局側伝送装置および通信システム監視方法
CN101499879A (zh) 一种故障反馈方法、系统及装置
KR100224106B1 (ko) 통신시스템의 전송장비를 원격에서 설치하는 방법
CN119232616A (zh) 网络环路位置的检测方法和系统、存储介质、电子设备
CN112217670A (zh) 网络设备及网络设备的报文处理方法

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 OM PH PL PT RO RU SC SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM 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 ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR BF BJ CF CG CI CM GA GN GQ 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)
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP