JPH08255133A - Device and method for user id management in decentralized server system - Google Patents

Abstract

PURPOSE: To make possible the utilization which is efficient in time and economy and freely select and use a server by reporting registered ID management information to a server other than the server whose use registration is accepted by an ID information management means. CONSTITUTION: In the decentralized server system consisting of plural servers which are decentralized and connected by a network, an ID registering means 1 receives ID management information on users whose use registration is accepted by the respective servers and registers it as ID management information by the servers at a time. Then an ID information management means 2 reports the ID management information registered by the ID registration means 1 to servers other than the servers having accepted the use registration. Consequently, after user registration is done once, data provided by ah the servers can freely be utilized in a short time at low cost irrelevantly to on which server the registration is done, and similar services can be offered from other service points at the time of congestion of the network and movement from an area to another.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a user ID management device and method for distributed server systems.

A server system has a function of providing registered users with various information via terminals and exchanging information as a communication tool between many users.

An identification number, a password, etc. for confirming the right of use is issued to each of the above registered users when using the system, and the user ID management device manages and operates it.

Further, the distributed server system is a system in which a plurality of servers are distributed in regions and are organically connected via a center server to realize sharing and cooperation of processing.

[0005]

2. Description of the Related Art Conventionally, in the construction of a centralized server system, data and IDs are centrally managed, so that the user can freely use any terminal. Further, in the past, it was sometimes desired to apply the distributed server system when the server system has a wide range of users or when the number of users is large.

However, as described below, in the construction of the conventional distributed server system, it is difficult to operate the system like the centralized system. As an operation method, a system in which ID management is performed centrally by one server and another is MHS (Message Handling Sy) which is a standard protocol of an electronic mail system.
data is exchanged for each server and prepared for each server, and ID management is performed by each server.
There is a management system.

However, in the former system, WAN (WideArea Network) is used between remote servers.
In the case of connection by rk), if the relay line is slow, it takes time to confirm the ID and the response is unavoidably deteriorated.

Further, in the latter system, even when the servers are connected by WAN, the data is regularly exchanged by the MHS and can be used without passing through the line, so that the response by the relay line is deteriorated. However, since each server individually holds and manages ID management information, users who are registered for use on other servers but whose IDs are not registered on the accessed server are: The ID cannot be accepted and the use is not permitted.

The configuration and operation of the conventional example will be described with reference to FIGS. FIG. 6 is a configuration example showing the principle of a conventional distributed server system. The center server 61 uses the other servers (62a
62 c) is an ID management server that centrally manages IDs. In the figure, “ID management # 1” to “ID management # 3” are #
The ID management areas of the servers 1 to # 3 are shown. Further, “data # 1” to “data # 3” indicate the data area of each server.

The operation of the configuration example of FIG. 6 will be described with reference to the flowchart example of FIG. When the user presents the ID to the server # 1 in step S71 and tries to use it, the presented ID is registered in the center server (ID management server) from the server # 1 in step S72 and is valid. ID verification is performed as to whether or not the user has the right to use, and it is confirmed whether or not the ID is a registered ID. If OK, the start of use is permitted (step S73). If it is not OK, the server that accepts the use performs a new ID registration in the center server (ID management server) after the ID management procedure based on the usage application (step S74).

As described above, each server needs to be connected to the center server not only at the time of registering a new ID but also at each collation of the ID for starting use, and connection and transmission in a relay line with the center server are required. Affected by response due to time. Further, as for data, only data registered in each server can be accessed, and data stored in other servers cannot be accessed.

FIG. 8 and FIG. 9 show an example of the configuration and operation of another conventional distributed server system. FIG. 8 is another configuration example showing the principle of the conventional distributed server system in which each server manages only its own local ID. The “server # 0” 81 is a center server, but has the same service function as the other servers 82a to 82c except that it additionally has a role as a center, and ID management is performed for each server including the center server 81. Local ID
Manages only.

Regarding the data, the center server 81 regularly exchanges the data # 0 to the data # 3 of each of the servers 82a to 82c by the MHS.
3 ”is stored and all can be shared.

In the figure, "ID management # 0" to "ID management # 3"
Indicates an ID management area, and #N represents an ID registered in the #N server. Further, "data # 0 to 3" indicates that all the data input to the servers # 0 to # 3 are stored.

As shown in FIG. 9, the operation is performed by the server # 1.
If there is access by ID, the server # 1
First, ID verification is performed (step S92). From the result, the presence or absence of registration is confirmed, and if it is not registered, it is possible to start the use after newly registering the ID in the server # 1 (step S94). However, since the registration of the new ID is not reflected in the other server, it is necessary to register the ID again when accessing from the other server.

[0016]

As described in the above prior art, in the conventional distributed server system,
As for ID management, there is a problem that it takes a long time to start the use procedure and that the servers other than the registered server cannot be used.

In view of the above points, the present invention enables centralized registration of use regardless of which server of the distributed server system is accessed, which enables efficient use in terms of time and money and is free. It is an object of the present invention to provide a means for selecting and using a server.

[0018]

The above-mentioned problems are solved by the user ID in the distributed server system configured as follows.
Solved by a management device and method.

FIG. 1 is a block diagram of the present invention. The ID registration means 1 receives the ID management information of a user whose usage registration is accepted by each server in a distributed server system including a plurality of servers which are distributedly arranged and connected by a network, and an ID for each server. The information is collectively registered as management information. Further, the ID notification management means 2 is I
The ID management information registered by the D registration means 1 is notified to a server other than the server that has accepted the usage registration.

[0020]

In the distributed server system which is composed of a plurality of servers which are distributed and are connected by the network,
The ID registration means 1 receives the ID management information of the user whose usage registration has been accepted by each server, and collectively registers the ID management information as ID management information for each server. 2 notifies the server other than the server that has accepted the usage registration.

[0021]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 2 is a network configuration diagram of an embodiment, and FIG. 3 is a flowchart for explaining its operation.

The embodiment shows the configuration of management by ID when a telephone, FAX, or data terminal accesses each access point via the telephone networks 24a to 24c. In FIG. 2, the center server 21 is a media server # 1 to # 3 (22a
22c) as the access points, the distributed server system has a function of controlling exchange of ID management information and data of each media server for ID management and data management.

Each media server 22a to 22c receives access from a telephone set, a FAX or a data terminal via a telephone network, and returns data extracted from data held by each server as needed. Do the service. For example, provide traffic information, weather information, notices, bulletin boards for exchanging information on shopping or information among users possessed by the distributed server system, e-mail, etc. as voice information, image information or text data. It is a service.

Although each media server is installed in a geographically distant place, it serves common information of a wide area to a distributed user group. For example, if the prefecture provides information to citizens of the prefecture, the above media servers can be installed in each city, and citizens who are users can access local media servers that can usually be connected by a low-cost local line. Get all the information.

The media servers 22a to 22c are regularly provided so that the information about the prefecture can be provided to the media servers 22a to 22c. In this embodiment, the media servers 2a to 22c are provided every 30 minutes.
The data of 2a to 22c are exchanged. In addition, even if the user, the citizen of the prefecture, moves to another city in the prefecture, he / she can access the prefecture information as before without having to register on the server in the city to which he / she is moving. The registered ID as well as the data is exchanged every 30 minutes so that it can be used with the same user ID when accessing an access point in an adjacent area. It is like this.

As described above, the distributed server system according to the present embodiment is configured such that the data and the ID management information are always exchanged so that the same service can be obtained regardless of which server is accessed although there is a time delay. The operation will be described below with reference to the flowchart of FIG.

In step S31, the user dials access point #N (N is 1, 2, 3, etc.) to request connection. In the dialed server #N, whether or not the user who has accessed by the ID management information held in the ID management unit is a legitimately registered user, ID verification,
Furthermore, the password is verified (step S32). As a result, if it is confirmed that the regular registration is made, the use permission is given and the use is started (step S33).
).

As a result of the ID collation, if it is not registered and a new registration is requested, the server #N is sent in step S34.
Apply for a new ID registration. The application process will be accepted immediately by email, but the registration process will take some time. This is indicated by a dotted arrow connecting to the use permission in step S35. Similarly, the dotted arrows below indicate that time elapses.

When the use is permitted, first the use of the #N server is permitted. In step S36, the ID management information newly registered from #N is periodically transmitted in response to the inquiry from the # 0 center server, and the ID management information of the center server is updated.

Further, when periodically distributing from the center server to each server, the ID newly registered from #N to the center server as described above is I of servers other than the registration source #N.
It is reflected in the D management section. This ensures that I
The newly registered #N user ID is reflected in the D management section (step S37).

Now, with respect to the method of reflecting the ID management information newly registered in each server in the ID management section of another server as described above, an explanatory diagram of inter-server exchange of ID management information of FIG. 4 and FIG. An example will be described using a flowchart for explaining the exchange of ID management information between servers.

First, in FIG. 4A, there are a server # 0 as a center server and servers # 1 to # 3 connected by lines 43a to 43c. As described above, these four servers are provided. All data and user IDs registered in each server are stored in each server. That is, all data are stored in the data # 0-3 of each server, and all IDs are stored in the ID management # 0-ID management # 3.

In the embodiment of the present invention, as described above, there is no change in the ID management information such that a new ID is registered in each server, the registered content of the ID registered so far is changed, or the ID is deleted. Held on a regular basis. Each server immediately reflects these changes in its own ID management unit, but there is a situation in which the changes are not reflected in the management units because of other servers.

Therefore, the inter-server exchange program of the ID management information of the server # 0 connected to each server as the center server by the lines 43a to 43c is regularly started every 30 minutes, and the above imbalance occurs. The ID management information is replaced and the same contents are exchanged. Roughly line 43a ~
43c is used to inquire from the server # 1 to the server # 3 in sequence whether or not the ID management information has been changed. If there is, the changed information will be downloaded and will be reflected only on the center server by then. The process proceeds at the stage of transmitting what has not yet been reflected to each server.

The operation will be described in detail with reference to the flowchart of FIG. Although only the exchange of the ID management information is described here, the data portion is actually exchanged as described above.

The program started every 30 minutes by the clock on the server # 0 starts with the first server # at step S51.
Communication for exchanging ID management information is started in order from 1. In step S52, an inquiry is made as to whether the ID management information of the server #S, that is, the server # 1 has any change, that is, new registration, update of contents, or deletion. Y if any of these changes have occurred since server # 1 last reported to the center server.
Proceeding to ES, in step S53, the ID management information changed in server # 1 is transmitted to server # 0 in the form of a change notification message for each ID.

The format of the change notification message is shown in FIG. 4 (c).
In addition, the structure of the ID management unit that stores the ID management information is shown in FIG.
It is shown in (b). Here, the ID management part exemplifies a part of the server # 0 as the center server, but the other parts are different only in that the leading # 0 management flag part is only for each server. Therefore, # 0 will be described as an example.

The occurrence code indicates which change in the latest ID management information is the cause and the cause of the occurrence. That is, when this data is 01, it is newly registered,
A value of 10 indicates that the content has been changed (updated), and a value of 11 indicates that the content has been deleted. 00 represents a vacant space, and when a new registration is made, the occurrence code column of 00 is searched and 01 indicating the new registration is entered therein.

The ID number is the server number + sequential number, and has a format in which the server numbers 0 to 3 and the serial numbers managed by each server are combined with a hyphen. This is to prevent duplication of numbers because new registration of ID can be accepted by any server. The ID number "2-045" indicates that it is the 45th one issued by the server number # 2. The password is applied and registered by the user, and is changed from time to time for security.When the change is made, the ID management unit of the server used is immediately changed, but other The ID management unit of the server will periodically be reflected by the inter-server exchange of the ID management information described here.

The attribute stores various information about the user who registered the ID, and includes a name, an address, a telephone number and the like. The change notification message is data that is transmitted as a set of each of the above information. The center server which has received the change notification message in step S53 reflects and updates the ID management unit of the server # 0 as shown in FIG. 4B. Update is performed as follows.

If the generation code is 01, it means that the registration is new registration and the ID number has not existed before. Therefore, the generation code column of the ID management section is 00, and a free state is searched for and the change notification message is stored as it is. At this time, the management flag is set to 1 corresponding to the server that has sent the notification message and the management message,
Other flags are set to 0. That is, the management flag indicates whether the ID management unit of the server of the corresponding number has already been updated. For example, the ID number “1-066” in FIG.
When the change notification message is received, the management flags of # 0 and # 1 are set to 1, which means that the remaining servers have not been reflected in the servers # 2 and # 3.

When the change notification message having the generation code of 10 or 11 is received, it is reflected in the ID management section by searching for the ID number as a key and replacing the matched ID management information with the contents of the change notification message. That is,
In the case of the occurrence code 10 indicating the content change, it is considered that there is a change in any part other than the ID number, so the password and the attribute are replaced. In the case of 11 meaning deletion, only the generated code is 11 without changing the existing information.
And it is sufficient.

As for the # 0 management flag, since the server of # 0 is the center server, it is necessary to exchange the ID management information. # 1
Although the flags up to # 3 are also provided, other general servers need only have flags for their own server numbers. However, it is a little different from the flag of the number indicating another server. For example, when the ID number in FIG. 4B is “0-107”, all flags are 0.
Since the server number at the beginning of the ID number is 0, the ID (occurrence code 0
1), which means that it is not yet reflected in the servers # 1 to # 3. The flag of # 0 is also 0,
Since this is the number of my server, it indicates that the change in the ID management information that has occurred in my server has not been transmitted to another server and is not reflected. The management flags in the other servers need only be related to their own server numbers, but have the same meaning as the flags corresponding to # 0 above.

In the flowchart of FIG. 5, in step S54, if there is any ID management information that has not been transmitted to the server in communication, it is transmitted and reflected. Here, among the management flags, the #S in communication, that is, the flag indicating the server of # 1 is 0, that is, the data that has not been transmitted yet is selected and transmitted to the server # 1 as a change notification message. The flag for # 1 is changed to 1 in order to mark the transmission completion. If the flags of # 0 are 0 when the flags corresponding to all the servers have become 1, this is set to 1 and it is recorded that the changes occurring in the server # 0 have been reflected to all the servers.

The following steps S55 and S56 are repeated to reflect the server # 2 and server # 3. Step
If there is no change in the ID management information in the server #S in S52, only the change information of the ID management information stored in # 0 is reflected in step S54.

As described above, the exchange of the ID management information to each server, which is once every 30 minutes in this case, may cause a difference in an instant, but the frequency is too high. With respect to the change operation of the ID management information, it is possible to always keep the same state in practice.

[0047]

As is apparent from the above description, according to the present invention, in a distributed server system, once a user is registered, no matter which server it is registered in, no matter which server is accessed, , You can freely use the data provided by all the servers in a short time at a low price, and even when the network is crowded or when you move locally, you can enjoy the same service from other access points, which is economical. There are significant industrial effects, such as the physical effect, the improvement of user efficiency, and the expansion of system availability.

[Brief description of drawings]

FIG. 1 is a block diagram of the present invention

FIG. 2 is a network configuration diagram of an embodiment of the present invention.

FIG. 3 is a flowchart for explaining the operation of the embodiment of the present invention.

FIG. 4 is an explanatory diagram of exchange of ID management information between servers.

FIG. 5 is a flowchart for explaining exchange of ID management information between servers.

FIG. 6 is a configuration example (1) of a conventional distributed server system.

FIG. 7 is an example of an operation flowchart of a conventional distributed server system (No. 1)

FIG. 8 is a configuration example (2) of a conventional distributed server system.

FIG. 9 is an example of an operation flowchart of a conventional distributed server system (No. 2)

[Explanation of symbols]

 1 ID registration means 2 ID notification management means

Claims (2)

[Claims] 1. A distributed server system comprising a plurality of servers which are distributedly arranged and connected by a network, wherein each server receives ID management information of a user whose usage registration has been accepted, and ID management for each server. It is characterized by having an ID registration unit that collectively registers as information, and an ID notification management unit that notifies the ID management information registered by the ID registration unit to a server other than the server that has accepted the use registration. A user ID management device in a distributed server system. 2. A distributed server system comprising a plurality of servers arranged in a distributed manner and connected by a network, wherein each server receives the ID management information of the user who has accepted the use registration and manages the ID of each server. A user ID management method in a distributed server system, wherein the registered ID management information is collectively registered as information, and the registered ID management information is notified to a server other than the server that has accepted the usage registration.