Authority management system, authority management device, authority management method, and program

Abstract

To prevent an access right from being transferred to a third party.SOLUTION: An authority management system comprises a non-transferable token information issuing unit that issues non-transferable token information to a user, which is predetermined non-transferable token information, and an access right granting unit that grants an access right to the user based on the issuance of the non-transferable token information to the user.SELECTED DRAWING: Figure 2

Description

[Technical field]

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

[0002] Web3, the next generation internet using blockchain technology, is becoming more and more widespread across borders. In this environment, there is a demand for measures and technologies specific to Web3, such as secure tokens for community management. For example, Patent Document 1 discloses an integrated service utilization device for using a service integrated with an object, a place, or an information transmission medium, the integrated service utilization device comprising: a token acquisition means for acquiring a token, which is information for identifying the service integrated with the object, the place, and the information transmission medium; a communication means for communicating with a predetermined server or terminal; a service information acquisition means for transmitting the token, or in addition to the token, either a user identifier or a terminal identifier, or both, to the predetermined server using the communication means, and acquiring service information including at least a unique identifier that is uniquely assigned to the service information; a mark display means for identifying a service identification mark corresponding to the service information each time the service information is acquired and additionally displaying the service identification mark; and a mark utilization means for enabling an operation on any service identification mark and executing a process corresponding to the operation. [Prior art documents] [Patent documents]

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

[0004] However, with the technology described in Patent Document 1, although it is possible to obtain a token and identify a service identification mark corresponding to service information each time service information is obtained, there is a concern that the service identification mark may be transferred to a third party. In addition, when access rights are granted based on a service identification mark, there is a concern that the access rights may be transferred to a third party. Thus, there was concern that access rights might be transferred to third parties.

[0005] The present invention has been made in consideration of the above circumstances, and its purpose is to provide an authority management system, an authority management device, an authority management method, and a program that can prevent access rights from being transferred to third parties. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present invention is an authority management system that includes a non-transferable token information issuing unit that issues non-transferable token information, which is predetermined non-transferable token information, to a user, and an access right granting unit that grants access rights to the user based on the issuance of the non-transferable token information to the user.

[0007] Another aspect of the present invention is an authority management device that includes a non-transferable token information issuing unit that issues non-transferable token information, which is predetermined non-transferable token information, to a user, and an access right granting unit that grants access rights to the user based on the issuance of the non-transferable token information to the user.

[0008] Another aspect of the present invention is an authority management method executed by a computer of an authority management device, the authority management method having a non-transferable token information issuance process for issuing non-transferable token information, which is predetermined non-transferable token information, to a user, and an access right granting process for granting access rights to the user based on the issuance of the non-transferable token information to the user.

[0009] Another aspect of the present invention is a program for causing a computer of an authority management device to execute a non-transferable token information issuance step of issuing non-transferable token information, which is predetermined non-transferable token information, to a user, and an access right granting step of granting access rights to the user based on the issuance of the non-transferable token information to the user. Effect of the Invention

[0010] As described above, according to one aspect of the present invention, it is possible to prevent access rights from being transferred to a third party. [Brief description of the drawings]

[0011] [Figure 1] 1 is a system configuration diagram showing an example of the configuration of a rights management system SYS according to a first embodiment of the present invention. [Diagram 2] 1 is a block diagram showing an example of a configuration of an authority management device 500 according to the present embodiment. [Diagram 3] 10 is a sequence diagram showing an example of a permission management process in the permission management system SYS according to the embodiment. FIG. [Figure 4] 13 is a flowchart showing an example of a right management process in the right management device 500 according to the present embodiment. [Diagram 5] FIG. 11 is a system configuration diagram showing an example of the configuration of a rights management system SYS according to a second embodiment of the present invention. [Figure 6] FIG. 2 is a block diagram showing an example of the configuration of a user authentication device 400 according to the present embodiment. [Figure 7] 10 is a sequence diagram showing an example of a user authentication process in the authority management system SYS according to the embodiment. FIG. [Figure 8] 5 is a flowchart showing an example of a user authentication process in the user terminal device 100 according to the present embodiment. [Figure 9] 10 is a flowchart showing an example of a user authentication process in the user authentication device 400 according to the present embodiment. [Figure 10] 13 is a flowchart showing an example of a user authentication process in the user authentication device 400 according to a modified example of the present embodiment. [Figure 11] FIG. 11 is a block diagram showing an example of a configuration of a user authentication device 400 according to a third embodiment of the present invention. [Figure 12] 10 is a flowchart showing an example of a user authentication process in the user authentication device 400 according to the present embodiment. [Figure 13] FIG. 11 is a block diagram showing an example of a configuration of a user authentication device 400 according to a fourth embodiment of the present invention. [Figure 14] 10 is a flowchart showing an example of a user authentication process in the user authentication device 400 according to the present 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 the authority management system SYS according to the first embodiment of the present invention. The rights management system SYS of the present invention includes a user terminal device 100 and a rights management device 500. The user terminal device 100 and the right management device 500 are connected to each other via a network, either wired or wirelessly, so as to be able to communicate with each other.

[0013] The authority management system SYS is an authority management system that issues non-transferable token information, which is predetermined non-transferable token information, to a user and grants access rights to the user based on the issuance of the non-transferable token information to the user.

[0014] Non-transferable token information is also called Soul Bound Token (SBT), Verifiable Credentials (VC), etc. Non-transferable token information is token information that cannot be transferred to a third party after it is acquired.

[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] When the authority management device 500 acquires user information from the user terminal device 100, the authority management device 500 issues non-transferable token information if the user satisfies a condition. The condition is, for example, that the user has participated in an event, or that the user has registered to participate in an event. The non-transferable token information can be issued for each event. Furthermore, the authority management device 500 grants an access right to the user based on the user issuing predetermined non-transferable token information. The access right is, for example, an access right to a network service, an access right to a specific community in the network service, an access right to a specific website in the network service, etc. Here, granting an access right to the user includes granting a digital certificate such as a certificate that proves that the user participated in the event in addition to granting the above access right.

[0017] In addition, granting an access right to a user may involve displaying the non-transferable token information as a two-dimensional code. The two-dimensional code may be, for example, a QR code (registered trademark). In this case, for example, the non-transferable token information is displayed as a two-dimensional code. For example, the displayed two-dimensional code can be used as a ticket when entering an event, participating in a specific community, or obtaining specific goods.

[0018] A user who has been granted access rights to a network service can, for example, participate in a specific community in the network service or connect to a specific website in the network service by connecting to a service server from the user terminal device 100. Also, a user who has been granted a digital certificate as an access right can, for example, prove that he or she actually participated in an event or registered to participate in the event.

[0019] In this way, the authority management device 500 can prove that the user has participated or registered to participate in an event, etc. Furthermore, the authority management device 500 can prevent the granted access right from being transferred to a third party.

[0020] Next, the configuration of the right management device 500 will be described.

[0021] FIG. 2 is a block diagram showing an example of the configuration of the authority management device 500 according to this embodiment. The right management device 500 includes a communication unit 51, a storage unit 52, an input unit 53, an output unit 54, and a control unit 55.

[0022] The communication unit 51 has a function of communicating with other devices such as the user terminal device 100 via wired or wireless communication. The communication unit 51 outputs various information received from other devices such as the user terminal device 100 to the control unit 55. The communication unit 51 also transmits various information output from the control unit 55 to other devices such as the user terminal device 100.

[0023] The memory unit 52 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 52 may be, for example, a non-volatile memory.

[0024] The storage unit 52 stores various data. For example, the storage unit 52 stores user information 521.

[0025] The user information 521 is information in which user identification information for identifying a user is associated with a wallet address corresponding to the user identification information. The user identification information is, for example, a user identifier (ID).

[0026] The input unit 53 is an input device such as a mouse or a keyboard connected to the authority management device 500. The input unit 53 accepts an operation input input from the outside. The input unit 53 outputs an operation signal to the control unit 55 according to the operation input.

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

[0028] The control unit 55 has a function of controlling each unit of the right management device 500 . The control unit 55 includes a user information acquisition unit 551 , an issuance authentication unit 552 , a non-transferable token information issuing unit 553 , and an access right granting unit 554 .

[0029] The user information acquisition unit 551 acquires user information. The user information acquired by the user information acquisition unit 551 is either or both of user identification information and a wallet address corresponding to the user identification information. The user information acquisition unit 551 acquires user information, for example, when a user applies to participate in an event, or when the user's participation in the event is accepted. The user information acquisition unit 551 outputs the user identification information to the issuance authentication unit 552.

[0030] The issuance authentication unit 552 executes an issuance authentication process for the user identification information. The issuance authentication process is, for example, a process of issuing a two-dimensional code for the user identification information, a process of issuing a one-time code for the user identification information, a process of acquiring a user's wallet address for the user identification information, etc.

[0031] The non-transferable token information issuing unit 553 issues non-transferable token information corresponding to the user identification information based on the issuance authentication process being executed by the issuance authentication unit 552. The non-transferable token information issuing unit 553 issues non-transferable token information corresponding to the user identification information based on, for example, the reading of a two-dimensional code. The non-transferable token information issuing unit 553 also issues non-transferable token information corresponding to the user identification information based on the input of a one-time code. The non-transferable token information issuing unit 553 also issues non-transferable token information from a specific wallet address to the user's wallet address based on the acquisition of the user's wallet address.

[0032] The access right granting unit 554 grants an access right to the user terminal device 100 corresponding to the user identification information, based on the issuance of the non-transferable token information by the non-transferable token information issuing unit 553. In addition, the access right granting unit 554 generates presentation information indicating that the granting of the access right has been completed, and notifies the user terminal device 100 of the presentation information via the communication unit 41.

[0033] Next, the flow of the authority management process in the authority management system SYS will be described.

[0034] FIG. 3 is a sequence diagram showing an example of a permission management process in the permission management system SYS according to this embodiment. In step ST101, the user terminal device 100 transmits user information when applying to participate in an event or when accepting participation in an event to the right management device 500. Next, the right management device 500 executes the process of step ST102.

[0035] In step ST102, the right management device 500 executes the issuance authentication process corresponding to the user information. Next, the user terminal device 100 executes the process of step ST103.

[0036] In step ST103, the user terminal device 100 transmits an authentication request, such as reading the two-dimensional code, inputting the one-time code, and registering the wallet address, to the authority management device 500. After that, the authority management device 500 executes the process of step ST104.

[0037] In step ST104, the right management device 500 issues non-transferable token information. After that, the right management device 500 executes the process of step ST105.

[0038] In step ST105, the authority management device 500 grants the issued non-transferable token information as an access right to the user terminal device 100. After that, the authority management system SYS ends the authority management process in FIG.

[0039] Next, the rights management process in the rights management device 500 will be described.

[0040] FIG. 4 is a flowchart showing an example of the authority management process in the authority management device 500 according to this embodiment. In step S101, the right management device 500 acquires user information from the user terminal device 100. Next, the right management device 500 executes the process of step S102.

[0041] In step S102, the right management device 500 executes an issuance authentication process. Then, the right management device 500 executes a process in step S103.

[0042] In step S103, the right management device 500 issues non-transferable token information. Then, the right management device 500 executes the process of step S104.

[0043] In step S104, the right management device 500 grants the issued non-transferable token information as an access right to the user terminal device 100. After that, the user terminal device 100 ends the right management process in FIG.

[0044] As such, the authority management system SYS of this embodiment comprises a non-transferable token information issuing unit 553 that issues non-transferable token information, which is specified non-transferable token information, to a user, and an access right granting unit 554 that grants access rights to the user based on the issuance of the non-transferable token information to the user.

[0045] In this way, the authority management device 500 can prove that the user has participated or registered to participate in an event, etc. Furthermore, the authority management device 500 can prevent the granted access right from being transferred to a third party.

[0046] Next, a second embodiment of the present invention will be described.

[0047] Second embodiment FIG. 5 is a system configuration diagram showing an example of the configuration of the authority management system SYS according to the second embodiment of the present invention. The rights management 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, a user authentication device 400, and a rights management device 500. The user terminal device 100, the service server device 200, the non-fungible token information management device 300, the user authentication device 400, and the authority management device 500 are connected to each other via a network via wired or wireless means so as to be able to communicate with each other.

[0048] Here, since the authority management device 500 according to this embodiment is similar to the authority management device 500 according to the first embodiment, the description in the first embodiment is used and will not be repeated.

[0049] The authority management system SYS issues non-transferable token information, which is predetermined non-transferable token information, to a user, and grants an access right to the user based on the issuance of the non-transferable token information to the user. The authority management system SYS is also an authority management system that acquires an authentication request indicating that the user is a specific user to whom an access right has been granted, requests first non-fungible token information associated with the specific user from a non-fungible token information management device, acquires the requested first non-fungible token information from the non-fungible token information management device, authenticates the user as a specific user based on the acquisition of the first non-fungible token information, and sets an access right in a network service for the specific user based on the authentication that the user is a specific user.

[0050] 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.

[0051] 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).

[0052] 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.

[0053] 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.

[0054] When the user authentication device 400 acquires a user authentication request from the user terminal device 100 to which the access right is granted by the authority management device 500, the user authentication device 400 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 the 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 the right to participate in a specific community in the network service or the right to connect to a specific website in the network service. Setting the access right means setting the participation right to allow participation in a specific community in the network service, or setting the connection right to allow connection to a specific website in the network service.

[0055] 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.

[0056] 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.

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

[0058] 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, the non-fungible token information management device 300, and the authority management device 500 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, the non-fungible token information management device 300, and the authority management device 500 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, the non-fungible token information management device 300, and the authority management device 500.

[0059] 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.

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

[0061] 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).

[0062] 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.

[0063] 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.

[0064] 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 non-transferable token information acquisition unit 451, a user information acquisition unit 452, a non-fungible token information acquisition unit 453, an authentication unit 454, an access right setting unit 455, and a notification unit 456.

[0065] The non-transferable token information acquisition unit 451 acquires the access right (non-transferable token information) granted by the authority management device 500 from the user terminal device 100.

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

[0067] When the user identification information is input from the user information acquisition unit 452, the non-fungible token information acquisition unit 453 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 453 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 453 outputs the non-fungible token information and the user identification information to the authentication unit 454.

[0068] When the authentication unit 454 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 453, the authentication unit 454 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 454 outputs the authentication result and the user identification information to the access right setting unit 455.

[0069] When the authentication result and the user identification information are input from the authentication unit 454, the access right setting unit 455 sets the access right for the user identification information. Specifically, the access right setting unit 455 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 455 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 455 generates a setting completion notice. The access right setting unit 455 outputs the setting completion notice to the notice unit 456.

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

[0071] Next, the flow of the authority management process in the authority management system SYS will be described.

[0072] FIG. 7 is a sequence diagram showing an example of a user authentication process in the authority management system SYS according to this embodiment. In step ST200, 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 S201.

[0073] In step ST201, the user terminal device 100 transmits non-transferable token information (access right) granted by the right management device 500 to the user authentication device 400. Next, the user authentication device 400 executes the process of step ST203.

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

[0075] In step ST204, 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 ST205.

[0076] In step ST205, the user authentication device 400 acquires, as a response to the non-fungible token information acquisition request, non-fungible token information corresponding to the user identification information from the non-fungible token information management device 300. After that, the user authentication device 400 executes the process of step ST206.

[0077] In step ST206, 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 ST207.

[0078] In step ST207, 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 ST208.

[0079] In step ST208, 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 ST209.

[0080] In step ST209, 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 ST210.

[0081] In step ST210, 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 authority management system SYS ends the user authentication process in FIG.

[0082] Here, instead of the processes from step S203 to step S205, the user authentication device 400 may perform authentication in step ST206 based on the non-transferable token information (access right) acquired in step ST202.

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

[0084] FIG. 8 is a flowchart showing an example of a user authentication process in the user terminal device 100 according to this embodiment. In step S201, the user terminal device 100 transmits non-transferable token information to the user authentication device 400. Next, the user terminal device 100 executes the process of step S202.

[0085] 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.

[0086] 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.

[0087] 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.

[0088] 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 ends the user authentication process in FIG.

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

[0090] FIG. 9 is a flowchart showing an example of the user authentication process in the user authentication device 400 according to this embodiment. In step S301, the user authentication device 400 acquires non-transferable token information (access right) from the user terminal device 100. After that, the user authentication device 400 executes the process of step S302. In step S302, 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 S303.

[0091] In step S303, 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 S304.

[0092] In step S304, 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 S305.

[0093] In step S305, 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 S306.

[0094] In step S306, 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 S307.

[0095] In step S307, 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.

[0096] As such, the authority management system SYS of this embodiment includes a non-transferable token information acquisition unit that acquires non-transferable token information, an authentication request acquisition unit (user information acquisition unit 452) 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 453) 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 454) 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 455 that sets access rights in network services for the specific user based on the authentication that the user is a specific user.

[0097] In this way, the authority management 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 authority management system SYS allows the user to use the network service without newly registering the user. Therefore, when a user uses a network service, the authority management system SYS can improve the convenience of either or both the operator and the user of the network service.

[0098] In the authority management 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.

[0099] 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.

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

[0101] 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).

[0102] FIG. 10 is a flowchart showing an example of user authentication processing in the user authentication device 400 according to the modified example of this embodiment.

[0103] In step S401, the user authentication device 400 acquires non-transferable token information from the user terminal device 100. After that, the user authentication device 400 executes the process of step S402.

[0104] In step S402, 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 S403.

[0105] In step S403, 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 S404.

[0106] In step S404, 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 453 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 S404 YES), the user authentication device 400 ends the user authentication process in Fig. 10. On the other hand, if the user identification information included in the authentication request is not an authenticated user (step S404 NO), the user authentication device 400 executes the process of step S405.

[0107] In step S405, the user authentication device 400 transmits a specific login URL, which is a login site of the authority management system, to the user terminal device 100. After that, the user authentication device 400 executes the process of step S406.

[0108] In step S406, 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 S407.

[0109] In step S407, 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 S408.

[0110] In step S408, 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 S409.

[0111] In step S409, 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 S410.

[0112] In step S410, 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. 10.

[0113] In this way, the authority management system SYS related to the modified example of the first embodiment includes an authentication request acquisition unit (user information acquisition unit 452) 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 453) 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 454) 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 455 that sets access rights in network services for the specific user based on the authentication that the user is a specific user.

[0114] In this way, the authority management 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 authority management system SYS allows the user to use the network service without newly registering the user. Therefore, when a user uses a network service, the authority management system SYS can improve the convenience of either or both the operator and the user of the network service.

[0115] In the authority management 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.

[0116] 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.

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

[0118] In the third 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 third embodiment, the differences from the second embodiment will be mainly described, and the description of the second embodiment will be used for the rest of the description, and the description will be omitted.

[0119] FIG. 11 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 non-transferable token information acquisition unit 451, a user information acquisition unit 452, a non-fungible token information acquisition unit 453, an authentication unit 454, an access right setting unit 455, a notification unit 456, an association unit 457, a software wallet information acquisition unit 458, and a comparison determination unit 459.

[0120] When the user identification information is input from the user information acquisition unit 452, the non-fungible token information acquisition unit 453 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 453 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 453 outputs the non-fungible token information and the user identification information to the matching determination unit 459.

[0121] In addition, the non-fungible token information acquisition unit 453 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 458.

[0122] Based on the result of the determination by the comparison determination unit 459, the authentication unit 454 authenticates that the user is a specific user.

[0123] The associating unit 457 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.

[0124] The software wallet information acquisition unit 458 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 458 outputs the software wallet address to the non-fungible token information acquisition unit 453.

[0125] The matching determination unit 459 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 459 outputs the determination result to the access right setting unit 455.

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

[0127] FIG. 8 is a flowchart showing an example of a user authentication process in the user authentication device 400 according to this embodiment.

[0128] In step S501, the user authentication device 400 acquires non-transferable token information from the user terminal device 100. Next, the user authentication device 400 executes the process of step S502.

[0129] In step S502, 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 S503.

[0130] In step S503, 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 S504.

[0131] In step S504, 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 S505.

[0132] In step S505, user authentication device 400 acquires the software wallet address from user terminal device 100. Thereafter, user authentication device 400 executes the process of step S506.

[0133] In step S506, 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 S507.

[0134] In step S507, 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 S508.

[0135] In step S508, 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 S509.

[0136] In step S509, 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.

[0137] In this way, the authority management system SYS of this embodiment includes an authentication request acquisition unit (user information acquisition unit 452) 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 453) 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 454) 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 455 that sets access rights in network services for the specific user based on the authentication that the user is a specific user.

[0138] In this way, the authority management 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 authority management system SYS allows the user to use the network service without newly registering the user. Therefore, when a user uses a network service, the authority management system SYS can improve the convenience of either or both the operator and the user of the network service.

[0139] In the authority management 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.

[0140] 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.

[0141] In addition, in the above-mentioned authority management system SYS, there is provided a user identifier acquisition unit (user information acquisition unit 452) that acquires a user identifier of a specific user in a network service, an association unit 457 that associates the user identifier with the first non-fungible token information, a wallet address acquisition unit (software wallet information acquisition unit 458) that 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 The system further includes a second non-fungible token information acquisition unit (non-fungible token information acquisition unit 453) that acquires non-fungible token information, and a comparison determination unit 459 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 453) acquires the first non-fungible token information based on a user identifier, and the access right setting unit 455 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.

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

[0143] (Fourth embodiment) Next, a fourth embodiment will be described.

[0144] In the fourth 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.

[0145] FIG. 9 is a block diagram showing an example of a configuration of a user authentication device 400 according to the fourth 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 non-transferable token information acquisition unit 451, a user information acquisition unit 452, a non-fungible token information acquisition unit 453, an authentication unit 454, an access right setting unit 455, a notification unit 456, a first association unit 460, a second association unit 461, and a matching determination unit 459.

[0146] The user information acquisition unit 452 acquires user information. Specifically, the user information acquisition unit 452 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 452 outputs the user identification information to the non-fungible token information acquisition unit 453.

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

[0148] When the user identification information is input from the user information acquisition unit 452, the non-fungible token information acquisition unit 453 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 453 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 453 outputs the non-fungible token information and the user identification information to the matching determination unit 459.

[0149] In addition, the non-fungible token information acquisition unit 453 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.

[0150] Based on the result of the determination by the comparison determination unit 459, the authentication unit 454 authenticates that the user is a specific user.

[0151] 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.

[0152] 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.

[0153] The matching determination unit 459 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 459 outputs the determination result to the access right setting unit 455.

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

[0155] FIG. 14 is a flowchart showing an example of the user authentication process in the user authentication device 400 according to this embodiment. Here is an example.

[0156] In step S601, the user authentication device 400 acquires from the user terminal device 100 the authority granted by the authority management device 500. Next, the user authentication device 400 executes the process of step S602.

[0157] In step S602, 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 S603.

[0158] In step S603, 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 S604.

[0159] In step S604, 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 S605.

[0160] In step S605, 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 S606.

[0161] In step S606, the user authentication device 400 transmits a non-fungible token information acquisition request corresponding to the user name in the marketplace of non-fungible token information to the marketplace of non-fungible token information. In response to the non-fungible token information acquisition request, the user authentication device 400 acquires non-fungible token information corresponding to the user name in the marketplace of non-fungible token information from the marketplace of non-fungible token information. After that, the user authentication device 400 executes the process of step S607.

[0162] In step S607, 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 S608.

[0163] In step S608, 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 S609.

[0164] In step S609, 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.

[0165] In this way, the authority management system SYS of this embodiment includes an authentication request acquisition unit (user information acquisition unit 452) 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 453) 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 454) 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 455: that sets access rights in network services for the specific user based on the authentication that the user is a specific user.

[0166] In this way, the authority management 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 authority management system SYS allows the user to use the network service without newly registering the user. Therefore, when a user uses a network service, the authority management system SYS can improve the convenience of either or both the operator and the user of the network service.

[0167] In the authority management 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.

[0168] 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.

[0169] In addition, in the above-mentioned authority management system SYS, there is provided a user identifier acquisition unit (user information acquisition unit 452) 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 the first non-fungible token information, a username acquisition unit (user information acquisition unit 452) 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 requests the marketplace that manages the second non-fungible token information from the marketplace using the username. The network service 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 459 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 453) acquires the first non-fungible token information based on a user identifier, and the access right setting unit 455 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.

[0170] 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.

[0171] For example, the access right setting unit 455 may change the type of access right or the privilege to be granted depending on the type of non-transferable token information held by the user or the number of pieces of non-transferable token information held by the user. In this case, for example, the more non-transferable token information held by the user, the higher the access right to be granted or the more privileges to be granted than when the number of pieces of non-transferable token information held is small.

[0172] Also, for example, the authority management device 500 may display a list of non-transferable token information granted to a user on a user terminal. In this case, for example, the user can check multiple or multiple types of non-transferable token information, and can be granted access rights or benefits according to the multiple or multiple types of non-transferable token information.

[0173] Also, for example, the authority management device 500 may display a list of non-transferable token information granted to a user on a user terminal. In this case, the authority management device 500 can recommend new services or the like according to the non-transferable token information held by the user by acquiring multiple or multiple types of non-transferable token information from the user terminal device 100.

[0174] Also, for example, in the above-described embodiment, an example configured with the user authentication device 400 and the authority management device 500 has been described, but one aspect of the present invention may also be realized by multiple devices including the user authentication device 400 and other devices capable of realizing part of the authority management device 500.

[0175] In addition, the program that runs on the user authentication device 400 and the authority management device 500 in one aspect of the present invention may be a program that controls one or more processors such as a CPU (Central Processing Unit) so as to realize the functions shown in each of the above-mentioned embodiments and modified examples 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 a HDD (Hard Disk Drive), and may be read, modified, and written by the CPU or the like as necessary.

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

[0177] The "computer system" here refers to a computer system built into the authority management device 500, 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 a computer system.

[0178] 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.

[0179] In addition, a part or all of the right management device 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. In addition, each functional block of the right management device 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. The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit and / or a general-purpose processor. In addition, when an integrated circuit technology that replaces LSI appears due to the advancement of semiconductor technology, it is also possible to use an integrated circuit based on that technology.

[0180] 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]

[0181] 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 Non-transferable token information acquisition unit 452 User Information Acquisition Unit 453 Non-fungible token information acquisition unit 454 Authentication Department 455 Access rights setting section 456 Notification Department 457 Association section 458 Software Wallet Information Acquisition Department 459 Matching and Judging Unit 460 First Association Section 461 Second Association Section 500 Authority Management Device 51 Communications Department 52 Storage section 521 User Information 53 Input section 54 Output section 55 Control section 551 User Information Acquisition Unit 552 Issuance and Certification Department 553 Non-transferable Token Information Issuer 554 Access Rights Granting Department SYS Privilege Management System

Claims

1. A non-transferable token information issuing unit that issues non-transferable token information, which is predetermined non-transferable token information, to a user; an access right granting unit that grants an access right to the user based on the issuance of the non-transferable token information to the user; An authority management system comprising:

2. The access right granting unit grants the access right to the user according to the number of pieces of non-transferable token information held by the user. The rights management system according to claim 1 .

3. The non-transferable token information is a Soul Bound Token (SBT) or Verifiable Credentials (VC), The rights management system according to claim 1 .

4. The non-transferable token information issuing unit issues predetermined non-transferable token information based on the user's participation in or registration for participation in an event. The rights management system according to claim 1 .

5. The access right granting unit grants the access right to the user by displaying the non-transferable token information as a two-dimensional code. The rights management system according to claim 1 .

6. A non-transferable token information issuing unit that issues non-transferable token information, which is predetermined non-transferable token information, to a user; an access right granting unit that grants an access right to the user based on the issuance of the non-transferable token information to the user; An authority management device comprising:

7. A rights management method executed by a computer of a rights management device, comprising: a non-transferable token information issuing step of issuing non-transferable token information, which is predetermined non-transferable token information, to a user; an access right granting step of granting an access right to the user based on the issuance of the non-transferable token information to the user; The authority management method has the following features:

8. In the authority management device computer, a non-transferable token information issuing step of issuing non-transferable token information, which is predetermined non-transferable token information, to a user; an access right granting step of granting an access right to the user based on the issuance of the non-transferable token information to the user; A program for executing the above.

Images