User information SBT conversion device, system, control method and program for user information SBT conversion device

Abstract

We provide a user information SBT (Science-Based Technology) device that makes titles and other achievements acquired by users available for use on online services. [Solution] The user information SBT conversion device comprises an issuing means and a guarantee means. The issuing means issues an SBT corresponding to user information, with the user as the owner, based on user information relating to the status of a user receiving the first service, which is information generated by a first server that provides the first service. The guarantee means enables a second server that provides the second service to display a guarantee that the user owns the SBT.

Description

Technical Field

[0006] , ,

[0005] ,

[0001] The present invention relates to a user information SBT conversion device, a system, a control method for the user information SBT conversion device, and a program.

Background Art

[0002] There is a technology for issuing tokens related to devices used by users.

[0003] For example, Patent Document 1 describes providing an NFT issuance system that enables a user to easily grasp the content and approval status of an NFT while issuing an NFT containing information related to the usage result of a device used by the user. The NFT issuance system of Patent Document 1 includes an NFT issuance unit, a display data processing unit, and an approval status monitoring unit. The NFT issuance unit is connected to a user device used by a user and issues an NFT containing information related to the usage result of the user device on a blockchain. The display data processing unit generates display data containing information related to the usage result and provides it to the user device. The approval status monitoring unit monitors the approval status of the NFT on the blockchain. Further, the display data processing unit includes information indicating the approval status in the display data.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] When the level of a character or the like operated by a user in an online game or the like reaches a predetermined value, there are users who want to claim the reached level as a "title" in another online service such as a metaverse space. However, there is no system that realizes such a demand.

[0006] Furthermore, Patent Document 1 merely discloses a technology for issuing NFTs that include information regarding the usage results of equipment used by a user. Therefore, the above requirements cannot be met by applying the technology disclosed in Patent Document 1.

[0007] The primary objective of this invention is to provide a user information SBT conversion device, system, control method for the user information SBT conversion device, and program that contribute to making titles and other information acquired by users available for use on online services. [Means for solving the problem]

[0008] According to a first aspect of the present invention, a user information SBT conversion device is provided, comprising: an issuing means for issuing SBTs (SoulBound Tokens) corresponding to user information, based on user information relating to the status of a user receiving the first service, with the user as the owner; and a guarantee means for enabling a second server providing a second service to display a guarantee that the user owns the SBT.

[0009] A second aspect of the present invention provides a system comprising: a first server that provides a first service; a second server that provides a second service; and a user information SBT conversion device, wherein the user information SBT conversion device includes issuing means for issuing SBTs (SoulBound Tokens) corresponding to user information, based on user information relating to the status of a user receiving the first service, with the user as the owner; and assurance means for enabling the second server to display an indication that the user owns the SBTs.

[0010] A third aspect of the present invention provides a control method for a user information SBT conversion device, comprising: an issuance step of issuing an SBT (SoulBound Token) corresponding to user information based on user information relating to the status of a user receiving the first service, with the user as the owner; and a guarantee step of enabling a second server providing a second service to display a guarantee that the user owns the SBT.

[0011] A fourth aspect of the present invention is provided, which causes a computer mounted on a user information SBT conversion device to execute an issuance process that issues an SBT (SoulBound Token) corresponding to user information, with the user being the owner, based on user information generated by a first server that provides a first service, which concerns the status of a user receiving the first service; and a guarantee process that enables a second server that provides a second service to display a guarantee that the user owns the SBT. [Effects of the Invention]

[0012] According to each aspect of the present invention, a user information SBT conversion device, system, control method for the user information SBT conversion device, and program are provided that contribute to making titles and other information acquired by users available on online services. However, the effects of the present invention are not limited to those described above. The present invention may produce other effects in lieu of or in conjunction with the effects described above. [Brief explanation of the drawing]

[0013] [Figure 1] Figure 1 is a diagram illustrating the outline of one embodiment. [Figure 2] Figure 2 is a flowchart showing the operation of one embodiment. [Figure 3] Figure 3 shows an example of a schematic configuration of an information processing system according to the embodiment of this disclosure. [Figure 4] FIG. 4 is a diagram for explaining the operation of the information processing system according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a diagram for explaining the operation of the information processing system according to an embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram showing an example of the processing configuration of the service server according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram showing an example of the user management database according to an embodiment of the present disclosure. [Figure 8] FIG. 8 is a diagram showing an example of the display of the terminal according to an embodiment of the present disclosure. [Figure 9] FIG. 9 is a diagram showing an example of the display of the terminal according to an embodiment of the present disclosure. [Figure 10] FIG. 10 is a diagram showing an example of the display of the terminal according to an embodiment of the present disclosure. [Figure 11] FIG. 11 is a diagram showing an example of the processing configuration of the token management server according to an embodiment of the present disclosure. [Figure 12] FIG. 12 is a flowchart showing an example of the operation of the SBT control unit according to an embodiment of the present disclosure. [Figure 13] FIG. 13 is a diagram showing an example of the display of the terminal according to an embodiment of the present disclosure. [Figure 14] FIG. 14 is a diagram showing an example of the display of the terminal according to an embodiment of the present disclosure. [Figure 15] FIG. 15 is a diagram showing an example of the display of the terminal according to an embodiment of the present disclosure. [Figure 16] FIG. 16 is a diagram showing an example of the display of the terminal according to an embodiment of the present disclosure. [Figure 17] FIG. 17 is a diagram showing an example of the display of the terminal according to an embodiment of the present disclosure. [Figure 18] FIG. 18 is a diagram showing an example of the display of the terminal according to an embodiment of the present disclosure. [Figure 19] FIG. 19 is a sequence diagram showing an example of the operation of the information processing system according to an embodiment of the present disclosure. [Figure 20]Figure 20 shows an example of a terminal display according to a modified embodiment of the present disclosure. [Figure 21] Figure 21 shows an example of the hardware configuration of the token management server related to this disclosure. [Modes for carrying out the invention]

[0014] First, an overview of one embodiment will be described. The reference numerals in the drawings attached to this overview are provided for convenience as examples to aid understanding, and this overview is not intended to be limiting in any way. Furthermore, unless otherwise specified, the blocks shown in each drawing represent functional units, not hardware units. The connecting lines between blocks in each drawing include both bidirectional and unidirectional lines. Unidirectional arrows schematically indicate the flow of the main signal (data) and do not exclude bidirectional flow. In this specification and in the drawings, elements that can be similarly described are given the same reference numerals to avoid redundant explanation.

[0015] A user information SBT conversion device 100 according to one embodiment comprises an issuing means 101 and a guarantee means 102 (see Figure 1). The issuing means 101 issues an SBT corresponding to user information, with the user as the owner, based on user information relating to the status of a user receiving the first service, which is information generated by a first server providing the first service (step S1 in Figure 2). The guarantee means 102 enables a second server providing the second service to display a guarantee that the user owns the SBT (step S2).

[0016] The User Information SBT Conversion Device 100 issues SBTs based on user information generated when a user receives the first service. For example, the User Information SBT Conversion Device 100 issues SBTs corresponding to titles acquired by the user in an online game. Furthermore, the User Information SBT Conversion Device 100 enables the second server providing the second service to display a notification guaranteeing that the user possesses SBTs. For example, the User Information SBT Conversion Device 100 transmits the SBTs issued to the user to the second server. The second server displays the titles acquired by the user in the online game in a way that other users receiving the second service can recognize. In other words, the user can use the acquired titles, etc., on the online service.

[0017] Specific embodiments will be described in more detail below with reference to the drawings.

[0018] [First Embodiment] The first embodiment will be described in more detail with reference to the drawings.

[0019] The information processing system according to the first embodiment issues SBT (SoulBound Token) which certifies titles, qualifications, etc., acquired by users in the virtual world and the real world. Users who receive SBT can use those titles, etc., in the virtual world. SBT is a token that is set to be non-resaleable and cannot be moved between wallets.

[0020] For example, when a user reaches a predetermined level (the level of their in-game character) by playing an online game, an SBT (Skill Battle Tome) is issued to certify that they have reached that predetermined level. Users who receive an SBT can identify themselves as players who have reached the predetermined level in the metaverse space. For example, a display such as "GameA:Lev10" will appear near the user's avatar. This display is expected to make communication in the metaverse space smoother and more active.

[0021] [System Configuration] As shown in Figure 3, the information processing system according to the first embodiment includes a token management server 10 and a plurality of service servers 20-1 to 20-4.

[0022] In the following explanation, unless there is a particular reason to distinguish between service servers 20-1 to 20-4, they will simply be referred to as "service server 20".

[0023] Users possess a device 30 such as a smartphone or HMD (Head Mounted Display). Users access various servers, etc., by operating the device 30.

[0024] The token management server 10 is a server managed and operated by a business operator (token management platform provider) that issues tokens such as NFTs (Non-Fungible Tokens) and SBTs. The token management server 10 issues SBTs that prove titles and other achievements acquired by users. The token management server 10 manages the SBTs issued to users. The token management server 10 is a user information SBT conversion device.

[0025] Furthermore, the token management server 10 implements a so-called marketplace. The token management server 10 facilitates the buying and selling of NFT-enabled digital content (digital assets) through the marketplace.

[0026] Service server 20 is a server managed and operated by a service provider that provides various online services to users.

[0027] For example, service server 20-1 is a game server that provides online games. Service server 20-1 controls the progress of the game. The games targeted by the information processing system according to the first embodiment include 3D games, FPS (First Person Shooter), action games, fighting games, RPG (Role Playing Game), etc.

[0028] For example, service server 20-2 is a video sharing server that provides video sharing services. Service server 20-2 provides a service where individuals, companies, etc., can upload videos, and users can view those uploaded videos. Service server 20-2 also provides functions such as allowing viewers to leave comments on videos and allowing video uploaders and viewers to chat.

[0029] For example, service server 20-3 is a video streaming server that provides video streaming services. Service server 20-3 streams programs such as anime, dramas, and movies.

[0030] For example, service server 20-4 is a metaverse server that provides a virtual space to users. Service server 20-4 is a virtual space control device that controls the virtual space. Users access service server 20-4 using an HMD or similar device and engage in activities within the metaverse space provided by service server 20-4.

[0031] The online services provided by the service server 20 described above are examples. The service server 20 may also provide SNS (Social Networking Service) services, EC (Electronic Commerce) services, etc.

[0032] Although not shown in Figure 3, the information processing system includes a wallet server that provides wallet services for tokens such as NFTs and SBTs. Users can prove ownership of NFTs and SBTs by opening an account (wallet) on the wallet server.

[0033] Each device shown in Figure 3 is connected to a network. Specifically, the token management server 10, the service server 20, and the terminal 30 are connected to the network by wired or wireless communication means.

[0034] The configuration of the information processing system shown in Figure 3 is illustrative and not intended to limit the possible configurations. For example, the system may include multiple token management servers 10. Load balancing and redundancy may be achieved by using multiple token management servers 10.

[0035] [General operation] Next, we will describe the general operation of the information processing system according to the first embodiment.

[0036] <Create an account> Users create accounts with each service provider to play online games, participate in the metaverse space, use marketplaces, and enjoy services such as wallets.

[0037] Specifically, the user operates terminal 30 to access the wallet server and create an account (wallet). The user operates terminal 30 to create an account on the game server of the game they want to play. The user operates terminal 30 to create an account (marketplace account) on the token management server 10.

[0038] <Account Linking> Users configure the token management server 10 with login information for each of the service servers 20. For example, a user configures the token management server 10 with login information (ID, password) for logging into service server 20-1 (game server) and service server 20-4 (metaverse server).

[0039] Furthermore, users configure their wallet address (a wallet address generated by the wallet server) on the token management server 10 and each service server 20.

[0040] The token management server 10 stores the user's login information (ID, password), wallet address, and login information corresponding to each service server 20, associating them with each other. Each service server 20 stores the login information and wallet address of its own service, associating them with each other.

[0041] <Accumulation of user information> When the service server 20 provides a service to a user, it stores information about that user (particularly information about the user's status) as user information. The service server 20 stores user information in the account of the logged-in user. The user information stored by the service server 20 varies depending on the service provided to the user.

[0042] For example, a service server 20-1 that provides an online game stores user information such as items acquired by the user in the game, levels reached, and events completed. The service server 20-1 also stores the game's play history.

[0043] Alternatively, the service server 20-2 providing the video sharing service stores user information such as comments left by users, amounts of donations, and purchased goods, categorized by the distributor's agency or the distributor themselves. For example, the service server 20-2 stores the amount of donations a user has made to a distributor (including virtual distributors who stream using avatars) and the fact that they have purchased goods from that distributor (purchased items, amount) in the user's account. Alternatively, the service server 20-2 stores points earned by users by charging distributors as user information.

[0044] Alternatively, the service server 20-3 providing the video streaming service stores information about the programs the user has watched (e.g., program name, viewing time, etc.) as user information. For example, if a user watches up to episode 10 of anime program A, which consists of 20 episodes, the service server 20-3 stores information such as "Anime program A: Episode 10 watched" in the user's account as user information.

[0045] Alternatively, the service server 20-4 that provides the metaverse space stores the actions of the user in the metaverse space as user information. For example, when the user holds an event in the metaverse space, the service server 20-4 stores the fact of the event in the user's account as user information.

[0046] <Issuance of SBT> As described above, the token management server 10 stores the login information of the online services used by the user. The token management server 10 accesses the service server 20 at regular or predetermined timings, and logs in to the user's account using the stored login information (step S01 in FIG. 4).

[0047] The token management server 10 acquires the user information stored in the logged-in account (step S02).

[0048] The token management server 10 determines whether it is possible to assign a "title" to the user using the acquired user information. For example, the token management server 10 refers to the table information storing the titles prepared for each online service and the conditions for acquiring the titles, and determines whether the title can be assigned.

[0049] For example, regarding online game A, when the user acquires a rare item B, the token management server 10 determines that it is possible to assign a title such as "Game A: Acquisition of Item B" to the user.

[0050] ' Alternatively, regarding the video sharing service, when the amount of money the user donates to the streamer A exceeds a predetermined amount, the token management server 10 determines that it is possible to assign a title such as "Streamer A: Donation of 10,000 yen" to the user.

[0051] Alternatively, regarding the video distribution service, when the user watches all episodes of the anime program A, the token management server 10 determines that it is possible to assign a title such as "Anime Program A: Watching All Episodes" to the user.

[0052] Alternatively, if a user hosts an event B for ramen lovers in metaverse space A, the token management server 10 determines that it can grant the user a title such as "Metaverse Space A: Ramen Event B Hosted".

[0053] If the token management server 10 determines that a title can be assigned to a user based on the user information, it obtains whether the user wishes to receive SBTs corresponding to the assignable title. In other words, the token management server 10 obtains whether the user wishes to use the acquired title online.

[0054] For example, when a user who has logged into the marketplace performs a predetermined action (for example, pressing the title acquisition button), the token management server 10 determines whether the title can be awarded, and if there is an awardable title, it obtains whether the user wishes to receive SBT for that title. Alternatively, the token management server 10 determines whether the title can be awarded when the user logs into their account, and if there is an awardable title, it obtains whether the user wishes to receive SBT for that title.

[0055] When a user requests the issuance of an SBT, the token management server 10 issues an SBT for the title the user wishes to use online (step S03).

[0056] In this case, the token management platform provider's representatives generate a smart contract to issue SBTs for the titles earned by the users, and then deploy the generated smart contract to the blockchain.

[0057] When the token management server 10 needs to issue SBT, it calls a function in the smart contract and inputs the information required to issue SBT (wallet address, information about acquired titles, ID of the token management platform provider, etc.).

[0058] When the smart contract is executed, the user's wallet (wallet address) is associated with the SBT (Social Battle Points) related to the title the user has earned. The user is then issued SBT corresponding to the title they have earned.

[0059] Users can check the SBTs they own in their account on the token management server 10. Users can check the SBTs and NFTs they own by logging into their account on the token management server 10.

[0060] <Use of titles> Users who receive BT corresponding to the title they have acquired can use that acquired title in online services. For example, a user can use a title acquired by playing an online game in the metaverse space. For instance, a user who has acquired the title "Game A: Item B acquired" can declare that fact in the metaverse space.

[0061] For example, in the metaverse space, a user who wishes to use an online game title logs in to the metaverse server (service server 20-4) (step S11 in Figure 5). The user instructs the logged-in service server 20-4 to obtain SBT. In response to this instruction, the service server 20-4 sends an SBT provision request, including the user's wallet address, to the token management server 10 (step S12).

[0062] The token management server 10 accesses the user's wallet using the wallet address included in the SBT provision request and obtains each SBT owned by the user (steps S13, S14).

[0063] The token management server 10 sends at least one SBT it has obtained to the service server 20-4 (step S15). Specifically, the token management server 10 sends an acknowledgment (response to the SBT provision request) containing at least one SBT to the service server 20-4.

[0064] When an SBT is acquired, the service server 20-4 displays a list of information about the acquired SBT on the terminal 30 and allows the user to select a title. For example, the service server 20-4 displays a list of SBTs owned by the user on the terminal 30.

[0065] Subsequently, the service server 20-4 uses the title selected by the user in the metaverse space in a format that allows others to recognize that title. For example, the service server 20-4 displays the acquired title near the user's avatar.

[0066] Next, we will describe the details of each device included in the information processing system according to the first embodiment.

[0067] [Service Server] Figure 6 shows an example of the processing configuration (processing module) of the service server 20 according to the embodiment disclosed herein. Referring to Figure 6, the service server 20 comprises a communication control unit 201, a user management unit 202, a function control unit 203, and a storage unit 204.

[0068] The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from terminal 30. The communication control unit 201 also transmits data to terminal 30. The communication control unit 201 passes data received from other devices to other processing modules. The communication control unit 201 transmits data acquired from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 201. The communication control unit 201 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.

[0069] The user management unit 202 is a means of controlling and managing users.

[0070] The User Management Unit 202 obtains information such as name, gender, date of birth, and login information (ID, password) from users who access a designated website (for example, a user registration site). Furthermore, the User Management Unit 202 obtains the user's wallet address.

[0071] The user management unit 202 stores the acquired name, login information, wallet address, etc., in the user management database (see Figure 7). The user management unit 202 stores the user's name, wallet address, login information, etc., in association with user information for each user's account. Note that the user management database shown in Figure 7 is an example and is not intended to limit the items to be stored. For example, the user management database may also store the user's biometric information (e.g., facial image).

[0072] User Management Unit 202 authenticates users who access designated websites, etc., in order to receive services. User Management Unit 202 authenticates such users using login information.

[0073] The function control unit 203 is a means for controlling the functions assigned to each service server 20.

[0074] The function control unit 203 stores user information generated by providing services to the user in the user's account.

[0075] Furthermore, the function control unit 203 acquires SBTs owned by the user in response to instructions from the user. For example, when the function control unit 203 detects a predetermined action by the user (e.g., pressing the SBT acquisition button), it sends an SBT provision request, including the user's wallet address, to the token management server 10.

[0076] The function control unit 203 receives a response to the SBT provision request from the token management server 10.

[0077] Upon receiving a negative response indicating that SBT is unavailable, the function control unit 203 notifies the user that there are no SBTs available or that SBT acquisition failed.

[0078] Upon receiving an acknowledgment indicating that an SBT is available, the function control unit 203 retrieves at least one SBT from the acknowledgment that the user wishes to use (declare their title) in the online service.

[0079] For example, the function control unit 203 identifies the SBT that the user wishes to use using a GUI as shown in Figure 8. Alternatively, as shown in Figure 8, the function control unit 203 may identify the SBT that the user wishes to use while displaying information obtained from each acquired SBT (such as the name of the title acquired by the user).

[0080] The function control unit 203 uses the identified SBT (SBT-certified designation) in the online service.

[0081] For example, the function control unit 203 of the game server (service server 20-1) displays the titles earned by the user near the player controlled by the user. Alternatively, the video sharing server (service server 20-2) or video distribution server (service server 20-3) displays the titles earned in its own account.

[0082] Alternatively, the metaverse server (service server 20-4) displays a title near the user's avatar. For example, as shown in Figure 9, the function control unit 203 displays a title corresponding to the SBT selected by the user near the user's avatar. Other users who come into contact with this title can start a conversation about Game A with the user (the user using the title).

[0083] Furthermore, the function control unit 203 implements the unique functions assigned to each service server 20.

[0084] The following describes the typical functions implemented by service servers 20-1 to 20-4, which correspond to game servers, video sharing servers, video streaming servers, and metaverse servers, respectively.

[0085] <Game Server> The function control unit 203 of the service server 20-1 controls the progress of the online game. As the game progresses, the function control unit 203 stores information such as the level reached and items acquired by the user as user information in the account.

[0086] <Video sharing server> The function control unit 203 of the service server 20-2 provides a video sharing service. The function control unit 203 stores information such as comments made by users to broadcasters and the amount of donations as user information in the account. Furthermore, if a user purchases merchandise from a broadcaster, the function control unit 203 also stores that fact as user information in the account.

[0087] Furthermore, the function control unit 203 may award points for actions taken by users towards streamers (especially for paid services). For example, the function control unit 203 may award users "support points" based on the amount of tips or the amount of goods purchased. Alternatively, the function control unit 203 may award support points to users when they purchase NFTs (such as illustrations of the streamer), invite friends, or answer surveys.

[0088] In this case, the function control unit 203 may set weights for the user's actions. For example, the function control unit 203 may set the largest weight for NFT purchases.

[0089] The number of support points earned may be stored in the user's account as user information. Support points are tallied and accumulated for each broadcaster and for each designated period (season).

[0090] The function control unit 203 may display the support points earned by each user for each broadcaster in a ranking format or the like. For example, when a user performs a predetermined action (for example, pressing the support ranking display button) on a broadcaster's page, the function control unit 203 displays a screen like the one shown in Figure 10 on the terminal 30.

[0091] As shown in Figure 10, the function control unit 203 displays the streamer's photo or avatar in the icon display area 41. Furthermore, the function control unit 203 displays the number of support points each user has earned and their ranking according to those support points.

[0092] Furthermore, the function control unit 203 displays the username and the number of support points earned for users with high support points. In this case, the function control unit 203 may also display the title the user has earned near the username. In Figure 10, "B-oshi Gold: Season 1" and other text displayed next to the username correspond to the user's title.

[0093] <Video streaming server> The function control unit 203 of the service server 20-3 streams the program selected by the user. The function control unit 203 stores information about the program the user has watched (e.g., program name, viewing time, etc.) as user information.

[0094] <Metaverse Server> The function control unit 203 of the service server 20-4 enables user actions in the metaverse space. The function control unit 203 stores predetermined user actions in the metaverse space as user information.

[0095] Here, the function control unit 203 may, instead of or in addition to displaying the title acquired by the user near the avatar, represent the title acquired by the user in another form. For example, the function control unit 203 may display an accessory corresponding to the title (an accessory worn by the avatar), or it may display the title in a status display.

[0096] Alternatively, the function control unit 203 may indicate that the titles, etc., acquired by the user are officially recognized by the service provider or IP (Intellectual Property) holder. The function control unit 203 may also indicate that the titles acquired by the user are officially recognized in a format that is visible to others. For example, the function control unit 203 may indicate that unauthorized accessories (counterfeit similar accessories) are distinguishable from legitimate accessories.

[0097] The memory unit 204 is a means for storing information necessary for the operation of the service server 20.

[0098] [Token Management Server] Figure 11 is a diagram showing an example of the processing configuration (processing module) of the token management server 10 according to the embodiment disclosed herein. Referring to Figure 11, the token management server 10 comprises a communication control unit 301, a user management unit 302, an SBT control unit 303, a My Page control unit 304, and a storage unit 305.

[0099] The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from terminal 30. The communication control unit 301 also transmits data to terminal 30. The communication control unit 301 passes data received from other devices to other processing modules. The communication control unit 301 transmits data acquired from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 301. The communication control unit 301 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.

[0100] The user management unit 302 is a means of controlling and managing users.

[0101] The user management unit 302 obtains information such as name, gender, date of birth, and login information (ID, password) from users who access a designated website (for example, a user registration site). Furthermore, the user management unit 302 obtains the user's wallet address and login information for logging into each service server 20 where the user created an account.

[0102] The user management unit 302 stores the acquired name, login information, wallet address, login information for each service server 20, etc., in a predetermined database. The user management unit 302 stores the login information etc. using a database similar to the user management database shown in Figure 7.

[0103] The SBT control unit 303 is a means for executing control related to the SBT assigned to the user.

[0104] The SBT control unit 303 has functions as both an issuing means and a guarantee means.

[0105] The issuing means issues SBTs corresponding to user information, with the user as the owner, based on user information relating to the status of the user receiving the first service, which is information generated by the first server providing the first service. The assurance means enables the second server providing the second service to make an indication that the user owns the SBTs. More specifically, the assurance means transmits the SBTs owned by the user to the second server in response to a request from the second server.

[0106] The first server is, for example, a game server or a video sharing server. The second server is, for example, a metaverse server. However, the first and second servers are not limited to these examples. The SBT issued by the guarantee means certifies that the user possesses the titles, etc., acquired by the user through the provision of the first service.

[0107] Furthermore, by having the SBT owned by the user sent to the second server, the second server can display a statement guaranteeing that the SBT is authorized by the service provider that provides the first service.

[0108] The first service provided by the first server includes at least one of the following: online game services, video sharing services, video streaming services, and metaverse services. The second service provided by the second server includes metaverse services.

[0109] Figure 12 is a flowchart illustrating an example of the operation of the SBT control unit 303 according to the embodiment disclosed herein. The operation of the SBT control unit 303 will be explained with reference to Figure 12.

[0110] The SBT control unit 303 obtains the user's user information (step S101). For example, the SBT control unit 303 obtains the latest user information stored in the account of the online service used by the user.

[0111] Specifically, the SBT control unit 303 accesses the service server 20, where the user's login information is registered, periodically or at predetermined intervals. For example, the SBT control unit 303 accesses the service server 20 when a user logs into their account (the account on the token management server 10). Alternatively, the SBT control unit 303 may access the service server 20 in response to instructions from the user who has logged into their account.

[0112] For example, if the user's account contains accounts for both a game server and a video sharing server, the SBT control unit 303 will access each of these servers (service server 20-1, service server 20-2). The SBT control unit 303 will log in to the game server, etc., using the login information corresponding to the game server, etc.

[0113] The SBT control unit 303 retrieves user information from the account of the logged-in service server 20.

[0114] For example, the SBT control unit 303 obtains the user's game play history from the service server 20-1 that provides the online game. For example, the SBT control unit 303 obtains information such as items acquired by the user in the game, levels reached, and events completed (play history) as user information.

[0115] Similarly, the SBT control unit 303 acquires user information from video sharing servers, video distribution servers, metaverse servers, etc.

[0116] Upon obtaining user information, the SBT control unit 303 determines whether or not a specific title can be assigned to the user (title assignment determination process; step S102).

[0117] For example, the SBT control unit 303 refers to table information that stores titles prepared for each online service and the conditions for obtaining those titles, and determines whether or not it is possible to assign the title.

[0118] If a title cannot be assigned to the user (step S103, No branch), the SBT control unit 303 terminates the process.

[0119] If a title can be assigned to a user (step S103, Yes branch), the SBT control unit 303 obtains whether the user wishes to have an SBT issued for that assignable title (step S104). For example, the SBT control unit 303 obtains whether the user wishes to have an SBT issued by displaying a GUI (Graphical User Interface) as shown in Figure 13 on the terminal 30.

[0120] If the user does not wish to issue an SBT (Step S105, No branch), the SBT control unit 303 terminates the process.

[0121] If a user wishes to be issued an SBT (Step S105, Yes branch), the SBT control unit 303 issues an SBT for the title that the user wishes to use online (Step S106).

[0122] Specifically, the SBT control unit 303 calls a function of a smart contract deployed on a node on the blockchain and issues SBT corresponding to the title acquired by the user.

[0123] For example, the SBT control unit 303 inputs the wallet address as the address of the SBT recipient and the wallet address of the token management platform provider as the ID of the SBT issuer into the smart contract. Furthermore, the SBT control unit 303 inputs information about the title acquired by the user, such as the name of the online service and the specific details of the title, into the smart contract. Alternatively, when issuing SBT related to a video sharing service, the SBT control unit 303 inputs information about the broadcaster and the agency to which the broadcaster belongs into the smart contract.

[0124] The smart contract uses this information to issue SBTs where the title holder is the owner and the token management platform provider is the issuer, and SBTs containing metadata about the titles granted to users.

[0125] The SBT control unit 303 repeats the process shown in Figure 12 for each service provider (service server 20) with linked accounts.

[0126] Furthermore, since the issuance of SBTs using smart contracts is contrary to the intent of this disclosure, a more detailed explanation will be omitted.

[0127] Furthermore, the SBT control unit 303 processes SBT provision requests received from the service server 20. Upon receiving an SBT provision request, the SBT control unit 303 accesses the user's wallet using the wallet address included in the request and obtains each SBT owned by the user.

[0128] When at least one SBT is obtained, the SBT control unit 303 sends an acknowledgment to the service server 20 indicating that SBTs are available. At that time, the SBT control unit 303 sends an acknowledgment to the service server 20 that includes at least one obtained SBT.

[0129] If at least one SBT cannot be obtained, the SBT control unit 303 sends a negative response to the service server 20 indicating that SBT cannot be provided.

[0130] The My Page Control Unit 304 is a means for controlling the user's account (My Page). The My Page Control Unit 304 has a function to display information about NFTs and SBTs owned by the user. The My Page Control Unit 304 has a function as a display means for displaying at least one SBT owned by the user.

[0131] When a user logs into the marketplace, the My Page control unit 304 displays a My Page on the terminal 30 as shown in Figure 14.

[0132] As shown in Figure 14, the My Page control unit 304 displays the owned NFT button 43 and owned SBT button 45 on the My Page.

[0133] When the Owned NFT button 43 is pressed (activated), the My Page control unit 304 displays a list of NFTs owned by the user in the list display area 47. Similarly, when the Owned SBT button 45 is pressed, the list of SBTs owned by the user is displayed in the list display area 47.

[0134] An example of how the My Page will appear when the owned SBT button 45 is pressed will be shown later.

[0135] To enable the display of a list of NFTs and SBTs, the My Page Control Unit 304 accesses the user's wallet and retrieves the NFTs and SBTs owned by that user. The timing of when the My Page Control Unit 304 retrieves the NFTs and SBTs may be when the user logs in or when the Owned NFT button 43 or Owned SBT button 45 is pressed.

[0136] When the account linking button 49 shown in Figure 14 is pressed, the My Page control unit 304 displays a list of service providers (online services) to which the user has linked their account. For example, if the user has registered accounts for a game server, a video sharing server, and a metaverse server on the marketplace, the My Page control unit 304 will display a list of the service names, etc., corresponding to these servers.

[0137] In addition to the owned NFT button 43, the My Page control unit 304 may also display a support points button 51, a showcase button 53, an NFT selfie button 55, etc., on the My Page. The operation of the My Page control unit 304 when these buttons are pressed will be described later.

[0138] When the settings button 57 shown in Figure 14 is pressed, the My Page control unit 304 enables various settings related to My Page and registration of login information for linked accounts.

[0139] Furthermore, the My Page control unit 304 displays the user's icon in the icon display area 59 of the My Page. The My Page control unit 304 may change the icons displayed in the icon display area 59 by changing the settings. For example, the My Page control unit 304 may display an image (digital art) corresponding to an NFT owned by the user as an icon in the icon display area 59.

[0140] The My Page control unit 304 may display a market button 61 on the My Page for participating in the marketplace.

[0141] The My Page control unit 304 may display the titles acquired by the user (titles for which SBT has been issued) on the My Page. For example, as shown in Figure 14, the My Page control unit 304 may display the titles for which SBT has been issued in the title display area 63. The titles displayed in the title display area 63 may be specified by the user on the settings page or the like, which is accessed when the settings button 57 is pressed.

[0142] Alternatively, the My Page control unit 304 may calculate the total transaction amount of the NFTs owned by the user (for example, the amount the user pays when purchasing NFTs) and display it on the My Page. For example, the My Page control unit 304 may display the calculated total amount in the NFT total amount display field 65, as shown in Figure 14.

[0143] The My Page control unit 304 may display buttons on the My Page that correspond to functions related to SNS (Social Networking Service).

[0144] For example, the My Page control unit 304 may display a follow button 67 on the My Page to display a list of other users that the user is following. Alternatively, the My Page control unit 304 may display a follower button 69 on the My Page to display a list of other users (followers) that are following the user. Alternatively, the My Page control unit 304 may display a timeline button 71 on the My Page to display the timeline.

[0145] Furthermore, if the account information of the SNS server providing the SNS service is registered with the token management server 10, the My Page control unit 304 may display SNS-related function buttons on the My Page. In addition, the My Page control unit 304 can log in to the user's SNS account using the SNS server's login information and obtain user information (such as follower IDs) from that account.

[0146] The My Page control unit 304 may provide an interface for sorting NFTs and SBTs displayed in the list display area 47, and for setting their display and hiding.

[0147] For example, the My Page control unit 304 may sort the NFTs and SBTs owned by the user according to the settings in the sorting box 73 displayed in the list display area 47. For example, the My Page control unit 304 may sort by the acquisition price of the NFTs, by the name of the NFT or SBT, or by the date and time of acquisition of the NFT or SBT, according to the settings.

[0148] Alternatively, the My Page control unit 304 may switch the display of NFTs and SBTs owned by the user on or off according to the setting value of the filter box 75 for selecting (filtering) the NFTs and SBTs to be displayed in the list display area 47.

[0149] The My Page control unit 304 may display tags set on NFTs and SBTs. For example, the My Page control unit 304 may display tags (hashtags) for NFTs listed on the My Page (NFTs displayed in the list display area 47).

[0150] Tags may be assigned by the user. Alternatively, the My Page control unit 304 may extract (calculate) tags from information such as that contained in the NFT's metadata.

[0151] For example, as shown in Figure 14, when the My Page control unit 304 detects a predetermined action performed by the user on an NFT on the My Page (e.g., clicking on the NFT or moving the mouse over it), it displays the NFT's tag in the popup 77. Alternatively, the NFT's tag may be displayed below the corresponding NFT.

[0152] Next, we will explain the operation of the My Page control unit 304 when the owned SBT button 45 is pressed.

[0153] When the Owned SBT button 45 is pressed, the My Page control unit 304 displays a list of SBTs owned by the user (a list of titles guaranteed by SBT) in the list display area 47 (see Figure 15).

[0154] In this case, the My Page Control Unit 304 may display a list of SBTs (titles) categorized by the information that formed the basis for the SBT issuance, as shown in Figure 15.

[0155] For example, the My Page Control Unit 304 may display SBT (titles) for each streaming service to which the user belongs when making a payment on the video sharing service. For example, Figure 15 shows titles A1 to A3 that the user has earned by making a payment for streaming B, who belongs to agency A. For example, title A1 is "Streamer B's Top 500 Season 1". Title A2 is "Participated in Streamer B's 3rd Anniversary Live". Title A3 is "Purchased Streamer B's 3rd Anniversary Live Goods".

[0156] Alternatively, the My Page Control Unit 304 may display SBT for each game played by the user. For example, Figure 15 shows titles B1 and B2 earned by the user playing game B. For example, title B1 is a title such as "SS Rank Achieved". Title B2 is a title such as "Logged in for 150 days".

[0157] Alternatively, the My Page Control Unit 304 may display SBT for each video streaming service used by the user. For example, Figure 15 shows the title C1 that the user earned by watching a program on streaming service C. For example, title C1 is a title that says "Watched all episodes of anime program C season 1".

[0158] Next, we will explain the operation of the My Page control unit 304 when the support points button 51, the showcase button 53, or the NFT selfie button 55 is pressed.

[0159] When the support points button 51 is pressed, the My Page control unit 304 displays information about the support points earned by the user on the video sharing service (see Figure 16). At that time, the My Page control unit 304 may also display support points for each agency and streamer. In the example in Figure 16, agencies are labeled as "Oshi-bako" and streamers as "Oshi-chara".

[0160] The My Page Control Unit 304 displays the total number of support points for streamers belonging to each agency in the Favorite Box Field 79. When a user selects an agency from those displayed in the Favorite Box Field 79, the My Page Control Unit 304 displays the support points (breakdown of total support points) for each streamer belonging to the selected agency in the Favorite Character Field 81.

[0161] In the example in Figure 16, agency A is selected by the user, and the support points earned by the user for each of the streamers B through D belonging to agency A are displayed.

[0162] When the showcase button 53 is pressed, the My Page control unit 304 enables the user to configure the system to display content corresponding to NFTs they possess (for example, image data or 3D models of characters) in a virtual showcase. For example, when the showcase button 53 is pressed, the My Page control unit 304 provides an interface as shown in Figure 17.

[0163] Figure 17 displays a list of NFTs (and their corresponding content) owned by the user, along with a simulated showcase 83. In Figure 17, when the user selects an NFT from the list and drags and drops it to any rectangular prism in the simulated showcase 83, the content corresponding to the selected NFT is placed in the dropped rectangular prism. In the example in Figure 17, the character corresponding to NFT4 is placed in the upper left rectangular prism of the simulated showcase 83.

[0164] The pseudo-showcase 83, in which the digital content (characters) is placed, may also be displayed on the user's My Page (see Figure 18).

[0165] When the NFT selfie button 55 is pressed, the My Page control unit 304 enables the overlaying of the user's NFT (NFT-compatible content) onto the user's selfie image. By overlaying the digital content (digital art) corresponding to the NFT selected by the user onto the user's selfie image, the My Page control unit 304 generates image data that makes it appear as if the user and the digital content (for example, a character) are in the picture together.

[0166] The memory unit 305 is a means for storing information necessary for the operation of the token management server 10.

[0167] The token management server 10 provides a marketplace for users to buy and sell NFTs of digital content (digital assets). A description of the processing module related to this marketplace is omitted.

[0168] [Terminal] Examples of terminal 30 include mobile devices such as smartphones, HMDs, mobile phones, game consoles, and tablets, as well as computers (personal computers, laptops). Terminal 30 can be any device that can receive user input and communicate with the token management server 10, etc. Furthermore, the configuration of terminal 30 is obvious to those skilled in the art, so a detailed explanation is omitted.

[0169] [System operation] Next, the operation of the information processing system according to the first embodiment will be described.

[0170] Figure 19 is a sequence diagram showing an example of the operation of the information processing system according to the embodiment disclosed herein. The operation of the information processing system according to the first embodiment will be described with reference to Figure 19.

[0171] The service server 20 sends an SBT provision request to the token management server 10 in response to instructions from the user (step S21).

[0172] The token management server 10 accesses the user's wallet and obtains SBT (step S22).

[0173] The token management server 10 sends the acquired SBT to the service server 20 (step S23).

[0174] The service server 20 uses the acquired SBT in the online service (step S24). For example, the metaverse server displays the title corresponding to the acquired SBT along with the user's avatar.

[0175] Next, a modified example of the first embodiment will be described.

[0176] <Example 1> In the above embodiment, it was explained that users can use the titles they have acquired in online services. However, users may also use online services to use the qualifications or achievements they possess. For example, SBTs may be issued for real-world qualifications such as doctor or lawyer, or for achievements such as attending a soccer class, and users may declare their possession of such qualifications or achievements for which SBTs have been issued in the metaverse space or elsewhere.

[0177] In this case, the token management server 10 obtains a certificate proving the qualifications of a doctor, lawyer, etc., and if the obtained certificate is valid, it issues the corresponding SBT. Alternatively, the token management server 10 may verify the membership card issued by the soccer school and confirm that the user has a record of attending the soccer school.

[0178] <Modification 2> The service server 20 may provide services corresponding to whether a user possesses a certain title. For example, if a user possesses a specific title, the metaverse server may allow them to purchase special items usable in the metaverse space. For example, the metaverse server may provide 3D items that can only be purchased by users who have reached a certain level in the game.

[0179] <Variation 3> The metaverse server (service server 20-4) may create a space where many users with the same SBT (same title, same level) reside. For example, the metaverse server may create a space that is only accessible to users with the same SBT. Alternatively, the metaverse server may create a space that highlights users with the same SBT (same title; for example, a title indicating that all episodes of the same anime series have been watched).

[0180] <Modification 4> Alternatively, the metaverse server (service server 20-4) may perform matching in the metaverse space using the titles (SBTs) owned by users. For example, the metaverse server may prioritize matching (conversation targeting) users who have the same type of title (common title). In this case, the metaverse server may display the titles used in the matching (titles common to both users) in a form that is recognizable to both users. Alternatively, the metaverse server may display the SBTs (titles) owned by each user by default.

[0181] <Modification 5> The metaverse server may provide a function to search for users with the same type and style of SBT (title) from among multiple users residing in the same metaverse space. For example, the metaverse server may display users who possess the searched SBT (title) from a list of user names. Alternatively, the metaverse server may implement controls to make users (user avatars) with the searched SBT stand out (for example, by making them glow).

[0182] <Variation 6> The use of SBT in the metaverse space described above can also be applied to other online services. For example, in a streaming service, when sending a chat to a person streaming a specific game, the video streaming server (service server 20-3) may send a comment with a colored icon that a third party can recognize, provided that the person has been proven to have achieved a certain rating or higher in online matches of that game.

[0183] <Example 7> The video sharing server (service server 20-2) may offer advertisements to allow users to support the broadcasters. In this case, the video sharing server displays an advertisement button 85 as shown in Figure 20.

[0184] When a user clicks the ad button 85, the video sharing server delivers the ad. Users who view the ad are awarded support points to the ad distributor. The video sharing server may also determine the content of the ad to deliver based on the SBT (Science Battle Points) the user owns. There may also be a limit on the number of times an ad is delivered (and support points are awarded) (up to 3 times per day in the example in Figure 20).

[0185] A video sharing server may select advertisements to deliver based on the titles (SBT) earned by the user. For example, if a user has earned the title "Anime Program A: All Episodes Watched," the video sharing server will deliver advertisements related to Anime Program A. The video distribution server may also visualize the SBT (title) used to select the advertisements so that the user can recognize it when delivering advertisements. The video sharing server may also award support points to the user when they click on a link or watch the advertisement video in its entirety. Furthermore, all or part of the advertising revenue paid by the user for watching the advertisements may be returned to the rights holder corresponding to the SBT that formed the basis of the advertisement selection (for example, the production company of Anime Program A in the above example).

[0186] <Differentiation Example 8> The token management server 10 may have various SNS-related functions. The token management server 10 may also have SNS server functionality.

[0187] The token management server 10 may allow users to select whether or not the content they post is related to a predetermined IP (intellectual property right). For example, the IP name on which the user holds SBT may be displayed above the posted message. Alternatively, related IPs may be searchable. Furthermore, if an IP is selected (i.e., the post is related to an IP), the token management server 10 may, when the user's post is displayed on the timeline, attach a tag with the IP name in a manner that is visible to the user, separate from the posted content. The IP tags have a hierarchical structure; for example, "Game A1" may exist under the tag "Game A".

[0188] The token management server 10 may preview all images posted to the social networking service (SNS) on the timeline with a digital watermark filter applied. Furthermore, when a user selects an image and requests to view its details, the token management server 10 may display a pop-up advertisement. Once the user has finished viewing the advertisement, the token management server 10 may display the image in full resolution without the watermark.

[0189] When an image is posted, if it is a derivative work, the user selects the original IP tag. Advertising revenue generated from the display of derivative works may be returned to the IP holder.

[0190] The token management server 10 may require the poster to select whether or not the image is an AI-generated image (including images that were originally AI-generated even if they have been edited by a human). If the poster selects that the image is AI-generated, the token management server 10 may forcibly add a tag to that effect to the posted image. Alternatively, if the poster selects that the image is not AI-generated, and a certain number of reports of suspected AI images have been received, the token management server 10 may request the poster to submit evidence that the image is not AI-generated (for example, layer information used during illustration creation). The token management server 10 may hide the posted image until evidence for the image is submitted. If the correct evidence is submitted (verification in this case may be done by human checks or AI checks), the token management server 10 may add a tag to the posted image indicating that it has been confirmed that the image is not AI-generated. Alternatively, the token management server 10 may provide a button that excludes AI-generated images from search results with a single tap.

[0191] The token management server 10 allows users to select the destination SBT when posting messages, etc. For example, the token management server 10 allows a user to post a message that will only be displayed on the timeline of SNS users who own at least one SBT related to a specific IP address. In addition, before the posted content is displayed, the destination information may be displayed separately from the posted content in a visible manner.

[0192] The token management server 10 can filter the timeline. If a user selects an IP name, the token management server 10 can display only messages and other posts that have that IP tag attached. Alternatively, if a user selects an SBT, the token management server 10 can display only posts from SNS users who own that SBT. The token management server 10 also manages the display history for each filter. Furthermore, users can register a predetermined number of their favorite filters.

[0193] The token management server 10 may provide a trend word function. The trend word function may extract words based on IP tags and SBTs, rather than by string aggregation. The token management server 10 may display a trend ranking for each IP.

[0194] The token management server 10 may provide a "Recommended for you" feature that displays posts from other users who are not followed. In this recommendation feature, users can also specify an IP address when searching for posts selected based on the SBTs they own. For example, normally, searching for "Yamada" will search for and display Yamadas from various fields (industries, business types). However, if a user selects the IP address for "Game B," or selects "Game B" in their SBT and then searches for "Yamada," the likelihood of being provided with information related to Yamadas who are involved with Game B increases.

[0195] <Modification 9> The token management server 10 may also have an SBT update function. In this case, the My Page control unit 304 periodically logs into the user's account using the login information from the service server 20.

[0196] For example, if a user possesses SBTs that are related to games provided on the game server, the My Page Control Unit 304 will acquire information corresponding to those SBTs (obtained from play history etc. stored in the game server account). If there are any updatable titles (user information corresponding to the titles) among the titles corresponding to the SBTs, the My Page Control Unit 304 will update the SBTs (reissue the SBTs).

[0197] For example, if the strength (level) of a character set in SBT is not at its maximum before accessing the game server but reaches its maximum as the game progresses, the My Page Control Unit 304 will issue a title such as "Level MAX" related to the strength of that SBT.

[0198] <Variation 10> In the above embodiment, the token management server 10 was described as issuing SBTs as a means of proving the titles, etc., acquired by the user. However, the token management server 10 may use other means to prove the user's title.

[0199] Specifically, the token management server 10 may issue a digital certificate using a public key infrastructure (PKI) as the title acquisition certificate. Alternatively, the token management server 10 may issue a verifiable credential certificate (VCs) whose contents can be verified online as the title acquisition certificate.

[0200] Furthermore, if digital certificates or credential certificates are issued via PKI as certificates of title acquisition, these certificates may be managed by the user's wallet or by an account on the token management server 10.

[0201] <Variation 11> The system configuration shown in Figure 3 is illustrative. For example, the token management server 10 may provide a wallet service. That is, the token management server 10 may also have the functionality of a wallet server.

[0202] As described above, the token management server 10 issues SBTs corresponding to titles, etc., acquired by users through online services. Users who receive SBTs can assert their acquired titles against third parties. By receiving SBTs, users can, for example, use titles acquired by playing online games in the metaverse space. In other words, the metaverse server can display the user's title along with their avatar, etc. This display is expected to make communication in the metaverse space smoother and more active.

[0203] Next, we will describe the hardware of each device that makes up the information processing system. Figure 21 shows an example of the hardware configuration of the token management server 10.

[0204] The token management server 10 can be configured using an information processing device (a so-called computer), and has the configuration illustrated in Figure 21. For example, the token management server 10 includes a processor 311, memory 312, input / output interface 313, and communication interface 314, etc. The components of the processor 311, etc., are connected by an internal bus or the like and are configured to communicate with each other.

[0205] However, the configuration shown in Figure 21 is not intended to limit the hardware configuration of the token management server 10. The token management server 10 may include hardware not shown, and it may not have an input / output interface 313 if necessary. Also, the number of processors 311 etc. included in the token management server 10 is not intended to be limited to the example in Figure 21; for example, multiple processors 311 may be included in the token management server 10.

[0206] The processor 311 is a programmable device such as a CPU (Central Processing Unit), MPU (Micro Processing Unit), or DSP (Digital Signal Processor). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs, including an operating system (OS).

[0207] Memory 312 includes RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive), SSD (Solid State Drive), etc. Memory 312 stores the OS program, application programs, and various data.

[0208] The input / output interface 313 is an interface for a display device or input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device that accepts user input such as a keyboard or mouse.

[0209] The communication interface 314 is a circuit, module, etc., that communicates with other devices. For example, the communication interface 314 includes a NIC (Network Interface Card), etc.

[0210] The functions of the token management server 10 are realized by various processing modules. These processing modules are realized, for example, by the processor 311 executing a program stored in memory 312. The program can also be recorded on a computer-readable storage medium. The storage medium can be a non-transitory material such as semiconductor memory, hard disk, magnetic recording medium, or optical recording medium. In other words, the present invention can also be embodied as a computer program product. Furthermore, the program can be downloaded via a network or updated using the storage medium on which the program is stored. Moreover, the processing module may be realized by a semiconductor chip.

[0211] Furthermore, the service server 20 and other similar devices can also be configured using information processing equipment, just like the token management server 10. Since their basic hardware configuration is the same as that of the token management server 10, a detailed explanation will be omitted.

[0212] The token management server 10, which is an information processing device, is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the token management server 10 executes a control method for the token management server 10 using this program. Similarly, the service server 20 is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the service server 20 executes a control method for the service server 20 using this program.

[0213] [Differentiation] The configuration and operation of the information processing system described in the above embodiment are illustrative examples and are not intended to limit the system configuration.

[0214] In the above embodiment, the case in which the service server 20 obtains SBT owned by the user via the token management server 10 was described. However, the service server 20 may also obtain SBT owned by the user by directly accessing the user's wallet.

[0215] In the above embodiment, the case in which the token management server 10 determines whether or not a user has acquired a title (whether or not SBT can be issued) was described. However, the service server 20 may determine whether or not a title can be awarded based on the user information stored in the account. If it is possible to award a title, the service server 20 sends information about the awardable title (for example, the name of the service, the specific content of the title) and the user's wallet address to the token management server 10. The token management server 10 promptly asks the user whether or not they want SBT issued, and issues SBT if the user wishes to receive it.

[0216] In the above embodiment, the case in which the token management server 10 issues SBTs that the user wishes to issue was described. However, the token management server 10 may also issue SBTs for each title that the user has acquired.

[0217] There is no limit to the number of SBTs (claimed ownership titles) a single user can use for online services. A user may use one SBT for online services, or multiple SBTs for online services. Naturally, different SBTs (titles) may be used for each online service.

[0218] The above embodiment describes a case in which SBTs are issued based on user information stored in the service server 20. However, SBTs may also be issued based on user information stored in the token management server 10. For example, the token management server 10 may give a user a title corresponding to the NFT transaction amount (for example, a title such as "NFT Transaction Amount No. 1: Season 1") and issue a corresponding SBT.

[0219] In the flowcharts (sequence diagrams) used in the above description, multiple processes (processes) are shown in order, but the execution order of the processes performed in the embodiment is not limited to the order in which they are shown. In the embodiment, the order of the illustrated processes can be changed to the extent that it does not impair the content, for example, by executing each process in parallel.

[0220] The embodiments described above are explained in detail to facilitate understanding of the disclosure, and it is not intended that all the configurations described above are necessary. Furthermore, when multiple embodiments are described, each embodiment may be used individually or in combination. For example, it is possible to replace parts of the configuration of one embodiment with those of another embodiment, or to add configurations from other embodiments to the configuration of one embodiment. In addition, it is possible to add, delete, or replace parts of the configuration of one embodiment with those of another.

[0221] As described above, the industrial applicability of the present invention is clear, and it is particularly suitable for information processing systems that enable users to use acquired titles in online services.

[0222] Some or all of the above embodiments may also be described as follows, but are not limited to the following:

[0223] [Note 1] Information generated by a first server providing the first service, based on user information relating to the status of a user receiving the first service, includes an issuing means for issuing SBT (SoulBound Token) corresponding to the user information, with the user as the owner. A guarantee means that enables a second server providing a second service to display a guarantee that the user owns the SBT, A user information SBT (Systematic Beta Test) device equipped with the necessary components.

[0224] [Note 2] The assurance means is a user information SBT device as described in Appendix 1, which enables the second server to display an indication that the SBT is authorized by the service provider that provides the first service.

[0225] [Note 3] The guarantee means is a user information SBT device as described in Appendix 2, which transmits the SBT owned by the user to the second server in response to a request from the second server.

[0226] [Note 4] The SBT is a user information SBT device as described in Appendix 3, which certifies that the user possesses a title acquired by the user through the provision of the first service.

[0227] [Note 5] The user information SBT device according to Appendix 4, further comprising display means for displaying at least one SBT owned by the user.

[0228] [Note 6] The user information SBT device described in any one of the appendices 1 to 5, wherein the first service includes at least one of the following: an online game service, a video sharing service, a video distribution service, and a metaverse service.

[0229] [Note 7] The user information SBT device described in any one of the appendices 1 to 5, wherein the second service includes a metaverse service.

[0230] [Note 8] A first server that provides the first service, A second server that provides the second service, User information SBT conversion device, Includes, The aforementioned user information SBT conversion device is An issuance means that issues SBT (SoulBound Token) corresponding to user information, with the user being the owner, based on user information relating to the status of a user receiving the first service, which is generated by the first server. The second server provides assurance means that enables the user to display an indication that the user owns the SBT, A system equipped with these features.

[0231] [Note 9] The assurance means is the system described in Appendix 8, which enables the second server to display an indication that the SBT is authorized by the service provider that provides the first service.

[0232] [Note 10] The assurance means is the system described in Appendix 9, which transmits the SBT owned by the user to the second server in response to a request from the second server.

[0233] [Note 11] The SBT is the system described in Appendix 10 that certifies that the user possesses the title acquired by the user through the provision of the first service.

[0234] [Note 12] The system according to Appendix 11, further comprising a display means for displaying at least one SBT owned by the user.

[0235] [Note 13] The system described in any one of the appendices 8 to 12, wherein the first service includes at least one of the following: an online game service, a video sharing service, a video distribution service, and a metaverse service.

[0236] [Note 14] The system described in any one of the appendices 8 to 12, wherein the second service includes a metaverse service.

[0237] [Note 15] Information generated by a first server providing the first service, based on user information relating to the status of the user receiving the first service, includes an issuance step of issuing an SBT (SoulBound Token) corresponding to the user information, with the user as the owner. A guarantee step, which enables a second server providing a second service to display a representation guaranteeing that the user owns the SBT, A control method for a user information SBT (Systematic Beta Test) device, comprising the above.

[0238] [Note 16] The assurance step is a control method for a user information SBT device as described in Appendix 15, which enables the second server to display an indication that the SBT is authorized by the service provider that provides the first service.

[0239] [Note 17] The control method for a user information SBT device as described in Appendix 16, wherein the assurance step involves transmitting the SBT owned by the user to the second server in response to a request from the second server.

[0240] [Note 18] The SBT is a control method for a user information SBT device as described in Appendix 17, which proves that the user possesses a title acquired by the user receiving the first service.

[0241] [Note 19] A control method for a user information SBT device as described in Appendix 18, further comprising a display step of displaying at least one SBT owned by the user.

[0242] [Note 20] A control method for a user information SBT device as described in any one of Appendix 15 to 19, wherein the first service includes at least one of the following: an online game service, a video sharing service, a video distribution service, and a metaverse service.

[0243] [Note 21] A control method for a user information SBT device as described in any one of appendices 15 to 19, wherein the second service includes a metaverse service.

[0244] [Note 22] The computer installed in the user information SBT device, Information generated by a first server providing the first service, based on user information relating to the status of the user receiving the first service, includes an issuance process that issues an SBT (SoulBound Token) corresponding to the user information, with the user as the owner. A guarantee process that enables a second server providing a second service to display a guarantee that the user owns the SBT, A program to execute.

[0245] [Note 23] The assurance process is a program as described in Appendix 22, which enables the second server to display an indication that the SBT is authorized by the service provider that provides the first service.

[0246] [Note 24] The assurance process is the program described in Appendix 23, which, in response to a request from the second server, transmits the SBT owned by the user to the second server.

[0247] [Note 25] The SBT is the program described in Appendix 24 that certifies that the user possesses a title acquired by the user through the provision of the first service.

[0248] [Note 26] The program described in Appendix 25, which further performs a display process to display at least one SBT owned by the user.

[0249] [Note 27] The program described in any one of the appendices 22 to 26, wherein the first service includes at least one of the following: an online game service, a video sharing service, a video distribution service, and a metaverse service.

[0250] [Note 28] The program described in any one of the appendices 22 to 26 includes a metaverse service.

[0251] Furthermore, some or all of the configurations described in Appendices 2 to 7, which are subordinate to Appendice 1 above, may also be subordinate to Appendices 8, 15, and 22 in the same way as those described in Appendices 2 to 7. Moreover, not limited to Appendices 1, 8, 15, and 22, some or all of the configurations described as appendices may also be subordinate to various hardware, software, various recording means for recording software, or systems, without departing from the embodiments described above.

[0252] Note that each disclosure of the above-cited prior art documents is incorporated herein by reference. Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely illustrative and that various modifications can be made without departing from the scope and spirit of the present invention. That is, the present invention naturally includes all disclosures including the claims, as well as various modifications and corrections that can be made by those skilled in the art in accordance with the technical idea.

Explanation of Reference Numerals

[0253] 10 Token management server 20 Service server 20-1 Service server 20-2 Service server 20-3 Service server 20-4 Service server 30 Terminal 41 Icon display area 43 Owned NFT button 45 Owned SBT button 47 List display area 49 Account link destination button 51 Support point button [[ID=,35]]53 Showcase button 55 NFT self-photo button 57 Settings button 59 Icon display area 61 Market button 63 Title display area 65 Total NFT display column " 67 Follow button 69 Follower button 7l Timeline button 73 Sorting box 75 Filter box 77 Pop-up 7l Push box field 8l Push character field 83 Virtual showcase 85 Ad Buttons 100 User Information SBT Conversion Device 101 Issuance method 102 Guarantee measures 201 Communication Control Unit 202 User Management Department 203 Function Control Unit 204 Storage section 301 Communication Control Unit 302 User Management Department 303 SBT Control Unit 304 My Page Control Unit 305 Storage section 311 Processors 312 memory 313 Input / Output Interfaces 314 Communication Interface

Claims

1. Information generated by a first server providing the first service, based on user information relating to the status of a user receiving the first service, includes an issuance means for issuing SBT (SoulBound Token) corresponding to the user information, with the user as the owner. A guarantee means that enables a second server providing a second service to display a guarantee that the user owns the SBT, A user information SBT conversion device equipped with the necessary components.

2. The user information SBT device according to claim 1, wherein the assurance means enables the second server to display an indication that the SBT is authorized by the service provider that provides the first service.

3. The user information SBT device according to claim 2, wherein the assurance means transmits the SBT owned by the user to the second server in response to a request from the second server.

4. The user information SBT device according to claim 3, wherein the SBT proves that the user possesses a title acquired by the user receiving the first service.

5. The user information SBT conversion apparatus according to claim 4, further comprising a display means for displaying at least one SBT owned by the user.

6. The user information SBT device according to any one of claims 1 to 5, wherein the first service includes at least one of an online game service, a video sharing service, a video distribution service, and a metaverse service.

7. The user information SBT device according to any one of claims 1 to 5, wherein the second service includes a metaverse service.

8. A first server that provides the first service, A second server that provides the second service, User information SBT conversion device, Includes, The aforementioned user information SBT conversion device is An issuance means for issuing SBT (SoulBound Token) corresponding to user information, with the user being the owner, based on user information relating to the status of a user receiving the first service, which is generated by the first server. The second server provides assurance means that enables the user to display an indication that the user owns the SBT, A system that includes these features.

9. Information generated by a first server providing the first service, based on user information relating to the status of the user receiving the first service, includes an issuance step of issuing an SBT (SoulBound Token) corresponding to the user information, with the user as the owner. A guarantee step, which enables a second server providing a second service to display a guarantee that the user owns the SBT, A control method for a user information SBT conversion device, comprising the above.

10. The computer installed in the user information SBT device, Information generated by a first server providing the first service, based on user information relating to the status of the user receiving the first service, includes an issuance process that issues an SBT (SoulBound Token) corresponding to the user information, with the user as the owner. A guarantee process that enables a second server providing a second service to display a guarantee that the user owns the SBT, A program to execute.

Images