JPH0879372A - Autonomous congestion control method in service control node - Google Patents

Abstract

(57) [Summary] [Purpose] The SCP in the IN is composed of a plurality of modules, and each module is composed of a plurality of processing units. There are various types of processing executed at the module level and the processing unit level. To provide an autonomous congestion control method in SCP that can be adopted even when existing in [Structure] When each module in the SCP has reached the limit load state that can guarantee the continuation of the processing being executed, the autonomous regulation at the module level is activated, and the SCP having the above module as a constituent element , The autonomous congestion control method in the SCP, which activates the autonomous regulation at the node level when the load reaches a limit that can guarantee the continuation of the process being executed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION The present invention relates to a service control node in an intelligent network (hereinafter referred to as "IN").
(Hereinafter, referred to as “SCP”), it is assumed that the SCP in IN is composed of a plurality of modules, and when a certain SCP is congested, a node that centrally controls the traffic in the network (network If the congestion state of the SCP further progresses (deteriorates) before the effect of the network traffic control (restriction) activated by the control node) appears, the SCP in the congestion is autonomously appropriate in its own node. The present invention relates to an autonomous congestion control method in the SCP that implements various restrictive measures and maximizes the processing capacity for continuing the ongoing call processing (service control).

[0002]

2. Description of the Related Art Conventionally, as a method that has been adopted as a congestion control method for SCP in an IN, a network-based congestion control (hereinafter referred to as network congestion control performed mainly by a network control node that centrally controls traffic in the network) , "Network congestion control"), and when the congestion state of the SCP further progresses before the effect of the network congestion control appears, the SCP itself during the congestion is autonomously implemented in its own node. Congestion control (hereinafter referred to as "autonomous congestion control"). The outline of the above-mentioned network congestion control is S
When the load (operating) status of the CP exceeds a specified value, the relevant SCP (hereinafter referred to as "congestion SCP") notifies the network control node to that effect, and the network control node receiving the notification causes congestion. This is to issue an instruction to regulate the transmission of a processing request to a congestion SCP to other peripheral nodes that transmit a processing request to the SCP. As a result, the number of processing requests sent to the congestion SCP decreases, so that the congestion is resolved. Note that, hereinafter, the restrictive action triggered by the above-described network congestion control is referred to as "network restriction". In addition, the outline of autonomous congestion control is
If the congestion state of the congestion SCP further progresses before the effect of the network congestion control described above appears, and the call processing (service control) being executed by the congestion SCP cannot be continued, the congestion SCP becomes autonomous. This is to restrict the acceptance of processing requests sent from peripheral nodes to the minimum necessary (rejection of acceptance). This makes it possible to maximize the processing capacity for continuing the call processing (service control) being executed in the congestion SCP. Note that, hereinafter, the restrictive measure triggered by the above-mentioned autonomous congestion control will be referred to as "autonomous restriction".

In the autonomous congestion control system of SCP currently used by Nippon Telegraph and Telephone Corporation for providing toll-free service and dial Q2 service, the congestion of SCP occurs before network congestion control becomes effective. If the status progresses, the SCP detects it when the processor usage rate, which is constantly measured by itself, exceeds the reference value, and uses this as a trigger to reject acceptance of a new call request. ing. In addition, regarding the known autonomous regulation / congestion control method, there are technologies represented by the following three patents. (1) "Control system for distributed control type electronic exchange" (Japanese Patent Laid-Open No. 61-1286)
(See Japanese Patent Publication No. 96) When an overload condition occurs in which the usage rate of control devices of multiple subsystems exceeds a reference value, a congestion signal is notified to other subsystems, and the outgoing connection trunk of the congestion subsystem is captured. Is a method to prevent. (2) "Distributed packet switch" (refer to Japanese Patent Laid-Open No. 3-217144) In a distributed packet switch in which a plurality of communication control modules are connected by a common bus, a communication proxy module is provided on the common bus, and each communication control module is provided. Is a method of detecting its own congestion state and causing the communication proxy module to perform processing for a new call. (3) "Distributed packet switch and communication control module
(See Japanese Patent Laid-Open No. 4-188930) In the above-mentioned distributed packet switch, when the communication control module is in a congestion state when a call request is made from the terminal, according to a predetermined circulation order. , A method in which another communication control module with a margin is substituted for the packet switching process.

[0004]

With the sophistication and customization of communication services, the functions required for the SCP become complicated, and the scale of the SCP gradually increases. Therefore,
It is assumed that the SCP in the IN is composed of one or more modules for each function so as to flexibly deal with the request for changing the function or scale. In the SCP composed of such a plurality of modules, the processing content (processing type) to be executed is different for each module constituting the SCP, and further, each module has a plurality of processing units (processing function units) according to its function. And the processing unit provided for each module is different. As described above, in an SCP composed of multiple modules, each module in the SCP is congested as a module (congestion at the module level) before the SCP is congested as a node (congestion at the node level).
A situation may arise in which In order to apply the conventional congestion control method to the SCP, it is necessary to consider not only the network regulation control or the autonomous regulation control focusing only on the node level congestion but also the control focusing on the module level congestion.

The above-mentioned autonomous congestion control in the SCP of Nippon Telegraph and Telephone Corporation corresponds only to the congestion at the node level, and all the methods disclosed in the above-mentioned three patents, One node has multiple modules (subsystem)
Although it is assumed that it is configured from the above, it is a method that limits the regulation target at the time of congestion to specific processing such as communication processing and call reception processing, and is specialized for limited systems. It is only an autonomous congestion control method. Therefore, these methods cannot be applied when there are various kinds of module-level processing executed in 1SCP and processing unit-level processing executed in each module.
The present invention has been made in view of the above circumstances, and an object of the present invention is to solve the above-mentioned problems in the related art, and the SCP in the IN is composed of a plurality of modules. It is an object of the present invention to provide an autonomous congestion control method in SCP that can be adopted even when there are various types of processing executed at the module level and the processing section level.

[0006]

The above object of the present invention comprises at least one SCP for controlling the execution of services for each call, and at least one network control node for centrally controlling the traffic in the network. In the IN, each of the SCPs is composed of one or more modules for each function, and the congestion state of a specific module in the SCP progresses, and the load state is the limit that can continue the call processing being executed in the module. In this case, in the SCP, the module autonomously regulates the execution of the processing request generated in the module to the minimum necessary, and the module and other modules cooperate with each other. , The processing request sent from the other module to the congested module is regulated to the necessary minimum, and the specific module or plural modules in the SCP are regulated. It proceeds congestion state of Lumpur, the S
When the load condition is such that the call processing being executed by the CP can be continued, the modules in the SCP cooperate with each other to autonomously minimize the execution of the processing request generated in the SCP. Characterized in that the reception of a processing request sent from outside the SCP to the SCP is autonomously restricted to the minimum necessary.
It is achieved by the autonomous congestion control method in.

[0007]

In the autonomous congestion control method in the SCP according to the present invention, by adopting the above configuration,
In order to guarantee the continuation of the call processing that is being executed by the module-level autonomy control when each module in the SCP has reached the limit load state that can guarantee the continuation of the processing that is being executed. The processing capacity as a module of can be secured to the maximum. Further, when the SCP having the above-mentioned module as a constituent element reaches a limit load state in which the continuation of the process being executed can be guaranteed, the autonomous regulation at the node level is activated and the node (SCP) executing the command is being executed. It is possible to maximize the processing capability as a node (SCP) for guaranteeing continuation of call processing.

[0008]

Embodiments of the present invention will be described below with reference to the drawings, and then embodiments will be described in detail with reference to the drawings.
First, clarify the prerequisites. As described above, the SCP that is the target of the autonomous congestion control method in the SCP according to the present invention is assumed to be composed of one or more modules for each function. Further, as in the conventional case, when it is determined that the SCP is congested as a node, the congested SCP notifies the network control node of the congestion, and the network control mainly of the network control node is activated. . The congestion state of the SCP that triggers the activation of this network regulation is the node level primary congestion (hereinafter referred to as "N level primary congestion").
I will call it. Note that the specific determination conditions for N-level primary congestion are outside the scope of the present invention.

When the SCP becomes the N level primary congestion,
Although the load of the SCP is considerably large, the function as a node (SCP) is not lost. The S
By limiting the processing request sent to the CP to the minimum required by the above-mentioned network regulation, normally, the SCP
The N-level primary congestion is eliminated without affecting the call processing being executed at. However, even if the processing request sent to the SCP is regulated by the network regulation as described above, it takes some time for the effect to appear. Therefore, if the load of the SCP rapidly increases during that time. In the, congestion status of the SCP further progresses, and finally the function as the node (SCP) cannot be maintained,
The process being executed cannot be continued. In such a case, it is assumed that the congestion SCP activates the autonomous regulation in its own node as in the conventional case. The congestion state of the SCP that triggers the activation of this autonomous regulation is called node-level secondary congestion (hereinafter referred to as "N-level secondary congestion").

Next, the handling of modules will be described. In order to judge that the SCP has become the N level primary congestion, the state of each module in the own node is grasped,
Judgment conditions that fully consider the function of each module and the importance (impact) in call processing are required. In the state of each module, which is an essential element for this determination condition, the state of module congestion is called module level primary congestion (hereinafter referred to as “M level primary congestion”). It is assumed that each module indirectly measures the load of its own module by the processor usage rate, the memory usage rate, or the like. The module is judged as M level primary congestion
Basically, it is when the load of the module exceeds the specified threshold, and this threshold is used as the module level primary congestion threshold (hereinafter, "M level primary congestion threshold").
Called).

As in the case where the SCP becomes the N level primary congestion, the following can be said. When the module becomes the M level primary congestion, the load on the module is considerably large, but the function as the module is not lost. By restricting the processing request sent to the module to the necessary minimum, the M level primary congestion is usually resolved without affecting the call processing being executed in the module. However, even if the above regulation is implemented, it takes some time for the effect to appear, so if the load on the module increases sharply during that time, the congestion status of the module further progresses and the final As a result, the function as a module cannot be maintained, and the process being executed cannot be continued. Therefore, the limit load state that can guarantee the continuation of the processing being executed in the module is called module level secondary congestion (hereinafter referred to as "M level secondary congestion"), and the load threshold that can detect it is It is called a module level secondary congestion threshold value (hereinafter referred to as "M level secondary congestion threshold value").

Each module constituting the SCP is classified into an essential module and a non-essential module in executing call processing. The former is called a call processing essential module and the latter is called a low importance module. . In addition, some of these modules include nodes (SC
It is assumed that there is a node management module that centrally maintains and manages all the modules in P), and this node management module is classified into a call processing essential module. Further, each module constituting the SCP is composed of a plurality of processing units, and each processing unit is classified into a processing unit indispensable for call processing and a processing unit other than the above processing units. Part and the latter will be referred to as a low importance processing part. In addition, among these processing units, there is a module management unit that centrally maintains and manages all the processing units in the module, and this module management unit is classified as a call processing essential processing unit. To do.

[0013] The restrictive measure activated by the autonomous congestion control method in the SCP according to the present invention is such that when a module in the SCP is determined to have M-level secondary congestion, the call processing being executed in the module is continued. In order to guarantee the maximum performance, the module level autonomous regulation (hereinafter referred to as "M level") that regulates the processing requests generated within the module and the transmission of processing requests from outside the module to the module to the minimum required. Autonomous regulation "), S
When the CP is determined to be N level secondary congestion, the SC concerned
In order to guarantee the continuation of the call processing being executed in P to the maximum extent, it is necessary to accept the processing requests that occur in the SCP and the various processing requests sent from outside the SCP to the SCP. There is a node level autonomous regulation (hereinafter referred to as "N level autonomous regulation").

The above-mentioned M level autonomous regulation and N level autonomous regulation will be described below. First, in the M level autonomous regulation, when a certain module becomes the M level secondary congestion, there are control performed by the module itself and control performed by each module other than the module. Intra-congestion module control, the latter is called secondary congestion module control. First, the control in the secondary congestion module will be described with reference to FIG. The module management unit of each module in the SCP measures the load of its own module and compares the measured value with the M level primary congestion threshold value and the M level secondary congestion threshold value at any time. M
When the level primary congestion threshold is exceeded, the node management module is notified to that effect. When the M level secondary congestion threshold is exceeded, the module management unit determines that the module itself has M level secondary congestion.
((1) in FIG. 10) to notify the node management module to that effect ((2) in FIG. 10), and restricts execution of a new processing request to each call processing essential section in the own module. To do so ((3) in FIG. 10).

Further, each low-importance processing unit in its own module is instructed to restrict execution of all processing requests.
((3) in FIG. 10). Here, the new processing request refers to something other than the processing required to continue the call processing that was being executed when the module was determined to have M level secondary congestion. Even if the call processing essential portion and the low importance processing portion receive a regulation instruction, transmission / reception of a control signal to / from the module management portion is not regulated. Next, the secondary congestion module control will be described with reference to FIG. When the node management module in the SCP is notified that a certain module has become M level secondary congestion ((1) in FIG. 11),
Determine whether N-level secondary congestion will occur ((2) in FIG. 11)
However, if it is not judged as the N level secondary congestion, the M
The call processing indispensable modules other than the level secondary congestion module are instructed to restrict the transmission of a new processing request to the relevant module, that is, the M level secondary congestion module ((3) in FIG. 11). Similarly, each low importance module is instructed to restrict the transmission of all processing requests to the module (M level secondary congestion module) ((3) in FIG. 11).

In each module that has received these restrictions, the module management section of each module instructs each processing section in its own module to enforce the previous restrictions. Here, the new processing request is any request other than the processing request necessary for continuing the call processing being executed in the module when each module receives the above-mentioned regulation instruction from the node management module. Point to. It should be noted that neither the call processing essential module nor the low importance module does not restrict transmission / reception of a control signal to / from the node management module even when receiving the previous restriction instruction. Next, the N-level autonomous regulation will be described based on FIG. When the node management module in the SCP is notified that a certain module has become M level secondary congestion ((1) in FIG. 12),
It is determined whether or not the level secondary congestion will occur ((2) in FIG. 11),
When it is determined that the congestion is the N-level secondary congestion, the N-level autonomous regulation as described below is activated. Here, the N level secondary congestion determination condition is the number of modules in the M level primary congestion state or the M level secondary congestion state, whether the module is a call processing essential module or a low importance module, and the function of the module is normal. It is set based on information such as whether another module in the state can be replaced. Note that specific conditions for the N-level secondary congestion determination will be shown in the examples.

The node management module, which has determined that the own node is in the N-level secondary congestion state, instructs each call processing essential module in the own node to regulate the execution and reception of the new processing request, and each low importance The execution and reception of all processing requests are regulated for each module. Here, the above-mentioned new processing request refers to a processing request other than the processing request necessary for continuing the call processing that was being executed when the node was determined to be in the N-level secondary congestion state. Even if the call processing essential module and the low importance module receive the previous restriction instruction, the control signal transmission / reception to / from the node management module is not restricted, as in the case described above. To summarize the above, by adopting the autonomous congestion control method in the SCP according to the present invention,
When each module in the M level secondary congestion state is activated, the M level autonomous regulation is activated, and the processing capability as a module for guaranteeing the continuation of the call processing being executed in the M level secondary congestion module. Can be secured to the maximum.

Further, S having the above module as a constituent element
Processing capability as a node (SCP) for guaranteeing the continuation of the call processing being executed by the N-level secondary congestion SCP when the CP enters the N-level secondary congestion state when the N-level autonomous regulation is activated. Can be secured to the maximum. Less than,
An embodiment of the present invention will be described with reference to the drawings. FIG. 1 is an SC that employs an autonomous congestion control method according to an embodiment of the present invention.
It shows an example of the configuration of IN including P, and shows only the portion related to autonomous congestion control and network congestion control. In the figure, 101 is a SCP, 102 is a network control node, 103 is a service switching node (hereinafter referred to as “SSP”), 104 is a terminal such as a telephone terminal, and each of a plurality of terminals 104 is accommodated in a specific SSP 103. , Each S
The SP 103 is a transmission network such as a common line signal network and is connected to each other. Further, each SCP 101 in the network is mutually connected to one or more SSPs 103 by a transmission network such as a common line signaling network. In addition, all SCP10
1, the SSP 103 is connected to the network control node 102 via an information transfer network such as a packet transfer network.

FIG. 2 shows an example of the structure of the SCP 101 composed of a plurality of modules. In the figure, 201 is a node management module (Mk-1), 202-
Reference numeral 204 denotes call processing essential modules (Mk-2 to Mk-m) other than the node management module, and 205 to 206 denote low importance modules (Mt-1 to Mt-n). The node management module 201 is also classified as a call processing essential module. The node management module 201 includes all modules 202 to 2 in the SCP 101 including the module.
06 and control signals can be transmitted and received. Call processing essential modules 201-204 and low importance module 205
The classification of ~ 206 depends on the function of each module. For example, the idea that a module accessed in executing call processing is a low importance module, or even a module accessed in call processing is There is a concept such as a module with a low importance level that does not impair the serviceability to the customer when the processing in the module is omitted, and it is necessary to perform the optimal classification according to the SCP configuration.

FIG. 3 shows an internal structure of a module common to the modules 201 to 206 in the SCP 101 shown in FIG. In the figure, 302 is a module management unit (Sk-1), and 303 to 305 are call processing essential units (Pk-).
2 to Pk-i) and 306 to 307 are low importance processing units (Pt-1).
~ Pt-j). The module management unit 30
2 is also classified as a call processing essential part. In addition, the module management unit 302 is responsible for all the processing units 30 in its own module.
3 to 307 and control signals can be transmitted and received. FIG. 4 is a flowchart of the processing unit level in the module management unit in the module in the M level secondary congestion state, and the process until the module enters the M level secondary congestion state and the M level autonomous regulation is activated. Of the M level secondary congestion module control (within the broken line frame in the figure)
It shows the positioning of. In the figure, L is the load of the module, Xon1 is the M level primary congestion threshold of the module, and Xon2 is the M level secondary congestion threshold of the module.

The operation will be described below with reference to FIG.
First, it is assumed that the module management unit 302 constantly monitors the load applied to its own module by measuring the processor usage rate and memory usage rate of its own module. Then, every time L is measured (step 11), L
With Xon1 and Xon2 (step 12). In this comparison, when L <Xon1, steps 11 and 12 are repeated. In the comparison of step 12, Xon1 <L <Xon2
In the case of, it is judged as M level primary congestion, and step 1
In step 3, the M-level primary congestion notification is output to the node management module, and thereafter steps 11 and 12 are repeated. If Xon2 <L in the comparison in step 12, it is determined that the congestion is M level secondary congestion, and in step 14, an M level secondary congestion notification is output to the node management module to process all calls in the own module. Issuing new processing request regulation instructions to essential parts
(Step 15) Further, all processing request regulation instructions are issued to all low importance processing units in the own module (Step 16).

FIG. 5 is a flowchart of the processing section level of the autonomous regulation (control within the M level secondary congestion module) in each call processing essential section of the module in the M level secondary congestion state. The operation will be described below with reference to FIG. When a new processing request regulation instruction is received from the module management unit (step 21), execution regulation and acceptance regulation of the new processing request other than transmission and reception of a control signal with the module management unit are started (step 22). FIG. 6 is a processing unit level flowchart of autonomous regulation (control within the M level secondary congestion module) in each low importance processing unit of the module in the M level secondary congestion state. The operation will be described below with reference to FIG. Upon receiving the instruction for restricting all processing requests from the module management unit (step 31), execution restriction and reception restriction of all processing requests other than transmission and reception of control signals with the module management unit are started (step 32).

FIG. 7 is a module-level flowchart in the node management module. When a module in the SCP receives a notification indicating that the module is in the M-level secondary congestion state, the M-level autonomous regulation for the module and It shows the flow of N level autonomous regulation when it is determined that the own node (SCP) is in the N level secondary congestion state by the above notification. Hereinafter, description will be given with reference to FIG. 7. When the M level primary congestion notification is received from a certain module (step 41) and it is determined that the N level primary congestion is detected (step 42), the N level primary congestion notification is sent to the network control node (step 43). Further, when the M level secondary congestion notification is received from a certain module (step 44), it is checked whether or not the N level secondary congestion determination condition is satisfied (step 45). When the condition is satisfied, it is determined to be N level secondary congestion. Here, as the N-level secondary congestion determination condition, for example, "one or more modules in which no alternative processable module exists in the node is M level secondary congestion, or the alternative processable module is a node In the case where a certain number or more of modules within the same type of module group in the module have M-level secondary congestion ”, etc.

If it is not judged as N level secondary congestion in the judgment of step 45, it is judged as M level autonomous regulation.
A new processing request regulation instruction for the M level secondary congestion module is issued to the all call processing essential module (step 46),
All processing request regulation instructions for the M level secondary congestion module are issued to all low importance modules (step 47). On the other hand, when it is determined that the congestion is the N-level secondary congestion in the determination in step 45, as a N-level autonomous regulation, a new processing request regulation instruction is issued to the all call processing essential module.
(Step 48), all processing request regulation instructions are issued to all low importance modules (Step 49). The processing request regulation here includes both the execution regulation and the transmission regulation of the processing request.
FIG. 8 is a module-level flowchart in each call processing essential module (other than the node management module), showing the flow of M-level autonomous regulation and N-level autonomous regulation that are executed according to the instruction from the node management module. is there.

Hereinafter, description will be made with reference to FIG. When the node management module receives a restriction instruction to send a new processing request to the M-level secondary congestion module (step 51), the restriction according to the above instruction is started in step 52. This corresponds to M-level autonomous regulation (against M-level secondary congestion module control). When the all-new processing request regulation instruction is received from the node management module (step 53), the all-new processing request execution regulation and the transmission regulation are started in accordance with the instruction (step 54). However,
Control signal transmission / reception with the node management module is not regulated. FIG. 9 is a module-level flowchart for each low-importance module, and shows the flow of M-level autonomous regulation and N-level autonomous regulation that is executed according to an instruction from the node management module. Hereinafter, description will be given with reference to FIG. If the node management module receives a restriction instruction to send all processing requests to the M-level secondary congestion module (step 61), the restriction according to the above instruction is started (step 62). This corresponds to M-level autonomous regulation (against M-level secondary congestion module control).

When an instruction for restricting all processing requests is received from the node management module (step 63), execution restriction and sending restriction for all processing requests are started in step 64 according to the above instruction. However, control signal transmission / reception with the node management module is not restricted. According to the above embodiment, the SCP
The M level autonomous regulation is activated when each module in the M level secondary congestion state is activated, and the processing capacity as a module for ensuring the continuation of the call processing being executed by the M level secondary congestion module is maximized. The effect of being able to secure the limit is obtained. In addition, when the SCP enters the N level secondary congestion state, the N level autonomous regulation is activated,
The effect that the processing capacity as a node for guaranteeing the continuation of the call processing being executed in the level second congestion SCP can be secured to the maximum is obtained. It is needless to say that the above embodiment shows one example of the present invention, and the present invention should not be limited to this.

[0027]

As described above in detail, according to the present invention, the SCP in IN is composed of a plurality of modules, and each module is composed of a plurality of processing units. The remarkable effect that the autonomous congestion control method in the SCP that can be adopted even when there are various types of processing executed by each is realized.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration example of an IN including an SCP adopting an autonomous congestion control method according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating a configuration example of an SCP configured by a plurality of modules.

FIG. 3 is a diagram showing a module internal configuration common to each module in the SCP shown in FIG.

FIG. 4 is a flowchart of a processing unit level in a module management unit in a module in an M level secondary congestion state.

FIG. 5 is a flowchart of a processing unit level of autonomous regulation in each call processing essential unit of the module in the M level secondary congestion state.

FIG. 6 is a flowchart of a processing unit level of autonomous regulation in each low importance processing unit of the module in the M level secondary congestion state.

FIG. 7 is a module-level flowchart in the node management module.

FIG. 8 is a module-level flowchart in each call processing essential module (other than the node management module).

FIG. 9 is a module-level flowchart for each low importance module.

FIG. 10 is a diagram showing an overall flow of M-level autonomous regulation (M-level secondary congestion module control).

FIG. 11 is a diagram showing an overall flow of M level autonomous regulation (against M level secondary congestion module control).

FIG. 12 is a diagram showing an overall flow of N-level autonomous regulation.

[Explanation of symbols]

101 SCP 102 Network control node 103 Service switching node (SSP) 104 Terminal 201 Node management module 202 to 204 Call processing required module other than node management module 205 to 206 Low importance module 302 Module management unit 303 to 305 Other than module management unit Call processing essential part 306-307 Low importance processing part

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Masanobu Yoshimi 1-1-6 Uchisaiwai-cho, Chiyoda-ku, Tokyo Nihon Telegraph and Telephone Corporation (72) Toshinori Suzuki 1-17-1 Toranomon, Minato-ku, Tokyo Oki Electric Industry Co., Ltd.

Claims (1)

[Claims] 1. An intelligent network comprising one or more service control nodes (SCP) for controlling the execution of services for each call and one or more network control nodes for centrally controlling traffic in the network, Each SCP is composed of one or more modules for each function, and the congestion state of a specific module in the SCP progresses (deteriorates), and the limit of the call processing (service control) being executed by the module can be continued. When the load (operating) state is reached, the S
In the CP, the module autonomously regulates the execution of the processing request generated in the module to the minimum necessary, and the module and the other module cooperate with each other, so that the congestion from the other module occurs. Limits the processing requests sent to the current module to the minimum necessary, and the congestion status of a specific module or multiple modules in the SCP progresses and the call processing being executed by the SCP can continue. In the case of the load state of, the respective modules in the SCP cooperate with each other to autonomously regulate the execution of the processing request generated in the SCP to the minimum necessary, and the SCP from outside the SCP.
An autonomous congestion control method in the SCP, characterized in that the acceptance of a processing request sent to the device is autonomously regulated to a necessary minimum.