KR100321082B1 - Transit call trace method - Google Patents

Abstract

The present invention is to determine the type of relay call (E1, T1) of the call requesting tracking to limit the tracking range to track only those corresponding to the relay call requesting tracking, so that the call tracking can be quickly made. It is related to the tracking method, and it is possible to selectively track only a specific signal method for a relay call in which the signaling method of the relay call is mixed, thus improving the maintenance efficiency of the system, and the operator only tracks the specific signaling method. Because of the choice, it is easy to manage and analyze the call performance of a specific signaling method, which provides the advantage of convenient and accurate system operation.

Description

Relay call trace method

The present invention relates to a relay call tracking method, and in detail, determines a relay call type (E1, T1) of a call requesting tracking to limit the tracking range so that only the call corresponding to the relay call that requires tracking is traced. Therefore, the present invention relates to a relay call tracking method for speeding up call tracking.

In the conventional call tracking method, if an operator wants to track a relay call of a specific signaling method, there is no way to select it. Therefore, the call tracking must be performed for all signaling methods assigned to the relay call, and then the operator directly selects the corresponding signal. There was an inconvenience.

In addition, since there is only one method in the case of T1 (North American 1.544Mb / s), E1 (European 2.048Mb / s), and one type of relay call, there is no difficulty in tracking the call. In the case where a mixed method is assigned, there is a problem that the operator must selectively determine the information being tracked because there is no way to accept the relay call of a specific signaling method if necessary.

In order to solve the conventional problems as described above, the present invention enables the operator to track only a specific signal method for a relay call in which the signaling method of the relay line is used in a mixed manner, thereby improving accuracy of the call tracking. In addition, an object of the present invention is to implement a relay call tracking method, which enables an operator to perform convenient relay call tracking.

1 is a flow chart illustrating a relay call tracking process according to the present invention.

FIG. 2 is a flowchart illustrating a process of storing a call processing library block relation when the input parameter of FIG. 1 is a relay line or a link type. FIG.

3 is a schematic block diagram of a call tracking path management unit to which the present invention is applied;

4 is a schematic block diagram of a root data processing unit to which the present invention is applied;

5 is a schematic block diagram of a number data processing unit to which the present invention is applied;

<Description of Symbols for Major Parts of Drawings>

31: call tracking path management unit 32: command execution control unit

33: route control unit 34: call tracking and route setting unit

35 subscriber monitoring unit 36 output control unit

37: number translation unit 38: root data processing unit

39: relay line data processing unit 40: telephone maintenance processing unit

41: call tracking path management unit 42: signaling service control unit

43: relay line matching unit 44: number data processing unit

45: operator request control unit 46: analog subscriber control unit

47: ISDN data processing unit 48: packet data processing unit

In the relay call tracking method for achieving the above object, a call tracking path manager analyzes a parameter of the command when a call tracking command by an operator is input when a command for a call tracking service that is not currently registered is input. And if the parameter is a relay line type and is related to an access switching processor (ASP) or a device, register a call trace for a specific relay line type in a local switching library block (LSL), and transmit a status transmission request signal for each step. A second step of storing the LSL relation and waiting for the occurrence of a relay call; if the parameter is a relay line type and is related to a relay line or a link, call tracking for a specific relay line type is registered with a call sequence library (CSL), Storing a state transmission request signal in the CSL relation and waiting for the occurrence of a relay call A third step of performing call tracking only for a specific type of relay line when the relay call is generated; in the second step, the type of relay line is determined by analyzing the input parameter; The type of relay line may be determined by analyzing the included data.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a flow chart illustrating a relay call tracking process according to the present invention, when a call tracking command is input, the call tracking related command management area 1 checks the type of command input by the operator and then checks the type of the corresponding command. Call tracking services such as R2 signal tracking, trunk line monitoring, digit monitoring, ISUP signal tracking, next generation AIN call tracking, and TCAP tracking Analyze if required (S11).

Then, it is determined whether the input call tracking is already registered, and if there is no registered call tracking service, the received call tracking data is transmitted to the call tracking command processing area 2, and the registered call tracking service exists. If the call tracking is in progress, the input call tracking request is error-processed (S12).

In the call tracking command processing area 2 receiving the call tracking command, a new call tracking is registered in a buffer (not shown) for managing call tracking data, and whether or not processors to perform the requested call tracking are implemented. Investigate and check whether the state of this processor is normal (S21).

If the status of the processor is abnormal as a result of the check, the registered data is deleted and error processing is performed. In contrast, in the normal case, a call tracking is requested by calculating an address of an actual processor in which the relay call for call tracking exists. .

On the other hand, in the call tracking management area 3 existing in the processor where the call is generated, in order to be able to process the data when the call tracking command management area 1 is transmitted, the processor processing the call tracking request call is tracked. After calculating the address of the processor to track the target call, the signal is linked to prepare for call tracking (S31).

In this state, when the call tracking request is input from the call tracking command processing area 2, the call tracking starts. The first step is to determine whether the parameter of the input call tracking command is a relay line type (S32).

As a result of the determination, if the relay line type is a parameter related to an access switching processor (hereinafter referred to as an ASP) and a device, call tracking is registered in a local switching library block (hereinafter referred to as LSL). After sending to the tracking area (4) it is stored in the LSL relation.

In this case, when the parameter is input to the device, it means that call tracking is performed for each T1 group or E1 group for each device. If the parameter is analyzed, it can be seen whether it is required to track the T1 group or the E1 group (S33).

In addition, if the determination result is a relay line type and a parameter related to trunk and link, call tracking is registered with a call processing library block (hereinafter referred to as CSL), and the stepped state transmission request signal is converted into a relay call tracking area ( 4) and store it in the CSL relation.

In this case, when the parameter is input through a relay line or a link, call tracking is performed only for the T1 signal type or only for the E1 signal type, and analyzing the data included in the link indicates whether it is required to track T1 or E1. There is (S34).

In addition, if the parameter type of the input command is a parameter related to the route other than the relay line, the step-by-step status transmission request signal is transmitted to the relay call tracking area 4 and then registered in the route control block (RCO). do.

In addition, if the parameter type of the input command is a digit number DN or a prefix number PFX, the stepped state transmission request signal is transmitted to the relay call tracking area 4, and then the number data processing unit (Number Data Handling) is described below. The number is translated in NDH) and registered in the relation (S35).

In this case, when the input command parameter is not a relay line type, that is, in step S34 and step S35, signal tracking means that call tracking is performed on all signal types regardless of the E1 and T1 signal types.

Subsequently, after completing each storing and registering step, the relay call corresponding to the relay call tracking is generated (S36).

Subsequently, when the operator desires a relay call in the standby state, the received data is checked to determine whether the operator occupies the channel of the desired signaling method (S41). Information about the connection status of the call and the use of the trunk line channel is output to the operator (S42), and if it is not occupied, the operator informs the operator where an error has occurred when canceling the call trace requested later. In order to know the channel occupied by the other signal system or the part where an error occurs, an error process (S43).

Meanwhile, when the input parameter is a relay line and a link type, a process of storing the CSL relation in detail will be described in detail. As shown in FIG. 2, when the command is input, the relay line state is checked, and if the state is not good, an error process is performed. (S341), if the relay line state is good as a result of the check, the relay line channel information assigned to the corresponding relay call to be tracked is read through the information of the E1 signaling method and the T1 signaling method, and the signaling method selected for the relay call tracking is actually tracked. It is determined whether or not it is assigned to the relay call that you want to (S342).

If it is determined that the corresponding relay line does not exist, error processing is performed, and if the relay call exists, data such as a good state and an allocated range of the support signaling channel are read (S343), and the stepped state transmission request signal is transmitted to the relay call tracking area. After transmitting to (4), the relay line call tracking registration information of the corresponding signaling method (T1 or E1) is stored in the CSL relation (S344).

Through the above process, the call tracking can be quickly performed because only the signaling required by the operator can be tracked.

In the present invention, the basic call tracking algorithm uses an algorithm currently used, and when performing this algorithm, the call tracking is performed by distinguishing which signaling method the call tracking requested by the operator corresponds to. It can be easily implemented.

Hereinafter, a process of processing the critical blocks when the above process is performed will be described.

First, a call tracking path management unit, which is a main block operated in the call tracking management region 3, will be described with reference to FIG.

Call Trace Path Management (hereinafter referred to as CTPM) 31 is mounted on an operator maintenance processor (CCP) (not shown) of the central control system (CCS) (not shown). Functions performed by the operator's request (call assignment path configuration, call line reconfiguration, subscriber call tracking, subscriber monitoring, R2 signal tracking, relay line monitoring, Digit monitoring, ISUP signal tracking, AIN call tracking, TCAP It analyzes and processes MMC commands for tracing) and receives the results of function execution from related blocks (CTPS, SOBS, RCO) and outputs them to the operator.

That is, designated route configuration request and result output function, call line reconfiguration request and result output function, call tracking request, stop and result output function, R2 trace request, stop and result output function, subscriber monitoring request, cancellation, inquiry, deletion Result output function, trunk line monitoring request, cancellation, inquiry and result output function, digit monitoring request, cancellation, inquiry and result output function, ISUP signal tracking request, cancellation, registration information output and result output, etc. Function of.

Looking at the operation process, it receives the operator's command from the command execution control unit 32 (ⓐ). Subsequently, the RPM signal tracking function is registered from the CTPM 31 to the root control unit 33 (corresponding to the case where the parameter of the input command is the root) (ⓑ).

Then, the CTPM 31 requests the call tracking and routing unit 34 to perform a function of configuring a designated path, reconfiguring, call tracking, and R2 signal tracking (©), and monitoring the subscriber with the subscriber monitoring unit 35. It requests to perform the function (ⓓ) and receives the result of the execution (ⓔ).

Subsequently, after receiving the result (the designated path configuration, reconfiguration, call tracking, and R2 signal tracking result) performed by the call tracking and routing block 34 (ⓕ), the route control unit 33 tracks the R2 signal. Is registered (ⓖ), and the output control unit 36 outputs the result when the output is requested (ⓗ).

In addition, if the subscriber number translation requested from the number translation unit 37 is requested (ⓘ), the subscriber number is translated and notified of the result (iii).

On the other hand, the root data processing unit, which is the main block operated in the call tracking management area 3, will be described with reference to FIG.

The route data processing unit (RDH) 38 is driven by an operator request, and the input command is received from an instruction control unit (EC) 32 and processed by the following procedure.

That is, when the command type analysis is completed, a procedure call or a child process is executed to execute the command. Subsequently, various data are manipulated using a data manipulation word DML to collect information and perform commands, and output the result to the output controller 36.

Referring to this through the drawing, when a command related to the route / relay line by the operator is input from the command execution control unit 32 (ⓐ), the corresponding process is performed and the result is output through the output control unit 36 (ⓑ). F. When the route information is output to the route control unit 33, the ASP search pointer is required, when the relay line is added / deleted, the ASP number addition / deletion request for the route and the relay line counting are requested, and the registration / cancellation of the reservation counter value is notified. (Ⓒ)

In addition, the Trunk Data Handlig (TDH) 39 notifies the relevant information when the route information is changed, requests the unmounted trunk line information, requests the search point of the relay line when the route information is output, and the signal specification of the relay line. (Time) Notifies changed information when changing information, notifies relay line added / deleted when relay line is added / deleted, requests relay line status information for each ASP of route when outputting state of relay line mounted on route, and relay line is mounted. When changing the self carrier of the route from T1_E1 to T1 / E1, it is required to confirm the existence of the T1 / E1 relay line of the route (ⓓ).

The route data processing unit 38 requests the telephone maintenance processing unit 40 to calculate the number of blocked relay lines when outputting / changing route information, and notifies the relay line of busy / free status when deleting the relay line. (Ⓔ)

In addition, the CTPM 41 receives the relay line R2 tracking registration request (ⓕ), the signal service control unit 42 requests monitoring for the status management of the ASP (ⓖ), and the relay line matching unit 43 adds a relay line / Notify the relay line information when deleting.

On the other hand, the number data processing unit, which is the main block operated in the call tracking management area 3, will be described with reference to FIG.

All functions processed in the NDH 44 are driven by the operator's request, and the input command is received from the command execution control unit 32 and processed by the following procedure.

That is, when the command type analysis is completed, a procedure call or a child process is executed to execute the command. Subsequently, various data are manipulated using a data manipulation word DML to collect information and perform commands, and output the result to the output controller 36.

When this is described with reference to the drawing, when a command related to a station number is input by an operator from the command execution control unit 32 (ⓐ), a corresponding process is performed and the result is output through the output control unit 36 (ⓑ). The operator request control (ORC) 45 checks the directory number for adding / deleting / changing / outputting a general voice subscriber and registering / deleting a special service and performing the request and checking the result. Send the output message to the block (ⓒ).

The NDH 44 sends a signal to the ASP from the NDH 44 to output an unassigned line among the ASP lines inputted to the analog subscriber controller 46, and outputs the unallocated line. Ⓓ) ISDN Data Handling (ISDNH 47) checks the directory number for ISDN subscriber addition / deletion / change / output request and special service registration / deletion To send the output message (ⓔ).

Finally, PacKet Data Handling (RKDH) 48 checks the directory number for packet subscriber addition / deletion / change / output request and special service registration / deletion, performs the request, and sends the result to the corresponding block. Output an output message (ⓕ).

As described in detail above, the present invention can increase the maintenance efficiency of the system because it is possible to selectively track only a specific signaling method for the relay call in which the signaling method of the relay call is mixed. Since only the traces can be selected, it is easy to manage and analyze the call performance of a specific signaling method, which provides a convenient and accurate system operation.

In addition, preferred embodiments of the present invention are disclosed for the purpose of illustration, those skilled in the art will be able to various modifications, changes, additions, etc. within the spirit and scope of the present invention, such modifications and modifications belong to the following claims You will have to look.

Claims (2)

A first step of, if a command for a call tracking service not currently registered is input, a call tracking path management unit analyzing a parameter of the command if a call tracking command is input by an operator; If the analysis results that the parameter is a relay line type and is related to an access switching processor (ASP) or a device, a call tracking for a specific relay line type is registered with a local switching library block (LSL), and a step-by-step state transmission request signal is transmitted to the LSL relation. A second step of storing and waiting for the occurrence of the relay call; If the parameter is a relay line type and a relay line or link, the call tracking is registered with a call sequence library (CSL) for a specific relay line type, and the stepped state transmission request signal is stored in the CSL relation, and then the relay call is generated. A third step of waiting; When the relay call is generated consists of a fourth step of performing call tracking only for a specific type of relay line, In the second step, a relay line type is determined by analyzing the input parameters, and in the third step, a relay line type is determined by analyzing data included in the link. The method of claim 1, In the fourth step, a call tracking is performed only for a specific signal method specified by an operator among a plurality of signal methods including a T1 signal method, an E1 signal method, and a T1-E1 signal method.