JPH10304410A - Charging data processing method for exchange system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce a duplicate processing time at start by configuring the method with a process, that restarts the exchange system, a process that confirms whether or not the system is set to the initializing mode depending on presence of a database, and a process that loads data for charging to a main storage section, when the database is in existence and forms data in a standby file to an execution file to simplify a charging task. SOLUTION: A CPU 10 controls speech changeover and various functions depending on a set program. A call-processing task 116 conducts a call- processing relation job of the system, a charging task 117 conducts call unit charging and immediate charging after the end of call processing, and a configuration/DB task 118 manages all the jobs related to loading and data bases as a program file. An NVM 30 is used for storing a database file, a flash memory 114 stores compressed program files and data bases and stores the contents of the NVM 30 once a day as an auxiliary storage device.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for processing billing data in an exchange.

[0002]

2. Description of the Related Art FIG. 1 is a block diagram of a conventional electronic exchange system. The electronic exchange system includes a CPU 10 for controlling call switching and various functions, and a RO for storing programs for calls and various functions and initial service data.
M20, a program and data processing area, and an NVM (Nonv
and an extension circuit 40 for controlling the interface between the extension telephone and the exchange.
A network 50 for switching various tones and voice data; a tone generator 60 for providing various tone signals to the network 50; a ring generator 70 for supplying a ring signal to the network 50;
quency Code) and the corresponding digital data
0, a DTMF transmitter 80 for outputting an MFC signal, and a line circuit for forming a line loop by scissoring the line and controlling an interface for a signal input from the line. 100 and the printer 23
0, an MT (Magenetic Tape) 120, an input / output unit 220 for connecting the terminal device 200 and the HDD 108.

When billing data is generated in a conventional exchange,
The billing data is first stored in the HDD 108. Thereafter, the billing data is stored in another auxiliary storage device such as the MT 120 and used for the bill calculation. If the billing calculation is completed for only one call, the billing data is stored in the NVM 30 in the form of a multiple billing, and after a certain period of time or when the terminal 200
When the storage command is executed, the accounting data is backed up in the HDD 108. And, NV
When the billing data stored in the M30 is lost, the backed up billing data of the HDD 108 is transferred to the NVM3.
Copy to 0.

Further, in the process of keeping the contents of the billing data in the execution memory and the contents of the billing data in the standby memory the same, a frequency billing is calculated every time the call processing is completed and recorded in both. If an abnormality occurs in one, the content of the other billing data is copied and the data is retained.

The above-mentioned backup in the HDD 108 is used when the contents of both memories are abnormal. However, backing up the billing data stored in the NVM 30 to the HDD 108,
Copying the contents of 108 to NVM 30 places a lot of burden on the billing task. Therefore, when designing a charging task, many parts must be allocated for the duplication processing, and it takes a long processing time to actually perform such work in the charging task. Also, when transferring billing data from the execution memory to the standby memory in response to a billing data request from the standby memory, the billing task must perform processing.

[0006]

As described above, the charging task requires more time for duplication processing than the original processing.
There has been a problem that task processing performance is degraded and task design is complicated.

[0007]

According to the present invention, there is provided a method for duplicating accounting information in an exchange system, comprising the first step of restarting the system and the step of checking whether the system is in an initialization mode based on the presence or absence of a database. It is characterized by comprising two steps, and a third step of loading data into the main storage unit for charging if there is a database and converting the data of the standby file into an executable file. The data for billing is compressed and stored in the flash memory.

[0008]

Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.

FIG. 2 is a block diagram of a memory device and an input / output unit of the switching system according to the present invention.

The CPU 10 controls call switching and various functions according to a set program. DRAM 221
Are used as main storage, call processing task 116, billing task 117, configuration / database task 118, I
/ O task 119 is included. The call processing task 116 is a task related to the call processing of the system.
After the call processing is completed, operations such as frequency accounting and immediate accounting are performed, and the configuration / database task 118 is a program file, and performs all management related to loading and database. The NVM 30 is used for storing database files, and the flash memory 114 stores program files and database files in a compressed state, and is used as an auxiliary storage device such as the hard disk 108. The input / output unit 220 is directly connected to input / output devices of the system (the terminal device 200 and the printer 230), and is controlled by the I / O task 119.
The terminal 200 performs operations related to system maintenance through the RS-232C, and the printer 230 outputs data necessary for immediate billing, system diagnosis, and alarm.

FIG. 3 is a block diagram of tasks related to duplication of billing data.

[0012] The call processing task 116 sends information necessary for accounting calculation to the accounting task 117. The charging task 117 sends the immediate charging information to the I / O task 119, and
The item designated by 0 is output from the printer 230. The frequency charging information is charging data managed in the exchange. In the present invention, the charging task 117 sets and processes the corresponding field of the database. All duplication operations are managed by the configuration / database task 118. The value of the database file to be corrected is stored in the DRAM 221. This is periodically backed up to the NVM 30. Then, the flash memory 114
Also functions as an auxiliary storage device in which the contents of the NVM 30 are stored once a day.

FIG. 4 is a flowchart for duplicating billing data using a database.

In step 411, the CPU 10 confirms the restart of the system. In step 412, it is determined whether the execution system is in the initialization mode based on the presence or absence of the database. If there is no database, the system initialization mode is performed in step 413. If there is a database, the database is stored in the flash memory 114 in step 414. DR information
Load to AM221. After loading, step 41
At 5, the data in the execution memory is copied to the standby memory. As a result, duplication work is performed because the billing data exists in the form of a database file. Data copying from the execution memory to the standby memory is also performed by the configuration / database task 118.

[0015]

As described above, the design of the charging task can be simplified, and the reliability of the management and storage of the charging data can be ensured in order to utilize the existing database. Further, since the charging data is duplicated in the database, the time required for the duplication when the system is restarted can be reduced.

[Brief description of the drawings]

FIG. 1 is a block diagram of a general switching system.

FIG. 2 is a block diagram of a module of a CPU of the exchange system of the present invention.

FIG. 3 is a block diagram of a charge data duplication processing module;

FIG. 4 is a flowchart of charging data duplication processing using a database.

[Explanation of symbols]

 Reference Signs List 10 CPU 20 ROM 30 NVM 40 Extension circuit 50 Network 60 Tone generator 70 Ring generator 80 DTMF receiver 90 DTMF transmitter 100 Local line circuit 108 HDD 114 Flash memory 116 Call processing task 117 Charging task 118 Configuration / database task 119 I / O task 120 MT 200 Terminal 220 Input / output unit 221 DRAM 230 Printer

Claims (3)

[Claims] A first step of restarting the system; a second step of checking whether the system is in an initialization mode based on the presence or absence of a database; And a third step of converting the data into an executable file. 2. The method for duplicating accounting information in an exchange system according to claim 1, wherein the data for accounting is compressed and stored. 3. The method according to claim 1, wherein data for charging is stored in a flash memory.