Workflow processing scheduler

• US 20040031035A1
• Filed: 04/17/2003
• Published: 02/12/2004
• Est. Priority Date: 04/19/2002
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Norman, Andrew Patrick, Shiu, Simon, Mont, Marco Casassa, Baldwin, Adrian
• Application Number:
  US10/417,776
• Publication Number:
  US 20040031035A1
• Time in Patent Office: Days
• US Class Current: 718/102
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

An operating system for processing multiple tasks, the operating system comprising means for generating the multiple tasks including data indicating a time at which or by which (and/or a frequency at which and/or one or more events in response to which) the task should be processed, means for associating time stamp data with the tasks, said time stamp data being indicative of the date and/or time at which the respective tasks were generated, and means for receiving said tasks for processing at a particular time, determining from the associated time stamp for each task the date and/or time at which said task was generated, determining whether or not the processing of said task at said particular time is consistent with one or more predetermined operating system policies, and causing said task to be processed at said particular time only if such processing is determined to be consistent with said operating system policies. The addition of timestamp data to the tasks allows the system to check that the time at which the task was created and then given to a scheduling system for processing corresponds with that expected of such a task (according to company policy and the nature of the task to be processed).

Claims

1. An operating system or application for processing multiple tasks, the operating system, or application, being arranged to generate said multiple tasks including data indicating when said task should be processed, associate time stamp data with said tasks, said time stamp data being indicative of the date and/or time at which the respective tasks were generated, and to receive said tasks for processing at a particular time, determine from the associated time stamp for each task the date and/or time at which said task was generated, determine whether or not the processing of said task at said particular time is consistent with one or more predetermined operating system, or application policies, and cause said task to be processed at said particular time only if such processing is determined to be consistent with said operating system, or application policies.

2. An operating system or application according to claim 1, comprising one or more task generation modules, one or more schedulers and one or more consuming modules, said one or more schedulers being arranged to determine from the associated time stamp data for each task the date and/or time at which said task was generated, determine whether or not the processing of said task at said particular time is consistent with predetermined operating system, or application policies, and cause said task to be processed at said particular time only if such processing is determined to be consistent with said operating system, or application policies.

3. An operating system or application according to claim 1, comprising one or more task generation modules, one or more schedulers and one or more consuming modules, said one or more consuming modules being arranged to determine from the associated time stamp data for each task the date and/or time at which said task was generated, determine whether or not the processing of said task at said particular time is consistent with predetermined operating system, or application policies, and cause said task to be processed at said particular time only if such processing is determined to be consistent with said operating system, or application policies.

4. An operating system or application according to claim 3, wherein the times at which each of a plurality of tasks are processed are offset by some predetermined amount.

5. An operating system or application according to claim 2, wherein said time stamp data is generated and associated with a task via said one or more task generation modules.

6. An operating system or application according to claim 3, wherein said time stamp data is generated and associated with a task via said one or more schedulers.

7. An operating system or application according to claim 1, wherein said time stamp data is provided and/or authenticated by a third party.

8. An operating system application according to claim 7, wherein said time stamp data is digitally signed by said third party.

9. An operating system or application according claim 1, wherein said tasks have associated therewith authentication data indicative of their origin within said operating system.

10. An operating system or application according to claim 9, wherein said authentication data includes a digital signature.

11. A method of processing multiple tasks within an operating system or application the method comprising the steps of generating said multiple tasks and including therein data indicating when said task should be processed, generating time stamp data to be associated with at least one of said tasks indicative of the date and/or time at which the at least one respective task was generated, receiving said tasks for processing at a particular time, determining from the associated time stamp data for each task the date and/or time at which said task was generated, determining whether or not the processing of said task at said particular time is consistent with predetermined operating system, or application policies, and causing said task to be processed at said particular time only if such processing is determined to be consistent with said operating system, or application policies.

12. A computer system programmed for scheduling task execution, wherein the computer system is programmed to generate tasks and to associate with generated tasks criteria for processing said tasks and data representing the time of generation of said tasks, and wherein the computer system is programmed to carry out said tasks in accordance with the associated criteria only after evaluation of the time of generation data.

13. A method of generating and processing tasks in a computer system, comprising:

generating a task, and associating with the task one or more criteria for processing the task, and a time of generation datum representing the time of generation of the task;

identifying when the one or more criteria for processing the task have been met;

evaluating the time of generation datum to determine whether it is appropriate to process the task; and

processing the task if the evaluation step is successful.

14. A method as claimed in claim 13, comprising scheduling a task for processing according to the one or more criteria, and evaluating the time of generation datum when the task is scheduled for processing.

17. A method as claimed in claim 16, wherein a task scheduled for processing is given a task identity.

18. A method as claimed in claim 17, wherein a task is scheduled for a plurality of different times under the same task identity, but when the task is processed it becomes unavailable for processing under that task identity.

19. A method as claimed in claim 16 or 17, wherein a task scheduled for repeated processing is given discrete task identities for each processing of the task.