KR100359993B1 - Backup method for subscriber's data of home location register - Google Patents

Abstract

The present invention relates to a method of backing up subscriber data of a home location register. The present invention relates to a method of backing up subscriber data of a home location register based on a first step of classifying a change type and a result of the classification of the first step. After generating the backup data according to the second file to be stored in the shared file system, the backup data has a file name that can identify the type of change, and the backup management unit of the backup-home location register for the shared file system A third step of reading the backup data from the backup data based on the file name of the backup data and reading the type of change of the backup data; and for backup, based on the reading result of the third step. The fourth step of changing the subscriber data stored in the home location register, and the change of the subscriber data of the backup-home location register in the fourth step is successful. If it is completed as the, characterized in that it comprises a fifth step of deleting the backup data stored in the shared file system for the change of the subscriber data. Accordingly, the present invention is characterized in that the inconsistency of subscriber data between the home location register and the backup system can be minimized without causing overload on the home location register and the network.

Description

Backup method for subscriber's data of home location register}

The present invention relates to a method of backing up subscriber data of a home location register. In particular, after analyzing the type of change of subscriber data stored in the home location register, the subscriber data can be efficiently stored by adopting different backup methods according to the type of change. The present invention relates to a method of backing up subscriber data of a home location register.

A home location register is a system introduced to a mobile telephone network to provide a mobile phone service regardless of a change in the location of a mobile phone subscriber. The home location register has jurisdiction over a predetermined area and is provided by subscriber terminals located in the area. It stores / manages all the information necessary to provide mobile phone service, ranging from subscriber number, terminal unique number and additional service selection information. Therefore, the home location register requires a high degree of reliability and must always be in a steady state. In addition, the mobile telephone network operator increases a plurality of home location registers as the number of mobile subscribers increases. FIG. 1 is a configuration diagram of an operation environment of such a home location register. Referring to FIG. 1, a plurality of home location registers 102 to 104 are connected to a Signaling System 7 Network (SS7) 101 and a Local Area Network (LAN) 108. At this time, the home location registers 102 to 104 are connected to other network elements (eg, mobile switching center (MSC), visitor location register (VLR) in the mobile communication network through the SS7 network 101. ), Short Message Service Center (SMSC), etc. (not shown)], the Customer Center 111 and the Network Management Center (NMC) for customer management through the LAN 108 Works with (not shown). In addition, the home location registers 102 to 104 interoperate with the operator terminals 105 to 107, respectively, for registration with the operator and system operation, maintenance, and maintenance. In the example of FIG. 1, home location register-1 102 interworks with operator terminal 105, home location register-2 103 interworks with operator terminal 106, and home location register-n 104. Is linked with the operator terminal 107.

If any one of these home location registers fails in the home location register, other network elements in the mobile communication network cannot know the location information of the mobile subscriber registered with the home location register. Therefore, the incoming call to the mobile telephone which has registered the location in the home location register where the failure occurs is impossible. As a result, the failure of the home location register results in a deterioration of the quality of the mobile phone service. In addition, service providers will be seriously injured.

Therefore, in order to minimize service quality deterioration and damages of operators due to the failure of the home location register, most mobile phone operators are adopting a backup system of the home location register. That is, as shown in Fig. 1, a backup-home location register 110 connected to a LAN 108 and an operator terminal 109 for operating the backup-home location register 110 are adopted. In an example, the backup-home location register 110 receives subscriber data stored in each home location register 102-104 from a plurality of home location registers 102-104 that are actually in operation via the LAN 108. Back up. And, if a failure occurs in one of the home location registers 102 to 104, the backup-home location register 110 is started using the subscriber data backed up to the backup-home location register 110, The backup-home location register 110 is operated as an alternative system of a failed home location register. Therefore, it is possible to minimize service downtime due to the home location register failure.

At this time, the home location registers 102 to 104 copy the subscriber data stored therein to the backup-home location register 110 at a predetermined backup period (for example, 4 to 24 hours) according to the system operating environment. The shorter this backup cycle, the more reliable the backed up subscriber data. However, the subscriber data has a limitation in shortening the backup cycle due to the large file size and the number of home location registers to be backed up. In other words, if the backup cycle is shortened, the work processing capacity peculiar to the home location register may be degraded due to the overload of the LAN and the home location register.

Therefore, in order to prevent such a problem, in the case of a large number of target systems (that is, home location registers), the start point of copying of database files is different from each other to reduce the overload of the LAN and to limit the number of backups. This reduces the number of times the overload occurs, and also prevents the quality of processing from being degraded.

However, in case of backing up subscriber data in such a conventional manner, since the change history of subscriber data generated between backup and backup is not backed up to the backup-home location register, the longer the period of backup, the more the backup-home location register and the home location register. There is a disadvantage that the inconsistency time of the subscriber data can be long. In addition, there is a problem in that the subscriber's data that is not frequently changed data is backed up every backup cycle, causing unnecessary load.

On the other hand, if the location information in the subscriber's network is changed so frequently that it is not backed up in real time, an incoming call may be generated due to inaccuracy of the location data even when the backup home location register is started using the backed up data when a failure occurs. There was a problem that many cases are not processed normally.

That is, when the home location registers are operated using the conventional home location register database backup method, there is a problem that an incoming call to the mobile phone becomes impossible when a system failure occurs due to the lack of real time backup of the subscriber database.

The present invention has been made to solve the above problems, and when the subscriber data stored in the home location register is changed, the change type is analyzed, and then different backup methods are adopted according to the change type. It is an object of the present invention to provide a subscriber data backup method of a home location register for backing up subscriber data and a computer readable recording medium storing a program for realizing the method.

1 is a configuration diagram of an operating environment of a general home location register.

2 is a block diagram of a home location register for backing up subscriber data in accordance with one embodiment of the present invention;

3 is an explanatory diagram for explaining a subscriber data backup process of a home location register according to an embodiment of the present invention;

4 is an explanatory diagram for explaining a method of backing up backup data of a plurality of home location registers to one backup-home location register according to an embodiment of the present invention. FIG. 5 is a kind of backup data for each occurrence factor of backup data. Figure 6 is an exemplary diagram for a table for managing the location information of the subscriber by the point code of the MSC in the backup-home location register according to an embodiment of the present invention.

7 is a process flow diagram for a method for a home location register to generate subscriber data for backup in a shared file system according to one embodiment of the invention.

8A and 8B are a flowchart illustrating a method of backing up subscriber data for backup stored in a shared file system by a backup-home location register according to an embodiment of the present invention. SS7 Network 220: Home Location Register 230: LAN 240: Operator Terminal 250: Customer Center 310: Shared File System 320: Backup-Home Location Register

In order to achieve the above object, the subscriber data backup method provided by the present invention is based on a first process of classifying a change type when a subscriber data is changed in a home location register and a classification result of the first process. After generating the backup data according to the second file to be stored in the shared file system, the backup data has a file name that can identify the type of change, and the backup management unit of the backup-home location register for the shared file A third step of reading the backup data from the system and reading the change type of the backup data based on the filename of the backup data; and the backup management unit of the backup-home location register based on the reading result of the third step. The fourth process of changing the subscriber data stored in the backup-home location register, and the change of the subscriber data of the backup-home location register in the fourth process When complete, the public, characterized in that it comprises a fifth step of deleting the backup data stored in the shared file system to a change in the subscriber data.

Hereinafter, a preferred embodiment of the subscriber data backup method of the home location register according to the present invention will be described similarly based on the accompanying drawings.

2 is a block diagram of a home location register 220 for backing up subscriber data in accordance with one embodiment of the present invention.

Referring to Figure 2, the home location register 220, maintenance / maintenance / operation management unit 221, SS7 matching unit 222, MAP (Mobile Application Part) message processing unit 223, database management unit 224, subscriber database 225, an operator matching unit 226, a customer center matching unit 227, and a real-time backup management unit 228. At this time, the rest of the devices except the real-time backup management unit 228 are components that are commonly equipped with a typical home location register. However, the communication method between the devices may be different according to the implementation method. Meanwhile, the home location register 220 is connected to the SS7 network 210 and the LAN 230, and the operator terminal 240 through the LAN 230. ) And the customer center 250.

The maintenance / operation management unit 221 is a set of software for processing the operation / maintenance / maintenance functions of the hardware and software of the home location register 220. The home location register communicates with the remaining components in the home location register. It is in charge of the operation, maintenance, maintenance, and management of the register. To this end, the maintenance / maintenance / operation management unit 221 needs to communicate with most of the remaining components in the home location register (220). This relationship is not shown in FIG.

SS7 matching unit 222 is responsible for matching between the home location register 220 and the SS7 network (210). At this time, the 'SS7 network' refers to a mobile communication network that complies with the SS7 protocol, and the 'SS7 protocol' means communication between other mobile communication network elements (for example, mobile switching center, visitor location register, etc.) to enable communication. Say the protocol for.

The MAP message processing unit 223 analyzes the MAP message received from the SS7 matching unit 222 and transmits a corresponding response to the mobile communication network, or makes a MAP message to be transmitted to the mobile communication network, and sends it to the SS7 matching unit 222. Do this.

In addition, since the subscriber data is required to perform the function, the MAP message processing unit 223 interacts with the subscriber database 225 (eg, a database operation such as a query or a change).

On the other hand, the message generated by the MAP message processing unit 223 is for changing the information stored in the subscriber database 225, there is a location change message of the subscriber, the power state change message of the subscriber terminal, the short message related information change messages. In addition, when the subscriber requests to change the subscriber database using the function code of the terminal, the MAP message processing unit 223 generates a change message for processing the same. The MAP message processing unit 223 changes the contents of the subscriber database 225 using these change messages, and reflects the change messages generated at that time in order to reflect the changed contents to the backup-home location register. To).

The database manager 224 manages the subscriber database 225 and performs a subscriber database processing request received through the operator matching unit 226 and the customer center matching unit 227. The subscriber database processing request message is also sent to the real-time backup management unit 228.

The subscriber database 225 is a mobile identification number (MIN), a subscriber terminal number (ESN: Electronic Serial Number), and location-related data in the subscriber's mobile communication network required for the home location register to perform its function. It is a set of systematically stored information needed for service provision, such as subscriber-specific mobile phone network supplementary service information. The operator matching unit 226, the customer center matching unit 227, the real-time backup management unit 228, and the like are interworked via the database manager 224.

The operator matching unit 226 transmits the subscriber database processing instruction of the home location register operator to the database manager 224. In addition, the operator matching unit 226 also interfaces with the remaining components of the home location register to provide an interface for performing a function requested by the operator. In FIG. 2, the interworking relationship with the remaining components of the home location register except for the database manager 224 is not shown.

The customer center matching unit 227 is in charge of accessing the customer center 250 operated by the mobile communication service provider. Since the customer center 250 generally requests and updates the subscriber database 225, the customer center matching unit 227 interworks with the database management unit 224 to process this.

The real-time backup management unit 228 and the database management unit 224, MAP message processing unit 223 and subscriber database 225 and the same to apply the changes of the subscriber data stored in the subscriber database 225 to the backup-home location register It works. That is, the real-time backup management unit 228 changes the location change message of the subscriber from the MAP message processing unit 223, the power state (On / Off) change message of the subscriber terminal and the short message related information change message, and the function code of the subscriber terminal (Feature) Code, e.g. * 89, ** etc.) Receive change messages to change the information by use. In addition, the database management unit 224 receives the subscriber database processing instructions transmitted from the operator matching unit 226 and the customer center matching unit 227. This change message and processing instructions are later transferred to the backup-home location register. By doing so, the change of the subscriber database of the home location register is equally applied to the backup-home location register. This backup process will be described in more detail in the description with reference to FIG. 3.

On the other hand, the operator terminal 240 connected to the home location register 220 and the LAN 230 is a device used for the operation of a typical system, such as querying the status of the home location register, query / change of the database. Such an operator terminal 240 is generally used to work with a home location register system through a LAN using a work station class computer, but may be a dummy terminal connected through a serial port. There is also. However, this is a matter of implementation, and in the description of the present invention, it is assumed that a workstation-class computer interworks with a home location register body through a LAN.

The customer center 250 is an organization for a mobile communication service provider to receive and resolve inconveniences of its customers. The customer center 250 allows operators to operate a home location register according to a predetermined authority at a remote location. Devices are generally present in customer center 250.

3 is an explanatory diagram for explaining a subscriber data backup process of a home location register according to an embodiment of the present invention.

In FIG. 3, the home location register 220 and the backup-home location register 320 interwork with each other to back up the subscriber database in real time.

At this time, the backup data transmitted between the home location register 220 and the backup-home location register 320 refers to the change messages used by the home location register 220 to change the contents stored in the subscriber database 225. In order to transfer the data for backup, the home location register 220 and the backup-home location register 320 use a shared file system 310 shared with each other.

The shared file system 310 should be implemented such that the home location register 220 is writable and the backup-home location register 320 is readable. However, no other restrictions apply. That is, the implementation method of the shared file system 310 is not a problem. For example, it is possible to implement a shared file system in the form of a network file system (NFS) or a file server. On the other hand, when the shared file system 310 is divided into a plurality of areas by an appropriate method (for example, each service home location register is divided into a directory having a different name), a plurality of home locations using one backup-home location register is used. The subscriber database of the registrar may also be backed up. In the example of FIG. 3, the shared file system 310 is divided into n areas (area-1, area-2, ..., area-n) 311 to 313, It is implemented to store the backup data generated by the home location register 220 in the area-2 (312) of the areas. The backup process will be described in more detail with reference to FIG. 3. First, the MAP message processing unit 223 or the database management unit 224 of the home location register 220 is an SS7 matching unit, an operator matching unit, or a customer center registration unit. The subscriber data change message is received from the unit (S301). Then, the MAP message processing unit 223 or the database management unit 224 updates the subscriber database 225 based on the request (S302), generates backup data by the subscriber data change message, and generates a real time backup management unit 228. It transmits to (S303). Then, the real-time backup management unit 228 records the backup data in the predetermined area (area-2) 312 of the shared file system 310 (S304). At this time, the real-time backup management unit 228 stores the subscriber database ( According to the change type of 225, the file name of the backup data to be recorded in the shared file system 310 is specified differently. This is to allow the backup-home location register 320 to determine the type of change based on the file name and to perform appropriate processing according to the change type. On the other hand, the real-time backup management unit of the backup-home location register 320 is performed. 328 reads the backup data from the area-2 312 of the shared file system 310 (S305), and then performs a predetermined process to reflect it to the subscriber database 325 (S306). At this time, the real-time backup management unit 328 may directly change the contents of the subscriber database 325, or transfer the backup data to the database management unit 324 (S307), the database management unit 324 the contents of the subscriber database 325 You can also change it. For example, when data is changed at the request of the operator matching unit or the customer center matching unit of the home location register 220, the backup data generated at this time is passed through the database manager 324 of the backup-home location register 320. If the data is changed at the request of the home location register 220 SS7 matching unit, the backup data generated at this time does not go through the database manager 324 of the backup-home location register 320. Instead, the real time backup management unit 328 is reflected in the subscriber database 325.

4 is an explanatory diagram for explaining a method of backing up backup data of a plurality of home location registers to one backup-home location register according to an embodiment of the present invention.

Referring to FIG. 4, in order to back up the backup data generated from the plurality of home location registers 410 to 430 to one backup-home location register 450, the shared file system 440 is first divided into a plurality of areas ( Area-1 to area-n) 441 to 443. FIG. After allocating the areas 441 to 443 to each of the plurality of home location registers 410 to 430, the home location registers 410 to 430 store backup data in the allocated area. That is, the real-time backup manager 411 of the home location register-1 (410) records the backup data generated by the home location register-1 (410) in the area-1441, and the home location register-2 (420). The real time backup management unit 421 records the backup data generated by the home location register-2 (420) in the area-2 (442), and the real time backup management unit 431 of the home location register-n (430) is the home location. The backup data generated by the register-n 430 is recorded in the area-n 443. At this time, the home location registers 410 to 430 define a file name differently for each occurrence cause of the backup data and store it in the corresponding area. Then, the backup-home location register 450 may know the type of backup data based on the file name, and may identify the home location register where the file is generated based on the area in which the file is stored.

Meanwhile, the backup home location register 450 periodically monitors the areas 441 to 443 of the shared file system 440 allocated to each of the home location registers 410 to 430, and then backup data files for backup are stored. If found, the domain name on the shared file system where the backup data files were found, the file name, and the creation time of the file are used to identify and identify what type of database change the backup data file was created at which home location register. Perform the appropriate treatment.

In the above, the components for real-time backup of the home location register subscriber database have been described. The above-described components perform any operation in any order for each type of data to be backed up, thereby backing up the database of the service home location register. The following describes whether the data is backed up in the register database.

First, in a typical home location register, the subscriber database can be classified into six types: (a) creation / deletion / change of subscriber data through the operator terminal; (b) generation of subscriber data from the customer center / (C) Change of subscriber's location according to change of subscriber's location (d) Change of terminal's status according to change of subscriber's power status (e) Change of subscriber's data due to short message related status change (f) Function of subscriber's terminal Change of subscriber data by code manipulation '(a) Type' occurs when the operator changes the subscriber database using MMC (Man Machine Command). '(C)' type occurs when the subscriber moves position in the mobile network, and '(d)' type occurs when the power state of the subscriber terminal is changed. '(E)' type is generated when a new short message delivered to the subscriber is newly generated or when the mobile communication exchange (MSC) is notified that the short message can be delivered to the subscriber. Occurs when the subscriber changes the information related to his / her service stored in the subscriber register database using the feature code (eg, * 88, * 89, **, etc.) on the terminal. Looking at the characteristics of the types, '(a) type' and '(b) type' have a low frequency of occurrence, but the change of data to be made at one time is large, '(c) type', '(d) type', The '(e)' and '(f)' types are more frequent, while the data changes that need to be made at one time are less frequent. Therefore, in the present invention, the processing method is applied differently for each type. That is, in the case of type (a), whenever the backup data is found, the backup data is immediately reflected to the backup-home location register, and '( b) Type 'and' (f) 'type, the change history is stored until a certain number of changes occur, and the certain number of changes are reflected at the same time in the backup-home location register and' (c) type ' In case of '(d)' type and '(e)' type, a certain number of changes are stored in the buffer of the operating home location register, and when the change reaches a certain number or more than a certain time, The details are reflected to the backup-home location register. Referring to FIGS. 2 and 3, the backup process according to the cause of the change of the subscriber database for each type is described as follows.

First, in case of '(a) type: generation / deletion / change of subscriber data through the operator terminal', the change command is performed by “operator terminal 240 → LAN 230 → operator matching unit 226” of FIG. 2. When delivered to the database manager 224 of FIG. 2, the database manager 224 updates the subscriber database 225 based on the change command. The database manager 224 transfers the change command to the real-time backup manager 228.

Meanwhile, referring to FIG. 3, the real-time backup manager 228 notified of the change command of 'a type' from the database manager 224 shares the entire message received with the backup-home location register 320. A file is generated in a predetermined area (area-2312 in FIG. 3) of the shared file system 310. Then, the real-time backup management unit 328 of the backup-home location register 320, which was monitoring the shared file system 310, grasps that the contents contained in the file are related to the database update by the operator after the file name. Read the content of the file, and delivers it to the database management unit (324).

The database management unit 324 receiving this changes the contents of the subscriber database 325 based on the contents thereof, thereby replacing the subscriber database 325 of the backup-home location register 320 with the subscriber database of the home location register 220. 225). Finally, the file whose processing is completed by the real-time backup management unit 328 is deleted from the shared file system 310.

In the case of type (b): creation / deletion / change of subscriber data from the customer center, the change order is via the “customer center 250 → LAN 230 → customer center matching unit 227” of FIG. 2. 2, the database manager 224 updates the subscriber database 225 after analyzing the change command. At this time, if the database update command fails, the database manager 224 transitions the operation state to the reception standby state of the next command.

Meanwhile, referring to FIG. 3, the database manager 224, which has successfully processed the subscriber database change command received from the customer center, transmits the entire change command received from the customer center matching unit to the real time backup manager 228. The received real-time backup management unit 228 records the change command in a predetermined internal buffer. If the internal buffer is full or the generation time of the data stored in the internal buffer has elapsed more than the threshold time (so that the operator can change it between 1 second and 120 minutes), the internal buffer is stored until then. The entire contents are recorded in the designated area of the shared file system 310. At this time, the name of the file indicates that the change of the subscriber database by the customer center. If not, the real-time backup management unit 228 transitions to the reception standby state of the next data.

Meanwhile, the real-time backup management unit 328 of the backup-home location register 320 monitoring the shared file system 310 detects that a new file is created on the shared file system 310 and analyzes the name of the file. It is determined that the contents contained in the file are related to the change of the subscriber database due to the customer center. After reading the name of the file into its internal buffer, the file read from the shared file system 310 is deleted.

In addition, the real-time backup management unit 328 takes out the oldest of the data entries (subscriber database change related instructions) read in the buffer and transfers them to the database management unit 324. Then, the database manager 324 properly changes the subscriber database 325 based on the command and then transitions to the next command waiting state.

In the case of type (c): location data change according to the subscriber's location change, the MAP message processing unit 223 of FIG. 2 detects the situation and corresponds to the subscriber database 225 of the home location register in service. The subscriber's location information is updated in the contents of the subscriber entry.

However, the location data of the subscriber has a lot of data to be backed up when the change, while some of the data has a characteristic that depends on the point code (PC) of the MSC. 5 shows the characteristics of such position data. That is, FIG. 5 is a diagram illustrating types of backup data for each occurrence factor of backup data. Referring to FIG. 5, data to be backed up according to a change in the location of a subscriber is a subscriber identification number (MIN) and an MSC identifier in which the subscriber is located. (MSC_ID), a code indicating the manufacturer of the MSC where the subscriber is located (SMTC: SystemMyTypeCodo), MSC's Transaction Capability (TCAPA), MSC's System Capability (SCAPA: System Capability), MSC's short message processing Short Message Service (SMS), Short Message Service Address (SMSA) associated with MSC, Point Code Subsystem Pair (PC_SSN) of MSC, PC uses SS7 address of MSC (SMS_DelivertPendingFlag) to inform the subscriber that there is a short message to be delivered to the subscriber (SMS_DelivertPendingFlag), the power status (MS_Status: Mobile Station Status) to inform the power status of the terminal, etc. There is this. However, among these, MSC_ID, SMTC, TCAPA, SCAPA, SMS, SMSA and PC_SSN depend on the point code (PC) of the MSC. Therefore, as shown in FIG. 6, if the MSC's PC is used as a key in the backup-home location register and a table including MSC_ID, SMTC, TCAPA, SCAPA, SMS, SMSA, and PC_SSN is included in each entry, When changing the location data, it is possible to reduce the amount of data transferred from the running home location register to the backup-home location register. That is, in the home location register, only the MIN, PC, MS_Status and SMS_DeliveryPendingFlag, which are the key of the subscriber database, are transmitted to the backup-home location register to inform the change history of the subscriber database due to the subscriber's location change. The subscriber's location information can be read by restoring the MSC_ID, SMTC, TCAPA, SCAPA, SMS, SMSA and PC_SSN of the corresponding MSC from a table (having the structure of FIG. 6) managed internally by the PC among the received information. Make sure

As a result, when the backup of the location-related information of the subscriber with a large amount of data to be backed up, it is possible to reduce the load on the LAN to back up the data. This will be described with reference to FIG. 3.

First, when the location change of the subscriber is detected by analyzing the message received from the SS7 matching unit by the MAP message processing unit 223 of the home location register 220 in operation, the MAP message processing unit 223 places the location of the subscriber database 225. After the relevant information is changed, the changed MIN, PC, MS_Status, and SMS_DeliveryPendingFlag are transmitted to the real-time backup management unit 228.

Then, the real-time backup management unit 228 is the internal buffer is full (Full), or when the generation time of the data stored in the internal buffer exceeds the threshold time (so that the operator can change between 1 second to 120 minutes), the internal The contents of the entire buffer are recorded in the designated area of the shared file system 310. At this time, the name of the file is defined so that it can be known that the update of the subscriber database by the location data change. If not, the real-time backup management unit 228 transitions to the reception standby state of the next data.

Meanwhile, the real-time backup management unit 328 of the backup-home location register 320 monitoring the shared file system 310 detects that a new file is created on the shared file system 310 and analyzes the name of the file. After determining that the contents included in the file are related to the change of the subscriber database due to the change of the subscriber's location, the contents of the file are stored in its own buffer. In addition, the real-time backup management unit 328 reads sequentially from the oldest data among the data read into the buffer and stores all the data related to the location by using the PC included therein and the table on the backup-home location register (FIG. 6). After restoring MSC_ID, SMTC, SCAPA, TCAPA, SMS, SMSA, PC_SSN, etc., the subscriber database 325 is updated using MIN as a key. When updating of the database is finished for all entries in the buffer, the real-time backup management unit 328 deletes the file on the shared file system 310. The size of the internal buffer of the real-time backup management unit 328 mentioned above can be changed from 1 to 10000 so that an appropriate value can be used according to the amount of database change caused by the subscriber location change occurring in the mobile communication network. Therefore, it is possible to adjust the load generated during the real-time backup of the subscriber database.

In the case of the type (d): terminal state change according to the change in the power state of the subscriber station, referring to FIG. 5, the content of the MS_Status, which is an attribute of the subscriber database, is changed. Therefore, when the MAP message processing unit 223 of FIG. 3 detects a database change due to terminal power on / off, the MAP message processing unit 223 changes the subscriber database 225 and then the real time backup management unit 228. ) To MIN and MS_Status. Then, the real-time backup management unit 228 adds the received MIN and MS_Status information to the internal buffer (the size of the buffer is 1 to 10000) as its entry as an entry.

If the internal buffer is full or the generation time of the data stored in the internal buffer has elapsed more than the threshold time (so that the operator can change it between 1 second and 120 minutes), the internal buffer is stored until then. The entire contents are recorded in the designated area of the shared file system 310. At this point, the file name identifies the cause of the database change. If not, the real-time backup management unit 228 transitions to the reception standby state of the next data and ends the operation.

In the case of '(e) Type: Change of subscriber data according to a change in short message related state', an attribute of a subscriber database to be backed up to a backup-home location register as illustrated in item 3 of FIG. 5 is a subscriber. MIN and SMS_Delivery PendingFlag, which are the keys of the database, are included. Referring to FIG. 3, when a subscriber database change command of type (e) is received from the SS7 matching unit, the MAP message processing unit 223 performs a change on the short message related data of the subscriber database 225. The real time backup management unit 228 transmits the contents (MIN, SMS_DeliveryPendingFlag, etc.).

Then, the real-time backup management unit 228 stores the received information (MIN, SMS_DeliveryPending Flag) in an internal buffer managed by itself. If the internal buffer is full or the generation time of the data stored in the internal buffer has elapsed more than the threshold time (so that the operator can change it between 1 second and 120 minutes), the internal buffer is stored until then. The entire contents are recorded in the designated area of the shared file system 310. At this point, the file name identifies the cause of the database change. If not, the real-time backup management unit 228 transitions to the standby state for receiving the next data and ends the operation.

On the other hand, the real-time backup management unit 328 of the backup-home location register 320 for monitoring the shared file system 310 detects that a new file has been created on the shared file system 310, and from the name of the file After determining that it is a message change related file, the contents of the file are read into its internal buffer. The file is then deleted from the shared file system. In addition, the real-time backup management unit 328 retrieves the short message service related attributes stored in the subscriber database 325 using the MIN included in the entry as the key from the oldest entries in time order among the contents of the file read into the buffer. Change it.

Type (f): change of subscriber data by operation of a function code of a subscriber terminal is generated when a subscriber uses a feature code using a terminal. If the MAP message processing unit 223 of FIG. 3 detects the need to change the subscriber database by the function code manipulation of the subscriber terminal, the MAP message processing unit 223 changes the subscriber data stored in the subscriber database 225 of the home location register 220 in service. Then, all data used to change the database is transferred to the real-time backup management unit 228.

Then, the real-time backup management unit 228 generates a file with a name that can be identified as a database change by a function code in the allocated area on the shared file system 310 and writes the received data to the file.

On the other hand, the real-time backup management unit 328 of the backup-home location register 320, which was monitoring the creation of a new file on the shared file system, detects the creation of a new file, and the contents stored in the file are stored in the function code from the file name. Read the contents of the file after recognizing that it is related to a change in the subscriber database. Then, the file is deleted from the shared file system 310. In addition, the real-time backup management unit 328 changes the relevant portion of the subscriber database 325 by using the contents of the read file.

7 is a flowchart illustrating a method of generating a subscriber data for backup in a shared file system by a home location register according to an embodiment of the present invention.

Referring to FIG. 7, the home location register waits to receive a subscriber database change request from the outside (S501). That is, it waits for an event from the outside that can be changed in the subscriber database of the home location register. As such, external events that can be changed to the subscriber database of the home location register include changes in the relevant data due to the change of the subscriber's location, changes in the subscriber database due to the change in the terminal's power on / off status, and changes in the subscriber database related to the short service. For example, there may be a change in the subscriber database due to the customer center, a change in the subscriber database due to the operator, and a change in the subscriber database caused by the subscriber using the function code. (S502), the subscriber database is updated according to the request (S503). That is, when an event causing a change in the subscriber database is received at the home location register, the home location register performs a change in the appropriate subscriber database corresponding to each. Then, the home location register checks whether the subscriber database update operation is successful (S504). If the operation fails, the home location register returns to the database change request waiting state (S501). If the operation is successful, the home location register returns to the subscriber database of the backup-home location register. The home location register analyzes the type of the updated data (S505) and then performs processing according to the type. At this time, the type of the updated data may be of the type (a) to (f) as mentioned above. As a result of the analysis (S505), if the updated data is of type (a) or (f), the home location register directly stores the updated data in the shared file system (S510), and the updated data is (b), ( In the case of any one of c), (d) and (e), the home location register first stores the updated data in the internal buffer (S507), and the buffer is full (S508), or in the buffer. If the storage time of the oldest data among the stored data has passed the transmission threshold time (S509), the contents of the buffer are stored in the shared file system (S510). If not the buffer pool (Full), and the data stored in the buffer has not passed the transmission threshold time, the database change request wait state (S501) is also returned.

8A and 8B are flowcharts illustrating a method of backing up backup subscriber data stored in a shared file system by a backup-home location register according to an embodiment of the present invention. Referring to FIGS. 8A and 8B, backup-home The location register checks whether a new file is created in a storage area of the shared file system (S601). At this time, the storage area of the shared file system is divided into predetermined areas, and each area stores backup data of different home location registers. Therefore, the backup-home location register shows which area has been created for each area. As a result of the check (S601), if a new file exists in a predetermined area of the shared file system (S602), the file is read into the backup-home location register (S603) and the file is analyzed (S604). . That is, the home location register is identified based on the area where the file is stored, and the type of subscriber data to be backed up is analyzed based on the name of the file. If there are a number of new files in a specific area of the shared file system, the names of the files are read, the names of the files are sorted according to the order of creation, and the list is selected from the first file in the list. The file is analyzed. If the type of data stored in the file is determined based on the file analysis result, processing according to the type is performed (S605). That is, if the data stored in the file is (a) type of data (data change by the operator), the real-time backup management unit of the backup-home location register transmits the contents of the file to the database management unit (S606), and the database management unit The subscriber database is updated based on the file contents (S607). If the data stored in the file is (f) type data (data change by function code), the real-time backup manager of the backup-home location register updates the subscriber database based on the contents of the file (S608). If the data stored in the file is of any one of (b), (c), (d) and (e), as shown in FIG. 8B, after reading the contents of the file into the buffer (S609), The data is retrieved from the buffer one by one and processed. This is because backup data is not generated in real time when the home location register is created, but because the predetermined data stored in the buffer for a predetermined time is generated as backup data at one time and stored in the shared file system. The real-time backup management unit takes out one of the data stored in the buffer (S610) and checks the type of the data (S611). If the data obtained from the buffer is (b) type of data (by the customer center) Data update), the real-time backup manager transmits the contents of the buffer to the database manager (S612) so that the database manager updates the subscriber database (S613). In the case of (c) type data (subscriber location data update), (d) type data (terminal power status data update) or (e) type data (short message service related data update), the real-time backup management unit The database is directly updated (S614). This series of processes (S610 to S614) is repeatedly performed until all the data in the buffer (S615).

As described above, the present invention can be variously substituted, modified, and changed by those skilled in the art without departing from the technical spirit of the present invention. Therefore, the present invention is not limited by the above-described embodiment and the accompanying drawings.

The present invention as described above, by reducing the number of data transfer to the backup system by varying the backup method according to the cause of the change of the subscriber data can effectively reduce the load on the home location register and LAN, and also the home location register in real time By backing up the subscriber's database, even if a failure occurs in the home location register in service, the backup database can be used to provide the service to the mobile subscriber without interruption.

Specifically, the present invention efficiently compresses data to be backed up to reduce the amount of data to be transmitted, thereby preventing overloading of the LAN and system during database backup, and dramatically reducing the backup cycle of the database. It is possible to minimize the degree of inconsistency between the backed up subscriber database and the actual operating database through real-time database backup, and also to minimize the inconsistency between the subscriber database of the service home location register and the subscriber home database of the backup home location register. By minimizing the failure of the service home location register, even if you continue to provide services using the backup home location register, there is an effect that can minimize the size of customer complaints and service provider damages.

Claims (3)

A method of backing up subscriber data of a home location register in a mobile communication network, A first process of classifying the change type when the subscriber data of the home location register is changed; A second process of generating backup data according to the change type based on the classification result of the first process and storing the backup data in a shared file system, wherein the backup data has a file name for identifying the change type; , A third step of reading the backup data from the shared file system by the backup management unit of the backup-home location register, and then reading the change type of the backup data based on the file name of the backup data; A fourth process of changing, by the backup management unit of the backup-home location register, the subscriber data stored in the backup-home location register based on the reading result of the third process; And a fifth step of deleting the backup data stored in the shared file system to change the subscriber data when the subscriber data change of the backup-home location register is successfully completed in the fourth step. To backup subscriber data. The method of claim 1, wherein the first process is Subscriber data change type (A) type means the creation / deletion / change of subscriber data through the operator terminal; (B) type means the creation / deletion / change of subscriber data at the request of customer center; (C) type means change of subscriber location data according to subscriber's location change, (D) type means a change in the state of the terminal according to the change in the power state of the subscriber station; (E) type means a change of subscriber data due to a change in state related to a short message; A method of backing up subscriber data in a home location register, characterized in that it is classified into any one of the types (f), which means the change of subscriber data by the function code manipulation of the subscriber terminal. The method of claim 2, wherein the second process When the change type of subscriber data is (a) type, backup data is generated in real time whenever data change occurs. If the change type of the subscriber data is either (b) or (f), the change data is stored in the buffer of the home location register, and when the number of change data reaches a predetermined number, the change data is backed up as one. To the data, If the change type of the subscriber data is any one of (c) type, (d) type and (e) type, the change data is stored in the buffer of the home location register, and the number of the changed data reaches a predetermined number, And storing the changed data in one backup data when the generation time of the changed data has elapsed for a predetermined time or more. The backup process of the fifth step, Sequentially transferring the contents of the data file read in accordance with the analysis of the name of the data file to update the subscriber data registered in the home location register in the database of the backup system, and to delete the subscriber data whose backup process is terminated. A subscriber data backup method of a home location register.