Apparatus and methods for widget update scheduling

Patent metadata

Field	Value
Publication number	US-9600261-B2
Application number	US-40757409-A
Country	US
Kind code	B2
Filing date	Mar 19, 2009
Priority date	Mar 25, 2008
Publication date	Mar 21, 2017
Grant date	Mar 21, 2017

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.

First claim

What is claimed is:

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.

Assignees

• Mandyam Giridhar D
• Suryanarayana Lalitha
• Bernard Christophe G
• Hunter Kevin E
• Raffaelli Noam
• Qualcomm Inc

Inventors

• Mandyam Giridhar D
• Suryanarayana Lalitha
• Bernard Christophe G
• Hunter Kevin E
• Raffaelli Noam

Classifications

• G06F8/658 Primary

  Incremental updates; Differential updates · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F9/451

  Execution arrangements for user interfaces · CPC title

• G06F8/656

  while running · CPC title

• H04L67/62

  Establishing a time schedule for servicing the requests · CPC title