Windows management instrument synchronized repository provider

• US 20040003007A1
• Filed: 01/16/2003
• Published: 01/01/2004
• Est. Priority Date: 06/28/2002
• Status: Abandoned Application

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Prall, John M., Urso, Jason T.
• Application Number:
  US10/346,276
• Publication Number:
  US 20040003007A1
• Time in Patent Office: Days
• US Class Current: 707/200
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• 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 69/329 in the application layer [OSI layer 7]

Abstract

A method and synchronized data repository provider that synchronize data of repositories among a plurality of computing nodes is disclosed. Each node includes a synchronized provider, which communicates with the synchronized providers in the other nodes to synchronize the data of the repositories. The communication is with data synchronization messages, which are multicast by a sending node via a multicast communication link to all of the other nodes. A synchronization scope as well as a class limits the data of a repository. A repository is initialized via a point-to-point communication link with another node. The method and synchronized provider include the capability to handle response storms, lost messages and duplicate messages.

Claims

1. A method of communication between a local node and a plurality of remote nodes in a computing system for the synchronization of data, said method comprising communicating data synchronization messages concerning the data of a repository in a multicast mode via a multicast communication link that interconnects all of said nodes.

2. The method of claim 1, wherein at least one of said data synchronization messages includes an identification of synchronization scope of said repository.

3. The method of claim 2, wherein said identification additionally identifies a class of said data.

4. The method of claim 1, wherein at least one of said data synchronization messages is an event instance notification.

5. The method of claim 4, wherein said local node receives said at least one data synchronization message, wherein said repository is a remote repository, wherein said local node includes a local repository, and further comprising updating the data of said local repository with event data of said event instance notification.

6. The method claim of 4, wherein said local node obtains said event instance notification from a local client, and said communicating step sends said at least one data synchronization message from said local node to said remote nodes via said multicast communication link.

7. The method of claim 1, wherein a sequence of said data synchronization messages is received by said local node, and further comprising detecting that at least one message of said sequence of data synchronization messages is lost and recovering said lost message.

8. The method claim 7, wherein each of said data synchronization messages includes an identification of sequence number and source of last update, wherein said detecting step detects a missing sequence number corresponding to said lost message, and wherein said recovering step sends a data synchronization message via said multicast communication link requesting said lost message.

9. The method of claim 1, wherein each of said data synchronization messages includes an identification of sequence number and source of last update, and further comprising detecting that a received one of said data synchronization messages is a duplicate of a previously received data synchronization message, except for a different source of last update;

and sending a data synchronization message requesting a resend of the duplicate message from one of said different sources of last update via said multicast communication link.

10. The method of claim 1, wherein a received data synchronization message requires a response data synchronization message, and wherein said communicating step randomly delays sending said response data synchronization message up to a predetermined amount of time to avoid a response storm.

11. The method of claim 10, wherein said predetermined amount of time is specified in said received data synchronization message.

12. The method of claim 11, wherein said communicating step cancels sending said response message if a valid response data synchronization message is first received from another remote node.

13. The method of claim 1, wherein said local node sends one of said data synchronization messages that requires a response, and wherein said one data synchronization message specifies a predetermined amount of time within which said response can be transmitted.

14. The method of claim 1, further comprising communicating a copy of the data of a repository via a point-to-point communication link between said local node and a single one of said remote nodes.

15. A synchronized repository provider for communication between a local node and a plurality of remote nodes in a computing system comprising a data communication device that synchronizes data of a repository by communicating data synchronization messages concerning the data of said repository in a multicast mode via a multicast communication link that interconnects all of said nodes.

16. The synchronized repository provider of claim 15, wherein at least one of said data synchronization messages includes an identification of synchronization scope of said repository.

17. The synchronized repository provider of claim 16, wherein said identification additionally identifies a class of said data.

18. The synchronized repository provider of claim 15, wherein at least one of said data synchronization messages is an event instance notification.

19. The synchronized repository provider of claim 18, wherein said local node receives said at least one data synchronization message, wherein said repository is a remote repository, wherein said local node includes a local repository, and wherein the data of said local repository is updated with event data of said event instance notification.

20. The synchronized repository provider claim of 18, wherein said communication device obtains said event instance notification from a local client, and wherein said communication device sends said at least one data synchronization message from said local node to said remote nodes via said multicast communication link.

21. The synchronized repository provider of claim 15, wherein a sequence of said data synchronization messages is received by said local node, and said communication device detects that at least one message of said sequence of data synchronization messages is lost and performs a process to recover said lost message.

22. The synchronized repository provider claim 21, wherein each of said data synchronization messages includes an identification of sequence number and source of last update, wherein said communication device detects a missing sequence number corresponding to said lost message, and wherein said process sends a data synchronization message via said multicast communication link requesting said lost message.

23. The synchronized repository provider of claim 15, wherein each of said data synchronization messages includes an identification of sequence number and source of last update, and wherein said communication device detects that a received one of said data synchronization messages is a duplicate of a previously received data synchronization message, except for a different source of last update;

and wherein said communication device sends a data synchronization message requesting a resend of the duplicate message from one of said different sources of last update via said multicast communication link.

24. The synchronized repository provider of claim 15, wherein a received data synchronization message requires a response data synchronization message, and wherein said communication device randomly delays sending said response data synchronization message up to a predetermined amount of time to avoid a response storm.

25. The synchronized repository provider of claim 24, wherein said predetermined amount of time is specified in said received data synchronization message.

26. The synchronized repository provider of claim 25, wherein said communicating step cancels sending said response message if a valid response data synchronization message is first received from another remote node.

27. The synchronized provider of claim 15, wherein said communication device sends one of said data synchronization messages that requires a response, and wherein said one data synchronization message specifies a predetermined amount of time within which said response can be transmitted.

28. The synchronized repository provider of claim 15, wherein said communication device also sends or receives a copy of the data of said repository via a point-to-point communication link between said local node and a single one of said remote nodes.

29. The synchronized provider of claim 15, wherein said communication device comprises a send thread for sending outgoing ones of said data synchronization messages and a receive thread for receiving incoming ones of said data synchronization messages.

30. The synchronized provider of claim 29, wherein said communication device further comprises a client process for processing (a) a client request to send one or more of said outgoing data synchronization messages and (b) one or more of said incoming messages.

31. The synchronized provider of claim 30, wherein at least one of said data synchronization messages is a member of the group which consists of:

event notification, lost message and duplicate message.

32. The synchronized provider of claim 31, wherein said communication device further comprises a sent message map and a receive message map, wherein said send thread saves sent messages to said sent message map and wherein said receive thread accesses at least one of said sent message map and said received message map when processing a lost message.

33. The synchronized provider of claim 31, wherein said communication device further comprises a sent message map and a receive message map, wherein said send thread saves sent messages to said sent message map and wherein said receive thread accesses at least one of said sent message map and said received message map when processing a duplicate message.