Abstract: Systems and methods for orchestrating synchronizations between different targets in a synchronization community. The order and nature of synchronizations may depend on multiple factors, including the initiator of the synchronization, the data being synchronized, and other characteristics of the synchronization participants and synchronization community.

Abstract: 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.

Abstract: Various technologies and techniques are disclosed that improve synchronization of data between varying types of devices and/or services. A full participant receives a request from another participant to perform a synchronization operation. The synchronization engine determines whether the device or service is a full, partial, or simple participant. The device or service is a simple participant if it has a data store for synchronized data and no knowledge store. The device or service is a partial participant if it has a data store for synchronized data and a knowledge store, but does not understand the knowledge. The device or service is a full participant type if it has a data store for synchronized data and a knowledge store and understands the knowledge. The synchronization engine performs the synchronization operation with the device or service using a set of logic that is appropriate for the type of device or service.

Abstract: 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,” “PerCent Change,” “Arbiter Deadlock Resolution,” 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.

Abstract: 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,” “PerCent Change,” “Arbiter Deadlock Resolution,” 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.

Abstract: 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.

Abstract: Systems and methods for orchestrating synchronizations between different targets in a synchronization community. The order and nature of synchronizations may depend on multiple factors, including the initiator of the synchronization, the data being synchronized, and other characteristics of the synchronization participants and synchronization community.

Abstract: After detecting that an event occurs for which notification is desired, a notification service determines an appropriate way to notify the user given the user's current circumstances. The notification service determines the appropriate notification method by accessing context information for the user (e.g., whether the user's telephone is on, busy, in hands-free mode, in meeting mode, or the like). The notification service then accesses a set of rules from which the appropriate notification method may be determined based on the current circumstances of the user. These rules may be, for example, default rules or may be set of the user. The notification service then causes the notification to be sent to the user using the appropriate notification method. The notification methods include voice notifications in which the notification is read to the user.

Abstract: Various technologies and techniques are disclosed that improve synchronization of data between varying types of devices and/or services. A full participant receives a request from another participant to perform a synchronization operation. The synchronization engine determines whether the device or service is a full, partial, or simple participant. The device or service is a simple participant if it has a data store for synchronized data and no knowledge store. The device or service is a partial participant if it has a data store for synchronized data and a knowledge store, but does not understand the knowledge. The device or service is a full participant type if it has a data store for synchronized data and a knowledge store and understands the knowledge. The synchronization engine performs the synchronization operation with the device or service using a set of logic that is appropriate for the type of device or service.

Abstract: Presented is a web-based enterprise management compliant management framework whose back end components are decoupled from the various user interfaces available for accessing the management system. In the Windows environment, the management system of the instant invention is also compliant with the Windows management instrumentation (WMI) requirements. This management system includes WMI providers which implement standard interfaces which decouple all semantic and syntactic checks from the user interface and which provide common error strings, help, etc. to a user regardless of the user interface being used. The providers of the management system of the instant invention store and access data in the active directory. As such, these providers present a customizable user interface which may be based on a user's expertise level and which may be dynamically localized to the user's preferred language.

Abstract: A dynamic throughput allocation method and framework are disclosed. The method includes initially providing an interface having a finite throughput. The data calls are allocated varying portions of the connection's available throughput. A throughput allocation server assigns portions of the finite throughput supported by the interface to connections between ones of a set of internal nodes and ones of a set of external nodes connected to ones of the set of internal nodes. The throughput allocation server includes a table describing the portions of the finite throughput assigned to each one of the connections. A throughput allocation controller monitors the available throughput. When under heavy usage, the throughput allocation controller determines that available throughput is less than a minimum desired value, and in response de-allocates a portion, but not all, of the throughput previously allocated to at least one data call.

Abstract: After detecting that an event occurs for which notification is desired, a notification service determines an appropriate way to notify the user given the user's current circumstances. The notification service determines the appropriate notification method by accessing context information for the user (e.g., whether the user's telephone is on, busy, in hands-free mode, in meeting mode, or the like). The notification service then accesses a set of rules from which the appropriate notification method may be determined based on the current circumstances of the user. These rules may be, for example, default rules or may be set of the user. The notification service then causes the notification to be sent to the user using the appropriate notification method. The notification methods include voice notifications in which the notification is read to the user.