JP2003259003A - Operation apparatus and congestion control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an operation apparatus and a congestion control method which can control or prevent the congestion and can maintain a network element (abbreviated as [NE] hereafter) consistently by promptly judging a processing delay due to concentration of autonomous messages from the NE and the like and by preceding an important autonomous message and an important process in the maintenance. <P>SOLUTION: A reception time is registered in a congestion control information table 23 when the autonomous message in a NE intensive server 1 is received. A registration time when the autonomous message is registered in a journal data base is also registered. A congestion monitoring process 24 acquires a process time of the autonomous message based on the reception time and the data base registration time. When the process time is judged as exceeding a threshold value, the journal data base registration process is skipped. The congestion due to the concentration of the autonomous messages and the like can be avoided thereby. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an operation device and a congestion control method, and more particularly to a network element (hereinafter referred to as "NE") such as an exchange or a transmission wireless device.
Information (hereinafter referred to as "autonomous message")
And a description) are displayed on the maintenance terminal, and an operation device for controlling the occurrence of congestion, and a congestion control method.

[0002]

2. Description of the Related Art FIG. 5 shows a conventional NE aggregation server 1
The outline of the process from receiving the autonomous message from the NE 3 and displaying it on the maintenance terminal is shown. As shown in the figure, one NE aggregation server 1 receives an autonomous message from a plurality of NEs 3. Therefore, when viewed from the NE aggregation server 1, a plurality of autonomous messages are notified from a plurality of NEs 3 at the same time.

The current type of autonomous message is a message of a level that is extremely urgent for a maintenance person and requires prompt action (hereinafter, "most urgent message").
Message), which is highly urgent and requires the implementation of primary measures such as primary isolation (hereinafter referred to as “emergency message”), and messages which are not urgent and require real-time measures (hereinafter "Error message"), and from the viewpoint of preventive maintenance,
It is classified into messages at levels not required for real-time monitoring (hereinafter referred to as "normal messages").

Each time the NE aggregation server 1 receives an autonomous message from the NE 3, the NE aggregation server 1 executes the following processes (1) to (4) and displays them on the autonomous message display screen of the maintenance terminal 4. (1) Each NE in the NE interface process 11
3 receives an autonomous message from. (2) The NE interface process 11 receiving this autonomous message receives the autonomous message receiving process 12 in order to store the autonomous message in the database.
To the autonomous message. Passing of autonomous messages between these processes is performed via the message queue MQ. Further, the maintenance terminal communication process 14 is notified of the reception of the autonomous message for display on the maintenance terminal 4. (3) The autonomous message receiving process 12 that has inherited the autonomous message passes the autonomous message to the journal database history registration process 13. Journal database history registration process 13 that received an autonomous message
Registers an autonomous message in the journal database 15 and performs journal database history registration. (4) The maintenance terminal communication process 14 transmits the information necessary for real-time notification to the maintenance person by the autonomous message transmission process to the corresponding maintenance terminal 4.

The NE aggregation server 1 is in a congestion state when a large number of autonomous messages are concentrated. The congestion of the NE aggregation server 1 has the following two modes depending on the difference in the communication procedure of the autonomous message with the NE 3. First, congestion of the NE aggregation server 1 when an autonomous message is exchanged between the NE aggregation server 1 and the NE 3 regardless of the state of the NE aggregation server 1 will be described.

At this time, if a large number of autonomous messages that exceed the normal processing capacity are concentrated in the NE aggregation server 1, the above-mentioned (3) database history registration processing in the NE aggregation server, etc. Causes processing delay. For this reason, autonomous messages that cannot be processed in real time are accumulated in the memory of the local system, and the maintenance terminal 4
Is displayed with a delay on the autonomous message display screen of.

Furthermore, if the number of autonomous messages due to processing delay exceeds the amount of memory that can be stored, memory congestion will occur. As a result, for the autonomous messages notified from the NE3 thereafter, all the autonomous messages from all the NE3 are sequentially discarded. At this time, the autonomous message from the NE that is centrally generating a large amount of autonomous messages and the NE that is generating only a normal amount of autonomous messages.
Discriminates autonomous messages from the above and discards them uniformly.
Also, the contents of the autonomous message are not distinguished for each level, and the autonomous messages of all levels are uniformly discarded.

With respect to the autonomous message discarded by the NE aggregation server 1, the maintenance person cannot be notified. Therefore, when the NE aggregation server 1 falls into the memory congestion state, only the alarm indicating the contents of the memory congestion is notified to the maintenance person. However, only by confirming this memory congestion warning, the maintenance person can identify the faulty NE that is sending the autonomous message in a concentrated manner and the contents of the autonomous message.
It is not possible to obtain the information necessary for calming memory congestion, such as the amount of autonomous messages and the processing delay time of autonomous messages. Therefore, the maintenance person needs to investigate the autonomous message display screen and the autonomous message log in order to obtain the information. Then, based on the information, after identifying the faulty NE, by issuing a command to the NE to specify a specific autonomous message notified in large numbers from the NE and suppress the generation of the autonomous message, memory congestion Calm down.

FIG. 6 shows the regulation contents (autonomous message uniform discard) for each autonomous message level in the NE aggregation server. As shown in the figure, at the “time of memory congestion”, the “most urgent”, “emergency”, “urgent”, and “emergency” sent from the “NE that intensively sends autonomous messages” and the other “normal NEs” For all levels of "Error" and "Normal" autonomous messages, "Maintenance terminal display" becomes "Not possible", "Database accumulation" is not performed, and "Discard"
To be done.

Next, O between the NE aggregation server and the NE
MAP (Operations and Mainte)
The congestion of the NE aggregation server 1 in the case where the communication flow is controlled by using the Nance Application Part will be described. OMA shown in FIG.
P (Operations and Maintena
communication flow using the No. Application Application Part) is performed by the following procedure. Step S
In 601, the autonomous message 2 generated on the NE 3 side is notified from the AP (Application Part) 52 to the OMAP layer 51. In step S602, the OMAP layer 51 on the NE3 side that has received the notification of the autonomous message 2 is the OMAP layer 5 on the NE aggregation server 1 side.
A data write request signal is sent to 4. In step S603, the notification confirmation from the OMAP layer 54 on the NE aggregation server 1 side to the AP 53 is performed. Step S
At 604, the NE aggregation server 1 performs step S6.
The autonomous message transmitted by the procedure from 01 to S603 is processed. This process is a process corresponding to the above (1) to (4). In step S605, when the process of step S604 ends,
A reception completion notification is sent to the MAP layer 54. Step S6
In 06, the OMAP layer 54 on the NE aggregation server 1 side
The data write acknowledgment signal from the OMAP layer 5 on the NE3 side
Returned to 1. In this situation, when the communication of one autonomous message and the processing in the NE aggregation server are completed by the reception of the data write acknowledgment signal, the NE 3 can transmit the next autonomous message 2 (2).

In this method, when the NE aggregation server 1 side is congested, the NE 3 side does not notify the NE 3 that it can transmit the next autonomous message. Therefore, the NE 3 side cannot transmit the next autonomous message. The NE3 side accumulates autonomous messages. That is, the NE3, in which a large amount of autonomous messages are concentrated, tries to send autonomous messages until the failure is recovered, but the NE3 is accumulated in the NE3.
Therefore, as viewed from the NE aggregation server 1 side, autonomous messages are not notified in real time until the congestion state is resolved, and important autonomous messages are also uniformly delayed and notified.

If the NE storage capacity is exceeded, the NE is discarded without being sent to the NE aggregation server 1. FIG. 8 shows the regulation content (flow control using OMAP) for each autonomous message level in the NE aggregation server 1. As shown in the figure,
In "during server congestion", all of the "most urgent", "emergency", "error", and "normal" sent from "NE that intensively sends autonomous messages" and other "normal NEs" Level autonomous message is "Maintenance terminal display"
Is "delayed" or "impossible", and "database accumulation" is also "delayed" or "discarded" without being accumulated.

[0013]

As described above, the NE aggregation server is in a congestion state due to concentration of autonomous messages and the like, and the conventional autonomous message uniform discarding method at the time of congestion of the NE aggregation server has the following problems. I can point out. Due to the processing delay, all autonomous messages are displayed with a delay, so the NE failure status is displayed in real time.
In addition, it becomes impossible to grasp accurately, and recovery from NE failure is prolonged. As a result, the autonomous messages from the failed NE continue to be transmitted in a concentrated manner, which also causes memory congestion in the NE aggregation server. Further, when the memory congestion occurs, the received autonomous message is uniformly discarded without being processed, and it becomes impossible to monitor all NEs.

Further, since the autonomous messages of the NEs other than the NEs that are centrally transmitting the autonomous messages are also uniformly discarded, the failure of the NEs other than the NEs that are centrally transmitting cannot be detected. In addition, even for NEs that are transmitted in a concentrated manner, it is not possible to discard autonomous messages for each level, so a new failure cannot be detected.

For the maintainer, since the information at the time of congestion of the NE aggregation server is only the memory congestion information, the cause search and the calming after the memory congestion of the NE aggregation server are delayed. Further, in the case of performing flow control using OMAP between the NE aggregation server and the NE of the related art, the following problems can be pointed out. In this case, all the autonomous messages of the faulty NE are not notified for a certain period of time or are not notified for a long time, so that the state of the faulty NE cannot be grasped accurately in real time.

Therefore, the NE of the prior art common to the flow control using the autonomous message uniform discard method and OMAP is used.
Regarding the problems of autonomous message processing in the aggregation server, there are the following problems. First, the processing delay of the NE aggregation server is immediately determined, and the delay of the autonomous message until it is displayed on the maintenance terminal is set to a short time.
It is necessary to be able to detect the above-mentioned failure early and to grasp the failure state in real time and accurately.

Further, in order to calm congestion or prevent congestion, it is necessary to be able to identify the NEs that are centrally transmitting autonomous messages and to grasp the amount of autonomous messages. Furthermore, the concentration of autonomous messages from a particular NE
NEs other than NEs that centrally send autonomous messages
Should not affect the autonomous message monitoring of.

In view of the above problems, an object of the present invention is to quickly judge a processing delay due to the concentration of autonomous messages, and to suppress or prevent congestion by giving priority to important autonomous messages and important processing in maintenance. The present invention is to provide an operation device for stably maintaining an NE and a congestion control method.

[0019]

An operation device according to claim 1 of the present invention is an operation device for receiving an autonomous message from at least one or more network elements and performing a process corresponding to the reception of the autonomous message. An acquisition unit that acquires a processing time required to process an autonomous message received from each of the network elements; and, if the processing time acquired by the acquisition unit exceeds a predetermined threshold value, the processing time by the processing that exceeds the threshold value is set. Control means for controlling so as to shorten,
It is characterized by having.

As described above, the processing delay can be directly detected by setting the threshold value based on the time required for processing the autonomous message. Therefore, the detection can be performed quickly and surely. Further, since the process that causes the process delay can be specified, it is possible to control only the process that causes the process delay. The operation device according to claim 2 of the present invention is the operation device according to claim 1, characterized in that the control means controls to perform maintenance processing corresponding to the autonomous message without performing processing exceeding the threshold value. .

As described above, by not performing the specific processing only without restricting the entire reception of the autonomous message, it is possible to guarantee the important minimum processing. As a result, it is possible to avoid a processing delay due to a long processing time. At the same time, it is possible to avoid deterioration in equipment monitoring, identify factors such as processing delays in real time, and reduce processing delays and congestion early.

According to a third aspect of the present invention, in the operating device according to the first aspect, the control means controls so as to disconnect the connection with the network element which transmits the autonomous message requiring the processing time exceeding the threshold value. Is characterized by. As a result, a faulty NE or the like that centrally transmits autonomous messages is separated, and other Ns due to congestion are separated.
It is possible to prevent deterioration of equipment monitoring such as E.

According to a fourth aspect of the present invention, in the operating device according to any one of the first to third aspects, the control means performs control according to a level relating to the urgency of the received autonomous message. And By performing control according to the level related to the urgency of autonomous messages, it is possible to preferentially process autonomous messages with high urgency and avoid the effects of processing delay and congestion, and autonomous messages with low urgency. With regard to the above, it is possible to calm down the processing delay by making it a control target.

According to a fifth aspect of the present invention, in the operating apparatus according to any one of the first to fourth aspects, the control means relates to a degree of congestion control based on a difference between the processing time and the predetermined threshold value. It is characterized in that the control level is judged and a predetermined control is performed according to the control level.

In this way, by adjusting the degree of congestion control according to the state of congestion, even when congestion control is performed, the processing of autonomous messages in the operation device such as real-time notification and database registration processing is maximized. It can be done. The operation device according to claim 6 of the present invention is the operation device according to any one of claims 1 to 5, wherein the acquisition unit sets a difference between a reception time of the autonomous message and a time when a process of acquiring the processing time is completed. It is characterized in that the processing time is acquired based on

By obtaining the processing time based on the difference between the reception time and the processing time, the processing delay time in the operation device can be known quickly and easily. A congestion control method according to claim 7 of the present invention is a congestion control method for an operation device which receives an autonomous message from at least one or more network elements and performs a process corresponding to the reception of the autonomous message, wherein the network element An acquisition step for acquiring the processing time required for processing the autonomous message received from each, and when the processing time acquired by the acquisition step exceeds a predetermined threshold, to shorten the processing time by the processing exceeding the threshold. And a control step for controlling.

A congestion control method according to claim 8 of the present invention comprises:
In claim 7, in the control step, control is performed so that maintenance processing corresponding to the autonomous message is performed without performing processing that exceeds the threshold value. The congestion control method according to claim 9 of the present invention is the method of claim 7
In the control step, control is performed so as to disconnect the connection with the network element that transmits the autonomous message that requires a processing time exceeding the threshold value.

A congestion control method according to a tenth aspect of the present invention is the congestion control method according to any one of the seventh to ninth aspects, wherein in the control step, control is performed according to a level relating to the urgency of the received autonomous message. Is characterized by. The congestion control method according to claim 11 of the present invention is the congestion control method according to any one of claims 7 to 10, wherein in the control step, a control regarding a degree of congestion control is performed based on a difference between the processing time and the predetermined threshold value. It is characterized in that the level is judged and a predetermined control is performed according to the control level.

A congestion control method according to a twelfth aspect of the present invention is the congestion control method according to any one of the seventh to eleventh aspects, wherein in the obtaining step, a process of obtaining the reception time of the autonomous message and the processing time is completed. It is characterized in that the processing time is acquired based on the difference from the time when the processing was performed.

[0030]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, embodiments of the present invention will be described with reference to the drawings. In each drawing referred to in the following description, the same parts as those in other drawings are indicated by the same reference numerals. FIG. 1 is a diagram illustrating an outline of processing in the NE aggregation server that has received the autonomous message according to the present embodiment.

As shown in the figure, the autonomous message is processed by the NE interface process 11, the autonomous message receiving process 12, the journal database history registration process 13, and the maintenance terminal communication process 14, Information required for maintenance is displayed on the maintenance terminal 4. Furthermore, in the present embodiment, the NE aggregation server 1 monitors these processes, and the congestion monitoring process 2 for regulating the processing delay or the occurrence of congestion is controlled.
4 is performed.

The operation of the NE aggregation server 1 which is performed during congestion monitoring and regulation in displaying the autonomous message from the NE 3 on the maintenance terminal 4 will be described below.
First, the NE interface process 11 arranged for each NE3 receives an autonomous message from each NE3. The NE interface process 11 that has received the autonomous message registers the number of autonomous messages received per unit time and the time received from the NE 3 in the congestion control information table 23. In the present embodiment, the congestion control information table 23 contains the number of received autonomous messages, NE
Information necessary for monitoring and regulating congestion in the NE aggregation server 1 such as the time received from the database 3, the database registration time, and the autonomous message reception flag are registered for each NE.

The journal database history registration process 13 that receives the autonomous message from the NE interface process 11 through the autonomous message reception process 12
Performs journal database history registration processing. Along with that, journal database history registration process 1
3 updates the database registration time of the NE corresponding to the autonomous message among the information registered in the congestion control information table 23 to the time at which the journal database history registration process was performed.

The congestion monitoring process 24 receives the autonomous message reception time registered in the congestion control information table 23,
The processing delay time is acquired by referring to the database registration time. Further, this processing delay time is compared with the threshold acquired from the congestion monitoring process management table 25.
In this comparison, if the processing delay time exceeds the threshold value, the autonomous message reception flag of the congestion control information table 23 is set to "ON". When the processing delay time is equal to or less than the threshold value, the autonomous message reception flag is left as it is (“OFF”). Further, in the present embodiment, the congestion monitoring process 24 issues a command for disconnecting the connection with the NE that intensively transmits autonomous messages, as will be described later, depending on the degree of the processing delay time.

In the present embodiment, only one NE aggregation server 1 is activated at any one time, and depending on the threshold value to be compared,
A comparison with the delay time and an operation of updating the congestion control information table 23 are performed at regular time intervals or each time a specific process is performed. Until the processing delay or congestion is subsided, the comparison with the threshold value is continuously performed and the regulation based on the comparison is performed.

The NE interface process 11 receives the corresponding N of the congestion control information table 23 when receiving the autonomous message.
Reference the autonomous message reception flag of E. When the autonomous message reception flag is “ON”, the fact is inherited to the autonomous message reception process 12. Therefore, after the autonomous message reception process 12 ends, the journal database history registration process 13 is not performed, and as shown by the arrow Y1, the process directly moves to the maintenance terminal communication process 14 to notify the maintenance terminal 4. That is, the processing by the journal database history registration process 13 is skipped. Autonomous message reception flag is "OFF"
In this case, the processing by the journal database history registration process 13 is executed without skipping the processing by the journal database history registration process 13. The autonomous message reception flag is used as information indicating whether to skip the process by the journal database history registration process 13. As described above, when the processing delay is detected, the specific processing that causes the processing delay is skipped, whereby the further processing delay can be eliminated. In the present embodiment, a processing time is particularly required, and the processing time by the journal database history registration process 13 having a low priority in performing the maintenance processing corresponding to the autonomous message is monitored and skipped when the processing is delayed.

As an alarm to be notified to the maintenance terminal when the NE aggregation server congestion occurs, the total amount of autonomous messages transmitted to the NE aggregation server 1, the name of the NE 3 that is centrally transmitting the autonomous messages, and the amount of autonomous messages , The amount for each autonomous message level, and the regulation level for the NE3. Based on these warnings, maintenance personnel, etc.
E The cause of memory congestion of the aggregation server 1 is searched, measures are taken, and the situation is quickly calmed down.

Further, the restriction such as the skip of the specific process which is executed when the processing time exceeds the threshold value can be performed according to the urgency level of the received autonomous message. In this embodiment, the autonomous message is
As described in the [Prior Art] section, there are four types of messages, the most urgent message, the urgent message, the error message, and the normal message, depending on the level of urgency. In the congestion control information table 23, by setting the regulation contents according to each message level, N
It can be processed for each E and for each level of autonomous message.

In this embodiment, in addition to skipping the journal database history registration process 13 described above, the NE that causes the processing delay is also controlled. Therefore, by classifying these restrictions for avoiding congestion into levels such as processing delay, it is possible to perform appropriate restrictions according to the status such as processing delay. In the present embodiment, the regulation is performed by dividing the regulation level L1 to the regulation level L3 when the processing delay is detected. FIG. 2 shows the regulation contents for each regulation level.

At the regulation level L1, the journal database history registration process 13 of only the error message and the normal message of the NE3 to be regulated, that is, the NE3 that has exceeded the processing time threshold value is skipped. As shown in FIG. 2, the “maintenance terminal display” is “guaranteed” for all messages because all autonomous messages are received as described above.

As described above, the journal database history registration process is skipped and the autonomous message is directly displayed on the maintenance terminal only for the NEs that are centrally transmitting the autonomous message. It is possible to perform the minimum regulation that does not affect the monitoring and journal database history registration and autonomous message monitoring of other NEs.

At the regulation level L2, the journal database history registration process 13 is performed not only for the NE3 that centrally transmits autonomous messages, but also for error messages and normal messages from other NE3.
Skip. As a result, the process of registering the journal database history 13 of the error message and the normal message of the NE3 that centrally transmits the autonomous message
Even if the NE aggregation server 1 congestion is not recovered by simply skipping, the quick recovery can be achieved. Also,
The journal database history registration is guaranteed for the most urgent messages and urgent messages from all NEs 3. Similar to the regulation level L1, the “maintenance terminal display” is “guaranteed” for all messages.

At the restriction level L3, the connection with the NE3 that is transmitting autonomous messages in a concentrated manner is disconnected. As a result, until the NE3 failure is recovered, the autonomous message is not continuously received, and the autonomous message monitoring of other NE3 is not affected. In the “restriction level L3” of FIG. 2, all the messages of “NE that centrally transmits autonomous messages” are also “impossible” in “maintenance terminal display”. This is because the autonomous message cannot be received due to the disconnection of the connection.

FIG. 3 is a diagram for explaining the correspondence between each NE and the regulation level. In the same figure, the number C of received autonomous messages of each NE corresponding to the NE number B, the delay time within the NE server D, the regulation range E, and the regulation level F are shown with respect to the total number A of autonomous messages received by the NE aggregation server. ing. In the present embodiment, in the congestion monitoring process, first, it is determined based on the delay time D in the NE server whether each NE is subject to regulation. Next, the degree of difference from the threshold value or the NE to be regulated
Based on the type, etc., the degree of regulation is determined, and the regulation level of the NE to be regulated is determined.

The threshold is, for example, NE shown in the figure.
It is set as the sum of the delay times of all autonomous message processing received in each NE at a constant value of the total number of receptions from all NEs in the aggregation server. That is, in the figure, it is a threshold that can be compared with the delay time D in the NE server. With this threshold, the NE that causes the processing delay is based on the delay time that depends on the number of receptions of each NE.
Can be specified. Or 1 regardless of NE
The threshold may be the average processing time per one autonomous message. In this case, after detecting the processing delay based on the threshold value, it is necessary to specify the NE that causes the processing delay based on other factors, for example, the number of receptions for each NE. In addition, as described above, it is possible to set the threshold value corresponding to the restriction level and the threshold value corresponding to each autonomous message, and perform the restriction based on the threshold value.

FIG. 4 shows a congestion control method according to this embodiment. In step S401 of the figure, reception of an autonomous message is monitored. When the autonomous message is received, the process proceeds to step S402. In step S402, it is determined whether the processing time required to process the autonomous message exceeds a predetermined threshold. If the threshold is exceeded, the control level is judged based on the difference from the threshold, and step S4 corresponding to each control level is determined.
The control of any of 03 to S405 is performed.

Step S403, S404 or S405
In control 1, control 1, control 2 or control 3 is performed as each control of control level L1, control level L2 or control level L3. Each control level is, for example, N to be controlled.
The difference is provided by setting the width of the range of E, the range of the autonomous message to be controlled, etc. By deciding the control level stepwise, it is possible to perform appropriate control that is less influenced by the control according to the congestion state.

[0048]

As described in detail above, by comparing the processing time for an autonomous message with a threshold value and detecting the processing delay in the NE aggregation server, the processing delay can be detected quickly and reliably. In addition, when a processing delay occurs, it is a process that occupies a dominant time in the process, and by skipping a process with a low priority in the maintenance process, the autonomous message displayed on the maintenance terminal, which is essential for maintenance, can be displayed. The delay can be short.
As a result, the NE failure can be detected early and the failure state can be grasped accurately in real time.

Even when the NE aggregation server makes a transition to a congestion state, the autonomous messages from all NEs are notified in real time by the maintainer to centrally transmit the autonomous messages, causing a delay in processing. Including the above, it is possible to avoid lowering the equipment monitoring level, ensure a stable operation state of the NE aggregation server, avoid service degradation due to delay in recovery measures due to equipment failure, and reduce separation operation.

NE Consolidation Server The contents of notification to the maintainer at the time of congestion enable early detection / primary isolation of the congestion state, primary measures, etc., and promptly identify the extent of impact on peripheral equipment, etc. Can be prevented in advance.

[Brief description of drawings]

FIG. 1 is a diagram illustrating an outline of processing in an NE aggregation server that has received an autonomous message according to the present embodiment.

FIG. 2 is a diagram illustrating the content of regulation for each regulation level.

FIG. 3 is a diagram illustrating correspondence between each NE and a regulation level.

FIG. 4 is a flowchart illustrating a congestion control method according to the present embodiment.

FIG. 5 is a diagram illustrating an outline of a process in which a conventional NE aggregation server receives an autonomous message from an NE and displays it on a maintenance terminal.

FIG. 6 is a diagram for explaining regulation contents (autonomous message uniform discard) for each autonomous message level in a conventional NE aggregation server.

FIG. 7 is a diagram illustrating a communication flow using a conventional OMAP.

FIG. 8: Regulation contents for each autonomous message level in the conventional NE aggregation server (flow control using OMAP)
It is a figure explaining.

[Explanation of symbols]

1 NE aggregation server 2 Autonomous messages 3 NE 4 maintenance terminals 11 Interface process 12 Autonomous message reception process 13 Journal database history registration process 14 Maintenance terminal communication process 15 Journal database 23 Congestion control information table 24 Congestion monitoring process 25 Congestion monitoring process management table

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Kazuhide Takahashi             2-11-1, Nagatacho, Chiyoda-ku, Tokyo Stock             Ceremony company NTT Docomo (72) Inventor Nobuhiro Tanikawa             2-11-1, Nagatacho, Chiyoda-ku, Tokyo Stock             Ceremony company NTT Docomo F term (reference) 5K030 GA01 GA12 GA13 HB08 HC01                       HC13 JA10 KA01 MA01 MA06                       MA07 MB01                 5K033 BA08 BA17 DA01 DB20 EA03                       EA07                 5K051 AA03 AA09 DD01 FF01 FF03                       KK05 LL01

Claims (12)

[Claims] 1. An operation device that receives an autonomous message from at least one or more network elements and performs a process corresponding to the receipt of the autonomous message, the process being required for processing the autonomous message received from each of the network elements. An acquisition unit that acquires time; and a control unit that controls, when the processing time acquired by the acquisition unit exceeds a predetermined threshold value, control so as to shorten the processing time by the processing that exceeds the threshold value. Characteristic operation device. 2. The operation apparatus according to claim 1, wherein the control unit controls to perform a maintenance process corresponding to the autonomous message without performing a process that exceeds the threshold value. 3. The operation apparatus according to claim 1, wherein the control unit controls to disconnect a connection with a network element that transmits an autonomous message that requires a processing time exceeding the threshold value. 4. The operation apparatus according to claim 1, wherein the control unit performs control according to a level regarding urgency of the received autonomous message. 5. The control means determines a control level relating to a degree of congestion control based on a difference between the processing time and the predetermined threshold value, and performs a predetermined control according to the control level. The operation device according to any one of claims 1 to 4, which is characterized by being characterized by the following. 6. The acquisition unit acquires the processing time based on a difference between a reception time of the autonomous message and a time at which the processing of acquiring the processing time is completed. The operation device according to any one of items 1 to 5. 7. A congestion control method for an operation device which receives an autonomous message from at least one or more network elements and performs a process corresponding to the receipt of the autonomous message, the method comprising: An acquisition step of acquiring a processing time required for the process, and a control step of controlling, when the processing time acquired by the acquisition step exceeds a predetermined threshold value, to shorten the processing time by the processing exceeding the threshold value, A congestion control method comprising: 8. The congestion control method according to claim 7, wherein, in the control step, control is performed such that maintenance processing corresponding to the autonomous message is performed without performing processing that exceeds the threshold value. 9. The congestion control method according to claim 7, wherein in the control step, control is performed so as to disconnect a connection with a network element that transmits an autonomous message that requires a processing time exceeding the threshold value. . 10. The control according to any one of claims 7 to 9, wherein in the control step, control is performed according to a level regarding urgency of the received autonomous message.
Congestion control method according to item. 11. In the control step, a control level relating to a degree of congestion control is judged based on a difference between the processing time and the predetermined threshold value, and predetermined control is performed according to the control level. The congestion control method according to any one of claims 7 to 10. 12. The processing time is acquired in the acquisition step based on a difference between a reception time of the autonomous message and a time at which the processing of acquiring the processing time is completed. The congestion control method according to any one of 7 to 11.