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

Abstract

PROBLEM TO BE SOLVED: To suitably provide attribute information of a user to a server.SOLUTION: An attribute information management server 10 confirms a user terminal 30 for permission for providing attribute information to a web server 20 and has an attribute value selected by the user terminal 30 regarding the attribute information registering a plurality of attribute values when a request occurs for the attribute information of one of types among the attribute information of a plurality of types. Then, the attribute information management server 10 creates the attribute value corresponding to the requested type of attribute value when permission is confirmed for providing the attribute information to a web server 20 as well as accepting the selection of the registering attribute values, and a profile of the selected attribute value. Next, the attribute information management server 10 transmits the created profile of the attribute information to the web server 20. Then, the web server 20 carries out user registration by using the attribute information when the requested attribute information is received from the attribute information management server 10.SELECTED DRAWING: Figure 1

Description

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

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

  The user performs user registration necessary for using the service provided by the other service provider in the Web server 200B of the other service provider, and at the time of user registration, the other service provider The attribute information of the user is acquired. On the other hand, user registration is required for the user to use the service provided by the service provider, but the attribute information of the user registered at that time is held by the other service provider. Get from attribute information.

  Therefore, an alliance for distributing the user's attribute information between the service provider and the other service provider in advance is established between the service provider and the other service provider. The service provider makes an application to the other service provider in advance, and obtains permission for performing a procedure when the service provider's Web server 200A 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. 18 is a block diagram for explaining the operation of each component of a conventional user attribute information distribution system. The user has registered his / her attribute information when using the service of the Web server 200B of another service provider. When a user registers with the service provider's Web server 200A, the service provider's Web server 200A acquires an access right to the other service provider's Web server 200B whose attribute information has been registered. (See (1) in FIG. 18).

  When performing user registration, the service provider's Web server 200A transmits an access right acquisition message to another service provider's Web server 200B in order to acquire user attribute information necessary for providing the service. ((2) in FIG. 18). Further, when a request token indicating an access right request is acquired from the other service provider's Web server 200B, the request token is redirected to the other service provider's Web server 200B, and the user is given access right to the other service provider. Authorization is requested ((3) in FIG. 18).

  Further, after authorization of the user, a request indicating an access right request is transmitted to another service provider's Web server 200B and exchanged for an access token indicating the access right ((5) in FIG. 18). Then, using the application interface defined by the Web server 200B of the other service provider, the user attribute information is acquired from the Web server 200B of the other service provider using the access token as a parameter ((6 in FIG. 18). )).

  Upon receiving the access right acquisition message from the service provider's Web server 200A, the other service provider's Web server 200B issues a request token and transmits it to the service provider's Web server 200A ((2) in FIG. 18). ). When redirected from the service provider's Web server 200A after the transmission of the request token, the user confirms whether the stored user attribute information can be distributed to the service provider's Web server 200A. The result is redirected again to the service provider's Web server 200A ((4) in FIG. 18).

  FIG. 19 shows a conventional signal sequence for distributing user attribute information. First, in order to use a service provided by another service provider, the user terminal 300 accesses the portal site of the Web server 200B of the other service provider from the user terminal 300 (steps S1 and S2), and then performs user registration. (Steps S3, 4). When registering a user, the user transmits his / her attribute information such as a name, an e-mail address, and a credit card number to other service providers.

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

  Upon receiving the user registration request, the service provider's Web server 200A pays out the user's account name (step S8), and then sends the other service provider's Web server 200B to the other service provider's Web server 200B. An access right request is transmitted (step S9).

  Upon receiving the access right request, the other service provider's Web server 200B transmits a request token indicating the access right request to the service provider's Web server 200A as an access right response (step S10). When the request token is transmitted to the Web server 200A of the service provider, the access right is not authorized by the user.

  Upon receiving the request token, the service provider's Web server 200A uses the unauthenticated request token as a parameter and requests the user registration request from another service provider's Web server in order to request the user to grant the access right. Redirect to 200B (step S11). Then, the Web server 200B of the other service provider transmits a response to the redirect to the user terminal 300 (Step S12).

  When a user who receives a response from another service provider's Web server 200B logs in to the other service provider's Web server 200B (step S13), the other service provider's Web server 200B receives the other service provider's Web server 200B. The user is inquired about whether to give the access right to the web server 200B to the web server 200A of the service provider (step S14).

  When the user authorizes the access right (step S15), the other service provider's web server 200B redirects to the service provider's web server 200A using the authorized request token as a parameter (step S16).

  The service provider's web server 200A transmits an access token request including an authorized request token to the other service provider's web server 200B (step S17), and indicates the access right in exchange for the authorized request token. An access token is acquired (step S18).

  The service provider's Web server 200A uses an interface preliminarily defined by another service provider, uses the access token as a parameter, and sends an acquisition request for user attribute information to the other service provider's Web server. 200B (step S19), and user attribute information necessary for user registration is acquired from the web server 200B of another service provider (step S20). Thereafter, the service provider Web server 200A performs user registration based on the acquired user attribute information, and responds to the user with a user registration (step S21).

  As described above, when the user terminal 300 performs user registration with the service provider's Web server 200A, the service provider's Web server 200A can be used for the specific other service provider holding the user's attribute information. 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.

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

  However, in the above-described conventional technology, user attribute information is acquired between Web servers, and thus depends on the content of the user attribute information held by the Web server from which the user attribute information is acquired. There has been a problem that the attribute information of the user cannot be appropriately provided to the original Web server.

  For example, when a user registers as a user on a large number of service provider's Web servers, the attribute information of the user necessary to provide a service to the user may be different for each Web server. To explain with a specific example, a credit card number is required for a service involving payment, but a credit card number is not required for a free mail distribution service.

  A specific other service provider's Web server from which the service provider's Web server obtains user attribute information includes a user required for the specific other service provider to provide a service to the user. Only the attribute information is stored. Therefore, depending on the service provider's Web server, the service may not be provided to the user only with the user attribute information that can be acquired from the other service provider's Web server.

  Further, when the user attribute information held by the other service provider is changed due to a change in the content of the service provided by the other service provider, the user attribute information that can be acquired from the other service provider is also displayed. It becomes difficult for the service provider to continue the service. Further, there may be a case where the attribute information of the user held by the other service provider cannot be acquired depending on the operation status of the service by the other service provider.

  Also, the value of specific attribute information registered in the Web server of a specific other service provider can only be registered in the Web server to be registered as a user. For example, even if the user holds a plurality of e-mail addresses, they cannot be used for each service provider.

  Accordingly, the present invention has been made to solve the above-described problems of the prior art, and an object thereof is to appropriately provide user attribute information to a Web server.

  In order to solve the above-described problems and achieve the object, a user attribute information management system provides services to an attribute information management apparatus that manages user attribute information and a user terminal that has been registered using predetermined attribute information. The attribute information management system includes a storage unit that stores one or a plurality of attribute values for a plurality of types of attribute information, and the plurality of types of attributes. If there is a request for any kind of attribute information among the information, the user terminal confirms authorization for providing the attribute information to the server, and the attribute information in which a plurality of attribute values are registered For, the confirmation unit that causes the user terminal to select an attribute value, and the confirmation unit confirms the authorization to provide the attribute information to the server, and When the selection of the attribute value to be registered is accepted, the creation unit that creates the attribute value corresponding to the requested type of attribute information and the profile of the selected attribute value, and the creation unit A transmission unit that transmits a profile of attribute information to the server, and when the server receives a user registration request from the user terminal, the server transmits attribute information necessary for the user registration to the attribute information management device. A requesting unit for requesting and a registration unit for performing user registration using the attribute information when the attribute information requested by the requesting unit is received.

  The user attribute information management system and the user attribute information management method disclosed in the present application have an effect of appropriately providing user attribute information to the server.

FIG. 1 is a schematic configuration diagram showing the overall configuration of the user attribute information management system according to the first embodiment. FIG. 2 is a block diagram showing a configuration of the attribute information management server according to the first embodiment. FIG. 3 is a diagram illustrating an example of a table stored in the attribute information storage unit. FIG. 4 is a diagram illustrating 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 user attribute information acquisition processing in the user attribute information management system according to the first embodiment. FIG. 7 is a sequence diagram illustrating 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 illustrating a screen display example displayed on the user terminal. FIG. 9 is a diagram illustrating an overview of the user attribute information management system according to the first embodiment. FIG. 10 is a diagram illustrating the flow of user attribute information acquisition processing in the user attribute information management system according to the second embodiment. FIG. 11A is a sequence diagram illustrating the flow of user attribute information management processing in the user attribute information management system according to the second embodiment. FIG. 11-2 is a sequence diagram illustrating the flow of user attribute information management processing in the user attribute information management system according to the second embodiment. FIG. 12 is a diagram illustrating the flow of user attribute information acquisition processing in the user attribute information management system according to the third embodiment. FIG. 13 is a block diagram illustrating a configuration of a user terminal according to the third embodiment. FIG. 14 is a sequence diagram illustrating the flow of user attribute information management processing in the user attribute information management system according to the third embodiment. FIG. 15 is a diagram for explaining the outline of the user attribute information management system according to the third embodiment. FIG. 16 is a diagram illustrating a computer that executes a program. FIG. 17 is a diagram showing an outline of a conventional user attribute information distribution system. FIG. 18 is a block diagram for explaining the operation of each component of a conventional user attribute information distribution system. FIG. 19 is a sequence diagram for explaining the flow of processing of a conventional user attribute information distribution system.

  Hereinafter, embodiments of a user attribute information management system and a user attribute information management method according to the present application will be described in detail with reference to the drawings. The user attribute information management system and the user attribute information management method according to the present application are not limited by this embodiment.

[First embodiment]
In the following embodiments, the configuration of the user attribute information management system according to the first embodiment, the configuration of the attribute information management server, the configuration of the Web server, and the processing flow in the user attribute information management system will be described in order. Next, 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 the overall configuration of the user attribute information management system according to the first embodiment.

  As shown in FIG. 1, a user attribute information management system 100 includes an attribute information management server 10, a plurality of service provider Web servers 20 </ b> A and 20 </ b> B, and a user terminal 30, which are connected via a communication network 40. ing. In addition, the number of each apparatus shown in FIG. 1 is an example to the last, and is not restricted to this. The web servers 20A and 20B are referred to as the web server 20 when they are not particularly distinguished.

  The attribute information management server 10 is connected to a communication network 40 such as an access network of the telecommunications carrier or the Internet. The user stores and centrally manages the attribute information of the user with respect to the user terminal 30, or the service provider's It supports to use different attribute information when using the Web service.

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

  In addition, the service provider provides user attribute information necessary for the service provider to provide the service with the user's authorization. The user attribute information provided to the service provider is managed for each account issued when the user registers as a user in the service provider's Web server 20, and the user own attribute information provided to the service provider. View and confirm for each account.

  The plurality of service provider Web servers 20 </ b> A and 20 </ b> B are servers that provide services to the user terminal 30. When receiving the user registration of the user terminal 30 from the user terminal 30, the service provider Web servers 20 </ b> A and 20 </ b> B requests acquisition of the access right to the attribute information management server 10, and the user information held by the attribute information management server 10. Process to get attribute information.

  The user terminal 30 is an information processing device used by a user. In order to use the service provider's Web server 20, the user terminal 30 accesses the portal site of the service provider's Web server 20 and performs user registration. When this user registration is performed, the user terminal 30 instructs the Web server 20 of the service provider to acquire an access right to the attribute information management server 10.

[Configuration of attribute information management server]
Next, the configuration of the attribute information management server shown in FIG. 1 will be described with reference to FIG. FIG. 2 is a block diagram showing a configuration of the attribute information management server according to the first embodiment. As illustrated 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 units will be described below.

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

  The GUI processing unit 14 has an interface for a user to register, modify, delete, and browse his / her own attribute information in the attribute information management server 10 and an interface for browsing his / her own attribute information provided to each Web server 20. Performs 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 has an attribute information storage unit 13 a and a profile information storage unit 13 b that are particularly closely related to the present invention.

  The attribute information storage unit 13a stores one or more attribute values corresponding to a plurality of types of attribute information. The attribute information stored in the attribute information storage unit 13 a is user attribute information 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 includes a “user ID” that uniquely identifies the user, the “name” of the user, the “date of birth” of the user, and the “address” of the user. And “phone number” of the phone owned by the user, “credit number” of the credit card etc. owned by the user, and “mail address” possessed by the user are stored in association with each other. Here, the attribute information storage unit 13a may store a plurality of attribute values for the same type of attribute information. For example, in the example of FIG. 3, two attribute values “XXX@XXX.co.jp” and “XXX@XXX.co.jp” are stored as the attribute information “mail address”.

  The profile information storage unit 13b stores a profile created by the creation unit 12b described later. For example, as illustrated in FIG. 4, the profile information storage unit 13 b includes the “account name” of the user and “URL of the Web server” that is information for identifying the Web server 20 to which the attribute information is registered. The “name” of the user, the “birth date” of the user, and the “mail address” possessed by the user are stored. Here, the type of attribute information included in the profile information differs depending on the Web server 20 to which the user is registered.

  The control unit 12 has an internal memory for storing a program that defines various processing procedures and necessary data, and performs various processes using them, and particularly as closely related to the present invention, It has the confirmation part 12a, the preparation part 12b, and the transmission part 12c.

  When there is a request for any kind of attribute information among a plurality of types of attribute information, the confirmation unit 12a confirms authorization for providing the attribute information to the Web server 20 with the user terminal 30. For the attribute information in which the attribute value is registered, the user terminal 30 is made to select the attribute value. Specifically, when there are a plurality of attribute values corresponding to the attribute information requested from the Web server 20, the confirmation unit 12 a authorizes the user terminal 30 to provide the attribute information to the Web server 20. When confirming, the user terminal 30 is made to select the attribute value registered in the Web server 20.

  For example, when there is a request for attribute information including, as a parameter, the account name issued by the Web server 20 to the user terminal that requested the user registration, the confirmation unit 12a includes an unauthorized request token embedded with the account name. When the request token is received from the web server 20 by redirection through the user terminal 30, the user terminal 30 is inquired about authorization for providing the attribute information to the web server 20, and the authorized request token Is received from the user terminal 30 to confirm the authorization to provide the attribute information to the Web server 20.

  When the confirmation unit 12a confirms the authorization of provision of attribute information to the Web server and accepts selection of an attribute value to be registered, the creation unit 12b corresponds to the type of attribute information requested. Create an attribute value and a profile of the selected attribute value.

  The transmission unit 12 c transmits the attribute information profile created by the creation unit 12 b to the Web server 20. Specifically, after transmitting the authorized request to the Web server 20 by redirection via the user terminal 30, the transmitting unit 12c receives the authorized request token, and then accesses the account name embedded therein. When the token is transmitted to the Web server 20 and the attribute information acquisition request using the access token is received, the profile of the attribute information created by the creation unit 12b is transmitted to the Web server 20.

[Web server configuration]
Next, the configuration of the Web server 20 shown in FIG. 1 will be described with reference to FIG. FIG. 5 is a block diagram showing the configuration of the Web server according to the first embodiment. As illustrated 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 units will be described below.

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

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

  The control unit 22 has an internal memory for storing a program that defines various processing procedures and the necessary data, and executes various processes using these programs. Particularly, as closely related to the present invention, It has a request unit 22a and a registration unit 22b.

  When the request unit 22a receives an instruction requesting the attribute information management server 10 for attribute information necessary for user registration using the account name as a parameter together with a user registration request from the user terminal 30, the request name is used as a parameter. In addition, the attribute information management server 10 is requested for attribute information necessary for the user registration. Specifically, when receiving a user registration request from the user terminal 30, the request unit 22 a requests the attribute information management server 10 for attribute information necessary for the user registration. When the request unit 22 a receives an unauthorized request token, the request unit 22 a transmits the request token to the attribute information management server 10 by redirection through the user terminal 30.

  Subsequently, when the request unit 22a receives the authorized request token from the attribute information management server 10 through redirection via the user terminal 30, the request unit 22a manages the access token using the authorized request token. Request to server 10. After that, when receiving the access token from the attribute information management server, the request unit 22a transmits an attribute information acquisition request using the access token to the attribute information management server 10.

  When receiving the attribute information requested by the request unit 22a, the registration unit 22b performs user registration using the attribute information. Specifically, the registration unit 22b performs user registration based on the user attribute information acquired from the attribute information management server 10, and sends a user registration response to the user.

[Processing by user attribute information management system]
Here, the flow of user attribute information acquisition processing 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 user attribute information acquisition processing in the user attribute information management system according to the first embodiment.

  As shown in FIG. 6, the user terminal 30 registers its own attribute information in the attribute information management server 10 in advance. At this time, if there are a plurality of values for one attribute, those values are registered respectively. Thereafter, when user registration with the service provider's Web server 20 is started, the attribute information of the service provider's Web server 20 is set with the account name issued by the service provider's Web server 20 as a parameter. A message instructing to acquire the access right to the attribute information management server 10 that holds the message is transmitted (see (1) in FIG. 6).

  Subsequently, when the attribute information management server 10 receives the access right request message from the service provider's Web server 20, the account name of the user issued by the service provider's Web server 20 in the request token indicating the access right request. Is transmitted to the service provider's Web server 20 (see (2) in FIG. 6). Then, the service provider's Web server 20 redirects the request token to the attribute information management server 10 via the user terminal 20 (see (3) in FIG. 6).

  Then, the user selects the value of his / her attribute to be registered in the service provider's Web server 20 from the attribute information management server 10 for the attribute information for which a plurality of values are set (see (4) in FIG. 6). . When the user selects his / her own attribute information to be registered in the service provider's Web server 20, a profile in which the attribute information is listed is created and managed for each user account name ((5) in FIG. 6). reference).

  The attribute information management server 10 authorizes the distribution of attribute information to the Web server 20 of the service provider, and redirects the approved request token to the Web server 20 via the user terminal 30 (see (6) in FIG. 6). ). This authorizes the distribution of the attribute information selected by the service provider's Web server.

  Then, the attribute information management server 10 associates the request token with the account requesting the access right to the attribute information management server 10. The attribute information management server 10 also sets the user's account name and sends it to the service provider's Web server 20 for the access token to be paid out after the user's authorization (see (7) in FIG. 6). Then, an account having an access right to the attribute information management server 10 is associated with an access token.

  When the service provider's Web server 20 transmits an access right request message to the attribute information management server 10, it adds the account name of the user to the parameter. Further, when the user attribute information is acquired using the application interface of the attribute information management server 10, the profile managed by the attribute management information server 10 for each account name is accessed ((8 in FIG. 6). )reference).

  For the account name set in the access right acquisition message by the service provider's Web server 20, the value after one-way encryption of the account name such as a hash function is used from the viewpoint of user privacy. May be. In this case, the account name set in the request token or access token is also a value after one-way encryption. The profile managed by the attribute information management server 10 is also managed for each value after one-way encryption.

  As described above, the attribute information management server 10 is arranged on the communication network 40 for the user to store and centrally manage his / her attribute information. In addition to the authorization of distribution of attribute information by a conventional user, it is possible for the user to select an attribute value 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. Therefore, the account name of the user issued 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 determines the attribute value selected by the user and other Web server 20. A profile that lists the attribute information to be registered is created and attached to the account name, and the attribute information to be registered for each Web server 20 is managed.

  As a result, the user can selectively use his / her own attribute information registered for each Web server 20. Further, the Web server 20 can provide a service without depending on the operation status of the service of another service provider holding the user attribute information or the user attribute information held.

  That is, in the user attribute information management system 100 according to the first embodiment, the attribute information management server 10 that stores and centrally manages user attribute information is a Web of a service provider that provides a service on the communication network 40. By allowing the user to use different attribute values to be registered in the Web server 20 for each server 20, the user can register his / her optimum attribute information for each Web server. The service provider holds user attribute information by acquiring user attribute information necessary for providing the service from the attribute information management server 10 for the user to store and centrally manage the attribute information. The service can be provided without depending on the service operation status of the other service providers that are operating and the attribute information of the held users.

  Next, processing performed by the user attribute information management system 100 according to the first embodiment will be described with reference to FIG. FIG. 7 is a sequence diagram illustrating 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, the user terminal 30 is a portal site of the attribute information management server 10 that supports unified management of its own attribute information in order to use a service provided by a service provider on the communication network 40. Is accessed (step S101). Then, the attribute information management server 10 transmits portal screen information and the like to the user terminal 30 as a response to the access (step S102).

  Subsequently, the user terminal 30 registers its own attribute information (step S103), and the attribute information management server 10 notifies that the registration is completed (step S104). The attribute information includes your name, e-mail address, credit card number, etc. For attribute information held by the user, such as e-mail address and credit card number, set the value of each attribute. sign up.

  Then, the user accesses the portal site of the service provider's Web server 20 from the user terminal 30 in order to use the service provided by the service provider (steps S105 and S106), and then requests the user registration with the desired account name. Is performed (step S107). At this time, the user terminal 30 instructs the service provider's Web server 20 to acquire an access right to the attribute information management server 10.

  Subsequently, the Web server 20 of the service provider that has received the user registration request pays out the account name of the user (step S108), and then transmits a request for access right to the attribute information management server to the attribute information management server 10. (Step S109). In the access right request, the account name is set as a parameter.

  Then, the attribute information management server 10 that has received the access right request transmits a request token indicating the access right request to the service provider's Web server 20 as an access right response (step S110). An area for setting the account name is defined in the format of the request token, and the account having the access right to the attribute information management server is associated with the request token by setting the account name in the request token. When the request token is transmitted to the Web server 20 of the service provider, the access right is not authorized by the user.

  The Web server 20 of the service provider that has received the request token redirects the user registration request to the attribute information management server 10 using the unauthenticated request token as a parameter in order to request the user to grant the access right. (Step S111).

  When the user terminal 30 receives a response from the attribute information management server 10 (step S112) and logs in to the attribute information management server 10 (step S113), the attribute information management server 10 accesses the attribute information management server 10. The user is inquired about whether to grant the right to the service provider's Web server 20 (step S114). At the same time, with regard to the attributes that are distributed to the service provider's Web server 20, for attributes whose values are registered in the attribute information management server 10, a list of those values is created and the service provider's The user is allowed to select the value of his / her attribute to be distributed to the Web server 20 (step S115).

  Here, an example of a screen displayed on the user terminal 30 when the user selects an attribute value will be described with reference to FIG. FIG. 8 is a diagram illustrating a screen display example displayed on the user terminal. As illustrated in FIG. 8, for example, the user terminal 30 displays an account name, and “name”, “birth date”, and “mail address” as its own attribute information to be distributed. For “mail address”, two attributes “XX@XXX.co.jp” and “XXX@XXX.co.jp” are used to allow the user to select from a plurality of attribute values. A “select” button corresponding to each value is displayed, and an attribute value to be registered is selected by pressing any “select” button. Further, the user terminal 30 displays an “execute” button and a “cancel” button. When the “execute” button is pressed, it is determined to give the access right to the attribute information management server 10 to the Web server 20 of the service provider for the displayed attribute information. If the “Cancel” button is pressed, user registration is canceled.

  Returning to the description of FIG. 7, when the user terminal 30 grants the access right, the attribute information management server 10 acquires the authorized request token and the value of the attribute selected by the user from the user terminal 30 (steps). S116).

  Then, the attribute information management server 10 acquires the account name of the user from the authorized request token (step S117). Then, the attribute information management server 10 creates a profile by listing the values of its own attributes selected by the user and binding them with the account name of the user (step S118).

  Then, the attribute information management server 10 redirects to the service provider's Web server 20 using the approved request token as a parameter (step S119). Subsequently, the service provider's Web server 20 requests an access token indicating an access right from the attribute information management server 10 in exchange for the authorized request token (step S120).

  Then, the attribute information management server 10 sends the access token to the service provider's Web server 20 (step S121). In the format of the access token, an area for setting the account name of the user is defined, and the account name is set in the access token so that the account having access rights to the attribute information management server 10 can be associated with the access token. Put it on.

  The service provider's Web server 20 uses the application interface defined in advance by the attribute information management server 10 and uses the access token as a parameter, and the attribute information of the user necessary for user registration from the attribute information management server 10 Is requested (step S122).

  The attribute information management server 10 identifies the profile attached to the account name from the account name of the user set in the access token, and sends the attribute information to the Web server 20 of the service provider (step) S123). The service provider's Web server 20 performs user registration based on the user attribute information acquired from the attribute information management server 10, and sends a user registration response to the user terminal 30 (step S124).

  In this way, the attribute information management server 10 is connected to a communication network 40 such as an access network of the telecommunications carrier or the Internet, and the user stores and centrally manages its own attribute information for the user terminal 30, It supports the use of different 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, the respective information is registered. The attribute information registered by the user terminal 30 is appropriately browsed and corrected from the portal site of the attribute information management server 10.

  In addition, the service provider provides user attribute information necessary for the service provider to provide the service with the user's authorization. The user attribute information provided to the service provider is managed for each account issued when the user registers as a user in the service provider's Web server 20, and the user own attribute information provided to the service provider. View and confirm for each account.

  When the attribute information management server 10 holds the user attribute information, the attribute information management server 10 issues an ID for identifying the user and manages the ID. The user's attribute information registered in the attribute information management server 10 and the user's attribute information registered in the service provider's Web server 20 are managed in association with the ID.

  Further, 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 Web server 20 acquires user 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 Web server 20 applies the attribute information management server. Get permission to do the procedure to access 10.

[Effect of the first embodiment]
As described above, the attribute information management server 10 stores one or a plurality of attribute values for a plurality of types of attribute information. When the web server 20 receives a user registration request from the user terminal 30, the web server 20 requests the attribute information management server 10 for attribute information necessary for the user registration. Subsequently, the attribute information management server 10 authorizes the user terminal 30 to provide the attribute information to the Web server 20 when there is a request for any kind of attribute information among a plurality of types of attribute information. As for the attribute information in which a plurality of attribute values are registered, the user terminal 30 is made to select the attribute value. Then, the attribute information management server 10 responds to the requested type of attribute information when the authorization of provision of the attribute information to the Web server 20 is confirmed and the selection of the attribute value to be registered is accepted. Create an attribute value and a profile of the selected attribute value. Subsequently, the attribute information management server 10 transmits the created profile of attribute information to the Web server 20. When the Web server 20 receives the requested attribute information from the attribute information management server 10, the Web server 20 performs user registration using the attribute information. For this reason, it is possible to appropriately provide user attribute information to the Web server 20.

  Further, when a user registers with the Web server 20 of a service provider that provides a service to the user, the attribute information management server of the central management destination stores the user attribute information necessary for the Web server 20 to provide the service. 10, many Web servers 20 provide services to users without depending on the contents of the user attribute information held by the Web server 20 of the specific service provider from which the user attribute information is acquired. It is possible to provide.

  In addition, when a user registers with a Web service of a service provider, a function for selecting a value of an attribute that the user registers in the Web server 20 is added to an existing authorization protocol for a user attribute having a plurality of values. By adding, it is possible for the user to use different attribute values for each Web server to be registered.

[Second Embodiment]
In the first embodiment described above, the case where the user selects the attribute information value when allowing the attribute information distribution has been described. However, the present invention is not limited to this. You may make it select the value of attribute information, when acquiring attribute information. In the second embodiment described below, a case where the value of attribute information is selected when the Web server acquires attribute information from the attribute information management server will be described. Note that the description of the configuration and processing common to the first embodiment is omitted.

  Since the configuration of the attribute information management 10 is the same as that in FIG. 2 described above, the description is omitted, but the Web server selects the attribute information value when acquiring the attribute information from the attribute information management server. The processing content of the part 12a is different. The confirmation unit 12a of the attribute information management server 10 according to the second embodiment provides the attribute information to the Web server 20 when there is a request for any kind of attribute information among a plurality of types of attribute information. If the user terminal 30 is checked for authorization to do so and the authorization for providing the attribute information to the Web server 20 is confirmed, there may be a plurality of attribute values corresponding to the attribute information requested from the Web server 20. For example, when the Web server 20 acquires attribute information from the attribute information management server 10, the user terminal 30 is made to select an attribute value to be registered in the Web server 20.

  Next, a flow of user attribute information acquisition processing in the user attribute information management system 100A according to the second embodiment will be described with reference to FIG. FIG. 10 is a diagram illustrating the flow of user attribute information acquisition processing in the user attribute information management system according to the second embodiment.

  The user terminal 30 registers its own attribute information in the attribute information management server 10 in advance. At this time, if there are a plurality of values for one attribute, those values are registered respectively. Thereafter, when user registration with the service provider's Web server 20 is started, the attribute information of the service provider's Web server 20 is set with the account name issued by the service provider's Web server 20 as a parameter. A message instructing to acquire the access right to the attribute information management server 10 that holds the message is transmitted (see (1) in FIG. 10).

  Further, after authorizing the service provider's Web server 20 to distribute its own attribute information (see (4) in FIG. 10), the service provider's Web server 20 receives the attribute information from the attribute information management server 10. Is acquired, the value of its own attribute information registered in the service provider's Web server 20 is selected (see (8) in FIG. 10).

  Upon receiving the access right request message from the service provider's Web server 20, the attribute information management server 10 sets the account name of the user issued by the service provider's Web server 20 in the request token indicating the access right request. To the service provider's Web server 20 (see (2) in FIG. 10).

  Then, the request token is associated with the account requesting the access right to the attribute information management server 10. Also for the access token to be paid out after the user's authorization, the user's account name is set and transmitted to the service provider's Web server 20 (see (5) in FIG. 10). Then, an account having an access right to the attribute information management server 10 is associated with an access token. When the user selects the value of his / her attribute to be registered in the service provider's Web server 20, a profile in which the value of the attribute is listed is created and managed for each user account name (( 8)).

  When the service provider's Web server 20 transmits an access right request message to the attribute information management server 10, it adds the account name of the user to the parameter. Further, when the user attribute information is acquired using the application interface of the attribute information management server 10, the user is redirected to the attribute information management server 10, and the service provider's Web server is used for the attribute having a plurality of values. The user is allowed to select an attribute value to be registered in 20 (see (8) in FIG. 10).

  Next, processing performed by the user attribute information management system 100A according to the second embodiment will be described with reference to FIGS. 11A and 11B. FIGS. 11A and 11B are sequence diagrams illustrating 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. 11A and 11B, after the service provider Web server 20 redirects the user registration request to the attribute information management server, the user who receives the response from the attribute information management server 10 When logging in to the attribute information management server 10 (step S213), the attribute information management server 10 inquires of the user whether to grant the access right to the attribute information management server 10 to the Web server 20 of the service provider (step S214).

  When the user terminal 30 authorizes the access right, the attribute information management server 10 acquires an authorized request token from the user (step S215). Subsequently, the attribute information management server 10 redirects to the Web server 20 of the service provider using the approved request token as a parameter (step S216).

  The service provider's Web server 20 obtains an access token indicating the access right from the attribute information management server 10 in exchange for the authorized request token (steps S217 and S218). An area for setting the user's account name is defined in the format of the access token. By setting the account name as an access token, an account having an access right to the attribute information management server 10 is associated with the access token. .

  The service provider's Web server 20 uses the application interface defined in advance by the attribute information management server 10 and uses the access token as a parameter, and the attribute information of the user necessary for user registration from the attribute information management server 10 Is requested (step S219).

  If the attribute information management server 10 includes attributes whose values are registered in the attribute information management server 10 among the attribute information requested by the service provider's Web server 20, the attribute information management server 10 Then, it is determined whether or not a value to be distributed to the service provider's Web server 20 is selected (step S220). As an example of the confirmation method, there is a presence / absence of a profile that lists attributes for which values are selected, and confirmation of the presence / absence of the attribute in the profile.

  Subsequently, when there is an attribute for which a value to be distributed to the service provider's Web server 20 is not selected (No at Step S220), the attribute information management server 10 manages attribute information with respect to the service provider's Web server 20. A response instructing redirection to the server 10 is made (step S221). If all the values to be distributed to the service provider's Web server 20 have been selected (Yes at step S220), the process proceeds to the following step S229.

  Then, the Web server 20 of the service provider redirects to the attribute information management server 10 using the access token and the identifier of the application interface used in step S219 as parameters (step S222). Then, the service provider's Web server 20 inquires of the user about the value of the user attribute requested for acquisition (step S223).

  Subsequently, the attribute information management server 10 creates a list of values of the attributes that are registered in the attribute information management server 10 for the attributes distributed to the Web server 20 of the service provider. Then, the user is allowed to select the value of his / her attribute to be distributed to the service provider's Web server 20 (step S224).

  Then, when the attribute information management server 10 acquires the value of its own attribute selected by the user (step S225), the attribute information management server 10 acquires the account name of the user from the access token (step S226). Then, the values of the user's own attributes selected by the user are listed, and are associated with the user's account name to create a profile (step S227).

  Subsequently, the attribute information management server 10 redirects to the service provider Web server 20 using the access token as a parameter (step S227). Then, the service provider's Web server 20 uses the application interface defined in advance by the attribute information management server 10 and uses the access token as a parameter, and the user information required for user registration from the attribute information management server 10. Request attribute information (step S228).

  Then, the attribute information management server 10 sends the user attribute information to the service provider Web server 20 (step S229). Then, the Web server 20 of the service provider performs user registration based on the user attribute information acquired from the attribute information management server 10, and sends a user registration response to the user (step S230).

[Effect of the second embodiment]
In the user attribute information management system 100A according to the second embodiment, when the attribute information management server 10 makes a request for any type of attribute information among a plurality of types of attribute information, the attribute information is displayed on the Web. When the authorization for provision to the server 20 is confirmed with the user terminal 30 and the authorization for provision of the attribute information to the Web server 20 is confirmed, the attribute value corresponding to the attribute information requested from the Web server 20 If there are multiple, the user terminal 30 is made to select the attribute value to be registered in the Web server.

  Therefore, when the service provider's Web server 20 acquires the user's attribute information from the attribute information management server 10 after the user authorizes the service provider's Web server 20 to access the attribute information management server 10. By allowing the user to select attribute values to be distributed to the service provider's Web server 20, the user actually distributes to the service provider's Web server 20 without selecting all the attribute values authorized for distribution. The procedure to select only the value of the attribute to be enabled becomes possible.

[Third embodiment]
In the third embodiment described above, a case will be described in which an attribute information management application installed in a user terminal manages user attribute information instead of the attribute information management server. The attribute information management application 50 is installed on the user terminal 30A and operates as an add-on to the Web browser 60 installed on the user terminal 30A. The user can centrally manage his / her attribute information and provide services to the user. The user's own web service is used for using different attribute information.

  First, the flow of user attribute information acquisition processing in the user attribute information management system 100B according to the third embodiment will be described with reference to FIG. FIG. 12 is a diagram illustrating the flow of user attribute information acquisition processing 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 on the user terminal 30A (see (1) in FIG. 12). At this time, if there are a plurality of values for one attribute, those values are registered respectively. Thereafter, when user registration to the service provider's Web server 20 is started (see (2) in FIG. 12), the service provider's Web server 20 is registered with the attribute information registered in the attribute information management application 50. At the same time as selecting the value of the attribute to be registered (see (4) in FIG. 12), the service provider's Web server 20 is permitted to distribute the attribute information selected by itself (see (6) in FIG. 12). In addition, after authorizing the distribution of the attribute information selected by the service provider's Web server 20 to the service provider, when the Web server 20 acquires the attribute information, only when there is a plurality of attribute information, An attribute value registered in the Web server 20 may be selected.

  The attribute information management application 50 identifies user attribute information requested by the service provider Web server 20 when the terminal Web browser 60 receives a user registration response from the service provider Web server 20, and identifies them. Are displayed on the Web browser 60. At this time, if there are attributes for which a plurality of values are registered in the attribute information management application 50, these values are displayed on the Web browser 60 and distributed to the service provider's Web server 20 by the user. The attribute value is selected (see (4) in FIG. 12). Then, when the user terminal 30A selects its own attribute information registered in the service provider's Web server 20, a profile in which the attribute information is listed is created and managed for each user account name ((( See 5)).

  When receiving the user registration request from the user, the service provider Web server 20 pays out the account name to the user, notifies the user of the account name, and also provides the user attribute information necessary for providing the service. To the user (see (3) in FIG. 12). When requesting the attribute information of the user, the content using the application interface of the attribute information management application 50 is transmitted to the Web browser 60 of the terminal, and the Web browser 60 has registered the attribute information of the user registered from the attribute information management application 50. And the requested attribute information is displayed on the Web browser 60.

  Next, the configuration of the user terminal 30A will be described with reference to FIG. FIG. 13 is a block diagram illustrating a configuration of a user terminal according to the third embodiment. As illustrated in FIG. 13, the user terminal 30 </ b> A 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 units 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 communication processing unit 31 controls communication related to various information exchanged with the connected Web server 20.

  The GUI processing unit 34 is an interface used when a user registers, modifies, deletes, and browses his / her attribute information in the attribute information management application 50 installed in the user terminal 30 </ b> A, and his / her attributes provided to each Web server 20. Performs processing to provide the user with an interface for browsing information.

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

  The attribute information storage unit 33a stores one or a plurality of attribute values corresponding to a plurality of types of attribute information. The profile information storage unit 33b stores a profile created by the creation unit 32b described later. Note that 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, and detailed description thereof is omitted. To do.

  The control unit 32 has an internal memory for storing a program that defines various processing procedures and the necessary data, and performs various processes by using these programs. Particularly, as closely related to the present invention, It has the confirmation part 32a, the preparation part 32b, and the transmission part 32c.

  When there is a request for any type of attribute information among a plurality of types of attribute information, the confirmation unit 32a confirms with the user authorization for providing the attribute information to the Web server 20. Specifically, when there are a plurality of attribute values corresponding to the attribute information requested from the Web server 20, the confirmation unit 32a confirms with the user permission to provide the attribute information to the Web server 20. At this time, the user terminal 30 is caused to select an attribute value to be registered in the Web server 20. For example, the confirmation unit 32a acquires each attribute information requested by the service provider's Web server 20 from the registered attribute values of the user and displays the attribute information on the Web browser 60. And the confirmation part 32a displays each value about the attribute in which the several value was registered among the attribute information displayed on the web browser 60, and displays it to the web server 20 of a service provider to a user. Select the value to register.

  In addition, after authorizing the distribution of the attribute information selected by the service provider's Web server 20 to the service provider, when the Web server 20 acquires the attribute information, only when there is a plurality of attribute information, An attribute value registered in the Web server 20 may be selected. In this case, when there is a request for any kind of attribute information among a plurality of types of attribute information, the confirmation unit 32a confirms authorization for providing the attribute information to the Web server 20 from the user. If the authorization to provide the attribute information to the Web server 20 is confirmed, if there are a plurality of attribute values corresponding to the attribute information requested from the Web server 20, the Web server 20 receives the request from the user terminal 30. When acquiring attribute information, the user is allowed to select an attribute value to be registered in the Web server 20.

  The creation unit 32b reads the attribute value corresponding to the requested type of attribute information from the attribute information storage unit 33a when the authorization to provide the attribute information to the Web server 20 is confirmed, and the read attribute value Are created and stored in the profile information storage unit 33b. Specifically, the creation unit 32b creates a profile by listing the attribute values of the user selected by the user and binding them with the user's account name.

  The transmission unit 32 c transmits the attribute information profile created by the creation unit 32 b to the Web server 20. Specifically, the transmission unit 32c transmits, to the service provider's Web server 20, the attribute information requested by the service provider's Web server 20 together with the attribute value 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. 14 is a sequence diagram illustrating 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. 14, in order to use a service provided by a service provider on a communication network, a user sends his / her attribute information to an attribute information management application 50 that supports unified management of his / her attribute information. Is registered (steps S301 and S302). The attribute information includes your name, e-mail address, credit card number, etc. For attribute information held by the user, such as e-mail address and credit card number, set the value of each attribute. sign up.

  Then, in order to use the service provided by the service provider, the user makes a user registration request after accessing the portal site of the service provider's Web server 20 from the user terminal 30A (steps S303 and S304) (step S303). S305).

  Subsequently, the service provider's Web server 20 that has received the user registration request pays out the account name of the user (step S306), and transmits the account name to the attribute information management application 50 of the user terminal 30A (step S307). . At this time, the Web server 20 of the service provider requests the content when responding in accordance with the application interface defined by the attribute information management application 50 in order to request user attribute information necessary for providing the service. The attribute to be described is described.

  Then, the attribute information management application 50 acquires each attribute information requested by the service provider's Web server 20 from the registered attribute values of the user (step S308) and displays it on the Web browser 60. (Step S309).

  Subsequently, in the attribute information displayed on the web browser 60, for the attributes for which a plurality of values are registered, each value is displayed, and the value registered in the service provider's web server 20 is displayed to the user. Select (step S310).

  When the user selects attribute values to be registered in the service provider's Web server 20 and authorizes distribution of those attribute values and other attribute information displayed on the Web browser 60 (step S311), the Web browser 60 Notifies the attribute information management application 50 of the profile creation request (step S312). Then, the attribute information management application 50 creates a profile by listing the attribute values of the user selected by the user and linking them with the user's account name (step S313).

  After that, the attribute information management application 50 transmits the attribute information requested by the service provider's Web server 20 together with the attribute value selected by the user to the service provider's Web server 20 (step S315). Then, the service provider's Web server 20 performs user registration based on the user attribute information acquired from the user terminal 30A, and sends a user registration response to the user (step S316).

  As shown in FIG. 15, the attribute information management application 50 is installed on the user terminal 30A and operates as an add-on to the web browser 60 installed on the user terminal 30A. It supports centralized management and the use of different attribute information when using the service provider's Web service. Specifically, the user registers his / her attribute information in advance from the GUI 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, the respective information is registered. In addition, about the attribute information which the user registered, a user browses and corrects suitably from GUI of the attribute information management application 50. FIG. In addition, the service provider provides user attribute information necessary for the service provider to provide the service with the user's authorization. The user attribute information provided to the service provider is managed for each account issued when the user registers as a user in the service provider's Web server 20, and the user own attribute information provided to the service provider. View and confirm for each account.

  The attribute information management application 50 defines 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 application interface specification, there is a URL or html specification for mounting an http server function in an attribute information management application and accessing the server function.

[Effect of the third embodiment]
As described above, in the user attribute information management system 100B according to the third embodiment, a user installs the attribute information management application 50 in his / her user terminal 30A, and his / her attribute information is unified in his / her user terminal 30A. By managing, the centralized management of its own attribute information and registration for each Web server 20 without being affected by the operation status of service specifications related to the management of user attribute information on the communication network 40 or failure. The user can use different attribute values.

[Fourth embodiment]
Although the embodiments of the present invention have been described so far, the present invention may be implemented in various different forms other than the above-described embodiments. Therefore, in the following, another fourth embodiment included in the present invention will be described as a fourth embodiment.

(1) System Configuration, etc. Each component of each illustrated device is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the confirmation unit 12a and the creation unit 12b may be integrated. Further, 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 hardware by wired logic.

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

(2) Program In addition, a program described in a language that can be executed by a computer can be created for the processing 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 management information server 10 according to the first embodiment. In this case, when the computer executes the user attribute information management program, the same effects as in the above embodiment can be obtained. Further, the user attribute information management program is recorded on a computer-readable recording medium, and the user attribute information management program recorded on the recording medium is read into the computer and executed, thereby executing the same as in the first embodiment. Processing may be realized. An example of a computer that executes a user attribute information management program that implements the same function as the attribute information management server 10 shown in FIG. 2 will be described below.

  FIG. 16 is a diagram illustrating a computer 1000 that executes a user attribute information management program. As illustrated in FIG. 16, the computer 1000 includes, 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 ROM (Read Only Memory) 1011 and a RAM (Random Access Memory) 1012 as illustrated in FIG. The ROM 1011 stores a boot program such as 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. The serial port interface 1050 is connected to a mouse 1110 and a keyboard 1120, for example, as illustrated in FIG. The video adapter 1060 is connected to a display 1130, for example, as illustrated in FIG.

  Here, as illustrated in FIG. 16, 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 user attribute information management program is stored in, for example, the hard disk drive 1090 as a program module in which a command executed by the computer 1000 is described.

  In addition, various data described in the above embodiment is 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 the program data 1094 stored in the memory 1010 and the hard disk drive 1090 to the RAM 1012 as necessary, and executes each processing procedure.

  The program module 1093 and the program data 1094 related to the user attribute information management program are not limited to being stored in the hard disk drive 1090, but are stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive or the like. May be. 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 the network interface It may be read by the CPU 1020 via 1070.

DESCRIPTION OF SYMBOLS 10 Attribute information management server 11 Communication processing part 12 Control part 12a Confirmation part 12b Creation part 12c Transmission part 13 Storage part 13a Attribute information storage part 13b Profile information storage part 20, 20A-20D Web server 30, 30A User terminal 40 Communication network 50 Attribute information management application 60 Web browser

Claims (9)

A user attribute information management system comprising: an attribute information management device that manages user attribute information; and a server that provides a service to a user terminal that has undergone user registration using predetermined attribute information.
The attribute information management device includes:
For multiple types of attribute information, a storage unit for storing one or more attribute values,
When there is a request for any kind of attribute information among the plurality of types of attribute information, the user terminal is authorized to provide the attribute information to the server, and a plurality of attribute values are registered. For the attribute information being made, a confirmation unit that causes the user terminal to select an attribute value;
When the confirmation unit confirms authorization to provide the attribute information to the server and accepts selection of an attribute value to be registered, an attribute value corresponding to the type of attribute information requested, and A creation section for creating a profile of the selected attribute value;
A transmission unit that transmits the profile of the attribute information created by the creation unit to the server,
The server
When a request for user registration is received from the user terminal, a request unit that requests the attribute information management apparatus for attribute information necessary for the user registration;
A user attribute information management system comprising: a registration unit that performs user registration using the attribute information when the attribute information requested by the request unit is received.   When there are a plurality of attribute values corresponding to the attribute information requested from the server, the confirmation unit checks the user terminal with permission to provide the attribute information to the server. The user attribute information management system according to claim 1, wherein an attribute value to be registered in the user terminal is selected by a user terminal.   When there is a request for attribute information from the server, the confirmation unit confirms authorization for providing the attribute information to the server with the user terminal, and authorization for provision of the attribute information to the server is confirmed. If confirmed, if there are a plurality of attribute values corresponding to the attribute information requested from the server, the attribute registered in the server when the server acquires the attribute information from the attribute information management device. The user attribute information management system according to claim 1, wherein a value is selected by the user terminal. The confirmation unit transmits an unauthenticated request token embedded with the account name when a request for attribute information is included as a parameter including the account name issued by the server to the user terminal that requested the user registration. When the request token is received from the server by redirection through the user terminal, the user terminal is inquired about authorization to provide the attribute information to the server, and the authorized request token is sent to the user terminal. To confirm the authorization of the provision of the attribute information to the server,
When the transmission unit receives the authorized request token after transmitting the authorized request to the server by redirection via the user terminal, the server sends the access token embedded with the account name. When the attribute information acquisition request using the access token is received, the attribute information profile created by the creation unit is sent to the server,
When the request unit receives a request for user registration from the user terminal and receives an instruction to request the attribute information management apparatus for attribute information necessary for the user registration using the account name as a parameter, the account name Is included in the parameter, and the attribute information management device is requested for the attribute information necessary for the user registration, and when the unauthorized request token is received, the request token is redirected through the user terminal. When transmitting to the attribute information management device and receiving the authorized request token from the attribute information management device by redirection through the user terminal, the access token is converted to the attribute using the authorized request token. When requesting the information management device and receiving the access token from the attribute information management device User attribute information management system according to any one of claims 1 to 3, characterized in that transmits an acquisition request for attribute information using the access token to the attribute information managing device. A user attribute information management system having a user terminal in which an attribute information management application for managing user attribute information is installed and a server that provides a service to a user terminal for which user registration has been performed using predetermined attribute information. And
The user terminal is
For multiple types of attribute information, a storage unit for storing one or more attribute values,
When there is a request for any type of attribute information among the plurality of types of attribute information, the user is asked for authorization to provide the attribute information to the server, and a plurality of attribute values are registered. For the attribute information, a confirmation unit that allows the user to select an attribute value;
When the confirmation unit confirms authorization to provide the attribute information to the server and accepts selection of an attribute value to be registered, an attribute value corresponding to the type of attribute information requested, and A creation section for creating a profile of the selected attribute value;
A transmission unit that transmits the profile of the attribute information created by the creation unit to the server,
The server
When a request for user registration is received from the user terminal, a request unit that requests the user terminal for attribute information necessary for the user registration;
A user attribute information management system comprising: a registration unit that performs user registration using the attribute information when the attribute information requested by the request unit is received.   When there are a plurality of attribute values corresponding to the attribute information requested from the server, the confirmation unit sends the confirmation information to the server when confirming authorization to provide the attribute information to the server. 6. The user attribute information management system according to claim 5, wherein the user selects an attribute value to be registered.   When there is a request for any kind of attribute information among the plurality of types of attribute information, the confirmation unit confirms authorization for providing the attribute information to the server, and the attribute When authorization to provide information to the server is confirmed, if there are a plurality of attribute values corresponding to the attribute information requested from the server, the server acquires attribute information from the user terminal. 6. The user attribute information management system according to claim 5, wherein the user is allowed to select an attribute value to be registered in the server. User attribute information management executed by a user attribute information management system having an attribute information management device for managing user attribute information and a server for providing a service to a user terminal for which user registration using predetermined attribute information has been performed A method,
The attribute information management device includes a storage unit that stores one or a plurality of attribute values for a plurality of types of attribute information,
When the server receives a user registration request from the user terminal, the server requests the attribute information management apparatus for attribute information necessary for the user registration; and
When there is a request for any kind of attribute information among the plurality of types of attribute information, the attribute information management apparatus confirms authorization for providing the attribute information to the server with the user terminal. , For attribute information in which a plurality of attribute values are registered, a confirmation step for causing the user terminal to select an attribute value;
The attribute information management device, when the confirmation step confirms authorization of provision of the attribute information to the server and accepts selection of an attribute value to be registered, A creation process for creating a profile of the attribute value corresponding to and the selected attribute value;
The attribute information management device transmits a profile of attribute information created by the creation step to the server;
The server includes a registration step of performing user registration using the attribute information when the requested attribute information is received from the attribute information management apparatus. Executed in a user attribute information management system having a user terminal in which an attribute information management application for managing user attribute information is installed and a server that provides a service to a user terminal for which user registration has been performed using predetermined attribute information A user attribute information management method,
The user terminal includes a storage unit that stores attribute values for a plurality of types of attribute information,
When the server receives a user registration request from the user terminal, the server requests the user terminal for attribute information necessary for the user registration; and
The user terminal, when there is a request for any kind of attribute information among the plurality of types of attribute information, a confirmation step of confirming to the user the authorization for providing the attribute information to the server;
The user terminal reads the attribute value corresponding to the requested type of attribute information from the storage unit when the authorization of providing the attribute information to the server is confirmed by the confirmation step, and reads the attribute value. Creating a profile of the attribute value,
The user terminal transmits a profile of attribute information created by the creation step to the server;
The server includes a registration step of performing user registration using the attribute information when the requested attribute information is received from the user terminal.

Images