Process and device for configurable management of the persistency of data in the equipment of a communication network

• US 20050073959A1
• Filed: 07/29/2004
• Published: 04/07/2005
• Est. Priority Date: 08/01/2003
• Status: Abandoned Application

• Current Assignee: Alcatel SA (Nokia Corporation)
• Original Assignee: Alcatel SA (Nokia Corporation)
• Inventors: Villeret, Pascal, Chevanne, Michel, Bergeot, Patrick, Lapraye, Bertrand
• Application Number:
  US10/901,190
• Publication Number:
  US 20050073959A1
• Time in Patent Office: Days
• US Class Current: 370/241
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/0226 Mapping or translating multiple network management protocols

Abstract

A device (D) is dedicated to the management of data persistency within an equipment management system (EMS) of a communication network that includes a large variety of network equipment (NE-i), where the equipment management system (EMS) is coupled to the equipment and to a network management system (NMS), and that includes a management information tree (MIT), coupled to the device (D), representing links between equipment (NE-i), and that includes primary data. This management device (D) includes configurable conversion resources (MTR) that are responsible for converting at least some of the primary data of the management information tree (MIT) into persistent data in accordance with persistency models which are each associated with different storage media (FP, BD), with a view to their storage in the storage medium which is associated with the persistency model that has been used for their conversion.

Claims

1. A device (D) for the management of data persistency in an equipment management system (EMS) of a communication network (N) that includes a large variety of network equipment (NE-i), where the said equipment management system (EMS) is coupled to the said equipment (NE-i) and to a network management system (NMS), and includes a management information tree (MIT) which is coupled to the said device (D), representing links between the equipment (NE-i), and which includes primary data, characterized in that it includes configurable conversion resources (MTR) which are arranged so as to convert at least some of the said primary data into persistent data in accordance with persistency models, each of which is associated with different storage media (FP, BD), with a view to their storage in the storage medium associated with the persistency model that has been used for their conversion.

2. A device in accordance with claim 1, characterized in that the said conversion resources (MTR) are arranged so as to determine the association of the said primary data with selected persistency sets associated with the different persistency models, and then to convert these primary data into persistent data in accordance with the persistency model associated with the persistency set to which they belong.

3. A device in accordance with claim 1, characterized in that it is suitable to be controlled/monitored by equipment description resources (MEM) of the said equipment management system (EMS).

4. A device in accordance with claim 1, characterized in that the said conversion resources (MTR) are arranged so as to convert the said primary data into persistent data by the generation of data tables in the format of the corresponding storage medium (FP, BD).

5. A device in accordance with claim 1, characterized in that the said conversion resources (MTR) are arranged, after performing a conversion of primary data into persistent data, so as to generate a storage interface that is suitable for the storage of the said persistent data in the corresponding storage medium (FP, BD).

6. A device in accordance with claim 5, characterized in that the said storage interface is of the JDBC type.

7. A device in accordance with claim 1, characterized in that the said conversion resources (MTR) are arranged so as to deliver persistent data that are matched to storage media selected from a group that includes at least flat files (FP) and databases (BD).

8. A device in accordance with claim 7, characterized in that at least one of the databases (BD) is of the relational type.

9. A device in accordance with claim 1, characterized in that the said primary data describes objects, and in that the said persistency sets are object classes.

10. A device in accordance with claim 1, characterized in that the said conversion resources (MTR) include at least one configuration file and at least one program code file.

11. A device in accordance with claim 10, characterized in that each configuration file is of the XML type.

12. A device in accordance with claim 10, characterized in that the said program codes are in the Java language.

13. An equipment management system (EMS) for a communication network (N) that includes a large variety of network equipment (NE-i), and suitable to be coupled to the said equipment (NE-i) and to a network management system (NMS), and that includes a management information tree (MIT) representing links between equipment, and that includes primary data, characterized in that it includes a management device (D) in accordance with one of the preceding claims, coupled to the said management information tree (MIT) and to equipment description resources (MEM).

14. A management server (MS) in a network management system (NMS), characterized in that it includes an equipment management system (EMS) in accordance with claim 13.

15. Network equipment (NE-i), characterized in that it includes an equipment management system (EMS) in accordance with claim 13.

24. Use of the management device (D), management server (MS), network equipment (NE-i), equipment management system (EMS) and management process in accordance with one of the preceding claims in the network technologies which have to be managed.

25. Use in accordance with claim 24, characterized in that the said network technologies are selected from a group that includes transmission networks, in particular of the WDM, SONET and SDH type, data networks, in particular of the Internet-IP and ATM type, and speech networks, in particular of the conventional, mobile and NGN type.

16. A process for the management of data persistency for a communication network (N) that includes a large variety of network equipment (NE-ij), and a network management system (NMS) coupled to an equipment management system (EMS) coupled to the said equipment (NE-i), representing links between equipment, and that includes a management information tree (MIT) that includes primary data, characterized in that it consists of converting at least some of the said primary data into persistent data in accordance with persistency models, each of which is associated with different storage media (FP, BD), with a view to their storage in the storage medium associated with the persistency model that has been used for their conversion.

17. A process in accordance with claim 16, characterized in that the association of the said primary data to selected persistency sets associated with the different persistency models is determined, and then these primary data are converted into persistent data in accordance with the persistency model associated with the persistency set to which they belong.

18. A process in accordance with claim 16, characterized in that the said primary data are converted into persistent data by the generation of data tables in the format of the corresponding storage medium.

19. A process in accordance with claim 16, characterized in that after performing a conversion of primary data into persistent data, a storage interface is generated that is suitable for the storage of the said persistent data in the corresponding storage medium (FP, BD).

20. A process in accordance with claim 19, characterized in that a storage interface of the JDBC type is generated.

21. A process in accordance with claim 16, characterized in that persistent data is delivered which is matched to storage media selected from a group that includes at least flat files (FP) and databases (BD).

22. A process in accordance with claim 21, characterized in that at least one of the databases (BD) is of the relational type.

23. A process in accordance with claim 16, characterized in that the said primary data describes objects, and in that the said persistency sets are object classes.