KR0168806B1 - Caller identification - Google Patents

Abstract

1. Technical field to which the invention described in the claims belongs: Method of storing after analyzing and reconstructing the stored calling number.

2. Technical problem to be solved by the present invention: The calling service through the gapless packet needs an algorithm for sending outgoing call after receiving the call request. On the other hand, after requesting the calling number for the incoming call into the system, an algorithm for analyzing the calling number is required to provide the calling number service to the extension terminal. However, in the related art, an algorithm for processing a gap class packet and an algorithm for analyzing a calling number are not implemented, and thus, the calling service cannot be provided.

3. Summary of the Invention Solution: The header data of the originating data is stored in the private exchange receiving the calling data corresponding to the calling party's telephone number from the sending exchange requesting the call through a gapless packet and storing it in a memory. A first step of retrieving the stored memory address, reconstructing the calling party data, and calculating a memory address to be stored; and reconfiguring and storing the calling party data continuously recorded in the header data into the memory address calculated in the first step; In step 2, if the repetition data indicating repetition of the same data as the calling data stored in the previous memory address is detected by analyzing the stored and stored calling number data, the third step of converting and storing the calling data stored in the previous memory address is stored. Reconstruction method through call number analysis.

4. Important uses of the invention: private exchange.

Description

Reconfiguration method through call number analysis

1 is a block diagram of a general private exchange.

2 is a control flowchart for receiving and storing a calling number according to the present invention.

3 is a control flowchart for analyzing and reconfiguring a call number according to the present invention.

4 is a private exchange internal memory map according to the present invention.

5 is a memory map for storing a received call number according to the present invention.

* Explanation of symbols for main parts of the drawings

110: CPU 112: memory

114: switching circuit 116: trunk line circuit

118: subscriber circuit 120: dedicated line circuit

122: DTMF reception circuit 124: DTMF reception circuit

126: tone supply circuit 128: interface circuit

The present invention relates to a private exchange, and more particularly, to a method for analyzing and reconstructing a call number received in a gapless packet.

The general gapless packet is a communication method used to transmit and receive an outgoing number during an exchange in Russia.

The calling service through the gapless packet requires an algorithm for receiving the calling request and sending the calling address. On the other hand, after requesting the calling number for the incoming call into the system, an algorithm for analyzing the calling number is required to provide the calling number service to the extension terminal.

However, in the related art, an algorithm for processing a gapless packet and an algorithm for analyzing a calling number are not implemented, so there is a problem in that the calling service cannot be provided.

Accordingly, an object of the present invention is to provide a method for analyzing and reconfiguring a calling number for providing billing, calling number authentication, and malicious call tracking service in a private exchange.

The present invention for achieving the above object, the process of storing the calling address data received in the gapless packet, the memory address in which the header data of the calling data is stored, and reconstructing the calling number data to calculate a memory address to be stored And reconstructing and storing the calling party data continuously recorded in the header data into the memory address calculated in the first step, and analyzing the reconfigured and stored calling party data and storing the calling party data stored in the previous memory address. When the repeating data indicating the repetition of the same data is detected, the process consists of converting and storing the calling party data stored in the previous memory address.

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

The configuration of the private exchange for carrying out the present invention is as shown in FIG. Referring to FIG. 1, the CPU 110 controls the overall performance of the private exchange in accordance with the set program. The memory 112 stores the extension number of the extension terminal according to the execution of the program for performing the exchange function with the operation program of the CPU 110. In addition, the controller 110 stores data generated when an operation is performed under the control of the CPU 110. The switching circuit 114 receives the corresponding trunk line CO of the trunk line circuit 116 or the terminal ST1-STn of the subscriber circuit 118 under the control of the CPU 110 to which the incoming call is input. Connect with The trunk line circuit 116 connects a plurality of general trunk lines (C.O) drawn from a local exchange (not shown) under the control of the CPU 11 to the switching circuit 114. The subscriber circuit 118 is controlled by the CPU 110 and connects the extension terminals ST1-STn with the call requests among the plurality of extension terminals ST1-STn to the switching circuit 114. The dedicated line circuit 120 has a plurality of dedicated lines connecting the private exchangers separated from each other, and connects a plurality of dedicated lines introduced from the counterpart key phone system to the switching circuit 114. The DTMF transmitter 122 converts the digits input from the CPU 110 into DTMF and transmits them to the switching circuit 114. The DTMF receiver 124 receives the DTMF signal from the switching circuit 114, converts the DTMF signal into a digit, and provides the same to the CPU 110. The tone supplier 126 generates various tone signals under the control of the CPU 110 and outputs the various tone signals to the switching circuit 114. The interface circuit 128 interfaces data transmitted and received between the CPU 110 and the corresponding configuration.

The process of receiving and storing a call number according to the present invention will be described with reference to FIG. 2. When a call request is received through a trunk line and a call loop is formed, a step of turning off the time switch momentarily, The process consists of storing the incoming call data on the received gapless packet and performing the call mode by turning on the time switch.

Referring to FIG. 3, a process of analyzing and reconfiguring a call number according to the present invention is described. The header of the received and stored call data is searched for a stored memory address, and a process of calculating a memory address to be stored by reconfiguring call data. And sequentially reconstructing the originating number data recorded in the header sequentially and storing the data in the reverse order in the calculated memory address, and converting and storing the repeated originating number by analyzing the reconfigured originating number.

The structure of the memory map of the private exchange according to the present invention is as shown in FIG.

The map structure according to FIG. 4 includes three extra segments corresponding to a virtual memory area for temporarily recording the addresses of different memory maps, and a memory for recording the address of the memory where the originating number is recorded. It consists of five data segments corresponding to an area and eight code segments corresponding to a storage area for recording codes consisting of a plurality of instructions.

A memory map structure according to an embodiment of storing a received call number according to the present invention is shown in FIG.

FIG. 5a is a memory map structure in which an extension subscriber receives and stores a gapless packet transmitted from a counterpart exchange when a call request is received in response to a call request from a CO line subscriber having 461-6000 call numbers. Is assigned. FIG. 5B is a memory map structure which is analyzed by analyzing the calling number stored in FIG. 5A according to the flowchart of FIG.

Therefore, an embodiment of the present invention will be described in detail with reference to the drawings.

First, referring to FIG. 2, the calling party storing process will be described. In operation 210, the CPU 110 detects whether a call request for calling an extension through the CO line is received by the CO line 116. When the call request is detected, the CPU 110 proceeds to step 212 to control the tone supply circuit 126 to provide a ring tone for calling the corresponding extension terminal ST1-STn through the subscriber circuit 118. In operation 214, the CPU 110 detects whether the corresponding station terminal ST1-STn is hooked off in response to the ring tone through the subscriber circuit 118. If the hook-off is not detected, the ringtone is continuously supplied in step 232 until the end of the call request is detected. However, if it is detected that the user is hooked off in response to the ring tone, the CPU 110 proceeds to step 216 to turn on the time switch to form a call loop. The CPU 110 detects whether a call request is received from the extension terminal ST1-STn in step 218 after the call loop is formed. If there is no call request, the flow proceeds to step 226 to perform a general call mode. However, if the call request is received in step 218, the flow proceeds to step 220 to turn off the time switch to temporarily block the call loop. In operation 222, the gapless packet including the data corresponding to the originating number provided from the counterpart exchange is received through the trunk line circuit 116, and the data corresponding to the originating number included in the received gapless packet is stored in the memory 112. Store in For example, when the originating number in the gapless packet is 461-6000, it is stored in a map structure as shown in FIG. 5A. When the storing of the data corresponding to the calling number is completed, the CPU 110 forms a call loop by turning on a time switch in step 224 and proceeds to step 226 to perform a call mode. If the end of the call is detected in step 228, the CPU 110 proceeds to step 230 to turn off the time switch and block the call loop.

Next, referring to FIG. 3, a process of analyzing and reconstructing a call number stored in the map structure illustrated in FIG. 5A by FIG. 2A is described with reference to FIG. 3. Store the first address shown in Figure 5a. The CPU 110 proceeds to step 312 in which the data (ES [BX]) stored in the memory 112 corresponds to the address stored in the BX, and is the OD corresponding to the header data indicating the start of the calling data. Compare If the header data is not the header data in step 312, the controller proceeds to step 314 to increase the address value stored in the BX by one, and then selects the next address and repeats step 312. When the header data is detected in step 312, the CPU 110 proceeds to step 316. The memory 112 stores the reconstructed calling number data by adding a specific integer value to the address where the header data is detected. ) Is stored in the temporary buffer SI. The determination of the specific integer value determines that the address of the area which does not affect the already stored calling number data can be selected. For example, it is set to an integer value of 39. When the reconfiguration address is determined in step 316, the CPU 110 sets the data DX to be stored in the counter buffer for selecting the calling party data stored in the map of FIG. 5a to zero (318). In step 320, the CPU 110 increments one of the DX values registered in the counter buffer and proceeds to step 322. In step 322, the CPU 110 determines the address of BX, which is the header address selected in step 312, plus the DX determined in step 320, as the BX value. In operation 324, the CPU 110 reads data stored in the data area corresponding to the address stored in the BX, and moves the data to the address stored in the SI determined in operation 316. In addition, in step 326, the CPU 110 decreases one address stored in the SI to store a value corresponding to the previous address, and proceeds to step 328 to determine whether all nine digits constituting the calling number are reconfigured. The counter value stored in the DX is greater than or equal to eight. In step 328, the calling number reconfiguration process performs steps 320, 322, 324, 326 and 328 until the value stored in the DX is less than or equal to 8. The structure of the memory map reconstructed through the reconstruction process is shown in FIG. 5B. As can be seen by comparing FIG. 5A and FIG. 5B, the calling number received and stored through the first trunk line is stored in the reverse order, but the original number is stored in the original order through the reconstruction process.

When the reconfiguration of all 9-digit calling numbers is completed, the CPU 110 proceeds to step 330 to set the value of the temporary buffer DX to zero. In step 322, the CPU 110 indicates that the calling party data stored in the data area corresponding to the address stored in the SI determined in step 326 is the same data as the calling party data registered in the previous address SI-1. Determine whether is stored. If it is determined in step 332 that the OE is stored, the CPU 110 decreases the address stored in the SI by one to select the previous address in step 334. Then, the calling party data stored in the data area corresponding to the address stored in the SI, which is the address selected in step 334, is read and stored in the temporary buffer AL. In addition, the CPU 110 proceeds to step 338 and increases the address stored in the SI, and then changes the OE stored in the data area corresponding to the increased address in step 340 to the calling address data stored in the temporary buffer AL. If it is determined in step 332 that it is not an OE, or in step 340, when the change of the calling party data is completed, the CPU 110 proceeds to step 342 in which the calling party data stored in the SI is reconstructed and stored in the address of the memory 112. Increment to select the next address. In addition, in step 344, the CPU 110 increases the counter value stored in the DX by one to determine whether all nine digits constituting the calling number data have been searched. In step 346, the counter value stored in the DX is greater than 8. Compare greater or equal. In step 346, steps 332, 334, 336, 338, 340, 342, 344, and 346 are performed until the value stored in the DX is less than or equal to 8, which is a call data change process. do. The CPU 11 terminates the function when it is determined that the change of all the calling party data stored in the step 346 is completed.

For example, as shown in FIG. 5A, when the caller number data 461-6000 is stored, the first address 6C00 is stored in the BX in step 310. In step 312 and step 314, the address where the OD as the header data is stored is retrieved. The searching is performed by comparing the stored calling number data with the OD while increasing the address one by one from 6C00 stored in the BX. In step 316, when the address OD is stored, the address 6C10 is searched, and in step 316, a specific integer 39 (when a specific integer is set to 39) is added to the searched address 6C10 to determine a storage address to be reconstructed and stored. The address where the reconstructed calling party data is stored is 6C4A. Then, after setting the count value for counting the calling party data reconstructed in steps 318 and 320 to 0, the count value is increased by one each time one calling party data shown in FIG. 5A is reconfigured and stored. In step 322, 6C11 is selected as the address 6C10 plus 1, and in step 324, 01 representing the calling party grade stored in the data area corresponding to the selected 6C11 is stored in the data area of 6C4A. In step 326, 6C49 is selected by subtracting 1 from 6C4A to designate the address to reconstruct and store the next call data. Store in When the calling data stored in the map structure of FIG. 5a is reconfigured into the map structure of FIG. 5b and the DX value indicating that the storage is completed is 8 in step 328, the reconfiguration process is terminated.

In step 330, the DX for counting the retrieved call data is set to 0 to retrieve the call data stored in FIG. 5B to change the repeated call data. In step 332, the caller data 04 stored in the data area of 6C43, which is the address stored in the SI, is compared with the OE representing repetitive data. Since it is not the same in step 332, the process proceeds to step 342 to select 6C44, which is increased by 1 to 6C43. Since it is not equal to or greater than 8, the process proceeds to step 332 to compare whether the 06 and the OE stored in the 6C44 data area are the same.

As described above, the address is increased one by one and the stored data is checked. In step 342, 6C48 is selected to determine that the data is the same in the comparison process in step 332. In step 332, if the address where the OE data is registered is detected, in step 334, 6C47, which is the previous address of 6C48, is selected, and in step 336, 0, which is the source number data stored in the data area of 6C47, is stored in the temporary buffer AL. In step 338, 6C48 is selected as the address where the OE is detected, and in step 340, the OE stored in the data area of 6C48 is changed to 0 stored in the AL and stored. If it is determined in step 344 and step 346 that the check of the calling party data stored in the map shown in FIG. 5B is completed up to 6C4A, the function ends.

As described above, the present invention enables memory allocation and service for each relay line in receiving and processing a gapless packet carrying data. In addition, it can be easily processed to receive, analyze and process multiple gapless packets, and can be easily recognized by other exchanges.

Claims (4)

Claims [1] A method of storing and reconstructing and storing a calling number stored in a private exchange receiving a calling number data corresponding to a calling party's telephone number from a sending exchange requesting a call through a gapless packet and storing it in a memory. A first step of retrieving a memory address in which header data of the former data is stored, reconstructing the original address data, and calculating a memory address to be stored; and a memory address calculated in the first step of the originating data continuously recorded in the header data Reconstructed and stored in the second process, and if repetitive data indicating repetition of the same data as the originating data stored in the preceding memory address is detected by analyzing the stored and stored originating data, Through the analysis of the calling number, characterized in that the third process of converting and storing How to configure. The method of claim 1, wherein the first step comprises: sequentially comparing the memory address from the first address of the memory by using a count value and comparing whether data stored in the selected memory address corresponds to header data of the originating data; And, when the memory address in which the header data is stored is found in the comparing step, determining a memory address which is increased by an integer set to the retrieved memory address and reconstructing the calling address data as a memory address to be stored. Method of reconstruction through analysis of three times. The method of claim 2, wherein the second process comprises: a counting step of detecting whether 9 pieces of calling number data are reconstructed and stored by using a count value, and differentially selecting from a next memory address of a memory address at which header data is stored; And a storing step of reading the calling address data stored in the selected memory address and storing the calling address data in the reverse order from the memory address determined in the determining step. The comparison process of claim 3, wherein the third process compares whether or not the calling party data reconstructed and stored in the storing step is the same as OE, which is repetitive data indicating repetition of the same data as the calling party data stored in the previous memory address. And a conversion step of converting and storing the OE stored in the memory address detected in the comparison step into the calling number data read from the previous memory address.