JP7063512B1 - Programs, information processing equipment, methods, and systems - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a program, an information processing apparatus, a method and a system for ensuring the rarity of digital data associated with a token. SOLUTION: In an information processing system in which a user terminal, a server and a distributed ledger system are connected via a network, the user terminal is a means for creating a first visual content of a computer including a storage device. 1 means for transmitting visual content to an external device, first means for preventing data expressing the same visual information as the first visual content from remaining in the storage device after transmission of the first visual content, and first. A means of requesting an external device (eg, a server or a distributed ledger system) to issue a first token proving to be the owner of the visual content or to list the first token on a platform where the token can be bought and sold. , Is executed. [Selection diagram] FIG. 12

Description

The present disclosure relates to programs, information processing devices, methods, and systems.

A technique (NFT (Non-Fungible Token)) that enables the digital data to be treated like a non-fungible tangible object by recording the token associated with the digital data on the blockchain is known. ..

Although Patent Document 1 does not disclose NFT, there is a technique for displaying a written image with virtual graffiti added to a visited place image as a proof of visit by storing virtual graffiti and geolocation information on the blockchain. It has been disclosed.

Japanese Unexamined Patent Publication No. 2020-071590

Since digital data can be easily duplicated, simply recording the token associated with the digital data on the blockchain cannot sufficiently guarantee the rarity of the digital data. That is, the asset value of digital data may be underestimated due to its easily replicable nature.

The purpose of this disclosure is to ensure the rarity of digital data associated with tokens.

The program of one aspect of the present disclosure is a means for creating a first visual content, a means for transmitting the first visual content to an external device, and after transmitting the first visual content, the computer provided with the storage device. 1 Means for preventing data expressing the same visual information as the visual content from remaining in the storage device, issuing a first token proving that the owner of the first visual content is available, or buying and selling tokens. It functions as a means for requesting an external device to sell the first token on the platform.

It is a block diagram which shows the structure of the information processing system of this embodiment. It is a block diagram which shows the structure of the user terminal of this embodiment. It is a block diagram which shows the structure of the server of this embodiment. It is a figure which shows the structure of the distributed ledger system of this embodiment. It is explanatory drawing of one aspect of this embodiment. It is explanatory drawing of one aspect of this embodiment. It is explanatory drawing of one aspect of this embodiment. It is explanatory drawing of one aspect of this embodiment. It is a figure which shows the data structure of the work database of this embodiment. It is a figure which shows the data structure of the token of this embodiment. It is a flowchart of the image creation process of this embodiment. It is a flowchart of the token issuance process of this embodiment. It is a figure which shows the screen example displayed in the information processing of this embodiment.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiments, the same components are designated by the same reference numerals in principle, and the repeated description thereof will be omitted.

In the following description, when a common description is given for a plurality of elements of the same type, a common reference numeral such as "99" may be used. On the other hand, when describing these elements individually, a code with a subscript added to a common code such as "99-1" or "99-2" may be used.

(1) Configuration of information processing system The configuration of the information processing system will be described. FIG. 1 is a block diagram showing a configuration of an information processing system of the present embodiment.

As shown in FIG. 1, the information processing system 1 includes a user terminal 10, a server 30, and a distributed ledger system 50.
The user terminal 10, the server 30, and the distributed ledger system 50 are connected via a network (for example, the Internet or an intranet) NW.

The user terminal 10 is an example of an information processing device that transmits a request to the server 30. The user terminal 10 is, for example, a smartphone, a tablet terminal, or a personal computer.

The server 30 is an example of an information processing device that provides the user terminal 10 with a response corresponding to a request transmitted from the user terminal 10. The server 30 is, for example, a web server.

The distributed ledger system 50 manages the distributed ledger in response to a request from the user terminal 10 or the server 30.

(1-1) Configuration of User Terminal The configuration of the user terminal will be described. FIG. 2 is a block diagram showing the configuration of the user terminal of the present embodiment.

As shown in FIG. 2, the user terminal 10 includes a storage device 11, a processor 12, an input / output interface 13, and a communication interface 14. The user terminal 10 is connected to the display 21 and the camera 22.

The storage device 11 is configured to store programs and data. The storage device 11 is, for example, a combination of a ROM (Read Only Memory), a RAM (Random Access Memory), and a storage (for example, a flash memory or a hard disk).

The program includes, for example, the following program.
-OS (Operating System) program-Program of an application that executes information processing (for example, a web browser or a target application described later)

The data includes, for example, the following data.
-Database referenced in information processing-Data obtained by executing information processing (that is, the execution result of information processing)

The processor 12 is a computer that realizes the functions of the user terminal 10 by activating the program stored in the storage device 11. The processor 12 is, for example, at least one of the following.
・ CPU (Central Processing Unit)
・ GPU (Graphic Processing Unit)
・ ASIC (Application Specific Integrated Circuit)
・ FPGA (Field Programmable Array)

The input / output interface 13 acquires information (for example, a user's instruction) from an input device connected to the user terminal 10 and outputs information (for example, an image signal) to an output device connected to the user terminal 10. It is configured as follows.
The input device is, for example, a camera 22, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display 21, a speaker, or a combination thereof.

The communication interface 14 is configured to control communication between the user terminal 10 and an external device (eg, the server 30 or the distributed ledger system 50).

The display 21 is configured to display an image (still image or moving image). The display 21 is, for example, a liquid crystal display or an organic EL display.

The camera 22 is configured to capture a subject and generate an image (still image or moving image).

(1-2) Server configuration The server configuration will be described. FIG. 3 is a block diagram showing a configuration of the server of the present embodiment.

As shown in FIG. 3, the server 30 includes a storage device 31, a processor 32, an input / output interface 33, and a communication interface 34.

The storage device 31 is configured to store programs and data. The storage device 31 is, for example, a combination of a ROM, a RAM, and a storage (for example, a flash memory or a hard disk).

The program includes, for example, the following program.
・ OS program ・ Application program that executes information processing

The data includes, for example, the following data.
・ Database referenced in information processing ・ Execution result of information processing

The processor 32 is a computer that realizes the function of the server 30 by activating the program stored in the storage device 31. The processor 32 is, for example, at least one of the following.
・ CPU
・ GPU
・ ASIC
・ FPGA

The input / output interface 33 is configured to acquire a user's instruction from an input device connected to the server 30 and output information to an output device connected to the server 30.
The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display.

The communication interface 34 is configured to control communication between the server 30 and an external device (eg, a user terminal 10 or a distributed ledger system 50).

(1-3) Configuration of Distributed Ledger System The configuration of the distributed ledger system will be described. FIG. 4 is a diagram showing the configuration of the distributed ledger system of the present embodiment.

As shown in FIG. 4, the distributed ledger system 50 includes a plurality of node computers 55-1 to 55-4.

The node computers 55 are connected to each other via a network (which may include the network NW of FIG. 1). In this embodiment, the network may include a public network, a private network, a leased line, a VPN (Virtual Private Network), or a combination thereof. The node computer 55 is connected to the network, for example, by wire or wirelessly. The node computers 55 communicate with each other in a peer-to-peer manner.

The node computer 55 manages a distributed ledger using, for example, blockchain technology.
Specifically, any node computer 55 acquires data regarding a token transaction to be recorded. The node computer 55 creates a block containing the acquired data and adds it to the blockchain. The node computer 55 transmits the information of the added block to another node computer 55. The other node computer 55 verifies the correctness of the received block, and if the verification is successful, the other node computer 55 adds the block to the blockchain. The node computer 55 determines the blockchain according to the number of blocks to be concatenated (approved number), for example. As a result, the same distributed ledger is stored across the plurality of node computers 55 constituting the distributed ledger system 50. The stored data is appropriately encrypted.

The configuration of the distributed ledger system 50 is not limited to that shown in FIG. For example, the distributed ledger system 50 may include five or more node computers 55, or may include two or three node computers 55. Further, the number of node computers 55 constituting the distributed ledger system 50 may fluctuate with time.

Since the hardware configuration of the node computer 55 may be the same as or similar to that of the user terminal 10 or the server 30, detailed description thereof will be omitted. As an example, the node computer 55 includes a processor, a storage device, an input / output interface, a communication interface, an input device, an output device, or a combination thereof.

(2) One aspect of the embodiment One aspect of the present embodiment will be described. FIG. 5 is an explanatory diagram of one aspect of the present embodiment. FIG. 6 is an explanatory diagram of one aspect of the present embodiment. FIG. 7 is an explanatory diagram of one aspect of the present embodiment. FIG. 8 is an explanatory diagram of one aspect of the present embodiment.

As shown in FIG. 5, the user US1 is a predetermined application (for example, an application for creating or managing a digital work (image), hereinafter referred to as a “target application”) on the user terminal 10-1. In the executed state, the user terminal 10-1 is operated, and the subject OBJ1 is photographed by the camera 22. As a result, the user terminal 10-1 generates an image IM10 (an example of "visual content") of the subject OBJ1 and temporarily stores the image IM10 in the storage device 11. Here, the image IM10 is not limited to a still image, but may be a moving image. The user terminal 10-1 uploads the generated image IM 10 to the server 30. The server 30 stores the uploaded image IM 10 in the storage device 31. On the other hand, the user terminal 10-1 deletes the image IM 10 from the storage device 11 after uploading the image IM 10. That is, the image IM 10 does not substantially remain in the hands of the user US1 and is transferred from the user terminal 10-1 to the server 30 as if it were a tangible object. As a result, the user US1 who is the creator of the image IM10 cannot freely duplicate the image IM10, so that the rarity of the image IM10 is guaranteed.

As shown in FIG. 6, the user US1 operates the user terminal 10-1 while the target application is being executed on the user terminal 10-1, and sends a viewing request for the image IM 10 to the server 30. Let me. The server 30 transmits the processed image IM 11 corresponding to the image IM 10 to the user terminal 10-1 in response to the viewing request. The user terminal 10-1 displays the processed image IM 11 on the display 21. The processed image IM 11 is an image obtained by subjecting the image IM 10 to irreversible processing such as watermark processing. In short, the processed image IM 11 has visual information similar to that of the image IM 10, but also has a difference in visual information to the extent that a human can recognize the difference. Therefore, the user US1 can determine whether or not to tokenize the image IM10 (that is, issue a token associated with the image IM10) by viewing the processed image IM11. On the other hand, even if the screenshot function of the user terminal 10-1 is abused, for example, the complete reproduction data of the image IM10 cannot be obtained.

As shown in FIG. 7, the user US1 operates the user terminal 10-1 while the target application is being executed on the user terminal 10-1, and requests to issue a token associated with the image IM 10. Is sent to the server 30. The server 30 requests the distributed ledger system 50 to issue a token associated with the image IM 10 in response to the issuance request. Here, the server 30 may collect a fee for the user US1 and issue the token after the payment is completed. As a result, the cost associated with the issuance of the token can be reliably recovered. When the distributed ledger system 50 completes the issuance of the token associated with the image IM 10, the user US1 can acquire the token using the user terminal 10-1. On the other hand, the server 30 deletes the image IM 10 from the storage device 31 after issuing the token. This makes it possible to prevent the value of the image IM 10 from being diluted due to the image IM 10 coexisting on the server 30 separately from the token. The image IM10 is typically stored on an external server (eg, a server provided by an NFT trading platform) or embedded in a token. In any case, in order to view the image IM10, the information described in the token associated with the image IM10 is required. Thereby, the token associated with the image IM10 proves that the owner of the token is the owner of the image IM10.

The user US1 who owns the tokenized image IM10 can distribute the image IM10 as shown in FIG. Specifically, the user US1 operates the user terminal 10-1 to sell the image IM10 desired by the user to another user US2. The user terminal 10-1 transfers the token associated with the image IM 10 to the user US2 who is the buyer of the image IM 10 in response to the sale of the image IM 10. Specifically, the user terminal 10-1 requests the distributed ledger system 50 to transfer the token possessed by the user US1 to the user US2. When the distributed ledger system 50 completes the transfer of the token, the user US2 acquires the token using the user terminal 10-2. After that, the user US2 can sell the image IM10 to another user (that is, secondary distribution).

Further, when the conditions for collecting royalties associated with the distribution of tokens are described in the token (for example, as transaction condition information described later), the distributed ledger system 50 transfers the tokens and collects royalties and collects them. The royalty is distributed to the right holder RH1 (for example, the person who has the publicity right of the subject OBJ1, the user US1 who is the creator of the image IM10, or a combination thereof). Royalty may be collected from the consideration paid by the buyer of the image IM10 for the image IM10, or may be collected from the seller or the buyer of the image IM10 independently of such consideration.

As described above, according to the information processing system 1, it can be ensured that the user US1 who is the creator of the image IM10 is restricted from replicating the image IM10 for the tokenized image IM10. That is, it is possible to ensure the rarity of the tokenized image IM10 and prevent the value of the image IM10 from being underestimated.

(3) Data structure The data structure will be described.

(3-1) Work database The work database of this embodiment will be described. FIG. 9 is a diagram showing the data structure of the work database of the present embodiment.

The work database is built in the storage device 31. Basic image information is stored in the work database. The basic image information is meta information of a work (that is, an image) created by a user of the target application.
As shown in FIG. 9, the work database includes a "user ID" field, an "image ID" field, a "save destination" field, a "shooting date" field, and a "shooting location" field. Each field is associated with each other. The various fields in the work database are just examples. For example, the "photographing location" field may not be provided.

The user ID is stored in the "user ID" field. The user ID is information that identifies the user of the target application, which corresponds to the creator of the image corresponding to the basic image information.

An image ID is stored in the "image ID" field. The image ID is information for identifying an image corresponding to the basic image information.

The save destination information is stored in the save destination field. The save destination information is information about the save destination of the image corresponding to the basic image information. The storage destination information may be, for example, address information in the storage device 31 or a URL (Uniform Resource Locator) for referencing an image.

The shooting date information is stored in the "shooting date" field. The shooting date information is information regarding the shooting date of the image corresponding to the basic image information. The shooting date information is added to the image by the user terminal 10 based on the time information, for example.

The shooting location information is stored in the "shooting location" field. The shooting location information is information regarding the shooting location of the image corresponding to the basic image information. The shooting location information is added to the image by the user terminal 10 based on the position information (as an example, GPS (Global Positioning System) information).

(3-2) Token The data structure of the token will be described. FIG. 10 is a diagram showing a data structure of the token of the present embodiment.

As shown in FIG. 10, the token includes a token ID, owner address information, metadata, and transaction condition information.

The token ID is information that identifies the token. The token ID is described by the distributed ledger system 50 when the token is issued.

The owner address information is information about the address of the owner of the token. As an example, the owner address information is information indicating the wallet of the owner of the token. The owner address information is updated by the distributed ledger system 50 at the time of token issuance and transfer.

The metadata includes information for enabling viewing of an image associated with the token (hereinafter referred to as "target image") (for example, a URL for viewing the target image or data corresponding to the target image). The metadata is described by the distributed ledger system 50 at the time of token issuance.

In addition, the metadata can also include information about the details of the target image. The information regarding the details of the target image may include, for example, a part of the basic image information (FIG. 9) corresponding to the target image. Further, at least a part of the information regarding the details of the target image is determined by, for example, at least one of the user who is the creator of the target image or the right holder of the subject of the target image (for example, a person who has the right of publicity of the subject). You may. As an example, the information regarding the details of the target image may be information regarding the title of the target image, the episode at the time of shooting the target image, the subject, the shooting date, the shooting location, or a combination thereof.

The transaction condition information is information regarding the transaction conditions of the target image. As an example, the transaction condition information can include information on the conditions for collecting royalties associated with the distribution of the target image (for example, information on the calculation method of royalties, the payee of royalties, or a combination thereof). The transaction condition information may be determined, for example, by the creator of the target image, the right holder regarding the subject of the target image, some rules (eg, the rules of the platform for buying and selling tokens), or a combination thereof. The transaction condition information is described by the distributed ledger system 50 at the time of issuing the token. Alternatively, the transaction condition information may be information regarding the resale destination, resale timing, or restriction of the resale price of the target image.

(4) Information processing The information processing of the present embodiment will be described.

(4-1) Image Creation Process The image creation process of the present embodiment will be described. FIG. 11 is a flowchart of the image creation process of the present embodiment.

The image creation process of FIG. 11 is started in response to, for example, a user performing a predetermined operation (for example, selection of an object that accepts an instruction to start shooting) while the target application is being executed on the user terminal 10. ..

As shown in FIG. 11, the user terminal 10 executes image creation (S110).
Specifically, the user terminal 10 activates, for example, the camera 22 to shoot a subject. As a result, the user terminal 10 creates an image (still image or moving image). The user terminal 10 temporarily stores the created image in the storage device 11.

After step S110, the user terminal 10 executes image transmission (S111).
Specifically, the user terminal 10 transmits (uploads) the image created in step S110 to the server 30.

After step S111, the user terminal 10 executes image deletion (S112).
Specifically, the user terminal 10 deletes the image created in step S110 from the storage device 11.

The target application may be configured not to accept the user's operation during the series of processes from step S110 to step S112. This makes it possible to more reliably prevent the user from duplicating the image.

On the other hand, after step S111, the server 30 executes image storage (S131).
Specifically, the server 30 acquires the image transmitted in step S111 and stores the image in the storage device 31.

(4-1) Token issuance process The token issuance process of this embodiment will be described. FIG. 12 is a flowchart of the token issuance process of the present embodiment. FIG. 13 is a diagram showing an example of a screen displayed in the information processing of the present embodiment.

In the token issuing process of FIG. 12, for example, when the target application is being executed on the user terminal 10, or when the user terminal 10 is displaying a screen of a specific SaaS (Software as a Service), the user determines. It starts according to the operation. The predetermined operation is, for example, selection of an object created by the user and receiving an instruction to confirm an image for which a token has not been issued (hereinafter, referred to as "a token-unissued work"). The specific SaaS provides a service for managing a token-unissued work created by using, for example, a target application to a user.

As shown in FIG. 12, the user terminal 10 executes an image viewing request (S210).
Specifically, the user terminal 10 generates a browsing request for any of the token-unissued works by the user, and transmits the browsing request to the server 30. The browsing request includes information (for example, an image ID) that can identify the designated unissued token-issued work.

After step S210, the server 30 executes the acquisition of the processed image (S230).
Specifically, the server 30 acquires the browsing request transmitted in step S210 and identifies the token-unissued work (image) to be browsed. The server 30 acquires the processed image corresponding to the specified image. The server 30 may generate a processed image each time based on the specified image, or may store the once generated processed image in the storage device 31 and reuse it repeatedly. Here, the processed image can be generated by performing the following processing on a part or the whole of the image before processing (hereinafter, referred to as "original image").
-Combining additional images-Measuring-Reducing resolution-Changing colors-Changing brightness-Trimming-Adding distortion Here, the additional image may be a transparent image such as a watermark. However, it may be a non-transparent image such as a stamp. Further, the content of the additional image may be fixed or variable. As an example of the variable additional image, an image representing information about the shooting date, the creator, or the viewing date can be adopted.

After step S230, the server 30 executes the transmission of the processed image (S231).
Specifically, the server 30 transmits the processed image acquired in step S230 to the user terminal 10.

After step S231, the user terminal 10 executes the display of the processed image (S211).
Specifically, the user terminal 10 displays the processed image transmitted in step S231 on the display 21. As an example, a user can display a processed image corresponding to a work on a UI (User Interface) (hereinafter referred to as "work management UI") for managing a work for which a token has not been issued. The work management UI is displayed on the display 21 of the user terminal 10. The work management UI may be, for example, the screen of the target application executed on the user terminal 10, or the screen of a specific SaaS displayed by the Web browser executed on the user terminal 10.

The work management UI of FIG. 13 includes display objects A10a to A10b and operation objects B10a to B10d.

The display object A10a displays a preview of the processed image IM12 of one of the selected works (hereinafter referred to as “selected works”) among the works for which tokens have not been issued. In the example of FIG. 13, the processed image IM12 corresponds to an image obtained by synthesizing the watermark image IM12a with the corresponding original image.

The display object A10b displays supplementary information of the selected work. The supplementary information may be generated based on the basic image information of the selected work registered in the work database.

The operation object B10a accepts an instruction to issue a token associated with the selected work. When the operation object B10a is selected, the user terminal 10 may further accept the designation of information regarding the issuance condition or the sale condition of the selected work.

The information regarding the issuance condition can be specified either when the token is given to the user himself or when the token is given to the buyer of the token. Information regarding issuance conditions may include, for example, at least one of the following:
-Token issue destination (for example, whether to issue the token to the creator or the buyer of the work decided before the token issuance)
・ Transaction conditions for platform tokens that issue tokens (for example, royalty collection conditions for creators)

Information about the terms of sale may be specified when granting the token to the buyer of the token. Information regarding the terms of sale may include, for example, at least one of the following:
・ Selling method (for example, a platform for buying and selling tokens)
・ Sales destination (for example, wallet information of the buyer of the work)
·Sale price

The operation object B10b accepts an instruction to delete the selected work from the set of works for which tokens have not been issued. As an example, the number of unissued tokens that can be registered by the user on the server 30 is finite, and the user can register new unissued tokens on the server 30 by deleting unnecessary unissued tokens. It becomes possible to do.

The operation object B10c receives an instruction to return to a predetermined screen (for example, a home screen) from the work management UI. When the operation object B10c is selected, the user terminal 10 displays a predetermined screen on the display 21 and ends the token issuance process of FIG.

The operation object B10d receives an instruction to switch the selected work. When the operation object B10d is selected, the user terminal 10 treats another token-unissued work as a new selected work. As a result, the user terminal 10 updates the contents of the display objects A10a to A10b by, for example, re-executing steps S210 to S211.

After step S212, the user terminal 10 executes a token issuance request (S212).
Specifically, the user terminal 10 is an operation (for example,) in which the user instructs the issuance of a token associated with any of the unissued tokens while the work management UI of FIG. 13 is displayed on the display 21. (Selection of the operation object B10a in FIG. 13) is accepted from the user. The user terminal 10 generates a token issuance request and sends the issuance request to the server 30. The issuance request may include information (for example, an image ID) that can identify a work designated by the user (for example, the above-mentioned selected work). In addition, the issuance request may include information that can identify the issuance condition, the sale condition, or a combination thereof specified by the user.

After step S212, the server 30 executes token issuance (S232).
Specifically, the server 30 acquires the issuance request transmitted in step S212. The server 30 requests the distributed ledger system 50 to issue a token associated with the work specified by the user. When the platform for issuing tokens is specified by the user, the server 30 requests the distributed ledger system 50 corresponding to the platform to issue tokens.

The server 30 specifies the owner address information, the metadata, and the transaction condition information described in the token. The server 30 may determine the owner address information according to the token issuance conditions specified by the user or a predetermined rule. The server 30 may determine the metadata based on the information obtained from the right holder (which may include the user who is the creator of the work) regarding the subject of the work, the basic image information, or a combination thereof. The server 30 may determine transaction condition information based on information obtained from the right holder regarding the subject of the work, predetermined rules, or a combination thereof.

Further, the server 30 may transmit the work (image) specified by the user to the external server. The external server corresponds to the storage destination of the image referred to by the information (metadata) described in the token. Alternatively, the server 30 may send the image to the distributed ledger system 50 in order to embed the image in the token.

Further, the server 30 may collect a token issuance fee from the user before executing the token issuance (S232). When the settlement of the issuance fee fails, the server 30 may notify the user terminal 10 of the settlement error and prompt the user terminal 10 to re-input the settlement information.

After step S232, the server 30 executes image deletion (S233).
Specifically, the server 30 deletes the image associated with the token issued in step S232 from the storage device 31.

On the other hand, after step S232, the user terminal 10 executes token acquisition (S213).
Specifically, the user terminal 10 acquires the token issued in step S232. Tokens may be earned for users of the Target App using, for example, a wallet generated by Ethereum's Web3 API or other means, or using a wallet owned by the user that is not related to the Target App. You may. However, if the buyer of the work designated by the user is determined at the time of issuing the token, the server 30 may issue the token to the wallet of the buyer according to the instruction of the user. In this case, step S213 may be omitted.

(5) Summary As described above, the user terminal 10 of the present embodiment transmits the created image to the server 30, and deletes the image from the storage device 11 after the transmission of the image. Further, the user terminal 10 requests the server 30 to issue a token proving that the owner of the image is the owner. As a result, the user cannot keep a copy of the image associated with the token at hand, so that the rarity of the image can be ensured.

The server 30 of the present embodiment acquires an image created by the user and stores the image in the storage device 31. The server 30 issues the token in response to the acquisition of a request for issuing a token proving that the owner of the image is issued, and deletes the image from the storage device 31 after the token is issued. As a result, after the token is issued, a copy of the image associated with the token cannot be left on the server 30, so that the rarity of the image can be ensured.

The server 30 may transmit the processed image generated by processing the token-unissued work (image) to the user terminal 10 in response to a request for viewing the image. As a result, the user cannot obtain complete duplicate data of the token-unissued work even if the screenshot function of the user terminal 10 is used, so that the rarity of the work can be ensured. The server 30 may generate a processed image by synthesizing an additional image with the token-unissued work. This makes it possible for the viewer to easily recognize the difference between the work for which the token has not been issued and the processed image, or that the processed image is not the original image.

(6) Modification Example The storage device 11 may be connected to the user terminal 10 via the network NW. The display 21 or the camera 22 may be provided in the user terminal 10 in advance, or may be an external peripheral device. The storage device 31 may be connected to the server 30 via the network NW.

In the above description, an example in which each step is executed in a specific order in each process is shown, but the execution order of each step is not limited to the example described as long as there is no dependency. Further, each step of the above information processing can be executed by any of the user terminal 10 and the server 30.

In the above description, an example is shown in which the creator (user) of the work requests the server 30 to issue a token by using the user terminal 10. However, the user can also sell the token (hereinafter referred to as "first token") associated with his / her work on a platform where the token can be bought and sold.
In this case, in the above description, the term "issue" can be appropriately read as "exhibition". Specifically, the user terminal 10 may request the server 30 to sell the first token on a platform on which tokens can be bought and sold, instead of requesting the server 30 to issue the first token. On the other hand, the server 30 may acquire a request for selling the first token instead of the request for issuing the first token, and sell the first token in response to the acquisition of the request. Then, after the first token is exhibited, the server 30 deletes the work (image) associated with the first token from the storage device 31.
The user may specify information about the listing conditions when listing the first token on the platform. The information regarding the listing conditions can include, for example, at least one of the following.
・ Platform for selling tokens ・ Suggested selling price of tokens ・ Selling period of tokens ・ Transaction conditions of tokens (for example, conditions for collecting royalties for creators)
As an example, the user terminal 10 may accept the designation of a platform for buying and selling tokens, and may send a token listing request containing information that can identify the platform to the server 30. This allows the user to list the token on the desired platform. On the other hand, the server 30 may sell the first token on the platform in response to a request for selling the first token, which includes information indicating the platform designated by the user. This allows the token to be listed on the user's desired platform.
Here, listing the first token may mean transmitting the work (image) associated with the first token to the server provided by the platform. In this case, the first token will be issued by the platform and granted to the buyer after the buyer has been determined. However, depending on the specifications of the platform, the server 30 may issue the first token to the wallet designated by the platform before the buyer of the first token is determined.

When a right related to a specific subject (for example, a publicity right) exists, the issuance or listing of a token associated with the image of the subject (for example, a celebrity) may be performed subject to the permission of the right holder. As an example, the user acquires (for example, purchases) the authority regarding a specific subject (for example, the authority to shoot a specific subject or the authority to tokenize an image of a specific subject) from the right holder. Then, the user terminal 10 may send a token issuance request or an exhibition request including information indicating the authority regarding a specific subject to the server 30. This makes it possible to issue or sell a token associated with an image of a specific subject without infringing on the rights relating to that subject. On the other hand, the server 30 may be configured not to issue or sell a token associated with an image of a particular subject unless it is confirmed that the information indicating the authority regarding the particular subject is appropriate. This makes it possible to prevent the issuance or listing of tokens that infringe the rights relating to a specific subject. Alternatively, the server 30 may issue a token unless the authentication source (eg, the person who has the right to the specific subject or the person who has been delegated to it) authenticates the image, which is specified by the information indicating the authority regarding the specific subject. It may be configured not to list. This makes it possible to prevent the issuance or listing of tokens associated with an image that the authentication source deems inappropriate (for example, an image that damages the honor of a specific subject). Here, for image authentication by the authentication source, it is preferable to provide a processed image instead of the original image from the viewpoint of ensuring the rarity of the image.

In the above description, an example is shown in which the server 30 deletes the image IM 10 from the storage device 31 after issuing or selling the token associated with the image IM 10. However, the image IM 10 may be stored in the storage device 31 of the server 30 even after the token is issued or exhibited. In this case, information (for example, URL) for accessing the image IM10 stored in the storage device 31 of the server 30 is described as token metadata.

In the above description, an example of creating an image (that is, visual content) by shooting a subject is shown. However, the image may be created by other means. As an example, the user terminal 10 may create an image (for example, a digital painting or a digital comic) according to a drawing operation of the user.

In the above description, an example of deleting the image from the storage device 11 after transmitting the image to the server 30 is shown. However, the user terminal 10 may prevent data representing the same visual information as the transmitted image from remaining in the storage device 11 by another method. As an example, the user terminal 10 may overwrite and save the image with a processed image corresponding to the image after transmitting the image to the server 30.

In the above description, an example of deleting the image from the storage device 31 after issuing or selling the token associated with the image is shown. However, the server 30 may prevent data representing the same visual information as the image associated with the token from remaining in the storage device 31 by another method. As an example, the server 30 may issue or sell a token associated with an image, and then overwrite and save the image with a processed image corresponding to the image.

In the above description, an example of generating a processed image by synthesizing an additional image with the original image is shown. Here, the server 30 may determine the position where the additional image is combined according to the subject of the original image. As an example, the server 30 may determine the composite position so as to avoid a specific subject (for example, a person), or determine the composite position so as to avoid a specific area (for example, a face area) of the specific subject. May be good. This ensures the rarity of the image while suppressing the adverse effect of the composition of the additional image on the selection of the image for which the token is issued or exhibited by the user, or the evaluation of the image associated with the token by the purchaser. Can be done.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above embodiments. Further, the above-described embodiment can be variously improved or modified without departing from the gist of the present invention. Further, the above embodiments and modifications can be combined.

1: Information processing system 10: User terminal 11: Storage device 12: Processor 13: Input / output interface 14: Communication interface 21: Display 22: Camera 30: Server 31: Storage device 32: Processor 33: Input / output interface 34: Communication interface 50: Distributed ledger system 55: Node computer

Claims (15)

A computer equipped with a storage device,
First means of creating visual content,
A means for transmitting the first visual content to an external device,
A means for preventing data representing the same visual information as the first visual content from remaining in the storage device after transmission of the first visual content.
A means for requesting the external device to issue a first token proving that it is the owner of the first visual content, or to sell the first token on a platform on which tokens can be bought and sold.
A program that functions as. The blocking means deletes the first visual content from the storage device.
The program according to claim 1. Further functioning the computer as a means of accepting the designation of the platform,
The means for requesting the issuance or listing of the first token sends the listing request for the first token to the external device, including information that can identify the designated platform.
The program according to claim 1 or 2. The first visual content is an image or a moving image of a specific subject.
The means for requesting the issuance or listing of the first token sends a request including information indicating authority regarding the specific subject to the external device.
The program according to any one of claims 1 to 3. A means of acquiring the first visual content created by the user,
A means for storing the first visual content in a storage device,
A means for issuing a first token proving that the owner of the first visual content, or obtaining a request for selling the first token on a platform capable of buying and selling the token.
A means for issuing or selling the first token in response to the issuance of the first token or the acquisition of a request for selling the first token.
An information processing device including means for preventing data representing the same visual information as the first visual content from remaining in the storage device after the issuance or listing of the first token. The blocking means deletes the first visual content from the storage device after the issuance or listing of the first token.
The information processing apparatus according to claim 5. A means for acquiring a request for viewing the first visual content from a user terminal, and
The fifth or sixth aspect of the present invention further comprising a means for transmitting the second visual content generated by processing the first visual content to the user terminal in response to the viewing request. Information processing equipment. The second visual content is generated by synthesizing an additional image with the first visual content.
The information processing apparatus according to claim 7. Further provided are means for determining the position where the additional image is combined according to the subject of the first visual content.
The information processing apparatus according to claim 8. The request for listing the first token includes information indicating the platform designated by the user.
The means for issuing or selling the first token is to sell the first token on the platform designated by the user in response to the request for selling the first token.
The information processing apparatus according to any one of claims 5 to 9. The first visual content is an image or a moving image of a specific subject.
The request for issuance or listing of the first token includes information indicating authority regarding the specific subject.
The means for issuing or selling the first token does not issue or sell the first token unless it is confirmed that the information indicating the authority regarding the specific subject is appropriate.
The information processing apparatus according to any one of claims 5 to 10. The first visual content is an image or a moving image of a specific subject.
The request for issuance or listing of the first token includes information indicating authority regarding the specific subject.
The means for issuing or selling the first token does not issue or sell the first token unless the authentication source specified by the information indicating the authority regarding the specific subject authenticates the first visual content.
The information processing apparatus according to any one of claims 5 to 10. The computer
The steps to get the first visual content created by the user,
The step of storing the first visual content in the storage device,
A step of obtaining a request to issue a first token proving that the owner of the first visual content or to sell the first token to a platform on which tokens can be bought and sold, and a step of obtaining the request.
The step of issuing or selling the first token in response to the acquisition of the request for issuing or selling the first token, and
A method comprising a step of preventing data representing the same visual information as the first visual content from remaining in the storage device after the issuance or listing of the first token. Computer,
A means of retrieving the first visual content created by the user,
A means for storing the first visual content in a storage device,
A means for obtaining a request to issue a first token proving to be the owner of the first visual content, or to sell the first token to a platform on which tokens can be bought and sold.
A means for issuing or selling the token in response to the acquisition of the request for issuing or selling the first token.
A program that functions as a means for preventing data representing the same visual information as the first visual content from remaining in the storage device after the issuance or listing of the first token. Equipped with a user terminal and a server,
The user terminal is
The first storage device and
First means of creating visual content,
A means for transmitting the first visual content to the server,
A means for preventing data representing the same visual information as the first visual content from remaining in the first storage device after the transmission of the first visual content.
A means for requesting the server to issue a first token proving that the owner of the first visual content or to sell the first token on a platform on which tokens can be bought and sold.
The server
The means for acquiring the first visual content and
A means for storing the first visual content in the second storage device,
The means for obtaining the request for issuance or listing of the first token, and
The means for issuing or selling the first token in response to the acquisition of the request for issuing or selling the first token, and
A means for preventing data representing the same visual information as the first visual content from remaining in the second storage device after the issuance or listing of the first token.
system.

Images