Persistent maintenance of customization data on computing devices

• US 20070169084A1
• Filed: 12/12/2005
• Published: 07/19/2007
• Est. Priority Date: 12/12/2005
• Status: Abandoned Application

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Ranga, Rajan, Eastwood, Mark, Frank, Davis, De Asis, Ezekiel
• Application Number:
  US11/302,313
• Publication Number:
  US 20070169084A1
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 2212/2022 Flash memory
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

In a computing device, customization data is persistently maintained independent of the device'"'"'s operating system. Customization data may stored in a computing device'"'"'s persistent memory (or ROM or equivalent memory component), along with but independent of the operating system. When the computing device is first initialized, or when the computing device is initialized immediately after a hard-reset event, the customization data is not lost.

Claims

1. A component for a computing device, the component comprising:

a persistent memory configured to store, in a hard-reset state, data corresponding to an operating system, and customization data;

a first logic that delineates a first region of the persistent memory where the operating system is stored from a second region in the memory where the customization data is stored, so that the customization data is retrievable from the second region without retrieving data from the first region; and

a second logic that reserves a location of the second region where the customization data is stored, wherein the location is based on a size of the customization data.

2. The component of claim 1, wherein at least a portion of the second region excluding the customization data is capable of being formatted using the second logic when a computing device containing the memory component is initialized from the hard-reset state.

3. The component of claim 1, wherein the customization data is class-specific for the computing device.

4. The component of claim 1, wherein the customization data is user-specific for the computing device.

5. The component of claim 1, wherein the customization data includes binary data corresponding to at least one of an application or an image.

6. The component of claim 1, wherein the customization data includes application data for use with applications that are executing when the computing device that holds the memory component is in an operational state.

7. The component of claim 1, wherein the persistent memory is a Flash memory.

8. The component of claim 7, wherein the persistent memory is a NAND Flash memory.

9. The component of claim 1, wherein the customization data includes data sets corresponding to one or more of an application, application data, an image, or an audio file.

10. The component of claim 1, wherein the second logic includes a token that is stored with the operating system.

11. The component of claim 10, wherein the token identifies a value that indicates a size of the customization data.

12. The component of claim 1, wherein at least one of the first logic or second logic is stored in the persistent memory.

13. A computing device comprising:

a first memory that persistently holds data corresponding to (i) an operating system in a first region of the memory and (ii) a customization data in a second region of the first memory that does not overlap with the first region, wherein in a hard-reset state, the second region is substantially unformatted with exception of the customization data;

a first logic associated with the first memory to define the first region and the second region;

a value stored with the operating system that indicates at least a size of the customization data; and

a second logic associated with the first memory that is configured upon initialization from the hard-reset state, to format a section of the second memory that does not include a portion in which the customization data is provided, where the size of the section is determined at least in part on the value stored indicating the size of the customization data.

14. The computing device of claim 13, wherein the customization data is provided at a logical end of the persistent memory, so that the value stored identifies the location of the customization data in the memory.

15. The computing device of claim 13, further comprising:

a second memory configured to hold data when the computing device is in an operational state;

a third logic that transfers data corresponding to at least the operating system from the first memory to the second memory when the computing device is placed in the operational state from the hard-reset state.

16. The computing device of claim 15, wherein the first memory is configured to provide a store that backs up data in use with the second memory when the computing device is in the operational state.

17. The computing device of claim 15, wherein the second memory is configured to erase when the computing device is subjected to a reset event.

18. The computing device of claim 13, wherein the customization data includes data sets corresponding to one or more of (i) an application, (ii) application data, (iii) an image, (iv) or an audio file.

19. The computing device of claim 13, wherein the customization data is class-specific or user-specific.

20. The computing device of claim 13, wherein the customization data includes binary data corresponding to at least one of an application or an image.

21. The method of claim 20, wherein formatting a portion of the second region that does not include the customization data includes sizing the portion of the second region by determining all of the second region less a portion of the second region where the customization data is provided. the second portion.

22. The method of claim 20, further comprising:

storing a value corresponding to the size of the customization data with the operating system; and

wherein formatting a portion of the second region that does not include the customization data includes using the value stored with the operating system to identify the portion of the second region containing the customization data.

23. The method of claim 22, wherein formatting a portion of the second region that does not include the customization data includes providing the customization data at a logical end of the second region, and sizing the portion of the second region that does not include the customization data using the value stored with the operating system.

20-1. A method for customizing a computing device, the method comprising:

persistently storing the operating system in a first region of a memory of the computing device;

storing the customization data in a second region of the memory independently of the first region of the memory;

upon initialization of the computing device from a hard-reset state, formatting a portion of the second region that does not include the customization data for use with the computing device in the operational state;

wherein the portion of the second region that is formatted is based on a size of the customization data.

24. A method for customizing a computing device, the method comprising:

upon initialization of the computing device from a hard-reset state, determining a size of a portion of a persistent memory of the computing device that is to be formatted, wherein the size is based on an amount of customization data that is stored in a region of the persistent memory that contains the portion to be formatted, and wherein the region of the persistent memory is independent of another persistent memory region where the operating system is stored; and

formatting the portion of the second memory without affecting the customization data.

25. The method of claim 24, further comprising storing in the persistent memory region, where the operating system is stored, a value based on the size of the customization data, and wherein determining a size of a portion of a persistent memory includes determining the size of that portion using the value stored in the persistent memory region.