DYNAMIC RESOURCE MANAGEMENT

• US 20080115141A1
• Filed: 11/15/2006
• Published: 05/15/2008
• Est. Priority Date: 11/15/2006
• Status: Abandoned Application

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Prasad, Srikiran, Welingkar, Bharat
• Application Number:
  US11/560,045
• Publication Number:
  US 20080115141A1
• Time in Patent Office: Days
• US Class Current: 718/104
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals

Abstract

Instead of initially deploying a full set of static data resources to a client device, when notification of an error experienced by the client device is made, a determination is made as to whether that error is frequently concurring. In such a case, the resource associated that error is scheduled to be part of a next resource file build, whereupon the generated resource file is wirelessly communicated to the client device for installation.

Claims

1. A system, comprising:

a client side component capable of experiencing an error during operation;

a server side component operatively connected to a store of static data resources, wherein, upon indication of the error to the server side component, the server side component is arranged to;

build a resource file including a resource selected from the store and associated with the error, and

wirelessly transmit the resource file to the client side component.

2. The system of claim 1, wherein the error experienced during operation is one for which the client side component cannot locally locate an associated resource.

3. The system of claim 1, wherein the at least one of static data resources is one of a text string, a bitmap, an image, a code, a character string, metadata, and a user interface feature.

4. The system of claim 1, wherein the store is configurable.

5. The system of claim 1, wherein the resource file is dependent on a type of the client side component, a group associated with the client side component, and a carrier of a service provided to the client side component.

6. The system of claim 1, wherein the resource file is wirelessly broadcast to the client side component in a form an executable library file.

7. The system of claim 1, wherein the client side component is any one of a mobile phone, a personal digital assistant, and a portable e-mail device.

8. The system of claim 1, wherein the store is manageable without interference in operations of the client side component.

9. The system of claim 1, wherein the resource file is wirelessly broadcast to the client side component in a form an HTTP message.

10. A method of performing resource management, comprising:

centrally storing at a server static data resources;

receiving an indication of an error experienced by a client device;

identifying a static data resource in response to the error indication;

causing a next build of a resource file to include the identified static data resource; and

wirelessly transmitting the resource file to the client device.

11. The method of claim 10, wherein the at least one of static data resources is one of a text string, a bitmap, an image, a code, a character string, metadata, and a user interface feature.

12. The method of claim 10, wherein the client device is any one of a mobile phone, a personal digital assistant, and a portable e-mail device.

13. The method of claim 10, wherein the resource file is wirelessly broadcast to the client device in a form an executable library file.

14. The method of claim 10, wherein the resource file is dependent on a type of the client device, a group associated with the client device, and a carrier of a service provided to the client device.

15. The method of claim 10, wherein building the resource file at the server occurs without interruption to operations of the client device.

16. A mobile computing device, comprising:

a first module arranged to detect an error experienced by the mobile computing device;

a second module arranged to determine that a static data resource does not locally exist for the error;

a third module arranged to facilitate indication of the error to a server component;

a fourth module arranged to wirelessly receive a resource file build by the server component and including a static data resource for the error; and

a fifth module arranged to install the resource file.

17. The mobile computing device of claim 16, wherein the static data resource is one of a text string, a bitmap, an image, a code, a character string, metadata, and a user interface feature.

18. The mobile computing device of claim 16, wherein the mobile computing device is any one of a mobile phone, a personal digital assistant, and a portable e-mail device.

19. The mobile computing device of claim 16, wherein the resource file is wirelessly received by the client device in a form an executable library file.

20. The mobile computing device of claim 16, wherein the resource file is dependent on a type of the client device, a group associated with the client device, and a carrier of a service provided to the client device.

21. The mobile computing device of claim 16, wherein the resource file is dynamically sent by the server.