JP2000295219A - Congestion controller for operation system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To control an exchange node operation system congestion to be the proper amount one by controlling a reception message to be the proper amount in the exchange node operation system of an exchange system where a plurality of exchange nodes are connected to the exchange node operation system. SOLUTION: When a message report is designated, a module operation state being discriminater DC setting specifications to an operation state managing part 21 is inquired first. Then it is checked whether the operation state is in the middle of operating or repair testing. When it is in the middle of repair testing as the result of the check, the DC setting contents B of a repair testing station is obtained. When it is in the middle of operation, the DC setting contents A of an operating station are obtained and, then, DC setting is realized. In this case, a non-instantaneous report is indicated to the exchange node NE during repair and it is controlled. Thus, it is prevented that even a useless message among the multiple messages with station construction testing is received owing to the negligence of a person in charge of repair testing.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a congestion control device for an operation system, and more particularly, to a congestion control device in a switching node operation system (OpS) accommodating a plurality of switching nodes (NEs).

[0002]

2. Description of the Related Art FIG. 22 is a conceptual diagram of a switching system to which the present invention is applied. In FIG. 1, reference numeral 1 denotes an exchange node operation system (hereinafter, OpS) that accommodates a plurality of exchange nodes (hereinafter, NEs) 2. The switching node 2 is connected to a subscriber terminal (not shown). Some switching nodes 2 are under construction of a station, and a plurality of other switching nodes form one group. One is a traffic control system (TCS) regulated controlled group switch A and a controlled TCS regulated controlled group switch B.
It is. Reference numeral 3 denotes a traffic control system (hereinafter, TCS) for instructing each switching node 2 to make a call restriction.

The function of OpS is to receive and display a message notified from the switching node 2, or
Command. On the other hand, the function of the TCS instructs each switching node 2 to restrict the transmission to the congested area (such as the telephone number of the ticket reservation center) in order to control the congestion of the exchange by the ticket reservation telephone or the like. In a certain regional unit, the switching instructions 2 in the area are grouped and the restriction instruction is simultaneously performed, for example, in a one-minute cycle.

[0004] Switching node 2 whose transmission is regulated by the TCS
Notifies the OpS of the enforcement in a message. As a result, a message is notified simultaneously in a controlled group unit in a one-minute period.

[0005] A station under construction is informed of a large number of messages in order to frequently carry out a test that frequently generates messages (restart processing, etc.) in the construction test. The discriminator (DC) function is a function of notifying the switching node 2 immediately from the OpS, and a function of designating and instructing, for each message, an instruction to store only in the switching node 2 and not to notify.

[0006] 1. NE issues a message at resumption A message is transmitted at a rate of several hundred to several thousand or more / second by resumption of NE. By the object-oriented design, a message is generated one by one for each device (including those having a large number of subscribers such as subscriber circuits). For example, a message such as an OCU (subscriber accommodating device) out-of-sync message / line message is transmitted in units of a subscriber accommodating device.

[0007] OCU out-of-synchronization or the like is a message notifying that a failure has occurred in each subscriber circuit except when the NE is restarted. Therefore, immediate notification is necessary for repair. However, NE
At the time of restart, in order to reset all the devices in the OCU, a failure occurrence message → a recovery message is transmitted once, twice for each device. The first is for reset and the second is for actual operation.

[0008] 2. Procedure of construction test The expansion of the NE takes the procedure of hardware construction → hardware test → accommodation in OpS → operation test (including restart test etc.).
The operation test includes a restart test of the NE by a command from the OpS, a power on / off control, and a confirmation test of a message at that time (all messages including a message to be made non-immediate during normal operation). Is a problem because there are so many messages.

3. Necessity of TCS message Notification required for TCS regulation control (number of calls to regulated destinations, etc.)
Is notified to the TCS. Each NE individually notifies the OpS of the ground, regulation rate, and the like at which regulation has been started at each station as a message. This information is information directly linked to the number of completed calls (sales) at each station, and is handled as necessary information.

[0010] 4. Classification by Message Importance The messages coming from the switching node (NE) 2 are:
Alarms are classified into alarms, state changes, and other messages. Alarms are mapped to four levels of cr (critical), mj (major), mn (minor), and wn (warning) according to their importance. Normally, cr-mn is instant notification,
wn is set non-immediately. The status change notifies the status of the device, and indicates the status of the device displayed on the monitoring screen.

[0011]

In the operation test, Op
There are NE restart, power on / off control, and a message at that time (all messages including non-immediate messages during normal operation) by a command from S, and a confirmation test. Due to the very large number of messages, OpS
The entire network is congested, which affects the maintenance of other NEs that are being aggregated.

[0012] These messages have a clear cause and are involved in the test of the station under construction, and therefore do not need to be monitored by a maintenance person in real time. Since this message causes the OpS to be overloaded and become congested, the maintenance function of the OpS is also adversely affected. However, not all resumption messages are required for all resumption tests, and only a part of them is required. However, the person in charge of the construction test is responsible for the construction test of the NE alone (even in the case of a contractor). Yes), there is little awareness of the effect on OpS that is centrally monitored on a branch-by-branch basis, and all messages are often displayed every time.

Further, when the NE is restarted, the NE performs an initialization process for a device having a large number of subscriber accommodation devices and the like in the restart process and notifies a message for each device. Messages are generated in bursts (for example, several hundred messages / second) in minutes (thousands of units), and the OpS is congested by receiving these messages.

This message is transmitted as follows: (1) The message is transmitted at a rate of several hundred to several thousand or more / second by resuming NE. According to the object-oriented design, a message is generated independently for each device (including a large number such as a subscriber circuit). For example, an OCU out-of-synchronization message / line message is transmitted in units of subscriber accommodation devices.

(2) OCU out-of-synchronization etc. is a message for notifying a failure of each subscriber circuit except when the NE is restarted, so it is essential to notify immediately for repair. However, when the NE is restarted, a failure occurrence message → a recovery message is transmitted once for each device in order to reset all the devices, and this message is known to recover immediately, and is unnecessary. , NE processing is performed using a common method for each object, and therefore cannot be distinguished, and frequent occurrences cannot be avoided.

Although the message is not required to be immediately displayed at the time of resumption, several hundred to several thousand messages are generated in one to two seconds. In this case, the number of received messages cannot be reduced, and the OpS congestion deteriorates.

Further, as described above, there are cases where OpS is congested due to a large number of messages due to the device initialization processing after the NE is restarted. There is a command scenario that starts this NE restart by input from OpS. As a result, the operation from the OpS causes the NE resumption to occur → frequent messages after resumption → OpS congestion.

At the time of detecting the OpS congestion, a "message having low importance and which can be predicted to occur frequently" in advance is registered as system data.
Although the control is performed so as to reduce the number of received messages by performing the C restriction, in the case of a message other than those registered in advance, the effect of the strengthening of the DC restriction is not effective, and the reception of a large number of messages deteriorates the OpS congestion.

When the traffic control system (hereinafter referred to as TCS) issues a call regulation (congestion regulation) instruction to the NE included in the local unit (control group) in order to perform congestion control of the switching network, the OpS accommodates. All NE
, The message to which the restriction instruction has been executed is notified to the OpS in synchronization with a one-minute period.

At this time, the NE receiving the transmission restriction instruction individually sets the restriction status (regulation telephone number, restriction rate, etc.) in a message.
Since the pS is notified to the pS every cycle (one minute), and the OpS receives the regulation status notification message from all the nodes belonging to the area at once, there is a problem that the OpS is congested.

It should be noted that the total number of calls to the regulated ground at the NE as a result of the regulation, the number of outgoing / incoming restricted calls, the load status of the NE
Usage rate, etc.) is notified to the TCS as regulatory status information,
OpS is notified of start / end of regulation {regulation ground (telephone number, area code, etc.), regulation rate}.

Since this TCS regulation information has a great influence on the number of completed calls, it is necessary for each station and branch office.
Since the regulations are implemented in regions and areas, it is not necessary to receive the status of each station individually in a message. There is a problem that OpS is congested by this message.

Further, in a case such as a failure of a common line network (for example, an STP network), the influence of one failure is over a wide range of N.
E, a failure message may be generated irregularly from a large number of NEs for each outgoing call at each NE, although the burst message is not bursty.

FIG. 23 is a diagram showing a failure occurrence state. The STP network has failed while each NE is connected to the STP network. In such a case, in the OpS congestion detection by monitoring the number of messages received from one NE and monitoring the load (CPU utilization) of the OpS, the number of messages from a single NE is not large. Cannot be detected by the monitoring, and the OpS load rises rapidly, causing fatal OpS congestion. That is, the STP failure message is irregularly notified from all of NE # 1 to NE # n, and the total exceeds the OpS capability (capacity).

When the message is restricted during OpS congestion and the number of inputs is reduced, and as a result, the load in the OpS (CPU usage rate, transaction stagnation, etc.) decreases and falls below the restriction release threshold, the restriction is released (restricted). Cancels the message notification). However, if message frequent occurrence in the NE continues (due to restart repeat or the like), the message is received again due to cancellation, and there is a problem that congestion → regulation is repeated again.

Also, OpS congestion is detected by monitoring the OpS load and the number of received messages. In this method, if message processing is delayed due to command load, the detection of congestion is delayed ( Or not). Due to conditions such as "command processing has no database access", there is a tendency that there is no transaction stagnation and the CPU load does not increase so much. However, the message processing is delayed due to the effect of the command processing load, and message display takes several minutes ( There is a problem that congestion regulation is not activated even though a delay of about 5 minutes has occurred.

The present invention has been made in view of the above problems, and an object of the present invention is to provide a congestion control device of an operation system capable of appropriately controlling OpS congestion.

[0028]

(1) FIG. 1 is a block diagram showing the principle of the present invention. The same components as those in FIG. 22 are denoted by the same reference numerals. In the figure, 1 is an exchange node operation system (OpS), and 2 is a plurality of exchange nodes (NE) connected to the OpS. Reference numeral 10 denotes a received message control means provided in the switching node operation for controlling a received message to an appropriate amount. Reference numeral 11 denotes a database (DB) storing various data for message reception control.

According to the present invention, the received message control unit 10 controls the received message from each NE to an appropriate amount according to a predetermined procedure, so that OpS is not congested.

(2) In this case, the received message control means 10 manages the exchange nodes to be accommodated separately in the station construction work and the normal operation state, and manages the exchange nodes in the station construction work. Is characterized in that a notification condition of a message that frequently occurs during station construction work is instructed and controlled to a non-immediate notification.

According to the present invention, since the received message control means 10 instructs (regulates) the message from the NE during the station construction work to the non-immediate notification, the OpS is not congested.

(3) When switching node 2 restarts,
The reception message control means 10 controls the notification condition of a message which frequently occurs when a restart occurs to non-immediate notification upon receiving the restart notification message notified first.

According to the present invention, when a restart occurrence message is detected, each NE is instructed and controlled to perform non-immediate notification.
OpS can be prevented from being congested. (4) Before inputting a command to the switching node instructing the execution of the restart processing from the switching node operation system, the received message control means uses the switching node operation system to instantaneously transmit a message which frequently occurs when the switching node is restarted. It is characterized by instructing the notification.

According to the present invention, since a frequent message accompanying the initial setting of the device after the restart can be regulated in advance, no unnecessary frequent message is received after the restart, and the OpS is not congested.

(5) When a specific message is frequently generated from the switching node, the received message control means
It is characterized by referring to the latest received messages, determining that the message is a message that frequently occurs, and instructing the message to be a non-immediate notification.

According to the present invention, even if a message other than the registered message is expected to occur frequently and bursts occur even if the message is the same as the message registered in the n histories, , Non-immediate notification, the number of received messages can be reduced, and congestion of OpS can be prevented.

(6) A plurality of switching nodes are accommodated,
In the case where messages having the same content are periodically notified from the respective switching nodes, and when the messages are processed, management means for managing the switching nodes that notify the messages having the same content in synchronization as one group is provided. The received message control means 10 refers to the management means and instructs immediate notification of the message from one switching node of the group, and instructs other switching nodes to instruct the message to be non-immediate notification. It is characterized by.

According to the present invention, one NE of the group
Only the immediate notification instruction is given for the other, and the others are regulated, so that OpS received messages can be minimized and congestion can be prevented.

(7) When each switching node is simultaneously affected by the failure of the transit network and the sum of messages from each switching node exceeds a predetermined threshold, the received message control means It is characterized in that a node is instructed to perform non-immediate notification.

According to the present invention, in the case of a failure that affects a wide area, a large number of total messages from many NEs are quickly detected, and the message is restricted to non-immediate notification.
OpS can be prevented from being congested.

(8) Further, the determination of the congestion restriction release of the received message control means is performed by determining that the non-immediate message frequent message is not output.

According to the present invention, congestion regulation can be released by judging that the number of messages regulated on the NE (switching node) side has decreased, so that congestion occurrence → restriction activation → load reduction → restriction release → It is possible to prevent the cycle of occurrence of congestion from being repeated again.

(9) Further, it is characterized in that congestion due to overload of the switching node operation system is detected by processing delay. According to the present invention, when the processing delay time exceeds the threshold value, it is possible to determine that OpS congestion has occurred and to regulate the command processing.
Can be prevented from being congested. In the case of the present invention, Op that hardly appears in the number of transactions staying, the CPU usage rate, etc.
By detecting a delay in message display processing due to the S load, command processing can be reduced by command regulation.

[0044]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 2 is a diagram showing a first embodiment of the present invention. 1 are denoted by the same reference numerals. In OpS, reference numeral 20 denotes a DC setting unit that performs DC control on the NE. The DC setting section 20 includes a DC setting content A of the operation station and a D setting of the construction test station.
C setting content B is stored. 2 is the switching node (N
E), which shows a module under construction. Op
S and NE communicate with each other using the X25 protocol.

An operation state management unit 21 manages the operation state of the system. A database (DB) 11 stores the NE operation state. Reference numeral 22 denotes an NE for controlling the accommodation of the NE.
It is an accommodation control unit. The DC setting unit 20, the operation state management unit 21, and the NE accommodation control unit 22 constitute the received message control unit 10. The operation of the device configured as described above will be described below.

In this embodiment, attention is paid to the fact that the message of the station under construction is a message that does not need to be immediately notified except during a test for confirming the message. The station is managed as a state, and a DC restriction instruction is issued to the station under construction to restrict the notification of a multiple message different from that of the normal operation station. At the time of a test necessary for confirming the regulation message, the tester individually changes only the necessary message from the control screen to the immediate notification and executes the test.

FIG. 3 is a flowchart showing the operation of the NE accommodation control unit 22. The NE accommodation control unit 22 contains the accommodation NE.
Is notified to the operation state management unit 21 (module i
d).

FIG. 4 is a flowchart showing the operation of the operation state management unit 21. When receiving the notification, the operation state management unit 21 registers in advance in the NE operation state management database 11 that the NE of the module id of the notification is under construction.

FIG. 5 is a flowchart showing the operation of the DC setting unit 20. When the message notification is specified, first, the operation status management unit 21 is inquired of the operation status of the module having the DC setting specification (S1). Next, it is checked whether the operation state is under operation or under construction test (S2).

As a result of the check, if the construction test is underway, the DC setting contents B (see FIG. 2) of the construction test station are acquired (S3). If the operation is underway, the DC setting contents of the operation station are acquired. A is acquired (S4). After that, DC setting is performed (S5). In this case, instruction control is performed to the NE under construction to give a non-immediate notification. However, notification is not restricted only for cr messages (critical messages). This is an important message.

According to this embodiment, it is possible to prevent a message that is frequently generated due to the station construction test from being received even if it is unnecessary due to the negligence of the person in charge of the construction test.
According to this embodiment, since the message control means 10 controls the message from the NE during the station construction work to the non-immediate notification, the OpS is not congested.

FIG. 6 is a diagram showing a second embodiment of the present invention. The same components as those in FIG. 2 are denoted by the same reference numerals. In the figure, reference numeral 20 denotes a DC setting unit, and reference numeral 23 denotes an NE communication MSG receiving unit that detects a restart occurrence notification message coming from the NE. 24 is the NEG MSG receiving unit 2
3 is a monitoring MSG display unit that outputs an NE restart occurrence upon receiving a detection notification from the terminal 3 and displays the content on a display unit (for example, the terminal HMI-WS). 25 is the monitoring MSG
A congestion control instructing unit that instructs the DC setting unit 20 to intensify the DC regulation upon receiving the NE restart notification from the display unit 24. The DC setting unit 20, the NE communication MSG receiving unit 23, the monitoring MSG display unit 24, and the congestion control instruction unit 25 constitute the message control unit 10 of the present invention. The operation of the device configured as described above will be described below.

In this embodiment, a large amount of messages (hereinafter, MSG) (for example, OCU out-of-synchronization messages) accompanying a large number of restart initializations after the occurrence of a restart are regulated. For this reason, a restart occurrence notification message is detected, and a message accompanying the restart initial setting that rises thereafter is regulated. For example, assuming that the number of restart occurrence notifications is 20, OCU
The number of messages associated with restart initialization such as loss of synchronization ranges from hundreds to thousands. Therefore, there is a need for regulation.

The restart notification message from NE is NE communication M
When notified to the SG receiving unit 23, the NE communication MSG receiving unit 23 notifies the monitoring MSG display unit 24 of the notification.
The monitoring MSG display unit 24 that has received the notification displays the fact on the display unit, and issues an NE restart occurrence notification to the congestion control instruction unit 25.

Upon receiving the NE restart notification, the congestion control instructing unit 25 notifies the DC setting unit 20 of a DC strengthening instruction for regulating the occurrence of multiple MSGs after the restart. Upon receiving this notification, the DC setting unit 20 issues an enhanced DC setting execution instruction to the NE. As a result, the message accompanying the initialization of the restart from the NE is not output.

FIG. 7 is a flowchart showing the operation of the monitoring MSG display unit 24. When a message is received, it is checked whether the message is a restart message by referring to the restart message list in the database 11 (S1). If the message is a restart message, the occurrence of the NE restart is notified to the congestion control instruction unit 25 (S2). If it is not a restart message, monitoring (a maintenance terminal for monitoring, for example, HMI-WS)
The message is transmitted to (S3).

According to this embodiment, the internal load of the OpS (the increase in the CPU usage rate and the number of transactions stuck).
Since the restriction instruction can be activated before the effect appears, it is possible to prevent the reception of bursty frequent messages,
The number of messages received to S can be reduced, and congestion can be prevented. According to this embodiment, when the restart occurrence message is detected, each NE is instructed to perform non-immediate notification, and
OpS can be prevented from being congested.

FIG. 8 is a view showing a third embodiment of the present invention. 6 are denoted by the same reference numerals. In the figure, 26 is a command transmission / reception unit for transmitting / receiving commands, 27 is a command control unit for performing command input control, 28 is a business / scenario control unit, and 29 is a terminal. The output from the command control unit 27 enters the congestion control instruction unit 25. The congestion control instructing unit 25 is provided with a function of notifying the NE of DC restriction before inputting a command to the NE when the NE is restarted. DC setting unit 20, monitoring MSG display unit 24, command transmission / reception unit 26, command control unit 2
7. The congestion control instruction unit 25 constitutes the message control means 10 of the present invention. The operation of the device configured as described above will be described below.

In this embodiment, it is known in advance that OpS commands, such as FUP, RMT, POW, etc., and F update work (scenario) are input from the OpS side to the NE. Prior to this, the congestion control instructing unit 25 preliminarily performs DC restriction on the DC setting unit 20 to prevent frequent messages.

The command described above is input from the terminal 29 to the command control unit 27, and a scenario is input from the business / scenario control unit 28. When these commands are input, it is predicted in advance that many messages will occur later (because it is oneself, it is understood by oneself). Therefore, the command control unit 27 outputs an NE restart activation notification to the congestion control instruction unit 25. I do.

The congestion control instructing unit 25 having received this notification
After the restart, the DC setting unit 20 issues a DC strengthening instruction to suppress multiple MSGs. Upon receiving this, the DC setting unit 20
The enhanced DC setting is performed for the NE. On the other hand, the congestion control instructing unit 25 issues a DC reinforcement instruction to the DC setting unit 20, and then issues a DC reinforcement completion completion notification to the command control unit 27.

According to the above-mentioned sequence, since the message after resumption from the NE does not occur frequently, the command input unit 27 inputs a command to the command transmitting / receiving unit 26, and the command transmitting / receiving unit 26 transmits the command to the NE. Give command. At the same time, the monitoring MSG display unit 24
Send and display messages on.

FIG. 9 is a flowchart showing the operation of the command control unit 27. It is checked whether the command is a restart start command by referring to the restart start command list from the database 11 (S1). If so, it notifies the congestion control instructing unit 25 of the NE restart activation (S2). Then, it waits for the completion of DC reinforcement (S3). The DC consolidation instruction is issued from the congestion control instruction unit 25 to the DC setting unit 20,
When the completion of the DC enhancement is notified, the original command is input (S4). Even if it is not the restart command in step S1, the original command is input.

According to this embodiment, since the frequent messages accompanying the initial setting of the apparatus after the restart can be regulated in advance, the unnecessary frequent messages are not received at all after the restart, and the OpS may be congested. Disappears.

FIG. 10 is a diagram showing a fourth embodiment of the present invention. 6 are denoted by the same reference numerals. In the figure, reference numeral 20 denotes a DC setting unit that activates DC regulation for the NE, 23 denotes an NE communication MSG receiving unit that receives a message from the NE, and 24 denotes a message that is received by receiving a message from the NE communication MSG receiving unit 23. A monitoring MSG display unit 25 for performing monitoring and display is a congestion control instructing unit that receives a message frequent notification together with a multiple MSG number from the monitoring MSG display unit 24. The output of the congestion control instructing unit 25 is a DC setting unit as a regulation strengthening instruction signal. 20 given.
DC setting unit 20, NE communication MSG receiving unit 23, monitoring MS
The G display unit 24 and the congestion control instruction unit 25 constitute the received message control unit 10 (see FIG. 1) of the present invention.
The operation of the device configured as described above will be described below.

The messages that frequently occur in the NE are generated for each device as in the case of the initial setting process of a device mounted as a large number of subscriber accommodation devices after the restart, so that several hundreds of the same messages are generated. In many cases, it occurs frequently. By utilizing this feature, several received message histories (5-1
(About 0), and if a message occurrence is detected frequently, the message in the message history is determined to be a message occurring frequently, so that the message occurrence can be specified. By restricting the message from DC, OpS congestion due to frequent occurrence of messages other than pre-registration is prevented.

When the NE communication MSG receiving section 23 receives a frequent message from the NE, the message is monitored by the monitoring MSG.
Send it to the display unit 24. In the monitoring MSG display unit 24, the memory 30 stores the past five message histories.

When the received message is the same as the stored message history, the monitoring MSG display unit 24 sends a message frequent occurrence notification to the congestion control instruction unit 25 together with the message frequent MSG number. When the congestion control unit 25 receives the notification of the frequent occurrence of the message, the DC
An instruction to strengthen regulation is issued by specifying the G number. The DC setting unit 20 applies the enhanced DC restriction to the corresponding message.

FIG. 11 is a flowchart showing the operation of the monitoring MSG display unit 24. The memory 30 of the monitoring MSG display unit 24 stores the latest message types for the past five times. In the figure, MSG history [0] to MSG history [4] are such. The MSG reception id is set to Mid (S1). Then, it is checked whether Mid is smaller than 4 (S2).

If it is smaller, the MSG number is saved in the MSG history [Mid] (S4). If Mid is greater than 4, Mid is initialized to 0 (S3). Or later,
Mid is updated from 0 to 4. By repeating the above process, the memory 30 always stores the latest five message histories.

If the received message is compared with the MSG history and many messages occur, the last five messages are fetched from the memory 30 (S6), and the five most recent MSG numbers are attached to the congestion control instruction unit 25. (S7).

FIG. 12 is a flowchart showing the operation of the DC setting unit 20. First, when a restriction instruction is received, a congestion restriction message number is obtained from the restriction message file 31 (S1). Next, it is checked whether there is a multiple MSG designation (S2). If there is a multiple MSG designation, the designated MSG number is added to the registered one, and the regulation instruction information is edited (S3). After that, a regulation instruction is executed (S
4).

According to this embodiment, even if a message other than a registered message is predicted to occur frequently and bursts occur, the message is the same as the message registered in n histories. In this case, since the instruction control is performed for the non-immediate notification, the number of received messages can be reduced.
Can be prevented from being congested.

FIG. 13 is a diagram showing a fifth embodiment of the present invention. The same components as those in FIG. 22 are denoted by the same reference numerals. In this embodiment, monitoring means (not shown)
Manages the NE by dividing it into a group A and a group B. For example, group A indicates an area having an area code of “03”, and group B indicates an area having an area code of “044”. Traffic control system (T
The CS) 3 changes the content of the regulation for each area, but in the case of the same area, gives the same regulation instruction to the NE of the area.

Therefore, in response to this TCS regulation instruction, NE
Are the same for each group. Since the rise of a large number of such messages results in OpS congestion, one NE from each group.
Is selected to raise the message to OpS (solid line in the figure), and the remaining NEs are subject to message immediate notification restriction (dashed line in the figure).

In this embodiment, the NEs in the control area of the TCS are managed as one group, one NE is extracted from the group, and an immediate notification instruction is sent to the extracted node as a regulation status message. By informing non-immediate notification to the other NEs, the OpS is controlled to receive only the regulation status message from one NE extracted from within the group, and the received message is limited to the minimum necessary. Thus, congestion of OpS is prevented.

The operation of the received message control means 10 shown in the figure will be described. First, referring to the database TCS regulation group management table, a TCS regulation group is acquired (S1). As shown in the figure, in the TCS regulation group management table, NEs belonging to each group are registered and managed. Next, the head NE of the group is immediately notified, and the others are determined as the regulatory symmetric NEs (S2).

Next, the TCS regulation MS of the database 11
The TCS-regulated MSG number is acquired with reference to the G number management table (S3). As shown in the figure, the TCS regulation MSG number management table is composed of a TCS regulation message number list. Next, one NE is extracted (S4). Next, it is checked whether or not the extracted NE is a NE to be immediately notified (S5).

If the NE is not the immediate notification target NE, the TCS
The regulation MSG is added to the regulation (S6). NE for immediate notification
In the case of, the TCS message is designated for immediate notification (S7). When the above processing is completed, DC regulation is set with the determined message (S8). Next, it is checked whether the DC setting of all the NEs to be connected has been completed (S9). If the processing has not been completed yet, the process returns to step S4 to start processing for extracting one NE, and if completed, the processing ends.

According to this embodiment, it is possible to minimize the number of OpS received messages to prevent congestion, and to display the outgoing connection enforcement status required in the group area as a message. As described above, according to this embodiment, only one NE of the group is instructed to immediately notify, and the others are regulated, so that OpS received messages can be minimized and congestion can be prevented. .

FIG. 14 is a diagram showing a sixth embodiment of the present invention. 6 are denoted by the same reference numerals. In the figure, reference numeral 20 denotes a DC setting unit for restricting message notification to NEs; 23, an NE communication MSG receiving unit for receiving an irregular message coming from each NE;
4 receives a message from each of the NE communication MSG receiving units 23, detects a large number of low-level messages,
This is a monitoring MSG display unit displayed on the display screen.

Reference numeral 25 denotes a congestion control instructing unit that receives a notification of the frequent occurrence of light level messages coming from the monitoring MSG display unit 24 and issues a regulation strengthening instruction command. This is a DC setting unit that receives the regulation strengthening instruction signal and regulates the message notification to each NE immediately. The DC setting unit 20, the NE communication MSG receiving unit 23, the monitoring MSG display unit 24, and the congestion control instructing unit 25 constitute the received message control unit 10. The operation of the device configured as described above will be described below.

When the common line network is broken, as shown in FIG. 23, call signals from the respective NEs rise discontinuously. If the total number of messages coming from each NE exceeds a threshold value, it is determined that OpS congestion will occur, and non-immediate notification regulation is applied to each NE.

In this embodiment, two message reception number monitoring thresholds of each NE are provided (t1 <t2), and t
2 is a conventional threshold value (for example, 80 MSG / min) for detecting a single message occurrence of one NE, and t1 according to the present invention.
Is a low value (for example, 10 MSG / min).

When a message exceeding t1 occurs, the regulation does not start immediately, but only that the message exceeding t1 occurs frequently is recorded. The number of NEs exceeding t1 is counted, and when this number exceeds the threshold value t2, it is determined that a message is frequently generated due to a wide-area failure, and all accommodated NEs (including NEs for which messages have not yet been sent) message regulation is performed. It is to be implemented.

If the common line network is broken, each NE repeatedly raises a message in an attempt to make a call. In this way, messages coming up irregularly from each NE
The corresponding monitoring MS received by the E-communication MSG receiving unit 23
It is displayed on the G display unit 24. The monitoring MSG display unit 24
Displays the received message on the display of the terminal,
The congestion control instructing unit 25 is notified that many messages of a light level (exceeding t1) occur frequently.

When the congestion control instructing unit 25 receives this notification, the congestion control instructing unit 25, when the total number of frequent notifications exceeds the threshold value t2,
An instruction to strengthen regulation is issued to the DC setting unit 20 by specifying a multiple MSG number. In response to this, the DC setting unit 20 restricts non-immediate notification to all NEs.

FIG. 15 is a flowchart showing the operation of the congestion control instructing unit 25. When the low-level MSG multiple occurrence notification is received from the monitoring MSG display unit 24 (S1), the notification source N
The E number and time are recorded in the low level MSG multiple occurrence NE management table of the database 11 (S2). Next, it is checked whether the number of NEs notified within T minutes is larger than a predetermined threshold value N (S3).

If the size is large, messages from each NE occur frequently, so the message is notified to all the accommodated NEs, and the communication restriction of non-immediate notification is imposed (S
4). If it is not large, the number of NEs in the notification is N or less, so no restriction is imposed (S5).

According to this embodiment, in the case of a failure that affects a wide area, a total message occurrence from many NEs is quickly detected, the message is restricted to non-immediate notification, and OpS Congestion can be prevented.

FIG. 16 is a diagram showing a seventh embodiment of the present invention. 6 are denoted by the same reference numerals. In the figure, 20 is a DC setting unit, 23 is an NE communication MSG receiving unit, 24 is a monitoring MSG display unit, and 25 is a congestion control instructing unit, and these constitute the received message control means 10 of the present invention. The operation of the device configured as described above will be described below.

In this embodiment, when the OpS internally controls the notification of a message coming from the NE, the message is coming from each NE. Therefore, when the OpS releases the restriction, the number of messages becomes excessive, and the cycle of the restriction is prevented from being repeated.

[0093] The DC setting unit 20 performs the enhanced DC setting for the restricted NE, but excludes the non-immediate message frequent messages from the DC restriction. The NE counts the number of messages that have been notified and regulated by the DC, and if the number exceeds a threshold (for example, 10 MSG / 5 minutes; this value can be changed by a command), this is indicated as "frequent occurrence of non-regulated messages". The message is used to notify that there is no more than 10 minutes (two-fifths period) from the NE that the message regulates, and the OpS
It is determined that the load on the vehicle is decreasing, and the regulation is released.

When non-immediate message frequent occurrence information enters the NE communication MSG receiving section 23 from the NE under DC regulation, the message is transmitted to the NE communication MSG receiving section monitoring MSG display section 24. The monitoring MSG display unit 24 notifies the congestion control instructing unit 25 from the received message each time a non-immediate message is frequently received from the NE.

FIG. 17 is a flowchart showing the operation of the monitoring MSG display unit. When a message is received,
The SG checks whether non-immediate MSG occurs frequently (S1). If so, congestion control instructing unit 2
5 (S2), and performs an existing message notification process (S3). If the received message is not non-immediate MSG, the existing message notification process is performed without notifying the congestion control instructing unit 25 (S3).

FIG. 18 is a flowchart showing the operation of the congestion control instructing unit 25. When a non-immediate MSG is frequently received, a reception history is stored in the database 11 (S
1). The congestion control instructing unit 25 checks whether the OpS load is equal to or less than a threshold (S2). If the OpS load is below the threshold, non-immediate MSG
It is checked whether or not a minute has been received (S3). If there is no reception, the restriction release is executed (S4). In step S2, when the OpS load is equal to or more than the threshold, and in step S3, non-immediate MSG
If it is within the minute, the restriction will not be released.

According to this embodiment, congestion regulation can be released by judging that the number of messages regulated on the NE side is decreasing, so that the message occurrence on the NE side has not stopped. It is possible to prevent repetition of the cycle of occurrence of congestion, occurrence of congestion → activation of restriction → reduction of load → removal of restriction → congestion occurrence again.

FIG. 19 is a diagram showing an eighth embodiment of the present invention. 6 and 8 are denoted by the same reference numerals. In the figure, 23 is an NE communication MSG receiving unit for receiving a message from the NE, 24 is a monitoring MSG display unit for detecting and displaying a delay in response to the message, 25
Is a congestion control instruction unit, 27 is a command control unit connected to the congestion control instruction unit 25 to exchange messages,
28 is a task of notifying the command control unit 27 of the scenario;
The scenario control unit 29 is a terminal that gives various commands to the command control unit 27. NE communication MSG receiver 2
3. The received message control means 1 of the present invention comprises the monitoring MSG display unit 24, the congestion control instruction unit 25, and the command control unit 27.
0. The operation of the thus configured device will be described below.

The command from the business / scenario control unit 28 or the terminal 29 is given to the command control unit 27, and the command control unit 27 inputs the command to the NE. On the other hand, when a message corresponding to the input command is sent from the NE, the NE communication MSG receiving unit 23 receives the message and notifies the monitoring MSG display unit 24. The monitoring MSG display unit 24 calculates the message delay time, and regards the message delay to the congestion control instruction unit 25. The congestion control unit instructing unit 25 issues a command to stop executing the command to the command control unit 27 based on the information provided from the monitoring MSG display unit 24.

When receiving an instruction to cancel a command being executed, the command control unit 27 issues a stop command to the NE and suspends the command. At the same time, command completion registration is made to the congestion control instructing unit 25.

FIG. 20 is a flowchart showing the operation of the monitoring MSG display unit 24. When a message is received, a delay time is calculated (S1). The calculation of the delay time is performed by the following equation.

The [NE time in MSG]-[Current time of OpS] message incorporates time information at the time of transmission from the NE. Therefore, the current time of OpS and MS
The delay time can be calculated from the difference from the NE time in G.

Here, it is checked whether or not the delay time is greater than a predetermined threshold value (S2). If it is large, the message delay is notified to the congestion control instruction unit 25 (S3). As a result, the congestion control unit instructing unit 25 can send an in-execution command abort instruction to the command instructing unit 27, and the command input is aborted.

FIG. 21 is a flowchart showing the operation of the eighth embodiment, and shows the operation when a delay occurs.
When the congestion control instructing unit 25 receives the in-execution command registration / end registration from the command control unit 27, it registers it in the in-execution command list 11 of the database 11 (S
1). The congestion control instructing unit 25 acquires the command being executed by referring to the command list being executed (S2). Next, an instruction to stop the command being executed is issued to the command control unit 27 (S3).

[0105]

As described above in detail, according to the present invention, (1) receiving message control means for appropriately controlling received messages in the switching node operation system is provided. The unit controls the received message from each NE to an appropriate amount according to a predetermined procedure, so that OpS does not become congested.

(2) In this case, the exchange nodes to be accommodated are managed separately during the station construction work and the normal operation state, and the exchange nodes under the station construction work frequently occur during the station construction work. By instructing the notification condition of the message to the non-immediate notification, the received message control means instructs the message from the NE under construction of the station to the non-immediate notification (regulation control), so that the OpS is not congested. .

(3) Further, when the switching node restarts, the notification condition of a message which frequently occurs at the time of restart occurrence is instructed and controlled to non-immediate notification upon reception of the restart notification message notified first. When the restart occurrence message is detected, instruction control is performed to each NE for non-immediate notification, thereby preventing OpS from being congested.

(4) In the switching node operating system, the received message control means instructs the non-immediate notification of a message that frequently occurs when the switching node is restarted, so that a message that frequently accompanies the initial setting of the device after the restart is prepared in advance. Since regulation can be performed, unnecessary unnecessary messages are not received at all after the restart, and OpS is not congested.

(5) The received message control means is n
The latest received message is referred to, it is determined that the message is a message that frequently occurs, and by instructing the message to be a non-immediate notification, the occurrence of the message is predicted in advance and other than the registered message. Even when a message occurs in a burst, if the message is the same as the message registered in the n histories, instruction control is performed for non-immediate notification, so that the number of received messages can be reduced.
It is possible to prevent pS from being congested.

(6) Also, the received message control means
One of the switching nodes in the group refers to the management means to immediately notify the message and instructs other switching nodes to non-immediately notify the message, thereby immediately controlling only one NE in the group. By giving a notification instruction and restricting the others, it is possible to minimize the number of OpS received messages and prevent congestion.

(7) When the sum of messages from the switching nodes exceeds a predetermined threshold, the received message control means instructs these switching nodes to perform non-immediate notification, thereby In the case of a failure that affects a wide area, it is possible to quickly detect the occurrence of a large number of total messages from many NEs, restrict the message to non-immediate notification, and prevent the OpS from being congested.

(8) Also, by determining that congestion restriction release is performed by determining that non-immediate message frequent messages have not been output, it is possible to confirm that the number of messages restricted on the NE side is reduced. Since congestion regulation can be canceled by making a decision, congestion occurrence → regulation activation → load reduction →
It is possible to prevent the cycle of restriction release → congestion occurrence from being repeated again.

(9) Further, by detecting the congestion due to the overload of the switching node operation system based on the processing delay, when the processing delay time exceeds the threshold value,
It is possible to determine the occurrence of OpS congestion and to regulate command processing, thereby preventing OpS congestion. In the case of the present invention, the number of transactions staying, the CPU
It is possible to detect a delay in message display processing due to an OpS load that hardly appears in the usage rate or the like, and reduce command processing by command regulation.

As described above, according to the present invention, it is possible to provide a congestion control device of an operation system capable of appropriately controlling OpS congestion.

[Brief description of the drawings]

FIG. 1 is a principle block diagram of the present invention.

FIG. 2 is a diagram showing a first embodiment of the present invention.

FIG. 3 is a flowchart illustrating an operation of an NE accommodation control unit.

FIG. 4 is a flowchart illustrating an operation of an operation state management unit.

FIG. 5 is a flowchart illustrating an operation of a DC setting unit.

FIG. 6 is a diagram showing a second embodiment of the present invention.

FIG. 7 is a flowchart showing an operation of a monitoring MSG display unit.

FIG. 8 is a diagram showing a third embodiment of the present invention.

FIG. 9 is a flowchart illustrating an operation of a command control unit.

FIG. 10 is a diagram showing a fourth embodiment of the present invention.

FIG. 11 is a flowchart showing an operation of a monitoring MSG display unit.

FIG. 12 is a flowchart illustrating an operation of a DC setting unit.

FIG. 13 is a diagram showing a fifth embodiment of the present invention.

FIG. 14 is a diagram showing a sixth embodiment of the present invention.

FIG. 15 is a flowchart illustrating an operation of a congestion control instruction unit.

FIG. 16 is a diagram showing a seventh embodiment of the present invention.

FIG. 17 is a flowchart showing an operation of a monitoring MSG display unit.

FIG. 18 is a flowchart illustrating an operation of a congestion control instruction unit.

FIG. 19 is a diagram showing an eighth embodiment of the present invention.

FIG. 20 is a flowchart showing the operation of the monitoring MSG display unit.

FIG. 21 is a flowchart showing the operation of the eighth embodiment.

FIG. 22 is a conceptual diagram of a switching system to which the present invention is applied.

FIG. 23 is a diagram illustrating a failure occurrence state.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Switching node operation system (OpS) 2 Switching node (NE) 10 Received message control means 11 Database

──────────────────────────────────────────────────の Continued on the front page (51) Int.Cl. ⁷ Identification code FI Theme coat ゛ (Reference) H04M 3/22 H04L 11/20 102E 3/36 3-19-2 Nippon Telegraph and Telephone Corporation (72) Inventor Ken Fujiwara 3-19-2 Nishishinjuku, Shinjuku-ku, Tokyo F-Term within Nippon Telegraph and Telephone Corporation 5K019 AA08 BA01 BB21 CA01 DA03 DC01 5K030 GA11 HA08 HB11 HC01 HC13 JA11 JA12 JA13 KA07 LC11 MA07 MB00 MC01 5K051 AA03 AA09 BB05 FF01 FF03 FF04 HH15 JJ11 KK07

Claims (9)

[Claims] 1. An operation in a switching system in which a plurality of switching nodes are connected to a switching node operating system, wherein said switching node operating system is provided with received message control means for appropriately controlling received messages. System congestion control device. 2. The received message control means manages the exchange nodes to be accommodated separately during a station construction operation and in a normal operation state, and controls the exchange nodes under the station construction operation during the station construction operation. 2. The congestion control device for an operation system according to claim 1, wherein a notification condition of a frequently occurring message is instructed and controlled to a non-immediate notification. 3. When the switching node restarts, upon receiving the restart notification message notified first, the received message control means instructs a non-immediate notification of a notification condition of a message that frequently occurs when restart occurs. 2. The congestion control device for an operation system according to claim 1, wherein: 4. Before receiving a command from the switching node operating system to instruct the switching node to execute restart processing, the received message control means uses the switching node operating system to non-immediately transmit a message that frequently occurs when the switching node is restarted. 2. The congestion control device for an operation system according to claim 1, wherein instruction control is performed for the notification. 5. When a specific message is frequently generated from a switching node, the received message control means refers to the n latest received messages, determines that the message is a message that frequently generates the message, and determines the message to be a message generated frequently. 2. The congestion control device for an operation system according to claim 1, wherein instruction control is performed for non-immediate notification. 6. A plurality of switching nodes are accommodated, and messages having the same content are periodically notified from each of the switching nodes.
In the case of processing the message, the system further comprises a management unit that manages switching nodes that notify messages of the same content synchronously as one group, wherein the received message control unit refers to the management unit and 2. The congestion control device of an operation system according to claim 1, wherein one of the switching nodes in the group issues an immediate notification instruction of the message, and the other switching nodes instruct and control the message to be a non-immediate notification. 7. When each switching node is simultaneously affected by a relay network failure and the sum of messages from each switching node exceeds a predetermined threshold, the received message control means 2. The congestion control device of an operation system according to claim 1, wherein the instruction control is performed for non-immediate notification. 8. The congestion control of an operation system according to claim 1, wherein the determination of the congestion restriction release of said received message control means is performed by determining that a non-immediate message frequent message is not output. apparatus. 9. The congestion control device for an operation system according to claim 1, wherein congestion due to overload of the switching node operation system is detected based on a processing delay.