Method, system and agent for connecting event consumers to event producers in a distributed event management system

• US 20030105801A1
• Filed: 11/30/2001
• Published: 06/05/2003
• Est. Priority Date: 11/30/2001
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Tse, Edwin, McAleer, David, Godin, Andre, Gosselin, Nicolas
• Application Number:
  US09/999,084
• Publication Number:
  US 20030105801A1
• Time in Patent Office: Days
• US Class Current: 709/202
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 41/0613 based on the type or category of the network elements
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

In a management system, a method, system, and agent for dynamically connecting event producers to event consumers, when the type of event notifications requested by event consumer(s) matches the type of event notification issued event producer(s). The agent receives advertisement or subscription request from event producers and consumers, and detects a match between the type of event notifications created by event producers and requested by event consumers. When a match is detected, the agent dynamically connects the egress port of the event producer to the ingress port of the event consumer. When another subscription request is received by the agent from another event consumer for the same type of event notifications, the agent first detects the optimal duplication node for duplicating the event notifications before sending them to both event consumers. The agent comprises a processor, an event producer table, and an event consumer table for storing the event notifications type each node generates or requests.

Claims

1. In a management system, 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.

2. The method claimed in claim 1, wherein the step iii) of dynamically connecting the event producer to the first event consumer comprises the step of:

v) dynamically connecting an egress port of the event producer to an ingress port of the first event consumer;

whereby the egress port of the event producer is used by the event producer to send event notifications, and the ingress port of the first event consumer is used by the first event consumer to receive event notifications.

3. The method claimed in claim 1, wherein the indication of the type of event notifications that the event consumer requests for receiving comprises a notification category parameter indicative of at least one notification category the event consumer requests for receiving.

4. The method claimed in claim 1, wherein prior to the step i) of transmitting the first Subscription Request message, the method further comprises the steps of:

vi) transmitting an advertisement message from the event producer to the agent, the advertisement message comprising an event category indicative of a type of event notifications the event producer generates; and

vii) registering in the agent the event category indicative of the type of event notifications the event producer generates.

5. The method claimed in claim 4, wherein step vii) of registering in the agent the event category indicative of the type of event notifications the event producer generates, comprises the step of:

registering in an event producer table of the agent an identity of the event producer, an identity of an egress port of the event producer, and the event category indicative of the type of event notifications the event producer generates.

6. The method claimed in claim 4, further comprises following step vii) but before step i) the steps of:

viii) detecting that no event consumer registered with the agent an interest in receiving event notifications of the category the event producer generates;

ix) connecting the event producer to a dummy event consumer that discards every received event notification;

x) sending the event notifications of the category the event producer generates from the event producer to the dummy event consumer; and

xi) upon receipt in the dummy event consumer, discarding the event notifications of the category the event producer generates.

7. The method claimed in claim 6, wherein:

step ix) comprises connecting the egress port of the event producer to an ingress port of the dummy event consumer;

step x) comprises sending the event notifications of the category the event producer generates from the egress port of the event producer to the ingress port of the dummy event consumer.

8. The method claimed in claim 6, further comprises before step iii) of dynamically connecting the event producer to the first event consumer, the step of:

disconnecting the event producer from the dummy event consumer.

9. The method claimed in claim 1, further comprising the steps of:

v) transmitting a second Subscription Request message from a second event consumer to the agent, the second Subscription Request message comprising an indication of a type of event notifications the second event consumer requests for receiving;

vi) upon receipt of the second Subscription Request message, detecting in the agent that the type of event notifications the second event consumer is interested in receiving is the same as the type of event notifications generated by the event producer and currently received by the first event consumer;

vii) detecting an optimal intermediate duplication node for duplicating the event notifications generated by the event producer in view of their transmission to both the first and the second event consumer;

viii) disconnecting the event producer from the first event consumer;

ix) dynamically connecting the event producer to detected optimal intermediate duplication node;

x) dynamically connecting the detected optimal intermediate duplication node to the first event consumer;

xi) dynamically connecting the detected optimal intermediate duplication node to the second event consumer; and

viii) sending the event notifications of the given type from the detected optimal intermediate duplication node to both the first and the second event producers.

10. The method claimed in claim 9, wherein:

the step viii) comprises disconnecting an egress port of the event producer from an ingress port of the first event consumer;

the step ix) comprises dynamically connecting the egress port of the event producer to an ingress port of the detected optimal intermediate duplication node;

the step x) comprises dynamically connecting an egress port of the detected optimal intermediate duplication node to the ingress port of the first event consumer;

the step xi) comprises dynamically connecting the egress port of the detected optimal intermediate duplication node to an ingress port of the second event consumer; and

the step viii) comprises sending the event notifications of the given type a) from the egress port of the detected optimal intermediate duplication node to the ingress port of the first event producers, and b) from the egress port of the detected optimal intermediate duplication node to the ingress port of the second event producers.

11. 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, detects 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.

12. The management system claimed in claim 11, wherein:

the event producer comprises an egress port for sending event notifications;

the first event consumer comprises an ingress port for receiving event notifications; and

the agent dynamically connects the egress port of the event producer to the ingress port of the first event consumer.

13. The management system claimed in claim 11, wherein the indication of the type of event notifications that the event consumer requests for receiving comprises a notification category parameter indicative of at least one notification category the event consumer requests for receiving.

14. The management system claimed in claim 11, wherein before the transmission of the first Subscription Request message by the first event consumer, the event producer transmits an advertisement message to the agent, the advertisement message comprising an event category indicative of the type of event notifications the event producer generates, and the agent registers the event category indicative of the type of event notifications the event producer generates.

15. The management system claimed in claim 14, wherein the agent comprises an event producer table for registering an identity of the event producer, an identity of an egress port of the event producer, and the event category indicative of the type of event notifications the event producer generates.

16. The management system claimed in claim 14, further comprising:

a dummy event consumer that discards every received event notification;

wherein when the agent detects that no event consumer registered with the agent requested to receive event notifications of the category the event producer generates, the agent connects the event producer to the dummy event consumer and sends the event notifications of the category the event producer generates from the event producer to the dummy event consumer, which discards the event notifications upon receipt.

17. The management system claimed in claim 16, wherein:

the agent connects the egress port of the event producer to an ingress port of the dummy event consumer, and the event notifications of the category the event producer generates are sent from the egress port of the event producer to the ingress port of the dummy event consumer.

18. The management system claimed in claim 16, wherein before dynamically connecting the event producer to the first event consumer, the agent first disconnects the event producer from the dummy event consumer.

19. The management system claimed in claim 11, wherein:

a second event consumer transmits a second Subscription Request message to the agent, the second Subscription Request message comprising an indication of a type of event notifications the second event consumer requests for receiving;

upon receipt of the second Subscription Request message, the agent detects that the type of event notifications the second event consumer is interested in receiving is the same as the type of event notifications generated by the event producer and currently received by the first event consumer;

the agent detects an optimal intermediate duplication node for duplicating the event notifications generated by the event producer in view of their transmission to both the first and the second event consumer;

the agent disconnects the event producer from the first event consumer;

the agent dynamically connects the event producer to the detected optimal intermediate duplication node;

the agent dynamically connects the detected optimal intermediate duplication node to the first event consumer;

the agent dynamically connects the detected optimal intermediate duplication node to the second event consumer; and

the event producer sends the event notifications to the detected optimal intermediate duplication nodes, which relays the event notifications to both the first and the second event producers.

20. The management system claimed in claim 19, wherein:

when the agent disconnects the event producer from the first event consumer, the agent disconnects an egress port of the event producer from an ingress port of the first event consumer;

when the agent dynamically connects the event producer to the detected optimal intermediate duplication node, the agent dynamically connects the egress port of the event producer to an ingress port of the detected optimal intermediate duplication node;

when the agent dynamically connects the detected optimal intermediate duplication node to the first event consumer, the agent dynamically connects an egress port of the detected optimal intermediate duplication node to the ingress port of the first event consumer;

when the agent dynamically connects the detected optimal intermediate duplication node to the second event consumer, the agent dynamically connects the egress port of the detected optimal intermediate duplication node to an ingress port of the second event consumer; and

when the event notifications of the given type are relayed to both the first and the second event producers, the event notifications of the given type are sent from the egress port of the detected optimal intermediate duplication node to the ingress port of the first event producers, and from the egress port of the detected optimal intermediate duplication node to the ingress port of the second event producer.

21. 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.

22. The agent claimed in the management system claimed in claim 21, wherein:

the event producer table comprises, for each event producer registered with the agent, an identity of the event producer, an address of an egress port of the event producer, and an event category identifying the type of event notifications produced by the event producer;

the event consumer table comprises, for each event consumer registered with the agent, an identity of the event consumer, an address of an ingress port of the event consumer, and an event category identifying the type of event notifications requested by the event consumer; and

when the processor detects a match between an event category identifying the type of event notifications produced by the first event producer and an event category identifying the type of event notifications requested by the first event consumer, the processor dynamically connects the egress port of the first event producer to the ingress port of the first event consumer.

23. The agent claimed in claim 21, wherein the match is detected responsive to a receipt by the agent of an advertisement message sent by the first event producer, the advertisement message comprising a first event category identifying the type of event notifications produced by the first event producer.

24. The agent claimed in claim 21, wherein the match is detected responsive to a receipt by the agent of subscription request message sent by the first event consumer, the subscription request message comprising a first event category identifying the type of event notifications requested by the first event consumer.

25. The agent claimed in claim 22, wherein the agent'"'"'s event producer table is provided with the information related to event producers managed by the agent from advertisement messages received from the event producers managed by the agent, each advertisement message comprising the type of event notifications generated by that event producer.

26. The agent claimed in claim 23, wherein:

the agent receives a second Subscription Request message from a second event consumer, the second Subscription Request message comprising an indication of a type of event notifications the second event consumer requests for receiving;

upon receipt of the second Subscription Request message, the agent'"'"'s processor detects that the type of event notifications the second event consumer requests for receiving is the same as the type of event notifications generated by the event producer and currently received by the first event consumer;

the agent detects an optimal intermediate duplication node for duplicating the event notifications generated by the event producer in view of their transmission to both the first and the second event consumer;

the agent disconnects the event producer from the first event consumer;

the agent dynamically connects the event producer to the detected optimal intermediate duplication node;

the agent dynamically connects the detected optimal intermediate duplication node to the first event consumer;

the agent dynamically connects the detected optimal intermediate duplication node to the second event consumer; and

the event producer sends the event notifications to the detected optimal intermediate duplication nodes, which relays the event notifications to both the first and the second event producers.

27. The agent claimed in claim 26, wherein:

when the agent disconnects the event producer from the first event consumer, the agent disconnects an egress port of the event producer from an ingress port of the first event consumer;

when the agent dynamically connects the event producer to the detected optimal intermediate duplication node, the agent dynamically connects an egress port of the event producer to an ingress port of the detected optimal intermediate duplication node;

when the agent dynamically connects the detected optimal intermediate duplication node to the first event consumer, the agent dynamically connects an egress port of the detected optimal intermediate duplication node to the ingress port of the first event consumer;

when the agent dynamically connects the detected optimal intermediate duplication node to the second event consumer, the agent dynamically connects the egress port of the detected optimal intermediate duplication node to an ingress port of the second event consumer; and

when the event notifications of the given type are relayed to both the first and the second event producers, the event notifications of the given type are sent from the egress port of the detected optimal intermediate duplication node to the ingress port of the first event producers, and from the egress port of the detected optimal intermediate duplication node to the ingress port of the second event producer.

28. The agent claimed in claim 21, wherein when the match is detected, the agent dynamically connects the first event producer to the first event consumer via at least one intermediate node.

29. The agent claimed in claim 21, wherein the processor detects a match between the type of event notifications generated by the first event producer and a type of event notifications requested by i) the first event consumer and ii) a second event consumer from the event consumers managed by the agent and, when the match is detected, the agent dynamically connects the first event producer to the first and second event consumers via at least one intermediate node.

30. The agent claimed in claim 29, wherein the at least one intermediate node comprises an optimal duplication node for duplicating event notifications received from the first event producer for relaying the event notifications to the first and second event consumers.

31. The agent claimed in claim 21, wherein the processor detects a match between a type of event notifications generated on one side by the first event producer and a second event producer from the event consumers managed by the agent, and on the other side, a type of event notifications requested by the first event consumer and a second event consumer from the event consumers managed by the agent, and, when the match is detected, the agent dynamically connects the first event producer and the second event producer to the first event consumer and the second event consumer via at least one intermediate node.

32. The agent claimed in claim 31, wherein the at least one intermediate node comprises an optimal duplication node for duplicating i) event notifications received from the first event producer for relaying the event notifications to the first and second event consumer, and ii) event notifications received from the second event producer for relaying the event notifications to the first and second event consumers.