Event management system

• US 7,177,925 B2
• Filed: 09/27/2002
• Issued: 02/13/2007
• Est. Priority Date: 09/27/2002
• Status: Expired due to Fees

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Avago Technologies General IP PTE Limited (Broadcom, Inc.)
• Inventors: Carcido, Glenn Rosa, Fryman, Robert Scott, Lemay, Kevin William, Mantong, Frank L.
• Primary Examiner(s): Wiley, David
• Assistant Examiner(s): Jean-Gilles, Jude J
• Application Number:
  US10/259,534
• Publication Number:
  US 20040205773A1
• Time in Patent Office: 1,600 Days
• Field of Search: 709223-225, 709/212, 709/245, 709103-105, 711/147, 712/2, 712/32, 712/244, 712/228, 713/1, 713/100
• US Class Current: 709/223
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

One embodiment of an event management system, operating on a computer system having event producers and event consumers, includes an initial event handler program and an event queue having a first event. The initial event handler program retrieves the first event from the event queue for event processing. This event processing returns a first response to the initial event handler program, wherein the initial event handler program manages the first event on the event queue based on the first response.

Claims

1. An event management system, operating on a computer system having event producers and event consumers, the event management system comprising:

an initial event handler program;

an event queue having a first event, wherein the initial event handler program retrieves the first event from the event queue for event processing that returns a first response to the initial event handler program, wherein the initial event handler program manages the first event on the event queue based on the first response;

an extended event handler program, wherein the initial event handler program uses the first event to call the extended event handler program for further event processing; and

an extended event, wherein the extended event handler program retrieves the extended event for further event processing and the extended event includes a retry vector and a head vector, wherein the head vector relates to the beginning of a chain of event consumers and the retry vector relates to where processing left off in the chain of event consumers.

2. The event management system of claim 1, further comprising an event processor pointer in a pointer table, wherein the initial event handler program uses the first event to look up the event processor pointer from the pointer table.

3. The event management system of claim 2, wherein the first event includes an index into the pointer table, wherein the initial event handler program uses the index to look up the event processor pointer.

4. The event management system of claim 2, wherein the event processor pointer points to one of the event consumers, wherein the initial event handler program uses the event processor pointer to call the event consumer.

5. The event management system of claim 2, wherein the event processor pointer points to the extended event handler program, wherein the initial event handler program uses the event processor pointer to call the extended event handler program for further event processing.

6. The event management system of claim 5, further comprising an extended event lookup table that includes the extended event.

7. The event management system of claim 6, further comprising extended pointers in an extended pointer table, wherein the extended event handler program uses the extended event to look up one extended pointer from the extended pointer table.

8. The event management system of claim 7, wherein the extended event includes the retry vector and the head vector indexing extended pointers in the extended pointer table, wherein the extended event handler program uses the retry vector to look up a first extended pointer unless the retry vector is null, wherein the head vector is used to look up a second extended pointer where the retry vector is null.

9. The event management system of claim 5, wherein the extended event handler program receives a second response, which includes event processing result indicators.

10. The event management system of claim 9, further comprising an extended pointer table having extended pointers including an event consumer pointer and a next event consumer pointer, wherein the extended event handler program uses the next event consumer pointer for further event processing where the second response indicates success and pass to next.

11. The event management system of claim 9, wherein the second response indicates success and consumed, and the extended event handler program returns success in the first response to the initial event handler program.

12. The event management system of claim 9, wherein the second response includes retry, wherein the extended event handler program returns retry in the first response to the initial event handler program.

13. The event management system of claim 1, wherein the first response indicates retry and the initial event handler program leaves the first event in the event queue.

14. The event management system of claim 1, wherein the first response is success or moved and the initial event handler program removes the first event from the event queue.

15. The event management system of claim 1, wherein the first response is success or retry and the initial event handler program frees memory associated with the first event.

16. The event management system of claim 1, wherein a second event is received by the initial event handler program from the event producers, wherein the initial event handler program posts the second event to the end of the event queue.

17. The event management system of claim 16, wherein the initial event handler program posts the second event to the event queue in an event data structure having an ID section, a sub-category section and a data section.

18. A method for managing events in a computer system including at least one processor and memory and having event producers and event consumers, the method comprising:

executing an initial event handler program that is stored in the memory and configured to schedule events that are requests for some action;

retrieving an event from an event queue, wherein the event queue has at least one event from one of the event producers;

calling an event processor for processing the retrieved event and returning a first response;

receiving the first response from the event processor, wherein the first response indicates a result of processing the retrieved event; and

managing the retrieved event on the event queue based on the first response, wherein calling an event processor comprises;

calling an extended event handler program based on the first event; and

analyzing an extended event via the extended event handler program, which includes;

determining if a retry vector is null, wherein the retry vector indicates which event consumer in a chain of event consumers processing left off at;

retrieving the retry vector where the retry vector is not null; and

retrieving a head vector where the retry vector is null, wherein the head vector indicates the beginning of the chain of event consumers.

19. The method of claim 18, wherein calling an event processor comprises calling one of the event consumers.

20. The method of claim 18, further comprising:

looking up the extended event from an extended event lookup table;

analyzing the extended event for an indexing vector; and

looking up an extended pointer using the indexing vector, wherein calling the chain of event consumers includes using the extended pointer.

21. The method of claim 18, further comprising receiving a second response from one of the event consumers in the chain of event consumers, wherein the second response indicates the results of event processing.

22. The method of claim 21, further comprising:

looking up an extended pointer entry having an event consumer pointer and a next event consumer pointer; and

using the next event consumer pointer where the second response indicates success and pass to next.

23. The method of claim 18, wherein managing the retrieved event includes leaving the retrieved event on the queue or removing the retrieved event from the queue based on the first response.

24. The method of claim 18, wherein retrieving an event includes retrieving a consumer index that points to the event in the event queue and indexing the event in the event queue using the consumer index.

25. The method of claim 18, further comprising:

receiving an event from one of the event producers;

organizing the event into an event data structure; and

posting the event data structure to the event queue.

26. A computer system, comprising:

memory storing an initial event handler program configured to schedule events that are requests for some action, an event queue, an extended event handler program and an extended event, wherein the initial event handler program has instructions including event queue posting instructions, event queue retrieving instructions and event queue management instructions and the extended event includes a retry vector and a head vector, wherein the head vector relates to the beginning of a chain of event consumers and the retry vector relates to where processing left off in the chain of event consumers; and

a processor, which executes the initial event handler program, wherein the processor executes to event queue posting instructions to post a new event to the event queue and wherein the processor executes the event queue retrieving instructions to retrieve a posted event from the event queue for event processing that returns a first response to the processor, wherein the processor executes the initial event handler program to call the extended event handler program for further event processing based on the posted event retrieved from the event queue and the processor executes the extended event handler program to retrieve the extended event for further event processing, wherein the processor executes the event queue management instructions to manage the retrieved event on the event queue based on the first response.

27. The computer system of claim 26, wherein the memory includes a pointer to event processing in a pointer table and the processor executes the initial event handler program to analyze the posted event retrieved from the event queue and look up the pointer to event processing.

28. The computer system of claim 26, wherein the first response is retry and the processor executes the event queue management instructions to leave the retrieved event on the event queue.

29. The computer system of claim 26, wherein the first response is success or moved and the processor executes the event queue management instructions to remove the retrieved event from the event queue.

30. The computer system of claim 26, wherein the first response is success or retry and the processor executes the initial event handler program to free memory associated with the retrieved event.

31. The computer system of claim 26, wherein the processor executes the extended event handler program to call more than one event consumer.

32. An event management system, operating on a computer system including at least one processor and memory configured to store the event management system and having event producers and event consumers, the event management system comprising:

an initial event handler program configured to schedule events that are requests for some action;

an event queue having a first event, wherein the initial event handler program retrieves the first event from the event queue for event processing that returns a first response to the initial event handler program, wherein the initial event handler program manages the first event on the event queue based on the first response;

an extended event handler program, wherein the initial event handler program uses the first event to call the extended event handler program for further event processing; and

an extended event wherein the extended event handler program retrieves the extended event for further event processing and the extended event includes a retry vector and a head vector, wherein the head vector relates to the beginning of a chain of event consumers and the retry vector relates to where processing left off in the chain of event consumers.