KR19990085416A - How to handle an abnormal charging process at the exchange - Google Patents

Abstract

In the case of an abnormality of the charging process in the exchange, the processing method periodically monitors whether the charging process is abnormally performed and requires a dummy performance in case of abnormality, and transfers the charging data to the charging generation process in the matching exchange processor when the abnormality is abnormal even after the dummy performance is performed. Prohibition is required to prevent the loss of billing data, and if no operator action is received for a certain period of time, restarts the billing process to recover the abnormality.

Description

How to handle an abnormal charging process at the exchange

The present invention relates to a process anomaly processing method of an exchange, and more particularly to a method for handling an abnormal state of a charging process.

In general, the exchange transfers billing data generated by the access network processor (ANP) to the operating and maintenance processor (OMP) at the end of a call. The operation and maintenance processor may include a billing data collection process, a billing data storage process, a billing data dump process, a billing data transmission process, and the maintenance process from the billing generation process of the match exchange processor. Process the billing data entered into. Looking at the process, first, the collecting process collects the charging data received from the matching exchange processor to form and store blocks (1Kbytes) in the memory, and the storage processor stores the collected charging data as a file on a disk. To record. In this case, when the disk is abnormal or there is an operator request, the collected charging data may be directly dumped to a digital-audio tape recorder (DAT) or an RDK by a dump process. The transmission process transmits the charging data to the centralized automatic message account (CAMA). The major processes responsible for billing in the Operation and Maintenance Processor (OMP) are billing data collection, billing data storage, billing data dump, and billing data transfer.

However, the conventional exchange transfers the charging data generated by the matching exchange processor (ANP) to the charging process in the operation and maintenance processor (OMP) unconditionally, regardless of whether or not the processes responsible for the above charge recording. That is, although the billing processes are abnormal and normal billing data processing cannot be performed, billing data may be lost because the matching exchange processor (ANP) continuously sends billing data to the operation and maintenance processor (OMP). There was a problem that could be.

Accordingly, an object of the present invention is to provide a method for preventing the loss of billing data by notifying the matching exchange processor when the state of the billing process is abnormal and prohibiting the transmission of billing data.

Still another object of the present invention is to provide a method of alerting an operator by generating an alarm when the state of the charging process is abnormal, and recovering the abnormal charging process by restarting the entire charging process when there is no action from the operator.

The abnormal processing method of the charging process in the exchange to achieve the above objectives, by monitoring whether the charging process is abnormally performed at regular intervals, and requires the abnormal performance of a certain number of times, the generation process when the abnormality even after the dummy performance Requiring prohibition of charging data and recovering the abnormality by restarting the charging process when no operator action is received for a certain time.

1 shows the charging processes provided in a maintenance processor (OMP) of an exchange according to the invention.

2 is a control flowchart for processing an abnormal charging processor in an exchange according to an embodiment of the present invention.

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

First, in adding reference numerals to the components of each drawing, the same components have the same reference numerals as much as possible even if they are displayed on different drawings. In describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

1 is a diagram illustrating the charging processes provided in a maintenance processor (OMP) in the present invention.

Referring to FIG. 1, the monitoring process 111 detects an abnormality of the charging processes provided in the maintenance processor 117 and performs a process thereof. The billing process 119 in the match exchange process (ANP) 116 sends the billing data generated at the end of the call to the maintenance processor 117 by a certain number of calls. The collecting process 112 collects the charging data from the match exchange processor 116, forms a block in the memory, and stores it. The storage process 113 reads out the stored charging block from the memory and stores it as a file in a disk when the charging data storage is completed on the memory. The dump process 115 reads the billing data from the disk when the disk is normal and stores it in the DTA or RDK. The dump process 115 reads the billing data from the memory and stores it in the DAT or RDK when the disk is abnormal. The transfer process 114 transmits the charging data stored on the disk to the central charging center (CAMA) 118 when it is necessary to transfer the stored charging data to the central charging center (CAMA).

Referring to the operation based on the configuration of FIG. 1, the charge generation process 119 in the match exchange process (ANP) 116 transfers the generated billing data to the maintenance processor 117 by a predetermined number of calls. In this case, the collecting process 112 collects the charging data received from the match exchange processor 116, forms a block in the memory, and stores the block data. When the storing of the charging data is completed, the collected charging data is read from the memory and stored in the disk as a file. If the disk is abnormal or the operator requests during the above-described execution process, the dump process 115 reads the collected charging data from the memory and stores it in the DAT or RDK. In addition, when the collected charging data is transmitted to the central charging center (CAMA) 118, the transfer process 114 transmits the collected charging data to the central charging center (CAMA) 118. During the charging data processing of the above-described processes, the monitoring process 111 checks whether the charging processes (collection process 112, storage process 113, transmission process 114, dump processor 115) abnormally at regular intervals, and performs processing thereof. In this case, when an abnormality is detected from any charging process, the monitoring process 111 requests prohibition of charging data to the charge generation process 119 of the matching exchange processor 116, and cancels the transmission prohibition when the abnormality is recovered. Resume transmission. Here, the charging generation process 119 in the matching exchange processor 116 waits for the charging data generated when the charging data transmission prohibition request is received from the monitoring process 111 in its own queue, and stores the charging data in its own queue when the prohibition of cancellation is notified. Charge data is sent back to the maintenance processor 117.

2 is a diagram illustrating a procedure for detecting and processing an abnormal state of charging processes according to an exemplary embodiment of the present invention.

Since the algorithms for recognizing and processing abnormal conditions of the four charging processes (collecting process 112, storage process 113, transmission process 114, and dump processor 115) described above are all the same, the present embodiment will be described as an example of the collecting process. Let's do it. In addition, prior to the description of the embodiment, a data structure for managing the number of executions (RunID) of each process will be described in Table 1 below.

Collection process Storage process Dump process Transfer process 1 minute ago AsmPreId StoPreId DmpPreId Sndpreld Current execution count AsmRunId StoRunId DmpRunId Sndrunld Dummy performance AsmDmyNo StoDmyNo DmpDmyNo SndDmyNo Abnormal alarm occurrence AsmAlmOn StoAlmOn DmpAlmOn SndAlmOn

In Table 1, AsmPreId is the number of times before the collection process (one minute ago), AsmRunId is the number of times the collection process is currently performed, AsmDmyNo is the number of dummy execution requests of the collection process, and AsmDmyOn indicates whether an abnormal alarm occurs in the collection process. . StoPreId is a previous number of executions of a storage process, StoRunId is a current number of executions of a storage process, StoDmyNo is a dummy execution request number of a storage process, and StoDmyOn indicates whether an abnormal alarm has occurred in the storage process. The DmpPreId is a previous execution number of the dump process, the DmpRunId is a current execution number of the dump process, DmpDmyNo is a dummy execution request number of the dump process, and DmpDmyOn indicates whether an abnormal alarm occurs in the dump process. SndPreId is the previous number of executions of the transmission process, SndRunId is the current number of executions of the transmission process, SndDmyNo is the dummy execution request number of the transmission process, and SndDmyOn indicates whether an abnormal alarm has occurred in the transmission process. In this case, the dummy execution means that the charging process in an abnormal state performs a separate processing routine at the request of the monitoring process 111 instead of the normal charging data processing routine. Increase the number of times.

Referring to FIG. 2, in step 211, the monitoring process 111 reads the current execution count (AsmRunID) of the collection process from the data structure as shown in Table 1 above, and checks whether the execution process is the same as the previous execution count (AsmPreId) in step 213. . At this time, if the current execution frequency (AsmRunId) is the same as the previous execution frequency (AsmPreId), the monitoring process 111 proceeds to step 215, and if it is different from the previous execution number (AsmPreId), the monitoring process 111 is step 231. Proceed to Recognizing that it is the same as the previous execution count (AsmPreId), the monitoring process 111 proceeds to step 215 and sets the dummy execution request count AsDmyNo of the collection process 112 by the set number (in this embodiment, defined as 1). In step 217, it is checked whether the increased number of dummy execution requests (AsmDmyId) is greater than a preset maximum number of dummy executions (MAX_DUMMY_RUN). At this time, if the maximum number of piles (MAX_DUMMY_RUN) is greater than the monitoring process 111 proceeds to step 219, if less than the maximum number of piles to perform the monitoring process 111 proceeds to step 237. The monitoring process 111, which detects that the increased number of dummy execution requests is greater than the maximum number of dummy executions and proceeds to step 219, indicates whether a false alarm of a collection process operated when the collection process is abnormal is already performed. Check from the AsmAlmOn value. In this case, when the malfunction alarm of the collection process is in operation, the monitoring process 111 proceeds to step 227, and when the malfunction alarm of the collection process is not in operation, the monitoring process 111 proceeds to step 221. Recognizing that the alarm is inactive, the monitoring process 111 proceeds to step 221 and activates the alarm, requesting prohibition of charging data to the billing process 119 in the match exchange process (ANP) 116 in step 223. Send a signal (IPC signal or message). Here, the charge generation process 119 in the match exchange processor (ANP) 116 stores the charge data in its own queue without transmitting the charge data. In step 225, the monitoring process 111 checks whether an operator action is received. That is, the operator recognizes the alarm sound and examines what action was taken accordingly. In this case, the monitoring process 111 may be interrupted according to the operator's action. At this time, if the operator's action is detected, the monitoring process 111 terminates the program. If the operator's action is not detected, the monitoring process 111 proceeds to step 227 to check whether the set time has elapsed. Herein, the set time is a time at which the monitoring process 111 arbitrarily sets a time from the time at which the operator action is received to take the next full processor restart operation. That is, when the elapse of the set time is detected, the monitoring process 111 proceeds to step 229. When the elapse of the set time is not detected, the monitoring process 111 returns to step 211 to check the state again. Rerun the step. The monitoring process 111 which detects the elapse of the set time and proceeds to step 229 restarts the entire process to restore the collection process 212 and then terminates the program. On the other hand, the current execution count (AsmRunId) read in step 213 is different from the previous execution count (AsmPreId) and the monitoring process 111 proceeds to step 231, the monitoring process 111 checks whether the malfunction alarm of the collection process 212 is in operation. In this case, when the malfunction alarm of the collection process is in operation, the monitoring process 111 proceeds to step 233. When the malfunction alarm of the collection process is not in operation, the monitoring process 111 reads the current number of executions of the current collection process. Return to step 211 above. The monitoring process 111, which detects that the malfunctioning alarm of the collection process is in operation and proceeds to step 233, releases the malfunctioning alarm of the active collection process. In step 235, the monitoring process 111 transmits a signal (IPC signal or message) for canceling the prohibition of charging data to the charging generation process 119 in the match exchange process (ANP) 116, and again the current number of executions of the collection process 112 ( Return to step 211 to read AsmRunId). Here, the charging generation process 119 in the matching exchange processor (ANP) 116 resumes the transmission of the charging data stored in its own queue. Meanwhile, in step 217, the monitoring process 111 detects that the number of dummy execution requests AsDmyNo is less than the maximum number of dummy executions MAX_DUMMY_RUN and proceeds to step 237 generates a dummy execution signal or an event in the collection process 112. In order to check the current number of executions of the collection process 112, the process returns to step 211 and re-executes the following steps.

That is, the present invention compares the current number of times and the previous number of times of the billing process with the monitoring process provided in the maintenance processor to determine whether the abnormal state, and if the abnormal state is detected, the billing with the matching exchange processor (ANP) It is to prevent the loss of billing data by prohibiting data transmission.

As described above, the present invention has an advantage that an operator can grasp the state of the process by generating an alarm when it is abnormal by monitoring whether or not the process state processing the charging data in the exchange is normal. In addition, the billing data transfer prohibition is requested to a match exchange processor (ANP) that generates billing data in case of abnormality, so that the billing process in the match exchange processor stores the billing data in its own queue, and when the abnormality is recovered, the billing data transfer is prohibited. By disabling the prohibition, it is possible to prevent the loss of billing data. In addition, even if there is no operator's action for a certain period of time after the alarm is generated, the entire charging process can be restarted by itself to enable the recovery of the charging process to its normal state, thereby providing an advantage of effectively performing abnormal processing of the charging process.

Claims (3)

In the abnormal processing method of the charging process in the exchanger, It monitors whether the charging process is abnormally performed at regular intervals and requests a dummy performance of a certain number of times of abnormal days, and if the abnormality is abnormal even after the dummy performance, requires the prohibition of charging data transmission to a charging generation process, and an operator action is received for a certain time. If not, restarting the charging process to recover the abnormality. In the abnormal processing method of the charging process in the exchanger, A first step of increasing the number of dummy runs by a predetermined number and checking whether the value is greater than or equal to the maximum number of runs if the current number of executions of the charging process is the same as comparing the previous number of executions; A second process of requesting the dummy processor to perform the dummy process and returning to the first process when the maximum number of piles is performed; A third step of operating a process malfunction alarm when the number of times of the maximum pile performance is exceeded, requesting prohibition of charging data transmission to a billing process, and then checking whether an operator action is received; And a fourth process of recovering the charging processor by restarting the entire charging process when the operator's action is not received and a set time elapsed is detected. The method of claim 2, A fifth process of checking whether a malfunction alarm is in operation when the current execution frequency is different from the previous execution number while the first process is being executed, and releasing the alarm when the operation is in progress, and requesting the prohibition of transmission of charging data to the charging generation process. Abnormal treatment method of the charging process of the exchange, characterized in that it further comprises.