KR20020087538A - Method for supplying information of managed object in Telecommunication Management Network System - Google Patents

Abstract

PURPOSE: A method of supplying managed element information in a communication network management system is provided to implement a managed element unit in a manager area, to transform a managed element tree into a tree, and to supply information on all elements to an operator, thereby reducing load of a managing agent. CONSTITUTION: A communication network management system reads data related to equipment management from database during initialization. When the system re-implements a managed element tree structure for the read data as a tree structure in accordance with a substantial physical location, the system forms an instance ID corresponding to one network component, the first child vertex, and a sibling vertex on each vertex of the tree. When an alarm is reported from a managing agent, the system collects information on a managed element generated with the alarm and information on all managed elements connected with the managed element through the re-implemented tree structure, and supplies the collected information to an operator.

Description

Method for supplying information of managed object in Telecommunication Management Network System}

The present invention relates to a method for providing management object information in a communication network management system, and implements a management object tree according to an actual physical location of management objects, and manages it in the manager area, so that an alarm occurs when an alarm is reported from a management agent. The present invention relates to a method of providing an operator with information on all management objects in an inclusion relationship and a connection relationship with a management object in which the alarm has occurred.

In general, the concept of telecommunications management network (TMN) proposed by 'ITU-T' is "to manage the telecommunications network and services by connecting the operating system and the network components with a standard interface, and through this interface the necessary management information is mutually It refers to a logical structure that is exchanged, and is defined as an "infrastructure that systematically supports telecommunication network management." Here, the communication management network management layer can be logically divided into a business management layer (BML), a service management layer (SML), a communication network management layer (NML), an element management layer (EML), and a communication network component layer (NEL). .

Here, the network management layer (NML) to be dealt with in the present invention manages a communication network from an overall perspective irrespective of the characteristics of the communication network components, and includes functions such as communication network configuration, communication network performance analysis and statistics. The communication management network information structure is a structure for exchanging management information about communication network resources expressed abstractly through information modeling based on an object-oriented approach, which will be described with reference to the drawings. It has a structure as shown.

The communication management network information structure has a form of a manager (1) and a management agent (2) as shown in the figure, and the basic function of the manager (1) is to manage network resources by processing standardized management information provided by a management interface. Manage. In addition, the basic role of the management agent 2 is a function of notifying the manager 1 through the management interface 3 or processing a request of the manager 1 of an information model in which communication network resources are standardized as management objects.

At this time, the interface between the manager (1) and the management agent (2) is made through a message communication function (Messenger Coffe Com).

As such, information transmitted between the manager 1 and the management agent 2 includes information on facility resource management of the network managed by the manager 1, which is a physical resource of a network element such as an exchanger, For example, they can be divided into functions that monitor or control the status of nodes, boards, ports, and elements of the rack and shelf units of the node. In order to monitor the network status, event reports such as management object creation, deletion, and change should be provided in real time, and control commands such as configuration, removal, and status change of equipment resources are provided through a standard interface.

The main management information in managing facility resources is an alarm status indicating the occurrence and extent of resource failure, and an operational status indicating whether a current operation of the part where the failure occurs is related to this value. ) And an administrative state indicating service providing and stopping according to an alarm. In general, the alarm status is transmitted from the management agent (2) to the administrator in the event reporting form when a failure occurs in the network component, and the management status is a part of the network as required by the administrator (1) (or operator) to see the alarm status. Information on commands input to the management agent (2) to suspend or resume the service.

As described above, for real-time monitoring of network resources in a communication network, a status change of a resource such as an alarm should be reported immediately upon occurrence of an event, and appropriately changed state values of other management objects related to the change of state of a specific management object.

For example, if a board or port failure occurs due to a device problem on a node containing multiple boards and ports, it will be reported by the administrator to the administrator of the board and port, in which case the failed board will fail. Nodes, racks, and shelves that physically contain ports and ports remain in a normal state unless they receive special alarm reports from the management agent.

In addition, the change of the management status of the node by the administrator should be reported with the change of the management status of all boards, ports, etc. included in the node. In other words, if there are n components such as racks, shelves, boards, and ports in a node, the status change report of n + 1 (1 represents the node itself), including the node itself, should be sent to the administrator. This means that if the management state of the node is changed to locked from the administrator's side, the components included in the node are also changed to the locked state.

As another example, in monitoring the status of a link, when an alarm occurs at a port at both ends of the link, it may be helpful to identify the network status when the alarm is switched to the link and provided to the administrator.

As such, the current state of the management object in the communication network reflects some or all of the states of other management objects. That is, the state of a trunk connected between two exchange periods is a value reflecting the state of ports of each exchange, and the state of the node is a combination of various component states included in the node.

However, in the current communication management network information structure, in the state change for the management object in the containment and connection relationship, after the state propagation is performed by the management agent, it is necessary to delay the processing time and the management network. This is not possible due to congestion of management information.

Therefore, there is a need for a technology that allows an administrator to monitor all information according to the inclusion and connection relationships as described above.

The present invention, in view of the conventional problems and requirements as described above, by reducing the load of the management agent through the management object means maintained on the manager side, and effectively handles the continuous state change to monitor the network status in real time The object of this invention is to implement a method of providing management object information in a communication network management system.

1 is a diagram showing a general communication management network information structure.

2 is a view showing a general structure management object management tree structure applied to the present invention.

3 is a view showing a modified management object binary tree structure through the management object server according to the present invention.

4 is a configuration diagram showing a use state of the management object server according to the present invention.

<Description of Symbols for Major Parts of Drawings>

15: Database 16: Network Management Agent

17: device management agent 18: management object server

19: user graphic interface unit 20: command processing unit

In order to achieve the above object, in the method for providing management object information using a management object tree associated with the facility management through the manager and the management agent in the communication network management system,

A first step of reading facility management-related data from a database in a communication network management system when the communication network management system is initialized;

Re-implement the managed object tree structure for the read data into a tree structure according to the actual physical location of the managed objects,

At each vertex of the tree, an instance ID corresponding to one network component, a first child vertex that points to the first child vertex for a pointer to another of the vertices, and a sibling vertex or parent of the same order A second process of respectively providing sibling vertices pointing to the vertices;

After re-implementing the tree, if an alarm is reported from a management agent, the re-implementation of information on the management object that generated the alarm, and information on all management objects that have an inclusion relationship and a connection relationship with the management object that generated the alarm Comprising a third process of collecting through the tree structure provided to the operator;

Each process is characterized in that performed in the manager area.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 2 is a diagram showing a tree management-related management object tree structure applied to the present invention. The management object in the facility management includes a network object (NetworkR1) (5), a network object (6), and a management element object ( (ManagedElementR1) (7), logical node network object (8), device object (equipmentR1) (9), device holder object (equipmentHolder) (10), circuit pack object (circuitPack) (11) ), A port object (12), a link object (13), and an access profile object (14).

In the above, the managed element object (managedElementR1) (7) represents the exchanger, the device object (equipmentR1) (i) represents the entire equipment of the exchanger, and the device holder object (equipmentHolder) (10) represents the rack, self, Slots and the like.

A circuitPack object (11) represents a board, a port object (12) has a function of pointing to a related link or a subscriber identification number in the case of a subscriber interface, and resource status such as bandwidth of a port. And an access profile object (14) having information for identifying the interface type (subscriber interface, inter-device interface, and communication network interface).

The link object 13 represents the trunk of the exchange period.

In addition, the use of the above management objects may be different according to the exchange, so the device (equipmentR1) may not be used, and in the case of a small exchange, there may be no distinction between a rack, a shelf, and a slot.

FIG. 3 is a diagram illustrating a tree management-related management object tree structure modified by a management object means (hereinafter referred to as a management object server) according to the present invention, which is an actual physical location of the management object tree structure shown in FIG. Restructured according to the structure.

This is because the management object tree as shown in FIG. 2 represents a hierarchical structure of the management objects and is reconstructed because it does not necessarily correspond to a physical location. Thus, a tree representing a physical relationship is required for state propagation.

The structure is as follows.

Full network vertex (ｓｕｂｎｅｔｗｏｒｋ).

A network vertex that is a child vertex exists under the entire network vertex, and nodes 1 (node 1) to node n vertices in a sibling vertex relationship with the network vertex are located.

Subsequently, a child vertex, which is a child vertex, exists under the network vertex, and device vertices having sibling relations with the network vertex are located.

Subsequently, there are logical node vertices 1 at a network vertex, which are child vertices, and link vertices at sibling vertices with the logical node vertices are located.

Furthermore, a rack vertex Ralcc1, which is a child vertex, exists below the device vertex, and sibling vertices of the rack vertex are located;

Self vertices (ｓｈｅｌｆ１), which are child vertices, exist below the rack vertices, and sibling vertices of the self vertices are located;

A slot vertex, which is a child vertex, exists below the self vertex, and sibling vertices of the slot vertex are located;

A board vertex (ｂ ｂ ａ ａ 인 인) which is a child vertex under the slot vertex exists, and sibling vertices of the board vertex are located;

Finally, a port vertex, a child vertex, is a child vertex under the board vertex, and sibling vertices of the port vertex are located.

The reasons for reconfiguring the managed object tree with the above structure are as follows.

The management object server implemented in the present invention reads data related to network equipment resources from a database (DB) or a management agent at the initial stage of the system, and continuously resides in the memory until the system is terminated.

Since a large amount of memory is required in a situation where a large amount of network resources are to be managed, the present invention places more weight on memory saving in a trade-off relationship between processing time and memory requirements. The processing time is to implement an efficient algorithm to satisfy the two factors of the trade-off of processing time and memory requirements.

Meanwhile, the data structure reconstructed to implement the management object server described above will be described in more detail. The reconstructed management object tree is a modified binary tree, and a vertex on the tree is a network resource. It is a class that represents and has a field for pointers to child vertices and sibling vertices, an instance ID, and managed object attribute fields.

In order to minimize memory usage, the thread to the parent is not defined as a pointer, but rather as a single byte flag to determine sibling or parent.

In this case, facility resource types are classified as member data of classes, and heterogeneous managed object instances are placed together in the same degree of binary tree to maintain a simple binary tree.

In addition, the meaning of 'a' shown in FIG. 2 indicates that there is a situation in which there is no corresponding management object on the management object tree, and various types of management objects according to the present invention can be extended. If the network component does not exist, the server creates a virtual vertex with an instance ID of negative number, and makes the component exist virtually to connect the tree.

Not only is this more efficient in constructing the tree, but it can also deal with processing delays that result from minimal memory usage.

In addition, the meaning of 'ｂ' shown in FIG. 2 indicates that the port or subport existed under the manegedElementR1 in the management object tree, but the management object server shortens the processing time by actually building it according to the physical inclusion relationship.

For example, the alarm of the port should lead to the alarm of the board. In this structure, the board does not find the board from the database information as in the structure shown in FIG. 2, and the parent vertex of the port becomes the board including the port. The subport also ensures that the parent vertex is the port that contains this subport.

Each vertex of the managed object server according to the present invention is defined by implementing one class, and has the following member data.

Identifier (long: 4 bytes): an instance identifier.

Flag (character: 1byte): Determines whether the sibling point points to a sibling or a parent.

Sibling point (Pointer: 4 bytes): Pointer to the sibling or parent vertex.

First child point (Pointer: 4 bytes): Pointer to the first child vertex.

-Administrative state (character: 1byte): Combination of own administrative state value and propagated state value.

-Alarm Status (character: 1byte): It shows the alarm status that combines the alarm status values of the self and sub management objects of the management object.

-Self Alarm Status (character: 1byte): It indicates the own alarm status of the management object.

Operational State (character: 1byte): Indicates the operational state of the resource associated with the managed object.

-Self Administrative (character: 1byte): Shows the administrative status that combines the administrative status values of self and upper management of the relevant administrative object.

-Facility Type (character: 1 byte): Indicates the type of equipment resource.

Access profile identifier (long: 4 bytes): Indicates the Id of the traffic profile instance of the port and the subport, and if it is negative, the port and the subport are inactive.

On the other hand, the continuous state change in the tree structure as described above can occur mostly in the alarm state, the management state and the operation state, and data for this is defined and whether the sibling point is sibling vertex or sibling vertex is defined. The flag to indicate is defined.

In addition, self administrative and self alarms among member data are used to distinguish their actual state from those propagated from upper and lower facility resources.

When a state change occurs, the management object server according to the present invention mainly includes a member function of a data structure structure and a function for processing a state change request. The main functions are as follows:

'AddChild' adds child vertices.

'DeleteChild' deletes all child vertices.

'ChangeState': changes state values

'upPropagation': propagates the reported state value to the upper vertex.

'downPropagation': propagates the reported state value to the lower vertex.

'getAllAncesterIdfunction': Represents the ID of the parent vertex.

'getDegree': Depth of the vertex in the tree.

The state of the management object server having the member function as described above is configured during system initialization and then changed by event reporting. In order to always maintain the state of the latest network resource, the type of event report and the type of equipment resource to be reported are as follows. It should be handled differently according to.

The summary of the process according to the general event report type and equipment resource type is as follows.

'ManagedElementR1' (creation): Creates a new node and reads the resources of the node from the database to form an object server.

-'circuitPack' (create): The new board has been added and the object server is configured after reading the port information included in the board from the database.

'atmLinkKT' (created): A new link has been added that reads the state from the database and configures the object server.

'atmAccessProfileKT' (Generate): Sets the access profile ID (access-ProfileId) created when the ATM port is enabled.

-'FrAccessProfileKT' (created): FR port is enabled and set access profile ID (accessProfileId).

-'subPortKT' (Create): A new subport has been added under the FR port. After reading the status value from the database, create a subport and place it under the corresponding port.

'ManagedElementR1' (delete): The node has been deleted and deletes the vertex that represents the node and any child vertices it contains.

'circuitPack' (delete): deletes the vertex and port vertex representing the board.

'AtmLinkKT' (Delete): Deletes the vertex that represents the link as the link is deleted.

-'AtmAccessProfileKT' (Deleted): The port is inactive. Set the access profile ID (accessProfileId) of the corresponding ATM port to a negative number.

-'FrAccessProfileKT' (Deleted): The port is inactive. Set the access profile ID (accessProfileId) of the corresponding FR port to a negative number.

-'subPortKT' (Deleted): A new subport has been added under the FR port. After reading the status value from the database, create a subport and place it under the corresponding port.

-'ManagedElementR1' (Change Status): In the case of changing the managed status of a node, it changes the managed status of the node and changes the managed status of all equipment resources including it.

-'CircuitPack' (Change Status): In the case of changing the management status of the board, change the management status of the vertex that represents the board and the containing port vertices.

-'PortKT' (Change Status): To change the management status of a port, change the management status of the port vertex and the child vertex.

'ManagedElementR1' (report alarm): An alarm has occurred in the node, which changes the alarm state of the node's vertex.

-'CircuitPack' (alarm report): An alarm has occurred on the board. It changes the alarm state of the board vertex and the parent vertex

'PortKT' (Alarm Report): An alarm has occurred on the port. It changes the alarm state of the port and parent vertices.

In the case of the equipment resource that does not appear in the event report above, there is no event report for the corresponding equipment resource. For example, in case of object creation, the port (portKT) does not appear. Because it reads. Summarizing the above, when creating a managed object, most new vertices are placed, and deleting a managed object deletes the vertex. In addition, the change of management status causes down propagation from the upper vertex to the lower vertex, while the change of alarm state causes the up propagation from the lower vertex to the upper vertex.

Referring to the drawings the state of use of the management object server having the characteristics described above with reference to the drawings as shown in Figure 4, the database 15 for storing network configuration and connection information;

When the event information is transmitted from the plurality of device management agents 17, the network management agent collects the event information, stores it in the database 15, and simultaneously transmits it to the management object server 18. The network management agent transmits the event information to the management object server 18. NB Ag16; 16;

Read only the data related to the network equipment resources from the database 15 to reconstruct the management object tree into a tree according to the actual physical location, and then uplinked from the network management agent 16 based on the structure of the tree. A management object server 18 which prepares information on an alarm report in consideration of an inclusion relation and a connection relation with an object on which an alarm is generated;

A user graphic interface unit (19) for displaying the alarm information generated by the management object server 18 to an administrator;

When the processing command according to the information displayed through the user graphic interface unit 19 is input from the administrator is provided with a command processing unit 20 for transmitting the processing command to the network management agent (16).

At this time, the management object server 18, the user graphic interface 19 and the command processing unit 20 resides in the manager area, the database 15 and the management object compared to FIG. The server 18, the user graphic interface 19, and the command processor 20 may be divided into an administrator 1, and the network management agent 16 and the device management agent 17 may be managed by the management agent 2. Can be distinguished.

In the above configuration, when the system is initialized, the management object server 18 reads network equipment resource data from the database 15 and reconstructs the tree structure according to the physical location, and from the network management agent 16. The current state of each managed object is maintained by event notifications.

This latest status provision is easy to grasp the instantaneous network status by the administrator (not shown), and is used as useful data in the user graphic interface unit 19 and the command processing unit 20.

And after changing the state corresponding to the event for the management object corresponding to the event report for the event report generated from the device management agent 17 in the lower network management agent 16, and stores in the database 15, The content is reported to the management object server 18.

When the above information is reported, the management object server 18 collects information on all objects having an event-related object and an inclusion relationship and a connection relationship according to the reconstructed tree structure and provides the information to the operator.

Therefore, the network management agent 16, which may have a large load while actually managing network resources, can significantly reduce the load on state propagation as compared to the prior art, and operate smoothly throughout the system.

As described in detail above, the present invention implements the management object means in the manager area, transforms the management object tree into a tree according to the actual physical position, and if there is an object that generates an alarm, includes the relationship and connection with the object. By providing the operator with information (status propagation) about all the objects in the relationship, it is possible to reduce the load of the management agent and to effectively monitor the status of the network in real time by effectively processing the continuous state changes. In the state propagation, the management state goes downward and the alarm state goes upward, so that the state propagation can be efficiently carried out in managing facility resources.

In addition, preferred embodiments of the present invention are disclosed for the purpose of illustration, those skilled in the art will be able to make various modifications, changes, additions, etc. within the spirit and scope of the present invention, such modifications and modifications belong to the following claims You will have to look.

Claims (5)

In a method for providing management object information using a management object tree related to facility management through a manager and a management agent in a communication network management system, A first step of reading facility management-related data from a database in a communication network management system when the communication network management system is initialized; Re-implement the managed object tree structure for the read data into a tree structure according to the actual physical location of the managed objects, At each vertex of the tree, an instance ID corresponding to one network component, a first child vertex that points to the first child vertex for a pointer to another of the vertices, and a sibling vertex or parent of the same order A second process of respectively providing sibling vertices pointing to the vertices; After re-implementing the tree, if an alarm is reported from a management agent, the re-implementation of information on the management object that generated the alarm, and information on all management objects that have an inclusion relationship and a connection relationship with the management object that generated the alarm Comprising a third process of collecting through the tree structure provided to the operator; Method for providing management object information in a communication network management system, characterized in that each process is performed in the manager area. The method of claim 1, The sibling vertex in the second process includes a flag indicating a sibling vertex or a parent vertex, the management object information providing method in a communication network management system. The method of claim 1, In the second process, each of the vertices further includes a data indicating the alarm state of the management object itself and a management state data value combining the management state values of the management object and the management object. Method for providing management object information in a communication network management system characterized in that. The method of claim 1, When reimplementing the tree structure in the second process, if a network component does not exist physically, a virtual vertex having a negative instance ID corresponding to the network component is created so that the component exists virtually so as to connect the tree. Method for providing management object information in a communication network management system, characterized in that. The method of claim 1, When the alarm occurs in the third process, the management agent performs only the state change corresponding to the alarm for the management object in which the alarm is generated, and stores it in the database and simultaneously reports the alarm to the manager. How to provide managed object information in the management system.