Framework for Rule-Based Execution and Scheduling of Tasks in Mobile Devices

• US 20080046888A1
• Filed: 12/13/2006
• Published: 02/21/2008
• Est. Priority Date: 08/15/2006
• Status: Abandoned Application

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Appaji, Anuradha K.
• Application Number:
  US11/610,009
• Publication Number:
  US 20080046888A1
• Time in Patent Office: Days
• US Class Current: 718/102
• CPC Class Codes: G06F 2209/482 Application
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/5038 considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration scheduling strategies G06F9/4881 and subgroups
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A system is provided. The system comprises a component to receive a device management object. The device management object includes a rule node containing a rule that promotes control of execution of a task on a mobile device based on a parameter in a node in the device management object.

Claims

1. A system comprising:

a component to receive a device management object including a rule node containing a rule that promotes control of execution of a task on a mobile device based on a parameter in a node in the device management object.

2. The system of claim 1, wherein the component is one of a mobile device component and a server component.

3. The system of claim 1, wherein the rule causes at least one of the execution of a first task when a condition for the execution of the first task is not met and the prevention of the execution of a second task when a condition for the execution of the second task is met.

4. The system of claim 1, wherein the execution of the task is based on information in at least one of a condition node, a user interface node, a task node, a reporting node, a state node, an initial state node, an extension node, and the rule node in the at least one of the device management object and the other device management object.

5. The system of claim 4, wherein a condition in the condition node is evaluated before the rule is evaluated.

6. The system of claim 1, wherein the rule allows a first schedule in a first device management object to have an effect on a second schedule in a second device management object.

7. The system of claim 6, wherein the first schedule and the second schedule are in a single schedule context.

8. The system of claim 6, further comprising a type node operable to allow the rule to be designated as an uncorrelated rule, and when the rule has been designated as an uncorrelated rule, the type node operable to prevent the evaluation of a second rule in the second device management object.

9. The system of claim 1, wherein the nodes in the device management object comply with an Open Mobile Alliance standard.

10. A system, comprising:

a server; and

a mobile device including;

a first component operable to receive a device management object from the server, the device management object operable to contain a rule operable to control execution of a task on the mobile device based on at least one parameter in at least one node in at least one of the device management object and another device management object, and

a second component operable to send data generated by the execution of the task to the server.

11. The system of claim 10, wherein the rule causes at least one of the execution of a first task when a condition for the execution of the first task is not met and the prevention of the execution of a second task when a condition for the execution of the second task is met.

12. The system of claim 10, wherein the execution of the task is based on information in at least one of a condition node, a user interface node, a task node, a reporting node, a state node, an initial state node, an extension node, and the rule node in the at least one of the device management object and the other device management object.

13. The system of claim 12, wherein a condition in the condition node is evaluated before the rule is evaluated.

14. The system of claim 10, wherein the rule allows a first schedule in a first device management object to have an effect on a second schedule in a second device management object.

15. The system of claim 14, wherein the first schedule and the second schedule are in a single schedule context.

16. The system of claim 14, further comprising a type node operable to allow the rule to be designated as an uncorrelated rule, and when the rule has been designated as an uncorrelated rule, the type node operable to prevent the evaluation of a second rule in the second device management object.

17. A method for controlling an execution of a task on a mobile device, comprising:

specifying a rule in a rule node in a device management object, the rule related to execution of the task, the rule operable to cause at least one of the execution of a first task when a first condition for the execution of the first task is not met and the prevention of the execution of a second task when a second condition for the execution of the second task is met;

transmitting the device management object to the mobile device; and

when at least one of the first condition and the second condition are met, enforcing the rule.

18. The method of claim 17, further comprising basing the execution of the task on information in at least one of a condition node, a user interface node, a task node, a reporting node, a state node, an initial state node, an extension node, and the rule node in the at least one of the device management object and the other device management object.

19. The method of claim 17, further comprising a first schedule in a first device management object having an effect on a second schedule in a second device management object, and wherein the first schedule and the second schedule are contained in a single schedule context.

20. The method of claim 19, further comprising including a type node in the device management object, the type node operable to allow the rule to be designated as an uncorrelated rule, and when the rule has been designated as an uncorrelated rule, the type node operable to prevent the evaluation of a second rule in the second device management object.