KR20000074019A - backup method of data base of moving communication user - Google Patents

Abstract

PURPOSE: A method for backing up a database of a mobile communication subscriber is provided to divide kinds of transactions into an immediately-backup required transaction and a general transaction, and to divide an entire backing-up data area into regular pages to maintain information for distinguishing the pages, so as to change only corrected parts of data of the general transaction by identifying the information when a backing up period comes, to perform a real-time backing-up operation. CONSTITUTION: A home location register(HLR) system divides entire memory areas for storing various subscriber data into predetermined pages. The system forms data tables matched by one by one as predetermined bits in the memory divided areas. If an updating process is performed by relating to stored data of a specific subscriber, the system updates the stored data and decides which area the data is included. The system changes the predetermined bits into designated specific states among the data tables. If a time point for backing up the subscriber data comes, the system backs up data only which exists in memory areas corresponding to the changed predetermined bits.

Description

Backup method of database of mobile subscribers {backup method of data base of moving communication user}

The present invention relates to an operation management method of a mobile communication service network, and more particularly, to a database of a mobile communication subscriber for reducing time and hardware burden for backing up and managing information such as location information and additional services of a mobile communication terminal. It is about backup method.

In general, in the mobile communication service network, due to the uniqueness of mobile communication, the subscriber's current location must be checked at all times, and data management must be continuously performed. HLR system is a system that is responsible for such a function.

In the HLR system, a data backup method is used to prevent damage to subscriber data caused by a system error. This backup method is a very important parameter that determines the performance of the HLR system.

In this case, referring to FIG. 1 to which the backup structure of the HLR system is attached, the HLR system shown in FIG. 1 uses a main memory database for real-time processing of a transaction.

That is, the data file existing on the disk when the system is running is loaded into the memory, and after loading, the data of the memory is frequently stored on the disk for the subscriber data backup.

However, in constructing the main memory storage system, one of the problems that must be considered is the recovery according to the damage of the stored data.

It uses a technique to keep log records in stable storage at the end of a transaction in an existing database system. During a transaction, all changes are reflected in the database in main memory, and log records are written to the log buffer. At the end of a transaction, a commit log record is written and all log data up to that point is reflected on disk. In addition to log records at checkpoint, all the data in the main memory that has been changed are reflected on disk.

This crash recovery method is not suitable for HLR systems that need to process a large amount of transactions in real time, and a log must be recorded every time a transaction occurs. There is a situation.

An object of the present invention to solve the above problems is to process a large amount of transactions in real time, so that the transaction type should be divided into a transaction that must be immediately backed up and a transaction that is not, and the congested data area to be backed up to a page of a constant size. By maintaining the information that distinguishes the changed page by dividing, the transaction that will not be backed up immediately checks this information when it is later backed up, and changes only the modified part of the data so that the real-time operation of the backup is performed. The present invention provides a method of backing up a subscriber's database.

1 is an exemplary diagram for explaining a data backup structure of an HLR system;

FIG. 2 is an exemplary diagram for explaining a modified data region classification method using a dirty bit, which is a technical concept applied in the present invention.

3 is a flowchart of an immediate backup operation by a database backup method of a mobile subscriber according to the present invention.

4 is a flowchart of a periodic backup operation by a database backup method of a mobile communication subscriber according to the present invention.

A feature of the present invention for achieving the above object is a data backup method in an HLR system for providing subscriber registration information and additional services, such as a memory for storing various subscriber manager fees according to system operation. A first process of subdividing the entire area into a predetermined number of page concepts, a second process of forming a data table that is one-to-one matched by a predetermined bit in a memory partition area divided through the first process, and storing data of a specific subscriber A third process of determining which of the memory partitions subdivided in the first process when an update situation occurs, and specifying a predetermined bit in a data table corresponding to the partition according to the determination of the third process 4th process of converting to state and reaching point in time of backing up subscriber's data to disk Through it said fourth step is to include a fifth step for backing up only data present in the memory partition corresponding to the predetermined number of bits converted into a specific state.

The above objects and various advantages of the present invention will become more apparent from the preferred embodiments of the invention described below with reference to the accompanying drawings by those skilled in the art.

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

2 is an exemplary diagram for explaining a modified data area classification method using dirty bits, FIG. 3 is a flowchart of an immediate backup operation by a database backup method of a mobile subscriber according to the present invention, and FIG. Is a flowchart of a periodic backup operation by a database backup method of a mobile subscriber according to the present invention.

First, with reference to the accompanying Figure 2 will be described with respect to the modified data region classification method using a dirty bit (dirty bit) which is a technical concept applied in the present invention.

The entire memory area is subdivided into a predetermined number of page concepts.

In this case, if each divided memory area is called a page, the dirty bits of one bit are sequentially listed in correspondence to each of the pages sequentially listed, and then the dirty bits corresponding to the page in which the changed contents are present ( dirty bit maintains a logic '1' or on state, and a dirty bit corresponding to a page for which no changes have been made maintains a logic '0' or off state.

Therefore, the entire data area is divided into a plurality of pages in the same amount, and a dirty bit corresponding to each page is allocated, and then the dirty bit is maintained. In other words, since the dirty bit is initially set to off and is turned on when the data in the page is changed, searching the contents of the dirty bit table to see whether the contents of each corresponding page have changed. Able to know.

As described above, the reason for applying the concept of a dirty bit in the present invention is briefly described as follows.

In general, the capacity of subscribers managed by the HLR system is in the range of several hundred thousand to millions. Therefore, there is a performance problem in backing up a large amount of whole data. In other words, it takes a lot of CPU and I / O time to perform backup while doing MAP (Mobile Application Part) operation for subscriber.

Therefore, the present invention starts from the viewpoint that it is advantageous to back up by reflecting only the changed portion of the data contents of the memory on the disk.

As described above, even if only the part of the data contents of the memory is backed up by applying the concept of dirty bit, the time of backup is important. Generally, the method that can be applied in a system such as an HLR system is an immediate backup method. It can be divided into a periodic backup method, but both backup methods are used in the present invention.

First, referring to FIG. 3 attached to an operation sequence for instant backup in the present invention, two types of transactions for changing data of an HLR system can be largely divided into two types, and a transaction is generally a MAP operation. Since REG, CAN, RTR, and LOC, which are responsible for the movement of subscribers during association, occur frequently, system performance is a problem for backing up the changes in memory to disk whenever these operations occur.

Therefore, frequently occurring MAP operations should be backed up periodically instead of immediately. Only operations such as adding and deleting subscribers are immediately backed up.

Also, even if you do not back up immediately, if you set the dirty bit to on and back up later, the disk will be backed up at that time.

Therefore, if it is determined in step S11 that data to be updated is present among the data in the memory, the flow proceeds to step S12. In step S12, the logic " 1 " EH turns on the dirty bit corresponding to the page containing the updated data, and the flow proceeds to step S13.

In step S13, it is determined whether the update currently generated in step S11 is data related to the transaction described above, and the data updated through step S14 is backed up to the disk only when it is determined that the update is related to the transaction. .

Unlike the case described above, in the case of periodic backup, as shown in the accompanying FIG. 4, it is determined in step S21 whether or not the backup period has been reached, and only when it is determined that the step period has elapsed, the dirty bit ( dirty bit) Only pages corresponding to a logical "1" or dirty bit in the table are backed up to disk.

EK, you should periodically back up to disk to back up changed data that was not immediately backed up. This frequency is determined by the operator and is generally maintained about once a day. Only pages with the dirty bit turned on are backed up to disk.

While the invention has been shown and described in connection with specific embodiments thereof, it will be appreciated that various modifications and changes can be made without departing from the spirit and scope of the invention as indicated by the claims. Anyone who owns it can easily find out.

By providing a database backup method of a mobile communication subscriber according to the present invention operating as described above

Claims (5)

A data backup method in an HLR system for providing subscriber registration information or additional services, etc., A first step of subdividing the entire area of the memory for storing various subscriber manager fees according to system operation into a predetermined number of page concepts; A second process of forming a data table that is one-to-one matched by a predetermined bit in the memory partition area divided by the first process; A third step of updating data when an update situation of stored data of a specific subscriber occurs and determining which of the memory partitions are divided in the first step; A fourth step of converting a predetermined bit in a data table corresponding to the partition into a promised specific state according to the determination of the third step; And And a fifth step of backing up only data existing in a memory partition corresponding to predetermined bits converted to a specific state through the fourth process when the point of time when the subscriber's data is backed up to the disk is reached. How to backup your database. The method of claim 1, A determination step of determining whether data updated in the third step after the fourth step belongs to a preset emergency transaction; In the determining process, if it is determined that the data updated in the third process does not belong to the emergency transaction, the process proceeds to the fifth process. If it is determined that the data belongs to the emergency transaction, the partition to which the data belongs is backed up to the disk in real time. And further comprising the step of proceeding to the fifth step. The method of claim 1, The data table formed in the second process is a database backup method for a mobile subscriber, characterized in that each of the bits consisting of one bit. The method according to claim 1 or 3, And said promised specific state is such that said dirty bit maintains a state of "1" or an on state. The method of claim 1, The time point at which the subscriber's data is backed up on the disk is based on 24 hours after the data backup.