Supply chain management method, supply chain management procedure, supply chain management system and transaction record display procedure

Abstract

The present invention provides a supply chain management method, a supply chain management program, a supply chain management system, and a transaction record display program. A data management server (60) manages transaction records (ReT) between traders (TR) in a supply chain (SC) constructed by multiple traders (TR). The data management server (60) obtains project data attached to a delivery project (IMi) delivered to a specific industry operator (TRs) and company data assigned to the specific industry operator (TRs), and calculates a hash value based on the project data and the company data. The hash value is provided to the specific industry operator (TRs) as project data attached to a delivery project (IMo) shipped from the specific industry operator (TRs) to other traders (TRs).

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on patent application No. 2019-123836 filed in Japan on July 2, 2019, and the contents of the basic application are cited in their entirety by reference. Technical Field

[0003] The disclosure of this specification relates to supply chain management technology for managing transaction records. Background Art

[0004] Patent document 1 discloses a management system for the treatment of articles for the purpose of traceability management related to the treatment of waste. Specifically, in the management system of Patent document 1, a QR code or IC tag recording waste information is circulated together with the waste as a list. Furthermore, identification information is given in advance to each trader who performs waste treatment, and when the trader who performs waste treatment reads the list, the execution record of the trader's treatment is stored in a distributed storage system.

[0005] Patent Document 1: Japanese Patent Application Publication No. 2018-169764

[0006] In the management system disclosed in Patent Document 1, the information recorded in the list is pre-set content such as waste type, waste amount, and treatment route. However, in order to eliminate the unfairness of traders in the supply chain, it is preferred to attach the content reflecting the previous transaction results to the items circulated between traders instead of attaching the pre-set content. However, it is very difficult to record all the information of multiple traders involved in the circulation process in QR codes and IC tags attached to the items. Summary of the invention

[0007] The present disclosure aims to provide a supply chain management method, a supply chain management program, a supply chain management system, a transaction record display program, and the like that can suppress the amount of data attached to an item and appropriately manage a supply chain.

[0008] In order to achieve the above-mentioned purpose, a disclosed method is a supply chain management method, which is implemented by a computer and uses blockchain to manage transaction records between traders in a supply chain constructed by multiple traders. The processing performed by at least one processor includes the following steps: obtaining project data attached to a delivery item delivered to a specific person as a trader, and node identification data assigned to the specific person; calculating a hash value based on the project data and the node identification data; and providing at least the hash value to the specific person as project data attached to a delivery item shipped from the specific person to other traders.

[0009] In addition, a disclosed method is a supply chain management method, which is implemented by a computer and uses blockchain to realize the management of transaction records between traders in a supply chain constructed by multiple traders by a data management server. The processing performed by at least one processor includes the following steps: obtaining project data attached to a delivery item delivered to a specific person as a trader; sending a transaction record at the specific person including at least the data item to the data management server; receiving a hash value calculated by the data management server at least based on the project data; and using the data including at least the hash value as project data attached to a delivery item shipped from the specific person to other traders.

[0010] In addition, one disclosed method is a supply chain management program that uses blockchain to manage transaction records between traders in a supply chain constructed by multiple traders, causing at least one processor to perform the following processing: obtaining item data attached to a delivery item delivered to a specific person as a trader, and node identification data assigned to the specific person; calculating a hash value based on the item data and the node identification data; and providing at least the hash value as item data attached to a delivery item shipped from the specific person to other traders to the specific person.

[0011] In addition, one disclosed method is a supply chain management program that uses blockchain to implement transaction records between traders in a supply chain constructed by multiple traders, which is managed by a data management server, and causes at least one processor to implement processing including the following steps: obtaining project data attached to a delivery item delivered to a specific person as a trader; sending a transaction record at the specific person including at least the data item to the data management server; receiving a hash value calculated by the data management server at least based on the project data; and using the data including at least the hash value as project data attached to a delivery item shipped from the specific person to other traders.

[0012] In addition, one disclosed method is a supply chain management system, which is a supply chain management system that uses blockchain to manage transaction records between traders in a supply chain constructed with multiple traders, the system including: a user node used by each trader; and at least one host node capable of communicating with multiple user nodes, the user node used by a specific trader having: an acquisition unit, which acquires item data attached to a delivery item delivered to the specific person and node identification data assigned to the specific person; and a sending unit, which sends the item data and node identification data acquired by the acquisition unit to the host node, the host node having: a calculation unit, which calculates a hash value based on the item data and node identification data received from the user node; and a providing unit, which provides at least the hash value to the specific person as item data attached to a delivery item shipped from the specific person to other traders.

[0013] According to these methods, a hash value reflecting the previous transaction results is attached to an item traded between multiple traders. This reduces the amount of data attached to the item, and the transaction records of the item between traders are accumulated in a way that is difficult to tamper with as the item circulates. Therefore, the supply chain can be properly managed.

[0014] In addition, one disclosed method is a supply chain management method, which is implemented by a computer and uses blockchain to manage transaction records between traders in a supply chain constructed by multiple traders. The processing performed by at least one processor includes the following steps: obtaining project data attached to a delivery item delivered to a specific person as a trader, and node identification data assigned to the specific person; associating and accumulating transaction records in the specific person with the project data; deciding to continue using the project data attached to the delivery item as project data attached to a shipment item shipped from the specific person to other traders; obtaining a reference request for the transaction record together with the project data; when the project data is continued to be used by multiple traders, extracting each transaction record of multiple traders using the project data from multiple transaction records managed using blockchain; and providing provision data based on the extracted transaction records to the request source of the reference request.

[0015] According to this method, the item data attached to the shipment item is continuously used by multiple traders. On the other hand, in the blockchain, the transaction records of multiple traders are associated with the one item data that is continuously used and accumulated. As a result, the amount of data attached to the item is suppressed, and the transaction records of the item between traders are accumulated in the blockchain in a manner that is difficult to be tampered with as the item circulates. Therefore, the supply chain can be properly managed.

[0016] In addition, a disclosed method is a transaction record display program that displays transaction records between multiple traders included in a supply chain, causing at least one processor to perform the following processing: reading project data, wherein the project data is attached to a specific project and the project data at least includes a hash value that reflects the circulation process of the specific project; sending a reference request for a transaction record associated with the specific project together with the project data to a host node; receiving provision data related to the transaction record from the host node, wherein the transaction record is managed using a blockchain and the transaction record is associated with a specific project; and based on the provision data, displaying the transaction record in a hierarchical state that reflects the circulation process of the specific project.

[0017] According to this method, by reading the item data attached to a specific item, the transaction record associated with the specific item can be obtained from the host node. Therefore, the amount of data attached to the item is suppressed, and the transaction record of the previous item can be referenced from the user side. In addition, since the transaction record is displayed in a hierarchical form reflecting the flow process of the specific item, it is easy to grasp the transaction record of the user. By ensuring the convenience of record reference as described above, it is easy to achieve appropriate management of the supply chain. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a diagram showing an overall image of the supply chain management system according to the first embodiment of the present disclosure.

[0019] Figure 2 It is a block diagram showing the electrical structure of a user device, a time stamp server, a data management server, and a user terminal.

[0020] Figure 3 This is a diagram showing an example of a two-dimensional code that records item data and the like and is attached to an item circulated between traders.

[0021] Figure 4 This is a flowchart showing the details of the response output process performed by the response output unit of the time stamp server.

[0022] Figure 5 This is a flowchart showing the details of the data anomaly verification process performed by the record verification unit of the data management server.

[0023] Figure 6 This diagram schematically shows the process of connecting hash values ​​as a Merkle tree as the project circulates.

[0024] Figure 7 This is a sequence diagram showing the details of the chain generation process performed in the supply chain management system.

[0025] Figure 8This is a sequence diagram showing the details of the record search process performed through the cooperation of the data management server and the user terminal.

[0026] Fig. 9 This is a diagram showing details of display transition of a GUI screen displayed on a user terminal by the traceability confirmation application.

[0027] Fig.10 It means that Figure 1 The diagram shows an application example of the supply chain management system applied to the supply chain of bread.

[0028] Fig.11 This is a sequence diagram showing the details of the initial setting process for registering initial setting data and issuing a basic information code.

[0029] Fig.12 It means that Figure 7 The chain generation process shown applies to Fig.10 Figure 2 shows an example of supply chain application.

[0030] Fig.13 It is a sequence diagram showing the details of the chain generation process according to the second embodiment.

[0031] Fig.14 It is a sequence diagram showing the details of the record search process according to the second embodiment. DETAILED DESCRIPTION

[0032] Hereinafter, multiple embodiments of the present disclosure are described based on the accompanying drawings. In addition, there is a case where repeated descriptions are omitted by marking the corresponding constituent elements with the same figure mark in each embodiment. When only a part of the structure is described in each embodiment, the structure of other embodiments described previously can be applied to the other parts of the structure. In addition, as long as it is not a combination of structures explicitly shown in the description of each embodiment, in particular, as long as it does not hinder the combination, the structures of multiple embodiments can be partially combined with each other even if it is not explicitly shown. Moreover, the combination of structures described in multiple embodiments and modified examples that is not explicitly shown is also disclosed through the following description.

[0033] (First Embodiment)

[0034] Figure 1 The supply chain management system 100 of the first embodiment of the present disclosure shown manages transaction records ReT of items traded between traders TR in a supply chain SC constructed by including multiple traders TR. In the supply chain management system 100, the blockchain BC technology is used in the management of the transaction records ReT for the purpose of preventing tampering of the transaction records ReT.

[0035] The supply chain SC is a connection between traders TR for delivering industrial products, agricultural products, and marine products to consumers CST, for example. As an example, in the supply chain SC for delivering industrial products to consumers CST, material developers, material producers, processors, transporters, and sellers are included in the trader TR. In this case, a supply chain SC from raw materials MAT to final products FP is constructed. In addition, in the present disclosure, consumers CST of the final product FP and waste disposal operators related to the disposal of the final product FP may also be included in the trader TR.

[0036] All the industry players except the consumer CST among the multiple traders TR are pre-certified by the certifier Cer (certification agency). As an example, the certifier Cer is the manager who manages the supply chain SC and is the provider of the final product FP to the consumer CST. The certifier Cer allows the industry players who meet the prescribed standards to participate in the supply chain SC by identifying them and issuing certification to the identified industry players. In addition, as described later, the certifier Cer can also be the responsibility of a company such as a system supplier or platform provider of the supply chain management system 100.

[0037] like Figure 1 and Figure 2 As shown, the supply chain management system 100 includes a plurality of user devices 10, a time stamp server 90, and at least one data management server 60. Each user device 10, time stamp server 90, and data management server 60 are respectively connected to a network NW and can communicate with each other.

[0038] At least one user device 10 is installed in each facility of each trader TR that produces and discards the final product FP. The user device 10 is used by the staff of the specific trader TR (hereinafter, the specific trader TRs) in the facility where the user device 10 is installed. The user device 10 sends the delivery record of the item delivered to the specific trader TRs (hereinafter, the delivery item IMi) to the data management server 60. In addition, the user device 10 receives information attached to the item shipped from the specific trader TRs (hereinafter, the shipment item IMo) from the data management server 60. The user device 10 has a reader 17, a GNSS (Global Navigation Satellite System) receiver 18, a printer 19, and a processing circuit 10a.

[0039] The reader 17 is a device that reads project data, company data, time stamp data, etc. Each data is recorded in a two-dimensional code such as a QR code (registered trademark). The reader 17 is a structure including an area sensor composed of a two-dimensional array of CCD elements. The reader 17 reads a two-dimensional code printed on a paper medium, etc., and outputs the information of the read two-dimensional code to the processing circuit 10a.

[0040] The project data is data attached to the delivery project IMi. A two-dimensional code (hereinafter referred to as the project code QRi) recording the project data is printed on a paper medium and affixed to the delivery project IMi as a label. The affixing location of the project code QRi is not limited to the product body, but may be any location in the packaging, casing, certificate, etc. The project code QRi records at least a hash value of the project data associated with the delivery project IMi and an IP address of the consulting object of the transaction record ReT (refer to Figure 3 ). As described later, the hash value is a value (Merkle route) that reflects the distribution process of the delivery item IMi so far.

[0041] In addition, in the item code QRi, the URL of the consulting object of the transaction record ReT may be recorded instead of the above-mentioned IP address. Among them, compared with the URL, the IP address has the advantage that the amount of data (number of digits) does not change. Furthermore, as a traceability system, if the information of the consulting object of the transaction record ReT is provided to each trader TR in advance by other means, the IP address and URL etc. indicating the consulting object may not be recorded in the item code QRi.

[0042] Company data is identification data representing TRs of a specific industry. The authenticator Cer gives each trader TR unique company data. A two-dimensional code (hereinafter referred to as company code QRc) recording company data is distributed to each trader TR in advance in a state of being printed on a paper medium, etc. The hash value pre-established by the authenticator Cer and each trader TR is recorded as company data in the company code QRc. The authenticator Cer has information such as the name (company name and representative name, etc.), address, business office name, and history of the trader TR as authentication data. Company data can also be based on the hash value of such authentication data.

[0043] In addition, the generation of company data and the distribution of company codes QRc may be implemented not by the manager of the supply chain SC that performs the certification, but by the system supplier of the supply chain management system 100. In this case, the system supplier is also considered to be a part of the certifier Cer. In addition, multiple company codes QRc may be provided to one enterprise. For example, company codes QRc may be distributed to multiple production plants owned by one enterprise respectively. In addition, different company codes QRc may be distributed to each production line that manufactures a specific product. In this case, the company data recorded in the company code QRc is information that can identify not only the enterprise, but also the production plant and production line.

[0044] The project code QRi and the company code QRc preferably use a secure QR code (SQRC, registered trademark) that can set the public and private information of the recorded information by using an encryption key. The data recorded in the SQRC is encrypted with a public key and can only be read by a user device 10 that knows the private key. As a result, the person who can read the project data and company data can be limited to the trader TR in the supply chain SC. Furthermore, the project code QRi and the company code QRc preferably use a copy-proof QR code that is difficult to copy by a copier or the like by using special ink.

[0045] The time stamp data is used as data associating the date and time of the delivery item IMi with the specific trader TRs. The time stamp data is generated by the time stamp server 90. A two-dimensional code (hereinafter, time stamp code QRt) having a hash value as the time stamp data recorded therein is provided to each trader TR as image data, for example.

[0046] The reader 17 can further read the initial setting data. The initial setting data is recorded in a two-dimensional code such as a QR code like other data. The initial setting data is a number that supplements the project data and company data. Part of the initial setting data may also overlap with the project data or company data. The initial setting data is mainly pre-registered in the data management server 60 (see Fig.11 ). As an example, information such as the origin and production equipment of the raw material MAT can be registered as initial setting data. The data management server 60 issues a two-dimensional code (hereinafter referred to as the basic information code QRb) recording the initial setting data. The basic information code QRb is provided to the trader TR who has registered the initial setting data, for example, as image data. The basic information code QRb is printed on a paper medium, etc., and is read by the reader 17 together with the project code QRi and the company code QRc, etc.

[0047] The GNSS receiver 18 receives positioning signals transmitted from a plurality of artificial satellites (positioning satellites) to determine the location where the user device 10 is being used. The location data of the user device 10 determined by the GNSS receiver 18 is historical data indicating the location of the delivery item IMi. The GNSS receiver 18 provides the location data based on the positioning signal to the processing circuit 10a.

[0048] The printer 19 is an output device that prints the new item code QRi obtained from the data management server 60 on a paper medium (such as a sticker). The item code QRi printed by the printer 19 is attached to the shipment item IMo and distributed to the next step trader TR in a state attached to the shipment item Imo.

[0049] The processing circuit 10a is a structure mainly composed of a microcontroller including a processor 11, a RAM 12, a storage unit 13, an input / output interface 14, and a bus connecting these structures. The processing circuit 10a functions as a computer of the user device 10. The processing circuit 10a has a plurality of functional units associated with the accumulation of transaction records ReT by accessing the RAM 12 of the processor 11. Specifically, the processing circuit 10a includes an information acquisition unit 21, an information transmission unit 22, a code reception unit 23, and a code output unit 24.

[0050] The information acquisition unit 21 acquires hash values ​​as item data, company data, and time stamp data from the image data of each code read by the reader 17. The information acquisition unit 21 acquires position data from the GNSS receiver 18. The information transmission unit 22 transmits the data acquired by the information acquisition unit 21 to the data management server 60 via the network NW.

[0051] The code receiving unit 23 receives the image data of the item code QRi generated by the data management server 60 through the network NW based on the transmission data of the information transmitting unit 22. The code output unit 24 outputs the item code QRi received by the code receiving unit 23 through the printer 19.

[0052] The time stamp server 90 is a server device that generates time stamp data. When the time stamp server 90 receives a request to provide information associated with time stamp data from other nodes such as the user device 10 and the data management server 60, it provides the time stamp data to the requesting node.

[0053] The time stamp server 90 is a computer-based structure having a processor, RAM, storage, input / output interface, and a bus connecting these components. The processor is hardware for performing calculations in conjunction with the RAM. The processor accesses the RAM to perform various processes associated with the generation and distribution of time stamp data. The time stamp server 90 includes a current event description acquisition unit 91, a time stamp generation unit 92, and a response output unit 93 based on a time stamp generation program stored in the storage unit.

[0054] The current event description acquisition unit 91 acquires news reports distributed in association with information indicating date and time, such as the date of the day, from a news distribution server connected to the network NW. The current event description acquisition unit 91 acquires news reports, for example, every day or at specified intervals. As an example, the current event description acquisition unit 91 acquires news reports such as "The beginning of the first year of Reiwa (May 1, 2019)", "176 tuna lined up. The first auction of Reiwa (May 2, 2019)", and "The Prime Minister of New Zealand is engaged (May 3, 2019)".

[0055] The timestamp generation unit 92 generates timestamp data based on the news reports acquired by the current affairs description acquisition unit 91. The timestamp generation unit 92 generates input information that sequentially combines date information (e.g., 20190501), a character string of a news report, and a pre-specified character string. The timestamp generation unit 92 calculates a hash value of a specified number of bits (e.g., 256 bits) as timestamp data by inputting the above-mentioned input information including the news report into a hash function such as SH-256. The timestamp generation unit 92 accumulates the calculated hash value, date information, news report, and specified character string as a set of search data in a timestamp list.

[0056] In addition, the hash function used in the supply chain management system 100 is a cryptographic hash function, which has the characteristics of not outputting the same hash value from different inputs and substantially being unable to infer the input from the output hash value. For example, instead of the above-mentioned SHA-256, encryption algorithms such as SHA-1, SHA-2, and SHA-3 may be appropriately used according to the required output length (number of bits).

[0057] The response output unit 93 obtains a request for providing information associated with the time stamp data from other nodes such as the user device 10 and the data management server 60 via the network NW. The response output unit 93 performs response output processing based on the acquisition of the provision request (see Figure 4). In the response output processing, the response output unit 93 determines whether there are parameters received together with the provision request, and further determines the content of the parameters (refer to S11). In the case of no parameters, the response output unit 93 determines whether there is the latest timestamp data (refer to S12). In the case of the latest timestamp data, the response output unit 93 returns the image data of the timestamp code QRt recorded with its hash value to the node of the request source (refer to S13). On the other hand, in the case of no timestamp data, the response output unit 93 notifies a value indicating an error (for example, 0) (refer to S20).

[0058] In addition, when the hash value is used as a parameter, the response output unit 93 searches the time stamp list for date information corresponding to the hash value (see S14). When the date information is found (see S15: Yes), the response output unit 93 returns the date to the node of the request source (see S16). On the other hand, when the date information is not found (see S15: No), the response output unit 93 notifies a value indicating an error (see S20).

[0059] Furthermore, when the date is used as a parameter, the response output unit 93 searches for a hash value corresponding to the date from the timestamp list (see S17). When the hash value is found (see S18: Yes), the response output unit 93 returns the found hash value to the node of the request source (see S19). On the other hand, when the hash value is not found (see S18: No), the response output unit 93 notifies a value indicating an error (see S20).

[0060] The data management server 60 is a host node that can communicate with multiple user devices 10. The data management server 60 accumulates transaction records ReT and implements data mining of the accumulated transaction records ReT. The data management server 60 is composed of a server device 60a, which is mainly composed of a computer having a processor 61, RAM 62, a storage unit 63, an input and output interface 64, and a bus connecting these components. The processor 61 is hardware for calculation processing in combination with the RAM 62. The processor 61 executes various processes related to data management by accessing the RAM 62. The storage unit 63 stores a supply chain management program that can perform data management.

[0061] In addition to the record generation function of accumulating transaction records ReT provided from a plurality of user devices 10, the data management server 60 also has a record reference function of providing transaction records ReT for reference. The following is a detailed description of the record generation function among these functions. In the storage unit 63, as one of the supply chain management programs, a record generation program for realizing the accumulation of transaction records ReT is stored. Based on the record generation program, the data management server 60 has functional units such as a record acquisition unit 71, a record verification unit 72, a chain generation unit 73, and a code providing unit 74.

[0062] The record acquisition unit 71 acquires information sent by the user device 10 through the network NW as a transaction record ReT. The transaction record ReT includes at least one item data, company data, time stamp data, and location data. The item data, company data, and time stamp data are hash values ​​of a predetermined number of digits. The record acquisition unit 71 further acquires the hash value of the location data by, for example, inputting the location data into a hash function such as SHA-256 for computational processing.

[0063] The record acquisition unit 71 sends a request for providing the hash value of the timestamp data as a parameter to the timestamp server 90. As a result, the record acquisition unit 71 receives date information corresponding to the sent hash value from the timestamp server 90. In addition, the transmission of the timestamp data from the user device 10 to the record acquisition unit 71 may be omitted. In this case, when the project data or the like is acquired from the user device 10, the record acquisition unit 71 acquires the hash value as the timestamp data in association with the date information of the day.

[0064] The record verification unit 72 compares the data acquired by the record acquisition unit 71 with the pre-registered data, etc., to perform data anomaly verification processing to verify whether each data acquired this time is normal (see Figure 5 ) The record verification unit 72 detects the mixing of improper products, parts, and raw materials MAT, etc., from uncertified businesses into circulation items in the supply chain SC.

[0065] Specifically, the record verification unit 72 refers to the list of company data set in each trader TR (see S31), and determines whether the company data acquired by the record acquisition unit 71 is consistent with the normal value registered in the list (see S32). If the hash value of the company data is different from the hash value in the list, the record verification unit 72 performs an abnormality determination that there is a possibility of mixing of an improper item (see S33).

[0066] The record verification unit 72 determines whether the item data acquired by the record acquisition unit 71 this time is repeated with the item data already acquired from other traders TR (refer to S34). If described in detail, when a new delivery item Imo is generated, in the processing (S164) described later, the delivery item Imo is recorded in the transaction record ReT as an unused item. If the delivery item IMi this time is an unused item, the record verification unit 72 changes the use status of the item to completed use. On the other hand, if the delivery item IMi this time is an item that has been used but not completed, the record verification unit 72 makes an abnormality judgment because more items than the number of production items have been generated.

[0067] The record verification unit 72 refers to the past time stamp data related to the project data, specifically, the time stamp data recorded by the trader TR before the previous process (see S35). The record verification unit 72 determines whether the time sequence is normal for the date information related to the past time stamp data (see S36). In the case of a time sequence contradiction, the record verification unit 72 performs an abnormality determination.

[0068] The record verification unit 72 refers to the list of location data of the specific industry TRs corresponding to the company data (see S37), and determines whether the acquired location data matches the location data of the registered specific industry TRs (see S38). For example, when the acquired location data is completely different from the registered location of the specific industry TRs, the record verification unit 72 makes an abnormality determination. On the other hand, when no abnormality is found in the data, the record verification unit 72 makes a normal determination that the delivery project IMi is a regular project (see S39).

[0069] The chain generation unit 73 accumulates the project data, company data, time stamp data, and location data obtained by the record acquisition unit 71 in a state that is difficult to tamper with using blockchain technology. The chain generation unit 73 calculates a hash value of new project data as a shipment project Imo attached to the specific industry TRs. The chain generation unit 73 prepares the project data of all delivery projects IMi associated with the shipment project IMo, the company data of the specific industry TRs, the time stamp data, and the location data. The chain generation unit 73 calculates the Merkle route of these hash values.

[0070] The chain generation unit 73 regards each data (hash value) obtained as a transaction record ReT as a block and links it to the end of the blockchain BC. In addition, the chain generation unit 73 regards the hash value of the last block as new item data. Through the above processing, the chain generation unit 73 repeatedly calculates the hash value reflecting the circulation process before this according to the progress of the item transaction between each trader TR in the supply chain SC. The chain generation unit 73 stores the transaction record ReT in the blockchain in the storage area in the storage unit 63.

[0071] The code providing unit 74 provides the hash value of the final block calculated by the chain generating unit 73 to the user device 10 which is the transmission source of the transaction record ReT. The code providing unit 74 generates a two-dimensional code including at least the hash value as a new item code QRi. The code providing unit 74 transmits the image data of the item code QRi to the user device 10. The item code QRi is output to a paper medium by the user device 10 and attached to the shipment item Imo which is shipped from the specific industry trader TRs to the other trader TR which is the next process.

[0072] based on Figure 6 , the generation process of blockchain BC based on the above record generation function is further explained. Figure 6 In the specific example shown, each shipment item Imo shipped from company A and company B is delivered to company C as delivery item IMi. Then, the shipment item Imo produced by company C using delivery item IMi is shipped to the trader TR of the next process. In this example, company A and company B are, for example, material suppliers, and are companies that become the starting point of the supply chain SC. On the other hand, company C is, for example, a parts supplier, and is a company that becomes the middle of the supply chain SC.

[0073] In company A and company B, the time stamp code QRt prepared by the time stamp server 90 and the company code QRc distributed from the authenticator Cer are read. The hash values ​​recorded in the codes QRt and QRc are sent from the user devices 10 of each company A and B to the data management server 60. These hash values ​​are set as transaction records ReT in the blockchain BC by the chain generation unit 73. In addition, the hash value of the final block is recorded in the item code QRi and sent to each company A and B. After being printed on a paper medium, the item code QRi is attached to the shipment item IMo.

[0074] In company C, in addition to the timestamp code QRt and the company code QRc, each item code QRi attached to the delivery item IMi delivered from each company A and B is read in. Each hash value recorded in each code QRt, QRc, and QRi is sent to the data management server 60 and embedded in the blockchain BC through the chain generation unit 73. By delivering the shipment items Imo from multiple traders TR to one trader TR, the blockchain BC is not in a straight chain, but in a tree. In this case, the hash value of the final block is also recorded in the item code QRi and sent to company C. After being printed on a paper medium, the item code QRi is attached to the shipment item Imo of the trader TR heading to the next process.

[0075] The hash value recorded in each of the above company codes QRc is, for example, a character string obtained by hashing the content such as "Company A (B or C) certified by Company X". This "Company X" is the name of the certifier Cer. In addition, the hash value of the project code QRi obtained by each company A and B is, for example, a character string that can refer to a matter such as "Product by Company A on 1st, May". Similarly, the hash value of the project code QRi obtained by company C is a character string that can refer to a matter such as "Product by Company C on 3rd, May using Product by Company A on 1st, May and Product by Company B on 2nd, May".

[0076] Next, based on Figure 7 The timing diagram shown in Figure 1 and Figure 2 , the details of the chain generation process implemented through the collaboration of the various structures described above are described.

[0077] In S191 implemented by the time stamp server 90, a search for news information and acquisition of news reports are implemented, and the process proceeds to S192. In S192, a hash value used as time stamp data is generated based on the news reports acquired in S191, and the process proceeds to S193. In S193, a time stamp code QRt having at least the hash value calculated in S192 recorded therein is generated and prepared in a state that can be provided to the user device 10 or the like.

[0078] In S111 implemented by the user device 10, the company code QRc is read and the process proceeds to S112. In S112, the project code QRi is read and the process proceeds to S113. When there are multiple delivery projects IMi, the project codes QRi attached to all the delivery projects IMi are read. In addition, when the basic information code QRb is prepared in advance, the basic information code QRb is also read in S112.

[0079] In S113, the time stamp code QRt prepared in S193 is requested to be presented, displayed on the screen, and read, and the process proceeds to S114. The order of the reading process from S111 to S113 can be changed as appropriate.

[0080] In S114, the hash value of each code read in S111 to S113 and the latest position data are sent to the data management server 60 as the current transaction record ReT, and the process proceeds to S115.

[0081] In S161 implemented by the data management server 60, the transaction record ReT sent from the user device 10 in S114 is received and the process proceeds to S162. In S162, a data anomaly verification process is implemented (see Figure 5 ), for each data associated with the current delivery item IMi, after confirming that there is no abnormality, enter S163. In addition, when an abnormality is determined by the data abnormality verification process, a value indicating an error is sent to the user device 10, and a series of processes are terminated.

[0082] In S163, the block based on the transaction record ReT obtained in S161 is embedded at the end of the blockchain BC, and the process proceeds to S164. In S164, the hash value of the last block is calculated, and the process proceeds to S165. In S164, the shipment item Imo attached to the calculated hash value is recorded as an unused item. As a result, the shipment item IMo is logged as UTXO (Unspent Transaction Output) in the blockchain BC.

[0083] In S165, the hash value calculated in S164 is recorded in the item code QRi. Then, the generated item code QRi is transmitted to the user device 10 which is the transmission source of the transaction record ReT, and a series of processes are terminated.

[0084] In S115 executed by the user device 10, the item code QRi transmitted from the data management server 60 in S165 is received, and the process proceeds to S116. In S116, the item code QRi received in S115 is output, and a series of processes are terminated.

[0085] Next, based on Figure 1 , Figure 2 , Figure 8 as well as Fig. 9 The details of the record reference function of the data management server 60 are described below. The storage unit 63 of the data management server 60 stores a record reference program as one of the supply chain management programs. The data management server 60 generates provision data PD to be sent to the user terminal 110 in response to a reference request from the user terminal 110 through processing based on the record reference program. The data management server 60 cooperates with the user terminal 110 connected to the network NW to perform record query processing (reference Figure 8 ). Hereinafter, the details of the functions of the data management server 60 and the user terminal 110 related to the record search process will be described.

[0086] The data management server 60 includes functional units such as a request acquisition unit 81 , a data extraction unit 82 , a data verification unit 83 , and a data providing unit 84 based on execution of the record reference program by the processor 61 .

[0087] The request acquisition unit 81 acquires the reference request and the item data of the specific item IMs sent from the request transmission unit 122 (see S181). The data extraction unit 82 refers to the blockchain BC and identifies the transaction record ReT associated with the item data acquired by the request acquisition unit 81 (see S182). The data extraction unit 82 extracts the transaction record ReT that is on the past side of the item data in the time series in the blockchain BC.

[0088] The data extraction unit 82 obtains the main data related to the hash value of the transaction record ReT, specifically, the name of the trader TR (manufacturing plant, production line, etc.), date and time, name of the project and other information. The data extraction unit 82 can also obtain date and time information by requesting the timestamp server 90. The data extraction unit 82 organizes each main data into a tree shape by a Merkle tree based on the hash value in the blockchain BC to generate the provision data PD (refer to S184). In the provision data PD, the transaction record ReT of the later process is more configured in the upper layer, and the transaction record ReT of the previous process is more configured in the lower layer.

[0089] The data verification unit 83 determines whether the transaction record ReT extracted by the data extraction unit 82 is likely to be tampered with through data verification processing (refer to S183). The data verification unit 83 combines the hash value as the transaction record ReT according to the shape of the Merkle tree, and repeatedly calculates the Merkle route. When the hash value as the project data obtained by the request acquisition unit 81 is consistent with the hash value recalculated based on the transaction record ReT, the data verification unit 83 regards that all transaction records ReT have not been tampered with. On the other hand, when the two hash values ​​are inconsistent, the data verification unit 83 infers that the transaction record ReT is likely to be tampered with.

[0090] When the data verification unit 83 deduces that there is a possibility of tampering, the data providing unit 84 transmits a value notifying an error to the user terminal 110. On the other hand, when the data verification unit 83 determines that there is no tampering, the data providing unit 84 transmits the provision data PD generated by the data extraction unit 82 to the user terminal 110 of the request source (see S185).

[0091] The user terminal 110 is an electronic device having a computer function, such as a smartphone, a tablet terminal, or a dedicated terminal. The user terminal 110 reads, for example, an item code QRi attached to a specific item IMs such as a final product FP, and displays a past transaction record ReT indicating its circulation path. The user terminal 110 includes a camera 116, a display 117, and a control circuit 120 including a processor 111, a RAM 112, a storage unit 113, an input / output interface 114, and a bus connecting these components.

[0092] The camera 116 generates image data of the item code QRi attached to the delivery item IMi or the specific item IMs, and supplies it to the control circuit 120. The display 117 is a display device such as a liquid crystal panel, and can display various images on the screen. The display 117 has a touch panel function for accepting user operations.

[0093] The processor 111 is hardware for performing calculation processing in conjunction with the RAM 112. The storage unit 113 stores a transaction record display program capable of confirming the transaction record ReT. The transaction record display program is an application program distributed via the network NW (hereinafter referred to as the traceability confirmation application). The traceability confirmation application can be downloaded to the storage unit 113 by using the camera 116 to read a two-dimensional code recording the site information.

[0094] When the traceability confirmation application is started by inputting a user operation to the display 117, the processor 111 executes various processes associated with the tracking of the transaction record ReT by accessing the RAM 112. Specifically, in the control circuit 120, functional units such as a code extraction unit 121, a request transmission unit 122, a data reception unit 123, and a display control unit 124 are constructed based on the traceability confirmation application.

[0095] The code extraction unit 121 obtains the photographic data of the item code QRi from the camera 116. The code extraction unit 121 obtains the item data recorded in the item code QRi as a hash value by analyzing the photographic data (see S121). The request transmission unit 122 transmits the item data obtained by the code extraction unit 121 together with the reference request of the transaction record ReT to the data management server 60 (see S122).

[0096] The data receiving unit 123 receives the provision data PD returned by the data management server 60 based on the reference request of the request transmitting unit 122 (see S123). The provision data PD includes the transaction record ReT associated with the specific item IMs.

[0097] The display control unit 124 is a functional unit that controls the screen display of the display 117. The display control unit 124 generates display data (see S124) using the provision data PD received by the data receiving unit 123, and causes the display 117 to display the transaction record ReT (see S125). The display control unit 124 displays a GUI screen 130 for consulting and presenting the transaction record ReT based on the traceability confirmation application (see Fig. 9 The display control unit 124 causes the GUI screen 130 to transition based on the user's operation and the communication with the data management server 60 .

[0098] When the traceability confirmation application is started by a click operation of the user, the display control unit 124 displays a startup screen as the GUI screen 130. The startup screen displays a code recognition area 131, a re-read button 132, a consultation button 133, and an end button 134. The code recognition area 131 is a display area for displaying the captured data of the camera 116. When the user terminal 110 is operated to display the item code QRi in the code recognition area 131, the code extraction unit 121 recognizes the item code QRi. As a result, the GUI screen 130 transitions from the startup screen to the code recognition screen.

[0099] In addition to the code recognition area 131 and each click icon, the code information display area 135 is displayed on the code recognition screen. In the code information display area 135, a hash value as project data and an IP address or URL of a server to be consulted are displayed as information read from the project code QRi by the code extraction unit 121. In this state, if a click operation of the consultation button 133 is input, the GUI screen 130 transitions from the code recognition screen to the communication screen.

[0100] In the communication screen, a message such as "In consultation" is displayed. As a result of the consultation with the data management server 60, when an error notification is received, the GUI screen 130 is transferred from the communication screen to the abnormal screen. In the abnormal screen, in addition to the code information display area 135, the re-read button 132 and the end button 134, an acquisition information display area 136 is provided. In the abnormal screen, in the acquisition information display area 136, a message such as "No information. Please contact the manufacturer." is displayed.

[0101] On the other hand, if the result of the inquiry to the data management server 60 is that the provision data PD can be received, the GUI screen 130 is transferred from the communication screen to the data display screen. In the data display screen, the code information display area 135, the re-read button 132, the end button 134, and the acquisition information display area 136 are provided in the same manner as the abnormal screen. In the data display screen, the acquisition information display area 136 displays the transaction records ReT associated with the specific item IMs in a hierarchical manner.

[0102] To be specific, in the acquired information display area 136, only the transaction record ReT of the trader TR who shipped the specific item IMs among the multiple transaction records ReT included in the provision data PD is first displayed. In this state, if the user clicks the expansion button 137 displayed in the acquired information display area 136, the transaction record ReT of the previous process of the currently displayed transaction record ReT is further displayed. As described above, the user can view a deeper transaction record ReT, in other words, a more past transaction record ReT, by repeatedly clicking the expansion button 137. In addition, if multiple transaction records ReT are expanded and displayed, the acquired information display area 136 can be scrolled.

[0103] In the first embodiment described above, a hash value reflecting the previous transaction results is attached to the items traded between multiple traders TR. Thus, the amount of data attached to the items is suppressed, and the transaction records ReT of the items between traders TR are accumulated in a manner that is difficult to tamper with as the items circulate. Thus, the supply chain SC can be properly managed.

[0104] Furthermore, if a hash value is used as item data as in the first embodiment, even if the amount of information that can be recorded in the item code QRi is limited to, for example, several tens of kilobytes, the item data can be recorded in the item code QRi. Thus, it is easy to utilize the advantages of the two-dimensional code, so that the item data inherent to the newly created shipment item IMo is sequentially attached to the shipment item IMo and circulated together with the shipment item IMo. Therefore, the feasibility of the management of the supply chain SC using the hash value can be ensured.

[0105] In addition, in the first embodiment, the hash value attached to the delivery item Imo is calculated based on the timestamp data related to the date and time when the delivery item IMi is under the specific industry TRs in addition to the item data and company data. As a result, in the transaction record ReT, the time information indicating the time of the transaction is still difficult to be tampered with. Therefore, the reliability of the supply chain SC can be further improved.

[0106] Furthermore, in the first embodiment, fraud in transactions between traders TR is detected based on the chronological relationship between dates and times indicated by a plurality of time stamp data. Thus, fraud such as reversal can be detected sequentially. As a result, the reliability of the supply chain SC can be further improved.

[0107] In addition, the company data of the first embodiment is the inherent content given by the certifier Cer to each trader TR. Moreover, for the company data provided by the user device 10, it is determined whether it is legitimate data. In this way, it is possible to prevent products, parts, raw materials MAT, etc. of industries not recognized by the certifier Cer from being mixed into the supply chain SC with high reliability.

[0108] In the first embodiment, the location data is further used as the calculation of the hash value of the item data. This makes it possible to detect fraud related to the place of origin and the place of production with high reliability. As a result, the reliability of the supply chain SC can be further improved.

[0109] Furthermore, in the first embodiment, the idea of ​​UTXO in the blockchain BC is used to detect duplication of item data sent to the data management server 60. Specifically, for the shipment item IMo produced and manufactured using the delivery item IMi, when a mismatch occurs in terms of quantity and weight, such a mismatch can be detected by using the idea of ​​UTXO related to double payment prevention of the blockchain BC. As described above, for the shipment item IMo, by sequentially managing whether it is an unused item, it is almost impossible to mix improper materials and products. Therefore, the reliability of the supply chain SC can be further improved.

[0110] In the first embodiment, by reading item data attached to specific items IMs, transaction records ReT associated with the specific items IMs can be acquired from the data management server 60. Therefore, the transaction records of items between traders TR can be referenced from the user side while suppressing the amount of data attached to the items.

[0111] In the first embodiment, since the transaction record ReT is displayed in a hierarchical form reflecting the distribution process of the specific item IMs, the user can easily understand the transaction record ReT. With the improvement of convenience as described above, it is easy to achieve appropriate management of the supply chain SC.

[0112] Furthermore, in the first embodiment, the transaction record ReT associated with the specific item IMs is extracted from the accumulated transaction records ReT based on the reference request sent from the user terminal 110. And the provision data PD based on the extracted transaction record ReT is provided to the user terminal 110. As described above, by organizing the required transaction record ReT by the data management server 60, the user can easily access the transaction record ReT that he wants to refer to.

[0113] In the above-mentioned embodiment, the project code QRi is equivalent to a "two-dimensional code", the company data is equivalent to "node identification data", and the specific industry person TRs is equivalent to a "specific person". In addition, the user device 10 is equivalent to a "user node", the information acquisition unit 21 is equivalent to an "acquisition unit", and the information sending unit 22 is equivalent to a "sending unit". In addition, the data management server 60 is equivalent to a "host node", and the server device 60a and the processing circuit 10a are respectively equivalent to a "computer". In addition, the chain generation unit 73 is equivalent to an "operation unit", the code providing unit 74 is equivalent to a "providing unit", and the user terminal 110 is equivalent to a "request source".

[0114] <Application example of the first embodiment>

[0115] The following is based on Figures 10 to 12 as well as Figure 8 , an application example of applying the supply chain management method of the first embodiment to the management of transaction records ReT of a supply chain SC for supplying bread is described. Fig.12 The chain generation process shown is Figure 7 Modification of the chain generation process shown. In the chain generation process of this application example, the data management server 60 obtains a time stamp from the time stamp server 90 .

[0116] The supply chain SC includes multiple traders TR related to the production and sale of bread as the final product FP. As an example, seed producers, wheat farmers, wheat flour manufacturers, bread manufacturers, and convenience stores are equivalent to traders TR constituting the supply chain SC of bread, forming the logistics path of bread (see Fig.10 ).

[0117] Specifically, in the logistics path of bread, (1) the seed producer ships wheat seeds to wheat farmers, (2) the wheat farmers ship the wheat grown from the seeds to the wheat flour manufacturer, (3) the wheat flour manufacturer ships the wheat flour made from the processed wheat to the bread manufacturer. Furthermore, (4) the bread manufacturer ships the bread made from the wheat flour to the convenience store, and (5) the convenience store sells the purchased bread to the consumer. Then, (6) the consumer can confirm the raw material MAT, processing steps, and distribution steps of the purchased bread.

[0118] The seed producer of (1) above prepares in advance a basic information code QRb based on initial setting data. The issuance of the basic information code QRb is performed by initial setting processing (see Fig.11 ) is implemented. In the initial setting process, the user device 10 obtains information such as land, equipment, pesticides and fertilizers required for the production of seeds as initial setting data (refer to S101). The user device 10 prepares the initial setting data, for example, by reading in text data, etc., and manually inputting by the staff of the seed producer. The user device 10 sends the acquired initial setting data to the data management server 60 via the network (refer to S102). In addition, the information on the land can use the location data such as the residence of the seed producer and GPS.

[0119] The data management server 60 receives and obtains the initial setting data sent from the user device 10 (refer to S151). The data management server 60 lists the acquired initial setting data in a prescribed data format (refer to S152), and generates a hash value related to the list of initial setting data (refer to S153). The data management server 60 saves the list of initial setting data in a state that can be compared from the hash value. In addition, the data management server 60 sets the generated hash value in the blockchain BC (refer to S154). The hash value of the initial setting data of the trader TR who supplies the raw material MAT is embedded in the first block of the blockchain BC. The data management server 60 generates a basic information code QRb that records the hash value and sends it to the user device 10 of the seed producer (refer to S155).

[0120] The user device 10 of the seed producer receives and obtains the basic information code QRb sent from the data management server 60 (see S103). The user device 10 outputs the received basic information code QRb to a paper medium, for example, by printing (see S104). Through the above, the seed producer prepares the basic information code QRb.

[0121] Here, information other than the hash value based on the initial setting data may also be recorded in the basic information code QRb. For example, the initial setting data logged in the blockchain BC, that is, the information on the land, equipment, pesticides, and fertilizers required for seed production, may also be recorded in the basic information code QRb in the form of text data or image data. Furthermore, the basic information code QRb may also directly record the initial setting data identical to the content logged in the blockchain BC in the form of text data or image data instead of the hash value.

[0122] When a seed producer ships the produced seeds, the chain generation process is performed by the cooperation of the user device 10 of the seed producer, the data management server 60 and the time stamp server 90 (see Fig.12 ). The user device 10 of the seed producer sequentially reads the company code QRc issued by the certifier Cer and the pre-prepared basic information code QRb (refer to S101 and S102). The user device 10 sends the hash value of each code obtained by reading as the current transaction record ReT to the data management server 60 (refer to S104).

[0123] In addition, at least one of the company data and the initial setting data may be pre-registered in the user device 10. In this manner, the storage unit 13 (refer to Figure 2 )The read data are sent to the data management server 60.

[0124] The data management server 60 receives the hash value sent from the user device 10 of the seed producer and obtains it as a transaction record ReT (see S161). The data management server 60 uses the acquisition of the transaction record ReT as a trigger to request the time stamp server 90 to provide the time stamp code QRt (or time stamp data). The data management server 60 obtains the time stamp code QRt provided based on the request (see S161a and S193a).

[0125] The data management server 60 performs data anomaly verification processing (see S162 and Figure 5 ). In the data anomaly verification process of the transaction record ReT obtained from the trader TR that supplies the raw material MAT, some processes such as confirming whether it is an unused item and matching the time series can be omitted (refer to Figure 5S34~S34). If the data management server 60 confirms that there is no abnormality in each data, it will embed the block of transaction records ReT based on the initial setting data and time stamp data at the end of the blockchain BC (refer to S163).

[0126] Furthermore, the data management server 60 calculates the hash value of the last block (see S164), and records the shipment item Imo to which the calculated hash value is attached as an unused item. The data management server 60 transmits the item code QRi recorded with the calculated hash value to the user device 10 of the seed producer (see S165).

[0127] The user device 10 of the seed producer receives the item code QRi sent from the data management server 60 (see S115), and outputs the received item code QRi to a paper medium by printing or the like (see S116). The seed producer attaches the printed item code QRi to the packaging of the seeds or the like, and ships the seeds to the wheat farmers.

[0128] For the wheat farmer in (2) above, the item code QRi attached to the package of the purchased seeds and the company code QRc issued to the wheat farmer from the certifier Cer are read by the user device 10 (refer to S101 and S102). In the case where the wheat farmer has logged in the initial setting data, the basic information code QRb is further read by the user device 10. For example, the wheat farmer can log in the information of the land where wheat is cultivated to the data management server 60. The user device 10 of the wheat farmer sends each hash value read from each code to the user device 10 (refer to S104).

[0129] The data management server 60 obtains the hash value and the like sent from the user device 10 of the wheat farmer as the transaction record ReT (see S161). In addition, the data management server 60 obtains the timestamp for recording the acquisition date and time of the hash value from the timestamp server 90 (see S161a and S193a). The data management server 60 performs the data anomaly verification process (see S162 and Figure 5 ) to confirm that there is no abnormality. Then, the data management server 60 embeds the block of transaction records ReT based on project data, initial setting data, and timestamp data at the end of the blockchain BC (refer to S163). In addition, the data management server 60 calculates the hash value of the last block (refer to S164), and sends the project code QRi recording the calculated hash value to the user device 10 of the wheat farmer (refer to S165).

[0130] The wheat farmer's user device 10 receives the item code QRi sent from the data management server 60 (see S115), and outputs the received item code QRi to a paper medium by printing or the like (see S116). The wheat farmer attaches the printed item code QRi to the packaging of wheat, etc., and ships the wheat to the wheat flour manufacturer.

[0131] In the wheat flour manufacturer of (3) above, the item code QRi attached to the package of the purchased wheat and the company code QRc issued to the wheat flour manufacturer from the authenticator Cer are read by the user device 10 (refer to S101 and S102). In the case where the wheat flour manufacturer has logged in the initial setting data, the basic information code QRb is further read by the user device 10. For example, the wheat flour manufacturer can log in information such as the equipment and method for producing wheat flour to the data management server 60. The user device 10 of the wheat flour manufacturer sends each hash value read from each code to the user device 10 (refer to S104).

[0132] The data management server 60 obtains the hash value and the like sent from the user device 10 of the wheat flour manufacturer as the transaction record ReT (see S161). Furthermore, the data management server 60 obtains the timestamp for recording the date and time of obtaining the hash value from the timestamp server 90 (see S161a and S193a). The data management server 60 performs the data anomaly verification process (see S162 and Figure 5 ) confirms that there is no abnormality. In addition, the data management server 60 embeds the block of transaction records ReT based on the project data, initial setting data, and timestamp data at the end of the blockchain BC (refer to S163). In addition, the data management server 60 calculates the hash value of the last block (refer to S164), and sends the project code QRi recording the calculated hash value to the user device 10 of the wheat flour manufacturer (refer to S165).

[0133] The user device 10 of the flour manufacturer receives the item code QRi sent from the data management server 60 (see S115), and outputs the received item code QRi to a paper medium by printing or the like (see S116). The flour manufacturer attaches the printed item code QRi to the packaging of the flour or the like, and ships the flour to the bread manufacturer.

[0134] In the bread manufacturer of (4) above, the company code QRc issued from the authenticator Cer to the bread manufacturer is read by the user device 10 (refer to S101). In addition, the item codes QRi attached to each package of wheat flour, yeast, salt, water and sugar purchased as raw materials for bread are read in sequence by the user device 10 (refer to S102). In the case where the bread manufacturer has logged in the initial setting data, the basic information code QRb is further read by the user device 10. For example, the bread manufacturer can log information such as the equipment and method for producing bread to the data management server 60. The user device 10 of the bread manufacturer sends each hash value read from each code to the user device 10 (refer to S104).

[0135] The data management server 60 obtains the hash value and the like sent from the user device 10 of the bread manufacturer as the transaction record ReT (see S161). Furthermore, the data management server 60 obtains the timestamp for recording the date and time of obtaining the hash value from the timestamp server 90 (see S161a and S193a). The data management server 60 performs the data anomaly verification process (see S162 and Figure 5 ) confirms that there is no abnormality. In addition, the data management server 60 embeds a block of transaction records ReT based on project data, initial setting data, and timestamp data at the end of the blockchain BC (refer to S163).

[0136] Here, as described above, the transaction record ReT obtained from the bread manufacturer contains project data of multiple raw materials such as wheat flour, yeast, salt, water and sugar. As a result, in the data management server 60, multiple blockchains BC that accumulate transaction records ReT of each raw material are aggregated into one through processing in the bread manufacturer. As a result, the data structure of the blockchain BC (Distributed Ledger) is not a one-to-one linear structure that connects each block, but presents a tree-like or radial form in which multiple blocks are connected to one block. Through such a data structure, it is possible to track each raw material from one project data, thereby achieving an improvement in the transparency of the circulation process for users and the ease of retrieval.

[0137] In addition, wheat flour can also be used for foods other than bread, such as ingredients for udon noodles. Therefore, it can also be considered that the information of a hash value generated as item data is spread to multiple items in the next process. In this case, the data structure of blockchain BC presents a one-to-many tree or radial form.

[0138] The data management server 60 calculates the hash value of the last block associated with the transaction record ReT of the plurality of ingredients (see S164 ), and transmits the item code QRi recording the calculated hash value to the user device 10 of the bread maker (see S165 ).

[0139] The user device 10 of the bread manufacturer receives the item code QRi sent from the data management server 60 (see S115), and outputs the received item code QRi to a paper medium by printing or the like (see S116). The bread manufacturer attaches the printed item code QRi to the packaging of the bread, etc., and ships the bread to a retail store such as a convenience store.

[0140] In the convenience store of (5) above, the company code QRc issued to the convenience store by the authenticator Cer and the item code QRi attached to the package of the purchased bread are read by the user device 10 (refer to S101 and S102). In the case where the convenience store has logged in the initial setting data, the basic information code QRb is further read by the user device 10. For example, the convenience store can log information such as the store name to the data management server 60. The user device 10 of the convenience store sends each hash value read from each code to the user device 10 (refer to S104).

[0141] The data management server 60 obtains the hash value and the like sent from the user device 10 of the convenience store as a transaction record ReT (see S161). In addition, the data management server 60 obtains a timestamp for recording the date and time of obtaining the hash value from the timestamp server 90 (see S161a and S193a). The data management server 60 performs data anomaly verification processing (see S162 and Figure 5 ) confirms that there is no abnormality. In addition, the data management server 60 embeds a block of transaction records ReT based on item data, initial setting data, and timestamp data at the end of the blockchain BC (see S163). Then, the data management server 60 calculates the hash value of the last block (see S164), and sends the item code QRi recording the calculated hash value to the user device 10 of the convenience store (see S165).

[0142] The user device 10 of the convenience store receives the item code QRi transmitted from the data management server 60 (see S115), and outputs the received item code QRi to a paper medium by printing or the like (see S116). The clerk of the convenience store attaches the printed item code QRi to the package of the bread, etc., and displays it on the shelf, etc. Thus, the bread is provided to the consumer CST.

[0143] The consumer CST of (6) can query the transaction record ReT of bread by installing the traceability confirmation application on the user terminal 110. The consumer CST of bread reads the item code QRi attached to the bread by executing the user terminal 110 of the traceability confirmation application. As a result, the user terminal 110 obtains the item data (hash value) recorded in the item code QRi (refer to Figure 8 S121), and sends the acquired project data together with the reference request to the data management server 60 (see S122).

[0144] The data management server 60 obtains the reference request and the item data of the bread sent from the user terminal 110 (see S181). The data management server 60 determines the blockchain BC related to the acquired item data and the transaction record ReT accumulated in the blockchain BC (see S182). After verifying the determined transaction record ReT (see S183), the data management server 60 generates provision data PD that reproduces the circulation path of the bread in a tree shape (see S184). The data management server 60 sends the generated provision data PD to the user terminal 110 of the request source (see S185).

[0145] When the user terminal 110 receives the provision data PD based on the reference request from the data management server 60 (see S123), it generates display data using the provision data PD (see S124). The user terminal 110 displays the acquired information display area 136 (see S126) of the display 117 based on the display data. Fig. 9 ) displays the transaction records ReT accumulated during the circulation of bread (refer to S125).

[0146] In the application example of the first embodiment described above, according to the management method of adding a hash value reflecting the transaction result to an item, the amount of data added to the item is suppressed, and the past transaction records ReT from the raw material MAT to the final product FP are accumulated in a manner that is difficult to be tampered with. Therefore, the supply chain SC can be properly managed.

[0147] In addition, in the above application example, the distribution path of bread from the raw material MAT (seed of wheat) to the final product FP (bread) delivered to the consumer CST is described as a specific example, but the management method disclosed in the first embodiment can also be applied to the supply chain SC of other items. As an example, the above management method can be applied to the supply chain of communication terminals, the supply chain of new and used cars, the supply chain of processed foods, food materials, beverages, alcoholic beverages, fishery products and meat, and the supply chain of pharmaceuticals.

[0148] Furthermore, the above-mentioned supply chain management method is not limited to the supply chain SC of tangible objects, but can also be applied to the supply chain SC of intangible objects. Specifically, the above-mentioned management method can also be applied to the supply chain related to e-commerce via the Internet, the supply chain related to the recipient information in the transfer of securities such as bills, and the supply chain related to the procurement of building materials to the construction of buildings.

[0149] In addition, even the supply chain SC of services can be managed using blockchain BC. Specifically, the providers and beneficiaries of services are coded in advance, and by reading the code when the services are used or provided, the provision and enjoyment relationship of services can be recorded as a transaction record ReT. As an example, the process of technology inheritance related to traditional crafts, in other words, the pedigree of the master-apprentice relationship, the relationship between the provider and the beneficiary of knowledge and technology related to specific qualifications, etc. can be managed using blockchain BC. In addition, for traditional crafts made by the accumulation of the craftsmanship of multiple craftsmen, the historical information of the processing implemented by each craftsman in charge of each process can also be recorded using blockchain BC. In this case, the value of the finished crafts can be permanently guaranteed. In addition, verbal promises such as batons on SNS can also be recorded through blockchain BC.

[0150] (Second Embodiment)

[0151] Fig.13 as well as Fig.14 The second embodiment of the present disclosure shown is a modified example of the first embodiment. In the chain generation process based on the record generation program of the second embodiment (refer to Fig.13 ), the issuance of the hash value of each trader TR and the item code QRi is omitted. In addition, in the record query processing based on the record reference program (refer to Fig.14 ), the transaction record ReT of the later process than the issuance of the item code QRi is extracted together with the past transaction record ReT. Figure 1 etc. will explain the chain generation process and record query process of the second embodiment.

[0152] In chain generation processing (refer to Fig.13 ) in the data management server 60, if the data management server 60 receives TRs from specific industries (refer to Figure 1 ) obtains the project data and company data (see S161), and obtains the timestamp data from the timestamp server 90 (see S161a). The data management server 60 determines the blockchain BC that manages the supply chain SC of the project to which the project data is attached, and performs verification processing for data anomalies (see S162 and Figure 5). If the data management server 60 confirms that there is no abnormality in the data, it links the block of transaction records ReT based on project data and timestamp data to the end of the blockchain BC (refer to S263). As a result, the current transaction records ReT (for example, processing information) in the specific industry TRs are associated with the project data and accumulated in the blockchain BC. In the second embodiment, the transaction records ReT in multiple traders TR are associated with one type of project data.

[0153] When the data management server 60 completes the registration of the current transaction record ReT, it determines whether to allow the continued use of the project data. The data management server 60 sends a permission notification to the user device 10 of the specific industry trader TRs, which is the source of the project data, indicating that the continued use of the project data is permitted (see S264).

[0154] When the user device 10 of the specific trader TRs receives the permission notification sent from the data management server 60 (see S215), it determines to continue to use the project data attached to the delivery project IMi (see S216). As a result, in the specific trader TRs, the project code QRi attached to the delivery project IMi is directly used as the project code QRi attached to the shipment project Imo. In this case, the user device 10 notifies the worker to continue to use the project data through a message such as a sound or a screen display.

[0155] Here, when it is difficult to continue to use the project code QRi physically even if it is decided to continue to use the project data, the user device 10 can re-output the same project code QRi as the project code attached to the delivery item IMi. As an example, when the project code QRi attached to the delivery item IMi is damaged or stained and it is determined that it hinders the reading of the project data, the user device 10 prints the project code QRi for re-pasting it on the shipment item IMo. In addition, when the packaging of the shipment item IMo is different from the packaging of the delivery item IMi, the user device 10 can print the project code QRi that records the same project data.

[0156] In record query processing (refer to Fig.14 ), the data management server 60 obtains the reference request and project data sent from the user terminal 110 (refer to S281). The data management server 60 determines the blockchain BC of the project to which the acquired project data is attached. The data management server 60 refers to the information related to the blockchain BC and determines whether the acquired project data is continued to be used by multiple traders TR (refer to S282). Specifically, when the transaction records ReT of multiple traders TR are related to the acquired project data, the data management server 60 determines that the project data is continued to be used.

[0157] The data management server 60 extracts the transaction record ReT associated with the acquired project data from the multiple transaction records ReT managed using the blockchain BC (refer to S283). Specifically, when the project data is related to the transaction record ReT of only one trader TR, the data management server 60 selects the transaction record ReT in the trader TR and the transaction record ReT on the past side (previous process) of the transaction record ReT as the provision object. On the other hand, when the project data is continuously used by multiple traders TR and is related to the transaction records ReT of multiple traders TR, all the transaction records ReT in the multiple traders TR are selected as the provision object together with the past transaction records ReT.

[0158] The data management server 60 performs data verification processing on the selected transaction record ReT and the like (see S284), and generates provision data PD based on the extracted transaction record ReT (see S285). Then, the data management server 60 provides the generated provision data PD to the user terminal 110, which is the request source of the reference request (see S286). When the user device 10 obtains the provision data PD sent from the data management server 60, the transaction record ReT associated with the item is displayed in the same manner as in the first embodiment (see S123 to S125).

[0159] In the second embodiment described above, the item data attached to the shipment item Imo is continuously used by multiple traders TR. Therefore, even if the circulation process is carried out, the amount of item data is difficult to increase. On the other hand, in the blockchain BC, the transaction records ReT of multiple traders TR are accumulated in association with one item data that is continuously used. Thus, the amount of data attached to the item is suppressed, and the transaction records ReT of the item between the traders TR are accumulated in the blockchain BC in a manner that is difficult to tamper with as the item circulates. Therefore, in the second embodiment, the supply chain SC can be properly managed.

[0160] In addition, in the second embodiment, the transaction records ReT of multiple traders TR can be associated with one project data. Moreover, for a reference request, each transaction record ReT of all multiple traders TR using the project data is extracted, and these transaction records ReT are provided to the request source. As a result, the transaction record ReT (for example, processing information, etc.) of the trader TR who last used the project data is always included in the provision data PD. Therefore, even if the project code QRi (project data) attached to the delivery project IMi is continuously used for the shipment project IMo, it is possible to provide an appropriate transaction record ReT for the reference request received together with the project data.

[0161] To explain in detail, when the project data is continuously used, the project data (hash value) attached to the project processed by the specific industry TRs does not reflect the information of the processing implemented by the specific industry TRs. However, on the blockchain BC, the information of the processing implemented by the specific industry TRs is reflected. That is, the information such as the raw materials, processing, producers, processors, and time of the processed products shipped from the specific industry TRs is recorded in a chain on the blockchain BC. Therefore, if the project code QRi attached to the project (for example, the raw material of a certain process) is read, even if the project code QRi is a project code issued multiple processes ago, all processes up to the previous process can be referenced.

[0162] Specifically, in a supply chain SC where a plurality of traders TR perform processing steps, the item code QRi attached to the processed product of each step remains the item code QRi issued to the first trader TR as the starting point of the step. This simplifies the issuance of the item code QRi.

[0163] In this case, the item code QRi that continues to be used reflects only the raw material information and does not reflect the processing information. However, if the trader TR of the supply chain SC accesses the blockchain BC, it can obtain the details of the processing implemented in the previous process, the information of the raw materials used, etc. Therefore, even with a single item code QRi, the entire supply chain SC or a specific section can be managed, and the traceability of the raw materials and processing steps can be ensured.

[0164] As an example, in the supply chain SC related to the supply of bread (refer to Fig.10 ), the item code QRi (item data) which reflects the information of wheat as a raw material has been used. Therefore, the bread manufacturer adds the item code QRi which reflects the information of wheat to the product, that is, bread.

[0165] Even in this case, the processing information of the flour manufacturer and the bread manufacturer is accumulated in the blockchain BC. Therefore, the bread manufacturer can refer to the processing history up to the previous process by using the item code QRi attached to the flour. Similarly, the consumer CST of bread, which becomes the final user, can refer to the processing information of the bread manufacturer by using the item code QRi attached to the bread. As described above, the issuance of the item code QRi that embodies the processing information of the flour manufacturer and the bread manufacturer can be omitted.

[0166] (Third Embodiment)

[0167] The third embodiment of the present disclosure is another variation of the first embodiment. The supply chain management system 100 of the third embodiment is designed on the premise of coexistence with other management systems that manage the supply chain SC. As an example, the other management system is a management system that does not use blockchain BC (hereinafter, the old management system).

[0168] In accordance with such a system configuration, the item code QRi of the third embodiment includes both information for management in the old management system and information (item data) for management in the supply chain management system 100. Specifically, in the two-dimensional code used as the item code QRi, a plurality of (two) registration data areas are defined.

[0169] In one area (hereinafter referred to as the first area), information used in the old management system is recorded. As an example, in the first area, the format of the first area, the number of data, the data body, and the terminal symbol of the first area are recorded in sequence. In the other area (hereinafter referred to as the second area), information used in the supply chain management system 100 is recorded. As an example, in the second area, the format of the data in the second area, the number of data, the data body, and the terminal symbol of the second area are recorded in sequence.

[0170] Furthermore, the second area is a hidden area that cannot be read in the old management system. Therefore, the data recorded in the second area can only be used by the user device 10 of the supply chain management system 100. As an example, by changing the reflectivity of the second area of ​​the item code QRi, the second area is hidden from the terminal of the old management system. In this case, the reflectivity of the second area (hidden area) is lower than the reflectivity of the first area (public area).

[0171] If the above item code QRi is added to the circulation item, the terminal of the old management system can selectively read only the information in the first area from the item code QRi when uploading the information of the item to the server of the old management system. In other words, the terminal of the old management system can intentionally ignore the information in the second area.

[0172] On the other hand, the reader 17 of the user device 10 can read the hidden portion of the second area. The user device 10 can ignore the information read from the first area by software and selectively send the item data read from the second area to the data management server 60.

[0173] In addition, the user device 10 is configured to output (print) the project code QRi having information of both systems. In detail, the user device 10 obtains the project data generated in a processable format such as an image form, a text form, and a program code form from the data management server 60. In addition, the user device 10 obtains the output data used in the old management system from the server of the old management system. The user device 10 generates the project code QRi in which the output data of the old management system and the project data are recorded in the first area and the second area, respectively, and prints the project code QRi through the printer 19.

[0174] In addition, the printing of the item code QRi can also be implemented through the terminal of the old management system. In this case, the user device 10 provides the item data to the terminal in a format that can be processed by the terminal of the old management system. As a result, the terminal of the old management system can output the item code QRi having management information used in both systems from the issuer or the like.

[0175] The third embodiment described above can also produce the same effects as the first embodiment, and the supply chain SC can be appropriately managed by using the item code QRi having information for both systems.

[0176] In addition, in the third embodiment, the information in the second area cannot be read from the terminal of the existing old management system. Therefore, it is difficult to produce a bad situation in which the information is read by the terminal of the old management system or the user device 10 because the item code QRi contains both types of information. According to the above structure, the operation of the supply chain management system 100 can be coordinated and started with the old management system without making changes to the existing old management system. Therefore, it is possible to realize the supply chain management system 100 that improves the compatibility with the existing old management system.

[0177] Here, the management system to which the first area and the second area are respectively allocated can also be changed. As an example, assume that after the operation of the supply chain management system 100 is stabilized, another management system (hereinafter referred to as the future system) that is newer than the management system 100 is introduced. In this case, the allocation of the recording area can be changed in such a way that the information (project data) used for the supply chain management system 100 is recorded in the first area, and the information used for the future system is recorded in the second area. As described above, if the recording area of ​​the information is moved from the hidden area to the public area in sequence in coordination with the update of the management system, it can contribute to a smooth system update.

[0178] As technical features related to the third embodiment described above, the following appendix is ​​further disclosed.

[0179] (Appendix 1)

[0180] An information code is attached to an item traded between each of the traders in a supply chain (SC) constructed by including a plurality of traders (TR), and is read by readers of a plurality of management systems that manage the supply chain.

[0181] The above information codes include:

[0182] a first area, read by a first reader, in which first information used in a first management system is recorded; and

[0183] The second area, which is read by the second reader, records second information used in the second management system.

[0184] In the information code (QR code, barcode, etc.) described above (Appendix 1), the second area is not recognized by the first reader. In the first area, a terminal symbol is provided to notify the first reader of the end of reading. In the reading sequence of the first reader, the second area is arranged behind the terminal symbol of the first area. On the other hand, the second reader excludes the first information recorded in the first area from the recognition object, and takes the second area behind the terminal symbol as the recognition object.

[0185] Furthermore, in addition to the first area and the second area, a plurality of recording areas (third area, fourth area, etc.) may be provided in the information code. In this case, the third area records the third information used in the third management system. Similarly, the fourth area records the fourth information used in the fourth management system. As described above, a plurality of recording areas may be provided in the information code according to the number of management systems that process transaction records of items. As a result, each recording area of ​​the information code may function as a dedicated recording area when the management system is updated, or as a dedicated recording area for management systems of multiple retailers that process items.

[0186] (Other Embodiments)

[0187] As mentioned above, although several embodiments of the present disclosure have been described, the present disclosure is not to be construed as being limited to the above embodiments, and can be applied to various embodiments and combinations within a scope not departing from the gist of the present disclosure.

[0188] In the first variation of the above-mentioned embodiment, the RFID (radio frequency identifier) ​​technology is used to realize the attachment of item data to the circulation item. In this first variation, the data recording medium attached to the circulation item uses an RFID tag instead of a paper medium printed with a two-dimensional code. When using RFID, the reader 17 of the user device 10 is configured to read the item data recorded on the RFID tag through short-range wireless communication. In addition, the user device 10 is equipped with a writer that can rewrite the information recorded on the RFID tag instead of the printer 19.

[0189] The code output unit 24 uses a writer to record the new hash value received by the code receiving unit 23 from the data management server 60 on the RFID tag attached to the shipment item Imo. Such processing replaces the processing of the data management server 60 that generates the item code QRi in the above embodiment (see S165), and is equivalent to a processing step of "recording the item data containing at least the hash value".

[0190] By using RFID as described above, even if the RFID tag cannot be visually confirmed, for example, the item data can be remotely read by the reader 17. In addition, by repeatedly overwriting the hash value as the item data, the work of printing and pasting the two-dimensional code can be omitted.

[0191] In addition, a QR code may be used in one part of the supply chain SC, and an RFID tag may be used in another part. In addition, both the QR code and the RFID tag may be attached to the item. Furthermore, a storage medium different from the QR code and the RFID tag may be used as a medium for storing hash values ​​and circulated together with the item.

[0192] Furthermore, means other than QR codes and RFID can be used to attach project data (hash values) to projects. Specifically, instead of labels, information embodying hash values ​​can be embedded in the project itself through branding, laser engraving, cutting, and other processing. In addition, media that record hash values ​​using biological methods or inorganic chemical methods can be used. Specifically, a method of spray coating can be used in a manner that does not cause physiological effects on the project using DNA information, molecular structure, element ratio, etc. that embody hash values, or a method of using or attaching a metal material having component information that embodies hash values ​​to a part of the project.

[0193] As described in the above-mentioned embodiment, the process of reading in the project code QRi, the basic information code QRb, and the company code QRc, respectively, and uploading these data to the blockchain BC can be appropriately omitted. Specifically, in variant example 2, in the storage unit 13 of the user device 10, hash values ​​recorded in the basic information code QRb and the company code QRc are pre-registered. When the user device 10 reads the project code QRi reflecting the commodity information of the delivery project, it sends each hash value read from the storage unit 13 to the data management server 60. Therefore, even if the reading operation of the company code QRc, etc. performed by the reader 17 is omitted, the company data (hash value), etc. are notified to the data management server 60 in sequence together with the project data. Based on the above, the workload for leaving the transaction record ReT can be reduced.

[0194] In the third variation of the second embodiment, the item code QRi is printed on a reusable paper medium. Therefore, even when different packages are used for the delivery item IMi and the shipment item Imo, the item code QRi peeled off from the delivery item IMi can be re-pasted to the shipment item IMo, and the same item code QRi can be used physically. In addition, the paper medium on which the item code QRi is printed can be a medium formed by overlapping multiple sheets of paper with a transfer function, or a medium that can be partially cut off. If such a paper medium is used, although a sheet or a portion of the paper medium may be peeled off during circulation between traders, the same item code QRi can be used continuously.

[0195] In addition, the second embodiment has an advantage in that the issuance of the item code QRi can be omitted compared to the first embodiment. On the other hand, the first embodiment has an advantage in that the search process of the transaction record ReT corresponding to the item data can be reduced compared to the second embodiment. In addition, the first embodiment has an advantage in that the risk of the item code QRi being difficult to read due to physical damage or the like is suppressed.

[0196] As described in the third embodiment, when the existing old management system is in operation, if you want to introduce a new supply chain management system 100 using blockchain BC, the old management system needs to be significantly rebuilt. In this case, time is also required for the rebuilt. This makes it difficult to introduce the supply chain management system 100 using blockchain BC.

[0197] Therefore, in the fourth variation of the above embodiment, the item code QRi of the supply chain management system 100 is annotated or covered with the information of the old management system and circulated together with the item. In detail, the user device 10 of the fourth variation sends the item code QRi as image data to a printer 19 or other issuer, and outputs it to a paper medium. The printed item code QRi is attached to or covered on the package. According to such a method, the compatibility of the new and old systems will not become a problem, and the traceability management using the blockchain can be easily performed.

[0198] In the above example, the information recorded in the blockchain is sent to the user device 10 in the form of a QR code image. However, the project data may be sent to the user device 10 or an issuer such as a printer 19 in various data formats such as text format, program code format, etc. instead of in the form of an image.

[0199] In the fifth variation of the above embodiment, the calculation of the Merkle route does not use the hash value of the timestamp data. In the sixth variation of the above embodiment, the calculation of the Merkle route does not use the hash value based on the location data. As described above, the timestamp data and the location data may be used only for abnormality detection when receiving data, and may not be embedded in the blockchain BC. In addition, the timestamp data and the location data may not be obtained.

[0200] In the modification 7 of the above embodiment, the reading of the time stamp code QRt by the user device 10 is omitted. The data management server 60 receives the time stamp data as a hash value from the time stamp server 90 based on the acquisition of the transaction record ReT from the user device 10. In addition, in the modification 8 of the above embodiment, the hash value as the time stamp data to be sent to the user device 10 is sent to the data management server 60 together with the item data in coordination with the transmission of the item code QRi. As described above, by automatically acquiring the time stamp data, the code reading work in the trader TR can be reduced.

[0201] In the variation 9 of the above embodiment, the data anomaly verification process in the chain generation process (see S162) is omitted. The record verification unit 72 of the variation 9 is independent of the chain generation process and repeatedly performs the data anomaly verification process on the acquired transaction record ReT. In addition, in the variation 7 of the above embodiment, the data verification process in the record query process (see S183) is omitted. The data verification unit 83 of the variation 10 is independent of the record query process and repeatedly performs the data verification process on the accumulated transaction record ReT.

[0202] The node identification data (company data) used in the variant 11 of the above embodiment may also be based on a hash value of only the company name. Alternatively, the hash value may be generated as company data in the data management server 60 using identification information related to the user device 10. As described above, the distribution of the company code QRc indicating that the authenticator Cer has recognized the trader TR may also be omitted.

[0203] In the GUI screen 130 of the modification 12 of the above embodiment, the transaction records ReT returned for the reference request are displayed at a glance. Specifically, in the modification 12, the date and time related to the timestamp data are displayed in sequence starting from the new (or old) transaction record ReT. As in the above modification 9, the display method of the transaction record ReT is not limited to the tree (hierarchical) form, and can also be changed appropriately. In addition, the GUI screen 130 can also be changed appropriately according to the type of the user terminal 110.

[0204] The items that can be referenced by the user terminal 110 in the transaction record ReT are not limited to the final product FP. For example, the module supplier can also use the item code QRi attached to the delivery item IMi to reference the transaction record ReT of the delivery item IMi. Furthermore, the user device 10 can also be provided with a function of referring to the transaction record ReT of the delivery item IMi.

[0205] As described above, the trader TR is not limited to the manufacturing company. For example, in the modification 13 of the above embodiment, after the vehicle as the final product FP is delivered to the user, the maintenance history and the history of parts replacement at the dealer are sent as the transaction record ReT from the dealer's user device 10 to the data management server 60. The data management server 60 connects the block based on the new transaction record ReT to the blockchain generated when the vehicle is manufactured. The data management server 60 generates an item code QRi recording the hash value of the final block and sends it to the dealer's user device 10. If a system that adds the item code QRi to vehicle verification is used, a supply chain SC with high reliability, including maintenance of the final product FP, can be constructed.

[0206] Furthermore, in the variant 14 of the above-mentioned embodiment, vehicle inspection operators, resellers, and recycling operators are included in the trader TR. Each trader sends a hash value return request to the data management server 60 at the time of vehicle inspection, resale, and recycling. In the data management server 60, the final block of the blockchain storing the actual performance of manufacturing and use is read, and the hash value of the final block is calculated. Each trader outputs the item code QRi recording the hash value of the final block through the user device 10, and attaches it to the print for vehicle verification, or the product or commodity for resale or recycling. If the above management system is used, a supply chain SC with high trust from the manufacture of products or commodities to recycling can be constructed.

[0207] In the above-mentioned embodiment, the item code QRi attached to the final product FP is a normal QR code. In contrast, in the variation 15 of the above-mentioned embodiment, in addition to the item code QRi composed of the normal QR code, an item code QRi composed of SQRC may be further attached. SQRC may also have a copy prevention function. By marking such a QR code together, it is possible to ensure the ease of record reference using a user terminal 110 such as a smartphone, and in the case of suspicion that the normal QR code has been tampered with, accurate record reference can be performed by reading the SQRC using a dedicated scanner.

[0208] In the above-mentioned embodiment, the case where the management method of the supply chain SC disclosed in the present invention is applied to industrial products is mainly described. According to the application of such a purpose, it is possible to exclude raw materials MAT (such as rare metals, etc.) developed through forced labor of children from the supply chain SC. In addition, according to the supply chain management method disclosed in the present invention, it is possible to later prove that certain information existed at a certain time. Therefore, the information stored by the blockchain is also suitable for public auditing.

[0209] Furthermore, as described above, the final product FP provided by the supply chain SC is not limited to industrial products. For example, if the final product FP is an agricultural product, the consumer CST can centrally refer to a series of historical information related to the place of origin, producer, inspection items, and inspection agencies from the item code QRi attached to the final product FP at the retail store. Similarly, if the final product FP is a seafood product, the consumer CST can centrally refer to a series of historical information related to the name of the country of origin, the name of the water area, the landing port, fishermen, farms, aquaculture industry, inspection items, and inspection agencies from the item code QRi attached to the final product FP. According to the application of such purposes, it is possible to increase the consumer CST's trust in food safety and reliably prove that it is a fair trade product.

[0210] In the above-mentioned embodiment, each function provided by the data management server and the time stamp server may also be provided by software and hardware executing the software, only software, only hardware, or a combination of these. In addition, similarly, each function provided by the processing circuit of the user device and the control circuit of the user terminal may also be provided by software and hardware executing the software, only software, only hardware, or a combination of these. In the case where such functions are provided by an electronic circuit as hardware, each function may also be provided by a digital circuit including a plurality of logic circuits, or an analog circuit.

[0211] Each processor in the above-mentioned embodiments may also be a structure including at least one CPU (Central Processing Unit) and GPU (Graphics Processing Unit) and other computing cores. In addition, the processor may also be a structure further including FPGA (Field-Programmable Gate Array), NPU (Neural Network Processing Unit) and other dedicated function IP cores.

[0212] As each storage unit of the above-mentioned embodiment is adopted, the storage medium for storing each program associated with the supply chain management method of the present disclosure can be appropriately changed. For example, the storage medium is not limited to a structure provided on a circuit substrate, but can also be a structure provided in the form of a memory card, etc., inserted into a socket, and electrically connected to the bus of a computer. In addition, the storage medium can also be a CD and a hard disk drive that serve as a copy basis for the program copied to the computer.

[0213] The control unit and method described in the present disclosure may also be implemented by a special-purpose computer, which is a processor programmed to execute one or more functions embodied by a computer program. Alternatively, the device and method described in the present disclosure may also be implemented by a special-purpose hardware logic circuit. Alternatively, the device and method described in the present disclosure may also be implemented by one or more special-purpose computers consisting of a combination of a processor that executes a computer program and one or more hardware logic circuits. In addition, the computer program may also be stored as an instruction executed by a computer in a non-transitional tangible recording medium that can be read by a computer.

Claims

1. A supply chain management method is implemented by a computer and uses a blockchain to manage transaction records between multiple traders in a supply chain. The process performed by at least one processor comprises the following steps: acquiring item data attached to a delivery item delivered to a specific person as one of the above-mentioned traders, and node identification data assigned to the above-mentioned specific person; The operation is based on the hash value of the above-mentioned project data and the above-mentioned node identification data; as well as providing at least the hash value as the item data attached to the shipment item shipped from the specific person to the other trader to the specific person, It also includes the following steps: a reference request for obtaining the above transaction record together with the above project data; extracting, based on the project data, the transaction record associated with the delivery project to which the project data is attached from the accumulated plurality of transaction records; and The provision data based on the extracted transaction record is provided to the request source of the reference request.

2. The supply chain management method according to claim 1, wherein: The method further includes the following step: recording the item data including at least the hash value in at least one of the two-dimensional code and the RFID tag attached to the shipping item.

3. The supply chain management method according to claim 1 or 2, wherein: In the step of acquiring data, further acquiring time stamp data associated with the date and time when the above-mentioned delivery item is under the above-mentioned specific person, In the step of calculating the hash value, the hash value is calculated based on the time stamp data in addition to the item data and the node identification data.

4. The supply chain management method according to claim 3, wherein: The method further comprises the following step: determining whether the transactions between the traders are improper based on the causal relationship between the dates and times indicated by the plurality of timestamp data.

5. The supply chain management method according to claim 1 or 2, wherein: The node identification data is a unique content given by the authenticator to each of the above traders. The supply chain management method further includes the step of determining whether the node identification data obtained from the specific person is the node identification data given by the authenticator.

6. The supply chain management method according to claim 1 or 2, wherein: In the step of acquiring data, location data indicating a location where the item data is read is further acquired. In the step of calculating the hash value, the hash value is calculated based on the position data in addition to the item data and the node identification data.

7. The supply chain management method according to claim 1 or 2, wherein: The method further includes the step of determining whether the item data obtained from the specific person overlaps with the item data already obtained from other traders.

8. The supply chain management method according to claim 1, wherein: The supply chain management method is implemented by a computer and uses a blockchain to realize the management of transaction records between traders in a supply chain consisting of multiple traders by a data management server. The process performed by at least one processor comprises the following steps: obtaining item data pertaining to a delivery item delivered to a specific person being one of the above transactors; sending the transaction record at the specified location including at least the project data to a data management server; receiving a hash value calculated by the data management server based on at least the project data; as well as The data including at least the hash value is used as the item data attached to the shipment item shipped from the specific person to the other traders.

9. A supply chain management method, implemented by a computer, using a blockchain to manage transaction records between multiple traders in a supply chain. The process performed by at least one processor comprises the following steps: acquiring item data attached to a delivery item delivered to a specific person as one of the above-mentioned traders, and node identification data assigned to the above-mentioned specific person; Associating and accumulating the transaction records in the above-mentioned specific person with the above-mentioned project data; Deciding to continue to use the said item data attached to the said delivered item as the said item data attached to the shipped item shipped from the said specific person to the said other traders; a reference request for obtaining the above transaction record together with the above project data; In a case where the project data is continuously used by a plurality of the traders, extracting each of the transaction records of the plurality of traders using the project data from the plurality of transaction records managed using the blockchain; and The provision data based on the extracted transaction record is provided to the request source of the reference request.

10. A storage medium storing a supply chain management program, the supply chain management program including commands, using blockchain to manage transaction records between each of the above traders in a supply chain constructed by multiple traders, When the above command is executed by at least one processor, at least one processor: acquiring item data attached to a delivery item delivered to a specific person as one of the above-mentioned traders, and node identification data assigned to the above-mentioned specific person; The operation is based on the hash value of the above-mentioned project data and the above-mentioned node identification data; as well as As the item data attached to the shipment item shipped from the specific person to the other trader, at least the hash value is provided to the specific person, The above command also enables at least one of the above processors: a reference request for obtaining the above transaction record together with the above project data; extracting, based on the project data, the transaction record associated with the delivery project to which the project data is attached from the accumulated plurality of transaction records; and The provision data based on the extracted transaction record is provided to the request source of the reference request.

11. The storage medium according to claim 10, wherein: A supply chain management program is stored, the supply chain management program includes instructions to use blockchain to implement the management of transaction records between traders in a supply chain including multiple traders by a data management server, When the above command is executed by at least one processor, at least one processor: obtaining item data pertaining to a delivery item delivered to a specific person being one of the above transactors; sending the transaction record at the specified location including at least the project data to a data management server; receiving a hash value calculated by the data management server based on at least the project data; as well as The data including at least the hash value is used as the item data attached to the shipment item shipped from the specific person to the other traders.

12. A supply chain management system that uses blockchain to manage transaction records between multiple traders in a supply chain, comprising: User nodes, used by each of the above traders; At least one host node capable of communicating with a plurality of the above user nodes, The user node used by a particular person as one of the above traders has: an acquisition unit that acquires item data attached to the delivery item delivered to the specific person and node identification data assigned to the specific person; and a sending unit, which sends the project data and the node identification data acquired by the acquiring unit to the host node, The above host node has: a calculation unit that calculates a hash value based on the item data received from the user node and the node identification data; and The providing unit provides at least the hash value to the specified person as the item data attached to the delivery item delivered from the specified person to the other trader. The above host node also has: a request acquisition unit for acquiring a reference request for the transaction record together with the project data; a data extraction unit that extracts the transaction record associated with the delivery item to which the project data is attached from the accumulated plurality of transaction records based on the project data; and The data providing unit provides the providing data based on the extracted transaction record to the request source of the reference request.

Images