JP2024058414A - Information processing system, information processing device, and program - Google Patents

Abstract

[Problem] To prevent unintended use of a target image to be shared. [Solution] An information processing system is characterized by comprising a receiving means for receiving handling information regarding the handling of a target image to be shared, a registering means for registering the handling information in a blockchain, an acquiring means for acquiring specific information capable of identifying the handling information registered in the blockchain, and an adding means for adding the specific information to the target image. [Selected Figure] Figure 1

Description

The present invention relates to an information processing system, an information processing device, and a program.

Patent Document 1 describes a registration device that transmits a first transaction (TX) in which image information is stored to a blockchain (BC) network, embeds and stores a two-dimensional code in which specific information for identifying the first TX registered in the BC is encoded in the image data, and transmits a second TX in which tamper-proof data including a hash value of the image data in which the two-dimensional code is embedded and the specific information is stored to the BC network.

JP 2020-182167 A

However, for example, there are cases where one user shares target information such as image data with other users. Image data is easy to copy and distribute, so there is a risk that the other users may share the target information such as image data with yet another user against the first user's will.
The present invention aims to prevent unintended use of target information that is to be shared.

For this purpose, the technology disclosed in this specification is an information processing system characterized by having a receiving means for receiving handling information regarding the handling of a target image to be shared, a registration means for registering the handling information in a blockchain, an acquisition means for acquiring specific information capable of identifying the handling information registered in the blockchain, and an addition means for adding the specific information to the target image.
Here, the handling information may include sharing information about the people who share the target image.
In addition, the addition means may add a transaction hash when the handling information was registered in the blockchain to the target image.
In addition, the adding means adds a specific image indicating the specific information and a suggestive image suggesting that the specific information has been added to the target image, and the specific image is presented in an invisible or difficult to see manner, and the suggestive image is presented in a visible or easily visible manner.
The method may also include a generation means for generating a hash value of the target image to which the specific information has been added, and the registration means may register registration information in the blockchain that associates hash information regarding the hash value with the handling information.
In addition, a plurality of different handling information may be registered in the blockchain, and the registration means may register one of the plurality of handling information registered in the blockchain in association with the target image.
In addition, it is preferable to include an output means for outputting the handling information to be registered in the blockchain and document information that has been written down from the input information received from the user.
In addition, the registration means may acquire information regarding changes to the handling information, and may associate the handling information before the change with the handling information after the change and register them in the blockchain.
The image forming apparatus may further comprise an information output means for outputting the content of the handling information corresponding to the specific information based on the specific information included in the target image.
In addition, it is preferable that the blockchain system forming the blockchain is provided with a judgment means for judging whether the handling conditions for the target image specified by the user satisfy predetermined conditions.

For this purpose, the technology disclosed in this specification is an information processing system that includes a receiving means for receiving shared information related to a sharer of a target image to be shared, a first registration means for registering the shared information in a blockchain, an acquisition means for acquiring a transaction hash that can identify the shared information registered in the blockchain, a transaction image that shows the transaction hash in an invisible or difficult to see manner, a suggestion image that suggests in a visible or easily visible manner that the transaction hash is included in the target image, and an image generation means for generating a shared image using the target image, and a second registration means for registering the hash value generated from the shared image and the shared information in association with each other in the blockchain.

Furthermore, for this purpose, the technology disclosed in this specification is an information processing system characterized by comprising a receiving means for receiving handling information regarding the handling of the target information to be shared, a registering means for registering the handling information in a blockchain, an acquiring means for acquiring specific information capable of identifying the handling information registered in the blockchain, and an adding means for adding the specific information to the target information.

In addition, for this purpose, the technology disclosed in this specification is an information processing device characterized by having an acquisition means for acquiring specific information capable of identifying handling information regarding the handling of a target image to be shared that is registered in a blockchain, and an image generation means for generating a shared image using the target image and the specific information.
Furthermore, for this purpose, the technology disclosed in this specification is a program for enabling a computer to realize the functions of obtaining specific information capable of identifying handling information regarding the handling of a target image to be shared that is registered in a blockchain, and generating a shared image using the target image and the specific information.

Furthermore, for this purpose, the technology disclosed in this specification is an information processing device characterized by comprising an image acquisition means for acquiring a target image to be shared, a reading means for reading specific information from the target image that can identify handling information regarding the handling of the target image registered in the blockchain, and an information output means for outputting the handling information registered in the blockchain based on the specific information.

The present invention makes it possible to prevent unintended use of the target information to be shared.

1 is a schematic diagram of a content management system according to an embodiment of the present invention; 1A and 1B are schematic diagrams of a shared image according to the present embodiment. FIG. 2 illustrates an example of a hardware configuration of a terminal device. FIG. 2 illustrates an example of a hardware configuration of a server device. FIG. 2 is a functional block diagram of a server device according to the present embodiment. FIG. 2 is an explanatory diagram of an embedded image according to the present embodiment. FIG. 4 is a diagram showing an example of a registration form screen according to the present embodiment. FIG. 13 is a diagram showing an example of an application screen according to the present embodiment. This is a sequence diagram for registering contract information in a blockchain system. FIG. 11 is a sequence diagram for sharing a content image. 10 is a flowchart showing a process for verifying a shared image according to the present embodiment.

Hereinafter, the present embodiment will be described with reference to the accompanying drawings.
<Content Management System 1>
FIG. 1 is a schematic diagram of a content management system 1 according to the present embodiment.
FIG. 2 is a schematic diagram of a shared image 100 according to the present embodiment.

As shown in Figure 1, the content management system 1 of this embodiment includes a first terminal device 10 used by one user, a second terminal device 20 used by another user, a blockchain system 30, and a server device 50 that processes information.
The first terminal device 10, the second terminal device 20, the block chain system 30, and the server device 50 are connected to each other via a network. The network is not particularly limited as long as it is a communication network used for data communication between the devices.

As shown in FIG. 2, the shared image 100 to be shared in this embodiment includes a content image 100C including an original image, an embedded image 100H embedded in the content image 100C, and a mark image 100M. The configuration of the shared image 100 will be described in detail later.

In the description of this embodiment, the first terminal device 10 can be exemplified by a personal computer (PC) used by a user a who is an employee of company A. The second terminal device 20 can be exemplified by a PC used by a user b who is an employee of company B.
For the sake of convenience in the explanation of this embodiment, a first terminal device 10 used by user a of company A and a second terminal device 20 used by user b of company B are respectively illustrated, however, multiple other terminal devices may be used depending on the users who use this system.
In addition, in the description of this embodiment, when there is no particular need to distinguish between the first terminal device 10 and the second terminal device 20, they will be collectively referred to as terminal devices.

In this embodiment, an example will be described in which user a of company A shares his company's shared image 100 with user b of company B. However, a contract has been concluded between company A and company B stating that the shared image 100 may only be used by user b within company B, and that further sharing, such as disclosure or transfer, of the image to outside company B is restricted.

The content management system 1 of this embodiment then accepts handling information regarding the handling of the content image 100C to be shared, and registers the handling information in the blockchain. Furthermore, the content management system 1 acquires specific information, such as a transaction hash, that can identify the handling information registered in the blockchain, and adds the specific information to the content image 100C.

That is, in the content management system 1 of this embodiment, specific information that can confirm that the shared image 100 is limited to use within Company B of user b is added to the content image 100C itself. If the shared image 100 is leaked outside Company B and made public by a third party, the specific information added to the shared image 100 makes it possible to confirm handling information related to the contract for handling the shared image 100. In this way, in the content management system 1 of this embodiment, the handling information of the shared image 100 can be confirmed based on the shared image 100 itself. Therefore, for example, user b of Company B will be conscious of taking sufficient care in handling the content image 100C obtained from Company A. That is, for example, user b of Company B can be deterred from leaking the content image 100C to a third party.

Content image 100C is a unique image represented in shared image 100. Content image 100C can be, for example, a photograph, a picture, an illustration, or an image that is not to be made public beyond a certain range, such as experimental results. In other words, content image 100C is not an image that anyone can use freely, but an image that has restrictions on its use or requires confidentiality. Content image 100C can be, for example, a still image in a data format such as JPEG, JPG, PNG, GIF, or TIFF.

The content image 100C also includes images on paper media and images on electronic media. Images on paper media become content image 100C by converting them into electronic data by scanning or the like. On the other hand, images on electronic media can be used as content image 100C in their original data format, or can be used as content image 100C by converting them into electronic data in a predetermined format as described above.

(First terminal device 10, second terminal device 20)
FIG. 3 is a diagram illustrating an example of a hardware configuration of a terminal device.

As shown in FIG. 3, the terminal device (first terminal device 10, second terminal device 20) includes a CPU 101, a RAM 102, a ROM 103, a memory unit 104, a display 105, a speaker 106, a microphone 107, a camera 108, and a network I/F 109.

The CPU 101 loads various programs stored in the ROM 103 or the like into the RAM 102 and executes them to realize various functions of the terminal device.
The RAM 102 is a memory used as a working memory for the CPU 101, etc.
The ROM 103 is a memory that stores various programs executed by the CPU 101 .
The storage unit 104 is, for example, a flash memory that stores various application programs and various data used by the programs.

The display 105 displays a screen or the like that conveys various information to the user. The display 105 may be, for example, a touch panel that accepts operational input from the user.
The speaker 106 outputs various sounds including the voice received from the other party.
The microphone 107 captures various sounds including the user's speech.
The camera 108 includes a lens and an imaging element (image sensor) such as a complementary metal-oxide semiconductor (CMOS), and captures an image of a subject.

The network I/F 710 transmits and receives data to and from other communication devices. Here, the network I/F 710 communicates with the server device 50 and the like via the network.

(Blockchain system 30)
The blockchain system 30 is composed of multiple nodes connected in a Peer to Peer (P2P) manner. One node in the blockchain system 30 becomes a minor node, which bundles unprocessed transactions to generate a new block. That is, the minor node performs mining. At least one node in the blockchain system 30 is a full node, which stores the entire data of the blockchain. In the blockchain system 30, a blockchain that is difficult to tamper with is formed by reaching an agreement between nodes using a predetermined consensus algorithm. In addition, the server device 50 of this embodiment constitutes a node in the blockchain system 30.
As the blockchain network, an existing blockchain network such as the Ethereum network can be used.

In the blockchain system 30, a wallet is used that is owned by each account, for example, of a company or an individual. The wallet has a private key that is used for an electronic signature when creating transaction data in the blockchain. In the content management system 1 of this embodiment, it is possible to check information on the person (account) who registered a transaction in the blockchain system 30 and the date and time when the transaction was registered.

(Server device 50)
FIG. 4 is a diagram showing an example of the hardware configuration of the server device 50. As shown in FIG.

As shown in FIG. 4, the server device 50 includes a CPU (Central Processing Unit) 501, which is a computing means, a RAM (Random Access Memory) 502, which is an execution area for programs, and a ROM (Read Only Memory) 503, which is a storage area for storing programs such as a BIOS (Basic Input Output System). The server device 50 also includes a HDD (Hard Disk Drive) 504, which is a storage area for storing various programs such as an OS (Operating System) and apps, input data for the various programs, output data from the various programs, and the like. Furthermore, the server device 50 has a communication interface (communication I/F) 505 for communicating with the outside.

Figure 5 is a functional block diagram of the server device 50 of this embodiment.

As shown in FIG. 5, the server device 50 includes a contract management unit 51 that manages contract information, etc., a content management unit 53 that manages content image 100C, etc., and a verification unit 55 that verifies the contract information, etc. associated with content image 100C.

First, the contract management unit 51 of this embodiment will be described in detail.
The contract management unit 51 manages contract information, which is a contract regarding the handling of the content image 100C. The contract information can be, for example, a non-disclosure agreement (NDA). The contract management unit 51 accepts contract information regarding the handling of the content image 100C from a registration form screen 200 (see FIG. 7 described later). Then, the contract management unit 51 registers the contract information in the blockchain system 30. The contract management unit 51 registers a plurality of different contract information in the blockchain system 30 in advance. The contract management unit 51 of this embodiment associates contract identification information that can uniquely identify one contract with the one contract. Specifically, the contract management unit 51 manages each individual contract by assigning an identifier such as a specific alphanumeric character as contract identification information to each contract.

By registering the contract information in the blockchain system 30, the possibility of the contents being tampered with is extremely low, and the information is managed with a high degree of reliability. The contract information registered in the blockchain system 30 is then associated with the content image 100C, as described below. The contract information is then referenced as necessary, for example, during verification.

The contract information in this embodiment includes the following information: The contract information includes contractor information on the contractor, the usage conditions of the content image 100C, and information on the method of returning the content image.
The contractor information includes the specific name of the contractor, such as the name of the company that is entering into the contract.
The usage conditions include information on the conditions for using the content image 100C, such as the disclosure range of the content image 100C, the usage period of the content image 100C, and the usage method of the content image 100C. The disclosure range specifies the range of disclosure of the content image 100C, such as limiting the use of the content image 100C to within a company or limiting the use to outsourced parties. The usage method specifies the specific usage method of the content image 100C, such as limiting the content image 100C to research or allowing the content image 100C to be published in media such as newspapers and magazines. The usage period specifies the specific period during which the content image 100C can be shared.
The return method specifies a method for returning the content image 100C. Examples of the return method include deleting the content image 100C, or showing evidence of the deletion.

Based on the information regarding the contract received from the registration form screen 200 (see FIG. 7 described later), the contract management unit 51 creates "registered contract information" to be registered in the blockchain system 30 and "contract document information" that can be recognized by the user as text. In other words, the contract management unit 51 of this embodiment outputs registered contract information and contract document information that correspond to each other based on one contract.

The registered contract information is information indicating the contents of the contract, and uses the information entered in the registration form screen 200. The contract management unit 51 then registers the registered contract information in the blockchain system 30. The contract management unit 51 manages the transaction hash obtained when the registered contract information is registered in the blockchain system 30 in association with the contract information. Specifically, the contract management unit 51 stores the contract identification information and the transaction hash in the database in association with each other.

The contract document information can be created based on a template document created in advance and information accepted on the registration form screen 200. The contract document information is information obtained by turning the information accepted on the registration form into text. The template document contains text about the contract with the date, proper name, individual conditions, etc., left blank. The contract document information is created by filling in the blanks in the template document with the information accepted on the registration form screen 200. For example, if "XXXY/Y/Z" is accepted as the end date of the usage period in the contract on the registration form screen 200, the contract document information will be written as "The contract period of this contract shall be XXXY/Y/Z. The contract period will continue unless Party B requests an extension...".
The contract management unit 51 holds the created contract document information, and also sends the contract document information to the user in response to a request from the user.

Next, the content management unit 53 of this embodiment will be described in detail.
The content management unit 53 associates the content image 100C with the contract information and registers them in the block chain system 30. By using the block chain system 30, it becomes substantially impossible to tamper with the registered content.

The content management unit 53 creates application information. Application information is created for each content image 100C, for example, when user a wants to make a content image 100C available to user b based on a contract. In this embodiment, the content management unit 53 accepts application information for sharing the content image 100C from the application screen 300 (see FIG. 8 described later).

The application information includes application identification information that can uniquely identify one application, applicant information that can identify the user (applicant) making the application, and selected contract identification information that identifies the contract information selected by the applicant. Furthermore, the application information includes sharing information of the party with whom the content image 100C will be shared, approver information that can identify the user (applicant) who approves the application, and condition application information in which the applicant specifies the conditions for using the content image 100C.

The application identification information is made possible to uniquely identify each application by assigning a specific identifier such as alphanumeric characters to each application.
The applicant information may be, for example, a specific name of an applicant who applies to share the target content image 100C. Note that the applicant information may be in other forms, such as an employee number or a symbol, other than a name, as long as it can identify the applicant.

The selected contract identification information is information for identifying the contract information to be associated with the content image 100C. In this embodiment, the selected contract identification information is the contract identification information of the contract information selected by the applicant from among a plurality of pieces of contract information to be associated with the content image 100C. In other words, the selected contract identification information specifies the contract identification information of the contract information concluded with the other party with which the content image 100C is shared.
The shared information is information about a company or individual with whom the applicant intends to share the content image 100C. As described above, the shared information is information about a contractor identified from contractor information in the selected contract identification information that identifies the contract information selected by the applicant.

The approver information is the specific name of the approver who approves the application made by the applicant. An example of an approver is a person in charge at a company, such as the applicant's superior. Note that the approver information only needs to be able to identify the approver, and may be in other forms, such as an employee number, in addition to a name.

The condition application information includes information regarding the conditions designated by the applicant when using the content image, such as the disclosure range of the content image 100C and the usage period of the content image.
The applicant specifies the scope of disclosure (publication scope) of the content image 100C, such as "limited to use of the content image 100C within the company" or "limited to mention of the content image 100C in papers and magazines."
The applicant specifies the method for returning the content image 100C as the return method.

In this embodiment, the conditions of the selected contract information are applied as is unless the applicant specifies otherwise. In other words, in the content management system 1 of this embodiment, it is not essential for the applicant to specify the handling conditions for the content image 100C.
On the other hand, if the applicant specifies the condition application information, the contents specified by the applicant are applied. However, the conditions specified by the applicant cannot deviate from the contract information. For example, if the usage period is specified in advance in the contract information, the applicant cannot specify a usage period that exceeds the range of the usage period of the contract information. In such a case, a warning message is displayed on the application screen of this embodiment to the effect that the content cannot be applied for.

Then, the content management unit 53 associates the contract information with the application information and registers them in the blockchain system 30.

The contract information is selected from among the contract information preregistered in the blockchain system 30. Here, the contract information refers to the contract information that the applicant (in this embodiment, user a of company A) associates with the content image 100C at the time of application. More specifically, the contract information is identified by the selected contract identification information, which is the contract identification information of the selected contract information.

As described above, the application information includes the above-mentioned application identification information, applicant information, approver information, selected contract identification information, and condition application information. The content management unit 53 then registers the application information as a transaction in the blockchain system 30.

The content management unit 53 obtains a transaction hash when the application information is registered in the blockchain system 30. Here, the transaction hash is information for identifying one transaction in the blockchain system 30. For example, the transaction hash is created as a 64-character alphanumeric code. The content management unit 53 then manages the application information in association with the transaction hash obtained in response to the registration of the application information in the blockchain system 30.

The content management unit 53 receives a designation of the content image 100C to be shared from the user. The content management unit 53 then embeds an image (hereinafter referred to as an embedded image 100H) indicating the transaction hash corresponding to the application information in the content image 100C. In other words, the content management unit 53 adds the transaction hash generated when the selected contract identification information included in the application information was registered in the blockchain to the content image 100C. In this way, the content management unit 53 generates the shared image 100 using the content image 100C and the transaction hash (embedded image 100H).

Figure 6 is an explanatory diagram of embedded image 100H in this embodiment.

The embedded image 100H to be embedded in the content image 100C is added to the content image 100C by, for example, the following method. The embedded image 100H representing the transaction hash is provided, for example, in the center of the content image 100C (see FIG. 2A). As shown in FIG. 6, the embedded image 100H of this embodiment is composed of pixels whose RGB values are different from those of the surrounding pixels. For example, if there is an area that represents red, the area is represented by a set of multiple pixels P1 represented by (R: 255, G: 0, B: 0). In contrast, the embedded image 100H is represented by pixels P2 whose RGB values are different by subtracting, for example, the R value from the RGB values, such as (R: 254, G: 0, B: 0). In other words, a character string such as an alphanumeric character is represented by the pixel P2 whose RGB value is different from that of the surrounding pixel P1. The embedded image 100H of this embodiment represents the transaction hash on the content image 100C based on this rule. In this way, embedded image 100H is displayed so as to overlap (superimpose) with content image 100C.

Furthermore, in this embodiment, as shown in FIG. 2(B), a slash "/" is added before and after each character string that makes up embedded image 100H. For example, to express "E12Y2B9...276F" in content image 100C, it is expressed as "/E12Y2B9...276F/". Based on the above RGB value rules, it is expected that the characters will be read as the original color expression of content image 100C. However, by adding the condition that the characters are enclosed between specific symbols, such as slashes, the reading accuracy of embedded image 100H is improved.

As described above, the content management unit 53 embeds the transaction hash information in the content image 100C using pixels whose RGB values do not differ significantly from those of the surrounding pixels. In this way, the content management unit 53 displays the embedded image 100H in a manner that is invisible or difficult for the user to view. The content management unit 53 also avoids compromising the original content of the content image 100C by not significantly modifying the content image 100C.

In the present embodiment, the embedded image 100H represents, for example, the transaction hash of the application information obtained from the blockchain system 30 as a character string, but is not limited to this. The embedded image 100H may be any other character string or image, as long as it is information that can uniquely identify the transaction hash of the application information.

Furthermore, as shown in FIG. 2A, the content management unit 53 adds a predetermined mark image 100M to the content image 100C. The mark image 100M is an image that is visible or easily visible to the user. The mark image 100M uses a color that is relatively conspicuous when placed on the content image 100C, such as black, unlike the surrounding colors. In addition, the mark image 100M is placed, for example, at the end of the content image 100C or outside the range of the content image 100C. The mark image 100M is an image common to the content image 100C registered in the blockchain system 30 in the content management system 1 of this embodiment. In other words, the mark image 100M is an image that is uniformly added regardless of the content of the content image 100C or the contract content.
It should be noted that the mark image 100M is an image that is superimposed on the content image 100C, and the embedded image 100H is an image that is not superimposed on the content image 100C.

The mark image 100M can be visually recognized by the user in the shared image 100. Therefore, the mark image 100M can suggest or make the user aware that the content image 100C is managed by the content management system 1 of this embodiment. In other words, the mark image 100M is an image that suggests that an embedded image 100H such as a transaction hash has been added to the content image 100C in the shared image 100. By providing the mark image 100M so that it is visually recognizable in the shared image 100, the user who has viewed the shared image 100 can be made aware of how to handle the shared image 100.

As described above, the content management unit 53 creates the shared image 100 by adding the embedded image 100H and the mark image 100M to the content image 100C.
Then, the content management unit 53 calculates a hash value of the shared image 100. The hash value is an irregular character string generated from the shared image 100 using a specific algorithm (hash function). In other words, the hash value represents the shared image 100 as short, fixed-length data. The hash value generated from the shared image 100 is a value unique to each shared image 100, and will be a completely different value if the content of the shared image 100 is even slightly different.

Then, the content management unit 53 associates the hash value generated from the shared image 100 with the already registered application information (application identification information) and registers them in the blockchain system 30. This hash value and application identification information of the shared image 100 are called "registered information." As a result, the shared image 100 (hash value), application information, and contract information are mutually associated on the blockchain system 30.

The blockchain system 30 has a limited amount of data that can be stored as one transaction or block. Therefore, in the content management system 1 of this embodiment, the shared image 100 itself is not registered in the blockchain, but rather a hash value is registered as described above. This reduces the load on the hardware resources that make up the blockchain system 30.

The content management unit 53 also stores the shared image 100 in which the embedded image 100H and the mark image 100M are added to the content image 100C. The content management unit 53 sends the shared image 100 to the user in response to a request from the user. Then, the first terminal device 10 transmits the shared image 100 to the second terminal device 20. That is, the user (e.g., user a) can share the shared image 100 (content image 100C) with a user (e.g., user b) outside the company, for example.

Next, the verification unit 55 of the present embodiment will be described in detail.
The verification unit 55 uses the shared image 100 and the blockchain system 30 to identify various pieces of information associated with the shared image 100. In particular, the verification unit 55 identifies information related to the handling of the content image 100C based on the various pieces of information.

The verification unit 55 acquires the shared image 100. Then, the verification unit 55 reads the embedded image 100H added to the shared image 100.
Then, the verification unit 55 of this embodiment reads the transaction hash of the application information from the embedded image 100H. Furthermore, the verification unit 55 identifies a transaction of the application information corresponding to the transaction hash in the blockchain system 30. This transaction of the application information includes various information including the contract identification information of the content image 100C. Therefore, the verification unit 55 identifies the contract information to be registered in the blockchain system 30 based on the contract identification information.

The verification unit 55 displays the contents of the contract information and application information associated with the shared image 100, for example, on the screen of the terminal device. In this way, the verification unit 55 shows information regarding the handling of the content image 100C.

Next, the registration form screen 200 displayed by the contract management unit 51 of this embodiment will be described.
FIG. 7 is a diagram showing an example of a registration form screen 200 according to this embodiment.

As shown in FIG. 7, the registration form screen 200 has a contractor input field 211 for inputting contractor information, a usage period input field 212 as a usage condition, a usage range input field 213 as a usage condition, a usage method input field 214 as a usage condition, and a return method input field 215.

A specific name, such as an individual's name or a company's name, can be entered in the contractor input field 211. Identification information, such as alphanumeric characters, that can uniquely identify an individual or company may also be entered in the contractor input field 211.

The start and end dates of the usage period of the content image 100C can be input in the usage period input field 212. In this example, the usage period input field 212 accepts the input of numbers.
The range of disclosure of the content image 100C is input in the usage range input field 213. In the usage range input field 213 of this embodiment, a selection can be made from a plurality of candidates for specifying the disclosure range.
A method of using the content image 100C is input in the method of use input field 214. In the method of use input field 214 of this embodiment, a selection can be made from a plurality of candidates for specifying the method of use.

The return method input field 215 is used to input the return method for the content image 100C. In this embodiment, the return method input field 215 allows the user to select from multiple options to specify the method of use.

Next, the application screen 300 displayed by the content management unit 53 of this embodiment will be described.
FIG. 8 is a diagram showing an example of the application screen 300 of this embodiment.

As shown in FIG. 8, the application screen 300 has an applicant input field 311 for inputting the applicant, a content image designation field 312 for designating the content image 100C, a contract information designation field 313 for designating the contract information, a sharing information field 314 for indicating the sharing destination of the content image 100C, and an approver input field 315 for inputting the approver.

The applicant input field 311 is a field for inputting an applicant who applies to share the content image 100C. Note that the applicant input field 311 may be used to input identification information, such as alphanumeric characters, that can uniquely identify the applicant.
The content image designation field 312 is a field for designating a content image 100C to be shared. The applicant uses the content image designation field 312 to upload a content image 100C or designate one content image 100C from a list display of a plurality of pre-stored content images 100C.

The contract information designation field 313 is a field for designating contract information to be associated with the content image 100C. The applicant uses the contract information designation field 313 to associate contract information with the designated content image 100C. That is, the applicant designates a contractor corresponding to the contractor who will share the content image 100C. In this manner, the contract information includes sharing information related to the contractor who will share the content image 100C. Note that the contract information designation field 313 can accept the designation of one piece of contract information from a list display of multiple pieces of contract information, for example.

The shared information field 314 displays the contractor information of the contract information specified in the contract information specification field 313. In this embodiment, the contractor of the contract information selected from the multiple pieces of contract information in the contract information specification field 313 corresponds to the contractor of the content image 100C. Then, the shared information field 314 displays information of the contractor who shares the content image 100C.

The approver input field 315 is a field for inputting information about an approver who approves an applicant's request to share the content image 100C. Note that identification information such as alphanumeric characters that can uniquely identify the approver may be input into the approver input field 315.

Furthermore, the application screen 300 includes a content confirmation button 321, a contract confirmation button 322, an application condition specification button 323, and an acceptance button 324.

The content confirmation button 321 is a button image for confirming the contents of the content image 100C specified by the applicant. When the content confirmation button 321 is pressed, the content image 100C is displayed on the screen of the terminal device.

The contract confirmation button 322 is a button image for confirming the contents of the contract information selected by the applicant. When the contract confirmation button 322 is pressed, the contract document information is displayed on the screen of the terminal device.

The application condition specification button 323 is a button image for accepting specifications from the applicant regarding the handling of the content image 100C. When the application condition specification button 323 is pressed, a reception screen (not shown) for accepting the specification of the usage conditions of the content image 100C is displayed on the screen. The reception screen allows the applicant to select from a number of options, similar to the usage conditions input field of the registration form screen 200. Note that if the usage conditions specified by the applicant do not satisfy the conditions of the contract information, a warning is issued to the applicant.

Next, the operation of the content management system 1 of this embodiment will be specifically described.
First, the operation when registering contract information in the blockchain system 30 will be described.
FIG. 9 is a sequence diagram showing the process of registering contract information in the blockchain system 30.

As shown in Fig. 9, contract information is accepted from the registration form screen 200 (see Fig. 7) displayed on the first terminal device 10 (S901). The contract information is created individually for each individual or company that concludes a contract. The first terminal device 10 transmits the contract information accepted on the registration form screen 200 to the server device 50 (S902).
The server device 50 also creates registered contract information based on the received contract information (S903). The server device 50 then requests the blockchain system 30 to register the registered contract information as a transaction (S904).

The blockchain system 30 registers the transaction of the registered contract information in the blockchain (S905). The blockchain system 30 also transmits the transaction hash of the registered registered contract information to the server device 50 (S906). In this manner, the contract information accepted on the registration form screen 200 is registered in the blockchain system 30.
Then, the server device 50 associates and manages the transaction hash obtained from the blockchain system 30 with the contract information (S907).

The server device 50 also creates contract document information based on the received contract information (S908). Meanwhile, the first terminal device 10 requests the server device 50 to transmit the contract document information (S909). In response to the request from the first terminal device 10, the server device 50 transmits the created contract document information (S910). In this way, the contract information received on the registration form screen 200 becomes available for download as a user-readable document.

As described above, in the content management system 1 of this embodiment, registered contract information is registered in the blockchain system 30. This registered contract information is created according to each individual contract. Therefore, multiple pieces of registered contract information are registered in the blockchain system 30.

Next, an operation for sharing the content image 100C will be described.
FIG. 10 is a sequence diagram when the content image 100C is shared.

As shown in FIG. 10, application information is accepted from the application screen 300 of the first terminal device 10 (S1001). Then, the first terminal device 10 transmits the accepted application information to the server device 50 (S1002). In this embodiment, the applicant user only needs to specify contract information according to the sharer with whom the content image 100C is to be shared. This allows, for example, the user to share the content image 100C without being required to closely examine the contract details. In other words, the content management system 1 of this embodiment can significantly reduce the workload of the applicant user.

The first terminal device 10 also transmits the content image 100C to the server device 50 (S1003). If the content image 100C that the user wishes to share is stored in advance in the server device 50, the content image 100C specified in the application information is used.

Then, the server device 50 requests the blockchain system 30 to register the application information as a transaction (S1004).
The blockchain system 30 registers the transaction of the application information in the blockchain (S1005). The application information includes information such as selected contract identification information that identifies the selected contract information, application identification information, and applicant information making the application. In other words, the selected contract information and application identification information are registered in the blockchain of the blockchain system 30 in a state that makes it almost impossible to tamper with them.

Thereafter, the blockchain system 30 transmits a transaction hash of the registered contract information to the server device 50 (S1006).
Meanwhile, the server device 50 adds the transaction acquired from the block chain system 30 to the content image 100C as an embedded image 100H, and creates the shared image 100 (see FIG. 2A) (S1007). Furthermore, the server device 50 generates a hash value of the shared image 100 (S1008). Then, the server device 50 requests the block chain system 30 to register registration information including the hash value of the shared image 100 and the application identification information of the application information as a transaction (S1009).

The blockchain system 30 registers the transaction of the registration information in the blockchain (S1010). Note that the server device 50 can obtain the transaction hash of the registration information.
In this manner, in the content management system 1 of this embodiment, the hash value of the shared image 100 is associated with the contract identification information and the application information and registered in the blockchain system 30 .

The server device 50 also transmits the created shared image 100 to the first terminal device 10 (S1011). For example, when the user actually wants to share the content image 100C, the shared image 100 with the embedded image 100H added to the content image 100C is shared.

Next, the operation during verification will be described.
FIG. 11 is a flowchart showing the process of verifying the shared image 100 according to this embodiment.

For example, it is assumed that a person who is not intended to use the content image 100C has made the content image 100C public. In this case, the target image is transmitted from the first terminal device 10 to the server device 50, for example.
11, the server device 50 reads the embedded image 100H added to the image to be verified (S1101). The verification unit 55 detects the embedded image 100H composed of pixels with RGB values different from those of the surrounding pixels, as described above.

The server device 50 identifies the transaction hash from the embedded image 100H (S1102).
Furthermore, the server device 50 acquires transaction information corresponding to the transaction hash from the block chain system 30 (S1103). This transaction information includes application information including contract identification information and application identification information.

Then, the server device 50 refers to the registered contract information corresponding to the contract identification information from the blockchain system 30 (S1104). This registered contract information includes information such as contractor information corresponding to the sharer and the terms of use of the content image 100C. The server device 50 displays the registered contract information to the user on the screen of the first terminal device 10, for example. Then, by referring to the registered contract information, it is possible to verify whether the content image 100C has been made public in the manner originally intended.

Next, it is verified whether the content image 100C of the target image has been tampered with.
The server device 50 generates a hash value of the target image (S1105).
Furthermore, the server device 50 refers to the registration information corresponding to the application identification information from the blockchain system 30 (S1106). This registration information includes information on the hash value of the shared image 100.

Then, the server device 50 compares the hash value of the target image with the hash value of the shared image 100 obtained from the blockchain system 30 (S1107). If the hash values match (Yes in S1107), it is determined that the contents of the content image 100C are the same (S1108). On the other hand, if the hash values do not match (No in S1107), it is determined that the contents of the content image 100C are different (S1109).

The server device 50 may output the determination result, such as whether or not the sharer identified from the target image matches the publisher of the target image, or whether or not the content image 100C matches, in the form of expressions such as "suitable" or "not suitable." Examples of the output include displaying the results on a web screen, sending the results by email, and printing out the determination results in writing.

As described above, the content management system 1 of this embodiment makes it possible to identify information regarding the handling of the content image 100C, such as the scope of disclosure, from an image that contains the content image 100C to be verified. Furthermore, the content management system 1 of this embodiment makes it possible to verify whether the content image 100C itself has been altered or replaced.

<Modification>
In addition, when registering the contract information, the contract management unit 51 of the present embodiment accepts specific information input by the user from the registration form screen 200 (see FIG. 7 ), but is not limited to this. The contract management unit 51 may create the contract information based on, for example, character information of a paper contract or an electronic contract in which the contract contents are described.

<Modification>
In the present embodiment, the content management unit 53 processes and changes a part of the content image 100C to represent the embedded image 100H such as the transaction hash in the content image 100C, but is not limited to this. The content management unit 53 may represent an image such as the transaction hash for the first time when generating the content image 100C. In other words, the generation unit that generates the image may generate the content image 100C on the premise that the embedded image 100H is represented.

<Modification>
The blockchain system 30 may automatically determine whether the condition application information satisfies the conditions of the contract information without the user or the server device 50. In this case, a so-called smart contract function (an example of a determination means) in the blockchain system 30 is used. For example, when an applicant specifies the handling conditions of the content image 100C as the condition application information, an algorithm for determining whether the application content satisfies the conditions set in the contract information is built into the blockchain system 30 in advance. In this way, the blockchain system 30 may determine whether the conditions regarding the handling of the content image 100C are satisfied.
In addition, when using a blockchain smart contract, the embedded image 100H added to the content image 100C can use, for example, an identifier that can identify the smart contract.

<Modification>
The blockchain system 30 of this embodiment is an example of an open network, but is not limited to this. For example, when the blockchain system 30 is configured as a private network, specific names such as the company name and user name in the contract can be used as they are. This makes it possible to keep detailed information in the contract information secret from the outside.
On the other hand, by configuring the blockchain system 30 as an open network, anyone can check the contents of the content image 100C when verifying the content image 100C. This ensures the transparency of the information added to the shared image 100, and makes it possible to increase the reliability of the system.

<Modification>
In this embodiment, the contract information is registered in the block chain system 30, but the contents of this contract may be made changeable (editable).
In this case, the changed contract information is newly registered in the blockchain system 30. At this time, the contract identification number of the contract information before the change is associated with the changed contract information and managed in the blockchain system 30. In this way, it is possible to change the contract information and to maintain continuity of the contract information before and after the change.

<Modification>
In the content management system 1 of the present embodiment, the content image 100C is used as an object to be shared, but the target information to be shared is not limited to the content image 100C.

The target information may be a video. The video may be in a data format such as MP3. The video is composed of a plurality of frame images. The content management system 1 adds an embedded image 100H and a mark image 100M to the frame images, similar to the shared image 100 described above. The frame images into which the embedded image 100H is embedded may be all of the frame images constituting the video, or may be some of the frame images among the frame images constituting the video.
In other words, the content management system 1 accepts handling information regarding the handling of the video, registers the handling information in the blockchain, obtains specific information that can identify the handling information registered in the blockchain, and adds the specific information to the frame images that make up the video.

The target information may be an audio file. The audio file may be in a data format such as MP4. The audio file includes information that can be recognized by hearing, such as musical instruments, singing, and human voices such as conversation. The content management system 1 embeds specific information into the music file as an audio watermark without compromising the original audio content. The audio watermark expresses information such as a character string on audio data by, for example, changing the frequency of the sound that constitutes the audio file based on a predetermined rule. The content management system 1 adds transaction hash information corresponding to the embedded image 100H to the audio file as an audio watermark. The content management system 1 also divides the audio file into an arbitrary number of parts, and embeds transaction hashes into the divided interval periods.
In other words, the content management system 1 accepts handling information regarding the handling of audio files, registers the handling information in the blockchain, obtains specific information that can identify the handling information registered in the blockchain, and adds the specific information to the audio file.

The target information may be an uneditable file that is not edited. The uneditable file is a file format that is, in principle, intended for viewing only, and the contents cannot be edited unless special editing software is used. An example of the uneditable file is a data format such as PDF (Portable Document Format). In addition, the content management system 1 adds a transaction hash corresponding to the embedded image 100H to the uneditable file using, for example, a digital signature function. The digital signature may be displayed, for example, in an image portion of the uneditable file that can be visually confirmed by the user, or may be written in a metadata structure portion that is separate from the image portion, for example, in which file profile information is stored.
In other words, the content management system 1 accepts handling information regarding the handling of uneditable files, registers the handling information in the blockchain, obtains specific information that can identify the handling information registered in the blockchain, and adds the specific information to the uneditable files.

Here, the content management system 1 is an example of an information processing system. The server device 50 is an example of an information processing device. The content image 100C is an example of a target image and target information. The embedded image 100H is an example of a specific image, specific information, and transaction image. The mark image 100M is an example of a suggestion image. The contract management unit 51 is an example of a reception means and an output means. The content management unit 53 is an example of a registration means, an acquisition means, an addition means, a generation means, a first registration means, an image generation means, and a second registration means. The verification unit 55 is an example of an image acquisition means, a reading means, and an information output means.

Furthermore, although various embodiments and modifications have been described above, these embodiments and modifications may be combined together to form a configuration.
Furthermore, the present disclosure is not limited to the above-described embodiments, and can be embodied in various forms without departing from the gist of the present disclosure.

1...content management system, 10...first terminal device, 20...second terminal device, 30...blockchain system, 50...server device, 51...contract management unit, 53...content management unit, 55...verification unit, 100C...content image, 100M...mark image, 100H...embedded image, 100...shared image

Claims (15)

A receiving means for receiving handling information regarding the handling of the target image to be shared;
A registration means for registering the handling information in a blockchain;
An acquisition means for acquiring specific information capable of identifying the handling information registered in the blockchain;
adding means for adding the specific information to the target image;
An information processing system comprising: The information processing system according to claim 1, characterized in that the handling information includes sharing information regarding the sharers who share the target image. The information processing system according to claim 1, characterized in that the adding means adds a transaction hash when the handling information is registered in the blockchain to the target image. The adding means adds a specific image indicating the specific information and a suggestion image suggesting that the specific information has been added to the target image,
2. The information processing system according to claim 1, wherein the specific image is displayed in an invisible or difficult to see manner, and the suggestive image is displayed in a visible or easily visible manner. a generation means for generating a hash value of the target image to which the specific information is added,
The information processing system according to claim 1 , wherein the registration means registers registration information in the blockchain that associates hash information regarding the hash value with the handling information. A plurality of different pieces of handling information are registered in the blockchain,
The information processing system according to claim 1, characterized in that the registration means registers the target image in association with one of the handling information selected from the multiple handling information registered in the blockchain. The information processing system according to claim 1, further comprising an output means for outputting the handling information to be registered in the blockchain and document information that documents the input information, using input information received from a user. The information processing system according to claim 1, characterized in that the registration means acquires information regarding changes to the handling information, and associates the handling information before the change with the handling information after the change and registers them in the blockchain. The information processing system according to claim 1, further comprising an information output means for outputting the contents of the handling information corresponding to the specific information included in the target image, based on the specific information. The information processing system according to claim 1, further comprising a determination means for determining whether the handling conditions of the target image specified by the user satisfy predetermined conditions on the blockchain system that forms the blockchain. A receiving means for receiving sharing information related to a sharer of a target image to be shared;
A first registration means for registering the shared information in a blockchain;
An acquisition means for acquiring a transaction hash capable of identifying the shared information registered in the blockchain;
an image generating means for generating a transaction image that displays the transaction hash in an invisible or difficult to see manner, a suggestion image that suggests in a visible or easily visible manner that the transaction hash is included in the target image, and a shared image using the target image;
A second registration means for registering a hash value generated from the shared image and the shared information in the blockchain in association with each other;
An information processing system comprising: An information processing system comprising: a receiving means for receiving handling information regarding the handling of target information to be shared; a registering means for registering the handling information in a blockchain; an acquiring means for acquiring specific information capable of identifying the handling information registered in the blockchain; and an adding means for adding the specific information to the target information. An acquisition means for acquiring specific information capable of identifying handling information regarding the handling registered in the blockchain of the target image to be shared;
an image generating means for generating a shared image using the target image and the specific information;
An information processing device comprising: On the computer,
A function to obtain specific information that can identify handling information registered on the blockchain of the target image to be shared; and
A function of generating a shared image using the target image and the specific information;
A program to achieve this. An image acquisition means for acquiring a target image to be shared;
A reading means for reading specific information capable of identifying handling information regarding the handling of the target image registered in the block chain from the target image;
An information output means for outputting the handling information registered in the blockchain based on the specific information;
An information processing device comprising:

Images