KR20010082898A - The method of maintaining lost metering data of the mobile communication switch - Google Patents

Abstract

PURPOSE: A method for preserving loss charging data in a mobile communication switch is provided to efficiently preserve the loss charging data and minimize charging data omitted when accounting the charging by storing the loss charging data as a raw data type in a disk of an OMID(Operation and Maintenance Interface Device). CONSTITUTION: It is judged whether loss charging data which are not stored in a charging disk of an OMP(Operation and Maintenance Processor) are generated(S2). If the loss charging data are generated, a CDR(Charging Data Recording) of the OMP transmits the loss charging data as a raw data type to a CLS(Charging data Lostcall Saving) of an OMID through an IPC(S3). The CLS of the OMID receives the transmitted loss charging data of the raw data type and stores the received loss charging data in a disk of the OMID(S4).

Description

Preservation of lost billing data in mobile communication exchange {THE METHOD OF MAINTAINING LOST METERING DATA OF THE MOBILE COMMUNICATION SWITCH}

The present invention relates to a method of preserving lost billing data in a mobile communication exchange. In particular, the present invention relates to a method of preserving lost billing data in a mobile communication exchange by storing raw lost data in a raw data format on a disk of an operation and maintenance interface device (OMID). The present invention relates to a method of preserving lost billing data in a mobile communication exchange that enables the billing data to be efficiently stored.

In general, there is an access switching processor (ASP) 10 and an operation and maintenance processor (OMP) 20 for collecting and processing billing data, as shown in FIG. 1, wherein the call processing is performed. A maximum of 32 ASP 10 processors can be implemented. The ASP 10 includes a Mobile Call Control (MCC) 11 that processes a call and a CDGM that collects billing data generated by a call generation. (Charging Data Generation for Mobile call) 12 is implemented.

In addition, the OMP 20 for operation and maintenance functions includes a charging data recording (CDR) for storing the charging data collected from each ASP 10 in the charging disk 30 and the charging MT (Magnetic Tape) 40 ( 21) is mounted.

In the configuration as described above, if the MCC 11 in the ASP 10 that processes this at the end of a call transmits the charging data to the CDGM 12 using IPC (Inter Processor Communication) according to the defined standard, the CDGM 12 ) Performs the necessary processing procedure for the received charging data and then transmits the charging data to the CDR 21 in the OMP 20.

Subsequently, the CDR 21 bundles the received charging data in the form of a block and sequentially stores the charging data in the charging disk 30 and the charging MT 40.

As described above, the billing data transmitted to the OMP 20 is temporarily stored in the CDR 21 memory queue of the OMP 20 and then stored in the billing disk 30. In this case, the billing data is charged according to any condition. If a situation occurs in which the disk 30 cannot be stored, the billing data continues to accumulate in the memory queue.

In this case, conventionally, when charging data accumulates in the memory queue more than 400 blocks, the charging MT 40 attempts to store the charging data, and when the charging data exceeds 600 blocks, the maximum size of the memory queue, a final method for preserving charging data is provided. Used.

That is, when the charge data is accumulated in the memory queue more than 600 blocks, the charge data is transmitted to the MMP (Man Machine Processor) and output to the operator screen, the output charge data is recorded on the disk of the MMP and used for billing settlement It was made.

At this time, IPC is used between the OMP 20 and the MMP. In this MMP, the IPC message is processed in several steps, thereby limiting the message processing speed.

That is, when the OMP 20 transmits billing data at a rate that can be processed by the MMP, billing data accumulates in the MMP's IPC queue, and when the maximum size of the IPC queue exceeds 28,000 90%, 100 or more are accumulated. The IPC of the block must be deleted. In this case, since the billing data transmitted from the OMP 20 exists in the deleted IPC, there is a problem that the billing data is lost and thus is lost in the billing settlement.

The present invention has been made to solve the above problems, and its object is to efficiently store lost billing data by storing lost billing data lost in the billing disk in the mobile communication exchange as raw data in the disk of the OMID. The present invention provides a method of preserving lost billing data in a mobile communication exchange that minimizes billing data that is lost in billing settlement.

1 is a block diagram of a mobile communication exchange for collecting charging data;

2 is an operation flowchart showing a method of storing lost charging data in a mobile communication switch according to the present invention;

3 is an operation flowchart of a CDR for performing the method of preserving lost billing data of the present invention;

4 is an operation flowchart of a CLS for performing a method of preserving lost billing data of the present invention;

5 to 8 are views showing the flow of various messages between the CDR and the CLS for performing the method of preserving lost billing data of the present invention.

<Description of the symbols for the main parts of the drawings>

10: ASP 11: MCC

12: CDGM 20: OMP

21: CDR 30: disk

40: MT

The method of preserving lost billing data in the mobile communication switch of the present invention for achieving the above object comprises: a step of determining whether lost billing data is generated in the CDR to determine whether lost billing data is lost and not stored in the OMP billing disk; If the lost billing data is generated in the step of determining the lost billing data, the lost billing data transmission step of transmitting the lost billing data in the form of raw data to the CLS (Charging data Lostcall Saving) through IPC, and the CLS charges the lost billing data. And a lost charging data storage step of receiving lost charging data in the form of raw data transmitted in the transmitting step and storing the lost charging data in a disk of the OMID.

Hereinafter, a method of preserving lost billing data in a mobile communication switch according to the present invention will be described in detail with reference to the accompanying drawings.

2 is an operation flowchart showing a method of preserving lost billing data in a mobile communication switch according to the present invention, FIG. 3 is an operation flowchart of a CDR for performing a method of preserving lost billing data of the present invention, and FIG. A flowchart of a CLS for performing a method of preserving lost billing data of the present invention.

5 to 8 are diagrams illustrating various message flows between a CDR and a CLS for performing a method of preserving lost billing data according to the present invention.

A method of preserving lost billing data of the present invention will be described with reference to FIGS. 2 to 8.

First, in the initial state (S1), the process proceeds to the step of determining the lost billing data generation (S2) to determine whether the lost billing data that is lost in the OMP billing disk is lost.

That is, the OMP CDR determines whether billing data is not stored in the billing disk and accumulates in the memory queue and exceeds 50% of the total capacity of the memory queue.If it exceeds 50%, the billing data of the memory queue is lost. It is regarded as data and confirms that lost billing data has occurred.

After the lost billing data generation determination step (S2), if the lost billing data is generated in step S3 after the lost billing data transmission step (S2) occurs, the lost billing data in the OMP CDR through the IPC in the form of raw data Send to CLS of OMID.

After the lost billing data transmission step S3, the lost billing data storage step S4 is performed, and the CLS of the OMID receives the lost billing data in the form of raw data transmitted in the step S3 and stores the lost billing data in the disk of the OMID.

In the present invention as described above, when lost billing data occurs, the CDR of the OMP transmits the lost billing data in the form of raw data to the CLS of the OMID through IPC, and then receives the lost billing data transmitted in the form of the raw data in the CLS. To save the lost billing data by saving it to the OMID disk.

Next, referring to FIG. 3, the operation of the CDR in the OMP is described in more detail. The CDR receives the charging data transmitted from the CDGM of each ASP (S11) and temporarily stores the seven charging data in the memory queue in units of one block. If the charge data is accumulated in one or more blocks in the memory queue, the charge data is stored in the charge disk and the charge MT (S12).

Thereafter, if the billing data is not stored on the billing disk and accumulated in the memory queue and exceeds 50% of the total capacity of the memory queue (S13), 60 billing data blocks of the memory queue are regarded as lost billing data and transmitted to the CLS of the OMID. Copy to the temporary memory area (S14).

Then, the CDR transmits a "CLS Alive Request" message to check whether the CLS of the OMID can receive the lost charging data (S15).

After transmitting the "CLS Alive Request" message in step S15, when receiving the "CLS Alive Reply" message from the CLS (S16), the lost data is loaded in the "Lostcall Data" message, and the billing data is stored in units of 10 blocks. If the "CLS Alive Reply" message is not received from the CLS (S16) and continues to transmit the "CLS Alive Request" message, the CLS Alive Reply message is not received from the CLS more than three times. (S18) After outputting the lost billing data in units of one block by MMP (S19), it is checked whether a "CLS Alive Notification" message indicating that the lost billing data is waiting to be received from the CLS is received every block (S20). If a "Notification" message arrives, the process proceeds to step S17 and the lost charging data is loaded on the "Lostcall Data" message and transmitted to the CLS in units of 10 blocks.

After transmitting the charging data of 10 blocks in the step (S17), when receiving the "Lostcall ACK" message from the CLS (S21), the charging data of the next 10 blocks to the "Lostcall Data" message to send to the CLS all 60 blocks After the transmission (S22) proceeds to the step (S13), if the "Lostcall ACK" message is not received from the CLS (S21) proceeds to the step (S15) and transmits a "CLS Alive Request" message to the CLS.

Referring to Figure 4 in more detail the operation of the CLS in the OMID, CLS sends a "CLS Alive Notification" message to the CDR in the initialization process after notifying that the state of waiting to receive the lost billing data (S31), the "CLS Alive from the CDR Wait for the "Request" message to be sent (S32).

After the step S32, when the "CLS Alive Request" message is transmitted from the CDR and the CLS receives the "CLS Alive Request" message (S33), the CLS transmits the "CLS Alive Reply" message to the CDR (S34). Wait for the message to be transmitted from the CDR (S35).

After the step S35, when the message " Lostcall Data " is transmitted from the CDR (S36), the CLS creates a new file on the disk of the OMID (S37) and stores the lost billing data included in the message " Lostcall Data " (S38). .

At this time, if a new file cannot be generated, the message " Lostcall STOP " is transmitted to the CDR (S39), and the process proceeds to the step S32.

In step S38, when the lost charging data is received in 10 blocks (S40), the CDR transmits a "Lostcall ACK" message to the CDR to inform the CDR that the CLS is operating normally (S41). Proceed.

If there is no response without transmitting any message from the CDR since step S35 (S42, S43), the process proceeds to step S39 and transmits a "Lostcall STOP" message to the CDR. If not, the flow proceeds to step S41 and transmits a "Lostcall ACK" message to the CDR.

After receiving the "Lostcall END" message from the CDRs after step S35 (S44), the CLS recognizes that reception of all lost billing data has ended and closes the open file (S45), and proceeds to step S32. Proceed.

5 is a message flow between the CDR and the CLS when the billing data is not stored in the billing disk and exceeds 50% of the memory queue, in which both the CDR and the CLS normally operate.

That is, after the CLS sends a "CLS Alive Notification" message (a) to notify the CDR that it is waiting to receive lost billing data, if the billing data is not stored on the billing disk and exceeds 50% of the memory queue, the CDR tells the CLS. The "CLS Alive Request" message (b) is sent to request the operation, and the CLS sends a "CLS Alive Reply" message (c) to indicate whether the operation is possible.

Subsequently, after receiving the "CLS Alive Reply" message (c), the CDR transmits 60 lost data blocks in the "Lostcall Data" message (d).

The CLS periodically sends a "Lostcall ACK" message (e) once every 10 blocks of "Lostcall Data" to inform the CDR that it is operating normally.

After all 60 blocks of "Lostcall Data" have been transmitted in the CDR, it is checked to see if it exceeds 50% of the memory queue and if so, then the next 60 blocks of billing data are sent to the CLS using the message "Lostcall Data" and 50 of the memory queue. If less than%, it sends a "Lostcall END" message (f) to inform the CLS that all lost billing data has been sent.

6 is a message flow when a message is not received for a certain time while receiving a "Lostcall Data" message in the CLS. If a message is not received for a certain time while receiving a "Lostcall Data" message in the CLS, the message "Lostcall ACK" is transmitted to the CDR. The message is sent three times, waiting for a response. If there is no response, the message "Lostcall STOP" is sent to the CDR and the CLS ends.

FIG. 7 is a message flow when a "Lostcall Data" message is not received for a certain time during transmission of a "Lostcall Data" message in a CDR. After transmitting 10 blocks of a "Lostcall Data" message in a CDR, a "Lostcall ACK" is performed for a predetermined time. "If no message is received, send" CLS Alive Request "message to CLS three times and wait for response. If there is no response, CDR terminates. If CDR receives" CLS Alive Reply "message, send" Lostcall Data "message. send.

8 is a message flow when the CLS does not perform a normal function while receiving a "Lostcall Data" message in the CLS. When the "Lostcall Data" message is received in the CLS, the "Lostcall STOP" is performed. CLS terminates after sending the message to the CDR.

As described above, the present invention has the effect of minimizing the billing data missing in billing settlement by storing and storing the lost billing data in the mobile communication exchange in the form of raw data on the disk of the OMID.

Claims (3)

A loss charging data generation determination step of determining whether the lost charging data that is not stored in the charging disk of the OMP is lost in the CDR; A loss charging data transmission step of transmitting the lost charging data from the CDR to the CLS through the IPC in the form of raw data if the lost charging data is generated in the determination of the occurrence of the lost charging data; The method of claim 6, wherein the CLS receives lost billing data in the form of raw data transmitted in the lost billing data transmission step and stores the lost billing data in a disk of an OMID. The method of claim 1, wherein the operation of the CDR, If the billing data exceeds 50% of the total capacity of the memory queue, the lost billing data copy step of copying the billing data of the memory queue as the lost billing data to the temporary memory, and the lost billing data after performing the lost billing data copying step Transmitting and receiving a check message after receiving the response check message to the CLS, and transmitting the lost charging data to the CLS in units of 10 blocks when receiving the response message in the message transmitting and receiving step; A message acknowledgment step of outputting lost billing data to the MMP if the response message is not received in the message transmission / reception step, and proceeding to the lost billing data transmission step as soon as the lost billing data reception waiting message is received from the CLS; CL after the lost billing data transfer phase When receiving a response message for the transmission of the lost billing data from S after transmitting all the lost billing data blocks to the CLS, proceeds to the copying of the lost billing data, if the response message is not received proceeds to the message transmission and reception step A method of preserving lost billing data in a mobile communication switch, characterized in that the response message receiving confirmation step. The method of claim 1, wherein the operation of the CLS, A message waiting step for receiving a check message for receiving lost billing data from the CDR after transmitting a lost billing data reception waiting message to the CDR; and a check for lost billing data for receiving a check message for receiving lost billing data in the message waiting step. After transmitting the response message that can be received to the CDR, and waiting for the lost billing data from the CDR, and waiting for the lost billing data, if the lost billing data is received in the lost billing data waiting step, create a file on the disk of the OMID A loss charging data storing step of storing the lost charging data, and a response message transmitting step of transmitting a response message indicating that the CLS has received the lost charging data to the CDR after performing the lost charging data storing step; Disk of OMID during data storage phase Stop message transmission step of transmitting a lost charge data transmission stop message to a CDR when a file is not created or no message is received in the lost charging data waiting step; and lost charging data from a CDR in the lost charging data waiting step The method for preserving lost billing data in a mobile communication exchange comprising closing a file open when receiving a transmission completion message and confirming completion of the completion message.