Processing device, processing program, and processing method

Abstract

To manage digital content and NFT so as to enable independent distribution.SOLUTION: When a user acquires digital content, the user and the content are associated with each other to generate content owner information for storage in a memory. When a request for issuance of the NFT for the content is received, an NFT issuance processing request is performed for a distributed ledger system. When completion of issuance of the NFT for the content is received, the user and the NFT are associated with each other based on the content owner information to generate NFT owner information for storage in the memory. When a request for transfer of ownership of the NFT alone is received, the content owner information is maintained, and the NFT owner information is updated.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a processing device, a processing program, and a processing method for managing the distribution of digital content and NFTs. [Background technology]

[0002] A technology for assigning tokens representing ownership to items acquired in a game and managing item ownership on a blockchain has been known. For example, Patent Document 1 describes an item trading system for trading items over a network, comprising: a price determination unit for determining a price of the item between a first user who owns the item and a second user different from the first user; an item transfer unit for transferring ownership of the item from the first user to the second user by the second user paying the first user a price determined by the price determination unit; and a database creation unit for storing a transaction history database containing a history of changes in ownership made by the item transfer unit, the item trading system further comprising a value change unit for changing the effect of the item on the network or in the real world in accordance with the number of users who own the same type of item as the item stored in the transaction history database.

[0003] Meanwhile, in recent years, attention has been focused on non-fungible tokens (NFTs), which can prove the uniqueness and ownership of digital content such as digital art, game items, or trading cards. However, digital content and NFTs tend to be circulated separately, making the relationship between the digital content and NFTs unclear after distribution, and there is a risk that further distribution of NFTs will be insufficient. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2019-79502 Summary of the Invention [Problem to be solved by the invention]

[0005] The present disclosure has been made against the above background and provides a processing device, processing program, and processing method that are capable of managing digital content and NFTs so that they can be distributed independently. [Means for solving the problem]

[0006] According to one aspect of the present disclosure, there is provided a processing device having at least one processor, wherein the at least one processor is configured to execute processing to: when a user acquires digital content, link the user to the content and generate content owner information, and store the information in memory; when a request to issue an NFT for the content is accepted, make an NFT issuance processing request to a distributed ledger system; when acceptance of completion of issuance of the NFT for the content, link the user to the NFT based on the content owner information, and generate NFT owner information, and store the information in memory; and when a request to transfer ownership of only the NFT is accepted, maintain the content owner information and update the NFT owner information.''

[0007] According to one aspect of the present disclosure, there is provided a processing program that causes a computer having at least one processor to function as follows: when a user acquires digital content, link the user to the content and generate content owner information, and store the information in memory; when a request to issue an NFT for the content is received, make an NFT issuance processing request to a distributed ledger system; when completion of issuance of the NFT for the content is received, link the user to the NFT based on the content owner information and generate NFT owner information, and store the information in memory; and when a request to transfer ownership of only the NFT is received, maintain the content owner information and update the NFT owner information.

[0008] According to one aspect of the present disclosure, there is provided a processing method executed by at least one processor in a computer having the at least one processor, the processing method including: when a user acquires digital content, linking the user to the content and generating content owner information and storing the content in memory; when a request to issue an NFT for the content is received, making an NFT issuance processing request to a distributed ledger system; when completion of issuance of the NFT for the content is received, linking the user to the NFT based on the content owner information and generating NFT owner information and storing the NFT in memory; and when a request to transfer ownership of only the NFT is received, maintaining the content owner information and updating the NFT owner information. [Effects of the Invention]

[0009] According to the present disclosure, it is possible to provide a processing device, processing program, and processing method that can manage digital content and NFTs so that they can be distributed independently.

[0010] It should be noted that the above effects are merely illustrative for the sake of convenience and are not limiting. In addition to or instead of the above effects, any effect described in this disclosure or an effect obvious to a person skilled in the art may be achieved. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram that schematically illustrates an overview of the transfer of items and NFTs in a processing system 1 according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a conceptual diagram schematically illustrating the configuration of a processing system 1 according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of the user terminal device 100 according to an embodiment of the present disclosure. [Figure 4] FIG. 4 is a block diagram showing an example of the configuration of the server device 200 according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a conceptual diagram showing a schematic configuration of a distributed ledger system 300 according to an embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram conceptually illustrating an item management table stored in the server device 200 according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram showing a processing sequence executed between the user terminal device 100 and the server device 200 according to an embodiment of the present disclosure. [Figure 8A] FIG. 8A is a diagram illustrating a processing sequence executed among the user terminal device 100, the server device 200, and the distributed ledger system 300 according to an embodiment of the present disclosure. [Figure 8B] FIG. 8B is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 8C] FIG. 8C is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 8D] FIG. 8D is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 8E] FIG. 8E is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 8F] FIG. 8F is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 9A] FIG. 9A is a diagram illustrating a processing sequence executed among the user terminal device 100, the server device 200, and the distributed ledger system 300 according to an embodiment of the present disclosure. [Figure 9B] FIG. 9B is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 9C] FIG. 9C is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 9D] FIG. 9D is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 9E] FIG. 9E is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 10A] FIG. 10A is a diagram illustrating a processing sequence executed among the user terminal device 100, the server device 200, and the distributed ledger system 300 according to an embodiment of the present disclosure. [Figure 10B] FIG. 10B is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 10C] FIG. 10C is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. [Figure 11] FIG. 11 is a diagram showing a processing sequence executed between the user terminal device 100 and the server device 200 according to an embodiment of the present disclosure. [Figure 12A] FIG. 12A is a diagram showing a processing flow executed in the server device 200 according to an embodiment of the present disclosure. [Figure 12B] FIG. 12B is a diagram showing a processing flow executed in the server device 200 according to an embodiment of the present disclosure. [Figure 12C]FIG. 12C is a diagram showing a processing flow executed in the server device 200 according to an embodiment of the present disclosure. [Figure 12D] FIG. 12D is a diagram showing a processing flow executed in the server device 200 according to an embodiment of the present disclosure. [Figure 13] FIG. 13 is a diagram that schematically illustrates an overview of the transfer of items and NFTs related to a processing system 1 according to a modified example of the present disclosure.

[0012] Embodiments of the present disclosure will be described with reference to the accompanying drawings, in which the same reference numerals are used to designate common components.

[0013] 1. Overview of Processing System 1 According to the Present Disclosure As an example, the processing system according to the present disclosure is used to manage ownership information for digital content (hereinafter also simply referred to as content) acquired by a user, as well as to perform processing related to the conversion of the content into NFTs and to manage ownership information for the NFTs. In particular, the processing system is suitably used, for example, when managing the owners of items acquired in a game and the NFTs corresponding to the items. Specifically, even when in-game items and NFTs are transferred independently and circulated in the in-game market and the NFT market, the processing system manages the items and NFTs so as to identify their owners. In other words, the processing system 1 separately manages the owner information, i.e., ownership information, of the items and NFTs, enabling their respective market distribution.

[0014] FIG. 1 is a diagram that schematically illustrates an overview of the transfer of items and NFTs related to a processing system 1 according to an embodiment of the present disclosure. In particular, FIG. 1 illustrates a case in which an item and an NFT, which are examples of content, are independently transferred to another user. Specifically, FIG. 1 assumes that a first user acquires an item in a game provided by a game operator (hereinafter also simply referred to as the operator) that manages a server device. In this state in which the first user owns an item, item owner information linking the first user to the content (i.e., information indicating that the owner of the item is the first user: content owner information) is stored in the server device.

[0015] Next, the first user performs a predetermined process to issue an NFT, and the owner of the NFT becomes the first user. In this state where the first user owns an NFT corresponding to an item, NFT owner information linking the first user and the NFT based on the stored item ownership information (i.e., information indicating that the owner of the NFT is the first user) is stored in the server device.

[0016] The first user then transfers the NFT to the second user, separate from the item. In other words, only the ownership of the NFT corresponding to the item is transferred to the second user, and the item and the NFT are now owned by separate entities. In this state where the second user owns the NFT, NFT owner information showing that the NFT owner has changed (i.e., information indicating that the NFT owner is the second user) is stored in the server device. At this time, the item owner information is not updated because the first user remains the owner of the item.

[0017] The first user then transfers the item they own to the third user. In other words, only the ownership of the item is transferred to the third user, and the item and the NFT continue to be owned by separate owners. In this state where the third user owns the item, item owner information showing that the item owner has changed (i.e., information indicating that the item owner is now the third user) is stored in the server device. At this time, the owner of the NFT remains the second user, so the NFT owner information is not updated.

[0018] In this way, in an embodiment of the present disclosure, an item is linked to its owner, and an NFT corresponding to the item is linked to its owner and stored in a server device. Although an item and an NFT corresponding to the item are linked, information related to each owner is updated even if each is transferred independently. In other words, in an embodiment of the present disclosure, management is implemented that allows items and NFTs to be circulated independently.

[0019] In this disclosure, "user" simply means a user who can use the services provided by the processing system. That is, in the embodiments of this disclosure, it is assumed that a game service provider will use the processing system, and such users include game players. However, since those who have ownership rights to NFTs are not limited to game players, users to whom NFTs can be transferred also include third parties other than game players. In either case, a "user" refers to a person who can own content, such as items, and NFTs corresponding to such content.

[0020] In this disclosure, "digital content" refers to content in digital format that is published or distributed on the web. This includes, in particular, documents, videos, music, or images converted into digital data. In the embodiments of this disclosure, we consider game items that can be acquired in games provided via the web. However, this digital content is not limited to the above or existing digital data, and naturally includes new digital content that will be published or distributed in the market in the future.

[0021] In this disclosure, even if a term such as "first" or "second" is used, it does not mean that the term is limited to only the two elements to which it is attached. Naturally, it may include "third," "fourth," and more elements.

[0022] 2. Configuration of Processing System 1 Figure 2 is a conceptual diagram illustrating the configuration of a processing system 1 according to an embodiment of the present disclosure. According to Figure 2, the processing system 1 includes a user terminal device 100 used by a user who receives game services provided by a business operator, a server device 200 used by the business operator for storing business activities and user information, a first distributed ledger system 300-1 and a second distributed ledger system 300-2 for managing crypto assets, and a network 400 such as the Internet that connects these systems so that they can communicate with each other. The network may be wireless, wired, or a combination of these.

[0023] 2, only one user terminal device 100 is shown, but it is possible to include two or more of each device. Also, although the server device 200 is shown as a single device, it is also possible to distribute the components and processes of the server device 200 to multiple server devices or cloud server devices.

[0024] 2 shows only two distributed ledger systems that utilize blockchain technology, but it goes without saying that three or more distributed ledger systems may be connected to the network 400. Although the first distributed ledger system 300-1 and the second distributed ledger system 300-2 are described separately, they may be collectively referred to as the distributed ledger system 300. However, even in such cases, this is merely a general term for each distributed ledger system, and does not imply that the first distributed ledger system 300-1 and the second distributed ledger system 300-2 have the same processing or configuration.

[0025] 3. Configuration of User Terminal Device 100 Fig. 3 is a block diagram showing an example of the configuration of a user terminal device 100 according to an embodiment of the present disclosure. The user terminal device 100 does not need to include all of the components shown in Fig. 3, and may have a configuration in which some components are omitted, or may include other components.

[0026] The user terminal device 100 is typically a user terminal device capable of wireless communication, such as a smartphone, but is not limited to these devices. For example, the user terminal device may be a feature phone, a personal digital assistant (PDA), a laptop computer, a desktop computer, a portable game console, a stationary game console, or any other device capable of executing the program according to the present disclosure. Furthermore, when there are multiple user terminal devices 100, the user terminal devices do not necessarily have to be the same type or the same user terminal device, and may be different types of user terminal devices.

[0027] 3, the user terminal device 100 includes an output interface 111, a processor 112, a memory 113 including RAM, ROM, or non-volatile memory (or HDD in some cases), a communication interface 114 including a communication processing circuit and an antenna, and an input interface 115 including a touch sensor and hard keys. These components are electrically connected to each other via control lines and data lines.

[0028] The output interface 111 functions as an output unit that outputs images captured by a connected camera (not shown) and various displays output by executing the program according to the present disclosure to devices such as a display or a printer in response to instructions from the processor 112. Note that such a display may be, for example, a liquid crystal display, an organic EL display, or electronic paper.

[0029] Processor 112 is configured with a CPU (microcomputer) and functions as a control unit that controls other connected components based on various programs stored in memory 113. Specifically, processor 112 reads out from memory 113 a program for executing an application according to the present disclosure and a program for executing an OS, and executes them. In the present disclosure, processor 112 particularly executes the processes described in the processing sequences of FIGS. 7, 8A, 9A, 10A, and 11 (details of the processes will be explained in each figure). Processor 112 may be configured with a single CPU, or may be configured with a combination of multiple CPUs and GPUs.

[0030] The memory 113 is composed of a ROM, a RAM, a non-volatile memory, a HDD, etc., and functions as a storage unit. The ROM stores instructions and commands for executing the application and OS according to the present disclosure as a program. The RAM is used to write and read data while the program stored in the ROM is being processed by the processor 112. The non-volatile memory is a memory into which data is written and read as the program is executed, and the data written therein is saved even after the execution of the program has ended. In the present disclosure, the memory 113 particularly stores programs for executing the processes described in the processing sequences of FIGS. 7, 8A, 9A, 10A, and 11 (details of the processes are explained in each figure).

[0031] Furthermore, in an embodiment of the present disclosure, a wallet app is stored in the memory 113, and various processes related to NFTs can be performed. For example, wallet apps include METAMASK, MEW Wallet, and tokenPocket. The type of wallet stored in the memory 113 is not limited to a wallet app, and may be a browser-extended wallet or an in-game wallet depending on the type of user terminal device 100, as long as the wallet can be used within a game, which will be described later.

[0032] The communication interface 114 functions as a communication unit that transmits and receives information to and from the remotely installed server device 200, each distributed ledger system, or other user terminal device via a communication processing circuit and an antenna. The communication processing circuit processes programs and various information used in the processing system 1 to transmit and receive information from the server device 200, each distributed ledger system, or other user terminal device as the processing progresses. In the present disclosure, in particular, information related to a login request, information related to an item storage request, wallet information, NFT information, NFT transfer destination selection information, NFT transfer decision information, NFT transfer destination information, NFT transfer decision information, item selection information, item transfer destination information, item transfer decision information, etc. are transmitted from the user terminal device 100 to the server device 200. In the present disclosure, transaction information related to a product purchase, information related to approval of a login request, and item transfer completion notification are received from the server device 200. Furthermore, in the present disclosure, NFT issuance completion notifications, NFT transfer completion notifications, etc. are received from the first distributed ledger system 300-1, and NFT transfer completion notifications, etc. are received from the second distributed ledger system 300-2.

[0033] The communication processing circuit processes based on a wideband wireless communication system such as the LTE system, but it can also process based on a narrowband wireless communication system or a contactless wireless communication system such as a wireless LAN such as IEEE802.11 or Bluetooth (registered trademark). Also, wired communication can be used instead of or in addition to wireless communication.

[0034] The input interface 115 is composed of a touch panel, hard keys, etc., and functions as an input unit that accepts instruction inputs related to the execution of the program according to the present disclosure, operation inputs for registering various information, etc. The touch panel is arranged to cover the output interface 111, and transmits position coordinate information corresponding to image data output from the output interface 111 to the display to the processor 112. Known touch panel methods can be used, such as a resistive film method, a capacitive coupling method, and an ultrasonic surface acoustic wave method. In the present disclosure, the touch panel detects swipe and tap operations on icons, etc. displayed on the output interface 111 by a pointer. Note that, although the present disclosure uses the input interface 115 provided in the user terminal device 100, it is also possible to use an input interface 115, such as a mouse, that is connected wirelessly or via a wire to a main body including the processor 112, etc.

[0035] 4. Configuration of Server Device 200 Fig. 4 is a block diagram showing an example of the configuration of a server device 200 according to an embodiment of the present disclosure. The server device 200 does not need to include all of the components shown in Fig. 4, and may have a configuration in which some components are omitted, or may include other components. Furthermore, the server device 200 does not need to include the components shown in Fig. 4 in a single housing, and the components and processes of the server device 200 may be distributed across multiple server devices or cloud server devices.

[0036] 4, the server device 200 includes a memory 211 including RAM, ROM, non-volatile memory, and HDD, a processor 212 including a CPU, and a communication interface 213. These components are electrically connected to each other via control lines and data lines.

[0037] The memory 211 includes RAM, ROM, nonvolatile memory, and HDD, and functions as a storage unit. The ROM stores instructions and commands for executing the application and OS according to the present disclosure as a program. Such a program is loaded and executed by the processor 212. The RAM is used to write and read data while the program stored in the ROM is being processed by the processor 212. The nonvolatile memory is memory into which data is written and read as the program is executed, and the data written therein is retained even after the execution of the program has ended.

[0038] In the present disclosure, the memory 211 stores programs for, among other things, "a process of linking a user with an item that is digital content, generating content owner information, and storing the information in the memory 211, when a user acquires the item," "a process of making an NFT issuance process request to the first distributed ledger system 300-1, when a request to issue an NFT for the item is accepted," "a process of linking a user with the NFT based on the content owner information, generating NFT owner information, and storing the information in the memory 211, when completion of issuance of the NFT for the item is accepted," and "a process of maintaining the content owner information and updating the NFT owner information, when a request to transfer ownership of only the NFT is accepted." The memory 211 also stores various information described in an item management table (FIG. 6).

[0039] In the present disclosure, the memory 211 stores user account information. Specifically, when a user registration process is completed in a game provided by the server device 200, the memory 211 stores information about the user. For example, the user information includes a user ID, a user name, the user's level in the game, and the user's wallet address.

[0040] The processor 212 is configured with a CPU (microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in the memory 211. Specifically, the processor 112 reads and executes programs for executing applications and an OS according to the present disclosure from the memory 211. In the present disclosure, the processor 212 executes, among other things, "a process of linking a user and an item, generating content owner information, and storing the content owner information in the memory 211, when a user acquires an item that is digital content; a process of issuing an NFT issuance process request to the first distributed ledger system 300-1, when a request to issue an NFT for the item is received; a process of linking a user and the NFT based on the content owner information, generating NFT owner information, and storing the NFT owner information in the memory 211, when a request to transfer ownership of only the NFT is received; and a process of maintaining the content owner information and updating the NFT owner information, when a request to transfer ownership of only the NFT is received." The processor 212 may be configured with a single CPU or multiple CPUs.

[0041] The communication interface 213 functions as a communication unit that transmits and receives information to and from other remotely installed server devices and user terminal devices 100 via a communication processing circuit and an antenna. The communication processing circuit processes programs used in the processing system 1, various information, and the like, to transmit and receive information from other server devices, user terminal devices 100, and each distributed ledger system 300 as the processing progresses. In the present disclosure, particularly, information related to approval of a login request and an item transfer completion notification are transmitted from the server device 200 to the user terminal device 100 via the communication interface 213. In addition, in the present disclosure, information related to a login request, information related to an item storage request, wallet information, NFT information, NFT transfer destination selection information, NFT transfer decision information, NFT transfer destination information, NFT transfer decision information, item selection information, item transfer destination information, item transfer decision information, and the like are received from the user terminal device 100. Furthermore, in the present disclosure, an NFT issuance processing request, an NFT transfer processing request, an NFT transfer processing request, etc. are sent from the server device 200 to the distributed ledger system 300. Then, in the present disclosure, an NFT issuance completion notification, an NFT transfer completion notification, an NFT transfer completion notification, etc. are received from the distributed ledger system 300.

[0042] The communication processing circuit processes based on a wideband wireless communication system such as the LTE system, but it can also process based on a narrowband wireless communication system or a contactless wireless communication system such as a wireless LAN such as IEEE802.11 or Bluetooth (registered trademark). Also, wired communication can be used instead of or in addition to wireless communication.

[0043] 5. Configuration of Distributed Ledger System 300 FIG. 5 is a conceptual diagram illustrating a schematic configuration of a distributed ledger system 300 according to an embodiment of the present disclosure. As shown in FIG. 5, the distributed ledger system 300 includes multiple node terminal devices 311-314. The node terminal devices 311-314 are communicatively connected to each other via a network. For example, the network may be a public network, a private network, a dedicated line, a VPN (Virtual Private Network), or a combination of these. The multiple node terminal devices 311-314 are connected to each other, for example, by wire or wirelessly. The multiple node terminal devices 311-314 communicate with each other in a peer-to-peer (P2P) manner.

[0044] As shown in FIG. 5, node terminal device 311 is a desktop PC, node terminal device 312 is a tablet terminal, node terminal device 313 is a laptop PC, and node terminal device 314 is a mobile phone such as a smartphone. However, node terminal devices 311-314 are not limited to these and may be any terminal device that can connect to a blockchain network. Also, in FIG. 5, node terminal devices 311-314 are each a different type of terminal, but they may also be the same type of terminal. Furthermore, the number of node terminal devices 311-314 constituting distributed ledger system 300 is not limited to four and can be set to any number greater than or equal to two. The number of node terminal devices 311-314 constituting distributed ledger system 300 may change over time.

[0045] Each of the node terminal devices 311 to 314 has the same configuration as the user terminal device 100 or the server device 200. For example, the node terminal devices 311 to 314 may include a processor, a memory, a communication interface, an input interface, and an output interface. Naturally, the node terminal devices 311 to 314 are not limited to this configuration, and do not need to include all of the components, and may have a configuration in which some components are omitted, or other components may be added. Furthermore, the configurations of the node terminal devices 311 to 314 may differ from one another.

[0046] The node terminal devices 311 to 314 manage a distributed ledger using, for example, blockchain technology. Specifically, one of the node terminal devices 311 to 314 acquires data related to token transactions to be recorded. The node terminal devices 311 to 314 create a block including the acquired data. The node terminal devices 311 to 314 then add the generated block to the blockchain. The node terminal devices 311 to 314 transmit information about the added block to the other node terminal devices 311 to 314. The other node terminal devices 311 to 314 verify the correctness of the received block. If the other node terminal devices 311 to 314 successfully verify the correctness of the block, they add the block to the blockchain. The node terminal devices 311 to 314 finalize the blockchain based on, for example, the number of linked blocks, which is the so-called approval number. As a result, the same distributed ledger is stored across multiple node terminal devices 311 to 314. The data stored on the blockchain is encrypted as appropriate.

[0047] As mentioned above, the distributed ledger system 300 includes the first distributed ledger system 300-1 and the second distributed ledger system 300-2. However, these systems do not necessarily have to be the same type or have the same terminal devices; they may be configured in different ways. Furthermore, since the first distributed ledger system 300-1 and the second distributed ledger system 300-2 configure different blockchains, the node terminal devices that configure the first distributed ledger system 300-1 and the node terminal devices that configure the second distributed ledger system 300-2 are separate. However, if it is possible to configure different blockchains, some of the node terminal devices of the first distributed ledger system 300-1 and the second distributed ledger system 300-2 may be shared.

[0048] 6. Information stored in the memory 211 of the server device 200 6 is a diagram conceptually illustrating an item management table stored in the server device 200 according to an embodiment of the present disclosure. The information illustrated in FIG. 6 is updated when a user obtains an item and an item storage request related to the item is received by the server device 200. Also, when the transfer of the item, the issuance of an NFT, the transfer of an NFT, or the movement of an NFT is completed, the items in the item management table are updated when the server device 200 receives a notification related to the completion.

[0049] The purchase history management table is composed of information related to the "user ID," "item ID," "acquisition date," "number of NFTs that can be issued," "NFT ID," and "NFT owner account." Therefore, the item management table stores information related to items acquired by each user and the NFTs corresponding to those items. Furthermore, even for the same user and the same product, the item management table stores separate information. Therefore, the item management table stores the "user ID," "item ID," "acquisition date," and "number of NFTs that can be issued" in association with each other, and also stores the "NFT ID" and "NFT owner account" linked to the information related to the item. In particular, the "user ID," "item ID," "acquisition date," and "number of NFTs that can be issued" make up item owner information (content owner information), and users and items are managed in association with each other. Furthermore, NFT owner information is made up of an "NFT ID" and an "NFT owner account," but in the initial stage when an NFT is issued (when there is no transfer of the NFT), the "NFT ID" and "NFT owner account" are linked to a "user ID" to make up the NFT owner information.

[0050] A "user ID" is a unique identifier assigned to a user who has completed the registration process for a game provided by a service provider. The user ID may be, for example, a serial number, a combination of letters and numbers set by the user, or an email address or part thereof. Therefore, the user ID may be freely set as long as it can identify the user.

[0051] An "item ID" is a unique identifier assigned to an item acquired by a user in a game provided by a provider. The "item ID" may be, for example, a serial number or may be composed of any letters and numbers. In addition, detailed information about the item (e.g., item name, function, etc.) may be stored in an item management table in association with the "item ID."

[0052] The "acquisition date" stores the date on which the user acquired the item in the game provided by the provider. In Figure 6, the year and date are listed, but the hour, minute, day of the week, etc. may also be stored.

[0053] The "number of NFTs that can be issued" stores the number of NFTs that can be issued for an item acquired by a user (i.e., the number of times that NFTs can be issued). Here, the "number of NFTs that can be issued" is calculated by the processor 212 of the server device 200 based on the rarity of the item acquired by the user, the amount of that item in circulation in the game, the item's attribute information, the user's level in the game, and the user attribute information. Furthermore, the item's attribute information is information that includes the type of item and its relationship with other items. Furthermore, the user attribute information is information that includes, for example, the amount of in-game currency used by the user in the game (i.e., the frequency of in-game purchases).

[0054] For the above reasons, in an embodiment of the present disclosure, the number of NFTs that can be issued is not determined for each item, but is determined taking into consideration information about the item itself as well as information about the user who acquired the item.The "number of NFTs that can be issued" in an embodiment of the present disclosure is updated and decreased each time an NFT is issued.

[0055] An "NFT ID" is a unique identifier assigned to an NFT issued based on an item acquired by a user. In particular, an "NFT ID" is an ID issued by a service provider of a game and used for management within the server device 200. The "NFT ID" may be, for example, a serial number or may be composed of any letters and numbers. Preferably, the "NFT ID" allows the relationship between the item and the NFT to be understood. In the embodiment of the present disclosure, an "NFT ID" is used that is an "item ID" with a subnumber added. While FIG. 6 illustrates a case where one NFT is issued for each item, if two or more NFTs are issued from the same item, multiple IDs are stored in the "NFT ID" field. This allows the user to manage all NFTs issued for a single item acquired by the user.

[0056] "NFT owner account" is information related to a user who owns an issued NFT. In an embodiment of the present disclosure, "NFT owner account" is account information related to the wallet of a user who owns an NFT. Here, FIG. 6 shows a case where one NFT is issued for each item, but if two or more NFTs are issued from the same item and have different owners, multiple accounts are stored in the "NFT owner account" field. This makes it possible to manage the owners of all NFTs issued for one item acquired by a user.

[0057] The item management table shown in FIG. 6 is merely an example and may include other items related to items or NFTs. For example, additional information such as the user's level in the game, the item's level, the NFT issuance date, or blockchain information related to the NFT may be included. Furthermore, a per-user item table that summarizes the items owned by each user and a per-NFT owner table that summarizes the owners of each NFT may be further stored in the memory 211 of the server device 200. In the server device 200, the processor 212 may perform calculations based on the item management table shown in FIG. 6, and the per-user item table, per-NFT owner table, or other management tables may be automatically generated and stored in the memory 211.

[0058] 7. Processing sequence performed by processing system 1 (A) Processing related to item storage from the start of the game Fig. 7 is a diagram showing a processing sequence executed between the user terminal device 100 and the server device 200 according to an embodiment of the present disclosure. Specifically, Fig. 7 is a diagram showing a processing sequence executed between the user terminal device 100 and the server device 200 from when a user logs in to a game to when the user acquires an item and further when the item is stored.

[0059] First, as shown in FIG. 7, the processor 112 of the user terminal device 100 receives a user's operational input via the input interface 115 and generates login information (S11). The login includes a user ID and a password. More specifically, the user's operational input refers to the user's operation of the user terminal device 100 to launch a game app, and the user's ID and password are entered via the input interface 115 on the launch screen of the game app. The processor 112 then transmits the generated login information via the communication interface 114 to the server device 200, along with a login request (T11) indicating an intention to start a game.

[0060] When the login information and login request generated by the user terminal device 100 are received by the server device 200 via the communication interface 213, the processor 212 of the server device 200 performs authentication processing for login based on the login information (S12). Specifically, the processor 212 of the server device 200 compares the received login information with the user information stored in the memory 211, and confirms whether the person making the login request is a registered user. If the processor 212 of the server device 200 confirms user registration, it approves the user's login as a result of the authentication processing (T12). On the other hand, if the processor 212 of the server device 200 cannot confirm user registration, it requests the user terminal device 100 to re-enter the user ID and password.

[0061] When the result of the authentication process (approval result) by the server device 200 is received by the user terminal device 100 via the communication interface 213, the game starts on the user terminal device 100 (S13). Specifically, the screen of the user terminal device 100 transitions from a login screen to a game home screen, and the game progresses sequentially as user input is accepted via the input interface 115. Then, by clearing an event in the game or a predetermined condition of the game, the user acquires an item in the game (S14). Here, the item is not limited to an item that can be used in the game, but also includes an item that has some value both in and outside the game.

[0062] When a game item is acquired in the user terminal device 100, the processor 112 of the user terminal device 100 requests that the acquired item be stored in the item management table in the memory 211 of the server device 200 (item storage request: T13), and also transmits information about the acquired item to the server device 200 via the communication interface 114.

[0063] When the server device 200 receives information about an item generated by the user terminal device 100 and an item storage request via the communication interface 213, the processor 212 of the server device 200 performs an item storage process based on the item information (S14). Specifically, the processor 212 of the server device 200 updates the item management table of FIG. 6 based on the received item information. In particular, in an embodiment of the present disclosure, a new row (e.g., a row with a user ID of U1 and an item ID of X1) is added to the item management table, and the user ID, item ID, acquisition cost, and number of NFTs that can be issued are stored. Here, the processor 212 of the server device 200 calculates the number of NFTs that can be issued when receiving information about the item. As described above, the processor 212 of the server device 200 may calculate the number of NFTs that can be issued based on, for example, the rarity of the item acquired by the user, the amount of the item in circulation in the game, attribute information of the item, the user level in the game, and user attribute information.

[0064] (B) Processing related to issuing NFTs corresponding to items FIG. 8A is a diagram illustrating a processing sequence executed among the user terminal device 100, the server device 200, and the distributed ledger system 300 according to an embodiment of the present disclosure. Specifically, FIG. 8A is a diagram illustrating a processing sequence executed among the user terminal device 100, the server device 200, and the distributed ledger system 300 after an item is acquired until an NFT corresponding to the item is acquired. Also, FIGS. 8B to 8F are diagrams illustrating example screens output to the user terminal device 100 according to an embodiment of the present disclosure. Specifically, FIG. 8B is a screen for starting processing for issuing an NFT, FIGS. 8C to 8E are screens related to wallet connection required for issuing an NFT, and FIG. 8F is a screen for performing final confirmation for issuing an NFT.

[0065] First, according to FIG. 8A, the processor 112 of the user terminal device 100 receives a user's item selection via the input interface 115 and generates item selection information (S21). The item selection information includes information related to the item for which the user wishes to issue an NFT, such as an item ID. More specifically, the user's operational input involves the user operating the user terminal device 100 to display a list of acquired items on the display, and selecting the item from the list that the user wishes to turn into an NFT. The processor 112 of the user terminal device 100 then transmits the generated item selection information to the server device 200 via the communication interface 114 (T21).

[0066] Next, according to FIG. 8A, the processor 112 of the user terminal device 100 receives a user's request to issue an NFT via the input interface 115 and generates NFT issuance request information (S22). The NFT issuance request information is trigger information that initiates the process to request the issuance of an NFT for the selected item. A more specific user input is the operation (pressing) of the "Issue / Confirm NFT" button 122 on the screen 121 output to the user terminal device 100 after item selection (S21), as shown in FIG. 8B. The other buttons are used to use or process the selected item in the game, and their description will be omitted. The processor 112 of the user terminal device 100 then transmits the generated NFT issuance request information to the server device 200 via the communication interface 114 (T22).

[0067] Next, as shown in FIG. 8A, the processor 112 of the user terminal device 100 receives a user's wallet connection request via the input interface 115 and generates wallet information (S23). The wallet information includes account information and network information related to the user's wallet entered or selected by the user via the input interface 115. As a more specific example of a user input, when the "Issue / Confirm NFT" button 122 in FIG. 8B is pressed, a screen 121 for selecting a wallet connection destination, as shown in FIG. 8C, is output to the user terminal device 100. Then, a button 123 for issuing a new NFT for the selected item is pressed, and then a "Connect / Update Wallet" button 124 is pressed. Subsequently, as shown in FIG. 8D, a screen 131, different from the screen 121, displays information related to Wallet Connect and prompts the user to select a wallet. Next, when a keyword, such as a wallet name, is entered in the wallet search input field 132, the corresponding wallet is displayed. Even if a wallet search is not performed, a list of connectable wallets is displayed below the input field 132. Thereafter, when the icon button 133 of the desired wallet is pressed, a confirmation as to whether to connect to the site of the selected wallet is requested on a screen 141 different from screen 131, as shown in Fig. 8E. Then, when connect button 142 is pressed on screen 141, as shown in Fig. 8E, information related to the selected wallet is generated and transmitted to server device 200 via communication interface 114 (T23). This series of operations approves the connection of the user's wallet to the game app, and the user's wallet is connected to the game app and can be used in the game.

[0068] Next, as shown in FIG. 8A, the processor 112 of the user terminal device 100 accepts the user's decision to issue an NFT via the input interface 115 and generates wallet issuance decision information (S24). This decision information indicates the user's final intention in the process of requesting the issuance of an NFT. More specifically, when the user presses the connect button 142 in FIG. 8E (S23), as shown in FIG. 8F, the destination wallet information is automatically entered in the account field 125 and network field 126 on the screen 121, and the "Issue NFT" button 127 is pressed. This final confirmation of the NFT issuance request based on the selected item and wallet is then made, and the generated decision information is sent to the server device 200 via the communication interface 114 (T24).

[0069] Note that, although the transmission of the information from T21 to T24 described above was processed so that each piece of information was sent in stages, it is also possible to send each piece of information all at once. That is, the user terminal device 100 may sequentially perform the processes from S21 to S24, and after the process of S24 is completed, the information may be sent all at once, and the server device 200 may then perform a process in response to the request from the user terminal device 100 (the NFT issuance request process described below).

[0070] When the server device 200 receives the information generated by the user terminal device 100 (selection information, desired information, wallet information, and decision information) via the communication interface 213, the processor 212 of the server device 200 performs an NFT issuance request process based on the information (S25). Specifically, the processor 212 of the server device 200 reads information about the item to be converted into an NFT and information about the person who will own the NFT (i.e., the wallet address) based on the received information, and generates NFT issuance request information. The processor 212 of the server device 200 references the "number of NFTs that can be issued" in the item management table based on the item ID of the selected item, and generates NFT issuance request information if the number is "1" or greater. The processor 212 of the server device 200 then transmits the generated NFT issuance request information, along with a request for an NFT issuance process, to the first distributed ledger system 300-1 via the communication interface 213 (T25). In other words, the processor 212 of the server device 200 uploads the item to be converted into an NFT to the first distributed ledger system 300-1, and sends information specifying the storage location of the issued NFT to the first distributed ledger system 300-1.

[0071] When the NFT issuance request information generated by the server device 200 is received by the first distributed ledger system 300-1, the first distributed ledger system 300-1 executes the NFT conversion process (i.e., the NFT issuance process) of the uploaded content using known blockchain technology (S26). The first distributed ledger system 300-1 then sends a notification (NFT issuance completion notification) to the user terminal device 100 and the server device 200 indicating that the NFT issuance has been completed (T26). Here, the user can confirm their ownership of the NFT corresponding to the selected item by operating the user terminal device 100 and checking the wallet connected to the game app. Meanwhile, the server device 200 can confirm whether the NFT has been issued by connecting the user's wallet to the game app.

[0072] When the server device 200 receives the NFT issuance completion notification sent from the first distributed ledger system 300-1 via the communication interface 213, the processor 212 of the server device 200 updates the item management table stored in the memory 211 (S27). Specifically, the processor 212 of the server device 200 updates the item management table of FIG. 6 by adding new information to the "NFT ID" and "NFT owner account" columns in the information for the row related to the item that is the original content to be NFTized, and by decrementing the value of the "number of NFTs that can be issued" by one. That is, the processor 212 of the server device 200 identifies the row in the item management table whose information should be updated from the NFT issuance completion notification (for example, the row with the user ID U1 and the item ID X1), and updates the "NFT ID," "NFT owner account," and "number of NFTs that can be issued." Here, the NFT issuance completion notification includes information about the item that is the original content that was converted into an NFT, and the wallet address of the user who owns it, so the processor 212 of the server device 200 can identify the row that needs to be updated.

[0073] (C) Processing related to the transfer of ownership of NFTs 9A is a diagram illustrating a processing sequence executed among the user terminal device 100, the server device 200, and the distributed ledger system 300 according to an embodiment of the present disclosure. Specifically, FIG. 9A is a diagram illustrating a processing sequence executed among the user terminal device 100, the server device 200, and the distributed ledger system 300 after an NFT is issued, until the NFT is transferred and ownership is changed. Also, FIGS. 9B to 9E are diagrams illustrating example screens output to the user terminal device 100 according to an embodiment of the present disclosure. Specifically, FIGS. 9B and 9C are screens related to processing for selecting an NFT, FIG. 9D is a screen related to determining the transferee of the NFT, and FIG. 9E is a screen for performing final confirmation before transferring the NFT.

[0074] First, as shown in FIG. 9A , the processor 112 of the user terminal device 100 receives a user's wallet connection request via the input interface 115 and generates wallet information (S31). The wallet information includes account information and network information related to the user's wallet entered or selected by the user via the input interface 115. As a more specific user input, as shown in FIG. 9B , the user selects the "Owned NFTs List" item on screen 121 to display a list of NFTs acquired by operating the user terminal device 100. Next, the user presses a "Owned NFTs" button 151 in the "Owned NFTs List" item, and then presses a "Wallet Connect / Update" button 152. Subsequently, as shown in FIG. 8D , a Wallet Connect screen 131, which is different from screen 121, displays a request for wallet selection. Next, when a keyword, such as a wallet name, is entered in the wallet search input field 132, the corresponding wallet is displayed. Even if a wallet search is not performed, a list of connectable wallets is displayed below the input field 132. Thereafter, when the icon button 133 of the desired wallet is pressed, a screen 141 different from the screen 131 is displayed, as shown in FIG. 8E, requesting confirmation as to whether to connect to the site of the selected wallet. Then, as shown in FIG. 8E, when the connect button 142 is pressed on the screen 141, information related to the selected wallet is generated and transmitted to the server device 200 via the communication interface 114 (T31). This series of operations approves the connection of the user's wallet to the game app, and the user's wallet is connected to the game app and becomes available for use in the game. In other words, the user's wallet can be used to access the distributed ledger system via the server device 200.

[0075] Next, as shown in FIG. 9A, the processor 112 of the user terminal device 100 receives an NFT selection from the user via the input interface 115 and generates NFT selection information (S32). The NFT selection information includes information related to the NFT desired for a specific process (transfer, transfer, etc.). More specifically, the user inputs an operation by pressing the connect button 142 as shown in FIG. 8E. Then, as shown in FIG. 9C, the screen 121 displays wallet information for the destination in the account field 153 and network field 154, and displays a list of NFTs owned in the selected wallet as uncontracts and names. In FIG. 9C, eight NFTs are displayed as search results. The user then operates the user terminal device 100 to select an NFT to transfer from the list of owned NFTs, and NFT selection information is generated. The processor 112 of the user terminal device 100 then transmits the generated NFT selection information to the server device 200 via the communication interface 114 (T32).

[0076] Next, according to FIG. 9A, the processor 112 of the user terminal device 100 accepts the user's NFT transfer destination selection process via the input interface 115 and generates NFT transfer destination information (S33). The transfer destination information includes information related to the user's wallet to which the NFT is to be transferred. More specifically, the user's operation input is, as shown in FIG. 9D, entering specific account information in the transfer destination account input field 162 on the screen 161 output to the user terminal device 100 after item selection (S33) and pressing the OK button 163. The processor 112 of the user terminal device 100 then transmits the generated transfer destination information to the server device 200 via the communication interface 114 (T33).

[0077] Next, according to FIG. 9A, the processor 112 of the user terminal device 100 accepts the user's NFT transfer decision process via the input interface 115 and generates NFT transfer decision information (S34). This decision information is information indicating the user's final intention in the process of requesting an NFT transfer. As a more specific user input, when the OK button 163 in FIG. 9D is pressed (S33), as shown in FIG. 9E, the account information of the transferor and transferee and the transfer fee are displayed on a screen 171, and the OK button 172 is pressed, generating NFT transfer decision information. The processor 112 of the user terminal device 100 then transmits the generated NFT transfer decision information to the server device 200 via the communication interface 114 (T34).

[0078] Note that, although the transmission of the information from T31 to T34 described above was processed so that each piece of information was sent in stages, it is also possible to send each piece of information all at once. That is, the user terminal device 100 may sequentially perform the processes from S31 to S34, and after the process of S34 is completed, the information may be sent all at once, and the server device 200 may then perform a process in response to the request from the user terminal device 100 (the NFT transfer request process described below).

[0079] When the server device 200 receives the various pieces of information generated by the user terminal device 100 (wallet information, NFT selection information, transferee information, and determination information) via the communication interface 213, the processor 212 of the server device 200 performs an NFT transfer request process based on the various pieces of information (S35). Specifically, the processor 212 of the server device 200 reads information about the NFT to be transferred, as well as information about the transferor and transferee of the NFT (i.e., wallet addresses), based on the various pieces of information received, to generate NFT transfer request information. The processor 212 of the server device 200 then sends the generated NFT transfer request information, along with an NFT transfer process request, to the first distributed ledger system 300-1 via the communication interface 213 (T35). In other words, the processor 212 of the server device 200 sends a transaction related to the transfer process to the first distributed ledger system 300-1.

[0080] When the NFT transfer request information generated by the server device 200 is received by the first distributed ledger system 300-1, the first distributed ledger system 300-1 executes the NFT ownership transfer process (i.e., a transaction transferring the ownership of the NFT from the transfer source to the transfer destination) using known blockchain technology (S36). The first distributed ledger system 300-1 then sends a notification that the NFT transfer has been completed (NFT transfer completion notification) to the user terminal device 100 and the server device 200 (T36). Here, the user can confirm that the selected NFT has been transferred by operating the user terminal device 100 to check the wallet connected to the game app. Meanwhile, the server device 200 can confirm the NFT transfer because the user's wallet is connected to the game app.

[0081] When the server device 200 receives the NFT transfer completion notification sent from the first distributed ledger system 300-1 via the communication interface 213, the processor 212 of the server device 200 updates the item management table stored in the memory 211 (S37). Specifically, the processor 212 of the server device 200 updates the "NFT owner account" column in the item management table of FIG. 6 in the information for the row related to the item that is the original content to be NFTized. That is, the processor 212 of the server device 200 identifies the row in the item management table whose information should be updated from the NFT transfer completion notification (for example, the row with the user ID U1 and the item ID X1) and updates the "NFT owner account." Here, the NFT transfer completion notification includes information on the wallet addresses of the users who are the previous owner (transferor) and new owner (transferee) of the NFT, so the processor 212 of the server device 200 can identify the row that should be updated.

[0082] (D) Processing related to the transfer of NFTs Fig. 10A is a diagram showing a processing sequence executed among the user terminal device 100, the server device 200, and the distributed ledger system 300 according to an embodiment of the present disclosure. Specifically, Fig. 10A is a diagram showing a processing sequence executed among the user terminal device 100, the server device 200, and the distributed ledger system 300 after an NFT is issued, until the NFT is transferred to another blockchain (network). Also, Figs. 10B and 10C are diagrams showing example screens output to the user terminal device 100 according to an embodiment of the present disclosure. Specifically, Fig. 10B is a screen related to determining the blockchain to which the NFT will be transferred, and Fig. 10C is a screen for making final confirmation before transferring the NFT.

[0083] First, as shown in FIG. 10A , the processor 112 of the user terminal device 100 receives a user's wallet connection request via the input interface 115 and generates wallet information (S41). The wallet information includes account information and network information related to the user's wallet entered or selected by the user via the input interface 115. As a more specific user input, as shown in FIG. 9B , the user selects the "Owned NFTs List" item on screen 121 to display a list of NFTs acquired by operating the user terminal device 100. Next, the user presses a "Owned NFTs" button 151 in the "Owned NFTs List" item, and then presses a "Wallet Connect / Update" button 152. Subsequently, as shown in FIG. 8D , a Wallet Connect screen 131, which is different from screen 121, displays a request for wallet selection. Next, when a keyword, such as a wallet name, is entered in the wallet search input field 132, the corresponding wallet is displayed. Even if a wallet search is not performed, a list of connectable wallets is displayed below the input field 132. Thereafter, when the icon button 133 of the desired wallet is pressed, a screen 141 different from the screen 131 is displayed, as shown in FIG. 8E, requesting confirmation as to whether to connect to the site of the selected wallet. Then, as shown in FIG. 8E, when the connect button 142 is pressed on the screen 141, information related to the selected wallet is generated and transmitted to the server device 200 via the communication interface 114 (T41). This series of operations approves the connection of the user's wallet to the game app, and the user's wallet is connected to the game app and becomes available for use in the game. In other words, the user's wallet can be used to access the distributed ledger system via the server device 200.

[0084] Next, according to FIG. 10A, the processor 112 of the user terminal device 100 accepts the user's NFT selection via the input interface 115 and generates NFT selection information (S42). The NFT selection information includes information related to the NFT desired for a specific process (transfer, transfer, etc.). More specifically, the user inputs an operation by pressing the connect button 142 as shown in FIG. 8E. Then, as shown in FIG. 9C, on the screen 121, wallet information for the destination wallet is displayed in the account field 153 and network field 154, and a list of NFTs owned in the selected wallet is displayed as uncontracts and names. In FIG. 9C, eight NFTs are displayed as search results. The user then operates the user terminal device 100 to select an NFT to transfer from the list of owned NFTs, and NFT selection information is generated. The processor 112 of the user terminal device 100 then transmits the generated NFT selection information to the server device 200 via the communication interface 114 (T42).

[0085] Next, according to FIG. 10A, the processor 112 of the user terminal device 100 accepts the user's NFT destination selection process via the input interface 115 and generates destination information for the NFT (S43). The destination information includes information on the other blockchain to which the NFT is to be moved. More specifically, the user's operation input is, as shown in FIG. 10B, inputting predetermined network information into an input field 182 for the destination blockchain on a screen 181 output to the user terminal device 100 after selecting an item (S43), and pressing an OK button 183. Then, the processor 112 of the user terminal device 100 transmits the generated destination information to the server device 200 via the communication interface 114 (T43).

[0086] Next, according to FIG. 10A, the processor 112 of the user terminal device 100 accepts the user's NFT transfer decision process via the input interface 115 and generates NFT transfer decision information (S44). This decision information is information indicating the user's final intention in the process to request an NFT transfer. As a more specific user input, when the OK button 183 in FIG. 10B is pressed (S43), as shown in FIG. 10C, the source and destination network information and the transfer fee are displayed on screen 191, and the OK button 192 is pressed, generating NFT transfer decision information. Then, the processor 112 of the user terminal device 100 transmits the generated NFT transfer decision information to the server device 200 via the communication interface 114 (T44).

[0087] Note that, although the transmission of the information from T41 to T44 described above has been processed so that each piece of information is transmitted in stages, each piece of information may also be transmitted all at once. That is, in the user terminal device 100, the processes from S41 to S44 may be performed sequentially, and after the process of S44, each piece of information may be transmitted all at once, and the server device 200 may perform a process in response to the request from the user terminal device 100 (an NFT transfer request process, which will be described later).

[0088] When the server device 200 receives the various pieces of information generated by the user terminal device 100 (wallet information, NFT selection information, transfer destination information, and decision information) via the communication interface 213, the processor 212 of the server device 200 performs NFT transfer request processing based on the various pieces of information (S45). Specifically, the processor 212 of the server device 200 reads information about the NFT to be transferred, as well as information about the transfer source and transfer destination of the NFT (i.e., network information), based on the various pieces of information received, to generate NFT transfer request information. The processor 212 of the server device 200 then transmits the generated NFT transfer request information, along with an NFT transfer processing request, to the first distributed ledger system 300-1 via the communication interface 213 (T45). In other words, the processor 212 of the server device 200 transmits a transaction related to the transfer processing to the first distributed ledger system 300-1.

[0089] When the NFT transfer request information generated by the server device 200 is received by the first distributed ledger system 300-1, the first distributed ledger system 300-1 executes an NFT sending process to send the NFT to be transferred to another blockchain (i.e., the second distributed ledger system 300-2) using known blockchain technology (S46).The first distributed ledger system 300-1 then transmits the sending information generated by the NFT sending process to the second distributed ledger system 300-2 and executes the NFT transfer (T46).

[0090] When the NFT transfer request information and NFT sending information generated in the first distributed ledger system 300-1 are received by the second distributed ledger system 300-2, the second distributed ledger system 300-2 executes an NFT acceptance process to accept the NFT to be transferred using known blockchain technology (S47). The second distributed ledger system 300-2 then sends a notification that the NFT transfer is complete (NFT transfer completion notification) to the user terminal device 100 and the server device 200 (T47). Here, the user can confirm that the selected NFT has been transferred by operating the user terminal device 100 to check the wallet connected to the game app. Meanwhile, the server device 200 can confirm the NFT transfer because the user's wallet is connected to the game app.

[0091] When the server device 200 receives the NFT transfer completion notification sent from the second distributed ledger system 300-2 via the communication interface 213, the processor 212 of the server device 200 updates the item management table stored in the memory 211 (S48). Specifically, the processor 212 of the server device 200 updates the item management table of FIG. 6 by adding one to the "number of NFTs that can be issued" in the information of the row related to the item that is the original content to be NFTized. Furthermore, if the memory 211 stores information about which distributed ledger system (blockchain) the NFT is managed by, that information is also updated. That is, the processor 212 of the server device 200 identifies the row in the item management table whose information should be updated from the NFT transfer completion notification (for example, the row with the user ID U1 and the item ID X1) and updates the "number of NFTs that can be issued." Here, since the NFT transfer completion notification includes owner information (NFT owner account) of the NFT to be transferred, the processor 212 of the server device 200 can identify the row that needs to be updated.

[0092] (E) Processing of transfer of ownership of items Fig. 11 is a diagram showing a processing sequence executed between the user terminal device 100 and the server device 200 according to an embodiment of the present disclosure. Specifically, Fig. 11 is a diagram showing a processing sequence executed between the user terminal device 100 and the server device 200 until an item, which is digital content acquired in a game, is transferred to another user and ownership is changed.

[0093] First, as shown in FIG. 11, processor 112 of user terminal device 100 receives a user's item selection via input interface 115 and generates item selection information (S51). The item selection information includes information related to the item to be transferred, such as an item ID. More specifically, the user's operation input is to display a list of items acquired by operating user terminal device 100 on the display, and select the item to be transferred from the list. Then, processor 112 of user terminal device 100 transmits the generated item selection information to server device 200 via communication interface 114 (T51).

[0094] Next, according to FIG. 11, the processor 112 of the user terminal device 100 receives a user's selection of a transferee of the item via the input interface 115, and generates transferee information for the item (S52). The transferee information includes information such as the user ID of the user to whom the item is to be transferred. More specifically, the user inputs an operation such as inputting the user ID of the transferee on the screen displayed on the user terminal device 100 after the item is selected (S51), generating transferee information, and pressing an OK button or the like. Then, the processor 112 of the user terminal device 100 transmits the transferee information to the server device 200 via the communication interface 114 (T52).

[0095] Next, as shown in FIG. 11, the processor 112 of the user terminal device 100 receives the user's item transfer decision process via the input interface 115 and generates item transfer decision information (S53). This decision information is information indicating the user's final intention in the process of requesting an item transfer. As a more specific user input, after the transferee decision process (S52), the user information of the transferor and transferee and the transfer fee are displayed, and the OK button is pressed, generating the item transfer decision information. Then, the processor 112 of the user terminal device 100 transmits the generated item transfer decision information to the server device 200 via the communication interface 114 (T53).

[0096] Although the above-described transmission of information from T51 to T53 has been processed so that each piece of information is transmitted in stages, it is also possible to transmit each piece of information all at once. That is, the user terminal device 100 may sequentially perform the processes from S51 to S53, and after the process of S53 is completed, the information may be transmitted all at once, and the server device 200 may then perform a process in response to the request from the user terminal device 100 (an item transfer request process, which will be described later).

[0097] When the server device 200 receives the information generated by the user terminal device 100 (item selection information, transferee information, and decision information) via the communication interface 213, the processor 212 of the server device 200 performs an item transfer request process based on the information (S54). Specifically, the processor 212 of the server device 200 reads information about the item to be transferred (i.e., the item ID), information about the transferor and transferee of the item (i.e., the user ID), etc., based on the received information, and updates the corresponding items in the item management table. That is, the processor 212 of the server device 200 identifies a row to be updated in the item management table (e.g., a row with user ID U1 and item ID X1) based on the information received from the user terminal device 100, and updates the "user ID." Here, since there is no change in the owner of the NFT, the "NFT owner account" is not updated. Thereafter, when the item management table is updated in the server device 200, the server device 200 transmits a notification to the effect that the item transfer has been completed (item transfer completion notification) to the user terminal device 100 (T54).

[0098] 8. Processing flow executed in the server device 200 Below, we will explain in detail the series of processing flows executed by the server device 200 for each process related to NFT issuance, NFT transfer, NFT movement, and item transfer.

[0099] (A) Processing related to issuing NFTs corresponding to items 12A is a diagram showing a processing flow executed by the server device 200 according to an embodiment of the present disclosure. Specifically, FIG. 12A is a diagram showing a processing flow from item selection to updating of the item management table upon completion of NFT issuance. This processing flow is mainly performed by the processor 212 of the server device 200 reading and executing a program stored in the memory 211.

[0100] 12A, the processor 212 of the server device 200 determines whether or not item selection information has been received from the user terminal device 100 (S111). Next, if the processor 212 of the server device 200 has received item selection information (S111: Yes), the processor 212 of the server device 200 determines whether or not wallet information has been received from the user terminal device 100 (S112). After that, if the processor 212 of the server device 200 has received wallet information (S112: Yes), the processor 212 of the server device 200 determines whether or not NFT issuance decision information has been received from the user terminal device 100 (S113). If the processor 212 of the server device 200 has not received the specified information in S111 to S113 (No in each step), the NFT issuance request is canceled, and this flow ends.

[0101] On the other hand, when processor 212 of server device 200 receives the decision information to issue an NFT (S113: Yes), it determines whether the number of NFTs that can be issued for the selected item is 1 or greater (step S114). Specifically, processor 212 of server device 200 identifies the row to refer to in the item management table (for example, the row where user ID is U1 and item ID is X1) based on the received item selection information, reads the "number of NFTs that can be issued" and determines whether it is 1 or greater. If the "number of NFTs that can be issued" is 1 or greater (S114: Yes), the NFT issuance limit has not been reached, so the process proceeds to S116. However, if the "number of NFTs that can be issued" is less than 1 (i.e., zero), the NFT issuance limit has been reached, so the process ends (S114: No).

[0102] Next, if the "number of issuable NFTs" is 1 or greater (S114: Yes), the processor 212 of the server device 200 determines that the conditions for performing the NFT issuance request process are met, and generates NFT issuance request information (S115). The NFT issuance request information is information that includes information on the item to be converted into an NFT and information on the person who will be the owner of the NFT, based on the received information. The processor 212 of the server device 200 then transmits the generated NFT issuance request information, along with an NFT issuance process request, to the first distributed ledger system 300-1 via the communication interface 213 (S116).

[0103] Next, the processor 212 of the server device 200 determines whether or not an NFT issuance completion notification has been received from the first distributed ledger system 300-1 (S117). Here, the processor 212 of the server device 200 does not proceed to the next step until it receives the NFT issuance completion notification (S117: No), and proceeds to the next step upon receiving the NFT issuance completion notification (S117: Yes). Then, upon receiving the NFT issuance completion notification, the processor 212 of the server device 200 updates the item management table stored in the memory 211 (S118). Specifically, the processor 212 of the server device 200 updates the item management table of FIG. 6 by adding new information to the "NFT ID" and "NFT owner account" columns in the information for the row related to the item that is the original content to be converted into an NFT, and by decrementing the value of the "Number of NFTs that can be issued" by one.

[0104] (B) Processing of transfer of ownership of NFTs 12B is a diagram showing a processing flow executed by the server device 200 according to an embodiment of the present disclosure. Specifically, FIG. 12B is a diagram showing a processing flow from a request for an NFT transfer to updating of the item management table upon completion of the issuance of the NFT. This processing flow is mainly performed by the processor 212 of the server device 200 reading and executing a program stored in the memory 211.

[0105] According to FIG. 12B, the processor 212 of the server device 200 determines whether or not wallet information has been received from the user terminal device 100 (S211). Next, if the processor 212 of the server device 200 has received wallet information (S211: Yes), it determines whether or not NFT information has been received from the user terminal device 100 (S212). Subsequently, if the processor 212 of the server device 200 has received NFT information (S212: Yes), it determines whether or not transferee information has been received from the user terminal device 100 (S213). Thereafter, if the processor 212 of the server device 200 has received transferee information (S212: Yes), it determines whether or not NFT transfer decision information has been received from the user terminal device 100 (S214). If the processor 212 of the server device 200 has not received the specified information in S211 to S214 (No in each step), the NFT transfer request is canceled, and this flow ends.

[0106] Meanwhile, the processor 212 of the server device 200 receives the NFT transfer decision information (S214: Yes), and generates NFT transfer request information, assuming that all the information necessary to process the NFT transfer request is complete (S215). The NFT transfer request information includes the NFT to be transferred, as well as the transferor and transferee of the NFT, based on the received information. The processor 212 of the server device 200 then transmits the generated NFT transfer request information, along with an NFT transfer processing request, to the first distributed ledger system 300-1 via the communication interface 213 (S216).

[0107] Next, the processor 212 of the server device 200 determines whether or not an NFT transfer completion notification has been received from the first distributed ledger system 300-1 (S217). Here, the processor 212 of the server device 200 does not proceed to the next step until it receives the NFT transfer completion notification (S217: No), and proceeds to the next step upon receiving the NFT transfer completion notification (S217: Yes). Then, upon receiving the NFT transfer completion notification, the processor 212 of the server device 200 updates the item management table stored in the memory 211 (S218). Specifically, the processor 212 of the server device 200 updates the "NFT owner account" in the information in the row related to the item that is the original content to be converted into an NFT in the item management table of FIG. 6.

[0108] (C) Processing related to the transfer of NFTs 12C is a diagram showing a processing flow executed by the server device 200 according to an embodiment of the present disclosure. Specifically, FIG. 12C is a diagram showing a processing flow from a request to transfer an NFT to another blockchain to updating the item management table upon completion of the transfer of the NFT. This processing flow is mainly performed by the processor 212 of the server device 200 reading and executing a program stored in the memory 211.

[0109] According to FIG. 12C, the processor 212 of the server device 200 determines whether or not wallet information has been received from the user terminal device 100 (S311). Next, if the processor 212 of the server device 200 has received wallet information (S311: Yes), it determines whether or not NFT information has been received from the user terminal device 100 (S312). Subsequently, if the processor 212 of the server device 200 has received NFT information (S312: Yes), it determines whether or not transfer destination information has been received from the user terminal device 100 (S313). Thereafter, if the processor 212 of the server device 200 has received transfer destination information (S312: Yes), it determines whether or not NFT transfer decision information has been received from the user terminal device 100 (S314). If the processor 212 of the server device 200 has not received the specified information in S311 to S314 (No in each step), the NFT transfer request is canceled, and this flow ends.

[0110] Meanwhile, the processor 212 of the server device 200 receives the NFT transfer decision information (S314: Yes), and generates NFT transfer request information, assuming that all the information necessary to process the NFT transfer request is complete (S315). The NFT transfer request information includes the NFT to be moved to another blockchain, as well as the source and destination of the NFT, based on the received information. The processor 212 of the server device 200 then transmits the generated NFT transfer request information, along with an NFT transfer processing request, to the first distributed ledger system 300-1 via the communication interface 213 (S316).

[0111] Next, processor 212 of server device 200 determines whether an NFT transfer completion notification has been received from second distributed ledger system 300-2 (S317). Here, processor 212 of server device 200 does not proceed to the next step until it receives an NFT transfer completion notification (S317: No), and proceeds to the next step upon receiving an NFT transfer completion notification (S317: Yes). Then, upon receiving the NFT transfer completion notification, processor 212 of server device 200 updates the item management table stored in memory 211 (S318). Specifically, processor 212 of server device 200 updates the item management table of FIG. 6 by increasing the "number of NFTs that can be issued" by one in the information for the row related to the item that is the original content to be converted into an NFT.

[0112] (D) Processing of transfer of ownership of items 12D is a diagram showing a processing flow executed in the server device 200 according to an embodiment of the present disclosure. Specifically, FIG. 12D is a diagram showing a processing flow from a request to transfer an item acquired in a game to another user to updating the item management table upon completion of the item transfer. This processing flow is mainly performed by the processor 212 of the server device 200 reading and executing a program stored in the memory 211.

[0113] 12D, processor 212 of server device 200 determines whether or not item selection information has been received from user terminal device 100 (S411). Next, if processor 212 of server device 200 has received item selection information (S411: Yes), processor 212 determines whether or not transferee information has been received from user terminal device 100 (S412). Thereafter, if processor 212 of server device 200 has received transferee information (S412: Yes), processor 212 determines whether or not item transfer decision information has been received from user terminal device 100 (S413). If processor 212 of server device 200 has not received the predetermined information in S411 to S413 (No in each step), the item transfer request is canceled, and this flow ends.

[0114] Meanwhile, the processor 212 of the server device 200 receives the item transfer decision information (S413: Yes). It then determines that all the information necessary for the item transfer process is complete and executes the item transfer process (S414). Specifically, based on the received information, the processor 212 of the server device 200 reads information about the item to be transferred (i.e., the item ID), information about the transfer source and transferee of the item (i.e., the user ID), and other information, and updates the corresponding items in the item management table. That is, based on the information received from the user terminal device 100, the processor 212 of the server device 200 identifies a row to be updated in the item management table (e.g., a row with user ID U1 and item ID X1) and updates the "user ID." Since the owner of the NFT remains unchanged, the "NFT owner account" is not updated. Once the item management table has been updated in the server device 200, the server device 200 transmits a notification (item transfer completion notification) to the user terminal device 100 indicating that the item transfer has been completed.

[0115] 9. Summary of the embodiments of the present disclosure The server device 200 according to an embodiment of the present disclosure is a processing device including at least one processor. The at least one processor 212 is configured to: when a user acquires an item of digital content, generate content owner information linking the user to the item and store it in memory 211; when a request to issue an NFT for the item is received, issue an NFT issuance process request to the distributed ledger system; when a completion of issuance of the NFT for the item is received, generate NFT owner information linking the user to the NFT based on the content owner information and store it in memory 211; and when a request to transfer ownership of only the NFT is received, maintain the content owner information and update the NFT owner information. This configuration allows the owner of an NFT to be managed by linking it to the owner of the item, while also enabling the owner of the item and the owner of the NFT to be identified and managed separately if the NFT is circulated independently of the item. In other words, the server device 200 according to an embodiment of the present disclosure allows items and NFTs to be managed independently and circulated independently.

[0116] The processor 212 of the server device 200 according to an embodiment of the present disclosure is configured to execute processing to calculate the number of NFTs that can be issued in association with the item, and store the number of NFTs that can be issued in association with the content owner information in the memory 211. For example, the processor 212 of the server device 200 according to an embodiment of the present disclosure may calculate the number of NFTs that can be issued based on characteristic information of the item or user information of the user. This configuration makes it possible to control the amount of NFTs in circulation for a given item, thereby optimizing the balance between the value and circulation of NFTs.

[0117] The processor 212 of the server device 200 according to an embodiment of the present disclosure is configured to execute a process for, when generating the NFT owner information, subtracting one from the number of NFTs that can be issued and storing the result in the memory 211. This configuration makes it possible to appropriately manage the number of NFTs that can be issued for one item, thereby optimizing the balance between the value and circulation of NFTs.

[0118] When the processor 212 of the server device 200 according to an embodiment of the present disclosure receives a request to transfer the NFT from the distributed ledger system to another distributed ledger system, the processor 212 executes processing to make an NFT transfer processing request to the distributed ledger system. This configuration enables the transfer of NFTs between different blockchains, thereby promoting the circulation of NFTs.

[0119] The processor 212 of the server device 200 according to an embodiment of the present disclosure is configured to, upon receiving the completion of the transfer of the NFT, execute a process to increment the number of NFTs that can be issued by one and store the incremented number in the memory 211. This configuration makes it possible to appropriately manage the number of NFTs that can be issued for one item for each blockchain, thereby optimizing the balance between the value and circulation of NFTs.

[0120] A processing program according to an embodiment of the present disclosure causes a computer including at least one processor 212 to function as follows: when a user acquires digital content, the at least one processor 212 links the user to the content, generates content owner information, and stores the information in the memory 211; when a request to issue an NFT for the content is accepted, the processor 212 issues an NFT issuance processing request to the distributed ledger system; when a completion of issuance of the NFT for the content is accepted, the processor 212 links the user to the NFT based on the content owner information, generates NFT owner information, and stores the NFT owner information in the memory 211; and when a request to transfer ownership of only the NFT is accepted, the processor 212 maintains the content owner information and updates the NFT owner information. This configuration allows the server device 200 according to an embodiment of the present disclosure to manage NFT owners by linking them to item owners, while also enabling the owner of the item and the owner of the NFT to be identified and managed separately if the NFT is distributed independently of the item. In other words, the server device 200 according to an embodiment of the present disclosure allows items and NFTs to be managed independently and circulated independently.

[0121] A processing method according to an embodiment of the present disclosure is a processing method executed by the processor 212 in a computer including the processor 212. The processing method includes the steps of: when a user acquires digital content, linking the user to the content and generating content owner information and storing the information in the memory 211; when a request to issue an NFT for the content is received, issuing an NFT issuance processing request to the distributed ledger system; when a completion of issuance of the NFT for the content is received, linking the user to the NFT based on the content owner information and generating NFT owner information and storing the information in the memory 211; and when a request to transfer ownership of only the NFT is received, maintaining the content owner information and updating the NFT owner information. This configuration allows the owner of an NFT to be managed by linking it to the owner of an item, while also enabling the owner of the item and the owner of the NFT to be identified and managed separately if the NFT is circulated independently of the item. In other words, the server device 200 according to an embodiment of the present disclosure enables items and NFTs to be managed independently and circulated independently.

[0122] 10. Variations In the above embodiment, the description was given assuming that items and NFTs are circulated separately, but the acquired NFT may be considered an item, and the item may be circulated simultaneously with the distribution of the NFT. Such a case will be described with reference to FIG. 13. FIG. 13 is a diagram that schematically illustrates an overview of the transfer of items and NFTs in a processing system 1 according to a modified example of the present disclosure.

[0123] As shown in Figure 13, when a first user acquires an NFT for an item, the item is managed as an integrated state with the NFT (NFT = item). As a result, the first user is unable to use the item in the game. When the NFT is subsequently transferred to a second user, a change in the NFT owner is recorded. The second user who received the NFT then redeems the NFT for an item, and the item acquired by the first user is considered to have been transferred to the second user, and a change in the item owner is recorded. In other words, the NFT acts like an exchange ticket for the item.

[0124] In this modified example, as in the above embodiment, the NFT may be circulated on another blockchain after conversion to an NFT. In other words, the original content of the NFT may be converted to an NFT and circulated between blockchains, providing an opportunity for a change of ownership.

[0125] When an item is converted into an NFT, all information about the item may be included, but this is not limited to this. For example, the NFT may include only identification information that serves as proof of ownership of the NFT, or other information may be added to the NFT. The other information may be information about the image or video itself, or information such as the title of the work or the creator. In other words, it is preferable to convert an NFT to include at least identification information that serves as proof of ownership of the NFT, and the other information may be selected as appropriate depending on the content of the digital content that is the subject of the NFT, the blockchain environment, and other circumstances.

[0126] If all information about an item is included in the NFT, all information about the item (owner, level, and other item-related information) will be carried over from the NFT and reproduced in the game when the NFT is redeemed for an item. If only identification information that serves as proof of ownership of the NFT is included in the NFT, only the item's owner information will be updated when the NFT is redeemed for an item, and other information (level, and other item-related information) will remain as is and be linked to the updated item's owner information.

[0127] In this way, by converting digital content into NFTs and distributing the digital content and NFTs simultaneously, the distribution of digital content using NFTs can be promoted. In other words, if there is an issue of wanting to widely distribute digital content while preventing unauthorized duplication of the digital content, rather than distributing the digital content itself in the general public, the digital content can be distributed in an NFTized state and restored to a usable state based on the NFT.

[0128] As described above, this variant provides the following processing device: A processing device including at least one processor, configured to execute processes to: when a user acquires digital content, link the user to the content and generate content owner information and store it in memory; when a request to issue an NFT for the content is accepted, make an NFT issuance processing request to a distributed ledger system; when acceptance of completion of issuance of the NFT for the content, link the user to the NFT based on the content owner information and generate NFT owner information and store it in memory; when acceptance of a request to transfer ownership of the NFT, update the NFT owner information; and when acceptance of a redemption request for the digital content based on the NFT, inherit the information included in the NFT to the digital content.

[0129] Furthermore, the at least one processor is configured to execute processing to issue an NFT transfer processing request to the distributed ledger system upon receiving a request to transfer the NFT from the distributed ledger system to another distributed ledger system. Naturally, the contents of the processing device according to the modified example can be diverted to a processing program and a processing method, as in the embodiment, and the modified example also includes a processing program and a processing method.

[0130] In the above embodiment and modified examples, items obtained in a game are used as an example of content that is the original data to be converted into NFTs, but items and NFTs may also be managed for digital items that can be obtained outside of a game. For example, digital items (trading cards) that can be purchased on an e-commerce site and their NFTs may be managed so that they can be distributed independently.

[0131] Furthermore, content that can be turned into NFTs may be something other than items. For example, digital content in genres such as art, manga, or anime may be targeted, and the digital content and its NFT may be managed so that they can be distributed independently.

[0132] The processes and procedures described herein can be implemented not only by those explicitly described in this disclosure, but also by software, hardware, or a combination thereof. Specifically, the processes and procedures described herein can be implemented by implementing logic corresponding to the processes in media such as integrated circuits, volatile memory, nonvolatile memory, magnetic disks, and optical storage. Furthermore, the processes and procedures described herein can be implemented as computer programs and executed by various computers, including user terminal devices and server devices.

[0133] Although processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, multiple software, multiple components, and / or multiple modules. Furthermore, although various information described herein is described as being stored in a single memory or storage unit, such information may be stored in multiple memories within a single device or multiple memories distributed across multiple devices. Furthermore, software and hardware elements described herein may be realized by integrating them into fewer components or by decomposing them into more components. [Explanation of symbols]

[0134] 100 User terminal device 200 Server device 300 Distributed Ledger System 300-1 First Distributed Ledger System 300-2 Second Distributed Ledger System

Claims

1. A processing device comprising at least one processor, The at least one processor: When a user acquires digital content, the system associates the user with the content, generates content owner information, and stores the information in a memory; When a request to issue an NFT for the content is received, an NFT issuance processing request is made to the distributed ledger system; Upon receiving a completion of the issuance of the NFT for the content, the device associates the user with the NFT based on the content owner information, generates NFT owner information, and stores the information in the memory; Upon receiving a request to transfer ownership of only the NFT, maintain the content owner information and update the NFT owner information. a processing unit configured to perform processing for:

2. The processing device according to claim 1 , wherein the at least one processor is configured to execute a process for calculating the number of NFTs that can be issued in association with the content, and storing the number of NFTs that can be issued in the memory in association with the content owner information.

3. The processing device according to claim 2 , wherein the at least one processor is configured to execute a process for calculating the number of NFTs that can be issued based on characteristic information of the content or user information of the user.

4. The processing device according to claim 2 or 3, wherein the at least one processor is configured to execute a process for subtracting one from the number of NFTs that can be issued and storing the result in the memory when generating the NFT owner information.

5. 2. The processing device of claim 1, wherein the at least one processor is configured to execute a process to, upon receiving a request to transfer the NFT from the distributed ledger system to another distributed ledger system, issue an NFT transfer processing request to the distributed ledger system.

6. The processing device according to claim 2 , wherein the at least one processor is configured to execute a process for, upon receiving a notification that the NFT has been transferred, incrementing the number of NFTs that can be issued by one and storing the incremented number in the memory.

7. In a computer having at least one processor, the at least one processor When a user acquires digital content, the system associates the user with the content, generates content owner information, and stores the information in a memory; When a request to issue an NFT for the content is received, an NFT issuance processing request is made to the distributed ledger system; Upon receiving a completion of the issuance of the NFT for the content, the device associates the user with the NFT based on the content owner information, generates NFT owner information, and stores the information in the memory; Upon receiving a request to transfer ownership of only the NFT, maintain the content owner information and update the NFT owner information. A processing program that makes it function like this.

8. A processing method executed by at least one processor in a computer having the at least one processor, comprising: When a user acquires digital content, generating content owner information by linking the user with the content and storing the content owner information in a memory; receiving a request to issue an NFT for the content, and then issuing an NFT issuance processing request to a distributed ledger system; Upon receiving a completion of the issuance of the NFT for the content, generating NFT owner information by linking the user and the NFT based on the content owner information and storing the NFT owner information in the memory; maintaining the content owner information and updating the NFT owner information upon receiving a request to transfer ownership of the NFT only; A processing method comprising:

Images