Browse Prior Art Database

Automatic wired and over-the-air synchronization of multiple local data copies from an original shared source

IP.com Disclosure Number: IPCOM000145249D
Publication Date: 2007-Jan-11
Document File: 2 page(s) / 30K

Publishing Venue

The IP.com Prior Art Database

Abstract

In some applications, a record copy is created from a source database and stored in the user's mailbox on the server or similar storage mechanism. This record is then synchronized over-the-air so that a second copy of that record is stored on the user's mobile device. Alternatively, it is first stored on the mobile device, and then synchronized with a server copy. The link to the original source is lost, however. It would be beneficial for the mobile copy to be synchronized in some way with the original source through a dependency, and have the ability to refresh or merge changes from that source when those changes occur. An example is remote address lookup, where contact information is fetched from the corporate directory (global address list) on the Exchange server. If lookup is used to retrieve contact information, it can be stored in the device's address book. It is then synchronized with the personal contact database in Outlook through the data sync protocol. However, both these copies are no longer associated with the source record which lives in the global address list. If an employee's office number changes, for instance, then the device is not informed. The user would need to periodically perform lookups on all contacts to retrieve the most up-to-date information, which is obviously impractical. The solution is to be able to detect changes in the source record, and then notify all users who have local copies of that record so that the changes can be merged automatically through a conflict resolution rule, or interactively with user control. The system will keep track of record copies through a link identifier that identifies copies of the original. Client databases will listen for changes to the master records and perform replacements as necessary. Alternatively, a server component can re-scan the global address list periodically through a polling mechanism. Any copies that are being linked to that no longer exist will be deleted. The server copy that gets updated will then get automatically synchronized with the copy present on the device. The effect is that if one of the fields of a contact in the global address list is changed in content, such as a phone number, it will get automatically updated in the user's personal address book, and will also get automatically synced with the device. In addition, in some cases it may be desirable for the personal address book copy to maintain a link to the source so that if the user changes a field on the device copy, the personal address book copy will get updated, as will the original source in the global address list. Permissions may be put in place to restrict which fields or which users are allowed to do this. For instance, system administrators may have permission to modify any global address list contact from their device.

This text was extracted from a Microsoft Word document.
This is the abbreviated version, containing approximately 52% of the total text.

improved data synchronization


Automatic wired and over-the-air synchronization of multiple local data copies from an original shared source

Disclosed Anonymously

In some applications, a record copy is created from a source database and stored in the user's mailbox on the server or similar storage mechanism. This record is then synchronized over-the-air so that a second copy of that record is stored on the user's mobile device. Alternatively, it is first stored on the mobile device, and then synchronized with a server copy. The link to the original source is lost, however. It would be beneficial for the mobile copy to be synchronized in some way with the original source through a dependency, and have the ability to refresh or merge changes from that source when those changes occur.

An example is remote address lookup, where contact information is fetched from the corporate directory (global address list) on the Exchange server. If lookup is used to retrieve contact information, it can be stored in the device's address book. It is then synchronized with the personal contact database in Outlook through the data sync protocol. However, both these copies are no longer associated with the source record which lives in the global address list. If an employee's office number changes, for instance, then the device is not informed. The user would need to periodically perform lookups on all contacts to retrieve the most up-to-date information, which is obviously impractical.

The solution is to be able to detect changes in the source record, and then noti...