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

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a service control node in an intelligent network (hereinafter referred to as "IN").
The autonomous congestion control method in the following (hereinafter referred to as "SCP"), particularly assuming that the SCP in IN is composed of a plurality of modules, and when a certain SCP becomes congested, a node (network) that centrally controls traffic in the network If the congestion state of the SCP further progresses (deteriorates) before the effect of the network traffic control (regulation) triggered by the (control node) appears, the SCP during the congestion automatically becomes appropriate within its own node. The present invention relates to an autonomous congestion control method in an SCP that implements various restrictive measures and ensures the maximum processing capability for continuing the ongoing call processing (service control).

[0002]

2. Description of the Related Art Conventionally, as a method of congestion control of an SCP in an IN, a network congestion control (hereinafter referred to as a network congestion control) mainly performed by a network control node for centrally controlling traffic in the network has been proposed. Before the effect of the network congestion control appears, if the congestion state of the SCP further progresses, the SCP during the congestion executes itself within its own node. Congestion control (hereinafter referred to as “autonomous congestion control”). The outline of the network congestion control described above is as follows:
When the load (operating) state of the CP exceeds a specified value, the SCP (hereinafter, referred to as “congestion SCP”) notifies the network control node of the fact, and the network control node receiving the notification notifies the network control node of the congestion. This is to instruct another peripheral node that sends a processing request to the SCP, to regulate sending of the processing request to the congested SCP. As a result, the number of processing requests sent to the congestion SCP is reduced, and congestion is resolved. In the following, the control measures triggered by the above-described network congestion control are referred to as “network controls”. 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 and the call processing (service control) being executed by the congestion SCP cannot be continued, the congestion SCP becomes autonomous. The reception of processing requests sent from peripheral nodes is restricted (rejected) to the minimum necessary. As a result, it is possible to ensure the maximum processing capability for continuing the call processing (service control) being executed in the congested SCP. In the following, the control measures triggered by the above-described autonomous congestion control are referred to as “autonomous control”.

[0003] In the autonomous congestion control method of SCP currently used for providing free dial service and dial Q2 service by Nippon Telegraph and Telephone Corporation, the congestion of SCP becomes effective before network congestion control becomes effective. When the state progresses, the SCP uses the method of detecting the processor usage rate, which is constantly measuring itself, when it exceeds the reference value, and rejecting the acceptance of a new call request upon this. ing. Further, as for the known autonomous regulation congestion control method, there are techniques represented by the following three patents. (1) "Control method of distributed control type electronic exchange" (JP-A-61-1286)
In the case of an overload state in which the usage rates of the control devices of a plurality of subsystems exceed a reference value, a congestion signal is notified to another subsystem, and the outgoing connection trunk of the congested subsystem is captured. It is a method to block. (2) "Distributed packet switch" (refer to JP-A-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 a method in which a congestion state is detected and the communication proxy module performs proxy processing for a new call. (3) "Distributed packet switch and communication control module
(See Japanese Patent Application Laid-Open No. Hei 4-188930) In the above-described distributed packet switch, when a call request is issued from a terminal, if the communication control module is in a congested state, a predetermined circulation order is followed. This is a method in which another spare communication control module performs the packet switching process.

[0004]

With the advancement and customization of communication services, the functions required of the SCP become complicated and the scale of the SCP gradually increases. Therefore,
It is assumed that the SCP in IN is composed of one or more modules for each function so as to flexibly respond to a request for a change in function or scale. In the SCP composed of a plurality of modules, the processing content (processing type) to be executed differs for each module constituting the SCP, and each module has a plurality of processing units (processing function units) according to its function. And the processing units provided for each module are different. As described above, in the SCP including a plurality of modules, each module in the SCP is congested as a module (module-level congestion) before the SCP congests as a node (node-level congestion).
Situation can occur. In order to apply the conventional congestion control method to the SCP, it is necessary to consider not only the network regulation control and the autonomous regulation control focusing only on the node-level congestion but also the control focusing on the module-level congestion.

The autonomous congestion control in the above-mentioned SCP of Nippon Telegraph and Telephone Corporation only responds to congestion at the node level, and any of the methods disclosed in the above three patents is: One node has multiple modules (subsystems)
Although it is assumed that the system is configured from the above, it is a method that restricts the target of congestion occurrence to specific processing such as communication processing and reception processing of call request, specialized in limited systems Only an autonomous congestion control method. Therefore, these methods cannot be applied when there are various types of module-level processing executed in one SCP and processing-unit-level processing executed in each module.
The present invention has been made in view of the above circumstances, and has as its object to solve the above-mentioned problems in the prior art, SCP in IN is composed of a plurality of modules, further, each module number multiple It is an object of the present invention to provide an autonomous congestion control method in an SCP which can be employed even when there are various types of processing to be executed at each of a module level and a processing unit level.

[0006]

SUMMARY OF THE INVENTION An object of the present invention is to provide at least one service control node (SCP) for controlling the execution of a service for each call, and to centrally control traffic in a network.
In an automatic congestion control method in SCP of an intelligent network having at least one network control node,
The SCP is configured from one or more respective modules for each function, congestion status of a particular module in the SCP is progress, load status of the limit can continue Kosho management running in the module Becomes, in the SCP, the module is generated in the module.
Execution of new processing requests with processor usage and memory usage
Autonomously regulated so that the rate is equal to or less than a predetermined value, also, the other mode
Module to the congested module.
Processor usage and memory usage
If the load is restricted to a certain value or less, and congestion of a specific module or a plurality of modules in the SCP progresses, and the load becomes a limit that can continue the call processing being executed in the SCP, the SCP New processing that occurs within
All requests for processing requests sent from outside the SCP to the SCP.
This is achieved by a self-autonomous congestion control method in the SCP, which is characterized in that it is regulated by using

[0007]

In the autonomous congestion control method in the SCP according to the present invention, by adopting the above configuration,
When each module in the SCP is in a limit load state that can guarantee the continuation of the processing being executed, autonomous regulation at the module level is activated to guarantee the continuation of the call processing being executed in the module. The maximum processing capability as a module can be secured. Further, when the SCP having the above-described module as a component is in a limit load state that can guarantee the continuation of the processing being executed, autonomous regulation at the node level is activated, and the The processing capability as a node (SCP) for guaranteeing the continuation of call processing can be secured to the maximum.

[0008]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The outline of the present invention will be described below with reference to the drawings, and the embodiments will also be described in detail with reference to the drawings.
First, the preconditions are clarified. As described above, it is assumed that the SCP to be subjected to the autonomous congestion control method in the SCP according to the present invention includes 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 congestion, and the network control mainly by the network control node is activated. . The congestion state of the SCP that triggers this network regulation is referred to as node-level primary congestion (hereinafter referred to as “N-level primary congestion”).
I will call it. Note that specific conditions for determining the N-level primary congestion are out of the scope of the present invention.

When the SCP becomes N-level primary congestion,
Although the load of the SCP is considerably increased, the function as the node (SCP) is not lost. The S
By restricting the processing request sent to the CP to the minimum required by the above network regulation, the
The N-level primary congestion is resolved without affecting the call processing being executed at the N. However, even if the processing request sent to the SCP is regulated by the network regulation as described above, it takes some time until the effect appears, and during that time, the load of the SCP suddenly increases. The congestion situation of the SCP further progresses, and eventually 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 autonomous regulation in its own node as in the related art. The SCP congestion state that triggers the autonomous regulation is called node-level secondary congestion (hereinafter, referred to as “N-level secondary congestion”).

Next, handling of modules will be described. In order to determine that the SCP has become the N-level primary congestion, the state of each module in the own node is grasped,
Judgment conditions that sufficiently consider the function of each module and the importance (influence) in call processing are required. In the state of each module, which is an essential element for this determination condition, a state in which the module is congested is referred to as module-level primary congestion (hereinafter, referred to as “M-level primary congestion”). For each module, the load of its own module is
And indirectly measured by the memory usage rate and the like. A module is determined to be at the M-level primary congestion basically when the load of the module exceeds a specified threshold. , "M-level primary congestion threshold").

[0011] As in the case where the SCP becomes N-level primary congestion, the following can be said. When the module becomes M-level primary congestion, the load of the module is considerably increased, but the function as the module is not lost. By regulating the processing requests sent to the module to the minimum necessary, the M-level primary congestion is usually resolved without affecting the call processing being executed in the module. However, even if the above regulations are implemented, it takes some time for the effects to appear, and during that time, if the load on the module suddenly increases, the congestion situation 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 by 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 referred to as a module level secondary congestion threshold (hereinafter, referred to as “M level secondary congestion threshold”).

Each module constituting the SCP is classified into a module essential for performing call processing and a module not required for performing the call processing. The former is referred to as a call processing essential module, and the latter is referred to as a low importance module. . Some of these modules include a node (SC
It is assumed that there is a node management module that centrally manages and manages all modules in P), and this node management module is classified as a call processing essential module. Each module constituting the SCP is composed of a plurality of processing units, and each processing unit is classified into a processing unit essential for call processing and other processing units. And the latter will be referred to as a low importance processing unit. Also, among these processing units, there is a module management unit that centrally manages and manages all processing units in the module, and this module management unit is classified as a call processing essential processing unit. I do.

[0013] The control measures triggered by the autonomous congestion control method in the SCP according to the present invention include, when a certain module in the SCP is determined to be M-level secondary congestion, the call processing being executed by the module is continued. Module level autonomous regulation (hereinafter referred to as “M level”) that regulates processing requests generated within the module and transmission of processing requests from the outside of the module to the module to the minimum necessary to ensure the maximum Autonomous regulation)) and S
If the CP is determined to be N-level secondary congestion, the SC
In order to guarantee the continuation of the call processing being executed in P to the utmost, the reception of processing requests generated within the SCP and various processing requests sent from outside the SCP to the SCP is minimized. There is a node-level autonomous regulation (hereinafter, referred to as “N-level autonomous regulation”).

The above-described 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 M-level secondary congestion, there are a control performed by the module itself and a control performed by each module other than the module. The control within the congestion module, the latter is called anti-secondary congestion module control. First, the control within 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 and the M-level secondary congestion threshold as needed. M
When the level primary congestion threshold is exceeded, the fact is notified to the node management module. If the M-level secondary congestion threshold is exceeded, the module management unit determines that the own module has become the M-level secondary congestion.
((1) in FIG. 10), the node management module is notified of this ((2) in FIG. 10), and execution of a new processing request is restricted for each call processing essential part in the own module. ((3) in FIG. 10).

Further, each low importance processing section in its own module is instructed to restrict execution of all processing requests.
((3) in FIG. 10). Here, the new process request refers to a process other than the process required to continue the call process being executed when the module is determined to be at the M-level secondary congestion. Even if both the call processing essential unit and the low importance processing unit receive the restriction instruction, the transmission and reception of the control signal with the module management unit are not restricted. Next, the control of the secondary congestion module 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 or not N-level secondary congestion occurs ((2) in FIG. 11)
However, if it is not determined that the N-level secondary congestion, the M
For each call processing essential module other than the level secondary congestion module, an instruction is issued ((3) in FIG. 11) to regulate the transmission of a new processing request to the module, that is, the M level secondary congestion module. Similarly, each low importance module is instructed to regulate the transmission of all processing requests to the module (M-level secondary congestion module) ((3) in FIG. 11).

In each of the modules that have received these restrictions, the module management unit of each module instructs each processing unit in the module to perform the previous restrictions. Here, the new processing request is defined as a request other than a processing request necessary for continuing the call processing being executed in the module at the time when each module receives the above-described regulation instruction from the node management module. Point. Even if both the call processing essential module and the low importance module receive the previous restriction instruction, the transmission and reception of the control signal with the node management module are not restricted. Next, N-level autonomous regulation 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. 12),
It is determined whether or not level secondary congestion occurs ((2) in FIG. 11),
When it is determined that the N-level secondary congestion occurs, the following N-level autonomous regulation is activated. Here, the N-level secondary congestion determination condition includes 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 whether the function of the module is normal. It is set based on information such as whether or not the state can be replaced by another module. The specific conditions for the N-level secondary congestion determination will be described in Examples.

The node management module, which has determined that its own node is in the N-level secondary congestion state, instructs each call processing essential module in its own node to regulate execution and acceptance of a new processing request, and The execution and acceptance of all processing requests are restricted 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 being performed when the node is determined to be in the N-level secondary congestion state. It should be noted that both the call processing essential module and the low importance module receive the previous restriction instruction, but do not restrict transmission and reception of control signals with the node management module, 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, the SCP
When each of the modules is in the M-level secondary congestion state, the M-level autonomous regulation is activated, and the processing capacity as a module for guaranteeing the continuation of the call processing being executed by the M-level secondary congestion module Can be maximized.

Further, S which has the above-mentioned module as a constituent element
When the CP enters the N-level secondary congestion state, the N-level autonomous regulation is activated, and the processing capability as a node (SCP) for guaranteeing the continuation of the call processing being executed in the N-level secondary congestion SCP Can be maximized. Less than,
An embodiment of the present invention will be described with reference to the drawings. FIG. 1 illustrates an SC adopting an autonomous congestion control method according to an embodiment of the present invention.
It shows a configuration example of an IN including P, and extracts and shows only portions related to autonomous congestion control and network congestion control. In the figure, 101 is an 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 the plurality of terminals 104 is accommodated in a specific SSP 103. , Each S
The SP 103 is a transmission network such as a common channel signal network, and is connected to each other. Each SCP 101 in the network is mutually connected to one or more SSPs 103 by a transmission network such as a common channel signal 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 a configuration example of the SCP 101 composed of a plurality of modules. In the figure, reference numeral 201 denotes a node management module (Mk-1);
Reference numeral 204 denotes a call processing essential module (Mk-2 to Mk-m) other than the node management module, and reference numerals 205 to 206 denote low importance modules (Mt-1 to Mt-n). Note that the node management module 201 is also classified as a call processing essential module. The node management module 201 includes all the 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
Classifications of to 206 are determined by the functions of each module. For example, even if a module accessed in executing call processing is considered to be a low importance module or a module accessed in call processing, If the serviceability to the customer is not impaired when the processing in the module is omitted, there is a concept such as a low importance module, and it is necessary to perform an optimal classification according to the SCP configuration.

FIG. 3 shows an internal configuration of a module common to each of 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 includes all the processing units 30 in the own module.
It is configured to transmit and receive control signals to and from 3 to 307. FIG. 4 is a flowchart at the processing unit level in the module management unit in the module in the M-level secondary congestion state, and shows the processing until the module is in the M-level secondary congestion state and the M-level autonomous regulation is activated. Of these, control within the M-level secondary congestion module (within the dashed box in the figure)
It shows the position 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 the own module by measuring the processor usage rate and the memory usage rate of the own module. Then, every time L is measured (step 11)
Then, L is compared with Xon1 and Xon2 (step 12). If L <Xon1 in this comparison, steps 11 and 12 are repeated. In the comparison of step 12, Xo
If n1 <L <Xon2, it is determined that the M-level primary congestion occurs, and an M-level primary congestion notification is output to the node management module in step 13, and thereafter, steps 11 and 12 are repeated. Also, in the comparison in step 12, Xon2 <L
In the case of, it is determined that M-level secondary congestion occurs, and
In step 4, an M-level secondary congestion notification is output to the node management module, a new processing request restriction instruction is issued to all call processing essential parts in the own module (step 15). An all-process-request restriction instruction is issued to the processing unit (step 16).

FIG. 5 is a flowchart at the processing unit level of autonomous regulation (control within the M-level secondary congestion module) in each call processing essential unit of the module in the M-level secondary congestion state. Hereinafter, the operation will be described with reference to FIG. When a new process request regulation instruction is received from the module management unit (step 21), regulation of execution and acceptance of a new process request other than transmission and reception of a control signal with the module management unit is started (step 22). FIG. 6 is a flowchart at the processing unit level of the 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. Hereinafter, the operation will be described with reference to FIG. When an all processing request regulation instruction is received from the module management unit (step 31), execution regulation and acceptance regulation 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 certain module in the SCP receives a notification that the M-level secondary congestion has occurred, the M-level autonomous regulation for the module is performed, and It shows the flow of N-level autonomous regulation when it is determined by the above notification that the own node (SCP) has entered the N-level secondary congestion state. Hereinafter, description will be given based on FIG. An M-level primary congestion notification is received from a certain module (step 41), and when it is determined that the N-level primary congestion is present (step 42), an N-level primary congestion notification is made to the network control node (step 43). When an M-level secondary congestion notification is received from a certain module (step 44), it is checked whether or not an N-level secondary congestion determination condition is satisfied (step 45). If the condition is satisfied, it is determined that N-level secondary congestion is present. Here, the N-level secondary congestion determination condition may be, for example, “one or more modules in which no alternative processable module exists in the node become M-level secondary congestion, Or more than a prescribed number of modules of the same type of modules existing in the M-level secondary congestion "may be considered.

If the N-level secondary congestion is not determined in step 45, the M-level autonomous regulation is performed as follows:
A new processing request regulation instruction for the M-level secondary congestion module is issued to all the call processing essential modules (step 46).
An instruction to restrict all processing requests for the M-level secondary congestion module is issued to all low importance modules (step 47). On the other hand, when it is determined that the N-level secondary congestion is determined in the above-described step 45, a new processing request restriction instruction is issued to all call processing essential modules as N-level autonomous restriction.
(Step 48), an instruction for restricting all processing requests is issued to all low importance modules (Step 49). Here, the processing request regulation includes both the execution restriction 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), and shows the flow of the M-level autonomous regulation and the N-level autonomous regulation performed in accordance with an instruction from the node management module. is there.

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

If an all processing request regulation instruction is received from the node management module (step 63), execution restriction and transmission regulation of all processing requests are started in step 64 according to the instruction. However, transmission / reception of control signals with the node management module is not restricted. According to the above embodiment, the SCP
The M-level autonomous regulation is activated when each of the modules in the M-level becomes in the M-level secondary congestion state, and the processing capacity as a module for guaranteeing the continuation of the call processing being executed by the M-level secondary congestion module is maximized. The effect is obtained that the maximum length can be secured. When the SCP enters the N-level secondary congestion state, the N-level autonomous regulation is activated, and the N-level
The effect is obtained that the processing capacity as a node for guaranteeing the continuation of the call processing being executed in the level secondary congestion SCP can be maximized. It should be noted that the above embodiment is an example of the present invention, and it is needless to say that the present invention is not limited to this.

[0027]

As described in detail above, 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. This has a remarkable effect that the autonomous congestion control method in the SCP can be realized, which can be adopted even when there are various types of processing to be executed.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating 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. 2;

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

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

FIG. 6 is a flowchart at a processing unit level of autonomous regulation in each low importance processing unit of a module in an 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 the overall flow of M-level autonomous regulation (M-level secondary congestion module control).

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

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

[Explanation of symbols]

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

──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Masanobu Yoshimi 1-1-6 Uchisaiwaicho, Chiyoda-ku, Tokyo Nippon Telegraph and Telephone Corporation (72) Inventor Toshinori Suzuki 1-7-112 Toranomon, Minato-ku, Tokyo (56) References JP-A-62-11355 (JP, A) JP-A-5-22406 (JP, A) (58) Fields investigated (Int. Cl. ⁷ , DB name) H04M 3/22

Claims (1)

(57) [Claims] 1. An intelligent network SCP comprising at least one service control node (SCP) for controlling execution of a service for each call and at least one network control node for centrally controlling traffic in the network . Automatic congestion control
In our method, the SCP is composed from one or more respective modules for each function, and line congestion is advanced a particular module in the SCP, the limit can continue Kosho management running in the module when it becomes load-shaped on purpose, within the SCP, the module occurs within the module
Execution of new processing requests with processor usage and memory usage
Autonomously regulated so that the rate is equal to or less than a predetermined value, also, the other mode
Module to the congested module.
Processor usage and memory usage
If the load is restricted to a certain value or less, and congestion of a specific module or a plurality of modules in the SCP progresses, and the load becomes a limit that can continue the call processing being executed in the SCP, the SCP New processing that occurs within
All requests for processing requests sent from outside the SCP to the SCP.
Own autonomous congestion control method in the SCP, characterized in that the regulating Te.