JPH07154473A - Control system of load on exchange - Google Patents

Abstract

PURPOSE:To improve the performance and to effectively utilize memory resources by dynamically deciding task constitution optimum for individual users' operation corresponding to the hardware and traffic. CONSTITUTION:A task state managing part 11 manages the task constitution (kind, number) of a system, and a device managing part 12 manages the packaging state and quantity of the hardware such as a line circuit and a trunk circuit, etc., and a maintenance/operation managing part 13 manages the operating mode of a subscriber, a central office line, and service, etc., registered from a maintenance console by a maintenance engineer. A call control part 14 provides the service of an extension and a line wire setting switching processing as a unit of processing function called as a task. Traffic information collection part 15 collects the information of call processing load such as the number of outgoing/incoming calls by receiving information from the call control part 14. As OS 16 manages the scheduling of task execution extending over the whole system, and also, allocates the memory resources on the task.

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 switch adopting a multi-task system, and more particularly to a load control system for a switch for controlling the number of tasks generated and the number of tasks activated during system operation.

[0002]

2. Description of the Related Art The number of tasks and the amount of resources required for the tasks to operate, that is, the amount of memory, are in direct proportion. Larger systems require more tasks for operation, so more memory must be implemented according to the number of tasks.

Further, since a plurality of types of tasks constituting the system can exhibit the most balanced performance of the system, the tasks are generated so as to have a certain task composition ratio in a limited resource. The boot process is designed.

Therefore, in the conventional system operation control method, by preparing an amount of memory commensurate with the system scale and increasing or decreasing the total number of tasks within the range of this memory amount without changing the task composition ratio, The task was generated and started according to the system scale. As a result, it was almost impossible to change this composition ratio without modifying the software operating based on this composition ratio.

From the viewpoint of processing capacity, the tasks that are generated and activated are under the control of the operating system (hereinafter referred to as the OS), and although the amount is very small, the system is in a non-processing state. Is a wasteful load.

[0006]

The system use of a private branch exchange, which is a mass-selling product, must be the greatest common denominator of all users in order to support a wide variety of users' usage patterns in a well-balanced manner.

In the conventional system operation control method, the composition ratio of the tasks composing the system is set to a certain value so that the most balanced performance can be exhibited regardless of the scale of the system.

Therefore, what kind of tasks are to be generated and how many are activated in a system of each scale is determined by the task configuration ratio and the system scale.

However, in today's diverse industries and business categories, the system configuration itself varies depending on the user, and the load on the system cannot always be constant. Ordinarily, it changes from moment to moment depending on the time of day.

Although hardware functions have been modularized and packaged, it is easy to increase or decrease the hardware for each function, but the number of software processing tasks for controlling this depends on the task composition ratio of the system scale as described above. Since the task composition ratio cannot be easily changed, there is a big problem that it is almost impossible to increase or decrease the processing tasks of a specific function during system operation according to the system operation mode.

Further, in the conventional system operation control method,
Regardless of whether or not an event has occurred, once a task has been created and activated, it has a problem that the processing capacity is adversely affected as a fixed load even if the task is idle and is not performing any processing. Such tasks should be deleted.

The object of the present invention is to make it possible to determine the optimum task configuration for the operation of an individual user in consideration of the hardware implementation status and traffic in consideration of the difficulty of finely customizing so as to satisfy the requirements of the individual user. By dynamically determining the load according to the above, software can be exchanged without stopping the operating system, and a load control method for a switch that improves performance and effectively uses memory resources is provided. is there.

[0013]

According to the present invention, in a switch of a multi-task system having a configuration in which individual tasks having different functions are multiplexed, hardware of peripheral circuits including a line circuit and a trunk circuit is provided. To monitor the hardware configuration conditions, the operation mode specified by the maintenance person, and the traffic state that changes with time, and to dynamically increase or decrease the number of processing tasks including call control after comprehensively judging these monitoring results. A load control system for an exchange characterized by the following is obtained.

Further, hardware management means for managing the mounting state of the hardware, maintenance / operation management means for managing information relating to the operation of the exchange service registered from the maintenance console by the maintenance person, and the inside of the system A control and monitoring means for controlling the generation, activation, termination, and deletion of tasks and periodical monitoring of the status of the tasks, and a collection means for collecting call processing traffic are provided, and an optimal and minimum task configuration is always provided in operation. A load control system for an exchange is obtained which is characterized by controlling the task multiplicity so that

Further, the hardware management means comprises a device management section for managing the mounting state and quantity of the hardware, and the maintenance / operation management means includes subscribers, station lines and services registered from the maintenance console. The maintenance / operation management unit manages the operation mode of the system, and the control / monitoring unit includes a task state management unit that manages the task configuration in the system and a call control unit that realizes exchange service processing in the task unit. The collection means comprises a traffic information collection unit that collects call processing load information in response to a notification from the call control unit, manages scheduling of task execution over the entire system, and memory resources for the task. Load control of an exchange characterized by having an operating system that allocates The formula is obtained.

[0016]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram of a software configuration for a private branch exchange system showing an embodiment of a load control system for an exchange of the present invention.

The entire software is a set of functions such as call processing, failure processing, and maintenance / operation management.

Referring to FIG. 1, the task state management unit 11
Manages the task configuration (type, number) in the system. The device management unit 12 manages the mounting state and quantity of hardware such as line circuits and trunk circuits. The maintenance / operation management unit 13 manages the operation mode of subscribers, station lines, services, etc. registered from the maintenance console by the maintenance person. The call control unit 14 realizes an extension service and an outside line service by using a switching function as a unit of a processing function called a task. The traffic information collection unit 15 receives the notification from the call control unit 14 and collects information on the call processing load such as the number of incoming and outgoing calls.
The OS 16 manages the task execution scheduling over the entire system and allocates memory resources to the tasks.

The call controller 14 is realized by the mutual operation of a plurality of types of tasks. For example, the task a executes the function A, the task b executes the function B, the task c executes the function C, and the task d executes the function D.

The task status management unit 11 controls the generation, activation, termination and deletion of processing tasks in the system. That is, the attribute data of this hardware is read from the database in the system from the mounting information of the hardware such as the line circuit and trunk circuit notified from the device management unit 12, and the corresponding processing task is generated, activated, and Instruct to end or delete.

For example, when the notification that the trunk circuit has changed from the unmounted state to the mounted state is received, the attribute data of this trunk circuit is read out, and if the data content is also normal, the call control unit 14 is instructed. Then, only one task of the line call processing is generated and activated.

Since the hardware is not necessarily in the serviceable state, the task is generated after confirming the consistency with the registered attribute data.

On the contrary, when the apparatus management unit 12 receives the notification that the trunk circuit is changed from the mounted state to the unmounted state, the processing task is terminated and deleted.

In this way, the task state management section 11 identifies activation / deactivation of the peripheral circuit and controls the generation, activation, termination and deletion of the corresponding task.

Next, FIG. 2 is a diagram showing a task configuration of the multi-task system in FIG.

Referring to FIG. 2, a task a which executes the function A includes a task a1 which executes the function A1 and tasks a2, a3 and a4 which have exactly the same functions. The multiplicity is 4. Here, the multiplicity of 4 indicates that requests for the function A can be processed up to four at the same time.

Similarly, tasks b1, b2, and b3 have a multiplicity of 3, tasks c1 and c2 have a multiplicity of 2, and task d has a multiplicity of 2.
1, d2 and d3 have a multiplicity of 3.

In order to exert a high processing capacity as a system, it is necessary to increase the multiplicity of the same task so as to increase the number of simultaneous processings. However, the number of tasks and the memory capacity required therefor are in direct proportion. Therefore, the multiplicity cannot be unnecessarily increased within the limited memory capacity.

Next, FIG. 3 is a task configuration diagram of the system in which the task configuration is biased because the particular function is overemphasized in the call control unit in FIG.

As shown in FIG. 3, if the multiplicity of a specific task (for example, task a) is increased to increase the processing capability of a specific function, the multiplicity of other tasks must be decreased. The processing capability of other functions is reduced, which is inconvenient for the entire system.

Therefore, conventionally, the multiplicity is set so that tasks can be generated and activated with a certain task configuration ratio so that the most balanced processing capacity as a system can be exhibited with a limited memory capacity. .

However, depending on the operating state and purpose, there may be cases where it is necessary to deviate specific functions and tasks.
For example, this is the case when the number of office lines accommodated is extremely large.

In such a case, the number of hardware packages corresponding to the trunk circuit for accommodating the central office line may be increased. Then, on the software side, it is necessary to increase the multiplicity of the station line call processing tasks so that the processing capability of the station line call processing becomes high.

However, since the task configuration in the system is set in consideration of the balance of all functions as described above, the number of station line call processing tasks is insufficient and the service of station line connection is deteriorated as it is. Will end up.

Further, in order to change the multiplicity of the office line call processing task, it is necessary to modify the software including changing the task composition ratio and to replace the modified software with the operating one. It has been a drawback of the conventional method that it cannot be performed easily.

Next, a procedure for determining the number of task generations and the number of activations according to the load control system of the exchange of the present invention will be described.

First, in restarting the initial setting of the system, the task state management unit 11 receives a notification of the mounting state of the peripheral circuits mounted from the device management unit 12, and performs maintenance / maintenance.
The operation management unit 13 receives a notification of information on the operation form.

At this time, the task state management unit 11 counts the number of mounted circuits for each type of peripheral circuit, and statically determines the number of generated tasks and the number of activated tasks based on the counting result. That is, the total number of tasks in the system is distributed according to the quantity ratio of each type of peripheral circuit, and the call control unit 14 is instructed to generate and activate the corresponding processing task.

For example, a subscriber circuit, an office line trunk circuit,
If the quantity ratio of the relay exchange is 5: 4: 1, each task should be created and activated with the task multiplicity such that the composition ratio of the tasks corresponding to each function becomes 5: 4: 1. , The most balanced task composition ratio for this system.

Therefore, in a station having a large number of office line circuits as in the above-mentioned example, many office line trunks commensurate with this should be installed, and naturally the multiplicity of the office line call processing tasks is also high. Has become.

However, before the task is generated and activated,
Be sure to check the consistency between the registered attribute data and the mounted peripheral circuits. Just by mounting the hardware, the peripheral circuits cannot be serviced, and the service can be provided only when the attribute data that is practical for processing is registered. Therefore, even if the hardware is installed, if it is not consistent with the attribute data, the load control is performed as if it were not installed.

Furthermore, the task status management unit 11 detects the call processing load on the system by the notification from the traffic information collection unit 15, and when it is determined that the number of tasks needs to be increased or decreased, the OS 16 reserves a memory. Alternatively, after requesting release, the call control unit 14 is instructed to dynamically generate or delete a task.

Next, with reference to FIGS. 3, 4 and 5, the task status monitoring performed by the task status management unit during system operation will be described.

FIG. 4 is a task configuration diagram showing the same system as FIG. 3 at another point in time, and FIG. 5 shows the task state management unit in FIG. 1 for monitoring the state of task a in FIGS. 3 and 4. It is a conceptual diagram of the monitoring memory used for.

First, it is assumed that the task a has nine tasks a1, ..., A9 generated and activated as shown in FIG. 3 from the number of mounted peripheral circuits and the registered attribute data.

The task status management unit 11 creates a management memory as shown in FIG. 5 for periodically checking the status of the task at the same time when the task is created and activated.

Referring to FIG. 5, the monitoring memory is composed of nine elements A [1], ..., A [9], and a counter is held inside. Although the initial value of this counter is "0", each of the elements A [1], ..., A [9] is incremented by one in the task state management module that is periodically activated.

Normally, when some event occurs and task a executes function A, A [] corresponding to this task is executed.
Returns to the initial value "0".

For example, when an event occurs and the task a1 executes processing, the element A [1] has an initial value "0".
Return to. On the other hand, for tasks that have been created and started but have not performed their functions at all, the counters are "2", "3",
"4" and "5" are added.

In this way, when the monitoring memory exceeds a certain threshold value, the corresponding task is determined to be an invalid task that has not executed any processing for a certain time or longer, and the peripheral circuit is mounted / not mounted. Regardless of this, the task status monitoring module uses the system resources effectively, so forcibly terminates this task and deletes it.

Assuming that the threshold value is "5", it is judged from FIG. 5 that the tasks a6, ..., A9 are invalid, and the nine tasks a1, ..., A9 existing in FIG. 3 are as shown in FIG. , The number of tasks a1, ..., A5 is reduced to five.

If an event that requires the processing of task a continues to occur and the tasks a1, ..., A5 become overloaded, the task a6 of FIG. 3 is again executed.
..., a9 is generated and started, and element A of the management memory
[6], ..., A [9] also return to the initial value “0”, and the task a
The load is processed together with 1, ..., A5.

[0054]

As described above, the load control system for an exchange according to the present invention monitors hardware configuration conditions, an operation mode designated by a maintenance person, or a traffic state changing with time, and comprehensively monitors these. By dynamically increasing or decreasing the number of processing tasks such as call control after making a judgment, it is possible to follow the operation form and operation state of the system without customization for users or exchange of software.

Further, it is possible to dynamically delete a substantially ineffective task in which the idling state continues for a certain period of time or longer, so that an unnecessary load can be eliminated and resources can be effectively used. Have.

[Brief description of drawings]

FIG. 1 is a block diagram of a software configuration for a private branch exchange system showing an embodiment of a load control system for an exchange of the present invention.

FIG. 2 is a diagram showing a task configuration of the multi-task system in FIG.

FIG. 3 is a task configuration diagram of a system in which a task configuration is biased because a particular function is overemphasized in the call control unit in FIG.

FIG. 4 is a task configuration diagram showing the same system as in FIG. 3 at another point in time.

5 is a conceptual diagram of a monitoring memory used by the task status management unit in FIG. 1 for monitoring the status of task a in FIGS. 3 and 4. FIG.

[Explanation of symbols]

 11 task status management unit 12 device management unit 13 maintenance / operation management unit 14 call control unit 15 traffic information collection unit 16 operating system (OS) A, B, C, D functions A [1], ..., A [9] Elements a, a1, ..., a9 Tasks that perform function A b, b1, ..., b3 Tasks that perform function B c, c1, c2 Tasks that perform function C d, d1, ..., d3 Perform function D task

Claims (3)

[Claims] 1. In a multi-task type switch having a configuration in which individual tasks having different functions are multiplexed, hardware configuration conditions of peripheral circuits including line circuits and trunk circuits are specified by a maintainer. A load control method for an exchange characterized by dynamically monitoring the number of processing tasks including call control after monitoring the operating mode and traffic conditions that change with time, and making a comprehensive determination of these monitoring results. 2. A hardware management means for managing the mounting state of the hardware, a maintenance / operation management means for managing information related to the operation of an exchange service registered from the maintenance console by the maintenance person, and a system A control and monitoring means for controlling the generation, activation, termination, and deletion of tasks and periodical monitoring of the status of the tasks, and a collection means for collecting call processing traffic are provided, and an optimal and minimum task configuration is always provided in operation. 2. The load control system for an exchange according to claim 1, wherein the task multiplicity is controlled so that 3. The hardware management means comprises a device management section for managing the mounting state and quantity of the hardware, and the maintenance / operation management means registers subscribers, station lines and services registered from the maintenance console. The control / monitoring unit includes a task state management unit that manages the task configuration in the system, and a call control unit that implements an exchange service process in the task unit. The collection means comprises a traffic information collection unit that collects call processing load information in response to a notification from the call control unit, manages scheduling of task execution over the entire system, and memory resources for the task. An exchange system according to claim 2, further comprising an operating system for allocating Load control method.