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

Technical Field

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

Background Art

[0002] There is a traceability management system that collects, manages, and makes traceable various information related to the production, processing, or distribution of an object. For example, there is a centralized traceability management system using a server (see, for example, Patent Documents 1-7). Also, there is a decentralized traceability management system that uses a blockchain network system to make it difficult to falsify or delete information, which has been an issue in centralized traceability management systems (see, for example, Patent Documents 8-9). Furthermore, there is a decentralized traceability management system that monitors data deficiencies and errors in various information collected from nodes by executing a predetermined smart contract in a blockchain network system (see, for example, Patent Documents 10-11).

Prior Art Documents

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

[0005] However, in the traceability management systems described in Patent Documents 10-11, even when there are no data deficiencies or errors in the collected information, it is difficult to objectively, neutrally, fairly, and impartially verify the inherent state of the data (evaluation, fraud, falsification, etc.). In other words, the inherent state of the data is prone to variability depending on the knowledge level of the person performing the verification, making objective, neutral, fair, and impartial verification difficult. Therefore, a system is desired that allows for objective, neutral, fair, and impartial, and easy verification of the inherent state of the data when tracking 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, fairly, impartially, and easily verifying the state inherent in data when tracking collected information. [Means for solving the problem]

[0007] The blockchain network system relating to the first perspective is a blockchain network system configured such that nodes are connected to each other on the network and the same information about an object is distributed and held among the nodes, wherein the nodes include a plurality of responsible nodes that are responsible for predetermined roles, a role assignment node that stores a role database defining a corresponding role for each of the responsible nodes and 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, and a state change monitoring node that stores a state change rule database defining state change rules between the arrival and departure of an object, and monitors the state change of the object by receiving the information from the terminal via the responsible nodes and determining whether the state change based on the corresponding arrival and departure information among the input information satisfies the state change rule.

[0008] The blockchain network system relating to the second perspective is a blockchain network system configured such that nodes are connected to each other on the network and the same information about an object is distributed and held among the nodes, wherein the nodes include a plurality of responsible nodes that are responsible for predetermined roles, a role assignment node that stores a role database defining a corresponding role for each of the responsible nodes and 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, and a distribution route monitoring node that stores a distribution route rule database defining distribution route rules regarding combinations of shipping sources and receiving destinations, and receives the information from the terminal via the responsible nodes and monitors the distribution route of the object by determining whether the combination of shipping sources and receiving destinations included in either or both of the shipping information and receiving information among the input information satisfies the distribution route rules.

[0009] The blockchain network system relating to the third perspective is a blockchain network system configured such that nodes are connected to each other on the network and the same information about an object is distributed and held among the nodes, wherein the nodes include a plurality of responsible nodes that are responsible for a predetermined role, and a role-assigning node that stores a role database defining a corresponding role for each of the responsible nodes, and is configured to assign a role to each of the responsible nodes based on the role database and connect to at least one corresponding terminal outside the blockchain network system, wherein at least one of the responsible nodes is assigned the role of an auditing body by the role-assigning node, stores an evaluation criteria database that associates conditions and evaluations for a predetermined evaluation target, and the information from the terminal is input via a responsible node other than the responsible node that has been assigned the role of an auditing body, and the evaluation target in the input information is evaluated based on the evaluation criteria database.

[0010] The blockchain network system relating to the fourth perspective is a blockchain network system configured such that nodes are connected to each other on the network and the same information about an object is distributed and held among the nodes, wherein the nodes include a plurality of responsible nodes that are responsible for a predetermined role, and a role-assigning node that stores a role database defining a corresponding role for each of the responsible nodes, and is configured to assign a role to each of the responsible nodes based on the role database and connect them to at least one corresponding terminal outside the blockchain network system.

[0011] The traceability management system relating to the fifth perspective comprises a blockchain network system relating to the first perspective, a role management terminal configured to connect to the role-assigning node, and a plurality of terminals configured to connect to the corresponding responsible node to which a role has been assigned by the role management terminal.

[0012] The sixth traceability management method is a traceability management method in which a blockchain network system configured to manage traceability is used, wherein nodes are connected to each other on the network and the same information about an object is distributed and held among the nodes, and the nodes are used to manage traceability, wherein the nodes include a plurality of responsible nodes that are responsible for predetermined roles, a role-assigning node configured to store a role database that defines a role corresponding to each of the responsible nodes, and a state change monitoring node configured to store a state change rule database that defines state change rules between the arrival and shipment of an object, and the traceability management method includes the steps of: the role-assigning node assigning a role to each of the responsible nodes based on the role database and connecting them to at least one corresponding terminal outside the blockchain network system; the input of the information from the terminal to the state change monitoring node via the responsible nodes to which the role has been assigned by the role-assigning node; and the monitoring node monitoring the state change of the object by determining whether the state change based on the corresponding arrival and shipment information among the input information satisfies the state change rules.

[0013] The seventh perspective on traceability management is a traceability management method in which a blockchain network system configured to manage traceability is used, wherein nodes are connected to each other on the network and the same information about an object is distributed and held among the nodes, and the nodes comprise a plurality of responsible nodes each responsible for a predetermined role, a role-assigning node configured to store a role database defining a role corresponding to each of the responsible nodes, and a distribution route monitoring node configured to store a distribution route rule database defining distribution route rules relating to combinations of shipping sources and receiving destinations, and the traceability management method comprises the steps of: the role-assigning node assigning a role to each of the responsible nodes based on the role database and connecting them to at least one corresponding terminal outside the blockchain network system; the role-assigning node inputting the information from the terminal to the distribution route monitoring node via the responsible nodes to which the roles have been assigned; and the distribution route monitoring node monitoring the distribution route of the object by determining whether the combination of shipping sources and receiving destinations included in either or both of the input information satisfies the distribution route rules.

[0014] The eighth traceability management method is a traceability management method in which a blockchain network system configured to manage traceability is used, wherein the nodes are connected to each other on the network and the same information about an object is distributed and held among the nodes, and the nodes comprise a plurality of responsible nodes that are responsible for a predetermined role, and a role-assigning node configured to store a role database that defines a role corresponding to each of the responsible nodes, the role-assigning 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, the responsible node that has been assigned the role of an auditing body by the role-assigning node stores an evaluation criteria database that associates conditions and evaluations for a predetermined evaluation target, and the information from the terminal is input to the responsible node that has been assigned the role of an auditing body via the responsible nodes other than the responsible node that has been assigned the role of an auditing body. The process includes the step of the assigned node, which has been assigned the role of the auditing body, evaluating the subject of evaluation in the input information based on the evaluation criteria database.

[0015] The traceability management method relating to the ninth perspective is a traceability management method in which a blockchain network system configured to manage traceability is used, wherein nodes are connected to each other on the network and the same information about an object is distributed and held among the nodes, and the nodes comprise a plurality of assigned nodes that are responsible for 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 traceability management method is such that 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] From a further perspective, separate programs for implementing, using a computer, the blockchain network system or traceability management method corresponding to each of the above perspectives are provided. These programs can also be integrated at least partially or wholly to be realized as one integrated program system. Each program can be realized on a computer at each respective terminal or node. Instructions and data necessary for implementation as a program can be recorded on a predetermined storage medium. The respective details thereof can be realized using known computer technologies, and in this document, the description thereof is omitted, but it is recognized that those skilled in the art can implement based on the description in this document and are regarded as being described as implementable by those skilled in the art. Note that the program can be recorded on a computer-readable storage medium. The storage medium can be a non-transient one such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, etc. Also, in this disclosure, it is also possible to embody it as a computer program product. The program is input into a computer device via an input device or from the outside via a communication interface, stored in a storage device, drives the processor according to predetermined steps or processes, and can display the processing result including intermediate states step by step via a display device as necessary, or can communicate with the outside via a communication interface. A computer device for that purpose typically includes, as an example, a processor, a storage device, an input device, a communication interface, and, as necessary, a display device that can be connected to each other by a bus.

Advantages of the Invention

[0017] According to the first to ninth perspectives, it can contribute to objectively, neutrally, fairly, and justly and easily confirming the state inherent in the data when tracking the collected information.

Brief Description of the Drawings

[0018] [Figure 1]This is a schematic block diagram showing the configuration of an example of a traceability management system according to Embodiment 1 before assigning roles. [Figure 2] This is a schematic block diagram showing the configuration of an example of a traceability management system according to Embodiment 1 after role assignment. [Figure 3] This block diagram schematically shows a configuration equivalent to that of Figure 2 after assigning roles to an example of a traceability management system according to Embodiment 1. [Figure 4] This is a schematic block diagram showing the configuration of a role assignment node in an example of a traceability management system according to Embodiment 1. [Figure 5] This is a schematic block diagram showing the configuration of the responsible nodes assigned to roles in the livestock industry, slaughterhouse, meat processing industry, wholesale industry, retail industry, or food service industry in an example of a traceability management system according to Embodiment 1, after role assignment. [Figure 6] This is a schematic block diagram showing the configuration of the assigned node for the auditing body in the configuration after role assignment, as an example of a traceability management system according to Embodiment 1. [Figure 7] This is a schematic block diagram showing the configuration of the responsible node to which the consumer role is assigned in the configuration after role assignment in an example of a traceability management system according to Embodiment 1. [Figure 8] This is a schematic block diagram showing the configuration of a distribution route monitoring node in an example of a traceability management system according to Embodiment 1. [Figure 9] This is a schematic block diagram showing the configuration of a state change monitoring node in an example of a traceability management system according to Embodiment 1. [Figure 10] This is a schematic block diagram showing the configuration of a terminal in an example of a traceability management system according to Embodiment 1. [Figure 11] This is a schematic diagram showing an example of a role database in an example of a traceability management system according to Embodiment 1. [Figure 12]This is a schematic diagram showing an example of the configuration of information transmitted from a predetermined terminal in an example of a traceability management system according to Embodiment 1. [Figure 13] This is a schematic diagram showing an example of an evaluation criteria database in an example of a traceability management system according to Embodiment 1. [Figure 14] This is a schematic diagram showing an example of evaluation information in an example of a traceability management system according to Embodiment 1. [Figure 15] This 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. [Figure 16] This is a schematic diagram showing an example of a state change rule database in an example of a traceability management system according to Embodiment 1. [Figure 17] This is a schematic sequence chart illustrating the operation of an example of a traceability management system according to Embodiment 1 when assigning roles. [Figure 18] This is a schematic sequence chart illustrating an example of the operation of a traceability management system according to Embodiment 1 when recording information related to the livestock industry. [Figure 19] This is a sequence chart schematically showing the operation of the traceability management system according to Embodiment 1 during evaluation. [Figure 20] This is a schematic sequence chart illustrating an example of the operation of a traceability management system according to Embodiment 1 when there is a direct transaction between a livestock farmer and a food service provider. [Figure 21] This is a schematic sequence chart illustrating an example of the operation when there is a discrepancy between incoming and outgoing goods at a processing company in an example of a traceability management system according to Embodiment 1. [Figure 22] This is a schematic block diagram showing the configuration of a modified example of the traceability management system according to Embodiment 1 after assigning roles to the different components. [Figure 23] This is a schematic block diagram showing the configuration of the traceability management system according to Embodiment 2 after the role has been assigned. [Figure 24] This is a schematic block diagram showing the configuration of the traceability management system according to Embodiment 3 after the role has been assigned. [Figure 25] This is a schematic block diagram showing the configuration of the traceability management system according to Embodiment 4 after the roles have been assigned. [Figure 26] This is a schematic block diagram showing the configuration of the traceability management system according to Embodiment 5 after the roles have been assigned. [Figure 27] This is a block diagram that schematically shows the configuration of hardware resources. [Modes for carrying out the invention]

[0019] Embodiments will be described below with reference to the drawings. Reference numerals used in the drawings in this application are solely for the purpose of aiding understanding and are not intended to limit the invention to the illustrated configuration. Furthermore, the embodiments described below are merely illustrative and do not limit the present invention. In addition, the connecting lines between blocks in the drawings and other diagrams referenced in the following description include both bidirectional and unidirectional lines. Unidirectional arrows schematically represent the flow of the main signal (data) and do not exclude bidirectionality. Furthermore, in the circuit diagrams, block diagrams, internal configuration diagrams, connection diagrams, etc., shown in this disclosure, although not explicitly shown, input ports and output ports exist at the input and output ends of each connecting line. The same applies to input / output interfaces. The program is executed via a computer device, which includes, for example, a processor, storage device, input device, communication interface, and, if necessary, a display device. The computer device is configured to communicate with internal or external equipment (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 drawings. Figure 1 is a schematic block diagram showing the configuration of an example of a traceability management system according to Embodiment 1 before assigning roles. Figure 2 is a schematic block diagram showing the configuration of an example of a traceability management system according to Embodiment 1 after assigning roles. Figure 3 is a schematic block diagram showing a configuration equivalent to the configuration in Figure 2 after assigning roles to an example of a traceability management system according to Embodiment 1.

[0021] The traceability management system 1 is a system that collects, manages, and makes traceable various information related to the production, processing, or distribution of an object (see Figure 1). Here, the object may be something that changes during the production, processing, or distribution process, for example, something that changes when parts are assembled, such as equipment, or something that changes when it is broken down into its parts, such as meat processing and cutting of livestock meat. In Embodiment 1, livestock meat will be used as an example of the object to be explained. The traceability management system 1 is configured to use a blockchain network system 2 to store (distributedly store) the same information as the various information collected about the object in each of the multiple responsible nodes 10a to 10i, role assignment node 20, distribution route monitoring node 30, and state change monitoring node 40. The traceability management system 1 is configured to use smart contracts to automatically monitor for data deficiencies and errors in the various information collected from predetermined responsible nodes 10a, 10c to 10h. The traceability management system 1 is configured to automatically monitor (verify) the state (evaluation, fraud, falsification, etc.) inherent in the data of various information collected from designated responsible nodes 10a, 10c-10h using smart contracts.

[0022] Here, the traceability management system 1 can be used for traceability management of production history (breeding process, cultivation process, harvesting process, etc.), processing history, and distribution history of livestock products (e.g., beef, pork, chicken, etc.), agricultural products (e.g., cotton, coffee, cocoa, etc.), fish and shellfish, farmed products, raw materials, mining products, gemstones, industrial products, etc. Furthermore, the traceability management system 1 can be used to verify compliance (industry standards, laws, regulations, ethics, de facto standards, etc.), fair trade practices, and whether there is any substitution. Additionally, the traceability management system 1 can be used to evaluate data based on evaluation criteria such as GGAP (Global Good Agricultural Practice), JGAP (Japanese Good Agricultural Practice), and Agricultural / Livestock HACCP (Hazard Analysis Critical Control Point). Furthermore, the traceability management system 1 can be used to evaluate elements that consumers are likely to favor (e.g., pesticide-free cultivation, organic farming, origin, compliance with animal welfare), and to verify elements that consumers are likely to dislike (e.g., poaching, theft, smuggling, conflict minerals, child labor, forced labor, animal welfare violations).

[0023] The traceability management system 1 has a function to assign role labels to the responsible nodes 10a to 10i and set the corresponding terminals 50a to 50i using the role assignment node 20 (see Figures 1 and 2). The traceability management system 1 can set the responsible nodes 10a to 10i from a state where no role labels are assigned to them (see Figure 1) to a state where role labels are assigned to them (see Figure 2), and it may also change the role labels assigned to the responsible nodes 10a to 10i. The configuration of the traceability management system 1 in Figure 2 is equivalent to the configuration in Figure 3, where the responsible nodes 10a to 10i with assigned role labels, the role assignment node 20, the distribution route monitoring node 30, and the status change monitoring node 40 are each connected to terminals 50a to 50i with corresponding roles, a role management terminal 60, a distribution route management terminal 70, and a status change management terminal 80. In the traceability management system 1, when a role label is assigned, communication is possible between the corresponding responsible nodes 10a-10i and terminals 50a-50i via the network 90. ​​In the traceability management system 1, communication is possible between the corresponding role assignment node 20, distribution route monitoring node 30, and 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 assignment node 20, distribution route monitoring node 30, and status change monitoring node 40 are nodes that have the roles of role assignment, distribution route monitoring, and status change monitoring pre-configured.

[0024] Blockchain Network System 2 is a blockchain-based network system in which nodes 10a-10i, 20, 30, and 40 are connected to each other on a P2P network 3, and the same information about the target object is distributed and held (redundantly held) on all or any of the nodes 10a-10i, 20, 30, and 40 (see Figures 1-3). Blockchain Network System 2 comprises the assigned nodes 10a-10i, the role-assigning node 20, the distribution route monitoring node 30, the state change monitoring node 40, and the P2P (Peer to Peer) network 3.

[0025] Nodes 10a-10i, 20, 30, and 40 are nodes (computers; servers are also acceptable) that perform predetermined operations and storage functions (see Figures 1-3). Each of nodes 10a-10i, 20, 30, and 40 (or any one of them) stores the collected information. Nodes 10a-10i, 20, 30, and 40 may be physical machines or virtual machines. Each of nodes 10a-10i, 20, 30, and 40 has its own unique identification information. Details of nodes 10a-10i, 20, 30, and 40 will be described later.

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

[0027] Next, the nodes and terminals in the traceability management system according to Embodiment 1 will be described with reference to the drawings. Figure 4 is a schematic block diagram showing the configuration of a role-assigned node in an example of the traceability management system according to Embodiment 1. Figure 5 is a schematic block diagram showing the configuration of a node assigned the roles of livestock farming, slaughtering, meat processing, wholesale, retail, or food service in an example of the traceability management system according to Embodiment 1 after role assignment. Figure 6 is a schematic block diagram showing the configuration of a node assigned the role of an auditing body in an example of the traceability management system according to Embodiment 1 after role assignment. Figure 7 is a schematic block diagram showing the configuration of a node assigned the role of a consumer in an example of the traceability management system according to Embodiment 1 after role assignment. Figure 8 is a schematic block diagram showing the configuration of a distribution route monitoring node in an example of the traceability management system according to Embodiment 1. Figure 9 is a schematic block diagram showing the configuration of a state change monitoring node in an example of the traceability management system according to Embodiment 1. Figure 10 is a schematic block diagram showing the configuration of a terminal in an example of the traceability management system according to Embodiment 1. Figure 11 is a schematic diagram showing an example of a role database in an example of a traceability management system according to Embodiment 1. Figure 12 is a schematic diagram showing an example of the configuration of information transmitted from a predetermined terminal in an example of a traceability management system according to Embodiment 1. Figure 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. Figure 14 is a schematic diagram showing an example of evaluation information in an example of a traceability management system according to Embodiment 1. Figure 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. Figure 16 is a schematic diagram showing an example of a state change rule database in an example of a traceability management system according to Embodiment 1.

[0028] Referring to Figure 4, the role-assigning node 20 is a node that assigns roles (role labels 14 in Figures 5 to 7) to the assigned nodes (10a to 10i in Figures 1 to 3) in the blockchain network system (Figures 1 to 3, part 2). By assigning roles, the role-assigning node 20 connects each of the assigned nodes 10a to 10i to at least one terminal 50a to 50i. In Figure 3, the role-assigning node 20 exclusively connects one terminal to one assigned node, but it is also possible to connect one terminal to multiple assigned nodes in a multifaceted manner. For example, in a large food manufacturer, one company may be engaged in livestock farming, slaughtering, meat processing, and other businesses, and due to the hardware configuration, one terminal may be used as a livestock terminal, slaughtering terminal, meat processing terminal, and processing terminal. In such cases, one terminal may be connected to multiple assigned nodes. The role labels are labels that indicate the roles of the assigned nodes 10a to 10i. Role labels may use strings, numbers, codes, etc., that represent the role. Role labels enable nodes (10b in Figure 6; role is auditing body) to evaluate objects according to their role (roles other than auditing body), distribution route monitoring nodes (30 in Figure 8) to monitor the distribution routes of objects, and state change monitoring nodes (40 in Figure 9) to monitor state changes of objects according to their role. The role assignment node 20 comprises a communication unit 21, a storage unit 22, and a control unit 23.

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

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

[0031] The control unit 23 is a functional unit that controls the communication unit 21 and the storage unit 22 (see Figure 4). The control unit 23 performs predetermined processing and executes a program to realize the role assignment unit 23a and the recording processing unit 23b. The role assignment unit 23a is a processing unit that assigns a role label to each responsible node 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 to the control unit (13 in Figures 5 to 7) of the responsible nodes 10a to 10i: certification processing unit (13a in Figure 5), recording processing unit (13b in Figures 5 to 7), browsing processing unit (13c in Figures 5 and 7), or evaluation processing unit (13d in Figure 6). When the role assignment unit 23a assigns the roles of livestock farming, slaughtering, meat processing, wholesale, retail, and food service to the assigned nodes 10a, 10c-10h, it sets the control units 13 of the assigned nodes 10a, 10c-10h to include the certification processing unit 13a, the recording processing unit 13b, and the viewing processing unit 13c (see Figure 5). When the role assignment unit 23a assigns the role of auditing body to assigned node 10b, it sets the control unit 13 of assigned node 10b to include the recording processing unit 13b and the evaluation processing unit 13d (see Figure 6). When the role assignment unit 23a assigns the role of consumer to assigned node 10i, it sets the control unit 13 of assigned node 10i to include the recording processing unit 13b and the viewing processing unit 13c (see Figure 7). The recording processing unit 23b is a processing unit that associates various information from assigned nodes 10a-10h, the distribution route monitoring node 30, and the status change monitoring node 40 and records it in the recording information database 25.

[0032] Referring to Figure 5, the assigned nodes 10a, 10c-10h are nodes that are responsible for a predetermined role (in this case, livestock farming / slaughtering / meat processing / wholesale / retail / restaurants). The assigned nodes 10a, 10c-10h are assigned a role (role label 14) by the role-assigning node (20 in Figures 1-3) and are connected to the corresponding terminals 50a, 50c-50h. The assigned nodes 10a, 10c-10h operate and store information according to the assigned role. The assigned nodes 10a, 10c-10h include a communication unit 11, a storage unit 12, and a control unit 13.

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

[0034] The memory unit 12 is a functional unit that stores various information and programs (see Figure 5). The memory unit 12 stores role labels 14 and a record information database (record information DB) 15. Role labels 14 are assigned by the role assignment node 20 based on the role database (24 in Figure 4), and in this case, they are role labels related to livestock farming / slaughtering / meat processing / wholesale / retail / food service. The record information database 15 is a database that records various information from the assigned nodes 10a to 10h, the distribution route monitoring node 30, and the status change monitoring node 40 in association with each other. The contents of the record information database 15 are the same as those of other record information databases (25 in Figure 4, 15 in Figure 6, 15 in Figure 7, 35 in Figure 8, and 45 in Figure 9).

[0035] The control unit 13 is a functional unit that controls the communication unit 11 and the storage unit 12 (see Figure 5). The control unit 13 performs predetermined processing. The control unit 13 is configured with an authentication processing unit 13a, a recording processing unit 13b, and a browsing processing unit 13c, according to the role of the role label 14 (here, livestock farming / slaughtering / meat processing / processing / wholesale / retail / food service) assigned by the role assignment node 20. The authentication processing unit 13a is a processing unit that checks for any missing or incorrect data in the information acquired from a terminal (one of 50a, 50c-50h in Figures 2 and 3) corresponding to the role label assigned to its own node (one of 10a, 10c-10h), and performs authentication if there are no missing or incorrect data, and is a processing unit that executes contracts. The authentication processing unit 13a records the authenticated information in association with the corresponding information in the recording information database 15 of its own node (one of 10a, 10c-10h). The certification processing unit 13a transmits the certified information to nodes other than its own node (any of 10a to 10i), the role assignment node 20, the distribution route monitoring node 30, and the status change monitoring node 40. The certification processing unit 13a may also limit the destinations to which the certified information is transmitted. If there is any missing or incorrect data in the acquired information, the certification processing unit 13a transmits a warning message to the terminal corresponding to the role label assigned to its own node (any of 50a, 50c to 50h in Figures 2 and 3) to inform them of the situation and draw their attention to it. The recording processing unit 13b is a processing unit that associates various information from nodes 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 it in the recording information database 15. The browsing processing unit 13c is a processing unit that, in response to a browsing request from a terminal (one of 50a, 50c, to 50h in Figures 2 and 3) corresponding to a role label assigned to its own node (one of 10a, 10c to 10h), reads the corresponding information and transmits it to the corresponding terminal. The browsing processing unit 13c may also 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~10h can be, for example, metadata that associates message ID, timestamp, type, movement, individual ID, quantity data, and additional data, as shown in Figure 12. The message ID is the unique identification information of the information (message), and can be a number or a character. The timestamp is the date and time of information transmission (or information creation). The type is the type of information, and one of the following types is selected, for example, birth, arrival, rearing, feeding, weight, treatment, medication, shipment, etc. Movement is data that identifies the source and destination of the object or its information, and can be the identification information of the source (terminal) and the identification information of the destination (terminal). Individual ID is the unique identification information of the object (for example, livestock), and can be a number or a character. Quantity data is the quantity of the object, and can be, for example, number of items, weight, volume, size, time, number of times, etc. Additional data is data related to the above items, and may include, for example, the breed of the individual, the means of transportation, the type of feed, the name of the medication administered, etc. If there is no additional data to add, it may be omitted.

[0037] Referring to Figure 6, the responsible node 10b is a node that operates and stores information according to the role label 14 (in this case, auditing body) assigned by the role-assigning node (20 in Figures 1 to 3). The responsible node 10b comprises a communication unit 11, a storage unit 12, and a control unit 13.

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

[0039] The memory unit 12 is a functional unit that stores various information and programs (see Figure 6). The memory unit 12 stores role labels 14, a record information database (record information DB) 15, and an evaluation criteria database (evaluation criteria DB) 16. Role labels 14 are assigned by the role assignment node 20 based on the role database (24 in Figure 4), and in this case, they are role labels related to auditing organizations. 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 contents of the record information database 15 are the same as those of other record information databases (25 in Figure 4, 15 in Figure 5, 15 in Figure 7, 35 in Figure 8, and 45 in Figure 9). The evaluation criteria database 16 is a database that associates conditions (e.g., multiple numerical ranges) and evaluations (e.g., excellent, good, fair, poor) for a predetermined evaluation target (e.g., weight change of adult cows) (see Figure 13). The evaluation criteria database 16 is not limited to the evaluation criteria shown in Figure 13, but may also include, for example, evaluation criteria that evaluate based on whether or not a single condition is met, or evaluation criteria that evaluate based on points for each condition. Furthermore, the evaluation criteria database 16 may be stored not only on the responsible node 10b (role: auditing body), but also on other nodes 10a, 10c~10i, 20, 30, 40, or on another blockchain network system (not shown) to further enhance security and fairness, and may be stored on the blockchain network system 2 as a separate blockchain from the record information databases 15, 25, 35, 45 (traceability information).

[0040] The control unit 13 is a functional unit that controls the communication unit 11 and the storage unit 12 (see Figure 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 assigned role label 14 (in this case, auditing body) by the role assignment 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 it in the recording information database 15. The evaluation processing unit 13d is a processing unit that, when it detects the reception of predetermined information (or at regular intervals), evaluates the detected information based on the evaluation criteria database 16 and executes a 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 the corresponding information in the recording information database 15 of its own assigned node 10b. The evaluation processing unit 13d transmits evaluation information to the assigned nodes 10a, 10c-10i (nodes other than its own), 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 evaluation processing at the assigned node 10b, it may also transmit the received predetermined information to the auditing organization terminal 50b so that the user of the auditing organization terminal 50b (an employee of the auditing organization) can perform the evaluation processing. Before the livestock farmer terminal 50a transmits formal information to the assigned node 10a (role: livestock farming), the evaluation processing unit 13d may, upon receiving an evaluation request (including information to be evaluated) from the livestock farmer terminal 50a, perform an evaluation of 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 metadata that associates the message ID, timestamp, evaluation, the message ID of the message being evaluated, and the evaluation criterion name, for example, as shown in Figure 14. The message ID is the unique identifier of the information (message), and can be a number, a character, or a hash value of the whole or part of the message being evaluated (for example, the message ID and timestamp). The timestamp is the date and time of information transmission (or information creation). The evaluation is performed by the evaluation processing unit 13d. The message ID of the message being evaluated 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] Referring to Figure 7, the responsible node 10i is a node that operates and stores information according to the role of the role label 14 (in this case, consumer) assigned by the role-assigning node (20 in Figures 1 to 3). The responsible node 10i comprises a communication unit 11, a storage unit 12, and a control unit 13.

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

[0044] The memory unit 12 is a functional unit that stores various information and programs (see Figure 7). The memory unit 12 stores role labels 14 and a record information database (record information DB) 15. Role labels 14 are assigned by the role assignment node 20 based on the role database (24 in Figure 4), and in this case, they are role labels related to consumers. 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 contents of the record information database 15 are the same as those of the other record information databases (25 in Figure 4, 15 in Figure 5, 15 in Figure 6, 35 in Figure 8, and 45 in Figure 9).

[0045] The control unit 13 is a functional unit that controls the communication unit 11 and the storage unit 12 (see Figure 7). The control unit 13 performs predetermined processing. The control unit 13 is configured with a recording processing unit 13b and a browsing processing unit 13c according to the role of the role label 14 (in this case, consumer) assigned by the role assignment 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 it in the recording information database 15. The browsing processing unit 13c is a processing unit that reads the corresponding information in response to a browsing request from a consumer terminal (50i in Figures 2 and 3) corresponding to the role label assigned to its assigned node 10i, and sends (replies to) the consumer terminal 50i.

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

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

[0048] The memory unit 32 is a functional unit that stores various information and programs (see Figure 8). The memory unit 32 stores the distribution route rule database (distribution route rule DB) 34 and the record information database (record information DB) 35. The distribution route rule database 34 is a database that defines distribution route rules related to the combination of the source of shipment (identification information of the source of movement) and the destination of shipment (identification information of the destination of movement) in the distribution route (see Figure 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 to 10i, 20, 40 and another blockchain network system (not shown) to further enhance security and fairness, and may be stored on the blockchain network system 2 as a blockchain separate from the record information databases 15, 25, 35, 45 (traceability information). The record information database 35 is a database that records various information from the responsible nodes 10a to 10h, the distribution route monitoring node 30 and the state change monitoring node 40 in association with each other. The record information database 35 shares the same content as the other record information databases (Figure 4-25, Figures 5-7-15, Figure 9-45).

[0049] Here, the distribution route rule database 34 defines the normal relationship between a shipper and a recipient in the distribution route, but combinations of shippers and recipients that are not defined may be considered abnormal or prohibited. Furthermore, even if the combination of shipper and recipient is normal, it may be considered abnormal if the quantities in the corresponding shipment information and arrival information do not match. Also, even if the combination of shipper and recipient is normal and the quantity data in the corresponding shipment information and arrival information match and are normal, it may be considered abnormal if the quantity traded exceeds a predetermined amount (for example, an unnatural transaction such as an unusually large amount of meat being directly traded between a meat retailer and a consumer, or a transaction that violates industry rules). Furthermore, even if the combination of shipper and recipient is normal, it may be considered abnormal if the time from shipment to arrival exceeds a predetermined time (for example, if the difference between the shipment date and time and the arrival date and time is too large and the transaction is unnatural). Also, even if the combination of shipper and recipient is normal, it may be considered abnormal if the corresponding arrival information is not received within a predetermined time after receiving the shipment information. Furthermore, while the distribution route rule database 34 in Figure 15 defines the relationship between suppliers and recipients in different industries, for example, a livestock farmer specializing in raising piglets may receive piglets and ship adult pigs. Therefore, the distribution route rule database 34 could also define the relationship between suppliers and recipients within the same industry.

[0050] The control unit 33 is a functional unit that controls the communication unit 31 and the storage unit 32 (see Figure 8). The control unit 33 performs predetermined processing and executes a program to realize the distribution route monitoring unit 33a and the recording processing unit 33b. The distribution route monitoring unit 33a is a processing unit that monitors the distribution route of the target object based on shipping information (information of type that is shipping) and receiving information (information of type that 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 terminals 50a, 50c to 50h via the corresponding responsible nodes 10a, 10c to 10h (or at regular intervals), it checks whether the combination of the shipping source and receiving destination included in the shipping information (or receiving information) satisfies the conditions (distribution route rules) defined in the distribution route rule database 34, and if the conditions are not met, it creates warning information and transmits it to each terminal (50a, 50c to 50h) related to the shipping source and receiving destination. Furthermore, the warning information may be transmitted not only to the terminals related to the shipping source and receiving destination, but also to other terminals. Here, the warning information is information that alerts the shipping source and receiving destination to the fact that the distribution route is not normal. The distribution route monitoring unit 33a may record information indicating that the distribution route rules are met in association with the shipping information and / or receiving information if the shipping source and / or receiving destination identified in the shipping information and / or receiving information meet the conditions defined in the distribution route rule database 34, and record it in each node 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 it in the recording information database 25.

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

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

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

[0054] Here, regarding the state change rule database 44, for example, if the role is livestock farming, the number of incoming piglets may decrease due to illness, death, etc. during the growth process, so the state change rule database 44 can be set so that the number of incoming piglets is greater than or equal to the number of adult pigs shipped (see Figure 16). Also, for example, if the role is meat processing, since bones are removed from the carcasses of slaughtered livestock to produce meat, the state change rule database 44 can be set so that the loss rate is higher.

[0055] The control unit 43 is a functional unit that controls the communication unit 41 and the storage unit 42 (see Figure 9). The control unit 43 performs predetermined processing and executes a program to realize the state change monitoring unit 43a and the recording processing unit 43b. The state change monitoring unit 43a is a processing unit that monitors the state changes of an object based on shipping information (information of type that is shipping), receiving information (information of type that is receiving), and the state change rule database 44, and is a processing unit that executes contracts. When the state change monitoring unit 43a detects the reception of shipping information from any of the assigned nodes 10a, 10c to 10h (or at regular intervals), it reads the receiving information from the same node immediately preceding the shipping information from the recording information database 45, determines whether the state changes based on the quantities (e.g., number of heads, weight, etc.) of the shipping information and receiving information satisfy the conditions (state change rules) defined in the state change rule database 44, and if the conditions are not satisfied, it creates warning information and transmits it to the terminal related to the shipping source in the shipping information (any of 50a, 50c to 50h). Furthermore, the warning information may be sent not only to the terminal related to the shipping source but also to other terminals. The status change monitoring unit 43a may record the certification information indicating that the status change rule is met in association with the shipping information when the quantities of the shipping information and receiving information satisfy the status change rule database 44, and record it in each node 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 it in the recording information database 25.

[0056] Referring to Figure 10, terminals 50a-50i, 60, 70, and 80 are terminals used by parties involved with the subject matter. Each terminal 50a-50i, 60, 70, and 80 has its own unique identification information. Terminal 50a is a livestock farmer terminal used by livestock farmers and other livestock businesses (see Figures 1-3). Terminal 50b is an auditing agency terminal used by auditing organizations such as animal welfare associations. Terminal 50c is a slaughterhouse terminal used by slaughterhouse operators. Terminal 50d is a meat processor terminal used by meat processors. Terminal 50e is a food processor terminal used by food processors. Terminal 50f is a wholesaler terminal used by wholesalers. Terminal 50g is a retailer terminal used by retailers. Terminal 50h is a food service operator terminal used by food service businesses. Terminal 50i is a consumer terminal used by consumers. Furthermore, consumers may include not only the end consumers of the object, but also investors and banks that invest in or finance businesses related to the object. Also, terminals 50a to 50i in Figures 1 to 3 are examples, and the names and number of terminals may change depending on the businesses, departments, and number of processes involved in the distribution process. Terminal 60 is a role management terminal used by an administrator with specific privileges 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 privileges regarding the distribution route monitoring node 30 in the blockchain network system 2. Terminal 80 is a state change management terminal used by an administrator with specific privileges regarding the state change monitoring node 40 in the blockchain network system 2.

[0057] Terminals 50a-50i, 60, 70, and 80 are equipped with a communication unit 51, a storage unit 52, an input unit 53, a display unit 54, and a control unit 55 (see Figure 10). The communication unit 51 is a functional unit that communicates with the blockchain network system 2 via the network (90 in Figures 1 and 2). The storage unit 52 is a functional unit that stores various information and programs. The input unit 53 is a functional unit that inputs information, and can 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, storage unit 52, input unit 53, and display unit 54, and performs predetermined information processing by executing a program.

[0058] Network 90 is a wired or wireless communication network that enables communication between the blockchain network system 2 and terminals 50a-50i, 60, 70, and 80 (see Figures 1-3). Network 90 can utilize, for example, a PAN (Personal Area Network), LAN (Local Area Network), MAN (Metropolitan Area Network), WAN (Wide Area Network), or GAN (Global Area Network).

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

[0060] First, the operation of the traceability management system according to Embodiment 1 when assigning roles will be explained using drawings. Figure 17 is a schematic sequence chart showing the operation of an example of the traceability management system according to Embodiment 1 when assigning roles. For the configuration of the traceability management system, please refer to Figures 1 to 3.

[0061] First, the role management terminal 60 creates a role database (corresponding to 24 in Figure 4, see Figure 11) through user operation (step A1). When creating the role database, a processing unit setting program is also created to set processing units (one of the following: certification processing unit (13a in Figure 5), recording processing unit (13b in Figures 5 to 7), browsing processing unit (13c in Figures 5 and 7), or evaluation processing unit (13d in Figure 6)) to be assigned to the responsible nodes 10a to 10i according to the role of the role label in the role database.

[0062] Next, the role management terminal 60 sends the created role database to the role assignment node 20 (step A2). When sending the role database, the processing unit configuration program is also sent.

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

[0064] Next, the role assignment node 20 stores the received role database (see Figure 4, 24 and Figure 11) (step A4). At this time, the processing unit setting program is also stored when the role database is stored.

[0065] Next, the role-assigning node 20 sends the corresponding role label to each of the assigned nodes 10a to 10i based on the stored role database 24 (step A5). When sending the role label, the processing unit setting program corresponding to the role label is also sent.

[0066] Next, each of the assigned nodes 10a to 10i receives its corresponding role label (step A6). At this point, when receiving the role label, it also receives the processing unit configuration program.

[0067] Finally, each of the assigned nodes 10a to 10i stores the received role label (step A7), and then terminates. At this point, when storing the role label, the processing unit setting program is executed to set the processing unit corresponding to the role of the role label in each of the assigned nodes 10a to 10i.

[0068] Adding, deleting, or changing the roles of nodes can be done by the role management terminal 60 modifying the contents of the role database 24 stored in the role-assigning node 20, or by updating it with a new role database 24. In conjunction with this, the processing unit corresponding to the role of the role label can be configured.

[0069] Next, the operation of the traceability management system according to Embodiment 1 during information registration will be explained using drawings. Figure 18 is a schematic sequence chart showing an example of the operation of a traceability management system according to Embodiment 1 when recording information related to the livestock industry. For the configuration of the traceability management system, please refer to Figures 1 to 3. Here, the operation when recording information related to the livestock industry after role assignment will be explained as an example.

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

[0071] Next, the livestock farmer terminal 50a generates information (corresponding to the information in Figure 12) through user operation (step B2). Here, the information may include, for example, birth information, arrival information, rearing information, treatment information, medication information, and shipping information (information of which type is birth, arrival, rearing, treatment, medication, and shipping).

[0072] Next, the livestock farmer terminal 50a sends the created information to the responsible node 10a (role: livestock farming) (step B3).

[0073] Next, the responsible node 10a (role: livestock farming) receives information from the livestock farmer terminal 50a (step B4).

[0074] Next, the responsible node 10a (role: livestock farming) checks whether there are any missing or incorrect data in the received information, and if there are no missing or incorrect data, it performs the certification process (step B5). If there are missing or incorrect data in the received information, the responsible node 10a (role: livestock farming) may send a warning message to the livestock farmer terminal 50a to inform them of the situation and then terminate the process.

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

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

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

[0078] Finally, the assigned nodes 10b-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 their respective node 10b-10i, 20, 30, and 40's record information databases (Figures 5-7, 15; Figure 4, 25; Figure 8, 35; Figure 9, 45) (Step B9), and then terminate.

[0079] Furthermore, steps B1 to B9 can also be applied to the recording of information regarding slaughtering, meat processing, wholesale, retail, and food service industries after role assignment.

[0080] Next, the operation of the traceability management system according to Embodiment 1 during evaluation will be explained using drawings. Figure 19 is a schematic sequence chart showing the operation of the traceability management system according to Embodiment 1 during evaluation. For the configuration of the traceability management system, please refer to Figures 1 to 3.

[0081] First, the responsible node 10b (role: auditing body) detects the receipt of predetermined information (corresponding to the receipt in step B8 of Figure 18) (step C1). Here, the predetermined information is information (see Figure 12) whose type of content corresponds to the evaluation target (e.g., feeding, treatment, medication, etc.) of the evaluation criteria database (16 in Figure 6). Alternatively, the predetermined information may also be information whose destination is the auditing body terminal (50b in Figures 1-3) or the identification information of the responsible node 10b (role: auditing body).

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

[0083] Next, the responsible node 10b (role: auditing body) creates evaluation information (see Figure 14) based on the evaluation of the detected information, and records the created evaluation information in relation to the corresponding information in its own responsible node 10b's (role: auditing body) record information database (15 in Figure 6) (step C3).

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

[0085] Next, nodes 10a, 10c-10i, 20, 30, and 40 each receive evaluation information from their assigned node 10b (role: auditing body) (step C5).

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

[0087] Steps C1 to C6 were explained using an 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 Embodiment 1 during distribution route monitoring will be explained using diagrams. Figure 20 is a schematic sequence chart showing an example of the operation of an example of the traceability management system according to Embodiment 1 when there is a direct transaction between a livestock farmer and a food service provider. For the configuration of the traceability management system, please refer to Figures 1 to 3. Here, we will explain using the operation when there is a direct transaction between a livestock farmer and a food service provider as an example.

[0089] First, the distribution route monitoring node 30 detects the receipt of shipping information (corresponding to the reception in step B8 of Figure 18) (step D1). Note that here only the receipt of shipping information is detected, but it may also be configured to detect only the receipt of the corresponding incoming information immediately afterward, or to detect the receipt of both shipping and incoming information.

[0090] Next, the distribution route monitoring node 30 determines whether the source of shipment (in this case, the livestock farmer terminal 50a) and the destination (in this case, the food service provider terminal 50h) in the detected shipment information meet the conditions defined in the distribution route rule database (see Figure 8, 34 and Figure 15) (step D2). If the conditions are met (YES in step D2), the process terminates.

[0091] Furthermore, if the above conditions are met (YES in step D2), certification information confirming that the detected shipment information is part of a normal distribution route may be associated with and recorded. Also, in step D2, even if the source and destination meet the conditions defined in the distribution route rule database, if the quantities of the corresponding shipment and arrival information do not match, the process may proceed to step D3. Also, in step D2, even if the source and destination meet the conditions defined in the distribution route rule database and the quantities of the corresponding shipment and arrival information match, if the quantity traded exceeds a predetermined amount (the transaction volume is abnormal), the process may proceed to step D3. Also, in step D2, even if the source and destination meet the conditions defined in the distribution route rule database, if the time from shipment to arrival exceeds a predetermined time (the transaction time is abnormal), 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 a warning information to alert the user that the distribution route is not functioning correctly (step D3). When creating the warning information, the warning information may also be associated with and recorded in relation to the detected shipping information.

[0093] Next, the distribution route monitoring node 30 transmits the created warning information to the source (livestock farmer terminal 50a) and destination (restaurant operator terminal 50h) in the detected shipment information (step D4). Note that the warning information may be transmitted not only to the terminals related to the source and destination, but also to other terminals.

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

[0095] Furthermore, after step D4, and in parallel with steps D5 and D6, the food service provider 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] Steps D1 to D8 may also be applied to combinations other than those between livestock farmers and food service businesses.

[0097] Next, the operation of the traceability management system according to Embodiment 1 during state change monitoring will be explained using drawings. Figure 21 is a schematic sequence chart showing an example of the operation when there is a discrepancy between incoming and outgoing goods at a processing company in an example of the traceability management system according to Embodiment 1. For the configuration of the traceability management system, please refer to Figures 1 to 3. Here, we will explain using the operation when there is a discrepancy between incoming and outgoing goods at a processing company as an example.

[0098] First, the state change monitoring node 40 detects the receipt of shipping information (corresponding to the reception in step B8 of Figure 18) (step E1). Note that although step E1 detects the receipt of shipping information, instead, it may be possible to detect the receipt of incoming information, then detect the receipt of the corresponding shipping information, skip step E2, and proceed to step E3.

[0099] Next, the state change monitoring node 40 reads incoming information from the record information database (45 in Figure 9) from the same node immediately preceding the detected shipping information (in this case, 10e (role: processing industry) in Figures 2 and 3) (step E2). If incoming information cannot be read from the record information database (45 in Figure 9), the process may proceed to step E3, determine that the conditions defined in the state change rule database 44 are not met, and then proceed to step E4.

[0100] Next, the state change monitoring node 40 determines whether the detected shipment information and the read-out arrival information quantities (here, weight) satisfy the conditions defined in the state change rule database 44 (here, processing industry, inbound / outbound volume relationship, and loss rate) (step E3). If the conditions are met (YES in step E3), the process terminates.

[0101] Furthermore, if the above conditions are met (YES in step E3), certification information confirming that the detected shipping information is a normal change in state may be associated with and recorded.

[0102] If the above conditions are not met (NO in step E3), the status change monitoring node 40 creates a warning information to alert the user that the status change is not normal (step E4). When creating the warning information, the warning information may be associated with and recorded in relation to the detected shipping information.

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

[0104] Next, the processing terminal 50e receives a warning from the status change monitoring node 40 (step E6), displays the received warning (step E7), and then terminates.

[0105] Embodiment 1 is configured as described above, but the configuration after assigning roles to the traceability management system can be modified as shown in Figure 22. That is, a configuration can be made in which multiple terminals 50a (livestock farmer terminals in Figure 22) are connected to one assigned node 10a to which a role (livestock farming in Figure 22) has been assigned. Also, for example, if there are multiple auditing bodies and each has different evaluation criteria, the blockchain network system 2 can be configured to have multiple assigned nodes 10b to which the same type of role (auditing bodies in Figure 22) has been assigned, and a terminal 50b (auditing body terminals in Figure 22) is connected to each assigned node 10b. In addition, in the blockchain network system 2, any excess assigned 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 Figure 11), or update to a new role database and set roles for each node. Furthermore, in the case of a large food manufacturer that has multiple business sectors (e.g., livestock farming, slaughtering, meat processing, etc.), there may be a node responsible for a single role that combines these multiple business sectors. Also, if a single business sector is subdivided into multiple departments, there may be a node responsible for a role that is assigned to each of those departments.

[0106] According to Embodiment 1, 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 body), the distribution route monitoring node 30, and the state change monitoring node 40 perform evaluation of the target object, monitoring of the distribution route, and monitoring of state changes. By viewing the results, it is possible to objectively, neutrally, fairly, and easily confirm the state (evaluation, fraud, falsification, etc.) inherent in the data when tracking the collected information. This allows stakeholders to immediately confirm evaluation, fraud, falsification, etc. without having to perform verification themselves.

[0107] Furthermore, according to Embodiment 1, since the role-assigning node 20 assigns roles to each responsible node 10a to 10i, data deficiencies and errors in the acquired information can be automatically monitored according to the role of each terminal 50a, 50c to 50h, and the distribution route and state changes can be automatically monitored. In contrast, in a normal blockchain network system without a role-assigning function, each node is equal and interacts freely with each other, so it is not possible to organize the collected information and automatically monitor the distribution route and state changes of the target object.

[0108] Furthermore, according to Embodiment 1, the assigned node 10b (role: auditing body) evaluates the object and makes the results available for viewing, thus demonstrating added value that the object has been evaluated according to objective, neutral, fair, and impartial evaluation criteria.

[0109] Furthermore, according to Embodiment 1, the distribution route monitoring node 30 monitors the distribution route of the target product, and the results are viewable. This ensures that the distribution route of the target product is consistent from start to finish, thereby gaining the reliability of the product and contributing to the widespread adoption of high value-added products.

[0110] Furthermore, according to Embodiment 1, the distribution route of the object can be monitored by the state change monitoring node 40, and the results can be viewed, thereby guaranteeing the authenticity of the object.

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

[0112] Furthermore, according to Embodiment 1, stakeholders can jointly operate the blockchain network system 2, and it is possible to prevent information from being altered (in a way that benefits that participant) at the behest of a particular participant.

[0113] As background, regarding cattle, currently, due to BSE (Bovine Spongiform Encephalopathy), information on cattle is managed by government agencies under national leadership. Information on cattle submitted by livestock farmers and intermediate processors is managed by government agencies, and these agencies grant certification (permission, guarantee) to beef. While other livestock species do not have problems like BSE, as animal welfare becomes more widespread, it will become necessary to show consumers that livestock products produced and distributed are certified to be raised in accordance with animal welfare standards. As animal welfare progresses, differences in breeding costs and prices will arise between those that comply and those that do not, potentially leading to misrepresentation of information and consumer distrust. To assure consumers that the information is not fraudulent, it is considered necessary to guarantee the information through a traceability system. However, for other livestock species, there is no nationally led system to guarantee information, and industry associations such as livestock farmers and intermediate processors must operate their own systems. When industry associations operate their own systems, they need to demonstrate to consumers the legitimacy of the information they manage. To achieve this, it is necessary for various related industries (livestock farming, processing, distribution, retail, etc.) to operate the system jointly or collaboratively. However, if the system is operated under the leadership of a specific industry, stakeholders will not feel comfortable participating, the system will not become widespread, and its use will not be promoted. Therefore, the conventional system can be operated arbitrarily by powerful businesses or in a way that favors specific participants. To ensure the quality, safety, and reliability of livestock products raised in accordance with animal welfare principles, a traceability management system for animal welfare products is necessary. Furthermore, because animal welfare livestock products have higher added value and are traded at higher prices than conventional livestock products, their traceability management system must be able to withstand food fraud and information falsification. Furthermore, there is no unified, government-led traceability system for non-cattle livestock such as pigs and chickens. Unlike cattle traceability, which is government-led, the system is operated and used jointly by multiple businesses with vested interests. Therefore, a system that ensures fairness is needed, as it would be problematic if information could be manipulated or if an unfair advantage or disadvantage were created based on the intentions of a particular business.Embodiment 1 provides a traceability management system that satisfies these needs.

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

[0115] The blockchain network system 2 is configured such that nodes 10a, 10c, ..., 20, and 40 are connected to each other on the network 3, and identical information about the object is distributed and held among nodes 10a, 10c, ..., 20, and 40.

[0116] Nodes 10a, 10c, ..., 20, and 40 comprise multiple assigned nodes 10a, 10c, ..., a role-assigning node 20, and a state change monitoring node 40.

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

[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 state change monitoring node 40 monitors the state changes of the target object. By viewing the results, it is possible to objectively, neutrally, fairly, and easily verify the state (fraud, falsification, etc.) inherent in the data when tracking the collected information.

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

[0120] The blockchain network system 2 is configured such that nodes 10a, 10c, ..., 20, and 30 are connected to each other on the network 3, and that identical information about the object is distributed and held among nodes 10a, 10c, ..., 20, and 30.

[0121] Nodes 10a, 10c, ..., 20, and 30 comprise multiple assigned nodes 10a, 10c, ..., a role-assigning node 20, and a distribution route monitoring node 30.

[0122] The assigned nodes 10a, 10c, ... are each responsible for a predetermined role. The role-assigning node 20 stores a role database that defines the corresponding role for each assigned node 10a, 10c, ... and is configured to assign a role (e.g., first role, second role, ...) to each of the assigned nodes 10a, 10c, ... based on the role database, and to connect them to at least one corresponding terminal 50a, 50b, ... outside the blockchain network system 2. The distribution route monitoring node 30 stores a distribution route rule database that defines distribution route rules regarding combinations of shipping sources and receiving destinations, and is configured to monitor the distribution route of the target goods by receiving information from terminals 50a, 50b, ... via the assigned nodes 10a, 10c, ... and determining whether the combinations of shipping sources and receiving destinations included in either or both of the shipping information and receiving information satisfy the distribution route rules.

[0123] According to Embodiment 3, in the blockchain network system 2, the role-assigning node 20 assigns roles to the responsible nodes 10a, 10c, ..., and the distribution route monitoring node 30 monitors the distribution route of the target object. By viewing the results, it is possible to objectively, neutrally, fairly, and easily verify the state (fraud, falsification, etc.) inherent in the data when tracking the collected information.

[0124] [Embodiment 4] The traceability management system according to Embodiment 4 will be described with reference to the drawings. Figure 25 is a schematic block diagram showing the configuration of the traceability management system according to Embodiment 4 after the roles have been assigned.

[0125] The blockchain network system 2 is configured such that nodes 10a, 10b, 10c, ..., 20 are connected to each other on the network 3, and identical information about the object is distributed and held among the nodes 10a, 10b, 10c, ..., 20.

[0126] Nodes 10a, 10b, 10c, and 20 comprise multiple assigned nodes 10a, 10b, 10c, ... and a role-assigning node 20.

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

[0128] According to Embodiment 4, in the blockchain network system 2, the role-assigning node 20 assigns roles to the responsible nodes 10a, 10b, 10c, ..., and the responsible node 10b (role: auditing body) performs the evaluation of the object. By viewing the results, it is possible to objectively, neutrally, fairly, and easily confirm the state (evaluation) inherent in the data when tracking the collected information.

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

[0130] The blockchain network system 2 is configured such that nodes 10a, 10c, ..., 20 are connected to each other on the network 3, and identical information about the object is distributed and held among nodes 10a, 10c, ..., 20.

[0131] Nodes 10a, 10c, ..., 20 comprise multiple assigned nodes 10a, 10c, ..., and a role-assigning node 20.

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

[0133] According to Embodiment 5, in the blockchain network system 2, by assigning roles to the responsible nodes 10a, 10c, ... via the role-assigning node 20, information can be organized to perform evaluation of the target object, monitoring of distribution routes, and monitoring of changes in state. By viewing the results, it is possible to objectively, neutrally, fairly, and easily verify the state (evaluation, fraud, falsification, etc.) inherent in the data when tracking the collected information.

[0134] The nodes and terminals according to Embodiments 1 to 5 can be composed of so-called hardware resources (information processing devices, computers), and those with the configuration illustrated in Figure 27 can be used. For example, the hardware resource 100 includes a processor 101, memory 102, network interface 103, etc., which are interconnected by an internal bus 104. The instruction program for operating the processor 101 and the necessary data are stored in the memory 102 and can be operated by inputting and outputting signals to the outside via the network interface 103 as needed.

[0135] The configuration shown in Figure 27 is not intended to limit the hardware configuration of the hardware resource 100. The hardware resource 100 may include hardware not shown (e.g., input / output interfaces). Similarly, the number of units such as processors 101 included in the device is not limited to the example in Figure 27; for example, multiple processors 101 may be included in the hardware resource 100. For example, a CPU (Central Processing Unit), MPU (Micro Processor Unit), GPU (Graphics Processing Unit), etc., can be used for the processor 101.

[0136] Memory 102 can be, for example, RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive), SSD (Solid State Drive), etc.

[0137] The network interface 103 can use, for example, a LAN (Local Area Network) card, a network adapter, a network interface card, etc.

[0138] The functions of the hardware resource 100 are realized by the processing module described above. This processing module is realized, for example, by the processor 101 executing a program stored in memory 102. Furthermore, this program can be downloaded via a network or updated using a storage medium containing the program. Moreover, the processing module may be implemented by a semiconductor chip. In other words, the functions performed by the processing module can be realized by the execution of software on some hardware.

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

[0140] [Note 1] A blockchain network system configured such that nodes are connected to each other on the network and that identical information about an object is distributed and held among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role-assigning node is configured to store a role database defining a corresponding role for each of the aforementioned assigned nodes, and to assign a role to each of the aforementioned assigned nodes based on the role database, thereby connecting them to at least one corresponding terminal outside the blockchain network system. A state change monitoring node is configured to store a state change rule database that defines the rules for state changes between the arrival and departure of an object, and to monitor the state changes of the object by receiving the information from the terminal via the assigned node and determining whether the state changes based on the corresponding arrival and departure information among the input information satisfy the state change rules, Equipped with, Blockchain network system. [Note 2] The status change monitoring node is configured to send alert information to the corresponding terminal to notify it that the status change is abnormal and to draw attention when the status change based on the incoming information and the outgoing information does not satisfy the status change rules defined in the status change rule database. The blockchain network system described in Appendix 1. [Note 3] The state change monitoring node is configured to record the warning information in association with both or either of the incoming information and outgoing information distributed and maintained among the nodes. The blockchain network system described in Appendix 2. [Note 4] The state change monitoring node is configured to record, when the state change based on the incoming information and the outgoing information satisfies the state change rule defined in the state change rule database, associate certification information indicating that the state change rule is satisfied with the incoming information and the outgoing information distributed and held on the node. The blockchain network system described in Appendix 2. [Note 5] The status change monitoring node is configured to send a warning message to alert the user that the status change is abnormal when there is no incoming information corresponding to the shipping information. The blockchain network system described in Appendix 1. [Note 6] A blockchain network system configured such that nodes are connected to each other on the network and that identical information about an object is distributed and held among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role-assigning node is configured to store a role database defining a corresponding role for each of the aforementioned assigned nodes, and to assign a role to each of the aforementioned assigned nodes based on the role database, thereby connecting them to at least one corresponding terminal outside the blockchain network system. A distribution route monitoring node is configured to store a distribution route rule database that defines distribution route rules regarding combinations of shipping source and receiving destination, and to monitor the distribution route of the target item by receiving the information from the terminal via the assigned node and determining whether the combination of shipping source and receiving destination included in either or both of the input information satisfies the distribution route rule, Equipped with, Blockchain network system. [Note 7] The distribution route monitoring node is configured to send warning information to the corresponding terminal to inform the distribution route of the abnormal distribution route when the combination of the origin and destination in either or both of the shipping information and the receiving information does not satisfy the distribution route rules. The blockchain network system described in Appendix 6. [Note 8] The distribution route monitoring node is configured to record the warning information in association with one or both of the incoming information and the outgoing information distributed and maintained among the nodes. The blockchain network system described in Appendix 7. [Note 9] The distribution route monitoring node is configured to record certification information indicating that the distribution route rule is met when the combination of the source and destination in either or both of the shipping information and the receiving information satisfies the distribution route rule, in conjunction with the shipping information and the receiving information distributed and maintained by the node. The blockchain network system described in Appendix 7. [Note 10] The aforementioned arrival information and the aforementioned shipment information each include data relating to quantity, The distribution route monitoring node is configured to transmit warning information to the corresponding terminal to alert the user that the distribution route is not functioning correctly when the quantities in the shipping information and the receiving information do not match, or when the quantities in the shipping information or the receiving information exceed a predetermined amount. The blockchain network system described in Appendix 6. [Note 11] The aforementioned shipping information and the aforementioned arrival information each include data relating to the date and time, The distribution route monitoring node is configured to transmit warning information to the corresponding terminal to alert the user that the distribution route is not functioning correctly when the time between the date and time of the shipment information and the date and time of the arrival information exceeds a predetermined time. The blockchain network system described in Appendix 6. [Note 12] The aforementioned shipping information includes data regarding the date and time, The distribution route monitoring node is configured to send a warning message to the corresponding terminal to alert it that the distribution route is not functioning correctly, if it fails to receive the corresponding incoming information within a predetermined time from the date and time of the shipment information. The blockchain network system described in Appendix 6. [Note 13] A blockchain network system configured such that nodes are connected to each other on the network and that identical information about an object is distributed and held among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role-assigning node is configured to store a role database defining a corresponding role for each of the aforementioned assigned nodes, and to assign a role to each of the aforementioned assigned nodes based on the role database, thereby connecting them to at least one corresponding terminal outside the blockchain network system. Equipped with, At least one of the aforementioned responsible nodes is assigned a role related to an auditing body by the role-assigning node, stores an evaluation criteria database that associates conditions and evaluations for a predetermined evaluation target, and is configured to receive the information from the terminal via a responsible node other than the responsible node assigned the role related to the auditing body, and to evaluate the evaluation target in the received information based on the evaluation criteria database. Blockchain network system. [Note 14] The assigned node, which has been assigned the role related to the auditing body, is configured to record evaluation information, including the evaluated results, in association with the information distributed and maintained on the node. The blockchain network system described in Appendix 13. [Note 15] A blockchain network system configured such that nodes are connected to each other on the network and that identical information about an object is distributed and held among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role-assigning node is configured to store a role database defining a corresponding role for each of the aforementioned assigned nodes, and to assign a role to each of the aforementioned assigned nodes based on the role database, thereby connecting them to at least one corresponding terminal outside the blockchain network system. A blockchain network system equipped with these features. [Note 16] The responsible node is configured to check whether there are any missing or incorrect data in the information from the corresponding terminal, and to distribute and store the information among the nodes if there are no missing or incorrect data. A blockchain network system as described in any one of the appendices 1 through 15. [Note 17] The responsible node is configured to read the corresponding information and transmit it to the corresponding terminal in response to a viewing request from the corresponding terminal. A blockchain network system as described in any one of the appendices 1 through 15. [Note 18] A blockchain network system described in any one of the appendices 1 to 15, A role management terminal configured to connect to the aforementioned role assignment node, Multiple terminals configured to connect to the corresponding assigned node to which a role has been assigned by the role management terminal, A traceability management system equipped with [features / equipment]. [Note 19] A traceability management method in which a blockchain network system is configured such that nodes are connected to each other on the network and the same information about an object is distributed and maintained among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role assignment node is configured to store a role database that defines the corresponding role for each of the aforementioned assigned nodes, A state change monitoring node configured to store a state change rule database that defines the rules for state changes between the arrival and departure of an object, Equipped with, The aforementioned traceability management method is: The steps include: 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; The steps include inputting the information from the terminal to the state change monitoring node via the assigned node to which the role has been assigned by the role assignment node, The state change monitoring node monitors the state change of the object by determining whether the state change based on the corresponding incoming and outgoing information among the input information satisfies the state change rule. A traceability management method that includes [the following]. [Note 20] A traceability management method in which a blockchain network system is configured such that nodes are connected to each other on the network and the same information about an object is distributed and maintained among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role assignment node is configured to store a role database that defines the corresponding role for each of the aforementioned assigned nodes, A distribution route monitoring node configured to store a distribution route rule database that defines distribution route rules regarding combinations of shipping source and receiving destination, Equipped with, The aforementioned traceability management method is: The steps include: 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; The steps include inputting the information from the terminal to the distribution route monitoring node via the assigned node to which a role has been assigned by the role-assigning node, The distribution route monitoring node monitors the distribution route of the object by determining whether the combination of origin and destination included in either or both of the shipment information and the arrival information among the input information satisfies the distribution route rule. A traceability management method that includes [the following]. [Note 21] A traceability management method in which a blockchain network system is configured such that nodes are connected to each other on the network and the same information about an object is distributed and maintained among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role assignment node is configured to store a role database that defines the corresponding role for each of the aforementioned assigned nodes, Equipped with, 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. The role-assigning node assigns the role related to the auditing body to the said node, and the said node stores an evaluation criteria database that associates conditions and evaluations for a predetermined evaluation target. The steps include inputting the information from the terminal to the responsible node assigned the role related to the auditing body via a responsible node other than the responsible node assigned the role related to the auditing body, The steps include: the assigned node, which has been given the role of the auditing body, evaluates the subject of evaluation in the input information based on the evaluation criteria database; A traceability management method that includes [the following]. [Note 22] A traceability management method in which a blockchain network system is configured such that nodes are connected to each other on the network and the same information about an object is distributed and maintained among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role assignment node is configured to store a role database that defines the corresponding role for each of the aforementioned assigned nodes, Equipped with, The aforementioned traceability management method is: 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. Traceability management methods.

[0141] Furthermore, each disclosure in the above-mentioned patent documents is incorporated into this document by reference and may be used as the basis or part of the present invention as necessary. Within the framework of the full disclosure of the present invention (including the claims and drawings), further modifications and adjustments to the embodiments or examples are possible based on the basic technical concept. Also, within the framework of the full disclosure of the present invention, various combinations or selections (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible. In other words, the present invention naturally includes the full disclosure, including the claims and drawings, and various modifications and alterations that a person skilled in the art could make in accordance with the technical concept. Furthermore, regarding the numerical values ​​and numerical ranges described in this application, any intermediate values, lower values, and smaller ranges are deemed to be described even if not explicitly stated. Moreover, each disclosure in the above-mentioned cited documents may, as necessary, be used in part or in whole as part of the disclosure of the present invention, in accordance with the spirit of the present invention, and may be combined with the matters described in this document, and these may also be considered to be included in (belonging to) the disclosures of this application. [Explanation of symbols]

[0142] 1. Traceability Management System 2 Blockchain network system 3. P2P Network (Network) Nodes responsible for 10a to 10n 11 Communications Department 12 Storage section 13 Control Unit 13a Certification Processing Unit 13b Recording Processing Unit 13c Browsing Processing Unit 13d Evaluation Processing Unit 14 Role Labels 15. Record Information Database 16 Evaluation Criteria Database 20 Role-assigned nodes (nodes) 21 Communications Department 22 Memory section 23 Control Unit 23a Role Assignment Unit 23b Recording Processing Unit 24 Role Database 25. Record Information Database 30 Distribution route monitoring nodes (nodes) 31 Communications Department 32 Storage section 33 Control Unit 33a Distribution Route Monitoring Department 33b Recording Processing Unit 34 Distribution Route Rules Database 35. Record Information Database 40 State change monitoring nodes (nodes) 41 Communications Department 42 Storage section 43 Control Unit 43a State change monitoring unit 43b Recording Processing Unit 44 State Change Rule Database 45 Record Information Database 50a~50i terminals 51 Communications Department 52 Storage section 53 Input section 54 Display section 55 Control Unit 60. Role Management Terminal (Terminal) 70 Distribution route management terminal (terminal) 80. Status Change Management Terminal (Terminal) 90 Networks 100 hardware resources 101 Processors 102 memory 103 Network Interface 104 Internal Bus

Claims

1. A blockchain network system configured such that nodes are connected to each other on the network and that identical information about an object is distributed and held among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role-assigning node is configured to store a role database defining a corresponding role for each of the aforementioned assigned nodes, assign a role to each of the assigned nodes based on the role database, and connect to at least one terminal outside the blockchain network system corresponding to the aforementioned role, A state change monitoring node is configured to store a state change rule database that defines state change rules for each role between the arrival and departure of an object, and to monitor the state changes of the object by receiving the information from the terminal via the assigned node and determining whether the state changes based on the arrival and departure information among the input information satisfy the state change rules for the role assigned to the assigned node, Equipped with, Blockchain network system.

2. The status change monitoring node is configured to send alert information to the corresponding terminal to notify it that the status change is abnormal and to draw attention when the status change based on the incoming information and the outgoing information does not satisfy the status change rules defined in the status change rule database. The blockchain network system according to claim 1.

3. A blockchain network system configured such that nodes are connected to each other on the network and that identical information about an object is distributed and held among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role-assigning node is configured to store a role database defining a corresponding role for each of the aforementioned assigned nodes, assign a role to each of the assigned nodes based on the role database, and connect to at least one terminal outside the blockchain network system corresponding to the aforementioned role, A distribution route monitoring node is configured to store a distribution route rule database that defines distribution route rules relating to the combination of roles of the shipping source and the receiving source, and to monitor the distribution route of the target object by receiving the information from the terminal via the responsible node and determining whether the combination of roles of the shipping source and the receiving source included in either or both of the shipping information and receiving 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 the network and that identical information about an object is distributed and held among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role-assigning node is configured to store a role database defining a corresponding role for each of the aforementioned assigned nodes, assign a role to each of the assigned nodes based on the role database, and connect to at least one terminal outside the blockchain network system corresponding to the aforementioned role, Equipped with, At least one of the aforementioned responsible nodes is assigned a role related to an auditing body by the role-assigning node, and stores an evaluation criteria database that associates conditions and evaluations for a predetermined evaluation target in a predetermined role. When information on the predetermined evaluation target is input from the terminal via the responsible node to which the predetermined role has been assigned, the node is configured to evaluate the evaluation target in the input information based on the evaluation criteria database. Blockchain network system.

5. A traceability management method in which a blockchain network system is configured such that nodes are connected to each other on the network and the same information about an object is distributed and maintained among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role assignment node is configured to store a role database that defines the corresponding role for each of the aforementioned assigned nodes, A state change monitoring node is configured to store a state change rule database in which state change rules for each role are defined for the state change between the arrival and departure of the target object, Equipped with, 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 terminal outside the blockchain network system that corresponds to the role. The steps include inputting the information from the terminal to the state change monitoring node via the assigned node to which the role has been assigned by the role assignment node, The state change monitoring node monitors the state change of the object by determining whether the state change based on the incoming information and outgoing information among the input information satisfies the state change rule in the role assigned to the responsible node, A traceability management method that includes [the following].

6. A traceability management method in which a blockchain network system is configured such that nodes are connected to each other on the network and the same information about an object is distributed and maintained among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role assignment node is configured to store a role database that defines the corresponding role for each of the aforementioned assigned nodes, A distribution route monitoring node configured to store a distribution route rule database that defines distribution route rules relating to the aforementioned combinations of roles between the shipping source and the receiving destination, Equipped with, 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 terminal outside the blockchain network system that corresponds to the role. The steps include inputting the information from the terminal to the distribution route monitoring node via the assigned node to which a role has been assigned by the role-assigning node, The distribution route monitoring node monitors the distribution route of the object by determining whether the combination of roles of the source and destination included in either or both of the shipment information and the arrival information among the input information satisfies the distribution route rule. A traceability management method that includes [the following].

7. A traceability management method in which a blockchain network system is configured such that nodes are connected to each other on the network and the same information about an object is distributed and maintained among the nodes, The aforementioned node is Multiple nodes, each responsible for a specific role, A role assignment node is configured to store a role database that defines the corresponding role for each of the aforementioned assigned nodes, Equipped with, 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 terminal outside the blockchain network system that corresponds to the role. The role-assigning node assigns the role related to the auditing body to the responsible node, which stores an evaluation criteria database that associates conditions and evaluations for a predetermined evaluation target in the predetermined role. The steps include inputting the predetermined information to be evaluated from the terminal to the responsible node assigned the role related to the auditing body via the responsible node assigned the predetermined role, The steps include: the assigned node, which has been given the role of the auditing body, evaluates the subject of evaluation in the input information based on the evaluation criteria database; A traceability management method that includes [the following].

Images