Microsoft Technology Licensing, LLC

Jörg-Thomas Pfenning

Lev Novik

Moe Khosravy

Michael Ray Clark

Michael Scott Beckerman

Oliver C Lee

Sean Michael Kelley

A sync community may include a group of synchronization endpoints. When two synchronization endpoints of the sync community synchronize with one another, a synchronization data conflict may be detected when the two synchronization endpoints make a change to a same particular data item and the two synchronization endpoints were unaware of the changes to the same particular data item made by the other respective synchronization endpoint at the time the changes were made. Resolution of the detected synchronization data conflict may be delayed and data indicative of the detected synchronization data conflict may be propagated to other synchronization endpoints during a synchronization operation.

Propagation of conflict knowledge

A variety of flexible conflict resolution policies are provided for loosely coupled devices to implement according to a variety of different synchronization scenarios. Choosing a conflict resolution policy, such as 'Most Frequent Updater,' 'Priority,' &#x201c;PerCent Change,&#x201d; &#x201c;Arbiter Deadlock Resolution,&#x201d; etc., enables devices to select how and when to resolve such synchronization conflicts. In addition, with reference to a conflict log, a user or synchronizing application can roll back synchronization state to a time before a conflict may have arisen, so that the user or application can undo a resolution of a conflict and/or the user or application can apply an alternative conflict resolution policy moving forward from that time.

Efficient knowledge representation in data synchronization systems

Growing community of inventors

Redmond, WA, United States of America

Jörg-Thomas Pfenning