Information processing apparatus, information processing method, and information processing system

Through electronic signatures and in-depth information verification, combined with blockchain addresses, the problem of difficulty in proving the authenticity of NFT content information in the existing technology is solved, and effective verification of content information and publishers is achieved to ensure the authenticity and credibility of NFTs. sex.

CN118923081APending Publication Date: 2024-11-08SONY GROUP CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380026853.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-18
Filing Date
2023-02-28
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

The prior art is difficult to prove the authenticity of content information to be NFTed, including whether the content information has been tampered with, forged and the legality of the publisher.

Method used

By using electronic signatures to verify the integrity of the content information, and after verification, requesting to issue a non-fungible token (NFT) corresponding to the content information, verify the authenticity of the issuer in combination with the blockchain address, and verify through in-depth information Legality of content information.

Benefits of technology

It realizes verification of the authenticity, integrity and legality of the content information to be NFTed to ensure the authenticity and credibility of the NFT.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923081A_ABST
    Figure CN118923081A_ABST
Patent Text Reader

Abstract

The present disclosure relates to an information processing device and method, and an information processing system capable of proving authenticity of NFT-converted content information. Whether or not the content information has been tampered with is verified by using an electronic signature, and if the result of the verification is determined that the content information has not been tampered with, issuing of an NFT corresponding to the content information is requested or an NFT corresponding to the content information is issued. The present disclosure can be applied, for example, to an information processing device, an electronic device, an information processing method, a program, or an information processing system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to an information processing device and method, and an information processing system, and more specifically to an information processing device and method, and an information processing system that can prove the authenticity of content information to be NFT-ified. Background Art

[0002] In the past, there was a method of issuing non-fungible tokens (NFT) for digital content information and using NFT to provide adaptive real-time distribution (for example, refer to Patent Document 1).

[0003] Prior art literature Patent Literature Patent document 1: WO2021 / 246498A Summary of the invention Technical issues to be solved by the invention However, in previous methods, it is difficult to prove the authenticity of the content information to be NFTized.

[0004] The present disclosure has been made in view of such a situation, and an object of the present disclosure is to enable the authenticity of content information to be NFTized to be proven.

[0005] Technical solutions for solving technical problems An information processing device according to one aspect of the present technology is an information processing device, comprising: a verification unit, which uses an electronic signature to verify whether content information has been tampered with; and a request unit, which requests the issuance of a non-fungible token (NFT) corresponding to the content information when it is determined as a result of the verification that the content information has not been tampered with.

[0006] An information processing method according to one aspect of the present technology is an information processing method comprising the steps of: using an electronic signature to verify whether content information has been tampered with; and when it is determined as a result of the verification that the content information has not been tampered with, requesting the issuance of a non-fungible token (NFT) corresponding to the content information.

[0007] According to another aspect of the present technology, an information processing device is an information processing device, comprising: a verification unit, which uses an electronic signature to verify whether content information has been tampered with; and an issuance unit, which issues a non-fungible token (NFT) corresponding to the content information when it is determined as a result of the verification that the content information has not been tampered with.

[0008] An information processing method according to another aspect of the present technology is an information processing method comprising the steps of: using an electronic signature to verify whether content information has been tampered with; and when it is determined as a result of the verification that the content information has not been tampered with, issuing a non-fungible token (NFT) corresponding to the content information.

[0009] According to another aspect of the present technology, an information processing device is an information processing device, including: a content information generation unit, which generates content information according to a user's operation; and a content information file generation unit, which generates a content information file that stores the content information and a blockchain address corresponding to the user.

[0010] An information processing method according to another aspect of the present technology is an information processing method comprising the steps of: generating content information according to a user's operation; and generating a content information file that stores the content information and a blockchain address corresponding to the user.

[0011] According to another aspect of the present technology, an information processing system is an information processing system comprising: a content information generating device, a verification device and a non-fungible token (NFT) issuing device, wherein the content information generating device comprises: a content information generating unit for generating content information according to user operations; a content information file generating unit for generating a content information file for storing the content information and a blockchain address corresponding to the user; and a verification request unit for requesting verification of the content information by supplying the content information file to the verification device, the verification device comprising: a verification unit for verifying whether the content information has been tampered with using an electronic signature; and an issuance request unit for requesting the NFT issuing device to issue an NFT corresponding to the content information when it is determined as a result of the verification that the content information has not been tampered with, and the NFT issuing device comprises: an issuance unit for issuing the requested NFT corresponding to the content information.

[0012] In an information processing device and method according to one aspect of the present technology, an electronic signature is used to verify whether content information has been tampered with, and if the result of the verification is that the content information is determined not to have been tampered with, a request is made to issue a non-fungible token (NFT) corresponding to the content information.

[0013] In an information processing device and method according to another aspect of the present technology, an electronic signature is used to verify whether content information has been tampered with, and if the result of the verification is that the content information is determined not to have been tampered with, a non-fungible token (NFT) corresponding to the content information is issued.

[0014] In an information processing device and method according to another aspect of the present technology, content information is generated according to a user's operation, and a content information file storing the content information and a blockchain address corresponding to the user is generated.

[0015] In an information processing system according to another aspect of the present technology, in a content information generating device, content information is generated according to a user's operation, and a content information file is generated that stores the content information and a blockchain address corresponding to the user. The content information file is supplied to a verification device, thereby requesting verification of the content information. In the verification device, verification is performed to determine whether the content information has been tampered with by using an electronic signature. If the result of the verification is that the content information has not been tampered with, a request is made to a non-fungible token (NFT) issuing device to issue an NFT corresponding to the content information. In the NFT issuing device, the requested NFT corresponding to the content information is issued. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A diagram showing a main configuration example of an image processing system.

[0017] Figure 2 A block diagram showing a main configuration example of a user terminal device.

[0018] Figure 3 A block diagram showing a main configuration example of an imaging device.

[0019] Figure 4 This is a block diagram showing a main configuration example of a verification server.

[0020] Figure 5 This is a block diagram showing an example of the main structure of a smart contract.

[0021] Figure 6 This is a flowchart for explaining an example of the flow of image processing.

[0022] Figure 7 This is a flowchart for explaining an example of the flow of registration processing.

[0023] Figure 8 is a diagram showing an example of a registration confirmation screen.

[0024] Fig. 9 A flowchart illustrating an example of the flow of imaging processing.

[0025] Fig.10 A diagram showing a main structural example of an image file.

[0026] Fig.11 This is a flowchart for explaining an example of the flow of the verification process.

[0027] Fig.12A diagram illustrating an example of a state of verification using a depth image.

[0028] Fig.13 A flowchart illustrating an example of the process of NFT issuance processing.

[0029] Fig.14 A flowchart illustrating an example of the process of NFT issuance processing.

[0030] Fig.15 A block diagram showing a main configuration example of a user terminal device.

[0031] Fig.16 A flowchart illustrating an example of the process of NFT issuance processing.

[0032] Fig.17 This is a flowchart for explaining an example of the flow of the verification process.

[0033] Fig.18 This is a block diagram showing a main configuration example of a verification server.

[0034] Fig.19 This is a block diagram showing an example of the main structure of a smart contract.

[0035] Fig. 20 This is a flowchart for explaining an example of the flow of the certificate issuance process.

[0036] Fig.21 This is a flowchart for explaining an example of the flow of the certification issuance process.

[0037] Fig. 22 To explain the following Fig.21 This is a flowchart showing an example of the flow of the subsequent verification issuance process.

[0038] Fig.23 A block diagram showing a main configuration example of a computer.

[0039] Reference numerals 100: image processing system; 101: user terminal device; 102: imaging device; 103: verification server; 104: smart contract; 110: network; 121: communication unit; 122: registration processing unit; 123: request unit; 124: storage unit; 141: communication unit; 142: registration unit; 143: imaging control unit; 144: image file generation unit; 145: upload unit; 146: storage unit; 147: imaging unit; 148: depth information generation unit Yuan; 161: Communication unit; 162: Verification unit; 163: Request unit; 164: Storage unit; 181: Communication unit; 182: NFT issuance unit; 183: Storage unit; 230: Image file; 231: Image data; 232: Blockchain address; 233: Depth information; 234: Camera electronic signature; 235: Camera certificate; 311: Verification unit; 411: Issuance processing unit; 421: Camera certificate issuance unit; 422: Verification unit; 900: Computer DETAILED DESCRIPTION Hereinafter, a mode for implementing the present disclosure (hereinafter referred to as an embodiment) will be described. Note that the description will be given in the following order.

[0040] 1. Documents supporting technical content and technical terminology, etc. 2. Proof of authenticity of NFT content information 3. First Embodiment (Image Processing System) 4. Example 2 (Verification after NFT issuance) 5. Example 3 (Verification by smart contract) 6. Additional Notes <1. Documents supporting technical content and technical terms> The scope disclosed in the present technology includes not only the contents described in the embodiments but also the contents described in the following patent documents and the like known at the time of filing the application, the contents of other documents cited in the following patent documents, and the like.

[0041] Patent Document 1: (as mentioned above) That is to say, the contents described in the above patent documents, the contents of other documents cited in the above patent documents, etc. are all the basis for determining the supporting requirements.

[0042] <2. Proof of authenticity of NFT content information> <NFT conversion of digital content information> In the past, there was a method of proving the ownership of digital content information by issuing non-fungible tokens (NFT). For example, Patent Document 1 discloses a method of providing adaptive real-time distribution using NFT.

[0043] NFT functions like a cryptographic token, but unlike cryptocurrencies, NFT has the characteristic of being non-exchangeable. In other words, there is no substitute for NFT. Therefore, each NFT may have different resources and may have different values. NFT is generated by linking the record of a cryptographic hash (a string used to identify a series of data) with the previous record through the blockchain and forming a chain of identifiable data blocks.

[0044] However, in the previous NFT technology, it is difficult to prove the authenticity of the content information to be NFTized. For example, although the content information can be identified as described above by applying NFT, it is impossible to prove whether the content information has been tampered with before the NFT is issued.

[0045] <Verification of authenticity> Therefore, an electronic signature is used to verify whether the content information has been tampered with, and when the result of the verification is that the content information is determined not to have been tampered with, a request is made to issue an NFT corresponding to the content information.

[0046] For example, the information processing device includes: a verification unit that uses an electronic signature to verify whether the content information has been tampered with; and a request unit that requests the issuance of an NFT corresponding to the content information when the result of the verification determines that the content information has not been tampered with.

[0047] As described above, by requesting the issuance of an NFT for content information that has been verified to be tampered with, the authenticity of the content information to be NFTized can be proven.

[0048] In addition, an electronic signature is used to verify whether the content information has been tampered with, and if the result of the verification is that the content information is determined not to have been tampered with, an NFT corresponding to the content information is issued.

[0049] For example, the information processing device includes: a verification unit that uses an electronic signature to verify whether the content information has been tampered with; and an issuance unit that issues an NFT corresponding to the content information when the result of the verification determines that the content information has not been tampered with.

[0050] In this way, by NFTing the content information after verifying whether the content information has been tampered with, the authenticity of the content information to be NFTed can be proved.

[0051] In addition, using the previous NFT technology, it is difficult to prove the authenticity of the issuer of the NFT (the applicant for NFT issuance). In other words, even if NFT is applied, it is difficult to confirm whether the issuer of the NFT is legal and valid. Therefore, for example, someone else who is not the creator of the content information can convert the content information into NFT without the permission of the creator.

[0052] Therefore, content information is generated according to the user's operation, and a content information file storing the content information and the blockchain address corresponding to the user is generated.

[0053] For example, the information processing device includes: a content information generation unit that generates content information according to a user's operation; and a content information file generation unit that generates a content information file that stores the content information and a blockchain address corresponding to the user.

[0054] In this way, by adding the blockchain address of the user who created the content information to the NFT-ized content information, the blockchain address can be used to verify the issuer of the NFT. In other words, the authenticity of the issuer of the NFT can be proved.

[0055] In addition, in the conventional NFT technology, even when NFT is applied, it is difficult to confirm whether the content information to be NFTized is forged. Therefore, for example, it is possible to convert a captured image (an image of a non-existent subject) forged using a technique such as special effect imaging into an NFT. For example, by capturing a 2D image by an image contributor, it is possible to generate a captured image that appears to be a 3D subject, and convert the captured image into an NFT.

[0056] Therefore, depth information corresponding to the content information can be generated and stored in a content information file. For example, the information processing device can further include a depth information generating unit for generating depth information corresponding to the content information, and the content information file generating unit can store the depth information in the content information file.

[0057] In this way, by adding depth information corresponding to the content information to be converted into NFT, it is possible to verify whether the content information to be converted into NFT is forged using the depth information.

[0058] <3. First Embodiment> <Image Processing System> Figure 1 : is a block diagram showing an example of the structure of an image processing system as one aspect of an information processing system to which the present technology is applied. Figure 1 The image processing system 100 shown is a system that uses (image data of) a captured image as content information and performs processing related to converting the content information into an NFT. Note that in the following description, the image data of a captured image may be simply referred to as a captured image.

[0059] like Figure 1As shown, the image processing system 100 includes a user terminal device 101, an imaging device 102, a verification server 103, and a smart contract 104. The user terminal device 101 to the smart contract 104 are each connected to the network 110 in a communicable manner. The user terminal device 101 to the smart contract 104 can communicate with other devices via the network 110. In addition, the user terminal device 101 and the imaging device 102 can also communicate through near field communication.

[0060] The user terminal device 101 is an information processing device used (or owned) by the user of the imaging device 102. The user of the user terminal device 101 (and the imaging device 102) is a user of the NFT and has a corresponding blockchain address. The blockchain is a list of growing records called blocks linked using encryption technology. Each block may contain a cryptographic hash of the previous block, a timestamp, transaction data, etc. NFT is an irreplaceable data unit that uses the blockchain. The blockchain address is the identification information of the user who uses the technology that uses such a blockchain. The blockchain address is generated by using a public key (also called a user public key) corresponding to a private key unique to the user (also called a user private key). The user terminal device 101 has a function of processing such a blockchain address. In addition, the user terminal device 101 has an NFT wallet function and is capable of processing transactions related to NFTs.

[0061] The user terminal device 101 performs processing related to the registration of the user's blockchain address, processing related to the verification of the image file that stores the captured image, processing related to the issuance of the NFT, etc. For example, the user terminal device 101 can communicate with the imaging device 102, the verification server 103, or the smart contract 104. For example, the user terminal device 101 can provide and register the user's blockchain address to the imaging device 102. In addition, the user terminal device 101 can request the smart contract 104 to issue the NFT. In addition, the user terminal device 101 can request the verification server 103 to verify the information stored in the image file. In addition, the user terminal device 101 can request the smart contract 104 to verify the information stored in the image file and issue the NFT.

[0062] The imaging device 102 performs processing related to the generation of a captured image (still image). For example, the imaging device 102 can communicate with the user terminal device 101 and the verification server 103. For example, the imaging device 102 can register a blockchain address supplied from the user terminal device 101. In addition, the imaging device 102 can capture an image of a subject and generate image data of the captured image according to the operation of the user (image contributor). In addition, the imaging device 102 can generate an image file that stores the captured image (image data). In addition, the imaging device 102 can attach the blockchain address of the user (image contributor) to the captured image and save the image in the image file. In addition, the imaging device 102 can request verification of the image file by sending the image file to the verification server 103. In addition, the imaging device 102 can request the generation of an NFT issuance transaction by sending the image file to the verification server 103, and the NFT issuance transaction is used to request the issuance of an NFT corresponding to the image file. In addition, the imaging device 102 can obtain and register a certificate supplied from the verification server 103. Note that the imaging device 102 can communicate with the smart contract 104.

[0063] The verification server 103 performs processing related to the verification of the image file and processing related to the issuance of the NFT. For example, the verification server 103 can communicate with the user terminal device 101, the imaging device 102, or the smart contract 104. For example, the verification server 103 can obtain an image file generated by the imaging device 102. In addition, the verification server 103 can verify the information stored in the image file.

[0064] In addition, the verification server 103 has an NFT wallet function and is capable of processing transactions related to NFTs. For example, the verification server 103 can request the smart contract 104 to issue an NFT corresponding to the image file by using its own wallet function. In addition, the verification server 103 can generate an NFT issuance transaction for requesting the issuance of an NFT corresponding to the image file, and supply the NFT issuance transaction to the user terminal device 101 to request the issuance of the NFT.

[0065] In addition, the verification server 103 can communicate with the imaging device 102 and the smart contract 104 to perform processing related to the issuance of the certificate.

[0066] The smart contract 104 is an information processing device that performs processing related to the issuance of NFT. For example, the smart contract 104 can communicate with the user terminal device 101, the imaging device 102, or the verification server 103. For example, the smart contract 104 can accept a request from the verification server 103 or the user terminal device 101, and issue an NFT in response to the request. In addition, the smart contract 104 can issue a certificate and provide the certificate to the verification server 103. In addition, the smart contract 104 accepts a request from the user terminal device 101, and verifies the information stored in the image file in response to the request and issues an NFT.

[0067] In the image processing system 100, the imaging device 102 is a content information generating device that generates content information, the verification server 103 is a verification device that verifies the content information, and the smart contract 104 is an NFT issuing device that issues NFT. That is, in the image processing system 100, the captured image (image data) is the content information, and the image contributor is the creator of the content information. In addition, the image file is a content information file that stores the content information.

[0068] Note that the user of the user terminal device 101 is the same as the user of the imaging device 102. Here, the user means the user (operator) or owner of the device. The user may be an individual, a company, or an organization. In addition, the user of the user terminal device 101 and the user of the imaging device 102 may be actually the same, or may be regarded as actually the same due to a contract or the like.

[0069] In the image processing system 100, for example, the imaging device 102 captures an image of a subject according to an operation of a user (image contributor) and generates a captured image. In addition, the imaging device 102 generates an image file that stores the captured image and a blockchain address corresponding to the user. In addition, the imaging device 102 supplies the image file to the verification server 103 to request verification of the captured image. Then, the verification server 103 uses an electronic signature to verify whether the content information has been tampered with. If the result of the verification is that the captured image has not been tampered with, the smart contract 104 is requested to issue an NFT corresponding to the captured image. Then, the smart contract 104 issues the requested NFT corresponding to the captured image.

[0070] Thus, an NFT corresponding to the content information whose authenticity has been verified by verification is issued. In other words, the image processing system 100 can verify the authenticity of the content information converted by the NFT.

[0071] Note that Figure 1In the example of , the image processing system 100 includes one user terminal device 101, one imaging device 102, one verification server 103, and one smart contract 104, but the number of each device is arbitrary. For example, multiple user terminal devices 101, multiple imaging devices 102, multiple verification servers 103, and multiple smart contracts 104 may be provided.

[0072] <User Terminal Device> Figure 2 1 is a block diagram showing a main configuration example of a user terminal device 101 as one aspect of an information processing device to which the present technology is applied. Figure 2 The main processing units and data flows are shown in FIG. Figure 2 That is, the user terminal device 101 may include Figure 2 In addition, there may be devices or processing units not shown as modules. Figure 2 The data flow or processing is shown by arrows etc.

[0073] The user terminal device 101 can be implemented with any structure. For example, the user terminal device 101 can be a dedicated device. In addition, the user terminal device 101 can be, for example, a portable information processing terminal device such as a so-called smart phone, a smart watch, a tablet terminal, a notebook personal computer, etc. In addition, the user terminal device 101 can include a single device or multiple devices.

[0074] like Figure 2 As shown, the user terminal device 101 includes a communication unit 121 , a registration processing unit 122 , a request unit 123 and a storage unit 124 .

[0075] The communication unit 121 performs processing related to communication with other devices. For example, the communication unit 121 can communicate with the imaging device 102, the verification server 103, or the smart contract 104 via the network 110. In addition, the communication unit 121 can perform near field communication with the imaging device 102.

[0076] The near field communication may be wired communication or wireless communication. For example, the user terminal device 101 and the imaging device 102 may be connected via a communication cable of a predetermined communication standard, and wired communication may be performed via the communication cable. The communication standard is arbitrary. For example, a universal serial bus (USB) (registered trademark), a high-definition multimedia interface (HDMI) (registered trademark), or other standards may be used. In addition, the user terminal device 101 and the imaging device 102 may perform near field communication of a predetermined communication standard. The communication standard is arbitrary. For example, Bluetooth (registered trademark), ultra-wideband (UWB), or Wi-Fi (registered trademark) may be used.

[0077] For example, the communication unit 121 may acquire information supplied from other devices through the above communication and supply the information to the registration processing unit 122 and the request unit 123. In addition, the communication unit 121 may acquire information supplied from the registration processing unit 122 or the request unit 123 and supply the information to other devices through the communication.

[0078] The registration processing unit 122 performs processing related to the registration of the blockchain address of the user. That is, the registration processing unit 122 may also be referred to as a registration unit. For example, the registration processing unit 122 may control the communication unit 121 to start a near field communication session with the imaging device 102. In addition, the registration processing unit 122 may obtain the blockchain address of the user from the storage unit 124. In addition, the registration processing unit 122 may supply the blockchain address to the imaging device 102 via the communication unit 121 to request registration of the blockchain address. Note that the blockchain address may be registered through near field communication with the imaging device 102 or through communication via the network 110.

[0079] The request unit 123 performs processing related to requesting the issuance of an NFT. The request unit 123 has an NFT wallet function. For example, the request unit 123 can obtain an NFT issuance transaction supplied from the verification server 103 via the communication unit 121. The NFT issuance transaction includes information required to issue the NFT. In addition, the request unit 123 can obtain the user wallet private key from the storage unit 124. In addition, the request unit 123 can request the smart contract 104 to issue the NFT by executing the NFT issuance transaction using the user wallet private key. With this processing, the information required to issue the NFT is supplied to the smart contract 104 via the communication unit 121.

[0080] The storage unit 124 includes any storage medium such as a hard disk or a semiconductor memory, and performs processing related to the storage and reading of any information. For example, the storage unit 124 may pre-store a blockchain address or a user wallet private key corresponding to the user of the user terminal device 101. Note that "pre-" means at least before the information is used. That is, the storage unit 124 may store this information, for example, at the time of shipment or after shipment. In addition, the storage unit 124 may read the blockchain address in response to a request from the registration processing unit 122, and supply the blockchain address to the registration processing unit 122. In addition, the storage unit 124 may read the user wallet private key in response to a request from the request unit 123, and supply the user wallet private key to the request unit 123.

[0081] In the user terminal device 101 having such a structure, for example, the communication unit 121 performs communication (near field communication) with the imaging device 102 , and the registration processing unit 122 utilizes the communication with the imaging device 102 to supply the blockchain address of the user to the imaging device 102 via the communication unit 121 .

[0082] Thereby, the user terminal device 101 can easily register the blockchain address in the imaging device 102 .

[0083] In addition, the request unit 123 executes the NFT issuance transaction. As a result, the user terminal device 101 can request the smart contract 104 to issue an NFT.

[0084] In addition, the request unit 123 acquires and executes the NFT issuance transaction supplied from the verification server 103 via the communication unit 121. Thus, it is possible to request issuance of an NFT corresponding to content information whose authenticity has been verified in the verification server 103.

[0085] <Imaging Device> Figure 3 1 is a block diagram showing a main configuration example of an imaging device 102 as one aspect of an information processing device to which the present technology is applied. Figure 3 In the figure, the main processing units, data flows, etc. are shown. Figure 3 That is, the imaging device 102 may include Figure 3 In addition, there may be devices or processing units not shown as blocks. Figure 3 The data flow or processing is shown by arrows etc.

[0086] The imaging device 102 may be implemented by any structure. For example, the imaging device 102 may be a dedicated device for capturing still images such as a so-called camera. In addition, the imaging device 102 may be a device capable of capturing both still images and moving images such as a so-called video camera. In addition, the imaging device 102 may be an information processing device having an imaging function such as a so-called smart phone, a smart watch, a tablet terminal, a notebook personal computer, etc. In addition, the imaging device 102 may include a single device or a plurality of devices.

[0087] like Figure 3 As shown, the imaging device 102 includes a communication unit 141, a registration unit 142, an imaging control unit 143, an image file generation unit 144, an upload unit 145, a storage unit 146, a UI unit 147, an imaging unit 148 and a depth information generation unit 149.

[0088] The communication unit 141 performs processing related to communication with other devices. For example, the communication unit 141 can communicate with the user terminal device 101, the verification server 103, or the smart contract 104 via the network 110. In addition, the communication unit 141 can perform near field communication with the user terminal device 101.

[0089] For example, the communication unit 141 may acquire information supplied from other devices through such communication and supply the information to the registration unit 142. In addition, the communication unit 141 may acquire information supplied from the registration unit 142 or the upload unit 145 and supply the information to other devices through the communication.

[0090] The registration unit 142 performs processing related to the registration of the user's blockchain address. For example, the registration unit 142 may control the communication unit 141 to start a near field communication session with the user terminal device 101. In addition, the registration unit 142 may acquire the blockchain address sent from the user terminal device 101 through the near field communication via the communication unit 141. In addition, the registration unit 142 may supply the blockchain address to the storage unit 146 and store the blockchain address. That is, the user's blockchain address is registered through this processing.

[0091] In addition, the registration unit 142 may cause the UI unit 147 (the output device included therein) to present information related to the registration of the blockchain address. In addition, the registration unit 142 may cause the UI unit 147 (the input device included therein) to accept the user's instruction (operation) related to the registration of the blockchain address. Then, the registration unit 142 may acquire information indicating the user's instruction (operation) received through the UI unit 147. In addition, the registration unit 142 may perform processing related to the registration of the blockchain address based on the information.

[0092] Note that the blockchain address may be manually registered by the user. In this case, the registration unit 142 may control the UI unit 147 to accept the input of the blockchain address by the user. The registration unit 142 may then acquire the input blockchain address from the UI unit 147. The registration unit 142 may then supply the acquired blockchain address to the storage unit 146 to store (register) the blockchain address.

[0093] The imaging control unit 143 performs processing related to the control of the imaging unit 148 and the depth information generating unit 149. That is, the imaging control unit 143 may also be referred to as a content information generating unit, a captured image generating unit, a depth information generating unit, etc. For example, the imaging control unit 143 may supply information related to imaging to the UI unit 147 to present the information. In addition, the imaging control unit 143 may cause the UI unit 147 (the input device included therein) to accept a user's instruction (operation) related to imaging. Then, the imaging control unit 143 may acquire information indicating the user's instruction (operation) received through the UI unit 147.

[0094] In addition, the imaging control unit 143 may control the imaging unit 148 to capture an image of the subject and generate a captured image according to the instruction (i.e., the user's operation). Then, the imaging control unit 143 may acquire the captured image. Then, the imaging control unit 143 may supply the captured image to the image file generation unit 144.

[0095] In addition, the imaging control unit 143 may control the depth information generation unit 149 according to the instruction (i.e., the user's operation) to generate depth information corresponding to the captured image generated in the imaging unit 148. Then, the imaging control unit 143 may acquire the depth information. Then, the imaging control unit 143 may supply the depth information to the image file generation unit 144.

[0096] The image file generation unit 144 performs processing related to the generation of an image file that stores the captured image. That is, the image file generation unit 144 may also be referred to as a content information file generation unit. For example, the image file generation unit 144 may obtain the captured image supplied from the imaging control unit 143. In addition, the image file generation unit 144 may obtain the depth information supplied from the imaging control unit 143. In addition, the image file generation unit 144 may obtain the blockchain address from the storage unit 146. In addition, the image file generation unit 144 may obtain the camera private key from the storage unit 146. The camera private key is a private key unique to the imaging device 102. In addition, the image file generation unit 144 may obtain a camera certificate from the storage unit 146. The camera certificate is a certificate for the camera private key. The camera public key may be included in the camera certificate. The camera public key is a public key corresponding to the camera private key.

[0097] For example, the image file generation unit 144 may generate an image file and save the captured image acquired from the imaging control unit 143 in the image file. In addition, the image file generation unit 144 may save the blockchain address acquired from the storage unit 146 in the image file. That is, the image file generation unit 144 may assign the blockchain address to the captured image as metadata. In addition, the image file generation unit 144 may save the depth information acquired from the imaging control unit 143 in the image file. That is, the image file generation unit 144 may attach the depth information to the captured image as metadata.

[0098] In addition, the image file generation unit 144 can use the captured image, blockchain address, depth information and camera private key to generate a camera electronic signature. The camera electronic signature is an electronic signature used to verify the captured image (and its metadata) stored in the image file. The camera electronic signature can be obtained by hashing the captured image or metadata (such as blockchain address, depth information, etc.) and encrypting the hashed captured image or metadata with the camera private key. Then, the image file generation unit 144 can save the generated camera electronic signature in the image file. That is, the image file generation unit 144 can attach the camera electronic signature to the captured image. In addition, the image file generation unit 144 can save the camera certificate in the image file. That is, the image file generation unit 144 can give the camera certificate to the captured image.

[0099] The image file generation unit 144 may supply the generated image file to the upload unit 145. In addition, the image file generation unit 144 may supply the generated image file to the storage unit 146 for storage.

[0100] The upload unit 145 performs processing related to uploading of image files. For example, the upload unit 145 can obtain the image file supplied from the image file generation unit 144. In addition, the upload unit 145 can supply (upload) the image file to the verification server 103 via the communication unit 141. With this upload, the upload unit 145 requests verification of the image file (captured image, etc.) (and the subsequent issuance of NFT). That is, the upload unit 145 can also be referred to as a request unit.

[0101] The storage unit 146 includes any storage medium such as a hard disk or a semiconductor memory, and performs processing related to the storage and reading of any information. For example, the storage unit 146 can pre-store a camera private key and a camera certificate. Note that "pre-" means at least before the information is used. That is, the storage unit 146 can store this information, for example, at the time of shipment or after shipment. Note that the camera private key is a private key unique to the imaging device 102. The camera certificate is a certificate for the camera private key. The camera certificate may contain a camera public key. The camera public key is a public key corresponding to the camera private key.

[0102] In addition, the storage unit 146 may acquire and store (register) the blockchain address supplied from the registration unit 142 .

[0103] In addition, the storage unit 146 may supply the camera private key to the image file generation unit 144 in response to a request from the image file generation unit 144. In addition, the storage unit 146 may supply the camera certificate to the image file generation unit 144 in response to a request from the image file generation unit 144. In addition, the storage unit 146 may supply the blockchain address to the image file generation unit 144 in response to a request from the image file generation unit 144.

[0104] In addition, the storage unit 146 may acquire and store the image file supplied from the image file generation unit 144 .

[0105] The UI unit 147 performs processing related to the user interface. For example, the UI unit 147 includes an output device that outputs images and audio. The output device can be any device, and can include, for example, a display that displays images, text information, etc. The display can be any device, for example, a liquid crystal display (LCD), an organic electroluminescent display (OELD), a projector, or a device other than these. In addition, the output device can include, for example, a speaker that outputs audio. The number of output devices included in the UI unit 147 is arbitrary. In addition, the UI unit 147 includes an input device that accepts user operations. The input device can be any device, and can include, for example, a touch panel, a switch, a keyboard, a mouse, an image sensor, a microphone, etc. The number of input devices included in the UI unit 147 is arbitrary.

[0106] The UI unit 147 is driven under the control of the registration unit 142 or the imaging control unit 143. For example, the UI unit 147 can present information to the user via an output device. That is, the UI unit 147 can also be referred to as an output unit, a presentation unit, etc. In addition, the UI unit 147 can accept the user's instructions (operations) via an input device. In addition, the UI unit 147 can supply information representing the received user's instructions (operations) to the request source (registration unit 142 or imaging control unit 143). That is, the UI unit 147 can also be referred to as an input unit. For example, the UI unit 147 can accept the user's instructions (operations) related to the registration of the blockchain address via an input device, and supply information representing the instructions (operations) to the registration unit 142. In addition, the UI unit 147 can accept the user's instructions (operations) related to imaging via an input device, and supply information representing the instructions (operations) to the imaging control unit 143. In addition, the UI unit 147 can accept the user's instructions (operations) related to the generation of depth information via an input device, and supply information representing the instructions (operations) to the imaging control unit 143.

[0107] The imaging unit 148 includes an optical system such as a lens, an aperture, and an image sensor, and uses the optical system and the image sensor to perform processing related to capturing an image of a subject. For example, the imaging unit 148 can be driven under the control of the imaging control unit 143. The control is performed according to the user's instructions (user's operation). In addition, the imaging unit 148 can be manually operated by the user. That is, the imaging unit 148 is driven according to the operation of the user (image contributor). For example, the imaging unit 148 can drive the optical system or the image sensor to capture an image of a subject and generate the captured image. That is, the imaging unit 148 can also be referred to as a content information generation unit, a captured image generation unit, etc. In addition, the imaging unit 148 can supply the generated captured image to the imaging control unit 143.

[0108] The depth information generating unit 149 includes a sensor (also referred to as a depth sensor) that detects the distance (depth value) of the subject, and uses the depth sensor to perform processing related to the generation of depth information. For example, the depth information generating unit 149 can be driven under the control of the imaging control unit 143. This control can be performed according to the user's instructions (user's operation). For example, the depth information generating unit 149 can drive the depth sensor to detect the depth value of the subject and generate depth information. In addition, the depth information generating unit 149 can supply the generated depth information to the imaging control unit 143.

[0109] The depth information may be any information as long as it includes a depth value. For example, similar to a captured image, the depth information may have a pixel array structure including a plurality of pixels. In this case, each pixel value of the depth information represents a distance (depth value) to the subject. In addition, the depth information may include a depth value of a predetermined representative position of the subject in the captured image.

[0110] Note that the depth information generation unit 149 can generate depth information corresponding to the captured image generated by the imaging unit 148. For example, the depth information generation unit 149 can detect the depth value of the subject imaged by the imaging unit 148 at approximately the same timing as the imaging performed by the imaging unit 148 to generate depth information. Here, "approximately the same timing" means a timing that is close to the extent that it is difficult to replace the subject between the imaging and the detection of the depth value, or the same timing. That is, the "depth information corresponding to the captured image" means information that can specify the position in the depth direction for each part of the subject in the captured image. In other words, the "depth information corresponding to the captured image" means information that can identify the three-dimensional shape of the subject in the captured image. That is, the depth information generation unit 149 can also be called a content information generation unit.

[0111] In the imaging device 102 having such a structure, for example, the imaging unit 148 generates a captured image according to the user's operation, and the image file generation unit 144 generates an image file that stores the captured image and the blockchain address corresponding to the user. Thus, the verification server 103 can verify whether the image contributor is the same as the issuer of the NFT (the person who requested the NFT issuance) based on the blockchain address. Thus, the verification server 103 can verify the authenticity of the image contributor (the creator of the content information) of the captured image to be NFTized.

[0112] In addition, the image file generation unit 144 saves the electronic signature corresponding to the captured image and the blockchain address in the image file. Thus, the verification server 103 can verify whether the captured image to be NFT-ized has been tampered with. Therefore, the verification server 103 can verify the authenticity of the captured image to be NFT-ized.

[0113] In addition, the image file generation unit 144 saves the camera certificate in the image file. Thus, the verification server 103 can use the information of the image file to verify whether the captured image to be NFTed has been tampered with. Therefore, the verification server 103 can more easily verify the authenticity of the captured image to be NFTed.

[0114] In addition, the depth information generation unit 149 generates depth information corresponding to the captured image, and the image file generation unit 144 saves the depth information in the image file. Thus, the verification server 103 can use the depth information to verify whether the captured image is legal and valid. Therefore, the verification server 103 can verify the authenticity of the captured image to be NFTized.

[0115] In addition, the upload unit 145 sends the image file to the verification server 103 to request verification of the captured image, etc. and to issue an NFT corresponding to the captured image. Thus, the verification server 103 can verify the captured image, and the smart contract 104 can issue an NFT corresponding to the captured image verified by the verification server 103. Thus, the verification server 103 can verify the authenticity of the captured image to be NFTized.

[0116] <Authentication Server> Figure 4 1 is a block diagram showing a main configuration example of the verification server 103 as one aspect of the information processing device to which the present technology is applied. Figure 4 The main processing units, data flows, etc. are shown in FIG. Figure 4 That is, the verification server 103 may include Figure 4 In addition, there may be devices or processing units not shown in FIG. Figure 4 The data flow or processing is shown by arrows etc.

[0117] The verification server 103 may be implemented in any structure. For example, the verification server 103 may be configured as hardware or software. For example, the verification server 103 may be configured by a single computer or multiple computers. In addition, the verification server 103 may be configured as a virtual computer. In addition, the verification server 103 may be configured as a so-called cloud server.

[0118] like Figure 4 As shown, the verification server 103 includes a communication unit 161 , a verification unit 162 , a request unit 163 and a storage unit 164 .

[0119] The communication unit 161 performs processing related to communication with other devices. For example, the communication unit 161 can communicate with the user terminal device 101, the imaging device 102, or the smart contract 104 via the network 110. For example, the communication unit 161 can obtain information supplied from other devices by using the communication, and supply the information to the verification unit 162 and the request unit 163. In addition, the communication unit 161 can obtain information supplied from the verification unit 162 or the request unit 163, and supply the information to other devices through the communication.

[0120] The verification unit 162 performs processing related to verification of a captured image, etc. For example, the verification unit 162 may acquire an image file transmitted from the imaging device 102 via the communication unit 161. That is, the verification unit 162 may acquire a request to verify the image file.

[0121] In addition, the verification unit 162 can verify the acquired image file in response to the request. For example, the verification unit 162 can verify whether the camera certificate contained in the image file is legal and valid. The verification method is arbitrary. For example, the verification unit 162 can verify whether the camera certificate is legal and valid by asking a certification authority that has registered information on the camera private key and the camera public key.

[0122] In addition, if the camera certificate is determined to be valid, the verification unit 162 can use the camera certificate and the camera electronic signature stored in the image file to verify whether the captured image and metadata have been tampered with. For example, the verification unit 162 can perform the verification by comparing the hashed image and metadata with the camera electronic signature decrypted with the camera public key.

[0123] In addition, when it is determined that the captured image and metadata have not been tampered with, the verification unit 162 may verify whether the captured image has been forged by using the depth information stored in the image file.

[0124] In addition, the verification unit 162 may supply information indicating the verification result as above to the storage unit 164 and store the information.

[0125] The request unit 163 performs processing related to the request for issuing the NFT. The request unit 163 has an NFT wallet function. For example, the request unit 163 can obtain information indicating the verification result of the verification unit 162 from the storage unit 164, and perform processing based on the verification result. In addition, the request unit 163 can obtain the signature private key from the storage unit 164. The signature private key is a private key unique to the verification server 103. In addition, the request unit 163 can obtain the server wallet private key from the storage unit 164.

[0126] For example, the request unit 163 may generate an NFT issuance transaction executed by itself. An NFT issuance transaction is a transaction requesting the issuance of an NFT and includes information required to issue the NFT. For example, the request unit 163 may generate an NFT issuance transaction by using a metadata URL and a blockchain address. The metadata URL is an address indicating the storage destination of the image file to be NFTized.

[0127] Then, the request unit 163 can execute the generated NFT issuance transaction using the server wallet private key. With this process, the information required for issuing the NFT is supplied to the smart contract 104 via the communication unit 121, and the issuance of the NFT is requested.

[0128] Note that the request unit 163 can verify whether the blockchain address stored in the NFTized image file matches the blockchain address of the user of the imaging device 102. Then, the request unit 163 can generate the above-mentioned NFT issuance transaction when the image contributor is confirmed to be legal and valid. Here, the blockchain address stored in the image file represents the creator of the content information (the image contributor who took the image). That is, through this verification, the request unit 163 is able to confirm whether the image contributor is legal and valid. Note that the blockchain address of the user of the imaging device 102 can be provided from the imaging device 102 to the verification server 103 together with the image file, or can be provided from the imaging device 102 to the verification server 103 in advance.

[0129] In addition, the request unit 163 may generate an NFT issuance transaction to be executed by other devices. For example, the request unit 163 may generate an NFT issuance transaction to be executed by the user terminal device 101. Then, the request unit 163 may send the generated NFT issuance transaction to the user terminal device 101 via the communication unit 161.

[0130] In this case, the request unit 163 can, for example, generate an NFT issuance transaction by using the above-mentioned metadata URL and blockchain address and an electronic signature (also called a cloud electronic signature). The cloud electronic signature is an electronic signature used to verify the tampering of the above-mentioned metadata URL and blockchain address. For example, the request unit 163 can generate the cloud electronic signature by using the above-mentioned metadata URL, blockchain address and signature private key. For example, the request unit 163 can generate a cloud electronic signature by hashing the image file and blockchain address corresponding to the above-mentioned metadata URL and encrypting it with the signature private key.

[0131] The storage unit 164 includes any storage medium such as a hard disk or a semiconductor memory, and performs processing related to the storage and reading of any information. For example, the storage unit 164 can pre-store a signature private key, a signature certificate, and a server wallet private key. The signature certificate is a certificate for a signature private key. The signature certificate may contain a public key (also referred to as a signature public key) corresponding to the signature private key. The signature certificate may be pre-registered in the smart contract 104. Note that "pre" means at least before the information is used. That is, the storage unit 164 can store this information, for example, at the time of shipment or after shipment. In addition, the storage unit 164 can store information representing the verification result supplied from the verification unit 162.

[0132] In addition, the storage unit 164 may read the signature private key, the signature certificate, or the server wallet private key in response to the request of the request unit 163, and supply the read information to the request unit 163. In addition, the storage unit 164 may read information indicating the verification result in response to the request from the request unit 163, and supply the information to the request unit 163.

[0133] In the verification server 103 having such a structure, for example, the verification unit 162 uses the camera electronic signature to verify whether the captured image has been tampered with, and if the result of the verification is that the captured image has not been tampered with, the request unit 163 requests the issuance of an NFT corresponding to the captured image. Thus, the verification server 103 can prove that the captured image to be NFTized has not been tampered with. That is, the verification server 103 can verify the authenticity of the content information to be NFTized.

[0134] In addition, the verification unit 162 uses the camera electronic signature to verify whether the metadata of the captured image has been tampered with. Thus, the verification server 103 can prove that the metadata of the captured image to be NFTed has not been tampered with. That is, the verification server 103 can verify the authenticity of the metadata of the content information to be NFTed.

[0135] In addition, the verification unit 162 uses the depth information corresponding to the captured image to verify whether the captured image is legal and valid. Thus, the verification server 103 can verify whether the captured image to be NFTized is forged. In other words, the verification server 103 can verify the authenticity of the content information to be NFTized.

[0136] In addition, the request unit 163 generates an NFT issuance transaction for requesting the issuance of an NFT. Thus, the verification server 103 can implement the request for the issuance of an NFT to the smart contract 104.

[0137] In addition, the request unit 163 executes the NFT issuance transaction. Thus, the verification server 103 can request the smart contract 104 to issue the NFT.

[0138] In addition, the request unit 163 supplies the NFT issuance transaction to the user terminal device 101 that requests the issuance of the NFT. Thus, the verification server 103 can cause the user terminal device 101 to request the issuance of the NFT.

[0139] <Smart Contract> Figure 5 This is a block diagram showing a main structural example of a smart contract 104 as one aspect of an information processing device to which the present technology is applied. Note that Figure 5 The main processing units, data flows, etc. are shown in FIG. Figure 5 That is, the smart contract 104 may include Figure 5 In addition, there may be devices or processing units not shown in FIG. Figure 5 The data flow or processing is shown by arrows etc.

[0140] Smart contract 104 can be implemented by any structure. For example, smart contract 104 can be configured as hardware or software. For example, smart contract 104 can include a single computer or multiple computers. In addition, smart contract 104 can be configured as a virtual computer. In addition, smart contract 104 can be configured as a so-called cloud server.

[0141] like Figure 5 As shown, the smart contract 104 includes a communication unit 181, an NFT issuance unit 182 and a storage unit 183.

[0142] The communication unit 181 performs processing related to communication with other devices. For example, the communication unit 181 can communicate with the user terminal device 101, the imaging device 102, or the verification server 103 via the network 110. For example, the communication unit 181 can obtain information supplied from other devices through the communication, and supply the information to the NFT issuing unit 182. In addition, the communication unit 181 can obtain information supplied from the NFT issuing unit 182, and supply the information to other devices through the communication.

[0143] The NFT issuing unit 182 performs processing related to the issuance of the NFT. That is, the NFT issuing unit 182 may also be referred to as an issuing unit. For example, the NFT issuing unit 182 may obtain a request for issuing the NFT from the verification server 103 via the communication unit 181. That is, the NFT issuing unit 182 may obtain information required for issuing the NFT (e.g., metadata URL, blockchain address, etc.) from the verification server 103 that has executed the NFT issuance transaction.

[0144] In addition, the NFT issuance unit 182 can verify whether the executor of the NFT issuance transaction is the verification server 103. The executor of the NFT issuance transaction is the requester (issuer) of the NFT issuance. That is, the NFT issuance unit 182 can verify whether the issuer is the verification server 103 that has verified the captured image, etc. The verification server 103 can verify whether the image contributor is legal and valid. In other words, by performing this verification, the NFT issuance unit 182 can confirm whether the issuer is legal and valid (whether the issuer is a legal and valid image contributor (creator of the content information)). Therefore, the smart contract 104 can prove the authenticity of the issuer of the NFT.

[0145] In addition, the NFT issuance unit 182 can obtain a request for NFT issuance from the user terminal device 101 via the communication unit 181. That is, the NFT issuance unit 182 can obtain the information required for issuing the NFT (e.g., metadata URL, blockchain address, cloud electronic signature, etc.) from the user terminal device 101 that has executed the NFT issuance transaction.

[0146] In addition, the NFT issuing unit 182 can obtain the signature certificate from the storage unit 183. Then, the NFT issuing unit 182 can use the cloud electronic signature and the signature certificate to verify whether the metadata URL, blockchain address, etc. have been tampered with. For example, the NFT issuing unit 182 can compare the result of hashing the image file and blockchain address corresponding to the metadata URL with the result of decrypting the cloud electronic signature with the signature public key (the public key corresponding to the signature private key) contained in the signature certificate. By performing this verification, the NFT issuing unit 182 can confirm whether the image file and blockchain address have been tampered with. Therefore, the smart contract 104 can prove the authenticity of the content information that has been NFTized.

[0147] In addition, the NFT issuance unit 182 can verify whether the executor of the NFT issuance transaction (user of the user terminal device 101 (the user)) corresponds to the blockchain address included in the NFT issuance transaction. The NFT issuance transaction contains the blockchain address of the image contributor (creator of the content information). Therefore, by performing this verification, the NFT issuance unit 182 can confirm whether the issuer is legal and valid (whether the issuer is a legal and valid image contributor (creator of the content information)). Therefore, the smart contract 104 can prove the authenticity of the issuer of the NFT.

[0148] In addition, the NFT issuing unit 182 can issue an NFT token ID using the information obtained as described above. That is, the NFT issuing unit 182 can issue an NFT corresponding to the content information verified by the verification server 103, and the NFT is requested from the verification server 103 or the user terminal device 101.

[0149] In addition, the NFT issuing unit 182 can supply a metadata URL indicating the storage location of the captured image to be NFTized to the storage unit 183 and store the metadata URL. In addition, the NFT issuing unit 182 can supply the issued NFT token ID to the storage unit 183 and store the NFT token ID.

[0150] The storage unit 183 includes any storage medium such as a hard disk or a semiconductor memory, and performs processing related to the storage and reading of any information. For example, the storage unit 183 can pre-store a private key unique to the smart contract 104 (also referred to as a smart contract private key), a public key corresponding to the smart contract private key (also referred to as a smart contract public key), and a signature certificate. The signature certificate is a certificate corresponding to the signature private key used by the verification server 103, including a signature public key corresponding to the signature private key. The signature certificate can be pre-supplied from the verification server 103. For example, the verification server 103 can pre-execute a transaction for registering a signature certificate, and the smart contract 104 can be registered after confirming whether the executor of the transaction is an account of the verification server 103. Note that "pre-" means at least before the information is used. That is, the storage unit 183 can store this information, for example, at the time of shipment or after shipment.

[0151] In addition, the storage unit 183 can read the signature certificate in response to a request from the NFT issuing unit 182 and supply the signature certificate to the NFT issuing unit 182 .

[0152] In addition, the storage unit 183 may store the metadata URL supplied from the NFT issuing unit 182. In addition, the storage unit 183 may store the NFT token ID supplied from the NFT issuing unit 182.

[0153] With this structure, the smart contract 104 can issue an NFT corresponding to an image file whose authenticity has been verified, such as a captured image, metadata, etc. As a result, the authenticity of the content information to be NFTized can be proven.

[0154] <Image Processing Flow> Next, refer to Figure 6 The flowchart illustrates an example of the flow of image processing performed by the image processing system 100 as described above.

[0155] When image processing is started, in step S101 , the user terminal device 101 and the imaging device 102 perform a registration process of registering a blockchain address.

[0156] In step S102 , the imaging device 102 performs an imaging process of capturing a subject and generating an image file.

[0157] In step S103 , the imaging device 102 and the verification server 103 perform verification processing to verify the authenticity of the information stored in the image file.

[0158] In step S104, the verification server 103 and the smart contract 104, or the user terminal device 101, the verification server 103 and the smart contract 104 execute the NFT issuance processing to issue the NFT corresponding to the verified image file.

[0159] When the process of step S104 ends, the image processing ends.

[0160] <Registration Process> Next, refer to Figure 7 The flowchart is described in Figure 6 An example of the flow of the registration process performed in step S101 of FIG.

[0161] When the registration process starts, in step S121, the registration processing unit 122 of the user terminal device 101 controls the communication unit 121 to start a near field communication session with the imaging device 102. The communication unit 121 performs near field communication with the imaging device 102 and starts the session according to the control. On the other hand, in step S131, the registration unit 142 of the imaging device 102 controls the communication unit 141 to start a near field communication session with the user terminal device 101. The communication unit 141 performs near field communication with the user terminal device 101 and starts the session according to the control.

[0162] When the session starts, in step S122, the registration processing unit 122 of the user terminal device 101 reads and acquires the blockchain address of the user from the storage unit 124. In addition, the registration processing unit 122 supplies the blockchain address to the imaging device 102 via the communication unit 121.

[0163] In step S132 , the registration unit 142 of the imaging device 102 acquires the blockchain address transmitted from the user terminal device 101 through the near field communication via the communication unit 141 .

[0164] In step S133, the registration unit 142 controls the UI unit 147 to display a registration confirmation screen or the like on the display to confirm to the user whether to register the blockchain address.

[0165] Figure 8 is a diagram showing an example of a registration confirmation screen. Figure 8 In the case of the example of , the registration confirmation screen 210 displays a message “Do you want to register the following blockchain address received from the external device?”, its blockchain address (in Figure 8In the case of the example of , it is "0xABABABABABABABABABABABAB"), a registration button 211 and a cancel button 212. The registration button 211 is a graphical user interface (GUI) to which an instruction to register the displayed blockchain address (registration cancellation instruction) is input through the user's operation. The cancel button 212 is a GUI to which an instruction to cancel the registration of the blockchain address (registration termination instruction) is input through the user's operation. The user who sees the above message operates the input device to press the registration button 211 or the cancel button 212. When the registration button 211 is pressed, the registration process continues, and the following process is performed. In addition, when the cancel button 212 is pressed, the registration process ends.

[0166] In a case where the registration button 211 is pressed and registration of a blockchain address is permitted, in step S134 , the registration unit 142 registers the blockchain address acquired from the user terminal device 101 (the blockchain address displayed on the registration confirmation screen 210 ).

[0167] When the process of step S134 ends, the registration process ends.

[0168] <Flow of Imaging Processing> Next, refer to Fig. 9 The flowchart is described in Figure 6 An example of the flow of the imaging process performed in step S102 of FIG.

[0169] When the imaging process starts, in step S151, the imaging control unit 143 of the imaging device 102 controls the imaging unit 148 to capture an image of the subject and generate a captured image based on the user's instruction accepted by the UI unit 147. The imaging unit 148 captures an image of the subject and generates a captured image according to the control. The imaging unit 148 supplies the generated captured image to the imaging control unit 143.

[0170] In step S152, the imaging control unit 143 controls the depth information generation unit 149 to generate depth information corresponding to the captured image. According to this control, the depth information generation unit 149 detects the depth value of the subject of the captured image and generates depth information. The depth information generation unit 149 supplies the generated depth information to the imaging control unit 143. Note that this processing is performed at substantially the same timing as the processing of step S151.

[0171] In step S153 , the image file generation unit 144 acquires the captured image from the imaging control unit 143 , and generates an image file storing the captured image.

[0172] In step S154, the image file generation unit 144 obtains the blockchain address from the storage unit 146 and stores the blockchain address in the image file. That is, the image file generation unit 144 attaches the blockchain address as metadata to the captured image.

[0173] In step S155, the image file generation unit 144 acquires the depth information from the imaging control unit 143 and saves the depth information in the image file. That is, the image file generation unit 144 adds the depth information to the captured image as metadata.

[0174] In step S156, the image file generation unit 144 obtains the camera private key from the storage unit 146. The image file generation unit 144 generates a camera electronic signature using the captured image, its metadata, and the camera private key. For example, the image file generation unit 144 generates the camera electronic signature by hashing the captured image and metadata and encrypting them with the camera private key. The image file generation unit 144 saves the generated camera electronic signature in the image file. That is, the image file generation unit 144 attaches the camera electronic signature to the captured image.

[0175] In step S157, the image file generation unit 144 acquires the camera certificate from the storage unit 146 and stores the camera certificate in the image file. That is, the image file generation unit 144 adds the camera electronic signature to the captured image.

[0176] When the processing of step S157 ends, the imaging processing ends.

[0177] Fig.10 1 is a diagram showing a main configuration example of an image file generated in the imaging device 102. The image file generating unit 144 generates an image file having Fig.10 The image file 230 of the structure shown. Fig.10 As shown, the image file 230 stores a captured image 231, a blockchain address 232, depth information 233, a camera electronic signature 234, and a camera certificate 235. Note that the blockchain address 232 and the depth information 233 may not be attached. In other words, the blockchain address 232 may not be stored in the image file 230. Similarly, the depth information 233 may not be stored in the image file 230. Of course, information other than these may be stored in the image file 230.

[0178] <Verification Process Flow> Next, refer to Fig.11 The flowchart is used to illustrate the Figure 6 An example of the flow of the verification process performed in step S103 of FIG.

[0179] When the authentication process starts, in step S171, the upload unit 145 of the imaging device 102 transmits (uploads) the image file generated by the image file generation unit 144 to the authentication server 103 via the communication unit 141. In step S181, the authentication unit 162 of the authentication server 103 acquires the image file via the communication unit 161.

[0180] In step S182, the verification unit 162 verifies whether the camera certificate stored in the image file is legal and valid by querying a certification authority that has registered information on the camera private key and the camera public key. If it is determined that the camera certificate is invalid, the verification process ends.

[0181] If the camera certificate is determined to be valid, in step S183, the verification unit 162 uses the camera certificate and camera electronic signature stored in the image file to verify whether the captured image and metadata stored in the image file have been tampered with. If it is determined that the captured image and metadata have been tampered with, the verification process ends.

[0182] When it is determined that the captured image and metadata have not been tampered with, in step S184 , the verification unit 162 uses the depth information to verify whether the captured image has been forged.

[0183] When the process of step S184 is completed, the verification unit 162 supplies information indicating the verification result to the storage unit 164 and stores the information. Then, the verification process ends.

[0184] Note that either the process of step S182 or the process of step S183 may be performed first.

[0185] Fig.12 1 is a diagram showing an example of the state of the processing of step S184, that is, verification of the captured image using the depth information. For example, it is assumed that the captured image 241 is generated in the imaging unit 148, and the depth information 242 is generated in the depth information generating unit 149. The depth information 242 is information corresponding to the captured image 241. In the depth information 242, each polygon represents a depth value. The smaller the number of angles, the farther the subject of the area represented by each polygon is from the imaging device 102 (depth information generating unit 149). In other words, the larger the number of angles, the closer the subject of the area represented by each polygon is to the imaging device 102 (depth information generating unit 149). Although the resolution of the depth information 242 is arbitrary, if the amount of data is not considered, it is better to have a higher resolution (for example, the same resolution as the captured image 241).

[0186] Note that the optical axis of the optical image for obtaining the captured image 241 and the optical axis of the optical image for obtaining the depth information 242 can be the same. The optical axis refers to the chief ray that passes through the center of the light flux passing through the entire system in the optical system. For example, the captured image 241 and the depth information 242 can be obtained from one optical image. Additionally, one optical image can be divided into two optical images (identical optical images) by using a beam splitter (half mirror) such as a prism, etc. The captured image 241 can be obtained from one optical image, and the depth information 242 can be obtained from the other optical image. That is, for example, the imaging unit 148 and the depth information generation unit 149 can share part or all of one optical system.

[0187] As described above, since the optical axis of the optical image for obtaining the captured image 241 is the same as the optical axis of the optical image for obtaining the depth information 242, it is possible to obtain depth information 242 of the subject within the range (field of view angle) of the scene included in the captured image 241 from the subject at the same angle as the captured image 241. Note that the range of the depth information 242 obtained from the optical image is arbitrary. For example, the range of this depth information 242 can be the same as the field of view angle of the captured image 241, or can be a range including part or all of the field of view angle. For example, the depth information 242 can include depth values obtained from the same angle as the captured image 241 at multiple positions within the field of view angle of the captured image 241.

[0188] Since the captured image 241 corresponds to the depth information 242, when the captured image 241 is obtained by legally and effectively photographing an actual three-dimensional object, as shown in the superimposed image 243, the uneven state of the object represented by the depth information 242 corresponds to the three-dimensional shape of the object estimated from the captured image 241 in the real space. However, when the captured image 241 is forged, the two may not match each other. For example, when the captured image 241 is a captured image (2D image) of a three-dimensional subject, the subject is represented as a plane in the depth information 242. However, since a three-dimensional shaped subject is estimated from the captured image 241, it does not match the depth information. In this way, the verification unit 162 can verify whether the captured image is forged by using the depth information.

[0189] <Process flow of NFT issuance processing> Next, with reference to Fig.13 the flowchart, an example of the process flow of NFT issuance processing executed in Figure 6 step S104 is described. As described above, the NFT issuance request can be executed by the verification server 103, or can be executed by something other than the verification server 103 (for example, the user terminal device 101). In Fig.13An example in which the authentication server 103 makes a request is described in FIG.

[0190] When the NFT issuance process starts, in step S201, the request unit 163 of the verification server 103 checks the blockchain address. Fig.11 In the case where it is determined in step S184 that the captured image is legal and valid, the request unit 163 verifies whether the blockchain address stored in the image file to be NFTized matches the blockchain address of the user of the imaging device 102. Here, the blockchain address stored in the image file represents the creator of the content information (the image contributor of the captured image). That is, through this verification, the request unit 163 is able to confirm whether the image contributor is legal and valid. Note that the blockchain address of the user of the imaging device 102 can be provided from the imaging device 102 to the verification server 103 together with the image file, or can be provided from the imaging device 102 to the verification server 103 in advance.

[0191] If it is determined that the blockchain address does not match and the NFT issuer is different from the image contributor, the NFT issuance process ends. In addition, if the blockchain address matches and the image contributor is confirmed to be legitimate and valid, the process proceeds to step S202.

[0192] In step S202, the request unit 163 generates an NFT issuance transaction, which includes a metadata URL indicating the storage destination of the image file (that is, the image file) and a blockchain address indicating the issuer of the NFT. The NFT issuance transaction is a transaction requesting the issuance of an NFT, and includes information required to issue an NFT corresponding to the image file.

[0193] When an NFT issuance transaction is generated, in step S203, the request unit 163 obtains the server wallet private key from the storage unit 164. The request unit 163 uses the server wallet private key to perform the NFT issuance transaction. With this process, the information required to issue the NFT is supplied to the smart contract 104 via the communication unit 161. That is, the issuance of the NFT is requested from the smart contract 104.

[0194] In step S211, the NFT issuing unit 182 of the smart contract 104 obtains the request. That is, the NFT issuing unit 182 obtains the information required to issue the NFT (for example, metadata URL, blockchain address, etc.) from the verification server 103.

[0195] In step S212, the NFT issuance unit 182 verifies the executor of the transaction. That is, the NFT issuance unit 182 verifies whether the executor of the NFT issuance transaction is the verification server 103. The executor of the NFT issuance transaction is the requester (issuer) of the NFT issuance. That is, the NFT issuance unit 182 verifies whether the issuer is the verification server 103 that has verified the captured image, etc. The verification server 103 can verify whether the image contributor is legal and valid. That is, by performing this verification, the NFT issuance unit 182 can confirm whether the issuer is legal and valid (whether the issuer is a legal and valid image contributor (creator of content information)). Therefore, the smart contract 104 can prove the authenticity of the issuer of the NFT.

[0196] If these blockchain addresses do not match and the issuer is determined to be invalid, the NFT issuance process ends. In addition, if it is determined that these blockchain addresses match and the issuer is legal and valid, the process proceeds to step S213.

[0197] In step S213 , the NFT issuing unit 182 issues the NFT token ID requested from the verification server 103 and corresponding to the content information verified by the verification server 103 , by using the acquired information.

[0198] When the processing of step S213 is completed, the NFT issuance processing is completed.

[0199] Next, refer to Fig.14 The flowchart illustrates an example of the flow of NFT issuance processing when the user terminal device 101 makes a request for issuance of an NFT.

[0200] When the NFT issuance process starts, in step S241, the request unit 163 of the verification server 103 generates a cloud electronic signature using the metadata URL, the blockchain address, and the signature private key. For example, the request unit 163 can generate a cloud electronic signature by hashing the image file and the blockchain address corresponding to the metadata URL and encrypting them with the signature private key.

[0201] In step S242, the request unit 163 generates an NFT issuance transaction including a metadata URL, a blockchain address, and a cloud electronic signature. The NFT issuance transaction is a transaction requesting the issuance of an NFT, and includes information required to issue the NFT.

[0202] In step S243 , the request unit 163 sends the generated NFT issuance transaction to the user terminal device 101 via the communication unit 161 .

[0203] In step S231 , the request unit 123 of the user terminal device 101 obtains the NFT issuance transaction via the communication unit 121 .

[0204] In step S232, the request unit 123 obtains the user wallet private key from the storage unit 124. The request unit 123 uses the user wallet private key to perform the NFT issuance transaction. With this process, the information required to issue the NFT is supplied to the smart contract 104 via the communication unit 121. That is, the issuance of the NFT is requested from the smart contract 104.

[0205] In step S251, the NFT issuing unit 182 of the smart contract 104 obtains the request. That is, the NFT issuing unit 182 obtains the information required to issue the NFT (for example, metadata URL, blockchain address, cloud electronic signature, etc.) from the user terminal device 101.

[0206] In step S252, the NFT issuing unit 182 obtains the signature certificate from the storage unit 183. The NFT issuing unit 182 uses the signature certificate and the cloud electronic signature to verify whether the captured image, blockchain address, etc. have been tampered with. For example, the NFT issuing unit 182 can compare the result of hashing the image file and blockchain address corresponding to the metadata URL with the result of decrypting the cloud electronic signature using the signature public key (the public key corresponding to the signature private key) contained in the signature certificate. By performing this verification, the NFT issuing unit 182 can confirm whether the image file and the blockchain address have been tampered with. Therefore, the smart contract 104 can prove the authenticity of the content information that has been NFTized.

[0207] If it is determined that the captured image, blockchain address, etc. have been tampered with, the NFT issuance process ends. In addition, if it is determined that the captured image and blockchain address have not been tampered with, the process proceeds to step S253.

[0208] In step S253, the NFT issuance unit 182 verifies whether the executor of the NFT issuance transaction (user of the user terminal device 101 (the user)) corresponds to the blockchain address included in the NFT issuance transaction. The NFT issuance transaction contains the blockchain address of the image contributor (creator of the content information). Therefore, by performing this verification, the NFT issuance unit 182 is able to confirm whether the issuer is legal and valid (whether the issuer is a legal and valid image contributor (creator of the content information)). Therefore, the smart contract 104 is able to prove the authenticity of the issuer of the NFT.

[0209] If it is determined that the blockchain address does not correspond to the transaction executor and the NFT issuer is invalid, the NFT issuance process ends. In addition, if it is determined that the blockchain address corresponds to the transaction executor and the NFT issuer is legal and valid, the process proceeds to step S254.

[0210] In step S254, the NFT issuance unit 182 issues an NFT token ID corresponding to the content information requested by the user terminal device 101 and verified by the verification server 103 by using the acquired information.

[0211] When the process of step S254 ends, the NFT issuance process ends.

[0212] By executing each process as described above, the smart contract 104 can issue an NFT corresponding to an image file whose authenticity such as a captured image and metadata has been verified. As a result, the authenticity of the content information to be NFT - ized can be proven.

[0213] <4. Second Embodiment> <Verification after NFT Issuance> In the first embodiment, it has been described that an NFT is issued after verifying an image file, but it is also possible to verify an image file after issuing an NFT. For example, it is possible to verify an image file (information stored therein) that has been NFT - ized by a conventional system.

[0214] <User Terminal Device> Fig.15 A block diagram showing a main structural example of the user terminal device 101 in this case. In this case, in addition to Figure 2 the structure shown, the user terminal device 101 further includes a verification processing unit 311.

[0215] The verification processing unit 311 executes processing related to a request for verifying a captured image or the like that has been NFT - ized. For example, the verification processing unit 311 can request the verification server 103 to verify a captured image or the like that has been NFT - ized via the communication unit 121. At this time, the verification processing unit 311 can make an inquiry using the smart contract address and the NFT token ID. The smart contract address is the identification information of the smart contract 104. That is, in this case, the verification processing unit 311 specifies the content information to be verified by using the NFT token ID, and specifies the smart contract 104 that has issued an NFT for this content information by using the smart contract address.

[0216] In addition, the verification processing unit 311 can acquire information indicating a verification result supplied from the verification server 103 as a response to this request via the communication unit 121. In addition, the verification processing unit 311 can supply information indicating this verification result to the storage unit 124 and store this information.

[0217] In addition, in this case, the request unit 123 can generate an NFT issuance transaction including a metadata URL indicating the storage destination of the image file. The NFT issuance transaction is a transaction that requests the issuance of an NFT and includes the information required for issuing the NFT. In addition, the request unit 123 can execute the generated NFT issuance transaction by using its own wallet function to request the smart contract 104 to issue an NFT. With this process, the information required for issuing the NFT is supplied to the smart contract 104 via the communication unit 121.

[0218] <Flow of NFT Issuance Process> Refer to Fig.16 the flowchart in to illustrate an example of the flow of the NFT issuance process in this case. When the NFT issuance process starts, in step S301, the request unit 123 of the user terminal device 101 generates an NFT issuance transaction including a metadata URL indicating the storage destination of the image file.

[0219] In step S302, the request unit 123 obtains the user wallet private key from the storage unit 124. The request unit 123 executes the NFT issuance transaction by using the user wallet private key, thereby requesting the smart contract 104 to issue an NFT. With this process, the information required for issuing the NFT is supplied to the smart contract 104 via the communication unit 121.

[0220] In step S311, the NFT issuance unit 182 of the smart contract 104 obtains this request. That is, the NFT issuance unit 182 obtains the information required for issuing the NFT supplied from the user terminal device 101.

[0221] In step S312, the NFT issuance unit 182 issues an NFT token ID corresponding to the content information requested from the user terminal device 101 by using the obtained information.

[0222] When the process of step S312 ends, the NFT issuance process ends.

[0223] <Flow of Verification Process> Next, refer to Fig.17 the flowchart in to illustrate an example of the flow of the verification process in this case. In this case, a verification process is performed on the content information that has been NFT - ized.

[0224] When the verification process starts, in step S331, the verification processing unit 311 of the user terminal device 101 makes an inquiry (that is, requests verification) using the smart contract address and the NFT token ID. In step S341, the verification unit 162 of the verification server 103 obtains this request via the communication unit 161.

[0225] In step S342, the verification unit 162 requests the metadata URL corresponding to the NFT token ID (the storage destination address of the content information specified by the NFT token ID) from the smart contract 104 specified by the smart contract address. In step S351, the NFT issuing unit 182 of the smart contract 104 obtains the request via the communication unit 181.

[0226] In step S352, the NFT issuing unit 182 specifies the requested metadata URL and sends the metadata URL as a response to the request to the verification server 103 as the request source via the communication unit 181. In step S343, the verification unit 162 of the verification server 103 obtains the response (i.e., the metadata URL) via the communication unit 161.

[0227] In step S344 , the verification unit 162 acquires the image file from the acquired metadata URL.

[0228] In step S345, the verification unit 162 verifies whether the camera certificate stored in the image file is legal and valid by querying a certification authority in which information of the camera private key and the camera public key is registered. If it is determined that the camera certificate is invalid, the process proceeds to step S349.

[0229] If the camera certificate is determined to be valid, in step S346, the verification unit 162 uses the camera certificate and camera electronic signature stored in the image file to verify whether the captured image and metadata stored in the image file have been tampered with. If it is determined that the captured image and metadata have been tampered with, the process proceeds to step S349.

[0230] If it is determined that the captured image and metadata have not been tampered with, in step S347, the verification unit 162 uses the depth information to verify whether the captured image has been forged. If it is determined that the captured image has been forged, the process proceeds to step S349.

[0231] If it is determined that the captured image is properly generated, in step S348, the verification unit 162 verifies whether the blockchain address stored in the image file matches the blockchain address of the NFT issuer contained in the NFT token ID. The blockchain address of the image contributor (creator of the content information) is stored in the image file. In other words, it is verified whether the blockchain address of the NFT issuer contained in the NFT token ID matches the blockchain address of the user (image contributor) of the imaging device 102.

[0232] In step S349, the verification unit 162 sends information indicating the verification result of the authenticity of the captured image, etc., using the blockchain address and depth information of the NFT issuer to the user terminal device 101 via the communication unit 161. In step S332, the verification processing unit 311 of the user terminal device 101 obtains the verification result via the communication unit 121. The verification processing unit 311 stores the verification result in the storage unit 124.

[0233] When the processing of step S332 ends, the verification processing ends.

[0234] By executing each process as described above, it is possible to verify the image file after the NFT is issued. Therefore, for example, it is possible to verify (the information stored in) an image file that has been NFT-ified by a conventional system.

[0235] Note that either the process of step S345 or the process of step S346 may be performed first. Also, either the process of step S347 or the process of step S348 may be performed first.

[0236] <5. Third Embodiment> <Verification by smart contract> In the first and second embodiments, the verification server 103 verifies the content information. However, the smart contract 104 may verify the content information.

[0237] <Authentication Server> Fig.18 1 is a block diagram showing a main configuration example of the verification server 103 in this case. Fig.18 As shown, the verification server 103 in this case includes an issuance processing unit 411 instead of Figure 4 The verification unit 162 and the request unit 163.

[0238] The issuance processing unit 411 performs processing related to the issuance of the camera certificate and the issuance of the NFT. For example, the issuance processing unit 411 may request the smart contract 104 to issue a camera certificate via the communication unit 161. In addition, the issuance processing unit 411 may obtain the camera certificate sent from the smart contract 104 as a response to the request via the communication unit 161. In addition, the issuance processing unit 411 may send the obtained camera certificate to the imaging device 102 via the communication unit 161.

[0239] In addition, the issuance processing unit 411 can obtain the image file sent from the imaging device 102 via the communication unit 161. In addition, the issuance processing unit 411 can enable the user terminal device 101 to request the issuance of an NFT for the image file. For example, the issuance processing unit 411 can generate an NFT issuance transaction for requesting the issuance of an NFT for the image file. In addition, the issuance processing unit 411 can send the NFT issuance transaction to the user terminal device 101 via the communication unit 161. Of course, the issuance processing unit 411 can request the smart contract 104 to issue an NFT for the image file.

[0240] <Smart Contract> Fig.19 1 is a block diagram showing a main structural example of the smart contract 104 in this case. Fig.19 As shown, except Figure 5 In addition to the structure, the smart contract 104 in this case also has a camera certificate issuing unit 421 and a verification unit 422.

[0241] The camera certificate issuing unit 421 performs processing related to the issuance of the camera certificate. For example, the camera certificate issuing unit 421 can obtain a request for issuing a camera certificate sent from the verification server 103 via the communication unit 181. In addition, the camera certificate issuing unit 421 can obtain a smart contract private key from the storage unit 183. The smart contract private key is a private key unique to the smart contract 104. In addition, the camera certificate issuing unit 421 can use the smart contract private key to issue (generate) the requested camera certificate. That is, in this case, the camera certificate issuing unit 421 generates a camera certificate and encrypts the camera certificate with the smart contract private key. In addition, the camera certificate issuing unit 421 can send the camera certificate (encrypted camera certificate) to the verification server 103 of the request source via the communication unit 181.

[0242] The verification unit 422 performs processing related to verification of content information of the issued NFT, etc. For example, the verification unit 422 may obtain a request for issuing the NFT from the user terminal device 101 via the communication unit 181. In other words, the verification unit 422 may obtain information (image file, etc.) required for issuing the NFT, which is sent from the user terminal device 101 that has executed the NFT issuance transaction, via the communication unit 181. Of course, the request for issuing the NFT may be sent from the verification server 103.

[0243] In addition, the verification unit 422 can verify the image file for which the NFT is requested to be issued. For example, the verification unit 422 can obtain the smart contract public key from the storage unit 183. The smart contract public key is the public key corresponding to the smart contract private key. In addition, the verification unit 422 can use the smart contract public key to verify whether the camera certificate stored in the image file is legal and valid. For example, if the camera certificate is a legal and valid certificate issued by the camera certificate issuing unit 421, the camera certificate is encrypted with the smart contract private key. Therefore, the verification unit 422 can use the smart contract public key to decrypt the encrypted camera certificate, and if the decryption is successful (when a normal decryption result is obtained), it is determined that the camera certificate is legal and valid.

[0244] In addition, if the camera certificate is determined to be valid, the verification unit 422 can use the camera certificate and the camera electronic signature stored in the image file to verify whether the captured image and metadata have been tampered with. For example, the verification unit 422 can perform the verification by comparing the hashed image and metadata with the camera electronic signature decrypted using the camera public key.

[0245] In addition, if it is determined that the captured image and metadata have not been tampered with, the verification unit 422 can verify whether the captured image is forged by using the depth information stored in the image file. Fig.11 and Fig.12 The case where verification is performed by the verification server 103 has been described.

[0246] In addition, when it is determined that the captured image is legal and valid, the verification unit 422 can verify whether the blockchain address saved in the image file matches the blockchain address of the user who has executed the transaction (i.e., the user of the user terminal device 101). Here, the blockchain address saved in the image file represents the creator of the content information (the image contributor of the captured image). In addition, for the smart contract 104, the user of the user terminal device 101 is the issuer who requests the issuance of the NFT. Therefore, the verification unit 422 can verify whether the image contributor has made a request for the issuance of the NFT corresponding to the image file by comparing the blockchain address as described above. Note that in the case where the verification server 103 requests the issuance of the NFT, the verification unit 422 is only required to verify whether the blockchain address of the verification server 103 of the request source is legal and valid.

[0247] In addition, the verification unit 422 may supply the storage unit 164 with information indicating the result of the verification as described above and store the information.

[0248] In this case, the NFT issuing unit 182 may issue an NFT token ID for the image file (captured image) verified as described above.

[0249] In the smart contract 104 having such a structure, for example, the verification unit 422 uses the camera electronic signature to verify whether the captured image has been tampered with, and if the result of the verification is that the captured image has not been tampered with, the NFT issuing unit 182 issues an NFT corresponding to the captured image. Thus, the smart contract 104 can prove that the captured image to be NFTized has not been tampered with. In other words, the smart contract 104 can prove the authenticity of the content information to be NFTized.

[0250] In addition, the verification unit 422 uses the camera electronic signature to verify whether the metadata of the captured image (e.g., blockchain address, etc.) has been tampered with. As a result, the smart contract 104 can prove that the metadata of the captured image to be NFTed by itself has not been tampered with. In other words, the smart contract 104 can prove the authenticity of the metadata of the content information to be NFTed.

[0251] In addition, the verification unit 422 uses the depth information corresponding to the captured image to verify whether the captured image is legal and valid. Thus, the smart contract 104 can verify whether the captured image to be NFT-ified by itself is forged. That is, the smart contract 104 can prove the authenticity of the content information to be NFT-ified.

[0252] In addition, the verification unit 422 verifies whether the requester (issuer) of the issuance of the NFT is legal and valid. Thus, the smart contract 104 can verify whether the issuer of the NFT is legal and valid. That is, the smart contract 104 can prove the authenticity of the issuer of the NFT. Note that this verification can be performed by the NFT issuance unit 182.

[0253] <Certificate issuance process> In this case, the smart contract 104 may issue a camera certificate as described above. Fig. 20 The flowchart of illustrates an example of the flow of the certificate issuance process executed at this time.

[0254] When the certificate issuance process starts, in step S411, the issuance processing unit 411 of the verification server 103 requests the smart contract 104 to issue a camera certificate via the communication unit 161. In step S421, the camera certificate issuance unit 421 of the smart contract 104 obtains the request via the communication unit 181.

[0255] In step S422, the camera certificate issuing unit 421 obtains the smart contract private key from the storage unit 183 and uses the smart contract private key to issue (generate) the requested camera certificate. For example, the camera certificate issuing unit 421 generates a camera certificate and encrypts the camera certificate with the smart contract private key.

[0256] In step S423 , the camera certificate issuing unit 421 transmits the camera certificate (encrypted camera certificate) to the authentication server 103 of the request source via the communication unit 181 . In step S412 , the issuing processing unit 411 of the authentication server 103 acquires the camera certificate via the communication unit 161 .

[0257] In step S413, the issuance processing unit 411 transmits the camera certificate to the imaging device 102 via the communication unit 161. In step S401, the registration unit 142 of the imaging device 102 acquires the camera certificate via the communication unit 141.

[0258] In step S402, the registration unit 142 supplies and stores the acquired camera certificate to the storage unit 146. The storage unit 146 stores (registers) the supplied camera certificate. When the process of step S402 ends, the certificate issuance process ends.

[0259] <Flow of verification and issuance processing> Next, refer to Fig.21 and Fig. 22 The flowchart of illustrates the process of verification and issuance processing, in which verification of content information, etc. and issuance of NFT are performed. The verification and issuance processing corresponds to Figure 6 The processing of step S103 and step S104.

[0260] When the verification issuance process begins, Fig.21 In step S441, the upload unit 145 of the imaging device 102 transmits the image file generated by itself to the verification server 103 via the communication unit 141. In step S451, the issuance processing unit 411 of the verification server 103 acquires the image file via the communication unit 161.

[0261] In step S452, the issuance processing unit 411 generates an NFT issuance transaction for requesting the issuance of an NFT corresponding to the acquired image file. The NFT issuance transaction includes information required for issuing the NFT. For example, the NFT issuance transaction may include a metadata URL indicating the storage destination of the image file, a blockchain address of the issuer of the NFT (the user of the user terminal device 101), a cloud electronic signature, etc.

[0262] In step S453, the issuance processing unit 411 transmits the generated NFT issuance transaction to the user terminal device 101 via the communication unit 161. In step S431, the request unit 123 of the user terminal device 101 acquires the NFT issuance transaction via the communication unit 121.

[0263] In step S432, the request unit 123 obtains the user wallet private key from the storage unit 124. The request unit 123 uses the user wallet private key to execute the NFT issuance transaction obtained in step S431. With this process, the information required for issuing the NFT is supplied to the smart contract 104 via the communication unit 121. That is, the issuance of the NFT is requested from the smart contract 104.

[0264] In step S461, the NFT issuing unit 182 of the smart contract 104 obtains the request. That is, the NFT issuing unit 182 obtains the information required to issue the NFT (for example, metadata URL, blockchain address, cloud electronic signature, etc.) from the user terminal device 101.

[0265] exist Fig. 22 In step S471, the verification unit 422 uses the smart contract public key to verify whether the camera certificate stored in the image file is legal and valid. As described above, the camera certificate stored in the image file is issued by the smart contract 104 and is encrypted with the smart contract private key. The verification unit 422 decrypts the encrypted camera certificate with the smart contract public key. If the encrypted camera certificate can be correctly decrypted and the same certificate as the certificate issued by the smart contract 104 is obtained, the camera certificate is determined to be legal and valid. In the case where the camera certificate cannot be correctly decrypted or the obtained camera certificate does not match the certificate issued by the smart contract 104, the camera certificate is determined to be invalid. In this case, the verification and issuance process ends.

[0266] If the camera certificate is determined to be valid, in step S472, the verification unit 422 uses the camera certificate and camera electronic signature stored in the image file to verify whether the captured image and metadata stored in the image file have been tampered with. If it is determined that the captured image and metadata have been tampered with, the verification and issuance process ends.

[0267] If it is determined that the captured image and metadata have not been tampered with, in step S473, the verification unit 422 uses the depth information to verify whether the captured image has been forged. If it is determined that the captured image has been forged, the verification issuance process ends.

[0268] When it is determined that the captured image is properly generated, in step S474, the verification unit 422 verifies whether the executor of the NFT issuance transaction (user of the user terminal device 101 (the user)) corresponds to the blockchain address included in the NFT issuance transaction. The NFT issuance transaction contains the blockchain address of the image contributor (creator of the content information). Therefore, the verification unit 422 can verify whether the issuer is legal and valid (whether the issuer is a legal and valid image contributor (creator of the content information)) by performing this verification. Therefore, the smart contract 104 can prove the authenticity of the issuer of the NFT.

[0269] If it is determined that the blockchain address does not correspond to the transaction executor and the NFT issuer is invalid, the verification and issuance process ends. In addition, if the blockchain address corresponds to the transaction executor and the NFT issuer is determined to be legal and valid, the process proceeds to step S475.

[0270] In step S475 , the NFT issuing unit 182 issues the NFT token ID corresponding to the content information verified by the verification server 103 , which is requested from the user terminal device 101 , by using the acquired information.

[0271] When the processing of step S475 is completed, the verification issuance processing is completed.

[0272] By executing each process as described above, the smart contract 104 can verify the authenticity of the captured image, metadata, etc. and issue NFT. As a result, the authenticity of the content information to be NFTized can be proved.

[0273] <6. Additional Notes> <Application Examples of Content Information, etc.> Although the above description uses the case where the content information is a captured image (still image) and the content information file is an image file as an example, the content information processed by the information processing device to which the present technology is applied is arbitrary and is not limited to the above example. For example, the content information may be a moving image. In addition, the content information may also be information other than images, such as characters and audio. In other words, the content information file is also arbitrary and may be a file other than an image file. In addition, the content information may be, for example, a combination of multiple types of content information such as images and audio. In other words, the creator of the content information may not be the image contributor. In addition, the content information generating device may be a device other than an imaging device.

[0274] <Computer> The above series of processing can be performed by hardware or software. In the case where a series of processing is performed by software, the program included in the software is installed in a computer. Here, the computer includes, for example, a computer embedded in dedicated hardware, a general-purpose personal computer that can perform various functions by installing various programs, etc.

[0275] Fig.23 This is a block diagram showing a configuration example of computer hardware that executes the above-described series of processes by a program.

[0276] exist Fig.23 In the illustrated computer 900 , a central processing unit (CPU) 901 , a read only memory (ROM) 902 , and a random access memory (RAM) 903 are connected to one another via a bus 904 .

[0277] In addition, an input / output interface 910 is also connected to the bus 904. An input unit 911, an output unit 912, a storage unit 913, a communication unit 914, and a drive 915 are connected to the input / output interface 910.

[0278] The input unit 911 includes, for example, a keyboard, a mouse, a microphone, a touch panel, an input terminal, etc. The output unit 912 includes, for example, a display, a speaker, an output terminal, etc. The storage unit 913 includes, for example, a hard disk, a RAM disk, a nonvolatile memory, etc. The communication unit 914 includes, for example, a network interface. The drive 915 drives a removable recording medium 921 such as a magnetic disk, an optical disk, an optical magnetic disk, or a semiconductor memory.

[0279] In the computer configured as described above, the CPU 901 loads the program stored in the storage unit 913 into the RAM 903 via the input / output interface 910 and the bus 904 and executes the program. As a result, the above series of processing is performed. The RAM 903 can appropriately store data and the like required when the CPU 901 executes various processing.

[0280] The program executed by the computer may be recorded in the removable recording medium 921 as a package medium, for example, and used. In this case, the program may be read from the removable recording medium 921 mounted in the drive 915 and installed in the storage unit 913 via the input / output interface 910 .

[0281] In addition, the program may be provided via any wired or wireless transmission medium such as a local area network, the Internet, digital satellite broadcasting, etc. In this case, the program may be received by the communication unit 914 and installed in the storage unit 913 via the input / output interface 910 .

[0282] Furthermore, the program may be pre-installed in the ROM 902 or the storage unit 913 or both.

[0283] <Target of application of this technology> The present technology can be applied to any structure. For example, the present technology can be applied to various electronic devices.

[0284] In addition, for example, the present technology can also be implemented as a partial structure of a device, such as a processor as a system large-scale integration (LSI) (e.g., a video processor), a module using multiple processors (e.g., a video module), a unit using multiple modules (e.g., a video unit), or a kit obtained by adding other functions to a unit (e.g., a video kit).

[0285] Note that in this specification, a system means a collection of multiple components (devices, modules (components), etc.), and it does not matter whether all components are in the same chassis. Therefore, multiple devices housed in other chassis and connected via a network and a single device containing multiple modules in a single chassis are both systems.

[0286] <Fields and uses where this technology can be applied> Systems, devices, processing units, etc. to which this technology is applied can be used in any field, such as transportation, medical care, crime prevention, agriculture, animal husbandry, mining, beauty, factories, home appliances, meteorology, natural monitoring, etc. In addition, its use is also arbitrary.

[0287] <Others> The embodiments of the present technology are not limited to the above-described embodiments, and various changes can be made without departing from the scope of the present technology.

[0288] For example, a structure described as one device (or processing unit) may be divided and configured as multiple devices (or processing units). Conversely, the structures described above as multiple devices (or processing units) may be combined and configured as one device (or processing unit). In addition, of course, structures other than those described above may be added to the structures of each device (or each processing unit). Furthermore, when the structure and operation of the system as a whole are basically the same, a portion of the configuration of a device (or processing unit) may be included in the configuration of other devices (or other processing units).

[0289] In addition, for example, the above-mentioned program can be executed in any device. In this case, it is only necessary to make the device have necessary functions (functional blocks, etc.) and obtain necessary information.

[0290] In addition, for example, each step in a flowchart may be executed by one device or by multiple devices. Furthermore, when multiple processes are included in one step, the multiple processes may be executed by one device or by multiple devices. In other words, the multiple processes included in one step may be executed as multiple steps. Conversely, the processes described as multiple steps may be collectively executed as one step.

[0291] In addition, for example, in a program executed by a computer, the processing of the steps describing the program may be executed in a time series order in the order described in this specification, or may be executed separately in parallel or at a necessary timing such as when a call is made. In other words, the processing of each step may be executed in an order different from the above order as long as there is no contradiction. Furthermore, the processing of the steps describing the program may be executed in parallel with the processing of other programs, or may be executed in combination with the processing of other programs.

[0292] In addition, for example, as long as there is no contradiction, multiple technologies related to the present technology can be independently implemented as a single entity. Of course, any multiple technologies can also be implemented in combination. For example, part or all of the present technology described in any embodiment can be combined with part or all of the present technology described in other embodiments to achieve. In addition, part or all of any of the above-mentioned technologies can be implemented in combination with other technologies not described above.

[0293] Note that the present technology can also have the following configurations.

[0294] (1) An information processing device comprising: A verification unit that uses an electronic signature to verify whether the content information has been tampered with; and The request unit, when it is determined as a result of the verification that the content information has not been tampered with, requests the issuance of a non-fungible token NFT corresponding to the content information.

[0295] (2) The information processing device according to (1), wherein: The verification unit uses the electronic signature to verify whether metadata of the content information has been tampered with.

[0296] (3) The information processing device according to (1) or (2), wherein: The verification unit uses the depth information corresponding to the content information to verify whether the content information is legal and valid.

[0297] (4) The information processing device according to (1), wherein: The requesting unit generates an NFT issuance transaction requesting the issuance of the NFT.

[0298] (5) The information processing device according to (4), wherein: The requesting unit executes the NFT issuance transaction.

[0299] (6) The information processing device according to (4), wherein: The request unit provides the NFT issuance transaction to the device requesting the issuance of the NFT.

[0300] (7) An information processing method comprising: Use electronic signatures to verify whether the content information has been tampered with. When it is determined as a result of the verification that the content information has not been tampered with, a request is made to issue a non-fungible token NFT corresponding to the content information.

[0301] (8) An information processing device comprising: A verification unit that uses an electronic signature to verify whether the content information has been tampered with; and The issuing unit issues a non-fungible token NFT corresponding to the content information when it is determined as a result of the verification that the content information has not been tampered with.

[0302] (9) The information processing device according to (8), wherein: The verification unit uses the electronic signature to verify whether metadata of the content information has been tampered with.

[0303] (10) The information processing device according to (8) or (9), wherein: The verification unit uses the depth information corresponding to the content information to verify whether the content information is legal and valid.

[0304] (11) The information processing device according to (8) or (9), wherein: The verification unit verifies whether the requester for issuance of the NFT is legal and valid.

[0305] (12) An information processing method comprising: Use electronic signatures to verify whether the content information has been tampered with. When it is determined as a result of the verification that the content information has not been tampered with, a non-fungible token NFT corresponding to the content information is issued.

[0306] (13) An information processing device comprising: a content information generating unit, generating content information according to a user's operation; and The content information file generating unit generates a content information file storing the content information and the blockchain address corresponding to the user.

[0307] (14) The information processing device according to (13), wherein: The content information file generation unit saves the electronic signature corresponding to the content information and the blockchain address in the content information file.

[0308] (15) The information processing device according to (13) or (14), wherein: The content information file generation unit stores a certificate including a public key corresponding to a private key unique to the information processing device in the content information file.

[0309] (16) The information processing device according to (13) or (14), further comprising: a depth information generating unit, generating depth information corresponding to the content information, The content information file generating unit stores the depth information in the content information file.

[0310] (17) The information processing device according to (13) or (14), further comprising: The requesting unit requests verification of the content information and issuance of a non-fungible token NFT corresponding to the content information by sending the content information file to other devices.

[0311] (18) The information processing device according to (13) or (14), wherein: The content information generating unit captures an image of a subject according to the operation of the user and generates the captured image as the content information, and The content information file generation unit generates an image file storing the captured image and the blockchain address as the content information file.

[0312] (19) An information processing method comprising: Generate content information based on user operations; and Generate a content information file that stores the content information and the blockchain address corresponding to the user.

[0313] (20) An information processing system comprising: a content information generating device, a verification device and a non-fungible token (NFT) issuing device, wherein: The content information generating device comprises: A content information generating unit, generating content information according to a user's operation; a content information file generating unit, which generates a content information file storing the content information and a blockchain address corresponding to the user; and a verification request unit for requesting verification of the content information by supplying the content information file to the verification device, The verification device comprises: a verification unit, which uses an electronic signature to verify whether the content information has been tampered with; and an issuance request unit that, when it is determined as a result of the verification that the content information has not been tampered with, requests the NFT issuance device to issue an NFT corresponding to the content information, The NFT issuance device includes: The issuing unit issues the requested NFT corresponding to the content information.

Claims

1. An information processing device, comprising: A verification unit that uses an electronic signature to verify whether the content information has been tampered with; as well as The request unit, when it is determined as a result of the verification that the content information has not been tampered with, requests the issuance of a non-fungible token NFT corresponding to the content information.

2. The information processing device according to claim 1, wherein: The verification unit uses the electronic signature to verify whether metadata of the content information has been tampered with.

3. The information processing device according to claim 1, wherein: The verification unit uses the depth information corresponding to the content information to verify whether the content information is legal and valid.

4. The information processing device according to claim 1, wherein: The requesting unit generates an NFT issuance transaction requesting the issuance of the NFT.

5. The information processing device according to claim 4, wherein: The requesting unit executes the NFT issuance transaction.

6. The information processing device according to claim 4, wherein: The request unit provides the NFT issuance transaction to the device requesting the issuance of the NFT.

7. An information processing method, comprising: Use electronic signatures to verify whether the content information has been tampered with. When it is determined as a result of the verification that the content information has not been tampered with, a request is made to issue a non-fungible token NFT corresponding to the content information.

8. An information processing device, comprising: A verification unit that uses an electronic signature to verify whether the content information has been tampered with; as well as The issuing unit issues a non-fungible token NFT corresponding to the content information when it is determined as a result of the verification that the content information has not been tampered with.

9. The information processing device according to claim 8, wherein: The verification unit uses the electronic signature to verify whether metadata of the content information has been tampered with.

10. The information processing device according to claim 8, wherein: The verification unit uses the depth information corresponding to the content information to verify whether the content information is legal and valid.

11. The information processing device according to claim 8, wherein: The verification unit verifies whether the requester for issuance of the NFT is legal and valid.

12. An information processing method, comprising: Use electronic signatures to verify whether the content information has been tampered with. When it is determined as a result of the verification that the content information has not been tampered with, a non-fungible token NFT corresponding to the content information is issued.

13. An information processing device, comprising: A content information generating unit, generating content information according to a user's operation; as well as The content information file generating unit generates a content information file storing the content information and the blockchain address corresponding to the user.

14. The information processing device according to claim 13, wherein: The content information file generation unit saves the electronic signature corresponding to the content information and the blockchain address in the content information file.

15. The information processing device according to claim 13, wherein: The content information file generation unit stores a certificate including a public key corresponding to a private key unique to the information processing device in the content information file.

16. The information processing device according to claim 13, further comprising: a depth information generating unit, generating depth information corresponding to the content information, The content information file generating unit stores the depth information in the content information file.

17. The information processing device according to claim 13, further comprising: The requesting unit requests verification of the content information and issuance of a non-fungible token NFT corresponding to the content information by sending the content information file to other devices.

18. The information processing device according to claim 13, wherein: The content information generating unit captures an image of a subject according to the operation of the user and generates the captured image as the content information, and The content information file generation unit generates an image file storing the captured image and the blockchain address as the content information file.

19. An information processing method, comprising: Generate content information based on user operations; as well as Generate a content information file that stores the content information and the blockchain address corresponding to the user.

20. An information processing system comprising: Content information generation device, verification device and non-homogeneous token NFT issuance device, wherein: The content information generating device comprises: A content information generating unit, generating content information according to a user's operation; a content information file generating unit, which generates a content information file storing the content information and a blockchain address corresponding to the user; and a verification request unit for requesting verification of the content information by supplying the content information file to the verification device, The verification device comprises: a verification unit, which uses an electronic signature to verify whether the content information has been tampered with; and an issuance request unit that, when it is determined as a result of the verification that the content information has not been tampered with, requests the NFT issuance device to issue an NFT corresponding to the content information, The NFT issuance device includes: The issuing unit issues the requested NFT corresponding to the content information.