KR0146564B1 - Data processing method for vlr in mobile communication system - Google Patents

Abstract

The present invention relates to a data processing method for a visited location register of a mobile communication system, which satisfies the real-time requirements of a mobile communication system and reflects the characteristics of such data so that it can be applied to a VLR most efficiently. It provides a data backup and recovery method for the visited location register of the mobile communication system to enable the rapid service provision of the system in the VLR to manage the mobility and unique information for the visited subscribers and to increase the reliability of the data. It provides a check pointing method to minimize the recovery time when recovering data of the database processor.

Description

A data processing method for in mobile system

1 is a block diagram of a mobile communication system in which a visited location register is configured according to the present invention.

2 is a configuration diagram of a database system environment for data backup and recovery according to the present invention.

3 is a database structure diagram for data backup and check pointing according to the present invention.

4 is a flowchart illustrating a log backup process according to the present invention.

5 is a flowchart illustrating a database check pointing process according to the present invention.

6 is a flowchart illustrating a data recovery process according to the present invention.

* Explanation of symbols for main parts of the drawings

100: Central Control Subsystem (CCS); Central control subsystem

101: Interconnection Networking Subsystem (INS); Network subsystem

102: Access Switching Subsystem (ASS); Subscriber exchange subsystem

103: Location Registration Subsystem (LRS); Location Registration Subsystem

104: Administration and Maintenance Processor (AMS); Maintenance subsystem

105: Operation and Maintenance Processor (OMP); Operation and Maintenance Processor

106: Man Machine Processor (MMP); Operator Registration Processor

107: Number Translation Processor (NTP); Number translation processor

108: INP (Interconnection Network Processor); Network processor

109: Access Switching Subsystem-Mobile (ASS-M); Subscriber-only exchange subsystem

110: ASS-S / T (Access Switching Subsystem-Subscriber / Trunk); Switching Subsystem for Investigator Subscriber and Trunk

111: Access Switching Subsystem-Trunk (ASS-T); Subscriber switching subsystem for trunk management.

112: ASS-7 (Access Switching Subsystem-No. 7); Subscriber switching subsystem for No.7 signaling.

113: Location Register Application Processor (LRAP); Location Registration Application Processor

114: Home Location Register (HLR); This subscriber location register

115: Visitor Location Register (VLR); Landing location register

116: Equipment Identity Register (EIR); Mobile terminal number register

117: Inter-Processor Communication (IPC); Interprocessor Communication Management System

118: Integrated Service Digital Network (ISDN); Integrated Information Network

119: Public Land Mobile Network (PLMN); Public land mobile communication network

120: Public Switched Telephone Network (PSTN); Public switched telephone network

The present invention relates to a data processing method for a visited location register (VLR) in a mobile communication system, and more particularly, to a data backup and recovery method for a visited location register in a mobile communication system.

Visitor Location Register (hereinafter referred to as 'VLR') is a database that manages data about subscribers in mobile communication system to satisfy the system's requirement to perform communication service anytime, anywhere. It requires real-time data management and manages the change of data caused by the frequent movement of each subscriber requesting service.

In order to satisfy these real-time processing requirements, the VLR is implemented as a main memory database and performs data retrieval and change by a special procedure with other components of the mobile communication system.

VLR also ensures the reliability of data by creating a log of changed data and storing it on disk, a stable storage location, in order to prevent the loss of data in volatile main memory caused by unexpected errors during operation. .

However, in a database system for real-time processing such as a mobile communication system, the load of I / O operations on a disk becomes a factor that can drastically reduce the throughput of a transaction and greatly affect the performance of the VLR. Therefore, logging or check pointing techniques that can cause such disk operations in the database system are very important along with the recovery procedure. In order to solve the performance degradation caused by the use of disk in real-time applications, many studies are being conducted.

However, all of them are designed to reflect the environment or nature of the target system to be utilized, and it is impossible to apply them to different applications.

Accordingly, the VLR to which the backup and recovery technique implemented in the present invention is applied requires more than 1000 transaction processing per second, and is a mixture of temporary data and temporary data stored in a database. In turn, these temporary data perform very frequent changes.

The present invention satisfies the real-time requirements of the mobile communication system and reflects the nature of such data so that it can be applied to the VLR most efficiently, so that the system can manage mobility and unique information for randomly moving visited subscribers. The purpose of the present invention is to provide a data backup and recovery method for a visited location register of a mobile communication system to enable rapid service provision and increase reliability of data.

Another object of the present invention is to provide a method of minimizing disk I / O operations in performing a check pointing method for minimizing recovery time when recovering data of a database processor.

Technical features of the present invention for achieving the above object, the first step of changing the memory according to the mobile subscriber's data change request received by the visited subscriber location register (VLR), and the memory change content A data change processing step of generating a log corresponding to the command type and whether or not the field is backed up and writing the log to the log buffer of the memory; A third step of comparing the usage ratio of the in-memory log buffer with a predetermined reference usage ratio in the data change process, and determining whether or not a log backup request is input by an operator; and by determining the third stage. A fourth step of replacing the log buffer in which the log is recorded with a recordable log buffer and storing the log buffer on a disk; and recording the information on the log backup and reporting the result of the log backup through a system operator terminal or the console. The backup process for the log is performed by performing the log processing process.

Secondly, the first step of determining whether the system is overloaded when the check pointing period set during the initial start-up of the system is reached, and whether there is a check pointing request during the operation by the operator when the check pointing period is not reached. And a log buffer area for storing a log generated during a checkpointing period in order to perform continuous data change operation when it is not overloaded by the system's overload determination and when there is a checkpointing request by the operator. A fourth step of checking whether there is a changed visitor data for each page by searching the database to select a third step of replacing and a page to be checked and a page in which the changed visitor data exists in the fourth step. For log backups that occur during checkpoints The fifth step of replacing the log storage area of the disk for the purpose of operation; and the checkpoint when the checkpointing is completed while continuously storing the page in which the changed data exists after the replacement of the log storage area of the disk on the disk. The sixth step of reporting the results to the operator is to always perform checkpointing.

Thirdly, if the database needs to be reactivated due to a malfunction of the system, the first step of resuming service immediately after recovering the processor storing the visited location register database and recovering the data of the database; A second step of determining whether a service request is inputted to the subscriber from the mobile switchgear, and a third step of checking whether the input data is valid when there is an input of the service request to the subscriber, and determining non-compliance and suitability; A fourth step of transmitting information on the subscriber to the mobile exchange if the input data is appropriate by the determination of the third step; and deleting the location of the subscriber by the request entered if the input data is inappropriate by the determination of the third step. If requested, delete the subscriber information from the database and send the result. A fifth step of continuously performing a service; and a sixth step of determining whether the request is from a home location register or a request from a mobile terminal if the request is not to delete the subscriber location in the fifth step; A seventh step of determining whether the paging result is normally received by performing paging to a corresponding mobile terminal when the request is generated from the home location register in the sixth step; and when the paging result is not normally received in the seventh step, An eighth step of transmitting data retrieval / change error information to the mobile exchange that has sent the access request; and if the paging result is normally received in the seventh step, after recovering the data by the home location register information, the subscriber information; A ninth step of transmitting the result of the processing to the mobile switching center; and a service for the subscriber in the second step. If there is no request for service on the subscriber information that has not been restored at the same time as the request is inputted, it is checked whether the data which read the subscriber information is valid and judges the nonconformity and suitability. The eleventh step and the eleventh step of checking whether the data is valid in the tenth step, and if the data is not suitable, the eleventh step of determining whether the result is normally received and the paging result in the eleventh step. If not, requesting the home subscriber location register to delete the subscriber location and deleting the subscriber information according to whether the deletion result is received; and if the paging result is normally received in the eleventh step and the sixth step; If the request originated from the mobile terminal at the step, check the subscriber information. A thirteenth step of checking whether the current recovery operation is due to a request for subscriber information or an additional recovery procedure when the particle location register is requested and the result is received; A step 14 of recovering the database based on the home location register information and transmitting the result of the subscriber information processing to the mobile exchange in case of restoration by the subscriber information request for service execution; In the case of an additional recovery procedure by the check in the thirteenth step, a data recovery is performed in a fifteenth step of restoring the subscriber relation by the home location register information and then restoring the next subscriber information.

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

1 illustrates a hardware environment in which a VLR to which the present invention is applied is mounted.

This environment is composed of CCS (100), INS (101) and ASS (102) subsystems as mobile communication exchanges that exchange voice and control information for performing subscriber call processing and location registration services in mobile communication systems. The number of ASS is determined as needed.

As shown, the ASS 102 is a subsystem consisting of subscriber and trunk line matching devices, time switches and various signaling devices and the like for performing call processing functions.

INS 103 is located in the center of the system is responsible for the space switch function, number translation and routing functions that connect the ASS mutually.

In addition, the CSS 100 includes an AMS 104 for managing operation management, maintenance, billing, statistical functions, hard disk management, and input / output device of the system, and an LRS 103 for managing location registration and subscriber information of a mobile subscriber. It consists of.

The AMS 104 is a network management, maintenance, testing, measurement, billing of the system, OMP 105 to perform a series of operations and maintenance related functions for the base station, the operator and operation center, the conversation, input and output devices And an MMP 106 for controlling the back.

In addition, the LRS 103 is composed of a LRAP 113 and a Location Register Application Precessor (LRDP) in which a database and a database management system for storing and managing information on data in a mobile communication service are mounted.

In this case, the LRAP 113 needs information on the mobile subscriber when processing functions such as call processing, handover, and location change for the mobile subscriber.

At this time, IPC 117 processing with other processors in the exchange, ISDN 118 or PSTN 119, and the No.7 signaling system between the exchange and network elements constituting the other network, such as a separate PLMN (120) It handles the Transmission Control Application Part (TCAP) and Mobile Application Part (MAP) and delivers the information in the LRDP to the desired location.

The LRDP is a processor name representing all of the HLR 114, VLR 115, and EIR 116. The LRDP is a processor that stores and manages information on a subscriber or a mobile terminal, and accesses information to a subscriber from the LRDP 113. It performs the processing of search / registration / cancel / change and is responsible for backing up all data to disk when subscriber information is changed or periodically.

Each processor in the LRS 103 has the same hardware structure as the other processors in the exchange, and uses a main memory database to meet real-time requirements.

In particular, the LRDP maintains 64 megabytes of main memory to manage data for mobile subscriptions.

In addition, the HLR 114 stores information about the mobile subscribers in the region where the mobile subscriber first registered and wants to receive the service, and the VLR 115 stores the information on the visited subscribers when receiving the communication service while moving to another region. To manage information

The EIR 116 is a database that stores information on mobile terminals that perform mobile services.

The transmission of data or signals between each of these subsystems or processors is performed by IPC 117, which is a communication protocol in the exchange.

2 shows the structure of the visitor information management database system to which the present invention is applied.

Information about the visitor is stored and managed in the LRDP, which is the visitor location information management processor 200.

This LRDP 200 has the same structure as other main processors in the mobile switchboard and has 64 megabytes of main memory 201.

The main memory 201 stores data of 123 bytes per subscriber in a relation form, and a database management system for managing the data is mounted.

The database management system consists of two software processes.

First, the mobile subscriber information management processor 202 is responsible for retrieving and changing data through the relational model, supports fast access techniques to meet real-time requirements, allocates and retrieves memory, audits data, Performs overall data management functions except backup and recovery procedures such as interface with application programs.

Second, the data backup and recovery process 203 is a process that handles all functions that cause operations with the disk in the operation of the database. The data backup and recovery process 203 is implemented separately from the basic data management process to perform a series of operations related to the disk. The data access request will continue during the process, with minimal impact on performance.

The disk 208 used here is a redundant disk and stores a log of changed data and a backup image of the database.

The process consists of four software modules, depending on the function: log backup module, check point processing module, processor recovery module, and subscriber data recovery module.

The log backup module 204 is a module for backing up the log generated for the data that needs to be backed up among the changed data to the disk. The log backup module 204 performs a backup function generated when a log area in the memory is recorded over a certain period. Perform.

In addition, the checkpoint processing module 205 is responsible for checkpointing periodically reflecting a memory image of a database on a disk in order to reduce the time required to apply a large amount of logs during recovery and to quickly perform a service. .

In addition, the processor recovery module 206 recovers the LRDP by a procedure such as restoring other processors of the mobile communication switch when the processor fails due to an unforeseen phenomenon during execution or restarts due to interruption of power supply. This module performs.

The recovery of the LRDP is performed by downloading a program and a data module from the disk 211 managed by the OMP 209 which is an operation preservation processor of the mobile communication exchange.

However, such a procedure is performed by a system loader in an operation preservation processor, and a disk 211 storing various software execution modules or data modules to be mounted on each processor is redundantly used to maintain stability.

The mobile subscriber data recovery module 207 is a module for restoring the data and data management system in the database after the LRDP processor in which the database is mounted is restored. To help.

3 shows a relation structure of visitor information to which the present invention is applied, which shows that it is operated in a logically divided form to apply efficient backup and recovery procedures.

Since the VLR uses an access method of multiple hash directories 300 having a tree structure to satisfy real-time requirements, hash directory and index information additionally used for database access during data backup should be backed up together.

However, this procedure will incur significant overhead in the backup and recovery of relatively large hash directories.

Therefore, the present invention selects a method of backing up and restoring only the data by separating the control information and the actual data used in the database management system, and reconstructing the hash directory and the index at the time of restoration.

This method saves disk I / O time, which takes the most time when the database is backed up and restored, and enables fast recovery by performing recovery by using a significantly faster CPU.

The unique information and location information of the visitor stored in the VLR is composed of 22 attributes (301), which can store information about 350,000 subscribers to satisfy the maximum capacity of the system. It is a relation with only tuples 306.

These attributes fall into three categories, depending on their nature and whether they are backed up.

The first category is the unique information of visit subscribers. If the data change operation is triggered during operation, the log must be generated and the unique number for each subscriber and the subscriber should be kept up to date when restoring the database. The device number of the mobile terminal owned, the operation type of the terminal and whether or not the incoming call of each terminal belongs to this (302).

The second class is information depending on the current position of the mobile terminal, which is information that can be recovered by a paging procedure to multiple writers of the database after processor recovery (303).

The third category is information changed by the operator during system operation, such as call monitoring and location tracking information, subscriber category, billing information, supplementary service information, and subscriber priority information (304).

The database backup process performs a backup by dividing the relation as described above, and divides the backupable part of the relation into page units for checkpoints to reduce the amount of logs and shorten the recovery time. When the checkpointing is requested by the request, the backup is performed only for the page in which the change has occurred, thereby minimizing the frequency of the overall disk I / O operation (305).

As described above, in FIG. 3, the hash directory area can be backed up and restored for storing and retrieving visitor information, and the relation for backup application according to the visitor data characteristics can be divided.

4 is a flowchart illustrating a log backup process according to the present invention, and illustrates a data change process and a log process thereof when a general data change request is input.

First, the first step (S1) of changing the memory in accordance with the mobile subscriber's data change request received by the visited subscriber location register (VLR), and the log of the memory change contents of the command type and field (Attribute) A data change processing step (A) comprising a second step (S2-S5) of generating and writing to a log buffer of a memory according to the backup status, and a predetermined use ratio of the log buffer in memory in the data change processing step (A) The third step (S6-S8) of judging whether or not the log backup request is input by the operator, and the log is compared with the reference usage ratio of the controller (eg, 90% or more). A fourth step (S0, S10) of replacing the recorded log buffer with a recordable log buffer and storing the information on the log backup; and the fifth step of reporting the log backup result through a system operator terminal or console. A log process (B) consisting of steps S11 and S12 is performed to backup the log.

The flow by these steps is explained as follows.

The types of data change that can be received by the VLR are the operation of inputting and deleting subscriber information and of changing any attribute of the relation.

Once the data change request is received, the tuple in which the corresponding information is stored is determined according to the access procedure, and the change is performed in the memory at the position (S1).

The log of the changed contents of the memory is generated by dividing each command.

In other words, if the command is an input of subscriber information, changes to all data that need to be backed up are recorded, including the type of the command and the subscriber's unique number. Record only the numbers.

When changing some attributes of the subscriber relations, it checks whether the changed attributes are required to back up, and if the field backup is required, records the type of command, subscriber ID number, location information of changed attributes, and changed values in the log. To generate a log (S2, S3, S4).

The log generated in this way is recorded in the log buffer of memory, and the log buffer is divided into two parts to maintain data consistency at checkpoint.

In other words, the log recorded in the first part is recorded in the second part from the point where a random checkpoint starts, and is also operated in the form of being recorded in the first part again from the next checkpoint point (S5).

The above data change processing process (Fig. 4 (a)) takes a postponed transaction completion method of returning the results to the application program before storing the log on a stable disk for real-time data processing.

In addition, the log processing process (Fig. 4 (b)) to perform the group completion to save to the disk at a certain point at a time is as follows.

This log processing process is configured separately from the data processing process so that disk I / O operations do not affect normal data access service performance.

The log backup process sometimes copies the log buffer in memory to the log storage on disk.

The first case is when the log buffer allocated in memory is over 90% full, and the second case is when the request is made directly from the system's operator (S6, S7, S8).

The log is generated because the change operation on the subscriber data is continuously performed during the log backup.

Therefore, random log may not be saved to disk due to collision of read operation and write operation for log buffer. To prevent this, divide log buffer area into two parts and write log to the other side when log backup to one side. Do it.

As a result, once a backup of a log is initiated, a log of changes that occur from then on is recorded from the beginning of the other parts of the log buffer.

In the log backup process, after replacing the position of the log buffer area to record the log (S9), the previous log buffer is read and stored on the disk as a stable storage location (S10).

When the log backup is completed, the log is reported through the system operator terminal or the console, and a record of the backup operation is separately stored (S11 and S12).

5 is a checkpointing process for data in a mobile subscriber according to the present invention, which reduces disk I / O operations as much as possible for the checkpoint technique used to reduce the amount of logs and minimize the recovery time of the database processor. Try to reduce the impact on the entire system.

According to the checkpointing process, the first step (S20, S22, S23) of determining whether the system is overloaded or adjusting the checkpoint period when the system is overloaded when the checkpointing period set at the initial startup is reached, and the checkpointing is performed. If the period is not reached, the second step (S21) of determining whether there is a checkpointing request during operation by the operator, and the checkpointing request by the operator when it is not overloaded by the system overload determination (S22). Step 3 (S24) to replace the log buffer area to store the log generated during the checkpointing cycle in order to perform continuous data change operation, and to search the database to select the page to checkpointing A fourth step (S25, S26) of checking whether the visitor data exists; A fifth step (S27) of replacing the log storage area of the disk in order to prepare for a log backup generated during the checkpoint when there is a page in which the child data exists, and changed after replacing the log storage area of the disk in the fifth step. After the page in which data exists is continuously stored in the disk and checkpointing is completed, the checkpointing is performed at all times by performing sixth steps (S28 and S29) of reporting the checkpoint result to the operator.

The flow by these steps is explained as follows.

The checkpointing implemented in the present invention is driven periodically or by direct command of the operator.

The period of checkpointing is set as a system parameter at system start-up and can be changed at the operator's command during operation.

Therefore, the checkpointing process is driven when the operator's command is input or the checkpoint period is reached.

At this time, in the case of the checkpointing performed periodically, the system checks the overload of the system and automatically changes the checkpoint period when the database processor has a load of a certain level or more, and suspends execution (S20, S22, and S23).

However, in case of operator's command, checkpoint is executed immediately without checking for overload, which operator usually checks the state of the system to request a series of tasks that can affect the system's performance. This is because the load of the database is measured in advance before the checkpoint is executed, and then the command is executed according to the result (S21).

Once the checkpoint procedure is started, the log buffer area to store the log generated during checkpointing is replaced to perform continuous data change operation (S24).

Then, the database is searched and a flag to checkpoint is selected by checking a flag for storing the existence of changed data for each page (S25).

In this case, the changed data may be recorded in a disk in which the changed data exists or more.

Once the page to be stored on the disk is selected, the log storage area of the disk is closed to replace the log area of the disk, and another log storage area is opened to prepare for log backup that may occur during checkpointing (S27).

It then searches the database, selects pages marked with the change flag, saves them to disk, and reports checks to the operator regarding their status, the amount of memory written to the disk, and the next checkpoint cycle. S28, S29).

6 is a flowchart showing a data recovery process according to the present invention.

This is efficiently performed for quick service resumption during data recovery with temporary data stored in the database and temporary data such as subscriber's unique information stored together.

The data recovery process is to restart the service to recover the data in the database after recovering the processor storing the visited location register database if the database needs to be reactivated due to a malfunction of the system. Step 1 (S30-S34), the second step (S35) of judging whether the service request is input to the subscriber from the mobile exchange, and if there is an input of the service request to the subscriber, it is checked whether the input data is valid. And a third step (S36, S37) of determining the suitability, and a fourth step (S38) of transmitting information on the subscriber to the mobile exchange if the input data is suitable according to the determination of the third step; If the input data is inappropriate by the judgment of the step, if the input request is a request to delete the subscriber's location, Deleting and transmitting the result, and then continues with the fifth step (S39, S40) and continue to perform the service, and if the request is not the request to delete the subscriber location in the fifth step determines whether the request originated from the home location register Or step 6 (S41S, 42) of determining whether the request is caused by the mobile terminal, and if the request is caused by the home location register in the sixth step, paging to the corresponding mobile terminal to receive a paging result normally. A seventh step (S43, S44, S45) of judging, and an eighth step of transmitting data retrieval / change error information to the mobile exchange which sent the data access request if the paging result is not normally received in the seventh step (S43, S44, S45). S46), and if the paging result is normally received in the seventh step, recover the corresponding data by the home location register information and then process the processing result of the subscriber information. The subscriber information is read when there is no input of the service request for the subscriber information which has not been recovered at the same time as the input of the service request to the subscriber in the second step (S47, S48) and the second exchange. If the data is valid, it is determined to be inadequate and suitable, and if appropriate, the tenth step (S49, S50) to perform recovery for the next subscriber information, and if the data is valid by checking the validity in the tenth step Paging to the mobile terminal to determine whether the result is normally received (S51 and S52), and if the paging result is not received in step 11, requesting the home subscriber location register to delete the subscriber location. Thereafter, step 12 (S53-S57) of deleting the subscriber information according to whether the deletion result is received, and in the eleventh step, the paging result is normally received. In the case of the request generated from the mobile terminal in step 6 and the request for confirmation of the subscriber information to the home subscriber location register and the result is received, if the current recovery operation is due to the request of the subscriber information to perform the service. 13th step (S58-S61) for checking whether it is due to an additional recovery procedure; and in case of recovery due to a request for subscriber information for service execution by the check in the 13th step, restoring the database by the home location register information And after transmitting the subscriber information processing result to the mobile exchange, step 14 (S62-S63) for performing recovery for the next subscriber information, and in case of additional recovery procedure by the check in step 13, the home location register. After restoring the subscriber relation based on the information, the 15th step (S64) is performed to recover the next subscriber information. Perform a recovery.

The flow is explained by these steps as follows.

If the system needs to be reactivated due to hardware failure or interruption of power during operation, it is necessary to restore the data stored in the database to the most recent state.

When the LRDP, the processor that stores the database, is reactivated, the necessary software can be managed using the system disk managed by the OMP 105, which is responsible for the operation and maintenance of the mobile switching center. Reload the data modules (S30).

After the recovery of the processor is completed by the loading procedure performed by the existing exchange, the VLR recovers the data by using the information stored on the disk by log backup and checkpointing.

Accordingly, the database image of the VLR disk is first applied to the memory (S31), and the memory in the disk is read (32) to read the log in the disk to reflect the changes generated after the random checkpointing.

An index tree is constructed to recover a hash directory and an index capable of performing an access scheme to perform a search and change on the data restored to memory (S34).

When the recovery procedure is performed up to the above steps, the system can perform a database search or change to perform the mobile service (S34). In the case of temporary data that has not been recovered yet, the service can be performed by a recovery procedure that has not yet been completed. When a request is made, a series of tasks are performed to get accurate data.

In addition, it is determined from the mobile exchange whether a service request for a specific subscriber is input (S35). When the service request is input, the validity of the corresponding tuple is checked and, if appropriate, the requested command is performed and the result is transmitted to the application program. S36, S37, S38) Otherwise, perform additional recovery procedures for each class of request.

If it is determined that the tuple is inappropriate, if the input request is a subscriber location deletion request, the tuple is deleted from the database, the result is transmitted, and the service is continuously performed (S39, S40).

When the input request is a request generated from the home location register (S41), the mobile terminal performs paging to obtain the location information of the corresponding subscriber (S43, S44).

When the paging result is normally received, information about the subscriber is requested to the home location register to obtain information other than the location information (S45 and S47).

The result is transmitted to the application program of the requesting mobile switch and the recovery flag for the corresponding tuple is changed to the recovery complete state (S48).

However, if the result of paging is not normally received or error information is received, error information is transmitted to the application program of the mobile exchange that sent the data access request, and the recovery flag is left as it is, so that recovery can be attempted later (S46). ).

In addition, in the case where the request is caused by the mobile terminal, data other than the location information is requested to the home location register (S42).

On the other hand, when there is a service request for the subscriber and at the same time there is no service request for the subscriber, the additional recovery procedure performs recovery one by one while searching for tuples from the beginning of the relation, excluding the subscribers recovered by the mobile service request procedure. And proceed (S49, S50).

Then, each unrecovered tuple (data) performs a paging to the corresponding mobile terminal and immediately sends a subscriber information request message to the home location register when the result is received (S51, S52, S53, S58).

When the result message is received from the Greek home location register and the result is normally received (S59, S60), it is checked whether the current recovery operation is due to a request for subscriber information or additional recovery procedure (S61). In case of recovery by data retrieval request, the value is transmitted to the application program that requested the data access after the database is restored (S62, S63).

In case of an additional recovery procedure, the subscriber relation is restored after the subscriber relation is restored (S64).

In the data recovery process, when there is no service request for a subscriber, a recovery load can be reduced by performing a recovery procedure when a request for access to unrecovered subscriber information is performed.

In addition, it is possible to save traffic load with the home location register by referencing only the information about the subscriber who has a response by paging during data recovery.

As described above, the present invention enables the rapid service provision, which is the maximum goal of the system, and the reliability of the data in the VLR, which must manage mobility and unique information for randomly moving subscribers.

Claims (7)

The first step of changing the memory in accordance with the mobile subscriber's data change request received by the visited subscriber location register (VLR), and generates a log of the memory change according to the command type and field backup, the log of the memory A data change processing process comprising a second step of writing to a buffer; A third step of comparing the usage ratio of the in-memory log buffer with a predetermined reference usage ratio in the data change process, and determining whether or not a log backup request is input by an operator; and by determining the third stage. A fourth step of replacing the log buffer in which the log is recorded with a recordable log buffer and storing the log buffer on a disk; and recording the information on the log backup and reporting the result of the log backup through a system operator terminal or the console. A data processing method for a visited location register of a mobile communication system, characterized in that for performing a log processing process performed to process a backup of the log. 2. The data as claimed in claim 1, wherein in the fourth step, the log buffer divides the log buffer area into two parts and records the log of the other side when the log backup of one side is performed. Treatment method. 2. The visited location of a mobile communication system according to claim 1, wherein the data change request is generated in the case of inputting and deleting information of a mobile subscriber and in changing some attributes of a mobile subscriber relation. Data processing method for the register. A first step of determining whether the system is overloaded when the checkpointing period set at initial startup of the system is reached; a second step of determining whether there is a checkpointing request during operation by the operator when the checkpointing period is not reached; And a third step of replacing a log buffer area to store a log generated during a checkpointing period in order to perform continuous data change operation when it is not overloaded by the overload determination of the system and when there is a checkpointing request by the operator. And a fourth step of checking whether there is a changed visitor data for each page by searching a database to select a page to be checked and a checkpoint if there is a page in which the changed visitor data exists in the fourth step. To prepare for log backups that occur The fifth step of replacing the log storage area of the disk and the page in which the data changed after the log storage area of the disk is continuously stored on the disk, and the checkpoint result is displayed when the checkpointing is completed. And a sixth step of reporting to the operator to perform checkpointing at all times. 5. The visited location of claim 4, wherein the fifth step includes replacing the log area of the disk by closing the log storage area of the disk and opening another log storage area when a page to be stored on the disk is set. Data processing method for the register. 5. The data processing method of claim 4, wherein the third step automatically changes a checkpoint period when the system is overloaded by determining whether the system is overloaded. If the database needs to be reactivated due to a malfunction of the system, the first step of resuming service immediately after recovering the processor storing the visited location register database and recovering the data of the database; A second step of determining whether a service request is inputted to the subscriber from the second step; a third step of determining whether the input data is valid when the service request is input to the subscriber; A fourth step of transmitting information on the subscriber to the mobile exchange if the input data is appropriate by the determination of the step; and a request date for deleting the location of the subscriber if the input data is inappropriate by the determination of the third step. If the subscriber information is deleted from the database, then the result is sent continuously. A fifth step of performing a service, and a sixth step of determining whether the request is caused by a home location register if the request is not to delete the subscriber location in the fifth step, or determining whether the request is caused by a mobile terminal; In the sixth step, if the request is caused by the home location register, a seventh step of determining whether a paging result is normally received by performing paging to a corresponding mobile terminal; and when the paging result is not normally received in the seventh step. An eighth step of transmitting data retrieval / change error information to the mobile exchange that has sent the data access request; and if the paging result is normally received in the seventh step, after recovering the data by the home location register information, the subscriber; A ninth step of transmitting the result of the processing of the information to the mobile switching center; If there is no input of service request for subscriber information that has not been recovered at the same time as input of service request, it is checked whether the data which read the subscriber information is valid and judges whether it is non-conformance and suitability. A tenth step of performing the step; and an eleventh step of checking whether the data is valid in the tenth step and determining whether the result is normally received by paging to a corresponding mobile terminal, and the paging result in the eleventh step. Is not received, requesting deletion of the subscriber location from the home subscriber location register, and deleting the subscriber information according to whether the deletion result is received; and if the paging result is normally received in the eleventh step; In step 6, if the request originated from the mobile terminal, the subscriber information is checked. A thirteenth step of checking whether the current recovery operation is due to a request for subscriber information or an additional recovery procedure when the subscriber location register is requested and the result is received; A step 14 of recovering the database based on the home location register information and transmitting the result of the subscriber information processing to the mobile exchange in case of restoration by the subscriber information request for service execution; In the case of the additional recovery procedure by the check in step 13, the mobile station comprises the fifteenth step of restoring the subscriber relation by the home location register information and then restoring the next subscriber information. A data processing method for a visiting location register of a communication system.