Blockchain network system, traceability management system, and method

Abstract

The present invention contributes to objective, neutral, equitable, fair, and easy confirmation of a state present in data when tracing collected information. Provided is a blockchain network system in which nodes are connected in a network and which is configured to allow the nodes to hold identical information about an object in a distributed manner, the nodes comprising: a plurality of responsible nodes each responsible for providing a predetermined role; and a role-providing node configured to store a role database in which a corresponding role is defined for each responsible node, provide each responsible node with a role on the basis of the role database, and connect the responsible node to at least one corresponding terminal outside the blockchain network system.

Description

Blockchain network system, traceability management system, and method

[0001] [Description of Related Applications] The present invention is based on the priority claim of Japanese Patent Application No. 2022-163488 (filed October 11, 2022), the entire contents of which are incorporated herein by reference. The present invention relates to a blockchain network system, a traceability management system, and a method.

[0002] There are traceability management systems that collect and manage various information related to the production, processing, or distribution of an object, enabling it to be traced. For example, there are centralized traceability management systems that use a server (see, for example, Patent Documents 1 to 7). There are also distributed traceability management systems that use a blockchain network system to make it difficult to falsify or erase information, a problem that has been present in centralized traceability management systems (see, for example, Patent Documents 8 and 9). There are also distributed traceability management systems that execute predetermined smart contracts in a blockchain network system to monitor for data deficiencies and errors in various information collected from nodes (see, for example, Patent Documents 10 to 11).

[0003] JP 2004-171398 A, JP 2004-213477 A, JP 2004-315154 A, JP 2005-160391 A, JP 2005-196507 A, JP 2005-251079 A, ​​JP 2005-267153 A, JP 2019-079253 A, JP 2020-144804 A, JP 2020-515092 A, JP 2022-517436 A

[0004] The following analysis is provided by the present inventors.

[0005] However, in the traceability management systems disclosed in Patent Documents 10-11, even if there are no data deficiencies or errors in the collected information, it is difficult to objectively, neutrally, impartially, and fairly verify the inherent state of the data (evaluation, fraud, falsification, etc.). In other words, the inherent state of the data is prone to variation depending on the level of knowledge of the person verifying it, making it difficult to verify it objectively, neutrally, impartially, and fairly. Therefore, a system is desired that can objectively, neutrally, impartially, and easily verify the inherent state of the data when tracing collected information.

[0006] The main objective of the present invention is to provide a blockchain network system, a traceability management system, and a method that can contribute to objectively, neutrally, impartially, fairly, and easily verifying the status inherent in data when tracking collected information.

[0007] A blockchain network system according to a first aspect is a blockchain network system in which nodes are connected to each other on a network and are configured to distribute and store identical information regarding an object in the nodes, and the nodes include a plurality of assigned nodes each assigned to a specific role; a role assignment node configured to store a role database that defines the role corresponding to each assigned node and assign a role to each assigned node based on the role database and connect the assigned nodes to at least one corresponding terminal outside the blockchain network system; and a status change monitoring node that stores a status change rule database that defines a status change rule between the time an object arrives and the time it is shipped, and is configured to input the information from the terminal via the assigned node and monitor status changes of the object by determining whether a status change based on corresponding arrival information and shipping information from the input information satisfies the status change rule.

[0008] A blockchain network system according to a second aspect is a blockchain network system in which nodes are connected to each other on a network and are configured to have the same information regarding an object stored in a distributed manner in the nodes, wherein the nodes include a plurality of assigned nodes each assigned to a predetermined role, a role assignment node configured to store a role database that defines the role corresponding to each of the assigned nodes and assign a role to each of the assigned nodes based on the role database and connect them to at least one corresponding terminal outside the blockchain network system, and a distribution route monitoring node that stores a distribution route rule database that defines distribution route rules regarding combinations of shippers and recipients, and is configured to input the information from the terminals via the assigned node and monitor the distribution route of the object by determining whether the combination of shipper and recipient included in one or both of the shipping information and receiving information among the input information satisfies the distribution route rule.

[0009] A blockchain network system according to a third aspect is a blockchain network system in which nodes are connected to each other on a network and are configured to distribute and store identical information regarding objects in the nodes, wherein the nodes include a plurality of assigned nodes each assigned to a specific role, and a role-assigning node configured to store a role database that defines the role corresponding to each assigned node, assign a role to each assigned node based on the role database, and connect the assigned nodes to at least one corresponding terminal outside the blockchain network system, wherein at least one of the assigned nodes is assigned a role related to an auditing agency by the role-assigning node, and stores an evaluation criteria database that associates conditions and evaluations for specific evaluation objects, and wherein the information from the terminal is input via a assigned node other than the assigned node that has been assigned the role related to the auditing agency, and the evaluation object in the input information is evaluated based on the evaluation criteria database.

[0010] A blockchain network system according to a fourth aspect is a blockchain network system configured so that nodes are connected to each other on a network and so that the nodes store the same information about an object in a distributed manner, and the nodes include a plurality of assigned nodes each assigned to a specific role, and a role-assigning node configured to store a role database that defines the role corresponding to each assigned node, assign a role to each assigned node based on the role database, and connect the assigned nodes to at least one corresponding terminal outside the blockchain network system.

[0011] A traceability management system according to a fifth aspect includes a blockchain network system according to the first aspect, a role management terminal configured to be connected to the role-assigning node, and a plurality of terminals configured to be connected to the corresponding responsible nodes to which roles have been assigned by the role management terminal.

[0012] A traceability management method according to a sixth aspect is a traceability management method in which traceability management is performed by a blockchain network system in which nodes are connected to each other on a network and are configured to have the nodes store the same information related to an object in a distributed manner, the nodes comprising: a plurality of assigned nodes each assigned to a predetermined role; a role assignment node configured to store a role database that defines the role corresponding to each of the assigned nodes; and a status change monitoring node configured to store a status change rule database that defines a status change rule between the time of arrival and the time of shipment of an object, the traceability management method including the steps of: the role assignment node assigning a role to each of the assigned nodes based on the role database and connecting each of the assigned nodes to at least one corresponding terminal outside the blockchain network system; inputting the information from the terminal to the status change monitoring node via the assigned node to which a role has been assigned by the role assignment node; and the status change monitoring node monitoring a status change of the object by determining whether a status change based on corresponding arrival information and shipping information from the input information satisfies the status change rule.

[0013] A traceability management method according to a seventh aspect is a traceability management method in which traceability management is performed by a blockchain network system in which nodes are connected to each other on a network and are configured to have the nodes store identical information about an object in a distributed manner, the nodes comprising a plurality of assigned nodes each assigned to a predetermined role, a role assignment node configured to store a role database that defines the role corresponding to each of the assigned nodes, and a distribution route monitoring node configured to store a distribution route rule database that defines distribution route rules related to combinations of shippers and recipients, the traceability management method including the steps of: the role assignment node assigning a role to each of the assigned nodes based on the role database and connecting each of the assigned nodes to at least one corresponding terminal outside the blockchain network system; inputting the information from the terminals to the distribution route monitoring node via the assigned node to which a role has been assigned by the role assignment node; and the distribution route monitoring node monitoring the distribution route of the object by determining whether a combination of shipper and recipient included in one or both of shipping information and receiving information from the input information satisfies the distribution route rule.

[0014] A traceability management method according to an eighth aspect is a traceability management method in which traceability management is performed by a blockchain network system in which nodes are connected to each other on a network and are configured to distribute and store identical information related to objects in the nodes, wherein the nodes include a plurality of assigned nodes each assigned to a predetermined role, and a role-assigning node configured to store a role database that defines the role corresponding to each of the assigned nodes, and the method includes a step in which the role-assigning node assigns a role to each of the assigned nodes based on the role database and connects the assigned nodes to at least one corresponding terminal outside the blockchain network system, a step in which the assigned node assigned a role related to an audit agency by the role-assigning node stores an evaluation criteria database that associates conditions and evaluations for a predetermined evaluation object, a step in which the assigned node inputs the information from the terminal to the assigned node assigned the role related to the audit agency via a assigned node other than the assigned node assigned the role related to the audit agency, and a step in which the assigned node assigned the role related to the audit agency evaluates the evaluation object in the input information based on the evaluation criteria database.

[0015] A traceability management method according to a ninth aspect is a traceability management method in which traceability management is performed by a blockchain network system configured so that nodes are connected to each other on a network and the nodes are configured to distribute and store the same information regarding objects, wherein the nodes include a plurality of assigned nodes each responsible for a specific role, and a role-assigning node configured to store a role database that defines the role corresponding to each assigned node, and in the traceability management method, the role-assigning node assigns a role to each of the assigned nodes based on the role database and connects them to at least one corresponding terminal outside the blockchain network system.

[0016] In a further aspect, separate programs are provided for implementing the blockchain network system or traceability management method corresponding to each of the above aspects using a computer. These programs can also be integrated at least partially or entirely to be realized as a single integrated program system. Each program can be implemented on a computer at each terminal or node. Instructions and data required for implementing the program can be recorded on a predetermined storage medium. Details of each program can be implemented using known computer technology, and although a detailed description is omitted herein, it is recognized that those skilled in the art can implement the program based on the description herein, and it is deemed to be described in a manner that enables them to be implemented by those skilled in the art. The program can be recorded on a computer-readable storage medium. The storage medium can be a non-transient medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. The present disclosure can also be embodied as a computer program product. The program is input to a computer device via an input device or an external communication interface, stored in a storage device, and drives a processor according to predetermined steps or processes. The processing results, including intermediate states, can be displayed step by step on a display device, or the program can communicate with the outside world via a communication interface. A computer device for this purpose typically includes a processor, a storage device, an input device, a communication interface, and, if necessary, a display device, all of which can be connected to one another via a bus, for example.

[0017] The first to ninth aspects can contribute to objective, neutral, fair, impartial, and easy confirmation of the state inherent in data when tracking collected information.

[0018] 1 is a block diagram schematically showing a configuration of an example of a traceability management system according to embodiment 1 before roles are assigned. FIG. 2 is a block diagram schematically showing a configuration of an example of a traceability management system according to embodiment 1 after roles are assigned. FIG. 3 is a block diagram schematically showing a configuration equivalent to the configuration of FIG. 2 after roles are assigned in an example of the traceability management system according to embodiment 1. FIG. 4 is a block diagram schematically showing a configuration of a role-assigned node in an example of the traceability management system according to embodiment 1. FIG. 5 is a block diagram schematically showing a configuration of a responsible node to which the role of livestock industry, slaughterhouse industry, meatpacking industry, processing industry, wholesale industry, retail industry, or food and beverage industry has been assigned in the configuration of an example of the traceability management system according to embodiment 1 after roles have been assigned. FIG. 6 is a block diagram schematically showing a configuration of a responsible node to which the role of an auditing organization has been assigned in the configuration of an example of the traceability management system according to embodiment 1 after roles have been assigned. FIG. 7 is a block diagram schematically showing a configuration of a responsible node to which the role of a consumer has been assigned in the configuration of an example of the traceability management system according to embodiment 1 after roles have been assigned. FIG. 8 is a block diagram schematically showing a configuration of a distribution route monitoring node in an example of the traceability management system according to embodiment 1. FIG. 1 is a block diagram schematically showing the configuration of a status change monitoring node in an example of a traceability management system according to embodiment 1. FIG. 2 is a block diagram schematically showing the configuration of a terminal in an example of a traceability management system according to embodiment 1. FIG. 3 is a schematic diagram showing an example of a role database in an example of a traceability management system according to embodiment 1. FIG. 4 is a schematic diagram showing an example of an example of the configuration of information transmitted from a predetermined terminal in an example of a traceability management system according to embodiment 1. FIG. 5 is a schematic diagram showing an example of an evaluation criteria database in an example of a traceability management system according to embodiment 1. FIG. 6 is a schematic diagram showing an example of evaluation information in an example of a traceability management system according to embodiment 1. FIG. 7 is a schematic diagram showing an example of a distribution route rule database in an example of a traceability management system according to embodiment 1. FIG. 8 is a schematic diagram showing an example of a status change rule database in an example of a traceability management system according to embodiment 1.1 is a sequence chart schematically showing an example of an operation when a role is assigned in an example of the traceability management system according to embodiment 1. FIG. 2 is a sequence chart schematically showing an example of an operation when information related to the livestock industry is recorded in an example of the traceability management system according to embodiment 1. FIG. 3 is a sequence chart schematically showing an example of an operation when an evaluation is performed in an example of the traceability management system according to embodiment 1. FIG. 4 is a sequence chart schematically showing an example of an operation when a direct transaction occurs between a livestock producer and a food and beverage supplier in an example of the traceability management system according to embodiment 1. FIG. 5 is a sequence chart schematically showing an example of an operation when arrival and shipment at a processor are inconsistent in an example of the traceability management system according to embodiment 1. FIG. 6 is a block diagram schematically showing a configuration after role assignment in a modified example of the traceability management system according to embodiment 1. FIG. 7 is a block diagram schematically showing a configuration after role assignment in a traceability management system according to embodiment 2. FIG. 8 is a block diagram schematically showing a configuration after role assignment in a traceability management system according to embodiment 3. FIG. 9 is a block diagram schematically showing a configuration after role assignment in a traceability management system according to embodiment 4. FIG. 10 is a block diagram schematically showing a configuration after role assignment in a traceability management system according to embodiment 5. FIG. 2 is a block diagram illustrating a configuration of hardware resources.

[0019] Hereinafter, embodiments will be described with reference to the drawings. Note that, when reference numerals are used in this application, they are intended solely to facilitate understanding and are not intended to limit the present invention to the illustrated embodiments. Furthermore, the following embodiments are merely illustrative and do not limit the present invention. Furthermore, connecting lines between blocks in the drawings, etc., referred to in the following description, include both bidirectional and unidirectional lines. Unidirectional arrows are used to schematically indicate the flow of main signals (data) and do not exclude bidirectionality. Furthermore, although not explicitly shown, input and output ports exist at the input and output ends of each connecting line in the circuit diagrams, block diagrams, internal configuration diagrams, connection diagrams, etc., shown in this disclosure. The same applies to input / output interfaces. A program is executed via a computer device, which includes, for example, a processor, a storage device, an input device, a communication interface, and, if necessary, a display device. The computer device is configured to communicate with internal or external devices (including computers) via the communication interface, whether wired or wireless.

[0020] [Embodiment 1] A traceability management system according to embodiment 1 will be described with reference to the drawings. Fig. 1 is a block diagram schematically showing the configuration of an example of a traceability management system according to embodiment 1 before roles are assigned. Fig. 2 is a block diagram schematically showing the configuration of an example of a traceability management system according to embodiment 1 after roles are assigned. Fig. 3 is a block diagram schematically showing a configuration equivalent to the configuration of an example of a traceability management system according to embodiment 1 after roles are assigned.

[0021] The traceability management system 1 is a system that collects and manages various information related to the production, processing, or distribution of an object, enabling it to be traced (see FIG. 1). Here, the object may change during the production, processing, or distribution process. For example, the object may change as parts are assembled, as in equipment, or may change as parts are broken down into smaller pieces, as in butchering and processing livestock meat. In the first embodiment, livestock meat is used as an example of the object. Using a blockchain network system 2, the traceability management system 1 is configured to store (distributedly store) the same information collected about the object in each of multiple responsible nodes 10a-10i, a role assignment node 20, a distribution route monitoring node 30, and a status change monitoring node 40. The traceability management system 1 is configured to automatically monitor for data deficiencies and errors in the various information collected from designated responsible nodes 10a, 10c-10h using smart contracts. The traceability management system 1 is configured to automatically monitor (confirm) the status (evaluation, fraud, falsification, etc.) inherent in the data of various information collected from designated responsible nodes 10a, 10c to 10h using smart contracts.

[0022] Here, the traceability management system 1 can be used for traceability management of the production history (breeding process, cultivation process, harvesting process, etc.), processing history, and distribution history of livestock products (e.g., beef, pork, chicken, etc.) related to livestock meat, agricultural products (e.g., cotton, coffee, cacao, etc.), seafood, farmed products, raw materials, mining products, gemstones, industrial products, etc. The traceability management system 1 can also be used to check whether compliance (industry standards, laws, regulations, ethics, de facto standards, etc.) is observed, whether it is fair trade, whether there is any substitution, etc. The traceability management system 1 can also be used to evaluate data based on evaluation criteria such as GGAP (Global Good Agricultural Practice), JGAP (Japanese Good Agricultural Practice), and agriculture / livestock HACCAP (Hazard Analysis Critical Control Point). The traceability management system 1 can also be used to evaluate elements that consumers are likely to like (for example, pesticide-free cultivation, organic cultivation, place of origin, compliance with animal welfare, etc.), as well as to confirm elements that consumers are likely to dislike (poaching, theft, smuggling, conflict minerals, child labor, forced labor, violations of animal welfare, etc.).

[0023] The traceability management system 1 has a function of assigning role labels to the responsible nodes 10a to 10i and setting the corresponding terminals 50a to 50i using the role assigning node 20 (see FIGS. 1 and 2). The traceability management system 1 not only sets the responsible nodes 10a to 10i from a state in which no role labels have been assigned (see FIG. 1) to a state in which role labels have been assigned to the responsible nodes 10a to 10i (see FIG. 2), but also changes the role labels assigned to the responsible nodes 10a to 10i. The configuration of the traceability management system 1 in FIG. 2 is equivalent to a configuration in which the responsible nodes 10a to 10i, the role assigning node 20, the distribution route monitoring node 30, and the status change monitoring node 40, each assigned a role label, are connected to the corresponding role terminals 50a to 50i, the role management terminal 60, the distribution route management terminal 70, and the status change management terminal 80, as shown in FIG. 3. In the traceability management system 1, when a role label has been assigned, communication is possible between the corresponding responsible nodes 10a to 10i and the terminals 50a to 50i via the network 90. ​​In the traceability management system 1, communication is possible between the corresponding role assigning node 20, distribution route monitoring node 30, status change monitoring node 40 and the role management terminal 60, distribution route management terminal 70, and status change management terminal 80 via the network 90. ​​The role assigning node 20, distribution route monitoring node 30, and status change monitoring node 40 are nodes in which the roles of role assignment, distribution route monitoring, and status change monitoring have been set in advance.

[0024] The blockchain network system 2 is a network system using blockchain, in which nodes 10a to 10i, 20, 30, and 40 are connected to one another on a P2P network 3, and is configured to have the same information about an object stored in a distributed manner (redundantly stored) on all or any of the nodes 10a to 10i, 20, 30, and 40 (see FIGS. 1 to 3). The blockchain network system 2 includes responsible nodes 10a to 10i, a role assignment node 20, a distribution route monitoring node 30, a status change monitoring node 40, and a P2P (Peer to Peer) network 3.

[0025] The nodes 10a to 10i, 20, 30, and 40 are nodes (computers; they can also be servers) that perform predetermined operations and store information (see FIGS. 1 to 3). Each of the nodes 10a to 10i, 20, 30, and 40 (any one of them is acceptable) stores collected information. The nodes 10a to 10i, 20, 30, and 40 may be physical machines or virtual machines. Each of the nodes 10a to 10i, 20, 30, and 40 has unique identification information. Details of the nodes 10a to 10i, 20, 30, and 40 will be described later.

[0026] The P2P network 3 is a network in which nodes 10a to 10i, 20, 30, and 40 are connected on an equal footing (see FIGS. 1 to 3). The P2P network 3 may be a public network, a private network, or a virtual network, or may be an appropriate combination of these.

[0027] Next, nodes and terminals in the traceability management system according to the first embodiment will be described with reference to the drawings. FIG. 4 is a block diagram schematically illustrating the configuration of a role-assigned node in an example of the traceability management system according to the first embodiment. FIG. 5 is a block diagram schematically illustrating the configuration of a responsible node to which the role of livestock industry, slaughterhouse industry, meatpacking industry, processing industry, wholesale industry, retail industry, or food and beverage industry has been assigned in the configuration of the example of the traceability management system according to the first embodiment after role assignment. FIG. 6 is a block diagram schematically illustrating the configuration of a responsible node to which the role of an auditing organization has been assigned in the configuration of the example of the traceability management system according to the first embodiment after role assignment. FIG. 7 is a block diagram schematically illustrating the configuration of a responsible node to which the role of a consumer has been assigned in the configuration of the example of the traceability management system according to the first embodiment after role assignment. FIG. 8 is a block diagram schematically illustrating the configuration of a distribution route monitoring node in an example of the traceability management system according to the first embodiment. FIG. 9 is a block diagram schematically illustrating the configuration of a status change monitoring node in an example of the traceability management system according to the first embodiment. FIG. 10 is a block diagram schematically illustrating the configuration of a terminal in an example of the traceability management system according to the first embodiment. Fig. 11 is a schematic diagram showing an example of a role database in an example of a traceability management system according to embodiment 1. Fig. 12 is a schematic diagram showing an example of an example of the configuration of information transmitted from a predetermined terminal in an example of a traceability management system according to embodiment 1. Fig. 13 is a schematic diagram showing an example of an evaluation criteria database in an example of a traceability management system according to embodiment 1. Fig. 14 is a schematic diagram showing an example of evaluation information in an example of a traceability management system according to embodiment 1. Fig. 15 is a schematic diagram showing an example of a distribution route rule database in an example of a traceability management system according to embodiment 1. Fig. 16 is a schematic diagram showing an example of a status change rule database in an example of a traceability management system according to embodiment 1.

[0028] Referring to FIG. 4, the role-assigning node 20 is a node that assigns roles (role labels 14 in FIGS. 5 to 7) to assigned nodes (10a to 10i in FIGS. 1 to 3) in the blockchain network system (2 in FIGS. 1 to 3). By assigning roles, the role-assigning node 20 connects each assigned node 10a to 10i to at least one terminal 50a to 50i. Note that in FIG. 3, the role-assigning node 20 exclusively connects one terminal to one assigned node, but a single terminal may also be connected to multiple assigned nodes. For example, a single company, such as a major food manufacturer, may be involved in livestock farming, slaughtering, meatpacking, and processing. If a single terminal is used as a livestock farming terminal, a slaughtering terminal, a meatpacking terminal, and a processing terminal due to its hardware configuration, a single terminal may be connected to multiple assigned nodes. The role labels indicate the roles of the assigned nodes 10a to 10i. The role label may be a character string, number, code, or the like that represents the role. The role label allows a node (10b in FIG. 6; role is audit agency) to evaluate the object according to the role (a role other than audit agency), a distribution route monitoring node (30 in FIG. 8) to monitor the distribution route of the object, and a status change monitoring node (40 in FIG. 9) to monitor status changes of the object according to the role. The role assignment node 20 includes a communication unit 21, a storage unit 22, and a control unit 23.

[0029] The communication unit 21 is a functional unit (see FIG. 4) that communicates with the responsible nodes 10a to 10i, the distribution route monitoring node (30 in FIGS. 1 to 3 and 8), and the status change monitoring node (40 in FIGS. 1 to 3 and 9) via the P2P network 3. The communication unit 21 can communicate with the role management terminal (60 in FIGS. 2 and 3) via the network (90 in FIG. 2).

[0030] The storage unit 22 is a functional unit that stores various information and programs (see FIG. 4). The storage unit 22 stores a role database (role DB) 24 and a record information database (record information DB) 25. The role database 24 is a database that associates the identification information (ID) of the assigned nodes 10a to 10i with roles (role labels) (see FIG. 11). The role database 24 may be stored not only in the role-assigning node 20 but also in other nodes 10a to 10i, 30, and 40 or in another blockchain network system (not shown) to further enhance security and fairness. It may also be stored as a blockchain separate from the record information databases 15, 25, 35, and 45 (traceability information) on the blockchain network system 2. The record information database 25 is a database that associates and records various information from the assigned nodes 10a to 10h, the distribution route monitoring node 30, and the status change monitoring node 40. The recording information database 25 has the same contents as the other recording information databases (15 in FIGS. 5 to 7, 35 in FIG. 8, and 45 in FIG. 9).

[0031] The control unit 23 is a functional unit that controls the communication unit 21 and the storage unit 22 (see FIG. 4). The control unit 23 performs predetermined processing and executes programs to realize a role assignment unit 23a and a recording processing unit 23b. The role assignment unit 23a is a processing unit that assigns a role label to each of the assigned nodes 10a to 10i based on the role database 24, and is a processing unit that executes contracts. Depending on the type of role label assigned, the role assignment unit 23a sets one of the following in the control unit (13 in FIGS. 5 to 7) of each of the assigned nodes 10a to 10i: an authentication processing unit (13a in FIG. 5), a recording processing unit (13b in FIGS. 5 to 7), a browsing processing unit (13c in FIGS. 5 and 7), or an evaluation processing unit (13d in FIG. 6). When the role assigning unit 23a assigns role labels of livestock, slaughter, meatpacking, processing, wholesale, retail, and food service to the nodes 10a, 10c, 10h, it sets the certification processing unit 13a, recording processing unit 13b, and browsing processing unit 13c in the control unit 13 of the nodes 10a, 10c, 10h (see FIG. 5). When the role assigning unit 23a assigns the role label of audit organization to the node 10b, it sets the recording processing unit 13b and evaluation processing unit 13d in the control unit 13 of the node 10b (see FIG. 6). When the role assigning unit 23a assigns the role label of consumer to the node 10i, it sets the recording processing unit 13b and browsing processing unit 13c in the control unit 13 of the node 10i (see FIG. 7). The recording processing unit 23b is a processing unit that associates various information from the nodes 10a, 10h, distribution route monitoring node 30, and status change monitoring node 40 and records them in the record information database 25.

[0032] Referring to Figure 5, the responsible nodes 10a, 10c to 10h are nodes in charge of a predetermined role (here, livestock industry / slaughtering industry / meat packing industry / processing industry / wholesale industry / retail industry / food service industry). The responsible nodes 10a, 10c to 10h are assigned roles (role labels 14) by a role-assigning node (20 in Figures 1 to 3) and are connected to the corresponding terminals 50a, 50c to 50h. The responsible nodes 10a, 10c to 10h operate and store information according to the assigned role. The responsible nodes 10a, 10c to 10h include a communication unit 11, a memory unit 12, and a control unit 13.

[0033] The communication unit 11 is a functional unit (see FIG. 5) that communicates with nodes other than its own node (any of 10a to 10i), role-assigning nodes (20 in FIGS. 1 to 4), distribution route monitoring nodes (30 in FIGS. 1 to 3 and 8), and status change monitoring nodes (40 in FIGS. 1 to 3 and 9) via the P2P network 3. The communication unit 11 can communicate with a terminal (any of 50a, 50c to 50h in FIGS. 2 and 3) corresponding to a role label assigned to its own node (any of 10a, 10c to 10h) via the network (90 in FIG. 2).

[0034] The memory unit 12 is a functional unit that stores various information and programs (see FIG. 5). The memory unit 12 stores role labels 14 and a record information database (record information DB) 15. The role labels 14 are assigned by the role assignment node 20 based on the role database (24 in FIG. 4), and in this case, are role labels related to the livestock industry, slaughterhouse industry, meatpacking industry, processing industry, wholesale industry, retail industry, and food service industry. The record information database 15 is a database that associates and records various information from the responsible nodes 10a to 10h, the distribution route monitoring node 30, and the status change monitoring node 40. The record information database 15 shares content with the other record information databases (25 in FIG. 4, 15 in FIG. 6, 15 in FIG. 7, 35 in FIG. 8, and 45 in FIG. 9).

[0035] The control unit 13 is a functional unit that controls the communication unit 11 and the storage unit 12 (see FIG. 5). The control unit 13 performs predetermined processing. The control unit 13 includes a certification processing unit 13a, a recording processing unit 13b, and a browsing processing unit 13c, which are configured according to the role label 14 (here, livestock industry / slaughtering industry / meat packing industry / processing industry / wholesale industry / retail industry / food service industry) assigned by the role-assigning node 20. The certification processing unit 13a checks for data deficiencies or errors in information acquired from a terminal (any of 50a, 50c-50h in FIGS. 2 and 3) corresponding to the role label assigned to its own node (any of 10a, 10c-10h), and certifies the information if there are no deficiencies or errors, and executes the contract. The certification processing unit 13a records the certified information in association with corresponding information in the record information database 15 of its own node (any of 10a, 10c-10h). The certification processing unit 13a transmits the certified information to a node other than its own node (any of 10a to 10i), the role assigning node 20, the distribution route monitoring node 30, and the status change monitoring node 40. The certification processing unit 13a may limit the destination of the certified information. When the acquired information contains insufficient or incorrect data, the certification processing unit 13a transmits warning information to a terminal (any of 50a, 50c to 50h in FIGS. 2 and 3) corresponding to the role label assigned to its own node (any of 10a, 10c to 10h) to notify the terminal of the insufficient or incorrect data and to call its attention. The recording processing unit 13b is a processing unit that associates various pieces of information from a node other than its own node (any of 10a to 10h), the distribution route monitoring node 30, and the status change monitoring node 40, and records them in the recording information database 15. The browsing processing unit 13c is a processing unit that reads out the corresponding information in response to a browsing request from a terminal (any of 50a, 50c to 50h in FIGS. 2 and 3) corresponding to the role label assigned to its own node (any of 10a, 10c to 10h) and transmits the corresponding information to the corresponding terminal. Note that the browsing processing unit 13c may control (limit, prohibit, etc.) the information that can be read in response to a browsing request.

[0036] Here, the information certified and transmitted by the certification processing unit 13a of the responsible nodes 10a, 10c to 10h can be, for example, information (metadata) that associates a message ID, timestamp, type, movement, individual ID, quantity data, and additional data, as shown in FIG. 12. The message ID is unique identification information for the information (message) and can be a number or a letter. The timestamp is the date and time when the information is sent (or can be when the information is created). The type is the type of information, and for example, one of the following types is selected: birth, arrival, rearing, feeding, weight, treatment, medication, and shipment. The movement is data that identifies the source and destination of the object or its information, and can be identification information for the source (terminal) and the destination (terminal). The individual ID is unique identification information for the object (e.g., livestock) and can be a number or a letter. The quantity data is the quantity of the object, and can be, for example, number, weight, volume, size, time, number of times, etc. The additional data is additional data related to the above items, and may be, for example, the breed of the individual, the means of transportation, the type of food, the name of the medication administered, etc., and may be omitted if there is no additional data to add.

[0037] 6, the responsible node 10b is a node that operates and stores data according to the role label 14 (here, an auditing organization) assigned by the role-assigning node (20 in FIGS. 1 to 3). The responsible node 10b includes a communication unit 11, a storage unit 12, and a control unit 13.

[0038] The communication unit 11 is a functional unit (see FIG. 6) that communicates with the responsible nodes 10a, 10c to 10i (nodes other than its own responsible node 10b), the role-assigning node (20 in FIGS. 1 to 4), the distribution route monitoring node (30 in FIGS. 1 to 3 and 8), and the status change monitoring node (40 in FIGS. 1 to 3 and 9) via the P2P network 3. The communication unit 11 can communicate with the inspection agency terminal (50b in FIGS. 2 and 3) that corresponds to the role label assigned to its own responsible node 10b via the network (90 in FIG. 2).

[0039] The memory unit 12 is a functional unit that stores various information and programs (see FIG. 6 ). The memory unit 12 stores a role label 14, a record information database (record information DB) 15, and an evaluation criteria database (evaluation criteria DB) 16. The role label 14 is assigned by the role assignment node 20 based on the role database ( 24 in FIG. 4 ). In this case, it is a role label related to an auditing organization. The record information database 15 is a database that records various information from the responsible nodes 10a to 10h, the distribution route monitoring node 30, and the status change monitoring node 40 in association with each other. The record information database 15 shares content with the other record information databases ( 25 in FIG. 4 , 15 in FIG. 5 , 15 in FIG. 7 , 35 in FIG. 8 , and 45 in FIG. 9 ). The evaluation criteria database 16 is a database that associates conditions (e.g., multiple numerical ranges) for a specific evaluation target (e.g., weight change of adult cattle) with evaluations (e.g., excellent, good, fair, and unacceptable) (see FIG. 13 ). The evaluation criteria database 16 is not limited to the evaluation criteria shown in Figure 13, but may be, for example, an evaluation criterion that evaluates whether or not one condition is met, an evaluation criterion that evaluates each condition using a score, etc. Note that the evaluation criteria database 16 may be stored not only in the responsible node 10b (role: auditing institution), but also in other nodes 10a, 10c to 10i, 20, 30, 40 or in another blockchain network system (not shown) to further enhance safety and fairness, and may be stored as a blockchain separate from the record information databases 15, 25, 35, 45 (traceability information) on the blockchain network system 2.

[0040] The control unit 13 is a functional unit that controls the communication unit 11 and the storage unit 12 (see FIG. 6 ). The control unit 13 performs predetermined processing. The control unit 13 is configured with a recording processing unit 13b and an evaluation processing unit 13d according to the role of the role label 14 (here, an auditing organization) assigned by the role-assigning node 20. The recording processing unit 13b is a processing unit that associates various information from the assigned nodes 10a, 10c-10h (nodes other than its own node), the distribution route monitoring node 30, and the status change monitoring node 40 and records them in the record information database 15. The evaluation processing unit 13d is a processing unit that evaluates the detected information based on the evaluation criteria database 16 when it detects the reception of predetermined information (or at regular intervals), and executes the contract. The evaluation processing unit 13d creates evaluation information based on the evaluation of the detected information. The evaluation processing unit 13d records the created evaluation information in association with corresponding information in the record information database 15 of its assigned node 10b. The evaluation processing unit 13d transmits the evaluation information to the nodes 10a, 10c to 10i (nodes other than its own node), the role assignment node 20, the distribution route monitoring node 30, and the status change monitoring node 40. Although the evaluation processing unit 13d automatically performs the evaluation process in the node 10b, the evaluation processing unit 13d may transmit the received predetermined information to the inspection agency terminal 50b so that a user of the inspection agency terminal 50b (an employee of the inspection agency) can perform the evaluation process. When the evaluation processing unit 13d receives an evaluation request (including the information to be evaluated) from the livestock farmer terminal 50a, before the livestock farmer terminal 50a transmits formal information to the node 10a (role: livestock farming), the evaluation processing unit 13d may evaluate the information related to the evaluation request based on the evaluation criteria database 16 and return the evaluation result to the livestock farmer terminal 50a.

[0041] Here, the evaluation information can be, for example, information (metadata) that associates a message ID, a timestamp, an evaluation, the message ID of the evaluation target, and the evaluation criterion name, as shown in FIG. 14. The message ID is unique identification information for the information (message), and can be a number, a character, or a hash value of the entire or part of the message to be evaluated (for example, the message ID and timestamp). The timestamp is the date and time when the information was sent (or when the information was created). The evaluation is an evaluation made by the evaluation processing unit 13d. The message ID of the evaluation target is the message ID of the information that forms the basis of the evaluation. The evaluation criterion name is the name of the criterion that formed the basis of the evaluation (for example, animal welfare evaluation criteria).

[0042] 7, the responsible node 10i is a node that operates and stores data according to the role of a role label 14 (here, a consumer) assigned by a role-assigning node (20 in FIGS. 1 to 3). The responsible node 10i includes a communication unit 11, a storage unit 12, and a control unit 13.

[0043] The communication unit 11 is a functional unit (see FIG. 7) that communicates with the assigned nodes 10a to 10h (nodes other than its assigned node 10i), the role-assigning node (20 in FIGS. 1 to 4), the distribution route monitoring node (30 in FIGS. 1 to 3 and 8), and the status change monitoring node (40 in FIGS. 1 to 3 and 9) via the P2P network 3. The communication unit 11 can communicate with the consumer terminal (50i in FIGS. 2 and 3) corresponding to the role label assigned to its assigned node 10i via the network (90 in FIG. 2).

[0044] The storage unit 12 is a functional unit that stores various information and programs (see FIG. 7). The storage unit 12 stores a role label 14 and a record information database (record information DB) 15. The role label 14 is assigned by the role assignment node 20 based on the role database (24 in FIG. 4), and in this case, it is a role label related to a consumer. The record information database 15 is a database that associates and records various information from the responsible nodes 10a to 10h, the distribution route monitoring node 30, and the status change monitoring node 40. The record information database 15 shares content with the other record information databases (25 in FIG. 4, 15 in FIG. 5, 15 in FIG. 6, 35 in FIG. 8, and 45 in FIG. 9).

[0045] The control unit 13 is a functional unit that controls the communication unit 11 and the storage unit 12 (see FIG. 7). The control unit 13 performs predetermined processing. A recording processing unit 13b and a browsing processing unit 13c are set in the control unit 13 according to the role of the role label 14 (consumer in this case) assigned by the role assigning node 20. The recording processing unit 13b is a processing unit that associates various information from the assigned nodes 10a to 10h, the distribution route monitoring node 30, and the status change monitoring node 40 and records the associated information in the recorded information database 15. The browsing processing unit 13c is a processing unit that reads out the corresponding information in response to a browsing request from a consumer terminal (50i in FIGS. 2 and 3) corresponding to the role label assigned to its assigned node 10i, and transmits (responds) the information to the consumer terminal 50i.

[0046] 8, the distribution route monitoring node 30 is a node that monitors the distribution route of an object based on various information collected from the nodes (10a, 10c to 10h in FIGS. 2 and 3). The distribution route monitoring node 30 includes a communication unit 31, a storage unit 32, and a control unit 33.

[0047] The communication unit 31 is a functional unit (see FIG. 8) that communicates with the responsible nodes 10a to 10i, the role assignment node (20 in FIGS. 1 to 4), and the status change monitoring node (40 in FIGS. 1 to 3 and 9) via the P2P network 3. The communication unit 31 can communicate with the distribution route management terminal (70 in FIGS. 2 and 3) via the network (90 in FIG. 2).

[0048] The storage unit 32 is a functional unit that stores various information and programs (see FIG. 8 ). The storage unit 32 stores a distribution route rule database (distribution route rule DB) 34 and a record information database (record information DB) 35. The distribution route rule database 34 is a database that defines distribution route rules relating to combinations of shippers (identification information of the source) and recipients (identification information of the destination) along the distribution route (see FIG. 15 ). The distribution route rule database 34 may be stored not only in the distribution route monitoring node 30, but also in other nodes 10a-10i, 20, and 40 or in another blockchain network system (not shown) to further enhance safety and fairness. It may also be stored as a blockchain separate from the record information databases 15, 25, 35, and 45 (traceability information) on the blockchain network system 2. The record information database 35 is a database that associates and records various information from the responsible nodes 10a-10h, the distribution route monitoring node 30, and the status change monitoring node 40. The recording information database 35 has the same contents as the other recording information databases (25 in FIG. 4, 15 in FIGS. 5 to 7, and 45 in FIG. 9).

[0049] Here, the distribution route rule database 34 defines normal relationships between senders and receivers in a distribution route. However, combinations of senders and receivers that are not defined may be considered abnormal or prohibited. Even if the combination of senders and receivers is normal, a mismatch in the quantities in the corresponding shipping and receiving information may be considered abnormal. Even if the combination of senders and receivers is normal and the quantity data in the corresponding shipping and receiving information match, a transaction may be considered abnormal if the transaction quantity exceeds a predetermined amount (e.g., an unnatural transaction such as an unusually large amount of meat being traded directly between a butcher and a consumer, or a transaction that violates industry rules). Even if the combination of senders and receivers is normal, a mismatch in the time between shipment and arrival may be considered abnormal if the time between shipment and arrival exceeds a predetermined time (e.g., an unnatural transaction where the difference between the shipping date and the arrival date is too large). Even if the combination of senders and receivers is normal, a mismatch in the corresponding receiving information may be considered abnormal if the corresponding receiving information is not received within a predetermined time after receiving the shipping information. Furthermore, although the distribution route rule database 34 in FIG. 15 defines the relationship between shippers and recipients in different industries, for example, a livestock farmer who specializes in raising piglets may receive piglets and ship adult pigs, so the distribution route rule database 34 may also define the relationship between shippers and recipients in the same industry.

[0050] The control unit 33 is a functional unit that controls the communication unit 31 and the storage unit 32 (see FIG. 8 ). The control unit 33 performs predetermined processing and executes programs to realize the distribution route monitoring unit 33a and the record processing unit 33b. The distribution route monitoring unit 33a is a processing unit that monitors the distribution route of an object based on shipping information (information whose type is shipping) and receiving information (information whose type is receiving), and the distribution route rule database 34, and is a processing unit that executes contracts. When the distribution route monitoring unit 33a detects shipping information (or receiving information) received from the terminals 50a, 50c, . . . 50h via the corresponding nodes 10a, 10c, . . . 10h (or at regular intervals), the distribution route monitoring unit 33a checks whether the combination of the shipper and the receiver included in the shipping information (or receiving information) satisfies the conditions (distribution route rules) defined in the distribution route rule database 34. If the conditions are not met, the distribution route monitoring unit 33a creates and transmits warning information to each terminal (any of 50a, 50c, . . . 50h) associated with the shipper and the receiver. The warning information may be transmitted not only to the respective terminals related to the shipper and the receiver, but also to other terminals. Here, the warning information is information that notifies the shipper and the receiver that the distribution route is not normal and calls for their attention. When the shipper and the receiver identified by the shipping information and / or the receiving information satisfy the conditions defined in the distribution route rule database 34, the distribution route monitoring unit 33a may associate information indicating that the shipping information and / or the receiving information satisfies the distribution route rule and record the association in each of the nodes 10a to 10i, 20, 30, and 40. The recording processing unit 33b is a processing unit that associates various information from the responsible nodes 10a to 10h, the distribution route monitoring node 30, and the status change monitoring node 40 and records the associated information in the recording information database 25.

[0051] 9, the status change monitoring node 40 is a node that monitors status changes of an object based on various information collected from the nodes (10a, 10c to 10h in FIGS. 2 and 3). The status change monitoring node 40 includes a communication unit 41, a storage unit 42, and a control unit 43.

[0052] The communication unit 41 is a functional unit (see FIG. 8) that communicates with the responsible nodes 10a to 10i, the role-assigning node (20 in FIGS. 1 to 4), and the distribution route monitoring node (30 in FIGS. 1 to 3 and 8) via the P2P network 3. The communication unit 41 can communicate with the status change management terminal (80 in FIGS. 2 and 3) via the network (90 in FIG. 2).

[0053] The storage unit 42 is a functional unit that stores various information and programs (see FIG. 9 ). The storage unit 42 stores a status change rule database (status change rule DB) 44 and a record information database (record information DB) 45. The status change rule database 44 is a database that defines status change rules (rules for changes in status such as weight and number of animals) between the time of arrival and the time of shipment of an object. For example, as shown in FIG. 16 , the status change rule database 44 can be a database that associates the relationship between normal inflow and outflow volume changes (e.g., arrival ≧ shipment) at the time of arrival and shipment of an object in a predetermined role (e.g., livestock farming), the target item (e.g., number of animals), and the loss rate (e.g., 10% or less). The status change rule database 44 may be stored not only in the status change monitoring node 40, but also in other nodes 10a-10i, 20, and 30 or in another blockchain network system (not shown) to further enhance safety and fairness. It may also be stored as a blockchain separate from the record information databases 15, 25, 35, and 45 (traceability information) on the blockchain network system 2. The record information database 45 is a database that associates and records various pieces of information from the responsible nodes 10a to 10h, the distribution route monitoring node 30, and the status change monitoring node 40. The record information database 45 shares the same contents as the other record information databases (25 in FIG. 4, 15 in FIGS. 5 to 7, and 35 in FIG. 8).

[0054] For example, if the role is livestock farming, the number of incoming piglets may decrease due to illness, death, or the like during growth, and therefore the status change rule database 44 can be set so that the number of incoming piglets is equal to or greater than the number of shipped adult pigs (see FIG. 16 ). Also, for example, if the role is butchering, the status change rule database 44 can be set so that the loss rate is higher, since meat is made by removing bones from the carcasses of slaughtered livestock.

[0055] The control unit 43 is a functional unit that controls the communication unit 41 and the storage unit 42 (see FIG. 9 ). The control unit 43 performs predetermined processing and executes programs to realize the status change monitoring unit 43a and the recording processing unit 43b. The status change monitoring unit 43a is a processing unit that monitors status changes of objects based on shipping information (information whose type is shipping), arrival information (information whose type is arrival), and the status change rule database 44, and executes contracts. When the status change monitoring unit 43a detects receipt of shipping information from one of the nodes 10a, 10c, 10d, 10e, 10f, 10g, 10h it is responsible for (or at regular intervals), it reads the arrival information from the same node immediately before the shipping information from the recording information database 45, determines whether the status change based on the shipping information and each quantity (e.g., number of animals, weight, etc.) in the arrival information satisfies the conditions (status change rules) defined in the status change rule database 44, and if the conditions are not met, creates and transmits warning information to the terminal (one of 50a, 50c, 10h) associated with the shipper in the shipping information. The alert information may be transmitted not only to the terminal related to the shipper but also to other terminals. When the quantities in the shipping information and arrival information satisfy the status change rule database 44, the status change monitoring unit 43a may associate the shipping information with certification information indicating that the status change rule is satisfied and record the association in each of the nodes 10a to 10i, 20, 30, and 40. The recording processing unit 43b is a processing unit that associates various information from the responsible nodes 10a to 10h, the distribution route monitoring node 30, and the status change monitoring node 40 and records the associated information in the recording information database 25.

[0056] Referring to FIG. 10, terminals 50a to 50i, 60, 70, and 80 are terminals used by parties involved with the object. Terminals 50a to 50i, 60, 70, and 80 each have unique identification information. Terminal 50a is a livestock producer terminal used by livestock producers such as livestock farmers (see FIGS. 1 to 3). Terminal 50b is an inspection agency terminal used by an inspection agency such as an animal welfare association. Terminal 50c is a slaughterhouse terminal used by slaughterhouses. Terminal 50d is a butcher terminal used by butchers. Terminal 50e is a processor terminal used by processors. Terminal 50f is a wholesaler terminal used by wholesalers. Terminal 50g is a retailer terminal used by retailers. Terminal 50h is a food and beverage supplier terminal used by a food and beverage supplier. Terminal 50i is a consumer terminal used by a consumer. Note that consumers may not only be end consumers of the target object, but also investors or banks that invest or lend in businesses related to the target object. Terminals 50a to 50i in Figures 1 to 3 are merely examples, and the names and number of terminals may vary depending on the traders, departments, number of processes, etc. involved in the distribution process. Terminal 60 is a role management terminal used by an administrator with specific authority regarding the role assignment node 20 in the blockchain network system 2. Terminal 70 is a distribution route management terminal used by an administrator with specific authority regarding the distribution route monitoring node 30 in the blockchain network system 2. Terminal 80 is a status change management terminal used by an administrator with specific authority regarding the status change monitoring node 40 in the blockchain network system 2.

[0057] The terminals 50a to 50i, 60, 70, and 80 each include a communication unit 51, a memory unit 52, an input unit 53, a display unit 54, and a control unit 55 (see FIG. 10). The communication unit 51 is a functional unit that communicates with the blockchain network system 2 via the network (90 in FIGS. 1 and 2). The memory unit 52 is a functional unit that stores various information and programs. The input unit 53 is a functional unit that inputs information, and may use, for example, a keyboard, mouse, touch panel, camera, sensor, reader, microphone, etc. The display unit 54 is a functional unit that displays (or outputs) information. The control unit 55 is a functional unit that controls the communication unit 51, memory unit 52, input unit 53, and display unit 54, and performs predetermined information processing by executing a program.

[0058] The network 90 is a wired or wireless communication network that communicatively connects the blockchain network system 2 with the terminals 50a to 50i, 60, 70, and 80 (see FIGS. 1 to 3). As the network 90, for example, a communication network such as a PAN (Personal Area Network), a LAN (Local Area Network), a MAN (Metropolitan Area Network), a WAN (Wide Area Network), or a GAN (Global Area Network) can be used.

[0059] The operation of the traceability management system according to the first embodiment will be described.

[0060] First, the operation of the traceability management system according to the first embodiment when assigning a role will be described with reference to the drawings. Fig. 17 is a sequence chart that schematically shows the operation of an example of the traceability management system according to the first embodiment when assigning a role. Please refer to Figs. 1 to 3 for the configuration of the traceability management system.

[0061] First, the role management terminal 60 creates a role database (corresponding to 24 in FIG. 4, see FIG. 11) in response to a user operation (step A1). When creating the role database, a processing unit setting program is also created to set a processing unit (any of the certification processing unit (13a in FIG. 5), recording processing unit (13b in FIGS. 5 to 7), browsing processing unit (13c in FIGS. 5 and 7), and evaluation processing unit (13d in FIG. 6)) that performs a predetermined process in the assigned nodes 10a to 10i, according to the role of the role label in the role database.

[0062] Next, the role management terminal 60 transmits the created role database to the role-assigned node 20 (step A2). When transmitting the role database, the processing unit setting program is also transmitted.

[0063] Next, the role assigning node 20 receives the role database from the role management terminal 60 (step A3).

[0064] Next, the role assigning node 20 stores the received role database (see 24 in FIG. 4 and FIG. 11) (step A4). When storing the role database, the processing unit setting program is also stored.

[0065] Next, the role assigning node 20 transmits the corresponding role labels to each of the assigned nodes 10a to 10i based on the stored role database 24 (step A5). When transmitting the role labels, the role assigning node 20 also transmits the processing unit setting program corresponding to the role labels.

[0066] Next, each of the responsible nodes 10a to 10i receives the corresponding role label (step A6). When receiving the role label, the responsible node also receives the processing unit setting program.

[0067] Finally, each of the assigned nodes 10a to 10i stores the received role label (step A7), and then ends the process. When storing the role label, the assigned nodes 10a to 10i execute a processing unit setting program to set a processing unit corresponding to the role of the role label in each of the assigned nodes 10a to 10i.

[0068] In addition, adding or deleting nodes or changing roles can be done by the role management terminal 60 changing the contents of the role database 24 stored in the role assignment node 20 or updating to a new role database 24, and in doing so, the processing units can be set according to the role of the role label.

[0069] Next, the operation of the traceability management system according to the first embodiment when registering information will be described with reference to the drawings. FIG. 18 is a sequence chart that schematically illustrates an example of the operation of the traceability management system according to the first embodiment when recording information related to the livestock industry. For the configuration of the traceability management system, please refer to FIGS. 1 to 3. Here, the operation of recording information related to the livestock industry after role assignment will be described as an example.

[0070] First, the livestock producer terminal 50a acquires or inputs identification information (ID) and data required to create information through user operation (step B1).

[0071] Next, the livestock producer terminal 50a creates information (corresponding to the information in FIG. 12) through user operation (step B2). Here, the information includes, for example, birth information, arrival information, rearing information, treatment information, medication information, and shipping information (information types such as birth, arrival, rearing, treatment, medication, and shipping).

[0072] Next, the livestock breeder terminal 50a transmits the created information to the node in charge 10a (role: livestock breeding) (step B3).

[0073] Next, the node in charge 10a (role: livestock industry) receives the information from the livestock industry terminal 50a (step B4).

[0074] Next, the responsible node 10a (role: livestock industry) checks whether there are any missing or incorrect data in the received information, and if there are no missing or incorrect data, performs a certification process (step B5). If there are missing or incorrect data in the received information, the responsible node 10a (role: livestock industry) may send warning information to the livestock industry terminal 50a to inform the livestock industry operator of this and call attention to the fact, and then end the process.

[0075] Next, the responsible node 10a (role: livestock industry) records the information (certified) in association with the corresponding information in the record information database (15 in Figure 5) of its own responsible node 10a (role: livestock industry) (step B6).

[0076] Next, the responsible node 10a (role: livestock industry) transmits the information (certified) to the responsible nodes 10b to 10i (nodes other than its own responsible node 10a), the role assignment node 20, the distribution route monitoring node 30, and the status change monitoring node 40 (step B7).

[0077] Next, the responsible nodes 10b to 10i, the role assigning node 20, the distribution route monitoring node 30, and the status change monitoring node 40 each receive the information (certified) from the responsible node 10a (role: livestock industry) (step B8).

[0078] Finally, the responsible nodes 10b to 10i, the role-assigning node 20, the distribution route monitoring node 30, and the status change monitoring node 40 each record the received information (certified) in association with the corresponding information in the recording information database of their own nodes 10b to 10i, 20, 30, and 40 (15 in Figures 5 to 7, 25 in Figure 4, 35 in Figure 8, and 45 in Figure 9) (step B9), and then terminate.

[0079] Steps B1 to B9 can also be applied to the operations when recording information relating to the slaughtering industry, meat packing industry, processing industry, wholesale industry, retail industry, and food service industry after the roles have been assigned.

[0080] Next, the operation of the traceability management system according to the first embodiment at the time of evaluation will be described with reference to the drawings. Fig. 19 is a sequence chart that schematically shows the operation of the traceability management system according to the first embodiment at the time of evaluation. Please refer to Figs. 1 to 3 for the configuration of the traceability management system.

[0081] First, the responsible node 10b (role: auditing institution) detects the reception of predetermined information (corresponding to the reception in step B8 in FIG. 18) (step C1). Here, the predetermined information is information whose type (see FIG. 12) is the evaluation target (e.g., care, treatment, medication, etc.) in the evaluation criteria database (16 in FIG. 6). The predetermined information may also be information whose destination (see FIG. 12) is the auditing institution terminal (50b in FIGS. 1 to 3) or the identification information of the responsible node 10b (role: auditing institution).

[0082] Next, the responsible node 10b (role: auditing organization) evaluates the detected information based on the evaluation criteria database 16 (step C2).

[0083] Next, the responsible node 10b (role: auditing agency) creates evaluation information (see Figure 14) based on the evaluation of the detected information, and records the created evaluation information in association with corresponding information in the recording information database (15 in Figure 6) of its own responsible node 10b (role: auditing agency) (step C3).

[0084] Next, the responsible node 10b (role: auditing agency) transmits the created evaluation information to the responsible nodes 10a, 10c to 10i (nodes other than its own node), the role-granting node 20, the distribution route monitoring node 30, and the status change monitoring node 40 (step C4).

[0085] Next, the nodes 10a, 10c to 10i, 20, 30, and 40 each receive the evaluation information from the responsible node 10b (role: audit organization) (step C5).

[0086] Finally, nodes 10a, 10c to 10i, 20, 30, and 40 each record the received evaluation information in association with the corresponding information in their own recorded information databases (15 in Figure 5, 15 in Figure 7, 25 in Figure 4, 35 in Figure 8, and 45 in Figure 9) (step C6), and then terminate.

[0087] Note that steps C1 to C6 have been explained using the example of evaluating information related to the livestock industry, but they may also be applied to the evaluation of information related to other industries. For example, information related to the processing industry (e.g., processing information) may be evaluated based on evaluation criteria related to food processing.

[0088] Next, the operation of the traceability management system according to the first embodiment when monitoring a distribution route will be described with reference to the drawings. Fig. 20 is a sequence chart that schematically illustrates an example of the operation of the traceability management system according to the first embodiment when a direct transaction takes place between a livestock farmer and a food service provider. For the configuration of the traceability management system, please refer to Figs. 1 to 3. Here, the operation when a direct transaction takes place between a livestock farmer and a food service provider will be described as an example.

[0089] First, the distribution route monitoring node 30 detects the receipt of shipping information (corresponding to the receipt in step B8 in FIG. 18) (step D1). Note that although the receipt of only shipping information is detected here, it is also possible to detect the receipt of only the corresponding immediately following arrival information, or to detect the receipt of both shipping information and arrival information.

[0090] Next, the distribution route monitoring node 30 determines whether the sender (here, the livestock farmer terminal 50a) and the recipient (here, the food service provider terminal 50h) in the detected shipping information satisfy the conditions defined in the distribution route rule database (see 34 in Figure 8 and Figure 15) (step D2). If the conditions are satisfied (YES in step D2), the process ends.

[0091] If the above conditions are met (YES in step D2), the detected shipping information may be associated with certification information certifying that the distribution route is normal and recorded. Furthermore, even if the shipper and receiver satisfy the conditions defined in the distribution route rule database in step D2, if the quantities in the corresponding shipping information and receiving information do not match, the process may proceed to step D3. Furthermore, even if the shipper and receiver satisfy the conditions defined in the distribution route rule database in step D2 and the quantities in the corresponding shipping information and receiving information match, the process may proceed to step D3 if the transaction quantity exceeds a predetermined amount (if the transaction volume is abnormal). Furthermore, even if the shipper and receiver satisfy the conditions defined in the distribution route rule database in step D2, if the time from shipment to receiving exceeds a predetermined time (if the transaction time is abnormal), the process may proceed to step D3. Furthermore, even if the shipper and receiver satisfy the conditions defined in the distribution route rule database in step D2, if corresponding receiving information cannot be received within a predetermined time after receiving shipping information, the process may proceed to step D3.

[0092] If the above conditions are not met (NO in step D2), the distribution route monitoring node 30 creates warning information to notify the user that the distribution route is not normal (step D3). When creating the warning information, the warning information may be recorded in association with the detected shipping information.

[0093] Next, the distribution route monitoring node 30 transmits the generated warning information to the sender (livestock farmer terminal 50a) and the receiver (food service provider terminal 50h) in the detected shipping information (step D4). Note that the warning information may be transmitted not only to the sender and receiver terminals, but also to other terminals.

[0094] After step D4, the livestock producer terminal 50a receives the warning information from the distribution route monitoring node 30 (step D5), displays the received warning information (step D6), and then ends the process.

[0095] Also, after step D4, in parallel with steps D5 and D6, the food and beverage business terminal 50h receives warning information from the distribution route monitoring node 30 (step D7), displays the received warning information (step D8), and then terminates.

[0096] Note that steps D1 to D8 may also be applied to combinations other than those between livestock breeders and food service businesses.

[0097] Next, the operation of the traceability management system according to the first embodiment when monitoring a change in status will be described with reference to the drawings. Fig. 21 is a sequence chart that schematically illustrates an example of the operation of the traceability management system according to the first embodiment when there is a mismatch between receipt and shipment at a processor. Please refer to Figs. 1 to 3 for the configuration of the traceability management system. Here, the operation when there is a mismatch between receipt and shipment at a processor will be described as an example.

[0098] First, the status change monitoring node 40 detects the receipt of shipping information (corresponding to the receipt in step B8 in FIG. 18) (step E1). Note that although the receipt of shipping information is detected in step E1, it is also possible to detect the receipt of arrival information instead, and then detect the receipt of corresponding shipping information, skipping step E2 and proceeding to step E3.

[0099] Next, the status change monitoring node 40 reads out the arrival information from the record information database (45 in FIG. 9) from the same node (here, 10e (role: processing) in FIGS. 2 and 3) immediately before the detected shipping information (step E2). If the arrival information cannot be read out from the record information database (45 in FIG. 9), the process may proceed to step E3, where it is determined that the conditions defined in the status change rule database 44 are not satisfied, and the process may proceed to step E4.

[0100] Next, the status change monitoring node 40 determines whether the detected shipping information and the quantities (here, weights) of the read-out receiving information satisfy the conditions (here, processing industry, input / output relationship, and loss rate) defined in the status change rule database 44 (step E3). If the conditions are satisfied (YES in step E3), the process ends.

[0101] If the above condition is met (YES in step E3), the detected shipping information may be recorded in association with certification information that certifies that the state change is normal.

[0102] If the above condition is not satisfied (NO in step E3), the status change monitoring node 40 generates warning information to notify the user that the status change is abnormal and to call the user's attention (step E4). When generating the warning information, the warning information may be recorded in association with the detected shipping information.

[0103] Next, the status change monitoring node 40 transmits the generated warning information to the shipper (processor terminal 50e) in the detected shipping information (step E5). Note that the warning information may be transmitted not only to the shipper terminal but also to other terminals.

[0104] Next, the processor terminal 50e receives the warning information from the status change monitoring node 40 (step E6), displays the received warning information (step E7), and then ends the process.

[0105] Although the first embodiment is configured as described above, the configuration of the traceability management system after role assignment can be modified as shown in FIG. 22 . That is, a configuration can be adopted in which multiple terminals 50a (livestock farmer terminals in FIG. 22 ) are connected to one responsible node 10a assigned a role (livestock industry in FIG. 22 ). Furthermore, for example, in a case where there are multiple auditing institutions with different evaluation standards, the blockchain network system 2 can be configured with multiple responsible nodes 10b assigned the same role (auditing institutions in FIG. 22 ), and each responsible node 10b can be connected to a terminal 50b (auditing institution terminal in FIG. 22 ). Furthermore, in the blockchain network system 2, excess responsible nodes 10n may be disabled without being assigned a role. Furthermore, when there is a shortage of nodes, the role-assigning node 20 may add new nodes and change the contents of the role database (see FIG. 11 ), or update the role database to a new one and assign roles to each node. For example, in the case of a major food manufacturer that has multiple industries (such as livestock, slaughtering, meatpacking, and processing), there may be a node in charge of the role of combining multiple industries. Also, if one industry is subdivided into multiple departments, there may be a node in charge of the role of each of the multiple departments.

[0106] According to the first embodiment, in the blockchain network system 2, the role assigning node 20 assigns roles to the responsible nodes 10a to 10i, and the responsible node 10b (role: auditing organization), the distribution route monitoring node 30, and the status change monitoring node 40 evaluate the target object, monitor the distribution route, and monitor status changes. Therefore, by viewing the results, it is possible to contribute to objectively, neutrally, impartially, fairly, and easily confirming the status (evaluation, fraud, falsification, etc.) inherent in the data when tracking collected information. This allows the parties involved to immediately confirm evaluation, fraud, falsification, etc. without having to verify it themselves.

[0107] Furthermore, according to the first embodiment, the role assigning node 20 assigns roles to each of the responsible nodes 10a to 10i, so that the acquired information can be automatically monitored for data deficiencies or errors according to the role of each of the terminals 50a, 50c to 50h, and distribution routes and status changes can be automatically monitored. Note that in a typical blockchain network system without a role assignment function, each node is equal and freely interacts with each other, so it is not possible to organize the collected information and automatically monitor the distribution routes and status changes of the target object.

[0108] Furthermore, according to embodiment 1, the object is evaluated by the responsible node 10b (role: auditing institution) and the results are made available for viewing, thereby demonstrating the added value that the object has been evaluated based on objective, neutral, fair, and impartial evaluation criteria.

[0109] Furthermore, according to the first embodiment, the distribution route of the object is monitored by the distribution route monitoring node 30, and the results can be viewed, so it is guaranteed that the distribution route of the object is consistent from start to finish, which helps to ensure the reliability of the object and contributes to the widespread adoption of high value-added products.

[0110] Furthermore, according to the first embodiment, the distribution route of the object is monitored by the status change monitoring node 40, and the results can be viewed, so that the authenticity of the object can be guaranteed.

[0111] Furthermore, according to embodiment 1, the information collected is managed using the blockchain network system 2, so it is possible to guarantee that the information has not been altered since it was recorded, and even if the information is altered, the alteration history is reliably recorded, so that it is possible to confirm after the fact that the information has been altered.

[0112] Furthermore, according to embodiment 1, stakeholders can jointly operate the blockchain network system 2, and it is possible to prevent information from being changed (to the advantage of a specific participant) at the discretion of that participant.

[0113] As background, due to concerns about BSE (Bovine Spongiform Encephalopathy), information on cattle is currently managed by government agencies under national leadership. Information on cattle submitted by livestock producers and intermediate processors is managed by government agencies, which then issue certifications (permissions and guarantees) for beef. While issues like BSE do not exist for other livestock species, as animal welfare becomes more widespread, it will become necessary to demonstrate to consumers that livestock products produced and distributed have been raised in accordance with animal welfare. As animal welfare advances, differences in raising costs and prices may arise between those that comply with animal welfare and those that do not, leading to information falsification and consumer distrust. To demonstrate to consumers that information is free of fraud, it is considered necessary to provide guarantees for the information through a traceability system. However, there is no nationally-led system for guaranteeing information for other livestock species, and industry associations, such as livestock producers and intermediate processors, must operate their own systems. If industry associations operate their own systems, they must demonstrate to consumers the legitimacy of the information they manage. To achieve this, it is necessary for various industries with mutual interests (livestock, processing, distribution, retail, etc.) to be able to operate jointly or in a pooled manner. However, if an operation where information is guaranteed only by a specific industry does not allow stakeholders to share the same information with confidence, it will not become widespread and its use will not be promoted. As a result, the conventional system allows powerful businesses to operate arbitrarily or in a way that benefits specific participants. A traceability management system for animal welfare products is needed to ensure the quality, safety, and reliability of livestock products raised in accordance with animal welfare principles. Furthermore, because animal welfare livestock products have higher added value and are traded at higher prices than regular livestock products, the traceability management system must be able to withstand food fraud and information tampering. In addition, there is no nationally led, unified traceability system for non-cattle livestock such as pigs and chickens. Unlike cattle traceability, it is not nationally led, and instead is operated and used jointly by multiple businesses with vested interests. Therefore, a system that allows information to be manipulated according to the wishes of a specific business or that creates advantages or disadvantages is problematic, so a system that can achieve fairness is required.The first embodiment provides a traceability management system that meets these needs.

[0114] [Embodiment 2] A traceability management system according to embodiment 2 will be described with reference to the drawings. Fig. 23 is a block diagram showing a schematic configuration of the traceability management system according to embodiment 2 after roles have been assigned.

[0115] The blockchain network system 2 is configured such that nodes 10a, 10c, ..., 20, 40 are connected to one another on a network 3 and the nodes 10a, 10c, ..., 20, 40 store the same information about an object in a distributed manner.

[0116] The nodes 10a, 10c, . . . , 20, 40 include a plurality of responsible nodes 10a, 10c, .

[0117] The responsible nodes 10a, 10c, ... are responsible for predetermined roles. The role assigning node 20 is configured to store a role database that defines roles corresponding to each responsible node 10a, 10c, ..., assign a role (e.g., a first role, a second role, ...) to each responsible node 10a, 10c, ... based on the role database, and connect each responsible node 10a, 10c, ... to at least one corresponding terminal 50a, 50b, ... outside the blockchain network system 2. The status change monitoring node 40 is configured to store a status change rule database that defines a status change rule between the time of arrival and the time of shipment of an object, and to receive information from the terminals 50a, 50b, ... via the responsible nodes 10a, 10c, ..., and to monitor status changes of the object by determining whether a status change based on the corresponding arrival information and shipment information among the input information satisfies the status change rule.

[0118] According to embodiment 2, in the blockchain network system 2, the role-assigning node 20 assigns roles to the responsible nodes 10a, 10c, ..., and the status change monitoring node 40 monitors status changes of the target object. Therefore, by viewing the results, it is possible to contribute to objectively, neutrally, impartially, fairly, and easily confirming the status (fraud, falsification, etc.) inherent in the data when tracking the collected information.

[0119] [Embodiment 3] A traceability management system according to embodiment 3 will be described with reference to the drawings. Fig. 24 is a block diagram showing a schematic configuration of the traceability management system according to embodiment 3 after roles have been assigned.

[0120] The blockchain network system 2 is configured such that nodes 10a, 10c, ..., 20, and 30 are connected to one another on a network 3, and the nodes 10a, 10c, ..., 20, and 30 store the same information related to an object in a distributed manner.

[0121] The nodes 10a, 10c, . . . , 20, 30 include a plurality of responsible nodes 10a, 10c, .

[0122] The responsible nodes 10a, 10c, ... are responsible for predetermined roles. The role assigning node 20 is configured to store a role database that defines roles corresponding to each responsible node 10a, 10c, ..., assign a role (e.g., a first role, a second role, ...) to each responsible node 10a, 10c, ... based on the role database, and connect each responsible node 10a, 10c, ... to at least one corresponding terminal 50a, 50b, ... outside the blockchain network system 2. The distribution route monitoring node 30 is configured to store a distribution route rule database that defines distribution route rules related to combinations of shippers and receivers, and to monitor the distribution route of an object by receiving information from the terminals 50a, 50b, ... via the responsible nodes 10a, 10c, ... and determining whether a combination of shippers and receivers included in one or both of the shipping information and the receiving information among the input information satisfies the distribution route rule.

[0123] According to embodiment 3, in the blockchain network system 2, roles are assigned to the responsible nodes 10a, 10c, ... by the role-assigning node 20, and the distribution route monitoring node 30 monitors the distribution route of the target object. Therefore, by viewing the results, it is possible to contribute to objectively, neutrally, impartially, fairly, and easily confirming the conditions (fraud, falsification, etc.) inherent in the data when tracking the collected information.

[0124] [Fourth Embodiment] A traceability management system according to a fourth embodiment will be described with reference to the drawings. Fig. 25 is a block diagram showing a schematic configuration of the traceability management system according to the fourth embodiment after roles have been assigned.

[0125] The blockchain network system 2 is configured such that nodes 10a, 10b, 10c, ..., 20 are connected to one another on a network 3 and the nodes 10a, 10b, 10c, ..., 20 store the same information about an object in a distributed manner.

[0126] The nodes 10a, 10b, 10c, and 20 include a plurality of responsible nodes 10a, 10b, 10c, . . . and a role assigning node 20.

[0127] The responsible nodes 10a, 10b, 10c, ... are responsible for predetermined roles. The role assigning node 20 is configured to store a role database that defines the role corresponding to each responsible node 10a, 10b, 10c, ..., assign a role (e.g., first role, auditing agency, second role, ...) to each responsible node 10a, 10b, 10c, ... based on the role database, and connect them to at least one corresponding terminal 50a, 50b, 50c, ... outside the blockchain network system 2. At least one of the responsible nodes 10a, 10b, 10c, ... (10b in Figure 25) is assigned a role related to an auditing agency by the role-assigning node 20, and stores an evaluation criteria database that associates conditions and evaluations for specified evaluation targets, and is configured so that information from a terminal (any of 50a, 50c, ...) is input via a responsible node 10a, 10c, ... other than the responsible node 10b that has been assigned the role related to an auditing agency, and the evaluation target in the input information is evaluated based on the evaluation criteria database.

[0128] According to embodiment 4, in the blockchain network system 2, roles are assigned to the responsible nodes 10a, 10b, 10c, ... by the role-assigning node 20, and the responsible node 10b (role: auditing institution) evaluates the object. Therefore, by viewing the results, it is possible to contribute to objectively, neutrally, fairly, impartially, and easily confirming the state (evaluation) inherent in the data when tracking collected information.

[0129] [Embodiment 5] A traceability management system according to embodiment 5 will be described with reference to the drawings. Fig. 26 is a block diagram showing a schematic configuration of the traceability management system according to embodiment 5 after roles have been assigned.

[0130] The blockchain network system 2 is configured such that nodes 10a, 10c, ..., 20 are connected to one another on a network 3 and the nodes 10a, 10c, ..., 20 store the same information about an object in a distributed manner.

[0131] The nodes 10a, 10c, . . . , 20 include a plurality of responsible nodes 10a, 10c, .

[0132] The assigned nodes 10a, 10c, ... are assigned predetermined roles. The role assigning node 20 is configured to store a role database that defines the roles corresponding to each assigned node 10a, 10c, ..., assign a role (e.g., first role, second role, ...) to each assigned node 10a, 10c, ... based on the role database, and connect each assigned node 10a, 10c, ... to at least one corresponding terminal 50a, 50c, ... outside the blockchain network system 2.

[0133] According to embodiment 5, by assigning roles to responsible nodes 10a, 10c, ... by the role-assigning node 20 in the blockchain network system 2, it becomes possible to organize information and evaluate the target object, monitor distribution routes, and monitor status changes. By viewing the results, it is possible to contribute to objectively, neutrally, impartially, fairly, and easily confirming the status inherent in the data when tracking collected information (evaluation, fraud, falsification, etc.).

[0134] The nodes and terminals according to the first to fifth embodiments can be configured using so-called hardware resources (information processing devices, computers), and those having the configuration shown in Fig. 27 can be used. For example, the hardware resource 100 includes a processor 101, a memory 102, a network interface 103, and the like, which are interconnected by an internal bus 104. An instruction program and required data for operating the processor 101 are stored in the memory 102, and the processor 101 can be operated by inputting and outputting signals to and from the outside via the network interface 103 as necessary.

[0135] 27 is not intended to limit the hardware configuration of the hardware resource 100. The hardware resource 100 may include hardware (e.g., an input / output interface) that is not shown. Furthermore, the number of units, such as the processor 101, included in the device is not intended to be limited to the example shown in FIG. 27 , and for example, multiple processors 101 may be included in the hardware resource 100. The processor 101 may be, for example, a central processing unit (CPU), a microprocessor unit (MPU), a graphics processing unit (GPU), or the like.

[0136] The memory 102 may be, for example, a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), or a solid state drive (SSD).

[0137] The network interface 103 may be, for example, a LAN (Local Area Network) card, a network adapter, a network interface card, or the like.

[0138] The functions of the hardware resource 100 are realized by the processing modules described above. The processing modules are realized, for example, by the processor 101 executing a program stored in the memory 102. The programs can be updated by downloading them over a network or by using a storage medium that stores the programs. Furthermore, the processing modules may be realized by semiconductor chips. In other words, it is sufficient that the functions performed by the processing modules can be realized by executing software on some kind of hardware.

[0139] Some or all of the above embodiments may be described as, but are not limited to, the following supplementary notes.

[0140] [Supplementary Note 1] A blockchain network system in which nodes are connected to each other on a network and configured to have the nodes store the same information related to an object in a distributed manner, the nodes comprising: a plurality of assigned nodes each assigned to a predetermined role; a role assignment node configured to store a role database that defines a role corresponding to each of the assigned nodes, and assign a role to each of the assigned nodes based on the role database and connect them to at least one corresponding terminal outside the blockchain network system; and a status change monitoring node that stores a status change rule database that defines a status change rule between the time of arrival and the time of shipment of an object, and is configured to input the information from the terminal via the assigned node, and monitor status changes of the object by determining whether or not status changes based on corresponding arrival information and shipment information from the input information satisfy the status change rule. [Supplementary Note 2] The blockchain network system according to Supplementary Note 1, wherein the status change monitoring node is configured to transmit warning information to the corresponding terminal when the status change based on the arrival information and the shipping information does not satisfy the status change rule defined in the status change rule database, notifying the corresponding terminal that the status change is abnormal and calling for attention. [Supplementary Note 3] The blockchain network system according to Supplementary Note 2, wherein the status change monitoring node is configured to associate the warning information with both or one of the arrival information and the shipping information stored in a distributed manner in the nodes and record it. [Supplementary Note 4] The blockchain network system according to Supplementary Note 2, wherein the status change monitoring node is configured to associate the arrival information and the shipping information stored in a distributed manner in the nodes and record it with certification information indicating that the status change rule is satisfied, when the status change based on the arrival information and the shipping information satisfies the status change rule defined in the status change rule database.[Supplementary Note 5] The blockchain network system according to Supplementary Note 1, wherein the status change monitoring node is configured to transmit warning information to notify users that the status change is abnormal and to call their attention when there is no arrival information corresponding to the shipping information. [Supplementary Note 6] A blockchain network system configured so that nodes are connected to each other on a network and so that the nodes store identical information related to an object in a distributed manner, the nodes comprising: a plurality of assigned nodes each assigned to a predetermined role, a role assigning node configured to store a role database that defines a role corresponding to each of the assigned nodes and to assign a role to each of the assigned nodes based on the role database and connect them to at least one corresponding terminal outside the blockchain network system, and a distribution route monitoring node that stores a distribution route rule database that defines distribution route rules related to combinations of shippers and recipients, and is configured to receive the information from the terminals via the assigned node and monitor the distribution route of the object by determining whether a combination of shippers and recipients included in one or both of the shipping information and the arrival information among the input information satisfies the distribution route rule. [Supplementary Note 7] The blockchain network system according to Supplementary Note 6, wherein the distribution route monitoring node is configured, when a combination of the shipper and the recipient in one or both of the shipping information and the receiving information does not satisfy the distribution route rule, to transmit warning information to the corresponding terminal in one or both of the shipping information and the receiving information distributed and stored in the node, informing that the distribution route is not normal and calling for attention. [Supplementary Note 8] The blockchain network system according to Supplementary Note 7, wherein the distribution route monitoring node is configured to record the warning information in association with one or both of the receiving information and the shipping information distributed and stored in the node.[Supplementary Note 9] The blockchain network system according to Supplementary Note 7, wherein the distribution route monitoring node is configured to, when a combination of the shipper and the recipient in one or both of the shipping information and the receiving information satisfies the distribution route rule, associate certification information indicating that the distribution route rule is satisfied with one or both of the shipping information and the receiving information distributed and stored in the node, and record the association. [Supplementary Note 10] The blockchain network system according to Supplementary Note 6, wherein the receiving information and the shipping information each include data on quantity, and when the quantities in the shipping information and the receiving information do not match, or when the quantity in the shipping information or the receiving information exceeds a predetermined amount, the distribution route monitoring node is configured to send warning information to the corresponding terminal to notify that the distribution route is abnormal and to call attention to the fact that the distribution route is not normal. [Supplementary Note 11] The blockchain network system according to Supplementary Note 6, wherein the shipping information and the arrival information each include data related to date and time, and the distribution route monitoring node is configured to, when the time between the date and time of the shipping information and the date and time of the arrival information exceeds a predetermined time, transmit warning information to the corresponding terminal to notify that the distribution route is not normal and to call for attention. [Supplementary Note 12] The blockchain network system according to Supplementary Note 6, wherein the shipping information includes data related to date and time, and when the distribution route monitoring node cannot receive corresponding arrival information within a predetermined time from the date and time of the shipping information, transmit warning information to the corresponding terminal to notify that the distribution route is not normal and to call for attention.[Supplementary Note 13] A blockchain network system configured so that nodes are connected to each other on a network and so that the nodes store the same information related to an object in a distributed manner, the nodes comprising: a plurality of assigned nodes each assigned to a predetermined role; and a role assigning node configured to store a role database that defines the role corresponding to each of the assigned nodes, assign a role to each of the assigned nodes based on the role database, and connect the assigned nodes to at least one corresponding terminal outside the blockchain network system, wherein at least one of the assigned nodes is assigned a role related to an audit organization by the role assigning node, and stores an evaluation criteria database that associates conditions and evaluations for a predetermined evaluation object, the blockchain network system being configured so that the information from the terminal is input via a assigned node other than the assigned node assigned the role related to the audit organization, and the blockchain network system evaluates the evaluation object in the input information based on the evaluation criteria database. [Supplementary Note 14] The blockchain network system according to Supplementary Note 13, wherein the assigned node assigned the role of the audit organization is configured to record evaluation information including the evaluation results in association with the information stored in a distributed manner in the nodes. [Supplementary Note 15] A blockchain network system configured so that nodes are connected to each other on a network and so that the nodes store the same information related to an object in a distributed manner, the blockchain network system comprising: a plurality of assigned nodes each assigned to a predetermined role; and a role assigning node configured to store a role database that defines a role corresponding to each assigned node, assign a role to each assigned node based on the role database, and connect the assigned nodes to at least one corresponding terminal outside the blockchain network system.[Supplementary Note 16] The blockchain network system according to any one of Supplements 1 to 15, wherein the responsible node is configured to check whether there are any data deficiencies or errors in the information from the corresponding terminal, and if there are no deficiencies or errors, to have the information distributed and stored in the nodes. [Supplementary Note 17] The blockchain network system according to any one of Supplements 1 to 15, wherein the responsible node is configured to read out the corresponding information in response to a viewing request from the corresponding terminal and send it to the terminal. [Supplementary Note 18] A traceability management system comprising: the blockchain network system according to any one of Supplements 1 to 15; a role management terminal configured to be connected to the role assigning node; and a plurality of terminals configured to be connected to the corresponding responsible nodes to which roles have been assigned by the role management terminal. [Supplementary Note 19] A traceability management method in which traceability is managed by a blockchain network system in which nodes are connected to each other on a network and are configured to have the nodes store the same information related to an object in a distributed manner, wherein the nodes include: a plurality of assigned nodes each assigned to a predetermined role; a role assignment node configured to store a role database that defines a role corresponding to each of the assigned nodes; and a status change monitoring node configured to store a status change rule database that defines a status change rule between the time of arrival and the time of shipment of an object, the traceability management method including the steps of: the role assignment node assigning a role to each of the assigned nodes based on the role database and connecting each of the assigned nodes to at least one corresponding terminal outside the blockchain network system; inputting the information from the terminal to the status change monitoring node via the assigned node to which a role has been assigned by the role assignment node; and monitoring a status change of the object by the status change monitoring node determining whether a status change based on corresponding arrival information and shipping information from the input information satisfies the status change rule.[Supplementary Note 20] A traceability management method in which traceability is managed by a blockchain network system in which nodes are connected to each other on a network and are configured to have the nodes store identical information related to an object in a distributed manner, wherein the nodes comprise: a plurality of assigned nodes each assigned to a predetermined role; a role assigning node configured to store a role database that defines the role corresponding to each of the assigned nodes; and a distribution route monitoring node configured to store a distribution route rule database that defines distribution route rules related to combinations of shippers and recipients, the traceability management method comprising: a step in which the role assigning node assigns a role to each of the assigned nodes based on the role database and connects each of the assigned nodes to at least one corresponding terminal outside the blockchain network system; a step in which the information from the terminals is input to the distribution route monitoring node via the assigned node to which a role has been assigned by the role assigning node; and a step in which the distribution route monitoring node monitors the distribution route of the object by determining whether or not a combination of a shipper and a recipient included in one or both of shipping information and receiving information among the input information satisfies the distribution route rule.[Supplementary Note 21] A traceability management method in which traceability is managed by a blockchain network system in which nodes are connected to each other on a network and are configured to have the nodes store identical information related to objects in a distributed manner, wherein the nodes include: a plurality of assigned nodes each assigned to a predetermined role; and a role assigning node configured to store a role database that defines a role corresponding to each of the assigned nodes, the traceability management method including the steps of: the role assigning node assigning a role to each of the assigned nodes based on the role database and connecting the assigned nodes to at least one corresponding terminal outside the blockchain network system; the assigned node to which a role related to an audit agency has been assigned by the role assigning node storing an evaluation criteria database that associates conditions and evaluations for a predetermined evaluation target; inputting the information from the terminal to the assigned node to which the role related to the audit agency has been assigned via a assigned node other than the assigned node to which the role related to the audit agency has been assigned; and the assigned node to which the role related to the audit agency has been assigned evaluating the evaluation target in the input information based on the evaluation criteria database. [Supplementary Note 22] A traceability management method in which traceability management is performed by a blockchain network system configured so that nodes are connected to each other on a network and the nodes are configured to store the same information related to an object in a distributed manner, wherein the nodes comprise: a plurality of assigned nodes each assigned to a predetermined role; and a role-assigning node configured to store a role database that defines the role corresponding to each of the assigned nodes, wherein the role-assigning node assigns a role to each of the assigned nodes based on the role database and connects the assigned nodes to at least one corresponding terminal outside the blockchain network system.

[0141] The disclosures of the above-cited patent documents are incorporated herein by reference and may be used as the basis or part of the present invention, as necessary. Modifications and adjustments of the embodiments and examples are possible within the scope of the entire disclosure of the present invention (including the claims and drawings), and further based on the basic technical concepts thereof. Furthermore, various combinations and selections (or non-selections, as necessary) of the various disclosed elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible within the scope of the entire disclosure of the present invention. In other words, the present invention naturally includes various modifications and alterations that would be possible by a person skilled in the art in accordance with the entire disclosure and technical concepts, including the claims and drawings. Furthermore, with regard to the numerical values ​​and numerical ranges described in this application, any intermediate values, lower values, and smaller ranges are deemed to be included, even if not explicitly stated. Furthermore, the disclosures of the above-cited documents, when used in part or in whole in combination with the disclosures herein as part of the disclosure of the present invention, are also deemed to be included in (belong to) the disclosures of this application, in accordance with the spirit of the present invention.

[0142] 1 Traceability management system 2 Blockchain network system 3 P2P network (network) 10a to 10n Responsible node (node) 11 Communication unit 12 Memory unit 13 Control unit 13a Certification processing unit 13b Recording processing unit 13c Viewing processing unit 13d Evaluation processing unit 14 Role label 15 Record information database 16 Evaluation criteria database 20 Role assignment node (node) 21 Communication unit 22 Memory unit 23 Control unit 23a Role assignment unit 23b Recording processing unit 24 Role database 25 Record information database 30 Distribution route monitoring node (node) 31 Communication unit 32 Memory unit 33 Control unit 33a Distribution route monitoring unit 33b Recording processing unit 34 Distribution route rule database 35 Record information database 40 Status change monitoring node (node) 41 Communication unit 42 Memory unit 43 Control unit 43a Status change monitoring unit 43b Recording processing unit 44 Status change rule database 45 Recording information database 50a to 50i Terminal 51 Communication unit 52 Storage unit 53 Input unit 54 Display unit 55 Control unit 60 Role management terminal (terminal) 70 Distribution route management terminal (terminal) 80 Status change management terminal (terminal) 90 Network 100 Hardware resource 101 Processor 102 Memory 103 Network interface 104 Internal bus

Claims

1. A blockchain network system configured such that nodes are connected to each other on a network and the nodes store the same information regarding an object in a distributed manner, The node: A plurality of nodes in charge of specific roles; A role assignment node configured to store a role database that defines a role corresponding to each of the assigned nodes and assign a role to each of the assigned nodes based on the role database and connect the assigned nodes to at least one corresponding terminal outside the blockchain network system; a status change monitoring node configured to store a status change rule database that defines a status change rule between the arrival and shipment of an object, receive the information from the terminal via the responsible node, and monitor a status change of the object by determining whether or not a status change based on corresponding arrival information and shipment information among the input information satisfies the status change rule; Equipped with Blockchain network system.

2. the status change monitoring node is configured to transmit, when the status change based on the arrival information and the shipping information does not satisfy the status change rule defined in the status change rule database, attention calling information for notifying the corresponding terminal that the status change is not normal and calling attention to the abnormality, The blockchain network system according to claim 1.

3. A blockchain network system configured such that nodes are connected to each other on a network and the nodes store the same information regarding an object in a distributed manner, The node: A plurality of nodes in charge of specific roles; A role assignment node configured to store a role database that defines a role corresponding to each of the assigned nodes and assign a role to each of the assigned nodes based on the role database and connect the assigned nodes to at least one corresponding terminal outside the blockchain network system; a distribution route monitoring node configured to store a distribution route rule database that defines distribution route rules related to combinations of shippers and receivers, receive the information from the terminal via the responsible node, and monitor the distribution route of the object by determining whether or not a combination of shippers and receivers included in one or both of the shipping information and the receiving information among the input information satisfies the distribution route rule; Equipped with Blockchain network system.

4. A blockchain network system configured such that nodes are connected to each other on a network and the nodes store the same information regarding an object in a distributed manner, The node: A plurality of nodes in charge of specific roles; A role assignment node configured to store a role database that defines a role corresponding to each of the assigned nodes and assign a role to each of the assigned nodes based on the role database and connect the assigned nodes to at least one corresponding terminal outside the blockchain network system; Equipped with at least one of the responsible nodes is assigned a role related to an auditing agency by the role assigning node, and stores an evaluation criteria database that associates conditions and evaluations for a specified evaluation target, and is configured so that the information from the terminal is input via a responsible node other than the responsible node that has been assigned the role related to the auditing agency, and the evaluation target in the input information is evaluated based on the evaluation criteria database. Blockchain network system.

5. A blockchain network system configured such that nodes are connected to each other on a network and the nodes store the same information regarding an object in a distributed manner, The node: A plurality of nodes in charge of specific roles; A role assignment node configured to store a role database that defines a role corresponding to each of the assigned nodes and assign a role to each of the assigned nodes based on the role database and connect the assigned nodes to at least one corresponding terminal outside the blockchain network system; A blockchain network system comprising:

6. A blockchain network system according to any one of claims 1 to 5; A role management terminal configured to be connected to the role assignment node; A plurality of terminals configured to be connected to the corresponding nodes to which roles have been assigned by the role management terminal; A traceability management system that includes:

7. A traceability management method in which a blockchain network system performs traceability management in which nodes are connected to each other on a network and the nodes are configured to distribute and hold the same information regarding an object, The node: A plurality of nodes in charge of specific roles; a role assignment node configured to store a role database in which a role corresponding to each of the assigned nodes is defined; a state change monitoring node configured to store a state change rule database that defines state change rules between the time of arrival and the time of shipment of an object; Equipped with The traceability management method includes: The role granting node grants a role to each of the responsible nodes based on the role database and connects them to at least one corresponding terminal outside the blockchain network system; inputting the information from the terminal to the status change monitoring node via the responsible node to which a role has been assigned by the role assigning node; a step of monitoring a state change of the object by the state change monitoring node judging whether or not a state change based on corresponding arrival information and shipping information among the input information satisfies the state change rule; A traceability management method, including:

8. A traceability management method in which a blockchain network system performs traceability management in which nodes are connected to each other on a network and the nodes are configured to distribute and hold the same information regarding an object, The node: A plurality of nodes in charge of specific roles; a role assignment node configured to store a role database in which a role corresponding to each of the assigned nodes is defined; A distribution route monitoring node configured to store a distribution route rule database that defines distribution route rules relating to combinations of shippers and recipients; Equipped with The traceability management method includes: The role granting node grants a role to each of the responsible nodes based on the role database and connects them to at least one corresponding terminal outside the blockchain network system; inputting the information from the terminal to the distribution route monitoring node via the responsible node to which a role has been assigned by the role assigning node; a step of monitoring the distribution route of the object by the distribution route monitoring node judging whether or not a combination of a shipper and a receiver included in one or both of the shipping information and the receiving information among the input information satisfies the distribution route rule; A traceability management method, including:

9. A traceability management method in which a blockchain network system performs traceability management in which nodes are connected to each other on a network and the nodes are configured to distribute and hold the same information regarding an object, The node: A plurality of nodes in charge of specific roles; a role assignment node configured to store a role database in which a role corresponding to each of the assigned nodes is defined; Equipped with The role granting node grants a role to each of the responsible nodes based on the role database and connects them to at least one corresponding terminal outside the blockchain network system; the responsible node to which the role of the audit authority has been assigned by the role assigning node stores an evaluation criteria database in which conditions and evaluations for a predetermined evaluation target are associated with each other; inputting the information from the terminal to the node in charge that has been assigned a role related to the auditing agency via a node in charge other than the node in charge that has been assigned a role related to the auditing agency; a step in which the responsible node, to which a role related to the auditing agency has been assigned, evaluates an evaluation target in the input information based on the evaluation criteria database; A traceability management method, including:

10. A traceability management method in which a blockchain network system performs traceability management in which nodes are connected to each other on a network and the nodes are configured to distribute and hold the same information regarding an object, The node: A plurality of nodes in charge of specific roles; a role assignment node configured to store a role database in which a role corresponding to each of the assigned nodes is defined; Equipped with The traceability management method includes: The role assignment node assigns a role to each of the responsible nodes based on the role database and connects them to at least one corresponding terminal outside the blockchain network system; Traceability management methods.