JP6510258B2 - User attribute information management system and user attribute information management method - Google Patents

Description

  The present invention relates to a user attribute information management system and a user attribute information management method.

  BACKGROUND Conventionally, there is known a distribution system of user attribute information that manages and distributes user attribute information. For example, as shown in FIG. 24, the conventional user attribute information distribution system 1000 includes a Web server 200A of a service provider, a Web server 200B of another service provider holding attribute information of a user, and respective services. It comprises a user terminal 300 which uses a provider's service, a telecommunications carrier's access network, and a communication network N0 such as the Internet. Here, the Web server of each service provider and the terminal of the user are connected to a communication network.

  The user has performed user registration necessary for using the service provided by the other service provider in the web server 200B of the other service provider, and the other service provider is registered when the user is registered. The attribute information of the user is acquired. The attribute information includes, for example, information necessary for the other service provider to provide the user with a service, such as the address, telephone number, credit card number, and mail address of the user. On the other hand, in order for the user to use the service provided by the service provider, user registration is required, but the attribute information of the user registered at that time is held by the other service provider. Acquire from attribute information.

  For that purpose, the service provider and the other service provider have previously formed a partnership for distributing the attribute information of the user between the service provider and the other service provider. The service provider makes an application to the other service provider in advance, and acquires the permission for performing the procedure when the web server 200A of the service provider accesses the web server 200B of the other service provider. When distributing the attribute information of the user, a standardized authorization protocol such as OAuth is used between the service provider and the other service provider.

  FIG. 25 is a configuration diagram for describing the operation of each component of the conventional user attribute information distribution system. When the user uses the service of the Web server 200B of another service provider, the user has registered his / her attribute information (see (0) in FIG. 25). When a user performs user registration in the service provider's Web server 200A, the service provider's Web server 200A acquires the access right to another service provider's Web server 200B whose attribute information has been registered. To give instructions (see (1) in FIG. 25).

  The service provider's Web server 200A redirects to the other service provider's Web server 200B in order to obtain user attribute information necessary for providing the service when performing user registration, Authorization of the access right to the service provider of (see (2) in FIG. 25). Furthermore, after user authorization, the authorization code acquired from the web server 200B of the other service provider is sent to the web server 200B of the other service provider, and the access right to the web server 200B of the other service provider is obtained. The access token is exchanged (see (4) in FIG. 25). Then, using the application interface defined by the Web server 200B of the other service provider, using the access token as a parameter, the user's attribute information is acquired from the Web server 200B of the other service provider ((5 )reference).

  When the web server 200B of another service provider is redirected from the web server 200A of the service provider, the web server 200B confirms to the user whether the user's attribute information may be distributed to the web server 200A of the service provider. Then, the service provider Web server 200A is redirected again with the result (see (3) in FIG. 25).

  The signal sequence of the conventional distribution system of user attribute information is as shown in FIG. First, after the user terminal 300 accesses the portal site of the Web server 200B of another service provider from the user terminal 300 in order to use the service provided by the other service provider (step S1, 2), the user registration is performed. (Steps S3 and 4). At the time of user registration, the user transmits his / her attribute information such as a name, an e-mail address, and a credit card number to other service providers.

  The user makes a user registration request after accessing the portal site of the web server 200A of the service provider from the user terminal 300 in order to use the service provided by the service provider (step S5, 6) (step S7) . At this time, the user instructs the Web server 200A of the service provider to acquire an access right to the attribute information management server.

  After the service provider's Web server 200A having received the user registration request issues the user's account name (step S8), in order to ask the user for permission to access the other service provider's Web server 200B, The user registration request is redirected to the web server 200B of another service provider (step S9). Then, the Web server 200B of the other service provider transmits a response to the redirect to the user terminal 300 (step S10).

  When the user who receives the response from the web server 200B of the other service provider logs in to the web server 200B of the other service provider (step S11), the web server 200B of the other service provider It asks the user whether to grant the access right to the web server 200B to the web server 200A of the service provider (step S12).

  When the user grants the access right (step S13), the web server 200B of the other service provider redirects to the web server 200A of the service provider with the authorization code as a parameter (step S14).

  The service provider Web server 200A transmits an access token request including the authorization code to the other service provider Web server 200B (step S15), and obtains an access token indicating the access right in exchange for the authorization code ((S15). Step S16). Further, when the expiration date of the access token has passed, a refresh token for updating the access token is also acquired (step S16).

  The service provider Web server 200A uses an interface defined in advance by another service provider, uses the access token as a parameter, and requests acquisition of user attribute information from the other service provider Web server. It transmits to 200B (step S17), and acquires user's attribute information required for user registration from Web servers 200B of other service providers (step S18). Thereafter, the Web server 200A of the service provider performs user registration based on the acquired attribute information of the user, and sends a user registration response to the user (step S19).

  As described above, when the user terminal 300 registers a user in the web server 200A of the service provider, the web server 200A of the service provider of the particular other service provider holding the attribute information of the user By acquiring the access right to the Web server 200B, the attribute information of the user necessary for providing the service is acquired from the Web server 200B of the other service provider, and the service is provided to the user terminal 300.

  After the user registers with the web server 200A of the service provider, the user changes the registered attribute information of the web server 200B of the specific other service provider that holds the attribute information of the user. May. FIG. 27 is a configuration diagram for describing the operation of each component of the conventional user attribute information distribution system when the web server 200A of the service provider follows the change of the attribute information.

  The user changes a part of his / her attribute information registered in the web server 200B of another service provider (see (0) in FIG. 27).

  The service provider Web server 200A uses the access token to update the attribute information acquired at the time of user registration to the attribute information after the change, and the Web server 200B of the other service provider periodically uses the access token. Attribute information is acquired and the presence or absence of a change is confirmed (refer (2) of FIG. 27). At this time, when the access token has expired, the Web server 200A of the service provider transmits a refresh token to the Web server 200B of the other service provider to update the access token. (See (1) in FIG. 27).

  When the web server 200B of the other service provider receives the refresh token from the web server 200A of the service provider, it transmits the updated access token to the web server 200A of the service provider (see (1) in FIG. 27). .

  The signal sequence of the conventional user attribute information distribution system when the web server 200A of the service provider follows the change of the user attribute information is as shown in FIG.

  The user accesses the portal site of the Web server 200B of the other service provider from the user terminal 300 (steps S20 and S21), and one of his / her attribute information registered in the Web server 200B of the other service provider. The set is changed (steps S22 and S23).

  The service provider Web server 200A makes an access token request to the other service provider Web server 200B together with the refresh token in order to update the access token (step S24). When the web server 200B of the other service provider receives the refresh token from the web server 200A of the service provider, the updated access token is transmitted to the web server 200A of the service provider (step S25). Also, when the expiration date of the access token has passed, a refresh token for updating the access token is also transmitted (step S25).

  The service provider's Web server 200A uses an interface defined in advance by another service provider, using the updated access token as a parameter, to request acquisition of user attribute information from the other service provider. It transmits to the web server 200B (step S26), and acquires user attribute information necessary for user registration from the web server 200B of another service provider (step S27).

  The Web server 200A of the service provider compares the acquired attribute information with the stored attribute information to confirm the presence or absence of a difference (step S28). If there is a difference (Yes at Step S28), the held attribute information is updated to the acquired attribute information (Step S29). Thereafter, after a certain period of time has elapsed, the process returns to step S15 (step S30), and the process is executed. If there is no difference (No at step S28), the process returns to step S15 after a certain period of time (step S30), and the process is executed.

  According to the above method of distributing user attribute information, the Web server 200A of the service provider periodically acquires the attribute information of the user from the Web server 200B of the other service provider, and holds the acquired attribute information. By confirming the difference, when the user's attribute information is changed, the held attribute information is followed and updated.

OAuth 2.0, [online], [August 22, 2014 search], Internet <http://oauth.net/2/>

  However, in the above-described conventional technique, when the server follows the change of the user's attribute information in the apparatus managing the attribute information, it is difficult to appropriately reflect the change of the user's attribute information to the following server .

  Specifically, the web server of the service provider periodically uses the access token to check the presence or absence of a change in the attribute information of the user acquired at the time of user registration from the web server of another service provider. It is necessary to obtain attribute information of Therefore, at the time of user registration, the web servers of all the service providers who have acquired user attribute information from the web server of the other service provider are the attributes of the user registered from the web server of the other service provider. Since the information is acquired regularly, the processing amount of the Web server of the other service provider increases. Therefore, the Web server of the other service provider requires a large amount of processing power, and the cost of installing the Web server of the other service provider becomes expensive.

  When a user who has registered as a user on the service provider's Web server changes his / her attribute information such as an address on another service provider's Web server, his / her attribute information after the change is the service provider's In order to be reflected in the web server, it is necessary for the web server of the service provider to obtain the attribute information of the user from the web server of the other service provider and to confirm the presence or absence of the change. Since the Web server of the service provider periodically acquires the attribute information of the user from the Web server of the other service provider, the service provider may obtain the attribute information of the user if the cycle is long. It takes a long time to reflect the changed attribute information of the user on the Web server of. Therefore, the user may not receive the service of the service provider's Web server such as a home delivery service according to his / her latest attribute information such as the address, and the convenience of the user may be deteriorated.

  Therefore, the present invention has been made to solve the above-described problems of the prior art, and relates to a server that follows a server following a change in user's attribute information in a device that manages attribute information. The purpose is to properly reflect changes in user attribute information.

  In order to solve the problems described above and achieve the purpose, the user attribute information management system provides a service to an attribute information management apparatus that manages attribute information of a user and a user terminal in which user information including predetermined attribute information is registered. User attribute information management system having a server for providing information, wherein the attribute information management device includes a storage unit for storing attribute information, a changing unit for changing the attribute information, and the attribute information by the changing unit. A notification unit for notifying the server of a change in the attribute information when changed, and a transmission unit for transmitting the attribute information requested by the server to the server, the server including the attribute information management device When a notification of change of attribute information is received, a request unit that requests at least a part of the attribute information for which the notification has been received from the attribute information management device, and the request If it is received the requested attribute information by, characterized in that it comprises an updating unit that updates the user information based on the attribute information.

  According to the present invention, when the server follows the change of the user's attribute information in the apparatus managing the attribute information, the change of the user's attribute information can be appropriately reflected on the following server.

FIG. 1 is a system configuration diagram showing an entire configuration of a user attribute information management system according to the first embodiment. FIG. 2 is a block diagram showing the configuration of the attribute information management server according to the first embodiment. FIG. 3 is a diagram showing an example of a table stored in the attribute information storage unit. FIG. 4 is a diagram showing an example of a table stored in the profile information storage unit. FIG. 5 is a block diagram showing the configuration of the web server according to the first embodiment. FIG. 6 is a diagram for explaining the flow of update processing of user attribute information in the user attribute information management system according to the first embodiment. FIG. 7 is a sequence diagram for explaining the flow of user attribute information management processing in the user attribute information management system according to the first embodiment. FIG. 8 is a diagram showing an example of screen display displayed on the user terminal. FIG. 9 is a diagram for explaining an overview of the user attribute information management system according to the first embodiment. FIG. 10 is a diagram for explaining the flow of registration of user attribute information in the user attribute information management system according to the first embodiment. FIG. 11 is a diagram for explaining the flow of addition of user attribute information in the user attribute information management system according to the first embodiment. FIG. 12 is a system configuration diagram showing an overall configuration of a user attribute information management system according to the second embodiment. FIG. 13 is a block diagram showing the configuration of the attribute information management server according to the second embodiment. FIG. 14 is a diagram showing an example of a table stored in the web server information storage unit. FIG. 15 is a block diagram showing the configuration of the leased line information management server according to the second embodiment. FIG. 16 is a diagram showing an example of a table stored in the leased line information storage unit. FIG. 17 is a diagram for explaining the flow of a process of updating user attribute information in the user attribute information management system according to the second embodiment. FIG. 18A is a sequence diagram for explaining the flow of user attribute information management processing in the user attribute information management system according to the second embodiment. FIG. 18B is a sequence diagram for explaining the flow of user attribute information management processing in the user attribute information management system according to the second embodiment. FIG. 19 is a diagram for explaining the flow of update processing of user attribute information in the user attribute information management system according to the third embodiment. FIG. 20 is a block diagram showing a configuration of a user terminal according to the third embodiment. FIG. 21 is a sequence diagram for explaining the flow of user attribute information management processing in the user attribute information management system according to the third embodiment. FIG. 22 is a diagram for explaining an overview of a user attribute information management system according to the third embodiment. FIG. 23 is a diagram showing a computer that executes a user attribute information management program. FIG. 24 is a diagram showing an outline of a conventional user attribute information distribution system. FIG. 25 is a configuration diagram for describing the operation of each component of the conventional user attribute information distribution system. FIG. 26 is a sequence diagram for explaining the flow of processing of a conventional user attribute information distribution system. FIG. 27 is a configuration diagram for describing the operation of each component of the conventional user attribute information distribution system when following a change in user attribute information. FIG. 28 is a sequence diagram for explaining the flow of processing of a conventional user attribute information distribution system when following change of user attribute information.

First Embodiment
In the following embodiment, the configuration of the user attribute information management system, the configuration of the attribute information management server, the configuration of the Web server, and the flow of processing in the user attribute information management system according to the first embodiment will be described in order. The effects of the first embodiment will be described.

[Configuration of User Attribute Information Management System According to First Embodiment]
First, the user attribute information management system according to the first embodiment will be described with reference to FIG. FIG. 1 is a system configuration diagram showing an entire configuration of a user attribute information management system according to the first embodiment.

  As shown in FIG. 1, the user attribute information management system 100 has an attribute information management server 10 which is an attribute information management device, Web servers 20A and 20B of a plurality of service providers, and a user terminal 30, and a communication network N Are connected to each other. The number of devices shown in FIG. 1 is merely an example, and the present invention is not limited to this. Further, the Web servers 20A and 20B will be described as the Web server 20 in the description without particular distinction. In the following, for example, a case where the user is registered in advance based on attribute information and a profile stored in the attribute information management server 10 will be described as an example.

  The attribute information management server 10 is connected to a communication network N such as an access network of a telecommunications carrier or the Internet, and the user stores and centrally manages his / her attribute information with respect to the user terminal 30, Helps you use your own attribute information when using Web services.

  In addition, when the user changes his / her registered attribute information from the portal site of the attribute information management server 10, the attribute information management server 10 identifies the Web server 20 of the service provider who provides the attribute information, Notification of the change of the attribute information and the service to the Web server 20 of the service provider that follows the change of the attribute information in the Web server 20 of the specified service provider, based on the permission of the user A request for credentials to secure the authenticity of the provider's Web server 20 is made. Then, the changed attribute information is provided to the Web server 20 of the service provider whose authenticity has been confirmed.

  Further, when holding attribute information of the user, the attribute information management server 10 issues an ID for identifying the user and manages the ID. The attribute information of the user registered in the attribute information management server 10 and the attribute information of the user registered in the Web server 20 of the service provider are managed in association with the ID.

  In addition, the service provider's Web server 20 is provided with the user's attribute information necessary for the service provider to provide the service under the approval of the user. As for the attribute information of the user provided to the service provider, a profile is created and managed for each account paid out when the user registers with the web server 20 of the service provider, and the user is provided to the service provider View and confirm the attribute information of the account.

  The web servers 20A and 20B of the plurality of service providers are servers that provide services to the user terminal 30. When the Web server 20A, 20B of the service provider receives the notification of the change of the attribute information from the attribute information management server 10, it requests at least a part of the attribute information for which the notification has been received from the attribute information management server 10 When the received attribute information is received, the user information is updated using the changed attribute information.

  The user terminal 30 is an information processing apparatus used by a user. The user terminal 30 registers its own attribute information in the attribute information management server 10, and browses or changes the attribute information. In addition, the user terminal 30 authorizes the distribution of the attribute information after the change to the Web server 20 of the service provider who follows the change of the attribute information of the user terminal 30.

[Configuration of attribute information management server]
Next, the configuration of the attribute information management server 10 shown in FIG. 1 will be described using FIG. FIG. 2 is a block diagram showing the configuration of the attribute information management server according to the first embodiment. As shown in FIG. 2, the attribute information management server 10 includes a communication processing unit 11, a control unit 12, a storage unit 13, and a GUI processing unit 14. The processing of each of these parts will be described below.

  The communication processing unit 11 controls communication regarding various information exchanged with the Web server 20 and the user terminal 30 connected.

  The GUI processing unit 14 is an interface when the user registers, changes, deletes, and browses his / her attribute information in the attribute information management server 10, and an interface when browsing his / her attribute information provided to each Web server 20. Perform processing to provide to the user.

  The storage unit 13 stores data and programs necessary for various processes performed by the control unit 12, and particularly, those closely related to the present invention include an attribute information storage unit 13a and a profile information storage unit 13b.

  The attribute information storage unit 13a stores attribute information. The attribute information stored in the attribute information storage unit 13 a is the attribute information of the user registered in advance from the portal site of the attribute information management server 10 by the user terminal 30. For example, as illustrated in FIG. 3, the attribute information storage unit 13 a uniquely identifies the user “user ID”, the user “name”, the user “birth date”, and the user “address”. , The "phone number" of the telephone owned by the user, the "credit card number" such as a credit card owned by the user, and the "e-mail address" owned by the user are stored in association with each other. For example, in the example of FIG. 3, “0aaa-bb-cccc” is stored as the attribute information “telephone number”.

  The profile information storage unit 13 b stores a profile created based on the above-described attribute information. For example, as illustrated in FIG. 4, the profile information storage unit 13 b includes the “account name” of the user and the “URL of the web server” which is information for identifying the web server 20 that is the registration destination of the attribute information. , The "name" of the user, the "telephone number" of the telephone owned by the user, and the "e-mail address" owned by the user. Here, the type of attribute information included in the profile information is different depending on the web server 20 that performs user registration.

  The control unit 12 has a program that defines various processing procedures and the like, and an internal memory for storing required data, and executes various processing by these, and particularly as closely related to the present invention, A change unit 12a, a notification unit 12b, and a transmission unit 12c are included.

  The change unit 12a changes the attribute information. Specifically, when the change unit 12a receives a change in attribute information from the user terminal 30, the change unit 12a changes the attribute information stored in the attribute information storage unit 13a according to the received attribute information.

  For example, when the change unit 12a receives a request to change the telephone number, which is one of the attribute information, to "0aaa-bb-dddd" from the user terminal 30 owned by Taro Yamada of the user ID "1", the attribute The telephone number corresponding to the user ID "1" stored in the information storage unit 13a is changed from "0aaa-bb-cccc" to "0aaa-bb-dddd". In addition, the changing unit 12a updates the profile stored in the profile information storage unit 13b, for example, based on the changed attribute information.

  The notification unit 12 b notifies the Web server 20 of the change in the attribute information when the change unit 12 a changes the attribute information. Specifically, when the change unit 12a changes the attribute information, the notification unit 12b notifies the change of the attribute information to the Web server 20 of the service provider who has authorized the user to distribute the changed attribute information. Do. For example, the notification unit 12 b notifies only the Web server 20 of the service provider selected by the user terminal 30 of the change of the attribute information.

  The transmitting unit 12 c transmits the attribute information changed by the changing unit 12 a to the Web server 20. Specifically, when the request for the attribute information notified by the notification unit 12 b is received from the Web server 20, the transmission unit 12 c transmits the attribute information changed by the change unit 12 a to the Web server 20. For example, the transmitting unit 12c transmits the attribute information changed by the changing unit 12a only to the Web server 20 of the service provider selected by the user terminal 30.

[Web server configuration]
Next, the configuration of the web server 20 shown in FIG. 1 will be described using FIG. FIG. 5 is a block diagram showing the configuration of the web server according to the first embodiment. As shown in FIG. 5, the Web server 20 includes a communication processing unit 21, a control unit 22, and a storage unit 23. The processing of each of these parts will be described below.

  The communication processing unit 21 controls communication regarding various information exchanged with the attribute information management server 10 and the user terminal 30 connected.

  The storage unit 23 stores data and programs necessary for various processes performed by the control unit 22. The storage unit 23 includes a user information storage unit 23a, which is particularly closely related to the present invention. For example, the user information storage unit 23a stores attribute information included in the profile received from the attribute information management server 10 and attribute information after change. Note that, as an example of the information stored in the user information storage unit 23a, it is the same as FIG. 4 described above.

  The control unit 22 has a program defining various processing procedures and the like, and an internal memory for storing required data, and executes various processings by these, and particularly as closely related to the present invention, It has a request unit 22a and an update unit 22b.

  When receiving a notification of change of attribute information from the attribute information management server 10, the request unit 22a requests the attribute information management server 10 for at least a part of the attribute information for which the notification has been received. Specifically, when requesting the attribute information for which the notification of the change of the attribute information has been received from the attribute information management server 10, the request unit 22a transmits a credential, which will be described later, to the attribute information management server 10. Then, when receiving the follow-up token described later from the attribute information management server 10, the request unit 22a transmits the received follow-up token to the attribute information management server 10 to request the attribute information for which the notification has been received.

  When the update unit 22 b receives the attribute information requested by the request unit 22 a, the update unit 22 b updates the user information using the attribute information.

[Process by user attribute information management system]
Here, the flow of update processing of user attribute information in the user attribute information management system 100 will be described with reference to FIG. FIG. 6 is a diagram for explaining the flow of update processing of user attribute information in the user attribute information management system according to the first embodiment.

  As shown in FIG. 6, after changing the attribute information of the user terminal 30 registered in the attribute information management server 10, the user terminal 30 selects the Web server 20 of the service provider to follow the change of the attribute information, The distribution of attribute information after change to the Web server 20 of the service provider is authorized (see (1) in FIG. 6).

  Here, when the user changes his / her attribute information, the attribute information management server 10 manages a list of web servers 20 of service providers who follow the change of the attribute information. The list is created when the service provider applies in advance to the attribute information management server 10 and acquires permission for performing a procedure for accessing the attribute information management server. When the user changes his / her attribute information, the attribute information management server 10 refers to the profile that manages the attribute information acquired by the Web server 20 of the service provider, and acquires the attribute information before the change. The provider's web server 20 is identified.

  Furthermore, the attribute information management server 10 specifies the web server 20 of the service provider that follows the change of the attribute information from the web servers 20 of the identified service provider. Then, the attribute information management server 10 notifies the Web server 20 of the identified service provider that the user's attribute information has been changed. Further, the attribute information management server 10 requests the credential of the service provider's Web server 20 in order to confirm that the Web server 20 of the service provider is genuine and is not impersonation ((2) in FIG. 6). reference). Here, it is assumed that the credential can confirm the combination of an ID and a password, an electronic certificate using a public key cryptosystem technology, a challenge response type authentication procedure, and the authenticity of the Web server 20 of the service provider. .

  The attribute information management server 10 receives the credentials from the service provider's web server 20 (see (3) in FIG. 6), and if it can be confirmed that the service provider's web server 20 is authentic, the service provider's A following token representing the access right to the changed attribute information is transmitted to the Web server 20 (see (4) in FIG. 6). In the follow-up token, in addition to the token identifier and the token type, the expiration date of the follow-up token, the changed attribute information, the change time, and the like are described.

  Then, when the attribute information management server 10 receives the acquisition request for the changed attribute information from the service provider's Web server 20 using the follow-up token (see (5) in FIG. 6), the attribute information management server 10 services the attribute information. While transmitting to the provider's Web server 20, the profile managing the attribute information distributed to the service provider's Web server 20 is updated (see (6) in FIG. 6).

  When the Web server 20 of the service provider receives a notification of change of the user's attribute information from the attribute information management server 10 (see (2) in FIG. 6), it determines whether it is necessary to follow the change of the user's attribute information. Do. At this point, from the viewpoint of preventing information leakage due to the impersonation of the web server 20 of the service provider, only notification that there has been a change in the attribute information of the user acquired by the web server 20 of the service provider , Notification that identifies the changed user attribute information is not performed.

  If it is determined that it is necessary to follow the change of the user's attribute information, the authentication server 10 sends the attribute information management server 10 a credential that can confirm the authenticity of the Web server 20 of the service provider. In addition, when the following token is acquired from the attribute information management server 10, the attribute information changed from the following token is specified, and it is determined whether it is necessary to acquire the attribute information. When acquiring the changed attribute information, the attribute information is requested from the application interface of the attribute information management server 10 using the tracking token (see (5) in FIG. 6).

  Thus, on the communication network N, the user arranges the attribute information management server 10 for storing and centrally managing his / her attribute information. Then, in addition to the conventional authorization of distribution of attribute information by the user, the user can select the value of the attribute to be distributed for each Web server 20 of the service provider, with respect to the attribute of the user holding a plurality of values. In order to do so, the account name of the user paid out by the Web server 20 is distributed between the Web server 20 and the attribute information management server 10, and the attribute information management server 10 uses the value of the attribute selected by the user and other Web servers 20 A profile in which attribute information to be registered in is listed is created and attached to the account name, and attribute information to be registered in each Web server 20 is managed.

  This enables the user to properly use his / her attribute information registered for each Web server 20. In addition, the Web server 20 can provide a service without depending on the operation status of the service of another service provider that holds the user attribute information or the attribute information of the held user.

  That is, in the user attribute information management system 100 according to the first embodiment, the attribute information management server 10 which stores and centrally manages the user attribute information is a Web of a service provider whose service is provided on the communication network N. By allowing the user to selectively use the value of the attribute registered in the Web server 20 for each server 20, the user can register its own optimum attribute information for each Web server 20. In addition, the service provider holds user attribute information by acquiring user attribute information necessary for providing a service from the attribute information management server 10 for the user to store and centrally manage attribute information. The service can be provided without depending on the service operation status of the other service providers who are using the service and the user's attribute information held.

  On the communication network N, the user arranges an attribute information management server 10 for storing and centrally managing his / her attribute information. Then, in addition to the conventional authorization of distribution of attribute information by the user, the attribute information management server 10 performs the authorization of the user in order to make the Web server 20 of the service provider follow the change of the attribute information. The change of the attribute information is notified to the Web server 20 of the service provider, and after the attribute information management server 10 confirms the authenticity of the Web server 20 of the service provider, access to the changed attribute information is made. Send a follow-up token that represents the right.

  Thereby, when the user's attribute information is changed, the Web server 20 of the service provider who has acquired the attribute information before the change promptly follows the change of the attribute information while suppressing the processing load of the attribute management server 10. Make it possible to

  That is, in the user attribute information management system 100 according to the first embodiment, when the user changes the user attribute information stored and centrally managed by the attribute information management server 10, the attribute information management server 10 changes the attribute information By notifying the Web server 20 of the service provider who has acquired the change of the attribute information, and enabling the Web server 20 of the service provider to acquire the changed attribute information. The amount of processing between the attribute information management server 10 and the Web server 20 of the service provider can be suppressed, and the processing amount of the attribute information management server 10 can be suppressed. Further, the Web server 20 of the service provider can promptly update the registration information of the user, and the convenience of the user who uses the service of the service provider is improved.

  Next, processing by the user attribute information management system 100 according to the first embodiment will be described using FIG. 7. FIG. 7 is a sequence diagram for explaining the flow of user attribute information management processing in the user attribute information management system according to the first embodiment.

  First, as shown in FIG. 7, in order to change the attribute information of the user terminal 30 managed by the attribute information management server 10 supporting the centralized management of the attribute information of the user terminal 30, the portal site of the attribute information management server 10 (Step S101). Then, the attribute information management server 10 transmits information of the screen of the portal site and the like to the user terminal 30 as a response to the access (step S102). Subsequently, the user terminal 30 changes the attribute information of itself (step S103).

  Then, the attribute information management server 10 refers to the profile managing the attribute information distributed to the Web server 20 of each service provider, and provides the service in which the changed user attribute information is distributed before the change. The web server 20 of the person is identified (step S104). Furthermore, the web server 20 of the service provider that follows the change of the user's attribute information is identified from the web server 20 of the identified service provider (step S105). Then, the user is requested to select the web server 20 of the service provider who authorizes the distribution of the changed attribute information from the web server 20 of the identified service provider (step S106).

  Then, the user terminal 30 selects the Web server 20 of the service provider who authorizes distribution of the changed attribute information of the user (step S107).

  Here, an example of a screen displayed on the user terminal 30 when selecting the Web server 20 of the service provider who authorizes the distribution of the changed attribute information of itself will be described with reference to FIG. FIG. 8 is a diagram showing an example of screen display displayed on the user terminal. As illustrated in FIG. 8, for example, the user terminal 30 displays that the changed attribute information is a telephone number, and displays the telephone number before the change and the telephone number after the change. Then, in order to make the user select the Web server 20 of the service provider who authorizes the circulation of the changed attribute information of his own, two service names of “service A” and “service B” provided by each service provider are Is displayed.

  In addition, the “Select” button corresponding to each service name is displayed, and the Web server 20 of the service provider corresponding to the service name for which the “Select” button is pressed approves the circulation of the changed attribute information of itself. Is selected as the web server 20 of the service provider to be In addition, the user terminal 30 displays a "execute" button and a "cancel" button. When the “execute” button is pressed, the web server 20 of the service provider corresponding to the service name for which the “select” button is pressed recognizes the distribution of the changed attribute information of itself. Decide as. Also, when the "cancel" button is pressed, the pressing of the "select" button is canceled, and the state returns to the state where the "select" button of all service names is not pressed.

  Returning to the description of FIG. 7, when the user terminal 30 determines the Web server 20 of the service provider that authorizes the distribution of the changed attribute information of itself, the list of the Web servers 20 of the authorized service provider is attribute information It transmits to the management server 10 (steps S108 and 109).

  The attribute information management server 10 notifies the Web server 20 of the service provider authorized by the user that there is a change in the attribute information of the user acquired by the Web server 20 of the service provider, and the service The credential of the provider's Web server 20 is requested (step S110).

  Then, the Web server 20 of the service provider determines whether or not it is necessary to acquire the changed attribute information of the user's attribute information acquired before the change (step S111). If it is necessary to obtain the changed attribute information (Yes at step S111), the service provider Web server 20 transmits the credentials of the service provider Web server 20 to the attribute information management server 10 (step S112). Further, when it is not necessary to obtain the changed attribute information (No at step S111), the Web server 20 of the service provider ends the process.

  If the attribute information management server 10 can confirm the authenticity of the Web server 20 of the service provider from the received credentials (Yes at Step S113), the Web server 20 of the service provider receives the changed attribute information. A tracking token representing the access right is transmitted (step S114). If the attribute information management server 10 can not confirm the authenticity of the Web server 20 of the service provider from the received credentials (No at step S113), the process ends.

  The Web server 20 of the service provider specifies the changed attribute information from the received following token (step S115). When it is necessary to obtain the attribute information (Yes at step S116), the Web server 20 of the service provider uses the application interface defined by the attribute information management server 10 to execute the process from the attribute information management server 10 Get attribute information. Specifically, when it is necessary to obtain the attribute information (Yes at step S116), the Web server 20 of the service provider transmits the received following token to the attribute information management server 10 (step S117). Then, the attribute information management server 10 updates the corresponding profile (step S118), and sends the changed attribute information to the Web server 20 of the service provider (step S119). Further, when it is not necessary to obtain the attribute information (No at step S116), the Web server 20 of the service provider ends the process.

  Thus, the attribute information management server 10 is connected to a communication network N such as an access network of a telecommunications carrier or the Internet, and the user stores and centrally manages his / her attribute information with respect to the user terminal 30, Helps you to use your own attribute information when using the service provider's web service.

  Specifically, as shown in FIG. 9, the user terminal 30 registers its own attribute information from the portal site of the attribute information management server 10 in advance. At this time, when a plurality of pieces of information are held for each attribute, such as an e-mail address and a credit card number, each piece of information is registered. The user terminal 30 appropriately browses and changes the attribute information registered by the user from the portal site of the attribute information management server 10.

  In addition, for the web server 20 of the service provider (for example, the web servers 20A to 20D in FIG. 9), the attribute information of the user necessary for the service provider to provide the service is obtained under the authorization of the user. Provided by As for the attribute information of the user provided to the service provider, a profile is created and managed for each account paid out when the user registers with the web server 20 of the service provider, and the user is provided to the service provider View and confirm the attribute information of the account.

  When the user changes his / her registered attribute information from the portal site of the attribute information management server 10, the attribute information management server 10 identifies the web server 20 of the service provider who provides the attribute information, and identifies the The service provider's Web server 20 that follows the change of the attribute information in the service provider's Web server 20 is notified of the change of the attribute information and the service provider under the user's permission Request for credentials to secure the authenticity of the Web server 20 of FIG. Then, the changed attribute information is provided to the Web server 20 of the service provider whose authenticity has been confirmed.

  In holding the user attribute information, the attribute information management server 10 issues an ID for identifying the user, and manages the ID in the ID management table. The attribute information of the user registered in the attribute information management server 10 and the attribute information of the user registered in the Web server 20 of the service provider are managed in association with the ID.

  Furthermore, the attribute information management server 10 defines an application interface for the service provider Web server 20 to acquire user attribute information from the attribute information management server 10. When the service provider's Web server 20 acquires user's attribute information from the attribute information management server 10, the service provider makes an application to the attribute information management server 10 in advance, and the service provider's Web server 20 takes on the attribute information management server Get permission to perform the procedure when accessing 10

  Here, when attribute information is newly added to the attribute information management server 10 as an example of the change of attribute information using FIG. 10 and FIG. 11, the Web server 20 of the service provider who authorizes distribution of the attribute information. An example of reflecting will be described. FIG. 10 is a diagram for explaining the flow of registration of user attribute information in the user attribute information management system according to the first embodiment. FIG. 11 is a diagram for explaining the flow of addition of user attribute information in the user attribute information management system according to the first embodiment. Specifically, FIG. 11 is a diagram for explaining the flow of addition of user attribute information after registration of the user attribute information shown in FIG.

  First, an example of the flow of registration of user attribute information in the user attribute information management system 100 will be described using FIG. First, the user registers his / her attribute information in the attribute information management server 10 (see (0) in FIG. 10). In the example shown in FIG. 10, the user registers a name, a date of birth, an address, and a telephone number in the attribute information management server 10 as attribute information.

  Next, when the user performs user registration in the web server 20 of the service provider, the web server 20 of the service provider is instructed to acquire the access right to the attribute information management server 10 (see FIG. 10). (Refer to (1)).

  The service provider's Web server 20 redirects to the attribute information management server 10 in order to acquire user attribute information necessary for providing a service when performing user registration, and the user is sent to the attribute information management server 10. It asks for the authorization of the access right to access (see (2) in FIG. 10). Then, when the attribute information management server 10 is redirected from the Web server 20 of the service provider, the user confirms whether the attribute information of the user he is holding may be distributed to the Web server 20 of the service provider. , Together with the result, redirect again to the web server 20 of the service provider (see (3) in FIG. 10). Furthermore, after authorization of the user, the authorization code acquired from the attribute information management server 10 is transmitted to the attribute information management server 10, and is exchanged for an access token indicating the access right to the attribute information management server 10 (see FIG. )reference).

  Then, the Web server 20 of the service provider acquires the attribute information of the user from the attribute information management server 10 by using the access token as a parameter, using the application interface defined by the attribute information management server 10 (see FIG. See 5). For example, when the attribute information management server 10 is requested to obtain user attribute information from the Web server 20 of the service provider, the attribute information management server 10 creates a profile corresponding to the account name embedded in the access token ((6 of FIG. )reference). In the example shown in FIG. 10, the Web server 20 of the service provider requests a name, a date of birth, an address, a telephone number, and a credit card number as attribute information. Therefore, the attribute information management server 10 creates a profile including the name, the date of birth, the address, the telephone number, and the credit card number as attribute information.

  Here, in the example shown in FIG. 10, the user registers a name, a date of birth, an address, and a telephone number in the attribute information management server 10 as attribute information. That is, the credit card number of the user is not registered in the attribute information management server 10. Therefore, the attribute information management server 10 transmits, for example, the name, the date of birth, the address, and the telephone number of the requested attribute information excluding the credit card number to the Web server 20 of the service provider. Then, for example, the attribute information management server 10 may add, to the profile, information indicating that the credit card number can not be distributed to the Web server 20 of the service provider among the attribute information.

  If the credit card number is information essential for registration of the service provider's web server 20, the attribute information management server 10 or the web server 20 of the service provider may request the user to register the credit card number. Good. Further, when the credit card number is information essential for registration of the service provider Web server 20, the attribute information management server 10 and the service provider Web server 20 require the user to register the service provider Web server 20. You may notify that it can not be done. Also, for example, if the credit card number is information optional for registration of the service provider's Web server 20, the service provider's Web server 20 completes the user's registration. It is also good.

  First, an example of the flow of addition of user attribute information in the user attribute information management system 100 will be described with reference to FIG. First, the user adds his / her attribute information to the attribute information management server 10 (see (1) in FIG. 11). In the example shown in FIG. 11, a name, a date of birth, an address, and a telephone number are already registered as attribute information in the attribute information management server 10, and the user newly adds a credit card number as attribute information.

  At this time, the attribute information management server 10 refers to the profile and confirms that the credit card number which could not be distributed at the time of registration of the user in the Web server 20 of the service provider is added as attribute information. Then, the attribute information management server 10 notifies that the credit card number has been added to the web server 20 of the service provider who could not acquire the credit card number at the time of registration of the user.

  For example, when the user adds his / her attribute information, the attribute information management server 10 refers to the profile that manages the attribute information requested by the Web server 20 of the service provider for acquisition, and then adds the attribute information before the addition. The Web server 20 of the service provider who has requested acquisition of is identified. Furthermore, the attribute information management server 10 specifies the web server 20 of the service provider that follows the change of the attribute information from the web servers 20 of the identified service provider. Then, the attribute information management server 10 notifies the Web server 20 of the identified service provider that the user's attribute information has been added. Further, the attribute information management server 10 requests the credential of the service provider's Web server 20 in order to confirm that the service provider's Web server 20 is genuine and is not impersonation ((2) in FIG. 11). reference). In addition, since the process of (3)-(6) in FIG. 11 is the same as the process of (3)-(6) in FIG. 6, description is abbreviate | omitted. Thus, even when attribute information is newly added, the attribute information management server 10 can appropriately reflect the addition of the user's attribute information on the following Web server 20.

[Effect of First Embodiment]
As described above, the attribute information management server 10 stores attribute information. Then, the attribute information management server 10 changes the attribute information in response to the request from the user terminal 30, and notifies the Web server 20 of the change of the attribute information. When the Web server 20 receives the notification of the change of the attribute information from the attribute information management server 10, the Web server 20 requests the attribute information management server 10 for at least a part of the attribute information for which the notification has been received. Thereafter, when the attribute information management server 10 receives the notified request for the attribute information from the Web server 20, the attribute information management server 10 transmits the changed attribute information to the Web server 20. Then, when the requested changed attribute information is received, the Web server 20 updates the user information based on the changed attribute information. Therefore, when the Web server 20 follows the change of the user's attribute information in the attribute information management server 10 which is an apparatus for managing attribute information, the change of the user's attribute information is appropriately made to the following Web server 20. It is possible to reflect.

  Further, the Web server 20 of the service provider does not need to periodically acquire the attribute information of the user already acquired from the attribute information management server 10 and check the presence or absence of the change of the attribute information. The amount of processing can be reduced.

  Furthermore, since the Web server 20 of the service provider can quickly acquire the changed attribute information and reflect it on the service to the user, the convenience of the user is improved.

  In addition, the attribute information management server 10 acquires the credential from the web server 20 and confirms the authenticity of the web server 20, so that it is possible to prevent the leakage of the user's attribute information due to the spoofing of the web server 20.

  In addition, the attribute information management server 10 notifies the Web server 20 selected by the user terminal 30 of the change in the attribute information, thereby allowing the user to use his / her attribute information when using the Web service 20 of the service provider. It is possible to support using properly.

Second Embodiment
In the first embodiment described above, although the case where the credential held by the web server is used to confirm the authenticity of the web server is described, the present invention is not limited to this, and information acquired from other than the web server The authenticity of the web server may be confirmed based on In the second embodiment described below, as shown in FIG. 12, the user attribute information management system 100A has a leased line information management server 40, and the attribute information management server 110 is a leased line information management server 40. The case where the authenticity of the web server 20 is confirmed based on the information acquired from FIG. The description of the configuration and processing common to the first embodiment will be omitted.

[Configuration of attribute information management server]
The configuration of the attribute information management server shown in FIG. 12 will be described using FIG. FIG. 13 is a block diagram showing the configuration of the attribute information management server according to the second embodiment. The same components as those of the attribute information management server 10 according to the first embodiment are given the same reference numerals and descriptions thereof will be omitted.

  The storage unit 113 stores data and programs necessary for various processes performed by the control unit 12. Particularly as closely related to the present invention, the attribute information storage unit 13a, the profile information storage unit 13b, and the web server information It has a storage unit 13c.

  The web server information storage unit 13c stores web server information. The web server information stored in the web server information storage unit 13 c is information used to confirm the authenticity of the web server 20. Specifically, the web server information stored in the web server information storage unit 13 c is information used to confirm the authenticity of the web server 20 of the service provider who follows the change of the attribute information. For example, as illustrated in FIG. 14, the web server information storage unit 13 c connects to the communication network N the “web server ID” that uniquely identifies the web server 20 and the web server 20 identified by the web server ID. It stores in association with the dedicated line number (hereinafter sometimes referred to simply as the “dedicated line number” or the “dedicated line number”). For example, in the example of FIG. 14, the web server 20 identified by the web server ID “server A” stores information indicating that it is connected to the communication network N by the dedicated line number “L1”.

  The other configuration of the attribute information management server 110 is omitted because it is the same as the attribute information management server 10 of FIG. 2 described above, but the authenticity of the Web server 20 is based on the information acquired from the leased line information management server 40. The processing content of the transmission unit 12c is different. The transmitting unit 12 c of the attribute information management server 110 according to the second embodiment transmits the secret key acquired from the Web server 20 to the leased line information management server 40, and thereby transmits the private key acquired from the leased line information management server 40. If the number matches the number of the dedicated line of the Web server 20 that has transmitted the secret key, the attribute information changed by the changing unit 12 a is transmitted to the Web server 20. The details of the secret key will be described later.

  Further, although the configuration of the Web server 20 is omitted because it is the same as that of FIG. 5 described above, since the authenticity of the Web server 20 is to be confirmed based on the information acquired from the leased line information management server 40, The processing content of the request unit 22a is different. When the request unit 22a according to the second embodiment receives the notification of the change of the attribute information from the attribute information management server 110, the request unit 22a requests the leased line information management server 40 to acquire the secret key. Is sent to the attribute information management server 110, thereby requesting at least a part of the attribute information for which the notification has been accepted. Specifically, when requesting the attribute information for which the notification of the change of the attribute information has been received from the attribute information management server 110, the request unit 22a requests the leased line information management server 40 to acquire the secret key. Then, when acquiring the secret key from the leased line information management server 40, the request unit 22a transmits the secret key to the attribute information management server 110. Then, when receiving the follow-up token from the attribute information management server 110, the request unit 22a transmits the received follow-up token to the attribute information management server 110, thereby requesting the attribute information for which the notification has been received.

[Configuration of leased line information management server]
Next, the configuration of the leased line information management server 40 shown in FIG. 12 will be described using FIG. FIG. 15 is a block diagram showing the configuration of the leased line information management server according to the second embodiment. As shown in FIG. 15, the leased line information management server 40 includes a communication processing unit 41, a control unit 42, and a storage unit 43. The processing of each of these parts will be described below.

  The communication processing unit 41 controls communication regarding various information exchanged with the attribute information management server 110 and the web server 20 connected.

  The storage unit 43 stores data and programs necessary for various processes performed by the control unit 42. Particularly, the storage unit 43 has a dedicated line information storage unit 43a as closely related to the present invention.

  The dedicated line information storage unit 43a stores dedicated line information. The dedicated line information stored in the dedicated line information storage unit 43 a is information used to confirm the authenticity of the Web server 20. Specifically, the leased line information stored in the leased line information storage unit 43a is information used to confirm the authenticity of the Web server 20 of the service provider who follows the change of the attribute information. For example, as illustrated in FIG. 16, the dedicated line information storage unit 43 a associates “Web server ID” that uniquely identifies a web server with the number of a dedicated line of the web server 20 identified by the web server ID. I remember it. The leased line information storage unit 43a also stores the type of leased line. As the type of the leased line, a type specified by the service type of the leased line or the line speed may be used. For example, in the example of FIG. 16, the web server 20 identified by the web server ID “server B” stores information indicating that it is connected to the communication network N by the dedicated line number “L2” of the type “T2”. Ru. In addition, as illustrated in FIG. 16, when a private key is paid out for a dedicated line number, the dedicated line information storage unit 43 a associates the private line number with the private key and stores the private key. . For example, in the example of FIG. 16, the private key “abcd” is stored in association with the leased line number “L1”. Further, as illustrated in FIG. 16, the dedicated line information storage unit 43a stores the expiration date of the issued private key.

  The control unit 42 has a program defining various processing procedures and the like, and an internal memory for storing required data, and executes various processings by these, and particularly as closely related to the present invention, It has an information receiving unit 42a, an information managing unit 42b, and an information transmitting unit 42c.

  The information receiving unit 42 a receives a request for acquisition of a secret key from the web server 20. Also, the information receiving unit 42 a receives the secret key from the attribute information management server 110.

  The information management unit 42b, for example, when the information receiving unit 42a receives a request for acquisition of a secret key from the Web server 20, the dedicated line connecting the Web server 20 requesting acquisition of the secret key to the communication network N Identify Specifically, the information management unit 42b specifies a dedicated line of the Web server 20 that requests acquisition of the secret key, based on the dedicated line information stored in the dedicated line information storage unit 43a. In the case of the example shown in FIG. 16, when the Web server ID of the Web server 20 that requests acquisition of the secret key is the server A, the information management unit 42b identifies the leased line number as L1. Then, the information management unit 42b delivers a secret key that is valid only for a certain period, and manages the secret key in association with the number of the dedicated line of the Web server 20 that requests acquisition of the secret key.

  For example, when a secret key is received from the attribute information management server 110 by the information receiving unit 42a, the information management unit 42b identifies the number of the dedicated line from the secret key after confirming the expiration date of the secret key. . Specifically, based on the leased line information stored in the leased line information storage unit 43a, the information management unit 42b identifies the number of the leased line from the received secret key. In the case of the example shown in FIG. 16, when receiving the secret key "abcd", the information management unit 42b identifies the leased line number as L1 after confirming the expiration date of the secret key.

  The information transmission unit 42 c transmits the secret key corresponding to the web server 20 to the web server 20 in response to the request from the web server 20. For example, in response to a request from the Web server 20, the information transmission unit 42c transmits the secret key paid out by the information management unit 42b to the Web server 20.

  When the information receiving unit 42a receives the secret key from the attribute information management server 110, the information transmitting unit 42c sends the leased line number corresponding to the secret key to the attribute information management server 110. For example, when the information receiving unit 42a receives the secret key from the attribute information management server 110, the information transmitting unit 42c transmits the number of the leased line specified by the information managing unit 42b to the attribute information management server 110.

  Next, the flow of update processing of user attribute information in the user attribute information management system 100A according to the second embodiment will be described with reference to FIG. FIG. 17 is a diagram for explaining the flow of a process of updating user attribute information in the user attribute information management system according to the second embodiment.

  After changing the attribute information of the user terminal 30 registered in the attribute information management server 110, the user terminal 30 selects the web server 20 of the service provider to be made to follow the change of the attribute information, and the web server of the service provider It authorizes the circulation of attribute information after changing to 20 (see (1) in FIG. 17).

  The attribute information management server 110 makes an application for acquiring in advance from the leased line information management server 40 the number of the leased line for the service provider Web server 20 to connect to the communication network N to the leased line information management server 40 in advance. . When the user changes his / her attribute information, a list of the web server 20 of the service provider who follows the change of the attribute information is managed. The list is created when the service provider applies in advance to the attribute information management server 110 and acquires the permission for performing the procedure for accessing the attribute information management server 110. When the user changes his / her attribute information, the attribute information management server 110 refers to the profile managing the attribute information acquired by the Web server 20 of the service provider, and acquires the attribute information before the change. The provider's web server 20 is identified.

  Further, among the web servers 20 of the identified service provider, the web server 20 of the service provider that follows the change of the attribute information is identified. Then, it notifies the Web server 20 of the identified service provider that the user's attribute information has been changed. Also, in order to confirm that the Web server 20 of the service provider is authentic and not spoofing, the credential of the Web server 20 of the service provider is requested (see (2) in FIG. 17).

  When the web server 20 of the service provider transmits the secret key linked to the dedicated line to which the communication network N connects the web server 20 of the service provider (see (6) in FIG. 17), the attribute information management The server 110 sends the private key to the leased line information management server 40 to acquire a leased line number (see (7) in FIG. 17).

  Then, it is possible to confirm that the web server 20 of the service provider is genuine by collating with the number of the dedicated line registered in advance in the attribute information management server 110 by the application from the web server 20 of the service provider. Then, the following token representing the access right to the changed attribute information is transmitted to the Web server 20 of the service provider (see (8) in FIG. 17). In the follow-up token, in addition to the token identifier and the token type, the expiration date of the follow-up token, the changed attribute information, the change time, and the like are described.

  Then, when a request for acquiring the changed attribute information is received from the service provider's Web server 20 using the following token, the attribute information is transmitted to the service provider's Web server 20 and the service provider's The profile managing the attribute information distributed to the Web server 20 is updated (see (10) in FIG. 17).

  The service provider's Web server 20 uses, as a credential for securing the authenticity of the service provider's Web server 20, the private key linked to the number of the dedicated line for connecting to the communication network N as a dedicated line. An application for obtaining information from the information management server 40 is made to the leased line information management server 40 in advance. In addition, the attribute information management server 110 uses the number of the dedicated line connecting the Web server 20 of the service provider to the communication network N to confirm the authenticity of the Web server 20 of the service provider. Application is made to the attribute information management server 110 in advance so that the line number is registered in the attribute information management server 110.

  When a notification of change of the user's attribute information is received from the attribute information management server 110 (see (2) in FIG. 17), it is determined whether it is necessary to follow the change of the user's attribute information. At this point, from the viewpoint of preventing information leakage due to the impersonation of the web server 20 of the service provider, only notification that there has been a change in the attribute information of the user acquired by the web server 20 of the service provider , Notification that identifies the changed user attribute information is not performed.

  If it is determined that it is necessary to follow the change of the user's attribute information, the private line information management server 40 is requested to request a secret key linked to the private line (see (3) in FIG. 17). When the secret key is acquired from the leased line information management server 40 (see (4) in FIG. 17), the secret key is transmitted to the attribute management server 110 (see (5) in FIG. 17). Further, when the following token is acquired from the attribute information management server 110, the attribute information changed from the following token is specified, and it is determined whether or not acquisition of the attribute information is necessary. When acquiring the changed attribute information, the attribute information is requested from the application interface of the attribute information management server 110 using the tracking token (see (9) in FIG. 17).

  The dedicated line information management server 40 manages information on a dedicated line connecting the service provider's Web server 20 to the communication network N. The information managed includes the number of the leased line and the type of leased line. When the dedicated line information management server 40 receives a request for a secret key linked to the number of the dedicated line from the web server 20 of the service provider who has made an application in advance (see (3) in FIG. 17), the service The leased line connecting the web server 20 of the provider to the communication network N is specified, the number of the leased line is acquired, and a secret key valid only for a certain period is paid out, and the number of the leased line The secret key is linked and managed, and the secret key is transmitted to the Web server 20 of the service provider (see (4) in FIG. 17).

  When a request for the number of a dedicated line connecting the service provider's Web server 20 to the communication network N is received using the secret key from the attribute information management server 110 for which the application has been made in advance (see FIG. 6) After confirming the expiration date of the secret key, specify the number of the dedicated line from the secret key, and transmit the secret key to the attribute information management server 110 ((7) in FIG. 17). reference).

  Thus, the leased line information management server 40 is disposed on the communication network N. Then, in order for the attribute information management server 110 to confirm the authenticity of the web server 20 of the service provider, the web server 20 of the service provider connects the web server 20 of the service provider to the communication network N. The private key linked to the number of the leased line is acquired from the leased line information management server 40. Then, the Web server 20 of the service provider sends the acquired secret key to the attribute information management server 110, and the attribute information management server 110 transmits the private line information management server 40 from the leased line information management server 40 using the secret key. Get the leased line number. Then, the attribute information management server 110 collates the acquired leased line number with the leased line number registered in advance in the attribute information management server 110.

  In addition, when the Web server 20 of the service provider acquires the changed attribute information, the service of the attribute information management server 110 confirms the authenticity of the Web server 20 of the service provider. By using the number of the dedicated line connecting the Web server 20 of the provider to the communication network N and the secret key associated with the number, it is possible to perform highly reliable verification of authenticity.

  As a result, when the user's attribute information is changed, the Web server 20 of the service provider who has acquired the attribute information before the change can quickly change the attribute information while suppressing the processing load of the attribute information management server 110. Make it possible to follow In addition, with regard to the web server 20 of the service provider, reliable verification of authenticity is enabled.

  Next, processing by the user attribute information management system 100A according to the second embodiment will be described using FIGS. 18-1 and 18-2. FIGS. 18A and 18B are sequence diagrams for explaining the flow of user attribute information management processing in the user attribute information management system according to the second embodiment.

  First, as shown in FIGS. 18A and 18B, the user terminal 30 changes the attribute information of the user terminal 30 in order to change its own attribute information managed by the attribute information management server 110 that supports centralized management of its own attribute information. The portal site of the information management server 110 is accessed (step S201). Then, the attribute information management server 110 transmits information of the screen of the portal site and the like to the user terminal 30 as a response to the access (step S202). Subsequently, the user terminal 30 changes the attribute information of itself (step S203).

  Then, the attribute information management server 110 refers to the profile that manages the attribute information distributed to the Web server 20 of each service provider, and distributes the changed attribute information of the user before the service provision. The web server 20 of the person is identified (step S204). Further, the web server 20 of the service provider who follows the change of the user's attribute information is identified from the web server 20 of the identified service provider (step S205). Then, the user is requested to select the web server 20 of the service provider who authorizes the distribution of the changed attribute information from the web server 20 of the identified service provider (step S206).

  Then, the user terminal 30 selects the web server 20 of the service provider who authorizes the distribution of the changed attribute information of the user (step S207). For example, the user terminal 30 selects, via the screen display shown in FIG. 8, the Web server 20 of the service provider who authorizes the distribution of the changed attribute information of itself. When the user terminal 30 determines the Web server 20 of the service provider who authorizes the distribution of the changed attribute information of itself, the user terminal 30 transmits a list of the Web servers 20 of the authorized service provider to the attribute information management server 110 (Step S208, 209).

  Subsequently, the attribute information management server 110 notifies the Web server 20 of the service provider authorized by the user that there is a change in the user's attribute information acquired by the Web server 20 of the service provider. , Requests the credentials of the Web server 20 of the service provider (step S210).

  Then, the Web server 20 of the service provider determines the necessity of acquiring the changed attribute information about the user's attribute information acquired before the change (step S211). When it is necessary to obtain the changed attribute information (Yes at step S211), the service provider Web server 20 causes the leased line information management server 40 to set the Web server 20 of the service provider to the communication network N. The number of the connected dedicated line is requested (step S212). Further, when it is not necessary to obtain the changed attribute information (No at step S211), the service provider Web server 20 ends the process.

  Then, the leased line information management server 40 searches the database of the leased line information management server 40 for the number of the leased line connecting the Web server 20 of the service provider to the communication network N (step S213). Then, the private key associated with the acquired private line number is issued (step S214), and the private line information management server 40 database (for example, dedicated) The line information storage unit 43a registers the same in the following) (step S215). Then, the secret key is transmitted to the web server 20 of the service provider (step S216).

  Then, in response to the request for the credential from the attribute information management server 110, the Web server 20 of the service provider responds the secret key acquired from the leased line information management server 40 (step S217).

  Subsequently, the attribute information management server 110 acquires the number of the dedicated line connecting the service provider Web server 20 to the communication network N from the secret key acquired from the service provider Web server 20. The private line information management server 40 is requested for the number of the private line using the private key (step S218).

  Then, the leased line information management server 40 confirms the expiration date of the secret key acquired from the attribute information management server 110, and if it is within the expiration date (Yes at step S219), the database of the leased line information management server 40. The leased line number linked to the secret key is searched from (step S220), and the leased line number is transmitted to the attribute information management server 110 (step S221). Also, if the private key information management server 40 has passed the expiration date of the secret key acquired from the attribute information management server 110 (No at step S219), the processing is ended.

  Subsequently, the attribute information management server 110 compares the leased line number acquired from the leased line information management server 40 with the dedicated line number of the web server 20 of the service provider registered in advance in the attribute information management server 110. (Step S222) If they match (Yes at Step S223), a tracking token representing the access right to the changed attribute information is transmitted to the Web server 20 of the service provider (Step S224). Also, the attribute information management server 110 does not match the leased line number acquired from the leased line information management server 40 and the dedicated line number of the Web server 20 of the service provider registered in advance in the attribute information management server 110. In the case (No at step S223), the process ends.

  Then, the Web server 20 of the service provider specifies the changed attribute information from the acquired following token (step S225), and the Web server 20 of the service provider changed the contents of the service provided by the Web server 20 of the service provider. It is determined whether attribute information is acquired from the attribute information management server 110 (step S226). If it is not necessary to obtain the attribute information (No at Step S226), the Web server 20 of the service provider ends the process. When the service provider Web server 20 acquires the changed attribute information (Yes at step S226), the attribute information management server uses the tracking token from the application interface defined by the attribute information management server 110. The attribute information is requested to 110 (step S227).

  Subsequently, the attribute information management server 110 acquires the following token from the acquisition request of the user's attribute information, and confirms the access right of the Web server 20 of the service provider who has transmitted the request. If the validity of the access right of the Web server 20 of the service provider can be confirmed, the attribute information management server 110 updates the corresponding profile (step S228), and requests the Web server 20 of the service provider The transmitted attribute information is transmitted (step S229).

[Effect of Second Embodiment]
The user attribute information management system 100A according to the second embodiment has the leased line information management server 40, and the attribute information management server 110 uses the Web server 20 based on the information acquired from the leased line information management server 40. Confirm the authenticity of Specifically, in the user attribute information management system 100A, when the Web server 20 of the service provider is requested by the attribute information management server 110 for the credentials of the Web server 20 of the service provider, the service provider's The web server 20 acquires, from the leased line information management server 40, the secret key linked to the number of the dedicated line connecting the web server 20 of the service provider to the communication network N. Then, the Web server 20 of the service provider transmits the acquired secret key to the attribute information management server 110, and the attribute information management server 110 transmits the secret key to the leased line information management server 40, and the secret Get the leased line number corresponding to the key. Then, the attribute information management server 110 collates the acquired number of the leased line with the number of the leased line which has been applied to the attribute information management server 110 by the web server 20 of the service provider in advance.

  Therefore, when the Web server 20 follows the change of the user's attribute information in the attribute information management server 110 which manages the attribute information, the change of the user's attribute information is appropriately made to the following Web server 20. It is possible to reflect. Specifically, the attribute information management server 110 can confirm the authenticity of the Web server 20 of the service provider using information of a highly reliable leased line, and distributes user attribute information safely. be able to. Also, when the service provider Web server 20 transmits the information on the dedicated line to the attribute information management server 110, the private key number is abused by using the private key instead of the dedicated line number. It is possible to prevent the spoofing to the web server 20 of the service provider by the above.

  Further, the Web server 20 of the service provider does not need to periodically acquire the attribute information of the user who has already been acquired from the attribute information management server 110 and check the presence or absence of the change of the attribute information. The amount of processing can be reduced.

  Furthermore, since the Web server 20 of the service provider can quickly acquire the changed attribute information and reflect it on the service to the user, the convenience of the user is improved.

Third Embodiment
In the third embodiment described above, a case will be described where the attribute information management application installed in the user terminal manages the user's attribute information instead of the attribute information management server. The attribute information management application 50 is installed in the user terminal 30A and operates as an add-on to the web browser 60 installed in the user terminal 30A, and the user centrally manages his / her attribute information for the user, and provides a service Support to use their own attribute information when using web services of people.

  First, the flow of update processing of user attribute information in the user attribute information management system 100B according to the third embodiment will be described using FIG. FIG. 19 is a diagram for explaining the flow of update processing of user attribute information in the user attribute information management system according to the third embodiment.

  The user registers his / her attribute information in the attribute information management application 50 installed in advance in the user terminal 30A. Then, the user is registered in the Web server 20 of the service provider who provides the service that the user wants to use (see (1) in FIG. 19). After that, when the user changes his / her attribute information registered in the attribute information management application 50, the user selects the web server 20 of the service provider to follow the change of the attribute information, and the web server of the service provider It authorizes the circulation of attribute information after the change to 20 (see (2) in FIG. 19).

  The attribute information management application 50 manages a list of web servers 20 of service providers who follow changes in the attribute information when the user changes the attribute information of the user. The list is created when the service provider registers in the attribute information management application 50 in advance. When the user changes the attribute information of the user, the attribute information management application 50 refers to the profile managing the attribute information acquired by the Web server 20 of the service provider, and acquires the attribute information before the change. The provider's web server 20 is identified.

  Furthermore, the attribute information management application 50 specifies the web server 20 of the service provider that follows the change of the attribute information among the web servers 20 of the identified service provider. Then, the attribute information management application 50 notifies the Web server 20 of the identified service provider that the user's attribute information has been changed.

  Further, the attribute information management application 50 requests the credentials of the service provider's Web server 20 in order to confirm that the service provider's Web server 20 is genuine and is not impersonation ((3) in FIG. 19). reference). Here, it is assumed that the credential can confirm the combination of an ID and a password, an electronic certificate using a public key cryptosystem technology, a challenge response type authentication procedure, and the authenticity of the Web server 20 of the service provider. .

  When the attribute information management application 50 confirms that the web server 20 of the service provider is authentic, it sends a tracking token representing the access right to the changed attribute information to the web server 20 of the service provider ( See (5) in FIG. In the follow-up token, in addition to the token identifier and the token type, the expiration date of the follow-up token, the changed attribute information, the change time, and the like are described. Then, when the attribute information management application 50 receives the acquisition request for the changed attribute information from the service provider Web server 20 using the follow-up token, the attribute information management application 50 transmits the attribute information to the service provider Web server 20. At the same time, the profile managing the attribute information distributed to the Web server 20 of the service provider is updated (see (7) in FIG. 19).

  When the Web server 20 of the service provider receives a notification of change of the user's attribute information from the attribute information management application 50 (see (3) in FIG. 19), it determines the necessity of following the change of the user's attribute information. Do. At this point, from the viewpoint of preventing information leakage due to the impersonation of the web server 20 of the service provider, only notification that there has been a change in the attribute information of the user acquired by the web server 20 of the service provider , Notification that identifies the changed user attribute information is not performed.

  If the service provider's Web server 20 determines that it is necessary to follow the change in the user's attribute information, it sends the attribute information management application 50 a credential that can confirm the authenticity of the service provider's Web server 20. (See (4) in FIG. 19). Further, when the tracking token is acquired from the attribute information management application 50, the Web server 20 of the service provider identifies the attribute information changed from the tracking token, and determines whether it is necessary to acquire the attribute information. When acquiring the said changed attribute information, the said attribute information is requested | required from the application interface of the said attribute information management application 50 using the said tracking token (refer (6) of FIG. 19).

  Next, the configuration of the user terminal 30A will be described using FIG. FIG. 20 is a block diagram showing a configuration of a user terminal according to the third embodiment. As shown in FIG. 20, the user terminal 30A includes a communication processing unit 31, a control unit 32, a storage unit 33, and a GUI processing unit 34. The processing of each of these parts will be described below. The control unit 32, the storage unit 33, and the GUI processing unit 34 are functions of the attribute information management application 50 installed in the user terminal 30A.

  The storage unit 33 stores data and programs necessary for various processes performed by the control unit 32. The storage unit 33 particularly includes an attribute information storage unit 33a and a profile information storage unit 33b, which are closely related to the present invention.

  The attribute information storage unit 33a stores attribute information. The profile information storage unit 33b stores a profile created based on the attribute information. The information stored in the attribute information storage unit 33a and the profile information storage unit 33b is the same as the information stored in the attribute information storage unit 13a and the profile information storage unit 13b described above, so a detailed description is omitted. Do.

  The control unit 32 has a program defining various processing procedures and the like, and an internal memory for storing required data, and executes various processings by these, and particularly as closely related to the present invention, A change unit 32a, a notification unit 32b, and a transmission unit 32c are included.

  The change unit 32a changes the attribute information. Specifically, when the change unit 32a receives a change in attribute information from the user, the change unit 32a changes the attribute information stored in the attribute information storage unit 33a according to the received attribute information. Further, the changing unit 32a updates the profile stored in the profile information storage unit 33b, for example, based on the changed attribute information.

  The notification unit 32 b notifies the Web server 20 of the change in attribute information when the change unit 32 a changes the attribute information. Specifically, when the attribute information is changed by the change unit 32a, the notification unit 32b notifies the Web server 20 of the service provider who authorized the circulation of the attribute information after the change of the attribute information to be changed. Do. For example, the notification unit 32b notifies only the Web server 20 of the service provider selected by the user of the change of the attribute information.

  The transmitting unit 32 c transmits the attribute information changed by the changing unit 32 a to the Web server 20. Specifically, when the request for the attribute information notified by the notification unit 32 b is received from the Web server 20, the transmission unit 32 c transmits the attribute information changed by the change unit 32 a to the Web server 20. For example, the transmitting unit 32c transmits the attribute information changed by the changing unit 32a only to the Web server 20 of the service provider selected by the user.

  Next, the flow of user attribute information management processing in the user attribute information management system 100B according to the third embodiment will be described with reference to FIG. FIG. 21 is a sequence diagram for explaining the flow of user attribute information management processing in the user attribute information management system according to the third embodiment.

  First, as shown in FIG. 21, the user accesses the attribute information management application 50 that supports centralized management of his / her attribute information, and changes the attribute information (step S301).

  Then, the attribute information management application 50 refers to the profile managing the attribute information distributed to the Web server 20 of each service provider, and provides the service in which the changed user attribute information is distributed before the change. The web server 20 of the person is identified (step S302). Furthermore, the attribute information management application 50 specifies the web server 20 of the service provider that follows the change of the user's attribute information from the web server 20 of the specified service provider (step S303). Then, the attribute information management application 50 requests the user to select the web server 20 of the service provider who authorizes distribution of the changed attribute information from the web server 20 of the identified service provider (step S304). .

  Then, the user selects the Web server 20 of the service provider who authorizes the distribution of the changed attribute information (step S305). For example, the user selects the web server 20 of the service provider who authorizes the distribution of the changed attribute information of his own through the screen displayed on the web browser 60 (for example, the screen display shown in FIG. 8). In this case, the web browser 60 passes the list of the web servers 20 of the service provider authorized by the user to the attribute information management application 50 (steps S306 and 307).

  Subsequently, the attribute information management application 50 notifies the Web server 20 of the service provider authorized by the user that there is a change in the attribute information of the user acquired by the Web server 20 of the service provider. , Requests the credentials of the Web server 20 of the service provider (step S308).

  Then, the Web server 20 of the service provider determines whether or not it is necessary to acquire the changed attribute information of the user's attribute information acquired before the change (step S309). If it is not necessary to acquire the changed attribute information (No at step S309), the Web server 20 of the service provider ends the process. Further, when it is necessary to obtain the changed attribute information (Yes at step S309), the Web server 20 of the service provider transmits the credential of the Web server 20 of the service provider to the attribute information management application 50. (Step S310).

  Subsequently, when the attribute information management application 50 can not confirm the authenticity of the Web server 20 of the service provider from the received credentials (No at step S311), the process ends. In addition, when the attribute information management application 50 can confirm the authenticity of the Web server 20 of the service provider from the received credentials (Yes in step S311), the attribute information changed to the Web server 20 of the service provider. A follow-up token representing the access right to the user is transmitted (step S312).

  Then, the Web server 20 of the service provider specifies the changed attribute information from the received following token (step S313). When it is necessary to obtain the attribute information (Yes at step S 314), the Web server 20 of the service provider uses the application interface defined by the attribute information management application 50 to use the attribute information management application 50 to execute the process. Get attribute information. Specifically, when it is necessary to obtain the attribute information (Yes at step S314), the Web server 20 of the service provider transmits the received tracking token to the attribute information management application 50 (step S315). Then, the attribute information management application 50 updates the corresponding profile (step S316), and sends the changed attribute information to the Web server 20 of the service provider (step S317). Further, when it is not necessary to obtain the attribute information (No at step S314), the Web server 20 of the service provider ends the process.

  As shown in FIG. 22, the attribute information management application 50 is installed in the user terminal 30A, operates as an add-on to the web browser 60 in the user terminal 30A, and the user centrally manages his / her attribute information for the user. Support the use of their own attribute information when using the service provider's web service. Specifically, the user registers his / her attribute information in advance from the GUI (Graphical User Interface) of the attribute information management application 50.

  At this time, when a plurality of pieces of information are held for each attribute, such as an e-mail address and a credit card number, each piece of information is registered. The user appropriately browses and changes the attribute information registered by the user from the GUI of the attribute information management application 50. In addition, with respect to the web server 20 of the service provider (for example, the web servers 20A to 20D in FIG. 22), the attribute information of the user necessary for the service provider to provide the service is obtained under the authorization of the user Provided by As for the attribute information of the user provided to the service provider, a profile is created and managed for each account paid out when the user registers with the web server 20 of the service provider, and the user is provided to the service provider View and confirm the attribute information of the account.

  When the user changes his / her registered attribute information from the GUI of the attribute information management application 50, the attribute information management application 50 identifies the web server 20 of the service provider who provides the attribute information, and is identified. The service provider's Web server 20 that follows the change of the attribute information in the service provider's Web server 20 is notified of the change of the attribute information under the user's permission and the service provider's A request for credentials for securing the authenticity of the Web server 20 is made. Then, the changed attribute information is provided to the Web server 20 of the service provider whose authenticity has been confirmed.

  The attribute information management application 50 specifies an application interface for the Web browser 60 to acquire user attribute information from the attribute information management application 50 and display the attribute information. As an example of the definition of the application interface, a server function of http (HyperText Transfer Protocol) is implemented in the attribute information management application 50, and URL (Uniform Resource Locator) or html (HyperText Markup Language) for accessing the server function. There is a rule.

[Effect of Third Embodiment]
As described above, in the user attribute information management system 100B according to the third embodiment, the user installs the attribute information management application 50 in the user terminal 30A of his own, and integrates his / her attribute information with the user terminal 30A of his own. By managing, when the Web server 20 follows the change of the user's attribute information in the user terminal 30A which is an apparatus for managing attribute information, the change of the user's attribute information is appropriately made to the following Web server 20 It is possible to reflect. Specifically, the user's own attribute information can be centrally managed or the attribute information can be changed without being influenced by the operation status such as a specification change or failure of a service related to management of user attribute information on the communication network N. At the time of the change, it is possible to make the changed contents follow the Web server 20 of the service provider.

  Furthermore, by installing the attribute information management application 50 for storing and centrally managing user attribute information in the user terminal 30A, changing the operation policy of the server managing the operation status such as a failure of the communication network N and the user attribute information. Etc. The influence of the communication network N or server can be prevented.

  In addition, it is not necessary for the service provider Web server 20 to periodically acquire the user's attribute information acquired from the attribute information management application 50 and check whether the attribute information has been changed or not. The amount of processing can be reduced.

  Furthermore, since the Web server 20 of the service provider can quickly acquire the changed attribute information and reflect it on the service to the user, the convenience of the user is improved.

  In addition, when the user terminal 30A acquires the credential from the Web server 20 and confirms the authenticity of the Web server 20, it is possible to prevent the leakage of the user's attribute information due to the spoofing of the Web server 20.

  In the present embodiment, the credentials sent by the Web server 20 of the service provider to the attribute information management application 50 are not limited to specific information, but the dedicated line numbers and the numbers described in the second embodiment You may use the attached secret key.

Fourth Embodiment
Although the embodiments of the present invention have been described above, the present invention may be implemented in various different modes other than the above-described embodiments. Thus, another embodiment included in the present invention will be described below as a fourth embodiment.

(1) System Configuration Etc. Each component of each device illustrated is functionally conceptual, and does not necessarily have to be physically configured as illustrated. That is, the specific form of the distribution and integration of each device is not limited to the illustrated one, and all or a part thereof may be functionally or physically dispersed in any unit depending on various loads, usage conditions, etc. It can be integrated and configured. For example, the change unit 12a and the notification unit 12b may be integrated. Furthermore, all or any part of each processing function performed in each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as wired logic hardware.

  Further, among the processes described in the present embodiment, all or part of the process described as being automatically performed can be manually performed, or the process described as being manually performed. All or part of them can be automatically performed by a known method. In addition to the above, the processing procedures, control procedures, specific names, and information including various data and parameters shown in the above documents and drawings can be arbitrarily changed unless otherwise specified.

(2) Program In addition, it is also possible to create a program described in a language that can be executed by a computer, regarding the process executed by each device described in the above embodiment. For example, a user attribute information management program described in a computer-executable language can be created for the processing executed by the attribute information management server 10 according to the first embodiment. In this case, when the computer executes the user attribute information management program, the same effect as that of the above embodiment can be obtained. Furthermore, the user attribute information management program is recorded on a computer readable recording medium, and the computer reads the user attribute information management program recorded on the recording medium and executes the same, as in the first embodiment. Processing may be realized. Hereinafter, an example of a computer that executes a user attribute information management program that realizes the same function as the attribute information management server 10 illustrated in FIG. 2 will be described.

  FIG. 23 is a diagram showing a computer that executes a user attribute information management program. As illustrated in FIG. 23, the computer 1000 has, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.

  The memory 1010 includes a read only memory (ROM) 1011 and a random access memory (RAM) 1012 as illustrated in FIG. The ROM 1011 stores, for example, a boot program such as a BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1090 as illustrated in FIG. The disk drive interface 1040 is connected to the disk drive 1041 as illustrated in FIG. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1041. The serial port interface 1050 is connected to, for example, a mouse 1110 and a keyboard 1120 as illustrated in FIG. The video adapter 1060 is connected to, for example, the display 1130 as illustrated in FIG.

  Here, as illustrated in FIG. 23, the hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the above-mentioned user attribute information management program is stored in, for example, the hard disk drive 1090 as a program module in which an instruction to be executed by the computer 1000 is described.

  In addition, various data described in the above embodiment are stored as program data in, for example, the memory 1010 or the hard disk drive 1090. Then, the CPU 1020 reads the program module 1093 and program data 1094 stored in the memory 1010 and the hard disk drive 1090 into the RAM 1012 as necessary, and executes each processing procedure.

  The program module 1093 and the program data 1094 relating to the user attribute information management program are not limited to being stored in the hard disk drive 1090, for example, stored in a removable storage medium and read by the CPU 1020 via the disk drive 1041 or the like. It may be issued. Alternatively, the program module 1093 and the program data 1094 related to the user attribute information management program are stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.), and a network interface It may be read by the CPU 1020 through 1070.

10, 110 attribute information management server 11 communication processing unit 12 control unit 12a changing unit 12b notification unit 12c transmission unit 13, 113 storage unit 13a attribute information storage unit 13b profile information storage unit 13c Web server information storage unit 20, 20A to 20D Web Server 30, 30A User terminal 40 Leased line information management server 41 Communication processing unit 42 Control unit 42a Information reception unit 42b Information management unit 42c Information transmission unit 43 Storage unit 43a Leased line information storage unit 50 Attribute information management application 60 Web browser N Communication network

Claims (16)

An attribute information management apparatus for managing attribute information of a user, a server for providing a service to a user terminal based on registered user information including predetermined attribute information, and a dedicated line for connecting the server to a communication network A user attribute information management system comprising: a leased line information management server for managing numbers;
The attribute information management device
A storage unit that stores attribute information;
A change unit that changes the attribute information;
A notification unit configured to notify the server of a change in the attribute information when the attribute information is changed by the change unit;
A transmitter configured to transmit attribute information requested by the server to the server;
The server is
A request unit that requests at least a part of the attribute information for which the notification has been received from the attribute information management device when receiving a notification of change of the attribute information from the attribute information management device;
An updating unit for updating user information based on the attribute information when the attribute information requested by the request unit is received;
The leased line information management server
In response to a request from the request unit, a secret key corresponding to the server is transmitted to the server, and when a secret key is received from the attribute information management device, the private line number corresponding to the secret key is An information transmission unit for transmitting to the attribute information management device;
Equipped with
When the request unit receives the notification of the change of the attribute information from the attribute information management device, the request unit requests the leased line information management server to acquire the secret key, and the secret key acquired from the leased line information management server is By transmitting to the attribute information management device, at least a part of the attribute information for which the notification has been accepted is requested,
The transmitting unit transmits the secret key acquired from the server to the leased line information management server, and the number of the dedicated line acquired from the leased line information management server is the number of the dedicated line of the server that has transmitted the secret key. A user attribute information management system characterized by transmitting attribute information requested by the request unit to the server when the number matches. The request unit transmits a credential indicating authenticity of the server to request at least a part of the attribute information for which the notification has been received from the attribute information management apparatus.
The user attribute according to claim 1 , wherein the transmitting unit transmits the attribute information requested by the server to the server when the authenticity based on the credential received from the request unit can be confirmed. Information management system.   The user attribute information management system according to claim 1, wherein the notification unit notifies the server selected by the user of the user terminal of a change in the attribute information. An attribute information management apparatus for managing attribute information of a user, a server for providing a service to a user terminal based on registered user information including predetermined attribute information, and a dedicated line for connecting the server to a communication network A user attribute information management system comprising: a leased line information management server for managing numbers;
The attribute information management device
A storage unit that stores attribute information;
A change unit that changes the attribute information;
When the attribute information is changed by the change unit, an operation of the user of the user terminal is accepted, and permission is given to which server the attribute information after change is distributed, and then the user terminal A notification unit for notifying the server selected by the authorization of the user of the change of the attribute information;
A transmitter for transmitting attribute information requested by the server to the server;
Equipped with
The server is
A request unit that requests at least a part of the attribute information for which the notification has been received from the attribute information management device when receiving a notification of change of the attribute information from the attribute information management device;
When the attribute information requested by the request unit is received, the updating unit updates the user information based on the attribute information
Equipped with
The leased line information management server
In response to a request from the request unit, a secret key corresponding to the server is transmitted to the server, and when a secret key is received from the attribute information management device, the private line number corresponding to the secret key is An information transmission unit for transmitting to the attribute information management device;
Equipped with
When the request unit receives the notification of the change of the attribute information from the attribute information management device, the request unit requests the leased line information management server to acquire the secret key, and the secret key acquired from the leased line information management server is By transmitting to the attribute information management device, at least a part of the attribute information for which the notification has been accepted is requested,
The transmitting unit transmits the secret key acquired from the server to the leased line information management server, and the number of the dedicated line acquired from the leased line information management server is the number of the dedicated line of the server that has transmitted the secret key. when matching the number, characteristics and be Ruyu over the attribute information management system that transmits the attribute information requested by the requesting unit to the server. A user terminal installed with an attribute information management application for managing attribute information of the user, a server providing a service to the user terminal based on registered user information including predetermined attribute information, and the server is connected to a communication network A user attribute information management system having a leased line information management server that manages the numbers of leased lines for
The user terminal is
A storage unit that stores attribute information;
A change unit that changes the attribute information;
A notification unit configured to notify the server of a change in the attribute information when the attribute information is changed by the change unit;
A transmitter configured to transmit attribute information requested by the server to the server;
The server is
A request unit configured to request at least a part of the attribute information for which the notification has been received from the user terminal when the notification for changing the attribute information is received from the user terminal;
An updating unit for updating user information based on the attribute information when the attribute information requested by the request unit is received;
The leased line information management server
In response to a request from the request unit, a secret key corresponding to the server is transmitted to the server, and when a secret key is received from the user terminal, a dedicated line number corresponding to the secret key is transmitted to the user terminal Information transmitter to send to
Equipped with
When the request unit receives a notification of change of attribute information from the user terminal, the request unit requests the leased line information management server to acquire the secret key, and the user acquires the secret key acquired from the leased line information management server. Requesting at least part of the attribute information for which the notification has been accepted by transmitting to the terminal;
The transmitting unit transmits the secret key acquired from the server to the leased line information management server, and the number of the dedicated line acquired from the leased line information management server is the number of the dedicated line of the server that has transmitted the secret key. A user attribute information management system characterized by transmitting attribute information requested by the request unit to the server when the number matches. The request unit requests the user terminal at least a part of the attribute information for which the notification has been accepted, by transmitting a credential indicating the authenticity of the server.
The user attribute according to claim 5 , wherein the transmitting unit transmits the attribute information requested by the server to the server when the authenticity based on the credential received from the request unit can be confirmed. Information management system. The user attribute information management system according to claim 5 , wherein the notification unit notifies the server selected by the user of the change of the attribute information. A user terminal installed with an attribute information management application for managing attribute information of the user, a server providing a service to the user terminal based on registered user information including predetermined attribute information, and the server is connected to a communication network A user attribute information management system having a leased line information management server that manages the numbers of leased lines for
The user terminal is
A storage unit that stores attribute information;
A change unit that changes the attribute information;
When the attribute information is changed by the change unit, an operation of the user of the user terminal is accepted, and permission is given to which server the attribute information after change is distributed, and then the user terminal A notification unit for notifying the server selected by the authorization of the user of the change of the attribute information;
A transmitter for transmitting attribute information requested by the server to the server;
Equipped with
The server is
A request unit configured to request at least a part of the attribute information for which the notification has been received from the user terminal when the notification for changing the attribute information is received from the user terminal;
When the attribute information requested by the request unit is received, the updating unit updates the user information based on the attribute information
Equipped with
The leased line information management server
In response to a request from the request unit, a secret key corresponding to the server is transmitted to the server, and when a secret key is received from the user terminal, a dedicated line number corresponding to the secret key is transmitted to the user terminal Information transmitter to send to
Equipped with
When the request unit receives a notification of change of attribute information from the user terminal, the request unit requests the leased line information management server to acquire the secret key, and the user acquires the secret key acquired from the leased line information management server. Requesting at least part of the attribute information for which the notification has been accepted by transmitting to the terminal;
The transmitting unit transmits the secret key acquired from the server to the leased line information management server, and the number of the dedicated line acquired from the leased line information management server is the number of the dedicated line of the server that has transmitted the secret key. when matching the number, characteristics and be Ruyu over the attribute information management system that transmits the attribute information requested by the requesting unit to the server. An attribute information management apparatus for managing attribute information of a user, a server for providing a service to a user terminal based on registered user information including predetermined attribute information, and a dedicated line for connecting the server to a communication network A user attribute information management method executed by a user attribute information management system having a leased line information management server for managing numbers, comprising:
The attribute information management device includes a storage unit that stores attribute information.
A changing step of changing the attribute information;
A notifying step of notifying the server of a change in the attribute information when the attribute information is changed in the changing step;
A request step of requesting at least a part of the attribute information for which the notification has been received from the attribute information management device, when the server receives a notification of change of the attribute information from the attribute information management device;
A transmitting step of transmitting the attribute information requested by the server to the server, when the attribute information management device receives the notified request for the attribute information from the server;
When the server receives attribute information requested by the request step, the server updates the user information based on the attribute information.
The dedicated line information management server transmits the secret key corresponding to the server to the server in response to the request by the request step, and when the secret key is received from the attribute information management device, the private line information management server supports An information transmitting step of transmitting the number of the leased line to the attribute information management device;
Including
The request step requests the leased line information management server to obtain the secret key when the notification of change of attribute information is received from the attribute information management device, and the secret key acquired from the leased line information management server is By transmitting to the attribute information management device, at least a part of the attribute information for which the notification has been accepted is requested,
In the transmitting step, the private line number acquired from the leased line information management server by transmitting the secret key acquired from the server to the leased line information management server is the private line of the server that has transmitted the secret key. A method of managing user attribute information, comprising transmitting the attribute information requested by the request step to the server if the number matches. The requesting step sends at least a part of the attribute information for which the notification has been accepted to the attribute information management device by transmitting a credential indicating the authenticity of the server.
10. The user attribute according to claim 9 , wherein the transmitting step transmits the attribute information requested by the server to the server when the authenticity based on the received credential is confirmed by the request step. Information management method. 10. The user attribute information management method according to claim 9 , wherein the notifying step notifies the server selected by the user of a change in the attribute information. An attribute information management apparatus for managing attribute information of a user, a server for providing a service to a user terminal based on registered user information including predetermined attribute information, and a dedicated line for connecting the server to a communication network A user attribute information management method executed by a user attribute information management system having a leased line information management server for managing numbers, comprising:
The attribute information management device includes a storage unit that stores attribute information.
A changing step of changing the attribute information;
When the attribute information is changed in the changing step, an operation of the user of the user terminal is accepted, and the server is authorized to distribute the changed attribute information, and then the user terminal is changed. Notifying the server selected by the authorization of the user of the change of the attribute information;
A request step of requesting at least a part of the attribute information for which the notification has been received from the attribute information management device, when the server receives a notification of change of the attribute information from the attribute information management device;
A transmitting step of transmitting the attribute information requested by the server to the server, when the attribute information management device receives the notified request for the attribute information from the server;
When the server receives attribute information requested by the request step, the server updates the user information based on the attribute information.
Including
The dedicated line information management server transmits a secret key corresponding to the server to the server in response to the request by the request step, and when the secret key is received from the attribute information management device, the private line information management server responds to the secret key. Including an information transmitting step of transmitting the number of the leased line to the attribute information management device;
The request step requests the leased line information management server to obtain the secret key when the notification of change of attribute information is received from the attribute information management device, and the secret key acquired from the leased line information management server is By transmitting to the attribute information management device, at least a part of the attribute information for which the notification has been accepted is requested,
In the transmitting step, the private line number acquired from the leased line information management server by transmitting the secret key acquired from the server to the leased line information management server is the private line of the server that has transmitted the secret key. when matching the number, characteristics and be Ruyu over the attribute information management method that transmits the attribute information requested by the request step to the server. A user terminal installed with an attribute information management application for managing attribute information of the user, a server providing a service to the user terminal based on registered user information including predetermined attribute information, and the server is connected to a communication network A user attribute information management method executed by a user attribute information management system having a leased line information management server for managing a dedicated line number for
The user terminal includes a storage unit that stores attribute information.
A changing step of changing the attribute information;
A notifying step of notifying the server of a change in the attribute information when the attribute information is changed in the changing step;
A request step of requesting at least a part of the attribute information for which the notification has been received from the user terminal, when the server receives a notification of change of the attribute information from the user terminal;
The transmission step of transmitting the attribute information requested by the request step to the server, when the user terminal receives the notified request for the attribute information from the server;
When the server receives attribute information requested by the request step, the server updates the user information based on the attribute information.
The dedicated line information management server transmits a secret key corresponding to the server to the server in response to a request by the request step, and when a secret key is received from the user terminal, a dedicated key corresponding to the secret key An information transmitting step of transmitting a line number to the user terminal;
Including
The request step requests the leased line information management server to acquire the secret key when the notification of the change of the attribute information is received from the user terminal, and the user acquires the secret key acquired from the leased line information management server. Requesting at least part of the attribute information for which the notification has been accepted by transmitting to the terminal;
In the transmitting step, the private line number acquired from the leased line information management server by transmitting the secret key acquired from the server to the leased line information management server is the private line of the server that has transmitted the secret key. A method of managing user attribute information, comprising transmitting the attribute information requested by the request step to the server if the number matches. The requesting step requests the user terminal from the user terminal at least a part of the attribute information for which the notification has been received, by transmitting a credential indicating the authenticity of the server.
Said transmitting step, when the authenticity based on the credentials received from the requesting process is confirmed, the user according to claim 1, wherein the transmitting the attribute information requested by the server to the server Attribute information management method. The notification process, the server selected by the user, the user attribute information management method according to claim 1, wherein the notifying the change of the attribute information. A user terminal installed with an attribute information management application for managing attribute information of the user, a server providing a service to the user terminal based on registered user information including predetermined attribute information, and the server is connected to a communication network A user attribute information management method executed by a user attribute information management system having a leased line information management server for managing a dedicated line number for
The user terminal includes a storage unit that stores attribute information.
A changing step of changing the attribute information;
When the attribute information is changed in the changing step, an operation of the user of the user terminal is accepted, and the server is authorized to distribute the changed attribute information, and then the user terminal is changed. Notifying the server selected by the authorization of the user of the change of the attribute information;
A request step of requesting at least a part of the attribute information for which the notification has been received from the user terminal, when the server receives a notification of change of the attribute information from the user terminal;
The transmission step of transmitting the attribute information requested by the request step to the server, when the user terminal receives the notified request for the attribute information from the server;
When the server receives attribute information requested by the request step, the server updates the user information based on the attribute information.
Including
The dedicated line information management server transmits a secret key corresponding to the server to the server in response to a request by the request step, and when a secret key is received from the user terminal, a dedicated key corresponding to the secret key Including an information transmission step of transmitting a line number to the user terminal;
The request step requests the leased line information management server to acquire the secret key when the notification of the change of the attribute information is received from the user terminal, and the user acquires the secret key acquired from the leased line information management server. Requesting at least part of the attribute information for which the notification has been accepted by transmitting to the terminal;
In the transmitting step, the private line number acquired from the leased line information management server by transmitting the secret key acquired from the server to the leased line information management server is the private line of the server that has transmitted the secret key. when matching the number, characteristics and be Ruyu over the attribute information management method that transmits the attribute information requested by the request step to the server.

Images