Method and device for processing data for generating alarms within a communication network

• US 20050091404A1
• Filed: 07/24/2003
• Published: 04/28/2005
• Est. Priority Date: 07/25/2002
• Status: Active Grant

• Current Assignee: Piece Future Pte., Ltd.
• Original Assignee: Alcatel SA (Nokia Corporation)
• Inventors: Chevanne, Michel, Drugmand, Philippe, Lapraye, Bertrand
• Granted Patent: US 8,719,395 B2
• Time in Patent Office: Days
• US Class Current: 709/246
• CPC Class Codes: H04L 41/0226 Mapping or translating multiple network management protocols
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

A data processing device (1) comprises processing means (4) capable of receiving from equipment (3) in a communications network primary data defining events in at least one primary format, and delivering to a management device in the network (2) secondary data defining alarms representing events, in a secondary format. The processing means (4) comprise an interpreter (5) provided with conversion rules, arranged in the form of “scripts” associated with the various primary event formats, and arranged to convert, by means of these rules, primary data received in one of the primary formats into secondary data in the secondary format which can be interpreted by the management device (2).

Claims

1. A data processing device (1) comprising processing means (4) capable of receiving, from equipment (3) in a communications network, primary data defining events in at least one primary format and of delivering to a management device in said network (2) secondary data defining alarms representing said events, in a secondary format, wherein said processing means (4) comprise an interpreter (5) provided with conversion rules, arranged in the form of “

scripts”

associated with the various primary event formats, and arranged so as to convert, by means of said rules, primary data received in one of said primary formats into secondary data in said secondary format which can be interpreted by said management device (2).

2. A device as claimed in claim 1, wherein said interpreter (5) is arranged to make said conversions into a secondary configuration file format by means of an interpreted language.

3. A device as claimed in claim 2, wherein said secondary configuration file format is a format chosen from a group comprising XML and the proprietary text formats.

4. A device as claimed in claim 2, wherein said interpreted language is chosen from a group comprising at least JavaScript, VisualBasic, TCL, Perl and Python.

5. A device as claimed in claim 1, wherein, when there are primary data associated respectively with event identifiers, said interpreter (5) is arranged to store at least some of said rules in correspondence with known event identifiers.

6. A device as claimed in claim 5, wherein said interpreter (5) is arranged to store at least one conversion rule defining a default script intended for the primary data associated with an unknown event identifier.

7. A device as claimed in claim 1, wherein said interpreter (5) is arranged to deduce alarm parameters from certain primary data received, so as to deliver a parameterized alarm to said management device (2).

8. A device as claimed in claim 7, wherein said interpreter (5) is arranged to deliver to said management device (2) alarms parameterized by “

hard-coded”

values.

9. A device as claimed in claim 7, wherein said interpreter (5) is arranged to deliver to said management device (2) alarms parameterized by values extracted from said primary data.

10. A device as claimed in claim 7, wherein, when the alarm state of an item of equipment (3) in the network is unknown, said interpreter (5) is arranged to extract from said equipment (3) chosen information representing said alarm state, and then to simulate the sending of primary data representing said state information, so as to generate an alarm intended to indicate to the management device (2) the alarm state of said equipment (3).

11. A device as claimed in claim 10, wherein said interpreter (5) is arranged to deliver to said management device (2) alarms parameterized by values extracted from the equipment from which it has received the primary data.

12. A device as claimed in claim 10, wherein said interpreter (5) is arranged to extract said information or values from a management information base (8) of the equipment concerned.

13. A device as claimed in claim 1, wherein said primary data are received in primary formats of the SNMP type.

14. A network management device (2), comprising a processing device (1) according to claim 1.

30. Use of the processing device (1) and management device (2) as claimed in claim 1 in network technologies which have to be managed.

15. A data processing method in which, on reception of primary data transmitted by equipment (3) in a communications network and defining events in at least one primary format, there are delivered to a management device of the network (2) secondary data defining alarms representing said events, in a secondary format, wherein said generation consists of converting, by means of conversion rules, arranged in the form of “

scripts”

associated with the various primary event formats, primary data received in one of said primary formats into secondary data in said secondary format which can be interpreted by said management device (2).

16. A method as claimed in claim 15, wherein conversion is carried out into a secondary configuration file format by means of an interpreted language.

17. A device as claimed in claim 16, wherein said secondary configuration file format is a format chosen from a group comprising XML and the proprietary text formats.

18. A device as claimed in claim 16, wherein said interpreted language is chosen from a group comprising at least JavaScript, VisualBasic, TCL, Perl and Python.

19. A method as claimed in claim 15, wherein, when there are primary data associated respectively with event identifiers, at least some of said conversion rules are associated with known event identifiers.

20. A method as claimed in claim 19, wherein at least one of said conversion rules defines a default script intended for primary data associated with an unknown event identifier.

21. A method as claimed in claim 15, wherein alarm parameters are deduced from certain primary data received, so as to deliver a parameterized alarm to said management device (2).

22. A method as claimed in claim 21, in which alarms parameterized by “

hard-coded”

values are delivered to said management device (2).

23. A method as claimed in claim 21, wherein alarms parameterized by values extracted from said primary data are delivered to said management device (2).

24. A method as claimed in claim 21, wherein, when the alarm state of an item of equipment (3) in the network is unknown, there is extracted from said equipment (3) chosen information representing said alarm state, and then the sending of primary data representing said state information is simulated so as to generate an alarm intended to indicate to the management device (2) the alarm state of said equipment (3).

25. A method as claimed in claim 24, wherein there are delivered to said management device (2) alarms parameterized by values extracted from the equipment (3) from which it received primary data.

26. A method as claimed in claim 24, wherein said information or values are extracted from a management information base (8) of the equipment (3) concerned.

27. A method as claimed in claim 15, wherein said primary data are received in primary formats of the SNMP type.

28. Use of the data processing method as claimed in claim 15 in network technologies which have to be managed.

29. Use as claimed in claim 28, wherein the network technologies are chosen from a group comprising transmission networks, in particular of the WDM, SONET and SDH type, data networks, in particular of the Internet-IP and ATM, and voice networks, in particular of the conventional, mobile and NGN type.