NFT management device, control method and program for NFT management device

Abstract

This invention provides an NFT management device that contributes to improving convenience for users who own NFTs issued through the purchase of products. [Solution] The NFT management device comprises an acquisition means and a display control means. The acquisition means acquires NFTs (Non-Fungible Tokens) issued when a user purchases a product. The display control means displays information about the acquired NFTs. The display control means may also display the fact of the product purchase as part of the NFT transaction history.

Description

Technical Field

[0001] The present invention relates to an NFT management device, a control method for the NFT management device, and a program.

Background Art

[0002] There are technologies related to digital assets.

[0003] For example, Patent Document 1 describes an encrypted digital asset for footwear products and a method for creating or using such an encrypted digital asset. The method for providing the digital asset of Patent Document 1 includes a first step and a second step. The first step is to receive a transaction confirmation indicating a completed transaction of a footwear product or a digital file representing it from a first party to a second party. The second step is to send an encrypted block to a distributed blockchain ledger to record the transfer of the encrypted digital asset to the second party.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] When purchasing figures, characters in a game, etc., there are users who want to bring the purchased characters, etc. into a virtual space such as the metaverse. In order to meet such demands, it is conceivable to issue an NFT (Non-Fungible Token) corresponding to a figure, etc. according to the user's purchase of a product. However, in this case, the problem is how the user manages their own NFT.

[0006] Furthermore, Patent Document 1 merely discloses a technology for generating digital assets for footwear products. Therefore, applying the technology disclosed in Patent Document 1 will not solve the above problem.

[0007] The primary objective of this invention is to provide an NFT management device, a control method for the NFT management device, and a program that contribute to improving the convenience of users who possess NFTs issued through the purchase of goods. [Means for solving the problem]

[0008] According to a first aspect of the present invention, an NFT management device is provided, comprising: acquisition means for acquiring NFTs (Non-Fungible Tokens) issued by a user upon purchase of a product; and display control means for displaying information regarding the acquired NFTs.

[0009] According to a second aspect of the present invention, a control method for an NFT management device is provided, which acquires NFTs (Non-Fungible Tokens) issued when a user purchases a product, and displays information about the acquired NFTs.

[0010] According to a third aspect of the present invention, a program is provided for a computer installed in an NFT management device to perform the following: a process of acquiring an NFT (Non-Fungible Token) issued by a user as a result of purchasing a product; and a process of displaying information about the acquired NFT. [Effects of the Invention]

[0011] From each perspective of the present invention, an NFT management device, a control method for the NFT management device, and a program are provided that contribute to improving the convenience of users who possess NFTs issued through the purchase of goods. 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]

[0012] [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] Figure 4 is a diagram illustrating the operation of an information processing system according to an embodiment of this disclosure. [Figure 5] Figure 5 is a diagram illustrating the operation of an information processing system according to an embodiment of this disclosure. [Figure 6] Figure 6 is a diagram illustrating the operation of an information processing system according to an embodiment of this disclosure. [Figure 7] Figure 7 shows an example of the processing configuration of the integrated management server according to the embodiment of this disclosure. [Figure 8] Figure 8 shows an example of a user management database according to an embodiment of this disclosure. [Figure 9] Figure 9 shows an example of the display of a terminal according to the embodiment of this disclosure. [Figure 10] Figure 10 shows an example of the display of a terminal according to the embodiment of this disclosure. [Figure 11] Figure 11 shows an example of the processing configuration of an NFT management server according to an embodiment of this disclosure. [Figure 12] Figure 12 is a flowchart showing an example of the operation of the sales control unit according to the present disclosure. [Figure 13] Figure 13 shows an example of the display of a terminal according to the embodiment of this disclosure. [Figure 14] Figure 14 shows an example of the display of a terminal according to the embodiment of this disclosure. [Figure 15] Figure 15 shows an example of the display of a terminal according to the embodiment of this disclosure. [Figure 16] Figure 16 shows an example of the display of a terminal according to the embodiment of this disclosure. [Figure 17] FIG. 17 is a diagram showing an example of the display of a terminal according to an embodiment of the present disclosure. [Figure 18] FIG. 18 is a diagram showing an example of the display of a terminal according to an embodiment of the present disclosure. [Figure 19] FIG. 19 is a diagram showing an example of the display of a terminal according to an embodiment of the present disclosure. [Figure 20] FIG. 20 is a diagram showing an example of the display of a terminal according to an embodiment of the present disclosure. [Figure 21] FIG. 21 is a diagram showing an example of the processing configuration of a metaverse server according to an embodiment of the present disclosure. [Figure 22] FIG. 22 is a diagram showing an example of the display of a terminal according to an embodiment of the present disclosure. [Figure 23] FIG. 23 is a diagram showing an example of the display of a terminal according to an embodiment of the present disclosure. [Figure 24] FIG. 24 is a diagram showing an example of the display of a terminal according to an embodiment of the present disclosure. [Figure 25] FIG. 25 is a diagram for explaining a metaverse space according to an embodiment of the present disclosure. [Figure 26] FIG. 26 is a diagram for explaining the operation of a metaverse control unit according to an embodiment of the present disclosure. [Figure 27] FIG. 27 is a diagram showing an example of the display of a terminal according to an embodiment of the present disclosure. [Figure 28] FIG. 28 is a diagram showing an example of the display of a terminal according to an embodiment of the present disclosure. [Figure 29] FIG. 29 is a diagram for explaining the operation of a metaverse control unit according to an embodiment of the present disclosure. [Figure 30] FIG. 30 is a diagram for explaining the operation of a metaverse control unit according to an embodiment of the present disclosure. [Figure 31] FIG. 31 is a diagram for explaining the operation of a metaverse control unit according to an embodiment of the present disclosure. [Figure 32] FIG. 32 is a diagram for explaining the operation of a metaverse control unit according to an embodiment of the present disclosure. [Figure 33] Figure 33 is a sequence diagram showing an example of the operation of an information processing system according to the embodiment of this disclosure. [Figure 34] Figure 34 shows an example of a terminal display according to a modified embodiment of the present disclosure. [Figure 35] Figure 35 shows an example of the hardware configuration of the NFT management server related to this disclosure. [Modes for carrying out the invention]

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

[0014] An NFT management device 100 according to one embodiment includes an acquisition means 101 and a display control means 102 (see Figure 1). The acquisition means 101 acquires NFTs (Non-Fungible Tokens) issued when a user purchases a product (step S1 in Figure 2). The display control means 102 displays information about the acquired NFTs (step S2).

[0015] The NFT management device 100 acquires NFTs issued in response to a user's purchase of a product. The NFT management device 100 displays information about the acquired NFTs. For example, the NFT management device 100 displays the purchase history of the product on which the NFT was issued as part of the NFT's transaction history, distinguishable from the NFT's issuance history. Alternatively, the NFT management device 100 displays the tags set on the NFTs. As a result, users can easily manage the NFTs they own. In other words, the convenience for users who own NFTs issued through product purchases is improved.

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

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

[0018] The information processing system according to the first embodiment issues NFTs (Non-Fungible Tokens) of digital content corresponding to products purchased by the user. For example, if a user purchases a figurine, an NFT is issued for the 3D data (3D model) of the figurine. Alternatively, if a user purchases a character in a game, an NFT is issued for the 3D model of the character.

[0019] [System Configuration] As shown in Figure 3, the information processing system according to the first embodiment includes a plurality of service servers 10-1 and 10-2, an integrated management server 20, a content management server 30, an NFT management server 40, a wallet server 50, and a metaverse server 60.

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

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

[0022] Service server 10 is a server managed and operated by a service provider that provides various services to users.

[0023] Service server 10-1 provides an e-commerce (Electronic Commerce) site that sells physical goods such as figurines (digital figurines in games or virtual spaces), CDs, and DVDs. Alternatively, service server 10-1 may sell books and e-books.

[0024] Service server 10-2 provides, for example, an online game. Service server 10-2 (game server) not only controls the progress of the game but also sells characters (people) used in the game to users. Users can progress through the game using the characters they have purchased. In other words, service server 10-2 sells users the right to use characters in the game.

[0025] In the first embodiment, the configuration and operation of the information processing system will be explained using the example of a case where the service server 10-2 provides a 3D game. However, this does not mean that the games targeted by the information processing system are limited to 3D games. The games disclosed in this application include FPS (First Person Shooter), action games, fighting games, RPG (Role Playing Game), etc.

[0026] The integrated management server 20 is a server managed and operated by a platform provider that provides a platform for managing purchased goods across multiple service providers (service servers 10). The integrated management server 20 provides cross-platform management services (management services related to purchased goods, etc.) for at least one service server 10 for which a user has an account.

[0027] Furthermore, the term "product" in this application includes not only tangible objects such as figures, CDs, and DVDs, but also intangible objects such as characters used in games. In other words, the term "product" in this application includes not only tangible objects in the real world, but also characters and items in 3D space. In the example above, the right to use characters appearing in the game, sold by the game server, also falls under the category of "product." Services provided by service providers to users are also included in the definition of "product." Moreover, the term "product" in this application is not limited to items transferred for a fee, but also includes items transferred free of charge.

[0028] The integrated management server 20 is linked to accounts on each service server 10. Specifically, users can log in to accounts created on each service provider (service server 10) via the integrated management server 20. Users can then purchase products or play games on the service server 10 they are logged into.

[0029] The integrated management server 20 can obtain the user's activity history on the service server 10. More specifically, the integrated management server 20 can obtain purchase history of products, game play history, etc. Based on the purchase history of products purchased on the e-commerce site and the game play history of games played on the game server, the integrated management server 20 generates a list of the user's purchased products.

[0030] The content management server 30 is a server that controls and manages digital content such as figures, CDs, and DVDs sold to general consumers, as well as digital content such as characters sold to game users.

[0031] For example, a content management server 30 is a server managed and operated by an IP (Intellectual Property) holder such as a record company, a figurine manufacturer, or a game manufacturer, which controls and manages its own IP (intellectual property rights).

[0032] The NFT management server 40 is a server managed and operated by an NFT platform provider (an NFT issuer) that issues NFTs (Non-Fungible Tokens). The NFT management server 40 issues (generates) NFTs of digital content corresponding to products purchased by users from service providers (businesses that operate e-commerce sites or online games). The NFT management server 40 is an NFT management device that manages the NFTs issued to users. The NFT management server 40 also functions as an NFT generation device that generates NFTs.

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

[0034] Wallet Server 50 is a server that provides wallet services for tokens such as NFTs and SBTs (SoulBound Tokens). Users can prove ownership of NFTs and SBTs by opening an account (wallet) with Wallet Server 50.

[0035] The metaverse server 60 is a server that provides a virtual space to users. The metaverse server 60 is a virtual space control device that controls the virtual space. Users access the metaverse server 60 using an HMD or similar device and engage in activities within the metaverse space provided by the metaverse server 60. The metaverse server 60 has the functionality of an NFT utilization device that uses NFT-converted digital content, and the functionality of a 3D model utilization device.

[0036] Each device shown in Figure 3 is connected to a network. Specifically, the service server 10, integrated management server 20, content management server 30, NFT management server 40, wallet server 50, metaverse server 60, and terminal 70 are connected to the network by wired or wireless communication means.

[0037] 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 integrated management servers 20. Load balancing and redundancy may be achieved by using multiple integrated management servers 20.

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

[0039] <Create an account> Users create accounts with each service provider to purchase figures and other items, play online games, use integrated management services, use marketplaces, and enjoy wallet services.

[0040] Specifically, the user operates terminal 70 to access wallet server 50 and create an account (wallet). The user operates terminal 70 to create an account on an e-commerce site that sells the product they wish to purchase or on a game server for a game they wish to play. The user operates terminal 70 to create an account on integrated management server 20. The user operates terminal 70 to create an account (marketplace account) on NFT management server 40.

[0041] <Account Linking> Users configure their login information for each service server 10 on the integrated management server 20. For example, users configure their login information (ID, password) for logging into an e-commerce site and their login information for logging into a game server on the integrated management server 20.

[0042] Furthermore, the user sets their wallet address (the wallet address generated by the wallet server 50) on the service server 10, the integrated management server 20, the NFT management server 40, and the metaverse server 60, respectively.

[0043] Each server stores the user's wallet address along with their login information (ID, password, etc.).

[0044] <Purchase of Products> Here, we will explain the operation of the information processing system using the example of a user logging into an e-commerce site (service server 10-1) and purchasing a figurine.

[0045] To purchase a figure, the user logs into an account on the integrated management server 20 (step S01 in Figure 4). The integrated management server 20 displays a list of e-commerce sites on the terminal 70, allowing the user to select an e-commerce site.

[0046] The integrated management server 20 redirects the terminal 70 to the login page of the e-commerce site selected by the user (step S02). Specifically, the integrated management server 20 sends a URL (Uniform Resource Locator) to the terminal 70 for logging into the e-commerce site account selected by the user.

[0047] The URL sent to terminal 70 is a redirect URL for connecting terminal 70 to the login page of the e-commerce site, and the user's login information (ID, password) is embedded in this redirect URL.

[0048] When terminal 70 receives a redirect URL, it accesses the login page of the e-commerce site according to that URL. At that time, since the redirect URL contains login information, the e-commerce site (service server 10) obtains the user's login information and authenticates them.

[0049] Users purchase figures on the e-commerce site they are logged into.

[0050] The e-commerce site stores the purchase history of the products (figures) that users have purchased. Specifically, the e-commerce site (service server 10-1) stores information such as the product name, product code, price, purchase date, and manufacturer name of the products sold as the purchase history.

[0051] Furthermore, the person in charge of the e-commerce site obtains information such as the product name and product code from the product manufacturer, etc., and registers the obtained information on the service server 10.

[0052] The integrated management server 20 retrieves the purchase history of products purchased by users on e-commerce sites. For example, the integrated management server 20 periodically or at predetermined intervals accesses e-commerce sites where users have logged in and retrieves the purchase history of products purchased by users on those e-commerce sites.

[0053] For example, the integrated management server 20 retrieves the purchase history, which includes information about the purchased items (e.g., product name, product code, price, purchase date, manufacturer name, etc.) (step S03). The integrated management server 20 stores the user's purchase history in the user's account.

[0054] The integrated management server 20 acquires the user's game play history for items sold in the online game, and extracts the purchase history of items purchased by the user from that play history. The integrated management server 20 stores the extracted purchase history (character purchase history) in the user's account.

[0055] <Purchase of NFT content for purchased items> Users who purchase a product can purchase the corresponding digital content. For example, if a user purchases a figurine, they can purchase the 3D model (3D data) of that figurine. Or, if a user purchases a character for use in a game, they can purchase the 3D model of that character.

[0056] A 3D model is a three-dimensional graphic used in 3D games and metaverse spaces, representing three-dimensional shape data. A 3D model is 3D shape information such as a polygon model consisting of combinations of faces, edges, and vertices, or a sculpted model consisting of numerous polygons. A 3D model is data whose shape is variable; it allows for changes to the positional relationships and angles of objects, and changes to the surface texture of objects while maintaining their shape.

[0057] Alternatively, if a user purchases a CD or DVD, they can purchase the audio data of each song included on the CD or the video data of movies, etc., included on the DVD. Similarly, if a user purchases a book or e-book, they can purchase the digital book data containing the contents of that book.

[0058] Digital content corresponding to products purchased by users will be converted into NFTs. In the following explanation, NFT-converted digital content corresponding to products purchased by users will be referred to as "NFT content."

[0059] Users who wish to purchase NFT content log in to the integrated management server 20. The user requests the integrated management server 20 (platform operator) to issue a purchase certificate for the product corresponding to the NFT content they wish to purchase. Specifically, when the user performs a predetermined action (for example, pressing the purchase certificate issuance button), the integrated management server 20 displays a list of products that the user has already purchased on the terminal 70. The user selects the NFT content they wish to purchase from the displayed list of products.

[0060] When a user selects a product, the integrated management server 20 issues a purchase certificate for the product selected by that user. Specifically, the integrated management server 20 issues a product purchase certificate that includes information identifying the purchaser of the product and information about the product, with the platform operator as the issuer.

[0061] For example, the integrated management server 20 sets the wallet address as information to identify the purchaser of the product and issues a product purchase certificate that includes product name, product code, price, purchase date, manufacturer name, etc. as information about the product.

[0062] In the first embodiment, we will describe a case where the integrated management server 20 issues a product purchase certificate as an SBT (SoulBound Token).

[0063] First, the platform operator's representative generates a smart contract to issue a product purchase certificate as described above, and then deploys the generated smart contract to the blockchain.

[0064] When the integrated management server 20 needs to issue a product purchase certificate, it calls a function of the smart contract and inputs the information necessary to issue the product purchase certificate (wallet address, product information, platform operator ID, etc.).

[0065] When the smart contract is executed, the user's wallet (wallet address) is associated with the SBT issued as proof of purchase.

[0066] Thus, the integrated management server 20 issues an SBT as a product purchase certificate, with the platform operator as the issuer and the product purchaser as the owner (step S04).

[0067] By obtaining a product purchase certificate, users can purchase NFT content. In this case, the user logs in to the marketplace provided by the NFT management server 40 (step S11 in Figure 5).

[0068] When a user performs a predetermined action (for example, pressing the NFT content purchase button), the NFT management server 40 uses the user's wallet address to obtain a product purchase certificate from the user's wallet (step S12). The NFT management server 40 displays a list of products corresponding to the product purchase certificates owned by the user on the terminal 70.

[0069] The user selects the NFT content they wish to purchase from the displayed list of products.

[0070] When a user selects a product, the NFT management server 40 verifies the product purchase certificate corresponding to the product selected by the user. For example, the NFT management server 40 determines whether the issuer of the product purchase certificate is a predetermined issuer (determining whether the issuer is a trustworthy platform provider).

[0071] Upon successful verification of the product purchase certificate, the NFT management server 40 retrieves the digital content to be sold (digital content to be converted into an NFT) and its associated information from the content management server 30. Specifically, the NFT management server 40 retrieves the digital content and associated information from the content management server 30 of the IP holder of the product corresponding to the NFT content.

[0072] For example, if a user wishes to purchase NFT content corresponding to a figurine they have purchased, the NFT management server 40 retrieves the digital content (3D model) related to that figurine from the content management server 30 managed by the figurine's manufacturer.

[0073] Alternatively, if a user wishes to purchase NFT content corresponding to a CD they have purchased, the NFT management server 40 retrieves the digital content (audio data) of that CD from the content management server 30 managed by the record company.

[0074] Alternatively, if a user wishes to purchase NFT content corresponding to a character used in the game, the NFT management server 40 retrieves the digital content (3D model) of that character from the content management server 30 managed by the game manufacturer.

[0075] Specifically, the NFT management server 40 sends information to the content management server 30 that identifies the product corresponding to the NFT content that the user wishes to purchase. For example, the NFT management server 40 sends a "content provision request" to the content management server 30 that includes product codes such as figures, CDs, and characters (step S13).

[0076] When the content management server 30 receives a content provision request, it sends the digital content corresponding to the product code included in the request and its associated information to the NFT management server 40 (step S14). For example, the content management server 30 sends a response to the NFT management server 40 that includes a 3D model such as a figurine or character and its associated information.

[0077] Examples of supplementary information for digital content include information referenced when using the digital content (e.g., 3D models or sound data) and information regarding restrictions on the use of the digital content. A more detailed explanation of supplementary information for digital content will be provided later.

[0078] Furthermore, figure manufacturers, record companies, game manufacturers, etc., register the product codes of the products they handle, digital content (for example, 3D models of characters, CD audio data, etc.), and related information in advance on the content management server 30. Manufacturers, etc., register the digital content and related information on the content management server 30 based on their own policies, etc.

[0079] Before or after acquiring the digital content, once the payment for the NFT content has been settled, the NFT management server 40 issues an NFT with the purchaser of the NFT content as the owner (step S15). Specifically, the NFT management server 40 uses a smart contract to issue (generate) an NFT with the purchaser as the owner and the NFT issuer as the issuer.

[0080] More specifically, the NFT management server 40 issues an NFT that includes metadata such as information about the underlying product (e.g., product name, product code, price, etc.) and a description of the NFT content (e.g., type of NFT content; e.g., 3D model). The metadata is configured to be updatable after the NFT is issued. For example, the metadata is stored in storage other than the blockchain so that the NFT issuer can update the metadata after the NFT is issued. Alternatively, a dynamic NFT whose content is updated by a smart contract may be used.

[0081] When an NFT for NFT content is issued, the user's wallet (wallet address) is associated with the NFT of the NFT content. The NFT content (digital content) and its associated information are stored in the storage of the NFT management server 40. A link (URL) to access the storage location of the NFT content is written on the NFT itself.

[0082] Users can log in to the marketplace and view the NFT content (digital content) stored on the NFT management server 40.

[0083] <Using NFT content in the metaverse space> Users who purchase NFT content can use that NFT content in the metaverse space.

[0084] A user who wishes to use NFT content in the metaverse space logs in to the metaverse server 60 (step S21 in Figure 6). The user instructs the logged-in metaverse server 60 to retrieve the NFT content. In response to this instruction, the metaverse server 60 accesses the user's wallet and retrieves the NFT corresponding to the NFT content owned by the user (step S22).

[0085] When an NFT is acquired, the metaverse server 60 displays a list of information related to the NFT content corresponding to the acquired NFT on the terminal 70, allowing the user to select the NFT content (the NFT content they wish to use on the metaverse). For example, the metaverse server 60 displays a list of product names corresponding to the NFT content (e.g., figure names, CD titles, character names) on the terminal 70.

[0086] Subsequently, the metaverse server 60 accesses the NFT management server 40 and retrieves the NFT content corresponding to the NFT selected by the user (step S23). The user can then use the retrieved NFT content in the metaverse space.

[0087] For example, the metaverse server 60 obtains information from the user regarding how they intend to use the acquired NFT content. For instance, if a user owns NFT content of a figurine, they can display that figurine in their room in the metaverse. Alternatively, if a user owns NFT content of a CD, they can play the corresponding audio data in their room. Or, if a user owns NFT content of a game character, they can place that character in their room in the metaverse space.

[0088] In this process, the metaverse server 60 uses the accompanying information obtained along with the NFT content to utilize the NFT content (for example, a 3D model of a character used in a game) in the metaverse space. For example, the metaverse server 60 models the character in the metaverse space with the height specified by the game maker. Alternatively, the metaverse server 60 models the CD jacket obtained from the accompanying information in the metaverse space. Furthermore, if the usage of the NFT content is specified by the rights holder as accompanying information, the user can only use the NFT content in the specified usage form. For example, if the usage form of a 3D model of a character is specified as only for display in space, the user cannot use the 3D model as an avatar. For example, if the usage form of a 3D model of a weapon is specified as only for use as an accessory, the user cannot place the 3D model in space.

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

[0090] [Integrated Management Server] Figure 7 shows an example of the processing configuration (processing module) of the integrated management server 20 according to the embodiment disclosed herein. Referring to Figure 7, the integrated management server 20 comprises a communication control unit 201, a user management unit 202, a purchase certificate control unit 203, and a storage unit 204.

[0091] 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 70. The communication control unit 201 also transmits data to terminal 70. 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 transmit 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.

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

[0093] 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 and login information for logging into each service server 10 where the user created an account.

[0094] The user management unit 202 stores the acquired name, wallet address, login information for logging into the service server 10, etc., in the user management database (see Figure 8). The user management unit 202 stores the login information associated with the service server 10 (EC site, game server) for each user's account. Note that the user management database shown in Figure 8 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).

[0095] When a logged-in user wishes to purchase a product or play a game, the user management unit 202 displays a list of e-commerce sites and game servers that the user can log into on the terminal 70 that the user possesses. For example, the user management unit 202 displays a GUI (Graphical User Interface) as shown in Figure 9 on the terminal 70, allowing the user to select an e-commerce site or online game.

[0096] When a user selects an e-commerce site or online game to log in to, the user management unit 202 redirects the terminal 70 to the login page of the e-commerce site or online game selected by the user. At that time, the user management unit 202 sends a redirect URL to the terminal 70 that contains the login information of the user who has logged into their account (login information corresponding to the e-commerce site or online game being logged into).

[0097] The purchase certificate control unit 203 is a means for controlling the purchase certificate of a product purchased by a user. Specifically, the purchase certificate control unit 203 issues a purchase certificate of the product (e.g., a figurine, CD, or game character) as an SBT to a user who has purchased the product. More specifically, the purchase certificate control unit 203 uses the user's wallet address to issue an SBT to the user that proves the user has purchased the product.

[0098] The purchase certificate control unit 203 periodically or at predetermined intervals accesses each e-commerce site and game server (service server 10) where login information is registered in the user's account. The purchase certificate control unit 203 logs in to the e-commerce site, etc., using the login information corresponding to each e-commerce site and game server.

[0099] The purchase certificate control unit 203 retrieves the purchase history of products purchased by the user from the product purchase history page of the service server 10 to which the user has logged in. Alternatively, the purchase certificate control unit 203 retrieves the play history of games played by the user from the play history page of the service server 10 to which the user has logged in.

[0100] Alternatively, the purchase certificate control unit 203 may, while logged into the service server 10, obtain the user's purchase history and play history using an API (Application Programming Interface) or the like predetermined by the service provider.

[0101] When the purchase history of a product is obtained, the purchase certificate control unit 203 stores information about the product purchased by the user (e.g., product name, product code, price, purchase date, manufacturer name, etc.) and information about the e-commerce site where the product was purchased in the purchased product list field of the user management database.

[0102] Alternatively, when the game play history is obtained, the purchase certificate control unit 203 extracts the purchase history of products (for example, characters, weapons, accessories, items, skins (armor, clothing, underwear), etc.) from the history and stores the information of those products in the user management database.

[0103] If the acquired purchase history is already stored in the user management database, the purchase certificate control unit 203 may discard the acquired product purchase history or overwrite it with the corresponding purchase history.

[0104] When a user who has logged into their account requests the issuance of a purchase certificate, the purchase certificate control unit 203 displays a list of products that the user has purchased (products listed in the purchased product list) and identifies the product for which the user requests the purchase certificate. For example, the purchase certificate control unit 203 displays a GUI as shown in Figure 10 to identify the product for which the user requests the purchase certificate.

[0105] When a user identifies a product for which they wish to obtain a purchase certificate, the purchase certificate control unit 203 calls a function of a smart contract deployed on a node on the blockchain to issue a smart purchase certificate (SBT).

[0106] For example, the purchase certificate control unit 203 inputs the wallet address as the recipient's address for the SBT and the platform operator's wallet address as the issuer's ID for the SBT into the smart contract. Furthermore, the purchase certificate control unit 203 may input information about the product purchased by the user, such as the product name, product code, price, purchase date, and manufacturer's name, into the smart contract.

[0107] The smart contract uses this information to issue a Smart Trust (SBT) as a proof of purchase, with the purchaser of the goods as the owner and the platform operator as the issuer, and the SBT containing metadata about the purchased goods.

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

[0109] The memory unit 204 is a means for storing information necessary for the operation of the integrated management server 20. For example, the memory unit 204 stores the names of e-commerce sites and online games in association with the URLs of their login pages.

[0110] [NFT Management Server] Figure 11 is a diagram showing an example of the processing configuration (processing module) of the NFT management server 40 according to the embodiment disclosed herein. Referring to Figure 11, the NFT management server 40 comprises a communication control unit 301, a user management unit 302, a sales control unit 303, a provision control unit 304, a My Page control unit 305, and a storage unit 306.

[0111] 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 70. The communication control unit 301 also transmits data to terminal 70. The communication control unit 301 passes the data received from other devices to other processing modules. The communication control unit 301 transmits the 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.

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

[0113] 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 wallet address. The user management unit 302 stores the obtained name, login information, wallet address, etc. in a designated database.

[0114] The sales control unit 303 is a means for performing controls related to the sale of NFT content.

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

[0116] When a user who has logged into the marketplace wishes to purchase NFT content, the sales control unit 303 connects to the user's wallet using the user's wallet address. The sales control unit 303 obtains the Item Purchase Certificate (SBT) associated with the user's wallet (step S101).

[0117] The sales control unit 303 obtains information about the product purchased by the user (e.g., product name, product code, price, purchase date, manufacturer name, etc.) from the acquired product purchase certificate. Using the acquired product information, the sales control unit 303 identifies the product corresponding to the NFT content that the user wishes to purchase (step S102).

[0118] For example, the sales control unit 303 displays a GUI as shown in Figure 13 on the terminal 70 to identify the product corresponding to the NFT content that the user wishes to purchase. At that time, the sales control unit 303 may also present the price of the NFT content to the user, as shown in Figure 13.

[0119] The sales control unit 303 may obtain the price of the NFT content by querying the content management server 30. Alternatively, the price of the NFT content may be set to a price obtained by multiplying the price of the corresponding product by a predetermined coefficient.

[0120] Once the user has finished selecting the NFT content to purchase, the sales control unit 303 verifies the product purchase certificate corresponding to the NFT content selected by the user (step S103).

[0121] Specifically, the sales control unit 303 verifies the issuer of the product purchase certificate. For example, the sales control unit 303 determines whether the ID of the issuer of the product purchase certificate (e.g., the platform operator's wallet address) is pre-registered as the ID of the platform operator with whom the transaction is taking place.

[0122] If the issuer's ID is registered, the sales control unit 303 determines that the product purchase certificate corresponding to the NFT content the user wishes to purchase is legitimate (determines that the verification of the product purchase certificate was successful). If the issuer's ID is not registered, the sales control unit 303 determines that the product purchase certificate corresponding to the NFT content the user wishes to purchase is invalid (determines that the verification of the product purchase certificate failed).

[0123] If the product purchase certificate is invalid (step S104, No branch), the sales control unit 303 notifies the user that the NFT content cannot be sold (notification of non-sale; step S105).

[0124] If the product purchase certificate is valid (step S104, Yes branch), the sales control unit 303 obtains the digital content to be sold to the user and its associated information from the content management server 30. Specifically, the sales control unit 303 sends a content provision request, including the product code of the product corresponding to the digital content, to the content management server 30 of the manufacturer or game manufacturer listed on the product purchase certificate (step S106).

[0125] The sales control unit 303 identifies the content management server 30 to which the content provision request will be sent by referring to table information that stores the IP holder (manufacturer, game manufacturer) name and the information of the content management server 30 (e.g., address) in association with each other.

[0126] The sales control unit 303 receives responses (affirmative responses, negative responses) to content provision requests from the content management server 30.

[0127] If a negative response indicating that the digital content cannot be provided is received (step S107, No branch), the sales control unit 303 notifies the user that the NFT content cannot be sold (notification of unavailability; step S105).

[0128] If an affirmative response indicating that the digital content is available is received (step S107, Yes branch), the NFT content is sold to the user (step S108).

[0129] Users can pay for NFT content using cryptocurrencies such as Bitcoin or Ethereum. Alternatively, credit cards or electronic money may be used to pay for NFT content.

[0130] Furthermore, all or part of the payment for NFT content made by the user will be paid to the corresponding IP holder (manufacturer, game developer, etc.).

[0131] Once payment for the NFT content is completed, the sales control unit 303 issues an NFT of the NFT content (step S109). The sales control unit 303 issues an NFT of the digital content obtained from the content management server 30 using a smart contract.

[0132] Here, the platform operator's representatives create a smart contract in advance to issue NFTs for NFT content. These representatives then deploy the smart contract to the blockchain.

[0133] The sales control unit 303 issues NFTs of NFT content using a smart contract for NFT issuance.

[0134] The smart contract for issuing NFTs designates the purchaser of the NFT content as the owner and issues an NFT that includes metadata containing information about the NFT content (e.g., the name of the corresponding product, the name of the manufacturer, etc.). The NFT content and its associated information are stored in the storage of the NFT management server 40, which is accessible from the outside. When the smart contract for issuing NFTs is executed, a link to the storage where the NFT content is stored is written to the NFT. The metadata of the NFT is also stored in the storage of the NFT management server 40. The information written in the metadata includes the product purchase date, the date the product purchase certificate was issued, and the purchase date of the NFT content (NFT issuance date).

[0135] Thus, the sales control unit 303 has functions as both an acquisition means and a generation means. The acquisition means acquires a 3D model and its associated information corresponding to the product purchased by the user. The associated information includes, for example, size information, which is reference information for the size of the product in the metaverse space. The generation means uses the acquired 3D model and associated information (e.g., size information) to generate (issue) an NFT (Non-Fungible Token) for the acquired 3D model. For example, the generation means manages the 3D model and associated information (size information) acquired from the content management server 30 so that it can be provided externally, and generates an NFT with the product purchaser as the owner.

[0136] Furthermore, the sales control unit 303 may generate NFTs for 3D models acquired from the IP holder (content management server 30) using not only size information but also full-body information and appearance information.

[0137] The provision control unit 304 is a means for performing control over the provision of NFT content and its associated information. When an external server (e.g., a metaverse server 60) accesses the storage according to the link described in the NFT of the NFT content, the provision control unit 304 provides the NFT content and associated information stored in the storage to the external server.

[0138] In other words, the provision control unit 304 has the function of a means of utilization, which controls the 3D model from which the NFT has been generated so that it can be used in the metaverse space. The provision control unit 304 provides the 3D model from which the NFT has been generated and its associated information to the metaverse server 60 in response to a request from the metaverse server 60. The provided 3D model and its associated information (e.g., size information) are used by the metaverse server 60.

[0139] The My Page Control Unit 305 is a means for controlling the user's account (My Page). The My Page Control Unit 305 has a function as an acquisition means for acquiring NFTs (Non-Fungible Tokens) issued when a user purchases a product, and a function as a display control means for displaying information about the acquired NFTs.

[0140] When a user logs into the marketplace, the My Page control unit 305 displays a My Page on the terminal 70 as shown in Figure 14.

[0141] As shown in Figure 14, when the Owned NFT button 71 is pressed (activated), the My Page Control Unit 305 displays a list of NFTs owned by the user in the NFT display area 72. The My Page Control Unit 305 accesses the user's wallet address and retrieves the NFTs owned by that user. The My Page Control Unit 305 uses the retrieved NFTs to generate a screen as shown in Figure 14.

[0142] When the settings button 73 is pressed, the My Page control unit 305 enables various settings related to My Page.

[0143] Furthermore, the My Page control unit 305 displays the user's icon in the icon display area 74 of the My Page. The My Page control unit 305 may also change the icons displayed in the icon display area 74 by changing the settings.

[0144] Here, the NFT platform provider may perform identity verification of the user when creating the user's account. For example, the user management unit 302 may perform identity verification using the user's selfie facial image and a facial image obtained from a passport or the like. The user management unit 302 may manage and remember users who have been verified as "authenticated users" and users who have not undergone this verification as "unauthenticated users."

[0145] The My Page control unit 305 may display on the My Page that a user who has logged into the account is an authenticated user. For example, as shown in Figure 14, the My Page control unit 305 may display an authentication mark 75 at the top of the icon display area 74. In this way, if a user is an authenticated user recognized by the NFT platform provider, the My Page control unit 305 may indicate in the NFT transaction history that the user is an authenticated user.

[0146] Alternatively, the My Page Control Unit 305 may calculate the transaction volume and transaction value of NFTs for each user over a predetermined period and assign a title or similar to each user according to the transaction volume. For example, the My Page Control Unit 305 may assign a title such as "Transaction Volume No. 1" to the user with the highest transaction volume (number of NFT sales and purchases).

[0147] Alternatively, the My Page control unit 305 may award a title such as "Transaction Amount No. 1" to the user with the highest transaction amount (total amount of NFTs sold and purchased) during a predetermined period.

[0148] The My Page control unit 305 may display the title on the My Page. For example, as shown in Figure 15, it may display a mark 76 corresponding to the title assigned to the user in place of or in addition to the authentication mark 75 displayed in the icon display area 74 of the My Page.

[0149] For example, the My Page control unit 305 displays a golden star as Mark 76 for users who have been given the title of Transaction Amount No. 1. In this way, the My Page control unit 305 may display titles given to users according to the total amount or value of NFTs they have traded.

[0150] Alternatively, the My Page control unit 305 may classify multiple users according to their NFT trading volume or transaction value and assign titles to the classified users. For example, the My Page control unit 305 may assign a title such as "Gold User" to the top 100 users with high trading volume. The My Page control unit 305 may also display a mark 76 corresponding to the Gold User on the My Page.

[0151] The My Page control unit 305 may display the tags set on the NFT. More specifically, the My Page control unit 305 may display tags (hashtags) for the NFTs listed on the My Page (NFTs displayed in the NFT display area 72).

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

[0153] Examples of NFT tags include the series name (IP name) of the game in which the character appears, the name of the game in which the character appears, the character's name, the time the character was acquired (e.g., a tag like #Season1), and the type of pose. Alternatively, examples of NFT tags include in-game titles (e.g., #LEV6, #SizeMAX, #DifferentColor, #LevelMAX), the market price of the same character (e.g., a tag like #SameCharacterExceeded10000Yen), and milestone numbers (e.g., #100thCharacter).

[0154] For example, as shown in Figure 16, when the My Page control unit 305 detects a predetermined action by the user on an NFT on the My Page (e.g., clicking on the NFT or moving the mouse), it displays the NFT's tag in a popup 77. Alternatively, the NFT's tag may be displayed at the bottom of the corresponding NFT. Note that tags set on the NFT platform may be displayed in the metaverse space, as will be described later.

[0155] When an NFT (an icon corresponding to an NFT) displayed in the NFT display area 72 is pressed, the My Page control unit 305 displays the detailed transaction history of that NFT. For example, when "NFT1" as shown in Figure 14 is pressed, the My Page control unit 305 displays a transaction history screen on the terminal 70 as shown in Figure 17.

[0156] As shown in Figure 17, the My Page control unit 305 displays a list of transaction history for NFTs selected by the user in the transaction history area 78. For the selected NFT, the My Page control unit 305 displays the purchase date, price, purchaser information (username), and the date on which the purchase certificate was issued for the underlying product. Furthermore, the My Page control unit 305 displays the NFT purchase date, price, and purchaser information, as well as the date, price, seller, and purchaser information at the time of the NFT transaction (resale). In this way, the My Page control unit 305 may display facts related to the purchase of the product as part of the NFT transaction history.

[0157] Furthermore, if an NFT is obtained by fulfilling conditions within the game, the My Page Control Unit 305 may display the date on which the conditions within the game were fulfilled, etc., on the transaction history screen.

[0158] In the transaction history, information about the user who purchased the product, the user who received a purchase certificate, and the user who purchased the NFT is listed in the TO column on the transaction history screen.

[0159] The My Page control unit 305 may display a message indicating that the user listed in the transaction history (the user listed in the FROM column and TO column) is an authenticated user. For example, as shown in Figure 17, the My Page control unit 305 may add a white star mark before the username.

[0160] Alternatively, the My Page control unit 305 may display titles or other symbols corresponding to the transaction volume or transaction amount on the transaction history screen.

[0161] Alternatively, the My Page control unit 305 may, when a username listed in the FROM column or elsewhere is clicked, display the type of user who clicked (authenticated user, unauthenticated user, title according to transaction volume, etc.) via a pop-up display or the like. Alternatively, the My Page control unit 305 may display a statement indicating that the user displayed in the transaction history is a celebrity (a famous person authenticated by the NFT platform provider).

[0162] Alternatively, the My Page control unit 305 may display the tags assigned to the NFT on the transaction history screen shown in Figure 17. For example, in the example in Figure 17, the tags may be displayed as a pop-up near "NFT1".

[0163] Furthermore, the My Page control unit 305 allows users to change the settings for displaying or hiding the star mark and other indicators that show the user is an authenticated user, as displayed in the FROM column, etc.

[0164] The NFT management server 40 may support cross-chain bridges (token bridges) for moving NFTs between different NFT platforms. In this case, the My Page control unit 305 may display the transaction history of NFTs before and after the cross-chain bridge in a distinguishable manner.

[0165] In other words, the NFT management server 40 may display the transaction history of NFTs received via the cross-chain bridge, including transactions before the bridge. For example, the transaction history up to the third line from the bottom in Figure 18 is the transaction history before the cross-chain bridge.

[0166] Furthermore, the My Page control unit 305 may display the fact that a cross-chain bridge has been implemented in the transaction history (see the second line from the top of the transaction history shown in Figure 18).

[0167] Furthermore, the My Page control unit 305 may display transactions before and after the cross-chain bridge in a way that allows the user to identify them. For example, the My Page control unit 305 may change the colors of the information displayed in the transaction history before and after the execution of the cross-chain bridge. In the example in Figure 18, transactions after the cross-chain bridge are displayed in bold.

[0168] Alternatively, the My Page control unit 305 may have a function to display NFT content owned by the user (e.g., 3D models of characters) in a pseudo-showcase. For example, when the setting button 73 shown in Figure 14 is pressed and a predetermined menu (e.g., pseudo-showcase) is selected, the My Page control unit 305 provides an interface as shown in Figure 19.

[0169] Figure 19 displays a list of NFTs (NFT content) owned by the user and a pseudo-showcase 90. For example, the pseudo-showcase 90 has 3 x 3 x 3 = 27 transparent rectangular blocks of a predetermined length (e.g., 2m) in the real coordinate system. In the pseudo-showcase 90, characters can be placed life-size at each vertex or center point of the blocks.

[0170] For example, a character set to be 2 meters tall in the real world will be placed within a rectangular prism, from floor to ceiling. In contrast, a character set to be 1 meter tall in the real world will be placed within a rectangular prism, at half the height of the floor to ceiling.

[0171] In Figure 19, when a user selects an NFT from the list and drags and drops it to any rectangular prism in the pseudo-showcase 90, the character corresponding to the selected NFT is placed on the rectangular prism where it was dropped. In the example in Figure 19, the character corresponding to NFT4 is placed on the upper left rectangular prism of the pseudo-showcase 90.

[0172] Furthermore, the My Page control unit 305 may allow selection of camera settings when placing a character in the pseudo-showcase 90. For example, in the case of an extremely large character, the My Page control unit 305 may allow selection of a camera viewpoint in which the character is leaning from the front to the back of the rectangular prism.

[0173] Thus, the My Page control unit 305 may display digital content (NFT-enabled digital content) corresponding to the user's purchased items in a pseudo-showcase. Furthermore, the pseudo-showcase 90, on which the character is placed, may be displayed anywhere on the My Page. For example, as shown in Figure 20, the pseudo-showcase 90 may be displayed on the My Page instead of the icon display area 74.

[0174] The memory unit 306 is a means for storing information necessary for the operation of the NFT management server 40.

[0175] [Metaverse Server] Figure 21 is a diagram showing an example of the processing configuration (processing module) of a metaverse server 60 according to the embodiment disclosed herein. Referring to Figure 21, the metaverse server 60 comprises a communication control unit 401, a user management unit 402, a metaverse control unit 403, and a storage unit 404.

[0176] The communication control unit 401 is a means for controlling communication with other devices. For example, the communication control unit 401 receives data (packets) from terminal 70. The communication control unit 401 also transmits data to terminal 70. The communication control unit 401 passes data received from other devices to other processing modules. The communication control unit 401 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data with other devices via the communication control unit 401. The communication control unit 401 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.

[0177] The User Management Unit 402 is a means of controlling and managing user-related matters.

[0178] The User Management Unit 402 obtains information such as name, gender, date of birth, login information (ID, password), and SNS information (e.g., follower IDs, followed by IDs) from users who access a designated website (e.g., a user registration site). Furthermore, the User Management Unit 402 obtains wallet addresses (wallet addresses for handling NFT content and cryptocurrencies). The User Management Unit 302 stores the obtained names, login information, wallet addresses, etc., in a designated database.

[0179] The metaverse control unit 403 is a means for controlling the metaverse (virtual space, virtual 3D space). Specifically, the metaverse control unit 403 realizes a metaverse platform. The metaverse control unit 403 generates a user avatar and makes the generated avatar move according to the user's actions.

[0180] <My Room> When a user creates an account on the metaverse server 60, the metaverse control unit 403 sets the user's "My Room" in the metaverse space. The metaverse control unit 403 generates a My Room for each user. When a user logs into the metaverse server 60, the metaverse control unit 403 displays the user's avatar in their My Room.

[0181] Users engage in various activities within their own rooms. For example, users can place a table or a television in their room.

[0182] Furthermore, users can access and use purchased NFT content in their own rooms (My Room).

[0183] For example, when a user who has logged into an account performs a predetermined action (for example, pressing the NFT content acquisition button), the metaverse control unit 403 acquires the NFT content owned by that user.

[0184] Specifically, the metaverse control unit 403 connects to the user's wallet using the user's wallet address. The sales control unit 303 retrieves the NFTs of each NFT content associated with the user's wallet.

[0185] When the metaverse control unit 403 acquires at least one NFT owned by the user, it uses the information obtained from the acquired NFT to display a list of NFT content owned by the user on the terminal 70. For example, the metaverse control unit 403 displays a GUI as shown in Figure 22 on the terminal 70, allowing the user to select NFT content they wish to bring into their own room (my room in the metaverse space).

[0186] When a user selects NFT content to bring into their My Room, the metaverse control unit 403 accesses the storage linked to the NFT corresponding to the NFT content acquired by the user, and retrieves the NFT content and associated information.

[0187] When NFT content and associated information are acquired, the metaverse control unit 403 makes use of the acquired NFT content and associated information in My Room.

[0188] For example, before and after acquiring NFT content, the metaverse control unit 403 obtains from the user how the NFT content will be used (usage format) selected by the user. For example, if NFT content (3D model) corresponding to a game or anime character is selected, the metaverse control unit 403 displays a GUI as shown in Figure 23 on the terminal 70.

[0189] The metaverse control unit 403 presents the user with options for how to use the NFT content, depending on the type of NFT content selected by the user. For example, if the user acquires character NFT content (3D model), the metaverse control unit 403 presents the user with options for how to use the NFT content, such as "display it in your room" or "use it as an avatar."

[0190] The metaverse control unit 403 utilizes the NFT content selected by the user on the metaverse in the usage format selected by the user.

[0191] Specifically, the metaverse control unit 403 controls the use of 3D character models obtained from IP holders via the NFT management server 40 in the metaverse space. More specifically, the metaverse control unit 403 converts the NFT-converted 3D models so that they can be used in the metaverse space.

[0192] In this process, the metaverse control unit 403 utilizes the 3D model of the character in the metaverse space, using not only the character's 3D model but also information regarding the character's size when modeling it in the metaverse space (size information).

[0193] In other words, the metaverse control unit 403 obtains the NFT content (a 3D model of a character) and its associated size information from the IP holder of the NFT content.

[0194] Here, size information refers to the reference size of a character's 3D model in the metaverse space. For example, size information is set to a value that assumes the character exists in the real world. For instance, a humanoid character might have size information = 180cm, while a monster character might have size information = 3m.

[0195] In this way, the metaverse control unit 403 acquires 3D shape information of a character used in a 3D game (data for displaying the character in 3D) and size information regarding the size of the character when it is brought into the metaverse space.

[0196] When the user obtains the 3D shape information and size information of a character purchased in the game, the metaverse control unit 403 uses this 3D shape information and size information to utilize the NFT-converted content (3D model of the character) in the metaverse space.

[0197] For example, the metaverse control unit 403 converts the acquired 3D model of the character into a 3D model having the size specified by the size information. In the metaverse space, the user's height is often used as the avatar's height, so the metaverse control unit 403 can determine the size of the character to be brought into the metaverse space using the ratio of the user's height to the avatar's height (number of pixels), and then convert it into a 3D model for use in the metaverse space.

[0198] For example, if the user's height is 180cm and the character's size information is set to 180cm, the metaverse control unit 403 should convert the NFT-converted 3D model into a 3D model (a character used in the metaverse space) that is the same height as the user's avatar.

[0199] Once a 3D model for use in the metaverse space is obtained, the metaverse control unit 403 uses the 3D model in the usage mode specified by the user.

[0200] For example, as mentioned above, when a user displays a character purchased in a game in their own room, the metaverse control unit 403 displays a screen on the terminal 70 as shown in Figure 24. In Figure 24, the user's My Room is shown, the user's avatar 79 is displayed, and the character 80 is placed in that room.

[0201] In this way, the metaverse control unit 403 assigns a My Room to each metaverse participant (a user who has logged into the metaverse server 60). Metaverse participants can then use NFT content in their own rooms.

[0202] The metaverse control unit 403 may change the size and placement of NFT objects in response to user operations, etc.

[0203] <Co-creation space> Here, the metaverse space realized by the metaverse control unit 403 consists of multiple spaces (fields where users are active), including My Room. Participants in the metaverse can move between these spaces and communicate with others.

[0204] The spaces that constitute the metaverse include spaces provided by metaverse operators and other organizations. These spaces are accessible to any metaverse participant.

[0205] In the following explanation, the space provided by the metaverse provider and accessible to all metaverse participants will be referred to as the "default space."

[0206] Metaverse users (users who have logged into Metaverse Server 60) can create communities consisting of multiple members. For example, high school or university classmates could form a community, or users with the same hobbies could create one.

[0207] The metaverse control unit 403 provides a function for creating communities for metaverse users. There are two types of communities in the metaverse space.

[0208] The first type of community is one in which participation (activity) by an unspecified number of users is not permitted. This first type of community is limited to users selected by the organizer (the user who created the community). This first type of community is referred to as a closed community.

[0209] The second type of community is one that can be joined by an unspecified number of users. In this second type of community, the organizer screens applicants, and only those who pass the screening can join. This second type of community is referred to as an open community.

[0210] When a metaverse user performs a predetermined action (for example, pressing the community creation button), the metaverse control unit 403 obtains the type of community (closed community, open community) that the user wishes to create.

[0211] Upon obtaining the community type, the metaverse control unit 403 selects the type of space (field) in which the participants of that community will be active. For example, the user might select a space type such as "island" or "town".

[0212] Once the type of space in which community participants are active is obtained, the metaverse control unit 403 obtains more detailed information about the community from the user (organizer). For example, the metaverse control unit 403 obtains the name of the community, the expected number of participants in the community, etc.

[0213] For example, the metaverse control unit 403 may acquire information such as: community type = closed, spatial type = island, community name = A University alumni association, and expected number of community members = 50. Alternatively, the metaverse control unit 403 may acquire information such as: community type = open, spatial type = town, community name = anime fan association, and expected number of community members = 100.

[0214] Upon obtaining the community type and the expected number of participants, the metaverse control unit 403 generates a space (field) in the metaverse space with an area corresponding to the expected number of participants. For example, the area of ​​the space allocated to a community with an expected number of participants is twice the area of ​​the space allocated to a community with an expected number of participants.

[0215] For example, in the above example, the metaverse control unit 403 generates a space where 50 users who belong to the community "A University Alumni Gathering" can be active. Alternatively, the metaverse control unit 403 generates a space where 100 users who belong to the community "Anime Fan Gathering" can be active.

[0216] Members of each community can operate within the space generated by the metaverse control unit 403. For example, members of the community "Anime Lovers' Gathering" can move to the community's space and immediately meet other people who like anime, and enjoy conversations about anime. In other words, metaverse users can easily meet others with the same interests in the space assigned to their community. Because users with the same interests are nearby, spontaneous conversations can easily occur.

[0217] Furthermore, members of each community can edit (create and develop) the space assigned to their community. For example, if the space is an "island," members can create a forest by planting trees. Or, if the space is a "town," members can lay roads.

[0218] In this way, community members cooperate with each other to create a single space. From this perspective, the space assigned to a community is referred to as a "co-creation space." The metaverse control unit 403 generates a co-creation space that can be edited by members of each community to which at least one user belongs.

[0219] The concepts of My Room, Default Space, and Co-creation Space are illustrated in Figure 25. As shown in Figure 25, My Room 81 is generated for each of the multiple metaverse participants in the metaverse space.

[0220] Furthermore, the metaverse control unit 403 generates a default space 82 that any metaverse participant can participate in (engage in). Note that the default space does not have the concept of participants creating the space themselves. Information and guidance from the metaverse provider are provided within the default space.

[0221] Furthermore, the metaverse control unit 403 generates co-creation spaces 83 and 84 corresponding to communities created by users (for example, a group of graduates from University A, a group of anime fans). Only members of these co-creation spaces can participate in activities within them.

[0222] When a co-creation space corresponding to a community is generated, the metaverse control unit 403 assigns an address to the generated co-creation space.

[0223] The organizer of a closed community will notify users who wish to join the community of the URL (Uniform Resource Locator) of the address assigned above. For example, the organizer will notify other users of this URL using a social networking service (SNS) or email. Users who have obtained the URL to join the closed community can join the community by accessing the metaverse server 60 according to that URL.

[0224] The metaverse control unit 403 identifies the community to which the user belongs based on the address accessed by the user. The metaverse control unit 403 stores the user's (the user who accessed the URL) ID and other information in a database prepared for each community. Once the ID is stored in the database, the user is treated as a member (participant) of the community.

[0225] Furthermore, if the number of community participants exceeds the number of participants set by the organizer, the metaverse control unit 403 may refuse participation of new users, or may expand the number of participants with the organizer's consent.

[0226] The organizer of an open community recruits members to join the community. For example, the organizer posts their own information (such as the organizer's nickname), community information (such as the community's name), and a URL with the organizer's ID embedded in it (a URL to join the community) on a bulletin board set up in the default space.

[0227] When a user who has viewed the bulletin board accesses the URL, the metaverse control unit 403 identifies the organizer based on the ID embedded in the URL and connects the identified organizer and the person who wishes to join the community so that they can converse (chat).

[0228] The organizer engages in conversation with individuals who wish to join the open community and decides whether to allow or deny their participation. The metaverse control unit 403 retrieves the result of the organizer's decision (participation permitted, participation denied).

[0229] Once the organizer grants permission for participation, the metaverse control unit 403 stores the IDs and other information of the permitted users in the community management database.

[0230] Furthermore, when a co-creation space is created or when new members join the community, the metaverse control unit 403 assigns a location (space) that will serve as a base for the activities of the members (including the organizer) within the co-creation space. For example, the metaverse control unit 403 assigns an area within the co-creation space that will serve as the user's "home."

[0231] For example, when a new member joins a community where the spatial type is selected as "island," the metaverse control unit 403 assigns the region 85 shown in Figure 26 as the member's home (including the garden).

[0232] The metaverse control unit 403 may assign a location according to the wishes of the community participants, or it may automatically select an empty space in the co-creation area and automatically assign a "house" to that selected empty space.

[0233] For example, in a town-based co-creation space, each member has their own residence, and friends can live on opposite sides of the road. Alternatively, in an island-based co-creation space, there are multiple living spaces on a single island, and each member takes turns choosing their preferred living space (each member selects their preferred location as their living space).

[0234] The metaverse control unit 403 places an exterior view corresponding to the member's My Room in each of the multiple co-creation spaces in which the user is a member. For example, the metaverse control unit 403 places My Home 87, which has the exterior of a house as shown in Figure 26, in correspondence with the My Room of a community participant.

[0235] Furthermore, metaverse users can belong to multiple communities. For example, one metaverse user may belong to a community of friends from university, a community of colleagues from work, a community of people with the same hobbies, and so on.

[0236] If a single metaverse user belongs to multiple communities, their "home" will be assigned to each of the co-creation spaces corresponding to the multiple communities they participate in. In the example above, a "home" with a house exterior will be assigned to each of the co-creation spaces corresponding to the community of college friends, the community of colleagues, and the community of people with the same hobbies.

[0237] The metaverse control unit 403 uses a database that manages each community to store the location of the home (my home) assigned to each user.

[0238] <Moving to the co-creation space> The metaverse control unit 403 enables users within their My Room to move to a co-creation space corresponding to the community to which they belong, via an exit (entrance / exit) installed inside their My Room. Furthermore, the metaverse control unit 403 enables the user's avatar to move into their My Room via an entrance (entrance / exit) installed on the exterior of their My Room (My Home).

[0239] Specifically, when a user logs into an account on the metaverse server 60, the metaverse control unit 403 sets the user's My Room as the starting point for activities in the metaverse space. The metaverse control unit 403 then displays the user's avatar within the user's My Room.

[0240] My Room has an exit for accessing the default space or the co-creation space. For example, as shown in Figure 27, door 88 is installed inside My Room.

[0241] For example, when a user (user's avatar 79) moves in front of door 88, the metaverse control unit 403 uses a GUI as shown in Figure 28 to obtain the desired destination space (community) for the user.

[0242] For example, in Figure 28, when a user selects "Anime Fan Gathering," the metaverse control unit 403 moves the user (avatar) to the co-creation space of the anime fan community.

[0243] For example, if area 85 is assigned to the user in Figure 26, the metaverse control unit 403 moves the user's avatar to area 85 (the user's garden). Alternatively, if there is a shared facility (e.g., a park) in the co-creation space, the metaverse control unit 403 may move the user to that shared facility.

[0244] <Activities within the co-creation space> Users (community members) move around within the co-creation space and converse with people they encounter. Alternatively, users can create (edit) their own gardens or shared facilities. For example, users can plant trees in their gardens. Gardens and shared facilities may have trees planted or buildings installed by default.

[0245] In this case, users can place NFT objects in the co-creation space, just as they can in their personal rooms. For example, as shown in Figure 29, a user can place character 89 within the co-creation space.

[0246] The metaverse control unit 403 may also display information about NFT objects placed in the co-creation space near the NFT objects. For example, the metaverse control unit 403 may display tag information related to character 89 (e.g., the title of the anime in which character 89 appears, or the name of character 89). In other words, the metaverse control unit 403 may automatically reflect (display) the tag information of NFT objects in the co-creation space.

[0247] <Moving from the co-creation space> When an activity in a co-creation space ends, the user (community member) leaves that space. For example, a user might leave a co-creation space to move to another community's co-creation space or the default space.

[0248] In this case, the user moves in front of their own home (the exterior of their room). The home has an entrance for entering the room. For example, as shown in Figure 30, each home has a door 91.

[0249] Users who wish to leave the co-creation space move to the door in front of their My Home. When the metaverse control unit 403 detects the user (user's avatar) who has moved to the door in front of My Home, it moves that user into My Room.

[0250] Users who wish to move to another co-creation space move to the exit in their My Room (door 88 shown in Figure 27). The metaverse control unit 403 obtains the user's desired destination using a GUI as shown in Figure 28.

[0251] As described above, the metaverse control unit 403 has the functions of a My Room generation means and a co-creation space control means. The My Room generation means generates a My Room for each user. The co-creation space control means generates a co-creation space that can be edited by members belonging to each community to which the user belongs. The co-creation space control means places the exterior of the My Room in each of the multiple co-creation spaces and enables the user's avatar to move into the My Room from an entrance provided on the exterior of the My Room. Furthermore, the co-creation space control means enables the user's avatar inside the My Room to move to a co-creation space corresponding to the community to which the user belongs from an exit provided inside the My Room.

[0252] As described above, NFT objects (objects corresponding to content that has been converted into NFTs and authorized by the rights holder) may be placed in the co-creation space. In this case, the metaverse control unit 403 may also function as a display means that displays information about the owner of the NFT object in a way that is visible to users staying in the co-creation space. For example, the metaverse control unit 403 may display the nickname of the user who placed the NFT object near the NFT object.

[0253] Alternatively, the metaverse control unit 403 may limit the number of NFT objects that can be placed in the co-creation space according to the number of members belonging to the community. For example, if there are 10 metaverses belonging to the community, the metaverse control unit 403 may allow 10 NFT objects to be placed. Or, if there are 100 metaverses belonging to the community, the metaverse control unit 403 may allow 100 NFT objects to be placed.

[0254] Alternatively, the metaverse control unit 403 may hide NFT objects placed in the co-creation space depending on the number of members staying in the co-creation space. For example, if the number of members staying in the co-creation space is five or less, the metaverse control unit 403 will display the NFT objects placed in the co-creation space. Conversely, if the number of members staying in the co-creation space is more than five, the metaverse control unit 403 will hide the NFT objects placed in the co-creation space.

[0255] <Opening of the co-creation space> As mentioned above, only community members can visit the co-creation space. However, the co-creation space may be made available to an unspecified number of users at the discretion of the organizer. Specifically, the metaverse control unit 403 generates a copy of the co-creation space designated by the organizer in the metaverse space in response to instructions from the organizer (specific operations performed by the organizer).

[0256] For example, if the organizer of an anime fan community wishes to make the community's co-creation space public, the metaverse control unit 403 generates a copy of the co-creation space corresponding to the anime fan community in the metaverse space.

[0257] In the following explanation, a copy of the co-creation space will be referred to as the "duplicate space." The duplicate space contains each member's personal home, NFT objects placed by each member, and other similar items.

[0258] Users who are not members of the community move from the default space provided by the metaverse server 60 to the replicated space. For example, the metaverse control unit 403 sets up a spot in the default space for users to move to the replicated space, along with guidance for the community corresponding to that replicated space. Users (avatars) who wish to move to the replicated space stand on this spot.

[0259] The metaverse control unit 403 moves the user standing on the spot into the replication space.

[0260] The user (avatar) can move within the replicated space and talk to the people encountered, just like in the co-creation space. Also, the user can view the NFT objects placed in the replicated space. However, a user who visits the replicated space cannot perform editing operations (e.g., placing an NFT object of a character) within the space.

[0261] In this way, the metaverse control unit 403 functions as a replicated space control means that generates a replicated space which is a replication of the co-creation space and can be accessed by users other than the members of the corresponding community.

[0262] <Comment in the co-creation space> The metaverse control unit 403 may be provided with a function that allows a user (member of the community) who visits the co-creation space to leave a comment on an object placed in the co-creation space, especially an NFT object. More specifically, the metaverse control unit 403 has a function of associating and storing the current position of a user who visits the co-creation space with the comment of the user.

[0263] For example, in FIG. 31, the user 94 can leave a comment near the character 93. For example, when the user 94 approaches near the character 93 (a predetermined range centered on the position of the character 93), the metaverse control unit 403 uses a GUI or the like to obtain the user 94's desire to leave a comment on the character 93, view other people's comments, or not.

[0264] If the user 94 wishes to leave a comment, the metaverse control unit 403 displays a signboard (virtual signboard) for inputting the comment.

[0265] The user 94 inputs the comment by voice or handwriting. In this case, the metaverse control unit 403 manages that the comment left by the user 94 is a comment on the character 93.

[0266] Specifically, the metaverse control unit 403 stores various information in a database that manages comments on NFT objects. For example, the metaverse control unit 403 manages and stores information about the owner of the NFT object, the location of the NFT object, information about the user who commented on the NFT object (e.g., ID), and the content of the comment.

[0267] More specifically, the metaverse control unit 403 stores in the database the position of the user (first user) in the 3D space (the co-creation space generated in the metaverse space) at the time the comment was made, and the date and time the comment was made, associating them with the comment.

[0268] When a user who has moved near an NFT object wishes to view comments from other users, the metaverse control unit 403 accesses the database that manages comments for NFT objects and displays the comments stored for the corresponding NFT object.

[0269] Specifically, when the metaverse control unit 403 receives a request to display comments from a user in 3D space (a second user), it selects at least one comment from among multiple comments stored in the database. More specifically, the metaverse control unit 403 selects at least one comment from among multiple stored comments based on the positions associated with the multiple stored comments and the position of the user who made the comment display request in 3D space.

[0270] For example, as shown in Figure 32, if user 95 wishes to view comments near character 93, the metaverse control unit 403 selects a comment from among several comments that is associated with a location substantially the same as user 95's location.

[0271] The metaverse control unit 403 displays at least one selected comment in a way that is visible to the user. For example, in the examples in Figures 31 and 32, comments including the comment from user 94 are presented to user 95.

[0272] Users (community members) who visit the co-creation space can see what others thought of the objects (NFT objects) near them.

[0273] Thus, the metaverse control unit 403 includes the functions of a comment receiving means, a display request receiving means, a comment selection means, and a display control means. The comment receiving means receives comments from a first user using the 3D space (metaverse space, co-creation space). The display request receiving means receives comment display requests from a second user in the 3D space. The comment selection means selects at least one comment from among multiple stored comments based on the position associated with multiple stored comments and the position of the second user in the 3D space who made the comment display request. The display control means displays the selected at least one comment so that the second user can see it. The position of the first user in the 3D space when the comment was made and the date and time when the comment was made are stored in the database (storage unit 404) in association with the comment.

[0274] Furthermore, the metaverse control unit 403 may select comments to present to the second user based on the date and time the comments were left. For example, the metaverse control unit 403 may prioritize displaying newer comments. That is, the metaverse control unit 403 may select at least one comment from among multiple stored comments based on the location and date and time associated with the multiple stored comments and the second user's location in 3D space.

[0275] The metaverse control unit 403 may, if multiple users have left comments on a single NFT object, display the users who made the comments in a way that allows comment viewers to identify them. The metaverse control unit 403 may also make comments made by other users identifiable to comment viewers.

[0276] For example, the metaverse control unit 403 may enclose and display a comment from one user, or display comments using different colors depending on the user. Alternatively, the metaverse control unit 403 may automatically assign a color to each user when they leave a comment, and store the comments obtained from that user in association with the assigned color.

[0277] <Tipping function> The metaverse control unit 403 may also include a mechanism (tipping function) that allows commenters to give money to the organizers of the co-creation space, the owners of NFT objects, and the rights holders of NFT objects.

[0278] For example, the metaverse control unit 403 displays a "tip button" in the GUI when retrieving comments from users. When this tip button is pressed, the metaverse control unit 403 retrieves the tip amount from the user (comment poster). The metaverse control unit 403 then transfers the retrieved amount from the tipping user's wallet (cryptocurrency wallet) to the community organizer's wallet.

[0279] Alternatively, tips made in the co-creation space may be paid to the owner or rights holder (author) of the NFT object, in addition to or on behalf of the community organizer. In this case, the metaverse control unit 403 transfers the amount, divided according to a predetermined ratio, to the wallets of the community organizer, the owner of the NFT object, the rights holder of the NFT object, etc. Note that the wallet of the rights holder of the NFT object may be set in the accompanying information of the NFT content or in the corresponding NFT.

[0280] Alternatively, the tip distribution rate may be automatically determined by the metaverse control unit 403. For example, the metaverse control unit 403 may determine the distribution rate using a learning model obtained by machine learning. For example, the metaverse control unit 403 inputs a comment with a tip into the learning model and obtains an evaluation of the comment (for example, a three-level evaluation of good, bad, and average). The metaverse control unit 403 determines the distribution rate based on the obtained evaluation of the comment. For example, the metaverse control unit 403 determines the distribution rate so that if the evaluation of the comment is high, a larger amount of the tip is distributed to the rights holder.

[0281] Alternatively, the metaverse control unit 403 may allow the commenter to determine the distribution rate when distributing tips. For example, the metaverse control unit 403 may propose a distribution rate to the commenter, and the commenter may arrange the proposed distribution rate within a predetermined range.

[0282] The metaverse control unit 403 stores the ID of the user who made the tip, the comment, and the tip amount in a database that manages comments. The metaverse control unit 403 may also write comments made to NFT objects to the NFT's metadata. The metaverse control unit 403 may store the date and time the comment was left, the name of the user who left the comment, the amount, and the content of the comment in the NFT object's metadata.

[0283] Furthermore, tips may be made not only in the co-creation space but also in the replication space. In this case, the metaverse control unit 403 may distribute the tips made in the replication space to the owners and rights holders of the NFT objects.

[0284] When displaying comments left on an NFT object, the metaverse control unit 403 may prioritize displaying comments that include tips. Alternatively, the metaverse control unit 403 may prioritize comments that include larger tips among the comments that include tips.

[0285] For example, the metaverse control unit 403 does not allow comments with a tip to be overwritten by other comments, or delays overwriting by other comments. Alternatively, the metaverse control unit 403 may give preferential treatment such as prioritizing the display order of comments with a tip, displaying them in the front, or displaying them in large characters.

[0286] In this way, the metaverse control unit 403 may accept comments and money from a third user who uses the 3D space. In this case, the position of the third user in the 3D space, the date and time when the comment was made, and the amount of money received are stored in the database (storage unit 404) in association with the comment. The metaverse control unit 403 may select at least one or more comments from the plurality of stored comments based on the position associated with the plurality of stored comments, the position of the second user in the 3D space who requested the comment display, and the amount of money. Furthermore, the metaverse control unit 403 may display the selected one or more comments in an order based on the amount of money (the amount of the received tip) given together with each comment.

[0287] In addition, the metaverse control unit 403 may have a function as a distribution means. When the NFT object is placed in the 3D space, the metaverse control unit 403 may distribute the money (tip) received together with the comment made within a predetermined range from the placement position of the object in the 3D space to the right holder at a predetermined distribution rate.

[0288] The metaverse control unit 403 may determine criteria for displaying comments made for each NFT object installed in the co-creation space. For example, the metaverse control unit 403 gives priority to displaying comments with a newer comment posting date and time for comments on character A. Alternatively, the metaverse control unit 403 gives priority to displaying comments with a larger tip amount for comments on character B.

[0289] Thus, the metaverse control unit 403 may display one or more comments selected according to a priority based on the location of the user who wishes to view the comments (location of the NFT object), in a manner that is visible to a second user.

[0290] The metaverse control unit 403 may display only comments from comment posters related to the user who wishes to view the comments. For example, the metaverse control unit 403 may display only comments from users that the user who wishes to view the comments follows or is followed by on SNS (Social Networking Service). Alternatively, the metaverse control unit 403 may prioritize displaying comments from users related to the comment viewer.

[0291] When retrieving or displaying comments, the metaverse control unit 403 may identify the target NFT object based on the direction the user (avatar) is looking. For example, if two characters are placed close together, and the user looks at the character on the right, the metaverse control unit 403 determines that the user wishes to leave or view comments for the character on the right.

[0292] Thus, the metaverse control unit 403 may use not only the user's location but also the direction the user is looking both when registering (retrieving) and displaying comments. That is, the direction the first user is facing in the co-creation space at the time the comment is made is stored in the database in association with the comment. Based on the location, date and time and direction associated with the multiple stored comments and the location and direction of the second user in the co-creation space, the metaverse control unit 403 selects at least one comment from among the multiple stored comments.

[0293] Detailed explanations regarding the implementation of basic functions of the metaverse space (metaverse platform) by the metaverse control unit 403 (e.g., avatar movement and conversation between avatars) are omitted. This is because the implementation of such functions is obvious to those skilled in the art and is outside the scope of the present disclosure.

[0294] The memory unit 404 is a means for storing information necessary for the operation of the metaverse server 60. For example, the memory unit 404 stores information regarding comments on NFT objects using a predetermined database.

[0295] [Service Server] A detailed explanation of the configuration and operation of service server 10 is omitted. Service server 10-1 only needs to store the purchase history of the product sold to the user. Alternatively, service server 10-2 only needs to store the user's game play history (including play history such as purchase history of characters and items).

[0296] [Wallet Server] A detailed explanation of the configuration and operation of the wallet server 50 is omitted. The wallet server 50 only needs to issue wallet addresses to users.

[0297] [Content Management Server] A detailed explanation of the configuration and operation of the content management server 30 is omitted. The content management server 30 stores the digital content and associated information of each product handled by the company, and transmits the digital content and associated information in accordance with requests from the NFT management server 40.

[0298] More specifically, if the digital content, etc., associated with the product code included in the content provision request does not exist, the content management server 30 sends a negative response to the NFT management server 40 indicating this. If the digital content, etc., associated with the product code included in the content provision request does exist, the content management server 30 sends an affirmative response to the NFT management server 40 indicating this, which includes the digital content and its associated information.

[0299] Furthermore, figure manufacturers and other companies register their product codes, digital content, and associated information with their products in advance on the content management server 30.

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

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

[0302] Figure 33 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 33.

[0303] When a user requests the issuance of a product purchase certificate, the NFT management server 40 retrieves the product purchase certificate from the user's wallet (step S31).

[0304] Furthermore, the NFT management server 40 obtains the digital content and associated information of the product corresponding to the product purchase certificate that the user wishes to issue from the content management server 30, and issues an NFT corresponding to the obtained digital content (step S32).

[0305] When a user requests to use NFT content in the metaverse space, the metaverse server 60 obtains the NFT content and associated information from the NFT management server 40 (step S33).

[0306] The metaverse server 60 uses the acquired NFT content and associated information to make the NFT content available in the metaverse space (step S34).

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

[0308] <Example 1> The NFT management server 40 may display a history of chats made with NFT content, particularly comments with tips. In this case, the My Page control unit 305 may display a history of comments related to the NFT selected by the user in response to the press of the comment history button 99, as shown in Figure 34.

[0309] Thus, NFTs are configured with comments from users of the metaverse space regarding the NFT placed in the metaverse space, and the My Page control unit 305 may display the comments on the NFT separately from the transaction history of the NFT. In particular, the My Page control unit 305 may display the history of comments with tips that originated within a predetermined range from the placement location of the NFT object placed in the metaverse space.

[0310] <Modification 2> The NFT management server 40 may also have a function to update tags (hashtags) set on NFTs. In this case, the NFT management server 40 performs account linking with the service server 10-2 (game server). The My Page control unit 305 of the NFT management server 40 periodically logs into the game server using the login information of the game server.

[0311] If any NFTs owned by the user are related to games provided on the game server, the My Page Control Unit 305 retrieves character information, etc., corresponding to the NFT (obtained from play history, etc., stored in the game server account). If there are any tags set on the NFT that can be updated from the play history, etc., the My Page Control Unit 305 updates the tags displayed on the My Page, etc.

[0312] For example, if the strength (level) of a character set in an NFT is not at its maximum before accessing the game server but reaches its maximum as the game progresses, the My Page Control Unit 305 updates the tag related to the strength of that NFT to "#LevelMAX".

[0313] Alternatively, the My Page control unit 305 may allow users to view the setting date and time and update date and time for each tag. That is, users can find out when a tag was set and when it was updated. Alternatively, the My Page control unit 305 may allow users to select the tags to be displayed on the NFT being sold when they sell (list) an NFT.

[0314] <Variation 3> The My Page control unit 305 may set (add) a tag to an NFT that corresponds to the market price of NFTs of the same type as the NFT owned by the user (the average value of the trading prices of multiple NFTs). For example, if the average trading price of game character A is 1000 yen, the My Page control unit 305 will set a tag such as "#Market price 1000 yen" to the corresponding NFT. Alternatively, if the trading price of an NFT reaches a new high, the My Page control unit 305 may automatically display the updated price (trading price) as a tag.

[0315] <Modification 4> Titles may be assigned to NFTs depending on their use in the metaverse space. For example, the use of an NFT in an event held in the metaverse space may be set as a condition for assigning a title. For instance, if an event about the IP (game) to which an NFT belongs is held in the metaverse space, and the number of participants in the event exceeds a predetermined number, and the NFT content (a 3D model of a character) is placed at the event venue, the condition may be deemed to have been met.

[0316] In this case, NFT content installed at the event venue will be deemed to have contributed to the promotion of games, etc., and will be awarded a designated title. The awarded title may be displayed as a tag on your My Page, etc. For example, a tag such as "#EventContribution" will be displayed on your My Page or transaction history screen.

[0317] <Modification 5> The NFT (and its metadata) may contain information about the metaverse spaces (metaverse platforms) where the content corresponding to the NFT is available. For example, it may contain information indicating that NFT1 is available in metaverse space 1 and metaverse space 2, and NFT2 is available in metaverse space 2 and metaverse space 3. This information may be pre-configured by the IP holder.

[0318] The My Page control unit 305 may display information about the metaverse space where NFT-compatible content is available as a tag. For example, the My Page control unit 305 may display a tag such as "#Metaverse Space 1 and Metaverse Space 2 Compatible" on the My Page or transaction history screen.

[0319] <Variation 6> An NFT may contain information about the metaverse space in which it was used. For example, if NFT1, which is available in both metaverse space 1 and metaverse space 2, is used in metaverse space 1, this fact will be recorded in the NFT (the NFT's metadata).

[0320] The My Page control unit 305 may display information such as the user's metaverse space usage trends on the My Page, based on the history of how NFTs owned by the user have been used in the metaverse space.

[0321] For example, the My Page control unit 305 displays the name of the metaverse space that the user uses most frequently (the space where they use the most NFT content) near the icon display area 74. Alternatively, the My Page control unit 305 may display the name of the metaverse space that last utilized NFT content on the My Page.

[0322] <Example 7> The metaverse server 60 and the NFT management server 40 may be linked by account. In this case, the My Page control unit 305 may access the metaverse server 60 and obtain the IDs of users who have been set as friends in the metaverse space. The My Page control unit 305 may use the obtained IDs to search the database and identify the user (user of the NFT platform) corresponding to the obtained IDs.

[0323] The My Page control unit 305 may display information about other users who have been set as friends in the metaverse space on the My Page or transaction history screen.

[0324] Alternatively, the My Page control unit 305 may provide an interface for searching for other users who have been set as friends in the metaverse space. For example, when a user enters a username used in the metaverse space, the My Page control unit 305 may display the My Page of the NFT platform user corresponding to that username. The user can then view a list of NFTs owned by users who have been set as friends in the metaverse space.

[0325] Alternatively, the My Page control unit 305 may suggest that users who have been set as friends in the metaverse space also be set as friends on the NFT platform.

[0326] The metaverse server 60 may display friends who have been set as friends on the NFT platform in an identifiable manner within the metaverse space. Alternatively, the metaverse server 60 may provide an interface that allows searching for friends on the NFT platform within the metaverse space.

[0327] <Differentiation Example 8> The metaverse server 60 may allow users visiting the replication space to comment on objects (NFT objects). In this case, the metaverse control unit 403 may make comments made in the replication space viewable by users (community members) in the corresponding co-creation space. In this case, the metaverse control unit 403 may display comments made in the replication space and comments made in the co-creation space (this space) in a form that can be identified by the comment viewer.

[0328] The metaverse control unit 403 controls whether visitors can view not only regular comments but also comments with tips in both the co-creation space and the replication space.

[0329] In this case, the metaverse control unit 403 only needs to distinguish and store in the database that manages comments whether each comment was made in the replication space or the co-creation space.

[0330] <Modification 9> Metaverse Server 60 may allow administrators (community organizers) or NFT object rights holders to verify the validity of comments before they are made public in co-creation or replication spaces.

[0331] In this case, when a comment is registered for an NFT object, the metaverse control unit 403 sends the registered comment to the co-creation space organizer, etc. The organizer verifies the comment and returns the verification result (whether the comment is appropriate or inappropriate) to the metaverse server 60. The metaverse control unit 403 deletes and does not store comments that are determined to be inappropriate. Alternatively, the metaverse control unit 403 sets comments that are determined to be inappropriate to be unavailable for viewing.

[0332] Alternatively, if the organizer determines that a comment is extremely malicious, they will notify the metaverse server 60 of this. The metaverse control unit 403 will remove the user who left the malicious comment from the community if the user is a participant. Alternatively, the metaverse control unit 403 will prevent the user who left the malicious comment from re-entering the replication space.

[0333] Verification of the above comments may be performed automatically by the metaverse server 60. For example, the metaverse control unit 403 may use an LLM (Large Language Model) to determine whether the comment is appropriate or not. Alternatively, upon receiving a report from a user who has viewed a comment, the metaverse control unit 403 may request the organizer to verify the comment, or it may verify it automatically.

[0334] Alternatively, the metaverse control unit 403 may store the number of times each user has left an inappropriate comment, and remove or prohibit entry to users whose number of inappropriate comments reaches a predetermined value from the co-creation space.

[0335] Alternatively, if the metaverse server 60 performs comment validation, the criteria for determining whether a comment is appropriate may differ between the co-creation space and the replication space. Specifically, the metaverse control unit 403 may determine a comment to be appropriate in the replication space but inappropriate in the co-creation space (community). For example, the metaverse control unit 403 may use different LLMs for the co-creation space and the replication space to make the above determination, or it may make the above determination by changing the prompt input to the LLM.

[0336] <Variation 10> The metaverse server 60 may have a function to integrate multiple communities into one community. For example, the metaverse control unit 403 may integrate multiple communities into one community in response to requests from the organizers of each community.

[0337] In this case, the metaverse control unit 403 may link the corresponding co-creation spaces, or it may regenerate a co-creation space of a size corresponding to the number of participating members in the new community.

[0338] <Variation 11> The metaverse server 60 may have a function that enables community searching in the default space. For example, the metaverse control unit 403 may implement a search using information about NFT objects installed in the co-creation space corresponding to each community.

[0339] For example, a user who wants to find the co-creation space (corresponding community) where character A from game A is located can simply enter "game A, character A" into the search window provided by the metaverse control unit 403.

[0340] The metaverse control unit 403 should refer to the NFTs and associated information of the NFT objects installed in each co-creation space and present the co-creation space (community) where the above character is installed as a search result.

[0341] <Variation 12> The community organizer may set ownership of specific NFT content as a condition for joining the community. In this case, the organizer will inform the applicant of the above condition when reviewing their application. The applicant will specify the requested NFT content from among the NFT content they own. The metaverse control unit 403 will retrieve the specified NFT content and its associated information from the NFT management server 40 and present it to the organizer.

[0342] <Example 13> In the co-creation space, NFT content owned by members (audio and video data corresponding to CDs, DVDs, etc.) may be playable. In this case, the NFT content or its associated information may have a limit on the number of people who can view it simultaneously.

[0343] The metaverse control unit 403 plays NFT content if the number of viewers is less than the set number. Alternatively, the metaverse control unit 403 makes NFT content playable if the number of community members is less than the number of viewers set for the NFT content. For example, the metaverse control unit 403 implements controls such as preventing NFT content that can be played by 4 people or less from being brought into a co-creation space that can be accessed by 5 or more people.

[0344] <Example 14> A co-administrator may be appointed for the community and its co-creation space. For example, the community organizer (administrator) may designate a co-administrator. If the organizer is absent from the co-creation space, the metaverse control unit 403 may ask the co-administrator to review applicants for community participation, etc.

[0345] <Variation 15> The metaverse control unit 403 may display the view of the co-creation space set by the user on the window that allows the user to see outside from inside their My Room. Alternatively, the metaverse control unit 403 may display the view of the co-creation space the user visited most recently on the window.

[0346] <Variation 16> In co-creation and replication spaces, companies and other organizations may advertise. Revenue from such advertising may be distributed to community organizers, NFT object rights holders, etc.

[0347] <Example 17> In the above embodiment, the operation of the information processing system was explained using a game as an example of a service provided using a 3D model. However, services using 3D models are not limited to games. For example, providing a metaverse space is also included in services using 3D models.

[0348] In other words, NFT content such as products purchased by a user in the metaverse space may be sold to the user. That is, the service server 10 may have the functions of the metaverse server 60, or the metaverse server 60 may have the functions of the service server 10.

[0349] More specifically, NFT content (3D models) of products purchased in the first metaverse space may be used in the second metaverse space.

[0350] Furthermore, the content that can be converted into NFTs is not limited to characters in games or the metaverse; it could also include items such as weapons used in games, or buildings and other elements that appear in the metaverse.

[0351] <Variation 18> NFT content (3D models) may be sold based on characters obtained by users through paid lottery draws (so-called gacha) within the game.

[0352] Alternatively, if character appearances (so-called skins) are sold within the game, a 3D model of the character having the appearance of the sold skin may be sold as NFT content.

[0353] <Modification Example 19> Products corresponding to NFT content that users can purchase may include characters, items, etc., that the user has obtained for free within the game. In this case, the integrated management server 20 may request the user to pay a certificate issuance fee when issuing a certificate of purchase for such free-obtained characters, etc.

[0354] Alternatively, when the NFT management server 40 sells NFT content corresponding to characters, etc., that the user has acquired for free, it may request the user to pay an NFT issuance fee.

[0355] Alternatively, NFT content for certain characters, etc., may be sold (transferred) to users completely free of charge. In other words, the integrated management server 20 may not require users to pay a fee for issuing a purchase certificate, and the NFT management server 40 may not require users to pay an NFT issuance fee; free (no charge) NFT content may be sold to users.

[0356] <Modification 20> Even without a request from the user, NFT content may be automatically distributed to the product purchaser for all or part of the purchased product. In other words, NFT content may be distributed to the user free of charge without the user having to request the integrated management server 20 to issue a product purchase certificate.

[0357] In this case, the metaverse server 60 may use NFT content purchased by the user and NFT content distributed free of charge in the metaverse space without distinction. If NFT content is distributed free of charge, the metaverse server 60 may periodically or at predetermined intervals access the user's wallet to determine whether or not newly distributed NFT content exists. If newly distributed NFT content exists, the metaverse server 60 may inquire with the user about the availability of such NFT content.

[0358] <Variation 21> In the above embodiment, the integrated management server 20 was described as obtaining product purchase history and game play history by logging into the service server 10, which is linked to the account. However, the integrated management server 20 may also obtain purchase history and play history from the service server 10 without linking accounts. For example, when a user purchases a product, the service server 10 sends information about the purchased product and the user's wallet address to the integrated management server 20. The integrated management server 20 can then identify the user using the received wallet address and store the purchase history in the identified user's account.

[0359] <Modification 22> In the above embodiment, the case in which the integrated management server 20 issues a product purchase certificate in response to a request from a user was described. However, the integrated management server 20 may also issue a product purchase certificate in response to obtaining the product purchase history from the service server 10. That is, the purchase certificate control unit 203 of the integrated management server 20 may issue a product purchase certificate automatically.

[0360] <Modification 23> In the above embodiment, the case in which the integrated management server 20 issues a product purchase certificate as an SBT (Service-Based Purchase Certificate) was described. However, the integrated management server 20 may issue product purchase certificates in other formats.

[0361] Specifically, the purchase certificate control unit 203 of the integrated management server 20 may issue a digital certificate using a public key infrastructure (PKI) as a product purchase certificate. Alternatively, the purchase certificate control unit 203 may issue a verifiable credential certificate (VCs) whose contents can be verified online as a product purchase certificate.

[0362] When a digital certificate or credential certificate is issued as proof of purchase, the NFT management server 40 verifies the electronic signature attached to these certificates. If the electronic signature verification is successful, the NFT management server 40 issues an NFT of the NFT content.

[0363] Furthermore, if digital certificates or credential certificates issued via PKI are used as proof of purchase, these certificates may be managed by the user's wallet or by an account on the integrated management server 20 or the NFT management server 40.

[0364] When the integrated management server 20 manages the user's product purchase certificate, the NFT management server 40 requests the integrated management server 20 to provide the product purchase certificate. Specifically, the sales control unit 303 of the NFT management server 40 sends the user's wallet address to the integrated management server 20. The integrated management server 20 uses the wallet address to identify the user who wishes to purchase NFT content and sends the product purchase certificate stored in the account of the identified user to the NFT management server 40.

[0365] When the NFT management server 40 manages a user's product purchase certificate, the purchase certificate control unit 203 of the integrated management server 20 sends the issued product purchase certificate along with the user's wallet address to the NFT management server 40. The user management unit 202 of the NFT management server 40 identifies the user who received the product purchase certificate using the wallet address and stores the received product purchase certificate in the account of the identified user.

[0366] <Modification 24> The system configuration shown in Figure 3 is illustrative. For example, an integrated management server 20 operated by a platform provider may provide a wallet service. That is, the integrated management server 20 may also have the functionality of a wallet server 50.

[0367] Alternatively, the above embodiment described a case in which the NFT management server 40 issues NFTs of NFT content. However, the integrated management server 20 may issue NFTs of NFT content. That is, the integrated management server 20 may have the same functions as the NFT management server 40.

[0368] As described above, the NFT management server 40, which is an NFT management device, acquires NFTs issued in response to a user's purchase of a product. The NFT management server 40 displays information about the acquired NFT. For example, the NFT management server 40 displays the purchase history of the product that formed the basis for the issuance of the NFT as part of the NFT's transaction history. Alternatively, the NFT management server 40 displays the tags set on the NFT. As a result, users can easily manage the NFTs they own. In other words, the convenience for users who own NFTs issued through product purchases is improved.

[0369] Next, we will describe the hardware of each device that makes up the information processing system. Figure 35 shows an example of the hardware configuration of the NFT management server 40.

[0370] The NFT management server 40 can be configured using an information processing device (a so-called computer), and has the configuration illustrated in Figure 35. For example, the NFT management server 40 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.

[0371] However, the configuration shown in Figure 35 is not intended to limit the hardware configuration of the NFT management server 40. The NFT management server 40 may include hardware not shown, and may not have an input / output interface 313 if necessary. Furthermore, the number of processors 311, etc., included in the NFT management server 40 is not limited to the example shown in Figure 35; for example, multiple processors 311 may be included in the NFT management server 40.

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

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

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

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

[0376] The functions of the NFT management server 40 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.

[0377] Furthermore, the service server 10, integrated management server 20, content management server 30, wallet server 50, and metaverse server 60 can also be configured using information processing devices, similar to the NFT management server 40. Since their basic hardware configurations are identical to those of the NFT management server 40, a detailed explanation is omitted.

[0378] The metaverse server 60, 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 metaverse server 60 executes a control method for the metaverse server 60 using this program. Similarly, the NFT management server 40 is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the NFT management server 40 executes a control method for the NFT management server 40 using this program.

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

[0380] In the above embodiment, the configuration and operation of the information processing system were explained using the case where NFT-enabled content is used in the metaverse space as an example. However, digital content used in the metaverse space does not have to be NFT-enabled. If a user has the authority to use a product in the metaverse space, the metaverse server 60 may use the digital content (3D model) corresponding to that product in the metaverse space. In this case, the metaverse server 60 may obtain a product purchase certificate from the user's wallet and request the content management server 30 to provide the digital content corresponding to the product code described in the product purchase certificate. For example, with respect to products such as CDs and DVDs, the appearance information and genre information of the CD, etc. may be provided to the metaverse server 60 free of charge as part of a service provided by the IP holder of the product. In this case, the sound data and video data of the CD, DVD, etc. may also be provided free of charge or for a fee.

[0381] In the above embodiment, it was explained that the user logs in to the e-commerce site or game server via the integrated management server 20. However, the user may log in to the e-commerce site, etc., directly.

[0382] The above embodiment described a case where the integrated management server 20 issues a product purchase certificate. However, the e-commerce site or game server where the user purchased the product may also issue the product purchase certificate.

[0383] In the above embodiment, when a user wishes to purchase NFT content, the NFT management server 40 verifies the product purchase certificate corresponding to the product selected by the user. However, the NFT management server 40 may also perform prior verification for each of the multiple product purchase certificates owned by the user and display a list of products for which the user can purchase NFT content. That is, the NFT management server 40 may exclude NFT content that the user cannot purchase and enable the user to select NFT content (selection of NFT content to purchase) using a GUI similar to that shown in Figure 13.

[0384] In the above embodiment, the case in which the NFT management server 40 stores the main data (actual data) and associated information of the NFT content was described. However, the main data of the NFT content may also be stored in the IP holder's content management server 30 or in the integrated management server 20. Alternatively, the main data of the NFT content may be stored in the blockchain. Alternatively, the associated information of the NFT content may be described in the NFT's metadata.

[0385] The integrated management server 20 may manage the issuance status of product purchase certificates (purchase status of NFT content) for each user's account. By managing the issuance status of product purchase certificates for users, the integrated management server 20 may display products for which certificates have not yet been issued and products for which certificates have been issued in the GUI shown in Figure 10 in a way that allows users to distinguish between them. For example, the integrated management server 20 may display "Certificate Issued" near the product name (product name) for which a product purchase certificate has been issued. Alternatively, the integrated management server 20 may display the title of a product for which a product purchase certificate has not been issued in bold.

[0386] The integrated management server 20 may perform user authentication before issuing a product purchase certificate. For example, if the integrated management server 20 successfully performs biometric authentication of a user who wishes to issue a product purchase certificate, it may display a GUI as shown in Figure 10 on the terminal 70. In this case, the integrated management server 20 obtains the user's (account holder's) biometric information (e.g., facial image) when the user's account is created. When a user (a user logged into the account) wishes to issue a product purchase certificate, the integrated management server 20 obtains the user's biometric information via the terminal 70. For example, the integrated management server 20 instructs the user to take a selfie using the terminal 70. The terminal 70 transmits the obtained biometric information to the integrated management server 20. If the biometric information stored in the account and the biometric information obtained from the terminal 70 substantially match, the integrated management server 20 determines that it has successfully authenticated the user who wishes to issue a product purchase certificate. Upon successful authentication of the user who wishes to issue a product purchase certificate, the integrated management server 20 displays the GUI shown in Figure 10 on the terminal 70.

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

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

[0389] As described above, the industrial applicability of the present invention is clear, and it is particularly suitable for use in information processing systems that sell digital content corresponding to products purchased by users.

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

[0391] [Note 1] The means of obtaining an NFT (Non-Fungible Token) issued when a user purchases a product, A display control means for displaying the information related to the acquired NFT, An NFT management device equipped with the following features.

[0392] [Note 2] The NFT management device according to Appendix 1, wherein the display control means displays the facts relating to the purchase of the product as part of the transaction history of the NFT, in a manner distinguishable from the issuance history of the NFT.

[0393] [Note 3] The NFT management device as described in Appendix 1, wherein the display control means displays in the transaction history of the NFT that the user is an authenticated user recognized by the NFT platform provider.

[0394] [Note 4] The NFT management device described in Appendix 1, wherein the display control means displays a title given to the user according to the total amount or total value of NFTs traded by the user.

[0395] [Note 5] The display control means is an NFT management device as described in Appendix 1, which displays the transaction history of the NFT before and after the cross-chain bridge in a distinguishable manner.

[0396] [Note 6] The aforementioned NFT has comments from users of the metaverse space set up for the NFT in the metaverse space. The display control means is an NFT management device as described in Appendix 1, which displays comments on the NFT separately from the transaction history of the NFT.

[0397] [Note 7] The display control means is an NFT management device as described in Appendix 1, which displays the tags set on the NFT.

[0398] [Note 8] The display control means is an NFT management device as described in Appendix 1, which displays digital content corresponding to the product in a pseudo-showcase.

[0399] [Note 9] In the NFT management device, The user obtains an NFT (Non-Fungible Token) issued when they purchase a product. A control method for an NFT management device that displays information about the acquired NFTs.

[0400] [Note 10] The computer installed in the NFT management device, The process of obtaining an NFT (Non-Fungible Token) issued when a user purchases a product, The process of displaying the information related to the acquired NFT, A program to execute.

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

[0402] Furthermore, each disclosure of the above-mentioned prior art documents cited herein is incorporated herein by reference. Although 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 are possible without departing from the scope and spirit of the present invention. That is, the present invention naturally includes the entire disclosure, including the claims, and various modifications and alterations that can be made by those skilled in the art in accordance with the technical idea. [Explanation of symbols]

[0403] 10 Service Servers 10-1 Service Server 10-2 Service Server 20. Integrated Management Server 30 Content Management Server 40 NFT Management Server 50 Wallet Servers 60 Metaverse Servers 70 devices 71 NFT buttons owned 72 NFT display area 73 Settings button 74 Icon display area 75 Certification Marks 76 Mark 77 Pop-up 78 Transaction History Area 79 Avatar 80 characters 81 My Room 82 Default Space 83 Co-creation space 84 Co-creation space 85 areas 87 My Home 88 doors 89 characters 90 Simulated Showcase 91 doors 93 characters 94 User 95 User 99 Comment History Button 100 NFT management device 101 Acquisition method 102 Display control means 201 Communication Control Unit 202 User Management Department 203 Purchase Certificate Control Unit 204 Storage section 301 Communication Control Unit 302 User Management Department 303 Sales Control Unit 304 Service Control Unit 305 My Page Control Unit 306 Storage section 311 Processors 312 memory 313 Input / Output Interfaces 314 Communication Interface 401 Communication Control Unit 402 User Management Department 403 Metaverse Control Unit 404 Storage section

Claims

1. A means of obtaining NFTs (Non-Fungible Tokens) issued when a user purchases a product, A display control means for displaying the information related to the acquired NFT, An NFT management device equipped with the following features.

2. The NFT management device according to claim 1, wherein the display control means displays the facts relating to the purchase of the product as part of the transaction history of the NFT, in a manner distinguishable from the issuance history of the NFT.

3. The NFT management device according to claim 1, wherein the display control means displays in the NFT transaction history that the user is an authenticated user recognized by the NFT platform provider.

4. The NFT management device according to claim 1, wherein the display control means displays a title given to the user according to the total amount or total value of NFTs traded by the user.

5. The NFT management device according to claim 1, wherein the display control means displays the transaction history of the NFT before and after the cross-chain bridge in a distinguishable manner.

6. The aforementioned NFT contains comments from users of the metaverse space regarding the NFT that is placed in the metaverse space. The NFT management device according to claim 1, wherein the display control means displays comments on the NFT separately from the transaction history of the NFT.

7. The NFT management device according to claim 1, wherein the display control means displays the tags set on the NFT.

8. The NFT management device according to claim 1, wherein the display control means displays digital content corresponding to the product in a pseudo-showcase.

9. In the NFT management device, The user obtains an NFT (Non-Fungible Token) issued when they purchase a product. A control method for an NFT management device that displays information about the acquired NFTs.

10. The computer installed in the NFT management device, The process of obtaining an NFT (Non-Fungible Token) issued when a user purchases a product, The process of displaying the information regarding the acquired NFT, A program to execute.

Images