JP5722271B2 - Attribute information acquisition method, attribute information acquisition system using the method, each device and program - Google Patents

Description

  The present invention relates to acquisition of attribute information when performing processing using attribute information, an attribute information acquisition method for acquiring attribute information by clarifying the type of attribute information, an attribute information acquisition system using the method, It relates to each device and program.

  The attribute information used in the information system can be roughly classified into three categories: attribute A: an attribute for performing authentication, attribute B: an attribute guaranteed by authentication, and attribute C: an attribute obtainable by non-authentication. Classified by type. Hereinafter, attribute A and attribute B are referred to as attribute type A and attribute type B.

  As a technique for acquiring the attribute information b corresponding to the attribute type B under the precondition that the attribute information a corresponding to the attribute type A is correct, for example, there is an identity management technique. As an identity management technique, SAML (Non-Patent Document 1), which is a framework that uses single sign-on in Web applications, and LDAP (Non-Patent Document 2), which is a protocol for systematically managing user accounts and user attributes. and so on.

Security Assertion Markup Language (SAML) V2.0 Technical Overview, http://www.oasis-open.org/committees/download.php/27819/sstc-saml-tech-overview-2.0-cd-02.pdf Lightweight Directory Access Protocol (V3) http://tools.ietf.org/html/rfc2251

In the conventional technology, for example, attribute information cannot be acquired and used beyond the frame of an application. FIG. 10 shows the problems of the prior art. The application α provides the attribute information b ₁ from the attribute information management device 90 to the application α after user authentication at the attribute information management device 90 by the attribute information a. Thereafter, it is impossible to even obtain an attempt to obtain a new attribute information b ₂ from other attribute information managing device 91. Symbols with circles and diagonal lines in the figure indicate that the application α cannot access the attribute information management apparatus 91.

  In the construction of a system for acquiring attributes, the conventional technology assumes that the attribute type of the attribute information to be handled is determined in advance. Therefore, unless the application is reconfigured, the attribute information other than the attribute type determined in advance is used. There is a technical limit such as “cannot be acquired”.

  Due to this limitation, it is not possible to flexibly change the attribute information acquisition source according to the attribute type in the situation where attribute information with mixed attribute types is handled, and the attribute information that can be acquired becomes information of a specific attribute type. A limited problem arises.

  The present invention has been made in view of such problems, and an attribute information acquisition method capable of acquiring attribute information without restructuring an application even in a situation where attribute types are mixed. Another object of the present invention is to provide an attribute information acquisition system using the method, each device, and a program.

  The attribute information acquisition method of the present invention includes an attribute information request process in which a user terminal sends an attribute information acquisition request to an attribute information distribution server to request acquisition of attribute information, and the attribute information distribution server or authentication attribute information management A user authentication process in which the server acquires attribute information a corresponding to the attribute type A, which is an attribute type for authentication from the user terminal, authenticates the user, and outputs the authentication result and an identifier representing the authentication source; , The attribute information management server manages the attribute information b corresponding to the attribute type B which is the attribute type guaranteed by the authentication, and provides the attribute information b corresponding to the authentication result to the attribute information distribution server The provision process and the attribute information distribution server respond to the recognition result from the authentication attribute information management server that manages the attribute information using the authentication result and the identifier representing the authentication source. Attribute information distribution process for acquiring attribute information b to be distributed to the user terminal, and attribute type C that is an attribute type that the user terminal can acquire without attribute information b from the attribute information distribution server and unauthenticated from the information providing server One or both of the attribute information c corresponding to the above, and using the attribute information b as authenticated attribute information.

  Moreover, the attribute information acquisition system of this invention is provided with the authentication attribute information management server which performs the above-mentioned attribute information acquisition method, an attribute information distribution server, and a user terminal.

  According to the attribute information acquisition method of the present invention, the attribute information b corresponding to the attribute type B that is an attribute type guaranteed by the authentication, and the attribute information c corresponding to the attribute type C that is an attribute type that can be acquired by non-authentication. And the attribute information b can be acquired from one or more authentication attribute information management devices that manage the attribute information using the identifier representing the authentication result and the authentication source. As a result, the acquisition destination of attribute information can be flexibly changed, and new attribute information can be acquired without restructuring the application.

The figure which shows the system configuration | structure of the attribute information acquisition system 100 of this invention. The figure which shows the operation | movement sequence of FIG. The figure which shows the operation | movement sequence at the time of giving separately the function of the authentication attribute information management server 50 to the authentication management server 60 and the attribute information management server 50 '. The figure which shows the function structural example of the user terminal. The figure which shows the operation | movement flow of the user terminal 10. The figure which shows the function structural example of the attribute information acquisition provision server 70. FIG. The figure which shows the function structural example of the attribute information distribution server 30. FIG. The figure which shows the operation | movement flow of the attribute information distribution server 30. The figure which shows the operation | movement sequence diagram of attribute information acquisition system 100 'of this invention. The figure for demonstrating the subject of a prior art.

  Embodiments of the present invention will be described below with reference to the drawings. The same reference numerals are given to the same components in a plurality of drawings, and the description will not be repeated.

FIG. 1 shows a system configuration of an attribute information acquisition system 100 of the present invention. The attribute information acquisition system 100 acquires, from one or more authentication attribute information management servers, the user terminal 10 that uses attribute information of different attribute types according to user operations and the attribute type B attribute information guaranteed by the authentication. Manages attribute information distribution server 30 distributed to user terminal 10, information providing server 40 that provides attribute information c that does not require authentication, and attribute information a that is attribute information corresponding to attribute type A for user authentication And one or more authentication attribute information management servers 50 (50 ₁ , 50 ₂ ,... 50 _n ) that manage the attribute information b of the attribute information corresponding to the attribute type B guaranteed by the authentication. The information providing server 40 is configured by a conventional technique such as a GPS receiver (details will be described later). Further, the authentication attribute information management server 50 is configured by, for example, conventional techniques described in Non-Patent Documents 1 and 2 described above.

  The servers 30, 40, 50 and the user terminal 10 are connected to each other via a network (hereinafter referred to as “NW”) 20. The server is a word that can be replaced with “device”, and the expression is unified to the server thereafter.

  The operation of the attribute information acquisition system 100 will be described with reference to FIG. The user terminal 10 generates an attribute information acquisition request for requesting acquisition of attribute information required by the application (step S1). The attribute information acquisition request includes attribute items corresponding to the attribute type B or attribute type C of the requested attribute information. Here, the attribute item represents a group of attribute information such as the name of a field storing the attribute value, for example, post information, name, temperature, and the like. The attribute value is, for example, “section manager”, “Yamada”, or “25 degrees”.

  The user terminal 10 determines whether or not the attribute type of the requested attribute information is an attribute type C that is an attribute that can be acquired without authentication (step S2). Step 2 is processing on the user terminal 10 although it is not on the lead line from the user terminal 10. If the requested attribute type is attribute type C (Yes in step S2), the attribute information c is requested from the information providing server 40 that provides the attribute information c corresponding to the attribute type C that is an attribute that does not require authentication (step S3). The information providing server 40 provides the attribute information c corresponding to the attribute type C to the user terminal 10 (step S4).

  The information providing server 40 is, for example, a wireless LAN access point, an IP simulcast radio, a GPS receiver, or the like. Attribute information that can be obtained from each information providing server 40 includes SSID for identifying an access point, information indicating the location of a connection area such as a connection source IP address, GPS coordinate information, and various sensor information. This is information corresponding to the usage environment of the user terminal 10. In addition, position information and various sensor information may exist in the user terminal 10 like a recent smart phone. For example, the information providing server 40 may be integrated with the user terminal 10.

  When the request attribute type requested by the user terminal 10 is attribute type B (No in step S2). The attribute information distribution server 30 performs authentication between the user terminal 10 and the authentication management server 50 (step S5). For example, authentication is performed using an ID / password. In that case, the attribute information distribution server 30 requests the user terminal 10 to input an ID / password that is the attribute information a corresponding to the attribute type A for user authentication, and obtains it. Then, the authentication attribute information management server 50 that manages the attribute information a is requested and obtained from the authentication management side ID / password corresponding to the user (steps S7 and S8).

  Step 5 for authenticating the user may be included in the processing of the authentication attribute information management server 50 (authentication indicated by a broken line (S5)). In this case, the ID / password input to the user terminal 10 is directly input to the authentication attribute information management server 50. Then, the authentication attribute information management server 50 gives an authentication result and an identifier representing the authentication source to the attribute information distribution server 30. Note that there may be a plurality of authentication attribute information management servers 50, and the authentication level may be different depending on each authentication attribute information management server. When authentication with an authentication level higher than that of the ID / password is required, for example, when authentication is performed using an electronic certificate, the electronic certificate necessary for authentication is sent from the user terminal 10 to the attribute information distribution server 30 or the authentication attribute information management. It is output to the server 50.

If the user is authenticated (Yes in step S9), the target user whose attribute information is to be extracted is specified based on the authentication result, and the corresponding attribute information b is requested to the authentication attribute information management server 50 (step S10). At this time, the access destination is uniquely determined from the authentication attribute information management servers 50 ₁ , 50 ₂ ,..., 50 _n that request the attribute information b, based on the identifier of the authentication attribute information management server 50. Alternatively, the attribute information acquisition request from the user terminal 10 includes ID information (PSID: Personal Station ID) unique to the authentication attribute information management server 50, for example, and the authentication attribute information management server of the ID information You may make it acquire attribute information from. Alternatively, a URL (Uniform Resource Locator) may be used as a method for specifying access destination information.

  One of the authentication attribute information management servers 50 provides the attribute information b to the attribute information distribution server 30 (step S11).

  The attribute information b is “information associated with the attribute information a”, and is information such as personnel information (affiliation, length of service, job title, etc.) corresponding to a person, for example. The attribute information b is output to the user terminal 10 as information obtained as a result of being authenticated by the attribute information a that is attribute information corresponding to the attribute type A in the attribute information distribution server 30 (step S12). Note that the attribute information distribution step of step S12 is a process in the attribute information distribution server 30 although it is not on the lead line from the attribute information distribution server 30 for convenience of illustration.

The user terminal 10 can separately acquire the attribute information c obtained by non-authentication in step S4 and the attribute information b obtained as a result of the authentication. Further, the access destination (authentication attribute information management servers 50 ₁ , 50 ₂ ,..., 50 _n ) when acquiring the attribute information is appropriately changed depending on the identifier that identifies the authentication attribute information management server 50, so that a new It is possible to obtain additional attribute information b. Thereby, new attribute information b can be acquired without restructuring the application. In FIG. 2, the application is not clearly shown. The application is provided in the user terminal 10 and provides some information to the user by using step S6 and step S13 and attribute information acquired including processing not shown. That is, in this embodiment, a use process using attribute information is expressed as an application.

Note that the authentication function and the attribute information management function of the authentication attribute information management server 50 may be separated into two. In this case, as shown by a broken line in FIG. 1, a plurality of authentication management servers 60 (60 ₁ , 60 ₂ , 60 _n ) and a plurality of attribute information management servers 50 ′ (50 ′ is not shown) are included. The attribute information providing system 100 ′ is configured in the form. The operation sequence of the attribute information providing system in that case is shown in FIG. Only the authentication attribute information management server 50 is separated into the authentication management server 60 and the attribute information management server 60, and the operation sequence is the same.

  Next, a functional configuration example of the user terminal 10 and the attribute information distribution server 30 constituting the attribute information acquisition system 100 of the present invention will be described in further detail.

[User terminal]
FIG. 4 shows a functional configuration example of the user terminal 10. The user terminal 10 includes a communication interface 11, a function block 12, and a control unit 13. The functional block 12 includes an attribute information request unit 110, an authentication unit 111, and an attribute information acquisition unit 112. Each part of the functional block 12 is controlled by the control means 13. The functional block 12 is connected to the NW 20 via the communication interface 11. Each functional unit in the functional block 12 represents only functional units having special technical features of the present invention. Functional parts that do not show special technical features such as a keyboard and a display part are omitted. The same applies to other servers.

  The communication interface 11, the functional block 12, and the control means 13 may be configured by executing a predetermined program on a computer, for example. That is, the user terminal 10 may be configured with a computer terminal.

  The operation will be described with reference to the operation flow of the user terminal 10 shown in FIG. The attribute information request unit 110 requests attribute information by sending an attribute information acquisition request including the attribute type and attribute item of the requested attribute information to the attribute information distribution server 30 or the information providing server 40 according to the attribute type. (Step S110). When the attribute type of the requested attribute information is the attribute type C, the attribute information is requested to the information providing server 40 (step S110a), and when the attribute type is B, the attribute information distribution server 30 is requested (step S110b). The requested attribute information is determined by the attribute information requesting unit 110 corresponding to the attribute type requested by the application. Alternatively, the attribute information necessary for each application may be prepared as the correspondence table 113 in which the attribute items are associated with the attribute types. In this case, the attribute information requested in the correspondence table 113 can be added / deleted / changed as necessary, for example, so that the degree of freedom in acquiring the attribute information can be further increased. Is possible.

  In response to the authentication request from the attribute information distribution server 30 or the authentication attribute information management server 50, the authentication unit 111 sends out attribute information a corresponding to the attribute type A that is an attribute type for authenticating the user. User authentication is requested (steps S111a, b). When there is no request for the attribute information a for authenticating the user, the user is requesting only the attribute information c that can be acquired by non-authentication (no step S111a). In this case, the attribute information acquisition unit 112 Acquires the attribute information c of the attribute information corresponding to the attribute type C from the information providing server 40 (step S112b).

  When there is a request for attribute information a from the attribute information distribution server 30 or the authentication attribute information management server 50 (there is step S111a), the user attribute information a is sent to the request source. Information transmitted as the attribute information a is determined according to the level of authentication. For example, when simple authentication is acceptable, an authentication method using only an ID / password is used. When strong authentication is required, an authentication method using an electronic certificate may be used. After the user is authenticated, the attribute information acquisition unit 112 acquires attribute information b corresponding to the attribute type, which is the attribute type guaranteed by the authentication, from the authentication attribute information management server 50 via the attribute information distribution server 30 ( Step S112a).

The user terminal 10 uses the attribute information c as attribute information obtained by non-authentication, and the attribute information b as authenticated attribute information (step S113). That is, the attribute information c obtained by non-authentication and the attribute information b obtained as a result of authentication can be distinguished and acquired. Further, the access destination (authentication attribute information management servers 50 ₁ , 50 ₂ ,..., 50 _n ) when acquiring the attribute information is appropriately changed depending on the identifier that identifies the authentication attribute information management server 50, so that a new When it becomes necessary to obtain additional attribute information b, there is no need to reconstruct the application.

  In addition, although the example provided with the attribute information acquisition part 112 inside the user terminal 10 demonstrated, attribute information provision may be implement | achieved by service forms, such as ASP (Application Service Provider). In this case, the user terminal 10 includes only information input / output means and an authentication unit, and the information providing service provided by the ASP is configured by the attribute information acquisition / providing server 70 shown in FIG.

  The functional block 72 of the attribute information acquisition and provision server 70 includes an authentication unit 720, an attribute information request reception unit 721, an attribute information acquisition unit 722, and an attribute information provision unit 723. The authentication unit 720 authenticates the user terminal 10 and the attribute information distribution server 30. The authentication unit 720 may authenticate the user terminal 10 and the attribute information distribution server 30 individually, or the authentication result in the authentication attribute information management server 50 is used as it is, and authentication of the attribute information distribution server 30 is unnecessary. Anyway. In that case, the attribute information distribution server 30 performs the function of only relaying the attribute information b from the authentication attribute information management server 50 that has authenticated the user to the authenticated user terminal 10.

  The attribute information receiving unit 721 receives an attribute information acquisition request from the user terminal 10.

  Based on the attribute information acquisition request, the attribute information acquisition unit 721 authenticates the attribute information b corresponding to the attribute type B, which is the attribute type guaranteed by the authentication from the authenticated attribute information distribution server 30, and the authentication from the information providing server 40. Attribute information c corresponding to attribute type C, which is an unnecessary and acquirable attribute type, is acquired. The attribute information providing unit 722 provides the user terminal 10 with the attribute information b or the attribute information c acquired by the attribute information acquisition unit 721.

  Thus, even the embodiment that receives provision of attribute information from the attribute information acquisition and provision server 70 can achieve the effects of the present invention described above.

[Attribute information distribution server]
FIG. 7 shows a functional configuration example of the attribute information distribution server 30. The attribute information distribution server 30 includes a communication interface 31, a function block 32, and a control unit 33. The functional block 32 includes a distribution authentication unit 320 and an attribute distribution unit 321. Each part of the functional block 32 is controlled by the control means 33. The functional block 32 is connected to the NW 20 via the communication interface 31. The relationship between the communication interface 31, the function block 32, and the control means 33 is the same as that of the user terminal 10 described above.

  The operation will be described with reference to the operation flow of the user terminal 10 shown in FIG. The distribution authentication unit 320 authenticates the user with the user terminal 10 or acquires the authentication result obtained by authenticating the user by the authentication management server 50 and the identifier of the authentication management server, and distributes the attribute information. Judgment is made. This distribution authentication process includes an authentication standby step S320 ′ and a distribution permission / inhibition determination step S320. Here, the authentication waiting step S320 ′ is a step of waiting until an authentication request from the user terminal 10 is generated, and the distribution permission determination step S320 is executed every time an authentication request is generated. If not, it waits until the next authentication request occurs again.

  When the distribution authentication unit 320 determines that the attribute information can be distributed, the attribute distribution unit 321 obtains the attribute information b corresponding to the attribute type B that is the attribute type guaranteed by the corresponding authentication from the authentication attribute information management server 50. Acquired and distributed to the user terminal 10 (step S321).

  In the first embodiment, the attribute information acquisition system capable of distinguishing and acquiring the attribute information c obtained by non-authentication and the attribute information b obtained as a result of authentication has been described. Since the attribute information c and the attribute information b can be acquired separately, the attribute item of the attribute information c and the attribute item of the attribute information b are collated to raise the authentication level of the attribute information c and correspond to the attribute information b. An attribute information acquisition system that can be handled as information is also conceivable.

  For example, assume that a user uses a license number in an application. In that case, the user inputs the number into the user terminal using a keyboard or the like while looking at the license. At that time, the number is only the attribute information c corresponding to the attribute type C, but there are cases where it is desired to use the number as the attribute information b guaranteed by the authentication.

  FIG. 9 shows an operation sequence diagram of the attribute information acquisition system that can raise the authentication level of the attribute information c. FIG. 9 is different from the first embodiment (FIG. 2) only in that attribute matching is performed on the user terminal 10 (step S14).

  In the attribute collation in step S14, it is verified whether or not the attribute item of the attribute information c matches the attribute item of the attribute information b. The verification is performed by the verification unit 114 (FIG. 3) of the user terminal 10. If matching is verified, attribute information corresponding to the attribute type C, such as a number input using a keyboard or the like, can be handled as information corresponding to the attribute type B. If they do not match, the application processing is interrupted.

  In this way, in an application in which an attribute value is required to be “information guaranteed by authentication”, attribute information c corresponding to attribute type C and attribute information b corresponding to attribute type B are collated. The reliability level of the attribute information c corresponding to the attribute type C can be raised to “information guaranteed by authentication”. The attribute information acquisition / providing server 70 can be provided with a function of raising the reliability level of attribute information corresponding to the attribute type C to “information guaranteed by authentication”. In this case, the functional block includes a functional unit corresponding to the collating unit 114, and collates the attribute information c of the attribute information corresponding to the attribute type C and the attribute information b of the attribute information corresponding to the attribute type B.

  As described above, according to the attribute information acquisition method of the present invention, the attribute information b that is an attribute guaranteed by authentication and the attribute information c that can be acquired by non-authentication can be acquired separately. The attribute information b can be acquired from one or more attribute management devices that manage the attribute information using the authentication result and an identifier representing the authentication source. As a result, the acquisition destination of attribute information can be flexibly changed, and new attribute information can be acquired without restructuring the application.

Note that the processes described in the above method and apparatus are not only executed in time series according to the order of description, but may also be executed in parallel or individually as required by the processing capability of the apparatus that executes the processes. Good.

  Further, when the processing means in the above apparatus is realized by a computer, the processing contents of functions that each apparatus should have are described by a program. Then, by executing this program on the computer, the processing means in each apparatus is realized on the computer.

  The program describing the processing contents can be recorded on a computer-readable recording medium. As the computer-readable recording medium, for example, any recording medium such as a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory may be used. Specifically, for example, as a magnetic recording device, a hard disk device, a flexible disk, a magnetic tape or the like, and as an optical disk, a DVD (Digital Versatile Disc), a DVD-RAM (Random Access Memory), a CD-ROM (Compact Disc Read Only). Memory), CD-R (Recordable) / RW (ReWritable), etc., magneto-optical recording medium, MO (Magneto Optical disc), etc., semiconductor memory, EEP-ROM (Electronically Erasable and Programmable-Read Only Memory), etc. Can be used.

  The program is distributed by selling, transferring, or lending a portable recording medium such as a DVD or CD-ROM in which the program is recorded. Further, the program may be distributed by storing the program in a recording device of a server computer and transferring the program from the server computer to another computer via a network.

  Each means may be configured by executing a predetermined program on a computer, or at least a part of these processing contents may be realized by hardware.

Claims (9)

An attribute information request process in which the user terminal sends an attribute information acquisition request to the attribute information distribution server to request acquisition of attribute information;
The attribute information distribution server or the authentication attribute information management server acquires attribute information a corresponding to the attribute type A that is an attribute type for performing authentication from the user terminal to authenticate the user, and the authentication result and the authentication source A user authentication process for generating an identifier representing
Attribute information in which the authentication attribute information management server manages attribute information b corresponding to attribute type B, which is an attribute type guaranteed by authentication, and provides attribute information b corresponding to the authentication result to the attribute information distribution server Providing process,
Attribute information that the attribute information distribution server acquires attribute information b corresponding to the recognition result from the authentication attribute information management server that manages the attribute information using the authentication result and an identifier representing the authentication source, and distributes the attribute information to the user terminal Distribution process,
User terminal, obtains attribute information b from the attribute information distribution server, the attribute information c that corresponds the information providing server on the attribute type C is obtainable attribute types in unauthenticated, one or both, the attribute An attribute information utilization process in which information b is used as authenticated attribute information;
Attribute information acquisition method having An attribute information request process in which the user terminal sends an attribute information acquisition request to the attribute information distribution server to request acquisition of attribute information;
The attribute information distribution server or the authentication attribute information management server acquires attribute information a corresponding to the attribute type A that is an attribute type for performing authentication from the user terminal to authenticate the user, and the authentication result and the authentication source A user authentication process for generating an identifier representing
Attribute information in which the authentication attribute information management server manages attribute information b corresponding to attribute type B, which is an attribute type guaranteed by authentication, and provides attribute information b corresponding to the authentication result to the attribute information distribution server Providing process,
Attribute information that the attribute information distribution server acquires attribute information b corresponding to the recognition result from the authentication attribute information management server that manages the attribute information using the authentication result and an identifier representing the authentication source, and distributes the attribute information to the user terminal Distribution process,
User terminal, the attribute information and attribute information b from the distribution server, information from the providing server attribute information c that corresponds to the attribute type C is obtainable attribute types unauthenticated, the attribute acquired one or both An attribute collation process for collating information b with the attribute information c, an attribute information utilization process for using the attribute information c collated in the attribute collation process as attribute information b of the attribute type B,
Attribute information acquisition method having In the attribute information acquisition method according to claim 1 or 2,
The attribute information acquisition request is
An attribute item that represents a group of attribute information for storing the attribute information and an attribute type indicating that the attribute information is an attribute for performing authentication, an attribute guaranteed by the authentication, or an attribute that can be acquired by non-authentication. And obtaining attribute information. Managing attribute information b of the attribute type corresponding to attribute type B that is an attribute type guaranteed by the attribute information a of attribute type corresponding to attribute type A corresponding to the attribute type A for authenticating the user; An authentication attribute information management server that provides attribute information b corresponding to the authentication result to the attribute information distribution server;
An attribute information distribution server that acquires attribute information b corresponding to the recognition result from the authentication attribute information management server and distributes the attribute information b to a user terminal;
Requests the authentication attribute information management server or the attribute information distribution server to authenticate with the attribute information a, acquires the attribute information b, and corresponds to the attribute type C that is an attribute type that can be acquired without authentication from the information providing server A user terminal that acquires attribute information c to be used and uses the attribute information b as authenticated attribute information;
An attribute information acquisition system characterized by comprising: The attribute information b corresponding to the attribute type B, which is the attribute type guaranteed by the attribute information a corresponding to the attribute type A corresponding to the attribute type A for authenticating the user, is managed, and the attribute corresponding to the authentication result An authentication attribute information management server for providing information b to the attribute information distribution server;
An attribute information distribution server that acquires attribute information corresponding to the recognition result from the authentication attribute information management server and distributes the attribute information to the user terminal;
Requests the authentication attribute information management server or the attribute information distribution server to authenticate with the attribute information a, acquires the attribute information b, and corresponds to the attribute type C that is an attribute type that can be acquired without authentication from the information providing server Attribute information c to be acquired, the attribute matching process for matching the attribute information b with the attribute information c, and the attribute information c of the attribute information corresponding to the attribute type B as the attribute information c verified in the attribute matching process. As a user terminal,
An attribute information acquisition system characterized by comprising: A user terminal connected to the attribute information distribution server and the authentication attribute information management server via a network,
An attribute information requesting unit for requesting attribute information by sending an attribute information acquisition request including an attribute type and an attribute item of the requested attribute information to the attribute information distribution server and the information providing server;
An authentication unit that sends the attribute information a corresponding to the attribute type A that is an attribute type for performing user authentication to the attribute information distribution server or the authentication attribute information management server, and requests user authentication;
From the information providing server, attribute information c corresponding to the attribute type C, which is an attribute type that can be acquired without authentication, and from the authentication attribute information management server, attribute information b corresponding to the attribute type B that is an attribute type guaranteed by the authentication. An attribute information acquisition unit to acquire each;
A user terminal comprising: An attribute information distribution server connected to a user terminal and an authentication attribute information management server via a network,
A distribution authentication unit that authenticates a user with the user terminal or acquires an authentication result of authentication of the user by the authentication attribute information management server and an identifier of the authentication attribute information management server;
The attribute information b corresponding to the attribute type B that is the attribute type guaranteed by the corresponding authentication is acquired from the corresponding authentication attribute information management server based on the authentication result output by the distribution authentication unit, and the attribute information b is An attribute information distribution unit distributed to the user terminal;
An attribute information distribution server characterized by comprising: An attribute information acquisition and provision server connected to a user terminal, an authentication attribute information management server, and an attribute information distribution server via a network,
An authentication unit for authenticating the user terminal and the attribute information distribution server;
An attribute information acquisition unit that acquires attribute information b corresponding to the attribute type B from Kishoku of information distribution servers on the authenticated is guaranteed attribute type by the authentication,
An attribute information providing unit that provides the user terminal with the attribute information acquired by the attribute information acquiring unit;
An attribute information acquisition and provision server characterized by comprising:   A program for causing a computer to function as the user terminal according to claim 6, the attribute information distribution server according to claim 7, or the attribute information acquisition / providing server according to claim 8.

Images