JP4770358B2 - Data matching method for subscriber database network - Google Patents

Description

  The present invention relates to a data matching method for a subscriber database network, for example, to an improvement in a data replication method including a plurality of subscriber databases storing subscriber data and matching the stored contents of all subscriber databases.

  For example, in a telephone communication system, the contents of contracts for providing services differ depending on subscribers (for example, presence / absence of an answering machine function, presence / absence of incoming call forwarding). Therefore, the call processing server that accommodates the subscriber terminal accesses the subscriber database and confirms the subscriber data in response to a call from the subscriber terminal or a request to provide a predetermined service to the subscriber terminal. Do something like that (see data). For example, the call processing server updates the corresponding subscriber data in the subscriber database in response to a request from the subscriber terminal that performs on / off control of the incoming call transfer or answering machine function or switches the transfer destination telephone number.

  Here, in the case of a telephone communication system, in order to avoid a system down as much as possible, a plurality of subscriber databases storing the same contents are prepared. For example, multiple subscriber databases may be prepared as act-standby systems, but multiple subscriber databases are provided as act-act systems by changing the basic jurisdiction, and a certain subscriber database is in a suspended state. In some cases, another subscriber database functions in place of the subscriber database.

In any case, data replication for matching stored contents in a plurality of subscriber databases is appropriately performed. As a data replication method, a synchronous data replication method (for example, refer to Patent Document 1) in which a plurality of subscriber databases synchronize and update data almost simultaneously, and an asynchronous data replication method in which a plurality of subscriber databases update data asynchronously. There is.
JP 11-168555 A

  However, in the synchronous data replication method, when one of the subscriber databases is stopped due to failure or maintenance, in other words, when all the subscriber databases cannot be updated, the subscribers to the subscriber database in operation Renewal of data is also refused. Therefore, there is a problem that a change from a subscriber of the telephone communication service may not be accepted, and the problem is great as a telephone communication service that wants to avoid the service stop as much as possible.

  Further, in the asynchronous data replication method, subscriber data may be different in each subscriber database, and in a different state, processing may differ depending on the subscriber database accessed by the call processing server. For example, when the transfer destination telephone number is switched and only one subscriber database is updated, the transfer destination changes depending on the subscriber database accessed by the call processing server. In order to solve such an inconvenience, it is conceivable that processing for matching all subscriber databases is executed at predetermined intervals, and reference and update of all subscriber databases are prohibited during the matching period. Such a matching method is appropriate for a system in which a system stop is hardly a problem, but it is a serious problem for a telephone communication service that wants to avoid a service stop as much as possible.

  Therefore, there is a need for a data matching method for a subscriber database network that can achieve consistency in the stored contents of all subscriber databases while keeping the system outage period from recognizing service outages.

The present invention has a plurality of subscriber database systems including a subscriber data section storing subscriber data and a database server that accesses the subscriber data section in response to a request for reference or update of subscriber data. In addition, data matching of the subscriber database network having a plurality of database clients for issuing the subscriber data reference request or update request and matching the stored contents of the subscriber data portions of the respective subscriber database systems In the method, (1) each subscriber database system has a subscriber difference data section capable of storing subscriber difference data whose stored contents of the subscriber data section differ due to the suspension of other subscriber database systems. (2) When any of the above subscriber database systems is stopped, All of the subscriber database systems accept subscriber data reference requests or update requests, and perform processing to match the stored contents of the subscriber data section. At least one of the subscriber database systems In the difference data section, subscriber difference data is stored for transmission upon restart of the suspended subscriber database system, and (3) at the time of restart of any of the suspended subscriber database systems, the subscriber database system that stores subscriber difference data to the subscriber difference data unit is configured to send to the subscriber database system restart subscriber difference data, the subscriber database system restarting Except for all the above subscriber database systems, the subscriber data reference request or update request is required. And at least one of the subscriber database systems continues to store in the subscriber difference data portion, and (4) subscriber difference data. When it is judged that the remaining transmission time to the restarted subscriber database system is less than the time allowed by the network stop, all the subscriber database systems including the restarted subscriber database system (5) When all subscriber difference data is transmitted to the subscriber database system, the subscriber database system is returned to the normal state when the subscriber data reference request or update request is rejected. Features.

  According to the data matching method of the subscriber database network of the present invention, it is possible to achieve the consistency of the stored contents of all the subscriber data sections while making the system stop period not to recognize the service stop.

(A) Embodiment Hereinafter, an embodiment of a data matching method for a subscriber database network according to the present invention will be described with reference to the drawings.

(A-1) Configuration of Embodiment FIG. 1 is a block diagram showing the overall configuration of a subscriber database network to which the data matching method of this embodiment is applied.

  In FIG. 1, the subscriber database network 1 of this embodiment includes a plurality of subscriber database systems 2-1 and 2-2 (FIG. 1 shows two examples; hereinafter, described as two). A plurality of call processing servers 3-1 to 3-4 (FIG. 1 shows four examples; hereinafter described as four) can be connected via a network (N 1 to N 3). is there.

  For example, the subscriber database system 2-1 is installed in the Kanto region, and the subscriber database system 2-2 is installed in the Kansai region.

Each of the subscriber database systems 2-1 and 2-2 has the same configuration and basically operates in parallel. In order to avoid load distribution and overall system stoppage when one system stops. A plurality are provided . Each of the subscriber database systems 2-1, 2-2 has a plurality of database servers 4-11, 4-12, 4-4 (FIG. 1 shows two examples; hereinafter, described as two) 21 and 4-22 and a plurality of database servers 4-11 and 4-12 of the subscriber database system, or common disks 5-1 and 5-2 common to 4-21 and 4-22.

  Each of the common disks 5-1 and 5-2 basically corresponds to a storage unit as a subscriber database. Functionally, the subscriber data units 10-1 and 10-2 and subscriber difference data The storage areas are divided into sections 11-1 and 11-2 and one-location state sections 12-1 and 12-2. The common disks 5-1 and 5-2 are configured by hardware, for example, one or more general storage devices that are commercially available.

  Each subscriber data part 10-1, 10-2 is a part that stores subscriber data. In this embodiment, a synchronous data replication method is employed, and both subscriber data sections 10-1 and 10-2 store the same subscriber data when both systems are in operation.

  Each of the subscriber difference data units 11-1 and 11-2 temporarily stores the subscriber difference data that prevents data coincidence between the two subscriber data units 10-1 and 10-2 that has arrived while the other system is stopped. This is the part stored in The subscriber difference data stored in each of the subscriber difference data sections 11-1 and 11-2 is transferred to the other system when the other system returns from the stoppage.

Each of the one-location status units 12-1 and 12-2 stores the current status in the own subscriber database systems 2-1 and 2-2.
Depending on the current state, whether the reference or update of subscriber data is permitted, the specific contents of the update processing of subscriber data, subscriber data matching processing with other subscriber database systems, and the like are different. There are four states: “in operation”, “one location updating”, “data matching”, and “one location blocked”, and the transition between these states is a state transition table shown in FIG. 4 to be described later. As described in. The processing is different between the “data matching in progress” state on the transmission side and the “data matching in progress” state on the reception side.

The database servers 4-11 and 4-12 are provided for accessing the common disk 5-1, and the database servers 4-21 and 4-22 are provided for accessing the common disk 5-2. A plurality of subscriber database systems 2-1 and 2-2 are provided in order to avoid load distribution in the subscriber database systems 2-1 and 2-2 and to stop the entire system when one of them stops.

  Each database server 4-11, 4-12, 4-21, 4-22 is a common to which the database server 4-11, 4-12, 4-21, 4-22 belongs in response to a request from the call processing server 3 (3-1 to 3-4) as a database client. The disks 5-1 and 5-2 are accessed and returned to the call processing server 3 as necessary. Further, each database server 4-11, 4-12, 4-21, 4-22 is a process according to an instruction from a maintenance terminal (not shown) directly connected or a maintenance terminal connected via a network. Is to execute. As such a process, there is a data matching process for matching the data of both subscriber database systems 2-1 and 2-2.

  Each database server 4-11, 4-12, 4-21, 4-22 is, for example, a server having a communication function that is commercially available in hardware (for example, Intel DL580). The functions shown in the functional block diagram shown in FIG. 2 are shown by functionally organizing programs and the like installed in the server and functionally representing the database servers 4-11, 4-12, 4-21, and 4-22. Have

  In FIG. 2, each database server 4 (4-11, 4-12, 4-21, 4-22) includes a received signal analysis unit 20, a health check handling unit 21, an in-operation processing unit 22, and a one-location updating process. A unit 23, a data matching transmission unit 24, a data matching receiving unit 25, a one-location blocked processing unit 26, and the like.

  The received signal analysis unit 20 analyzes a signal arriving from the outside (call processing server or maintenance terminal) and determines the state of the subscriber database system 2 (2-1, 2-2) at that time and the received signal. A processing unit determined in accordance with the activation is started, and a received signal is delivered if necessary.

  Moreover, the received signal analysis part 20 rewrites the storage state of the one location state part 12 (12-1, 12-2), when a received signal is an instruction | indication of the state transition of the said subscriber database system 2. Is. As shown in FIG. 4, when the received signal analysis unit 20 receives a “one location update” instruction command from a maintenance terminal (not shown) in the “in operation” state, the received signal analysis unit 20 changes the state to “one location update in progress” If an “instruction for updating one location” instruction command is received in the state, an “error” is returned. When the reception signal analysis unit 20 receives the “one location update release” instruction command from the maintenance terminal in the “single location update” state, the reception signal analysis unit 20 starts the data matching transmission process and then makes a state transition to “data matching”. If a “one location update release” instruction command is received in another state, an “error” is returned. When the “data matching” error is notified from the opposing subscriber database system in the “data matching” state, the reception signal analysis unit 20 makes a transition to the “one-location updating” state.

  The health check handling unit 21 returns a reception response signal when a health check signal is given from any of the call processing servers 3 (3-1 to 3-4).

  The in-operation processing unit 22 functions when the subscriber database system 2 is in an “in operation” state. As shown in FIG. 4, when the reference request is given from any of the call processing servers 3, the in-operation processing unit 22 corresponds to the corresponding subscriber data (or the corresponding item data of the corresponding subscriber data). Is retrieved from the subscriber data section 10 (10-1, 10-2) and sent back to the call processing server 3 as the request source. Further, when an update request is given from any of the call processing servers 3, the operating processing unit 22 corresponds to the corresponding subscriber data in the subscriber data unit 10 (or corresponding item data of the corresponding subscriber data). ) And an update response is sent back to the call processing server 3 as the request source.

  When the subscriber database system (for example, 2-1) is “in operation”, the other subscriber database system (for example, 2-2) is also in “in operation”, and the update of subscriber data is performed in parallel. Executed.

  The one-location updating processing unit 23 functions when the subscriber database system 2 is in the “one-location updating” state. The processing in the case where a reference request is given from one of the call processing servers 3 to the one-location updating processing unit 23 is the same as the processing unit 22 in operation. When an update request is given from any of the call processing servers 3, the one-location updating processing unit 23 corresponds to the corresponding subscriber data (or the corresponding item data of the corresponding subscriber data) of the subscriber data unit 10. ) And an update response is returned to the call processing server 3 as the request source, and the updated subscriber data is stored in the subscriber differential data section 11 (11-1, 11-2). In the “Updating One Location” state, the other subscriber database system is shut down, so that the update is performed only by the subscriber database system.

  The data matching transmission unit 24 is activated by issuing a “one location update release” instruction command, and the subscriber differential data (11-1, 11-2) stored in the subscriber differential data unit 11 (11-1, 11-2). Subscriber data) to the other subscriber database system. The data matching transmission unit 24 operates in the same manner as the one-location updating processing unit 23 for a reference request or an update request for subscriber data given from any of the call processing servers 3 during the transmission operation. That is, reference and update are executed, and at the time of update, writing to the subscriber difference data unit 11 is also performed.

  When the remaining number of subscriber difference data that must be sent to the other subscriber database system for data matching reaches a predetermined threshold number, the data matching transmission unit 24 sets the status to “one location blocked”. And the one-location occlusion processing unit 26 is activated. Here, the predetermined threshold number is the number of times (blocking time) required for transferring the subscriber difference data corresponding to the number of cases is about one second, and the request from the call processing server 3 is changed to the both subscriber databases. Even if the systems 2-1 and 2-2 do not receive it, the number corresponds to a blocking time that cannot be regarded as a failure of the telephone communication system.

  In response to the transmission of the subscriber differential data (subscriber data) to the other subscriber database system, the data matching transmission unit 24 returns a status when a “data matching” error is returned from the other subscriber database system. Is returned to “Updating one location”.

  The data matching receiving unit 25 stores the subscriber differential data (subscriber data) given for data matching from the other subscriber database system in the subscriber data unit 10 (10-2, 10-1). Is. Although a reception response is returned to the transmission side, a “data matching” error is returned when receiving, for example, subscriber differential data (subscriber data) that cannot be stored in the subscriber data section. In addition, when all the subscriber difference data (subscriber data) is received, the data matching receiving unit 25 changes the subscriber database system to the “in operation” state.

  In the subscriber database system that has been stopped and then restored, only the data matching receiving unit 25 functions after the restoration, and the in-operation processing unit 22 functions when the data matching processing is completed. is there.

  The function for transmitting the subscriber differential data (subscriber data) stored in the subscriber differential data unit 11 to the other subscriber database system in the one-location blocked processing unit 26 is the same as the data matching transmission unit 24. It is. However, the one-location blocked processing unit 26 is configured not to accept a reference request or an update request for subscriber data given from any of the call processing servers 3. That is, in the closing time that is a very short time during which the one-location blocking processing unit 26 is functioning, neither of the subscriber database systems 2-1 and 2-2 accepts a reference request or update request for subscriber data. .

  The one-location blocked processing unit 26 returns to the “in operation” state when transmission (transfer) of all subscriber difference data (subscriber data) is completed.

  Each of the call processing servers 3-1 to 3-4 executes call processing related to the telephone terminal accommodated therein. The call processing servers 3-1 to 3-4 are distributed at many points. For example, a plurality of call processing servers are installed at each point.

  Each call processing server 3-1 to 3-4, through the database server 4 (4-11, 4-12, 4-21, 4-22), when it is necessary to refer to subscriber data in call processing. Then, the subscriber data section 10 (10-1, 10-2) is accessed to reference desired subscriber data. Each of the call processing servers 3-1 to 3-4 receives the database server 4 (4-11, 4-12, 4-21, 4-4) when an instruction to update subscriber data is given from the telephone terminal. -22), the subscriber data section 10 (10-1, 10-2) is accessed to update the corresponding subscriber data.

  In terms of such functions, each of the call processing servers 3-1 to 3-4 is a subscriber database client.

  FIG. 3 is a functional block diagram of the call processing server 3 (3-1 to 3-4) according to the embodiment from the subscriber database client functional aspect.

  In FIG. 3, the call processing server 3 (3-1 to 3-4) includes a health check unit 30, a subscriber database state management unit 31, a server access order setting unit 32, a subscription from the functional aspect of the subscriber database client. A subscriber data reference unit 33 and a subscriber data update unit 34.

  The health check unit 30 checks the health of all database servers 4-11, 4-12, 4-21, 4-22 at a predetermined cycle (for example, 1 second) (connection check and database operation check; life / death check). Is to do. The database server is determined to be “dead” only when the health check result is “dead” for a predetermined number of times (for example, 3 times) instead of once, and the subscriber database state management unit 31 determines A message to that effect is written.

  The health check unit 30 determines whether any database server 4-11, 4-12, 4-21, 4-22 is determined to be dead, or all the database servers belonging to a certain subscriber database system determine the death. In such a case, a management device (not shown) on which maintenance, an administrator, etc. are waiting is notified to that effect.

  The subscriber database state management unit 31 is a state based on the health check results of the database servers 4-11, 4-12, 4-21, and 4-22 by the health check unit 30, a maintenance device (not shown), and a subscription. It manages the status of the subscriber database systems 2-1 and 2-2 given from the subscriber database systems 2-1 and 2-2.

  Since the call processing server 3 is allowed to access any of the database servers 4-11, 4-12, 4-21, and 4-22, the server access order setting unit 32 refers to the call processing server 3. The database server order is set. When the higher ranking is in a state where it cannot be referred to, such as a dead state, the database server of the next ranking is to be referred to. The setting contents of the reference order may be determined by a maintenance device (not shown) and stored in the server access order setting unit 32, or determined by a maintenance person and stored in the server access order setting unit 32 via the maintenance device. It can be made to be updatable and can be updated.

  For example, the reference order is set for each of the call processing servers 3-1 to 3-4 as follows. For the call processing server 3-1, the order of 4-11 → 4-12 → 4-21 → 4-22 is set. For the call processing server 3-2, the order of 4-12 → 4-11 → 4-22 → 4-21 is set. The order of 4-21 → 4-22 → 4-11 → 4-12 is set for the call processing server 3-3. For the call processing server 3-4, the order of 4-22 → 4-21 → 4-12 → 4-11 is set. With such a setting, it becomes possible to distribute the load evenly so that reference requests from many call processing servers 3-1 to 3-4 are not biased to one database server.

  The reference order set in the server access order setting unit 32 is also used to determine a database server used when updating subscriber data, as will be described later.

The subscriber data reference unit 33, when a call processing unit (not shown) or the like determines that it is necessary to refer to the subscriber data for the call processing at that time (for example, when it is necessary to check whether call forwarding is on or off) ), subscriber refers to the setting storage order content and server access order setting unit 32 of the database state management unit 31, upon determining the database server 4 which mediate the common disk 5 in which the database server 4 is connected The desired subscriber data (all or a part of items) to be referred to by accessing the subscriber data section 10 is retrieved.

  The subscriber data update unit 34, when a call processing unit (not shown) determines that the subscriber data needs to be updated (for example, when switching call forwarding from on to off), With reference to the stored contents and the setting order of the server access order setting unit 32, the database server 4-1 (4-11 or 4-12), 4- 2 (4-21 or 4-22), the subscriber data sections 10-1 and 10-2 of the common disks 3-1 and 3-2 are accessed to obtain desired subscriber data (entire or one). Part item).

  In the case of this embodiment, basically, the synchronous data replication method is adopted, so that the subscriber data update unit 34 updates the subscriber data in all the subscriber database systems 2-1 and 2-2 almost simultaneously. Update.

  For example, when the two database servers 4-11 and 4-12 belonging to the subscriber database system 2-1 are both normal, the subscriber data update unit 34 has a higher reference order. If the two database servers 4-21 and 4-22 belonging to the subscriber database system 2-2 are both normal, the update of the subscriber data is performed via the one with the higher reference order. To update the subscriber data.

Further, the subscriber data update unit 34 is one of the subscriber database systems 2-1, in which the subscriber database state management unit 31 describes a state in which the subscriber data is not updated, such as the system being stopped. may not to request the updating of subscriber data for 2-2, also may be sending the request. In the latter case, the subscriber data is not updated because the subscriber database systems 2-1 and 2-2 do not correspond.

(A-2) Operation of Embodiment Hereinafter, the operation of the subscriber database network 1 of the embodiment will be described.

  First, the operation in a state where both the subscriber database systems 2-1 and 2-2 can be normally operated will be described.

  When the call processing server 3-1 needs to refer to the subscriber data, the call processing server 3-1 accesses the subscriber data unit 10-1 through the first database server 4-11 in the order determined by itself. Read and reference desired subscriber data.

  When the subscriber data needs to be updated, the call processing server 3-1 has one subscriber database system 2-1 with the higher ranking belonging to the system 2-1. The subscriber data section 10-1 is accessed via the database server 4-11, the corresponding subscriber data is updated, and the other subscriber database system 2-2 belongs to the system 2-2. The subscriber data unit 10-2 is accessed via the database server 4-21 on the higher order side, and the corresponding subscriber data is updated. That is, the corresponding subscriber data is always stored twice.

  The call processing server 3-1 performs health checks on all the database servers 4-11, 4-12, 4-21, and 4-22 at a predetermined cycle (for example, 1 second), and continues for a predetermined number of times (for example, 3 times). Then, the database server that becomes abnormal in the health check is determined to be dead. However, for example, even if the database server 4-11 is determined to be dead, if the database server 4-12 that is accessed by the common disk 5-1 to be accessed is not dead, the database server 4-11 mediates. Switching to refer to and update the subscriber data via the database server 4-12 (according to the priority order).

  Note that the call processing server 3-1 notifies a maintenance device or management device (not shown) of an abnormality (dead state) of the database server alone or an abnormality (dead state) of all database servers belonging to the subscriber database system. To do.

  Next, the operation when the subscriber database system 2-2 is stopped and the operation when it is restored will be described.

  For example, the subscriber database system 2-2 may be stopped for maintenance. Further, for example, the system may stop due to a failure of the subscriber database system 2-2, such as when a failure occurs in both the database servers 4-21 and 4-22.

  When such a subscriber database system 2-2 is shut down, the maintenance person who recognizes the fact uses a maintenance device (not shown) to the other subscriber database system 2-1, "one location. Give an "update" instruction command. The database server 4-11 or 4-12 that has received the “one location update” instruction command thereby changes the state from “in operation” to “one location update in progress” (see FIG. 4).

  In addition, the maintenance person broadcasts that the subscriber database system 2-2 is stopped to all the call processing servers 3-1 to 3-4 using the maintenance apparatus. It should be noted that the call processing servers 3-1 to 3-4 autonomously recognize the suspension of the subscriber database system 2-2 by the health check function of the call processing servers 3-1 to 3-4. , You may not broadcast.

  In such a system stop state of one subscriber database system 2-2, for example, when the call processing server 3-1 needs to refer to subscriber data, the other subscriber database system 2- 1, the subscriber data section 10-1 is accessed via the first database server 4-11 in the order determined by itself, the desired subscriber data is read and referenced, and the subscriber data is updated. When it becomes necessary, the subscriber data section 10-1 is accessed via the database server 4-11 on the higher-order side determined for the other subscriber database system 2-1, and the corresponding subscriber Update the data.

  The database server 4-11 not only updates the subscriber data in the subscriber data section 10-1, but also the subscriber differential data section in response to the subscriber data update request in the "one location update in progress" state. The subscriber data relating to the update request is stored for 11-1.

  Even if only the subscriber database system 2-1 becomes accessible, the two database servers 4-11 and 4-12 are provided, and the higher priority differs depending on the call processing servers 3-1 and 3-4. The load on each of the database servers 4-11 and 4-12 can be evenly distributed, and it is possible to respond quickly to reference requests and update requests from the respective call processing servers 3-1 to 3-4. it can.

  When one subscriber database system 2-2 is stopped, the call processing server 3-1 requests the subscriber database system 2-2 to make an update request to the subscriber database system 2-1. No renewal request is made. Even if an update request is made to the subscriber database system 2-2, since the system is stopped, the update request becomes meaningless.

  When restarting the suspended subscriber database system 2-2, the maintenance person uses the maintenance device or the like to instruct the other subscriber database system 2-1 to perform a “one location update release” instruction command. give. The database server 4-11 or 4-12 of the subscriber database system 2-1 that has received the “one location update release” instruction command changes the state from “one location update in progress” to “data matching in progress” (FIG. 4). It should be noted that the restarted subscriber database system 2-2 does not enter the “in operation” state immediately after the restart and is not shown in FIG. Only the reception processing of the subscriber differential data (subscriber data) for is allowed.

  When the state changes to “data matching in progress”, the database server 4-11 or 4-12 restarts the subscriber differential data (subscriber data) stored in the subscriber differential data section 11-1 from the stopped state. It is transmitted to the activated subscriber database system 2-2. One of the database servers 4-11 and 4-12 may be in charge of transmission of such subscriber difference data, or may be in charge of transmission by a predetermined number of data or alternately every predetermined period. .

  Note that the database server 4-11 or 4-12 also responds to a subscriber data reference request or a subscriber data update request coming from the call processing servers 3-1 to 3-4 in the "data matching" state. Perform the process. In response to the subscriber data update request, the storage operation in the subscriber difference data section 11-1 is also performed.

  The database server 4-21 or 4-22 of the subscriber database system 2-2 in which the subscriber differential data (subscriber data) has arrived, in accordance with the received subscriber differential data (subscriber data), the subscriber data section Update processing for 10-2 is performed. The database server 4-21 or 4-22 receives the subscriber data reference request from the call processing servers 3-1 to 3-4 in the reception state of the subscriber differential data (subscriber data) for such data matching. Even if an update request for subscriber data arrives, the request is rejected.

  In the database server 4-11 or 4-12, the remaining number of subscriber differential data (subscriber data) that must be sent to the other subscriber database system 2-2 for data matching becomes a predetermined threshold number. When the status is changed, the state is changed from “data matching” to “one-location blocked”.

  Even in this “one-location blocked” state, the database server 4-11 or 4-12 continues to transmit subscriber differential data (subscriber data) to the subscriber database system 2-2. However, in the “single location blocked” state, the database server 4-11 or 4-12 receives a request for subscriber data reference or a request for updating subscriber data from the call processing servers 3-1 to 3-4. But reject the request.

  When the transmission of the subscriber differential data (subscriber data) is completed, the database server 4-11 or 4-12 of the subscriber database system 2-1 returns the state from “one location blocked” to “in operation”. . When the database server 4-21 or 4-22 of the other subscriber database system 2-2 completes the reception of the subscriber differential data (subscriber data), the status is changed from “matching data receiving” to “in operation”. change.

  As a result, both subscriber database systems 2-1 and 2-2 become “in operation” and return to the normal state in which synchronous data replication is executed.

  Here, when the network N3 is stopped, one subscriber database system 2-1 accepts subscriber data reference requests and update requests from the call processing servers 3-1 and 3-2. The other subscriber database system 2-2 enters a “one-location updating” state in which subscriber data reference requests and update requests from the call processing servers 3-3 and 3-4 are accepted. When the network N3 is restored, data matching transmission similar to that described above from the subscriber database system 2-1 to the subscriber database system 2-2, and from the subscriber database system 2-2 to the subscriber database system 2-1. Data matching transmission similar to that described above is executed.

  That is, even when the network is divided, individual subscriber data can be referred to and updated with respect to the subscriber database systems 2-1 and 2-2, and a very short request rejection time ( Data can be matched only by the blockage time).

  When the network N3 is stopped, the subscriber database system 2-2 appears to be stopped when viewed from the subscriber database system 2-1. Conversely, the subscriber N2 is viewed from the subscriber database system 2-2. It seems that the database system 2-1 is stopped. For this reason, in the claims, the case where some subscriber database systems are stopped is expressed, but this expression also includes a case where the network is divided.

(A-3) Effect of Embodiment According to the above embodiment, when all the subscriber database systems are normal, the subscriber data is updated according to the synchronous data replication method, and the subscriber data is multiplexed. Can be achieved.

  In addition, according to the above embodiment, even when one subscriber database system is stopped while adopting the synchronous data replication method, the subscriber data reference and update for the other subscriber database system is very short blocking time. Therefore, it is possible to always provide a call processing service (telephone communication service).

  Furthermore, in the period in which the subscriber data is referred or updated by the other subscriber database system, for the update request of the subscriber data, considering the data consistency between the systems later, In addition to updating, it is stored as subscriber differential data, and the subscriber differential data stored when the subscriber database system is restarted at the time of suspension is transmitted to the restarting system to update the subscriber data. Since it did in this way, the subscriber data of both subscriber database systems can be matched.

  Even at the time of transmission for data matching, the subscriber database system on the sender side allows the reference and update of subscriber data except for a very short blocking time, so the call processing service (telephone communication service) A consistent provision can be achieved.

  In addition, since both subscriber database systems provide a very short blocking time for prohibiting the reference and update of subscriber data and complete data matching, data matching can be ensured.

(B) Other Embodiments In the description of the above embodiment, the case where there are two subscriber database systems is shown, but there may be three or more. Even in this case, all subscriber database systems are operated in parallel and the data is kept the same. When a certain subscriber database system is stopped, the same processing as in the above embodiment is performed. Even in this case, data is matched in a plurality of normal subscriber database systems, and at least one system stores subscriber difference data. When the shutdown system is restarted, the data is stored in the same manner as described above. Align.

  In the above embodiment, the subscriber database network of the present invention is applied to a telephone communication system. However, the present invention can also be applied to subscriber database networks of other systems. For example, the present invention can be applied to a subscriber database network related to a credit card. The term “subscriber” includes the concepts “customer” and “contractor”.

  Furthermore, in the above embodiment, the subscriber data stored by the call processing server giving the subscriber data update request to all the subscriber database systems when all the subscriber database systems are normal. However, the call processing server gives a subscriber data system update request to a certain subscriber database system, and the subscriber database system that receives the request immediately copies it to other subscriber database systems. Thus, the subscriber data may be matched.

  Furthermore, in the above-described embodiment, the transition determination to the “one-location blocked” state, which is the final stage of data matching, is performed based on the remaining number of subscriber difference data, but the remaining data capacity, etc. Other parameters may be used. In short, it is only necessary that the blocking time during which all subscriber database systems do not accept reference requests and update requests is made very short.

It is a block diagram which shows the whole structure of the subscriber database network of embodiment. It is a block diagram which shows the functional structure of the database server of embodiment. It is a block diagram which shows the functional structure of the call processing server (subscriber database client) of embodiment. It is explanatory drawing which shows the state transition of the subscriber database system of embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Subscriber database network, 2-1, 2-2 ... Subscriber database system, 3-1 to 3-4 ... Call processing server 4, 4-11, 4-12, 4-21, 4-22 ... Database server, 5-1, 5-2 ... common disk, 10-1, 10-2 ... subscriber data part, 11-1, 11-2 ... subscriber difference data part, 12-1, 12-2 ... piece Location state part 20 ... Received signal analysis part 21 ... Health check corresponding part 22 ... In-operation processing part 23 ... One-location updating in-process part 24 ... Data matching transmitting part 25 ... Data matching receiving part 26 ... One location block processing unit, 30 ... health check unit, 31 ... subscriber database state management unit, 32 ... subscriber data reference unit, 33 ... subscriber data update unit.

Claims (3)

A plurality of subscriber database systems including a subscriber data section storing subscriber data and a database server that accesses the subscriber data section in response to a request for reference or update of subscriber data; In a data matching method for a subscriber database network, which has a plurality of database clients that issue subscriber data reference requests or update requests, and matches the stored contents of the subscriber data portions of the subscriber database systems.
Each of the above subscriber database systems includes a subscriber differential data section that can store subscriber differential data in which the stored contents of the subscriber data section differ due to the suspension of other subscriber database systems,
When any one of the subscriber database systems is stopped, all the other subscriber database systems receive a reference request or update request for subscriber data, and perform a process of matching the stored contents of the subscriber data section, at least One subscriber database system stores subscriber difference data in the subscriber difference data section for transmission upon restart of the suspended subscriber database system,
As restarting any of the subscriber database system has been stopped, the subscriber database system containing the subscriber difference data to the subscriber difference data unit was restarted the subscriber difference data above All of the subscriber database systems, except for the restarted subscriber database system, receive subscriber data reference requests or update requests and store the contents stored in the subscriber data section. The matching process is performed, and at least one of the subscriber database systems continues to store in the subscriber difference data section,
When it is determined that the remaining transmission time of the subscriber differential data to the restarted subscriber database system is less than or equal to the time allowed by the network stop, all the above including the restarted subscriber database system The subscriber database system rejects a request to reference or update subscriber data;
A data matching method for a subscriber database network, characterized in that when all subscriber difference data is transmitted to the subscriber database system, all the subscriber database systems are returned to a normal state.   2. The subscriber database network data matching method according to claim 1, wherein each of the subscriber database systems has a common subscriber data section and a plurality of database servers.   3. The data matching method for a subscriber database network according to claim 1, wherein each database client sets an order with respect to a database server to which a request for subscriber data reference is transmitted. .

Images