KR20010086641A - The method of managing a call register of the communication switch - Google Patents

Abstract

PURPOSE: A method for managing a call resistor in a communication switching system is provided to efficiently improve the performance of a switching system by increasing the speed for an idle call resistor and reducing the load used required for finding the same. CONSTITUTION: In an initial state(S21), a first_index which shows a first number of an idle call resistor in an idle_callreg arrangement for managing the idle call resistor is initialized to 0 and a last_index representing a last number is initialized to 2047. In a call resistor assignment request process(S22), when a call resistor assignment request is arrived, the process proceeds to a first_index value checking process(S23), to check whether the value of the idle_callreg corresponding to a current first_index is -1. After the first_index value checking process(S23), the process proceeds to a first_index value return and true setting process(S25). If the value of the idle_callreg corresponding to the current first_index is -1 in the checking process(S23), the process returns -1 to a library block and notifies that there is no the idle call resistor. Otherwise, if the value of the idle_callreg corresponding to the current first_index is not -1 in the checking process(S23), the process(S25) returns the value of the idle_callreg corresponding to the current first_index to the library block and sets a usage_flag to true, to thereby indicate an assignment status and set the first_index value to -1. An index comparing process(S26) determines whether the first_index and the last_index are equal or not. If they are equal to each other, the process proceeds to an index value setting process(S27) and sets the value of the first_index and the last_index to -1. Otherwise, the process proceeds to an index increasing process(S28) and increases the first_index by 1. In an index comparing process(S29), if the first_index increased in the increasing process(S28) is more than 2047, the process sets the first_index to 0(S30). Otherwise, the process proceeds to the first_index value checking process(S23).

Description

Call register management method in communication exchange {THE METHOD OF MANAGING A CALL REGISTER OF THE COMMUNICATION SWITCH}

The present invention relates to a method of managing a call register in a communication exchange, and in particular, a separate arrangement for managing idle call registers so as to quickly find an idle call register and allocate or release a call register. A call register management method in a communication exchange is provided.

In general, a switch in a communication system includes a call register having a structure of call processing related variables in an ASS (Access Switching Subsystem), which has 2048 structures having a structure arrangement structure. have.

In addition, the call register uses an array for knowing whether to allocate call registers, that is, usage_flag having 2048 arrays, to manage the number of call registers being used. Use an array, used_callreg_cnt, and present_callreg_no, which represents the index of the call register to look for.

Referring to (a) and (b) of FIG. 1, the conventional call register allocation and decommissioning operations will be described first. In the case of call register allocation, a library block named MSL, which manages the allocation and decommissioning operations of the call register, is loaded. (Loading) initializes the usage_flag array to FALSE, which is unallocated, and initializes used_callreg_cnt and present_callreg_no to 0 (S1).

Then, when a call register allocation request comes (S2), the internal variable i for finding an idle call register among the 2048 call registers is initialized to 0 (S3), and then usage_flag is allocated with present_callreg_no indicating the index of the call register to start searching. Check whether the state is true (SUE) (S4).

As a result of checking in step S4, if usage_flag is true, first, present_callreg_no is increased by 1 (S5), and if present_callreg_no is greater than 2047 (S6), present_callreg_no is 0 to find an idle call register until a false appears. Set to (S7) and increase the internal variable i by 1 (S8), and if present_callreg_no increased in step S5 is less than 2047 (S6), proceed directly to step S8 to set internal variable i to 1; Increase.

Subsequently, if the internal variable i increased in the step S8 is less than 2047, the process proceeds to the step S4, and the following steps are repeated. Signal that there is no call register.

On the other hand, if the usage_flag is found to be false, the usage_flag is set to true by allocating a call register, the used_callreg_cnt is increased by 1, and present_callreg_no is returned to the library block (S11).

That is, after initializing the internal variable i to find the call register to 0 and incrementing by 1, it searches up to 2048 and if there is an idle call register, sets usage_flag corresponding to present_callreg_no to true, increases used_callreg_cnt by 1, and sets present_callreg_no to the library. Return to the block.

If there is no idle call register, -1 is returned to the library block indicating that there are no more idle call registers.

Subsequently, when the call register release request is received (S12), the used_callreg_cnt is decreased by 1, the call register is released, and usage_flag corresponding to present_callreg_no is set to false (S13).

In this case, since a call occurs first, it is not released first, and after a certain amount of call progress, as shown in FIG. 2, the usage_flag array has a value irregularly.

As described above, in order to find an idle call register when allocating and releasing a call register, the present_callreg_no needs to be incremented from 1 to 2048 to find an idle call register, as shown in FIG. 3. There was a problem to find 2048.

That is, as shown in FIG. 3, when used_callreg_cnt is 2047, one remaining call register must be found. Unfortunately, when present_callreg_no is one remaining call register number + 1, the worst case is one idle call register. To find 2048 is to find.

As described above, the conventional call register management method of searching for idle call registers by loops and managing call registers is not only inefficient in finding idle call registers but also inefficient, such as an increase in load due to a large number of seek operations. There was a problem with performance.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and its object is to provide a separate arrangement for managing idle call registers to quickly find idle call registers and to allocate or release call registers to find idle call registers. The present invention provides a method of managing a call register in a communication exchange that can increase the number of times and reduce the load required to find.

1 (a) and (b) is a flow chart showing the allocation and release operation of the conventional call register,

2 is a view showing an example after a call progresses to some extent to explain the release operation of a conventional call register;

3 is a diagram illustrating an example of a worst case occurring when allocating and releasing a conventional call register;

4 is a view illustrating initialization of an idle call register management array and index variables required when performing a call register management method of the present invention;

5 is a flowchart showing an operation of allocating a call register according to the call register management method of the present invention;

6 is a flowchart showing the release operation of the call register according to the call register management method of the present invention;

7 is a diagram showing an example of allocation of a call register by the call register management method of the present invention;

8 is a diagram showing an example of releasing a call register by the call register management method of the present invention.

The call register management method in the communication exchange of the present invention for achieving the above object sets an idle call register management array (idle_callreg) using first_index indicating the first number of idle call registers and last_index indicating the last number. After the idle call register management array setting step and the idle call register management array setting step are performed, the usage_flag corresponding to the idle_callreg value of first_index is set to true when the call register allocation is requested, and the value of the first_index is set to true. If call register release is requested after the call register allocation step of setting -1 and the idle call register management array setting step is performed, the first_index and last_index are increased to idle_callreg of last_index which is increased when the value of the first_index and last_index are not -1. Sets the number of the requested call register and uses the usage_flag call call released. That comprising the arc off register setting a False characterized.

Hereinafter, a call register management method in a communication exchange according to the present invention will be described in detail with reference to the accompanying drawings.

FIG. 4 is a diagram illustrating initialization of an idle call register management array and an index variable required when performing a call register management method according to the present invention. In the present invention, an arrangement for managing idle call registers, that is, idle_callreg, is separately provided. We use first_index for the first number of idle call registers in and last_index for the last number.

Referring to the flowchart of Fig. 5 the allocation operation of the call register by the call register management method of the present invention is as follows.

First, as shown in FIG. 4, the process proceeds to the call register allocation request step S22 in the initial state S21 and requests call register allocation.

In the initial state 21, first_index indicating the first number of idle call registers is initialized to 0 in the idle_callreg array for managing idle call registers, and last_index indicating the last number is initialized to 2047, respectively.

When the call register allocation request comes in the call register allocation request step S22, the process proceeds to the first_index value checking step S23 to determine whether the idle_callreg value corresponding to the current first_index is -1.

After the first_index value checking step (S23), return to the first_index value and true setting step (S25), if the value of idle_callreg corresponding to the current first_index in step (S23) is -1, -1 is returned to the library block and is idle. Notify that there is no call register (S24).

On the other hand, if the idle_callreg value corresponding to the current first_index is not -1 in step S23, the idle_callreg value corresponding to the current first_index is returned to the library block and the corresponding usage_flag is set to true to indicate the allocation status. The value of the first_index is set to -1 and left blank (S25).

After the first_index value return and true setting step (S25), go to the index comparison step (S26) to determine whether the first_index and last_index is the same, and if the first_index and last_index is the same, proceed to the index value setting step (S27) to first_index and last_index Set the value of to -1.

That is, since the first_index and the last_index are the same, it means that there is only one idle call register left. Therefore, the values of first_index and last_index are set to -1 to indicate that there are no more idle call registers.

If the first_index and the last_index are different, the process proceeds to the index increment step S28 to increase the first_index by 1 so that the next idle call register can be found continuously.

After the index increase step S28, the process proceeds to the index comparison step S29, and if first_index increased in step S28 is greater than 2047, first_index is set to 0 (S30), and if it is less than 2047, checking the value of the first_index. Proceed to (S23) to repeat the following process.

Next, the release operation of the call register according to the call register management method of the present invention will be described with reference to the flowchart of FIG. 6.

When the call register release request comes from the call register release request step S31, the process proceeds to the usage_flag check step S32 to determine whether the usage_flag to release the call register is true.

If the usage_flag of the call register requesting the release in the usage_flag check step (S32) is not true, it is regarded as a request for the release of the call register that is not allocated by the application program (S33).

In addition, if the usage_flag of the call register requesting the release is true in the usage_flag check step (S32), the process proceeds to the index value check step (S34) to determine whether the values of the first_index and the last_index are -1.

If the value of the first_index and the last_index is -1 in the index value checking step S34, the process proceeds to the index value setting step S35 and sets the values of the first_index and the last_index to zero.

That is, since the value of the first_index and the last_index is -1 means that the call registers are all in use and the first one is released and in an idle state, the first_index and the last_index are set to 0.

After the index value setting step S35, the process proceeds to the false setting step S36, sets the number of the call registers requested to be released in the idle_callreg corresponding to the last_index of the step S35, and sets a false number in the usage_flag in which the call register is released. Set it.

If the value of first_index and last_index is not -1 in the index value checking step S34, the process proceeds to the index increasing step S37 to increase the last_index by one.

After the index increase step S37, the process proceeds to the index comparison step S38. When the last_index increased in the step S37 is greater than 2047, the last_index is set to 0 (S39). In step S36, the call register number requested to be released is set in the idle_callreg corresponding to the last_index increased in the step S37, and a false is set in the usage_flag in which the call register is released.

7 is a diagram illustrating an example of allocation of a call register by the call register management method of the present invention, and FIG. 8 is a diagram illustrating an example of release of a call register by the call register management method of the present invention. Similarly, find the 200-numbered call register set in first_index = 4 in usage-flag and set it to true, and then increase the first_index by 1 to make first_index = 5 so that an idle call register with 200 number can be found and assigned. do.

Call register release also increases last_index by 1 to make last_index = 1 to last_index = 1, and then sets the number 200 of call registers released in idle_callreg corresponding to last_index = 1. The 200 number of the used usage_flag is set to false so that the call register with the 200 number previously allocated can be found and released.

As described above, the present invention provides a separate arrangement for managing idle call registers to quickly find an idle call register and allocate or release the call register to increase the speed of searching for an idle call register and to find it. The load can be reduced to handle more calls in the ASS, thereby effectively improving the performance of the exchange.

Claims (3)

An idle call register management array setting step of setting an idle call register management array (idle_callreg) using an index (first_index) pointing to the first number of idle call registers and an index (last_index) pointing to the last number; A call register allocation step of setting a usage_flag corresponding to the idle_callreg value of first_index to true and setting -1 to the value of the first_index when the call register allocation is requested after performing the idle call register management array setting step; After performing the idle call register management array setting step, when call register release is requested, the number of call registers requested to release is set in idle_callreg of last_index which is increased when the value of first_index and last_index is not -1, and A call register management method in a communication exchange comprising a call register release step of setting a fault in a usage_flag in which a register is released. The method of claim 1, wherein the call register allocation step, When a call register allocation request comes after initializing first_index and last_index of the idle_callreg, first_index value checking step of checking whether the value of idle_callreg corresponding to first_index is -1 indicating that there is no idle call register, and checking the first_index value. If the value of idle_callreg corresponding to first_index is -1 in the step, return -1 to the library block; otherwise, set the usage_flag corresponding to the idle_callreg value of first_index to true and set the value of first_index to -1 After performing the return and true setting step and the return and true setting step, determine whether first_index and last_index are the same. 1 increase the index comparison and index value setting step, and compare and index the index 'S value is increased at the setting step sets the first_index first_index greater than 2047 to 0, and less than 2047 method call register management in a communication switch which comprises a step of comparing the index proceeds to check the step first_index value. The method of claim 1, wherein the call register release step, When a call register release request comes in, it determines whether the usage_flag to release the call register is true, handles an error if usage_flag is not true, and if it is true, the usage_flag check and index value verification steps to determine whether the value of first_index and last_index is -1. And setting the values of first_index and last_index to 0 when the values of first_index and last_index are -1 in the usage_flag checking and checking index values step, and increasing the last_index by 1 when the value of first_index and last_index is -1; In the setting of the index value and the step of setting the index to set the number of the call register to be released to the idle_callreg of the last_index set in the step of increasing the index, and set the fall in the usage_flag the call register is released, and the increase in the index value setting and the index increment step If last_index is less than 2047, proceed to the above step of setting false; if greater than 2047, last An index comparison step of setting _index to 0, characterized in that the call register management method in the communication switch.