MOBILE PHONE DATA BACKUP SYSTEM

• US 20070250645A1
• Filed: 04/20/2007
• Published: 10/25/2007
• Est. Priority Date: 04/20/2006
• Status: Abandoned Application

• Current Assignee: Asurion, LLC (NEW Asurion Corporation)
• Original Assignee: Asurion, LLC (NEW Asurion Corporation)
• Inventors: Salcedo, Jonathan, Meadows, Robert, Larsson, Garrett
• Application Number:
  US11/737,900
• Publication Number:
  US 20070250645A1
• Time in Patent Office: Days
• US Class Current: 709/248
• CPC Class Codes: G06F 11/1446 Point-in-time backing up or restoration of persistent data
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A method and apparatus for backing-up and synchronizing mobile handset data are disclosed. According to one embodiment of the invention, a Mobile Solutions Platform (MSP) architecture and server are defined, such that the MSP provides back-up and synchronization servers to a wide variety of mobile handsets. In addition to supporting a wide variety of mobile handsets, the MSP architecture and server provide support for a wide variety of data types, to include contact information (e.g., names, addresses, and phone numbers), calendar information (e.g., meeting times, and appointment times), tasks, notes, as well as graphics and picture files, video files, and audio files (e.g., ringtones, and music files).

Claims

1. A synchronization server, comprising:

a synchronization interface component including one or more communication protocols for establishing a data communication session with a mobile handset;

content rules stored at the synchronization server and independent of any server-side executable code, wherein said content rules include a list of handset attributes supported by various handset devices; and

;

an intelligent synchronization engine configured to synchronize data received from a mobile handset with data stored in a database integrated with said server.

2. The synchronization server of claim 1, wherein the content rules stored at the synchronization server include customization rules, wherein said customization rules determine services available to a user on a mobile handset.

3. The synchronization server of claim 2, wherein the content rules stored at the synchronization server define a level of customization for handsets associated with a particular carrier, and said server determines the carrier associated with a particular handset by examining a source IP address of an incoming message that is part of a connection request received at the server.

4. The synchronization server of claim 2, wherein the content rules define customizable attributes of a handset, including any one or more of the following:

branding and user experience, language support, configuration of application features enabled based on carrier rules or user subscription level.

5. The synchronization server of claim 2, wherein modifying a content rule stored at the server provides a mechanism by which new menus, representing new services, are dynamically presented on a mobile handset.

6. A method comprising:

receiving, from a mobile handset, a request to synchronize handset data with data stored at a synchronization server;

verifying said data stored at the synchronization server has recently been synchronized with data from one or more third-party data services, and if so, performing a synchronization operation to synchronize the handset data with the data stored at the synchronization server.

7. The method of claim 6, wherein, if the data stored at the synchronization server has not recently been synchronized with the data from one or more third-party data services, initiating a synchronization operation to synchronize the data stored at the synchronization server with data stored at the third-party data service.

8. The method of claim 7, wherein, after the data stored at the synchronization server has been synchronized with data stored at the third-party data service, performing a synchronization operation to synchronize the handset data with the data stored at the synchronization server.

9. The method of claim 6, wherein data conflicts arising during the synchronization operation are resolved by the synchronization server according to default data conflict rules.

10. The method of claim 6, wherein data conflicts arising during the synchronization operation are resolved by the synchronization server according to user-defined data conflict rules.