Information processing apparatus, information processing method, and information processing program

Abstract

A manufacturer-side management device registers a contribution value calculation SC (603) in an SC store (630) of a distributed ledger. A supplier-side management device registers evidence data in an evidence data store (610) of a distributed ledger. The manufacturer-side management device registers a token in a token data store (620) of the distributed ledger. According to a calculation request, various devices serving as nodes use the contribution value calculation SC (603) and a compensation ratio calculation SC (601) to calculate a compensation ratio indicating a ratio of a distribution of compensation to each participant. For example, the compensation ratio calculation SC (601) specifies, on the basis of the token, the contribution value calculation SC (603) corresponding to a data type included in the evidence data and inputs an actual value. Furthermore, for example, the compensation ratio calculation SC (601) calculates the compensation ratio on the basis of the contribution value obtained by converting the actual value for each evidence data.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, and an information processing program.

Background Art

[0002] Conventionally, there exists a system called a supply chain in which a plurality of processes for manufacturing or distributing a product are shared by a plurality of participants. Here, when manufacturing or distributing a product, reduction of CO2 emissions or the like is desired. For example, it is conceivable to promote reduction of CO2 emissions of each participant by distributing the profit obtained from the product to each participant according to the degree of contribution of each participant to the reduction of CO2 emissions.

[0003] As prior art, for example, there is one that executes a first smart contract for managing a processing history of a transaction in a distributed ledger and executes a second smart contract for calculating the degree of contribution of each of a plurality of organizations to a management target system based on the processing history. Further, for example, there is a technique for updating a smart contract without impairing the immutability of the underlying data by a parent-child model of a smart contract. Further, for example, there is a technique for uploading an extended smart contract of an original smart contract to a blockchain network. Further, for example, there is a technique for determining a carbon emission reduction equivalent corresponding to carbon behavior data based on the first smart contract that matches the carbon behavior data and attributes.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Patent Document 3

Patent Document 4

SUMMARY OF THE INVENTION

PROBLEMS TO BE SOLVED BY THE INVENTION

[0005] However, in the prior art, it may be difficult to appropriately distribute benefits to each participant. For example, a method of distributing benefits to each participant using a smart contract in a blockchain network formed by nodes owned by each participant can be considered. In this method, it becomes difficult to appropriately distribute benefits to each participant in consideration of fluctuations in the contribution degree of each participant.

[0006] In one aspect, the present invention aims to make it easier to appropriately distribute benefits to a plurality of participants.

MEANS FOR SOLVING THE PROBLEMS

[0007] According to one embodiment, among a plurality of information processing apparatuses that manage a distributed ledger, it corresponds to any one of a plurality of processes related to a profit generation source, and for each of the plurality of processes, the actual value in the process regarding the objective is, according to the actual type of the actual value, converted into an index value indicating the degree of contribution to the objective based on a unified standard in the plurality of processes, stores a first smart contract, calculates a ratio for distributing the profit obtained from the generation source to a plurality of participants who share the plurality of processes based on the index value, registers first evidence data indicating the correspondence relationship between any one of the processes, the actual value in the process regarding the objective, and the actual type of the actual value in the distributed ledger, and with reference to the distributed ledger, based on a token indicating the correspondence relationship between the generation source and the evidence data registered in the distributed ledger for each of the processes, uses the first smart contract corresponding to each of the processes to calculate the index value regarding the process according to the actual type of the actual value in the process regarding the objective, and uses the second smart contract to calculate a ratio for distributing the profit obtained from the generation source to the plurality of participants according to the calculated index value regarding each of the processes. An information processing apparatus, an information processing method, and an information processing program are proposed.

Effect of the Invention

[0008] According to one aspect, it becomes possible to easily and appropriately distribute profits to a plurality of participants.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Figure 38

Figure 39

Figure 40

Figure 41

Figure 42

Figure 43

Figure 44

Figure 45

Figure 46

Figure 47

Figure 48

Figure 49

Embodiments for Carrying Out the Invention

[0010] Hereinafter, with reference to the drawings, embodiments of an information processing apparatus, an information processing method, and an information processing program according to the present invention will be described in detail.

[0011] (An Example of an Information Processing Method According to an Embodiment) FIG. 1 is an explanatory diagram showing an example of an information processing method according to an embodiment. The information processing apparatus 100 is a computer that forms a node of a blockchain network and manages a distributed ledger. The distributed ledger is also called a BC (Block Chain). The information processing apparatus 100 is, for example, a server or a PC.

[0012] There are a plurality of information processing apparatuses 100. Each of the information processing apparatuses 100 corresponds to one of a plurality of processes. The plurality of processes are processes related to the source of profit. The source of profit is, for example, a product or a service. The plurality of processes are, for example, two or more processes for manufacturing a product. The plurality of processes may be, for example, two or more processes for providing a service.

[0013] Conventionally, there is a system called a supply chain in which a plurality of processes are shared by a plurality of participants. Here, it may be desirable to distribute the profit obtained from a product to each participant according to the degree of contribution of each participant to a predetermined purpose. However, it is difficult to calculate the ratio for distributing the profit obtained from the product to each participant. The predetermined purpose is, for example, environmental contribution. Specifically, the predetermined purpose is reduction of CO2 emissions, reduction of fuel consumption, reduction of power consumption, or reduction of plastic consumption. For this reason, it is difficult to appropriately distribute the profit to each participant. As a result, it is difficult to promote the contribution of each participant to the predetermined purpose.

[0014] In addition, when there are various participants, it may be desirable to securely calculate the ratio for distributing the profit to each participant. In contrast, referring to the following Reference 1, a method of preparing a smart contract for distributing profit to each participant at a fixed ratio in a blockchain network formed by nodes owned by each participant can be considered.

[0015] Reference 1: “ERC-2571: Creators’ Royalty Token standard”, [online], March 29, 2020, [searched on February 22, 2022], Internet <URL: https: / / github.com / ethereum / EIPs / issues / 2571>

[0016] However, with this method, it is not possible to sequentially evaluate the degree of contribution of each participant to a predetermined purpose and distribute benefits to each participant based on the evaluation results. Therefore, it is difficult to appropriately distribute benefits to each participant considering the fluctuations in the degree of contribution of each participant.

[0017] Another method can be considered, which is to modify this method and prepare a smart contract in the blockchain network to evaluate the degree of contribution of each participant to a predetermined purpose and calculate the ratio of distributing benefits to each participant based on the evaluation results.

[0018] With this other method, it is difficult to handle changes in performance types or evaluation criteria for the degree of contribution. For example, the smart contract has to be rewritten according to changes in performance types or evaluation criteria for the degree of contribution.

[0019] For example, without the consent of multiple participants, rewriting the smart contract may not be permitted, and the cost associated with rewriting the smart contract tends to increase. The cost is, for example, human, time, or monetary cost. Also, it is not possible to generate a smart contract in anticipation of changes in performance types or evaluation criteria for the degree of contribution. Therefore, it is also difficult to appropriately distribute benefits to each participant with this other method.

[0020] Also, rewriting a smart contract is preferably permitted only in situations that have an adverse impact on all participants, such as when a programming defect is discovered, and there may be a policy that it is preferably not permitted in cases such as adding functions.

[0021] Therefore, in the present embodiment, an information processing method that can easily and appropriately distribute benefits to a plurality of participants will be described. The present embodiment can easily and appropriately distribute benefits to a plurality of participants even when there are changes in, for example, the type of achievements or the evaluation criteria for the degree of contribution. In the following description, a smart contract may be referred to as "SC".

[0022] In FIG. 1, the plurality of steps include Step 1, Step 2, Step 3, and Step 4. The plurality of steps relate to the source of benefits. The benefits are, for example, money. The source is, for example, Product 101. Step 1 is a step of manufacturing the parts of Product 101 in Factory 102. Step 2 is a step of manufacturing the parts of Product 101 in Factory 103. Step 3 is a step of manufacturing an integrated circuit that becomes a part of Product 101 in Factory 104 using the parts manufactured in Step 1 and the parts manufactured in Step 2. Step 4 is a step of manufacturing Product 101 using the integrated circuit manufactured in Step 3. Here, when benefits are obtained from Product 101, it is desired to distribute the benefits to each of the plurality of participants who share the plurality of steps.

[0023] Each information processing apparatus 100 corresponds to one of a plurality of processes. Each information processing apparatus 100 stores a first SC for each of the plurality of processes. Each information processing apparatus 100 stores the first SC, for example, by registering it in a distributed ledger managed by the apparatus itself. The first SC has a function of converting, for any process, the actual value in the process regarding the target into an index value indicating the degree of contribution to the target according to the type of the actual value, based on a standard unified among a plurality of processes. The target is, for example, environmental contribution. Specifically, the target is reduction of CO2 emissions, reduction of fuel consumption, reduction of power consumption, or reduction of plastic consumption, etc.

[0024] The actual value is, for example, a measured value in any process regarding the target. The measured value is, for example, fuel consumption, power consumption, or the amount of plant-derived raw material used, etc. The type of actual value indicates, for example, whether the measured value that becomes the actual value is fuel consumption, power consumption, or the amount of plant-derived raw material used, etc. The index value is a contribution value indicating the degree of contribution to the target. The contribution value may be the actual value as it is. Specifically, the contribution value is the reduction amount of CO2 emissions, the reduction amount of fuel consumption, the reduction amount of power consumption, or the reduction amount of plastic consumption, etc. The first SC is generated by one of the information processing apparatuses 100, included in a block, and registered in a distributed ledger managed by each information processing apparatus 100.

[0025] Each information processing apparatus 100 stores a second SC. Each information processing apparatus 100 stores the second SC, for example, by registering it in a distributed ledger managed by the apparatus itself. The second SC calculates the ratio for distributing the profit obtained from the source of generation to a plurality of participants sharing a plurality of processes based on the index value. The second SC has a function of calculating, for example, the ratio for distributing the profit obtained from the source of generation to a plurality of participants sharing a plurality of processes based on the index value for each process. The second SC is generated by one of the information processing apparatuses 100, included in a block, and registered in a distributed ledger managed by each information processing apparatus 100.

[0026] (1-1) Each information processing apparatus 100 registers first evidence data indicating the correspondence relationship between the process corresponding to the apparatus itself, the performance value in the process regarding the objective, and the performance type of the performance value in the distributed ledger managed by each information processing apparatus 100. Each information processing apparatus 100 measures, for example, the performance value in the process regarding the objective in response to the completion of the process corresponding to the apparatus itself. Each information processing apparatus 100 registers first evidence data indicating the correspondence relationship between the process corresponding to the apparatus itself, the measured performance value in the process regarding the objective, and the performance type of the performance value in the distributed ledger managed by each information processing apparatus 100.

[0027] (1-2) Each information processing apparatus 100 refers to the distributed ledger managed by the apparatus itself, and based on the token, uses the first SC corresponding to each process, and calculates an index value regarding the process according to the performance type of the performance value in the process regarding the objective. The token indicates the correspondence relationship between the source of generation and the evidence data registered in the distributed ledger for each process.

[0028] The token is generated by any one of the information processing apparatuses 100, included in a block, and registered in the distributed ledger managed by each information processing apparatus 100. Specifically, it is conceivable that after being generated by any one of the information processing apparatuses 100 corresponding to the last process 4, it is included in a block, distributed to each information processing apparatus 100, and registered in the distributed ledger managed by each information processing apparatus 100.

[0029] Each information processing apparatus 100, for example, in response to registering the token in the distributed ledger managed by the apparatus itself, refers to the distributed ledger managed by the apparatus itself, and based on the token, identifies the first SC corresponding to each process. For each process, each information processing apparatus 100 uses the identified first SC and calculates an index value regarding the process according to the performance type of the performance value in the process regarding the objective.

[0030] (1-3) Each information processing apparatus 100 calculates, using the second SC, a ratio for distributing the profit obtained from the source of generation to a plurality of participants according to the calculated index value for each process. Thereby, each information processing apparatus 100 can calculate a ratio for appropriately distributing the profit to each participant according to the degree of contribution to the purpose of each participant. For this reason, each information processing apparatus 100 can make it possible to appropriately distribute the profit to each participant, and can facilitate promoting the contribution of each participant to the purpose.

[0031] Also, each information processing apparatus 100 can easily and securely calculate a ratio for distributing the profit to each participant even when there are various participants. Further, each information processing apparatus 100 can sequentially evaluate the degree of contribution of each participant to a predetermined purpose of each participant in consideration of the fluctuation of the degree of contribution of each participant, and can appropriately distribute the profit to each participant based on the evaluation result.

[0032] Also, each information processing apparatus 100 can form an information processing system that is easy to handle changes in the type of achievement or the evaluation criteria for the degree of contribution. Specifically, each information processing apparatus 100 can manage without rewriting the existing first SC and the existing second SC even when there is a change in the type of achievement or the evaluation criteria for the degree of contribution. Specifically, each information processing apparatus 100 can handle changes in the type of achievement or the evaluation criteria for the degree of contribution by registering a new first SC or the like in the distributed ledger managed by each information processing apparatus 100. Therefore, each information processing apparatus 100 can suppress an increase in cost.

[0033] (An example of the information processing system 200) Next, with reference to FIG. 2, an example of the information processing system 200 to which the information processing apparatus 100 shown in FIG. 1 is applied will be described.

[0034] FIG. 2 is an explanatory diagram showing an example of the information processing system 200. In FIG. 2, the information processing system 200 includes a plurality of supplier-side environments 210, a manufacturer-side environment 220, a purchaser-side environment 230, and a block generation device 201.

[0035] The supplier-side environment 210 corresponds to any one of a plurality of processes related to the source of profit. The supplier-side environment 210 includes a supplier-side management device 211 and a supplier-side terminal device 212. The manufacturer-side environment 220 corresponds to any one of a plurality of processes related to the source of profit. The manufacturer-side environment 220 corresponds to, for example, the last process of a plurality of processes. The manufacturer-side environment 220 includes a manufacturer-side management device 221 and a manufacturer-side terminal device 222. The purchaser-side environment 230 includes a purchaser-side management device 231 and a purchaser-side terminal device 232.

[0036] In the information processing system 200, the supplier-side management device 211 and the supplier-side terminal device 212 are connected via a wired or wireless network 240. The network 240 is, for example, a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, or the like. In the information processing system 200, the supplier-side management device 211 and the block generation device 201 are connected via a wired or wireless network 240.

[0037] In the information processing system 200, the manufacturer-side management device 221 and the manufacturer-side terminal device 222 are connected via a wired or wireless network 240. In the information processing system 200, the manufacturer-side management device 221 and the block generation device 201 are connected via a wired or wireless network 240.

[0038] In the information processing system 200, the purchaser-side management device 231 and the purchaser-side terminal device 232 are connected via a wired or wireless network 240. In the information processing system 200, the purchaser-side management device 231 and the block generation device 201 are connected via a wired or wireless network 240.

[0039] The supplier-side management device 211 and the manufacturer-side management device 221 correspond to the information processing device 100 shown in FIG. 1. The supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231 are computers that are nodes forming the same blockchain network. The supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231 store and manage a distributed ledger of the same content.

[0040] The supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231 have a first SC. The first SC has a function of converting the actual value in any process related to the purpose into an index value indicating the degree of contribution to the purpose, which is shown based on a unified standard in a plurality of processes according to the type of the actual value. The supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231 have the first SC, for example, by registering the first SC in the distributed ledger managed by each device itself.

[0041] The supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231 have a second SC. The second SC has a function of calculating the ratio for distributing the profit to a plurality of participants based on the index values indicating the degree of contribution to the purpose for each of the plurality of processes. The supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231 have the second SC, for example, by registering the second SC in the distributed ledger managed by each device itself.

[0042] The supplier-side management device 211 receives traceability data from the supplier-side terminal device 212. The traceability data indicates the correspondence relationship between any process, the performance value in the process related to the purpose, and the performance type of the performance value. The supplier-side management device 211 issues a transaction including the traceability data and transmits it to the block generation device 201. Thereby, the supplier-side management device 211 can distribute the block including the traceability data to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0043] When the supplier-side management device 211 receives a block including the traceability data from the block generation device 201, it stores the block including the traceability data in the distributed ledger managed by the device itself. When the supplier-side management device 211 receives a block including a token from the block generation device 201, it stores the block including the token in the distributed ledger managed by the device itself. The token indicates the correspondence relationship between the source of profit and the traceability data registered in the distributed ledger for each of the plurality of processes.

[0044] When the supplier-side management device 211 receives a block including the first SC from the block generation device 201, it stores the block including the first SC in the distributed ledger managed by the device itself. When the supplier-side management device 211 receives a block including the second SC from the block generation device 201, it stores the block including the second SC in the distributed ledger managed by the device itself.

[0045] When the supplier-side management device 211 receives a block including a calculation request from the block generation device 201, it stores the block including the calculation request in the distributed ledger managed by the device itself. The calculation request requests to calculate the ratio for distributing the profit to a plurality of participants. The participants include the supplier and the manufacturer, etc. The calculation request includes the specification of the token.

[0046] The supplier-side management device 211 calculates, in response to a calculation request, an index value indicating the degree of contribution to the objective for each of a plurality of processes using the first SC based on a token. The supplier-side management device 211 calculates, based on a token, the ratio for distributing the profit to a plurality of participants using the second SC based on the index value indicating the degree of contribution to the objective for each of the plurality of processes. The supplier-side management device 211 is, for example, a server or a PC.

[0047] The supplier-side terminal device 212 generates trace data indicating the correspondence relationship between the process corresponding to the own device, the actual value in the process regarding the objective, and the type of actual value of the actual value based on the operation input of the supplier-side user. The supplier-side terminal device 212 transmits the generated trace data to the supplier-side management device 211. The supplier-side terminal device 212 is, for example, a PC, a tablet terminal, or a smartphone.

[0048] The manufacturer-side management device 221 receives the trace data from the manufacturer-side terminal device 222. The manufacturer-side management device 221 issues a transaction including the trace data and transmits it to the block generation device 201. Thereby, the manufacturer-side management device 221 can distribute the block including the trace data to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0049] The manufacturer-side management device 221 receives the token from the manufacturer-side terminal device 222. The manufacturer-side management device 221 issues a transaction including the token and transmits it to the block generation device 201. Thereby, the manufacturer-side management device 221 can distribute the block including the token to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0050] The manufacturer-side management device 221 receives the first SC from the manufacturer-side terminal device 222. The manufacturer-side management device 221 issues a transaction including the first SC and transmits it to the block generation device 201. Thereby, the manufacturer-side management device 221 can distribute the block including the first SC to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0051] The manufacturer-side management device 221 receives the second SC from the manufacturer-side terminal device 222. The manufacturer-side management device 221 issues a transaction including the second SC and transmits it to the block generation device 201. Thereby, the manufacturer-side management device 221 can distribute the block including the second SC to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0052] When the manufacturer-side management device 221 receives a block including trace data from the block generation device 201, it stores the block including the trace data in a distributed ledger managed by the device itself. When the manufacturer-side management device 221 receives a block including a token from the block generation device 201, it stores the block including the token in a distributed ledger managed by the device itself.

[0053] When the manufacturer-side management device 221 receives a block including the first SC from the block generation device 201, it stores the block including the first SC in a distributed ledger managed by the device itself. When the manufacturer-side management device 221 receives a block including the second SC from the block generation device 201, it stores the block including the second SC in a distributed ledger managed by the device itself.

[0054] When the manufacturer-side management device 221 receives a block including a calculation request from the block generation device 201, it stores the block including the calculation request in a distributed ledger managed by the device itself. The calculation request requests to calculate a ratio for distributing profits to a plurality of participants. The participants are, for example, suppliers and manufacturers. The participants may not include a manufacturer, for example. The calculation request includes the specification of tokens.

[0055] In response to the calculation request, the manufacturer-side management device 221 calculates, using the first SC based on the tokens, an index value indicating the degree of contribution to the objective for each of a plurality of processes. The manufacturer-side management device 221 calculates, using the second SC based on the tokens, a ratio for distributing profits to a plurality of participants based on the index values indicating the degree of contribution to the objective for each of the plurality of processes. The manufacturer-side management device 221 is, for example, a server or a PC.

[0056] Based on the operation input of the manufacturer-side user, the manufacturer-side terminal device 222 generates evidence data indicating the correspondence relationship between the process corresponding to the device itself, the actual value in the process regarding the objective, and the type of actual value of the actual value. The manufacturer-side terminal device 222 transmits the generated evidence data to the manufacturer-side management device 221. Based on the operation input of the manufacturer-side user, the manufacturer-side terminal device 222 generates tokens. The manufacturer-side terminal device 222 transmits the generated tokens to the manufacturer-side management device 221.

[0057] Based on the operation input of the manufacturer-side user, the manufacturer-side terminal device 222 generates the first SC. The manufacturer-side terminal device 222 transmits the generated first SC to the manufacturer-side management device 221. Based on the operation input of the manufacturer-side user, the manufacturer-side terminal device 222 generates the second SC. The manufacturer-side terminal device 222 transmits the generated second SC to the manufacturer-side management device 221. The manufacturer-side terminal device 222 is, for example, a PC, a tablet terminal, or a smartphone.

[0058] The purchaser-side management device 231 receives a calculation request from the purchaser-side terminal device 232. The purchaser-side management device 231 issues a transaction including the calculation request and transmits it to the block generation device 201. As a result, the purchaser-side management device 231 can distribute the block including the calculation request to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0059] When the purchaser-side management device 231 receives a block including the evidence data from the block generation device 201, it stores the block including the evidence data in the distributed ledger managed by the device itself. When the purchaser-side management device 231 receives a block including a token from the block generation device 201, it stores the block including the token in the distributed ledger managed by the device itself.

[0060] When the purchaser-side management device 231 receives a block including the first SC from the block generation device 201, it stores the block including the first SC in the distributed ledger managed by the device itself. When the purchaser-side management device 231 receives a block including the second SC from the block generation device 201, it stores the block including the second SC in the distributed ledger managed by the device itself.

[0061] When the purchaser-side management device 231 receives a block including the calculation request from the block generation device 201, it stores the block including the calculation request in the distributed ledger managed by the device itself. The calculation request requests to calculate the ratio for distributing the profit to a plurality of participants. The participants include the purchaser and the manufacturer, etc. The calculation request includes the designation of a token.

[0062] The purchaser-side management device 231 calculates, in response to a calculation request, an index value indicating the degree of contribution to the objective for each of a plurality of processes by using the first SC based on a token. The purchaser-side management device 231 calculates, based on a token, the ratio for distributing the profit to a plurality of participants by using the second SC based on the index value indicating the degree of contribution to the objective for each of the plurality of processes. The purchaser-side management device 231 is, for example, a server or a PC or the like.

[0063] The purchaser-side terminal device 232 generates a calculation request for any one of the tokens based on an operation input by the purchaser-side user. The calculation request includes the specification of a token. The purchaser-side terminal device 232 transmits the generated calculation request to the purchaser-side management device 231. The purchaser-side terminal device 232 is, for example, a PC, a tablet terminal, or a smartphone or the like.

[0064] The block generation device 201 receives a transaction including trace data from the supplier-side management device 211 and generates a block including the trace data. The block generation device 201 transmits the generated block to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0065] The block generation device 201 receives a transaction including trace data from the manufacturer-side management device 221 and generates a block including the trace data. The block generation device 201 transmits the generated block to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0066] The block generation device 201 receives a transaction including a token from the manufacturer-side management device 221 and generates a block including the token. The block generation device 201 transmits the generated block to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0067] The block generation device 201 receives a transaction including the first SC from the manufacturer-side management device 221 and generates a block including the first SC. The block generation device 201 transmits the generated block to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0068] The block generation device 201 receives a transaction including the second SC from the manufacturer-side management device 221 and generates a block including the second SC. The block generation device 201 transmits the generated block to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0069] The block generation device 201 receives a transaction including a calculation request from the purchaser-side management device 231 and generates a block including the calculation request. The block generation device 201 transmits the generated block to the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231. The block generation device 201 is, for example, a server or a PC.

[0070] Here, the case where the block generation device 201 is a device different from any of the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231 has been described, but it is not limited to this. For example, the block generation device 201 may be integrated with any of the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231.

[0071] Here, the case where the supplier-side management device 211 and the supplier-side terminal device 212 are different devices has been described, but it is not limited to this. For example, the supplier-side management device 211 may have the function of the supplier-side terminal device 212 and may also operate as the supplier-side terminal device 212.

[0072] Here, the case where the manufacturer-side management device 221 and the manufacturer-side terminal device 222 are different devices has been described, but it is not limited to this. For example, the manufacturer-side management device 221 may have the function of the manufacturer-side terminal device 222 and may also operate as the manufacturer-side terminal device 222.

[0073] Here, the case where the purchaser-side management device 231 and the purchaser-side terminal device 232 are different devices has been described, but it is not limited to this. For example, the purchaser-side management device 231 may have the function of the purchaser-side terminal device 232 and may also operate as the purchaser-side terminal device 232.

[0074] (Hardware configuration example of computer 300) Next, a hardware configuration example of the computer 300 will be described with reference to FIG. 3. The computer 300 can be the supplier-side management device 211, the supplier-side terminal device 212, the manufacturer-side management device 221, the manufacturer-side terminal device 222, the purchaser-side management device 231, the purchaser-side terminal device 232, or the block generation device 201.

[0075] FIG. 3 is a block diagram showing a hardware configuration example of the computer 300. In FIG. 4, the computer 300 includes a CPU (Central Processing Unit) 301, a memory 302, a network I / F (Interface) 303, a recording medium I / F 304, and a recording medium 305. Also, each component is connected by a bus 310.

[0076] Here, the CPU 301 controls the overall operation of the computer 300. The memory 302 includes, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), and a flash ROM. Specifically, for example, the flash ROM and the ROM store various programs, and the RAM is used as the working area of the CPU 301. The programs stored in the memory 302 are loaded into the CPU 301, causing the CPU 301 to execute the coded processes. The memory 302 may store, for example, a distributed ledger.

[0077] The network I / F 303 is connected to the network 240 through a communication line and is connected to other computers 300 via the network 240. Then, the network I / F 303 manages the interface between the network 240 and the internal components and controls the input / output of data from other computers 300. The network I / F 303 is, for example, a modem or a LAN adapter.

[0078] The recording medium I / F 304 controls the read / write of data to and from the recording medium 305 according to the control of the CPU 301. The recording medium I / F 304 is, for example, a disk drive, an SSD (Solid State Drive), a USB (Universal Serial Bus) port, etc. The recording medium 305 is a non-volatile memory that stores the data written under the control of the recording medium I / F 304. The recording medium 305 is, for example, a disk, a semiconductor memory, a USB memory, etc. The recording medium 305 may be detachable from the computer 300.

[0079] In addition to the components described above, the computer 300 may have, for example, a keyboard, a mouse, a display, a printer, a scanner, a microphone, a speaker, etc. Also, the computer 300 may have multiple recording medium I / Fs 304 and recording media 305. Further, the computer 300 may not have a recording medium I / F 304 or a recording medium 305.

[0080] (Functional Configuration Example of Information Processing Apparatus 100) Next, with reference to FIG. 4, a functional configuration example of an information processing apparatus 100 that can be a supplier-side management apparatus 211, a manufacturer-side management apparatus 221, a purchaser-side management apparatus 231, or the like will be described.

[0081] FIG. 4 is a block diagram showing a functional configuration example of the information processing apparatus 100. The information processing apparatus 100 includes a storage unit 400, an acquisition unit 401, an issuance unit 402, a registration unit 403, a calculation unit 404, and an output unit 405. The information processing apparatus 100 corresponds to any one of a plurality of steps related to a profit generation source.

[0082] The storage unit 400 is realized by a storage area such as the memory 302 and the recording medium 305 shown in FIG. 3, for example. Hereinafter, the case where the storage unit 400 is included in the information processing apparatus 100 will be described, but it is not limited thereto. For example, the storage unit 400 may be included in a device different from the information processing apparatus 100, and the stored content of the storage unit 400 may be referable from the information processing apparatus 100.

[0083] The acquisition unit 401 to the output unit 405 function as an example of a control unit. Specifically, the acquisition unit 401 to the output unit 405 realize their functions by causing the CPU 301 to execute a program stored in a storage area such as the memory 302 and the recording medium 305 shown in FIG. 3, or by the network I / F 303. The processing result of each functional unit is stored in a storage area such as the memory 302 and the recording medium 305 shown in FIG. 3, for example.

[0084] The storage unit 400 stores various information that is referred to or updated in the processing of each functional unit. The storage unit 400 stores, for example, a distributed ledger. The distributed ledger is formed by connecting blocks. The blocks are registered in the distributed ledger by the registration unit 403, for example.

[0085] Specifically, the storage unit 400 stores evidence data. The evidence data indicates, for example, the correspondence between any process, the performance value in the process related to the objective, and the performance type of the performance value. The evidence data is acquired, for example, by the acquisition unit 401. More specifically, the storage unit 400 stores the block including the evidence data by means of a distributed ledger. The block including the evidence data is acquired, for example, by the registration unit 403.

[0086] Specifically, the storage unit 400 stores tokens. The tokens indicate, for example, the correspondence between the source of profit and the evidence data registered in the distributed ledger for each process. The tokens are acquired, for example, by the acquisition unit 401. More specifically, the storage unit 400 stores the block including the tokens by means of a distributed ledger. The block including the tokens is acquired, for example, by the registration unit 403.

[0087] Specifically, the storage unit 400 stores the SC. Specifically, the storage unit 400 stores the first SC. The first SC has a function of converting, for example, the performance value in any process related to the objective into an index value indicating the degree of contribution to the objective, which is shown by a unified standard in a plurality of processes according to the performance type of the performance value. The first SC may have a function of converting, for example, the performance value in any process related to the objective into an index value indicating the degree of contribution to the objective, which is a contribution type corresponding to the performance type of the performance value. The first SC is acquired, for example, by the acquisition unit 401. More specifically, the storage unit 400 stores the block including the first SC by means of a distributed ledger. The block including the first SC is acquired, for example, by the registration unit 403.

[0088] The storage unit 400 specifically stores the second SC. The second SC has a function of calculating, for example, the ratio for distributing the profit obtained from the source of generation to a plurality of participants who share a plurality of processes, based on the index value indicating the degree of contribution to the objective in each process. The second SC may have a function of calculating, for example, the ratio for distributing the profit obtained from the source of generation to a plurality of participants, based on the index value indicating the degree of contribution to the objective, which is a different type of contribution. The second SC is obtained, for example, by the acquisition unit 401. More specifically, the storage unit 400 stores the block including the second SC in the distributed ledger. The block including the second SC is obtained, for example, by the registration unit 403.

[0089] The storage unit 400 specifically stores the calculation request. The calculation request includes the specification of a token. The calculation request requests to calculate the ratio for distributing the profit obtained from the source of generation corresponding to the specified token to a plurality of participants, based on the evidence data corresponding to the specified token. The calculation request is obtained, for example, by the acquisition unit 401. More specifically, the storage unit 400 stores the block including the calculation request in the distributed ledger. The block including the calculation request is obtained, for example, by the registration unit 403.

[0090] The acquisition unit 401 acquires various information used for the processing of each functional unit. The acquisition unit 401 stores the acquired various information in the storage unit 400 or outputs it to each functional unit. Also, the acquisition unit 401 may output the various information stored in the storage unit 400 to each functional unit. The acquisition unit 401 acquires various information, for example, based on the operation input of the user. The acquisition unit 401 may receive various information from a device different from the information processing apparatus 100, for example.

[0091] The acquisition unit 401 acquires, for example, a registration request for evidence data. The acquisition unit 401 acquires, for example, a registration request for evidence data when the own device corresponds to the supplier-side management device 211. The registration request includes, for example, evidence data. The registration request is generated, for example, in response to completion of any process. Specifically, the acquisition unit 401 acquires the registration request for evidence data by receiving it from another computer. The other computer is, for example, the supplier-side terminal device 212. Specifically, the acquisition unit 401 acquires the registration request for evidence data by accepting an input of the registration request for evidence data based on a user's operation input.

[0092] The acquisition unit 401 acquires, for example, a registration request for a token. The acquisition unit 401 acquires, for example, a registration request for a token when the own device corresponds to the manufacturer-side management device 221. The registration request includes, for example, a token. The registration request is generated, for example, in response to completion of a plurality of processes. Specifically, the acquisition unit 401 acquires the registration request for the token by receiving it from another computer. The other computer is, for example, the manufacturer-side terminal device 222. Specifically, the acquisition unit 401 acquires the registration request for the token by accepting an input of the registration request for the token based on a user's operation input.

[0093] The acquisition unit 401 acquires, for example, a registration request for a first SC corresponding to any process. The acquisition unit 401 acquires, for example, a registration request for a first SC corresponding to any process when the own device corresponds to the manufacturer-side management device 221. The registration request includes, for example, the first SC. The registration request includes, for example, a designation of any process. Specifically, the acquisition unit 401 acquires the registration request for the first SC by receiving it from another computer. The other computer is, for example, the manufacturer-side terminal device 222. Specifically, the acquisition unit 401 acquires the registration request for the first SC by accepting an input of the registration request for the first SC based on a user's operation input.

[0094] The acquisition unit 401 acquires, for example, the registration request of the second SC. The acquisition unit 401 acquires, for example, the registration request of the second SC when the own device corresponds to the manufacturer-side management device 221. The registration request includes, for example, the second SC. Specifically, the acquisition unit 401 acquires the registration request of the second SC by receiving it from another computer. The other computer is, for example, the manufacturer-side terminal device 222. Specifically, the acquisition unit 401 acquires the registration request of the second SC by accepting the input of the registration request of the second SC based on the user's operation input.

[0095] The acquisition unit 401 acquires, for example, the registration request of the calculation request. The acquisition unit 401 acquires, for example, the registration request of the calculation request when the own device corresponds to the purchaser-side management device 231. The registration request includes, for example, the calculation request. Specifically, the acquisition unit 401 acquires the registration request of the calculation request by receiving it from another computer. The other computer is the purchaser-side terminal device 232. Specifically, the acquisition unit 401 acquires the registration request of the calculation request by accepting the input of the registration request of the calculation request based on the user's operation input.

[0096] The acquisition unit 401 may receive a start trigger for starting the processing of any functional unit. The start trigger is, for example, that there has been a predetermined operation input by the user. The start trigger may be, for example, that predetermined information has been received from another computer. The start trigger may be, for example, that any functional unit has output predetermined information.

[0097] The acquisition unit 401 may receive, for example, the fact that various registration requests have been acquired as a start trigger for starting the processing of the issuing unit 402. The acquisition unit 401 may receive, for example, the detection that a block including a calculation request has been registered in the distributed ledger stored in the storage unit 400 as a start trigger for starting the processing of the calculation unit 404.

[0098] The issuing unit 402 issues a transaction. For example, the issuing unit 402 issues a transaction including the first SC. Specifically, the issuing unit 402 issues a transaction including the first SC in response to acquiring a registration request for the first SC corresponding to any step by the acquisition unit 401. Thereby, the issuing unit 402 can control the information processing apparatuses 100 to register a block including the first SC in the distributed ledger managed by each of the plurality of information processing apparatuses 100.

[0099] The issuing unit 402 issues a transaction including the second SC, for example. Specifically, the issuing unit 402 issues a transaction including the second SC in response to acquiring a registration request for the second SC by the acquisition unit 401. Thereby, the issuing unit 402 can control the information processing apparatuses 100 to register a block including the second SC in the distributed ledger managed by each of the plurality of information processing apparatuses 100.

[0100] The issuing unit 402 issues a transaction including evidence data, for example. Specifically, the issuing unit 402 issues a transaction including evidence data in response to acquiring a registration request for the evidence data by the acquisition unit 401. Thereby, the issuing unit 402 can control the information processing apparatuses 100 to register a block including the evidence data in the distributed ledger managed by each of the plurality of information processing apparatuses 100.

[0101] The issuing unit 402 issues a transaction including a token, for example. Specifically, the issuing unit 402 issues a transaction including a token in response to acquiring a registration request for the token by the acquisition unit 401. Thereby, the issuing unit 402 can control the information processing apparatuses 100 to register a block including the token in the distributed ledger managed by each of the plurality of information processing apparatuses 100.

[0102] The issuing unit 402 issues a transaction including a calculation request, for example. Specifically, the issuing unit 402 issues a transaction including a calculation request in response to the acquisition unit 401 acquiring a registration request for the calculation request. Thereby, the issuing unit 402 can control the information processing device 100 to register a block including the calculation request in the distributed ledger managed by each of the plurality of information processing devices 100 of the information processing device 100.

[0103] The registration unit 403 registers the first SC for each of the plurality of steps. The registration unit 403 may register one first SC common to two or more steps. For example, when the registration unit 403 receives a block including the first SC in response to a transaction, the registration unit 403 registers the block including the first SC in the distributed ledger. Thereby, the registration unit 403 can make the first SC available.

[0104] The registration unit 403 registers the second SC. For example, when the registration unit 403 receives a block including the second SC in response to a transaction, the registration unit 403 registers the block including the second SC in the distributed ledger. Thereby, the registration unit 403 can make the second SC available.

[0105] The registration unit 403 registers the trace data for any one of the steps. For example, when the registration unit 403 receives a block including the trace data in response to a transaction, the registration unit 403 registers the block including the trace data in the distributed ledger. Thereby, the registration unit 403 can make the trace data available. The registration unit 403 can make the performance values in each step regarding the purpose available.

[0106] The registration unit 403 registers a token for any of the processes. For example, when the registration unit 403 receives a block including a token in response to a transaction, it registers the block including the token in the distributed ledger. Thereby, the registration unit 403 can make the token available. When calculating the ratio for distributing the profit obtained from the origin corresponding to the token to a plurality of users, the registration unit 403 can identify which trace data should be referred to based on the token.

[0107] The registration unit 403 registers a calculation request for any of the processes. For example, when the registration unit 403 receives a block including a calculation request in response to a transaction, it registers the block including the calculation request in the distributed ledger. Thereby, the registration unit 403 can make the calculation request available. The registration unit 403 can identify based on which token it is required to calculate the ratio for distributing the profit to a plurality of users.

[0108] The calculation unit 404 calculates an index value for each process. For example, in response to registering a block including a calculation request that designates a token, the calculation unit 404 calculates an index value for each process. Specifically, the calculation unit 404 refers to the distributed ledger, uses the first SC corresponding to each process based on the token, and calculates the index value for the process according to the performance type of the performance value in the process related to the purpose. Thereby, the calculation unit 404 can obtain a guideline for calculating the ratio for distributing the profit obtained from the origin to a plurality of participants.

[0109] Specifically, the calculation unit 404 may calculate the index value for the process, which is the contribution type corresponding to the performance type of the performance value in the process related to the purpose, by referring to the distributed ledger, using the first SC corresponding to each process based on the token. Thereby, the calculation unit 404 can obtain a guideline for calculating the ratio for distributing the profit obtained from the origin to a plurality of participants. The calculation unit 404 can obtain a plurality of guidelines from different perspectives.

[0110] The calculation unit 404 calculates the ratio for distributing the profit obtained from the source of generation to a plurality of participants. For example, the calculation unit 404 uses the second SC to calculate the ratio for distributing the profit obtained from the source of generation to a plurality of participants according to the index values for the respective calculated steps. Thereby, the calculation unit 404 can appropriately distribute the profit obtained from the source of generation to a plurality of participants.

[0111] For example, the calculation unit 404 may calculate the ratio for distributing the profit obtained from the source of generation to a plurality of participants based on the weights for each contribution type according to the index values, which are the contribution types corresponding to the performance types of the actual values in the respective steps related to the purpose, using the second SC. Thereby, the calculation unit 404 can appropriately distribute the profit obtained from the source of generation to a plurality of participants in consideration of the index values of different contribution types.

[0112] The calculation unit 404 may calculate the distribution amount for distributing the profit obtained from the source of generation to each participant based on the calculated ratio. Thereby, the calculation unit 404 can appropriately distribute the profit obtained from the source of generation to each participant.

[0113] The output unit 405 outputs the processing result of at least any one of the functional units. The output format is, for example, display on a display, print output to a printer, transmission to an external device via the network I / F 303, or storage in a storage area such as the memory 302 or the recording medium 305. Thereby, the output unit 405 can notify the user of the processing result of at least any one of the functional units and improve the convenience of the information processing apparatus 100.

[0114] The output unit 405 outputs the ratio calculated by the calculation unit 404. For example, the output unit 405 outputs the ratio calculated by the calculation unit 404 in a manner that can be referred to by the user. For example, the output unit 405 may output the ratio calculated by the calculation unit 404 to a functional unit that distributes the profit obtained from the source of generation to each participant. The functional unit may be included outside the information processing apparatus 100, for example. Thereby, the calculation unit 404 can appropriately distribute the profit obtained from the source of generation to a plurality of participants.

[0115] The output unit 405 may output the distribution amount calculated by the calculation unit 404. For example, the output unit 405 outputs the distribution amount calculated by the calculation unit 404 in a manner that can be referred to by the user. For example, the output unit 405 may output the distribution amount calculated by the calculation unit 404 to a functional unit that distributes the profit obtained from the source of generation to each participant. The functional unit may be included outside the information processing apparatus 100, for example. Thereby, the calculation unit 404 can appropriately distribute the profit obtained from the source of generation to a plurality of participants.

[0116] (Functional configuration example of the information processing system 200) Next, with reference to FIG. 5, a functional configuration example of the information processing system 200 will be described.

[0117] FIG. 5 is a block diagram showing a functional configuration example of the information processing system 200. In FIG. 5, the manufacturer-side terminal device 222 includes a reception unit 501, a transmission unit 502, and a display unit 503. The reception unit 501 receives operation inputs from manufacturer-side users. The transmission unit 502 transmits, based on the received operation inputs from manufacturer-side users, requests for registering evidence data, requests for registering tokens, and requests for registering SCs, etc., to the manufacturer-side management device 221. The display unit 503 displays a screen for receiving operation inputs from manufacturer-side users.

[0118] Similarly, the supplier-side terminal device 212 includes a reception unit 501, a transmission unit 502, and a display unit 503. Also, the purchaser-side terminal device 232 similarly includes a reception unit 501, a transmission unit 502, and a display unit 503.

[0119] The manufacturer - side management device 221 includes a distributed ledger 510, a receiving unit 511, a processing unit 512, and a transmitting unit 513. The distributed ledger 510 stores, by including them in blocks, evidence data, tokens, SCs, etc. The receiving unit 511 receives a registration request for evidence data, a registration request for tokens, a registration request for SCs, etc. from the manufacturer - side terminal device 222. The receiving unit 511 receives a block including evidence data, a block including a token, a block including an SC, etc. from the block generation device 201.

[0120] The processing unit 512 corresponds to each functional unit shown in FIG. 4. The processing unit 512, in response to a calculation request, calculates an index value indicating the degree of contribution for each process using an SC based on the token specified in the calculation request, and calculates the ratio for distributing the consideration that becomes a profit to each participant. The transmitting unit 513 transmits, in response to various registration requests, a transaction including evidence data, a transaction including a token, a transaction including an SC, etc. to the block generation device 201.

[0121] Similarly, the supplier - side management device 211 includes a distributed ledger 510, a receiving unit 511, a processing unit 512, and a transmitting unit 513. Also, the purchaser - side management device 231 similarly includes a distributed ledger 510, a receiving unit 511, a processing unit 512, and a transmitting unit 513.

[0122] The block generation device 201 includes a receiving unit 521, a generating unit 522, and a transmitting unit 523. The receiving unit 521 accepts transactions. The receiving unit 521 receives, for example, a transaction including evidence data, a transaction including a token, a transaction including an SC, etc. from the manufacturer - side management device 221, the supplier - side management device 211, or the purchaser - side management device 231.

[0123] The generation unit 522 generates blocks according to transactions. The generation unit 522 generates, for example, blocks including trace data, blocks including tokens, and blocks including SCs according to various transactions. The transmission unit 523 transmits the generated blocks to the manufacturer-side management device 221, the supplier-side management device 211, or the purchaser-side management device 231. The block generation device 201 is a mining node or an Ordering Service of Hyperledger Fabric, which is open-source software of a consortium-type blockchain. [x] in the figure indicates the participant x corresponding to a computer such as the manufacturer-side management device 221, the supplier-side management device 211, or the purchaser-side management device 231.

[0124] (Flow of operations of the information processing system 200) Next, with reference to FIG. 6, the flow of operations of the information processing system 200 will be described.

[0125] FIG. 6 is an explanatory diagram showing the flow of operations of the information processing system 200. In FIG. 6, the distributed ledger 510 is managed in a blockchain network. The blockchain network includes the supplier-side management device 211, the manufacturer-side management device 221, and the purchaser-side management device 231 as nodes. The distributed ledger 510 is shared by various devices serving as nodes.

[0126] The distributed ledger 510 stores a trace data store 610, a token data store 620, and an SC store 630. The trace data store 610 contains trace data. The token data store 620 contains tokens. The SC store 630 contains SCs. The SC store 630 includes, for example, a consideration ratio calculation SC 601. The SC store 630 includes, for example, a contribution standard pool 602. The contribution standard pool 602 includes, for example, a contribution value calculation SC 603.

[0127] (7-1) The manufacturer uses the manufacturer-side terminal device 222 to generate a contribution value calculation SC603 that describes the process of calculating the contribution value based on the actual performance value. The contribution value calculation SC603 includes, for example, "Data Type" representing the actual performance type of the actual performance value and a "calculation formula for converting the actual performance value into the contribution value". The manufacturer-side terminal device 222 transmits the contribution value calculation SC603 to the manufacturer-side management device 221. The manufacturer-side management device 221 registers the contribution value calculation SC603 in the SC store 630 of the distributed ledger 510. Thereby, the contribution value calculation SC603 is shared by various devices serving as nodes.

[0128] (7-2) When the supplier completes the process related to the product it is in charge of, the supplier uses the supplier-side terminal device 212 to generate trace data including the actual performance value. The trace data includes, for example, "Trace ID" which is the identification information of the trace data, the "actual performance value" in the process related to the product, "Data Type" representing the actual performance type of the actual performance value, and "account information" representing the participants to whom the consideration is allocated. The supplier-side terminal device 212 transmits the trace data to the supplier-side management device 211. The supplier-side management device 211 registers the trace data in the trace data store 610 of the distributed ledger 510. Thereby, the trace data is shared by various devices serving as nodes.

[0129] (7-3) When the manufacturer completes the process related to the product it is in charge of and produces the product, the manufacturer uses the manufacturer-side terminal device 222 to generate a token. The token includes, for example, "Token ID" which is the identification information of the token, "token owner information (owner)" representing the participant who generated the token, and "product information" representing the product for which the consideration is paid. The token further includes, for example, "Trace ID" which is the identification information of the trace data related to each process of the product. The manufacturer-side terminal device 222 transmits the token to the manufacturer-side management device 221. The manufacturer-side management device 221 registers the token in the token data store 620 of the distributed ledger 510. Thereby, the token is shared by various devices serving as nodes.

[0130] (7-4) The purchaser purchases the product and pays the consideration for the product. For example, the purchaser purchases a token related to the product and pays the consideration for the token. The purchaser uses the purchaser-side terminal device 232 to generate a calculation request including the specification of the token. The calculation request includes, for example, the "token ID" which is the identification information of the token. The purchaser-side terminal device 232 transmits the calculation request to the purchaser-side management device 231. The purchaser-side management device 231 registers the calculation request in the distributed ledger 510. As a result, the calculation request is shared by various devices serving as nodes.

[0131] (7-5) Various devices serving as nodes calculate a consideration ratio representing the ratio for distributing the consideration to each participant by using the contribution value calculation SC603 and the consideration ratio calculation SC601 in response to the calculation request. The contribution value calculation SC603 may be controlled by, for example, the consideration ratio calculation SC601.

[0132] For example, in the manufacturer-side management device 221, the consideration ratio calculation SC601 searches for the token from the distributed ledger 510 using the token ID included in the calculation request as a key. For example, the consideration ratio calculation SC601 searches for the trace data from the distributed ledger 510 using the trace ID included in the searched token as a key. For example, the consideration ratio calculation SC601 acquires the Data Type, the actual value, and the account information included in the searched trace data. For example, the consideration ratio calculation SC601 identifies the contribution value calculation SC603 corresponding to the acquired Data Type and inputs the actual value.

[0133] For example, the contribution value calculation SC603 calculates a contribution value obtained by converting the input actual value using the calculation formula included in the contribution value calculation SC603 and inputs it to the consideration ratio calculation SC601. Specifically, if the actual value is the amount of power, [Contribution value]=100-[Amount of power]*2 is calculated. Specifically, if the actual value is the amount of fuel, [Contribution value]=100-[Amount of fuel]*14 is calculated.

[0134] For example, the consideration ratio calculation SC601 obtains the contribution value converted for each piece of evidence data, and based on the obtained contribution value, uses the calculation formula included in the consideration ratio calculation SC601 to calculate the consideration ratio. Specifically, [consideration ratio] = [any contribution value] / [total value of contribution values] * 100 is calculated. More specifically, for Supplier 1, [consideration ratio] =

[20] / [20 + 30] * 100 = 40% is calculated. More specifically, for Supplier 2, [consideration ratio] =

[30] / [20 + 30] * 100 = 60% is calculated.

[0135] Thereby, the information processing system 200 can calculate an appropriate consideration ratio. The information processing system 200 can separately manage the contribution value calculation SC603 for each contribution criterion, manage the evidence data with tokens, and make it possible to identify the evidence data corresponding to the token when a consideration occurs for the token.

[0136] Therefore, the information processing system 200 can suppress the adverse effects on each participant when adding the contribution value calculation SC603 or the like. Therefore, the information processing system 200 can be made more adaptable to changes in the situation. The information processing system 200 can appropriately manage the evidence data, make it easier to calculate the consideration ratio, and make it easier to identify the participant who gives the consideration.

[0137] (First operation example of information processing system 200) Next, with reference to FIGS. 7 to 24, the first operation example of the information processing system 200 will be described.

[0138] FIGS. 7 to 24 are explanatory diagrams showing the first operation example of the information processing system 200. Specifically, FIGS. 7 and 8 show the initial state of the distributed ledger 510. As shown in FIG. 7, the distributed ledger 510 stores the consideration ratio calculation SC601. The consideration ratio calculation SC601 includes a calculation formula. The distributed ledger 510 has a contribution criterion pool 602. Next, the description of FIG. 8 will be continued.

[0139] As shown in FIG. 8, the distributed ledger 510 stores the evidence data store 610, the token data store 620, and the consideration ratio data store 800. In the initial state, the evidence data store 610 is empty. The token data store 620 is empty. The consideration ratio data store 800 is empty.

[0140] The evidence data store 610 has fields for an evidence ID, a data type, an actual value, and an account. The evidence data store 610 stores evidence data as records by setting information in each field for each process. In the field of the evidence ID, the "evidence ID", which is the identification information of the evidence data, is set. In the field of the data type, the "data type", which represents the type of actual value of the actual value, is set. In the field of the actual value, the "actual value" is set. In the field of the account, the "account information", which represents the participant to whom the consideration is distributed, is set.

[0141] The token data store 620 has fields for a token ID, an owner, product information, and an evidence ID. The token data store 620 stores tokens as records by setting information in each field for each product. In the field of the token ID, the "token ID", which is the identification information of the token, is set. In the field of the owner, the "token owner information (owner)", which represents the participant who generated the token, is set. In the field of the product information, the "product information", which represents the product for which the consideration is paid, is set. In the field of the evidence ID, the "evidence ID", which is the identification information of the evidence data related to each process of the product, is set.

[0142] The consideration ratio data store 800 has fields for a token ID, a payee, and a consideration ratio. The consideration ratio data store 800 stores the consideration ratio as a record by setting information in each field for each participant. In the field for the token ID, a "token ID" which is identification information of token data regarding the product for which the consideration has occurred is set. In the field for the payee, "participant information" which represents the participant for whom the consideration ratio is calculated and to whom the consideration is given is set. In the field for the consideration ratio, a "consideration ratio" corresponding to the participant is set. Next, we will move on to the description of FIG. 9.

[0143] FIG. 9 specifically shows a sequence diagram illustrating an example of an SC registration processing procedure for registering a contribution value calculation SC603 in the information processing system 200. In FIG. 9, the manufacturer-side terminal device 222 generates a contribution value calculation SC603 based on an operation input by a manufacturer-side user.

[0144] In the following description, the different types of contribution value calculations SC603 may be denoted as "contribution value calculation SCX603" for distinguishability. X is A, B, C, etc. In the example of FIG. 9, the manufacturer-side terminal device 222 generates a contribution value calculation SCA603. The contribution value calculation SC603 is generated from the perspective of environmental protection by the manufacturer or an expert regarding environmental protection.

[0145] The manufacturer-side terminal device 222 transmits an SC registration transaction issuance request including the generated contribution value calculation SCA603 to the manufacturer-side management device 221 serving as a node (step S901). When the manufacturer-side management device 221 receives the SC registration transaction issuance request, it generates an SC registration transaction including the contribution value calculation SCA603 and attaches a signature (step S902). The manufacturer-side management device 221 issues the SC registration transaction to the block generation device 201 (step S903).

[0146] When the block generation device 201 receives an SC registration transaction, it sends a completion notice to the manufacturer-side management device 221 (step S904). When the manufacturer-side management device 221 receives the completion notice, it sends the completion notice to the manufacturer-side terminal device 222 (step S905).

[0147] When the block generation device 201 receives an SC registration transaction, it generates a block including the contribution value calculation SCA603 (step S906). The block generation device 201 distributes the generated block to the manufacturer-side management device 221 (step S907). The block generation device 201 distributes the generated block to various devices 900 serving as nodes (step S908).

[0148] The various devices 900 are, for example, the supplier-side management device 211 corresponding to supplier 1, the supplier-side management device 211 corresponding to supplier 2, the supplier-side management device 211 corresponding to supplier 3, and the purchaser-side management device 231, etc.

[0149] When the manufacturer-side management device 221 receives a block by the processing unit 512, it verifies the received block (step S909). When the block is verified as legitimate by the processing unit 512 of the manufacturer-side management device 221, it registers the block in the distributed ledger 510 (step S910). The manufacturer-side management device 221 receives a completion notice from the distributed ledger 510 by the processing unit 512 (step S911).

[0150] When the various devices 900 receive a block by the processing unit 512, they verify the received block (step S912). When the block is verified as legitimate by the processing unit 512 of the various devices 900, they register the block in the distributed ledger 510 (step S913). The various devices 900 receive a completion notice from the distributed ledger 510 by the processing unit 512 (step S914). Thus, the information processing system 200 can share the contribution value calculation SC603 among multiple nodes. Next, we will move on to the description of FIG. 10.

[0151] Specifically, FIG. 10 shows the state of the distributed ledger 510. As shown in FIG. 10, through the SC registration process, the distributed ledger 510 stores the contribution value calculation SCA603 in the contribution standard pool 602. Thereby, the contribution value calculation SCA603 can be made referable in the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like. In the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like, it is possible to calculate the contribution value based on the performance value.

[0152] The supplier can grasp that it is sufficient to contribute to environmental protection from the perspective indicated by the contribution value calculation SC603 with reference to the contribution standard pool 602. If there are a plurality of contribution value calculations SC603 in the contribution standard pool 602, the supplier can select, with reference to the contribution standard pool 602, which contribution value calculation SC603 contributes to environmental protection from the perspective indicated. If the supplier wishes to contribute to environmental protection from other perspectives, the supplier can register the contribution value calculation SC603 from other perspectives in the distributed ledger 510 via the supplier-side management device 211 or by requesting the manufacturer.

[0153] The contribution value calculation SCA603 includes the data type (Data Type) which is the type of the performance value and the calculation formula that enables the calculation of the contribution value based on the performance value. The calculation formula calculates, for example, the contribution value = CO2 reduction amount. Specifically, the calculation formula is 100 - p * 2. p is the performance value. The performance value is, for example, the power consumption. The smaller the power consumption, the larger the CO2 reduction amount, and thus the larger the contribution value. Next, the description of FIG. 11 will be moved on.

[0154] Specifically, FIG. 11 shows a sequence diagram showing an example of the trace data registration processing procedure for registering trace data in the information processing system 200. In FIG. 11, the supplier-side user corresponding to Supplier 1 selects the data type (Data Type) of the performance value in the process of Supplier 1.

[0155] The supplier-side user inputs the correspondence relationship between the selected performance type Data Type and the performance value into the supplier-side terminal device 212 corresponding to Supplier 1. Based on the operation input of the supplier-side user, the supplier-side terminal device 212 generates evidence data. In the example of FIG. 11, the supplier-side terminal device 212 generates evidence data 1 including evidence ID = A1, performance type Data Type = A (electric energy quantity), performance value, and account information.

[0156] The supplier-side terminal device 212 sends a request to issue an evidence data registration transaction including the generated evidence data 1 to the supplier-side management device 211 serving as a node (step S1101). When the supplier-side management device 211 receives the request to issue an evidence data registration transaction, it generates an evidence data registration transaction including the evidence data 1 and attaches a signature (step S1102). The supplier-side management device 211 issues the evidence data registration transaction to the block generation device 201 (step S1103).

[0157] When the block generation device 201 receives the evidence data registration transaction, it sends a completion notice to the supplier-side management device 211 (step S1104). When the supplier-side management device 211 receives the completion notice, it sends the completion notice to the supplier-side terminal device 212 (step S1105).

[0158] When the block generation device 201 receives the evidence data registration transaction, it generates a block including the evidence data 1 (step S1106). The block generation device 201 distributes the generated block to the supplier-side management device 211 (step S1107). The block generation device 201 distributes the generated block to various devices 1100 serving as nodes (step S1108).

[0159] The various devices 1100 are, for example, the manufacturer-side management device 221, the supplier-side management device 211 corresponding to the supplier 2, the supplier-side management device 211 corresponding to the supplier 3, and the purchaser-side management device 231, etc.

[0160] When the supplier-side management device 211 receives a block by the processing unit 512, it verifies the received block (step S1109). When the block is verified as legitimate by the processing unit 512, the supplier-side management device 211 registers the block in the distributed ledger 510 (step S1110). The supplier-side management device 211 receives a completion notice from the distributed ledger 510 by the processing unit 512 (step S1111).

[0161] When the various devices 1100 receive a block by the processing unit 512, they verify the received block (step S1112). When the block is verified as legitimate by the processing unit 512, the various devices 1100 register the block in the distributed ledger 510 (step S1113). The various devices 1100 receive a completion notice from the distributed ledger 510 by the processing unit 512 (step S1114). Thereby, the information processing system 200 can share the trace data 1 among a plurality of nodes.

[0162] Similarly, assume that the supplier-side terminal device 212 corresponding to the supplier 2 generates the trace data 2 including the trace ID = B1, the performance type Data Type = A (electric energy quantity), the performance value, and the account information based on the operation input of the supplier-side user. Assume that the information processing system 200 shares the trace data 2 among a plurality of nodes. Next, the description will move on to FIG. 12.

[0163] Figure 12 specifically shows the state of the distributed ledger 510. As shown in Figure 12, through the evidence data registration process, the distributed ledger 510 will store evidence data 1 and evidence data 2 in the evidence data store 610. As a result, it becomes possible for the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. to refer to evidence data 1 and evidence data 2. It becomes possible for the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. to specify the actual values based on the evidence data. Next, we will move on to the explanation of Figure 13.

[0164] Figure 13 specifically shows a sequence diagram illustrating an example of the token registration processing procedure for registering tokens in the information processing system 200. In Figure 13, the manufacturer-side user inputs, to the manufacturer-side terminal device 222, the correspondence between the product information representing the product and the evidence ID = A1, B1 representing the evidence data related to the product, in response to the production of the product. The product information is, for example, a URI (Uniform Resource Identifier), or the individual identification information of the product, etc.

[0165] Based on the operation input of the manufacturer-side user, the manufacturer-side terminal device 222 generates a token. In the example of Figure 13, the manufacturer-side terminal device 222 generates token 1 including the product information representing the product and the evidence ID = A1, B1 representing the evidence data related to the product.

[0166] The manufacturer-side terminal device 222 sends a token registration transaction issuance request including the generated token 1 to the manufacturer-side management device 221 serving as a node (step S1301). When receiving the token registration transaction issuance request, the manufacturer-side management device 221 generates a token registration transaction including token 1 and attaches a signature (step S1302). The manufacturer-side management device 221 issues the token registration transaction to the block generation device 201 (step S1303).

[0167] When the block generation device 201 receives a token registration transaction, it sends a completion notice to the manufacturer-side management device 221 (step S1304). When the manufacturer-side management device 221 receives the completion notice, it sends the completion notice to the manufacturer-side terminal device 222 (step S1305).

[0168] When the block generation device 201 receives a token registration transaction, it generates a block including Token 1 (step S1306). The block generation device 201 distributes the generated block to the manufacturer-side management device 221 (step S1307). The block generation device 201 distributes the generated block to various devices 1300 serving as nodes (step S1308).

[0169] The various devices 1300 are, for example, a supplier-side management device 211 corresponding to Supplier 1, a supplier-side management device 211 corresponding to Supplier 2, a supplier-side management device 211 corresponding to Supplier 3, and a purchaser-side management device 231, etc.

[0170] When the manufacturer-side management device 221 receives a block by the processing unit 512, it verifies the received block (step S1309). When the block is verified to be legitimate by the processing unit 512 of the manufacturer-side management device 221, it registers the block in the distributed ledger 510 (step S1310). The manufacturer-side management device 221 receives a completion notice from the distributed ledger 510 by the processing unit 512 (step S1311).

[0171] When the various devices 1300 receive a block by the processing unit 512, they verify the received block (step S1312). When the block is verified to be legitimate by the processing unit 512 of the various devices 1300, they register the block in the distributed ledger 510 (step S1313). The various devices 1300 receive a completion notice from the distributed ledger 510 by the processing unit 512 (step S1314). Thereby, the information processing system 200 can share Token 1 among a plurality of nodes. Next, the description of FIG. 14 will be moved on.

[0172] FIG. 14 specifically shows the state of the distributed ledger 510. As shown in FIG. 14, through the token registration process, the distributed ledger 510 will store Token 1 in the token data store 620. As a result, the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can refer to Token 1. The supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can identify the evidence data to be referred to when distributing the consideration based on Token 1. Next, the description will proceed to FIGS. 15 and 16.

[0173] FIGS. 15 and 16 specifically show a sequence diagram illustrating an example of the calculation processing procedure for calculating the consideration ratio for distributing the consideration in the information processing system 200. In FIG. 15, when the purchaser-side user pays the consideration for Token 1, the purchaser-side user inputs the token ID into the purchaser-side terminal device 232. Based on the operation input of the purchaser-side user, the purchaser-side terminal device 232 generates a consideration ratio calculation request including the token ID. In the example of FIG. 15, the purchaser-side terminal device 232 generates a consideration ratio calculation request including the token ID of Token 1.

[0174] The purchaser-side terminal device 232 transmits a consideration ratio calculation transaction issuance request including the generated consideration ratio calculation request to the purchaser-side management device 231 serving as a node (step S1501). When receiving the consideration ratio calculation transaction issuance request, the purchaser-side management device 231 generates and signs a consideration ratio calculation transaction including the consideration ratio calculation request (step S1502). The purchaser-side management device 231 issues the consideration ratio calculation transaction to the block generation device 201 (step S1503).

[0175] When receiving the consideration ratio calculation transaction, the block generation device 201 transmits a completion notice to the purchaser-side management device 231 (step S1504). When receiving the completion notice, the purchaser-side management device 231 transmits the completion notice to the purchaser-side terminal device 232 (step S1505).

[0176] When the block generation device 201 receives the consideration ratio calculation transaction, it generates a block including the consideration ratio calculation request (step S1506). The block generation device 201 distributes the generated block to the purchaser side management device 231 (step S1507).

[0177] When the purchaser side management device 231 receives a block by the processing unit 512, it verifies the received block (step S1508). When the block is verified to be legitimate by the processing unit 512 of the purchaser side management device 231, it executes the consideration ratio calculation SC601 and inputs the token ID included in the block to the consideration ratio calculation SC601 (step S1509).

[0178] The purchaser side management device 231 searches for the token corresponding to the token ID from the token data store 620 using the token ID as a key by the consideration ratio calculation SC601 (step S1510). The purchaser side management device 231 acquires token 1 by the consideration ratio calculation SC601 (step S1511).

[0179] The purchaser side management device 231 searches for the evidence data corresponding to the evidence ID from the evidence data store 610 using the evidence ID included in the token as a key by the consideration ratio calculation SC601 (step S1512). The purchaser side management device 231 acquires evidence data 1 and evidence data 2 by the consideration ratio calculation SC601 (step S1513).

[0180] The purchaser side management device 231 executes the contribution value calculation SCA603 based on the evidence data 1 by the consideration ratio calculation SC601 (step S1514). The consideration ratio calculation SC601 passes, for example, the performance value = 40 to the contribution value calculation SCA603. The purchaser side management device 231 acquires the contribution value = 20 calculated by the contribution value calculation SCA603 by the consideration ratio calculation SC601 (step S1515).

[0181] The purchaser-side management device 231 executes contribution value calculation SCA603 based on the evidence data 2 by means of consideration ratio calculation SC601 (step S1516). The consideration ratio calculation SC601 passes, for example, the actual value = 35 to the contribution value calculation SCA603. The purchaser-side management device 231 acquires the contribution value = 30 calculated by the contribution value calculation SCA603 by means of the consideration ratio calculation SC601 (step S1517).

[0182] The purchaser-side management device 231 calculates the consideration ratio for each participant based on the acquired contribution value by means of the consideration ratio calculation SC601 (step S1518). The purchaser-side management device 231, for example, calculates the consideration ratio x n = y n / y sum by means of the consideration ratio calculation SC601. y n is the contribution value. y sum is the total of the contribution values. n is the number of the participant.

[0183] Specifically, the purchaser-side management device 231 calculates the consideration ratio of supplier 1 as 20 / (20 + 30) = 0.4 and the consideration ratio of supplier 2 as 30 / (20 + 30) = 0.6 by means of the consideration ratio calculation SC601. The purchaser-side management device 231 registers the correspondence between the token ID and the calculated consideration ratio for each participant in the consideration ratio data store 800 of the distributed ledger 510 by means of the consideration ratio calculation SC601 (step S1519).

[0184] The purchaser-side management device 231 receives a completion notice from the distributed ledger 510 by means of the consideration ratio calculation SC601 (step S1520). The purchaser-side management device 231 transmits the completion notice to the processing unit 512 by means of the consideration ratio calculation SC601 (step S1521). Thereafter, the purchaser-side management device 231 gives consideration to each participant based on the consideration ratio. Next, the description of FIG. 16 is proceeded with.

[0185] In FIG. 16, the block generation device 201 distributes the generated blocks to various devices 1600 serving as nodes (step S1601). The various devices 1600 are, for example, the manufacturer - side management device 221, the supplier - side management device 211 corresponding to supplier 1, the supplier - side management device 211 corresponding to supplier 2, and the supplier - side management device 211 corresponding to supplier 3, etc.

[0186] When the various devices 1600 receive a block by the processing unit 512, they verify the received block (step S1602). When the block is verified as legitimate by the processing unit 512 of the various devices 1600, they execute the consideration ratio calculation SC601 and input the token ID included in the block into the consideration ratio calculation SC601 (step S1603).

[0187] The various devices 1600 search for the token corresponding to the token ID from the token data store 620 using the token ID as a key by the consideration ratio calculation SC601 (step S1604). The various devices 1600 acquire token 1 by the consideration ratio calculation SC601 (step S1605).

[0188] The various devices 1600 search for the evidence data corresponding to the evidence ID from the evidence data store 610 using the evidence ID included in token 1 as a key by the consideration ratio calculation SC601 (step S1606). The various devices 1600 acquire evidence data 1 and evidence data 2 by the consideration ratio calculation SC601 (step S1607).

[0189] The various devices 1600 execute the contribution value calculation SCA603 based on the evidence data 1 by the consideration ratio calculation SC601 (step S1608). The consideration ratio calculation SC601 passes, for example, the performance value = 40 to the contribution value calculation SCA603. The various devices 1600 acquire the contribution value = 20 calculated by the contribution value calculation SCA603 by the consideration ratio calculation SC601 (step S1609).

[0190] Various devices 1600 execute contribution value calculation SCA603 based on evidence data 2 by means of consideration ratio calculation SC601 (step S1610). The consideration ratio calculation SC601 passes, for example, the actual value = 35 to the contribution value calculation SCA603. The various devices 1600 obtain the contribution value = 30 calculated by the contribution value calculation SCA603 by means of the consideration ratio calculation SC601 (step S1611).

[0191] The various devices 1600 calculate the consideration ratio for each participant based on the obtained contribution value by means of the consideration ratio calculation SC601 (step S1612). The various devices 1600 calculate, for example, the consideration ratio x n = y n / y sum . y n is the contribution value. y sum is y n belonging to the same contribution type as y n is the total of the contribution values including y. n is the number of the participant.

[0192] Specifically, the various devices 1600 calculate the consideration ratio of supplier 1 as 20 / (20 + 30) = 0.4 and the consideration ratio of supplier 2 as 30 / (20 + 30) = 0.6 by means of the consideration ratio calculation SC601. The various devices 1600 register the correspondence between the token ID and the calculated consideration ratio for each participant in the consideration ratio data store 800 of the distributed ledger 510 by means of the consideration ratio calculation SC601 (step S1613).

[0193] The various devices 1600 receive a completion notice from the distributed ledger 510 by means of the consideration ratio calculation SC601 (step S1614). The various devices 1600 send the completion notice to the processing unit 512 by means of the consideration ratio calculation SC601 (step S1615). Thereafter, the various devices 1600 give consideration to each participant based on the consideration ratio. Next, the description of FIG. 17 will be moved on.

[0194] FIG. 17 specifically shows the state of the distributed ledger 510. As shown in FIG. 17, through the consideration ratio calculation process, the distributed ledger 510 will store the consideration ratio for each participant in the consideration ratio data store 800. Thereby, the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can refer to the consideration ratio. The supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can appropriately distribute the consideration based on the consideration ratio.

[0195] In this way, the information processing system 200 can appropriately distribute the consideration to each participant from the perspective of the amount of CO2 reduction caused by the power consumption. Next, we will move on to the description of FIG. 18.

[0196] In FIG. 18, it is assumed that it is desired to appropriately distribute the consideration to each participant considering other perspectives in addition to the amount of CO2 reduction caused by the power consumption. Other perspectives are, for example, the amount of CO2 reduction caused by the fuel quantity. In this case, similar to the SC registration process shown in FIG. 9, the information processing system 200 registers the contribution value calculation SCB603 regarding other perspectives in addition to the amount of CO2 reduction caused by the power consumption in the distributed ledger 510 and shares it among multiple nodes.

[0197] FIG. 18 specifically shows the state of the distributed ledger 510. As shown in FIG. 18, through the SC registration process, the distributed ledger 510 will store the contribution value calculation SCB603 in the contribution standard pool 602. Thereby, the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can refer to the contribution value calculation SCB603. The supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can calculate the contribution value based on the actual performance value.

[0198] The information processing system 200 can share the contribution value calculation SCB603 among the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc., without affecting the existing contribution value calculation SCA603 and the consideration ratio calculation SC601. Therefore, the information processing system 200 does not need to rewrite the SC, and can reduce costs. Since the information processing system 200 does not need to rewrite the SC, it can easily suppress the occurrence of program bugs and improve reliability.

[0199] The contribution value calculation SCB603 includes the data type which is the type of the actual value, and a calculation formula that enables the calculation of the contribution value based on the actual value. The calculation formula is, for example, to calculate the contribution value = CO2 reduction amount. Specifically, the calculation formula is 100 - p * 10. p is the actual value. The actual value is, for example, the fuel quantity. The smaller the fuel quantity, the larger the CO2 reduction amount, and thus the larger the contribution value. Next, we will move on to the description of FIG. 19.

[0200] In FIG. 19, assume that the supplier-side terminal device 212 corresponding to Supplier 1 generates the trace data 3 in the same manner as the trace data registration process shown in FIG. 11. The trace data 3 includes, for example, based on the operation input of the supplier-side user, trace ID = A2, actual type Data Type = A (power consumption), actual value, and account information. Assume that the information processing system 200 registers the trace data 3 in the distributed ledger 510 and shares it among multiple nodes in the same manner as the trace data registration process shown in FIG. 11.

[0201] Also, assume that the supplier-side terminal device 212 corresponding to Supplier 2 generates the trace data 4 in the same manner as the trace data registration process shown in FIG. 11. The trace data 4 includes, for example, based on the operation input of the supplier-side user, trace ID = B2, actual type Data Type = A (power consumption), actual value, and account information. Assume that the information processing system 200 registers the trace data 4 in the distributed ledger 510 and shares it among multiple nodes in the same manner as the trace data registration process shown in FIG. 11.

[0202] Also, assume that the supplier-side terminal device 212 corresponding to Supplier 3 generates trace data 5 in the same manner as the trace data registration process shown in FIG. 11. The trace data 5 includes, for example, a trace ID = C2, a performance type Data Type = B (fuel quantity), a performance value, and account information based on the operation input of the supplier-side user. The information processing system 200 registers the trace data 5 in the distributed ledger 510 and shares it among multiple nodes in the same manner as the trace data registration process shown in FIG. 11.

[0203] Specifically, FIG. 19 shows the state of the distributed ledger 510. As shown in FIG. 19, through the trace data registration process, the distributed ledger 510 stores the trace data 3, the trace data 4, and the trace data 5 in the trace data store 610. As a result, the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can refer to the trace data 3, the trace data 4, and the trace data 5. The supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can identify the performance value based on the trace data. Next, we will move on to the description of FIG. 20.

[0204] In FIG. 20, in response to the production of the product, the manufacturer-side user inputs the correspondence between the product information representing the product and the trace IDs = A2, B2, C2 representing the trace data related to the product into the manufacturer-side terminal device 222. The manufacturer-side terminal device 222 generates a token 2 including the product information representing the product and the trace IDs = A2, B2, C2 representing the trace data related to the product. The information processing system 200 registers the token 2 in the distributed ledger 510 and shares it among multiple nodes in the same manner as the token registration process shown in FIG. 13.

[0205] FIG. 20 specifically shows the state of the distributed ledger 510. As shown in FIG. 20, through the token registration process, the distributed ledger 510 will store a new token 2 in the token data store 620. Thereby, the new token 2 can be made accessible to the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. The supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can identify the evidence data to be referred to when allocating consideration based on the new token 2. Next, the description will proceed to FIGS. 21 to 23.

[0206] FIGS. 21 to 23 specifically show a sequence diagram illustrating an example of a calculation processing procedure for calculating a consideration ratio for allocating consideration in the information processing system 200. In FIG. 21, when the purchaser-side user pays consideration for token 2, the purchaser-side user inputs the token ID into the purchaser-side terminal device 232. Based on the operation input of the purchaser-side user, the purchaser-side terminal device 232 generates a consideration ratio calculation request including the token ID. In the example of FIG. 21, the purchaser-side terminal device 232 generates a consideration ratio calculation request including the token ID of token 2.

[0207] The purchaser-side terminal device 232 transmits a consideration ratio calculation transaction issuance request including the generated consideration ratio calculation request to the purchaser-side management device 231 serving as a node (step S2101). When receiving the consideration ratio calculation transaction issuance request, the purchaser-side management device 231 generates a consideration ratio calculation transaction including the consideration ratio calculation request and attaches a signature (step S2102). The purchaser-side management device 231 issues the consideration ratio calculation transaction to the block generation device 201 (step S2103).

[0208] When receiving the consideration ratio calculation transaction, the block generation device 201 transmits a completion notice to the purchaser-side management device 231 (step S2104). When receiving the completion notice, the purchaser-side management device 231 transmits the completion notice to the purchaser-side terminal device 232 (step S2105).

[0209] When the block generation device 201 receives the consideration ratio calculation transaction, it generates a block including the consideration ratio calculation request (step S2106). Next, the description proceeds to FIG. 22.

[0210] In FIG. 22, the block generation device 201 distributes the generated block to the purchaser-side management device 231 (step S2201). When the purchaser-side management device 231 receives the block by the processing unit 512, it verifies the received block (step S2202). When the purchaser-side management device 231 verifies that the block is legitimate by the processing unit 512, it executes the consideration ratio calculation SC601 and inputs the token ID included in the block to the consideration ratio calculation SC601 (step S2203).

[0211] The purchaser-side management device 231 searches for the token corresponding to the token ID from the token data store 620 using the token ID as a key by the consideration ratio calculation SC601 (step S2204). The purchaser-side management device 231 acquires token 2 by the consideration ratio calculation SC601 (step S2205).

[0212] The purchaser-side management device 231 searches for the evidence data corresponding to the evidence ID from the evidence data store 610 using the evidence ID included in token 2 as a key by the consideration ratio calculation SC601 (step S2206). The purchaser-side management device 231 acquires evidence data 3, evidence data 4, and evidence data 5 by the consideration ratio calculation SC601 (step S2207).

[0213] The purchaser-side management device 231 executes the contribution value calculation SCA603 based on the evidence data 3 by the consideration ratio calculation SC601 (step S2208). The consideration ratio calculation SC601 passes, for example, the actual value = 40 to the contribution value calculation SCA603. The purchaser-side management device 231 acquires the contribution value = 20 calculated by the contribution value calculation SCA603 by the consideration ratio calculation SC601 (step S2209).

[0214] The purchaser-side management device 231 executes contribution value calculation SCA603 based on the evidence data 4 by means of consideration ratio calculation SC601 (step S2210). The consideration ratio calculation SC601 passes, for example, the actual value = 35 to the contribution value calculation SCA603. The purchaser-side management device 231 acquires the contribution value = 30 calculated by the contribution value calculation SCA603 by means of the consideration ratio calculation SC601 (step S2211).

[0215] The purchaser-side management device 231 executes contribution value calculation SCB603 based on the evidence data 5 by means of consideration ratio calculation SC601 (step S2212). The consideration ratio calculation SC601 passes, for example, the actual value = 5 to the contribution value calculation SCB603. The purchaser-side management device 231 acquires the contribution value = 50 calculated by the contribution value calculation SCB603 by means of the consideration ratio calculation SC601 (step S2213).

[0216] The purchaser-side management device 231 calculates the consideration ratio for each participant based on the acquired contribution value by means of consideration ratio calculation SC601 (step S2214). Specifically, the purchaser-side management device 231 calculates, by means of consideration ratio calculation SC601, the consideration ratio of Supplier 1 as 20 / (20 + 30 + 50) = 0.2. Specifically, the purchaser-side management device 231 calculates, by means of consideration ratio calculation SC601, the consideration ratio of Supplier 2 as 30 / (20 + 30 + 50) = 0.3. Specifically, the purchaser-side management device 231 calculates, by means of consideration ratio calculation SC601, the consideration ratio of Supplier 3 as 50 / (20 + 30 + 50) = 0.5.

[0217] The purchaser-side management device 231 registers, in the consideration ratio data store 800 of the distributed ledger 510, the correspondence between the token ID and the calculated consideration ratio for each participant by the consideration ratio calculation SC601 (step S2215). The purchaser-side management device 231 receives a completion notice from the distributed ledger 510 by the consideration ratio calculation SC601 (step S2216). The purchaser-side management device 231 transmits the completion notice to the processing unit 512 by the consideration ratio calculation SC601 (step S2217). Thereafter, the purchaser-side management device 231 gives consideration to each participant based on the consideration ratio. Next, the description will proceed to FIG. 23.

[0218] In FIG. 23, the block generation device 201 distributes the generated block to various devices 2300 serving as nodes (step S2301). The various devices 2300 are, for example, the manufacturer-side management device 221, the supplier-side management device 211 corresponding to supplier 1, the supplier-side management device 211 corresponding to supplier 2, and the supplier-side management device 211 corresponding to supplier 3.

[0219] When the various devices 2300 receive a block by the processing unit 512, they verify the received block (step S2302). When the various devices 2300 verify that the block is legitimate by the processing unit 512, they execute the consideration ratio calculation SC601 and input the token ID included in the block into the consideration ratio calculation SC601 (step S2303).

[0220] The various devices 2300 search for the token corresponding to the token ID from the token data store 620 using the token ID as a key by the consideration ratio calculation SC601 (step S2304). The various devices 2300 acquire token 2 by the consideration ratio calculation SC601 (step S2305).

[0221] The various devices 2300 retrieve, by the consideration ratio calculation SC601, evidence data corresponding to the evidence ID from the evidence data store 610 using the evidence ID included in the token 2 as a key (step S2306). The various devices 2300 acquire, by the consideration ratio calculation SC601, evidence data 3, evidence data 4, and evidence data 5 (step S2307).

[0222] The various devices 2300 execute, by the consideration ratio calculation SC601, the contribution value calculation SCA603 based on the evidence data 3 (step S2308). The consideration ratio calculation SC601 passes, for example, the actual value = 40 to the contribution value calculation SCA603. The various devices 2300 acquire, by the consideration ratio calculation SC601, the contribution value = 20 calculated by the contribution value calculation SCA603 (step S2309).

[0223] The various devices 2300 execute, by the consideration ratio calculation SC601, the contribution value calculation SCA603 based on the evidence data 4 (step S2310). The consideration ratio calculation SC601 passes, for example, the actual value = 35 to the contribution value calculation SCA603. The various devices 2300 acquire, by the consideration ratio calculation SC601, the contribution value = 30 calculated by the contribution value calculation SCA603 (step S2311).

[0224] The various devices 2300 execute, by the consideration ratio calculation SC601, the contribution value calculation SCB603 based on the evidence data 5 (step S2312). The consideration ratio calculation SC601 passes, for example, the actual value = 5 to the contribution value calculation SCB603. The various devices 2300 acquire, by the consideration ratio calculation SC601, the contribution value = 50 calculated by the contribution value calculation SCB603 (step S2313).

[0225] The various devices 2300 calculate the consideration ratio for each participant based on the obtained contribution value by the consideration ratio calculation SC601 (step S2314). Specifically, the various devices 2300 calculate the consideration ratio of Supplier 1 as 20 / (20 + 30 + 50) = 0.2 by the consideration ratio calculation SC601. Specifically, the various devices 2300 calculate the consideration ratio of Supplier 2 as 30 / (20 + 30 + 50) = 0.3 by the consideration ratio calculation SC601. Specifically, the various devices 2300 calculate the consideration ratio of Supplier 3 as 50 / (20 + 30 + 50) = 0.5 by the consideration ratio calculation SC601.

[0226] The various devices 2300 register the correspondence between the token ID and the calculated consideration ratio for each participant in the consideration ratio data store 800 of the distributed ledger 510 by the consideration ratio calculation SC601 (step S2315). The various devices 2300 receive a completion notice from the distributed ledger 510 by the consideration ratio calculation SC601 (step S2316). The various devices 2300 send the completion notice to the processing unit 512 by the consideration ratio calculation SC601 (step S2317). Thereafter, the various devices 2300 give consideration to each participant based on the consideration ratio. Next, the description of FIG. 24 will be proceeded with.

[0227] Specifically, FIG. 24 shows the state of the distributed ledger 510. As shown in FIG. 24, by the consideration ratio calculation process, the distributed ledger 510 stores the consideration ratio for each participant regarding Token 2 in the consideration ratio data store 800. Thereby, the consideration ratio can be made referable in the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. The consideration can be appropriately allocated based on the consideration ratio in the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc.

[0228] In this way, the information processing system 200 can calculate a common contribution value from the perspective of the amount of CO2 reduction caused by the amount of electricity and from the perspective of the amount of CO2 reduction caused by the amount of fuel, and can appropriately allocate the consideration to each participant. The information processing system 200 can achieve cost reduction without rewriting the SC. Since the information processing system 200 does not need to rewrite the SC, it can easily suppress the occurrence of program bugs and improve reliability. The information processing system 200 can appropriately allocate the consideration to each participant without affecting the existing contribution value calculation SCA603 and the consideration ratio calculation SC601.

[0229] (Second operation example of the information processing system 200) Next, with reference to FIGS. 25 to 33, a second operation example of the information processing system 200 will be described. The first operation example corresponds to the case where there is one contribution type (Target Type) of the contribution value. The second operation example corresponds to the case where there are two or more contribution types of the contribution value. As the contribution type, for example, in addition to the amount of CO2 reduction, the amount of plastic reduction, etc. can be considered. In the following description, the amount of plastic reduction may be referred to as the "plastic reduction amount".

[0230] FIGS. 25 to 33 are explanatory diagrams showing a second operation example of the information processing system 200. Specifically, FIGS. 25 and 26 show the initial state of the distributed ledger 510. As shown in FIG. 25, the distributed ledger 510 stores the consideration ratio calculation SC601. The consideration ratio calculation SC601 includes a calculation formula. The calculation formula is different from that of the first operation example. The distributed ledger 510 has a contribution standard pool 602. Next, the description will proceed to FIG. 26.

[0231] As shown in FIG. 26, the distributed ledger 510 stores an evidence data store 610, a token data store 620, and a consideration ratio data store 800. The evidence data store 610 further has a field of Target Type. In the field of Target Type, "Target Type" representing the contribution type of the contribution value is set. In the initial state, the evidence data store 610 is empty. The token data store 620 is empty. The consideration ratio data store 800 is empty. Next, the description will move on to FIG. 27.

[0232] In FIG. 27, it is assumed that the information processing system 200 registers a contribution value calculation SCA603 regarding the perspective of the CO2 reduction amount caused by the power consumption in the distributed ledger 510 and shares it among a plurality of nodes, in the same manner as the SC registration process shown in FIG. 9.

[0233] Also, it is assumed that the information processing system 200 registers a contribution value calculation SCB603 regarding the perspective of the CO2 reduction amount caused by the fuel amount in the distributed ledger 510 and shares it among a plurality of nodes, in the same manner as the SC registration process shown in FIG. 9.

[0234] Also, it is assumed that the information processing system 200 registers a contribution value calculation SCC603 regarding the perspective of the PLA reduction amount caused by the usage amount of plant-derived raw materials in the distributed ledger 510 and shares it among a plurality of nodes, in the same manner as the SC registration process shown in FIG. 9.

[0235] Specifically, FIG. 27 shows the state of the distributed ledger 510. As shown in FIG. 27, through the SC registration process, the distributed ledger 510 stores the contribution value calculation SCA603, the contribution value calculation SCB603, and the contribution value calculation SCC603 in the contribution standard pool 602. Thereby, the contribution value calculation SCA603, the contribution value calculation SCB603, and the contribution value calculation SCC603 can be made referable in the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. The contribution values of the same standard can be calculated based on the performance values from different perspectives in the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc.

[0236] The contribution value calculation SCA603 includes a data type which is the performance type of the performance value, a target type which is the contribution type of the contribution value, and a calculation formula that enables the calculation of the contribution value based on the performance value. The calculation formula calculates, for example, the contribution value = CO2 reduction amount. Specifically, the calculation formula is 100 - p * 2. p is the performance value. The performance value is, for example, the power consumption. The smaller the power consumption, the larger the CO2 reduction amount, and thus the larger the contribution value.

[0237] The contribution value calculation SCB603 includes a data type which is the performance type of the performance value, a target type which is the contribution type of the contribution value, and a calculation formula that enables the calculation of the contribution value based on the performance value. The calculation formula calculates, for example, the contribution value = CO2 reduction amount. Specifically, the calculation formula is 100 - p * 14. p is the performance value. The performance value is, for example, the fuel quantity. The smaller the fuel quantity, the larger the CO2 reduction amount, and thus the larger the contribution value.

[0238] The contribution value calculation SCC603 includes a data type which is the performance type of the performance value, a target type which is the contribution type of the contribution value, and a calculation formula that enables the calculation of the contribution value based on the performance value. The calculation formula calculates, for example, the contribution value = plastic reduction amount. Specifically, the calculation formula is p * 2. p is the performance value. The performance value is, for example, the usage amount of plant-derived raw materials. The larger the usage amount, the larger the plastic reduction amount, and thus the larger the contribution value. Next, we will move on to the description of FIG. 28.

[0239] In FIG. 28, assume that the supplier-side terminal device 212 corresponding to Supplier 1 generates trace data 1 based on the operation input of the supplier-side user. The trace data 1 includes a trace ID = A1, a performance type Data Type = A (power consumption), a contribution type Target Type = T1 (CO2 reduction amount), a performance value, and account information. Assume that the information processing system 200 shares the trace data 1 among a plurality of nodes in the same way as the trace data registration process shown in FIG. 11.

[0240] Also, assume that the supplier-side terminal device 212 corresponding to Supplier 2 generates trace data 2 based on the operation input of the supplier-side user. The trace data 2 includes a trace ID = B1, a performance type Data Type = B (fuel quantity), a contribution type Target Type = T1 (CO2 reduction amount), a performance value, and account information. Assume that the information processing system 200 shares the trace data 2 among a plurality of nodes in the same manner as the trace data registration process shown in FIG. 11.

[0241] Also, assume that the supplier-side terminal device 212 corresponding to Supplier 3 generates trace data 3 based on the operation input of the supplier-side user. The trace data 3 includes a trace ID = C1, a performance type Data Type = C (plant-derived raw material quantity), a contribution type Target Type = T2 (plastic reduction amount), a performance value, and account information. Assume that the information processing system 200 shares the trace data 3 among a plurality of nodes in the same manner as the trace data registration process shown in FIG. 11.

[0242] Specifically, FIG. 28 shows the state of the distributed ledger 510. As shown in FIG. 28, through the trace data registration process, the distributed ledger 510 stores the trace data 1, the trace data 2, and the trace data 3 in the trace data store 610. Thereby, the trace data 1, the trace data 2, and the trace data 3 can be made referable by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like. The performance value can be specified based on the trace data by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like. Next, the description will shift to FIG. 29.

[0243] In FIG. 29, when a manufacturer-side user produces a product, the manufacturer-side user inputs into the manufacturer-side terminal device 222 the correspondence between product information representing the product and evidence IDs = A1, B1, C1 representing evidence data related to the product. The manufacturer-side terminal device 222 generates a token 1 including product information representing the product and evidence IDs = A1, B1, C1 representing evidence data related to the product. It is assumed that the information processing system 200 registers the token 1 in the distributed ledger 510 and shares it among a plurality of nodes in the same way as the token registration process shown in FIG. 13.

[0244] Specifically, FIG. 29 shows the state of the distributed ledger 510. As shown in FIG. 29, through the token registration process, the distributed ledger 510 stores the token 1 in the token data store 620. As a result, the token 1 can be made referable by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like. The evidence data to be referred to when distributing the consideration based on the token 1 can be made specifiable by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like. Next, the description will proceed to FIGS. 30 to 32.

[0245] Specifically, FIGS. 30 to 32 show a sequence diagram showing an example of the calculation processing procedure for calculating the consideration ratio for distributing the consideration in the information processing system 200. In FIG. 30, when a purchaser-side user pays consideration for the token 1, the purchaser-side user inputs the token ID into the purchaser-side terminal device 232. The purchaser-side terminal device 232 generates a consideration ratio calculation request including the token ID based on the operation input of the purchaser-side user. In the example of FIG. 30, the purchaser-side terminal device 232 generates a consideration ratio calculation request including the token ID of the token 1.

[0246] The purchaser-side terminal device 232 transmits a transaction issuance request for calculating the total consideration ratio including the generated total consideration ratio calculation request to the purchaser-side management device 231 serving as a node (step S3001). When receiving the transaction issuance request for calculating the total consideration ratio, the purchaser-side management device 231 generates a transaction for calculating the total consideration ratio including the total consideration ratio calculation request and attaches a signature (step S3002). The purchaser-side management device 231 issues the transaction for calculating the total consideration ratio to the block generation device 201 (step S3003).

[0247] When receiving the transaction for calculating the total consideration ratio, the block generation device 201 transmits a completion notice to the purchaser-side management device 231 (step S3004). When receiving the completion notice, the purchaser-side management device 231 transmits the completion notice to the purchaser-side terminal device 232 (step S3005).

[0248] When receiving the transaction for calculating the total consideration ratio, the block generation device 201 generates a block including the total consideration ratio calculation request (step S3006). Next, the description will proceed to FIG. 31.

[0249] In FIG. 31, the block generation device 201 distributes the generated block to the purchaser-side management device 231 (step S3101). When receiving the block by the processing unit 512, the purchaser-side management device 231 verifies the received block (step S3102). When the block is verified to be legitimate by the processing unit 512, the purchaser-side management device 231 executes the total consideration ratio calculation SC601 and inputs the token ID included in the block to the total consideration ratio calculation SC601 (step S3103).

[0250] The purchaser-side management device 231 searches for the token corresponding to the token ID from the token data store 620 using the token ID as a key by the total consideration ratio calculation SC601 (step S3104). The purchaser-side management device 231 acquires Token 1 by the total consideration ratio calculation SC601 (step S3105).

[0251] The purchaser-side management device 231 searches for the evidence data corresponding to the evidence ID from the evidence data store 610 using the evidence ID included in the token 1 as a key through the consideration ratio calculation SC601 (step S3106). The purchaser-side management device 231 acquires evidence data 1, evidence data 2, and evidence data 3 through the consideration ratio calculation SC601 (step S3107).

[0252] The purchaser-side management device 231 executes the contribution value calculation SCA603 corresponding to the combination of Data Type and Target Type based on the evidence data 1 through the consideration ratio calculation SC601 (step S3108). The consideration ratio calculation SC601 passes, for example, the actual value = 40 to the contribution value calculation SCA603. The purchaser-side management device 231 acquires the contribution value = 20 calculated by the contribution value calculation SCA603 through the consideration ratio calculation SC601 (step S3109).

[0253] The purchaser-side management device 231 executes the contribution value calculation SCB603 corresponding to the combination of Data Type and Target Type based on the evidence data 2 through the consideration ratio calculation SC601 (step S3110). The consideration ratio calculation SC601 passes, for example, the actual value = 5 to the contribution value calculation SCB603. The purchaser-side management device 231 acquires the contribution value = 30 calculated by the contribution value calculation SCB603 through the consideration ratio calculation SC601 (step S3111).

[0254] The purchaser-side management device 231 executes the contribution value calculation SCC603 corresponding to the combination of Data Type and Target Type based on the evidence data 3 through the consideration ratio calculation SC601 (step S3112). The consideration ratio calculation SC601 passes, for example, the actual value = 10 to the contribution value calculation SCC603. The purchaser-side management device 231 acquires the contribution value = 20 calculated by the contribution value calculation SCC603 through the consideration ratio calculation SC601 (step S3113).

[0255] The purchaser-side management device 231 calculates the consideration ratio for each participant based on the obtained contribution value by the consideration ratio calculation SC601 (step S3114). Specifically, the purchaser-side management device 231 calculates the consideration ratio x n =y n / y sum *1 / z. Here, z is the number of contribution types, and n is the participant number.

[0256] Specifically, the purchaser-side management device 231 calculates the consideration ratio of Supplier 1 as 20 / (20 + 30)*1 / 2 = 0.2 by the consideration ratio calculation SC601. Specifically, the purchaser-side management device 231 calculates the consideration ratio of Supplier 2 as 30 / (20 + 30)*1 / 2 = 0.3 by the consideration ratio calculation SC601. Specifically, the purchaser-side management device 231 calculates the consideration ratio of Supplier 3 as 20 / 20*1 / 2 = 0.5 by the consideration ratio calculation SC601.

[0257] The purchaser-side management device 231 registers the correspondence between the token ID and the calculated consideration ratio for each participant in the consideration ratio data store 800 of the distributed ledger 510 by the consideration ratio calculation SC601 (step S3115). The purchaser-side management device 231 receives a completion notice from the distributed ledger 510 by the consideration ratio calculation SC601 (step S3116). The purchaser-side management device 231 sends the completion notice to the processing unit 512 by the consideration ratio calculation SC601 (step S3117). After that, the purchaser-side management device 231 gives consideration to each participant based on the consideration ratio. Next, the description moves to FIG. 32.

[0258] In FIG. 32, the block generation device 201 distributes the generated block to various devices 3200 serving as nodes (step S3201). The various devices 3200 are, for example, the manufacturer-side management device 221, the supplier-side management device 211 corresponding to Supplier 1, the supplier-side management device 211 corresponding to Supplier 2, and the supplier-side management device 211 corresponding to Supplier 3.

[0259] Upon receiving a block, various devices 3200 verify the received block by the processing unit 512 (step S3202). When the block is verified as legitimate by the processing unit 512, various devices 3200 execute the consideration ratio calculation SC601 and input the token ID included in the block into the consideration ratio calculation SC601 (step S3203).

[0260] Using the token ID as a key, various devices 3200 search the token data store 620 for the token corresponding to the token ID by the consideration ratio calculation SC601 (step S3204). Various devices 3200 obtain token 1 by the consideration ratio calculation SC601 (step S3205).

[0261] Using the evidence ID included in token 1 as a key, various devices 3200 search the evidence data store 610 for the evidence data corresponding to the evidence ID by the consideration ratio calculation SC601 (step S3206). Various devices 3200 obtain evidence data 1, evidence data 2, and evidence data 3 by the consideration ratio calculation SC601 (step S3207).

[0262] Based on evidence data 1, various devices 3200 execute the contribution value calculation SCA603 corresponding to the combination of Data Type and Target Type by the consideration ratio calculation SC601 (step S3208). The consideration ratio calculation SC601 passes, for example, the actual value = 40 to the contribution value calculation SCA603. Various devices 3200 obtain the contribution value = 20 calculated by the contribution value calculation SCA603 by the consideration ratio calculation SC601 (step S3209).

[0263] The various devices 3200 execute a contribution value calculation SCB603 corresponding to the combination of Data Type and Target Type based on the evidence data 2 by the consideration ratio calculation SC601 (step S3210). The consideration ratio calculation SC601 passes, for example, the actual value = 5 to the contribution value calculation SCB603. The various devices 3200 acquire the contribution value = 30 calculated by the contribution value calculation SCB603 by the consideration ratio calculation SC601 (step S3211).

[0264] The various devices 3200 execute a contribution value calculation SCC603 corresponding to the combination of Data Type and Target Type based on the evidence data 3 by the consideration ratio calculation SC601 (step S3212). The consideration ratio calculation SC601 passes, for example, the actual value = 10 to the contribution value calculation SCC603. The various devices 3200 acquire the contribution value = 20 calculated by the contribution value calculation SCC603 by the consideration ratio calculation SC601 (step S3213).

[0265] The various devices 3200 calculate the consideration ratio for each participant based on the acquired contribution values by the consideration ratio calculation SC601 (step S3214). Specifically, the various devices 3200 calculate the consideration ratio of Supplier 1 as 20 / (20 + 30)*1 / 2 = 0.2 by the consideration ratio calculation SC601. Specifically, the various devices 3200 calculate the consideration ratio of Supplier 2 as 30 / (20 + 30)*1 / 2 = 0.3 by the consideration ratio calculation SC601. Specifically, the various devices 3200 calculate the consideration ratio of Supplier 3 as 20 / 20*1 / 2 = 0.5 by the consideration ratio calculation SC601.

[0266] Each type of device 3200 registers, in the consideration ratio data store 800 of the distributed ledger 510, the correspondence between the token ID and the calculated consideration ratio for each participant by the consideration ratio calculation SC601 (step S3215). Each type of device 3200 receives a completion notice from the distributed ledger 510 by the consideration ratio calculation SC601 (step S3216). Each type of device 3200 transmits the completion notice to the processing unit 512 by the consideration ratio calculation SC601 (step S3217). Thereafter, each type of device 3200 gives consideration to each participant based on the consideration ratio. Next, the description moves on to FIG. 33.

[0267] Specifically, FIG. 33 shows the state of the distributed ledger 510. As shown in FIG. 33, by the consideration ratio calculation process, the distributed ledger 510 stores the consideration ratio for each participant for token 1 in the consideration ratio data store 800. Thereby, the consideration ratio can be made referable in the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. The consideration can be appropriately distributed based on the consideration ratio in the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc.

[0268] In this way, the information processing system 200 can calculate a common contribution value from each of the viewpoints of the CO2 reduction amount due to the amount of power and the CO2 reduction amount due to the amount of fuel. Also, the information processing system 200 can calculate a common contribution value for each of the different contribution types of the CO2 reduction amount and the plastic reduction amount. For this reason, the information processing system 200 can appropriately distribute the consideration based on different combinations of the performance type and the contribution type. The information processing system 200 can achieve cost reduction without rewriting the SC. Since the information processing system 200 does not need to rewrite the SC, it can easily suppress the occurrence of program bugs and improve reliability. The information processing system 200 can appropriately distribute the consideration to each participant without affecting the existing contribution value calculation SCA603 and the consideration ratio calculation SC601.

[0269] (Third operation example of information processing system 200) Next, with reference to FIGS. 34 to 45, a third operation example of the information processing system 200 will be described. The third operation example corresponds to the case where different weights are assigned for each contribution type. The third operation example can, for example, easily handle the case where it is preferable to emphasize the contribution value of any contribution type depending on the time flow and the like changes.

[0270] FIGS. 34 to 45 are explanatory diagrams showing a third operation example of the information processing system 200. Specifically, FIGS. 34 and 35 show the initial state of the distributed ledger 510. As shown in FIG. 34, the distributed ledger 510 stores the consideration ratio calculation SC601. The consideration ratio calculation SC601 includes a calculation formula. The calculation formula is different from that of the first operation example. The calculation formula is, for example, y n / y sum *w n / w sum That is. y n is the contribution value. y sum is the sum of the contribution values belonging to the same contribution type as y n including y n . w n is the weight of the contribution value. w sum is the sum of the weights of the contribution values. n is the number of the participant. The distributed ledger 510 has a contribution standard pool 602. Next, the description will move on to FIG. 35.

[0271] As shown in FIG. 35, the distributed ledger 510 stores the evidence data store 610, the token data store 620, and the consideration ratio data store 800. The distributed ledger 510 further stores the contribution standard weight data store 3500.

[0272] The contribution standard weight data store 3500 has fields for Target Type and Target Weight. The contribution standard weight data store 3500 stores contribution standard weight data as records by setting information in each field for each contribution type. In the field of Target Type, "Target Type" representing the contribution type of the contribution value is set. In the field of Target Weight, "Target Weight" representing the contribution standard weight for the contribution type is set.

[0273] In the initial state, the evidence data store 610 is empty. The token data store 620 is empty. The consideration ratio data store 800 is empty. The contribution standard weight data store 3500 is empty. Next, we move on to the description of FIGS. 36 and 37.

[0274] FIGS. 36 and 37 specifically show a sequence diagram illustrating an example of an SC registration processing procedure for registering the contribution value calculation SC603 and the contribution standard weight in the information processing system 200. In FIG. 36, the manufacturer-side terminal device 222 generates the contribution value calculation SC603 based on the operation input of the manufacturer-side user. In the example of FIG. 36, the manufacturer-side terminal device 222 generates the contribution value calculation SCA603.

[0275] The manufacturer-side terminal device 222 transmits an SC registration transaction issuance request including the generated contribution value calculation SCA603 to the manufacturer-side management device 221 serving as a node (step S3601). When receiving the SC registration transaction issuance request, the manufacturer-side management device 221 generates and signs an SC registration transaction including the contribution value calculation SCA603 (step S3602). The manufacturer-side management device 221 issues the SC registration transaction to the block generation device 201 (step S3603).

[0276] When the block generation device 201 receives an SC registration transaction, it sends a completion notice to the manufacturer-side management device 221 (step S3604). When the manufacturer-side management device 221 receives the completion notice, it sends the completion notice to the manufacturer-side terminal device 222 (step S3605).

[0277] When the block generation device 201 receives an SC registration transaction, it generates a block including the contribution value calculation SCA603 (step S3606). The block generation device 201 distributes the generated block to the manufacturer-side management device 221 (step S3607). The block generation device 201 distributes the generated block to various devices 3600 serving as nodes (step S3608).

[0278] The various devices 3600 are, for example, the supplier-side management device 211 corresponding to supplier 1, the supplier-side management device 211 corresponding to supplier 2, the supplier-side management device 211 corresponding to supplier 3, and the purchaser-side management device 231, etc.

[0279] When the manufacturer-side management device 221 receives a block by the processing unit 512, it verifies the received block (step S3609). When the block is verified as legitimate by the processing unit 512 of the manufacturer-side management device 221, it registers the block in the distributed ledger 510 (step S3610). The manufacturer-side management device 221 receives a completion notice from the distributed ledger 510 by the processing unit 512 (step S3611).

[0280] When the various devices 3600 receive a block by the processing unit 512, they verify the received block (step S3612). When the block is verified as legitimate by the processing unit 512 of the various devices 3600, they register the block in the distributed ledger 510 (step S3613). The various devices 3600 receive a completion notice from the distributed ledger 510 by the processing unit 512 (step S3614). Thereby, the information processing system 200 can share the contribution value calculation SC603 among a plurality of nodes. Next, the description of FIG. 37 will be moved on.

[0281] In FIG. 37, the manufacturer-side terminal device 222 generates a contribution reference weight for the contribution type represented by the Target Type of the contribution reference weight based on the operation input of the manufacturer-side user. In the example of FIG. 37, the manufacturer-side terminal device 222 generates a contribution reference weight T1 = 3.

[0282] The manufacturer-side terminal device 222 transmits a contribution reference weight registration transaction issuance request including the generated contribution reference weight T1 to the manufacturer-side management device 221 serving as a node (step S3701). When receiving the contribution reference weight registration transaction issuance request, the manufacturer-side management device 221 generates a contribution reference weight registration transaction including the contribution reference weight T1 and attaches a signature (step S3702). The manufacturer-side management device 221 issues the contribution reference weight registration transaction to the block generation device 201 (step S3703).

[0283] When receiving the contribution reference weight registration transaction, the block generation device 201 transmits a completion notification to the manufacturer-side management device 221 (step S3704). When receiving the completion notification, the manufacturer-side management device 221 transmits the completion notification to the manufacturer-side terminal device 222 (step S3705).

[0284] When receiving the contribution reference weight registration transaction, the block generation device 201 generates a block including the contribution reference weight T1 (step S3706). The block generation device 201 distributes the generated block to the manufacturer-side management device 221 (step S3707). The block generation device 201 distributes the generated block to various devices 3700 serving as nodes (step S3708).

[0285] The various devices 3700 are, for example, the supplier-side management device 211 corresponding to supplier 1, the supplier-side management device 211 corresponding to supplier 2, the supplier-side management device 211 corresponding to supplier 3, and the purchaser-side management device 231, etc.

[0286] When the manufacturer-side management device 221 receives a block by the processing unit 512, it verifies the received block (step S3709). When the block is verified as legitimate by the processing unit 512 of the manufacturer-side management device 221, it registers the block in the distributed ledger 510 (step S3710). The manufacturer-side management device 221 receives a completion notice from the distributed ledger 510 by the processing unit 512 (step S3711).

[0287] When each type of device 3700 receives a block by the processing unit 512, it verifies the received block (step S3712). When the block is verified as legitimate by the processing unit 512 of each type of device 3700, it registers the block in the distributed ledger 510 (step S3713). Each type of device 3700 receives a completion notice from the distributed ledger 510 by the processing unit 512 (step S3714). As a result, the information processing system 200 can share the contribution reference weight T1 among a plurality of nodes.

[0288] Also, assume that the information processing system 200 registers the contribution value calculation SCB603 and the contribution reference weight T1 in the distributed ledger 510 and shares them among a plurality of nodes, similar to the SC registration process shown in FIGS. 36 and 37. At this time, since the contribution reference weight T1 has already been registered, the information processing system 200 may omit the processes of steps S3701 to S3714 shown in FIG. 37. Also, assume that the information processing system 200 registers the contribution value calculation SCC603 and the contribution reference weight T2 in the distributed ledger 510 and shares them among a plurality of nodes, similar to the SC registration process shown in FIGS. 36 and 37. Next, the description will proceed to FIGS. 38 and 39.

[0289] Figures 38 and 39 specifically show the state of the distributed ledger 510. As shown in Figure 38, through the SC registration process, the distributed ledger 510 will store the contribution value calculation SCA603, the contribution value calculation SCB603, and the contribution value calculation SCC603 in the contribution standard pool 602. As a result, the contribution value calculation SCA603, the contribution value calculation SCB603, and the contribution value calculation SCC603 can be made referable by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like.

[0290] The contribution value calculation SCA603 includes the data type which is the performance type of the performance value, the target type which is the contribution type of the contribution value, and a calculation formula that enables the calculation of the contribution value based on the performance value. The calculation formula is, for example, to calculate the contribution value = CO2 reduction amount. Specifically, the calculation formula is 100 - p * 2. p is the performance value. The performance value is, for example, the power consumption. The smaller the power consumption, the larger the CO2 reduction amount, and thus the larger the contribution value.

[0291] The contribution value calculation SCB603 includes the data type which is the performance type of the performance value, the target type which is the contribution type of the contribution value, and a calculation formula that enables the calculation of the contribution value based on the performance value. The calculation formula is, for example, to calculate the contribution value = CO2 reduction amount. Specifically, the calculation formula is 100 - p * 14. p is the performance value. The performance value is, for example, the fuel quantity. The smaller the fuel quantity, the larger the CO2 reduction amount, and thus the larger the contribution value.

[0292] The contribution value calculation SCC603 includes the data type which is the performance type of the performance value, the target type which is the contribution type of the contribution value, and a calculation formula that enables the calculation of the contribution value based on the performance value. The calculation formula is, for example, to calculate the contribution value = plastic reduction amount. Specifically, the calculation formula is p * 2. p is the performance value. The performance value is, for example, the usage amount of plant-derived raw materials. The larger the usage amount, the larger the plastic reduction amount, and thus the larger the contribution value. Next, we will move on to the description of Figure 39.

[0293] FIG. 39 specifically shows the state of the distributed ledger 510. As shown in FIG. 39, through the SC registration process, the distributed ledger 510 will store the contribution standard weight data T1 and the contribution standard weight data T2 in the contribution standard weight data store 3500. The larger the contribution standard weight, the more likely the contribution value is to be large.

[0294] Thereby, the contribution standard weight data T1 and the contribution standard weight data T2 can be made referable by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. The contribution value can be calculated based on the actual performance value by using the contribution standard weight by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. Next, the description of FIG. 40 will be shifted to.

[0295] In FIG. 40, it is assumed that the supplier-side terminal device 212 corresponding to Supplier 1 generates the trace data 1 based on the operation input of the supplier-side user. The trace data 1 includes the trace ID = A1, the performance type Data Type = A (electric energy amount), the contribution type Target Type = T1 (CO2 reduction amount), the actual performance value, and the account information. It is assumed that the information processing system 200 shares the trace data 1 among a plurality of nodes in the same way as the trace data registration process shown in FIG. 11.

[0296] Also, it is assumed that the supplier-side terminal device 212 corresponding to Supplier 2 generates the trace data 2 based on the operation input of the supplier-side user. The trace data 2 includes the trace ID = B1, the performance type Data Type = B (fuel amount), the contribution type Target Type = T1 (CO2 reduction amount), the actual performance value, and the account information. It is assumed that the information processing system 200 shares the trace data 2 among a plurality of nodes in the same way as the trace data registration process shown in FIG. 11.

[0297] Also, assume that the supplier-side terminal device 212 corresponding to Supplier 3 generates the evidence data 3 based on the operation input of the supplier-side user. The evidence data 3 includes an evidence ID = C1, a performance type Data Type = C (plant-derived raw material quantity), a contribution type Target Type = T2 (plastic reduction amount), a performance value, and account information. The information processing system 200 is assumed to share the evidence data 3 among a plurality of nodes in the same way as the evidence data registration process shown in FIG. 11.

[0298] Specifically, FIG. 40 shows the state of the distributed ledger 510. As shown in FIG. 40, through the evidence data registration process, the distributed ledger 510 stores the evidence data 1, the evidence data 2, and the evidence data 3 in the evidence data store 610. As a result, the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can refer to the evidence data 1, the evidence data 2, and the evidence data 3. The supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can identify the performance value based on the evidence data. Next, we will move on to the description of FIG. 41.

[0299] In FIG. 41, the manufacturer-side user inputs, to the manufacturer-side terminal device 222, the correspondence between the product information representing the product and the evidence IDs = A1, B1, C1 representing the evidence data related to the product, in response to the production of the product. The manufacturer-side terminal device 222 generates a token 1 including the product information representing the product and the evidence IDs = A1, B1, C1 representing the evidence data related to the product. The information processing system 200 is assumed to register the token 1 in the distributed ledger 510 and share it among a plurality of nodes in the same way as the token registration process shown in FIG. 13.

[0300] FIG. 41 specifically shows the state of the distributed ledger 510. As shown in FIG. 41, through the token registration process, the distributed ledger 510 will store token 1 in the token data store 620. As a result, the token 1 can be referred to by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like. The supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like can identify the evidence data to be referred to when allocating consideration based on token 1. Next, the description will move on to FIGS. 42 to 44.

[0301] FIGS. 42 to 44 specifically show a sequence diagram illustrating an example of a calculation processing procedure for calculating the consideration ratio for allocating consideration in the information processing system 200. In FIG. 42, when the purchaser-side user pays consideration for token 1, the purchaser inputs the token ID into the purchaser-side terminal device 232. Based on the operation input of the purchaser-side user, the purchaser-side terminal device 232 generates a consideration ratio calculation request including the token ID. In the example of FIG. 42, the purchaser-side terminal device 232 generates a consideration ratio calculation request including the token ID of token 1.

[0302] The purchaser-side terminal device 232 transmits a consideration ratio calculation transaction issuance request including the generated consideration ratio calculation request to the purchaser-side management device 231 serving as a node (step S4201). When receiving the consideration ratio calculation transaction issuance request, the purchaser-side management device 231 generates a consideration ratio calculation transaction including the consideration ratio calculation request and attaches a signature (step S4202). The purchaser-side management device 231 issues the consideration ratio calculation transaction to the block generation device 201 (step S4203).

[0303] When receiving the consideration ratio calculation transaction, the block generation device 201 transmits a completion notice to the purchaser-side management device 231 (step S4204). When receiving the completion notice, the purchaser-side management device 231 transmits the completion notice to the purchaser-side terminal device 232 (step S4205).

[0304] When the block generation device 201 receives the consideration ratio calculation transaction, it generates a block including a consideration ratio calculation request (step S4206). Next, the description proceeds to FIG. 43.

[0305] In FIG. 43, the block generation device 201 distributes the generated block to the purchaser-side management device 231 (step S4301). When the purchaser-side management device 231 receives the block by the processing unit 512, it verifies the received block (step S4302). When the purchaser-side management device 231 verifies that the block is legitimate by the processing unit 512, it executes the consideration ratio calculation SC601 and inputs the token ID included in the block to the consideration ratio calculation SC601 (step S4303).

[0306] The purchaser-side management device 231 searches the token data store 620 for the token corresponding to the token ID using the token ID as a key by the consideration ratio calculation SC601 (step S4304). The purchaser-side management device 231 acquires token 1 by the consideration ratio calculation SC601 (step S4305).

[0307] The purchaser-side management device 231 searches the evidence data store 610 for the evidence data corresponding to the evidence ID using the evidence ID included in token 1 as a key by the consideration ratio calculation SC601 (step S4306). The purchaser-side management device 231 acquires evidence data 1, evidence data 2, and evidence data 3 by the consideration ratio calculation SC601 (step S4307).

[0308] The purchaser-side management device 231 executes the contribution value calculation SCA603 corresponding to the combination of the Data Type and the Target Type based on the evidence data 1 by the consideration ratio calculation SC601 (step S4308). The consideration ratio calculation SC601 passes, for example, the actual value = 40 to the contribution value calculation SCA603. The purchaser-side management device 231 acquires the contribution value = 20 calculated by the contribution value calculation SCA603 by the consideration ratio calculation SC601 (step S4309).

[0309] The purchaser-side management device 231 executes a contribution value calculation SCB603 corresponding to the combination of Data Type and Target Type based on the evidence data 2 by the consideration ratio calculation SC601 (step S4310). The consideration ratio calculation SC601 passes, for example, the actual value = 5 to the contribution value calculation SCB603. The purchaser-side management device 231 acquires the contribution value = 30 calculated by the contribution value calculation SCB603 by the consideration ratio calculation SC601 (step S4311).

[0310] The purchaser-side management device 231 executes a contribution value calculation SCC603 corresponding to the combination of Data Type and Target Type based on the evidence data 3 by the consideration ratio calculation SC601 (step S4312). The consideration ratio calculation SC601 passes, for example, the actual value = 10 to the contribution value calculation SCC603. The purchaser-side management device 231 acquires the contribution value = 20 calculated by the contribution value calculation SCC603 by the consideration ratio calculation SC601 (step S4313).

[0311] The purchaser-side management device 231 searches for the contribution standard weight corresponding to Target Type from the contribution standard weight data store 3500 based on the evidence data 1, the evidence data 2, and the evidence data 3 by the consideration ratio calculation SC601 (step S4314). The purchaser-side management device 231 acquires the contribution standard weight T1 and the contribution standard weight T2 by the consideration ratio calculation SC601 (step S4315).

[0312] The purchaser-side management device 231 calculates the consideration ratio for each participant based on the acquired contribution value by the consideration ratio calculation SC601 (step S4316). Specifically, the purchaser-side management device 231 calculates the consideration ratio x n =y n / y sum *w n / w sum . n is the number of the participant.

[0313] Specifically, the purchaser-side management device 231 calculates the consideration ratio of Supplier 1 as 20 / (20 + 30) * 3 / (3 + 1) = 0.3 by the consideration ratio calculation SC601. Specifically, the purchaser-side management device 231 calculates the consideration ratio of Supplier 2 as 30 / (20 + 30) * 3 / (3 + 1) = 0.45 by the consideration ratio calculation SC601. Specifically, the purchaser-side management device 231 calculates the consideration ratio of Supplier 3 as 20 / 20 * 1 / (3 + 1) = 0.25 by the consideration ratio calculation SC601.

[0314] The purchaser-side management device 231 registers, in the consideration ratio data store 800 of the distributed ledger 510, the correspondence between the token ID and the calculated consideration ratio for each participant by the consideration ratio calculation SC601 (step S4317). The purchaser-side management device 231 receives a completion notification from the distributed ledger 510 by the consideration ratio calculation SC601 (step S4318). The purchaser-side management device 231 transmits the completion notification to the processing unit 512 by the consideration ratio calculation SC601 (step S4319). Thereafter, the purchaser-side management device 231 gives consideration to each participant based on the consideration ratio. Next, the description of FIG. 44 will be continued.

[0315] In FIG. 44, the block generation device 201 distributes the generated blocks to various devices 4400 serving as nodes (step S4401). The various devices 4400 are, for example, the manufacturer-side management device 221, the supplier-side management device 211 corresponding to Supplier 1, the supplier-side management device 211 corresponding to Supplier 2, and the supplier-side management device 211 corresponding to Supplier 3.

[0316] When the various devices 4400 receive a block by the processing unit 512, they verify the received block (step S4402). When the block is verified to be valid by the processing unit 512, the various devices 4400 execute the consideration ratio calculation SC601 and input the token ID included in the block into the consideration ratio calculation SC601 (step S4403).

[0317] The various devices 4400 search for the token corresponding to the token ID from the token data store 620 using the token ID as a key by the consideration ratio calculation SC601 (step S4404). The various devices 4400 acquire token 1 by the consideration ratio calculation SC601 (step S4405).

[0318] The various devices 4400 search for the evidence data corresponding to the evidence ID from the evidence data store 610 using the evidence ID included in token 1 as a key by the consideration ratio calculation SC601 (step S4406). The various devices 4400 acquire evidence data 1, evidence data 2, and evidence data 3 by the consideration ratio calculation SC601 (step S4407).

[0319] The various devices 4400 execute the contribution value calculation SCA603 corresponding to the combination of Data Type and Target Type based on the evidence data 1 by the consideration ratio calculation SC601 (step S4408). The consideration ratio calculation SC601 passes, for example, the actual value = 40 to the contribution value calculation SCA603. The various devices 4400 acquire the contribution value = 20 calculated by the contribution value calculation SCA603 by the consideration ratio calculation SC601 (step S4409).

[0320] The various devices 4400 execute the contribution value calculation SCB603 corresponding to the combination of Data Type and Target Type based on the evidence data 2 by the consideration ratio calculation SC601 (step S4410). The consideration ratio calculation SC601 passes, for example, the actual value = 5 to the contribution value calculation SCB603. The various devices 4400 acquire the contribution value = 30 calculated by the contribution value calculation SCB603 by the consideration ratio calculation SC601 (step S4411).

[0321] Various devices 4400 execute a contribution value calculation SCC603 corresponding to the combination of Data Type and Target Type based on the evidence data 3 by the consideration ratio calculation SC601 (step S4412). The consideration ratio calculation SC601 passes, for example, the actual value = 10 to the contribution value calculation SCC603. Various devices 4400 acquire the contribution value = 50 calculated by the contribution value calculation SCC603 by the consideration ratio calculation SC601 (step S4413).

[0322] The purchaser-side management device 231 searches for the contribution standard weight corresponding to Target Type from the contribution standard weight data store 3500 based on the evidence data 1, the evidence data 2, and the evidence data 3 by the consideration ratio calculation SC601 (step S4414). The purchaser-side management device 231 acquires the contribution standard weight T1 and the contribution standard weight T2 by the consideration ratio calculation SC601 (step S4415).

[0323] Various devices 4400 calculate the consideration ratio for each participant based on the acquired contribution value by the consideration ratio calculation SC601 (step S4416). Specifically, various devices 4400 calculate the consideration ratio of supplier 1 as 20 / (20 + 30) * 3 / (3 + 1) = 0.3 by the consideration ratio calculation SC601. Specifically, various devices 4400 calculate the consideration ratio of supplier 2 as 30 / (20 + 30) * 3 / (3 + 1) = 0.45 by the consideration ratio calculation SC601. Specifically, various devices 4400 calculate the consideration ratio of supplier 3 as 20 / 20 * 1 / (3 + 1) = 0.25 by the consideration ratio calculation SC601.

[0324] The various devices 4400 register, in the consideration ratio data store 800 of the distributed ledger 510, the correspondence between the token ID and the calculated consideration ratio for each participant by the consideration ratio calculation SC601 (step S4417). The various devices 4400 receive a completion notice from the distributed ledger 510 by the consideration ratio calculation SC601 (step S4418). The various devices 4400 transmit the completion notice to the processing unit 512 by the consideration ratio calculation SC601 (step S4419). Thereafter, the various devices 4400 give consideration to each participant based on the consideration ratio. Next, the description moves to FIG. 45.

[0325] Specifically, FIG. 45 shows the state of the distributed ledger 510. As shown in FIG. 45, by the consideration ratio calculation process, the distributed ledger 510 stores the consideration ratio for each participant for token 1 in the consideration ratio data store 800. Thereby, the consideration ratio can be made referable in the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like. In the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, and the like, the consideration can be appropriately distributed based on the consideration ratio.

[0326] In this way, the information processing system 200 can calculate a common contribution value from the perspective of the CO2 reduction amount caused by the power consumption and from the perspective of the CO2 reduction amount caused by the fuel consumption. Also, the information processing system 200 can calculate a common contribution value for each of the different contribution types of the CO2 reduction amount and the plastic reduction amount. Also, the information processing system 200 can appropriately use the contribution standard weights for each contribution type.

[0327] Therefore, the information processing system 200 can appropriately allocate consideration based on different combinations of performance types and contribution types, taking into account the contribution standard weights. The information processing system 200 can avoid rewriting the SC and reduce costs. Since the information processing system 200 does not need to rewrite the SC, it can easily suppress the occurrence of program bugs and improve reliability. The information processing system 200 can appropriately allocate consideration to each participant without affecting the existing contribution value calculation SCA603 and the consideration ratio calculation SC601.

[0328] (Fourth operation example of the information processing system 200) Next, with reference to FIGS. 46 to 49, a fourth operation example of the information processing system 200 will be described. The fourth operation example corresponds to another pattern when different weights are assigned for each contribution type. Specifically, the fourth operation example corresponds to the case where the contribution standard weight is included in the token.

[0329] FIGS. 46 to 49 are explanatory diagrams showing a fourth operation example of the information processing system 200. Specifically, FIG. 46 shows an initial state of the distributed ledger 510. As shown in FIG. 46, the distributed ledger 510 stores the evidence data store 610, the token data store 620, and the consideration ratio data store 800. The distributed ledger 510 further stores the contribution standard weight data store 3500.

[0330] The token data store 620 further has a field of Target Weight. In the Target Weight field, "Target Weight" representing the contribution standard weight for the contribution type is set.

[0331] In the initial state, the evidence data store 610 is empty. The token data store 620 is empty. The consideration ratio data store 800 is empty. Here, similar to FIG. 34, it is assumed that the distributed ledger 510 stores the consideration ratio calculation SC601. It is assumed that the distributed ledger 510 has a contribution standard pool 602.

[0332] It is assumed that the information processing system 200 registers the contribution value calculation SCA603 regarding the perspective of the CO2 reduction amount caused by the power consumption in the distributed ledger 510 and shares it among a plurality of nodes, in the same manner as the SC registration process shown in FIG. 9.

[0333] It is also assumed that the information processing system 200 registers the contribution value calculation SCB603 regarding the perspective of the CO2 reduction amount caused by the fuel amount in the distributed ledger 510 and shares it among a plurality of nodes, in the same manner as the SC registration process shown in FIG. 9.

[0334] It is further assumed that the information processing system 200 registers the contribution value calculation SCC603 regarding the perspective of the plastic reduction amount caused by the usage amount of plant-derived raw materials in the distributed ledger 510 and shares it among a plurality of nodes, in the same manner as the SC registration process shown in FIG. 9. Next, the description will move on to FIG. 47.

[0335] In FIG. 47, it is assumed that the supplier-side terminal device 212 corresponding to Supplier 1 generates the trace data 1 based on the operation input of the supplier-side user. The trace data 1 includes the trace ID = A1, the performance type Data Type = A (power consumption), the contribution type Target Type = T1 (CO2 reduction amount), the performance value, and the account information. It is assumed that the information processing system 200 shares the trace data 1 among a plurality of nodes, in the same manner as the trace data registration process shown in FIG. 11.

[0336] It is also assumed that the supplier-side terminal device 212 corresponding to Supplier 2 generates the trace data 2 based on the operation input of the supplier-side user. The trace data 2 includes the trace ID = B1, the performance type Data Type = B (fuel amount), the contribution type Target Type = T1 (CO2 reduction amount), the performance value, and the account information. It is assumed that the information processing system 200 shares the trace data 2 among a plurality of nodes, in the same manner as the trace data registration process shown in FIG. 11.

[0337] Also, assume that the supplier-side terminal device 212 corresponding to Supplier 3 generates trace data 3 based on the operation input of the supplier-side user. The trace data 3 includes a trace ID = C1, a performance type Data Type = C (plant-derived raw material quantity), a contribution type Target Type = T2 (plastic reduction amount), a performance value, and account information. Assume that the information processing system 200 shares the trace data 3 among multiple nodes in the same way as the trace data registration process shown in FIG. 11.

[0338] Specifically, FIG. 47 shows the state of the distributed ledger 510. As shown in FIG. 47, through the trace data registration process, the distributed ledger 510 stores the trace data 1, the trace data 2, and the trace data 3 in the trace data store 610. Thereby, the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can refer to the trace data 1, the trace data 2, and the trace data 3. The supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can specify the performance value based on the trace data. Next, we will move on to the description of FIG. 48.

[0339] In FIG. 48, in response to the production of the product, the manufacturer-side user inputs the product information representing the product, the trace IDs = A1, B1, C1 representing the trace data related to the product, and the correspondence with the contribution standard weights T1, T2 to the manufacturer-side terminal device 222. The manufacturer-side terminal device 222 generates a token 1 including the product information representing the product, the trace IDs = A1, B1, C1 representing the trace data related to the product, and the contribution standard weights T1, T2. Assume that the information processing system 200 registers the token 1 in the distributed ledger 510 and shares it among multiple nodes in the same way as the token registration process shown in FIG. 13.

[0340] FIG. 48 specifically shows the state of the distributed ledger 510. As shown in FIG. 48, through the token registration process, the distributed ledger 510 will store token 1 in the token data store 620. As a result, the token 1 can be made referable by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. The token 1 can be made identifiable with the trace data and the contribution standard weight to be referred to when distributing the consideration based on the token 1 by the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. Next, the description will move on to FIG. 49.

[0341] The information processing system 200 calculates the consideration ratio for each participant in the same way as the calculation process shown in FIGS. 42 to 44. In this case, in step S4314, the purchaser-side management device 231 will search for the contribution standard weight corresponding to the Target Type from the token data store 620 through the consideration ratio calculation SC601. Similarly, in step S4414, the purchaser-side management device 231 will search for the contribution standard weight corresponding to the Target Type from the token data store 620 through the consideration ratio calculation SC601.

[0342] For example, various devices serving as nodes specifically calculate the consideration ratio of Supplier 1 as 20 / (20 + 30) * 3 / (3 + 1) = 0.3. Various devices specifically calculate the consideration ratio of Supplier 2 as 30 / (20 + 30) * 3 / (3 + 1) = 0.45. Various devices specifically calculate the consideration ratio of Supplier 3 as 20 / 20 * 1 / (3 + 1) = 0.25. Various devices register the correspondence between the token ID and the calculated consideration ratio for each participant in the consideration ratio data store 800 of the distributed ledger 510.

[0343] FIG. 49 specifically shows the state of the distributed ledger 510. As shown in FIG. 49, through the consideration ratio calculation process, the distributed ledger 510 will store the consideration ratio for each participant regarding Token 1 in the consideration ratio data store 800. Thereby, the consideration ratio can be made referable in the supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. The supplier-side management device 211, the manufacturer-side management device 221, the purchaser-side management device 231, etc. can appropriately allocate the consideration based on the consideration ratio.

[0344] In this way, the information processing system 200 can calculate a common contribution value from each of the viewpoints of the CO2 reduction amount due to the power consumption and the CO2 reduction amount due to the fuel amount. Also, the information processing system 200 can calculate a common contribution value for each of the different contribution types of the CO2 reduction amount and the plastic reduction amount. Further, the information processing system 200 can appropriately use the contribution standard weights corresponding to the respective contribution types for each token. For this reason, the information processing system 200 can set the contribution standard weights with a fine granularity, can easily handle various products, and can improve convenience.

[0345] For this reason, the information processing system 200 can appropriately allocate the consideration in consideration of the contribution standard weights based on different combinations of the performance type and the contribution type. The information processing system 200 can avoid rewriting the SC and can reduce costs. Since the information processing system 200 does not need to rewrite the SC, it can easily suppress the occurrence of program bugs and can improve reliability. The information processing system 200 can appropriately allocate the consideration to each participant without affecting the existing contribution value calculation SCA603 and the consideration ratio calculation SC601.

[0346] As described above, according to the information processing apparatus 100, for each process, the first SC that converts the performance value in the process regarding the objective into an index value indicating the degree of contribution to the objective according to the performance type of the performance value can be stored based on a unified standard. According to the information processing apparatus 100, the second SC that calculates the ratio for distributing the profit obtained from the source of generation to a plurality of participants who share a plurality of processes can be stored based on the index value. According to the information processing apparatus 100, the first evidence data indicating the correspondence relationship between any one process, the performance value in the process regarding the objective, and the performance type of the performance value can be registered in the distributed ledger 510. According to the information processing apparatus 100, referring to the distributed ledger 510, the first SC corresponding to each process can be specified based on a token indicating the correspondence relationship between the source of generation and the evidence data registered in the distributed ledger 510 for each process. According to the information processing apparatus 100, using the first SC specified for each process, the index value regarding the process can be calculated according to the performance type of the performance value in the process regarding the objective. According to the information processing apparatus 100, using the second SC, the ratio for distributing the profit obtained from the source of generation to a plurality of participants can be calculated according to the calculated index values regarding each process. Thereby, the information processing apparatus 100 can easily and appropriately distribute the profit obtained from the source of generation to a plurality of participants.

[0347] According to the information processing apparatus 100, the first transaction including the first SC can be issued. Thereby, the information processing apparatus 100 can control the information processing apparatus 100 to register the first block including the first SC in the distributed ledger 510 managed by each of the plurality of information processing apparatuses 100. For this reason, the information processing apparatus 100 can distribute the first SC to the plurality of information processing apparatuses 100 so that the index value can be calculated.

[0348] According to the information processing apparatus 100, for each process, a first SC can be stored that converts the performance value in the process related to the objective into an index value indicating the degree of contribution to the objective, which is a contribution type corresponding to the performance type of the performance value. According to the information processing apparatus 100, a second SC can be stored that calculates the ratio for distributing the profit obtained from the source of generation to a plurality of participants based on the index values of different contribution types. According to the information processing apparatus 100, by referring to the distributed ledger 510 and using the first SC corresponding to each process based on the token, the index value related to the process, which is the contribution type corresponding to the performance type of the performance value in the process related to the objective, can be calculated. Thereby, even if there are index values of different contribution types, the information processing apparatus 100 can easily and appropriately distribute the profit obtained from the source of generation to a plurality of participants.

[0349] According to the information processing apparatus 100, by using the second SC, the ratio for distributing the profit obtained from the source of generation to a plurality of participants can be calculated based on the weight for each contribution type. Thereby, the information processing apparatus 100 can easily and appropriately distribute the profit obtained from the source of generation to a plurality of participants in consideration of the weight for each contribution type.

[0350] According to the information processing apparatus 100, when the own apparatus corresponds to the last process of a plurality of processes, a second transaction including a token can be issued in response to the completion of the plurality of processes. According to the information processing apparatus 100, the information processing apparatus 100 can be controlled to register a second block including a token in the distributed ledger 510 managed by each of the plurality of information processing apparatuses 100. For this reason, the information processing apparatus 100 can distribute the token to the plurality of information processing apparatuses 100 so that the ratio for distributing the profit obtained from the source of generation to a plurality of participants can be calculated.

[0351] According to the information processing apparatus 100, it is possible to receive a third block that specifies a token and register it in the distributed ledger 510 managed by the own apparatus. According to the information processing apparatus 100, in response to registering the third block, it is possible to calculate an index value related to the process according to the performance type of the performance value in the process related to the purpose. Thereby, the information processing apparatus 100 can calculate the index value at an appropriate timing.

[0352] Note that the information processing method described in the present embodiment can be realized by executing a program prepared in advance on a computer such as a PC or a workstation. The information processing program described in the present embodiment is recorded on a computer-readable recording medium and executed by being read from the recording medium by a computer. The recording medium is a hard disk, a flexible disk, a CD (Compact Disc)-ROM, an MO (Magneto Optical disc), a DVD (Digital Versatile Disc), or the like. Further, the information processing program described in the present embodiment may be distributed via a network such as the Internet.

[0353] Regarding the above-described embodiment, the following supplementary notes are further disclosed.

[0354] (Supplementary Note 1) Among a plurality of information processing apparatuses that manage a distributed ledger, any information processing apparatus corresponding to any one of a plurality of processes related to a profit generation source, For each of the plurality of processes, store a first smart contract that converts a performance value in the process related to the purpose into an index value indicating the degree of contribution to the purpose according to the performance type of the performance value, based on a unified standard in the plurality of processes, Store a second smart contract that calculates a ratio for distributing the profit obtained from the generation source to a plurality of participants who share the plurality of processes based on the index value, Register the first evidence data indicating the correspondence relationship between any of the above steps, the actual value in the step related to the purpose, and the type of actual value in the distributed ledger. Based on the token indicating the correspondence relationship between the source of generation and the evidence data registered in the distributed ledger for each of the above steps, use the first smart contract corresponding to each of the above steps to calculate the index value related to the step according to the type of actual value of the actual value in the step related to the purpose. Using the second smart contract, calculate the ratio for distributing the profit obtained from the source of generation to the plurality of participants according to the calculated index value related to each of the above steps. An information processing apparatus characterized by having a control unit.

[0355] (Appendix 2) The control unit Control the information processing apparatus to register a first block including the first smart contract in the distributed ledger managed by each of the information processing apparatuses of the plurality of information processing apparatuses by issuing a first transaction including the first smart contract. The information processing apparatus according to Appendix 1, characterized in that.

[0356] (Appendix 3) The control unit For each of the above steps, store a first smart contract that converts the actual value in the step related to the purpose into an index value indicating the degree of contribution to the purpose, which is a type of contribution corresponding to the type of actual value of the actual value. Store a second smart contract that calculates the ratio for distributing the profit obtained from the source of generation to the plurality of participants based on the index values of different types of contributions. Based on a token indicating the correspondence between the source of generation and the evidence data registered in the dispersion ledger for each of the processes, using the first smart contract corresponding to each of the processes, calculate the index value for the process regarding the contribution type corresponding to the performance type of the performance value in the process regarding the objective. The information processing apparatus according to appended note 1 or 2, characterized in that.

[0357] (Appended note 4) The control unit Using the second smart contract, according to the index value for the process regarding the contribution type corresponding to the performance type of the performance value in each of the processes regarding the objective, calculate the ratio for distributing the profit obtained from the source of generation to the plurality of participants based on the weight for each contribution type. The information processing apparatus according to appended note 3, characterized in that.

[0358] (Appended note 5) The control unit When the own apparatus corresponds to the last process of the plurality of processes, in response to the completion of the plurality of processes, issue a second transaction including the token, and register a second block including the token in the dispersion ledger managed by each of the information processing apparatuses of the plurality of information processing apparatuses. Control the information processing apparatus as such. The information processing apparatus according to any one of appended notes 1 to 4, characterized in that.

[0359] (Appended note 6) The control unit Receive a third block specifying the token, and in response to registering it in the dispersion ledger managed by the own apparatus, refer to the dispersion ledger, and using the first smart contract corresponding to each of the processes based on the token, calculate the index value for the process regarding the contribution type corresponding to the performance type of the performance value in the process regarding the objective. The information processing apparatus according to any one of appended notes 1 to 5, characterized in that.

[0360] (Appended note 7) Among the plurality of information processing apparatuses managing the dispersion ledger, any information processing apparatus corresponding to any one of the plurality of processes regarding the source of profit For each of the plurality of processes, store a first smart contract that converts the performance value in the process related to the objective into an index value indicating the degree of contribution to the objective according to the performance type of the performance value, based on a standard unified among the plurality of processes. Store a second smart contract that calculates the ratio for distributing the profit obtained from the source of generation to a plurality of participants who share the plurality of processes, based on the index value. Register first evidentiary data indicating the correspondence relationship between any one of the processes, the performance value in the process related to the objective, and the performance type of the performance value in the distributed ledger. With reference to the distributed ledger, use the first smart contract corresponding to each process based on a token indicating the correspondence relationship between the source of generation and the evidentiary data registered in the distributed ledger for each process, and calculate the index value related to the process according to the performance type of the performance value in the process related to the objective. Use the second smart contract to calculate the ratio for distributing the profit obtained from the source of generation to the plurality of participants according to the calculated index values related to each process. An information processing method characterized by executing processing.

[0361] (Appendix 8) In any one of the plurality of information processing apparatuses that manage a distributed ledger and correspond to any one of the plurality of processes related to the source of profit, For each of the plurality of processes, store a first smart contract that converts the performance value in the process related to the objective into an index value indicating the degree of contribution to the objective according to the performance type of the performance value, based on a standard unified among the plurality of processes. Store a second smart contract that calculates the ratio for distributing the profit obtained from the source of generation to a plurality of participants who share the plurality of processes, based on the index value. Register first evidentiary data indicating the correspondence relationship between any one of the processes, the performance value in the process related to the objective, and the performance type of the performance value in the distributed ledger. Based on a token indicating the correspondence between the source of generation and the evidence data registered in the dispersion ledger for each of the processes, using the first smart contract corresponding to each of the processes, calculate the index value for the process according to the performance type of the performance value in the process related to the objective. Using the second smart contract, calculate the ratio for distributing the profit obtained from the source of generation to the plurality of participants according to the calculated index value for each of the processes. An information processing program characterized by causing the execution of processing.

Explanation of Signs

[0362] 100 Information processing device 101 Product 102 - 104 Factory 200 Information processing system 201 Block generation device 210 Supplier - side environment 211 Supplier - side management device 212 Supplier - side terminal device 220 Manufacturer - side environment 221 Manufacturer - side management device 222 Manufacturer - side terminal device 230 Purchaser - side environment 231 Purchaser - side management device 232 Purchaser - side terminal device 240 Network 300 Computer 301 CPU 302 Memory 303 Network I / F 304 Recording medium I / F 305 Recording medium 310 Bus 400 Storage unit 401 Acquisition unit 402 Issuance unit 403 Registration unit 404 Calculation unit 405 Output unit 501, 511, 521 Receiver Unit 502, 513, 523 Transmitter Unit 503 Display Unit 510 Dispersion Ledger 512 Processing Unit 522 Generation Unit 601 Consideration Ratio Calculation SC 602 Contribution Criterion Pool 603 Contribution Value Calculation SC 610 Audit Trail Data Store 620 Token Data Store 630 SC Store 800 Consideration Ratio Data Store 3500 Contribution Criterion Weight Data Store

Claims

1. Among a plurality of information processing devices that manage a decentralized ledger, any one of the information processing devices corresponding to any one of a plurality of processes related to a profit source, For each of the plurality of processes, store a first smart contract that converts the actual value in the process related to the purpose into an index value indicating the degree of contribution to the purpose based on a standard unified in the plurality of processes according to the type of actual value of the actual value, Store a second smart contract that calculates a ratio for distributing the profit obtained from the source of profit to a plurality of participants who share the plurality of processes based on the index value, Register first evidence data indicating the correspondence relationship between any one of the processes, the actual value in the process related to the purpose, and the type of actual value of the actual value in the decentralized ledger, With reference to the decentralized ledger, based on a token indicating the correspondence relationship between the source of profit and the evidence data registered in the decentralized ledger for each of the processes, use the first smart contract corresponding to each of the processes to calculate the index value related to the process according to the type of actual value of the actual value in the process related to the purpose, Use the second smart contract to calculate a ratio for distributing the profit obtained from the source of profit to the plurality of participants according to the calculated index value related to each of the processes, An information processing device characterized by having a control unit.

2. The control unit is configured to Control the information processing device to register a first block including the first smart contract in the decentralized ledger managed by each of the plurality of information processing devices by issuing a first transaction including the first smart contract. The information processing device according to claim 1, characterized in that.

3. The control unit is configured to For each of the processes, store a first smart contract that converts the actual value in the process related to the purpose into an index value indicating the degree of contribution to the purpose, which is a contribution type corresponding to the type of actual value of the actual value, Store a second smart contract that calculates a ratio for distributing the profit obtained from the source of profit to the plurality of participants based on the index values of different contribution types, Based on a token indicating the correspondence between the source of the benefit and the evidentiary data registered in the dispersion ledger for each of the processes, using the first smart contract corresponding to each of the processes, calculate the index value for the process regarding the contribution type corresponding to the performance type of the performance value in the process regarding the objective. The information processing apparatus according to claim 1 or 2, characterized in that.

4. The control unit Using the second smart contract, according to the index value for the process regarding the contribution type corresponding to the performance type of the performance value in each of the processes regarding the objective, based on the weight for each contribution type, calculate the ratio for distributing the profit obtained from the source of the benefit to the plurality of participants. The information processing apparatus according to claim 3, characterized in that.

5. The control unit When the own apparatus corresponds to the last process of the plurality of processes, in response to the completion of the plurality of processes, issue a second transaction including the token, so that the second block including the token is registered in the dispersion ledger managed by each of the information processing apparatuses of the plurality of information processing apparatuses. Control the information processing apparatus, characterized in that. The information processing apparatus according to any one of claims 1 to 4.

6. Among the plurality of information processing apparatuses that manage the dispersion ledger, any information processing apparatus corresponding to any one of the plurality of processes regarding the source of the benefit For each of the plurality of processes, store a first smart contract that converts the performance value in the process regarding the objective into an index value indicating the degree of contribution to the objective according to the unified standard in the plurality of processes according to the performance type of the performance value. Store a second smart contract that calculates the ratio for distributing the profit obtained from the source of the benefit to the plurality of participants who share the plurality of processes based on the index value. Register the first evidentiary data indicating the correspondence between any one of the processes, the performance value in the process regarding the objective, and the performance type of the performance value in the dispersion ledger. Based on the token indicating the correspondence between the source of profit and the evidentiary data registered in the dispersion ledger for each of the processes, using the first smart contract corresponding to each of the processes, calculate the index value for the process related to the objective according to the performance type of the performance value in the process related to the objective. Using the second smart contract, calculate the ratio for distributing the profit obtained from the source of profit to the plurality of participants according to the calculated index value for each of the processes. An information processing method characterized by executing the process.

7. Among the plurality of information processing apparatuses that manage the dispersion ledger, in any one of the information processing apparatuses corresponding to any one of the plurality of processes related to the source of profit. For each of the plurality of processes, store a first smart contract that converts the performance value in the process related to the objective into an index value indicating the degree of contribution to the objective based on a unified standard in the plurality of processes according to the performance type of the performance value. Store a second smart contract that calculates the ratio for distributing the profit obtained from the source of profit to the plurality of participants who share the plurality of processes based on the index value. Register first evidentiary data indicating the correspondence between any one of the processes, the performance value in the process related to the objective, and the performance type of the performance value in the dispersion ledger. Based on the token indicating the correspondence between the source of profit and the evidentiary data registered in the dispersion ledger for each of the processes, using the first smart contract corresponding to each of the processes, calculate the index value for the process related to the objective according to the performance type of the performance value in the process related to the objective. Using the second smart contract, calculate the ratio for distributing the profit obtained from the source of profit to the plurality of participants according to the calculated index value for each of the processes. An information processing program characterized by causing the process to be executed.

Images