Method and apparatus and program for scheduling and executine events in real time over a network

• US 20040177108A1
• Filed: 02/03/2003
• Published: 09/09/2004
• Est. Priority Date: 02/03/2003
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Connelly, Jon Christopher, Hansen, Dian, Shurtleff, Robert Glenn III
• Granted Patent: US 7,376,733 B2
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

The present invention relates to a method, system, computer program product, or apparatus that schedules and executes events within a network in real-time. An event processor contacts one or more event schedulers, and it receives back from them event schedule updates. It then calculates the time when each event is to occur from information contained in the received scheduling information for each event. Next, it places event scheduling information contained in the received scheduling information for each event, plus the calculated occurrence time of the corresponding event, into an event queue. Finally, at the time when each event is to occur, as indicated by examination of the calculated times in the event queue, the event processor sends out event firing messages to event processors that are named in the received scheduling information for each event.

Claims

1. A method for scheduling and executing a real-time event in a networked environment, the method comprising:

(a) contacting one or more event schedulers;

(b) receiving an event schedule update from the event schedulers;

(c) calculating the time when each event is to occur from information contained in the received scheduling information for each event;

(d) placing event scheduling information contained in the received scheduling information for each event plus the calculated time for that same event into an event queue; and

(e) at the time when each event is to occur, as indicated by examination of the calculated times in the event queue, contacting one or more event processors designated by the received scheduling information corresponding to that event and sending an event firing message to the designated event processors.

2. The method according to claim 1, wherein the step (a) is performed periodically and is a request for an update.

3. The method according to claim 1, wherein the received event scheduling information is formatted as an XML document or its equivalent to includes an event identifier, a resolution value defining when an event is to occur, a designator of at least one event processor, and additional data to be supplied to the at least one designated event processor when an event is to occur.

4. The method according to claim 3, wherein each such XML or equivalently formatted event document containing event scheduling information comprises any number of event schedules, including zero schedules, and where the inclusion of zero schedules indicates the cancellation of any currently pending event schedules from the event queue.

5. The method according to claim 1, including the additional step of conveying attempts to contact the schedulers through a load balancer and into a farm of machines such that the event requests may originate from machines carrying out intranet or Internet web activities or both.

6. The method according to claim 5, wherein the contacting in step (a) is contacting a schedule document that is updated by one or more event schedulers, and wherein this document is received in step (b).

7. The method according to claim 1, wherein the message transmitted to the event processor is transmitted through a load balancer and into a farm of machines such that the event processors may be installed on machines carrying out intranet or Internet web activities or both.

8. The method according to claim 7, wherein the message is an addressed HTTP or SOAP or equivalently-addressed message including event data, and wherein the address and the event data are both obtained from the event scheduling information for the scheduled event to which the message relates.

9. A system for scheduling and executing a real time event over a network, the system comprising:

at least one farm of machines sharing a load balancer;

a cluster of servers arranged to replace each other in case of malfunction, the cluster networked to the farm;

at least one event processor within the farm of machines able to cause an event to occur in response to a received message;

at least one event scheduler within the farm of machines able to provide event schedules indicating when one or more events are to occur and the addresses of the event processors that can cause the events to occur;

an event manager within the cluster that comprises an event queue, an event loader that accepts event schedules from the schedulers and places them into an event queue, and a timekeeper that examines the event queue and, at the time of a scheduled event, transmits a message requesting firing of the event to an event processor whose address is obtained from the corresponding event schedule.

10. The system according to claim 9, wherein within the cluster, one server takes over the responsibilities of another server as needed to insure the availability of the event manager at all times.

11. The system according to claim 10, wherein each of the plurality of servers in the cluster comprises a computer having management software that monitors each of the plurality of other servers within the cluster in real-time.

12. The system according to claim 9, wherein the event loader requests event schedules from the event schedulers periodically.

13. The system according to claim 9, wherein the event loader accepts event schedules from the event schedulers which are presented to the event loader by the event schedulers.

14. The system according to claim 9, wherein the event schedules are documents or their equivalent posted and updated by the event schedulers so that they may be addressed directly and retrieved directly by the event manager at any time.

15. The system according to claim 10, wherein at least one of the plurality of servers is continuously operating the event manager at any given time, and wherein in case of difficulties another of the plurality of servers takes over operating the event manager such that the servers back each other up.

16. The system according to claim 9, wherein the event manager is multi-threaded, with the threads coordinating their activities about shared access to the event queue, the event loader comprising a first thread, and the timekeeper comprising a second thread.

17. The system according to claim 16, wherein the event manager further comprises a second request queue containing requests for the firing of events placed there by the timekeeper, and wherein the timekeeper further comprises a communicator comprising a third thread that coordinates its activities with the timekeeper second thread about shared access to the request queue and that checks the request queue and retrieves requests for the firing of events from the request queue and then generates the messages that are sent to the event processors when such requests appear in the request queue.

18. The system according to claim 9, wherein the event manager further comprises a record queue associated with the timekeeper having an associated communications program, the timekeeper placing requests for the transmission of event messages into the request queue, and the communications program retrieving those requests, sending out the messages to the event processors, and confirming that the messages are actually received by the event processors or taking corrective actions if they are not received, whereby delays in message transmission and receipt do not slow down the scheduling and the processing of other events.

19. The system according to claim 9, wherein the event manager additionally comprises an event data structure which comprises information taken from a corresponding event schedule plus a computed time of the next occurrence of a corresponding event, and wherein the event queue is structured to accept and to manage such event data structures for multiple scheduled events.

20. The system according to claim 19, wherein the event queue is structured as an object which maintains event data structures organized such that the next event to occur is positioned within the queue to a position immediately accessible to the timekeeper.

21. The system according to claim 9, wherein the event manager contacts the event schedulers to accept information from them via HTTP links or their equivalent.

22. A computer program product having program code that is executable by a computer for scheduling and executing real-time events in a networked environment, the program code configured to cause the computer to perform the method comprising:

(a) contacting one or more event schedulers;

(b) receiving an event schedule update from the event schedulers;

(c) calculating the time when each event is to occur from information contained in the received scheduling information for each event;

(d) placing event scheduling information contained in the received scheduling information for each event plus the calculated time for that same event into an event queue; and

(e) at the time when each event is to occur, as indicated by examination of the calculated times in the event queue, contacting one or more event processors designated by the received scheduling information corresponding to that event and sending an event firing message to the designated event processors.

23. The program product according to claim 22, wherein the step (a) is performed periodically and is a request for an update.

24. The program product according to claim 22, wherein the received event scheduling information is formatted as an XML document or its equivalent to includes an event identifier, a resolution value defining when an event is to occur, a designator of at least one event processor, and additional data to be supplied to the at least one designated event processor when an event is to occur.

25. The program product according to claim 24, wherein each such XML or equivalently formatted event document containing event scheduling information comprises any number of event schedules, including zero schedules, and where the inclusion of zero schedules indicates the cancellation of any currently pending event schedules from the event queue.

26. The program product according to claim 22, including the additional step of conveying attempts to contact the schedulers through a load balancer and into a farm of machines such that the event requests may originate from machines carrying out intranet or Internet web activities or both.

27. The program product according to claim 26, wherein the contacting in step (a) is contacting a schedule document that is updated by one or more event schedulers, and wherein this document is received in step (b).

28. The program product according to claim 22, wherein the message transmitted to the event processor is transmitted through a load balancer and into a farm of machines such that the event processors may be installed on machines carrying out intranet or Internet web activities or both.

29. The program product according to claim 28, wherein the message is an addressed HTTP or SOAP or equivalently-addressed message including event data, and wherein the address and the event data are both obtained from the event scheduling information for the scheduled event to which the message relates.

30. An apparatus for scheduling and executing real-time events over a network comprising:

event management means for receiving event schedule updates from a networked environment, said event management means comprising;

calculation means for calculating the time when each event is to occur from information contained in the most recently received event schedule update for each event;

(d) event queue synchronizing means for establishing an event queue, for placing information taken from incoming event schedule updates and the calculated times of event occurrence into the event queue, and for synchronizing the contents of the event queue with later-arriving event schedule updates when they are received; and

(e) communicating means for sending out an event firing message to a network address designated by the most recently received event scheduling update information corresponding to an event at the time when that event is scheduled to occur, as indicated by examination of the calculated time of occurrence for that event contained within the event queue.