JPH098907A - Load limit control system for central management control network - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize a load limit control system for a central management control network in which overload control is made efficient in response to a cause to occurrence of an overload of a central management controller so as to avoid and prevent the occurrence of the over load state in the load limit control system for a central management control network. SOLUTION: A central management controller 10 decides a limiting rate based on data relating to various load information and starts one of limit processing sections 1-3 for an inquiry execution device 20. The limit processing 1 restricts the load based on the limiting rate and informs the result to the inquiry execution device 20. The limit processing 2 restricts the load without notice. The limit processing 3 sends the limiting rate to the inquiry execution devie 20, by which the load is limited.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a load control system for a centralized management / control type network, and more particularly to a centralized management / control device in a centralized management / control type network for collectively controlling and controlling data collectively. The present invention relates to a load regulation control system for a centralized management / control type network that avoids or prevents the overload state of the network.

The centralized management / control type network performs network control to support the realization of an advanced information society required by society, and centrally manages each inquiry execution device by the centralized management / control device. Thus, even if a new service request occurs in the future, the request can be easily met. In a centralized management / control type network, inquiries to the centralized management / control unit are concentrated in the short term due to the nature of the network that there is only one centralized management / control unit. The processing capacity is lowered, and in the worst case, there is a possibility that the system will be inoperable due to a system failure.

Therefore, the centralized control / control device can automatically or manually control so as to avoid an overload state, or prevent an overload when an overload state is predicted in advance. It is possible to prevent the occurrence of abnormal situations by
It is necessary and essential in a controlled network.

[0004]

2. Description of the Related Art As an overload control method in a centralized control / control type network, an Automatic Call Gapping (ACG) method generally advocated by Bellcore is given as a method adapted to an intelligent network. To be The ACG method is based on the load status of the centralized management / control device (also called the service control point).
The central management / control device notifies the inquiry execution device (also referred to as a service exchange point) of the regulation time (for example, 3 seconds), and the inquiry execution device keeps the central management / control device until the regulation time elapses. It is a method of not inquiring to.

The conventional centralized control / control device provides a load monitoring control section for monitoring the traffic state of the network and its own load state to determine a regulation time according to the traffic / load state, and a load monitoring control section. It is composed of a load processing section that regulates each inquiry execution device in response to the regulated time. A database that stores various service control data (for example, service control data regarding a freephone service) is connected to the centralized management / control device.

To the centralized management / control device, a plurality of inquiry execution devices (also referred to as service exchange points) for executing inquiry processing regarding various services are connected. A central office switch is connected to the inquiry execution device, a subscriber terminal and a private branch exchange (PBX) are connected to the central office exchange, and an extension terminal is connected to the private branch exchange. An inquiry execution device may be provided in the central office switch.

In the system constructed as above,
When an inquiry is made from a certain query execution device to the centralized management / control device, the load processing unit in the centralized management / control device searches the database for service control data. At the same time, the load monitoring control unit determines the regulation time based on the traffic state of the network and its own load state, and notifies the load processing unit. The load processing unit returns a response to the inquiry execution device that has made the inquiry, and notifies the regulation time from the next time. The inquiry execution unit will perform centralized management / control during the notified regulation time.
Do not inquire the control device.

[0008]

In the above-mentioned conventional system, there is a problem that effective load control may not be possible as described below. (I) Since the decision logic of the condition for calculating the effective regulation time is complicated, the processing load becomes large because the regulation processing is performed.

(Ii) In the method of controlling the load by the regulation time, excessive regulation is applied, and even inquiries that should normally be controlled by the centralized management / control device are regulated, which may deteriorate serviceability. . This tendency becomes particularly strong when the number of inquiry execution devices controlled by the centralized management / control device is small. (Iii) In the method of controlling the load by the regulation time, since the centralized management / control device inquiries again after the lapse of the regulation time, the overload condition cannot be avoided successfully and the regulation processing is triggered again by the regulation time. Repeated to occur,
In some cases, smooth regulation processing cannot be performed.

Further, the following points have not been taken into consideration in the current overload control. (I) Minimize the deterioration of serviceability or minimize the influence on other services depending on the cause of the overload condition. (Ii) The maintenance person can change the load control method according to the occurrence of overload, and can adjust the load control while observing the effect of the load control.

(Iii) When an overload is expected in advance, the overload state can be prevented in advance. In centralized control / control type networks, where demand is expected to increase further in the future, a mechanism for avoiding and preventing an overload condition in the centralized control / control device that affects the entire network will be of utmost importance. Assuming automatically,
In addition, the greatest problem is that overload control can be performed manually.

The present invention has been made in view of the above problems, and efficiently performs overload control in accordance with the cause of the overload state of the centralized control / control apparatus to prevent the overload state from occurring. It is an object of the present invention to provide a load regulation control system for a centralized management / control type network that can be avoided or prevented.

[0013]

According to the present invention, an inquiry to a centralized management / control device connected to at least one inquiry execution device and processing and responding to an inquiry issued from the inquiry execution device is regulated. A load regulation control device that controls the load of the centralized management / control device by monitoring the load of the centralized management / control device, and determines the regulation ratio according to the load, and the load monitoring control unit that is based on the regulation ratio. An apparatus is provided that comprises a load processing unit that controls the load by rejecting queries in due proportion.

According to the present invention, the centralized management / control is performed by restricting the inquiry to the centralized management / control device which is connected to at least one inquiry execution device and processes and responds to the inquiry issued by the inquiry execution device. There is also provided a load regulation controller for controlling the load on the device, the device comprising means for rejecting all inquiries based on a pre-specified type of call.

[0015]

1 is a block diagram of a system according to a first embodiment of the present invention. In the figure, 1 is a database in which various service control data are stored,
Reference numeral 10 is a centralized management / control device for giving an instruction according to the collation result / analysis result obtained by referring to the database 1 for an inquiry, and 20 makes an inquiry to the centralized management / control device 10. It is at least one inquiry execution device that performs a predetermined process according to the result.

Reference numeral 2 is a central office connected to the inquiry execution device 20, 3 is a subscriber terminal connected to the central office 2, and 4 is a central control unit (CC) for controlling exchange of the central office 2. Reference numeral 5 is a private branch exchange (PBX) connected to the central office exchange 2, and 6 is an extension terminal connected to the private branch exchange 5. In the figure, the inquiry execution device 20 and the central office switch 2
In the figure, the inquiry execution device 20 may be provided in the central office switch 2 in some cases.

The inquiry execution devices 20 are provided in n units from # 1 to #n, but it is necessary that at least one device is provided (the same applies to the following specific examples). In the centralized management / control device 10, 14 is a load monitoring control unit that receives various load information data and performs load monitoring control, and 15 receives the regulation rate data provided from the load monitoring control unit 14, and each inquiry execution device 20. Is a load processing unit that performs load processing in.

In the load monitoring control unit 14, 14a is a monitoring unit that monitors the traffic volume based on various load information data, and 14b receives the output of the monitoring unit 14a and determines the regulation rate for each inquiry execution device 20. It is a restriction activation unit that outputs. A regulation rate table 14c in which the regulation rate according to the regulation level is stored for each type of regulation processing is provided in the regulation activating unit 14b.

As the load information data, for example, as shown in the figure, the data of the usage rate of the central control unit for controlling the central control / control unit 10 and the central control / control unit 10 are used when performing the processing. There are a common resource usage rate, a response processing time until a response to an inquiry from the inquiry execution device 20 is completed, and the like. Regarding the upper limit value and the lower limit value, the central controller utilization data is X1 (upper limit value) to X2 (lower limit value), and the resource utilization data is Y1.
(Upper limit value) to Y2 (lower limit value), response processing time data is Z
1 (upper limit value) to Z2 (lower limit value). The number of inquiry requests per unit time can also be used as load information data.

FIG. 2 is a diagram showing an example of the regulation rate table 14c. For each of restriction processing 1 to restriction processing 4 (described later), restriction levels are set in order from level 1. For example, when the regulation process i is selected, the regulation rate at the regulation level 1 is 10%, the regulation rate at the level 2 is 20%, and the regulation rate at the level 3 is 30%.

In the load processing unit 15, 15a is a control unit for performing various controls, and 15b is various control processes. This regulation processing 15b includes regulation processing 1 to regulation processing 4 described above.
Is included. The contents are as follows. (Regulation processing 1) In response to an inquiry from the inquiry execution device 20, control is performed based on a restriction rate determined according to the load state of the centralized management / control device 10, and the inquiry execution device 20 receives a processing request. It will be notified by means such as announcement. The regulation based on the regulation rate means that, for example, when the regulation rate is 10%, 90% of the inquiries are accepted and 10% are rejected.

(Regulation processing 2) In response to an inquiry from the inquiry execution apparatus 20, the inquiry is restricted by ignoring the inquiry based on the restriction rate determined according to the load state of the centralized management / control apparatus 10. . At this time, the inquiry execution device 20 is not notified of the restriction. (Regulation processing 3) The centralized management / control device 10 notifies the inquiry execution device 20 of the regulation ratio determined according to the load state of the centralized management / control device 10, and the inquiry execution device 20 notifies the notified regulation ratio. Based on this, inquiries to the centralized management / control device 10 are regulated.

(Regulation processing 4) A combination of the restriction processing 1, the restriction processing 2, and the restriction processing 3 is executed according to the load condition. For example, when the restriction processing 1 and the restriction processing 2 are combined, the inquiry is rejected with a notification of rejection for the inquiry of α%, the inquiry is rejected without notification for the inquiry of β%, and γ (= 100− Accepts α-β)% inquiries.

In the regulation processing 1 to 3 among the regulation processings 1 to 3, the central management / control apparatus 10 must make a judgment as to whether an inquiry is accepted or rejected and a notification of the refusal. Is the heaviest. Therefore, the greater the number of rejected inquiries, the greater the amount of processing to do so, which further reduces the number of inquiries that can be accepted. In the regulation processing 3, the regulation processing is entrusted to the inquiry execution apparatus 20, so the burden on the centralized management / control apparatus 10 is the lightest. Regulation processing 2 is regulation processing 1
Is between control processing 3 and. Therefore, any one of the regulation processes 1 to 4 is selected according to the load situation, and when the regulation process 4 is selected, which is combined with which is determined. This determination may be made by a maintenance person and set in advance, or may be automatically determined by the centralized management / control device 10. The control unit 15a executes the regulation process selected from these regulation processes.

The various service control data managed by the database 1 are as follows. (I) Credit card service (ii) Alternate billing service (Alternate
Billing service) (iii) Freephone service (iv) Virtual Private Network service (v) Number Portability In the system configured in this way, from the inquiry execution device 20 of # 1. When an inquiry is made to the centralized management / control device 10, in the centralized management / control device 10, the monitoring unit 14a of the load monitoring control unit 14 determines the restriction level based on various load information data, and the restriction activating unit 14b.
To notify. The restriction activating unit 14b uses the restriction rate table 14
With reference to c, a regulation rate according to the regulation level in the selected regulation process is obtained and notified to the load processing unit 15.

The regulation unit 15a of the load processing unit 15 first returns a response to the corresponding # 1 inquiry execution device 20, and thereafter, based on the regulation process selection and the regulation rate at that time, the regulation processes 1 to Activate 4. FIG. 3 is a diagram showing the determination of the regulation level according to the load fluctuation in the load monitoring control unit 14 of the present invention. The vertical axis represents the load or usage rate of the centralized control / control device 10, and the upper limit value (X1, Y1, Z1) and the lower limit value (X2, Y2, Z2) of the various load information data described above.
It is shown. The horizontal axis is time. If the conditions for invoking the regulation process continue to be satisfied even after a certain period of time, the ratio of the regulation rate increases every certain period of time. For example, when the upper limit is exceeded at time t1, the control unit 15a activates the level 1 regulation process.

If the upper limit value is still exceeded at time t2 after the elapse of a certain period of time, the regulation level is increased from the previous level 1 to level 2. Since the upper limit value is still exceeded at time t3, the control unit 15a further updates the regulation level and raises it to level 3. As a result, the regulation effect is brought about, and at time t4, the load utilization rate falls below the upper limit value, but since the load utilization rate is between the upper limit value and the lower limit value, level 3 is maintained.

Next, at time t5, the effect of the regulation appeared and the load usage rate fell below the lower limit value. In this case, the control unit 15a reduces the regulation rate to Level 2. Time t6
However, since the load usage rate is further decreasing, the control unit 15a
Further lowers the regulation level to level 1. As described above, in the present invention, when the load is larger than the upper limit value, the regulation is activated so that the regulation becomes stronger gradually, and when the load becomes smaller than the lower limit value thereafter, the regulation is gradually released. When multiple variables are adopted as variables that indicate the load, if at least one of them is above the upper limit, it is judged that the load exceeds the upper limit, and if all are below the lower limit, the load is below the lower limit. It is judged to be smaller than. Instead of the upper and lower limits, a single regulation activation value is adopted.If the load variable exceeds this value, it is judged that the load exceeds the upper limit value.If the load variable falls below this value, the load is lower than the lower limit value. May be judged to be small, and the regulation rate determination algorithm described above may be applied.

According to the first specific example described above, the centralized management / control device 1 is caused by the centralized number of inquiries from the inquiry execution device 20 to the centralized management / control device 10.
When 0 becomes an overload state, in order to avoid or prevent the overload state, by executing the above-described regulation processing 1 to regulation processing 4 in accordance with the regulation condition designated in advance, Efficient overload control as shown in can be achieved.

(I) Since the logic for determining the conditions for calculating the effective regulation rate is simple, the processing load for the regulation processing can be reduced. (Ii) Since the regulation rate can be set in stages according to the duration of the overload state, the excessive regulation is eliminated and the serviceability is improved. (Iii) Since the regulation rate according to the duration of the overload state can be set stepwise, smooth regulation processing can be performed, and the system capacity of the centralized management / control device 10 can be utilized to the maximum extent. can do.

(Iv) Overload control operates effectively over the entire range, from small to large networks, regardless of the size of the network. First mentioned above
In the specific example, the operation of the centralized management / control device 10 is controlled by a service management system (not shown) that is a dedicated maintenance operation device in the network. The operation of the inquiry execution device 20 is controlled by a terminal (not shown) connected to the inquiry execution device 20 and used for maintenance. From the maintenance operation device or the terminal, the following uses can be considered as other functions.

(I) At the request of a maintenance person, the current regulation state is displayed including detailed information on the regulation content (regulation level, regulation activating factor, regulation influence range, etc.). (Ii) Detailed information on the content of regulation (regulation level, factor invoking regulation, scope of regulation, etc.) is displayed only when necessary items are designated by the maintenance person. It is preferable to notify the subscriber who has requested the intelligent network service call by means of announcement or the like that the call is rejected by the load regulation processing. As a result, the subscriber can recognize that he is currently in a congestion state.

Further, in the first specific example, an upper limit value and a lower limit value for each of the regulation processing activation conditions are set by a maintenance person,
By making it possible to change and display, the regulation process can be performed efficiently and promptly. Further, by enabling the maintenance person to set, change, and display the validity / invalidity of the regulation processing activation condition, the regulation processing can be performed efficiently and promptly.

Further, when a regulation level is set for each regulation process, the maintenance person can set, change, and display the regulation rate for the regulation level.
The regulation process can be performed efficiently and promptly. Also, when the regulatory processing is activated, whether the maintenance person is automatically notified that the regulatory processing has been activated, and when the regulatory processing is canceled, the maintenance person is automatically notified. By allowing the maintenance person to select whether to notify or not, changing the selection state, and enabling the display of the selection state, the restriction process can be performed efficiently and promptly.

Further, when it is possible to automatically notify the maintenance person including the detailed information of the regulation content, it is determined whether each item of the detailed information of the regulation content is included in the automatic notification. By selecting, changing the selection state, and enabling the display of the selection state, the restriction process can be performed efficiently and promptly. In addition, when it is possible to automatically notify the maintenance person each time there is a change in the regulation content while the regulation processing is in effect, whether or not to automatically notify the maintenance person every time the regulation content changes. By selecting, changing the selection state, and enabling the display of the selection state, the restriction process can be performed efficiently and promptly.

FIG. 4 is a block diagram showing the configuration of the second embodiment of the present invention. 1 are denoted by the same reference numerals. In FIG. 4 and the subsequent figures, the central office switch and the like connected to the inquiry execution device 20 are omitted. In this specific example, when the service control data is classified into different types of databases for each service,
When the centralized management / control device 10 becomes overloaded due to calls concentrated on a certain service, the restriction processing is automatically invoked only for the service call and not restricted for other service calls. For example, when calls are concentrated on the freephone service and the centralized management / control device 10 is overloaded, the regulation control is activated only for the freephone calls.

In the figure, the database 1 is classified into different types of service 1 to service n for each service. In the database 1, an inquiry request number storage table 1a that stores the number of service inquiry requests for each service type, and a regulation activation that determines how much the number of requests per unit time should be activated. A service-specific regulation activation value table 1b in which values are stored for each service is provided.

When an inquiry from the inquiry execution device 20 reaches the centralized management / control device 10, the service control unit 16 provided in the centralized management / control device 10 reads the database 1 according to the inquiry from the inquiry execution device 20. Access, refer to the corresponding service, and implement the service according to the search result. At the same time, the service control unit 16 counts up the corresponding portion of the inquiry request number table 1a each time an inquiry arrives. The monitoring unit 14a in the load monitoring control unit 14 repeats the following processing at regular intervals.

(I) A comparison is made between the number of inquiry requests and the service-specific regulation activation value of the service-specific regulation activation value table 1b which is fixed by the system or set in advance by the maintenance person. (Ii) When the number of inquiry requests is larger than the regulation activation value,
The regulation level is determined so that the regulation process is triggered in stages for the service and is released in stages when the regulation process is small.

(Iii) All the inquiry request numbers are cleared to prepare for the next cycle of processing. The service activation value for each service can also be changed by a maintenance person. As a result, it becomes possible to quickly respond to the overload situation of the centralized management / control device 10. The regulation activating unit 14b uses the regulation level from the monitoring unit 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level. In the load processing unit 15, the control unit 1
5a executes the above-mentioned regulation processing 1 to regulation processing 4 only for the regulated service. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution apparatus 20 is notified of the regulation. In the case of the regulation process 2, the inquiry is regulated based on the regulation rate, and no notification is given. In the case of the regulation process 3, the regulation rate and the regulated service are notified to the corresponding inquiry execution apparatus 20, and the regulation execution unit 21 of the inquiry execution apparatus 20 that has received the notification performs the centralized management / control apparatus according to the regulation rate only for the corresponding service. Restrict inquiries to 10.

If the maintenance person is requested to notify the triggering factor of the regulation processing, the load processing section 15
Notifies the maintenance person of the relevant service regulation level by means of an alarm message or the like. The activation value of the service-specific regulation activation value table 1b can be changed by a maintenance person. This makes it possible to quickly respond to load fluctuations.

In this example and the examples described below,
It is explained that the regulation level is determined by comparing the number of inquiry requests per unit time with the regulation activation value for each classification in order to determine the regulation rate for each classification. Similar to the specific example of, the upper limit value and the lower limit value may be used instead of the single restriction activation value. Also, instead of counting the number of inquiry requests per unit time for each classification, or in combination with this, the utilization rate and / or response time of the common resource for each classification may be used as a variable representing the load. good.

FIG. 5 is a configuration block diagram showing a third example of the present invention. The same parts as those in FIG. 4 are designated by the same reference numerals. In this specific example, when the service control data is classified into different types of databases for each service, the restriction process is activated only for the service that is expected to be overloaded and the restriction process is not performed for other services. By the service management system, it is possible to specify only the relevant service in advance as a regulation target. For example, in the freephone service, it is expected that a large number of calls will be concentrated, but in the case of other services, the calls will not be concentrated so much. In this case, the service subject to restriction in advance may be limited to only the freephone. .

The database 1 is the same as in the case of FIG.
Each service is classified into different types of service 1 to service n. Then, a regulation target / non-target table 1 indicating whether each service is regulated or non-regulated
I have c. The service control unit 16 responds to the inquiry from the inquiry execution device 20,
Access the relevant service, and perform the service according to the search result. Similarly to the above, the monitoring unit 14a calculates and / or inputs various load information data and determines the regulation level as described above. The restriction activating section 14b uses the restriction level from the monitoring section 14a,
The regulation rate according to the regulation level is determined by referring to the regulation rate table 14c. The load processing unit 15 recognizes the regulated / non-targeted data by referring to the regulated / non-targeted table 1c, and performs the regulated processes 1 to 4 only for the regulated services. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution apparatus 20 is notified of the regulation. In the case of the regulation process 2, the inquiry is regulated based on the regulation rate, and no notification is given. In the case of the regulation process 3, the regulation rate and the regulated service are notified to the corresponding inquiry execution apparatus 20, and the regulation execution unit 21 of the inquiry execution apparatus 20 which has received the notification performs centralized management according to the regulation rate only for the corresponding service. Inquiries to the control device 10 are regulated.

When the maintenance person is requested to notify the cause of the activation of the regulation processing, the load processing unit 15 notifies the maintenance person of the relevant service regulation level by means of an alarm message or the like. To do. The service restriction target / non-target data value of the restriction target / non-target table 1c can be changed by the maintenance person. This makes it possible to quickly respond to load fluctuations.

FIG. 6 is a block diagram showing the configuration of a fourth example of the present invention. The same components as those in FIG. 5 are denoted by the same reference numerals. In this specific example, when the data is classified into different types of databases for each service, the calls are concentrated on specific data (telephone number) of a certain service, and the centralized management / control device 10 becomes overloaded. In this case, the restriction processing is automatically activated only for the call to the telephone number, and the call to the other telephone number and the service call are not regulated. For example, when calls are concentrated on a specific telephone number of the freephone service and the centralized management / control device 10 is overloaded, the restriction processing is activated only for the freephone call to the telephone number.

The database 1 is the same as in the case of FIG.
Each service is classified into different types of service 1 to service n. Then, a data-specific inquiry request number table 1d that stores the number of inquiry requests for each specific data (telephone number) of a certain service, and a data-specific restriction activation value that determines whether or not to apply a restriction for each specific data of the service Has a regulation activation reference value table 1e that stores

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. Further, according to the inquiry, the data on the data-specific inquiry request number table 1d is searched. If there is corresponding data in the inquiry request count table 1d, the time stamp (time recording data at the time of the previous processing) is checked, and if there is a gap between the current time and a certain period or more, the request count is set to the initial value. To do. If there is no difference between the current time and a certain period, the request count is incremented. If there is no corresponding data in the inquiry request count table 1d, the corresponding data is registered in the table and the request count is set as an initial value. When the number of requests is changed, the time stamp is updated.

The monitoring unit 14a repeats the following processing at regular intervals. (I) Check all data in the data-based inquiry request count table 1d. (Ii) When the time stamp differs from the current time by a certain period or more, the corresponding data is deleted from the table. (Iii) When the time stamp does not differ from the current time by a certain period or more, the requested number is compared with the fixed value or the data-based restriction activation value of the restriction activation value table 1e set by the maintenance person in advance.

(Iv) The regulation level is determined so that when the number of requests is larger than the regulation activation value, the regulation process is activated stepwise for the relevant data of the relevant service, and when it is smaller, it is released stepwise. (V) Clear all request numbers to prepare for the next cycle of processing. The regulation activating unit 14b uses the regulation level from the monitoring unit 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level. The load processing unit 15 performs the regulation process 1 only on the relevant data of the regulated service.
~ Perform the restriction process 4. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution apparatus 20 is notified of the regulation. In the case of the regulation process 2, the inquiry is regulated based on the regulation rate, and no notification is given. In the case of the regulation process 3, the regulation rate and the relevant data of the regulated service are notified to the relevant inquiry execution device 20, and the regulation execution part 21 of the inquiry execution device 20 which received the notice.
Regulates inquiries to the centralized management / control device 10 according to the regulation rate only in the case of relevant data of the relevant service.

When it is required to notify the maintenance person of the cause of activation of the regulation processing, the load processing unit 15 notifies the maintenance person of the relevant service regulation level by means of an alarm message or the like. To do. Note that the data-based restriction activation value of the restriction activation value table 1e can be changed by the maintenance person. This makes it possible to quickly respond to load changes.

FIG. 7 is a configuration block diagram showing a fifth example of the present invention. 6 are denoted by the same reference numerals. In this specific example, when the data is classified into different types of databases for each service, the restriction process is preliminarily limited to only calls to data (telephone number) with a certain service that is expected to be overloaded. ,
Only the relevant data (telephone number) of the relevant service can be designated as the subject of regulation in advance by the service management system so that the regulation process is not activated for calls to other numbers and other services.

For example, when a large number of calls are expected to be concentrated on a certain telephone number of the freephone service, but calls are not concentrated on other numbers or other services, the regulation is performed beforehand. It limits the object only to that number on the freephone. Database 1
Are classified into different types of service 1 to service n for each service, as in the case of FIG. Then, it has a regulated data table 1f having a record of regulated data for each service for each service.

The service control unit 16 accesses the database 1 in response to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. The monitoring unit 14a calculates and / or inputs various load information data as described above, and determines the regulation level as described above. Regulation enforcement part 14
b uses the regulation level from the monitoring unit 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level.

The load processing section 15 refers to the restriction target data table 1f and performs the restriction processing 1 to the restriction processing 4 only on the restricted data. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution apparatus 20 is notified of the regulation.
In the case of the regulation process 2, the inquiry is regulated based on the regulation rate, and no notification is given. In the case of the regulation process 3, the regulation rate, the regulated service, and the regulated data are notified to the relevant inquiry execution apparatus 20, and the inquiry execution apparatus 20 which received the notification.
The regulation execution unit 21 regulates the inquiry to the centralized management / control device 10 according to the regulation rate only for the corresponding data of the corresponding service.

It should be noted that the regulated data may be sent in advance to the inquiry execution device 20 instead of being sent to the inquiry execution device 20 when the restriction is activated. Further, when it is required to notify the maintenance person of the cause of the activation of the regulation process, the load processing unit 15 informs the maintenance person of the relevant data of the relevant service, the regulation level, etc. by means of an alarm message output or the like. Make a notification. The data in the regulated data table 1f can be changed by a maintenance person. This makes it possible to quickly respond to load fluctuations.

As described above, in the fifth specific example, the case where the restriction is activated only on the restricted data of the restricted service has been described. On the contrary, a certain number is called even when the restriction process is executed. You may want to pass through. In this case, only that number may be set as a non-regulation target and the other numbers may be treated as a regulation target. FIG. 8 is a configuration block diagram showing a sixth example of the present invention. The same parts as those in FIG. 7 are designated by the same reference numerals. In this specific example, when the centralized management / control device 10 is overloaded due to a large number of call requests from a certain inquiry execution device 20, the regulation process is activated only by the call from the corresponding inquiry execution device 20. The restriction processing is not activated for the call from the other inquiry execution device 20.

The database 1 is the same as in the case of FIG.
Each service is classified into different types of service 1 to service n. Further, inside thereof, an inquiry request number table 1g for storing the number of inquiry requests for each inquiry execution device 20 (exchange point), and a regulation activation value table 1h for storing a reference value for activating regulation for each inquiry execution device 20. have.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. At the same time, the number of inquiry requests for each inquiry execution device 20 in the inquiry request number table 1g is counted up. The monitoring unit 14a repeats the following processing at regular intervals.

(I) The number of inquiry requests is compared with the restriction activation value table 1h, which is fixed by the system or set by the maintenance person in advance for each inquiry execution apparatus 20. (Ii) When the number of inquiry requests is larger than the regulation activation value,
The restriction processing is activated stepwise with respect to the inquiry execution device 20, and when it is small, the restriction level is determined so as to be released stepwise.

(Iii) Clear all inquiry request numbers in the inquiry request number table 1g in preparation for the processing of the next cycle. In addition, the inquiry execution device-specific restriction activation value of the restriction activation value table 1h can be changed by a maintenance person. As a result, it becomes possible to respond swiftly according to load fluctuations.

The regulation activating section 14b uses the regulation level from the monitoring section 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level. The load processing unit 15
The restriction processing 1 to the restriction processing 4 are performed only for the inquiry from the restriction target inquiry execution device 20. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution apparatus 20 is notified of the regulation. In the case of the regulation process 2, the inquiry is regulated based on the regulation rate, and no notification is given. In the case of the regulation process 3, the regulation rate is notified to the relevant inquiry execution apparatus 20, and the regulation execution unit 21 of the relevant inquiry execution apparatus 20 that has received the regulation regulates the inquiry to the centralized management / control apparatus 10 according to the regulation rate. .

If the maintenance person is required to notify the activation factor of the regulation processing, the load processing unit 1
Reference numeral 5 is a means such as an alarm message for notifying the maintenance person of the relevant inquiry execution device 20 and the regulation level. FIG. 9 is a block diagram showing the configuration of a seventh example of the present invention. 8 are denoted by the same reference numerals. In the example shown in FIG. 9, the number of call requests for a certain service from a certain inquiry execution device 20 is so large that when the centralized management / control device 10 becomes overloaded, the regulation process is automatically triggered. Only the corresponding service call from the corresponding inquiry execution device 20 is performed, and the restriction process is not activated for other service calls and calls from the other inquiry execution device 20.

The database 1 is similar to the case of FIG.
Each service is classified into different types of service 1 to service n. Further, inside thereof, an inquiry request number table 1i for storing the number of inquiry requests for each service type for each inquiry execution device 20 (exchange point) and a reference value for activating a restriction for each service type for each inquiry execution device 20 are provided. It has a regulation activation value table 1j to be stored.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. At the same time, the inquiry request number of the corresponding service for each inquiry execution device 20 in the inquiry request number table 1i is counted up. Monitoring unit 14
The a repeats the following processing at a constant cycle.

(I) A comparison is made between the inquiry request count and the service type regulation activation value of the inquiry execution apparatus 20 which is fixed by the system or preset by the maintenance person in the regulation activation value table 1j. (Ii) When the number of inquiry requests is larger than the regulation activation value,
The regulation level is determined so that the regulation process is triggered stepwise for the corresponding service of the inquiry execution device 20 and is released stepwise when the service is small.

(Iii) Clear all the inquiry request numbers in the inquiry request number table 1i in preparation for the processing of the next cycle. The service type restriction activation value for each inquiry execution device 20 in the restriction activation value table 1j can be changed by the maintenance person. As a result, it becomes possible to respond swiftly according to load fluctuations.

The regulation activating section 14b uses the regulation level from the monitoring section 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level. The load processing unit 15
The restriction processing 1 to the restriction processing 4 are performed only for the inquiry about the corresponding service from the restriction target inquiry execution device 20. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution device 20 is notified of the regulation. In the case of the regulation process 2, the inquiry is regulated according to the regulation rate, and no notification is given. In the case of the regulation processing 3, the regulation execution rate and the regulated service are notified to the relevant inquiry execution apparatus 20, and the inquiry execution apparatus 2 which received the notification.
The regulation execution unit 21 of 0 regulates the inquiry to the centralized management / control device 10 according to the regulation rate only for the corresponding service.

If the maintenance person is requested to notify the activation factor of the regulation processing, the load processing unit 1
Reference numeral 5 is a means such as an alarm message for notifying the maintenance person of the relevant inquiry execution device 20 and the regulation level. FIG. 10 is a configuration block diagram showing an eighth example of the present invention. The same parts as those in FIG. 9 are designated by the same reference numerals. In this specific example, when a request for specific data (number) of a certain service from a certain inquiry execution device 20 is very large, when the centralized management / control device 10 becomes overloaded, the regulation process is activated. Is automatically invoked only for a call to the corresponding number of the corresponding service from the corresponding inquiry execution device 20, and a call to another number,
The restriction process is not activated for other service calls and calls from other inquiry execution devices 20.

The database 1 is the same as in the case of FIG.
Each service is classified into different types of service 1 to service n. Further, inside thereof, an inquiry request number table 1k that stores the number of inquiry requests for each specific number for each service type for each inquiry execution device 20 (exchange point), and for each specific number for each service type for each inquiry execution device 20 It has a regulation activation value table 11 that stores a reference value for activating regulation.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. At the same time, the corresponding data of the corresponding service for each inquiry execution device 20 in the inquiry request number table 1k is searched. Then, when there is the corresponding data in the inquiry request number table 1k, the time stamp is checked, and when there is a difference between the current time and a certain period or more, the request number is set as an initial value. When there is no difference between the time stamp and the current time for a certain period or more, the number of inquiry requests in the inquiry request number table 1k is counted up. When there is no corresponding data in the inquiry request count table 1k, the corresponding data is registered in the inquiry request count table 1k, and the request count is set as an initial value. When the number of requests is changed, the time stamp is updated.

The monitoring section 14a repeats the following processing at regular intervals. (I) Check all the data in the inquiry request count table 1k. (Ii) If the time stamp differs from the current time by a certain amount or more, the corresponding data is deleted from the table. (Iii) When the time stamp does not differ from the current time by a certain amount or more, the number of inquiry requests and the regulation activation value table 1l
Of the inquiry execution device 20 fixed by the system or set in advance by the maintenance person and compared with the regulation activation value for each specific data for each service type.

(Iv) When the number of inquiry requests is larger than the regulation activation value, the regulation processing is activated stepwise for the specific data of the service of the inquiry execution device 20,
When it is small, the regulation level is decided so that it is released in stages. (V) Clear all the inquiry request numbers in the inquiry request number table 1k in preparation for the processing of the next cycle.

Note that the restriction activation value for each specific data for each service type for each inquiry execution apparatus 20 in the restriction activation reference value table 11 can be changed by a maintenance person. As a result, it becomes possible to take an agile response according to the load change. The restriction activating unit 14b uses the restriction level from the monitoring unit 14a to calculate the restriction rate table 1
4c, the regulation rate according to the regulation level is determined. The load processing unit 15 performs the regulation processing 1 to the regulation processing 4 only for the inquiry about the corresponding data of the corresponding service from the regulation target inquiry execution device 20. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution apparatus 20 is notified that the inquiry is regulated. In the case of the regulation processing 2, the inquiry is regulated according to the regulation rate, and in the case of the regulation processing 3, the regulation rate and the relevant data of the relevant target service are notified to the relevant inquiry execution apparatus 20, and the inquiry execution apparatus 20 having received the notice. The regulation execution unit 21 regulates the inquiry to the centralized management / control device 10 according to the regulation rate only for the relevant data of the relevant service.

FIG. 11 is a block diagram showing the configuration of the ninth embodiment of the present invention. The same components as those in FIG. 10 are denoted by the same reference numerals. In this specific example, when the centralized management / control device 10 is overloaded due to a large number of requests for calls from a specific area controlled by a certain inquiry execution device 20, the restriction processing is automatically performed. In addition, the restriction process is not executed for calls from other areas and other inquiry execution devices 20.

As in the case of FIG. 10, the database 1 has services 1 to n of different types for each service.
It is classified into. Further, inside thereof, an inquiry request number table 1m that stores the number of inquiry requests for each area for each inquiry execution device 20 (exchange point), and a regulation that stores a reference value that activates the regulation for each area for each inquiry implementation device 20 It has an activation value table 1n.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. At the same time, the number of inquiry requests of the corresponding area of each inquiry execution device 20 in the inquiry request number table 1m is counted up. Monitoring unit 14a
Repeats the following processing at regular intervals.

(I) The inquiry request number of the corresponding area stored in the inquiry request number table 1m and the restriction activation value of the corresponding area of the restriction activation value table 1n fixed by the system or preset by the maintenance person. Compare. (Ii) When the number of inquiry requests in the relevant area is larger than the regulation activation value of the relevant area in the regulation activation value table 1n, the regulation processing is activated stepwise to the inquiry execution device 20. The regulation level is decided so that it will be lifted.

(Iii) Next, all the inquiry request numbers stored in the inquiry request number table 1m are cleared. This is to prepare for the processing of the next cycle. The area-specific restriction activation value in the restriction activation value table 1n can be changed by a maintenance person. In the embodiment, a single value is set for all areas of the inquiry execution device 20, but the activation restriction value can be set for each area. As a result, it becomes possible to respond swiftly according to load fluctuations.

The regulation activating section 14b uses the regulation level from the monitoring section 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level. The load processing unit 15
The restriction processing 1 to the restriction processing 4 are executed only for the inquiry from the applicable area of the restriction target inquiry execution device 20. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution apparatus 20 is notified of the regulation. In the case of regulation processing 2, inquiries are regulated according to the regulation rate and no notification is given. In the case of the restriction processing 3, the inquiring device 20 that has received the notification notifies the applicable inquiring device 20 of the restricted area and the restricting rate.
The regulation execution unit 21 regulates the inquiry to the centralized management / control device 10 according to the regulation rate for the corresponding area. In addition, when the maintenance person is requested to notify the activation factor of the regulation process, the load processing unit 15 informs the maintenance person by means of an alarm message output or the like to the regulation subject area of the relevant inquiry execution device 20 and the regulation. Notify the level etc.

FIG. 12 is a configuration block diagram showing a tenth embodiment of the present invention. The same components as those in FIG. 11 are denoted by the same reference numerals. In this specific example, when the centralized management / control device 10 becomes overloaded due to a large number of requests for a specific service call from a specific area controlled by a certain inquiry execution device 20, a regulation process is performed. Is automatically activated only for the corresponding service call from the corresponding area of the relevant inquiry execution device 20, and the restriction processing is not activated for other service calls and calls from the other inquiry execution device 20.

As in the case of FIG. 11, the database 1 has services 1 to n of different types for each service.
It is classified into. Further, inside thereof, an inquiry request number table 1p for storing a plurality of service types and the number of inquiry requests thereof for each area for each inquiry execution device 20 (exchange point), and for each service type for each area for each inquiry execution device 20. It has a regulation activation value table 1q that stores reference values for activating regulation.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. At the same time, the number of inquiry requests of the corresponding service in the area provided for each inquiry execution device 20 in the inquiry request number table 1p is counted up.

The monitoring section 14a repeats the following processing at regular intervals. (I) The number of inquiry requests of the service of the corresponding area of the inquiry execution device 20 stored in the inquiry request number table 1p and the number of the inquiry services of the regulation activation value table 1q fixed by the system or set by the maintenance person. Compare with the regulation activation value.

(Ii) When the number of requests for the corresponding service is larger than the regulation activation value, the regulation processing is activated stepwise for the relevant service in the area of the inquiry execution device 20, and when it is small, it is released stepwise. To determine the regulation level. (Iii) Next, all the inquiry request numbers stored in the inquiry request number table 1p are cleared. This is to prepare for the processing of the next cycle.

The service-specific regulation activation value in the regulation activation value table 1q can be changed by a maintenance person.
In this specific example, a case where a single reference value is set for all areas of the inquiry execution device 20 is shown.
It is also possible to set a regulation activation value for each service in each area. As a result, it becomes possible to respond swiftly according to load fluctuations.

The regulation activating section 14b uses the regulation level from the monitoring section 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level. The load processing unit 15
The regulation processing 1 to regulation processing 4 are changed only for the relevant service in the relevant area of the inquiry from the regulation target inquiry execution device 20. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution apparatus 20 is notified of the regulation. In the case of the regulation process 2, the inquiry is regulated according to the regulation rate, and no notification is given.
In the case of the regulation process 3, the regulation target inquiry execution device 20
Only the relevant area, the regulated service and the regulation rate are notified, and the regulation execution unit 21 of the inquiry execution device 20 that has received the notification makes an inquiry to the central management / control apparatus 10 according to the regulation rate regarding the relevant service in the relevant area. Regulate. In addition, when the maintenance person is requested to notify the activation factor of the regulation processing, the load processing unit 15 informs the maintenance person by means of an alarm message output or the like to the regulation target area of the inquiry execution device 20, Notification of service, regulation level, etc.

FIG. 13 is a block diagram showing the configuration of the eleventh embodiment of the present invention. The same parts as those in FIG. 12 are designated by the same reference numerals. In this specific example, the centralized management / control device 10 is overrun because there are too many call requests for specific data (number) of a specific service from a specific area controlled by a certain inquiry execution device 20. When a load condition occurs, the regulation process is automatically activated only for the corresponding data of the corresponding service call from the corresponding area of the relevant inquiry execution device 20, and the call to the other number, the other service call, the other area. The restriction processing is not activated for the call from the other inquiry execution device 20.

As in the case of FIG. 12, the database 1 has services 1 to n of different types for each service.
It is classified into. Further, inside thereof, an inquiry request number table 1r for storing the inquiry request number for each specific data for each service type for each area for each inquiry execution device 20 (exchange point), and for each area for each inquiry execution device 20 Regulation activation value table 1 storing a reference value for activating regulation for each specific data for each service type
have s.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. At the same time, the corresponding data for each service in each area provided for each inquiry execution device 20 in the inquiry request number table 1r is searched. If there is corresponding data in the inquiry request count table 1r, the time stamp is checked, and if there is a difference between the current time and a certain period or more, the inquiry request count is set to an initial value, and the current time and the certain period or more are set. If there is no opening, the number of inquiry requests for the relevant data is counted up. When there is no corresponding data in the inquiry request number table 1r, the corresponding data is registered in the table 1r and the inquiry request number is set to an initial value. In this case, the time stamp is updated when the number of inquiry requests is changed. This is to prepare for the next inquiry.

The monitoring section 14a repeats the following processing at regular intervals. (I) Check all data in the inquiry request count table 1r. (Ii) When the time stamp differs from the current time by a certain amount or more, the corresponding data is deleted from the table. (Iii) When the time stamp does not differ from the current time by a certain amount or more, the system fixes the number of inquiry requests for the corresponding data of the corresponding service of the corresponding area of the corresponding inquiry execution device 20 stored in the table 1r, Alternatively, it is compared with the regulation activation value of the corresponding data in the regulation activation value table 1s preset by the maintenance person.

(Iv) When the number of inquiry requests is larger than the regulation activation value, the regulation processing is activated stepwise for the relevant data of the relevant service in the relevant area, and when it is smaller,
The regulation level is determined so that it is released in stages. (V) Clear all inquiry request counts in preparation for the next cycle of processing.

The regulation activation value of the relevant data for each service in the regulation activation value table 1s can be changed by the maintenance person. As a result, it becomes possible to respond swiftly according to load fluctuations. The restriction activating unit 14b uses the restriction level from the monitoring unit 14a and uses the restriction rate table 14c.
Refer to to determine the regulation rate according to the regulation level. The load processing unit 15 activates the regulation processing 1 to regulation processing 4 only for the relevant data of the relevant service in the relevant area of the inquiry from the regulation target inquiry execution device 20. For example,
In the case of the regulation processing 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution device 20 is notified of the regulation. In the case of the regulation process 2, the inquiry is regulated based on the regulation rate, and in the case of the regulation process 3, only the regulated inquiry execution device 20 is notified of the relevant area, the regulated service, the relevant data and the regulation rate, and notified. The restriction execution unit 21 of the inquiry execution device 20 that has received the request restricts the inquiry to the centralized management / control device 10 based on the restriction rate for the applicable data of the applicable service in the applicable area. In addition,
When the maintenance person is requested to notify the activation factor of the regulation process, the load processing unit 15 asks the maintenance person by means of an alarm message output or the like to the regulation target area of the corresponding inquiry execution device 20, the corresponding service, Applicable data,
Notify the regulation level.

FIG. 14 is a block diagram showing the configuration of the twelfth embodiment of the present invention. The same components as those in FIG. 13 are denoted by the same reference numerals. In this specific example, when the restriction processing is limited to only the call from the inquiry execution apparatus 20 that is expected to be overloaded, and the restriction processing is not to be activated for the calls from other inquiry execution apparatuses 20, the service management system notifies Only the relevant inquiry execution device 20 can be designated in advance as a regulation target.

As in the case of FIG. 13, the database 1 includes services 1 to n of different types for each service.
It is classified into. Further, inside thereof, a regulated / non-regulated data table 1t for designating regulated / non-regulated targets for each inquiry execution device 20 (exchange points), and a regulation table 1u for designating regulated / non-regulated targets for each service type. have.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. The monitoring unit 14a calculates and / or inputs various load information data as described above, and determines the regulation level as described above. Regulation enforcement part 1
4b uses the regulation level from the monitoring unit 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level.

The load processing unit 15 uses the inquiry execution device 2
By referring to the 0-based restriction target / non-target table 1t, the restriction process 1 to the restriction process 4 are activated only for the inquiry execution device 20 that is a restriction target. For example, in the case of the regulation process 1, the inquiry is regulated based on the regulation rate, and the relevant inquiry execution apparatus 20 is notified of the regulation. In the case of the regulation process 2, the inquiry is regulated based on the regulation rate, and in the case of the regulation process 3, the regulation rate is notified to the relevant inquiry execution device 20, and the regulation execution part 21 of the inquiry execution device 20 which has received the notice. Inquires to the centralized management / control device 10 are regulated based on the regulation rate.

Further, when the maintenance person is required to notify the activation factor of the regulation processing, the load processing section 15
Notifies the maintenance person of the service, regulation level, etc. of the corresponding inquiry execution device 20 by means of an alarm message or the like. In this case, the data of the regulation target / non-target data table 1t for each inquiry execution device 20 can be changed by the maintenance person. As a result, it becomes possible to respond swiftly according to load fluctuations.

Further, in the specific example shown in FIG. 14, even in the call from the inquiry execution device 20 that is subject to the restriction, the restriction target / non-target can be further specified for each service. The regulation target / non-target is stored in the regulation target / non-target table 1u. The regulation processing operation in this case is
This is the same as the case where the above-mentioned inquiry execution device 20 is restricted. In this case, the load processing unit 15 refers to the regulation target / non-target table 1u and activates the regulation processing only for the corresponding service. As a result, it becomes possible to restrict only the target service of the restricted target inquiry execution device 20.

FIG. 15 is a block diagram showing the configuration of the 13th embodiment of the present invention. The same components as those in FIG. 14 are denoted by the same reference numerals. In this specific example, a large number of calls are generated from an area controlled by the inquiry execution device 20,
For this reason, when overload is expected, the service management is performed when the restriction processing is activated only for the calls from the corresponding area and the restriction processing is not activated for the calls from the other area and the other inquiry execution device 20. It is possible to previously specify only the applicable area of the applicable inquiry execution device 20 as a restriction target from the system.

As in the case of FIG. 14, the database 1 has services 1 to n of different types for each service.
It is classified into. Further, inside thereof, a regulation target / non-target table 1v for designating the regulation target / non-regulation target for each area for each inquiry execution device 20 (exchange point),
It has a regulation target / non-target table 1w for designating the regulation target / non-regulation target for each service of each inquiry execution device 20.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and implements the service according to the search result. The monitoring unit 14a calculates and / or inputs various load information data as described above,
The regulation level is determined as described above. The regulation activating unit 14b uses the regulation level from the monitoring unit 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level. This can prevent the occurrence of an overload condition. The load processing unit 15 refers to the restriction target / non-target table 1v that stores the restriction target / non-target for each area provided for each inquiry execution device 20, and described only the relevant area of the inquiry execution device 20 to be restricted. The restricted process 1 to the restricted process 4 are executed.

The regulated / non-targeted data values of the regulated / non-targeted table 1v which stores the regulated / non-targeted area by exchange point can be changed by the maintenance person. This makes it possible to quickly respond to load changes. In addition, when it is required to notify the maintenance person of the activation factor of the regulation process, the load processing unit 15
Notifies the maintenance person of the applicable area of the applicable inquiry execution device 20 and the regulation level by means of an alarm message output or the like.

Further, in the embodiment shown in FIG. 15, the load processing unit 15 refers to the regulated / non-regulated table 1w for designating the regulated / non-regulated subject for each service of the inquiry execution device 20 which is the regulated subject. As a result, the regulation process can be activated for each corresponding service of the corresponding inquiry execution device 20. The restriction processing operation in this case is the same as the case of restricting each area of the inquiry execution device 20 described above. In this case, the load processing unit 15 refers to the regulation target / non-target table 1w and activates the regulation processing only for the corresponding service. Then, it becomes possible to restrict only the target service of the restricted inquiry processing device 20 together with the restricted / non-targeted data value for each area.

When it is required to notify the maintenance person of the activation factor of the regulation processing, the load processing unit 15 notifies the maintenance person of the corresponding inquiry execution device 20 by means such as outputting an alarm message. Notification of service and regulation level. FIG. 16 is a configuration block diagram showing a fourteenth embodiment of the present invention. The same parts as those in FIG. 15 are designated by the same reference numerals. In this specific example, a subscriber registered in advance is not subject to regulation even when regulation processing occurs due to overload.

As in the case of FIG. 15, the database 1 has services 1 to n of different types for each service.
It is classified into. Further, inside thereof, an unregulated table 1x or 1y for storing unregulated subscriber data.
Is provided. The non-regulated table 1x simply stores the subscriber data that is not regulated, and the non-regulated table 1y is the regulated / non-regulated for each service type that it has for each subscriber data that is not regulated. It also includes the target data.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and implements the service according to the search result. The monitoring unit 14a calculates and / or inputs various load information data as described above, and determines the regulation level as described above. Regulation enforcement part 1
4b uses the regulation level from the monitoring unit 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level.

The load processing section 15 refers to the regulation target / non-target table 1x or 1y and activates the regulation processing 1 to regulation processing 4 for the subscribers who are not on the data. When it is required to notify the maintenance person of the activation factor of the regulation process, the load processing unit 15 notifies the maintenance person of the corresponding subscriber, regulation level, etc. by means such as output of an alarm message. As for the non-regulated subscribers, the regulation target / non-target may be set for each service as shown in the regulation target / non-target table 1y. As a result, fine regulation processing can be performed according to the load fluctuation.

FIG. 17 is a block diagram showing the structure of a fifteenth embodiment of the present invention. The same components as those in FIG. 16 are denoted by the same reference numerals. In this specific example, the subscriber class (general subscriber, public telephone, test call, etc.) is subject to regulation or non-regulation. As in the case of FIG. 16, the database 1 is classified into different types of service 1 to service n for each service. Further, inside thereof, a subscriber class table 30a for storing regulated subscriber classes, or a subscriber class table for storing a plurality of classes for each service type and storing regulated / non-regulated data for each class 30b, or a plurality of classes are provided for each data type of service types, and a subscriber class table 30c for storing data to be regulated / not regulated for each class is provided.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. The monitoring unit 14a calculates and / or inputs various load information data as described above, and determines the regulation level as described above. Regulation enforcement part 1
4b uses the regulation level from the monitoring unit 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level.

The load processing unit 15 refers to the subscriber class table 30a and activates the restriction processing 1 to the restriction processing 4 only for the call from the corresponding subscriber class. In this case, the regulated subscriber class data value of the subscriber class table 30a can be changed by the maintenance person. Also, a subscriber class can be set for each service as shown in the table 30b. Further, as shown in the table 30c, the subscriber class can be set for each data type for each service. As a result, it becomes possible to respond swiftly in response to load fluctuations.

FIG. 18 is a block diagram showing the configuration of the 16th embodiment of the present invention. The same parts as those in FIGS. 1 and 17 are designated by the same reference numerals. In this specific example, in order to prevent an overload condition, the number of subscribers who can access a certain number is limited to, for example, the subscribers having a suffix of 3. The following examples can be considered as applications of this specific example.

(I) The maintenance can be freely scheduled by the maintenance person so that the tail limit can be changed depending on the day of the week, the time, etc. (Ii) The allowable end can be changed from the subscriber terminal. (Iii) In the case of (ii), the change is allowed only from the subscriber registered in advance.

As in the case of FIG. 17, the database 1 has services 1 to n of different types for each service.
It is classified into. Further, inside thereof, a restriction table 30d for storing tail restriction target data for restricting tails for each service type, or a restriction table 30e for storing schedule restriction target data for each data type for each service type in units of days of the week. have.

The centralized management / control device 10 responds to the inquiry from the inquiry execution device 20 with the restriction table 3
The tail regulation target data of 0d is checked, and all the inquiries based on the call whose tail is regulated are rejected. This tail regulation data can be changed by a maintenance person, and thus it is possible to quickly respond to load fluctuations. Alternatively, the centralized management / control device 10 checks the restriction table 30e on the basis of the call generation time and date in response to the inquiry from the inquiry execution device 20, and rejects all inquiries based on the call whose end is restricted. This tail end regulation schedule data can be changed by the maintenance person, and by doing so, it is possible to react swiftly to a load change.

In this case, the tail restriction target data can be changed from the subscriber terminal 3. Further, it is possible to allow the change only from the subscriber terminal registered in advance. Also in the case of this specific example, if the centralized management / control device 10 becomes overloaded, it is possible to activate the above-described restriction processing from restriction processing 1 to restriction processing 4.

FIG. 19 is a block diagram showing the configuration of a seventeenth example of the present invention. The same components as those in FIG. 18 are denoted by the same reference numerals. In this example, to prevent an overload condition, the subscribers who can access a certain number are
For example, it is limited to subscribers from a certain area. As in the case of FIG. 18, the database 1 is classified into different types of service 1 to service n for each service. In addition, the inquiry execution device (exchange point)
The non-regulation target data table 30f in which the non-regulation target number data is stored for each area of 20 or the non-regulation target data table in which the non-regulation data is stored for each service of the inquiry execution device 20 for each area of each day of the week. 30 g
have.

In response to the inquiry from the inquiry execution device 20, the centralized management / control device 10 refers to the non-regulated data table 30f and rejects all inquiries based on calls from areas other than the corresponding area. The non-regulation target data of the non-regulation target data table 30f can be changed by the maintenance person, and it is possible to quickly respond to the load fluctuation.

Alternatively, the central management / control device 10 checks the non-regulation target schedule of the non-regulation target data table 30g in response to the inquiry from the inquiry execution device 20 based on the time and the date and time of the call. Reject all call-based inquiries from anyone other than. The non-regulation target schedule data of the non-regulation target table 30g can be changed by a maintenance person, which enables swift response to a load change.

The non-regulation target tables 30f and 30g.
Can be changed from the subscriber terminal 3. It is also possible to change only from the subscriber terminal registered in advance. Also in the case of this specific example, if the central control / control device 10 becomes overloaded,
It is possible to activate the above-described restriction processings 1 to 4.

FIG. 20 is a block diagram showing the structure of an eighteenth embodiment of the present invention. The same parts as those in FIG. 19 are designated by the same reference numerals. In this example, to prevent an overload condition, the subscribers who can access a certain number are
For example, it is limited to subscribers who have already registered. The following examples can be considered as applications of this specific example.

(I) Scheduling is performed so that subscriber restrictions can be varied depending on the day of the week, time, etc. (Ii) Allowable subscribers can be changed, added, and deleted from the subscriber terminal. (Iii) In (ii), changes, additions, and deletions are allowed only by the subscribers registered in advance.

As in the case of FIG. 19, the database 1 includes services 1 to n of different types for each service.
It is classified into. Further, inside thereof, there is a non-regulation target data table 30h in which subscriber data not subject to regulation is stored, or a non-regulation target data table 30i in which non-regulation target data is stored for each day of the week. In response to the inquiry from the inquiry execution device 20, the centralized management / control device 10 refers to the non-regulation target table 30h to check the call regulation non-target subscriber data, and in the case of the corresponding call, other than the allowable subscriber. Reject all inquiries based on the call. The non-regulation target data of the non-regulation target data table 30h can be changed by the maintenance person, which enables a prompt response according to the load change.

Alternatively, the centralized management / control device 10 checks the non-restricted schedule of the non-restricted data table 30i based on the call generation time and date in response to the inquiry from the inquiry execution device 20 and applies the result. For calls, reject all call-based inquiries from non-allowing subscribers. The non-regulation target schedule data of the non-regulation target table 30i can be changed by a maintenance person, which enables an agile response according to a load change.

In this case, the non-regulation target table 3
The caller restriction non-target data of 0h can be changed from the subscriber terminal 3. It is also possible to change only from the subscriber terminal registered in advance. Also in the case of this specific example, if the centralized management / control device 10 becomes overloaded, it is possible to activate the above-described restriction processing from restriction processing 1 to restriction processing 4.

FIG. 21 is a block diagram showing the structure of a nineteenth embodiment of the present invention. The same parts as those in FIG. 17 are designated by the same reference numerals. In this specific example, when a call can be classified according to information attributes such as voice, video, and digital information, only the relevant attribute can be automatically set to be subject to restriction. As a result, the load regulation control can be efficiently performed according to the attribute.

As in the case of FIG. 17, the database 1 has services 1 to n of different types for each service.
It is classified into. Further, inside thereof, an attribute table 30j in which data of attributes to be regulated is stored, an attribute table 30k in which attribute data to be regulated for each service type is stored, or a regulation target for each data for each service type It has an attribute table 30l in which the attribute data is stored.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and executes the service according to the search result. The monitoring unit 14a calculates and / or inputs various load information data as described above, and determines the regulation level as described above. Regulation enforcement part 1
4b uses the regulation level from the monitoring unit 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level.

The load processing unit 15 refers to the attribute table 30j, and performs only the restriction processing 1 to the restriction call for the attribute-specified call.
The restriction process 4 is activated. In this case, when it is required to notify the maintenance person of the activation factor of the regulation process, the load processing unit 15 notifies the maintenance person of the regulation level, attribute, etc. by means of an alarm message or the like. The restricted attribute data value of the attribute table 30j can be changed by the maintenance person. Further, like the attribute table 30k, attribute data can be set for each service. Further, like the attribute table 301, the attribute data can be set for each data for each service.

FIG. 22 is a block diagram showing the configuration of the twentieth embodiment of the present invention. The same parts as those in FIG. 21 are designated by the same reference numerals. In this specific example, even if a call should be rejected by the restriction process when the restriction process occurs due to overload,
For example, when a call rejection announcement is made and a password is entered, the call is released from restriction and the call is connected.

In this case, the service management system limits the password to those who are qualified to change or display the password, validates only when the password is entered by the subscriber, and changes the password from the subscriber terminal. The application can be expanded so that it can be done. As a result, even if the call is rejected by the restriction process while the restriction process is being activated, the restriction activating means in the centralized management / control device 10 cancels the restriction process for the call when a certain password is input. As a result, in an emergency or the like, a specific call can be accepted even during regulation.

As in the case of FIG. 21, the database 1 has services 1 to n of different types for each service.
It is classified into. Further, inside thereof, there is a password table 30m for storing non-regulated password data (set for each valid service) or a password table 30n for storing valid subscriber data for each password.

The service control unit 16 accesses the database 1 according to the inquiry from the inquiry execution device 20, refers to the corresponding service, and implements the service according to the search result. The monitoring unit 14a calculates and / or inputs various load information data as described above, and determines the regulation level as described above. Regulation enforcement part 1
4b uses the regulation level from the monitoring unit 14a and refers to the regulation rate table 14c to determine the regulation rate according to the regulation level.

The load processing unit 15 refers to the password table 30m for the call in which the password is input,
Restriction processing 1 for calls other than calls with valid password input
The restriction process 4 is activated. In this case, the password data that is not subject to the regulation processing is the inquiry execution device 20 when the regulation is activated.
It is also possible to send the information to the inquiry execution device 20 in advance instead of sending the information to the inquiry execution device 20. Further, when the maintenance person is requested to notify the activation factor of the regulation process, the load processing unit 15 notifies the maintenance person of the non-regulated password, the regulation level, etc. by means of an alarm message output or the like. Do.

The password data value not subject to regulation is
It can be changed by a maintenance person, which enables agile response according to load fluctuations. Also,
As shown in the password table 30n, each password can have valid subscriber data. Also, the password can be validated only when the password is input from a specific subscriber terminal.

[0136]

As described above in detail, according to the present invention, the overload control is efficiently performed according to the cause of the overload state of the centralized management / control device, and the overload state is generated. Provided is a load regulation control system for a centralized management / control type network that can be avoided or prevented.

[Brief description of drawings]

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

FIG. 2 is a diagram showing an example of a regulation rate table.

FIG. 3 is a diagram illustrating determination of a regulation level according to a load change according to the present invention.

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

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

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

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

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

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

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

FIG. 11 is a block diagram showing a ninth embodiment of the present invention.

FIG. 12 is a block diagram showing a tenth embodiment of the present invention.

FIG. 13 is a block diagram showing an eleventh embodiment of the present invention.

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

FIG. 15 is a block diagram showing a thirteenth embodiment of the present invention.

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

FIG. 17 is a block diagram showing a fifteenth embodiment of the present invention.

FIG. 18 is a block diagram showing a sixteenth embodiment of the present invention.

FIG. 19 is a block diagram showing a seventeenth embodiment of the present invention.

FIG. 20 is a block diagram showing an eighteenth embodiment of the present invention.

FIG. 21 is a block diagram showing a nineteenth embodiment of the present invention.

FIG. 22 is a block diagram showing a twentieth embodiment of the present invention.

[Explanation of symbols]

 1 ... Database 10 ... Centralized Management / Control Device 13 ... Regulation Enforcement Unit 20 ... Inquiry Execution Device

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁶ Identification number Office reference number FI technical display location H04M 3/36 9466-5K H04L 11/08 3/38 (72) Inventor Tadaaki Tanaka Kawasaki City, Kanagawa Prefecture 4-1-1 Kamiodanaka, Nakahara-ku, Fujitsu Limited

Claims (24)

[Claims] 1. A central management / control device load is controlled by restricting an inquiry to a central management / control device which is connected to at least one inquiry execution device and processes and responds to an inquiry issued from the inquiry execution device. A load regulation control device that controls the load, by monitoring the load of the centralized management / control device and determining the regulation rate according to the load, and by rejecting the inquiry at a rate based on the regulation rate. And a load processing unit for controlling the device. 2. The load processing unit rejects an inquiry at a rate based on the regulation rate, and notifies the inquiry execution apparatus that issued the rejected inquiry that the inquiry has been rejected, based on the regulation rate. A second regulation process for rejecting an inquiry without notifying in proportion, a third regulation process for instructing an inquiry execution device to regulate an inquiry at a rate based on a regulation rate, and
The apparatus according to claim 1, wherein one of the fourth regulation processings, which is performed by combining two or more of the second and third regulation processings, can be performed according to a selection according to the load of the centralized management / control device. 3. The load monitoring control unit, when the load exceeds a preset upper limit value, means for determining the regulation rate to a non-zero value, and a state in which the load exceeds the preset upper limit value continues. 3. The apparatus according to claim 2, further comprising means for increasing the regulation rate stepwise, and means for gradually reducing the regulation rate when the load falls below a preset lower limit value. 4. The load monitoring control unit monitors a plurality of variables indicating the load of the centralized management / control device, and judges that the load exceeds the upper limit value when at least one of the plurality of variables exceeds the upper limit value, 4. The apparatus according to claim 3, wherein the load is determined to be below the lower limit when all of the plurality of variables are below the lower limit. 5. The centralized management / control device processes inquiries about a plurality of service types, and the load monitoring control unit, for each of the service types,
The device according to claim 2, wherein the load of the centralized management / control device is monitored to determine a regulation rate according to the load, and the load processing unit rejects an inquiry for each service type at a rate based on the regulation rate. 6. The apparatus according to claim 2, wherein the load processing unit rejects the inquiry only for the service type designated in advance at a rate based on the regulation rate. 7. The central control / control device processes inquiries about a plurality of service types, and the load monitoring control unit monitors the load of the central control / control device for each service type and number data and responds to the load. The device according to claim 2, wherein the regulation rate is determined, and the load processing unit rejects the inquiry for each of the service type and the number data at a rate based on the regulation rate. 8. The apparatus according to claim 2, wherein the load processing unit rejects the inquiry only for the predesignated number data of the predesignated service type at a rate based on the regulation rate. 9. The load monitoring control unit centrally manages and inquires about each of the inquiry execution devices that request an inquiry.
The device according to claim 2, wherein the load of the control device is monitored to determine a regulation rate according to the load, and the load processing unit rejects the inquiry for each of the inquiry execution devices at a rate based on the regulation rate. 10. The apparatus according to claim 2, wherein the load processing unit rejects the inquiry only with respect to the inquiry execution apparatus designated in advance at a rate based on the regulation rate. 11. The centralized management / control device processes inquiries about a plurality of service types, and the load monitoring control unit determines the load of the centralized management / control device for each of the inquiry execution device and the service type for which an inquiry is requested. The device according to claim 2, wherein the regulation ratio is monitored and the regulation ratio is determined according to the load, and the load processing unit rejects the inquiry for each of the inquiry execution device and the service type at a ratio based on the regulation ratio. 12. The apparatus according to claim 2, wherein the load processing unit rejects the inquiry at a rate based on the regulation rate only with respect to a prespecified inquiry execution apparatus and a prespecified service type. 13. The centralized management / control device processes inquiries about a plurality of service types, and the load monitoring control unit provides a centralized management / control device for each of the inquiry execution device, the service type and the number data requesting the inquiry. 3. The device according to claim 2, wherein the load is monitored to determine a regulation rate according to the load, and the load processing unit rejects the inquiry for each of the inquiry execution device, the service type and the number data at a rate based on the regulation rate. . 14. The load monitoring control unit monitors the load of the centralized management / control device for each of the area for requesting a service and the inquiry execution device for requesting an inquiry, and determines a regulation rate according to the load. The device according to claim 2, wherein the processing unit rejects the inquiry for each of the area and the inquiry execution device at a rate based on the regulation rate. 15. The load processing unit only for a predesignated area and a predesignated inquiry execution device,
The apparatus according to claim 2, wherein the inquiry is rejected at a rate based on the regulation rate. 16. The centralized management / control device processes inquiries about a plurality of service types, and the load monitoring control unit centrally manages each of the area requesting a service, the inquiry execution device requesting an inquiry, and the service type. 3. The load of the control device is monitored to determine a regulation rate according to the load, and the load processing unit rejects the inquiry for each of the area, the inquiry execution device, and the service type at a rate based on the regulation rate. Equipment. 17. The apparatus according to claim 2, wherein the load processing unit rejects the inquiry only at a predetermined area, a predetermined inquiry execution apparatus, and a predetermined service type at a rate based on the regulation rate. 18. The centralized management / control device processes inquiries about a plurality of service types, and the load monitoring control unit regards each area for requesting a service, inquiry execution device requesting an inquiry, service type and number data. , The centralized management / control device is monitored to determine the regulation rate according to the load, and the load processing unit makes inquiries about each area, inquiry execution device, service type and number data at a rate based on the regulation rate. The device according to claim 2, which rejects. 19. The apparatus according to claim 2, wherein the load processing unit rejects the inquiry only for a predesignated subscriber at a rate based on the regulation rate. 20. The apparatus according to claim 2, wherein the load processing unit rejects the inquiry only for a subscriber class designated in advance at a rate based on the regulation rate. 21. The apparatus according to claim 2, wherein the load processing unit rejects the inquiry only for the attribute of the information designated in advance at a rate based on the regulation rate. 22. The apparatus according to claim 2, wherein the load processing unit rejects the inquiry only at an inquiry for which a predetermined password is not input, at a rate based on the regulation rate. 23. Further comprising means for rejecting all inquiries based on a pre-specified type of call.
The described device. 24. By controlling an inquiry to a centralized management / control device which is connected to at least one inquiry execution device and processes and responds to an inquiry issued from the inquiry execution device, the load of the centralized management / control device is reduced. A load regulation control device for controlling, which is provided with means for rejecting all inquiries based on a call of a predetermined type.