KR19990000130A - How to handle the mountain climbing charge at the exchange - Google Patents

Abstract

end. TECHNICAL FIELD OF THE INVENTION

How to make frequency billing at the exchange.

I. Technical Problems to be Solved by the Invention

Providing a way to preserve billing data that can be lost in frequency billing.

All. The point of the solution of the invention

The frequency billing method of the exchanger includes the steps of receiving billing data and checking frequency of billing data when the call is terminated, storing the billing data in a detailed billing file if the billing frequency is not the result of the check, A step of accumulating the frequency of the frequency in the corresponding number of the table when the table allocated to the memory exists, checking whether there is a table that is not registered in the memory when the table allocated to the memory does not exist And storing the table in the detailed charging table of the memory when the table is not registered as an inspection result, and allocating the table when the table that is not registered as an inspection result does not exist, A method of handling the mountain climbing charge in an exchange.

la. Important Uses of the Invention

How to handle the mountain climbing charge at the exchange.

Description

How to handle the mountain climbing charge at the exchange

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a billing method for an exchange, and more particularly,

Generally, there are two methods of billing in exchanges: frequency climbing method and detailed billing method. First, the detailed charging method is a method of transmitting a total of 48 bits of data including 16-bit outgoing call time and 16-bit start time and 8-bit end time and 8-bit end time after the call is terminated and stored in the detailed billing database. In addition, the frequency-based mountain climbing method is a method in which the exchange determines the amount of each bill directly, and the frequency for each node is calculated and accumulated in the frequency database for each subscriber.

In the frequency climbing method, there is a table in the exchange having a number corresponding to the telephone number of each subscriber. Hereinafter, the number registered in the table will be referred to as a mounting number. Since the number of calls is accumulated in each of the subscriber numbers in the exchange, it is inconvenient to classify and charge the subscriber in accordance with the telephone number at the time of settlement of the call charge of the subscriber. Also, when the billing data is backed up once, the billing data on the disk of the exchange is also deleted. Therefore, if the backup disk is damaged due to the carelessness of the administrator, there is inconvenience that the details to be charged are lost.

It is therefore an object of the present invention to provide a method of corresponding the telephone number of each subscriber and the actual number of the exchange.

Another object of the present invention is to prevent loss of backed up billing data.

It is still another object of the present invention to provide a method of performing detailed billing when the frequency of mountain climbing is impossible.

According to another aspect of the present invention, there is provided a frequency billing method for an exchange, comprising the steps of: receiving billing data when a call is terminated and checking whether the billing data is authorized; and storing the billing data in a detailed billing table Checking whether there is a table assigned to the memory in case of the frequency of the test and accumulating the frequency in the corresponding number of the table when the table allocated to the memory exists; Checking whether there is a table that is not registered in the memory when the table does not exist, storing the table in the detailed charge table of the memory when the table is not registered as an inspection result, If the table does not exist, it allocates the table. The exchanger according to claim characterized constituted by any frequency climbing accounting method.

1 is a block diagram of an electronic exchange system to which the present invention is applied;

Figure 2 is a flow chart of a subscriber performing a call and transferring billing data;

3 is a detailed flowchart of a process of storing received charging data in a frequency table according to an embodiment of the present invention.

4 is a flowchart illustrating a process of backing up frequency billing data according to an embodiment of the present invention.

5 is a schematic diagram of a frequency table and table information according to an embodiment of the present invention;

BRIEF DESCRIPTION OF THE DRAWINGS FIG.

1 is a block diagram of an electronic exchange system to which the present invention is applied.

The electronic switching system (Switch) comprises a Switch Netwark Sub System 100, a subscriber switch subsystem 110, a trunk line subsystem 120, and an operation and storage switch subsystem 140.

First, the switch network subsystem 100 includes a Network Synchronization (NES) 1, a plurality of Central Data Link (CDL) 2, a Space Switch 3, (Interprocessor Communication Unit) 4 and a number of control processors.

A control processor of the switch network subsystem 100 includes an Inter Network Processor (INP) 5 for controlling the entire system by a call, a number translation processor A Network Synchronization Processor (NSP) 9 for controlling the Network Synchronization Device 1 and an Interconnection Network Maintenance Processor (INMP) 8 for the maintenance of the switch network. A Space Switch Processor (SSP) 7 for controlling the space division switch 3, and a Central Link Interface Processor (CLIP) 10 for controlling the processor communication controller in the central part of the system.

Reference numerals 110 and 120 denote access switch subsystems. The access switch subsystem is divided into subscriber subsystem 110 and trunk line subsystem 120 according to its use.

Each of the access switch subsystems 110 and 120 includes an access switch processor (ASP) 20 for controlling the corresponding access switch system, an access switch maintenance processor (Access Switch A Time Switch Processor (TSP) 23 for controlling the time-divisional switch and the local data link 22, and a time-division-switch control processor Respectively.

The subscriber switch subsystem 110 includes an analog subscriber interface (ASI) 24 for connecting a plurality of subscribers, an analog subscriber interface process (ASIP) 25 for controlling the subscriber module, A local service unit (LSI) 26 for processing a DTMF (Dual Tone Multi Frequency) signal and various audible signals, and a local service processor (LSP) 27.

The trunk line subsystem 12 includes a T1 T1 line interface unit (DTI) 28, a T1 T1 control processor (DTIP) 29 for controlling the T1 trunk line unit 28, an E1 trunk line unit An E1 trunk line control processor 31 for controlling the E1 trunk line unit 30, a local service unit (LSI) 32 for processing an R2 signal, And a local service processor (LSP) 33 for controlling the LSP 32.

Reference numeral 130 denotes an operation and maintenance switch subsystem. The operation and maintenance switch subsystem includes a processor 40 (hereinafter referred to as OMP) for managing and maintaining operations, and a MMC processor (Man Machine Processor: MMP) 41 for processing MMC (Man Machine Communication) A Comman Control Maintenance Processor (CCMP) 42 for maintaining the operation and maintenance subsystem, and various peripheral devices.

The peripheral devices include a disk (DK) 43, a magnetic tape (MT) 44, a CRT 45, a printer (PRT) 46, a PC 47, and an alarm panel .

2 is a flow chart of subscriber's call execution and billing data transmission.

If the subscriber hooks off, the subscriber module 24 of the subscriber switch subsystem 110 changes the state of the corresponding subscriber port. Then, in step 211, the subscriber control processor 25 detects a change in the state of the subscriber module and delivers the hook-off information to the subscriber processing block of the access switch processor 20 through the IPCU 4.

In the subscriber call processing block receiving the hook-off information, the state of the subscriber (whether or not the calling process is possible, the calling party number, and the system status) is checked in step 213. If the calling process is possible, Time switch control processor 23 to request the connection of the time switch 22 and requests the local service processor 27 to occupy the signaling device.

Thereafter, when the called subscriber number is dialed in step 215, the local service processor 27 detects subscriber dialing information through the local service unit 26 and notifies the access switch processor 20 of the subscriber dialing information. The notified dialing information requests number translation and routing data translation in the number translation processor 6. The translated data notifies subscriber call processing block 110 and trunk line subsystem 120 of the result.

In step 217, the subscriber processor 20, which has received the trunk line occupancy notification, requests occupancy of the trunk line subsystem 120 through the trunk line subsystem 120 according to the translated data. Searches for idle dues of the calling party and the called party, and requests the space division switch processor 7 to establish a path connection when the idle path is searched. In step 219, the trunk line subsystem 120 checks whether a call path is connected by the switching operation of the space switch 3. If the subscriber of the called party hooks off the call path as a result of the check, As shown in FIG.

In step 223, a hook-on operation of the called party or calling party in the call mode is checked to see if the call is terminated. When the call is completed, the access switch processor 20 transmits the call time information received through the subscriber processor 25 to the OMP 40 in step 225. The OMP 40 calculates the received charging data by using a frequency table. Also, the OMP 40 records the charging data received in step 227 in the disk 43.

3 is a detailed flowchart illustrating a process of storing received charging data in a frequency table according to an exemplary embodiment of the present invention.

2, the OMP 40 receives the call history received from the subscriber processing processor 20 in step 311. In step 311, The OMP 40 checks if the data received in step 313 is terminated. The OMP 40 proceeds to step 315 when the reception of the inspection result is completed, or continues to receive the data of step 311. [ The OMP 40 checks whether the received data is frequency billed data by flag data of the received data.

The OMP 40 proceeds to step 317 when the received data is frequency charging, and proceeds to the detailed charging data storing method when the detailed charging is performed. Here, a detailed description of the detailed charging method is omitted. If the received data is checked by frequency billing, the OMP 40 checks the table of the disk 43 in step 317 and checks the existence of a table matching the peak number of the subscriber numbers of the calling subscriber. The OMP 40 proceeds to step 319 if there is a table having the same number of digits as the number of digits to be checked, and to step 323 if the table does not exist.

As shown in FIG. 5, a peak number is allocated to each table, and a frequency of each subscriber is accumulated corresponding to the remaining digits of the subscriber number. This is as shown in Fig.

If there is a table with the same peak digits in step 317 and the process proceeds to step 419, the OMP 40 searches the table for the remaining digits of the calling subscriber number and selects a matching line. The OMP 40 accumulates the current frequency with the frequency of use of the subscriber in the selected line.

On the other hand, if there is no table corresponding to the peak number of the calling subscriber number in step 317, the OMP 40 checks whether there is a teardown to which the peak number is not allocated in the disk 43. [ If there is a table that is not allocated as a result of the inspection, the OMP 40 proceeds to step 325. Otherwise, the OMP 40 performs detailed accounting. The OMP 40 checks whether additional data is present in the received data. If it is determined that there is a frequency (volume frequency) to be separately charged, the process proceeds to step 329; otherwise, the process proceeds to step 317. In step 327, the OMP 40 checks whether there is a table that is not allocated to the disk 43 when the received data has a volume figure and proceeds to step 329. If the unassigned table exists, the OMP 40 proceeds to step 331. If the unassigned table does not exist, the OMP 40 proceeds to step 331. In step 329, And proceeds to step 317 to process the frequency billing.

As shown in FIG. 5, since the table of the "normal number" and the "volume number" can be set separately and the billing can be separately performed, the billing can be easily settled. The peak number and the lower number in FIG. 5 are the numbers set in the exchange. Therefore, as shown in the example of Table 1 below, it has a table for associating the subscriber number and the dial number mounted in the exchange.

[Table 1]

Subscriber number mounted on switchboard Individual dial number 111-0000 123-4567 111-0001 234-4321 111-0002 321-7890 ... ...

Therefore, in the present invention, the table is managed only by the dial number of the individual, ignoring the mounting number.

4 is a flowchart illustrating a process of backing up frequency billing data according to an embodiment of the present invention.

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

The OMP 40 waits for one minute to back up the data recorded on the disk 43 in step 441. [ In step 413, the OMP 40 checks whether the set time for backing up has elapsed. The OMP 40 proceeds to step 415 when the set time of the test result has elapsed, and proceeds to step 411 if it has not yet elapsed and waits for 1 minute. In step 415, the OMP 40 checks whether the state of the disk 43 is normal. If it is determined that the OMP 40 is normal, the process proceeds to step 417. Otherwise, the process proceeds to step 411. If it is not detected as normal, the disk is defective or is not normally inspected when it is being backed up. In step 317, the OMP 40 checks whether the frequency table of the disk 43 is reliable. If it is determined that the OMP 40 is reliable, the process proceeds to step 419, and if it is determined that the OMP 40 is not reliable, the process proceeds to step 433.

If it is determined in step 419 that the disk 43 is reliable, the OMP 40 checks whether there is a need to back up the frequency stored in the disk. If it is determined that there is a need for backup, the OMP 40 proceeds to step 421. If it is determined that there is no need for backup, the OMP 40 proceeds to step 411. The OMP 40 opens the disk 43 in step 421 and proceeds to step 423 to check whether the disk table is normally opened. If the disk 43 is opened normally, the OMP 40 proceeds to step 429 to perform backup to the magnetic tape unit 44 and initialize the backup time. If the disk 43 is not opened normally, the OMP 40 proceeds to step 425, Is present. If the inspection result table exists, the OMP 40 proceeds to step 411, and if not, proceeds to step 427 to form a table. The OMP 40 performs backup to the magnetic tape unit 44 according to the table formed in step 429 and initializes the backup time.

Here, backup refers to moving the table data stored in the disk and the frequency billing table charged in accordance with the table equally. In addition, the conventional exchange clears all the data stored in the disk 43 of the exchanger and initializes it when the backup is executed. However, in the present invention, charging data is accumulated and used continuously without being deleted.

The method described above can be calculated as a method of calculating the difference by comparing the two frequencies by backing up the billing history and storing the previous billing data in total oxygen. 5, for example, if the number of previous billing cycles corresponding to the lower number 0000 is 3601 and the number of backed billing cycles is 3872, the difference between the previous billing cycles is calculated from the backup billing frequency do. Then the billing frequency is 3872 - 3601. Therefore, the billing frequency becomes 271 degrees. Since the billing history is calculated in this way, data once backed up is not deleted from the disk 43 in the exchange.

On the other hand, if it is determined in step 417 that the frequency table is unreliable, the OMP 40 opens the disk 43 in step 433. In step 435, the OMP 40 checks whether the disk 43 is normally opened. If the disk 43 is normally opened, the OMP 40 proceeds to step 443. If the disk 43 is not normally opened, In step 443, the OMP 40 reads the data of the table of the disk 43, sets the reliability of the frequency table, and ends the process.

If it is determined in step 435 that the disk does not normally open, the OMP 40 checks whether a disk table exists in the disk 43. If there is no table in the disk 43, the OMP 40 initializes the table information in the disk 43 in step 439, sets the reliability of the frequency table in step 441, and sets the reliability of the frequency table in step 411 .

As described above, when the frequency billing is impossible even in the frequency billing process, the billing data can be prevented from being lost by adding a method of processing by the detailed billing. In addition, since the subscriber number and the exchange-by-exchange management number are managed in correspondence with each other, there is an advantage that data can be processed quickly and conveniently, and when the data is backed up, .

Claims (4)

In the frequency billing method of an exchange, When the call is terminated, receiving billing data and checking whether it is frequency billing data; Storing the result in the detailed billing table when the result of the checking is not frequency bills; Checking whether there is a table allocated to the memory in case of frequency of the test, accumulating the frequency of the frequency in the corresponding number of the table when the table allocated to the memory exists, Checking whether there is a table not registered in the memory when a table allocated to the memory does not exist; Storing in a detailed billing table of the memory if there is no unregistered table as a result of the checking; And allocating a table when there is no unregistered table as a result of the checking. The method according to claim 1, Checking whether an allocated table for the number of volumes is present in the memory when the received charging data is a volume number; Allocating a table when the allocated table does not exist as a result of the checking; And adding a detailed charge if the allocated table does not exist. In the method for backing up the frequency of climbing charge of an exchange, Wherein when the setup time of the backup elapses, the table is searched for on the disk where the billing details of the exchange are stored, the billing details are backed up to another disk, and the billing data recorded on the disk of the exchange is not deleted. Mountain climbing treatment method. In the frequency climbing method of exchanger, And a memory table for associating a first subscriber number of the subscriber table registered for charging in the switchboard with a second subscriber number for dialing of each subscriber, wherein the billing frequency is set according to the first subscriber number at the time of billing settlement Process, Wherein the settled billing count is calculated and output in correspondence with the second subscriber number.