Apparatus and method for allocating memory blocks

• US 7,136,982 B2
• Filed: 11/09/2001
• Issued: 11/14/2006
• Est. Priority Date: 11/09/2001
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Danger Incorporated (Microsoft Corporation)
• Inventors: Britt, Joe Freeman Jr.
• Primary Examiner(s): Shah, Sanjiv
• Assistant Examiner(s): Rojas, Midys
• Application Number:
  US10/053,205
• Publication Number:
  US 20030093643A1
• Time in Patent Office: 1,831 Days
• Field of Search: 711/161, 711/162
• US Class Current: 711/170
• CPC Class Codes: G06F 11/1004 to protect a block of data words, e.g. CRC or checksum G06F11/1076 takes precedence; security arrangements for protecting computers or computer systems against unauthorized activity G06F21/00
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

Abstract

A method is disclosed for storing program code on a data processing device comprising: splitting the program code into one or more blocks; assigning each of the blocks a header containing a sequence number identifying which portion of the program code each of the blocks correspond to; and storing the one or more blocks of program code and the associated headers in a non-volatile memory.

Claims

1. A method implemented by a service for maintaining control over stored one or more applications on a data processing device:

transmitting said one or more applications from a server to said data processing device concurrently with block allocation data indicating blocks on said data processing device into which said one or more applications are to be stored; and

maintaining a list of all subsequent data transactions performed with said data processing device during end-user operation of said device, said list usable by said server to construct a map of all applications stored on said data processing device.

2. The method as in claim 1 further comprising:

generating said map of all applications stored on said data processing device prior to a new transaction with said data processing device.

3. The method as in claim 2 wherein said new transaction is an application patch.

4. The method as in claim 2 wherein said new transaction is a new application download.

5. The method as in claim 3 further comprising:

transmitting said patch to said data processing device along with an indication of where said patch should overwrite a portion of said application.

6. The method as in claim 5 wherein said indication is an offset in memory.

7. The method as in claim 6 further comprising:

loading said one or more blocks of program code into volatile memory,

identifying said portion of said program code with said offset and

overwriting said portion of said program code with said program code patch.

8. The method as in claim 7 further comprising:

executing an error checking algorithm to ensure said one or more blocks of program code containing said program code patch are valid.

9. The method as in claim 8 further comprising:

storing said one or more blocks of program code containing said program code patch to non-volatile memory.

10. A method comprising:

maintaining a program code map on a server indicating how program code is allocated among a plurality of non-volatile memory blocks on a data processing device;

using said program code map to facilitate modifications to said program code on said data processing device;

maintaining a list of transactions between said server and said data processing device during end-user operation of said data processing device; and

running an algorithm to construct said map in realtime using said list of transactions, said algorithm being an algorithm executed on said data processing device to store program code within said plurality of non-volatile memory blocks of the data processing device.

11. The method as in claim 10 wherein using said program code map comprises:

calculating a location of a program code patch within said program code; and

transmitting said program code patch to said data processing device along with said location.

12. The method as in claim 11 wherein said location is an offset in memory.

13. The method as in claim 10 wherein said non-volatile memory blocks are flash memory blocks.

14. The method as in claim 10 wherein using said program code map comprises:

identifying a specific block within said non-volatile memory to be replaced;

transmitting said specific block to said data processing device;

said data processing device combining said block in volatile memory with one or more other blocks containing program code for a specific application and verifying a signature of said application; and

saving said specific block to non-volatile memory once said signature is verified.

15. The method as in claim 14 further comprising:

executing a cyclical redundancy checking (CRC) to verify that said program code within said specific block is valid.

16. A system comprising:

a server to transmit program code to a data processing device and during end-user operation of said data processing device to maintain a list of transactions between said server and said data processing device and to monitor (1) which program code is stored on said data processing device and (2) specific areas in a memory space in which said program code is stored on said data processing device; and

the server to transfer additional program code to said data processing device along with storage location data indicating where in said memory said additional program code should be stored.

17. The system as in claim 16 wherein said storage location data comprises an offset in said memory of said data processing device indicating where within said memory said additional program code should be transmitted.

18. The system as in claim 16 wherein said storage location data comprises one or more non-volatile memory blocks where said additional program code should be stored.

19. The system as in claim 18 wherein said additional program code comprises a patch to a current program stored on said data processing device.

20. The system as in claim 19 wherein said server transfers an updated CRC value with said patch, said CRC value identifying data within a particular block in which said patch is required as being valid data.

21. The system as in claim 18 wherein said server transfers a cyclical redundancy checking (CRC) value with each block of program code transmitted to said data processing device.

22. The system as in claim 19 wherein said server transfers an updated application signature usable by said data processing device to authenticate an application upgraded by said patch.

23. The system as in claim 16 wherein said data processing device is a wireless device.