APPARATUS AND METHODS FOR WIDGET UPDATE SCHEDULING

• US 20090249321A1
• Filed: 03/19/2009
• Published: 10/01/2009
• Est. Priority Date: 03/25/2008
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Suryanarayana, Lalitha, Hunter, Kevin E., Mandyam, Giridhar D., Raffaelli, Noam, Bernard, Christophe G.
• Granted Patent: US 9,600,261 B2
• Time in Patent Office: Days
• US Class Current: 717/171
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests

Abstract

Methods and apparatus for scheduling a content update of a mobile widget are provided. The method may include receiving a widget update consideration. The method may also include generating a content update schedule for a mobile widget based on the update consideration. Further, the method may include storing the generated content update schedule for use in updating a content of the mobile widget.

Claims

1. A method of scheduling a content update of a mobile widget, comprising:

receiving a widget update consideration;

generating a content update schedule for a mobile widget based on the update consideration; and

storing the generated content update schedule for use in updating a content of the mobile widget.

2. The method of claim 1, wherein receiving widget update consideration further comprises receiving a wireless network operator-related widget update consideration.

3. The method of claim 2, wherein the widget update consideration comprises temporal network usage data.

4. The method of claim 2, wherein the widget update consideration comprises historical or projected temporal network capacity data.

5. The method of claim 1, wherein receiving widget update consideration further comprises receiving a widget executing device-related widget update consideration.

6. The method of claim 5, wherein the widget update consideration comprises temporal network usage data.

7. The method of claim 1, further comprising identifying a content type corresponding to the content of the mobile widget, and wherein generating the content update schedule is further based on the content type.

8. The method of claim 1, further comprising receiving a user content update preference, and wherein generating the content update schedule is further based on the user content update preference.

9. The method of claim 1, further comprising receiving a user update pattern historical data, and wherein generating the content update schedule is further based on the user update pattern historical data.

10. The method of claim 9, wherein the user update pattern historical data corresponds to the mobile widget and to other mobile widgets operable on a respective wireless communication device, and wherein generating the content update schedule for the mobile widget is based on the user update pattern historical data corresponding to at least one of the other mobile widgets.

11. The method of claim 1, further comprising identifying an operational context corresponding to the mobile widget, and wherein generating the content update schedule is further based on the operational context.

12. The method of claim 11, wherein the operational context comprises at least one of a time or a geographic location.

13. The method of claim 1, further comprising obtaining a wireless device capability corresponding to a wireless communication device on which the mobile widget is operable, and wherein generating the content update schedule is further based on the wireless device capability.

14. The method of claim 13, wherein obtaining a wireless device capability further comprises obtaining the wireless device capability comprising one of battery life or microprocessor capability or wireless connection capability.

15. The method of claim 1, further comprising identifying a content type corresponding to the content of the mobile widget and receiving a user update pattern historical data, and wherein generating the content update schedule is further based on the content type and the user update pattern historical data.

16. The method of claim 1, further comprising at least two of:

(i) identifying a content type corresponding to the content of the mobile widget;

or (ii) receiving a user content update preference;

or (iii) receiving a user update pattern historical data;

or (iv) identifying an operational context corresponding to the mobile widget;

or (v) obtaining a wireless device capability corresponding to a wireless communication device on which the mobile widget is operable, wherein generating the content update schedule is further based on the at least two of;

(i) the content type;

or (ii) the user content update preference;

or (iii) the user update pattern historical data;

or (iv) the operational context;

or (v) the wireless device capability.

17. At least one processor configured to schedule a content update of a mobile widget, comprising:

a first module for receiving a widget update consideration;

a second module for generating a content update schedule for a mobile widget based on the update consideration; and

a third module for storing the generated content update schedule for use in updating a content of the mobile widget.

18. A computer program product for scheduling a content update of a mobile widget, comprising:

a computer-readable medium comprising;

at least one instruction for causing a computer to receive a widget update consideration;

at least one instruction for causing the computer to generate a content update schedule for a mobile widget based on the update consideration; and

at least one instruction for causing the computer to generate content update schedule for use in updating a content of the mobile widget.

19. A network device for scheduling a content update of a mobile widget, comprising:

means for receiving a widget update consideration;

means for generating a content update schedule for a mobile widget based on the update consideration; and

means for storing the generated content update schedule for use in updating a content of the mobile widget.

20. A network device for scheduling a content update of a mobile widget, comprising:

a communication module operable to receive a widget update consideration;

an update scheduling manager operable to generate a content update schedule for a mobile widget based on the update consideration; and

a database operable to store the generated content update schedule for use in updating a content of the mobile widget.

21. The network device of claim 20, wherein the communications module is further operable to receive a wireless network operator-based widget update consideration

22. The network device of claim 21, wherein the wireless network operator-related widget update consideration comprises temporal network usage data.

23. The network device of claim 21, wherein the wireless network operator-related widget update consideration comprises historical or projected temporal network capacity data.

24. The network device of claim 20, wherein the communications module is further operable to receive a widget executing device-related widget update consideration.

25. The network device of claim 24, wherein the widget executing device-related widget update consideration comprises temporal network usage data.

26. The network device of claim 20, wherein the update scheduling manager is further operable to identify a content type corresponding to the content of the mobile widget, and wherein the content update schedule is further based on the content type.

27. The network device of claim 20, wherein the update scheduling manager is further operable to receive a user content update preference, and wherein the content update schedule is further based on the user content update preference.

28. The network device of claim 20, wherein the update scheduling manager is further operable to receive a user update pattern historical data, and wherein the content update schedule is further based on the user update pattern historical data.

29. The network device of claim 28, wherein the user update pattern historical data corresponds to the mobile widget and to other mobile widgets operable on a respective wireless communication device, and wherein the content update schedule for the mobile widget is based on the user update pattern historical data corresponding to at least one of the other mobile widgets.

30. The network device of claim 20, wherein the update scheduling manager is further operable to identify an operational context corresponding to the mobile widget, and wherein the content update schedule is further based on the operational context.

31. The network device of claim 30, wherein the operational context comprises at least one of a time or a geographic location.

32. The network device of claim 20, wherein the update scheduling manager is further operable to obtain a wireless device capability corresponding to a wireless communication device on which the mobile widget is operable, and wherein the content update schedule is further based on the wireless device capability.

33. The network device of claim 20, wherein the update scheduling manager is further operable to identify a content type corresponding to the content of the mobile widget and is further operable to receive a user update pattern historical data, and wherein the content update schedule is further based on the content type and the user update pattern historical data.

34. The network device of claim 20, wherein the update scheduling manager is further operable to perform at least two of:

(i) identifying a content type corresponding to the content of the mobile widget;

or (ii) receiving a user content update preference;

or (iii) receiving a user update pattern historical data;

or (iv) identifying an operational context corresponding to the mobile widget;

or (v) obtaining a wireless device capability corresponding to a wireless communication device on which the mobile widget is operable, wherein the content update schedule is further based on the at least two of;

(i) the content type;

or (ii) the user content update preference;

or (iii) the user update pattern historical data;

or (iv) the operational context;

or (v) the wireless device capability.

35. A method of updating content of a mobile widget on a wireless device, comprising:

obtaining a mobile widget;

receiving a content update schedule for use in updating a content of the mobile widget, wherein the content update schedule is generated based on an update consideration;

receiving a content update based on the content update schedule; and

storing the content update.

36. The method of claim 35, wherein receiving a content update schedule further comprises receiving the content update schedule that is generated based on a wireless network operator-related update consideration.

37. The method of claim 36, further comprising obtaining a user update pattern historical data, wherein the content of the mobile widget corresponds to a content type, and wherein the content update schedule is further based on the content type and the user update pattern historical data.

38. The method of claim 35, wherein receiving a content update schedule further comprises receiving the content update schedule that is generated based on the wireless device-related update consideration.

39. The method of claim 35, further comprising:

obtaining at least one of a user content update preference, or a user update pattern historical data, or an operational context corresponding to the mobile widget, or a wireless device capability corresponding to a wireless communication device on which the mobile widget is operable; and

transmitting to another device the respective at least one of the user content update preference, or the user update pattern historical data, or the operational context corresponding to the mobile widget, or the wireless device capability,

wherein the content schedule is further based on the respective at least one of the user content update preference, or the user update pattern historical data, or the operational context corresponding to the mobile widget, or the wireless device capability.

40. The method of claim 35, wherein the content update schedule is further based on at least two of:

(i) a content type corresponding to the content of the mobile widget;

or (ii) a user content update preference;

or (iii) a user update pattern historical data;

or (iv) an operational context corresponding to the mobile widget;

or (v) a wireless device capability corresponding to a wireless communication device on which the mobile widget is operable.

41. At least one processor configured to update content of a mobile widget, comprising:

a first module for obtaining a mobile widget;

a second module for receiving a content update schedule for use in updating a content of the mobile widget, wherein the content update schedule is generated based on an update consideration;

a third module for receiving a content update based on the content update schedule; and

a fourth module for storing the content update.

42. A computer program product for updating content of a mobile widget, comprising:

a computer-readable medium comprising;

at least one instruction for causing a computer to obtain a mobile widget;

at least one instruction for causing the computer to receive a content update schedule for use in updating a content of the mobile widget, wherein the content update schedule is generated based on an update consideration;

at least one instruction for causing the computer to receive a content update based on the content update schedule; and

at least one instruction for causing the computer to store the content update.

43. A wireless device for updating content of a mobile widget, comprising:

means for obtaining a mobile widget;

means for receiving a content update schedule for use in updating a content of the mobile widget, wherein the content update schedule is generated based on an update consideration;

means for receiving a content update based on the content update schedule; and

means for storing the content update.

44. A wireless communication device, comprising:

a memory comprising a widget management client;

a processor in communication with the memory and operable to execute the widget management client, wherein the widget management client is operable to obtain a mobile widget, wherein the widget management client is further operable to receive a content update schedule for use in updating a content of the mobile widget, wherein the content update schedule is generated based on an update consideration, wherein the widget management client is further operable to receive a content update based on the content update schedule; and

a database operable to store the content update.

45. The wireless communication device of claim 44, wherein the widget management client is further operable to receive a content update schedule from at least one of a serving network or the wireless communication device.

46. The wireless communication device of claim 44, wherein the content update schedule is further generated based on a wireless network operator-related update consideration.

47. The wireless communication device of claim 44, wherein the content update schedule is further generated based on a wireless device-related update consideration.

48. The wireless communication device of claim 44, wherein the widget management client is further operable to obtain a user update pattern historical data, wherein the content of the mobile widget corresponds to a content type, and wherein the content update schedule is further based on the content type and the user update pattern historical data.

49. The wireless communication device of claim 44, further comprising:

obtaining at least one of a user content update preference, or a user update pattern historical data, or an operational context corresponding to the mobile widget, or a wireless device capability corresponding to a wireless communication device on which the mobile widget is operable; and

transmitting to another device the respective at least one of the user content update preference, or the user update pattern historical data, or the operational context corresponding to the mobile widget, or the wireless device capability,

wherein the content schedule is further based on the respective at least one of the user content update preference, or the user update pattern historical data, or the operational context corresponding to the mobile widget, or the wireless device capability.

50. The wireless communication device of claim 44, wherein the content update schedule is further based on at least two of:

(i) a content type corresponding to the content of the mobile widget;

or (ii) a user content update preference;

or (iii) a user update pattern historical data;

or (iv) an operational context corresponding to the mobile widget;

or (v) a wireless device capability corresponding to a wireless communication device on which the mobile widget is operable.