Data backup for a mobile computing device

• US 8,812,614 B2
• Filed: 06/05/2008
• Issued: 08/19/2014
• Est. Priority Date: 06/05/2008
• Status: Expired due to Fees

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Welingkar, Bharat, Nair, Jiji
• Primary Examiner(s): Rashid, Harunur
• Application Number:
  US12/134,154
• Publication Number:
  US 20090307284A1
• Time in Patent Office: 2,266 Days
• Field of Search: 709/217, 709/218, 709/219, 707/640
• US Class Current: 709/217
• 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 21/1082 Backup or restore

Abstract

A system and method of backing up a data file from a mobile computing device is disclosed. The method can include receiving a data file from the mobile computing device at a server computer and storing the data file on a storage device. The method can include receiving data indicative of changes made to the data file on the mobile computing device. The method can further include changing the data file stored on the storage device based on the data indicative of changes made to the data file on the mobile computing device.

Claims

1. A method of backing up a first file stored on a mobile computing device, comprising:

receiving, at a server computer, a first data based on the first file;

storing a second file based on the first data on a storage device remote from the mobile computing device, the storage device corresponding to a predetermined particular backup location, wherein the first file and the second file have a same database file format, such that the second file stored is substantially identical at a binary level to the first file;

receiving, at the server computer, second data indicative of changes made to the first file, wherein the second data comprises indications of changes to the first file since a previous backup of the first file, the changes including data added or data deleted, the previous backup being associated with a previous modification number, wherein the indications of data changed in the first file since a previous backup comprises a new modification number associated with the changes made to the first file;

determining that the new modification number is different from the previous modification number;

upon determining that the new modification number is different from the previous modification number, changing the second file based on the data indicative of changes made to the first file, wherein the changed second file is substantially identical at a binary level to and has a same database file format as the changed second file stored on the mobile computing device, wherein changing the second file comprises updating a schema of the second file; and

in response to updating the schema, updating data of the changed second file.

2. The method of claim 1, wherein the first data and second data are received via wireless communication.

3. The method of claim 1, wherein the second data is received periodically.

4. The method of claim 1, wherein the second data is communicated via a synchronization protocol.

5. The method of claim 1, further comprising:

encrypting the second file.

6. The method of claim 1, wherein the first data file comprises user calendar data and the second data comprises at least one of an added calendar entry and a deleted calendar entry.

7. The method of claim 1, further comprising:

receiving a request to download data to the mobile computing device or a second mobile computing device; and

transmitting the changed second file to the mobile computing device or the second mobile computing device without sending incremental data.

8. The method of claim 7, wherein the changed second file received from the storage device is saved on the mobile computing device in the same database file format in which it was stored on the storage device.

9. The method of claim 1, further comprising:

in response to changing the second file, deleting at least some of the second data.

10. The method of claim 1, wherein the database file format of both the first file and the second file is a relational database file format.

11. The method of claim 10, wherein the database file format of both the first file and the second file is a structured query language format.

12. The method of claim 11, wherein the first file and the second file have a same file extension.

13. The method of claim 12, wherein the file extension is .db3.

14. The method of claim 1, further comprising:

storing application files received from the mobile computing device on the storage device.

15. The method of claim 1, wherein the first file and the first data are received from the mobile computing device at the server computer through a communications module configured to communicate using at least one of an Open Mobile Alliance for Device Management protocol or an Open Mobile Alliance for Device Synchronization protocol.

16. The method of claim 1, further comprising:

storing a third file received from the mobile computing device in a different format than the database file format.

17. A server, comprising:

a processor; and

one or more non-transitory computer-readable media having program code stored thereon, the program code being executable by the processor to implement;

a first program code module configured to receive a first data from a mobile computing device based on a first file,

a second program code module configured to store a second file based on the first data on a storage device, the storage device corresponding to a predetermined particular backup location, wherein the first file and the second file have a same database file format, such that the second file stored is substantially identical at a binary level to the first file,

a third program code module configured to receive second data indicative of changes made to the first file, wherein the second data comprises indications of changes to the first file since a previous backup of the first file, the changes including data added or data deleted, the previous backup being associated with a previous modification number, wherein the indications of data changed in the first file since a previous backup comprises a new modification number associated with the changes made to the first file,

a fourth program code module configured to determine that the new modification number is different from the previous modification number, and

a fifth program code module configured to change the second file based on the data indicative of changes made to the first file upon determining that the new modification number is different from the previous modification number, including updating a schema of the second file, and in response to updating the schema, updating data of the second file; and

wherein the changed second file is substantially identical at a binary level to and has a same database file format as the changed second file stored on the mobile computing device.

18. The server of claim 17, wherein the program code is executable by the processor to implement a sixth program code module configured to provide a user account for the mobile computing device and configured to authenticate a message from the mobile computing device before changing the second file stored on the storage device.

19. The server of claim 17, wherein the program code is executable by the processor to implement a seventh program code module configured to encrypt the changed second file stored in the storage device and to store the encrypted changed second file in the storage device.