JP2682467B2 - Subscriber information management method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION The present invention comprises a host computer, a plurality of sub-computers under the control of the host computer, and a plurality of subscriber terminals under the control of each sub-computer. The sub computer manages the information data of each subscriber terminal under its control, and the host computer collectively manages the information of the subscriber terminals under the control of each sub computer managed by each sub computer. Regarding the subscriber information management system that is doing.

[0002]

2. Description of the Related Art In the conventional subscriber information management system,
Since the host computer collectively manages the subscriber information data, the modification of the subscriber information data is performed as described in (1) and (2) below.

(1) When the subscriber information data of the host computer and the subscriber information data of the sub computer do not match, the subscriber information data of the sub computer is rewritten with the subscriber information data of the host computer. .

(2) For updating the subscriber information data from the subscriber terminal, the subscriber information data of the sub computer is rewritten after retrieving and updating the subscriber information data of the host computer.

[0005]

In the above-mentioned conventional subscriber information management system, even when the subscriber information data of the host computer is destroyed due to a failure or the like, the subscriber information data of the sub computer is rewritten with the data. However, there is a drawback in updating the subscriber information data that the subscriber information data desired by the subscriber cannot be obtained unless the subscriber information data of the host computer is updated.

Therefore, an object of the present invention is to provide a subscriber information management system which does not have the above-mentioned drawbacks.

[0007]

According to the subscriber information management system of the present invention, a host computer, a plurality of sub computers subordinate to the host computer, and a plurality of sub computers subordinate to each sub computer are provided. Each sub-computer manages the information data of each subscriber terminal under its control, and the host computer manages the information data of each sub-computer under the control of each sub-computer. A subscriber information management system for collectively managing information of subscriber terminals, wherein the host computer and the sub-computers each have a reliability index indicating reliability of data in each subscriber information data managed by the host computer and the sub-computers. While giving each, the host computer periodically monitors the subscriber information data managed by itself and the subscriber information data managed by each sub computer, and the corresponding subscriber If the mismatch between broadcast data occurs, it has a subscriber information data updating means for rewriting update subscriber information data unreliable towards the subscriber information data with higher reliability.

Further, the host computer and each of the sub-computers access the subscriber information data managed by themselves, and when the subscriber information data can be read normally and the related processing can be performed, the reliability index is changed. When a failure occurs, a low index is given to the reliability index, and when the host computer drives the subscriber information data updating means to rewrite the subscriber information data, the host computer and each of the above It is preferable to give the reliability index of the sub-computer an intermediate index that is normal.

Further, when the sub-computer is requested to change the subscriber information data by a subordinate terminal under the control of the sub-computer and the change processing can be normally performed, the reliability index of the subscriber terminal requesting the change is calculated. Give a high index to.

[0010]

When the subscriber information data of the host computer is destroyed due to a failure or the like, the host computer holds the reliability index of the subscriber information data held by itself and the reliability of the subscriber information data corresponding to the sub computer. Since it is compared with the index and is rewritten with the subscriber information data with the higher reliability index, the highly reliable subscriber information data can always be held, and the subscriber information data in the sub computer is Since it is rewritable according to the request, the subscriber information data is as desired by the subscriber.

[0011]

Next, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a subscriber information management system to which an embodiment of the subscriber information management system of the present invention is applied. The host computer 10 is a sub computer 20,3.
0 and 40 are managed as subordinates, and sub computers 20, 30 and
40 is terminals 21, 22, 23 and terminals 31, 32, 33
And the terminals 41, 42 and 43 are managed as subordinates.

The sub-computers 20, 30, 40 are the terminals 2
1, 22, 23, terminals 31, 32, 33 and terminal 4
In order to manage 1, 42, 43 respectively, the information of the subordinate terminals is stored. For example, the sub computer 20 stores information about the terminals 21, 22, 23 under its control as a table configured as shown in FIG. That is, the terminal information 221, 222, 223 is stored corresponding to the subscriber numbers of the terminals 21, 22, 23 (the same applies to the sub computers 30, 40).

The terminal information 221, 222, 223 has the following terminal information indicating whether or not there is subsequent terminal information (for example, in the case of the terminal information 221, the storage location of the terminal information 222 is Address), a subscriber number to which the terminal information belongs, a reliability index indicating the degree of reliability of the terminal information, and subscriber information that is various information regarding the subscriber. If there is subsequent terminal information, it is repeated in the same format as the terminal information 221, 222, 223.

The sub-computer 20 (similarly to the sub-computers 30 and 40, but only the sub-computer 20 for simplification of description will be referred to as a sub-computer 20) from a subordinate subscriber terminal, for example, the subscriber terminal 21. When there is a subscriber information change request, the sub computer table 220 is searched using the subscriber number of the subscriber terminal 21 as a key, and the subscriber information of the terminal information 221 is read. In this case, if it is instructed that the information data next to the terminal information 221 has subsequent terminal information, the subscriber information of the terminal information 222 and the subscriber information of the terminal information 223 are subsequently read. If a read failure occurs during the reading of the subscriber information, the reliability index of the terminal information 221 is regarded as a low level and set to "0" (in the present embodiment, the high level is set to a high level). "2", the normal level used when rewriting the host computer 10 is "1"). When the subscriber information is normally read and the above-mentioned subscriber information change is normally performed, the sub computer 20 operates as the subscriber terminal 21.
The reliability index of is set to a high level “2”.

Further, when there is a request from the subscriber terminal 21 under the control of the sub computer 20 for a service regarding the subscriber information of a subscriber terminal not under its control (for example, a subscriber terminal 43 under the control of the sub computer 40), The request is for host computer 1
Delivered to 0.

The host computer 10 is a sub computer 20,3.
It stores all the terminal information about the terminals 21, 22, 23, the terminals 31, 32, 33 and the terminals 41, 42, 43 which are controlled by 0 and 40, respectively. That is, the host computer table 110 stores the sub computer tables 220, 230, 240 shown in FIG. 2 and the terminal information 221, 222, ..., 243 belonging to the sub computer tables 220, 230, 240. ing. Therefore, the host computer 10 determines, based on the delivered request, the corresponding subscriber from the sub computer table 240 stored in the host computer table 110 and the terminal information 241, 242, 243 stored in correspondence therewith. The information is read and passed to the sub computer 20. If a read failure occurs during the reading of the subscriber information, the corresponding terminal information 24 stored in the host computer 10 is read.
The reliability indexes 1, 242 and 243 are regarded as low levels and set to "0". Further, when the subscriber information is read normally and the above-mentioned subscriber information is changed normally, the reliability index is not changed.

Next, the monitoring of the subscriber information of the sub-computer which is periodically performed by the host computer will be described with reference to the flow chart of FIG. The host computer 10 uses the sub computer table 2 stored in the host computer table 110.
It is determined whether or not there is subscriber information recorded in the terminal information stored corresponding to 20, 230, 240 (step S1). If there is no recorded one, the process ends, but if there is recorded one, the subscriber information of the relevant terminal information is taken out from the sub computer (step S2) and also taken out from the host computer (step S).
3). It is determined whether or not the subscriber information extracted from both parties match (step S4). If they do not match, the reliability indexes of the terminal information of the both are compared to determine whether the reliability index of the host computer is lower (step S5).

When the reliability index of the host computer is lower, the subscriber information of the host computer is rewritten by the subscriber information of the terminal information from the sub computer (step S).
6). If the reliability index of the host computer is higher or the same, the subscriber information of the sub computer is rewritten with the subscriber information of the host computer (step S7). After these rewritings are completed, the reliability index of the corresponding terminal information of the host computer and the sub computer is normally set to "1" (step S8).

Further, it is determined whether or not there is terminal information that follows the terminal information set to "1" in step S8 (step S9). If there is subsequent terminal information, the process returns to step S2, and the same monitoring is repeated for the subscriber information of the subsequent terminal information. If there is no subsequent terminal information, it is determined whether there is terminal information belonging to another sub computer (step S1).
0). If not, the process ends, but if there is, the process returns to step S2 to repeat similar monitoring. If the subscriber information matches in step S4, the process proceeds to step S8.

[0020]

As described above, according to the present invention, even if the subscriber information data of the host computer is destroyed due to a failure or the like, the host computer drives the subscriber information data updating means to retain itself. The reliability index of the subscriber information data to be compared with the reliability index of the corresponding subscriber information data of the sub-computer is rewritten with the subscriber information data with the higher reliability index, so that the highly reliable subscription is possible. The subscriber information data can always be held, and the subscriber information data in the sub computer can be rewritten according to the subscriber's request, so that the subscriber information data can be as desired by the subscriber. There is.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a subscriber information management system to which an embodiment of a subscriber information management system of the present invention is applied.

FIG. 2 is a diagram showing information stored by a sub-computer in the embodiment of FIG. 1 regarding a subscriber terminal under its control.

FIG. 3 is a diagram showing information stored by a host computer regarding a subscriber terminal under the control of a sub computer in the embodiment of FIG.

FIG. 4 is a flowchart for explaining the operation of the embodiment of FIG. 1;

[Explanation of Codes] 10 host computer 20,30,40 sub computer 21,22, ..., 43 subscriber terminal 110 host computer table 220 sub computer table 221,222, ..., 243 terminal information S1, S2, ..., S10 step

Claims (4)

(57) [Claims] 1. A host computer, a plurality of sub-computers subordinate to the host computer, and a plurality of subscriber terminals subordinate to each sub-computer, each sub-computer being its own Subscriber information that manages the information data of each subscriber terminal under its control, and that the host computer collectively manages the information of subscriber terminals under the control of each sub computer managed by each sub computer In the management method, the host computer and the sub-computers each give a reliability index indicating data reliability to each subscriber information data managed by the host computer, and the host computer periodically manages itself. The subscriber information data and the subscriber information data managed by the respective sub-computers are monitored, and if there is a discrepancy between the corresponding subscriber information data, the Subscriber information management system characterized by having a lower subscriber information data updating means for rewriting update the subscriber information data having higher reliability subscriber information data of. 2. The host computer and each sub computer access subscriber information data managed by itself,
When the subscriber information data can be read normally and the related processing can be performed, the reliability index is not changed, and when a failure occurs, the reliability index is given a low index, and the host computer makes the subscriber information data. 2. The subscriber information management system according to claim 1, wherein when the updating means is driven to rewrite the subscriber information data, an intermediate index indicating normal is given to the reliability index of the host computer and each of the sub computers. 3. The subscriber information management system according to claim 2, wherein the high index, the intermediate index, and the low index are 2, 1 and 0, respectively. 4. When the sub-computer is requested by a subordinate subscriber terminal to change the subscriber information data and the sub-computer is normally changed, the reliability index of the subscriber terminal requesting the change is calculated. The subscriber information management system according to claim 2 or 3, wherein a high index is given to.