Managing a portal application

• US 9,383,800 B2
• Filed: 03/22/2011
• Issued: 07/05/2016
• Est. Priority Date: 03/22/2011
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: DeLuca, Lisa Seacat, Price, Dana Lea
• Primary Examiner(s): SONG, DAEHO D
• Application Number:
  US13/053,585
• Publication Number:
  US 20120246570A1
• Time in Patent Office: 1,932 Days
• Field of Search: 715/738, 715/742, 715/702, 715/744, 709/223, 709/227, 713/324, 713/300
• US Class Current: 1/1
• CPC Class Codes: G06F 1/3212 Monitoring battery levels, e.g. power saving mode being initiated when battery voltage goes below a certain level
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A mobile device includes a processor that executes a portal application to implement a plurality of portlet modules; and a user interface that allows a user to establish a trigger for reducing power consumption in the mobile device. The processor is configured to pause operations in a number of the portlet modules in the portal application in response to the trigger occurring.

Claims

1. A mobile device, comprising:

a processor that executes a portal application to implement a plurality of portlet modules within a portal page, the portal application embedding the plurality of portlet modules within the portal page; and

a user interface that allows a user to establish a pausing trigger for reducing power consumption in the mobile device, said processor being configured to pause operations in a number of said portlet modules in said portal application in response to said trigger occurring, the pausing of operations of a number of said portlet modules comprising graying out a graphical user interface that represents a paused portlet within the portal page;

wherein pausing operations in the plurality of said portlet modules comprises saving the state of at least one paused portlet to a temporary cache of the mobile device and queueing a number of service calls received from the at least one paused portlet in the temporary cache;

wherein the at least one paused portlet is reloaded and restored to the at least one paused portlet'"'"'s saved state in response to an unpausing trigger occurring by releasing the queued number of service calls originated from the at least one paused portlet; and

wherein the unpausing trigger comprises a determination that a measured power consumption of the plurality of portlet modules has decreased.

2. The mobile device of claim 1, said user interface displaying a word indicating that said number of portlet modules has been paused.

3. The mobile device of claim 1, wherein pausing operations in said number of said portlet modules further comprises:

receiving said service calls at an operating system of said mobile device or to a network to which said mobile device belongs;

preventing said attempted calls from being serviced until said operations of said number of said portlet modules are resumed.

4. The mobile device of claim 1, said trigger being determined by a user of said mobile device.

5. The mobile device of claim 1, said trigger comprising an instruction received by said mobile device to pause operations in said number of said portlets.

6. The mobile device of claim 1, in which the portal application aggregates the plurality of portlet modules for displaying to a user of the mobile device.

7. The mobile device of claim 1, wherein the second trigger is based on:

a measured level of activity associated with at least one of the plurality of portlet modules;

a lapse in time from which at least one of the plurality of portlet modules has maintained a threshold level of activity;

a measured power consumption associated with at least one of the plurality of portlet modules;

an amount of system resources requested for at least one of the plurality of portlet modules;

or

combinations thereof.

8. The mobile device of claim 1, wherein a first portlet of the plurality of portlets is paused based on the established trigger while any remaining portlets are not paused.

9. The mobile device of claim 1, wherein the pausing operations comprise disabling any service and method calls originating from the paused portlet.

10. The mobile device of claim 1, wherein the trigger for reducing power consumption in the mobile device is based on:

a measured level of activity associated with at least one of the plurality of portlet modules;

a lapse in time from which at least one of the plurality of portlet modules has maintained a threshold level of activity;

a measured power consumption associated with at least one of the plurality of portlet modules;

an amount of system resources requested for at least one of the plurality of portlet modules;

or combinations thereof.

11. A computer program product for managing a portal application, the computer program product comprising:

a tangible computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising;

computer readable program code configured to establish a pausing trigger for reducing power consumption in a device that executes a plurality of portal applications;

computer readable program code configured to determine that said pausing trigger has occurred;

computer readable program code configured to pause operations of at least one of the plurality of portlet modules within said portal application, wherein the pausing of operations of the at least one of the plurality of portlet modules comprising graying out a graphical user interface that represents a paused portlet within a portal page;

computer readable program code configured to save the state of the at least one paused portlet module to a temporary cache and queue a number of service calls from the at least one paused portlet module in the temporary cache;

computer readable program code configured to determine that an unpausing trigger has occurred; and

computer readable program code configured to reload the at least one paused portlet from the saved state of the at least one paused portlet;

wherein the portal application implements a plurality of portlet modules within a portal page by embedding the plurality of portlet modules in the portal page; and

wherein the unpausing trigger comprises a determination that a measured power consumption of a plurality of portlets has decreased.

12. The computer program product of claim 11 in which the portal application aggregates a plurality of portlet modules for displaying to a user of the device.

13. The computer program product of claim 11, wherein the unpausing trigger is further based on:

a measured level of activity associated with the portlet module;

a lapse in time from which the portlet module has maintained a threshold level of activity;

an amount of system resources requested for the portlet module;

or

combinations thereof.

14. The computer program product of claim 11, wherein the portlet module is paused while other portlet modules associated with the portal application are not paused.

15. The computer program product of claim 11, wherein pausing operation of a portlet module comprises disabling any service and method calls originating from the paused portlet.

16. A computing device, comprising:

a processor to execute a portal application, the portal application to implement a plurality of portlets within a portal page and to embed the plurality of portlets within the portal page;

a user interface to display a power options menu comprising options to implement pausing triggers for reducing power consumption in the computing device;

wherein the processor is to;

pause the at least one portlet based on the occurrence of at least one of the pausing triggers, the at least one pausing trigger comprising a measurement of system resources requested from the plurality of portlets, wherein the at least one pausing trigger comprising graying out a graphical user interface that represents the at least one paused portlet within the portal page;

save a state of the paused portlet and intercept and queue a number of service calls to the operating system of the computing device originating from the paused portlet while the paused portlet is paused;

save the queued number of service calls originating from the paused portlet in a temporary cache associated with the computing device;

determine that an unpausing trigger for the paused portlet has occurred;

release the queued number of service calls associated with the paused portlet from the temporary cache of the computing device; and

reload the paused portlet from the saved state and release the queued number of service calls originating from the paused portlet while the portlet was paused;

wherein the unpausing trigger is determined when a measured amount of system resources requested for the plurality of portlets has decreased.

17. The computing device of claim 16, wherein the pausing triggers are further comprising on:

a measured level of activity associated with at least one of the plurality of portlets;

a lapse in time from which at least one of the plurality of portlets has maintained a threshold level of activity;

a measured power consumption associated with at least one of the plurality of portlets;

or combinations thereof.

18. The computing device of claim 16, wherein the unpausing trigger is based on a measured level of activity associated with at least one of the plurality of portlets;

a lapse in time from which at least one of the plurality of portlets has maintained a threshold level of activity;

a measured power consumption associated with at least one of the plurality of portlets;

an amount of system resources requested for at least one of the plurality of portlets;

or combinations thereof.