Apparatus and methods for widget update scheduling

• US 9,600,261 B2
• Filed: 03/19/2009
• Issued: 03/21/2017
• Est. Priority Date: 03/25/2008
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Mandyam, Giridhar D., Suryanarayana, Lalitha, Bernard, Christophe G., Hunter, Kevin E., Raffaelli, Noam
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Wang, Ben C
• Application Number:
  US12/407,574
• Publication Number:
  US 20090249321A1
• Time in Patent Office: 2,924 Days
• US Class Current: 1/1
• 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 including at least a hierarchical depth to which a user of a mobile device navigates within the mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device;

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

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

2. The method of claim 1, wherein the widget update consideration includes 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 the widget update consideration includes a widget executing device-related widget update consideration that is related to the mobile device configured to execute the mobile widget.

6. The method of claim 5, wherein the widget executing device-related 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 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 the mobile 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 of the mobile device.

13. The method of claim 1, wherein the widget update consideration includes a device capability of the mobile device, and wherein generating the content update schedule is based on the device capability.

14. The method of claim 13, wherein the device capability comprises 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 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 user update pattern historical data;

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

or (v) obtaining a device capability of the mobile device, 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 device capability.

17. The method of claim 1, wherein the widget update consideration further includes a device capability of the mobile device.

18. The method of claim 1, wherein the widget update consideration further includes a frequency at which the user accesses the mobile widget.

19. The method of claim 1, wherein the widget update consideration further includes a geographic location of the mobile device configured to execute the mobile widget.

20. The method of claim 1, wherein the widget update consideration further includes a geographic location of the mobile device configured to execute the mobile widget and a device capability of the mobile device.

21. The method of claim 1, wherein the widget update consideration further includes a device capability of the mobile device and a frequency at which the user accesses the mobile widget.

22. The method of claim 1, wherein the widget update consideration further includes a geographic location of the mobile device configured to execute the mobile widget and a frequency at which the user accesses the mobile widget.

23. The method of claim 1, wherein the widget update consideration further includes a geographic location of the mobile device configured to execute the mobile widget, a device capability of the mobile device, and a frequency at which the user accesses the mobile widget.

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

a first module configured to receive a widget update consideration including at least a hierarchical depth to which a user of a mobile device navigates within the mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device;

a second module configured to generate a content update schedule for the mobile widget based on the widget update consideration; and

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

25. A non-transitory computer-readable medium comprising:

at least one instruction for causing a computer to receive a widget update consideration including at least a hierarchical depth to which a user of a mobile device navigates within a mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device;

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

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

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

means for receiving a widget update consideration including at least a hierarchical depth to which a user of a mobile device navigates within the mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device;

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

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

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

a communications component that includes a receiver and a transmitter, the communications component operable to receive a widget update consideration including at least a hierarchical depth to which a user of a mobile device navigates within the mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device;

a processor component that is configured to execute an update scheduling manager operable to generate a content update schedule for the mobile widget based on the widget update consideration; and

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

28. The network device of claim 27, wherein the widget update consideration includes a wireless network operator-related widget update consideration.

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

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

31. The network device of claim 27, wherein the widget update consideration includes a widget executing device-related widget update consideration that is related to the mobile device configured to execute the mobile widget.

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

33. The network device of claim 27, 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.

34. The network device of claim 27, 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.

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

36. The network device of claim 35, wherein the user update pattern historical data corresponds to the mobile widget and to other mobile widgets operable on the mobile 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.

37. The network device of claim 27, 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.

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

39. The network device of claim 27, wherein the widget update consideration includes a device capability of the mobile device and wherein the content update schedule is based on the device capability.

40. The network device of claim 27, 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 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.

41. The network device of claim 27, 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 user update pattern historical data;

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

or (v) obtaining a device capability of the mobile device, 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 device capability.

42. A method of updating content of a mobile widget, comprising:

obtaining the mobile widget;

receiving a content update schedule for use in updating the content of the mobile widget, wherein the content update schedule is generated based on a widget update consideration including at least a hierarchical depth to which a user of a mobile device navigates within the mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device;

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

storing the content update.

43. The method of claim 42, wherein the widget update consideration includes a wireless network operator-related widget update consideration.

44. The method of claim 43, further comprising obtaining user update pattern historical data, wherein the updated 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.

45. The method of claim 42, wherein the widget update consideration includes a widget executing device-related widget update consideration that is related to the mobile device configured to execute the mobile widget.

46. The method of claim 42, further comprising:

obtaining at least one of a user content update preference, or user update pattern historical data, or an operational context corresponding to the mobile widget, or a device capability of the mobile device; 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 device capability, wherein the content update 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 device capability.

47. The method of claim 42, 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) user update pattern historical data;

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

or (v) a device capability of the mobile device.

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

a first module configured to obtain the mobile widget;

a second module configured to receive a content update schedule for use in updating the content of the mobile widget, wherein the content update schedule is generated based on a widget update consideration including at least a hierarchical depth to which a user of a mobile device navigates within the mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device;

a third module configured to receive a content update based on the content update schedule; and

a fourth module configured to store the content update.

49. A non-transitory 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 content of the mobile widget, wherein the content update schedule is generated based on a widget update consideration including at least a hierarchical depth to which a user of a mobile device navigates within the mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device;

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.

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

means for obtaining the mobile widget;

means for receiving a content update schedule for use in updating the content of the mobile widget, wherein the content update schedule is generated based on a widget update consideration including at least a hierarchical depth to which a user of the mobile device navigates within the mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device;

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

means for storing the content update.

51. A mobile 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 content of the mobile widget, wherein the content update schedule is generated based on a widget update consideration including at least a hierarchical depth to which a user of the mobile device navigates within the mobile widget, wherein the mobile widget is configured for execution on the mobile device and is independent of any web browsing application configured for execution on the mobile device and 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.

52. The mobile device of claim 51, wherein the widget management client is further operable to receive the content update schedule from at least one of a serving network or the mobile device.

53. The mobile device of claim 51, wherein the widget update consideration includes a wireless network operator-related widget update consideration.

54. The mobile device of claim 51, wherein the widget update consideration includes a widget executing device-related widget update consideration that is related to the mobile device configured to execute the mobile widget.

55. The mobile device of claim 51, wherein the widget management client is further operable to obtain user update pattern historical data, wherein the updated 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.

56. The mobile device of claim 51, further comprising:

obtaining at least one of a user content update preference, or user update pattern historical data, or an operational context corresponding to the mobile widget, or a device capability of the mobile device; 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 device capability,

wherein the content update 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 device capability.

57. The mobile device of claim 51, 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) user update pattern historical data;

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

or (v) a device capability of the mobile device.