User authentication system, user authentication device, user authentication method, and program

Abstract

To improve convenience for one or both of a network service operator and a user when a user uses a network service.SOLUTION: A user authentication system comprises: an authentication request acquisition unit for acquiring an authentication request indicating that a user is a specific user; a first non-fungible token information acquisition unit for requesting a non-fungible token information management device for first non-fungible token information associated with the specific user and acquiring the requested first non-fungible token information from the non-fungible token information management device; a specific user authentication unit for authenticating that the user is the specific user based on the acquisition of the first non-fungible token information; and an access right setting unit for setting access rights in a network service for the specific user based on the authentication of the user that the user is the specific user.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a user authentication system, a user authentication device, a user authentication method, and a program. [Background technology]

[0002] In product development and sales, attempts are being made to build and operate communication services such as social networking services (SNS) in order to incorporate user opinions about products and the like. For example, Patent Document 1 discloses an example of such a communication service in which a network system is composed of an unspecified number of individuals, their own network-connected devices (such as mobile phones and PCs), a network allowing communication between the unspecified number of individuals, a server computer with the function of editing registered personal information into specific groups and connecting them to the network, and an operator who operates and manages the server computer.The network system allows conversations and information exchanges between comrades who have been registered in advance by the individual users via the network communication network, and the system discloses a passive chat service system with arbitrary time designation that is characterized by judging the suitability of subscribers within the group and connecting them. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2004-318584 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the technology described in Patent Document 1, when using a communication service, personal information such as address, name, telephone number, email address, and place of employment must be registered in advance. Therefore, there is a problem that the operator of the communication service must incur costs in managing personal information. In addition, there is a problem that the user must register as a user for each network service such as a communication service, which is not convenient for the user. Thus, when a user uses a network service, there is a problem that the convenience for either the operator of the network service or the user, or for both, is insufficient.

[0005] The present invention has been made in consideration of the above circumstances, and its object is to provide a user authentication system, a user authentication device, a user authentication method, and a program that can improve the convenience of either or both the operator and the user of a network service when a user uses the network service. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present invention is a user authentication system comprising an authentication request acquisition unit that acquires an authentication request indicating that the user is a specific user, a first non-fungible token information acquisition unit that requests first non-fungible token information associated with the specific user from a non-fungible token information management device and acquires the requested first non-fungible token information from the non-fungible token information management device, a specific user authentication unit that authenticates the user as the specific user based on the acquisition of the first non-fungible token information, and an access right setting unit that sets access rights in network services for the specific user based on the authentication that the user is the specific user.

[0007] Also, one aspect of the present invention is a user authentication device that includes an authentication request acquisition unit that acquires an authentication request indicating that the user is a specific user, a first non-fungible token information acquisition unit that requests first non-fungible token information associated with the specific user from a non-fungible token information management device and acquires the requested first non-fungible token information from the non-fungible token information management device, a specific user authentication unit that authenticates the user as the specific user based on the acquisition of the first non-fungible token information, and an access right setting unit that sets access rights in network services for the specific user based on the authentication that the user is the specific user.

[0008] Also, one aspect of the present invention is a user authentication method executed by a computer of a user authentication device, the user authentication method having an authentication request acquisition step of acquiring an authentication request indicating that the user is a specific user, a first non-fungible token information acquisition step of requesting first non-fungible token information associated with the specific user from a non-fungible token information management device and acquiring the requested first non-fungible token information from the non-fungible token information management device, a specific user authentication step of authenticating that the user is the specific user based on the acquisition of the first non-fungible token information, and an access right setting step of setting access rights in network services for the specific user based on the authentication that the user is the specific user.

[0009] Also, one aspect of the present invention is a program for causing a program to function as an authentication request acquisition means for acquiring an authentication request indicating that the user is a specific user, a first non-fungible token information acquisition means for requesting first non-fungible token information associated with the specific user from a non-fungible token information management device and acquiring the requested first non-fungible token information from the non-fungible token information management device, a specific user authentication means for authenticating that the user is the specific user based on the acquisition of the first non-fungible token information, and an access right setting means for setting access rights in network services for the specific user based on the authentication that the user is the specific user. Effect of the Invention

[0010] As described above, according to one aspect of the present invention, when a user uses a network service, it is possible to improve convenience for one or both of the operator and the user of the network service. [Brief description of the drawings]

[0011] [Figure 1] 1 is a system configuration diagram showing an example of the configuration of a user authentication system according to a first embodiment of the present invention. [Diagram 2] 1 is a block diagram showing an example of a configuration of a user authentication device according to an embodiment of the present invention; [Diagram 3] 10 is a sequence diagram showing an example of a user authentication process in the user authentication system according to the embodiment. FIG. [Figure 4] 10 is a flowchart illustrating an example of a user authentication process in the user terminal device according to the embodiment. [Diagram 5] 5 is a flowchart showing an example of a user authentication process in the user authentication device according to the embodiment. [Figure 6] 10 is a flowchart showing an example of a user authentication process in a user authentication device according to a modified example of the present embodiment. [Figure 7]FIG. 11 is a block diagram showing an example of a configuration of a user authentication device according to a second embodiment of the present invention. [Figure 8] 5 is a flowchart showing an example of a user authentication process in the user authentication device according to the embodiment. [Figure 9] FIG. 13 is a block diagram showing an example of a configuration of a user authentication device according to a third embodiment of the present invention. [Figure 10] 5 is a flowchart showing an example of a user authentication process in the user authentication device according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] (First embodiment) A first embodiment of the present invention will now be described with reference to the drawings. FIG. 1 is a system configuration diagram showing an example of the configuration of a user authentication system SYS according to the first embodiment of the present invention. The user authentication system SYS of the present invention includes a user terminal device 100, a service server device 200, a non-fungible token information management device 300, and a user authentication device 400. The user terminal device 100, the service server device 200, the non-fungible token information management device 300, and the user authentication device 400 are connected to each other via a network via wired or wireless means so as to be able to communicate with each other.

[0013] The user authentication system SYS is a user authentication system that receives an authentication request indicating that the user is a specific user, requests first non-fungible token information associated with the specific user from a non-fungible token information management device, obtains the requested first non-fungible token information from the non-fungible token information management device, authenticates that the user is a specific user based on the acquisition of the first non-fungible token information, and sets access rights in network services for the specific user based on the authentication that the user is a specific user.

[0014] Non-fungible token information is also called proof of authenticity information or NFT (Non-Fungible Token). Non-fungible token information is a unique and non-fungible token recorded on the blockchain.

[0015] The user terminal device 100 is a terminal device that can be used by a user, such as a smartphone, a tablet terminal device, or a personal computer (PC).

[0016] The service server device 200 is a server device operated by a network service provider such as a communication service provider. For example, the service server device 200 provides a network service to the user terminal device 100 by performing user registration, login, etc. by the user terminal device 100. In addition, the service server device 200 provides a specific network service to a specific user, the specific user being a user authenticated using non-fungible token information. The specific network service is a specific community service in the network service, a specific website in the network service, etc.

[0017] The non-fungible token information management device 300 is a management device that manages non-fungible token information. In this embodiment, the non-fungible token information management device 300 will be described as managing non-fungible token information when a user has acquired non-fungible token information in advance, but the user may newly acquire non-fungible token information by purchasing or the like, and the non-fungible token information newly acquired may be managed by the non-fungible token information management device 300. The non-fungible token information management device 300 may be, for example, a software wallet management device that manages software wallets, a marketplace for non-fungible token information, or a platform for non-fungible token information.

[0018] When the user authentication device 400 acquires a user authentication request from the user terminal device 100, it requests the non-fungible token information associated with the user from the non-fungible token information management device 300. The user authentication device 400 acquires the non-fungible token information associated with the user in response to the request. The user is a user who has been authenticated as a specific user or is about to be authenticated as such. The user authentication device 400 authenticates the user as a specific user based on the acquisition of the non-fungible token information, and sets an access right in the network service for the specific user based on the authentication as the specific user. The access right in the network service is a participation right in a specific community in the network service or a connection right to a specific website in the network service. Setting the access right means setting a participation right to allow participation in a specific community in the network service, or setting a connection right to allow connection to a specific website in the network service.

[0019] A user who has been granted access rights to a network service can join a specific community in the network service or connect to a specific website in the network service by connecting to a service server from a user terminal device 100.

[0020] In this way, the user authentication device 400 can authenticate whether the user is a specific user without managing the user's personal information in the device itself, thereby reducing the cost of managing personal information. Furthermore, when the user uses a network service, the user authentication device 400 allows the user to use the network service without newly registering the user. Therefore, when the user uses the network service, the user authentication device 400 can improve the convenience of one or both of the operator of the network service and the user.

[0021] Next, the configuration of user authentication device 400 will be described.

[0022] FIG. 2 is a block diagram showing an example of the functional configuration of the user authentication device 400 according to this embodiment. The user authentication device 400 includes a communication unit 41 , a storage unit 42 , an input unit 43 , an output unit 44 , and a control unit 45 . The communication unit 41 has a function of communicating with each of the user terminal device 100, the service server device 200, and the non-fungible token information management device 300 via wired or wireless communication. The communication unit 41 outputs various information received from each of the user terminal device 100, the service server device 200, and the non-fungible token information management device 300 to the control unit 45. In addition, the communication unit 41 transmits various information output from the control unit 45 to each of the user terminal device 100, the service server device 200, and the non-fungible token information management device 300.

[0023] The memory unit 42 is configured with a storage medium, for example, a hard disk drive (HDD), a flash memory, an electrically erasable programmable read only memory (EEPROM), a random access read / write memory (RAM), a read only memory (ROM), or any combination of these storage media. The storage unit 42 may be, for example, a non-volatile memory.

[0024] The storage unit 42 stores various data. For example, the storage unit 42 temporarily stores user information 421.

[0025] The user information 421 is information in which user identification information for identifying a user and non-fungible token information corresponding to the user identification information are associated with each other. The user identification information is, for example, a user identifier (ID). The non-fungible token information is non-fungible token identification information, for example, a non-fungible token identifier (ID).

[0026] The input unit 43 is an input device such as a mouse or a keyboard connected to the user authentication device 400. The input unit 43 accepts an operation input input from the outside. The input unit 43 outputs an operation signal to the control unit 45 according to the operation input.

[0027] The output unit 44 is an output device such as a display device, etc. The output unit 44 outputs presentation information such as a display image output from the control unit 45 to an output device of its own device or to another device such as the user terminal device 100.

[0028] The control unit 45 has a function of controlling each unit of the user authentication device 400 . The control unit 45 is configured to include a user information acquisition unit 451, a non-fungible token information acquisition unit 452, an authentication unit 453, an access right setting unit 454, and a notification unit 455.

[0029] The user information acquisition unit 451 acquires user information. Specifically, the user information acquisition unit 451 acquires an authentication request indicating that the user is a specific user from the user terminal device 100 via a network service operated by the service server device 200. The authentication request includes user identification information of the user. The user information acquisition unit 451 outputs the user identification information to the non-fungible token information acquisition unit 452.

[0030] When the user identification information is input from the user information acquisition unit 451, the non-fungible token information acquisition unit 452 requests non-fungible token information corresponding to the user identification information from the non-fungible token information management device 300. In response to the request, the non-fungible token information acquisition unit 452 acquires non-fungible token information corresponding to the user identification information from the non-fungible token information management device 300 via the communication unit 41. The non-fungible token information acquisition unit 452 outputs the non-fungible token information and the user identification information to the authentication unit 453.

[0031] When the authentication unit 453 receives the user identification information and the non-fungible token information corresponding to the user identification information from the non-fungible token information acquisition unit 452, the authentication unit 453 authenticates the user corresponding to the user identification information as a specific user based on the acquisition of the non-fungible token information. The authentication unit 453 outputs the authentication result and the user identification information to the access right setting unit 454.

[0032] When the authentication result and the user identification information are input from the authentication unit 453, the access right setting unit 454 sets the access right for the user identification information. Specifically, the access right setting unit 454 causes the service server device 200 to set the access right for the user identification information via the communication unit 41. More specifically, the access right setting unit 454 causes the user identification information to set a participation right to enable participation in a specific community in the network service, and causes the user identification information to set a connection right to enable connection to a specific website in the network service. When the access right setting is completed, the access right setting unit 454 generates a setting completion notice. The access right setting unit 454 outputs the setting completion notice to the notice unit 455.

[0033] When the setting completion notification is input from the access right setting unit 454, the notification unit 455 generates presentation information indicating that the setting of the access right has been completed. The notification unit 455 notifies the user terminal device 100 of the presentation information via the communication unit 41.

[0034] Next, the flow of user authentication processing in the user authentication system SYS will be described.

[0035] FIG. 3 is a sequence diagram showing an example of a user authentication process in the user authentication system SYS according to this embodiment. In step ST100, the user terminal device 100 connects to a network service operated by the service server device 200. Based on the user's selection of an operator on the display screen of the user terminal device 100 indicating that authentication is to be performed for the specific user, the user terminal device 100 executes the process of step ST101.

[0036] In step ST101, the user terminal device 100 transmits an authentication request including user identification information to the user authentication device 400. Next, the user authentication device 400 executes the process of step ST102.

[0037] In step ST102, the user authentication device 400 transmits a non-fungible token information acquisition request including the user identification information to the non-fungible token information management device 300. After that, the user authentication device 400 executes the process of step ST103.

[0038] In step ST103, the user authentication device 400 acquires non-fungible token information corresponding to the user identification information from the non-fungible token information management device 300 in response to the non-fungible token information acquisition request. After that, the user authentication device 400 executes the process of step ST104.

[0039] In step ST104, the user authentication device 400 authenticates the user of the user identification information corresponding to the non-fungible token information as a specific user based on the acquired non-fungible token information. After that, the user authentication device 400 executes the process of step ST105.

[0040] In step ST105, the user authentication device 400 sets an access right to the user identification information. Specifically, the user authentication device 400 causes the service server device 200 to set an access right to the user identification information. After that, the user authentication device 400 executes the process of step ST106.

[0041] In step ST106, when the setting of the access right is completed, the user authentication device 400 generates presentation information indicating that the setting of the access right is completed. The user authentication device 400 outputs the presentation information indicating that the setting of the access right is completed to the user terminal device 100. Next, the user terminal device 100 executes the process of step ST107.

[0042] In step ST107, the user terminal device 100 connects to a specific community in the network service operated by the service server device 200, or connects to a specific website in the network service operated by the service server device 200. After that, the service server device 200 executes the process of step ST108.

[0043] In step ST108, based on the connection of the user terminal device 100, the service server device 200 provides contents in a specific community in the network service operated by the service server device 200 or contents in a specific website in the network service operated by the service server device 200. After that, the user authentication system SYS ends the user authentication process in FIG.

[0044] Next, the user authentication process in the user terminal device will be described.

[0045] FIG. 4 is a flowchart showing an example of a user authentication process in the user terminal device 100 according to this embodiment. In step S101, the user terminal device 100 transmits an authentication request including user identification information to the user authentication device 400. Next, the user terminal device 100 executes the process of step S102.

[0046] In step S102, the user terminal device 100 acquires, as a response to the authentication request, presentation information indicating that the setting of the access right has been completed, from the user authentication device 400. Next, the user terminal device 100 executes the process of step S103.

[0047] In step S103, based on the access right being set (granted), the user terminal device 100 connects to content in a specific community in the network service operated by the service server device 200 or to content in a specific website in the network service operated by the service server device 200. After that, the user terminal device 100 ends the user authentication process in FIG.

[0048] Next, the user authentication process in the user authentication device 400 will be described.

[0049] FIG. 5 is a flowchart showing an example of a user authentication process in the user authentication device 400 according to this embodiment. In step S201, the user authentication device 400 acquires an authentication request indicating that the user is a specific user from the user terminal device 100. Next, the user authentication device 400 executes the process of step S202.

[0050] In step S202, the user authentication device 400 transmits a non-fungible token information acquisition request corresponding to the user identification information included in the authentication request to the non-fungible token information management device 300. After that, the user authentication device 400 executes the process of step S203.

[0051] In step S203, as a response to the non-fungible token information acquisition request, non-fungible token information corresponding to the user identification information is acquired from the non-fungible token information management device 300. After that, the user authentication device 400 executes the process of step S204.

[0052] In step S204, the user authentication device 400 authenticates the user identification information corresponding to the non-fungible token information as a specific user based on the acquired non-fungible token information. After that, the user authentication device 400 executes the process of step S205.

[0053] In step S205, the user authentication device 400 sets an access right for the user identification information. Specifically, the user authentication device 400 causes the service server device 200 to set an access right for the user identification information. More specifically, the user authentication device 400 causes the service server device 200 to set a participation right for the user identification information to enable participation in a specific community in the network service. The user authentication device 400 also causes the service server device 200 to set a connection right for the user identification information to enable connection to a specific website in the network service. Thereafter, the user authentication device 400 executes the process of step S206.

[0054] In step S206, the user authentication device 400 generates presentation information indicating that the access right setting has been completed. The user authentication device 400 transmits the presentation information indicating that the access right setting has been completed to the user authentication device 100. Then, the user authentication device 400 ends the user authentication process in FIG.

[0055] As such, the user authentication system SYS of this embodiment includes an authentication request acquisition unit (user information acquisition unit 451) that acquires an authentication request indicating that the user is a specific user, a first non-fungible token information acquisition unit (non-fungible token information acquisition unit 452) that requests first non-fungible token information associated with the specific user from the non-fungible token information management device and acquires the requested first non-fungible token information from the non-fungible token information management device, a specific user authentication unit (authentication unit 453) that authenticates that the user is a specific user based on the acquisition of the first non-fungible token information, and an access right setting unit 454 that sets access rights in network services for the specific user based on the authentication that the user is a specific user.

[0056] In this way, the user authentication system SYS can authenticate whether the user is a specific user without managing the user's personal information on its own device, thereby reducing the cost of managing personal information. Furthermore, when a user uses a network service, the user authentication system SYS allows the user to use the network service without newly registering the user. Therefore, when a user uses a network service, the user authentication system SYS can improve the convenience of either or both the operator and the user of the network service.

[0057] In the above user authentication system SYS, the access right is the right to participate in a specific community in a network service or the right to connect to a specific website in a network service.

[0058] In this way, a user can participate in a specific community or connect to a specific website without providing personal information, so that, for example, in a royal customer participation community service for incorporating user opinions in product development and sales at a manufacturer, the user can be easily authenticated as a royal customer and the user's opinions can be incorporated. This improves user convenience. In addition, since the manufacturer can centrally manage the user's purchase proof and behavior history, it becomes unnecessary to build a new system, and the cost associated with building the system can be reduced.

[0059] Next, a modification of this embodiment will be described.

[0060] In this modified example, a case will be described in which a specific user is an application or program for automating certain tasks or processes, which is called a bot (BOT).

[0061] FIG. 6 is a flowchart showing an example of a user authentication process in the user authentication device 400 according to the modified example of this embodiment. In step S301, the user authentication device 400 acquires an authentication request. The authentication request includes user identification information. The user identification information is chat user identification information, that is, BOT user identification information. After that, the user authentication device 400 executes the process of step S302.

[0062] In step S302, user authentication device 400 temporarily stores the user identification information included in the authentication request in storage unit 42. After that, 400 executes the process of step S303.

[0063] In step S303, the user authentication device 400 judges whether the user identification information included in the authentication request is an already authenticated user. Specifically, the non-fungible token information acquisition unit 452 refers to the storage unit 42 and judges whether the user identification information included in the authentication request is an already authenticated user. If the user identification information included in the authentication request is an already authenticated user (step S303 YES), the user authentication device 400 ends the user authentication process in Fig. 6. On the other hand, if the user identification information included in the authentication request is not an authenticated user (step S303 NO), the user authentication device 400 executes the process of step S304.

[0064] In step S304, user authentication device 400 transmits a specific login URL, which is a login site of the user authentication system, to user terminal device 100. After that, user authentication device 400 executes the process of step S305.

[0065] In step S305, the user authentication device 400 determines whether or not the user terminal device 100 has connected to the specific login URL, based on the specific login URL being provided to the user via the user terminal device 100. After that, the user authentication device 400 executes the process of step S306.

[0066] In step S306, the user authentication device 400 transmits a non-fungible token information acquisition request corresponding to the user identification information of the user terminal device 100 to the user terminal device 100. After that, the user authentication device 400 executes the process of step S307.

[0067] In step S307, the user authentication device 400 acquires non-fungible token information corresponding to the user identification information in response to the request to acquire non-fungible token information, and then executes the process of step S308.

[0068] In step S308, the user authentication device 400 associates the acquired non-fungible token information with the user identification information and temporarily stores them in the storage unit 42. The user authentication device 400 also compares the non-fungible token information corresponding to the user identification information temporarily stored in the storage unit 42 with the non-fungible token information corresponding to the user identification information acquired from the non-fungible token information management device 300. If the comparison result shows that the non-fungible token information corresponding to the user identification information temporarily stored in the storage unit 42 matches the non-fungible token information corresponding to the user identification information acquired from the non-fungible token information management device 300, the user authentication device 400 executes the process of step S309.

[0069] In step S309, the user authentication device 400 sets an access right for the user identification information. Specifically, the user authentication device 400 causes the service server device 200 to set an access right for the user identification information. More specifically, the user authentication device 400 causes the service server device 200 to set a participation right for the user identification information to enable participation in a specific community in the network service. The user authentication device 400 also causes the service server device 200 to set a connection right for the user identification information to enable connection to a specific website in the network service. Thereafter, the user authentication device 400 ends the user authentication process in FIG. 6.

[0070] In this way, the user authentication system SYS relating to the modified example of the first embodiment includes an authentication request acquisition unit (user information acquisition unit 451) that acquires an authentication request indicating that the user is a specific user, a first non-fungible token information acquisition unit (non-fungible token information acquisition unit 452) that requests first non-fungible token information associated with the specific user from the non-fungible token information management device and acquires the requested first non-fungible token information from the non-fungible token information management device, a specific user authentication unit (authentication unit 453) that authenticates that the user is a specific user based on the acquisition of the first non-fungible token information, and an access right setting unit 454 that sets access rights in network services for the specific user based on the authentication that the user is a specific user.

[0071] In this way, the user authentication system SYS can authenticate whether the user is a specific user without managing the user's personal information on its own device, thereby reducing the cost of managing personal information. Furthermore, when a user uses a network service, the user authentication system SYS allows the user to use the network service without newly registering the user. Therefore, when a user uses a network service, the user authentication system SYS can improve the convenience of either or both the operator and the user of the network service.

[0072] In the above user authentication system SYS, the access right is the right to participate in a specific community in a network service or the right to connect to a specific website in a network service.

[0073] In this way, a user can participate in a specific community or connect to a specific website without providing personal information, so that, for example, in a royal customer participation community service for incorporating user opinions in product development and sales at a manufacturer, the user can be easily authenticated as a royal customer and the user's opinions can be incorporated. This improves user convenience. In addition, since the manufacturer can centrally manage the user's purchase proof and behavior history, it becomes unnecessary to build a new system, and the cost associated with building the system can be reduced.

[0074] Second Embodiment Next, a second embodiment will be described.

[0075] In the second embodiment, an example of a case where a user authentication process is performed using an address of a software folder will be described. Here, in the second embodiment, the differences from the first embodiment will be mainly described, and the description of the other aspects will be omitted by citing the description of the first embodiment.

[0076] FIG. 7 is a block diagram showing an example of a configuration of a user authentication device 400 according to the second embodiment of the present invention. The user authentication device 400 includes a communication unit 41, a storage unit 42, an input unit 43, an output unit 44, and a control unit 45. The storage unit 42 stores user information 421. The control unit 45 includes a user information acquisition unit 451, a non-fungible token information acquisition unit 452, an authentication unit 453, an access right setting unit 454, a notification unit 455, an association unit 456, a software wallet information acquisition unit 457, and a comparison determination unit 458.

[0077] When the user identification information is input from the user information acquisition unit 451, the non-fungible token information acquisition unit 452 requests non-fungible token information corresponding to the user identification information from the non-fungible token information management device 300. In response to the request, the non-fungible token information acquisition unit 452 acquires non-fungible token information corresponding to the user identification information from the non-fungible token information management device 300 via the communication unit 41. The non-fungible token information acquisition unit 452 outputs the non-fungible token information and the user identification information to the matching determination unit 458.

[0078] In addition, the non-fungible token information acquisition unit 452 acquires non-fungible token information (second non-fungible token information) corresponding to the software wallet from the non-fungible token information platform based on the software wallet address acquired by the software wallet information acquisition unit 457.

[0079] Based on the result of the determination by the comparison determination unit 458, the authentication unit 453 authenticates that the user is a specific user.

[0080] The associating unit 456 associates the user identification information with non-fungible token information (first non-fungible token information) corresponding to the user identification information, and temporarily stores the information in the storage unit 42.

[0081] The software wallet information acquisition unit 457 acquires a software wallet address, which is the address of the user's software wallet, from the user terminal device 100. The software wallet information acquisition unit 457 outputs the software wallet address to the non-fungible token information acquisition unit 452.

[0082] The matching determination unit 458 verifies whether or not the non-fungible token information (first non-fungible token information) corresponding to the user identification information stored in the storage unit 42 corresponds to the non-fungible token information (second non-fungible token information) corresponding to the software wallet address, i.e., whether or not they match. If the first non-fungible token information corresponds to the second non-fungible token information, the matching determination unit 458 outputs the determination result to the access right setting unit 454.

[0083] Next, the user authentication process in the user authentication device 400 according to this embodiment will be described.

[0084] FIG. 8 is a flowchart showing an example of a user authentication process in the user authentication device 400 according to this embodiment. In step S401, the user authentication device 400 acquires an authentication request indicating that the user is a specific user from the user terminal device 100. Next, the user authentication device 400 executes the process of step S402.

[0085] In step S402, the user authentication device 400 transmits a non-fungible token information acquisition request corresponding to the user identification information included in the authentication request to the non-fungible token information management device 300. After that, the user authentication device 400 executes the process of step S403.

[0086] In step S403, as a response to the non-fungible token information acquisition request, non-fungible token information corresponding to the user identification information is acquired from the non-fungible token information management device 300. After that, the user authentication device 400 executes the process of step S404.

[0087] In step S404, user authentication device 400 acquires the software wallet address from user terminal device 100. Thereafter, user authentication device 400 executes the process of step S405.

[0088] In step S405, the user authentication device 400 transmits a request to acquire non-fungible token information corresponding to the software wallet address to the platform for non-fungible token information. In response to the request, the user authentication device 400 acquires non-fungible token information corresponding to the software wallet address from the platform for non-fungible token information. The user authentication device 400 then executes the process of step S406.

[0089] In step S406, the user authentication device 400 compares the first non-fungible token information with the second non-fungible token information. The user authentication device 400 authenticates that the user is a specific user based on the correspondence between the first non-fungible token information and the second non-fungible token information. After that, the user authentication device 400 executes the process of step S407.

[0090] In step S407, the user authentication device 400 sets an access right for the user identification information. Specifically, the user authentication device 400 causes the service server device 200 to set an access right for the user identification information. More specifically, the user authentication device 400 causes the service server device 200 to set a participation right for the user identification information to enable participation in a specific community in the network service. The user authentication device 400 also causes the service server device 200 to set a connection right for the user identification information to enable connection to a specific website in the network service. Thereafter, the user authentication device 400 executes the process of step S408.

[0091] In step S408, the user authentication device 400 generates presentation information indicating that the access right setting has been completed. The user authentication device 400 transmits the presentation information indicating that the access right setting has been completed to the user terminal device 100. Then, the user authentication device 400 ends the user authentication process in FIG.

[0092] As such, the user authentication system SYS of this embodiment includes an authentication request acquisition unit (user information acquisition unit 451) that acquires an authentication request indicating that the user is a specific user, a first non-fungible token information acquisition unit (non-fungible token information acquisition unit 452) that requests first non-fungible token information associated with the specific user from the non-fungible token information management device and acquires the requested first non-fungible token information from the non-fungible token information management device, a specific user authentication unit (authentication unit 453) that authenticates that the user is a specific user based on the acquisition of the first non-fungible token information, and an access right setting unit 454 that sets access rights in network services for the specific user based on the authentication that the user is a specific user.

[0093] In this way, the user authentication system SYS can authenticate whether the user is a specific user without managing the user's personal information on its own device, thereby reducing the cost of managing personal information. Furthermore, when a user uses a network service, the user authentication system SYS allows the user to use the network service without newly registering the user. Therefore, when a user uses a network service, the user authentication system SYS can improve the convenience of either or both the operator and the user of the network service.

[0094] In the above user authentication system SYS, the access right is the right to participate in a specific community in a network service or the right to connect to a specific website in a network service.

[0095] In this way, a user can participate in a specific community or connect to a specific website without providing personal information, so that, for example, in a royal customer participation community service for incorporating user opinions in product development and sales at a manufacturer, the user can be easily authenticated as a royal customer and the user's opinions can be incorporated. This improves user convenience. In addition, since the manufacturer can centrally manage the user's purchase proof and behavior history, it becomes unnecessary to build a new system, and the cost associated with building the system can be reduced.

[0096] Also, in the above user authentication system SYS, there is provided a user identifier acquisition unit (user information acquisition unit 451) which acquires a user identifier of a specific user in a network service, an association unit 456 which associates the user identifier with first non-fungible token information, a wallet address acquisition unit (software wallet information acquisition unit 457) which requests a wallet address corresponding to the second non-fungible token information from the software wallet management device and acquires the wallet address corresponding to the requested second non-fungible token information from the software wallet management device, and requests the second non-fungible token information from the non-fungible token information management device based on the wallet address. The system further includes a second non-fungible token information acquisition unit (non-fungible token information acquisition unit 452) that acquires non-fungible token information, and a comparison determination unit 458 that determines whether the first non-fungible token information and the second non-fungible token information correspond to each other. The first non-fungible token information acquisition unit (non-fungible token information acquisition unit 452) acquires the first non-fungible token information based on a user identifier, and the access right setting unit 454 sets participation rights to enable participation in a specific community in the network service or connection rights to enable connection to a specific website in the network service when the first non-fungible token information and the second non-fungible token information correspond to each other.

[0097] In this way, access rights can be managed more easily.

[0098] (Third embodiment) Next, a third embodiment will be described.

[0099] In the third embodiment, an example of a case where user authentication processing is performed via a marketplace for non-fungible token information will be described. Here, in the third embodiment, the differences from the first embodiment will be mainly described, and the description of the other aspects will be omitted by citing the description of the first embodiment.

[0100] FIG. 9 is a block diagram showing an example of a configuration of a user authentication device 400 according to the third embodiment of the present invention. The user authentication device 400 includes a communication unit 41, a storage unit 42, an input unit 43, an output unit 44, and a control unit 45. The storage unit 42 stores user information 421. The control unit 45 includes a user information acquisition unit 451, a non-fungible token information acquisition unit 452, an authentication unit 453, an access right setting unit 454, a notification unit 455, a first association unit 460, a second association unit 461, and a matching determination unit 458.

[0101] The user information acquisition unit 451 acquires user information. Specifically, the user information acquisition unit 451 acquires an authentication request indicating that the user is a specific user from the user terminal device 100 via a network service operated by the service server device 200. The authentication request includes user identification information of the user. The user information acquisition unit 451 outputs the user identification information to the non-fungible token information acquisition unit 452.

[0102] In addition, the user information acquisition unit 451 acquires the user name in the marketplace of the non-fungible token information from the user terminal device 100. The user information acquisition unit 451 outputs information on the user name in the marketplace of the non-fungible token information to the non-fungible token information acquisition unit 452.

[0103] When the user identification information is input from the user information acquisition unit 451, the non-fungible token information acquisition unit 452 requests non-fungible token information corresponding to the user identification information from the non-fungible token information management device 300. In response to the request, the non-fungible token information acquisition unit 452 acquires non-fungible token information corresponding to the user identification information from the non-fungible token information management device 300 via the communication unit 41. The non-fungible token information acquisition unit 452 outputs the non-fungible token information and the user identification information to the matching determination unit 458.

[0104] In addition, the non-fungible token information acquisition unit 452 acquires non-fungible token information (second non-fungible token information) corresponding to the username from the marketplace of non-fungible token information based on the username of the marketplace of non-fungible token information.

[0105] Based on the result of the determination by the comparison determination unit 458, the authentication unit 453 authenticates that the user is a specific user.

[0106] The first associating unit 460 associates the user identification information with non-fungible token information (first non-fungible token information) corresponding to the user identification information and temporarily stores the information in the storage unit 42.

[0107] The first associating unit 460 associates the user name with non-fungible token information (second non-fungible token information) corresponding to the user name and temporarily stores the information in the storage unit 42.

[0108] The matching determination unit 458 checks whether the non-fungible token information (first non-fungible token information) corresponding to the user identification information stored in the storage unit 42 corresponds to the non-fungible token information (second non-fungible token information) corresponding to the user name, i.e., whether they match. If the first non-fungible token information corresponds to the second non-fungible token information, the matching determination unit 458 outputs the determination result to the access right setting unit 454.

[0109] Next, the user authentication process in the user authentication device 400 according to this embodiment will be described.

[0110] FIG. 10 is a flowchart showing an example of a user authentication process in the user authentication device 400 according to this embodiment. Here is an example. In step S501, the user authentication device 400 acquires an authentication request indicating that the user is a specific user from the user terminal device 100. Next, the user authentication device 400 executes the process of step S502.

[0111] In step S502, the user authentication device 400 transmits a non-fungible token information acquisition request corresponding to the user identification information included in the authentication request to the non-fungible token information management device 300. After that, the user authentication device 400 executes the process of step S503.

[0112] In step S503, as a response to the non-fungible token information acquisition request, non-fungible token information corresponding to the user identification information is acquired from the non-fungible token information management device 300. After that, the user authentication device 400 executes the process of step S504.

[0113] In step S504, the user authentication device 400 acquires the user name in the marketplace of the non-fungible token information from the user terminal device 100. After that, the user authentication device 400 executes the process of step S505.

[0114] In step S505, the user authentication device 400 transmits a request to acquire non-fungible token information corresponding to a user name in the marketplace of non-fungible token information to the marketplace of non-fungible token information. In response to the request to acquire non-fungible token information, the user authentication device 400 acquires non-fungible token information corresponding to a user name in the marketplace of non-fungible token information from the marketplace of non-fungible token information. The user authentication device 400 then executes the process of step S506.

[0115] In step S506, the user authentication device 400 compares the first non-fungible token information with the second non-fungible token information. The user authentication device 400 authenticates that the user is a specific user based on the correspondence between the first non-fungible token information and the second non-fungible token information. After that, the user authentication device 400 executes the process of step S507.

[0116] In step S507, the user authentication device 400 sets an access right for the user identification information. Specifically, the user authentication device 400 causes the service server device 200 to set an access right for the user identification information. More specifically, the user authentication device 400 causes the service server device 200 to set a participation right for the user identification information to enable participation in a specific community in the network service. The user authentication device 400 also causes the service server device 200 to set a connection right for the user identification information to enable connection to a specific website in the network service. Thereafter, the user authentication device 400 executes the process of step S508.

[0117] In step S508, the user authentication device 400 generates presentation information indicating that the access right setting has been completed. The user authentication device 400 transmits the presentation information indicating that the access right setting has been completed to the user terminal device 100. Then, the user authentication device 400 ends the user authentication process in FIG.

[0118] As such, the user authentication system SYS of this embodiment includes an authentication request acquisition unit (user information acquisition unit 451) that acquires an authentication request indicating that the user is a specific user, a first non-fungible token information acquisition unit (non-fungible token information acquisition unit 452) that requests first non-fungible token information associated with the specific user from the non-fungible token information management device and acquires the requested first non-fungible token information from the non-fungible token information management device, a specific user authentication unit (authentication unit 453) that authenticates that the user is a specific user based on the acquisition of the first non-fungible token information, and an access right setting unit 454 that sets access rights in network services for the specific user based on the authentication that the user is a specific user.

[0119] In this way, the user authentication system SYS can authenticate whether the user is a specific user without managing the user's personal information on its own device, thereby reducing the cost of managing personal information. Furthermore, when a user uses a network service, the user authentication system SYS allows the user to use the network service without newly registering the user. Therefore, when a user uses a network service, the user authentication system SYS can improve the convenience of either or both the operator and the user of the network service.

[0120] In the above user authentication system SYS, the access right is the right to participate in a specific community in a network service or the right to connect to a specific website in a network service.

[0121] In this way, a user can participate in a specific community or connect to a specific website without providing personal information, so that, for example, in a royal customer participation community service for incorporating user opinions in product development and sales at a manufacturer, the user can be easily authenticated as a royal customer and the user's opinions can be incorporated. This improves user convenience. In addition, since the manufacturer can centrally manage the user's purchase proof and behavior history, it becomes unnecessary to build a new system, and the cost associated with building the system can be reduced.

[0122] In addition, in the above user authentication system SYS, there is provided a user identifier acquisition unit (user information acquisition unit 451) that acquires a user identifier of a specific user in a network service, a first association unit (first association unit 460) that associates the user identifier with first non-fungible token information, a username acquisition unit (user information acquisition unit 451) that requests a username associated with the second non-fungible token information from a marketplace that manages the second non-fungible token information and acquires the username associated with the second non-fungible token information from the marketplace, a second association unit (second association unit 461) that associates the username with the user identifier, and a user name acquisition unit (user information acquisition unit 452) that acquires the second non-fungible token information from the marketplace using the username. The system further includes a second non-fungible token information acquisition unit that requests the marketplace and acquires the requested second non-fungible token information from the marketplace, and a comparison determination unit 458 that determines whether the first non-fungible token information and the second non-fungible token information correspond to each other. The first non-fungible token information acquisition unit (non-fungible token information acquisition unit 452) acquires the first non-fungible token information based on a user identifier, and the access right setting unit 454 sets participation rights to enable participation in a specific community in the network service or connection rights to enable connection to a specific website in the network service when the first non-fungible token information and the second non-fungible token information correspond to each other.

[0123] Although the embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes, etc. are possible within the scope that does not deviate from the gist of the present invention.

[0124] For example, in the above embodiment, an example configured with the user authentication device 400 has been described, but one aspect of the present invention may be realized by a plurality of devices including another device capable of realizing a part of the user authentication device 400.

[0125] The program that runs on the user authentication device 400 in one aspect of the present invention may be a program that controls one or more processors such as a CPU (Central Processing Unit) to realize the functions shown in the above-mentioned embodiments and modifications related to one aspect of the present invention (a program that makes a computer function). The computer here also includes a quantum computer. The information handled by each of these devices is temporarily stored in a RAM (Random Access Memory) during processing, and then stored in various storage devices such as a flash memory or an HDD (Hard Disk Drive), and may be read, modified, or written by the CPU or the like as necessary.

[0126] A part or the whole of the user authentication device 400 in each of the above-mentioned embodiments and modifications may be realized by a computer having one or more processors. In this case, the control function may be realized by recording a program for realizing the control function on a computer-readable recording medium, and reading and executing the program recorded on the recording medium into a computer system.

[0127] The "computer system" here refers to a computer system built into the user authentication device 400, and includes hardware such as an OS and peripheral devices. Also, the "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system.

[0128] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and a medium that stores a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in such a case. The above program may be one that realizes part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0129] Also, a part or all of the user authentication device 400 in each of the above-mentioned embodiments and modifications may be realized as an LSI, which is typically an integrated circuit, or may be realized as a chip set. Also, each functional block of the user authentication device 400 in each of the above-mentioned embodiments and modifications may be individually formed into a chip, or may be integrated into a chip in part or in whole. Also, the integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit and / or a general-purpose processor. Also, when an integrated circuit technology that replaces LSI appears due to the advancement of semiconductor technology, it is possible to use an integrated circuit based on that technology.

[0130] Although the embodiments and modifications have been described above in detail with reference to the drawings as one aspect of the present invention, the specific configuration is not limited to the embodiments and modifications, and includes design changes within the scope of the gist of the present invention. In addition, one aspect of the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in the above embodiments and modifications are replaced with elements that have the same effect are also included. [Explanation of symbols]

[0131] SYS User Authentication System 100 User terminal device 200 Service server device 300 Non-fungible token information management device 400 User authentication device 41 Communications Department 42 Storage section 421 User Information 43 Input section 44 Output section 45 Control section 451 User Information Acquisition Unit 452 Non-fungible token information acquisition unit 453 Authentication Department 454 Access rights setting section 455 Notification Department 456 Association section 457 Software Wallet Information Acquisition Department 458 Matching and Judging Unit 460 First Association Section 461 Second Association Section

Claims

1. an authentication request acquisition unit that acquires an authentication request indicating that the user is a specific user; a first non-fungible token information acquisition unit that requests first non-fungible token information associated with the specific user from a non-fungible token information management device and acquires the requested first non-fungible token information from the non-fungible token information management device; A specific user authentication unit that authenticates the specific user based on the acquisition of the first non-fungible token information; an access right setting unit that sets an access right for a network service to the specific user based on the authentication of the specific user; A user authentication system comprising:

2. The access right is a right to participate in a specific community in the network service or a right to connect to a specific website in the network service.

2. The user authentication system according to claim 1.

3. a user identifier acquisition unit that acquires a user identifier of the specific user in the network service; an association unit that associates the user identifier with the first non-fungible token information; a wallet address acquisition unit that requests a wallet address corresponding to second non-fungible token information from a software wallet management device and acquires the wallet address corresponding to the requested second non-fungible token information from the software wallet management device; A second non-fungible token information acquisition unit that acquires the second non-fungible token information by requesting the second non-fungible token information from the non-fungible token information management device based on the wallet address; A matching determination unit that determines whether the first non-fungible token information and the second non-fungible token information correspond to each other; Further equipped with The first non-fungible token information acquisition unit acquires the first non-fungible token information based on the user identifier, the access right setting unit sets a participation right to enable participation in a specific community in the network service or a connection right to enable connection to a specific website in the network service when the first non-fungible token information and the second non-fungible token information correspond to each other; The user authentication system according to claim 2.

4. a user identifier acquisition unit that acquires a user identifier of the specific user in the network service; a first association unit that associates the user identifier with the first non-fungible token information; A username acquisition unit that requests a username associated with second non-fungible token information from a marketplace that manages the second non-fungible token information and acquires the username associated with the second non-fungible token information from the marketplace; a second association unit that associates the user name with the user identifier; A second non-fungible token information acquisition unit that requests the second non-fungible token information from the marketplace using the user name and acquires the requested second non-fungible token information from the marketplace; A matching determination unit that determines whether the first non-fungible token information and the second non-fungible token information correspond to each other; Further equipped with The first non-fungible token information acquisition unit acquires the first non-fungible token information based on the user identifier, the access right setting unit sets a participation right to enable participation in a specific community in the network service or a connection right to enable connection to a specific website in the network service when the first non-fungible token information and the second non-fungible token information correspond to each other; The user authentication system according to claim 2.

5. an authentication request acquisition unit that acquires an authentication request indicating that the user is a specific user; a first non-fungible token information acquisition unit that requests first non-fungible token information associated with the specific user from a non-fungible token information management device and acquires the requested first non-fungible token information from the non-fungible token information management device; A specific user authentication unit that authenticates the specific user based on the acquisition of the first non-fungible token information; an access right setting unit that sets an access right for a network service to the specific user based on the authentication of the specific user; A user authentication device comprising:

6. A user authentication method executed by a computer of a user authentication device, comprising: an authentication request acquisition step of acquiring an authentication request indicating that the user is a specific user; a first non-fungible token information acquisition step of requesting first non-fungible token information associated with the specific user from a non-fungible token information management device and acquiring the requested first non-fungible token information from the non-fungible token information management device; a specific user authentication step of authenticating the specific user based on the acquisition of the first non-fungible token information; an access right setting step of setting an access right for a network service for the specific user based on the authentication of the specific user; A user authentication method comprising:

7. Program, an authentication request acquisition means for acquiring an authentication request indicating that the user is a specific user; a first non-fungible token information acquisition means for requesting first non-fungible token information associated with the specific user from a non-fungible token information management device and acquiring the requested first non-fungible token information from the non-fungible token information management device; A specific user authentication means for authenticating the specific user based on acquisition of the first non-fungible token information; an access right setting means for setting an access right for a network service to the specific user based on the authentication of the specific user; A program to function as a

Images