KR100964118B1 - Method for releasing call setup in full electronic telephone exchange - Google Patents

Abstract

The call processing recovery method in the electronic switch according to the present invention is a process in which a test is performed when there is a response of a test process and a corresponding process by checking a response of a test process and a corresponding process according to call setup information. Determining a call setup state according to a result of comparing the response information and the corresponding process response information; And when there is no response of the process or corresponding process in which the test is performed or the process response information on which the test is performed and the corresponding process response information do not coincide with each other, the call setup processor determines that the call setup state is not returned. Recovering the call setup according to the normal call release procedure of the system, detecting errors such as the recovery of the line state and the inability to recover the internal memory (call register (CR)) among the resources used for call setup It can be used to set up another call.

Description

Method for releasing call setup in full electronic telephone exchange}

1 is a block diagram showing a functional block of an electro-electronic exchanger according to the present invention.

2 is a flowchart illustrating a method of outputting call setup details in an electronic switch according to the present invention.

3 is a flow chart illustrating a method of performing a test on call setup to recover a call that was determined to be non-resilient.

FIG. 4A is a flowchart illustrating a recovery method when the call setup is in the call register state in the call setup recovery step of the flowchart shown in FIG. 3; FIG.

FIG. 4B is a flowchart showing a recovery method when the call setup is in a line state in the call setup restoration step of the flowchart shown in FIG. 3; FIG.

5 is a flow chart illustrating a function of specifying and recovering a specific call register by an operator.

The present invention relates to a method for recovering a call setup in an electronic switchboard, and more particularly, outputs information such as an occupied line number, an internal memory index, etc., by a subscriber or part of a supplementary service in a call, and among the resources used for call setup. The present invention relates to a call recovery method in an all-electronic exchange that can detect and recover errors such as line state recovery, inability to recover internal memory (call register (CR)), and the like, to set up another call.

A typical full electronic telephone exchange is a software controlled system.

Call attempts from an incoming trunk circuit (ICC) or digital subscriber line (DSL) may be received by a subscriber line control processor or an integrated services digital network user part (ISP). Is detected by a message, and a process A for controlling it is created, and a memory area (call register (CR)) for storing necessary data is allocated.

In addition, control procedures such as number translation and outgoing trunk circuits are carried out to notify the processor controlling the outgoing circuit, and the processor establishes a corresponding process B and stores necessary data. An internal memory area (call register CR) is allocated.

Process A and corresponding process B, where the test is performed, control and set up the call by exchanging information with each other to set up the call, and perform the call release procedure by exchanging and receiving the information necessary to release the call even when the call is released. Processes A and B end.

However, in a large-capacity system that handles many calls, the subscriber terminates the call due to clock instability in the system, logical errors in the software, and signaling failure with the power, but the resources of some switching systems are not recovered. This happens.

Therefore, when a new call is set up, the unrecovered lines and internal memory are not used, and thus there is a problem in that they do not fully utilize switching system resources.

An object of the present invention for solving the above problems is to output a call setup history by the subscriber or part of the additional service in the call even for the line in the call.

Another object of the present invention for solving the above problems is to detect and recover an error such as the recovery of line status, the inability to recover the internal memory (call register) among the resources used for call setup, and can be used when setting up another call. It is.

Another object of the present invention for solving the above problems is to be able to recover arbitrarily by specifying a specific internal memory (call register) by the operator.

Call setup recovery method in the electronic switch of the present invention for achieving the above object,
Outputting call setting information on a line in a call;

delete

According to the call setup information, the process of the test is performed and the response of the corresponding process is checked, and if there is a response from the process of the test and the corresponding process, the process response information of the test is performed and the corresponding process response information. Determining a call setup state according to the comparison result; And
In the determining of the call setup state, if there is no response of the process or the corresponding process in which the test is performed, or if the process response information in which the test is performed and the corresponding process response information do not match, it is determined that the call setup is not repaired. Restoring the call setup according to a normal call release procedure of the call processing processor.

The above and other objects and features and advantages of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings.

delete

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a view showing a functional block of an all-electronic exchanger according to the present invention. Only the functional blocks associated with the present invention are shown here.

The electronic switch 10 includes a main processor 1, a processing processor 2, a database 3, a display 4, and a call register 5.
Here, the main processor 1 analyzes and determines the operator's instructions.

The processing processor 2 processes the corresponding functions according to the instructions analyzed and determined by the main processor 1.

delete

The database 3 stores information such as call setting details and call tracking data.

The display 4 outputs the result according to the operator's command and displays it so that the operator can recognize it.

The call register 5 is a memory area that stores data necessary for controlling and processing a call inside the processor. The call register 5 is repeatedly used while a predetermined number of call registers CR are circulated. Here, a general call that is not using an additional service uses one call register CR.

2 is a flowchart illustrating a method of outputting call setup details in an electronic switch according to the present invention. Here, in order to carry out the method according to the present invention, an additional parameter CONN for setting the line state is established in the call tracking command TRC-CALP.

When the call tracking command TRC-CALP is input by the operator (S1), the input parameters are checked (S2). If there is no error, the additional parameter CONN is checked (S3). However, by checking the input parameters (S2), if there is an error and outputs an error result (S4).

If the value of the additional parameter CONN is TRUE, since the line state is set to busy, it is checked whether the actual line state is using the supplementary service or on a call, that is, busy (S5). If the line state is in use, the main processor 1 makes a call setup history output request to the database 3 (S7). However, if the line state is not in use (idle) (S5), an error result is output (S8).

On the other hand, when the value of the additional parameter CONN is FALSE, regardless of the additional parameter CONN, the call setup check function for the call that is not in a call is performed according to the existing call tracking command RTC-CALP (S6).

The database 3 transmits the call setup details to the processing processor 2 in response to the call setup history output request (S9). Therefore, the processing processor 2 outputs the call setting details through the display 4 (S10). Here, the call establishment details include the individual line information of the special service or additional service subscriber and the subscriber to which the call is set, and the corresponding side information in the same system.                     

3 is a flow chart illustrating a method for recovering a call that has been determined to recover by performing a test on call establishment.

When the call test command TEST-CALL is input by the operator (S11), the input parameter is checked (S12), and if there is an error, an error result is output (S13) and the test is terminated.

If the input parameter is normal (S12), it is checked whether there is a response of the process A in which the test is performed (S14), and if there is a response, the response is requested to the corresponding process B (S15).

If there is a response of the corresponding process B (S16), if there is a response, it is checked whether the response information of the process A on which the test is performed and the response information of the corresponding process B are consistent (S17).

If the response information of the process A on which the test is performed and the response information of the corresponding process B coincide, it is determined that the test is performed as a normal call (S18) and the test ends.

On the other hand, when there is no response of the process A on which the test is performed, when there is a response of the process A on which the test is performed, but there is no response of the corresponding process B, and the response information of the process A on which the test is performed and the response of the corresponding process B If the information does not match, it is determined that the call setup is not restored (S19), the call setup is restored (S19), and the test is finished. Here, the call setup includes a call register CR state and a line state.

In the call setup mismatch recovery function, the judgment criteria and recovery range change according to the test target.

FIG. 4 is a flowchart for performing a call setup recovery function in the flowchart shown in FIG. 3.

First, it is checked whether the current test mode is a release mode (S21).

If the current test mode is the recovery mode, it automatically recovers the call setting determined to be not recovered (S22).

When the recovery is completed for the determined call recovery, the recovery result is output (S23) and the recovery function is terminated.

If the current test mode is a simple test mode (test mode) other than the recovery mode, the test result is output (S24) and the recovery function is terminated.

Here, the call setup determined to recover from includes a call register state and a line state. If the call register state is recovered, the call register CR and Child PID are restored, and if the line state mismatch is restored, the line state is restored.

First, the determination criteria and the recovery range for processing the call register state mismatch recovery function are shown in [Table 1]. Here, a case in which the call register CR is used for the processor A on which the test is performed and all the CG / CD information is described will be described.                     

TABLE 1

Processor A under test Processor B judgment restore CR CG / CD
Information Child PID
Confirm Line status CG / CD Information Child PID Check Line status use has exist match busy Same as A match busy Normal arc use has exist mismatch idle No confirmation required CR recovery CR recovery use has exist match busy No information matched with A CR / PID
Recovery CR / PID Recovery use has exist mismatch busy No information matched with A CR / Line recovery CR recovery

Here, CG / CD represents a calling number / called number, and Child PID is a unique value of processor A, which means call register CR table information and line line state table information.

In the first case, the response information of process A where the test is performed matches the result of checking the Child PID, that is, the information in the call register CR table and the information in the Line state table match, and the line state is busy. (busy), since the response information of the corresponding process B coincides with the response information of the process A, it is determined as a normal call.

In the second case, the response information of the process A on which the test is performed does not match the result of checking the Child PID, that is, the information in the call register CR table does not match the information in the line Line state table, Since it is not in use, the call register CR on the processor A side on which the test is performed is not recovered without requiring a response from the corresponding processor B, and the call register CR is recovered.

In the third case, the response information of process A where the test is performed matches the result of checking the Child PID, that is, the information in the call register CR table and the information in the line Line state table match, and the line state is in use, Compared with the response information of the corresponding processor B, since there is no matching information, both the call register CR and the child PID are judged to be non-recovery, and both the register and the child PID are recovered.

In the fourth case, the response information from process A where the test is performed does not match the child PiD, which means that the information in the call register CR table and the information in the line Line state table do not match, but the line state is used. The call register CR and the line state recovery are determined because the response information of the corresponding process B does not match the response information of the processor A under test. The current test mode is the call register state mismatch recovery function. Therefore, only the call register CR is recovered.

On the other hand, the determination criteria and the recovery range for the processing for the line state mismatch recovery function is as shown in [Table 2]. Here, an example will be described in which the processor A performing the test is busy with line setting and all the CG / CD information.

TABLE 2

Processor A under test Processor B judgment restore Line setting CR status Child PID
Confirm Line status CG / CD
Information Child PID
Confirm Line
condition busy use match busy Same as A match busy Normal arc busy use mismatch idle No confirmation required CR recovery CR recovery busy use match busy No information matched with A CR / PID recovery CR / PID Recovery busy use mismatch busy No information matched with A CR / Line recovery Line recovery busy Unused - - No information matched with A Line recovery Line recovery

Here, CG / CD represents a calling number / called number, and Child PID is a unique value of processor A, which means call register CR table information and line line state table information.

In the first case, the response information from process A where the test is performed matches the result of checking the Child PID, that is, the information in the call register CR table and the information in the line Line state table match, and the line state is busy ( busy), and the response information of the corresponding process B coincides with the response information of the process A, so it is determined to be a normal call.

In the second case, the response information of process A where the test is performed does not match as a result of checking the Child PID, that is, the information in the call register CR table does not match the information in the line Line state table, and also uses the line state. Since it is not in use (idle), the call register CR on the processor A side where the test is performed without requesting a response from the corresponding processor B is determined to be recovered, and the call register CR is recovered.

In the third case, the response information from process A where the test is performed matches the result of checking the Child PID, that is, the information in the call register CR table and the information in the line Line state table match, and the line state is also in use ( busy), but because there is no matched information when compared with the response information of the corresponding processor B, both the call register CR and the child PID are judged to be non-recovery, and both the register CR and the child PID are recovered.

In the fourth case, the response information from process A where the test is performed does not match the child PID result, that is, the information in the call register CR table and the information in the line Line state table do not match, but the line state is used. Busy and the call register CR and line state recovery are determined because the response information of the corresponding processor B does not match the response information of the processor A under test. The current test mode is the line state mismatch recovery function. Only the line state is restored.

In the fifth case, the response information of the process A in which the test is performed is determined to be a line state recovery because the line setting is busy but the call register CR is not in use and recovers the line state.

If it is determined that the recovery of the line state other than the above is true, the state of the line input by the operator is managed as being in use. However, if there is no processor using the line and the state of the line input by the operator is managed as being in use. However, there is a case where the corresponding processor B registered in the call register CR has no response or does not match the information of the processor A.

In such a case, it is determined that the circuit is not recovered, and the line state is restored.

In this way, in the main processor 1 of the electronic switchgear 10, when a call is set, a process A for controlling an originating call and a corresponding process B corresponding thereto are paired to control the setting of the call. Control number PID and corresponding line number CG / CD.

Therefore, by comparing the process line information of process A with the information of the corresponding process B, it is possible to confirm whether the line is actually on the line, and if the line is not busy and the line state is busy or occupies the call register CR. Retrieve it and make it available when setting up another call.                     

5 is a flowchart illustrating a function in which a specific call register is designated and restored by an operator.

First, when the call register recovery command RESET-CR is input (S41), the input parameters are checked to be normal (S42), and it is checked whether the designated call register CR is in use (S43).

If the input parameters are not normal, an error result is output (S44) and the call register recovery function ends.

If the designated call register CR is in use, the call register CR is reset (S45).

If the designated call register CR is not in use, an error result is output (S46) and the call register recovery function is terminated.

When the reset operation for the designated call register CR is completed, the reset result is output (S47), and the call register recovery function is terminated.

As such, the call tracking function can output the self processor A and the corresponding processor B information of the line currently being used to output all the call setting details of the subscriber who is performing the specific service. Maintenance function will be easy and easy.

In addition, special functions such as call transfer and call forwarding service are implemented, but an additional function of outputting call setup history is implemented even when the corresponding subscriber status is not in a call.                     

It will improve the efficiency and stability of resources in the system by searching the call register CGs by processor to determine whether the information contained in each call register is normal and automatically recovering, as well as individual recovery functions by operator instructions. .

In addition, it is possible to prevent the difficulty of complaints or system maintenance due to the line state mismatch occurring in the field by determining whether the line state of the subscriber and the relay line are inconsistent, and to quickly take action when maintenance is required.

As described above, the call processing data mismatch determination and recovery method in the electronic switch according to the present invention, by applying a call trace facility (CTF) function to the line in the call, the information of the call currently set even during a call There is an effect that can be output.

In addition, by determining the actual use of the line and the memory occupied by the actual call, and the ability to recover the line when the line is not actually used, the recovery of resources caused by a temporary error accumulates to accumulate the entire resource There is an effect that can be prevented from being wasted.

It will be apparent to those skilled in the art that various modifications, additions, and substitutions are possible, and that various modifications, additions and substitutions are possible, within the spirit and scope of the appended claims. As shown in Fig.

Claims (18)

Outputting call setting information on a line in a call; The process of the test is performed according to the call setup information and the response of the corresponding process is checked, and if there is a response of the process from which the test is performed, the process response information from which the test is performed is compared with the corresponding process response information. Determining a call setup state according to the result; And In the determining of the call setup state, if there is no response of the process or the corresponding process in which the test is performed, or if the process response information in which the test is performed and the corresponding process response information do not match, it is determined that the call setup is not repaired. And restoring the call setup according to a normal call release procedure of a call processing processor. The method of claim 1, And outputting the call setting information comprises executing a call setting information output command from an operator. The method according to any one of claims 1 and 2, The step of outputting the call setup information, Identifying an input parameter; If the input parameter is intact, checking an additional parameter indicating a setting for a corresponding line; Checking whether the line state of the additional parameter is actually in a call for the corresponding line when the setting for the corresponding line is set to busy; And And outputting call setup information when the corresponding line is actually in a call. The method of claim 1, The determining of the call setup state may include performing a call test command from an operator. The method of claim 1, Determining the call setup state, Identifying an input parameter; If the input parameter is normal, confirming a response of the process in which the test is performed; Confirming a response of the corresponding process when there is a response of the process in which the test is performed; Comparing the response information of the process in which the test is performed with the response information of the corresponding process when there is a response from the corresponding processor; And And confirming a call setup state according to the result of the comparing step. The method of claim 5, And the call setup state is a state of a call register. The method of claim 6, Checking the response of the processor on which the test is performed, Checking whether the call register is in use; Identifying a unique value of a processor on which the test is performed; Checking whether there is outgoing information and incoming information; Checking whether a line corresponding to the call register in use is busy; And Whether or not the call register is used, a result of confirming a unique value of the processor on which the test is performed, whether or not the processor is performed according to the state of the corresponding line and the presence or absence of the originating and incoming information, and the state of the corresponding line And determining the call processing. The method of claim 7, wherein The step of identifying a unique value of the processor on which the test is performed comprises comparing the data stored in the call register information table with the data stored in the corresponding line state table. Method to recover call processing from a server. The method according to claim 6 or 7, Checking the response of the corresponding process, Checking whether there is outgoing information and incoming information; Identifying a unique value of the corresponding process; Checking whether the line on which the test is performed is busy in the process in which the test is performed; And Determining whether or not the corresponding processor responds according to a result of checking the presence or absence of the originating and incoming information, a unique value of the corresponding process, and the state of the corresponding line. Process recovery method. The method of claim 9, Identifying the intrinsic value of the corresponding processor comprises comparing the data stored in the call register information table of the process where the test is performed with the data stored in the corresponding line state table. How to recover call processing in an electronic exchange. The method of claim 5, And the call establishment state is a line state. The method of claim 11, Checking the response of the processor on which the test is performed, Checking in what state the line state is being managed by an operator; Checking whether a call register corresponding to a line whose line state is being managed by an operator is in use; Checking whether there is outgoing information and incoming information; Identifying a unique value of a processor on which the test is performed; If the corresponding call register is in use, checking whether the corresponding line is busy; And Determining whether the processor performing the test is in response to a result of checking the presence or absence of the calling information and the incoming information, the unique value of the process in which the test is performed, and the state of the corresponding line. How to repair call processing in an electronic exchanger. 13. The method of claim 12, The step of identifying a unique value of the processor on which the test is performed comprises comparing the data stored in the call register information table with the data stored in the corresponding line state table. Method to recover call processing from a server. The method of claim 11 or 12, Checking the response of the corresponding process, Checking whether there is outgoing information and incoming information; Identifying a unique value of the corresponding process; Checking whether the line on which the test is performed is busy in the process in which the test is performed; And Determining whether or not the corresponding processor responds according to a result of checking the presence or absence of the originating and incoming information, a unique value of the corresponding process, and the state of the corresponding line. Process recovery method. The method of claim 14, Identifying the intrinsic value of the corresponding processor comprises comparing the data stored in the call register information table of the process where the test is performed with the data stored in the corresponding line state table. How to recover call processing in an electronic exchange. The method of claim 1, The call processing recovery method in an electronic switch, characterized in that further comprising the step of designating and recovering a specific call register by the operator. The method of claim 16, Restoring the specific call register, And a call register recovery command inputted by the operator to be performed. The method according to any one of claims 16 and 17, Restoring the specific call register, Identifying input parameters; If the input parameters are normal, checking whether the particular call register is in use; And And resetting the call register if the particular call register is in use.

Images