METHOD FOR DATA COMMUNICATION AND DEVICE AS WELL AS COMMUNICATION SYSTEM

Abstract

A method for data communication between a management system and a network element is provided as well as a device and a communication system. The method includes the steps of (i) Setting up a connection between the management system and the network element; (ii) The management system sends a message to the network element utilizing the connection; and (iii) Upon said message of the management system, the network element provides static information to the management system.

Description

The invention relates to a method for data communication, to a device and to a communication system comprising such a device.

The concept of alarming is widely used in IT and telecommunications networks to notify erroneous conditions or any other event that may require attention and/or intervention of an operator.

Alarms are preferably emitted by managed network elements and they are sent to management systems, which, e.g., process, store and display the alarms to the operator.

An alarm in particular comprises:

• • dynamic information, which is specific for the actual alarm instance, e.g., an exact date, time or location (port, process, etc.) of the current problem;
  • static information, which is independent of the actual alarm instances, e.g., textual description of the alarm, follow up or suggested repair actions.

However, disadvantageously static alarm information is sent along with every instance of an alarm. This leads to significant network traffic to be transmitted throughout a managed network. Furthermore, for some types of alarm, the size for an alarm notification is limited thereby restricting the available data size for static information to be transmitted. Also, the static alarm information regarding all alarms is not available for the operator at the management system (lack of overview).

It is another disadvantage that in case of preinstalled alarm information at the management system, a re-installation is required each time a static alarm information of a managed element changes, e.g., due to an update or a new alarm added.

The object to be solved is to overcome the disadvantages as stated before and to provide an efficient communication between a management system and at least one network element (managed element).

This problem is solved according to the features of the independent claims. Further embodiments result from the depending claims.

In order to overcome this problem, a method for data communication between a management system and a network element is provided, said method comprising the following steps:

• • Setting up a connection between the management system and the network element;
  • The management system sends a message to the network element utilizing the connection;
  • Upon said message of the management system, the network element provides static information to the management system.

Hence, based on the connection set up between the management system and the network element, the management systems sends a message to the network element, said message may initiate the network element sending static information to the management system.

It is to be noted that the network element as referred to may comprise or be a managed (network) element, an element manager or an element management system (EMS).

In an embodiment, said static information comprises static alarm information.

As an advantage, the static alarm information is made available to the management system and hence informs an operator at the management system about all alarms that may occur.

In an embodiment, the static information comprises a textual description of at least on event and an identifier for each such at least one event.

Hence, there is a mapping between the event (that may be an alarm) and the textual description of the event. This allows the network element to notify an alarm to the network management system, in particular by transmitting said identifier together with dynamic alarm information such as an actual alarm instance, e.g., an exact date and/or time and/or location (port, process, line card, etc.) of the problem. The identifier received at the management system can be translated into a textual description relating to the alarm instance in general (e.g., regarding its meaning and/or what to do in case such an alarm is reported) and hence the full information regarding the alarm comprising dynamic alarm information as well as static alarm information can be displayed to the operator.

In another embodiment, the event is notified by the network element (to the management system) by sending dynamic event information together with said identifier thereby enabling the management system to produce static information related to said identifier.

In a further embodiment, the event comprises an alarm event that is (to be) notified to the management system.

In a next embodiment, the connection between the management system and the network element is associated with a Common Object Request Broker Architecture (CORBA).

It is also an embodiment that the connection is associated with a file transfer protocol (FTP).

Pursuant to another embodiment, the message sent by the management system comprises a request, in particular an update request regarding static alarm information.

According to an embodiment, the management system is a network management system.

According to another embodiment, the network element is of the following type:

• • a managed element;
  • a network node;
  • a gateway;
  • a switch;
  • a terminal;
  • a relay node;
  • a router;
  • an edge router.

The problem stated above is also solved by a device comprising a processor unit that is arranged such that the method as described can be executable on said processor.

Further, the problem is solved by a device for communicating with a management system, the device comprising a processor unit that is equipped such that the following steps are executable:

• • Setting up a connection between the management system and the device;
  • The management system sends a message to the device utilizing the connection;
  • Upon said message of the management system, the device provides static information to the management system.

Such device preferably is a network element, in particular a managed network element.

In addition, the problem is solved by a device for communicating with a network element, the device comprising a processor unit that is equipped such that the following steps are executable:

• • Setting up a connection between the device and the network element;
  • The device sends a message to the network element utilizing the connection;
  • Upon said message of the device, the network element provides static information to the device.

Such device preferably is a management system.

Furthermore, the problem is solved by a communication system comprising a device as described herein.

Embodiments of the invention are shown and illustrated in the following figures:

FIG. 1 shows a graph comprising a network management system and several managed elements to illustrate an automatic upload of static alarm information to a file system at the network management system;

FIG. 2 shows a message chart between a network management system and a managed element showing as how to provide static information to the network management system.

FIG. 1 shows a diagram comprising a Management System 101 with a File System 102, a Server 103 and a Client Alarm Display 104. Furthermore, a Managed Element 105 is shown comprising a Dynamic Alarm component 106 and several Static Alarm Information records 107. Another Managed Element 108 is shown also comprising a Dynamic Alarm component 109 and several Static Alarm Information records 110.

The respective Static Alarm Information records 107 and 110 of Managed Element 105 and 108 are uploaded into the File System 102 of the Management System 101. Such upload can be processed based on a connection such as a CORBA I/F interface, which may be realized as an extension to TMF 814.

Thus, the records 107 and 110 of both Managed Elements 105 and 108 are once uploaded and then be accessible at the Management System 101.

In case a Managed Element 105 becomes aware of an alarm to be notified to the Management System 101, the Dynamic Alarm data 106 is sent to the Server 103 of the Management System 101. The Dynamic Alarm data 106 comprises an identifier of the alarm type that allows the Server 103 to access additional data related to this particular alarm type from its File System 102. The Server 103 further compiles the alarm notification comprising dynamic data sent from the Dynamic Alarm component 106 and static data that is obtained from the File System 102 (records are previously entered into said File System 102 as described). The full notification is forwarded from the Server 103 to the Client Alarm Display 104 thereby notifying, e.g., an operator of the alarm of Managed Element 105 with detailed information, i.e. dynamic components and static components.

Advantageously, only dynamic portions in addition to an identifier to a static record are sent from the Dynamic Alarm component 106 to the Management System 101 in case an alarm occurs. This reduces the amount of redundant data to be transferred as the static portion of an alarm remains unchanged and can be addressed by the identifier as described.

FIG. 1 can also be summarized as follows:

• a) The static alarm information is uploaded at runtime from the Managed Element 105 and/or 108 to the Management System 101 and it is stored in its File System 102. Hence, multiple heterogeneous managed elements can be handled. As an interface between the Managed Element 105 or 108 and the Management System 101 an extension of the TMF 814 CORBA interface can be defined.
• b) At the Management System 101 the complete alarm information is available by merging the dynamic alarm portion obtained from the Managed Element 105 or 108 with the static portion already available and stored in the File System 102.

The approach presented herewith shows in particular the following advantages:

• 1) The CORBA interface selected for uploading the static alarm information fits smoothly into a TMF 814 concept for dynamic alarm notifications:
  • i) Performance of the data transfer is excellent since the data transfer is binary encoded.
  • ii) The CORBA connection between management system and managed element is anyway necessary for dynamic alarm notifications. Hence, it can be reused for uploading the static alarm information as shown. Advantageously, no additional infrastructure (e.g., a setup of user accounts) is required.
• 2) Static alarm information is separated from the dynamic alarm instance:
  • i) The redundant static information of an alarm can be avoided, thus reducing the overall network traffic.
  • ii) Furthermore, static information is not limited in size (as opposed to dynamic alarms which are usually limited). This allows each alarm to be described more elaborate, e.g. detailed description or instruction regarding repair actions can be provided.
• 3) The static alarm information is retrieved at runtime from the managed element:
  • i) The overall static alarm information is available to the operator at the management system. Such information can be displayed and also further processed or exported.
  • ii) As the alarm information is dynamically uploaded during runtime, changes of the alarm information are transparent to the management system, i.e. there is no need for an update installation of the management system.
  • iii) Multiple heterogeneous managed elements and also different versions of a network element can be supported. The static alarm information can be uploaded and stored for each managed element individually.

FIG. 2 shows a message chart comprising a Network Management System 210 and a Managed Element 220. The communication exchanged between both entities is based on an existing and already established connection 201, e.g. according to a CORBA interface. The Network Management System 210 sends an Update Request 202 to the Managed Element 220 thereby initiating it to send a Static Information response 203 comprising an identifier ID, a name, a description, a severity indication and an instruction-follow up of the respective static alarm information. This kind of communication can initiated by the Network Management System 210 with each associated Managed Element, thereby setting up the File System as shown in FIG. 1 with the alarm information of all available alarms to be notified by said Managed Elements.

Claims

1-14. (canceled)

15. A method of data communication between a management system and a network element, the method which comprises the following steps: setting up a connection between the management system and the network element;sending a message from the management system to the network element utilizing the connection;upon receiving the message of the management system, providing static information from the network element to the management system, the static information comprising a textual description of at least one event and an identifier for each such at least one event; andnotifying, by the network element, an event by sending dynamic event information together with the identifier to enable addressing of the static information at the management system.

16. The method according to claim 15, wherein the static information comprises static alarm information.

17. The method according to claim 15, wherein the event comprises an alarm event to be notified to the management system.

18. The method according to claim 15, wherein the connection is associated with a Common Object Request Broker Architecture.

19. The method according to claim 15, wherein the connection is associated with a file transfer protocol.

20. The method according to claim 15, wherein the message sent by the management system comprises a request.

21. The method according to claim 20, wherein the request is an update request regarding static alarm information.

22. The method according to claim 15, wherein the management system is a network management system.

23. The method according to claim 15, wherein the network element complies with at least one of the following: a managed element;a network node;a gateway;a switch;a terminal;a relay node;a router;an edge router.

24. A device, comprising a processor unit with a processor programmed to execute the method according to claim 15.

25. A communication system, comprising the device according to claim 24.

26. A device for communicating with a management system, the device comprising: a processor unit configured to enable execution of the following steps:setting up a connection between the management system and the device;sending a message from the management system to the device utilizing the connection;upon the message of the management system, providing with the device static information to the management system, the static information being formed of a textual description of at least one event and an identifier for each such at least one event; andnotifying, by the device, an event by sending dynamic event information together with the identifier to enable addressing of the static information at the management system.

27. A communication system, comprising the device according to claim 26.

28. A device for communicating with a network element, the device comprising: a processor unit configured enable execution of the following steps;setting up a connection between the device and the network element;sending a message from the device to the network element utilizing the connection;upon the message of the device, providing with the network element static information to the device, the static information being formed of a textual description of at least one event and an identifier for each such at least one event; andnotifying, by the network element, an event to the device by sending dynamic event information together with the identifier to enable addressing the static information at the device.

29. A communication system, comprising the device according to claim 28.