Systems and methods for synchronizing data between communication devices in a networked environment

• US 10,212,227 B1
• Filed: 08/09/2016
• Issued: 02/19/2019
• Est. Priority Date: 12/12/2003
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: Open Invention Network LLC
• Inventors: Jones, Dan, Vernon, Todd, Kriese, Jeffrey
• Primary Examiner(s): Serrao, Ranodhi
• Application Number:
  US15/232,030
• Time in Patent Office: 924 Days
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1004 Server selection for load balancing
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols

Abstract

A source communication device comprises a cluster manager to group destination device connections into a plurality of performance clusters. The cluster manager then causes a synchronization mechanism to be generated for each performance cluster. Each synchronization cluster can then allow data to be optimally shared between the source device and destination devices within a given cluster.

Claims

1. A device, comprising:

a processor and a memory unit; and

a cluster manager to enable the device to operate as a source device of a cluster, the cluster manager structured to remove one or more of a plurality of communication connections associated respectively with a plurality of destination devices that do not respond within a timeout threshold from the cluster formed with the source device, wherein the source device is structured to share data stored in a source data buffer of the source device with the plurality of destination devices via the plurality of communication connections to replicate the data onto destination data buffers on each of the plurality of destination devices respectively, and when the removed one or more destination devices respond to the timeout threshold, detect a new connection, determine a performance of the new connection, and add the new connection to a cluster based on the performance of the new connection;

wherein the cluster manager is further structured to provide the removed one or more of the plurality of destination devices full-buffer updates until a recent average latency performance of the removed one or more destination devices is at a level that merits insertion back into one of the clusters.

2. The device of claim 1, wherein the cluster manager is structured to group a plurality of connections between the source device and a plurality of destination devices into clusters based on at least one of performance similarities, client service priorities, and resource priorities.

3. The device of claim 1, further comprising a plurality of connection interfaces, wherein the source device is interfaced with the plurality of destination devices via the plurality of connection interfaces and the plurality of communication connections.

4. The device of claim 3, wherein the source data buffer is configured to store data, and wherein the source device is structured to share the data stored in the source data buffer with the plurality of destination devices interfaced with the source device via the plurality of connection interfaces.

5. The device of claim 3, further comprising a plurality of synchronization mechanisms coupled with the plurality of connection interfaces, wherein the cluster manager is configured to assign a synchronization mechanism to each of the clusters.

6. The device of claim 5, wherein each of the plurality of synchronization mechanisms is configured to provide computations and protocols needed to communicate data over the plurality of connections.

7. The device of claim 1, wherein the cluster manager is configured to at least one of create fewer clusters when it is determined that resource priorities are a priority and create more clusters when it is determined that client service is a priority.

8. The device of claim 1, wherein the cluster manager is further configured to detect a change in performance capabilities for one of the plurality of connections and to assign a connection for the one of the plurality of connections to another cluster based on the change in performance capabilities.

9. A system, comprising:

a processor and a memory unit;

an intermediate source device configured to share data stored in an intermediate source data buffer of the intermediate source device with one or more destination devices to replicate the data onto destination data buffers on each of the one or more destination devices respectively, wherein the intermediate source device comprises;

a cluster manager configured to remove one or more destination devices that do not respond within a timeout threshold from a distinct cluster formed with the intermediate source device, but when the removed one or more destination devices respond to the timeout threshold, detect a change in performance capabilities for a connection in one cluster and to assign the connection to another cluster based on the change in performance capabilities;

wherein the removed one or more destination devices receive full-buffer updates until a recent average latency performance of the removed one or more destination devices is at a level that merits insertion back into the distinct cluster.

10. The system of claim 9, wherein the cluster manager is configured to determine subsets of connections from a set of connections and group each of the subsets in the distinct cluster, wherein each connection in each subset has similar performance capabilities with the other connections in the same subset.

11. The system of claim 10, wherein the performance capabilities are based on at least one of performance similarities, client service priorities, and resource priorities.

12. The system of claim 11, wherein the performance similarities for each subset of connections is determined by a similarity in connection bandwidth.

13. The system of claim 11, wherein the performance similarities for each subset of connections is determined by a similarity in connection security.

14. The system of claim 11, wherein the performance similarities for each subset of connections is determined by a similarity in connection error rate.

15. The system of claim 9, further comprising a plurality of synchronization mechanisms, wherein the cluster manager is configured to assign a synchronization mechanism to each distinct cluster.

16. The system of claim 15, wherein each of the plurality of synchronization mechanisms is configured to provide computations and protocols needed to communicate data over the set of connections.

17. A device, comprising:

a processor and a memory unit;

the processor structured to remove one or more of a plurality of destination devices that do not respond within a timeout threshold from a cluster formed with a source device configured to share data stored in a source data buffer of the source device with the plurality of destination devices to replicate the data onto destination data buffers on each of the plurality of destination devices respectively, and when the removed one or more destination devices respond to the timeout threshold, detect a new connection, determine a performance of the new connection, and add the new connection to a cluster based on the performance of the new connection;

wherein the processor is further structured to provide the removed one or more of the plurality of destination devices full-buffer updates until a recent average latency performance of the removed one or more destination devices is at a level that merits insertion back into one of the clusters.