Program, information processing method, and information processing device

The use of a blockchain-based system for recording rights percentage agreements in collaborative production applications addresses the challenge of ensuring the integrity and validity of agreements among creators, enhancing the security and transparency of negotiations for jointly produced works.

WO2024247462A1PCT designated stage expired Publication Date: 2024-12-05SONY GROUP CORP +1
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/012116
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-26
Filing Date
2024-03-26
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Negotiating and recording the rights percentage for jointly produced copyrighted works among multiple creators is challenging due to the lack of a secure and integrity-guaranteed method, leading to difficulties in ensuring the validity and completeness of agreements.

Method used

A system that utilizes a blockchain to record and verify the rights percentage agreements among creators through a collaborative production application, ensuring the integrity and validity of the contract terms and rights ratios by generating and recording information on a distributed ledger.

Benefits of technology

This approach provides a secure and transparent method for negotiating and recording rights percentages, ensuring the legitimacy and completeness of agreements, thereby reducing disputes related to jointly produced works.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024012116_05122024_PF_FP_ABST
    Figure JP2024012116_05122024_PF_FP_ABST
Patent Text Reader

Abstract

Provided is a program for causing a computer to function as: an acquisition unit that acquires, via a chat between producers of a collaborative product, information relating to the ratio of rights of the producers; an information generation unit that generates information for recording the information relating to the ratio of rights in a blockchain; and an agreement generation unit that generates an agreement relating to the ratio of rights on the basis of the information relating to the ratio of rights and the agreement status of each of the producers with respect to the ratio of rights.
Need to check novelty before this filing date? Find Prior Art

Description

Program, information processing method, and information processing device

[0001] The present disclosure relates to a program, an information processing method, and an information processing device.

[0002] In recent years, there has been a study into using blockchain to leave evidence of contracts exchanged between multiple parties (see, for example, Patent Document 1 below).

[0003] A blockchain is a transaction ledger made up of blocks that store records of transactions, called transactions, linked together like a chain. Blockchain can ensure the integrity of transaction content through a consensus-building process within the network. Therefore, by recording information about contracts and agreements to contracts as transactions on the blockchain, it is possible to ensure the integrity of the contract content and leave evidence of agreement to the contract content.

[0004] JP 2017-220710 A

[0005] When multiple creators collaborate on the creation of a work, it is possible that each creator will jointly own the rights to the resulting work. In such cases, it is important for the creators to negotiate the rights ratios and determine the respective rights ratios before creating the work. However, when rights ratios are negotiated verbally or via email, it is difficult to leave a complete record of the agreement on the rights ratios for the resulting work.

[0006] Therefore, there was a need to leave evidence of agreements regarding the rights division of collaborative works created by multiple creators using a means that ensures integrity, such as blockchain.

[0007] According to the present disclosure, a program is provided to cause a computer to function as an acquisition unit that acquires information regarding the right shares of each creator of a collaborative work through chat between the creators, an information generation unit that generates information for recording the information regarding the right shares in a blockchain, and an agreement generation unit that generates an agreement regarding the right shares based on the information regarding the right shares and the agreement status of each creator regarding the right shares.

[0008] Furthermore, according to the present disclosure, there is provided a computer-based information processing method including: obtaining information regarding the right shares of each creator of a collaborative work via chat between the creators; generating information for recording the information regarding the right shares in a blockchain; and generating an agreement regarding the right shares based on the information regarding the right shares and the agreement status of the creators regarding the right shares.

[0009] Furthermore, according to the present disclosure, an information processing device is provided that includes an acquisition unit that acquires information regarding the right shares of each creator of a collaborative work through chat between the creators, an information generation unit that generates information for recording the information regarding the right shares in a blockchain, and an agreement generation unit that generates an agreement regarding the right shares based on the information regarding the right shares and the agreement status of each creator regarding the right shares.

[0010] 1 is a block diagram illustrating an overall overview of an information processing system according to an embodiment of the present disclosure. FIG. 1 is a block diagram illustrating the functional configuration of a collaborative production application. FIG. 2 is a diagram illustrating an example of an application image presented to a creator by the collaborative production application. FIG. 3 is a sequence diagram illustrating the operation of an information processing system from the start of a collaborative production project to recording information regarding contract terms in a blockchain. FIG. 4 is a diagram illustrating an example of an image displayed in a decision area of ​​an application image when a first creator inputs a right ratio. FIG. 5 is a diagram illustrating an example of an image displayed in a decision area of ​​an application image when a second creator and a third creator agree or reject the right ratio. FIG. 6 is a diagram illustrating an example of an image displayed in a communication area of ​​an application image regarding negotiation of contract terms. FIG. 7 is a diagram illustrating an example of an image displayed in a communication area of ​​an application image regarding agreement on contract terms. FIG. 8 is a sequence diagram illustrating the operation of an information processing system that records information regarding agreement to contract terms in a blockchain. FIG. 9 is a sequence diagram illustrating the operation of an information processing system when recording the final product of a collaborative production and information regarding agreement to the final product in a blockchain. FIG. 10 is a diagram illustrating an example of an image displayed in the decision area of ​​an application image when a first creator decides on the final product. FIG. 11 is a diagram illustrating an example of an image displayed in the decision area of ​​an application image when a second creator and a third creator agree or reject the final product. FIG. 1 is a sequence diagram showing the operation of an information processing system when creating a split sheet. FIG. 2 is a diagram showing an example of an image displayed in the decision area of ​​an application image when a first creator readjusts the right ratio when creating a split sheet. FIG. 3 is a diagram showing an example of an image displayed in the decision area of ​​an application image when a second creator and a third creator agree to or reject the readjusted right ratio. FIG. 4 is a diagram showing an example of an image displayed in the communication area of ​​an application image regarding the creation of a split sheet. FIG. 5 is a diagram showing an example of a split sheet created. FIG. 6 is a sequence diagram showing the operation of an information processing system when creating a split sheet when the minimum right ratio is guaranteed.Fig. 1 is a block diagram showing an example of the hardware configuration of an information processing device on which a collaboration application runs. Fig. 2 is a block diagram explaining an overview of information processing according to a modified example. Fig. 3 is a block diagram explaining an overview of collaboration according to a modified example. Fig. 4 is a flowchart (1) showing a processing procedure according to a modified example. Fig. 5 is a flowchart (2) showing a processing procedure according to a modified example. Fig. 6 is a flowchart (3) showing a processing procedure according to a modified example. Fig. 7 is a flowchart (4) showing a processing procedure according to a modified example.

[0011] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant description will be omitted.

[0012] The explanation will be given in the following order: 1. Overall configuration of the information processing system 2. Configuration of the collaborative production application 3. Images presented by the collaborative production application 4. Operation of the information processing system 4.1. Recording the contractual conditions of the collaborative production on the blockchain 4.2. Recording the collaborative production on the blockchain 4.3. Issuance of a split sheet 4.4. Cases where the minimum rights ratio is guaranteed 4.5. Supplementary notes 5. Hardware configuration 6. Modified examples 6.1. Background 6.2. Pre-registration of the production on the blockchain 6.3. Mode of collaborative production 6.4. Example of processing procedure related to the modified examples 6.5. System configuration related to the modified examples 6.6. Effects of the modified examples

[0013] 1. Overall Configuration of Information Processing System An overall overview of an information processing system according to an embodiment of the present disclosure will be described with reference to Fig. 1. Fig. 1 is a block diagram illustrating an overall overview of an information processing system 10 according to this embodiment.

[0014] As shown in FIG. 1 , the information processing system 10 includes a collaborative production application 100 , a DB storage unit 400 , a management system 200 , and a blockchain 300 .

[0015] The collaborative production application 100 is a program used among multiple creators Cr who are engaged in collaborative production. For example, the collaborative production application 100 provides a communication interface for the multiple creators Cr to set, negotiate, and agree on the content of a contract regarding the production of a collaborative work. The collaborative production application 100 may also provide a communication interface for the multiple creators Cr to exchange messages and data when producing a collaborative work.

[0016] Furthermore, the collaborative application 100 can generate an agreement (also called a split sheet) that describes the right percentages for each creator Cr in a collaborative work agreed upon among multiple creators Cr. This allows a creator Cr who is involved in a collaborative work to negotiate the right percentages for the collaborative work with other creators Cr via the collaborative application 100 and to document the right percentages agreed upon in the negotiations as a split sheet.

[0017] The DB storage unit 400 stores an agreement (split sheet) that describes the rights ratio for each creator Cr of a collaborative work agreed upon among multiple creators Cr. The legitimacy and completeness of the content of the split sheet stored in the DB storage unit 400 is guaranteed by the blockchain 300, which will be described later. The DB storage unit 400 may also store a contract regarding the production of the collaborative work.

[0018] The management system 200 is a system that manages transactions to the blockchain 300. The management system 200 records information that proves the legitimacy and completeness of the content of a split sheet for a collaborative work as a transaction in the blockchain 300. For example, the management system 200 may record information regarding the right percentage for each creator Cr of an agreed-upon collaborative work as a transaction in the blockchain 300. This allows the management system 200 to verify the legitimacy and completeness of the content of the split sheet generated by the collaborative application 100 (i.e., the right percentage for each creator Cr of the collaborative work) based on the information recorded in the blockchain 300.

[0019] In addition, the management system 200 may record the contents of a contract regarding the production of a collaborative work or information regarding the produced collaborative work in the blockchain 300 as a transaction.

[0020] The blockchain 300 is a distributed ledger managed on a peer-to-peer network. Information on the right share of each creator Cr of a collaborative work, which is information that proves the legitimacy and integrity of the contents of the split sheet, is recorded as a transaction in a block of the blockchain 300. Since the information recorded in the blockchain 300 is difficult to tamper with, the creator Cr of a collaborative work can guarantee the legitimate right share of the collaborative work that he or she owns by using the information recorded in the blockchain 300 as evidence.

[0021] According to the information processing system 10 of this embodiment, the creator Cr of a collaborative work can leave evidence of their own right share in the collaborative work and of the agreement on the right share on the blockchain 300. Therefore, the creator Cr of the collaborative work can legitimately guarantee their own right share in the collaborative work. Therefore, the information processing system 10 of this embodiment can reduce problems regarding the rights of collaborative works created by multiple creators Cr.

[0022] 2. Configuration of Collaborative Production Application The functional configuration of the collaborative production application 100 will be described with reference to Fig. 2. Fig. 2 is a block diagram showing the functional configuration of the collaborative production application 100.

[0023] As shown in FIG. 2, the collaboration application 100 includes a timeline generation unit 120 , an acquisition unit 130 , an information generation unit 140 , and an agreement generation unit 150 .

[0024] The timeline generation unit 120 generates a chat-style timeline on which messages and data are exchanged between multiple creators Cr who are engaged in collaborative production. Specifically, the timeline generation unit 120 may generate a timeline on which messages and data sent by the creator Cr who operates the collaborative production application 100 are displayed on one side, and messages and data sent by other creators Cr are displayed on the other side. This allows the collaborative production application 100 to display a history of message and data exchange between the multiple creators Cr in chronological order.

[0025] The timeline log generated by the timeline generation unit 120 may be stored, for example, in the DB storage unit 400. This allows multiple creators Cr to later check and verify the interactions during collaborative production and the status of the interactions.

[0026] The acquisition unit 130 acquires information regarding the right percentage for each creator Cr of the collaborative work via chat between the creators Cr on the timeline generated by the timeline generation unit 120. The right percentage for each creator Cr of the collaborative work may be negotiated between the creators Cr via chat. The right percentage for each creator Cr of the collaborative work may be expressed, for example, as a percentage where the total of the right percentages is 100, or as a ratio where the total of the right percentages does not equal 100.

[0027] The information generating unit 140 generates information for recording information about the right ratio of the collaborative work acquired by the acquiring unit 130 in the blockchain 300. Based on the information generated by the information generating unit 140, the management system 200 can record information about the right ratio of the collaborative work in the blockchain 300 as a transaction.

[0028] Furthermore, the information generating unit 140 may further generate information for recording information regarding the agreement status of each of the creators Cr regarding the right share of the collaborative work in the blockchain 300. Based on the information generated by the information generating unit 140, the management system 200 can record information indicating that each of the creators Cr has agreed to the right share of the collaborative work in the blockchain 300 as a transaction.

[0029] Furthermore, when the agreed-upon right percentage of the collaborative work is readjusted, the information generating unit 140 may further generate information for recording information about the readjusted right percentage of the collaborative work in the blockchain 300. The information generating unit 140 may further generate information for recording information about the agreement status of each creator Cr regarding the readjusted right percentage of the collaborative work in the blockchain 300. In this way, the information generating unit 140 can generate information for recording the history of the setting, agreement, readjustment, and agreement after the readjustment of the right percentage of the collaborative work in the blockchain 300.

[0030] In addition, after the production of the collaborative work is completed, the information generator 140 may further generate information for recording information about the final product of the collaborative work in the blockchain 300. The final product of the collaborative work is determined based on the agreement of each of the creators Cr. The information about the final product of the collaborative work may include identification information of the collaborative work, identification information of the creators Cr of the collaborative work, and a hash value of the final product.

[0031] The agreement generation unit 150 generates a split sheet for the collaborative product based on information about the right shares of the collaborative product and the agreement status of each of the creators Cr regarding the right shares. Specifically, when a right share is set for each of the creators Cr of the collaborative product and the set right share is agreed upon by each of the creators Cr, the agreement generation unit 150 generates a split sheet indicating the agreed right shares of the collaborative product.

[0032] Information regarding the right share for each creator Cr of the collaborative work and information regarding the agreement status of each creator Cr regarding the right share are recorded in the blockchain 300. Therefore, the contents of the split sheet generated by the agreement generation unit 150 can be verified for completeness and legitimacy from the information recorded in the blockchain 300.

[0033] The collaborative production application 100 including the above configuration enables multiple creators Cr to smoothly carry out collaborative production by exchanging messages and data between them on a chat-style timeline.

[0034] Furthermore, the collaborative application 100 can record information regarding the right percentage for each creator Cr of the collaborative work and information regarding the agreement status of each creator Cr regarding the right percentage in the blockchain 300 via the management system 200. This allows the collaborative application 100 to leave evidence of the right percentage for each creator Cr of the collaborative work and the agreement status of each creator Cr regarding the right percentage on the blockchain 300. Therefore, the creator Cr of the collaborative work can prove the completeness and validity of the split sheet that describes the right percentage for the collaborative work by referring to the information recorded in the blockchain 300.

[0035] 3. Image Presented by Collaborative Production Application Now, an image presented by the collaborative production application 100 to the creator Cr will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of an application image 500 presented by the collaborative production application 100 to the creator Cr.

[0036] As shown in FIG. 3, an application image 500 presented by the collaborative production application 100 to the producer Cr ("AA" in FIG. 3) includes a project selection area 510, a member display area 520, a communication area 530, and a decision area 540.

[0037] The project selection area 510 is an area for switching the content of the project displayed in the member display area 520, communication area 530, and decision area 540. The project selection area 510 displays, in tab format, each of the collaborative projects in which the creator Cr ("AA" in FIG. 3) is participating. The creator Cr can switch the content of the project displayed in the member display area 520, communication area 530, and decision area 540 by selecting a tab displayed in the project selection area 510.

[0038] 3 displays three collaborative projects, "Pj_01," "Pj_02," and "Pj_03," in which the creator Cr ("AA" in FIG. 3) is participating. The creator Cr can switch the content displayed in the member display area 520, communication area 530, and decision area 540 by selecting the tabs "Pj_01," "Pj_02," and "Pj_03" in the project selection area 510, respectively. Note that in the application image 500 of FIG. 3, "Pj_02" is selected, and the content of "Pj_02" is displayed in the member display area 520, communication area 530, and decision area 540.

[0039] In addition, in the project selection area 510, a check mark may be placed on a completed project ("Pj_01" in FIG. 3), and an icon representing the number of unread messages may be placed on a project ("Pj_03" in FIG. 3) that has unread messages.

[0040] The member display area 520 is an area that displays, with icons, the members participating in the project selected in the project selection area 510. In the application image 500 of Fig. 3, the member who started the project (director "AA") is displayed with an "A" icon, the members who will be collaborating (co-producers "AA", "BB", and "CC") are displayed with "A", "B", and "C" icons, and the member who can view the contents of the project without participating in the collaborating (viewer "DD") is displayed with a "D" icon.

[0041] The communication area 530 displays a chat-style timeline generated by the timeline generation unit 120. Specifically, the communication area 530 displays messages and data exchanged between multiple creators Cr who are collaborating in a chronological order. In the communication area 530, messages and data sent by a creator Cr ("AA" in FIG. 3) are displayed on one side, and messages and data sent by other creators Cr ("BB" and "CC" in FIG. 3) are displayed on the other side.

[0042] The decision area 540 is an area for deciding the contractual terms of the collaborative project. For example, in the decision area 540, the contractual terms of the collaborative project, including the rights ratio of the collaborative product, are entered by the member (director) who initiated the project in the "1. Collaborative Production Agreement" item. Furthermore, in the "2. Decide Product" item, the final product of the collaborative product is decided after the collaborative production is completed. Furthermore, in the "3. Issue Split Sheet" item, an instruction is entered to issue a split sheet indicating the rights ratio of the collaborative product.

[0043] The contract terms entered in the "1. Co-production Agreement" section are, for example, "rights share priority at the time of contract," "rights share readjustment," or "minimum rights share guaranteed." The "rights share priority at the time of contract" is a contract term that determines the rights share of each producer Cr before the co-production. The "rights share readjustment" is a contract term that determines the rights share of each producer Cr before the co-production and allows for readjustment of each rights share after the co-production. The "minimum rights share guaranteed" is a contract term that determines the rights share and minimum rights share of each producer Cr before the co-production and guarantees a rights share equal to or higher than the minimum rights share when readjusting each rights share after the co-production. The member (director) who launched the project can select and enter the contract terms, including the rights share of each producer Cr, from the above.

[0044] The collaborative production application 100 can support collaborative production by a plurality of creators Cr via the application image 500 described above.

[0045] 4. Operation of the Information Processing System (4.1. Recording of contract terms of a collaborative work in the blockchain) The operation of the information processing system 10 from the start of a collaborative project to recording information about the contract terms and information about agreement to the contract terms in the blockchain 300 will be described with reference to FIGS. 4 to 9.

[0046] FIG. 4 is a sequence diagram illustrating the operation of the information processing system 10 from the start of a collaborative project to recording information regarding contract terms in the blockchain 300. FIG. 5 is a diagram showing an example of an image displayed in the decision area 540 of the application image 500 when the first creator Cr1 inputs the rights ratio. FIG. 6 is a diagram showing an example of an image displayed in the decision area 540 of the application image 500 when the second creator Cr2 and the third creator Cr3 agree or reject the rights ratio. FIG. 7 is a diagram showing an example of an image displayed in the communication area 530 of the application image 500 regarding negotiation of contract terms. FIG. 8 is a diagram showing an example of an image displayed in the communication area 530 of the application image 500 regarding agreement on contract terms.

[0047] 4, first, a collaborative project is created by a first creator Cr1 (director) in the collaborative application 100 (S102). Subsequently, a notification informing the second creator Cr2 and a third creator Cr3, who have been selected as participating members (co-creators) of the created project, of the creation of the project is sent (S104, S106).

[0048] Next, the first creator Cr1 inputs contract terms, including the right percentages of the collaborative work, into the collaborative application 100 (S108). Specifically, the first creator Cr1 inputs contract terms of "contract-time right percentage priority type," "right percentage readjustment type," or "minimum right percentage guaranteed type" in the decision area 540 of the application image 500, and may further input the right percentages of each creator Cr for the collaborative work. For example, the first creator Cr1 "AA" may input the right percentages of the first creator Cr1 "AA," the second creator Cr2 "BB," and the third creator Cr3 "CC" as equal percentages of "33.3%," as shown in image 541 in FIG. 5 .

[0049] Next, the second creator Cr2 acquires the contract terms including the right percentage for the collaborative product input by the first creator Cr1 via the collaborative application 100 (S110) and confirms the acquired right percentage (S112). Similarly, the third creator Cr3 acquires the contract terms including the right percentage for the collaborative product input by the first creator Cr1 via the collaborative application 100 (S114) and confirms the acquired right percentage (S116).

[0050] For example, the second creator Cr2 and the third creator Cr3 are presented with the right percentages for the collaborative product entered by the first creator Cr1 in image 542 shown in Fig. 6. The second creator Cr2 and the third creator Cr3 can indicate whether they accept or reject the presented right percentages for the collaborative product by selecting either "Accept" or "Reject and request revision" in image 542 shown in Fig. 6.

[0051] Here, it is assumed that the third creator Cr3 selects "Reject and request revision" in image 542 shown in Fig. 6. The selection of "Reject and request revision" by the third creator Cr3 "CC" is communicated to the first creator Cr1 "AA" via the communication area 530, as shown in image 531 shown in Fig. 7. Thereafter, the third creator Cr3 "CC" can negotiate the desired rights ratio with the first creator Cr1 "AA" via chat in the communication area 530 (S118).

[0052] The first creator Cr1 receives the negotiation details from the third creator Cr3 via the communication area 530 of the collaborative application 100 (S120) and confirms the negotiation details (S122). As a result, the first creator Cr1 updates the rights ratio of the collaborative product input into the decision area 540 of the collaborative application 100 (S124).

[0053] After updating the right share, the third creator Cr3 acquires the updated right share via the collaborative application 100 (S126), confirms the acquired right share (S128), and then agrees to the updated right share (S130). Similarly, the second creator Cr2 acquires the updated right share via the collaborative application 100 (S132), confirms the acquired right share (S134), and then agrees to the updated right share (S136).

[0054] Next, the first creator Cr1 registers the contract terms, including the agreed-upon right ratio, in the collaborative production application 100 (S140). This allows the collaborative production application 100 to record information about the contract terms, including the agreed-upon right ratio, in the blockchain 300 via the management system 200 (S142). When recording of the information about the contract terms in the blockchain 300 is complete, the collaborative production application 100 may notify the first creator Cr1 "AA," the second creator Cr2 "BB," and the third creator Cr3 "CC" in the communication area 530 that the agreed-upon contract terms have been established, as shown in image 532 in FIG. 8 .

[0055] Through the above operations, the information processing system 10 can perform operations from the start of a collaborative project to recording information about the contract terms in the blockchain 300. Therefore, the information processing system 10 can record information about the contract terms, including the right ratio of the collaborative work, in the blockchain 300.

[0056] FIG. 9 is a sequence diagram illustrating the operation of the information processing system 10 for recording information regarding agreement to the contract terms in the blockchain 300.

[0057] As shown in FIG. 9, after the contract terms are recorded in the blockchain 300 (S142), the first producer Cr1, the second producer Cr2, and the third producer Cr3 each agree to the contract terms.

[0058] Specifically, the first creator Cr1 records information about the contract terms in the blockchain 300 (S142), and then inputs agreement to the contract terms in the collaborative production application 100 (S150). This enables the collaborative production application 100 to record the first creator Cr1's agreement to the contract terms in the blockchain 300 via the management system 200 (S152).

[0059] Furthermore, the second creator Cr2 acquires the contract terms via the collaborative application 100 (S154), confirms the acquired contract terms (S156), and then inputs his / her agreement to the contract terms into the collaborative application 100 (S158). This allows the collaborative application 100 to record the second creator Cr2's agreement to the contract terms in the blockchain 300 via the management system 200 (S160). Similarly, the third creator Cr3 acquires the contract terms via the collaborative application 100 (S162), confirms the acquired contract terms (S164), and then inputs his / her agreement to the contract terms into the collaborative application 100 (S166). This allows the collaborative application 100 to record the third creator Cr3's agreement to the contract terms in the blockchain 300 via the management system 200 (S168).

[0060] Through the above operations, the information processing system 10 can record the agreement status of the creators Cr to the contract conditions, including the right shares of the collaborative work, in the blockchain 300. Therefore, by referring to the information recorded in the blockchain 300, the information processing system 10 can ensure that each of the creators Cr has agreed to the contract conditions.

[0061] Here, if the third creator Cr3 confirms the legitimacy and completeness of the contract terms, the third creator Cr3 confirms the contract terms with the collaborative application 100 (S170). The collaborative application 100 acquires information regarding the contract terms from the blockchain 300 via the management system 200 (S172). Next, the collaborative application 100 verifies the contract terms based on the information regarding the contract terms acquired from the blockchain 300 (S174). Thereafter, the collaborative application 100 notifies the third creator Cr3 of the contract terms and the verification results of the contract terms (S176). This allows the third creator Cr3 to confirm the contract terms, including the right ratio, and to confirm that the contract terms are agreed upon and legitimate, based on the information recorded in the blockchain 300.

[0062] (4.2. Recording of Collaborative Product in Blockchain) With reference to Figures 10 to 12, the operation of the information processing system 10 when recording the final product of the collaborative product and information regarding agreement on the final product in the blockchain 300 will be described.

[0063] Fig. 10 is a sequence diagram showing the operation of the information processing system 10 when recording the final product of the collaborative work and information regarding agreement on the final product in the blockchain 300. Fig. 11 is a diagram showing an example of an image displayed in the decision area 540 of the application image 500 when the first creator Cr1 decides on the final product. Fig. 12 is a diagram showing an example of an image displayed in the decision area 540 of the application image 500 when the second creator Cr2 and the third creator Cr3 agree or reject the final product.

[0064] 10 , after the production of the collaborative work is completed, the first creator Cr1 determines a final deliverable of the collaborative work and registers the determined final deliverable in the collaborative work application 100 (S202). This allows the collaborative work application 100 to record information about the final deliverable of the collaborative work in the blockchain 300 via the management system 200 (S204).

[0065] For example, the first creator Cr1 may determine the final product of the collaborative work in image 543 shown in Fig. 11. In image 543 shown in Fig. 11, a song is produced as the collaborative work, and the sound source of the song, "Melody A_1," and the lyrics, "Lyrics_Additional 1," are determined as the final product. Also, in image 543 shown in Fig. 11, the work title of the collaborative work, "This song," the names of the song's lyricists, "AA, BB, CC," and the names of the composers, "AA, BB, CC," are determined.

[0066] Next, the first creator Cr1 inputs his / her agreement on the final product of the collaborative work into the collaborative application 100 (S206). This allows the collaborative application 100 to record the first creator Cr1's agreement on the final product of the collaborative work in the blockchain 300 via the management system 200 (S208).

[0067] 12 is presented to the second producer Cr2 and the third producer Cr3. From the presented image 544, the second producer Cr2 and the third producer Cr3 can confirm the sound source of the song "Melody A_1," the song lyrics "Lyrics_Additional 1," the work title "This song," the names of the lyricists "AA, BB, CC," the names of the composers "AA, BB, CC," etc., which are the final product of the collaborative work.

[0068] The second creator Cr2, who has confirmed the final deliverable of the collaborative work, etc. in image 544 shown in FIG. 12 , inputs his / her agreement to the final deliverable of the collaborative work into the collaborative application 100 (S210). This allows the collaborative application 100 to record the second creator Cr2's agreement to the final deliverable in the blockchain 300 via the management system 200 (S212). Similarly, the third creator Cr3, who has confirmed the final deliverable of the collaborative work, etc. in image 544 shown in FIG. 12 , inputs his / her agreement to the final deliverable of the collaborative work into the collaborative application 100 (S214). This allows the collaborative application 100 to record the third creator Cr3's agreement to the contract terms in the blockchain 300 via the management system 200 (S216).

[0069] Through the above operations, the information processing system 10 can record information about the final product of the collaborative work and the status of the creators Cr's agreement on the final product in the blockchain 300. Therefore, by referring to the information recorded in the blockchain 300, the information processing system 10 can guarantee that each of the creators Cr has agreed to the final product of the collaborative work.

[0070] (4.3. Issuance of Split Sheet) The operation of the information processing system 10 when creating a split sheet in which the right percentage for each creator Cr of a collaborative work is described will be described with reference to FIGS.

[0071] FIG. 13 is a sequence diagram showing the operation of the information processing system 10 when creating a split sheet. FIG. 14 is a diagram showing an example of an image displayed in the decision area 540 of the application image 500 when the first creator Cr1 readjusts the right ratio when creating a split sheet. FIG. 15 is a diagram showing an example of an image displayed in the decision area 540 of the application image 500 when the second creator Cr2 and the third creator Cr3 agree to or reject the readjusted right ratio. FIG. 16 is a diagram showing an example of an image displayed in the communication area 530 of the application image 500 regarding the creation of a split sheet. FIG. 17 is a diagram showing an example of a created split sheet.

[0072] As shown in FIG. 13, first, the first creator Cr1 instructs the collaborative production application 100 to create a split sheet based on the contract conditions (S220).

[0073] Here, if the contract terms are "rights percentage readjustment type," the first creator Cr1 readjusts the rights percentages (S222). Specifically, as shown in image 545 in FIG. 14, the first creator Cr1 "AA" can readjust the rights percentages of the first creator Cr1 "AA," the second creator Cr2 "BB," and the third creator Cr3 "CC" from the initial equal division of "33.3%" when creating the split sheet. For example, the first creator Cr1 "AA" may change the rights percentage of the first creator Cr1 "AA" to "20%," the rights percentage of the second creator Cr2 "BB," and the rights percentage of the third creator Cr3 "CC" from the initial equal division of "33.3%" to "40%," respectively.

[0074] After the right percentage is readjusted, the readjusted right percentage is recorded in the blockchain 300 via the collaborative application 100 (S224). Thereafter, the first creator Cr1 inputs his / her agreement to the readjusted right percentage into the collaborative application 100 (S226). This allows the collaborative application 100 to record the first creator Cr1's agreement to the readjusted right percentage in the blockchain 300 via the management system 200 (S228).

[0075] The second creator Cr2 acquires the readjusted right percentage (S230) and confirms the readjusted right percentage (S232) via the collaborative production application 100. Similarly, the third creator Cr3 acquires the readjusted right percentage (S238) and confirms the readjusted right percentage (S240) via the collaborative production application 100.

[0076] The second creator Cr2 and the third creator Cr3 are presented with the readjusted right percentages entered by the first creator Cr1 in, for example, image 546 shown in Fig. 15. For example, in image 546 shown in Fig. 15, the right percentage for the first creator Cr1 "AA" is "20%," the right percentage for the second creator Cr2 "BB" is "40%, and the right percentage for the third creator Cr3 "CC" is "40%." The second creator Cr2 and the third creator Cr3 can indicate whether they accept or reject the presented readjusted right percentages by selecting either "Accept" or "Reject and request revision" in image 546 shown in Fig. 15.

[0077] When the second creator Cr2 agrees to the readjusted rights percentage (S234), the collaborative application 100 can record the second creator Cr2's agreement to the readjusted rights percentage in the blockchain 300 via the management system 200 (S236). Similarly, when the third creator Cr3 agrees to the readjusted rights percentage (S242), the collaborative application 100 can record the third creator Cr3's agreement to the readjusted rights percentage in the blockchain 300 via the management system 200 (S244).

[0078] When the first creator Cr1, the second creator Cr2, and the third creator Cr3 agree on the rights ratios and are recorded in the blockchain 300, the collaborative production application 100 may notify the first creator Cr1 "AA," the second creator Cr2 "BB," and the third creator Cr3 "CC" in the communication area 530 that a split sheet has been created, as shown in image 533 in FIG. 16 .

[0079] If the contract conditions are "contract-time right share priority type," the operations of steps S222 to S224 are skipped. In this case, the collaboration application 100 can create a split sheet based on the agreement of the first creator Cr1, the second creator Cr2, and the third creator Cr3 to the initial right shares.

[0080] This allows the collaborative production application 100 to create a split sheet based on the rights ratios agreed upon by each of the producers Cr.

[0081] For example, the collaborative production application 100 can create a split sheet SS shown in Fig. 17. The split sheet SS shown in Fig. 17 includes the creation date and information about the collaborative production, such as the title of the work "This song," the sound source "Melody A_1," the lyrics "Lyrics_Additional 1," the names of the lyricists "AA, BB, CC," and the names of the composers "AA, BB, CC." The split sheet SS also includes the rights shares of the multiple producers "AA, BB, CC" and a timestamp of the agreement between the multiple producers "AA, BB, CC."

[0082] Information about the collaborative work, information about the right shares of the multiple creators Cr, and information about the agreement on the right shares of the multiple creators Cr are recorded on the blockchain 300. Therefore, the collaborative application 100 can ensure the legitimacy and integrity of the content of the split sheet SS by referring to the information recorded on the blockchain 300.

[0083] For example, when the third creator Cr3 checks the legitimacy and completeness of the split sheet content, the third creator Cr3 confirms the split sheet to the collaborative application 100 (S246). The collaborative application 100 acquires information about the split sheet content from the blockchain 300 via the management system 200 (S248). Next, the collaborative application 100 verifies the split sheet content based on the information acquired from the blockchain 300 (S250). Thereafter, the collaborative application 100 notifies the third creator Cr3 of the split sheet and the verification results of the split sheet content (S252). This allows the third creator Cr3 to check the split sheet content and confirm that the split sheet content is agreed upon and legitimate using the information recorded in the blockchain 300.

[0084] (4.4. When the minimum right share is guaranteed) The operation of the information processing system 10 when creating a split sheet that describes the right share for each creator Cr of a collaborative work when the minimum right share is guaranteed will be described with reference to Fig. 18. Fig. 18 is a sequence diagram showing the operation of the information processing system 10 when creating a split sheet when the minimum right share is guaranteed.

[0085] Under the terms of the "minimum rights percentage guaranteed" contract, a minimum rights percentage is set in addition to the rights percentages of each producer Cr before the joint production. The minimum rights percentage is the minimum rights percentage guaranteed even if the rights percentages of each producer Cr are readjusted after the joint production.

[0086] In such a case, before the collaboration, the collaborative application 100 records the right percentage of each creator Cr in the blockchain 300, and also records a smart contract that rejects the setting of a right percentage below the minimum right percentage in the blockchain 300. In this way, the collaborative application 100 can prevent, by the smart contract, a right percentage below the guaranteed minimum right percentage from being recorded in the blockchain 300 when the right percentage of each creator Cr is readjusted after the collaboration.

[0087] For example, under the contract conditions of the "minimum right percentage guarantee type," as shown in Fig. 18, the first creator Cr1 instructs the collaborative production application 100 to create a split sheet based on the contract conditions (S220). At this time, if the right percentage is readjusted (S222), an attempt is made to record information about the readjusted right percentage in the blockchain 300 via the collaborative production application 100 (S224).

[0088] However, if the readjusted rights percentage is lower than the minimum rights percentage of the smart contract recorded in the blockchain 300, the recording of information regarding the readjusted rights percentage in the blockchain 300 is denied (S260). Subsequently, the collaborative production application 100 notifies the first creator Cr1 that the recording of the readjusted rights percentage in the blockchain 300 has been denied (S262).

[0089] As a result, the first producer Cr1 again readjusts each of the rights ratios so that they are equal to or greater than the minimum rights ratio (S264), and information regarding the readjusted rights ratios is recorded in the blockchain 300 via the collaborative production application 100 (S266).

[0090] Thereafter, the first creator Cr1 inputs their agreement to the readjusted rights percentage into the collaborative application 100 (S226). This allows the collaborative application 100 to record the first creator Cr1's agreement to the readjusted rights percentage in the blockchain 300 via the management system 200 (S228). Furthermore, similar to the operation shown in FIG. 13 , the second creator Cr2 and the third creator Cr3 obtain and confirm the readjusted rights percentage, and then agree to the readjusted rights percentage. This allows the collaborative application 100 to record the second creator Cr2's and the third creator Cr3's agreement to the readjusted rights percentage in the blockchain 300 via the management system 200.

[0091] According to the above operation, the collaborative production application 100 can prevent, by means of a smart contract, a right percentage below the guaranteed minimum right percentage from being recorded in the blockchain 300 when readjusting the right percentage of each creator Cr after collaborative production.

[0092] (4.5. Supplementary Note) If the number of creators Cr increases or decreases during collaborative production, the collaborative production application 100 can adjust the right ratio of each of the creators Cr after the increase or decrease in number using the following method.

[0093] For example, in the "rights ratio readjustment type" and "minimum rights ratio guarantee type," in which each right ratio is readjusted after the collaborative production, the collaborative production application 100 can readjust the rights ratio of the creator Cr that has increased or decreased after the collaborative production after the collaborative production.

[0094] Note that if an increase in the number of creators Cr causes the total right percentage of the increased creators Cr to exceed 100% in percentage terms, the collaborative production application 100 may calculate the right percentage of each creator Cr by treating the percentage as a ratio. For example, if the total right percentage of the increased creators Cr is 120%, the value obtained by dividing each right percentage of the creators Cr by the total right percentage of the increased right percentages (120% / 100%=1.2) may be used as the percentage of each creator Cr. Similarly, for the minimum right percentage guaranteed in the "minimum right percentage guaranteed" type, the value obtained by dividing the minimum right percentage by the total right percentage of the increased right percentages (120% / 100%=1.2) may be used as the minimum right percentage.

[0095] On the other hand, in the "contract right share priority type" in which the right shares of each creator Cr are determined before the collaborative production, the collaborative production application 100 can determine the increased or decreased right shares of the creator Cr by restarting the project from scratch or by re-determining and re-agreeing on the contract terms, including the right shares. However, when restarting a project from scratch, it is desirable that the newly launched project can inherit the history, such as the timeline, from before the number of creators Cr increased or decreased.

[0096] Furthermore, in the "rights percentage readjustment type" and "minimum rights percentage guarantee type," as in the "contract-time rights percentage priority type," the collaborative production application 100 may cause a new project to be launched or the contract terms, including the rights percentage, to be determined and agreed upon again in order to set the increased or decreased rights percentage of the creator Cr.

[0097] In addition, if the right percentage of each creator Cr is readjusted or redetermined due to an increase or decrease in the number of creators Cr, the readjusted or redetermined right percentage and each creator Cr's agreement with the right percentage are recorded in the blockchain 300 via the management system 200. In other words, it is desirable that the decisions and changes regarding the right percentage of the collaborative work and the agreement status of the creators Cr be recorded in the blockchain 300 each time in order to leave a history on the blockchain 300.

[0098] 5. Hardware Configuration The hardware configuration of an information processing device 900 that runs the collaboration application 100 according to this embodiment will be described with reference to Fig. 19. Fig. 19 is a block diagram showing an example of the hardware configuration of the information processing device 900 that runs the collaboration application 100.

[0099] The functions of the collaboration application 100 according to this embodiment can be realized by cooperation between software and hardware included in the information processing device 900 described below. The functions of the timeline generation unit 120, the acquisition unit 130, the information generation unit 140, and the agreement generation unit 150 may be executed by, for example, the CPU 901.

[0100] The collaboration application 100 according to this embodiment may be, for example, a native application that runs on an information processing terminal owned by each creator Cr, or a web application that runs on an information processing server accessed by an information processing terminal owned by each creator Cr. The collaboration application 100 according to this embodiment may also be a hybrid application that runs in conjunction with each other on both the information processing server and the information processing terminal.

[0101] As shown in FIG. 19, the information processing device 900 includes a CPU (Central Processing Unit) 901 , a ROM (Read Only Memory) 902 , and a RAM (Random Access Memory) 903 .

[0102] The information processing device 900 may further include a host bus 904a, a bridge 904, an external bus 904b, an interface 905, an input device 906, an output device 907, a storage device 908, a drive 909, a connection port 910, or a communication device 911. The information processing device 900 may have a processing circuit such as a DSP (Digital Signal Processor) or an ASIC (Application Specific Integrated Circuit) instead of or together with the CPU 901.

[0103] The CPU 901 functions as an arithmetic processing device or control device, and controls operations within the information processing device 900 in accordance with various programs recorded in the ROM 902, RAM 903, storage device 908, or a removable recording medium attached to the drive 909. The ROM 902 stores programs used by the CPU 901, calculation parameters, etc. The RAM 903 temporarily stores programs used in the execution of the CPU 901, and parameters used during the execution of the programs.

[0104] The CPU 901, ROM 902, and RAM 903 are interconnected by a host bus 904a capable of high-speed data transmission. The host bus 904a is connected to an external bus 904b, such as a CI (Peripheral Component Interconnect / Interface) bus, via a bridge 904. The external bus 904b is connected to various components via an interface 905.

[0105] The input device 906 is a device that accepts input from a user, such as a mouse, keyboard, touch panel, button, switch, or lever. The input device 906 may also be a microphone that detects the user's voice. The input device 906 may also be, for example, a remote control device that uses infrared rays or other radio waves, or may be an externally connected device that supports operation of the information processing device 900.

[0106] The input device 906 further includes an input control circuit that outputs an input signal generated based on information input by the user to the CPU 901. By operating the input device 906, the user can input various data to the information processing device 900 or instruct the information processing device 900 to perform processing operations.

[0107] The output device 907 is a device capable of visually or audibly presenting information acquired or generated by the information processing device 900 to a user. The output device 907 may be, for example, a display device such as an LCD (Liquid Crystal Display), a PDP (Plasma Display Panel), an OLED (Organic Light Emitting Diode) display, a hologram, or a projector, or may be a sound output device such as a speaker or headphones, or may be a printing device such as a printer. The output device 907 can output information acquired by processing by the information processing device 900 as video such as text or images, and sound such as voice or audio.

[0108] The storage device 908 is a data storage device configured as an example of a storage unit of the information processing device 900. The storage device 908 may be configured, for example, by a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device, an optical storage device, or a magneto-optical storage device. The storage device 908 can store programs executed by the CPU 901, various data, various data acquired from the outside, and the like.

[0109] The drive 909 is a device for reading or writing data from or to a removable recording medium such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory, and is built into or externally attached to the information processing device 900. For example, the drive 909 can read information recorded on an attached removable recording medium and output the information to the RAM 903. The drive 909 can also write data to an attached removable recording medium.

[0110] The connection port 910 is a port for directly connecting an external device to the information processing device 900. The connection port 910 may be, for example, a Universal Serial Bus (USB) port, an IEEE 1394 port, or a Small Computer System Interface (SCSI) port. The connection port 910 may also be an RS-232C port, an optical audio terminal, or a High-Definition Multimedia Interface (HDMI) (registered trademark) port. By connecting the connection port 910 to an external device, various types of data can be transmitted and received between the information processing device 900 and the external device.

[0111] The communication device 911 is, for example, a communication interface configured with a communication device for connecting to the network 920. The communication device 911 may be, for example, a communication card for a wired or wireless LAN (Local Area Network), Wi-Fi (registered trademark), Bluetooth (registered trademark), or WUSB (Wireless USB). The communication device 911 may also be a router for optical communication, a router for ADSL (Asymmetric Digital Subscriber Line), or a modem for various types of communication.

[0112] The communication device 911 can transmit and receive signals, for example, via the Internet or other communication devices using a predetermined protocol such as TCP / IP. The network 920 connected to the communication device 911 is a wired or wireless network, and may be, for example, an Internet communication network, a home LAN, an infrared communication network, a radio wave communication network, or a satellite communication network.

[0113] It is also possible to create a program that causes hardware such as the CPU 901, ROM 902, and RAM 903 built into a computer to perform functions equivalent to those of the information processing device 900. It is also possible to provide a computer-readable recording medium on which the program is recorded.

[0114] 6. Modifications In the above embodiment, an example was described in which the information processing system 10 recorded the agreements of each creator when creating a collaborative work (a collaborative work). However, the information processing system 10 may record other information. For example, prior to issuing a project to create a collaborative work, the information processing system 10 may accept registration of works created by each creator who intends to participate in the project. In other words, when starting a collaborative work, the information processing system 10 has a function for recruiting co-creators and a function for verifying the experience of the co-creators.

[0115] (6.1. Background) First, the production system for collaborative works will be described as the background for the information processing system 10 having the above functions.

[0116] In recent years, the spread of networks has significantly changed the styles of creators' activities. In particular, there has been a trend toward increased activity among independent creators who are not affiliated with publishers or organizations, and creators who are not affiliated with record companies and who distribute their works themselves (known as DIY creators, etc.). On the other hand, as shown in the embodiments, collaborative production, in which music is created jointly, is also on the rise. For example, collaborative production may involve dividing the work between music and lyrics, or multiple people working together to create music and lyrics. Under these circumstances, collaborative production, which previously took place between acquaintances, is now being carried out between strangers, both domestically and internationally, due to the development of networks. This has led to a diversification of production styles.

[0117] However, in reality, it is difficult for creators seeking collaboration (hereafter referred to as "initiators") to find other creators with the desired skills. For example, initiators often have no choice but to contact creators they come across by chance while browsing a website or other means. Furthermore, while creators who are acquaintances often know each other's past works and genres of expertise, initiators do not have access to information about creators they meet by chance. In this case, initiators can ask creators to present their work before proposing a collaboration, but there is a risk that inexperienced creators may present other creators' work as if it were their own, leaving them with few means to reliably trust the creator. For example, there is a risk that potential participants may include creators who do not disclose personal information such as their real names, creators who use temporary contact information (so-called disposable email addresses), or creators who impersonate well-known creators.

[0118] The function of the modified example addresses the above-mentioned problems, and the information processing system 10 provides a means for the initiator to confirm in advance whether the work submitted by the prospective participant is the original creator's own work before the initiator begins the collaborative project. In other words, the information processing system 10 verifies the creator's ability as a creator in advance, thereby reducing problems after the collaborative project begins. Specifically, the function of the modified example verifies each creator's work registered on the blockchain based on immutable information such as NFTs (non-fungible tokens), thereby preventing the counterfeiting or impersonation of works. This allows the information processing system 10 to build a system in which creators can connect with each other with peace of mind and provide an environment in which appropriate collaborative projects can be realized.

[0119] (6.2. Pre-registration of a production to a blockchain) A modified example will be described with reference to Fig. 20 and subsequent figures. Fig. 20 is a block diagram illustrating an overview of information processing according to the modified example.

[0120] 20 schematically shows a process in which a first creator Cr11 or a second creator Cr12 creates an arbitrary creation as their own work and registers it in the management system 200. Note that the components shown in FIG. 20, such as the collaborative production application 100, the management system 200, the blockchain 300, and the DB storage unit 400, are the same as those in the embodiment.

[0121] In a modified example, the first creator Cr11 and the second creator Cr12 register their own information in advance in the management system 200 before producing a collaborative work. Furthermore, the first creator Cr11 and the second creator Cr12 appropriately perform a process of registering the created work in the management system 200. In this way, when a certain initiator launches a collaborative project, the initiator can determine whether or not a person who wishes to participate is a creator who has registered a work in the management system 200.

[0122] (6.3. Collaborative Creation) An example of a processing flow is shown in Figure 20. When a first creator Cr11 creates a work, the first creator Cr11 requests the collaborative creation application 100 to register the work (step S301). Note that the request for work registration is not limited to the collaborative creation application 100, and may be made via any creative work registration service (such as a web service used by the creator).

[0123] When the collaborative production application 100 receives a request to register a work, it sends information about the work and the creator to the management system 200 (step S302). The management system 200 registers the work in the blockchain 300. At this time, the management system 200 issues a proof of existence as proof that the first creator Cr11 created the work. For example, the management system 200 issues a token such as an NFT as the proof of existence using a smart contract on the blockchain 300.

[0124] This proof of existence is recorded, for example, in a wallet of the blockchain 300 linked to the first creator Cr11. This allows the first creator Cr11 to manage his or her own unfalsifiable proof of existence. Note that NFT is just one example, and the management system 200 may use any information that can serve as proof of existence (such as an ID that can uniquely identify information).

[0125] When the collaborative production application 100 receives the proof of existence issued by the management system 200 (step S303), it stores the work produced by the first creator Cr11 as a creative work in the DB storage unit 400 (step S304).

[0126] The second creator Cr12 also registers his / her own work in the management system 200 in the same manner as the first creator Cr11 (steps S311 to S314).

[0127] In this way, each creator who uses the information processing system 10 manages proof of existence that they have definitely created the work, and also registers the work in advance on the information processing system 10. That is, by recording the works they have created through their daily creative activities on the information processing system 10, which functions as a creative work registration service, creators can prove their own creative activities when engaging in collaborative production, which will be described later.

[0128] Next, an example in which proof of existence of a work is used when a collaborative project is launched will be described with reference to Fig. 21. Fig. 21 is a block diagram illustrating an overview of collaborative production according to a modified example.

[0129] 21, first, the first creator Cr11 transmits a request to start a collaborative project to the collaborative application 100 (step S321). That is, in the example of FIG. 21, the first creator Cr11 is the initiator of the project.

[0130] At this time, the first creator Cr11 presents the work and the NFT, which is proof of the existence of the work, that he or she has registered in advance in the information processing system 10 prior to launching the project to the collaborative production application 100.

[0131] Upon receiving the request, the collaborative production application 100 queries the management system 200 for the presented NFT (step S332). The management system 200 verifies the NFT recorded in the blockchain 300. After verifying the NFT of the first creator Cr11, the management system 200 returns the result to the collaborative production application 100 (step S333). The collaborative production application 100 also identifies the work linked to the verified NFT in the DB storage unit 400 (step S334).

[0132] As a result, the collaborative production application 100 can verify the works that the first creator Cr11 who started the project has worked on to date, and that the works were definitely created by the first creator Cr11. Next, the collaborative production application 100 displays a message indicating that the works have been verified, and invites people who wish to participate in the project.

[0133] It is assumed that a second creator Cr12 who has viewed the project transmits a request to the collaborative production application 100 to participate in the project (step S331).

[0134] In this case, the collaborative production application 100 verifies the NFT presented by the second creator Cr12 in the same manner as the verification process performed by the first creator Cr11. The collaborative production application 100 then identifies works that the second creator Cr12 has worked on in the past, verifies that the works were definitely created by the second creator Cr12, and so on.

[0135] Because the second creator Cr12 has presented the NFT of the work, verified his or her work, and then expressed his or her intention to participate in the project, the first creator Cr11 can at this point understand the technical capabilities and areas of expertise of the second creator Cr12. This allows the first creator Cr11 to decide whether or not to carry out the project together with the second creator Cr12.

[0136] Meanwhile, suppose that a third creator Cr13, who has viewed the project but has no history of registering works, sends a request to the collaborative production application 100 to participate in the project, just like the second creator Cr12 (step S335).

[0137] In this case, the collaborative production application 100 attempts to verify the NFT of the third creator Cr13 in the same manner as the verification process for the second creator Cr12, but if there is no past work registration history, the NFT of the third creator Cr13 cannot be verified. Therefore, the collaborative production application 100 attaches information to the third creator Cr13 indicating that the work of the third creator Cr13 cannot be verified.

[0138] Because the third creator Cr13 has not registered his / her own work, the first creator Cr11 cannot at this point grasp the technical capabilities or areas of expertise of the third creator Cr13. For this reason, the first creator Cr11 can refuse the third creator Cr13's participation in the project.

[0139] In this way, the first creator Cr11, who is the initiator, can accurately identify creators who wish to participate in the project and whose works are registered. Since a project is not run solely by the initiator but by all those who wish to participate, the decision on whether to participate in the project may be made by voting among those who wish to participate, rather than by the first creator Cr11's decision. That is, each person who wishes to participate in the project may view the works of other participants and understand their technical areas of expertise, and then vote to approve the participation of creators with whom they wish to work together on the project. The collaborative production application 100 certifies creators who receive a certain number of votes as members who can participate in the project and officially creates the project. Voting may be performed, for example, using a mechanism such as a governance token in a decentralized autonomous organization (DAO). Furthermore, the processing after project creation may be the same as that of the embodiment, for example, as shown in FIG. 4.

[0140] As described above, the information processing system 10 according to the modified example provides creators with a platform utilizing the blockchain 300, enabling individuals to safely establish organizations such as production committees and secure human resources without the intervention of a trusted company. Furthermore, as shown in the embodiment, the information processing system 10 provides contract details and compensation in advance and records such information on the blockchain 300, thereby protecting individual creators from tampering or breach of contract after the project has begun. Furthermore, creators can participate in production or support projects without disclosing their personal information. In this case, the information processing system 10 allows initiators to verify the backgrounds and areas of expertise of participants using past works recorded on the blockchain 300 as evidence.

[0141] (6.4. Example of processing procedure related to modified example) Next, an example of processing procedure from project launch to reward distribution will be shown using Figs. 22 to 25. Fig. 22 is a flowchart (1) showing processing procedure related to modified example. Note that, for simplicity of explanation, the processing will be described below as being performed by the information processing system 10, but in reality, each element constituting the information processing system 10 (such as the collaboration application 100 and the management system 200) executes the processing.

[0142] First, the information processing system 10 receives a request to launch a collaborative project from a first creator who is the initiator (step S341). The information processing system 10 records the project outline and recruitment conditions specified by the first creator in the DB storage unit 400 or the like, and writes them to the blockchain 300 so that they cannot be tampered with (step S342).

[0143] Next, the information processing system 10 verifies the existence of several works submitted by the first creator among the works registered by the first creator as proof of existence (step S343). The information processing system 10 determines whether the proof of existence has been verified (step S344). Specifically, the information processing system 10 verifies the NFT of the works and verifies whether the works are indeed registered.

[0144] If the verification is successful (step S344; Yes), the information processing system 10 marks the first creator as verified, makes the project public, and makes it available for participation registration (step S345).

[0145] On the other hand, if the proof of existence of the first creator cannot be verified (step S344; No), the information processing system 10 returns an error, such as refusing to create the project, on the grounds that there is a problem with the reliability of the first creator (step S346).

[0146] Next, a description will be given of Fig. 23. Fig. 23 is a flowchart (2) showing a processing procedure according to a modified example.

[0147] The information processing system 10 accepts registrations for participation from each creator for the published project (step S351). For example, the information processing system 10 displays the project outline and recruitment conditions, and also provides information regarding participation, such as the need to register examples of the creator's own work and agree to the recruitment conditions.

[0148] Then, the information processing system 10 determines whether or not there are any registered works for each creator who has registered to participate, based on the registration ID of each creator (step S352).

[0149] If a registered work exists (step S352; Yes), the information processing system 10 verifies the registered work based on the NFT or the like, and marks the work as verified if the verification is successful (step S353). On the other hand, if a registered work does not exist (step S352; No), the information processing system 10 marks creators whose works are not registered as unverified (step S354). Note that the information processing system 10 may also mark creators whose works have been registered but whose proof of existence of the NFT or the like could not be verified as unverified.

[0150] Thereafter, the information processing system 10 writes the agreement of each creator on the conditions for participating in the project to the blockchain 300, as in the embodiment (step S355).

[0151] Thereafter, the information processing system 10 determines whether the recruitment period for the project has ended (step S356). If the recruitment period has not ended (step S356; No), the information processing system 10 continues the recruitment. On the other hand, if the recruitment period has ended (step S356; Yes), the information processing system 10 ends the recruitment.

[0152] Next, a description will be given of Fig. 24. Fig. 24 is a flowchart (3) showing a processing procedure according to a modified example.

[0153] When the project recruitment period ends, the information processing system 10 accepts votes regarding project participation (step S361). For example, the information processing system 10 accepts votes from all creators who have sent project participation requests, indicating which creators they would like to participate in the project from among other creators.

[0154] Thereafter, the information processing system 10 determines whether a certain number of votes have been cast (step S362). For example, the information processing system 10 determines that a certain number of votes have been cast when all creators have cast their votes or when the set voting period has ended. If a certain number of votes have not been cast (step S362; No), the information processing system 10 continues to accept votes.

[0155] On the other hand, if a certain number of votes have been cast (step S362; Yes), the information processing system 10 displays, on the user interface of the collaborative production application 100, the members who have received more than the specified number of votes, and indicates that the project is ready to start (step S363).

[0156] Thereafter, the information processing system 10 receives an agreement result from each creator who has been approved to participate in the project, such as whether they agree to start the project between themselves or decline, and writes the received result to the blockchain 300 (step S364).

[0157] The information processing system 10 determines whether or not agreement has been reached among all creators participating in the project (step S365). If agreement has not been reached (step S365; No), the information processing system 10 waits until agreement is reached. Note that the information processing system 10 may assume that a creator who is unable to confirm his or her intention to agree within a certain period of time has withdrawn from the project.

[0158] On the other hand, if an agreement has been reached (step S365; Yes), the information processing system 10 starts the project (step S366).

[0159] Next, a description will be given of Fig. 25. Fig. 25 is a flowchart (4) showing a processing procedure according to a modified example.

[0160] While the project is in progress, the information processing system 10 registers the intermediate deliverables uploaded by each creator in the collaborative production application 100 (step S371). The information processing system 10 then determines whether the final deliverable has been obtained (step S372). For example, the information processing system 10 determines that the final deliverable has been obtained when it receives a notification of project completion from the initiator. If the final deliverable has not been obtained (step S372; No), the information processing system 10 continues the project.

[0161] On the other hand, if a final product is obtained (step S372; Yes), the information processing system 10 obtains agreement on the final product from the creators who participated in the project (step S373).Then, the information processing system 10 distributes rewards to each creator based on the initial agreement using the smart contract of the blockchain 300 (step S374).

[0162] (6.5. System Configuration Related to Modification) A system related to the modification may have the same configuration as the information processing system 10 according to the embodiment. For example, the processing related to the modification is executed by the collaborative production application 100. However, the subject of the processing is not limited to the collaborative production application 100, and the processing related to the modification may be executed in a form in which the collaborative production application 100, the management system 200, and the like cooperate with each other. Furthermore, the platform that accepts registration of works by each creator is not limited to the collaborative production application 100, and may be a predetermined creative work registration service, etc.

[0163] (6.6. Effects of Modification) As described above, a program according to the modification (e.g., collaborative production application 100) causes a computer to function as an acquisition unit (e.g., acquisition unit 130) and an information generation unit (e.g., information generation unit 140). The acquisition unit acquires information about works independently created by each creator prior to the creation of a collaborative work. The information generation unit generates information for recording the acquired works in a blockchain, and also generates proof information for proving the existence of the works. For example, the information generation unit uses an NFT in a blockchain as proof information.

[0164] The acquisition unit acquires a request for the creation of a collaborative work from a first creator (promoter). When the request is acquired, the information generation unit verifies the work certification information registered in advance by the first creator, and if verified, generates information about the collaborative work project based on the request.

[0165] The acquisition unit also acquires a request to participate in the project from a second creator (each creator other than the initiator) who is a creator who wishes to participate in the project. When the participation request is acquired, if there is a work pre-registered by the second creator, the information generation unit verifies the certification information of the work pre-registered by the second creator and generates information indicating that the work has been verified, and if there is no work pre-registered by the second creator, generates information indicating that the work has not been verified.

[0166] The acquisition unit also acquires votes indicating whether or not the second creators can participate in the project. The information generation unit generates information indicating the second creators who can participate in the project based on the results of the votes.

[0167] The acquisition unit may acquire information indicating whether a second creator can participate in the project from the first creator. The information generation unit generates information indicating second creators who can participate in the project based on the information acquired from the first creator.

[0168] In this way, the program according to the modified example can guarantee the capabilities of creators who wish to participate in a project by registering their work in advance and issuing proof of existence using NFTs prior to the creation of the project. Furthermore, by specifying prior work registration as a condition for participating in the project, initiators can eliminate in advance impersonating creators or creators who do not fit the project's objectives, and start the project with the members they desire.

[0169] Furthermore, because projects are managed on a blockchain, creators can register various content (e.g., rough sketches, settings, storyboards, rejected takes, etc.) obtained during the collaborative process as intermediate deliverables. In other words, each creator can register content that does not constitute the final product but may be valuable among fans, for example, as a by-product of the final product, allowing them to enjoy profits based on their value. For example, if the final product generates a lot of profit, each creator may be able to enjoy profits based on intermediate deliverables in accordance with the project guidelines. Thus, with the system disclosed herein, even independent creators, such as individuals, can receive long-term compensation while receiving appropriate management of their privacy information, allowing them to continue their active creative activities with peace of mind.

[0170] Although the preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, the technical scope of the present disclosure is not limited to such examples. It is clear that a person skilled in the art of the present disclosure can conceive of various modified or altered examples within the scope of the technical idea described in the claims, and it is understood that these also naturally fall within the technical scope of the present disclosure.

[0171] Furthermore, the effects described herein are merely descriptive or exemplary and are not limiting. In other words, the technology according to the present disclosure may achieve other effects that will be apparent to those skilled in the art from the description of this specification, in addition to or in place of the above-described effects.

[0172] Note that the following configurations also fall within the technical scope of the present disclosure. (1) A program for causing a computer to function as: an acquisition unit that acquires information regarding the right shares of each creator of a collaborative work via chat between the creators; an information generation unit that generates information for recording the information regarding the right shares in a blockchain; and an agreement generation unit that generates an agreement regarding the right shares based on the information regarding the right shares and the agreement status of the creators regarding the right shares. (2) The program described in (1), in which the information generation unit further generates information for further recording information regarding the creators' agreement to the right shares in the blockchain before the creation of the collaborative work. (3) The program described in (1) or (2), in which, if the right shares are readjusted after the creation of the collaborative work, the information generation unit generates information for further recording information regarding the readjusted right shares in the blockchain. (4) The program described in (3), in which the information generation unit generates information for further recording information regarding the creators' agreement to the readjusted right shares in the blockchain. (5) The program according to (3) or (4), wherein the right share recorded in the blockchain before the production of the collaborative work is set to a minimum guaranteed value for the right share for each creator. (6) The program according to (5), wherein if the right share readjusted after the production of the collaborative work is below the minimum guaranteed value, recording of information regarding the right share in the blockchain is refused by a smart contract. (7) The program according to any one of (1) to (6), wherein the content of the agreement is verifiable by information acquired from the blockchain. (8) The program according to any one of (1) to (7), wherein information regarding the created collaborative work is further recorded in the blockchain. (9) The program according to (8), wherein information regarding the agreement of each creator to the created collaborative work is further recorded in the blockchain.(10) The program according to any one of (1) to (9), causing the computer to further function as a timeline generation unit that generates a timeline that chronologically shows the exchanges in the chat. (11) The program according to (10), wherein data is further transmitted and received between the creators on the timeline. (12) The program according to any one of (1) to (11), wherein, when the number of creators of the collaborative work increases or decreases, the acquisition unit again acquires information regarding the right shares of each creator, and the information generation unit generates information for further recording the reacquired information regarding the right shares in the blockchain. (13) The program according to (1), wherein, prior to the production of the collaborative work, the acquisition unit acquires information regarding works independently created by each of the creators, and the information generation unit generates information for recording the acquired works in the blockchain and also generates certification information for proving the existence of the works. (14) The program according to (13), wherein the acquisition unit acquires a request to create the collaborative work from a first creator, and the information generation unit, when the request is acquired, verifies certification information of a work pre-registered by the first creator, and if the verification is successful, generates information related to the collaborative work project based on the request. (15) The program according to (14), wherein the acquisition unit acquires a request to participate in the project from a second creator who is a creator requesting to participate in the project, and when the participation request is acquired, if there is a work pre-registered by the second creator, the information generation unit verifies certification information of the work pre-registered by the second creator and generates information indicating that the verification has been successful, and if there is no work pre-registered by the second creator, generates information indicating that the work is not verified. (16) The program according to (15), wherein the acquisition unit acquires a vote indicating whether the second creator can participate in the project, and the information generation unit generates information indicating the second creator who is available to participate in the project based on the result of the vote.(17) The program according to (15) or (16), wherein the acquisition unit acquires, from the first creator, information indicating whether the second creator can participate in the project, and the information generation unit generates information displaying the second creator who can participate in the project based on the information acquired from the first creator. (18) The program according to any one of (13) to (17), wherein the information generation unit uses a non-fungible token in the blockchain as the proof information. (19) An information processing method by a computer, including: acquiring information regarding the right shares of each creator in a collaborative work via a chat between the creators; generating information for recording the information regarding the right shares in a blockchain; and generating an agreement regarding the right shares based on the information regarding the right shares and an agreement status between the creators regarding the right shares. (20) An information processing device comprising: an acquisition unit that acquires information regarding the right shares of each creator of a collaborative work through chat between the creators; an information generation unit that generates information for recording the information regarding the right shares in a blockchain; and an agreement generation unit that generates an agreement regarding the right shares based on the information regarding the right shares and the agreement status of the creators regarding the right shares.

[0173] 10 Information processing system 100 Collaborative production application 120 Timeline generation unit 130 Acquisition unit 140 Information generation unit 150 Agreement generation unit 200 Management system 300 Blockchain 400 DB storage unit 500 Application image 510 Project selection area 520 Member display area 530 Communication area 540 Decision area Cr Producer SS Split sheet

Claims

1. A program for causing a computer to function as: an acquisition unit that acquires information regarding the rights shares of each creator of a collaborative work through chat between the creators; an information generation unit that generates information for recording the information regarding the rights shares in a blockchain; and an agreement generation unit that generates an agreement regarding the rights shares based on the information regarding the rights shares and the agreement status of the creators regarding the rights shares.

2. The program of claim 1, wherein the information generation unit further generates information for further recording information regarding each creator's agreement to the rights ratio in the blockchain prior to the production of the collaborative work.

3. The program of claim 1, wherein, if the rights ratio is readjusted after the production of the collaborative work, the information generation unit generates information for further recording information regarding the readjusted rights ratio in the blockchain.

4. The program described in claim 3, wherein the information generation unit generates information for further recording information regarding each creator's agreement to the re-adjusted rights ratio in the blockchain.

5. The program of claim 3, wherein the rights percentage recorded on the blockchain prior to the production of the collaborative work is set with a minimum guaranteed value for each creator with respect to the rights percentage.

6. The program of claim 5, wherein if the right percentage readjusted after the production of the collaborative work falls below the minimum guaranteed value, information regarding the right percentage is refused from being recorded on the blockchain by a smart contract.

7. The program of claim 1, wherein the contents of the agreement are verifiable by information obtained from the blockchain.

8. The program of claim 1, wherein the blockchain further records information about the collaborative work that was created.

9. The program of claim 8, wherein the blockchain further records information regarding each creator's agreement to the created collaborative work.

10. The program according to claim 1, for causing the computer to further function as a timeline generation unit that generates a timeline showing the chat conversations in chronological order.

11. The program according to claim 10, wherein the timeline further allows data to be transmitted and received between the creators.

12. The program described in claim 1, wherein, when the number of creators of the collaborative work increases or decreases, the acquisition unit again acquires information regarding the right shares of each creator, and the information generation unit generates information for further recording the reacquired information regarding the right shares in the blockchain.

13. The program described in claim 1, wherein the acquisition unit acquires information regarding works created independently by each of the creators prior to the production of the collaborative work, and the information generation unit generates information for recording the acquired works in the blockchain and generates certification information for proving the existence of the works.

14. The program described in claim 13, wherein the acquisition unit acquires a request to produce the collaborative work from a first creator, and the information generation unit, when the request is acquired, verifies certification information of the work previously registered by the first creator, and, when verified, generates information regarding the collaborative work project based on the request.

15. The program described in claim 14, wherein the acquisition unit acquires a request to participate in the project from a second creator who is a creator who wishes to participate in the project, and the information generation unit, when the participation request is acquired, if there is a work pre-registered by the second creator, verifies certification information of the work pre-registered by the second creator and generates information indicating that it has been verified, and if there is no work pre-registered by the second creator, generates information indicating that the work has not been verified.

16. The program described in claim 15, wherein the acquisition unit acquires a vote indicating whether the second creator can participate in the project, and the information generation unit generates information indicating the second creator who can participate in the project based on the result of the vote.

17. The program described in claim 15, wherein the acquisition unit acquires information from the first creator indicating whether the second creator can participate in the project, and the information generation unit generates information displaying the second creator who can participate in the project based on the information acquired from the first creator.

18. The program described in claim 13, wherein the information generation unit uses a non-fungible token in the blockchain as the proof information.

19. A computer-based information processing method comprising: obtaining information regarding each creator's right share in a collaborative work through chat between the creators; generating information for recording the information regarding the right share in a blockchain; and generating an agreement regarding the right share based on the information regarding the right share and the agreement status of each creator regarding the right share.

20. An information processing device comprising: an acquisition unit that acquires information regarding the right shares of each creator of a collaborative work through chat between the creators; an information generation unit that generates information for recording the information regarding the right shares in a blockchain; and an agreement generation unit that generates an agreement regarding the right shares based on the information regarding the right shares and the agreement status of the creators regarding the right shares.

Citation Information

Patent Citations

  • Contract agreement method, agreement verification method, contract agreement device, and agreement verification device

    JP2017220710A

  • Server device and program

    JP2015060365A

  • Smart Contracts

    JP2022502768A

  • Information processing device, information processing method, and information processing program

    WO2020203340A1

  • NFT issuing method, computer, and program

    WO2023080075A1