WO2012029280A1 - Disk management method, disk management system, disk management device and memory device - Google Patents

Abstract

A disk management device being low cost and having high reliability is provided. A disk management device (100) managing memory devices (103a, 103b), into which subscriber data retrieved from a DK device (102) storing subscriber data of mobile equipment are stored, is composed of: a data usage rate managing unit (113) detecting remaining storage capacities of subscriber data memories (104a, 104b) storing subscriber data in memory devices (103a, 103b); a traffic volume managing unit (114) detecting remaining traffic volumes of the subscriber data memories (104a, 104b); and a disk managing unit (111) storing the same subscriber data as transfer source subscriber data into a memory device having a remaining storage capacity larger than the amount of subscriber data stored in the memory device (103a) and having a remaining traffic volume larger than the traffic volume of access to the transfer source subscriber data.

Description

Disk management method, disk management system, disk management device, memory device

The present invention relates to a disk management method, a disk management system, a disk management device, and a memory device for managing subscriber data of a mobile terminal device, and particularly manages subscriber data of a plurality of memory devices connected to the disk management device. The present invention relates to a disk management method, a disk management system, a disk management device, and a memory device.

Currently, in mobile communication networks, call control is performed along with management of subscriber data including user location information and contract information in an HSS (Home Subscriber Server). There is also a system having a configuration in which the HSS function is added to IPSCP (IP Service Control Point).
With the expansion of services provided by mobile communication networks and the increase in the number of subscribers, the amount of subscriber data to be held in HSS or IPSCP tends to increase. Furthermore, it is expected that information to be held as subscriber data is diversified, and the trend of increase in subscriber data amount is expected to increase more and more.

FIG. 14 is a diagram for explaining a conventional disk management system 1 for managing subscriber data. The disk management system 1 shown in FIG. 14 takes out a part of subscriber data stored in the disk device (hereinafter referred to as DK device) 2 and the DK device 2 (hereinafter also referred to as pulling up) and stores it. The memory devices 3a and 3b are configured. In the configuration shown in FIG. 14, the DK device 2 stores subscriber data of a mobile phone.

Such a configuration is made in order to respond to high-speed access by allowing the exchange 5 to frequently access subscriber data with call control. That is, the system shown in FIG. 14 stores part of the subscriber data stored in the DK device 2 in a plurality of memory devices in order to meet the demand for high-speed access to the subscriber data. Increasing access speed.

The DK device 2 stores system backup data in addition to subscriber data backup data. The subscriber data and the system backup data are stored in different areas, respectively, and the subscriber data is stored in the order along the telephone number of the mobile phone. An area where system backup data is stored is referred to as a system backup unit in the figure, and an area where subscriber data backup data is stored is referred to as a subscriber data part. In addition, a series of continuous ranges of telephone numbers is hereinafter also referred to as “number band” in this specification.

The memory devices 3a and 3b are configured similarly. For this reason, only the memory device 3a will be described here, and it will be replaced with the description of the memory device 3b. The memory device 3a includes a data pulling unit 6a for retrieving subscriber data from the DK device 2, a subscriber data memory 4a for storing subscriber data pulled by the data pulling unit 6a, and a subscription stored in the subscriber data memory 4a. A subscriber data management unit 7a for managing subscriber data and a switch 5 connected to the exchange 5 and having access to subscriber data stored in the subscriber data memory 4a when a call is generated are provided.

The data pulling unit 6a takes out the subscriber data stored in the DK device 2, and stores it in the subscriber data memory 4a. Generally, the subscriber data memory 4a stores about 500,000 pieces of subscriber data in the order of their telephone numbers. The exchange 5 maintains a list in which the memory device in which the subscriber data is stored and the telephone number are associated with each other, and specifies the memory device to be accessed from the telephone number of the mobile phone when the subscriber inquires or makes a call connection. is doing.

However, in the disk management system 1 shown in FIG. 14, when the subscriber data memory included in any of the plurality of memory devices fails, the exchange 5 cannot access the subscriber data memory, and the failed subscriber Communication with a mobile phone in which subscriber data is stored in the data memory is hindered. In order to prevent such a situation, in the conventional disk management system 1, as shown in FIG. 15, an operating unit and a spare unit are provided for the disk management system 1, and the exchange 5 stores the subscriber data memory in which a failure has occurred. The memory device 3a communicates with a memory device 3a ′ which is a spare device of the memory device 3a instead of the memory device 3a. Note that the spare machine in FIG. 15 is configured in the same manner as the operating machine. For this reason, in FIG. 15, each component included in the spare machine is indicated by adding “′” to the reference numeral of the corresponding component in the operating machine, and the description thereof is omitted.
Such a system is described in Non-Patent Document 1, for example.

However, the configuration shown in FIG. 15 has a problem that the hardware configuration of the memory device has to be provided in all two (hardware duplication), and the cost of the hardware increases. Further, in the configuration shown in FIG. 15, since it is necessary to synchronize data between the duplicated memory devices, there is a problem that the cost of the disk management system is increased by adding software for executing synchronization. there were.

The present invention has been made in view of such a point, and even when the memory part of the memory device fails without duplication of hardware, the subscriber stored in the failed memory part An object of the present invention is to provide a disk management method, a disk management system, a disk management device, and a memory device that can access data and that are low in cost and highly reliable.

In order to solve the above problems, a disk management system according to an aspect of the present invention is a disk device (for example, the DK device 102 shown in FIG. 1) in which subscriber data including information used for communication of a mobile device is stored. A plurality of memory devices in which the subscriber data is distributed and stored (for example, the memory devices 103a and 103b shown in FIG. 1), and a disk management device for managing the subscriber data stored in the memory device ( For example, a disk management system including a disk management system 100 shown in FIG. 1, wherein the disk management apparatus is a storage area (for example, shown in FIG. 1) used for storing the subscriber data in the memory device. In the subscriber data memory 104a, 104b), a remaining storage capacity that is a capacity of a storage area that can further store the subscriber data is detected. A memory remaining capacity detecting unit (for example, the data usage rate managing unit 113 shown in FIG. 1) and a traffic remaining capacity detecting unit for detecting a traffic remaining capacity that is allowed to increase with respect to access to the storage area ( For example, the traffic volume management unit 114) shown in FIG. 1 and access to the storage area having the remaining storage capacity equal to or greater than the data amount of the migration source subscriber data and storing the migration source subscriber data. A disk management unit that acquires and stores the same subscriber data as the source subscriber data from the disk device in the memory device having the storage area having the remaining traffic capacity equal to or greater than the traffic amount (for example, FIG. 1), and a disk management unit 111) shown in FIG.

In the disk management system according to one aspect of the present invention, in the above-described invention, at least a part of the plurality of memory devices is the source memory while the subscriber data is stored in the destination memory device. A differential data management unit (for example, the differential data management units 109a and 109b shown in FIG. 1) that stores differential data that is stored and updated by the requested access to the apparatus; Preferably, after the same subscriber data as the migration source subscriber data is stored in the migration destination memory device, the difference data is transferred to the migration destination memory device.

A disk management device according to an aspect of the present invention manages a disk device in which subscriber data including information used for communication of a mobile device is stored, and the subscriber data is distributed and stored in a plurality of memory devices. A memory management remaining capacity detection for detecting a remaining storage capacity, which is a capacity of a storage area that can further store the subscriber data, in a storage area used for storing the subscriber data in the memory device. A traffic remaining capacity detecting unit that detects a traffic remaining capacity that is an increase in traffic allowed for access to the storage area, and a migration source memory device that is one of the plurality of memory devices. The same subscriber data as the migration source subscriber data being transferred is transferred to another memory device that is another one of the memory devices. In the case of storing, the remaining storage capacity equal to or larger than the data amount of the migration source subscriber data and the remaining traffic capacity equal to or greater than the traffic volume of access to the storage area in which the migration source subscriber data is stored. The memory device having the storage area has a disk management unit that acquires and stores the same subscriber data as the migration source subscriber data from the disk device.

The disk management device according to an aspect of the present invention is the disk management device according to the above-described invention, wherein the subscriber data is divided and stored in a use area obtained by dividing the storage area of the memory device, and the memory storage remainder is stored. A capacity detection unit detects the remaining storage capacity for each used area, the remaining traffic capacity detection unit detects a remaining traffic capacity for each used area, and the disk management unit is stored in the used area. The remaining storage capacity equal to or greater than the data amount of the migration source subscriber data, and the remaining traffic capacity equal to or greater than the traffic volume of access to the migration source subscriber data stored in the use area. Acquiring and storing the same subscriber data as the source subscriber data from the disk device in the memory device having the use area; Masui.

A memory device according to an aspect of the present invention is a memory device in which a part of subscriber data including information used for communication of a mobile device stored in a disk device is stored (for example, the memory device 103a shown in FIG. 1). 103b), wherein the subscriber data stored in the disk device is distributed and stored in a plurality of memory devices, and stored in a source memory device which is one of the plurality of memory devices. When the same subscriber data as the migration source subscriber data is stored in the migration destination memory device which is another one of the plurality of memory devices, the subscriber data is stored in the migration destination memory device. The difference data management unit (for example, the difference data shown in FIG. 1) stores difference data that is data updated by the requested access to the migration source memory device. Data management unit 109a, 109b) wherein the difference data management unit is characterized by transferring the difference data to the differential data management unit of the target memory device.

A disk management method according to an aspect of the present invention manages a disk device in which subscriber data including information used for communication of a mobile device is stored, and the subscriber data is distributed and stored in a plurality of memory devices. In the disk management method, a remaining traffic capacity detecting step for detecting a remaining traffic capacity, which is a traffic volume allowed to increase with respect to access to a storage area used for storing the subscriber data in the memory device (for example, FIG. Step S804) shown in FIG. 8 and a memory remaining capacity detecting step for detecting a remaining storage capacity that is a capacity of the storage area that can further store the subscriber data (for example, Step S805 shown in FIG. 8). And a migration source stored in a migration source memory device that is one of the plurality of memory devices When the same subscriber data as the entry data is stored in the migration destination memory device which is another one of the plurality of memory devices, access to the storage area in which the migration source subscriber data is stored The subscriber data that is the same as the source subscriber data is stored in the memory device having the remaining traffic capacity that is equal to or greater than the traffic amount and the remaining memory capacity that is equal to or greater than the data amount of the source subscriber data. Including a subscriber data pull-up instruction step (for example, steps S712 and S713 shown in FIG. 7).

According to the above-described invention, the same subscriber data as the subscriber data stored in the migration source memory device can be stored in the migration destination memory device, so that the subscriber data memory of the migration source memory device has a failure or the like. Even when this occurs, the memory device can be continuously accessed using the migration destination memory device. Therefore, high reliability of the disk management system can be obtained without duplicating the memory device. At this time, in order to consider not only the amount of subscriber data and the memory capacity of the memory for recording the subscriber data of the memory device, but also the traffic capacity of the memory, a more suitable memory device as the destination memory device is selected. It is possible to smoothly continue the communication processing even after the subscriber data is selected and the subscriber data is pulled up in the migration destination memory device.

In addition, according to the above-described invention, since the subscriber data is stored in a smaller use area, the same subscriber data stored in the migration source memory device is stored in another migration destination memory device. It can be distributed and stored. For this reason, options for selecting the migration destination memory device are increased, and the migration destination memory device can be easily selected.
According to the above-described invention, since the difference data can be transferred from the migration source memory device to the migration destination memory device, the information updated in the migration source memory device is reflected in the migration destination memory device while the subscriber data is being pulled up. be able to.

It is a figure for demonstrating the disk management system of Embodiment 1 of this invention. It is a figure for demonstrating the process of raising the subscriber data of Embodiment 1 of this invention. It is a figure for demonstrating the disk management system provided with the front end apparatus of Embodiment 1 of this invention. It is the figure which showed concretely the memory device management table | surface with which the disk management apparatus of Embodiment 1 of this invention is provided. It is the figure which illustrated allocation of the telephone number with respect to the use area | region of Embodiment 1 of this invention. It is a figure for demonstrating the specific method of managing the traffic amount of the data management system of Embodiment 1 of this invention. It is a flowchart for demonstrating the operation | movement which concerns on raising of the subscriber data of Embodiment 1 of this invention. FIG. 8 is a diagram for more specifically explaining the allocation determination process using the traffic volume in the allocation determination step shown in FIG. 7. It is a figure for demonstrating the procedure of the transfer of the difference data of Embodiment 1 of this invention. It is a figure for demonstrating the procedure which switches the transfer origin memory device of Embodiment 1 of this invention to a transfer destination memory device. It is a figure for demonstrating the effect acquired by Embodiment 1 of this invention. It is a figure for demonstrating the disk management system of Embodiment 2 of this invention. It is a figure for demonstrating the other structural example of the disk management system of Embodiment 2 of this invention. It is a figure for demonstrating the conventional disk management system. It is a figure for demonstrating the subject of the conventional disk management system.

Embodiments 1 and 2 of a disk management method, a disk management system, a disk management device, and a memory device according to the present invention will be described below with reference to the drawings. In the first and second embodiments, when the memory portion in which the subscriber data is stored fails, the amount of subscriber data stored in each of the plurality of memory devices and the traffic load are leveled. Can be applied.

In the first and second embodiments described below, the disk of the present invention is mainly applied when a failure occurs in a subscriber data memory included in a memory device and access to the subscriber data becomes impossible. A management method, a disk management system, a disk management device, and a memory device will be described.

Embodiment 1
(Disk management system configuration)
FIG. 1 is a diagram for explaining a disk management system according to the first embodiment of the present invention, and shows a disk management system including the disk management apparatus 100 according to the first embodiment. The first embodiment will be described on the assumption that the disk management device 100 manages the disk device that stores the subscriber data of the mobile phone and controls the allocation of the subscriber data stored in the disk device to the memory device. The subscriber data is data including a telephone number and an e-mail address used for communication of the mobile phone, and contract information (type of service provided to the user, fee system, etc.). In the present specification, allocation refers to processing for determining a storage area of a subscriber data memory of a memory device in which subscriber data is stored.

The illustrated disk management system includes a disk device (hereinafter referred to as a DK device) 102, a plurality of memory devices 103a and 103b, and a disk management device 100. The DK device 102 has a large-scale memory, and in this memory, a system backup unit 101 that stores backup data of system data related to the operation of the DK device 102, a subscriber that stores subscriber data. There are data parts 110a, 110b.

1 shows only two memory devices 103a and 103b as a plurality of memory devices, but more memory devices may be included. Such a disk management system generally includes a larger number of memory devices. In the allocation of subscriber data described later, it is assumed that memory devices other than the memory devices 103a and 103b are also included in the disk management system. I am explaining.

The subscriber data sections 110a and 110b are memories, and the memory area is divided in advance. The subdivided subscriber data is stored in each of the divided relatively small areas. The subscriber data D1.1, D1.2, D1.3, D2.1, D2.2, and D2.3 shown in the figure subdivide the entire subscriber data stored in the subscriber data sections 110a and 110b. This is subscriber data with a relatively small amount of data. In the first embodiment, the subscriber data sections 110a and 110b are subdivided to facilitate assignment of subscriber data to be described later.

The memory device 103a includes a subscriber data memory 104a for storing subscriber data, a data pulling unit 106a for extracting subscriber data from the subscriber data units 110a and 110b of the DK device 102 and storing the subscriber data in the subscriber data memory 104a, A subscriber data management unit 107a that manages subscriber data stored in the subscriber data memory 104a, a call control unit 108a that controls access to the subscriber data memory 104a in response to access by an exchange (not shown), and other memory devices A difference data management unit 109a is provided for managing newly stored and updated data in response to an access request made to the memory device 103a while the subscriber data is being pulled up. In this specification, the operation of taking out subscriber data from the subscriber data unit 110 of the DK apparatus 102 and storing it in the subscriber data memory is referred to as “pull-up”.

The memory device 103b is configured in substantially the same manner as the memory device 103a, and extracts subscriber data from the subscriber data memory 104b for storing subscriber data and the subscriber data sections 110a and 110b of the DK device 102. The data pulling unit 106b stored in the subscriber data memory 104b, the subscriber data management unit 107b for managing the subscriber data stored in the subscriber data memory 104b, and the subscriber data memory in response to an access request by an exchange not shown. The call control unit 108b that controls access to the memory device 104b, while the subscriber data is being pulled up in another memory device, newly stored and updated data (hereinafter, referred to as an access request made to the memory device 103b) A differential data management unit 109b for managing differential data) To have.

However, the storage capacity and traffic capacity of the subscriber data memories 104a and 104b may be different from each other or may be equal to each other. In the first embodiment, the data pulling unit 106a extracts the subscriber data D1.1, D1.2, D1.3 from the subscriber data unit 110a and stores it in the subscriber data memory 104a. The data pulling unit 106b takes out subscriber data D2.1, D2.2, and D2.3 from the subscriber data unit 110b and stores them in the subscriber data memory 104b. Therefore, as shown in FIG. 1, the subscriber data memory 104a stores the subscriber data D1.1, D1.2, D1.3, and the subscriber data memory 104b stores the subscriber data D2.1, D2.2 and D2.3 are stored.

The call controllers 108a and 108b receive a signal requesting reading of subscriber data. Then, the subscriber data management unit 107a or the subscriber data management unit 107b is requested to read out the requested subscriber data.
The subscriber data management units 107a and 107b hold information related to the address of the subscriber data in the subscriber data memories 104a and 104b, and the subscriber data in response to a request from the call control unit 108a or the call control unit 108b. Access the subscriber data in the memories 104a, 104b. In the first embodiment, it is assumed that the subscriber data management units 107a and 107b measure and manage the number of accesses to the subscriber data, the traffic volume, and the like. The traffic amount in the first embodiment refers to the number of signals processed per unit time by the subscriber data management units 107a and 107b.

Note that the maximum number of times per unit time that the subscriber data memories 104a and 104b can be accessed is determined by the maximum traffic volume that can be processed by the subscriber data management units 107a and 107b. In the first embodiment, the maximum traffic volume that can be processed by the subscriber data management units 107a and 107b is referred to as traffic capacity. In addition, the traffic capacity of the subscriber data management unit 107a is also referred to as the traffic capacity of the subscriber data memory 104a accessed by the subscriber data management unit 107a. In addition, the traffic capacity of the subscriber data management unit 107b is also referred to as the traffic capacity of the subscriber data memory 104b accessed by the subscriber data management unit 107b.

The difference data management units 109a and 109b are updated by an access request made to the memory devices 103a and 103b during the failure of the subscriber data memories 104a and 104b (while subscriber data is being pulled up in other memory devices). In this configuration, the difference data stored and updated is managed.

The difference data is data newly stored in the subscriber data memories 104a and 104b or deleted from the subscriber data memories 104a and 104b if no failure occurs. Since such difference data is not stored in the subscriber data memories 104a and 104b or deleted from the subscriber data memories 104a and 104b during the failure of the subscriber data memories 104a and 104b, the difference data management units 109a and 109b The difference data is stored in place of the subscriber data memories 104a and 104b, and the stored difference data is updated as necessary.
The difference data management units 109a and 109b include a memory for temporarily storing the difference data and a function for writing the stored difference data to the corresponding subscriber data memory 104a or the subscriber data memory 104b.

The disk management device 100 includes a disk management unit 111, a failure monitoring unit 112, a data usage rate management unit 113, and a traffic volume management unit 114. The failure monitoring unit 112 monitors the memory devices 103a and 103b and detects the occurrence of a failure in the subscriber data memories 104a and 104b. The data usage rate management unit 113 monitors the amount of subscriber data stored in the subscriber data memories 104a and 104b of the memory devices 103a and 103b. The data usage rate management unit 113 calculates and holds subscriber data amounts that can be further stored in the subscriber data memories 104a and 104b. In the first embodiment, the amount of subscriber data that can be stored in the subscriber data memory 104a is described as the remaining storage capacity of the subscriber data memory 104a. Further, the amount of subscriber data that can be stored in the subscriber data memory 104b is described as the remaining storage capacity of the subscriber data memory 104b.

The traffic volume management unit 114 manages the usage status of traffic (represented by the number of signal processes (unit TPS)) in the subscriber data memories 104a and 104b. The subscriber data memories 104a and 104b calculate and hold the number of signal processes that can be further processed. In the first embodiment, the subscriber data management unit 107a determines the number of signal processings that can be further processed, the remaining traffic capacity of the subscriber data memory 104a, and the subscriber data management unit 107b determines the number of signal processings that can be further processed by the subscriber data. This is referred to as the remaining traffic capacity of the memory 104b.

The disk management unit 111 collects data stored in the subscriber data management units 107a and 107b of the memory devices 103a and 103b (hereinafter referred to as management data) and stores the data in the subscriber data memories 104a and 104b. Know subscriber data. Further, the data usage rate management unit 113 periodically receives management data notifications from the subscriber data management units 107a and 107b to grasp the data amount of the subscriber data, and the traffic volume management unit 114 receives the subscriber data management unit 107a. , 107b periodically receives management data notifications and grasps the traffic volume of subscriber data. As a result, the disk management device 100 can grasp the latest state of the memory devices 103a and 103b.

The disk management unit 111 receives the failure detected by the failure monitoring unit 112, the remaining storage capacity calculated by the data usage rate management unit 113, and the remaining traffic capacity calculated by the traffic amount management unit 114 from the DK device 102. Is instructed to the data pulling units 106a and 106b. The subscriber data pulled by the data pulling units 106a and 106b is stored in the subscriber data memory 104a or 104b.

Furthermore, the memory device 103a and the memory device 103b are connected to each other and can exchange subscriber data. In the first embodiment, the difference data that is the subscriber data updated during the movement of the subscriber data is moved to the destination subscriber data memory. The movement of the difference data to the subscriber data memory is performed by an instruction from the disk management unit 111 to the difference data management unit 109a and the difference data management unit 109b.

(Subscriber data withdrawal process)
FIG. 2 is a diagram for explaining the process of pulling up subscriber data. In the example shown in FIG. 2, a failure occurs in the subscriber data memory 104a of the memory device 103a, and access to the subscriber data D1.1, D1.2, D1.3 stored in the subscriber data memory 104a. It is assumed that it is not possible to In such a case, the failure monitoring unit 112 detects a failure in the subscriber data memory 104a and notifies the disk management unit 111 of the failure in the subscriber data memory 104a.

From the management data, the disk management unit 111 knows that D1.1, D1.2, and D1.3 are stored in the subscriber data memory 104a of the memory device 103a and the data amount. Further, the disk management unit 111 obtains the remaining traffic capacity of the subscriber data memory of the other memory device (including the memory device 103b) from the data usage rate management unit 113 from the traffic amount management unit 114.

Then, part or all of the subscriber data D1.1, D1.2, D1.3 stored in the subscriber data memory 104a is transferred from the DK device 102 to the subscriber data memory 104b of the memory device 103b. Judge whether it can be raised. The determination is made that the data amount of some or all of the subscriber data D1.1, D1.2, D1.3 is less than the remaining storage capacity of the subscriber data memory 104b, and the subscriber data D1. This is performed depending on whether or not the traffic volume of some or all of the data of 1, D1.2 and D1.3 is less than or equal to the remaining traffic capacity of the subscriber data memory 104b.

In the first embodiment, it is assumed that, among the subscriber data stored in the subscriber data memory 104a, it is determined that the subscriber data D1.1 can be stored in the subscriber data memory 104b. In such a case, the disk management unit 111 instructs the data pulling unit 106b to pull up the subscriber data D1.1. The data pulling unit 106b pulls the subscriber data D1.1 from the subscriber data unit 110a of the DK device 2 according to the instruction.

After the subscriber data D1.1 is pulled up, the subscriber data D1.1 is stored twice in the subscriber data memories 104a and 104b. The subscriber data D1.1 stored in the subscriber data memory 104a may be deleted after the memory device 103a is restored.

Further, the disk management unit 111 instructs the subscriber data D1.1 to be pulled up, and at the same time, the subscriber data D1.1 updated while the subscriber data D1.1 is being pulled up to the differential data management unit 109a. Instructs storage of difference data. The difference data is transferred from the difference data management unit 109a to the difference data management unit 109b after completion of the processing related to the storage of the subscriber data D1.1 in the subscriber data memory 104b (after the construction of the subscriber data D1.1). The

Further, the difference data management unit 109b writes the transferred difference data in the subscriber data memory 104b. When the writing of the difference data by the difference data management unit 109b is completed, the subscriber data management unit 107b updates the management data. In addition, the disk management unit 111 updates information related to the operation state of the subscriber data memory 104b of the memory device 103b.
In the first embodiment, the disk management system having the above-described configuration may be configured such that a front-end device is provided between the memory devices 103 a and 103 b and the exchange 105.

FIG. 3 is a diagram for explaining a disk management system having such a front-end device. 3 that are the same as those shown in FIGS. 1 and 2 are denoted by the same reference numerals, and a description thereof is partially omitted.
The front- end devices 120a and 120b include access destination management units 121a and 121b, respectively. The access destination management units 121a and 121b are configured to store a list of number bands occupied by subscriber data stored in the subscriber data memories 104a and 104b.

In the first embodiment, after the disk management unit 111 updates the information related to the operation state of the subscriber data memory 104b, the list of the access destination management unit 121b is updated. In this way, the information in the list stored in the access destination management unit 121b can be always updated. Needless to say, when the information related to the operation state of the subscriber data memory 104a is updated, the disk management unit 111 updates the list of the access destination management unit 121a.
In the first embodiment, the processing described above is performed based on a memory device management table provided in the disk management device 100.

FIG. 4 is a diagram specifically showing the memory device management table. The illustrated memory device management table is created in cooperation with each component included in the disk management device 100.
The memory device management table shows the operational status of the subscriber data memory X (whether or not it is in failure), the amount of subscriber data stored in the subscriber data memory X, and the remaining storage capacity of the subscriber data memory X (see FIG. In the “Memory amount monitoring / use area” column in the form of “data amount / remaining storage capacity”), the subscriber data traffic amount stored in the subscriber data memory X and the subscriber data memory traffic This is realized by recording and updating the remaining capacity (indicated in the form of “traffic volume / traffic remaining capacity” in the “signal amount monitoring / use area” in the figure). This recording and updating is performed by the disk management unit 111.
The storage area of the subscriber data memory is subdivided, and management by the disk management function is performed for each subdivided storage area. The subdivided storage area is referred to as “use area” in FIG.

The subscriber data referred to in the first embodiment is specifically a telephone number of a mobile phone, location information of the telephone number, contract information, and the like. Subscriber data is assigned to each band. An example of telephone number assignment is shown in FIG. The column in FIG. 5 shows the area used for the subscriber data memory, and the row shows the area for the subscriber data section. The column where the usage area of the subscriber data memory and the area of the subscriber data section intersect indicates the subscriber data stored in both the usage area of the subscriber data memory and the area of the subscriber data section. In the example shown in FIG. 5, the areas 2-1-1 to 2-1-3 in the subscriber data section 110 of the DK device 102 and the used area 1-1 set in any of the subscriber data memories are used. In addition, subscriber data relating to telephone numbers in a number band of “8190111 **” to “8190113 **” is stored. In addition, in the areas 2-2-1 to 2-2-3 in the subscriber data unit 110 and the use area 1-2 set in any of the subscriber data memories, "81190114 **" to " Subscriber data relating to telephone numbers in the number band “8190116 **” is stored.

Further, in the example shown in FIG. 5, the areas 2-x-1 to 2-x-3 in the subscriber data unit 110 and the use area 1-x set in any of the subscriber data memories are included. , Subscriber data related to telephone numbers in the number band of “819011717 **” to “8190119 **” are stored.

In the example shown in FIG. 4, it is assumed that the subscriber data memory 1-1 is out of order and the subscriber data cannot be read. Further, the capacity of the usable area of the entire subscriber data memory 1-1 is 5 Gbytes, and 4.4 Gbytes of this is the total free area.
In the first embodiment, the storage area is subdivided into a use area 2-1-1 to a use area 2-x-3, and the use areas 2-1-1 to 2-1-3 are respectively 200 Mbytes and 250 Mbytes. , 150 Mbytes of subscriber data is stored.

Due to the failure of the subscriber data memory 1-1, it is necessary to store the subscriber data stored in the use areas 2-1-1 to 3 in another subscriber data memory. The disk management unit 111 searches the remaining traffic for each used area for other subscriber data memories that are determined to be able to store subscriber data by the above-described processing. In the example shown in FIG. 4, the disk management unit 111 determines that the remaining traffic capacity of the usage area 2-1-1 of the subscriber data memory 1-x is the usage area 2-1-1 of the subscriber data memory 1-1. It is determined that it is equal to the traffic volume of the subscriber data stored in.

In addition, the disk management unit 111 has a subscription in which the remaining traffic capacity of the usage area 2-1-2 of the subscriber data memory 1-x is stored in the usage area 2-1-2 of the subscriber data memory 1-1. Is determined to be equal to the traffic volume of the user data. Further, the disk management unit 111 adds the remaining traffic in the usage area 2-1-3 of the subscriber data memory 1-2 to the usage area 2-1-3 of the subscriber data memory 1-1. Is determined to be equal to the traffic volume of the user data.

Next, the disk management unit 111 searches the remaining storage capacity of each subscriber data memory for each used area. In the example shown in FIG. 4, the disk management unit 111 converts the subscriber data stored in the usage area 2-1-1 of the subscriber data memory 1-1 into the usage of the subscriber data memory 1-x. It is determined that data can be stored in the area 2-1-1.

Further, the disk management unit 111 stores the subscriber data stored in the usage area 2-1-2 of the subscriber data memory 1-1 in the usage area 2-1-2 of the subscriber data memory 1-x. Judge that you can. Further, the disk management unit 111 stores the subscriber data stored in the usage area 2-1-3 of the subscriber data memory 1-1 in the usage area 2-1-3 of the subscriber data memory 1-2. Judge that you can.

Based on the result of the above determination, the disk management unit 111 determines the storage destination of the subscriber data stored in the use areas 2-1-1 to 2-3 of the subscriber data memory 1-1.
The “reference value” for monitoring the amount of memory or monitoring the amount of signal shown in FIG. 4 is a value applied to both the subscriber data memories 104a and 104b. That is, in the example shown in FIG. 4, the subscriber data management unit 107a notifies the disk management unit 111 when the usage amount of the entire subscriber data memory 104a reaches 4.5 Gbytes. Further, the subscriber data management unit 107b notifies the disk management unit 111 when the usage amount of the entire subscriber data memory 104b reaches 4.5 Gbytes.

Further, in the example shown in FIG. 4, the subscriber data management unit 107a notifies the disk management unit 111 when the traffic volume of the entire subscriber data memory 104a reaches 2700 TPS. The subscriber data management unit 107b notifies the disk management unit 111 when the traffic volume of the entire subscriber data memory 104b reaches 2700 TPS.

FIG. 6 is a diagram for explaining a specific method for managing the traffic volume of the data management system according to the first embodiment. In the memory devices 103a and 103b, the subscriber data management units 107a and 107b count the number of accesses to the subscriber data for each usage area of the subscriber data memories 104a and 104b. Counting is performed by specifying a mobile phone using an MSISDN (Mobile Subscriber Integrated Services Digital Digital Network Number) key and counting access traffic (traffic volume) for this mobile phone number every second ( p1).

Further, the subscriber data management units 107a and 107b notify the disk management device 100 of the traffic volume at a constant cycle (p2). In the example shown in FIG. 6, the traffic volume in the usage area 2-1-1 of the subscriber data section is 1000 TPS, the traffic volume in the usage area 2-1-2 of the subscriber data section is 500 TPS, and the usage of the subscriber data section. The traffic amount in the area 2-1-3 is 900 TPS. The notification period is preferably about 15 seconds, for example.

In the example shown in FIG. 6, subscriber data in the A number band is stored in the use area 2-1-1 of the subscriber data section (p3), and the use area 2-1-2 of the subscriber data section is stored. The subscriber data of the B number band is stored in (p4), and the subscriber data of the C number band is stored in the use area 2-1-3 of the subscriber data section (p5).

In the disk management apparatus 100, the traffic volume management unit 114 manages the maximum traffic volume of the subscriber data memories 104a and 104b for each used area. For example, the maximum traffic amount in the use area 2-1-1 is set to 3000 TPS (p6). In the subscriber data management units 107a and 107b, the traffic volume management unit 114 reflects the traffic volume notified from the subscriber data management units 107a and 107b in the memory device management table shown in FIG. 4 (p7). The traffic volume notified from the subscriber data management units 107a and 107b is recorded in the corresponding column as the current traffic volume in each used area.

The traffic volume management units 114a and 114b calculate the remaining traffic capacity by subtracting the corresponding recorded traffic volume from the maximum traffic volume of the subscriber data memories 104a and 104b for each usage area (p8). The calculated remaining traffic capacity is recorded in the corresponding column as the current remaining traffic capacity in each used area.

In the example shown in FIG. 6, when notified that the traffic volume in the use area 2-1-1 is 1000 TPS, the traffic volume management unit 114 subtracts the traffic volume 1000 TPS notified from the maximum traffic volume 3000 TPS. The remaining traffic capacity 2000 TPS is calculated. The calculated remaining traffic capacity is recorded in the corresponding column of the memory management device table shown in FIG.

(Operation)
(A) Pull-up of subscriber data FIG. 7 is a flowchart for explaining an operation related to pull-up of subscriber data in the disk management apparatus 100 according to the first embodiment having the above-described configuration. The data usage rate management unit 113 of the disk management device 100 periodically receives notification of the memory usage rate (stored data amount) from the memory devices 103a and 103b. The traffic volume management unit 114 periodically receives traffic volume notifications from the memory devices 103a and 103b. Further, when a failure occurs in the subscriber data memories 104a and 104b, the subscriber data management units 107a and 107b notify the failure monitoring unit 112, so that the failure monitoring unit 112 indicates the operation state of the memory devices 103a and 103b. Receiving information.

The failure monitoring unit 112 constantly monitors for failures in the subscriber data memories 104a and 104b (step S701). The monitoring is performed by determining whether or not information indicating the occurrence of a failure is included in the information related to the operation state of the subscriber data memories 104a and 104b transmitted from the subscriber data management units 107a and 107b. Done.

The data usage rate management unit 113 monitors the data amount stored in the subscriber data memories 104a and 104b (step S702), and the traffic amount management unit 114 monitors the traffic amount of the subscriber data memories 104a and 104b. (Step S703). The disk management unit 111 includes the failure monitoring unit 112, the data usage rate management unit 113, the traffic volume management unit 114, the operation status of the subscriber data memories 104a and 104b, the amount of data stored for each usage region, and the usage amount for each usage region. The traffic volume is collected (step S704). Then, the memory management table shown in FIG. 4 is created and updated based on the collected information, or the storage remaining capacity and traffic remaining capacity for each used area calculated using the collected information (step S705). .

When the failure monitoring unit 112 detects a failure in the subscriber data memories 104a and 104b (step S706), the data usage rate management unit 113 detects an over-reference value of the data amount stored in the subscriber data memories 104a and 104b. If the traffic volume management unit 114 detects that the traffic volume reference value of the subscriber data memories 104a and 104b exceeds the reference value (step S708), the detection information is input to the disk management unit 111 (step S707). S709).

When the disk management unit 111 detects a failure or the amount of data stored in the subscriber data memories 104a and 104b or the amount of traffic exceeds the reference value, the disk management unit 111 stores the failure in the subscriber data memory in which the failure or the reference value has exceeded. Subscriber data similar to the stored subscriber data is pulled into the other subscriber data memory. Prior to such processing, the disk management unit 111 determines to which usage area of which memory device the subscriber data is to be pulled up. In the first embodiment, this determination is referred to as “assignment determination” (step S710).

After the assignment determination is completed (step S711), the disk management unit 111 determines the subscriber data to the subscriber data memory of another memory device different from the memory device in which a failure or the like has occurred from the DK device 102 based on the result of the assignment determination. To the data pulling unit of the subscriber data memory in which a failure or the like has occurred (step S712). When the subscriber data pull-up is completed (step S713), the operation related to the subscriber data pull-up shown in the flowchart of FIG. 7 is completed.

(B) Allocation of subscriber data FIG. 8 is a diagram for more specifically explaining the allocation determination process using the traffic volume in the allocation determination of step S704 in FIG. In the allocation determination process shown in FIG. 8, an example will be described that is executed when a failure is detected in any of the subscriber data memories.

The disk management unit 111 determines whether a failure has occurred (step S801). If it is determined that a failure has been detected (step S801: Yes), the subscriber data stored in (assigned to) the subscriber data memory in which the failure has been detected is confirmed for each usage region ( Step S802). Further, the disk management unit 111 extracts the subscriber data of the DK device 102 in which the fragmented subscriber data stored in the use area is stored (step S803).

Next, the disk management unit 111 sorts the used area of the subscriber data memory where the failure has occurred according to the amount of traffic for each used area. FIG. 8A is a diagram showing the order of the used areas before and after sorting. Further, the disk management unit 111 calculates the remaining traffic capacity by subtracting the traffic volume for each usage area from the maximum traffic volume for each usage area for another subscriber data memory different from the subscriber data memory in which the failure has occurred. . Then, the used area of the subscriber data memory is sorted from the one with the large calculated traffic remaining capacity. FIG. 8B is a diagram showing the order of the used areas before and after sorting.

Further, the disk management unit 111 allocates the traffic volume of the usage area of the subscriber data memory where the failure has occurred to the usage area of the other subscriber data memory. In this allocation, the traffic volume of the subscriber data memory in which a failure has occurred is allocated in order from the largest to the use area where the remaining storage capacity of the other subscriber data memory is large. FIG. 8 (3) is a diagram showing the allocation of the subscriber data to the use area.
Next, in the first embodiment, the remaining traffic capacity is recalculated when the traffic volume is allocated to the use area. If there is further subscriber data to be allocated, the processes of FIGS. 8 (3) and (4) are repeated until there is no subscriber data to be allocated.

(C) Transfer of Difference Data FIG. 9 is a diagram for explaining a procedure for transferring difference data performed between the disk management device 100 and the memory devices 103a and 103b. After the allocation determination is completed (step S31), the disk management unit 111 of the disk management device 100 performs difference data of a memory device (memory device 103a, hereinafter also referred to as a migration source memory device) having a subscriber data memory in which a failure has occurred. The management unit 109a holds difference data between subscriber data that is the same as the subscriber data that is withdrawn from the DK device 102 to another memory device, and subscriber data that is updated during the data withdrawal process. An instruction is given (step S35). The difference data management unit 109a holds the difference data in accordance with the instruction (step S36).

The disk management unit 111 backs up the latest subscriber data in the DK device 102 (step S32), and causes the DK device 102 to pull up the subscriber data from the DK device 102 to the data pulling unit of another memory device (step S32). Step S33). After the data pulling is completed (step S34), the disk management unit 111 instructs the subscriber data management unit 107a of the memory device 103a serving as the migration source memory device to transfer the difference data (step S37). The subscriber data management unit 107a notifies the instruction of the disk management unit 111 to the differential data management unit 109a and the subscriber data management unit 107b, and transfers the differential data to the differential data management unit 109b (step S38).

In the memory device 103b where the subscriber data is pulled up, the subscriber data management unit 107b receives a differential data transfer instruction from the subscriber data management unit 107a (step S39), and the transferred differential data is transferred to the subscriber. The difference data management unit 109b is instructed to store in the data memory 104b (step S41). The difference data management unit 109b receives the transferred difference data (step S40), and reflects the difference data by storing it in the subscriber data memory 104b. Such a process is referred to as a difference data reflection process (step S42).

(D) Switching of Memory Device FIG. 10 is a diagram for explaining a procedure for switching the migration source memory device to the migration destination memory device as an access destination to the pulled-up subscriber data. The procedure shown in FIG. 10 is performed between the disk management device 100, the memory devices 103a and 103b, and the front end device 120b. The difference data management unit 109b of the memory device 103b, which is the migration destination memory device, determines whether or not the remaining amount of difference data transferred has reached a predetermined threshold value or less (step S28).

At the timing when the remaining amount of difference data reaches the threshold value or less, the difference data management unit 109b instructs the subscriber data management unit 107b to transmit a switching notification. The subscriber data management unit 107b transmits a switching notification to the subscriber data management unit 107a to the memory device 103a that is the migration source memory device in accordance with the instruction (step S27).

The subscriber data management unit 107a that has received the switching notification transmits a switching notification to the disk management unit 111 (step S22). Upon receiving the switching notification (step S21), the disk management unit 111 transfers data indicating that the subscriber data stored in the memory device 103a has been transferred to the memory device 103b to the front- end devices 120a and 120b. Therefore, an instruction is given to prepare for data buffering (step S24). After the instruction, data indicating that the subscriber data stored in the memory device 103a has been transferred to the memory device 103b is transferred to the front- end devices 120a and 120b.

Also, the disk management unit 111 instructs the subscriber data management unit 107a to stop transferring the final call display (step S23). The access destination management units 121a and 121b are instructed to switch access destinations so as to make an access request for the subscriber data stored in the memory device 103a to the migration destination memory device (step S25).

The difference data management unit 109b confirms the final call of the transferred difference data (step S29). The completion of the transfer of difference data is detected by confirmation of the final call. The disk management unit 111 receives the notification of the completion of the differential data transfer, and instructs the access destination management unit 121b to rewrite the memory in which the list is stored (step S26). In response to the instruction, the access destination management unit 121b rewrites the memory in which the list of subscriber data stored in the subscriber data memory 104b is stored.

The rewriting of the memory is reflected in the memory device management table shown in FIG. 4 managed by the subscriber data management unit 107b (step S30).
FIG. 11 is a diagram for explaining an effect obtained by the first embodiment described above in consideration of not only the remaining storage capacity of the subscriber data memory but also the remaining traffic capacity. The memory device generally stores subscriber data in units based on the number band. When there are a plurality of such memory devices, when the stored subscriber data is pulled up to another memory device, it seems to be sufficient to compare the data amount with the remaining memory capacity of the other memory device. It is.

However, as shown in FIG. 11, since the number of subscriber data to be managed by one switch is smaller than that in the Tokyo metropolitan area, the accommodation area is set wider as shown in FIG. For this reason, location registration is less frequent in rural areas than in the Tokyo metropolitan area, and there is a tendency for the amount of traffic to the memory storing subscriber data to be small. Conversely, in areas such as the Tokyo metropolitan area where there are many mobile phones to be managed by the exchange, the location area is frequently registered because the accommodation area is small.

Thus, the traffic volume of subscriber data can vary greatly depending on conditions such as the area where the mobile phone is used. The first embodiment has been made paying attention to such points, and not only the storage capacity of a memory device used for storing subscriber data but also the amount of traffic in consideration of other traffic data. It is assigned to the memory device.
According to the first embodiment, when a failure occurs or subscriber data is leveled, a more suitable memory device or subscriber data memory can be selected as a destination of the subscriber data.

Further, in the first embodiment described above, when a failure occurs in any of the subscriber data memories of a plurality of memory devices, a difference that is originally updated by an access made to the subscriber data memory in which the failure has occurred. The data is stored by the differential data management unit and transferred after the subscriber data is transferred. Then, after the transfer is completed, the subscriber data stored in the failed subscriber data memory is maintained without stopping the communication service even when the subscriber data memory fails by switching the memory device to be accessed by the exchange. Can be accessed.

The first embodiment is particularly effective for a system related to communication in which service stoppage is not permitted due to server maintenance or the like.
The disk management system, disk management device, memory device, and disk management method of the first embodiment are not limited to the configuration described above. That is, the first embodiment described above describes the case where the memory device has failed. However, the first embodiment is not limited to the one applied when the subscriber data memory included in the memory device fails, but when the data amount and traffic amount of the subscriber data are leveled between the plurality of memory devices. Can also be applied.

When the first embodiment is applied to leveling of the amount of subscriber data and the amount of traffic, for example, the disk management device calculates the average value of the amount of subscriber data and the amount of traffic stored in a plurality of memory devices. The subscriber data allocation determination may be started when the data amount or traffic of the subscriber data stored in each memory device reaches an average value.

Embodiment 2
Next, Embodiment 2 of the present invention will be described. The second embodiment differs from the first embodiment in that the disk management device is provided in each of the memory devices, whereas the disk management device that controls the plurality of memory devices is controlled in the first embodiment. To do.
FIG. 12 is a diagram for explaining the disk management system according to the second embodiment. In the second embodiment, the components described with reference to the drawings described in the first embodiment are denoted by the same reference numerals as those in the first embodiment, and the description thereof is partially omitted.

The disk management system according to the second embodiment is provided inside the memory devices 123a and 123b. The disk management device provided in the memory device 123a includes a disk management unit 111a, a failure monitoring unit 112a, a data usage rate management unit 113a, and a traffic volume management unit 114a. The disk management device provided in the memory device 123b includes a disk management unit 111b, a failure monitoring unit 112b, a data usage rate management unit 113b, and a traffic volume management unit 114b.

The disk management units 111a and 111b cooperate with the disk management unit of another memory device to determine a migration destination memory device for subscriber data stored in the memory device 123a. The failure monitoring units 112a and 112b detect a failure in the subscriber data memory of the corresponding memory device. The data usage rate management units 113a and 113b detect the amount of subscriber data stored in the corresponding memory device. The traffic volume management units 114a and 114b detect the traffic volume for the subscriber data memory of the corresponding memory device. The disk management units 111a and 111b calculate the remaining storage capacity and traffic remaining capacity of the subscriber data using the detected data volume and traffic volume.

Also in the second embodiment, similarly to the first embodiment, a front end device including an access destination management unit can be provided. FIG. 13 shows a configuration in which a front-end device is provided in the disk management system of the second embodiment.

The present invention relates to any system as long as it is a system that manages allocation of subscriber data in a memory device in which subscriber data stored in a disk device related to a communication system of a mobile device is distributed and stored. Can also be applied.

DESCRIPTION OF SYMBOLS 1 Disk management system 100 Disk management apparatus 101 System backup part 102 DK apparatus 103a, 103b Memory apparatus 104a, 104b Subscriber data memory 105 Exchange 106a, 106b Data pull-up part 107a, 107b Subscriber data management part 108a, 108b Call control part 109a , 109b Differential data management unit 110a, 110b Subscriber data unit 111 Disk management unit 112 Failure monitoring unit 113 Data usage rate management unit 114 Traffic volume management unit 120a, 120b Front- end device 121a, 121b Access destination management unit

Claims (6)

1. A disk device in which subscriber data including information used for mobile communication is stored;
   A plurality of memory devices in which the subscriber data is distributed and stored;
   A disk management device for managing the subscriber data stored in the memory device;
   A disk management system including:
   The disk management device
   A memory storage remaining capacity detecting unit for detecting a storage remaining capacity that is a capacity of a storage area that can further store the subscriber data in a storage area used for storing the subscriber data in the memory device;
   For access to the storage area, a traffic remaining capacity detection unit that detects a traffic remaining capacity that is a traffic amount that is allowed to increase; and
   The same subscriber data as the migration source subscriber data stored in the migration source memory device which is one of the plurality of memory devices is transferred to the migration destination which is the other one of the plurality of memory devices. When storing in a memory device,
   The storage area having the remaining storage capacity equal to or greater than the data amount of the migration source subscriber data and having the remaining traffic capacity equal to or greater than the traffic volume of access to the storage area in which the migration source subscriber data is stored. A disk management unit for acquiring and storing the same subscriber data as the migration source subscriber data in the memory device from the disk device;
   A disk management system comprising:
2. At least some of the plurality of memory devices are
   A differential data management unit for storing differential data which is data updated by access requested to the migration source memory device while the subscriber data is stored in the migration destination memory device;
   The difference data management unit transfers the stored difference data to the migration destination memory device after the subscriber data identical to the migration source subscriber data is stored in the migration destination memory device. The disk management system according to claim 1, wherein:
3. A disk management device for managing a disk device in which subscriber data including information used for communication of a mobile device is stored, and the subscriber data is distributed and stored in a plurality of memory devices,
   A memory storage remaining capacity detecting unit for detecting a storage remaining capacity that is a capacity of a storage area that can further store the subscriber data in a storage area used for storing the subscriber data in the memory device;
   For access to the storage area, a traffic remaining capacity detection unit that detects a traffic remaining capacity that is a traffic amount that is allowed to increase; and
   The same subscriber data as the migration source subscriber data stored in the migration source memory device which is one of the plurality of memory devices is transferred to the migration destination which is the other one of the plurality of memory devices. When storing in a memory device,
   The storage area having the remaining storage capacity equal to or greater than the data amount of the migration source subscriber data and having the remaining traffic capacity equal to or greater than the traffic volume of access to the storage area in which the migration source subscriber data is stored. A disk management unit for acquiring and storing the same subscriber data as the migration source subscriber data from the disk device in the memory device having:
   A disk management apparatus comprising:
4. The subscriber data is divided and stored in a use area obtained by dividing the storage area of the memory device,
   The memory storage remaining capacity detection unit detects the storage remaining capacity for each used area,
   The traffic remaining capacity detection unit detects a traffic remaining capacity for each used area,
   The disk management unit
   The remaining storage capacity is equal to or greater than the data amount of the migration source subscriber data stored in the use area, and is equal to or greater than the traffic volume of access to the use area where the migration source subscriber data is stored. 4. The disk according to claim 3, wherein the same subscriber data as the migration source subscriber data is acquired from the disk device and stored in the memory device having the used area having the remaining traffic capacity. Management device.
5. A memory device in which a part of subscriber data including information used for communication of a mobile device stored in a disk device is stored,
   The subscriber data stored in the disk device is distributed and stored in a plurality of memory devices, and the source subscriber data stored in a source memory device that is one of the plurality of memory devices. And storing the same subscriber data in a migration destination memory device that is another one of the plurality of memory devices,
   A differential data management unit for storing differential data which is data updated by access requested to the migration source memory device while the subscriber data is stored in the migration destination memory device;
   The difference data management unit transfers the difference data to the difference data management unit of the migration destination memory device.
6. A disk management method for managing a disk device in which subscriber data including information used for communication of a mobile device is stored, and the subscriber data is distributed and stored in a plurality of memory devices,
   A traffic remaining capacity detecting step for detecting a traffic remaining capacity, which is a traffic volume allowed to increase with respect to access to a storage area used for storing the subscriber data in the memory device;
   For the storage area, a memory storage remaining capacity detecting step for detecting a storage remaining capacity that is a capacity of a storage area capable of further storing the subscriber data;
   The same subscriber data as the migration source subscriber data stored in the migration source memory device that is one of the plurality of memory devices is the migration destination that is the other one of the plurality of memory devices. When stored in a memory device,
   The storage area having the remaining traffic capacity equal to or greater than the traffic volume of access to the storage area where the migration source subscriber data is stored, and having the remaining storage capacity equal to or greater than the data volume of the migration source subscriber data A subscriber data pull-up instruction step for acquiring and storing the same subscriber data as the migration source subscriber data from the disk device in the memory device having:
   A disk management method comprising:

Images