Distributed messaging system and method for sharing network status data

• US 8,180,882 B2
• Filed: 07/22/2004
• Issued: 05/15/2012
• Est. Priority Date: 07/22/2004
• Status: Expired due to Fees

• Current Assignee: Tyco Electronics Subsea Communications LLC (TE Connectivity Ltd. (United Kingdom))
• Original Assignee: Tyco Electronics Subsea Communications LLC (TE Connectivity Ltd. (United Kingdom))
• Inventors: Liss, Jonathan M., Sabet, Sameh A., Deverin, Jeffrey A.
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US10/896,541
• Publication Number:
  US 20060020686A1
• Time in Patent Office: 2,854 Days
• Field of Search: 709/251
• US Class Current: 709/224
• CPC Class Codes: H04L 41/052 using standardised network management architectures, e.g. telecommunication management network [TMN] or unified network management architecture [UNMA]
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

A distributed messaging system and method allows servers in a network to share data, such as network status data associated with all of the servers in the network. In one embodiment, the distributed messaging system and method may be used in element management system (EMS) servers in a distributed network management system (NMS). The servers in the network share the data in a distributed manner by transmitting messages including the network status data, for example, using a star/broadcast method or a circular message queue (CMQ) method.

Claims

1. A method for sharing network status data between an element management system (EMS) server and a plurality of other EMS servers in an optical communication network wherein each EMS server in the network manages associated network elements and wherein the network status data for each EMS server in the network includes data forwarded to the EMS server from the network elements associated therewith, said method comprising:

providing a data structure in said EMS server, said data structure including network status data associated with all said EMS servers in said network;

receiving at least one message in said EMS server, said received message being sent by at least one of said other EMS servers and said received message including network status data associated with all said EMS servers in said network;

updating said data structure in said EMS server with updated network status data from said received message;

updating said data structure in said EMS server with updated network status data obtained by said EMS server when performing EMS functions;

transmitting at least one message from said EMS server to all of said other EMS servers at a predetermined time, said at least one transmitted message including said updated data structure, said updated data structure comprising network status data associated with all said EMS servers in said network;

providing a list of said other EMS servers in said EMS server, wherein transmitting said at least one message includes transmitting said message to a neighboring one of said EMS servers as according to an order defined by said list of EMS servers;

determining if a predetermined timeout time for receiving said message from a neighboring server has expired;

broadcasting an availability status request message to said other EMS servers if said predetermined timeout time for receiving said message has expired to determine which of said other EMS servers are available EMS servers; and

transmitting said message to at least one of said available EMS servers.

2. The method of claim 1 further comprising updating a user interface with said updated network status data from said received message and said updated network status data obtained by said EMS server when performing EMS functions.

3. The method of claim 1 wherein said network status data includes network alarm status data and EMS status data.

4. The method of claim 1 wherein said data structure is provided in a message buffer.

5. The method of claim 1 wherein said data structure includes data blocks corresponding to each of said EMS servers.

6. The method of claim 5 wherein each of said data blocks includes a date/time stamp of a last update for said data block.

7. The method of claim 6 wherein each of said data blocks includes EMS server availability data.

8. The method of claim 1 wherein transmitting said at least one message includes broadcasting said at least one message to other said EMS servers in said network.

9. The method of claim 8 wherein said predetermined time for transmitting is a transmit time for broadcasting.

10. The method of claim 8 further comprising comparing said data structure to a last transmitted message, and wherein said at least one message is transmitted if said data structure has changed from said last transmitted message.

11. The method of claim 10 further comprising broadcasting said at least one transmitted message after a predetermined keep alive time even if said data structure has not changed from said last transmitted message.

12. The method of claim 10 further comprising determining if a message has not been received from at least one of said other EMS servers after a receive time expires.

13. The method of claim 8 wherein said data structure includes data blocks corresponding to said EMS servers in said network, and wherein each of said data blocks includes a date/time stamp of a last update for said data block, EMS status data, EMS alarm status data, and EMS server availability data.

14. The method of claim 1 wherein said predetermined time for transmitting is a predetermined delay time after receiving said message from a neighboring EMS server.

15. The method of claim 1 wherein said at least one message is transmitted to said neighboring EMS server only if said neighboring EMS server is available.

16. The method of claim 1 wherein said data structure includes, for each of said EMS servers, availability data, a delay time, a time stamp of the last message transmittal, and alarm status data.

17. The method of claim 1 further comprising synchronizing a time clock in said EMS server with time clocks in said other EMS servers.

18. A non-transitory machine-readable medium whose contents cause a computer system to perform a method of sharing network status data between an element management system (EMS) server and a plurality of other EMS servers in an optical communication network wherein each EMS server in the network manages associated network elements and wherein the network status data for each EMS server in the network includes data forwarded to the EMS server from the network elements associated therewith, said method comprising:

providing a data structure in said EMS server, said data structure including network status data associated with all said EMS servers in said network;

receiving at least one message in said EMS server, said received message being sent by at least one of said other EMS servers and said received message including network status data associated with all said EMS servers in said network;

updating said data structure in said EMS server with updated network status data from said received message;

updating said data structure in said EMS server with updated network status data obtained by said EMS server when performing EMS functions;

transmitting at least one message from said EMS server to all of said other EMS servers at a predetermined time, said at least one transmitted message including said updated data structure, said updated data structure comprising network status data associated with all said EMS servers in said network;

providing a list of said other EMS servers in said EMS server, wherein transmitting said at least one message includes transmitting said message to a neighboring one of said EMS servers as according to an order defined by said list of EMS servers;

determining if a predetermined timeout time for receiving one of said messages from a neighboring server has expired;

broadcasting an availability status request message to said other EMS servers if said predetermined timeout time for receiving said one of said messages has expired to determine which of said other EMS servers are available EMS servers; and

transmitting said message to at least one of said available EMS servers.

19. The non-transitory machine-readable medium of claim 18 wherein transmitting said at least one message includes broadcasting said at least one message to other said EMS servers in said network at a predetermined transmit time.

20. The non-transitory machine-readable medium of claim 19 wherein said data structure includes data blocks corresponding to said EMS servers in said network, and wherein each of said data blocks includes a date/time stamp of a last update for said data block, EMS status data, EMS alarm status data, and EMS server availability data.

21. The non-transitory machine-readable medium of claim 19 wherein said method further comprises comparing said data structure to a last transmitted message, and wherein said at least one message is transmitted if said data structure has changed from said last transmitted message or if after a predetermined keep alive time even if said data structure has not changed from said last transmitted message.

22. The non-transitory machine-readable medium of claim 18 wherein said data structure includes, for said EMS servers, availability data, a delay time, a time stamp of the last message transmittal, and alarm status data.

23. The non-transitory machine-readable medium of claim 18 wherein said method further comprises synchronizing a time clock in said EMS server with time clocks in other said EMS servers.

24. A method for distributed messaging of network status data between an element management system (EMS) servers in an optical communication network wherein each of the EMS servers in the network manages associated network elements and wherein the network status data for each of the EMS servers in the network includes data forwarded to the EMS server from the network elements associated therewith, said method comprising:

providing a message buffer in each of said EMS servers, said message buffer including data blocks with network status data associated with all said EMS servers in said network, wherein said network status data in each of said data blocks includes EMS alarm status data and EMS status data;

updating said message buffer in each of said EMS servers with updated network status data obtained by each of said EMS servers;

broadcasting messages from each of said EMS servers at different transmit times, each of said messages including a copy of said message buffer from a respective one of said EMS servers, said copy of said message buffer including data blocks with network status data associated with all said EMS servers in said network;

determining if a predetermined timeout time for receiving said message at a first one of said EMS servers from a second one of said EMS servers has expired;

broadcasting an availability status request message from said first one of said EMS severs to other ones of said EMS servers if said predetermined timeout time for receiving said message has expired to determine which of said other ones of said EMS servers are available EMS servers; and

updating said message buffers in each of said EMS available servers based on said network status data in said messages received by said EMS available servers.

25. The method of claim 24 wherein each of said data blocks includes a date/time stamp of a last update of said data block and EMS server availability data.

26. The method of claim 24 further comprising comparing said data blocks in said message buffer to said data blocks in a last transmitted message, wherein each of said EMS servers broadcasts said message if said data blocks has changed from a last transmitted message.

27. The method of claim 26 further comprising broadcasting said messages if a predetermined keep alive time expires from said last transmitted message even if said data blocks does not change from said last transmitted message.

28. The method of claim 24 further comprising updating user interfaces managed by said EMS servers with updated network status data.

29. The method of claim 24 further comprising synchronizing time clocks in said EMS servers.

30. A distributed network management system (NMS) comprising:

a plurality of element management systems (EMSs) for managing network elements, each of said EMSs comprising hardware and including a data structure containing network status data associated with each of said EMSs;

wherein each of said EMSs is configured to obtain network status data from said network elements being managed;

wherein each of said EMSs is configured to transmit by broadcasting and receive messages directly to and from other said EMSs in said network at a predetermined transmit time, said messages including said data structures from respective said EMSs;

wherein each of said EMSs is configured to update said data structure with said network status data obtained from said network elements being managed and with said network status data in said messages received from other said EMSs;

wherein at least a first one of said EMSs is configured to determine if a predetermined timeout time for receiving one of said messages from a second one of said EMSs has expired;

wherein said first one of said EMSs is configured to broadcast an availability status request message to other ones of said EMSs if said predetermined timeout time for receiving said one of said messages has expired to determine which of said other ones of said EMSs are available EMSs; and

wherein said first one of said EMSs is configured to broadcast said messages to said available EMSs.

31. The distributed network management system of claim 30 wherein each of said EMSs is configured to transmit a message by transmitting said message to a neighboring EMS, as defined by a list of said EMSs, after a predetermined delay from when said message is received.

32. The distributed network management system of claim 30 wherein each of said EMSs is time synchronized with other said EMSs.