KR20000044381A - Method for self reporting in network management system - Google Patents

Abstract

PURPOSE: A method for self-reporting in a network management system, is provided to delete a work of generating/interrupting a association, when many notifications are generated in a short time, and to prevent a case disusing notifications, not processed. CONSTITUTION: In a method for self-reporting in a network management system, an agent reports a manager autonomously in a communication system utilized the network management system using the manager and the agent, which are composed by use of a common management information protocol(CMIP). The method contains processes. The first process is, when a notification to be transmitted, is generated, but a association with the manager is not bound, to bind the association, and to transmit a notification to the manager. The second process is, when another notification is continued to be generated in a regular time, after transmitting the notification, to maintain the association, and to transmit the another notification to the manager. The third process is to intercept the association, when not generating the another notification.

Description

Voluntary Reporting Method in Network Management System

The present invention relates to a communication system in which a network management system (NMS) is implemented, and more particularly to a method for an agent to make an autonomous report to a network manager.

The systems that make up the network notify the network manager through voluntary reporting of the change of its state. Many communication systems use the Common Management Information Protocol (CMIP) recommended by the International Telecommunication Union (ITU) to configure, use, and manage the network manager 100 and the agent 102 as shown in FIG. Doing. In the case of the network manager 100 and the agent 102 using the CMIP, the agent 102 voluntarily reports the agent 102 in the destination list of the object named "EventforwardingDiscriminator". It is made to the network manager 100. In the case of CMIP, in order to transmit information, an association is a connection oriented protocol that must first bind. Accordingly, in order for the system to report the change of state to the network manager 100, the system must first establish a binding and then send a notification, which is a voluntary report, to the network manager 100.

However, the number of combinations that the network manager 100 can manage at the same time is limited. As a result, keeping all systems together is not only a waste of system resources, but also becomes practically difficult when the number of systems in the network increases.

For this reason, in the related art, as shown in FIG. 2, a spontaneous reporting procedure according to the state change of the system establishes the association between the network manager 100 and the agent 102 and immediately after the notification is sent, disconnects the association. Normally, you do not have a binding and then set the binding only if you send a notification.

However, this method has the advantage of using system resources only when needed. However, if a large number of notifications occur in a short time, it is necessary to set up join and then cut again every time. It becomes inefficient. This inefficiency causes the notification to take a long time to process, thereby accumulating notifications to be processed inside the agent 102. In the worst case, the number of notifications that can be stored by the agent 102 may be accumulated until some of the notifications that need to be discarded. In this case, for example, when an alarm is processed, a large amount of alarms are continuously generated in comparison with the processing capacity within a predetermined period.

As described above, the conventional voluntary reporting method is a problem when a large amount of notifications occur within a short time. In this case, in the conventional method, in addition to processing one notification, the setting and cutting of the coupling should be performed before and after. In this case, the processing time is long, and the joint delivery may be delayed. In addition, if this delay continues, if the number of notifications that can be stored in the agent exceeds, there is a problem that the notification may need to be discarded.

Accordingly, an object of the present invention is to provide a method for efficiently and spontaneously reporting even when a large number of notifications occur continuously within a certain period of time.

1 is a block diagram of a typical network management system implemented using a CMIP,

2 is a typical voluntary reporting procedure,

3 is a voluntary reporting procedure according to an embodiment of the present invention;

4 is a flowchart of a notification generation procedure according to an embodiment of the present invention;

5 is a flow chart of a timeout event procedure according to an embodiment of the invention.

The present invention for achieving the above object is a method for spontaneously reporting from the agent to the manager in a communication system implemented with a network management system for managing the network using the manager and agent configured using the CMIP, to the manager When a notification to be sent occurs When a binding is not set with the manager The process of establishing a connection and sending the notification to the manager, and when another notification continues to occur within a period of time after the notification is sent Sending another notification to the manager while maintaining the association.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description and the annexed drawings, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the subject matter of the present invention will be omitted.

First of all, the present invention does not break the set coupling when a large amount of notifications continuously occurs within a short time. From an agent's point of view, there is no need to set up a new association and send a notification if there is a association with the manager to send. Therefore, if notifications continue to occur for a short period of time, if the join can not be cut, the work of setting up and cutting the join is not performed, thus enabling efficient notification processing.

3 shows a voluntary reporting procedure according to an embodiment of the present invention accordingly. Conventionally, each time a notification is sent, the connection is set up and then cut again. However, if a large number of notifications occur in a short time and the agent 102 can recognize them, the notifications that occur continuously after establishing the association once when starting to send notifications that are voluntary reports, as shown in FIG. You can reduce the work outside of the notification process by keeping all the cuts until you send them.

In other words, the continuous occurrence of the notification in a short time means that another notification is continuously generated since the notification is generated. As described above, in order to recognize that the notification continuously occurs within a certain period, the present invention adds a timeout event procedure to the agent 102. In addition, if another notification continues to occur within a period of time after one notification is sent, a notification generation procedure is generated to the agent 102 to transmit the notification to the manager while maintaining the association. Add a new procedure).

4 is a flow chart of the notification generation procedure according to an embodiment of the present invention, the flow of processing when the notification occurs in the agent 102 of FIG. 3 in the steps (200) to (218) It is seen. In step 200, if the notification occurs and the notification occurs, in step 202, the destination list for the network manager 100 to which the notification is to be transmitted is obtained as in the normal case. In step 204, it is checked whether there is a combination previously set. As described above, in the prior art, the binding is set and disconnected every time a notification is sent. However, in the present invention, if another notification continues to occur within a predetermined period, the binding is maintained. It is to check if there is a previously set combination.

If there is no association in step 204, the network manager 100 requests the association. In step 206, it is checked whether the association is established. In this case, if the association fails, the corresponding notification is discarded and the process proceeds to the step 200 in step 308. In contrast, if the binding is set, in step 210, the notification information table as shown in Table 1 is generated, and then in step 212, the notification is transmitted to the network manager 100, and in step 200, Proceed.

Administrator Information Timeout value One 2 3 ··· max

Agent 102 can send notifications to different network managers simultaneously using different channels. Therefore, the notification information table consists of manager information and timeout value, which are information on each of the channels that sent the notification. The timeout value is a value that can be provisioned by an operator to check whether a notification is within a certain period when another notification occurs after one notification occurs. In addition, in Table 1, "1" through "max" correspond to the number of network managers that sent one notification.

If there is a binding in step 204, the notification information is retrieved using the binding information in step 214, and in step 216, the timeout value is initialized from the notification information table shown in Table 1 above. , That is, changed to the value provisioned by the operator. Here, the timeout value decreases every timeout event occurs in the timeout event procedure as described below. If another notification continues to occur before the timeout value reaches 0, check the elapse of a certain period from then on. To change the initial value. Next, the notification is transmitted in step 218 and the process proceeds to step 200.

FIG. 5 is a flowchart illustrating a timeout event procedure according to an embodiment of the present invention. In the agent 102 of FIG. 3, the flows processed according to timeout events generated at predetermined time intervals 300 to ( It is shown in step 310). The timeout event is caused to continue to exist within the period in which the agent 102 operates in a timer driven by the agent 102. If a timeout event occurs by waiting for a timeout event in step 300, in step 302, it is checked whether there is a notification information table as shown in Table 1 above. In this case, if there is no notification information table, if the process proceeds to step 300, the timeout value of the corresponding notification information table is decreased by one, and then it is checked in step 306 that it becomes zero. If the timeout value is not 0, the process proceeds to step 300. If the timeout value is 0, the association is disconnected in step 308, and then the corresponding notification information table is deleted in step 310.

4 and 5 will be described as follows. Agent 102 checks if there is a previously established association when a notification occurs. At this time, if there is no join, the join is set up, the notification information table is created, the administrator information and the timeout value are registered, and the notification is transmitted. If there is a join, the timeout value is initialized in the notification information table. Change it to a value and send the notification. In this state, each timeout event occurs, the notification information table is examined to reduce the timeout value by one when the manager information and the timeout value, which are channel information, are set. When the timeout event continues and the timeout value reaches 0, the corresponding truncation is disconnected. On the other hand, if another notification occurs before the timeout value becomes 0, it is transmitted to the network manager 100 through the existing channel, and the agent 102 updates the notification information table to update the timeout value. Change back to its initial value.

In this way, if the notification continues to occur before the timeout value becomes 0, the notification can be sent to the network manager 100 without disconnecting the association.

This improves the performance of the system by eliminating the task of creating and tearing joints when a large number of notifications occur in a short time. These performance improvements will prevent you from having to dispose of notifications and discard them.

As described above, the present invention improves the performance of the system by eliminating the task of creating and cutting a joint when a large number of notifications occur within a short time, and prevents the necessity of discarding the notification due to the failure to process the notification. There is an advantage to this.

Claims (2)

In a communication system implemented a network management system for managing a network using a manager and an agent configured using a CMIP, the agent voluntarily reports to the manager, When the notification to be transmitted to the manager occurs, when the association with the manager is not set, setting the association and transmitting the notification to the manager; And if another notification continues to occur within a period of time after the notification is transmitted, sending another notification to the manager while maintaining the association. The spontaneous reporting method of claim 1, further comprising: cutting the bond if the other notification does not occur within the predetermined period.