Event bus with passive queuing and active routing

• US 20040028069A1
• Filed: 08/07/2002
• Published: 02/12/2004
• Est. Priority Date: 08/07/2002
• Status: Abandoned Application

• Current Assignee: Daedalus Blue LLC
• Original Assignee: Daedalus Blue LLC
• Inventors: Tindal, Glen D., Schenk, Jeffery A.
• Application Number:
  US10/213,950
• Publication Number:
  US 20040028069A1
• Time in Patent Office: Days
• US Class Current: 370/429
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 45/56 Routing software

Abstract

An event bus for managing network event messages is described. In one embodiment, the event bus includes an interface for receiving an event message; a routing manager configured to determining whether an event message received at the interface should be routed to a destination device or whether it should be queued for retrieval by the destination device; a queue for storing the event message; and a network event storage device configured to store a copy of the event message.

Claims

1. A method for managing an event message, the method comprising the steps of:

receiving the event message at a central event messaging location;

determining whether the received event message should be routed to a destination device or whether the received event message should be queued for retrieval by the destination device;

responsive to determining that the received event message should be routed to the destination device, routing the event message to the destination device; and

responsive to determining that the received event message should be queued, queuing the received network event message.

2. The method of claim 1, wherein the step of receiving the event notification comprises the step of:

receiving an indicator of the type of the event message.

3. The method of claim 2, wherein the step of determining comprises the steps of:

determining whether the indicator indicates that the event message is of a first type or a second type;

responsive to the indicator indicating that the event message is of the first type, determining to route the event message; and

responsive to the indicator indicating that the event message is of the second type, determining to queue the event message in a queue.

4. The method of claim 1, further comprising the step of:

storing the event message in an event database.

5. The method of claim 4, further comprising the step of:

storing the event message in an event database responsive to determining that the event message should be routed to the destination device.

6. The method of claim 1, wherein the step of receiving comprises the step of:

receiving the event message at a central messaging location included with a network manager unit.

7. The method of claim 1, further comprising the step of:

retrieving a queued event message from the queue.

8. The method of claim 7, further comprising the step of:

altering the operation of the destination device according to the event message retrieved from the queue.

9. An event bus comprising:

an interface for receiving an event message;

a routing manager in communication with the interface, the interface configured to determining whether an event message received at the interface should be routed to a destination device or whether the event message should be queued for retrieval by the destination device;

a queue in communication with the interface, the queue for storing the event message responsive to the routing manager determining that the event message received at the interface should be queued; and

a network event storage device in communication with the interface, the network event storage device configured to store a copy of the event message responsive to at least the routing manager determining that the event message received at the interface should be routed to the destination device.

10. The event bus of claim 9, wherein the queue comprises:

a primary queue; and

a secondary queue.

11. The event bus of claim 9, wherein the interface comprises:

an enterprise application interface.

12. A computer system for managing an event message, the computer system comprising:

at least a first processor device;

at least a first memory device accessible by the at least a first processor device;

a plurality of instructions stored on the at least a first memory device, the plurality of instructions configured to cause the at least a first processor device to;

process a received event message;

determine whether the received event message should be routed to a destination device or whether the received event message should be queued for retrieval by the destination device;

responsive to determining that the received event message should be routed to the destination device, route the event message to the destination device; and

responsive to determining that the received event message should be queued, queue the received network event message.

13. The computer system of claim 12, wherein the plurality of instructions are configured to cause the at least a first processor to:

identify a type for the received event message, wherein the received event message can be of at least a first type and a second type.

14. The computer system of claim 13, wherein the plurality of instructions are configured to cause the at least a first processor to:

responsive to the type of the received event message being the first type, determine to route the event message; and

responsive to the type of the received event message being the second type, determine to queue the event message in a queue.

15. The computer system of claim 12, wherein the plurality of instructions are further configured to cause the at least a first processor to:

store the event message in an event database.

16. The computer system of claim 15, wherein the plurality of instructions are further configured to cause the at least a first processor to:

store the event message in an event database responsive to determining that the event message should be routed.

17. The computer system of claim 12, wherein the plurality of instructions are configured to cause the at least a first processor to:

queue the event message in a short-term queue.