JP2002251573A - User database server and user information acquisition device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a user database server capable of concentrically managing user information used in provision of a service via a network for reducing labor of each service providing server and each user. SOLUTION: This user database server is provided with a user database 173 storing user information used in a service providing server 2 providing a service to the user through the Internet 4, a user identifier defined univocally for the user, and a server identifier specifying the service providing server 2 while associating them to each other, a user registration means 121 associating the transmitted user identifier and the user information with each other and registering them in the user database 173, and a server registration means 122 associating the transmitted server identifier with the user identifier and registering them in the user database 173.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a server and a user information acquisition device used for providing various services via a network, and more particularly to a server and a user device used for conducting electronic commerce and the like via the Internet. The present invention relates to a user information acquisition device.

[0002]

2. Description of the Related Art In recent years, with the rapid development of network networks such as the Internet, various services have been provided via networks. Recently, e-commerce using networks, particularly the Internet, has become active. Generally, provision of a service via such a network is performed through a network server (hereinafter, referred to as a service providing server) operated by a service provider. A user who wants to receive the service can access the service providing server using a personal computer, a mobile terminal, or the like, acquire various types of information, and receive the service.

When providing services via such a network, personal information (hereinafter, referred to as an address, a name, a telephone number, and an e-mail address) relating to a user is required for reasons such as the necessity of shipping products.
User information). For this reason, the above-described service providing server often holds the user information of the user providing the service as a database.

[0004]

Conventionally, a database storing such user information is provided independently for each service providing server, so that one user can provide services from a plurality of service providing servers. When receiving, a similar operation, that is, an operation of registering user information in a database, has been performed in a plurality of service providing servers. Since the construction and operation of such a database requires a great deal of labor and cost, there has been a demand for a system for reducing this.

In such a case, it is necessary for the user to register his / her own user information in a plurality of service providing servers. However, the user inputs (registers) the same user information redundantly in a plurality of service providing servers. This input operation was very complicated.

When the user information of the user is changed, for example, when the user information such as the address and the telephone number is changed due to moving or marriage, the user information is updated in a plurality of service providing servers. There is a need to. Today, when one user is receiving services from many service providing servers, such a task is very complicated.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems of the related art, and intensively manages user information used when providing a service via a network to provide a service. It is an object of the present invention to provide a user database server and a user information acquisition device capable of reducing the labor and cost of user management in a server and also reducing the labor of each user.

[0008]

In order to solve the problems in the prior art, the present invention provides a service providing server which provides a service to a user via a network. A user database in which user information of the user to be used, a user identifier uniquely defined for the user, and a server identifier for specifying a service providing server to which the user receives a service are stored in association with each other. User registration means for associating a user identifier and user information transmitted via a network with each other and registering them in the user database; and a server identifier transmitted via the network to a user identifier transmitted via the network. Server registration to associate and register in the above user database Characterized by comprising a stage.

[0009] This makes it possible for the user database server to collectively manage the user information of each user collectively, so that each service providing server independently builds a database and manages the user information of each user. You don't have to. Also, for users,
Only by specifying the user identifier and the server identifier, services can be provided from a plurality of service providing servers, and it is possible to eliminate the trouble of repeatedly inputting user information for each service providing server. In this case, the user authentication, that is, the operation of confirming whether or not the registered user is a physically existing person can be collectively performed in the user database server, so that each service can be provided. The server does not need to perform a unique operation for user authentication, such as storing a predetermined authentication key on a floppy (registered trademark) disk or the like and mailing it to the user's address, thereby reducing costs. .

[0010] Further, the present invention is characterized in that there is provided updating means for updating the user database based on a user identifier and user information transmitted via a network.

Accordingly, even when the user information of the user is changed due to, for example, moving or marriage of the user, the user information used when each service providing server provides the service is collectively stored in the user database server. Can be changed. Therefore, the user can change the user information in all the service providing servers by inputting the changed user information only once, and it is possible to save the trouble of the user's input.

Another aspect of the present invention is characterized in that a user information acquiring means for acquiring user information associated with a server identifier of one information providing server from the user database server via a network. User information acquisition device.

Further, another aspect of the present invention comprises a database updating means for updating a unique user database installed in the one information providing server based on the user information acquired by the user information acquiring means. It is characterized by the following.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a user database server according to an embodiment of the present invention will be described in detail with reference to the drawings. FIG. 1 is a schematic diagram illustrating a configuration of a network according to the present embodiment.

In FIG. 1, a user database server 1, a service providing server 2, and a client terminal 3
Are connected to the Internet 4 via communication devices 11, 21, 31 such as routers and terminal adapters, respectively. The user database server 1 and the service providing server 2 have a function as a Web server as described later, whereby the client terminal 3 operated by the user is connected to the user database server 1 and the service providing server 2 via the Internet 4. You have access to it. As shown in FIG. 1, the user database server 1 and the service providing server 2 are connected to each other via a network 5 such as a dedicated line.

FIG. 2 is a diagram showing an example of a hardware configuration of the user database server 1 in the present embodiment. User database server 1 in the present embodiment
Is composed of a general network server computer, a personal computer, and the like. As shown in FIG. 2, a central processing unit (CPU) 12, an input device 13 such as a keyboard and a mouse, and a display such as a display. The apparatus includes a device 14, a storage device including a ROM 15, a RAM 16, and a hard disk 17, and a communication interface 18. The connection to the Internet 4 and the transmission and reception of data to and from the client terminal 3 are performed via the communication interface 18, and the connection to the dedicated line 5 (the service providing server 2) and the data to and from the service providing server 2 Is also transmitted and received via the communication interface 18. Since the user database server 1 only needs to have a function of connecting to the Internet 4 and the service providing server 2 and communicating with the client terminal 3 and the service providing server 2, for example, the above-described input device 13 and display device 14 Not a required element.

Storage device 1 of user database server 1
In 5-17, C in cooperation with OS (Operating System)
A computer program code for giving instructions to the PU 12 and performing predetermined processing is stored. This computer program is executed by being loaded into the RAM 16. The computer program includes a program started in response to a request from the client terminal 3, for example, a CGI (Common Gateway Interface).
face) The program 171 is included and this is the CPU
User registration means 1 described later by cooperating with
21, each unit such as a server registration unit 122 and an updating unit 123 is configured, and predetermined processing is performed.

Further, the computer program includes:
A program for functioning as a Web server is also included, so that the user database server 1
Functions as a b server. The functions described above may be realized by one computer, or may be realized by cooperating a plurality of computers.

Further, the hard disk 17 of the user database server 1 has an HTML (Hyper Text Markup Language) describing information to be provided to the client terminal 3.
A file 172 is also stored. Web pages such as a registration page, a confirmation page, a login page, and an update page, which will be described later, are configured by the HTML file 172 or the HTML code created by the CGI program 171. That is, the client terminal 3
If there is a request to obtain information from
The L file 172 or the HTML code is output to the client terminal 3, and the information described in the HTML file 172 or the HTML code is output to the client terminal 3.
Will be displayed in the browser window.

Further, the hard disk 17 of the user database server 1 stores a user database 173 in which user information used when providing services in the service providing server 2 is registered. In the user database 173, the user information of each user includes a user identifier uniquely determined for the user and the service providing server 2 to which the user is provided with the service.
Is registered in association with a server identifier that specifies FIG. 3 shows an example of the structure of such a user database 173. As shown in FIG. 3, the user database 173 in the present embodiment includes a user ID as a user identifier, a password, an authentication key, a service providing server name as a server identifier, a name, an address, a telephone number as user information, An e-mail address is registered.

Further, the hard disk 17 of the user database server 1 stores a server list 174 in which a list of service providing servers collectively managed by the user database server according to the present invention is registered. FIG. 4 shows an example of such a server list. As shown in FIG. 4, in the present embodiment, a list of names of the service providing servers 2 that are collectively managed by the user database server 1 is used as the server list 174.

FIG. 5 is a diagram showing an example of a hardware configuration of the service providing server 2 in the present embodiment. The service providing server 2 according to the present embodiment is configured by a general network server computer, a personal computer, or the like, and as shown in FIG. 5, a central processing unit (CPU) 22 and an input such as a keyboard and a mouse. Device 23, a display device 24 such as a display, and R
A storage device including an OM 25, a RAM 26, and a hard disk 27, and a communication interface 28 are provided. The connection to the Internet 4 and the transmission and reception of data to and from the client terminal 3 are performed via the communication interface 28. The connection to the dedicated line 5 (user database server 1) and the data to and from the user database server 1 Is also transmitted and received via the communication interface 28. Since the service providing server 2 only needs to have a function of connecting to the Internet 4 and the user database server 1 and communicating with the client terminal 3 and the user database server 1, for example, the input device 23 and the display device 24 described above are Not a required element.

The storage devices 25 to 2 of the service providing server 2
7, a computer program code for giving instructions to the CPU 22 and the like in cooperation with the OS and performing predetermined processing is stored. This computer program
This is executed by being loaded into the RAM 26. The computer program includes a program module 271 as a user information acquisition device, which cooperates with the CPU 22 to configure a unit such as a user information acquisition unit 221 described later, and performs predetermined processing.

Further, the computer program includes:
A program for functioning as a Web server is also included, whereby the service providing server 2 functions as a Web server. The functions described above may be realized by one computer, or may be realized by cooperating a plurality of computers.

Further, the hard disk 27 of the service providing server 2 also stores an HTML file 272 describing information to be provided to the client terminal 3, and these HTML files 272 constitute a predetermined Web page. That is, when there is a request to acquire information from the client terminal 3, these HTML files 272 are output to the client terminal 3,
Information described in the TML file 272 is displayed in a browser window or the like of the client terminal 3. Thus, the user can receive various services from the service providing server 2.

FIG. 6 is a diagram showing an example of a hardware configuration of the client terminal 3 in the present embodiment. The client terminal 3 is configured by a general personal computer or the like, and as shown in FIG. 6, a central processing unit (CPU) 32, an input device 33 such as a keyboard and a mouse, and a display device such as a display. 34 and ROM3
5, a storage device including a RAM 36 and a hard disk 37, and a communication interface 38. The connection to the Internet 4 and the transmission and reception of data between the user database server 1 and the service providing server 2 are performed via the communication interface 38.

The storage devices 35 to 37 of the client terminal 3
Stores a computer program code for giving instructions to the CPU 32 and the like in cooperation with the OS and performing predetermined processing. This computer program is called R
This is executed by being loaded into the AM 36. This computer program includes a program (browser or the like) 371 for browsing a Web site.
The user can make a request for obtaining information to a predetermined Web site via a browser or the like activated by the program 371 and receive various information.

Next, a process for registering user information in the user database 173 of the user database server 1 according to the present invention will be described. FIG. 7 is a flowchart showing the flow of processing when registering user information in the user database 173.

First, a user operating the client terminal 3 starts a browser on the client terminal 3. Then, the user accesses the Web site of the user database server 1 via the browser, and requests acquisition of a predetermined HTML file stored in the user database server 1 (step 1).

The user database server 1 that has received this request reads, from the HTML file 172 stored in the hard disk 17 of the user database server 1,
A corresponding HTML file (an HTML file constituting a registration page described below) is returned to the client terminal 3 (step 2).

The browser of the client terminal 3 uses the above HT
Upon receiving the ML file, a registration page P1 shown in FIG. 8 is displayed on the browser window of the client terminal 3 (step 3). As shown in FIG. 8, the registration page P1 includes fields F11 to F17, a transmission button B11 for transmitting a value input in each field to the user database server 1, and a button B12 for clearing the value of each field. Contains. The field F is a field F for inputting a user ID as a user identifier.
11. Password input fields F12 and F1
3. A field F14 for inputting the user's name, a field F15 for inputting the user's address, a field F16 for inputting the user's telephone number, and a field F17 for inputting the user's e-mail address are provided.

In such a registration page P1, the user uses the input device 33 of the client terminal 3 to enter the user ID, password, and user name, address, telephone number, and e-mail address used as user information, respectively. Input is made to the corresponding fields F11 to F17 (step 4). Then, the user presses the send button B11.
When the button is clicked, a request is transmitted to the user database server 1 via the browser (step 5).
The send button B11 is used for the user database server 1
URL corresponding to the CGI program 171 in the
m Resource Locator), and in the user database server 1 receiving the request, the program 1
71 is activated (step 6). The values entered in the fields F11 to F17 of the registration page P1 are as follows:
By a method such as being added to the URL as an argument,
Passed to the above program.

When the program 171 is started, first,
The value passed to the program, that is, the value input to the fields F11 to F17 of the registration page P1 is obtained (step 7). Note that the acquired fields F11 to F11
The value of F17 is stored in the RAM 16 of the user database server 1.
Alternatively, it is stored in the hard disk 17 (step 8).
Then, it is checked whether the same user ID as the input user ID is registered in the user database 173 (step 9). If the same user ID is already registered, a predetermined HTML code is added. It is created and output to the client terminal 3 to inform the user that it should be registered with a different user ID (step 1).
0). If the same user ID does not exist, an HTML code constituting a confirmation page described below is created, and this HTML code is output to the client terminal 3 (step 11).

The browser of the client terminal 3 uses the above HT
Upon receiving the ML code, a confirmation page P2 shown in FIG. 9 is displayed on the browser window of the client terminal 3 (step 12). As shown in FIG. 9, the confirmation page P2 includes a user ID and user information entered by the user on the registration page P1, a registration button B21 for registering the user ID and user information in the user database server 1, And a button B22 for returning to the registration page P1.

When the user clicks the registration button B21 using the input device 33 of the client terminal 3, a request is transmitted to the user database server 1 via the browser (step 13). This registration button B2
1 is linked to a URL corresponding to the CGI program 171 in the user database server 1, and the program 171 is started in the user database server 1 that has received the request (step 14).

When the program 171 is started, in step 8 described above, the R
The user I stored in the AM 16 or the hard disk 17
An authentication key is issued for D, the password, and the user information (step 15). This authentication key is issued using an existing authentication technology. Then, these user ID, password,
The user information and the authentication key are stored in the user database 173.
(Step 16). These passwords,
The user information and the authentication key are registered in association with a user ID that is a user identifier. Then, the specified HT
The ML code is created and output to the client terminal 3 to inform the user that the registration of the user information is completed (step 17). The authentication key is passed to the user by physical means, such as storing it on a floppy disk and mailing it to the user's address. Thus, the user authentication is performed by the user database server 1.
Therefore, it is not necessary for each service providing server 2 to perform the work for user authentication independently, and the cost can be reduced.

Next, a description will be given of a process of registering a service providing server to which a user is provided with a service in the user database 173 after the registration of the user information. FIG. 10 is a flowchart showing the flow of processing when the service providing server is registered in the user database 173.

The user who has received the above authentication key,
The user accesses the Web site of the user database server 1 via the browser started on the client terminal 3 and requests acquisition of a predetermined HTML file stored in the user database server 1 (step 2).
1).

Upon receiving this request, the user database server 1 converts the corresponding HTML file (HTML file constituting the login page described below) from the HTML file 172 stored on the hard disk of the user database server 1 to the client terminal. 3 is returned (step 22).

The browser of the client terminal 3 uses the above HT
Upon receiving the ML file, a login page P3 shown in FIG. 11 is displayed on the browser window of the client terminal 3 (step 23). This login page P3
As shown in FIG. 11, it includes fields F31 to F33, a transmission button B31 for transmitting a value input to each field to the user database server 1, and a button B32 for clearing the value of each field. The fields include a field F31 for inputting a user ID as a user identifier, a field F32 for inputting a password, and a field F33 for inputting an authentication key.

The user uses the input device 33 of the client terminal 3 to enter the user ID, the password, and the issued authentication key in the corresponding fields F31 to F3.
3 (step 24). Then, when the user clicks the send button B31, a request is sent to the user database server 1 via the browser (step 25). The send button B31 is linked to the URL corresponding to the CGI program 171 in the user database server 1, and the program 171 is activated in the user database server 1 that has received the request (step 26). The values entered in the fields F31 to F33 of the login page P3 are SSL
(Secure Socket Layer), etc., and passed to the above program while security is ensured.

When this program is started, first, the value passed to the program, that is, the value input to the fields F31 to F33 of the login page P3 is obtained (step 27). The acquired field F31
The values of F33 are stored in the RAM1 of the user database server 1.
6 or the hard disk 17 (step 2
8). Then, it is determined whether the input user ID, password, and authentication key are valid, that is, whether the entered user ID, password, and authentication key are registered in the user database 173 (step 29). Is a given HT
The ML code is created and output to the client terminal 3 to inform the user that the login has failed (step 30). If the server is valid, a list of service providing servers is obtained from the server list 174 (step 31). Then, an HTML code constituting an operation page described below is created, and the created HTML code is output to the client terminal 3 (step 32).

The browser of the client terminal 3 uses the above HT
Upon receiving the ML code, an operation page P4 shown in FIG. 12 is displayed on the browser window of the client terminal 3 (step 33). As shown in FIG. 12, the operation page P4 includes a check box group C41 in which the service providing servers 2 registered in the server list 174 are displayed in a selectable manner, and a service providing server selected by the check box group C41. A registration button B41 to be transmitted to the database server 1 and a change button B42 for changing user information are included.

In such an operation page P4, the user uses the input device 33 of the client terminal 3 to select a check box corresponding to the service providing server to receive the service (step 34). And
When the user clicks the registration button B41, a request is transmitted to the user database server 1 via the browser (Step 35). This registration button B41 is
CGI program 17 in user database server 1
1. The user database server 1 receiving the above request links the program 17
1 is started (step 36). The value selected in the check box group C41 of the operation page P4 is passed to the program by a method such as being added to the URL as an argument.

When the program 171 is started, first,
The value passed to the program, that is, the service providing server selected in the check box group C41 of the operation page P4 is obtained (step 37). Then, the server registration means 122 causes the above-described login page P3
Is searched from the user database 173, and the service providing server selected on the operation page P4 is registered in the searched record (step 38). Thereafter, a predetermined HTML code is created and output to the client terminal 3 (step 39), and the user is notified that the registration has been completed.

When a user accesses a Web site of the service providing server 2 via the browser of the client terminal 3 and receives a service from the service providing server 2, it may be necessary to obtain user information. . In such a case, the program module 271 as the user information acquisition device of the service providing server 2 is activated, and the user information acquisition means 221 configured thereby acquires user information from the user database 173 of the user database server 1.

The user information obtaining means 221 connects to the user database 173 of the user database server 1 via the dedicated line 5 and obtains user information associated with the server identifier of the service providing server from the user database 173. That is, the user database 173 of the user database server 1 is searched using the service providing server name as a server identifier as a key, and the user information of the user receiving the service from the service providing server 2 is obtained. The obtained user information can be used when the service providing server provides a service. As described above, since the user database server 1 can collectively manage the user information of each user collectively, each service providing server 2 independently builds a database and manages the user information of each user. You don't have to.

Here, for example, when the user information of the user is changed due to the moving or marriage of the user,
User database 17 of user database server 1
3 needs to be updated with new user information. In that case, the processing is performed as follows. FIG. 13 is a flowchart showing the flow of processing when updating the user information registered in the user database 173.

When the user wants to update the user information, he or she clicks the above-mentioned change button B42 on the operation page P4. When the change button B42 is clicked,
A request is transmitted to the user database server 1 via the browser (Step 41). This registration button B
Reference numeral 42 is linked to a URL corresponding to the CGI program 171 in the user database server 1, and the user database server 1 receiving the request starts the program 171 (step 42).

When the program 171 is started, the user ID and the password stored in the RAM 16 or the hard disk 17 of the user database server 1 are obtained in the above-mentioned step 28 (step 43), and based on this, an update page described below is obtained. Is generated, and the HTML code is output to the client terminal 3 (step 44).

The browser of the client terminal 3 uses the above HT
Upon receiving the ML code, an update page P5 shown in FIG. 14 is displayed on the browser window of the client terminal 3 (step 45). As shown in FIG. 14, the update page P5 includes fields F51 to F54, a transmission button B51 for transmitting a value input to each field to the user database server 1, and a button B52 for clearing the value of each field. Contains. In each field, the current user information is displayed in a state where it is input in advance.

In such an update page P5, the user uses the input device 33 of the client terminal 3 to input new user information into the corresponding fields F51 to F54 (step 46). Then, when the user clicks the send button B51, a request is sent to the user database server 1 via the browser (step 47). The transmission button B51 is a button for the UR corresponding to the CGI program 171 in the user database server 1.
L, the program 171 is started in the user database server 1 that has received the request (step 48). The values input to the fields F51 to F54 of the update page P5 are passed to the program by a method such as being added to the URL as an argument.

When the program 171 is started, first,
The value passed to the program, that is, the value input to the fields F51 to F54 of the update page P5 is obtained (step 49). Then, the user database 173 is updated based on the user information changed by the updating unit 123.
Is updated (step 50). After that, the specified HTM
L code is created and this is the client terminal 3
To inform the user that the update of the user information is completed (step 51).

As described above, even when the user information of the user is changed due to, for example, moving or marriage of the user, the user information used when each service providing server 2 provides the service is stored in the user database server 1.
Can be changed collectively. Therefore,
The user only needs to enter the changed user information once,
The user information in all the service providing servers 2 can be changed, and it is possible to save the trouble of user input.

Although one embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment, and may be implemented in various forms within the scope of the technical idea. Hereinafter, examples of these different modes will be described.

In the above-described embodiment, a case has been described in which the service providing server 2 does not independently provide a database storing user information. However, such a database may be provided independently in each service providing server 2. . In this case, database updating means for updating the database is constituted by the program module. This database updating means,
The database is updated based on the user information obtained by the user information obtaining means 221.

In the above-described embodiment, an example has been described in which the Internet 4 is used as a network between the client terminal 3 and the user database server 1 and the service providing server 2. However, the present invention is not limited to this. It goes without saying that the present invention can be applied. Also, an example in which the dedicated line 5 is used as the network between the user database server 1 and the service providing server 2 has been described.
The connection may be made using the Internet after security is secured by a dual private network.

In the above embodiment, the user database server 1 and the service providing server 2
The case of the server b has been described, but the present invention is not limited to this, and any server may be used as long as it can communicate with the client terminal 3. It should be noted that the illustrated hardware configuration, database configuration, and web page configuration are examples, and the present invention is not limited to these.

[0059]

As described above, according to the present invention, it is possible to collectively manage the user information of each user collectively in the user database server, so that each service providing server has its own database. There is no need to construct and manage user information of each user. In addition, a user can receive a service from a plurality of service providing servers simply by specifying a user identifier and a server identifier, thereby eliminating the need to input user information for each service providing server. Becomes Further, in this case, the work for user authentication can be collectively performed in the user database server in a lump, so that it is not necessary for each service providing server to perform work for user authentication independently. Can be reduced.

Further, even when the user information of the user is changed due to, for example, moving or marriage of the user, the user information used when each service providing server provides the service is collectively stored in the user database server. It can be changed. Therefore, the user can change the user information in all the service providing servers by inputting the changed user information only once, and it is possible to save the trouble of the user input.

[Brief description of the drawings]

FIG. 1 is a schematic diagram illustrating a configuration of a network according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating an example of a hardware configuration of a user database server according to an embodiment of the present invention.

FIG. 3 is a diagram illustrating an example of a structure of a user database stored in a storage device of a user database server according to an embodiment of the present invention.

FIG. 4 is a diagram illustrating an example of a service providing server list stored in a storage device of a user database server according to an embodiment of the present invention.

FIG. 5 is a block diagram illustrating an example of a hardware configuration of a service providing server according to an embodiment of the present invention.

FIG. 6 is a block diagram illustrating an example of a hardware configuration of a client terminal according to an embodiment of the present invention.

FIG. 7 is a flowchart showing a flow of processing when registering user information in a user database according to an embodiment of the present invention.

FIG. 8 is a diagram illustrating an example of a registration page according to an embodiment of the present invention.

FIG. 9 is a diagram illustrating an example of a confirmation page according to an embodiment of the present invention.

FIG. 10 is a flowchart showing the flow of processing when a service providing server is registered in a user database in one embodiment of the present invention.

FIG. 11 is a diagram illustrating an example of a login page according to an embodiment of the present invention.

FIG. 12 is a diagram illustrating an example of an operation page according to an embodiment of the present invention.

FIG. 13 is a flowchart showing a flow of processing when updating user information registered in a user database according to an embodiment of the present invention.

FIG. 14 is a diagram illustrating an example of an update page according to an embodiment of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 User database server 2 Service providing server 3 Client terminal 4 Internet 5 Dedicated line 11, 21, 31 Communication device 12, 22, 32 Central processing operation unit 13, 23, 33 Input device 14, 24, 34 Display device 15, 25, 35 ROM 16, 26, 36 RAM 17, 27, 37 Hard disk 18, 28, 38 Communication interface 121 User registration means 122 Server registration means 123 Update means 171 CGI program 172, 272 HTML file 173 User database 174 Server list 221 User information acquisition Means 271 Program module

Claims (4)

[Claims] 1. A service providing server that provides a service to a user via a network, wherein the user information of the user is used when providing the service.
A user identifier uniquely determined for the user,
A user database that stores a server identifier that specifies a service providing server to which the user is receiving a service in association with each other; and a user identifier that transmits a user identifier and user information transmitted via a network in association with each other in the user database. A user database server comprising: a user registration unit for registering; and a server registration unit for registering the server identifier transmitted via the network in the user database in association with the user identifier transmitted via the network. . 2. The user database server according to claim 1, further comprising updating means for updating the user database based on a user identifier and user information transmitted via a network. 3. A user information acquiring means for acquiring, via a network, user information associated with a server identifier of one information providing server from the user database server according to claim 1 or 2. User information acquisition device. 4. The apparatus according to claim 3, further comprising a database updating unit that updates a user database installed in the one information providing server based on the user information acquired by the user information acquiring unit. User information acquisition device.