Information processing device, information processing system, and information processing program

Abstract

To provide an information processing device capable of disseminating game program data and derivative creation data more appropriately.SOLUTION: A server device 20 includes a storage unit 21 and a token management unit 232. The storage unit 21 stores game program data and MOD data. The token management unit 232 issues an NFT corresponding to the game program data and an NFT corresponding to the MOD data on the distributed ledger. The NFT corresponding to the game program data includes URL information that allows access to the game program data. The NFT corresponding to the MOD data includes URL information that allows access to the MOD data.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to an information processing device, an information processing system, and an information processing program. [Background technology]

[0002] A conventional game system is described in the following Patent Document 1. In this game system, a user operates a terminal device to download a game program, thereby enabling the user to play a game on the terminal device. [Prior art documents] [Patent documents]

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

[0004] In recent years, more and more users are playing games through general-purpose PCs (Personal Computers) instead of dedicated home game consoles. Currently, most PC games are available for purchase as downloads on the Internet through specific sales companies. Therefore, companies that develop PC games have no choice but to sell their games through such specific sales companies, and must, for example, pay high fees to the specific sales companies or comply with excessive restrictions on game content imposed by the specific sales companies. This makes it difficult for developers to sell their games as they wish.

[0005] In addition, in recent PC games, data that allows modification of game content, so-called MOD data, has become widespread. Currently, users are free to distribute derivative data such as MOD data, so there is a considerable risk of malware being installed when the derivative data is installed in a game. Therefore, there is still room for improvement regarding the spread of derivative data.

[0006] The present invention has been made in consideration of these circumstances, and its purpose is to provide an information processing device, an information processing system, and an information processing program that are capable of more appropriately disseminating game program data and derivative work data. [Means for solving the problem]

[0007] An information processing device that solves the above problem includes a storage unit and a token management unit. The storage unit stores game program data and derivative data derived from the game. The token management unit issues a non-fungible first token corresponding to the game program data and a non-fungible second token corresponding to the derivative data on a distributed ledger. The first token includes first access information that allows access to the game program data. The second token includes second access information that allows access to the derivative data.

[0008] An information processing system that solves the above problem includes a storage unit and a token management unit. The storage unit stores game program data and derivative data derived from the game. The token management unit issues a non-fungible first token corresponding to the game program data and a non-fungible second token corresponding to the derivative data on a distributed ledger. The first token includes first access information that allows access to the game program data. The second token includes second access information that allows access to the derivative data.

[0009] An information processing program that solves the above problem causes a computer to store game program data and derivative data created from the game in a memory unit, and to issue a non-fungible first token corresponding to the game program data and a non-fungible second token corresponding to the derivative data on a distributed ledger, the first token including first access information that allows access to the game program data, and the second token including second access information that allows access to the derivative data.

[0010] According to these information processing devices, information processing systems, and information processing programs, since the first token is associated with the game program data, the uniqueness of the game program data can be ensured based on the first token. Similarly, since the second token is associated with the derivative data, the uniqueness of the derivative data can be ensured based on the second token. Therefore, according to the above information processing devices, information processing systems, and information processing programs, since the uniqueness of each of the game program data and the derivative data can be ensured, for example, a developer can sell and distribute the game program data and the derivative data by himself / herself without going through a specific sales company. Therefore, it is possible to disseminate the game program data and the derivative data more appropriately. Effect of the Invention

[0011] According to the information processing device, information processing system, and information processing program of the present invention, it is possible to disseminate game program data and derivative creation data more appropriately. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of an information processing system according to a first embodiment. [Diagram 2] FIG. 2 is a block diagram showing the hardware configuration of a terminal device and a server device according to the first embodiment. [Diagram 3] FIG. 2 is a block diagram showing the functional configuration of a server device according to the first embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a distribution pattern of game program data in the information processing system of the first embodiment. [Diagram 5] FIG. 2 is a diagram showing an example of information included in an NFT corresponding to program data of the game of the first embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of a distribution pattern of game program data in the information processing system of the first embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of a distribution mode of MOD data in the information processing system according to the first embodiment. [Figure 8] FIG. 2 is a diagram showing an example of information included in an NFT corresponding to MOD data of the first embodiment. [Figure 9] 3A and 3B are diagrams illustrating a money transfer mode in the first embodiment. [Figure 10] FIG. 2 is a block diagram showing the functional configuration of a terminal device according to the first embodiment. [Figure 11] 4 is a sequence chart showing an example of the operation of the information processing system according to the first embodiment. [Figure 12] 4 is a sequence chart showing an example of the operation of the information processing system according to the first embodiment. [Figure 13] 4 is a sequence chart showing an example of the operation of the information processing system according to the first embodiment. [Figure 14] FIG. 11 is a diagram showing an example of information included in an NFT corresponding to MOD data of the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an information processing device, an information processing system, and an information processing program according to an embodiment of the present invention will be described with reference to the drawings. In order to facilitate understanding of the description, the same components in each drawing are denoted by the same reference numerals as much as possible, and duplicated descriptions will be omitted. First Embodiment The information processing system 10 shown in FIG. 1 is a system for managing and selling program data of a game developed by a developer, save data of the game, and MOD data that is derivatively created by a secondary creator other than the developer. Save data is data that saves the state of the game during its progress. By loading the save data into the game, it is possible to start the game reflecting the state corresponding to the save data. MOD data is data that can be installed into the game to modify the content of the game. Examples of modifications to the game content include adding a scenario different from the original game, adding a new game character, and adding a new graphic model of the game character. In this embodiment, the MOD data corresponds to the derivative data and the modification program data.

[0014] 1, an information processing system 10 includes a server device 20, a distributed ledger system 30, and a terminal device 40. The server device 20, the distributed ledger system 30, and the terminal device 40 are connected to each other via a network line N so that they can communicate with each other. The server device 20 is a device that provides a marketplace where game program data and the like can be bought and sold on the Internet. In the marketplace provided by the server device 20, in addition to buying and selling game program data, it is also possible to buy and sell save data and MOD data. The server device 20 is owned, for example, by a management company of the marketplace. The management company of the marketplace may be a developer that develops game program data, or may be a different company. By the developer managing the server device 20, the developer can manage various data such as game program data and MOD data, as well as the buying and selling of these data, by himself / herself, without going through a specific sales company or the like. In this embodiment, the server device 20 corresponds to an information processing device.

[0015] The distributed ledger system 30 has multiple nodes 31. Each node 31 has a distributed ledger 310. The distributed ledger system 30 issues non-fungible tokens, so-called NFTs (Non Fungible Tokens), corresponding to the game program data and MOD data, respectively, based on a request from the server device 20. The distributed ledger system 30 stores the issued NFTs in the distributed ledger 310 of each node 31 using known distributed ledger technology.

[0016] The terminal device 40 is, for example, any one of a personal computer, a smartphone, and a tablet terminal. The terminal device 40 is owned by each user who uses the information processing system 10 of the present embodiment, such as a player who plays a game or a creator who creates MOD data. The user can use the marketplace provided by the server device 20, for example, by operating the terminal device 40 to access the server device 20. After purchasing program data of a game on the marketplace, the user can play the game on the terminal device 40 by installing the program data on the terminal device 40. In addition, the user can sell the MOD data on the marketplace by operating the terminal device 40 and then uploading the MOD data from the terminal device 40 to the server device 20. Furthermore, the user can purchase MOD data created by another user using the marketplace, and then play a game in which the MOD data is reflected by installing the MOD data on the terminal device 40.

[0017] (Hardware configuration of server device and terminal device) As shown in FIG. 2, the server device 20 and the terminal device 40 have, as hardware configurations, a processor 11, a storage device 12, a communication device 13, an input device 14, and an output device 15. The processor 11 is a CPU (Central Processing Unit) or a GPU (Graphical Processing Unit). The storage device 12 is, for example, composed of at least one of a memory, an HDD (Hard Disk Drive), and an SSD (Solid State Drive). The communication device 13 performs wired communication or wireless communication. The input device 14 is a device that accepts input operations by a user, and is, for example, composed of at least one of a keyboard, a touch panel, a mouse, and a microphone. The output device 15 is a device that outputs information, and is, for example, composed of at least one of a display, a touch panel, and a speaker.

[0018] (Server device configuration) As shown in FIG. 3, the server device 20 includes, as its functional components, a storage unit 21, a communication unit 22, and a control unit 23. The storage unit 21 has a function of storing various programs and various data such as a user database 210, a game database 211, and a MOD database 212. The storage unit 21 can be realized, for example, by the storage device 12 shown in FIG.

[0019] The user database 210 stores account information, game program data purchase history, MOD data purchase history, wallet information, and user setting information for each user who uses the marketplace. The account information includes a user's identification number and password used when using the marketplace, as well as information on whether or not the user owns NFTs of game program data and MOD data. The wallet information includes bank account information and credit card information registered by the user. The user setting information includes, for example, information on the selling price of MOD data set by the user.

[0020] The game database 211 stores program data of games created by each developer and save data of the games. URL information enabling access to the data on the Internet is individually assigned to the program data of each game. The game database 211 stores the program data of each game in association with the corresponding URL information, etc. Similarly, the save data of each game is individually assigned with URL information enabling access to the save data on the Internet. The game database 211 stores the save data in association with the corresponding URL information, etc.

[0021] MOD data created by each user is stored in MOD database 212. URL information that enables access to the MOD data over the Internet is individually assigned to each MOD data. In MOD database 212, the corresponding URL information and the like are stored in association with each MOD data.

[0022] The communication unit 22 has a function of performing various communications with the distributed ledger system 30 and the terminal device 40 via the network line N. The communication unit 22 can be realized, for example, by the processor 11 shown in FIG. 2 executing a program stored in the storage unit 21 to control the communication device 13.

[0023] The control unit 23 shown in Fig. 3 has a function of comprehensively controlling the server device 20. The control unit 23 can be realized, for example, by the processor 11 shown in Fig. 2 executing a program stored in the storage unit 21. The control unit 23 includes, as its functional configuration, a data registration unit 230, a data transmission unit 231, a token management unit 232, and a transaction processing unit 233.

[0024] (Data Registration Department) When a request to register MOD data is received from terminal device 40, data registration unit 230 registers the MOD data in MOD database 212. Specifically, the identification number of the user who created the MOD data is transmitted from terminal device 40 to server device 20 together with the MOD data. When data registration unit 230 receives the MOD data and the user identification number via communication unit 22, it creates dedicated URL information that enables access to the MOD data, and registers the created URL information, the MOD data, the identification number of the user who created the MOD data, etc. in the MOD database 212 in association with each other.

[0025] (Data transmission section) When the URL information of the game program data is accessed from the terminal device 40, the data transmission unit 231 transmits the game program data corresponding to the URL information to the terminal device 40 via the communication unit 22. This makes it possible to install the game program data in the terminal device 40. By installing the game program data in the terminal device 40, it becomes possible to play the original game on the terminal device 40.

[0026] Furthermore, when the URL information of the save data is accessed from the terminal device 40, the data transmission unit 231 transmits the save data corresponding to the URL information to the terminal device 40 via the communication unit 22. This makes it possible to play a game on the terminal device 40 that reflects the state corresponding to the save data by using the save data when playing the game on the terminal device 40.

[0027] Furthermore, when the URL information of the MOD data is accessed from the terminal device 40, the data transmission unit 231 transmits the MOD data corresponding to the URL information to the terminal device 40 via the communication unit 22. This makes it possible to install the MOD data in the terminal device 40. By installing the MOD data in the terminal device 40, it becomes possible to play a game modified based on the MOD data on the terminal device 40.

[0028] (Token Management Department) Each time game program data and MOD data are purchased, the token management unit 232 requests the distributed ledger system 30 to issue the corresponding NFT.

[0029] For example, as shown in FIG. 4, if user A11 purchases game program data on the marketplace MP, the token management unit 232 requests the distributed ledger system 30 to issue an NFT 101 corresponding to the game program data. 5, the NFT101 includes, in addition to the token ID, the issuer of the NFT101, the owner of the NFT101, metadata corresponding to the game program data, transaction data, and the like. The token ID field registers information on an identification number unique to the NFT101. The issuer field of the NFT101 registers, for example, the name of the management company of the server device 20, and the like. The owner field of the NFT101 registers, for example, the identification number of the user A11 who purchased the game program data.

[0030] The metadata includes the game name, the version of the metadata, the creator name of the developer, the primary sales price of the game program data, the secondary sales price, the server information of the game program data, the server information of the save data, and the private key information. The creator name of the developer is the name of the developer who actually created the game at the developer. The primary sales price item is the price at which the game program data is initially purchased. The secondary sales price item is the price at which the game program data once purchased is sold to another user either alone or together with the save data. For example, the primary sales price is used when a primary purchaser first purchases game program data on the Marketplace MP. The secondary sales price is used when a secondary purchaser purchases the game program data purchased by the primary purchaser together with the save data. The primary sales price is set, for example, by the developer of the game. The secondary sales price is set, for example, by the purchaser who purchased the game program data. The server information item of the game program data is registered with URL information at which the game program data can be accessed. The server information item of the save data is registered with URL information at which the save data corresponding to the game program data, in other words, the save data created by the user A11, can be accessed. The private key information item stores information on whether the game program data and save data are encrypted or not, and if they are encrypted, information on the encryption key.

[0031] Note that the metadata information of the NFT 101 shown in FIG. 5 can be overwritten only by the owner of the NFT 101. For example, as shown in FIG. 4, when user A11 purchases game program data on the marketplace MP, the owner of the game program data becomes user A11. In this case, user A11 is the only person who can edit the metadata of the NFT 101 corresponding to the game program data. By editing the metadata of the NFT 101, user A11 can, for example, set the secondary sales price by himself.

[0032] The transaction data item stores information about the transaction history of the NFT 101. The transaction data stores information about transactions such as transfers and sales of the NFT 101 that have been conducted up to now, for example, the transfer origin and transfer destination of the transaction in association with each other. In this embodiment, the NFT 101 corresponding to the game program data shown in Fig. 5 corresponds to the first token. Furthermore, the server information of the game program data included in the NFT 101 corresponds to the first access information capable of accessing the game program data. Furthermore, the server information of the save data included in the NFT 101 corresponds to the third access information capable of accessing the save data.

[0033] As shown in FIG. 4, when a user A12, who is different from the user A11, purchases game program data in the marketplace MP, the token management unit 232 requests the distributed ledger system 30 to issue an NFT 102, which is different from the NFT 101 owned by the user A11, as an NFT corresponding to the game program data. In this NFT 102, a token ID different from that of the NFT 101 is set. In other words, the NFT 102 is different from the NFT 101. In the NFT 102, information similar to that of the NFT 101 is basically registered in the items other than the token ID, but there are also items in which information different from that of the NFT 101 is registered. For example, an identification number corresponding to the user A12 is registered in the owner item in the NFT 102. In addition, URL information that allows access to the save data created by the user A12 is registered in the server information item of the save data in the NFT 102.

[0034] In this way, in this embodiment, different NFTs are issued unlimitedly for each program data of a purchased game. As shown in Fig. 6, assume that after a user A11 purchases game program data, the user A11 plays the game to create save data, and then sells the save data together with the game program data on the marketplace MP. When another user A13 purchases the game program data with the attached save data on the marketplace MP, the token management unit 232 executes a process to transfer the owner of the NFT 101. Specifically, the token management unit 232 requests the distributed ledger system 30 to execute a process to change the owner of the NFT 101 from user A11 to user A13.

[0035] 7, assume that user A12 creates MOD data based on the program data of the purchased game, and then uploads the MOD data to the server device 20. At this time, the token manager 232 requests the distributed ledger system 30 to issue an NFT 201 corresponding to the MOD data.

[0036] As shown in FIG. 8, the NFT201 includes, in addition to the token ID, the issuer of the NFT201, the owner of the NFT201, metadata corresponding to the MOD data, and transaction data. In the token ID field, information on an identification number unique to the NFT201, which is different from the token ID of the NFT102 corresponding to the game program data shown in FIG. 5, is registered. Therefore, the NFT201 of the MOD data is different from the NFT101 of the game program data. In the issuer field of the NFT201 shown in FIG. 8, for example, the name of the management company of the server device 20 is registered. In the owner field of the NFT201, the identification number of the user A12 who created the MOD data is registered. As shown in FIG. 7, when the user A12 starts selling MOD data and the MOD data has not been purchased by another user, the owner of the MOD data is set to the user A12 who created the MOD data.

[0037] The metadata includes the name of the game that runs on the MOD data, the name of the MOD data, the version of the game that runs on the MOD data, the creator of the MOD data, the version of the MOD data, the selling price of the program data of the game that runs on the MOD data, the selling price of the MOD data, server information for the MOD data, and private key information. The selling price of the MOD data is set, for example, by the user A12 who created the MOD data. The server information field for the MOD data registers URL information that enables access to the MOD data. The private key information field registers information on whether the MOD data is encrypted, and if it is encrypted, information on the encryption key.

[0038] The transaction data item stores information about the transaction history of the NFT 201. The transaction data stores information about transactions such as transfers and sales of the NFT 201 that have been conducted up to now, such as the transfer origin and transfer destination of the transaction, in association with each other. In this embodiment, the NFT 201 corresponding to the MOD data shown in Fig. 8 corresponds to the second token. Furthermore, the server information of the MOD data included in the NFT 201 corresponds to second access information that enables access to the MOD data.

[0039] The metadata of the NFT201 shown in Fig. 8 can be overwritten only by the owner. Therefore, for example, if the owner of the NFT201 is user A12 as shown in Fig. 8, user A12 can edit the metadata of the NFT201 to set, for example, the selling price of the MOD data by himself.

[0040] As shown in FIG. 7, if user A12 sells MOD data associated with NFT201 on the marketplace MP and then another user A21 purchases the MOD data associated with NFT201 on the marketplace MP, the token management unit 232 requests the distributed ledger system 30 to change the owner of the NFT201 corresponding to the MOD data from user A12 to user A21.

[0041] On the other hand, user A12 can sell multiple MOD data on the marketplace MP. For example, when selling MOD data other than the MOD data associated with NFT201, the token management unit 232 requests the distributed ledger system 30 to issue NFT202, which is different from NFT201, as an NFT corresponding to the MOD data. In this NFT202, a token ID different from that of NFT201 is set. In other words, NFT202 is different from NFT201. If user A22 purchases MOD data associated with this NFT202 on the marketplace MP, the token management unit 232 requests the distributed ledger system 30 to change the owner of NFT201 corresponding to the MOD data from user A12 to user A22.

[0042] In this way, in this embodiment, different NFTs are issued for each purchased MOD data, without limit. (Transaction Processing Unit) 3 executes various processes related to the marketplace MP, such as buying and selling of game program data on the marketplace MP, buying and selling of MOD data, etc. For example, when game program data or MOD data is purchased on the marketplace MP, the transaction processing unit 233 executes a deposit / withdrawal process related to the transaction.

[0043] Specifically, when a user operates the terminal device 40 to purchase game program data, the transaction processing unit 233 executes a payment process from the user to the marketplace MP based on the wallet information of the user. For example, when a user A11 purchases game program data as shown in Fig. 4, the transaction processing unit 233 acquires information on the primary selling price of the game program data from the game database 211 and withdraws an amount according to the acquired selling price from the wallet of the user A11. For example, when the selling price of the game program data is set to 10,000 yen, the transaction processing unit 233 withdraws 10,000 yen from the wallet of the user A11 and deposits the withdrawn 10,000 yen into the wallet of the marketplace MP.

[0044] The transaction processing unit 233 also executes a deposit / withdrawal process for buying and selling game program data to which save data is attached. For example, as shown in FIG. 6, assume that a user A13 purchases game program data and save data owned by a user A11 on the marketplace MP together with an NFT 101. In this case, the transaction processing unit 233 acquires information on the secondary selling price of the game program data from the NFT 101 and withdraws an amount according to the acquired secondary selling price from the wallet of the user A11. For example, if the secondary selling price is set to 12,000 yen, the transaction processing unit 233 withdraws 12,000 yen from the wallet of the user A13. Then, as shown in FIG. 9(A), the transaction processing unit 233 deposits 1,200 yen, which is an amount obtained by multiplying 12,000 yen by a predetermined rate, for example, 10%, into the wallet of the marketplace MP as a fee, and deposits the remaining amount, 10,800 yen, into the wallet of the user A11.

[0045] Furthermore, as shown in Fig. 7, when user A21 purchases MOD data created by user A12 on the marketplace MP, the transaction processing unit 233 acquires information on the selling price of the MOD data from the MOD database 212 and withdraws an amount corresponding to the acquired selling price from the wallet of user A21. For example, when the selling price of the MOD data is set to 1,000 yen, the transaction processing unit 233 withdraws 1,000 yen from the wallet of user A21. Then, as shown in Fig. 9(B), the transaction processing unit 233 deposits 100 yen, which is the amount obtained by multiplying 1,000 yen by a predetermined rate, for example, 10%, into the wallet of the marketplace MP as a fee, and deposits the remaining amount, 900 yen, into the wallet of user A12.

[0046] By executing the above-mentioned deposit and withdrawal processing, the management company etc. that manages the Marketplace MP can collect an amount according to the primary sales price when the game program data is primarily distributed on the Marketplace MP. In addition, the management company etc. can also collect a commission according to the secondary sales price when the game program data with the save data is traded between users on the Marketplace MP, and a commission according to the sales price of the MOD data when the MOD data is traded between users.

[0047] Users can also transfer the game program data and MOD data that come with the save data to other users free of charge. In this case, the above-mentioned deposit and withdrawal process is not carried out, and the ownership of the NFT is simply transferred between users. (Configuration of distributed ledger system) The distributed ledger system 30 shown in FIG. 1 is a system that manages NFTs for game program data and MOD data based on so-called blockchain technology. The distributed ledger system 30 registers NFTs in the distributed ledger 310 based on a request from the server device 20, specifically, based on a request to issue NFTs for the game program data and MOD data. In addition, when a transaction such as a transfer is made for each of the game program data and MOD data, the distributed ledger system 30 registers the transaction data in the distributed ledger 310. Specifically, the distributed ledger 310 stores a plurality of blocks including a hash value and a list of transactions. A transaction is information about a transaction of game program data and MOD data associated with an NFT. The hash value is calculated based on a hash function from a part of the previous transaction. In the distributed ledger 310, transaction history is stored with each block linked like a chain by a hash value.

[0048] (Terminal Device Configuration) As shown in FIG. 10, the terminal device 40 includes, as its functional configuration, a display unit 41, a storage unit 42, an input unit 43, a communication unit 44, and a control unit 45.

[0049] The display unit 41 has a function of displaying various screens. For example, the display unit 41 displays an operation screen of the marketplace MP, a game play screen, etc. The display unit 41 can be realized by, for example, the output device 15 shown in FIG. The storage unit 42 has a function of storing various information of the terminal device 40. Various programs and the like are stored in the storage unit 42. In addition, the storage unit 42 stores user account information and the like used when using the marketplace MP. Furthermore, when a user purchases game program data on the marketplace MP and then installs the game program data on the terminal device 40, the storage unit 42 stores the game program data, save data, and the like. Furthermore, when a user operates the terminal device 40 to create MOD data or purchases user MOD data on the marketplace MP, the MOD data is stored in the storage unit 42. The storage unit 42 can be realized, for example, by the storage device 12 shown in FIG. 2.

[0050] The input unit 43 has a function of accepting operations from a user. The input unit 43 can be realized by, for example, the input device 14 shown in FIG. The communication unit 44 has a function of performing various communications with the server device 20 via the network line N. The communication unit 44 enables the user to perform various operations in the marketplace MP provided by the server device 20 by performing various communications with the server device 20. For example, when the user operates the input unit 43 to use the marketplace MP, the account information stored in the storage unit 42 is transmitted to the server device 20. As a result, authentication based on the account information is performed by the server device 20. When the authentication is established, the user is able to use the marketplace MP.

[0051] In addition, the communication unit 44 communicates with the server device 20 based on the user's operation of the input unit 43, thereby obtaining game program data, save data, MOD data, etc. from the server device 20 via the network line N, and stores the obtained data in the memory unit 42.

[0052] Furthermore, the communication unit 44 communicates with the server device 20 based on a user's operation of the input unit 43, thereby transmitting save data, MOD data, and the like stored in the storage unit 42 to the server device 20. This makes it possible to register save data in the game database 211 of the server device 20 and to register MOD data in the MOD database 212 of the server device 20.

[0053] The control unit 45 has a function of comprehensively controlling the terminal device 40. The control unit 45 can be realized, for example, by the processor 11 shown in Fig. 2 executing a program stored in the storage unit 42. The control unit 45 includes, as its functional configuration, a game execution unit 450 and a display control unit 451.

[0054] (Game Execution Department) The game execution unit 450 executes the game program data stored in the storage unit 42 based on the operation of the input unit 43 by the user. Specifically, when an operation to execute a game is performed by a user, the game execution unit 450 authenticates the user by communicating with the server device 20 through the communication unit 44. For example, the game execution unit 450 transmits the account information stored in the storage unit 42 to the server device 20. At this time, the server device 20 compares the user's account information transmitted from the terminal device 40 with the owner of the NFT corresponding to the program data of the game, and determines whether the user of the terminal device 40 is the owner of the NFT corresponding to the program data of the game. When the server device 20 determines that the user of the terminal device 40 is the owner of the NFT corresponding to the program data of the game, it notifies the terminal device 40 that authentication has been established. On the other hand, when the server device 20 determines that the user of the terminal device 40 is not the owner of the NFT corresponding to the program data of the game, it notifies the terminal device 40 that authentication has not been established. When the game execution unit 450 is notified by the server device 20 that authentication has been established, it executes the program data of the game. This makes it possible to play the game on the terminal device 40. On the other hand, if the game execution unit 450 is notified by the server device 20 that the authentication has not been established, the game execution unit 450 does not execute the program data of the game. In this case, the game cannot be played on the terminal device 40.

[0055] Furthermore, the game execution unit 450 reads the save data stored in the storage unit 42 based on the user's operation of the input unit 43, and executes the game program data in which the save data is reflected. In this case as well, the server device 20 authenticates the user based on the NFT of the game program data, and the game execution unit 450 executes the game program data if the authentication is successful, and does not execute the game program data if the authentication is not successful.

[0056] Furthermore, the game execution unit 450 reads the MOD data stored in the storage unit 42 based on the user's operation of the input unit 43, and executes the game program data in which the MOD data is reflected. At this time, in order to execute the game program data in which the MOD data is reflected, the user needs to own not only the NFT of the MOD data but also the NFT of the game program data. In order to confirm this, the server device 20 authenticates not only the NFT corresponding to the MOD data, but also the NFT corresponding to the game program data. Specifically, the server device 20 compares the user's account information transmitted from the terminal device 40 with the owner of the NFT corresponding to the MOD data, and determines whether the user of the terminal device 40 is the owner of the NFT corresponding to the MOD data. Similarly, the server device 20 also determines whether the user of the terminal device 40 is the owner of the NFT corresponding to the game program data. The server device 20 transmits the authentication results of the NFTs of the MOD data and the game program data to the terminal device 40. When the authentication of the NFTs of the MOD data and the game program data is established, the game execution unit 450 executes the game program data in which the MOD data is reflected. This allows the game in which the MOD data is reflected to be played on the terminal device 40. On the other hand, if authentication of the NFT of at least one of the MOD data and the game program data is not established, the game execution unit 450 does not execute the game program data in which the MOD data is reflected. In this case, the game in which the MOD data is reflected cannot be played on the terminal device 40.

[0057] (Display control unit) The display control unit 451 controls the display output of the display unit 41. For example, the display control unit 451 executes control to display on the display unit 41 an operation screen of the marketplace MP, a game play screen, and the like.

[0058] (Example of operation of information processing system) Next, an example of the operation of the information processing system 10 of this embodiment will be described with reference to Fig. 11 to Fig. 13. First, an example of the operation of the information processing system 10 when a user A11 purchases game program data will be described. In the following, the terminal device 40 owned by the user A11 will be referred to as "terminal device 40a".

[0059] As shown in FIG. 11, if the user A11 performs an operation to purchase game program data on the marketplace MP on the terminal device 40a (step S10), the terminal device 40a transmits a notice of the operation to the server device 20. When the transaction processing unit 233 of the server device 20 receives the notice of the purchase of the game program data (step S20), it executes the transaction processing (step S21). In addition, the token management unit 232 of the server device 20 requests the distributed ledger system 30 to issue an NFT corresponding to the purchased game program data (step S22). When the distributed ledger system 30 receives a request from the server device 20 (step S30), it registers the NFT corresponding to the game program data in the distributed ledger 310 (step S31). This gives the user A11 ownership of the game program data.

[0060] Thereafter, when the user A11 performs an operation to install the game on the terminal device 40a, the terminal device 40a requests the server device 20 to transmit the game program data based on the URL information included in the NFT (step S11). When this request is received by the communication unit 22 of the server device 20 (step S23), the data transmission unit 231 of the server device 20 transmits the game program data stored in the game database 211 to the terminal device 40a (step S24). When the terminal device 40a receives the game program data transmitted from the server device 20 (step S12), the game program data is installed on the terminal device 40a, and the game can be played on the terminal device 40a (step S13).

[0061] Next, an example of the operation of the information processing system 10 when a user A13 purchases program data and save data of a game owned by a user A11 will be described. In the following, the terminal device 40 owned by the user A13 will be referred to as the "terminal device 40b." 12, if a user A11 plays a game on terminal device 40a, creates save data, and then performs an operation to sell the game program data to which the save data is attached on the marketplace MP (step S14), a notice that the operation has been performed is transmitted from terminal device 40a to server device 20. When the transaction processing unit 233 of server device 20 receives a request to sell the game program data and save data (step S25), it sells the game program data to which the save data is attached on the marketplace MP (step S26).

[0062] After that, if a user A13, who is different from the user A11, performs an operation to purchase game program data and save data on the marketplace MP on the terminal device 40b (step S40), the terminal device 40b transmits a notice of the operation to the server device 20. When the transaction processing unit 233 of the server device 20 receives the notice of the purchase of the game program data and save data (step S27), it executes the transaction processing (step S28). In addition, the token management unit 232 of the server device 20 requests the distributed ledger system 30 to transfer the NFT corresponding to the purchased game program data from the user A11 to the user A13 (step S29). When the distributed ledger system 30 receives the request from the server device 20 (step S32), it changes the owner of the NFT corresponding to the game program data from the user A11 to the user A13 (step S33). As a result, the ownership of the game program data and save data is granted to the user A13.

[0063] Thereafter, when the user A13 performs an operation to install the game on the terminal device 40b, the terminal device 40b requests the server device 20 to transmit the program data and save data of the game based on the URL information included in the NFT (step S41). When this request is received by the communication unit 22 of the server device 20 (step S50), the data transmission unit 231 of the server device 20 transmits the program data and save data of the game stored in the game database 211 to the terminal device 40b (step S51). When the terminal device 40b receives the program data and save data of the game transmitted from the server device 20 (step S42), the program data and save data of the game are installed on the terminal device 40b, and the game corresponding to the save data can be played on the terminal device 40b (step S43).

[0064] Next, an example of the operation of the information processing system 10 when another user A21 purchases MOD data created by a user A12 will be described. In the following, the terminal device 40 owned by the user A12 will be referred to as "terminal device 40c," and the terminal device 40 owned by the user A21 will be referred to as "terminal device 40d."

[0065] As shown in FIG. 13, suppose that the user A12 creates MOD data on the terminal device 40c and then uploads the MOD data to the server device 20 (step S60). After receiving the MOD data (step S52), the communication unit 22 of the server device 20 stores the MOD data in the MOD database 212 (step S53). At this time, the token management unit 232 of the server device 20 requests the distributed ledger system 30 to issue an NFT corresponding to the MOD data (step S54). Upon receiving the request from the server device 20 (step S34), the distributed ledger system 30 registers the NFT corresponding to the MOD data in the distributed ledger 310 (step S35). This puts the MOD data in a state in which the NFT is assigned. Thereafter, suppose that the user A12 performs an operation to sell the MOD data on the marketplace MP on the terminal device 40c (step S61). A notice that the operation has been performed is transmitted from the terminal device 40c to the server device 20. As a result, the transaction processing unit 233 of the server device 20 sells the MOD data on the marketplace MP (step S55).

[0066] In addition, user A12 can sell multiple MOD data on the marketplace MP. The multiple MOD data may be the same MOD data or may be different MOD data. Each of the multiple MOD data sold on the marketplace MP is associated with a different NFT, more specifically, an NFT having a different token ID.

[0067] Thereafter, if the user A21 performs an operation to purchase MOD data on the marketplace MP on the terminal device 40d (step S70), the terminal device 40d transmits a notice of the operation to the server device 20. When the transaction processing unit 233 of the server device 20 receives the notice of the purchase of the MOD data (step S56), it executes the transaction processing (step S57). In addition, the token management unit 232 of the server device 20 requests the distributed ledger system 30 to transfer the NFT corresponding to the purchased MOD data from the user A12 to the user A21 (step S58). When the distributed ledger system 30 receives the request from the server device 20 (step S36), it changes the owner of the MOD data from the user A12 to the user A21 (step S37). This gives the ownership of the MOD data to the user A21.

[0068] Thereafter, when user A21 performs an operation to install the MOD data on terminal device 40d, terminal device 40d requests server device 20 to transmit the MOD data based on the URL information included in the NFT (step S71). When this request is received by communication unit 22 of server device 20 (step S59), data transmission unit 231 of server device 20 transmits the MOD data stored in MOD database 212 to terminal device 40d (step S80). When terminal device 40d receives the MOD data transmitted from server device 20 (step S72), the MOD data is installed on terminal device 40d, and it becomes possible to play the game corresponding to the MOD data on terminal device 40d (step S73).

[0069] (Actions and Effects of the Information Processing System of the Present Embodiment) As described above, the server device 20 of this embodiment includes the storage unit 21 and the token management unit 232. The storage unit 21 stores game program data and MOD data that is derivatively created from the game. The token management unit 232 issues NFTs corresponding to the game program data and NFTs corresponding to the MOD data in the distributed ledger 310. The NFTs corresponding to the program data include URL information that allows access to the game program data. The NFTs corresponding to the MOD data include URL information that allows access to the MOD data.

[0070] According to this configuration, since the NFT is associated with the game program data, the uniqueness of the game program data can be ensured based on this token. Similarly, since the NFT is associated with the MOD data, the uniqueness of the MOD data can be ensured based on this token. Therefore, according to the configuration of this embodiment, since the uniqueness of each of the game program data and the MOD data can be ensured, for example, by the developer becoming the administrator of the server device 20, the developer can sell and distribute the game program data and the MOD data by himself / herself without going through a specific sales company. Therefore, the game program data and the MOD data can be more appropriately disseminated.

[0071] The NFT corresponding to the game's program data contains URL information that allows access to the game's save data. This configuration also ensures the uniqueness of the save data of the game, making it possible to disseminate the save data more appropriately. Furthermore, in cases where a celebrity such as a professional gamer plays a game and creates save data, if the save data can be bought and sold while ensuring the uniqueness of the save data, it will be possible to sell the game program data to which the save data is attached in an appropriate manner, for example, to fans of the celebrity.

[0072] The NFT corresponding to the game program data further includes information on the primary and secondary sales prices of the game program data, while the NFT corresponding to the MOD data includes information on the sales price of the MOD data. With this configuration, the primary and secondary sales prices of the game program data, as well as the sales price of the MOD data, can be managed in NFT, making it possible to manage sales prices more appropriately.

[0073] <Second embodiment> Next, a second embodiment of the information processing system 10 will be described. The following mainly describes the differences from the information processing system 10 of the first embodiment. In the information processing system 10 of this embodiment, when MOD data is registered in the server device 20, the MOD data is screened, and only MOD data that has been approved through the screening is sold on the Marketplace MP.

[0074] (Server device configuration) 3, the control unit 23 of the server device 20 of this embodiment further includes, as its functional configuration, an examination unit 234. In addition, the token management unit 232 and the transaction processing unit 233 of the control unit 23 differ from the token management unit 232 and the transaction processing unit 233 of the first embodiment in the following points.

[0075] (Examination Department) The examination unit 234 examines the contents of the MOD data when a request to register MOD data is received from the terminal device 40. The examination unit 234 performs, for example, security examination processing and compliance examination processing on the MOD data. The security examination processing is processing of analyzing the contents of the MOD data to examine whether or not it contains harmful data such as malware. The compliance examination is processing of analyzing the contents of the MOD data to examine whether or not it contains data that violates public order and morals. Note that the examination of the MOD data may be partially performed manually.

[0076] If the MOD data passes the screening process, the screening unit 234 approves the MOD data. On the other hand, if the MOD data does not pass the screening process, the screening unit 234 disapproves the MOD data. (Token Management Department) When the token manager 232 requests the distributed ledger system 30 to issue an NFT for the MOD data, the token manager 232 registers information on the review result of the review unit 234 in the NFT. Specifically, the token manager 232 requests the distributed ledger system 30 to issue an NFT 203 as shown in FIG. 14 as an NFT corresponding to the MOD data.

[0077] 14, the metadata of the NFT 203 includes approval / non-approval information for the MOD data, and approval content information for the MOD data. The approval / non-approval information item registers information on whether the MOD data has been approved by the review by the review unit 234. The approval content information registers the specific content that has actually been approved by the review by the review unit 234.

[0078] (Transaction Processing Unit) When displaying MOD data on the marketplace MP, the transaction processing unit 233 reads the approval / non-approval information of the MOD data included in the NFT corresponding to the MOD data. If information indicating that the MOD data is approved is registered in the approval / non-approval information field, the transaction processing unit 233 displays the MOD data on the marketplace MP. This allows other users to purchase the MOD data via the marketplace MP, so that the MOD data is distributed in the market via the marketplace MP. On the other hand, if information indicating that the MOD data is not approved is registered in the approval / non-approval information field, the transaction processing unit 233 does not display the MOD data on the marketplace MP. In this case, other users cannot purchase the MOD data, so that the MOD data is not distributed in the market.

[0079] (Terminal Device Configuration) The terminal device 40 of this embodiment differs from the terminal device 40 of the first embodiment in the following points. (Game Execution Department) When executing the program data of the game in which the MOD data is reflected, the game execution unit 450 acquires the approval / non-approval information included in the NFT corresponding to the MOD data based on the user's operation of the input unit 43. If the information indicating approval is registered in the approval / non-approval information field, the game execution unit 450 executes the program data of the game in which the MOD data is reflected. If the information indicating non-approval is registered in the approval / non-approval information field, the game execution unit 450 does not execute the program data of the game in which the MOD data is reflected.

[0080] (Actions and Effects of the Information Processing System of the Present Embodiment) As described above, the information processing system 10 of this embodiment further includes the examination unit 234 that executes examination processing on the MOD data. According to this configuration, the appropriateness of the MOD data can be ensured, and it is therefore possible to prevent, for example, MOD data that violates compliance or public order and morals from being distributed in the market.

[0081] The transaction processing unit 233 of this embodiment executes processing related to buying and selling of MOD data. The transaction processing unit 233 executes buying and selling of MOD data when the MOD data has been approved by the screening process of the screening unit 234. On the other hand, when the MOD data has not been approved by the screening process of the screening unit 234, the transaction processing unit 233 does not execute buying and selling of MOD data. According to this configuration, only MOD data that has been approved by the review unit 234 is traded, making it possible to trade more appropriate MOD data.

[0082] The NFT of the MOD data includes approval / disapproval information indicating whether the MOD data is approved. When executing the game program data, the game execution unit 450 reads the approval / disapproval information included in the NFT and determines whether the MOD data is approved based on the approval / disapproval information. If the MOD data is approved, the game execution unit 450 executes the game program data, and if the MOD data is not approved, the game execution unit 450 does not execute the game program data. This configuration can prevent a game that reflects unauthorized MOD data from being executed.

[0083] <Other embodiments> The above embodiment can also be implemented in the following forms. The NFTs of the game program data and the NFTs of the MOD data may be viewable only by certain parties, such as predetermined specific businesses or individuals. MOD data associated with an NFT may be further modified to develop and sell second-generation MOD data. There may or may not be a restriction on the number of generations of MOD data. However, while any user may be allowed to modify MOD data, there may be a restriction that the sale of modified MOD data is only permitted with the permission of the creator of the MOD data before modification. Information on whether or not to permit the sale of this MOD data may be further included in the NFT of the MOD data.

[0084] It may be possible to allow only users who own the NFT of the game program data to develop MOD data. For example, when a request to register MOD data is made from the terminal device 40, the data registration unit 230 determines whether or not the user is the owner of the NFT of the game program data, based on account information of the user of the terminal device 40, etc. If the user is the owner of the NFT of the game program data, the data registration unit 230 registers the MOD data in the MOD database 212, but if the user is not the owner of the game program data, the data registration unit 230 does not register the MOD data in the MOD database 212.

[0085] Development of MOD data may be allowed only on Marketplace MP, for example. In this case, only owners of NFTs corresponding to the game's program data may be allowed to develop MOD data. In the Marketplace MP, it may be possible to buy and sell only the save data by itself. In this case, for example, if an NFT corresponding to the save data is issued separately from an NFT corresponding to the game's program data, it is possible to manage the game's program data and the save data separately.

[0086] All of the components respectively provided in the server device 20 and the terminal device 40 may be provided in the server device 20 alone, the terminal device 40 alone, a communication terminal separate from the server device 20 and the terminal device 40, or two of these devices that can be combined. The present disclosure is not limited to the above specific examples. Any of the above specific examples to which a person skilled in the art has made appropriate design changes are also included within the scope of the present disclosure as long as they have the features of the present disclosure. The elements of each of the above specific examples, as well as their arrangements, conditions, shapes, etc., are not limited to those exemplified and can be changed as appropriate. The elements of each of the above specific examples can be appropriately combined as long as no technical contradiction occurs. [Explanation of symbols]

[0087] 10: information processing system, 20: server device (information processing device), 21: memory unit, 232: token management unit, 233: transaction processing unit, 234: examination unit, 310: distributed ledger, 450: game execution unit.

Claims

1. A storage unit for storing game program data and derivative data derived from the game; a token management unit that issues a non-fungible first token corresponding to the program data of the game and a non-fungible second token corresponding to the derivative creation data on a distributed ledger; the first token includes first access information that enables access to program data of the game; the second token includes second access information that enables access to the derivative work data; The derivative work data is modification program data that can modify the game. Information processing device.

2. The first token further includes third access information that enables access to the save data of the game. The information processing device according to claim 1 .

3. The first token further includes information on the primary sale price of the game program data and information on the secondary sale price. The information processing device according to claim 1 .

4. The second token includes information on the selling price of the derivative data. The information processing device according to claim 1 .

5. The apparatus further includes an examination unit that executes an examination process on the modification program data. The information processing device according to claim 1 .

6. A transaction processing unit that executes processing related to buying and selling of the modification program data, The transaction processing unit includes: If the modification program data is approved by the review process of the review department, the purchase and sale of the modification program data is carried out; If the modification program data has not been approved by the review process of the review department, the sale and purchase of the modification program data will not be carried out. The information processing device according to claim 5 .

7. The second token further includes approval / non-approval information indicating whether the modification program data is approved or not. The information processing device according to claim 5 .

8. A game execution unit that executes program data of the game is further provided, The game execution unit is reading the approval / disapproval information included in the second token when executing the game program data; determining whether the modification program data is approved based on the approval / non-approval information; If the modification program data is approved, execute the program data of the game; If the modification program data is not approved, the game program data will not be executed. The information processing device according to claim 7.

9. A storage unit for storing game program data and derivative data derived from the game; a token management unit that issues a non-fungible first token corresponding to the program data of the game and a non-fungible second token corresponding to the derivative creation data on a distributed ledger; the first token includes first access information that enables access to program data of the game; the second token includes second access information that enables access to the derivative work data; The derivative work data is modification program data that can modify the game. Information processing system.

10. On the computer, storing game program data and derivative data derived from said game in a storage unit; issuing a non-fungible first token corresponding to the program data of the game and a non-fungible second token corresponding to the derivative creation data on a distributed ledger; the first token includes first access information that enables access to program data of the game; the second token includes second access information that enables access to the derivative work data; The derivative work data is modification program data that can modify the game. Information processing program.

Images