TECHNIQUES FOR CONTROLLING DESKTOP STATE

• US 20100218187A1
• Filed: 02/26/2009
• Published: 08/26/2010
• Est. Priority Date: 02/26/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Venkateswaran, Srinivasa Ragavan, Pasupathilingam, Sankarasivasubramanian
• Granted Patent: US 8,819,703 B2
• Time in Patent Office: Days
• US Class Current: 718/100
• CPC Class Codes: G06F 2209/545 Gui
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Techniques for controlling desktop state are provided. Processing events are associated with desktop states and are associated with resource actions. When a desktop encounters the processing events and a known state is established, automated actions are forced on the resources to customize the known state.

Claims

1. A computer-implemented method that is adapted to executed by a processor to perform the method, comprising:

detecting a change in state for a processing environment of a client desktop that is moving from a first state to a second state;

looking up the second state in a configuration store for custom-defined user actions to take in response to the second state; and

notifying one or more desktop services to take the actions in response to the processing environment moving from the first state into the second state.

2. The method of claim 1, wherein detecting further includes acquiring the change in state from a desktop bus that executes on the processor as an inter process communication system daemon.

3. The method of claim 1, wherein detecting further includes acquiring the change in state when one or more of the following is detected within the processing environment:

the processor is detected as moving from alternating current power to direct current power, the processor is detected as moving from the direct current power to the alternating current power;

a wireless connection is detected as transitioning from a home network to a mobile network, a wired connection is detected as transitioning to the wireless connection, the wireless connection is detected as transitioning to the wired connection, a specific application is initiated on the processor, a running application is terminated on the processor.

4. The method of claim 1, wherein detecting further includes forcing the change in state to the second state when the first state remains unchanged for a configurable period of time and a profile that identifies the configurable period for the first state indicates that the second state is to be forced.

5. The method of claim 1, wherein looking further includes indexing into the configuration store using:

an identifier for the second state, or an identifier for the first state and the identifier for the second state combined.

6. The method of claim 1, wherein notifying further includes initiating a particular desktop service that was previously not executing within the processing environment in response to the actions defined for the second state.

7. The method of claim 1, wherein notifying further includes terminating a particular desktop service that was executing or that was scheduled to begin execution within the processing environment in response to the actions defined for the second state.

8. A computer-implemented method that is adapted to executed by a processor to perform the method, comprising, comprising:

identifying events being exchanged between services within a processing environment for a client desktop;

matching one or more of the identified events to a known transition state for the processing environment; and

instructing a number of the services to take predefined actions in response to the known transition state to customize a user'"'"'s experience while the user executes in the known transition state within the client desktop.

9. The method of claim 8 further comprising, instructing the number of services to resume their normal processing that existed or that was scheduled to exist on the client desktop before the predefined actions were taken when the known transition state terminates within the client desktop.

10. The method of claim 8, wherein identifying further includes matching each event detected within the processing environment to a profile that includes each of the identified events.

11. The method of claim 8, wherein matching further includes comparing the one or more identified events to configured events or configured combinations of events that map to the known transition state.

12. The method of claim 11, wherein comparing further includes identifying the configured events or the configured combinations of events as a user-defined state, which is the known transition state and which was previously configured by a user of the client desktop.

13. The method of claim 8, wherein instructing further includes recognizing the known transition state as a secure state and providing instructions to logging services on the desktop to temporarily shut down and not log any activities of a user during the secure state.

14. The method of claim 8, wherein instructing further includes recognizing the known transition state as a particular state that attempts to maximize processor throughput of the processor for a designated service by turning off or throttling down other executing services on the processor during the known transition state.

15. A machine-implemented system adapted to be executed on one or more processors, comprising:

a desktop interface implemented in a computer readable medium and to execute on a processor of a client desktop; and

a desktop state controller implemented in a computer readable medium and to execute on the processor of the client desktop;

wherein a principal interacts with the desktop interface to define a known desktop state based on one or more known events that occur in a processing environment of the client desktop and the principal associates one or more actions to automatically and dynamically process when the client desktop enters the known desktop state, and wherein the desktop state controller dynamically, automatically, and in real time monitors processing events occurring within the processing environment and when a match occurs to the one or more known events, the desktop state controller instructs one or more services of the client desktop to take the one or more actions on behalf of the principal.

16. The system of claim 15, wherein the principal is a user, an administrator, or an automated agent that executes on the processor of the client desktop.

17. The system of claim 15, wherein the desktop interface enforces policy restrictions against the principal to prevent some actions from being defined with the known desktop state when the principal lacks proper security to define.

18. The system of claim 15, wherein the principal custom defines the known desktop state and custom defines a description associated with the known desktop state.

19. The system of claim 15, wherein at least one of the one or more actions alter a schedule associated with an automated service that is scheduled to begin execution on the processor of the desktop client during the known desktop state.

20. The system of claim 15, wherein at least one of the one or more known events include other limitations that are evaluated when that particular event is encountered and the evaluation of the other limitations assist in identifying the known desktop state.

21. A machine-implemented system adapted to be executed by one or more processors, comprising:

a client desktop having a processor and memory and a plurality of resources adapted to execute on the processor of the client desktop; and

a desktop state controller implemented in a computer-readable storage medium of the client desktop and to execute on the processor of the client desktop;

wherein a user custom defines a particular desktop state by predefining one or more events associated with the resources and the user associates actions to instruct select ones of the resources to take when the particular desktop state is detected in a processing environment of the client desktop, and wherein the desktop state controller matches the events occurring in the processing environment to identify the particular desktop state and the desktop state controller instructs the select resources to take the actions in response thereto.

22. The system of claim 21, wherein at least one action is associated with a particular resource that is not yet executing on the processor but is scheduled to execute or has the potential to execute during the particular desktop state.

23. The system of claim 21, wherein at least one action is associated with terminating a particular resource as soon as it is detected to have started for execution on the processor during the particular desktop state.

24. The system of claim 21, wherein at least one action is associated with disabling a feature of a particular resource during the particular desktop state.