Value information management device, value information management system, value information management method, and value information management program

Abstract

Ensure the reliability of valuable information. [Solution] The value information management device 1 includes a local management information receiving unit 111 that receives a pre-shipment product ID that is attached to a first object received by a first user and identifies the first object, a post-shipment product ID that identifies the second object and value information relating to the second object, which is attached to the second object when the first user hands over the first object to a second user as a second object, a hash value calculation unit 112 that calculates a hash value using the pre-shipment product ID, the post-shipment product ID and the value information, and a blockchain management information storage unit 115 that stores blockchain management information D112 including the hash value, the pre-shipment product ID and the post-shipment product ID in the blockchain BC.

Description

Technical Field

[0001] The present invention relates to a value information management device, a value information management system, a value information management method, and a value information management program.

Background Art

[0002] Traceability management often refers to the management until a product is completed or a service is completed. For example, until a product is completed, it goes through various processes such as material incoming, material outgoing, and processing of materials. Therefore, traceability management is required to manage information regarding these multiple processes. For example, Patent Document 1 discloses a technique for managing information regarding products handled by participants in a supply chain.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] For example, until a product reaches the final consumption destination, multiple participants may be involved. Even when value transfer and additional value assignment are repeated among multiple participants in this way, it is necessary to ensure the reliability of the value information attached to the product or service.

[0005] An object of the present invention is to provide a value information management device, a value information management system, a value information management method, and a value information management program capable of ensuring the reliability of value information when transfer and additional assignment of a product or the like are repeated among multiple participants and when transfer and additional assignment of value are repeated among multiple participants.

Means for Solving the Problems

[0006] A value information management device according to one embodiment of the present invention includes: an information receiving unit that receives first identification information attached to a first object received by a first user to identify the first object; second identification information attached to a second object when the first user passes the first object to a second user as a second object, and second value information relating to the second object; a hash value calculation unit that calculates a hash value using the first identification information, the second identification information, and the second value information; and an information storage unit that stores blockchain management information including the hash value, the first identification information, and the second identification information on the blockchain.

[0007] Another embodiment of the present invention is a value information management system comprising: an information output unit that outputs first identification information that identifies the first object and is attached to the first object accepted by the first user; second identification information that identifies the second object and second value information relating to the second object, which is attached to the second object when the first user passes the first object to the second user as the second object; an information receiving unit that receives the first identification information, second identification information and second value information from the information output unit; a hash value calculation unit that calculates a hash value using the first identification information, second identification information and second value information; and an information storage unit that stores blockchain management information including the hash value, first identification information and second identification information on the blockchain. The information output unit is managed by the first user, and the information receiving unit, hash value calculation unit and information storage unit are managed by an administrator separate from the first user and the second user.

[0008] Another embodiment of the present invention is a value information management method comprising the steps of: receiving first identification information attached to a first object accepted by a first user to identify the first object; second identification information attached to a second object when the first user passes the first object to a second user as a second object, to identify the second object, and second value information relating to the second object; calculating a hash value using the first identification information, the second identification information and the second value information; and storing blockchain management information including the hash value, the first identification information and the second identification information on the blockchain.

[0009] Another embodiment of the present invention, a value information management program, causes a computer to function as an information receiving unit that receives first identification information attached to a first object accepted by a first user and identifying the first object, second identification information attached to a second object when the first user passes the first object to a second user as a second object, and second value information relating to the second object; a hash value calculation unit that calculates a hash value using the first identification information, the second identification information and the second value information; and an information storage unit that stores blockchain management information including the hash value, the first identification information and the second identification information on the blockchain.

[0010] The value information management device, value information management system, value information management method, and value information management program described above calculate a hash value using the first specific information, the second specific information, and the second value information. Then, blockchain management information, including the hash value, the first specific information, and the second specific information, is stored in the blockchain. As a result, the blockchain management information contains the hash value generated by the first specific information and the second specific information, and by using this hash value, the relationship between the first object and the second object can be confirmed. Consequently, the reliability of the value information can be ensured even when value is repeatedly transferred between multiple participants.

[0011] The above-described value information management device may include an authentication unit that determines whether or not to allow a second user to view the value information storage unit that stores the second value information. With this configuration, the first user can restrict who can access the second value information. As a result, the confidentiality of the second value information can be ensured.

[0012] The above-described value information management device may have an information preparation unit that includes contact information for requesting access to the second value information in the blockchain management information. With this configuration, a user who wishes to access the second value information can request access to the second value information from a user who has the authority to disclose the second value information.

[0013] The value information management device described above includes a viewing processing unit for requesting access to first value information relating to a first object. The viewing processing unit may include a blockchain management information receiving unit that acquires blockchain management information relating to the first object stored on the blockchain, a query information acquisition unit that extracts query information for obtaining first value information relating to the first object from the blockchain management information relating to the first object, and a viewing processing unit that requests permission from an authentication unit to allow the first user to view the value information storage unit where the first value information is stored, based on the query information. With this configuration as well, a user who wishes to view second value information can request access to the second value information from a user who has the authority to disclose the second value information.

[0014] The browsing processing unit of the value information management device described above may include a data verification unit that checks whether the hash value included in the blockchain management information relating to the first object matches the hash value obtained using the first value information and first identification information obtained by the browsing processing unit. With this configuration, it is possible to check whether the information stored on the blockchain has been tampered with. [Effects of the Invention]

[0015] According to the present invention, a value information management device, a value information management system, a value information management method, and a value information management program are provided that can ensure the reliability of value information when value is repeatedly transferred among multiple participants. [Brief explanation of the drawing]

[0016] [Figure 1] Figures 1(a) and 1(b) illustrate scenarios in which the value information management device, value information management system, value information management method, and value information management program of the first and second embodiments are applied. [Figure 2] Figure 2 is a diagram illustrating the concept of a value information management device, which is the first embodiment. [Figure 3]FIG. 3 is an example of blockchain management information stored in a distributed ledger on a blockchain by a value information management device. [Figure 4] FIG. 4 is a diagram for explaining data registration by a value information management device. [Figure 5] FIG. 5 is a diagram for explaining the confirmation of history by a value information management device. [Figure 6] FIG. 6 is a diagram for explaining the confirmation of another history by a value information management device. [Figure 7] FIG. 7 is a diagram for explaining the detailed confirmation of data by a value information management device. [Figure 8] FIG. 8 is a diagram showing a value information management system configured by a value information management device according to the first embodiment. [Figure 9] FIG. 9 is a diagram for explaining the physical configuration of the value information management device shown in FIG. 8. [Figure 10] FIG. 10 is a functional block diagram of the value information management device according to the first embodiment shown in FIG. 8. [Figure 11] FIG. 11 is an illustration of data handled by the value information management device according to the first embodiment shown in FIG. 8. [Figure 12] FIG. 12 is a flowchart showing a registration process in a value information management method executed by the value information management device according to the first embodiment shown in FIG. 8. [Figure 13] FIG. 13 is a flowchart showing a browsing process and an authentication process in a value information management method executed by the value information management device according to the first embodiment shown in FIG. 8. [Figure 14] FIG. 14 is a diagram for explaining the storage of data, which is the first use case by the value information management device according to the first embodiment. [Figure 15] FIG. 15 is a diagram for explaining the confirmation of data, which is the second use case by the value information management device according to the first embodiment. [Figure 16] FIG. 16 is a diagram for explaining the display of a product supply chain, which is the third use case by the value information management device according to the first embodiment. [Figure 17] Figure 17 is a diagram illustrating the fourth use case, which is the acquisition of detailed data, by the value information management device of the first embodiment. [Figure 18] Figure 18 illustrates a fifth use case of the value information management device of the first embodiment, which is the retrieval and visualization of supply chain provenance detail data. [Figure 19] Figure 19 is a diagram showing the configuration of the value information management device according to the second embodiment. [Figure 20] Figure 20 is a functional block diagram of the value information management device of the second embodiment shown in Figure 19. [Figure 21] Figure 21 is a flowchart showing the registration process in the value information management method performed by the value information management device of the second embodiment shown in Figure 19. [Figure 22] Figure 22 is a flowchart showing the browsing process and authentication process in the value information management method performed by the value information management device of the second embodiment shown in Figure 19. [Figure 23] Figure 23(a) is a diagram illustrating a first use case of the value information management device of the second embodiment. Figure 23(b) is a diagram illustrating a second use case of the value information management device of the second embodiment. [Figure 24] Figure 24(a) is a diagram illustrating a third use case of the value information management device of the second embodiment. Figure 24(b) is a diagram illustrating a fourth use case of the value information management device of the second embodiment. [Figure 25] Figure 25(a) is a diagram illustrating a fifth use case of the value information management device according to the second embodiment. Figure 25(b) is a diagram illustrating a sixth use case of the value information management device according to the second embodiment. [Figure 26] Figure 26 shows an example of the operation screen of a value information management device. [Figure 27] Figure 27 shows an example of another operation screen for the value information management device. [Modes for carrying out the invention]

[0017] Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the attached drawings. In the description of the drawings, the same elements are denoted by the same reference numerals, and redundant descriptions are omitted. In the following description, first, the situations to which the value information management device, value information management system, value information management method, and value information management program described as the first and second embodiments are applied and a brief overview will be described. Furthermore, several use cases for these will also be described. Then, the value information management device, value information management system, value information management method, and value information management program of the first and second embodiments will be described in detail, along with their respective use cases.

[0018] <Overview> Referring to Figures 1 to 7 as appropriate, we will now describe the situations to which the value information management device, value information management system, value information management method, and value information management program described as the first and second embodiments are applied, along with a brief overview. As an example of a situation to which the value information management device, value information management system, value information management method, and value information management program described as the first and second embodiments are applied, we will use the ammonia supply chain as an example. The supply chain shown in Figure 1(a) illustrates the process from ammonia production to ammonia-fueled power generation.

[0019] This supply chain involves six companies: Company A (Ca), Company B (Cb), Company C (Cc), Company D (Cd), Company E (Ce), and Company F (Cf). Company A (Ca) manufactures ammonia. Company B (Cb) transports the ammonia manufactured by Company A (Ca) by sea. Company C (Cc) stores the ammonia transported by Company B (Cb) by sea. Companies D (Cd) and E (Ce) transport the ammonia stored by Company C (Cc) by land. Company F (Cf) generates electricity using the ammonia transported by Company D (Cd) and E (Ce) by land.

[0020] Let's explain in more detail the process by which ammonia goes from Company A (Ca) to Company F (Cf). First, Company A (Ca) assigns several IDs to the ammonia it manufactures. In the example in Figure 1(a), Company A (Ca) assigns IDs (N0001), (N0002), and (N0003). The different IDs indicate that different values ​​have been assigned to each other. For example, when Company A (Ca) manufactures ammonia, it may assign different IDs based on, for example, the manufacturing lot. Then, Company A (Ca) ships all the ammonia with IDs (N0001), (N0002), and (N0003) to Company B (Cb). Since Company B (Cb) is a company that transports ammonia by sea, the shipment from Company A (Ca) to Company B (Cb) can be interpreted as loading ammonia from a tank owned by Company A (Ca) onto a ship owned by Company B (Cb).

[0021] Company B Cb is a company that transports ammonia by sea from Company A Ca to Company C Cc, so it can be said that Company B Cb adds value by transporting ammonia. An example of the value added by Company B Cb is the transport of ammonia with ID (N0001) from Company A Ca to Company C Cc by a first vessel. When Company B Cb transports ammonia with ID (N0001) from Company A Ca to Company C Cc by a large vessel, it assigns a new ID (M0001) in place of ID (N0001). When Company B Cb transports ammonia with ID (N0002) from Company A Ca to Company C Cc by a second vessel, it assigns a new ID (M0002) in place of ID (N0002). Company B Cb assigns a new ID (M0003) to ammonia that has been transported from Company A Ca to Company C Cc by a third vessel, replacing ID (N0003). Then, Company B Cb ships ammonia with IDs (M0001), (M0002), and (M0003) to Company C Cc. Shipment from Company B Cb to Company C Cc may also be interpreted as unloading from a vessel owned by Company B Cb into ammonia storage tanks owned by Company Cc.

[0022] Company Cc is a company that stores ammonia, so it can be said that Company Cc adds value by storing ammonia under certain conditions. For example, it is exemplified that ammonia with ID (M0001) is stored in a first tank for a first period. Company Cc assigns ID (P0001) to the ammonia stored in the first tank for the first period instead of ID (M0001). Similarly, it is exemplified that ammonia with ID (M0002) is stored in a second tank for a second period. Company Cc assigns ID (P0002a) and ID (P0002b) to the ammonia stored in the second tank for the second period instead of ID (M0002). Here, the destinations of the ammonia stored in the second tank for the second period are two companies: Company D Cd and Company E Ce. Therefore, Company C C assigns a unique ID to each destination for ammonia that has the same added value. This can be described as assigning an ID in conjunction with the transfer of value. Furthermore, it is exemplified that ammonia with ID (M0003) is stored in a third tank for a third period. Company C C assigns ID (P0003) to the ammonia stored in the third tank for the third period, replacing ID (M0003). Then, Company C C C ships the ammonia with IDs (P0001) and (P0002a) to Company D Cd, which is engaged in land transport. Shipment from Company C C to Company D Cd may also mean loading ammonia from a tank owned by Company C Cc onto a vehicle owned by Company D Cd that transports ammonia. Additionally, Company C C C ships ammonia with IDs (P0002b) and (P0003) to Company E Ce, which is engaged in land transport. The shipment from Company C (Cc) to Company E (Ce) may also be defined as loading ammonia from a storage tank owned by Company C (Cc) onto a transport vehicle owned by Company E (Ce).

[0023] Company D Cd is a company that transports ammonia by land from Company C Cc to Company F Cf, so it can be said that Company D Cd adds value by transporting ammonia. An example of the value added by Company D Cd is the transport of ammonia with ID (P0001) from Company Cc to Company F Cf by vehicle. Here, Company D Cd transports the ammonia with ID (P0001) from Company Cc to Company F in two separate trips. This could be transported by two different vehicles, or by one vehicle making two round trips between Company D Cd and Company F Cf. At this time, Company D Cd assigns a new ID (GT0001a) to the ammonia with ID (P0001) that was transported from Company Cc to Company F Cf in the first transport. Furthermore, Company D Cd assigns a new ID (GT0001b) to the ammonia that was transported from Company Cc to Company F Cf by the second transport, replacing ID (P0001). Then, Company D Cd assigns a new ID (GT0002) to the ammonia that was transported from Company Cc to Company F Cf by vehicle, replacing ID (P0002a). The shipment from Company Cc to Company F Cf may be defined as unloading from a vehicle owned by Company Cc to a tank storing ammonia owned by Company F Cf.

[0024] Since Company E Ce, like Company D Cd, is a company that transports ammonia by land from Company C Cc to Company F Cf, it can be said that Company E Ce adds value by transporting ammonia. An example of the value added by Company E Ce is the transport of ammonia with ID (P0002b) from Company C Cc to Company F Cf by vehicle. When Company E Ce transports ammonia with ID (P0002b) from Company C Cc to Company F Cf by vehicle, it assigns a new ID (GE0002) in place of ID (P0002b). When Company E Ce transports ammonia with ID (P0003) from Company C Cc to Company F Cf by vehicle, it assigns a new ID (GE0003) in place of ID (P0003).

[0025] Thus, ammonia is transferred from Company A (Ca) to Company F (Cf) via Company B (Cb), Company C (Cc), Company D (Cd), and Company E (Ce). In recent years, ammonia-fueled power generation technology has attracted attention. Ammonia does not contain carbon as a constituent element. Therefore, it has the characteristic of not producing carbon dioxide when burned. Consequently, power generation using ammonia as fuel can contribute to the reduction of carbon dioxide. However, if we focus only on power generation at Company F (Cf), it may be seen as contributing to the reduction of carbon compounds, but unless carbon dioxide generation is suppressed in the process from production at Company A (Ca) to transportation to Company F (Cf), it cannot be said that an overall reduction in carbon dioxide has been achieved. Therefore, the ammonia transferred between each company is associated with value information called "environmental value," and this environmental value moves between companies along with the movement of the ammonia. For example, "environmental value" may be guaranteed by a transaction certificate as shown in Figure 1(b). Furthermore, the ammonia transferred between each company may also be associated with the environmental value (burden) of each company's activities.

[0026] For example, as shown in Figure 1(b), the environmental value (impact) of Company A's activities related to ammonia (ID(N0001), ID(N0002), ID(N0003)) shipped from Company A's Ca to Company B's Cb is guaranteed by transaction certificate C100b. Transaction certificate C100b is provided from Company A's Ca to Company B's Cb in tangible form such as paper, or intangible form such as an electronic file.

[0027] Similarly, the environmental value (impact) of Company B Cb's activities related to ammonia (ID(M0001), ID(M0002), ID(M0003)) shipped from Company B Cb to Company Cc is guaranteed by transaction certificate C100c. Transaction certificate C100c is provided from Company B Cb to Company Cc. The environmental value (impact) of Company Cc's activities related to ammonia (ID(P0001), ID(P0002a)) shipped from Company Cc to Company D Cd is guaranteed by transaction certificate C100d. Transaction certificate C100d is provided from Company Cc to Company D Cd. The environmental value (impact) of Company Cc's activities related to ammonia (ID(P0002b), ID(P0003)) shipped from Company Cc to Company E Ce is guaranteed by transaction certificate C100e. Transaction certificate C100e is provided from Company C Cc to Company E Ce. The environmental value (impact) of Company D Cd's business activities related to ammonia (ID(GT0001a), ID(GT0001b), ID(GT0002)) shipped from Company D Cd to Company F Cf is guaranteed by transaction certificate C100f1. Transaction certificate C100f1 is provided from Company D Cd to Company F Cf. The environmental value (impact) of Company E Ce's business activities related to ammonia (ID(GT0002), ID(GT0003)) shipped from Company E Ce to Company F Cf is guaranteed by transaction certificate C100f2. Transaction certificate C100f2 is provided from Company E Ce to Company F Cf.

[0028] Furthermore, the "environmental value" assigned to ammonia is expected to be reliable among the companies participating in the supply chain. However, even among companies participating in a common supply chain, it is not desirable to share all information. In such a business environment, the value information management device, value information management system, value information management method, and value information management program described as the first and second embodiments provide reliable value information while limiting the information disclosed to other companies.

[0029] In addressing the above challenges, the inventors of this invention conducted extensive research and, as a result, focused on identification IDs assigned to ammonia as a means of limiting disclosed information and ensuring the reliability of value information. As mentioned above, several IDs ((N0001), (N0002), (N0003)) are assigned to ammonia shipped from Company A Ca. Differences in IDs can be considered as differences in the value assigned to the ammonia. For example, Company B Cb, upon receiving ammonia with ID (N0001), changes the ID (N0001) to ID (M0001) after sea transport and delivers it to Company C Cc. In other words, it is possible to trace the origin using the ID as a clue.

[0030] However, identification by ID alone cannot guarantee the reliability of the aforementioned "value information." Furthermore, it does not guarantee, for example, whether ammonia with ID (N0001) matches ammonia with ID (M0001).

[0031] Therefore, the inventors of this application conceived of inputting the ID attached to the accepted ammonia, the ID that was replaced with that ammonia, and the environmental value associated with the ID replacement they performed into a hash function to obtain a hash value. This hash value and ID are then stored in a distributed ledger 200 formed on a so-called blockchain and made accessible to all participants involved in the supply chain. However, since the only information accessible is the hash value and ID, each company does not need to disclose information it does not wish to disclose. If additional information such as "environmental value" is to be checked, the hash value and ID recorded in the distributed ledger 200 are obtained, along with the inquiry information stored therein. For example, Company C Cc uses this inquiry information to request Company B Cb to view the "environmental value" information for ammonia with ID (M0002). Company B Cb can verify that the request is from Company C Cc, confirm that it is possible to grant permission, and then allow Company Cc to view the "environmental value" information.

[0032] In short, the value information management device, value information management system, value information management method, and value information management program enable the management of the entire lifecycle of ammonia, including the manufacturing, transportation, storage, and consumption processes, through the two elements described below.

[0033] The first element is the verification of transaction history throughout the process from product to consumption, and addressing changes in environmental impact and environmental value that occur during transportation and storage. Participants in the supply chain who require value information management in connection with the transfer of goods along the supply chain create a post-value ID based on their own activities from the pre-value-added product ID for the products they manufacture, transport, store, or consume. Next, they register the activity information and both IDs in a database that participants can commonly access. By linking the two IDs registered in the database as pairs in a tree structure (or graph structure), information on the origin and value changes up to final consumption in the supply chain can be managed. When value is transferred to physically different products, the transfer can be managed by changing the source product ID to a new ID corresponding to the value transfer, and also by setting a new ID corresponding to the value transfer for the destination product ID.

[0034] The second element is ensuring data confidentiality and data integrity as needed, given the involvement of various stakeholders. This confidentiality and data integrity are achieved by using blockchain technology. The registrant of activity information inputs the activity information as a value into a hash function to obtain a hash value. The registrant stores the activity information and the calculated hash value in their own storage device. The registrant stores their identity information, their ID before value is assigned by their activity, their ID after value is assigned, and their hash value in the blockchain ledger. All information registered in the blockchain ledger can be viewed by any blockchain participant. Participants authorized to view detailed registration information can obtain detailed transaction information by requesting disclosure from the registered company. To verify that the obtained transaction information is tamper-proof, a hash value is generated from the information received from the registrant and its consistency is checked against the hash value on the blockchain. The participation of multiple companies enables the distributed ledger to function, ensuring tamper integrity.

[0035] The idea conceived by the inventors can be easily understood from Figure 2. Figure 2 shows only Company A Ca and Company B Cb as participants. Company A Ca and Company B Cb each possess a value information management device 1a and 1b. The specific configuration and operation of the value information management devices 1a and 1b will be explained in the first and second embodiments, so only a brief explanation will be given here. In the example in Figure 2, we assume that Company B Cb wants to view value information regarding ammonia (N0001) shipped by Company A Ca to Company B Cb.

[0036] Company A Ca stores blockchain registration information T311 related to ammonia (N0001) in Company A Ca's distributed ledger 200a (P21). The blockchain registration information T311 stored in distributed ledger 200a is shared with another distributed ledger 200b within blockchain BC (P22). Then, Company B Cb accesses Company B Cb's distributed ledger 200b (P23) and obtains information with a predetermined post-shipment product ID (P24). This information includes a "contact URL". Using this "contact URL" as a clue, Company B Cb requests Company A Ca to allow access to detailed information (P25). For example, as shown in Figure 7, Company B Cb, wanting to obtain detailed information (G74) for a product corresponding to a predetermined pre-shipment product ID, sends Company A Ca a request to access the information along with the "pre-shipment ID (N0001)". Based on its access rights to Company B Cb, Company A Ca grants Company B Cb permission to access the detailed data (P26).

[0037] Figure 3 is an example of blockchain registration information T311 as described in processes P21 and P22. As shown in Figure 3, the blockchain registration information T311 stored in the distributed ledger 200a may be information formed as, for example, a two-dimensional table. Blockchain registration information T311 includes several information elements. The information elements included in blockchain registration information T311 include "shipping destination," "shipping origin," "inquiry URL," "post-shipment product ID," "pre-shipment product ID," "hash value," and "timestamp."

[0038] For example, Figure 3 shows that for an ammonia transfer where the "source" is company A and the "destination" is company B, the "contact information" is "http: / / A.com / ...", the post-shipment product ID is N0001, and there is no pre-shipment product ID. Furthermore, as will be described later, a hash value (332djls·jfkay) generated from the destination information, source information, post-shipment product ID, and pre-shipment product ID, as well as a timestamp (yyyy / mm / dd / HH:MM:ss) indicating the date and time of registration, are shown.

[0039] Similarly, Figure 3 shows that for the transfer of ammonia where the "source" is Company B and the "destination" is Company C, the "contact information" is "http: / / B.com / ...", the post-shipment product ID is M0001, and the pre-shipment product ID is N0001. Furthermore, the hash value (kdjae3s·jfdady) generated from the destination information, source information, post-shipment product ID, and pre-shipment product ID, as well as the timestamp (yyyy / mm / dd / dd:MM:ss) indicating the date and time of registration, are shown.

[0040] Furthermore, blockchain registration information T311 does not need to include all of these listed information elements, and may consist of several information elements selected from among them. Blockchain registration information T311 may also include information elements other than those listed.

[0041] Figure 4 is a diagram illustrating in detail the process (P21) for storing blockchain registration information T311 in Figure 2. The value information management device 1a owned by Company A Ca obtains a hash value using hash value generation data D42 (P41). Hash value generation data D42 includes detailed data D41, destination, origin, post-shipment product ID, and pre-shipment product ID. Detailed data D41 includes, for example, certificates, GHG emissions, methodology, and calculation data. In the example in Figure 4, the following specific information is shown as hash value generation data D42. Shipped from: Company A Shipping destination: Company B Product ID after shipment: M0001 Product ID before shipment: N0001 An example of a hash value generated from the hash value generation data D42, which includes these elements, is shown below. Hash value: ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb

[0042] The value information management device 1a stores information including the shipping destination, shipping source, contact URL, post-shipment product ID and pre-shipment product ID, hash value, and timestamp as blockchain registration information D43 in the distributed ledger 200a of Company A Ca (P42).

[0043] Here, the value information management device 1a does not include the detailed data D41 in the blockchain registration information D43. In other words, the detailed data D41 is not stored in the distributed ledger 200a and is therefore never made public. The information stored in the distributed ledger 200a of company A Ca is immediately shared with the distributed ledger 200b of company B Cb via the blockchain (P43).

[0044] In addition to registering blockchain registration information D43 in the distributed ledger 200, the value information management device 1a also has the function of displaying the information registered in the distributed ledger 200 based on the display format requested by the user. Examples of what can be displayed by the value information management device 1a are shown in Figures 5 and 6. Furthermore, Figure 7 illustrates the process of checking the details of the data using the value information management device 1a.

[0045] Figure 5 shows an example of a history information display. The example of a history information display shown in Figure 5 shows the results of searching for the history of ammonia with ID (N0001). The example of a history information display includes a display unit G51 that visually shows the history of ammonia with ID (N0001), and a display unit G52 that lists and displays the history of ammonia with ID (N0001).

[0046] Display unit G51 shows symbols representing an ammonia production plant Ha (Company A, Ca), a ship transporting ammonia Hb (Company B, Cb), ammonia storage tank Hc (Company C, Cc), ammonia transport vehicle Hd1 (Company D, Cd), ammonia transport vehicle Hd2 (Company E, Ce), and ammonia-powered electricity generation plant Hf (Company F). Arrows connecting these symbols indicate the source and destination of the ammonia shipment. Near the arrows, the IDs assigned to the transferred ammonia are displayed. Display unit G51 allows for a visual understanding of the transfer history of the ammonia with ID (N0001).

[0047] Display unit G52 shows a table summarizing detailed information about the ammonia with the ID (N0001) visually displayed on display unit G51. The table includes the destination, origin, post-shipment product ID, pre-shipment product ID, and timestamp. The first row shows that for ammonia shipped from company A to company B, there is no pre-shipment product ID, the post-shipment product ID is N0001, and the information was registered on April 1, 2024 at 9:00. The second row shows that for ammonia shipped from company B to company C, the pre-shipment product ID is N0001, the post-shipment product ID is M0001, and the information was registered on May 15, 2024 at 9:00. The third row shows that for ammonia shipped from company C to company D, the pre-shipment product ID is M0001, the post-shipment product ID is P0001, and the information was registered on May 17, 2024 at 9:00. The fourth line shows that for ammonia shipped from Company D to Company F, the pre-shipment product ID is P0001, the post-shipment product ID is GT0001a, and the date and time the information was registered is May 20, 2024, at 9:00. The fifth line shows that for ammonia shipped from Company D to Company F, the pre-shipment product ID is P0001, the post-shipment product ID is GT0001b, and the date and time the information was registered is May 21, 2024, at 9:00.

[0048] In other words, according to the provenance information shown in Figure 5, it can be seen that the ammonia with ID (N0001) arrived at Company G via the provenance shown for ID (N0001), ID (P0001), and ID (GT0001a), and also via the provenance shown for ID (N0001), ID (P0001), and ID (GT0001b). In short, it is possible to confirm the parties associated with the product ID, as well as the origin and destination of the product.

[0049] Figure 6 shows an example of a display that identifies the parties associated with a product ID, as well as the origin and destination of the product. This is another example of a display showing the results of searching for the history of ammonia assigned ID (N0001). A display like the one in Figure 6 is also called a graph network structure (display unit G61). It also includes a display unit G62 that lists and displays the history of ammonia assigned ID (N0001), similar to Figure 5.

[0050] Display unit G61 shows a simple diagram illustrating how ammonia is transferred between companies. The visual information displayed on display unit G61 may also be the result of a search using the product ID (N0001) as a keyword. Display unit G61 in Figure 6 shows six markers M61 to M66. Marker M61 represents Ca from company A. Marker M62 represents Cb from company B. Marker M63 represents Cc from company C. Marker M64 represents Cd from company D. Markers M65 and M66 represent Cf from company F. In addition, the arrows connecting the markers indicate the source of shipment at the starting point and the destination at the ending point. The characters displayed near the arrows are the product IDs.

[0051] To explain display unit G61 in detail, first, the arrow extending from marker M61 to marker M62 indicates that ammonia was transferred from the source, company A Ca, to the destination, company B Cb, along with ID (N0001). Next, the arrow extending from marker M62 to marker M63 indicates that ammonia was transferred from the source, company B Cb, to the destination, company C Cc, along with ID (M0001). Next, the arrow extending from marker M63 to marker M64 indicates that ammonia was transferred from the source, company Cc, to the destination, company D Cd, along with ID (P0001). Finally, the arrow extending from marker M64 to marker M65 indicates that ammonia was transferred from the source, company D Cd, to the destination, company F Cf, along with ID (GT0001a). Furthermore, the arrow extending from marker M64 to marker M66 indicates that ammonia was transferred from the source, company D (Cd), to the destination, company F (Cf), along with its ID (GT0001b).

[0052] Display unit G62 displays a list of product IDs for tracing the origin of ammonia and the relevant parties shown in display unit G61. The table in display unit G62 shows the following items: "Post-shipment product ID," "Pre-shipment product ID," "Destination," and "Shipment source." The first row in the table in display unit G62 shows that the shipment source is company A, the destination is company B, there is no pre-shipment product ID, and the post-shipment product ID is N0001. The second row shows that the shipment source is company B, the destination is company C, the pre-shipment product ID is N0001, and the post-shipment product ID is M0001. The third row shows that the shipment source is company C, the destination is company D, the pre-shipment product ID is M0001, and the post-shipment product ID is P0001. The fourth row shows that the supplier is Company D, the recipient is Company F, the pre-shipment product ID is P0001, and the post-shipment product ID is GT0001a. The fifth row shows that the supplier is Company D, the recipient is Company F, the pre-shipment product ID is P0001, and the post-shipment product ID is GT0001b.

[0053] Figure 7 shows an example of the process for verifying data details. The distributed ledger 200 contains information such as that shown in Table G72. Table G72 includes the following items: "Recorder", "Destination", "Origin", "Post-shipment product ID", "Pre-shipment product ID", "Hash value", and "Timestamp". Each item contains specific information. In Table G72, the "Recorder" is Company S, the "Destination" is Company B, the "Origin" is Company A, the "Post-shipment product ID" is M0001, the "Pre-shipment product ID" is N0001, the "Hash value" is ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb, and the "Timestamp" is 2024 / 04 / 01 09:00:00.

[0054] Users can access the distributed ledger 200 and obtain the information contained in table G72. If a user wishes to check the detailed information of a product with a pre-shipment product ID (N0001), they send an information disclosure request to server F71 of company A, which holds the detailed information of the pre-shipment product ID (N0001). The information disclosure request may also include the post-shipment product ID and hash value. Furthermore, not just anyone can send an information disclosure request P71 to server F71 of company A; only companies in the commercial supply chain may be permitted to send information disclosure requests to server F71 of company A. If the information disclosure request is accepted, server F71 of company A discloses the detailed information of the product with the pre-shipment product ID (N0001) P72.

[0055] Table G73 is an example of detailed information registered on server F71 of Company A. Table G73 includes the following items: "BC Management No.", "Post-Shipment Product ID", "Destination", "Origin", "CI Value", "Pre-Shipment Product ID", "Post-Shipment Product Quantity", "Pre-Shipment Product Usage", "Transaction Certificate", "Methodology", "Certification Authority", and "Hash Value". Each item contains specific information. Table G73 shows that "BC Management No." is 1, "Post-Shipment Product ID" is M0001, "Destination" is Company B, "Shipment Source" is Company A, "CI Value" is a predetermined value, "Pre-Shipment Product ID" is N0001, "Post-Shipment Product Quantity" is a predetermined value, "Pre-Shipment Product Usage Quantity" is a predetermined value, "Transaction Certificate" is a predetermined file name, "Methodology" is a predetermined method, "Certification Authority" is a predetermined certification authority, and "Hash Value" is ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb. Server F71 of Company A, which approved the information disclosure request P71, discloses the detailed information registered in Table G73 to the user.

[0056] <First Embodiment> Next, with reference to Figures 8 to 13, the first embodiment of the value information management device, value information management system, value information management method, and value information management program P100 will be described. As shown in Figure 8, the first embodiment of the value information management device 1 constitutes the traceability management system 100, which is a value information management system. The traceability management system 100 includes a blockchain BC and a plurality of value information management devices 1a, 1b, and 1c. In the following description, when the relationship between the value information management device and the user is not specified, it will simply be referred to as "value information management device 1".

[0057] Blockchain BC has multiple value information management devices 1a, 1b, and 1c connected to it via a network such as the internet. Blockchain BC is a tamper-resistant database system that manages data in a distributed manner by multiple nodes. In this embodiment, each of the multiple nodes may correspond to a distributed ledger 200a, 200b, and 200c. The distributed ledgers 200a, 200b, and 200c of Blockchain BC are configured to allow storage, updating, and retrieval of various types of data from the value information management devices 1a, 1b, and 1c.

[0058] In the first embodiment, the value information management device 1 is an information terminal device such as a personal computer or smartphone owned by each company. The value information management device 1 includes a local management information processing unit 11 for storing value information in a distributed ledger 200a, a viewing unit 12 for viewing detailed data, a viewing request authentication unit 13 for authenticating viewing requests, and a local server 2. These functional and physical elements are realized by a computing device (computer) such as a server device or personal computer having the configuration illustrated in Figure 9.

[0059] As shown in Figure 9, the value information management device 1 physically includes a processor 31 which is a CPU (Central Processing Unit), a recording medium consisting of RAM (Random Access Memory) 32 and ROM (Read Only Memory) 33, a communication module 34, and input / output devices 35, each of which is electrically connected internally. The input / output devices 35 include a keyboard, mouse, display device, touch panel display device, speaker, etc. The computer elements shown in Figure 9 may be provided on a server in the cloud, or they may be provided separately on multiple network-connected computers. Each functional unit of the value information management device 1 described above is realized by loading the value information management program P100 of the embodiment onto the hardware such as the processor 31 and RAM 32, thereby operating the communication module 34 and input / output devices 35, etc., under the control of the processor 31, and reading data from ROM 33, and reading and writing data to RAM 32. In other words, when the value information management program P100 is loaded onto the above hardware, it causes the computer 30 to operate as a local management information processing unit 11, a viewing unit 12, and a viewing request authentication unit 13. Furthermore, the value information management device 1 may be equipped with other types of recording media, such as HDDs (Hard Disk Drives) and SSDs (Solid State Drives).

[0060] <Value information management device of the first embodiment> As shown in Figure 10, the value information management device 1 includes several functional components implemented on the processor 31 and a local server 2.

[0061] The value information management device 1 includes, as functional components, a local management information processing unit 11, a browsing unit 12, and a browsing request authentication unit 13.

[0062] The local management information processing unit 11 obtains blockchain management information based on the local management information. The local management information processing unit 11 includes a local management information receiving unit 111, a hash value calculation unit 112, a local management information storage unit 113, a blockchain management information preparation unit 114, and a blockchain management information storage unit 115.

[0063] The local management information receiving unit 111 receives local management information D111 as shown in Figure 11. Local management information D111 includes multiple pieces of information about the product. Local management information D111 includes detailed data, ID data, destination data, source data, CI value, shipment volume, evidence file, and inquiry URL, etc. Note that this data is illustrative, and it is not necessary for local management information D111 to include all of it, and it may also include other data not exemplified. Furthermore, detailed data may include certificate data, GHG emissions, methodology, and calculation data. ID data may include post-shipment product ID and pre-shipment product ID. Destination data may include destination latitude and longitude. Source data may include source latitude and longitude. Of these, detailed data, ID data, destination data, source data, CI value, shipment volume, and evidence file may be treated as hash value generation information D113 used to calculate the hash value. Furthermore, all the information and data contained in local management information D111 are stored in the local server 2. The local management information receiving unit 111 may receive local management information D111 via the input / output device 35, or it may receive local management information D111 via the communication module 34.

[0064] The hash value calculation unit 112 obtains a hash value using a hash function, targeting the hash value generation information D113 contained in the local management information D111. The hash value calculation unit 112 stores the hash value in the local server 2. A hash function is a function that can output a value of a predetermined length from document data. If even slightly different information is input to the hash function, the output hash value will be completely different. Even if different information is input, it is generally considered very difficult to make the hash values ​​output by the hash function the same. In other words, it is difficult to change the information while maintaining the hash value. For example, the hash value calculation unit 112 may use SHA3-256, which outputs a 256-bit value, as the hash function.

[0065] The local management information storage unit 113 stores the local management information D111 received by the local management information receiving unit 111 in the local server 2. The local management information storage unit 113 stores all information and data contained in the local management information D111 in the local server 2.

[0066] The blockchain management information preparation unit 114 reads predetermined information and data constituting blockchain management information D112 from local management information D111 stored on local server 2. An example of the information and data read by the blockchain management information preparation unit 114 is shown in the blockchain management information D112 in Figure 11. Blockchain management information D112 is made public to participants involved in the supply chain. Blockchain management information includes hash values, ID data, destination data, origin data, timestamp, and inquiry URL. Blockchain management information D112 does not include information such as detailed data, CI values, shipment volume, and evidence files. This information is not intended to be made public to participants involved in the supply chain. This information can only be viewed if a participant involved in the supply chain requests to view it and the recipient of the viewing request grants permission.

[0067] The blockchain management information storage unit 115 stores the blockchain management information D112 generated by the blockchain management information preparation unit 114 in the distributed ledger 200. The blockchain management information storage unit 115 outputs the blockchain management information D112 via the communication module 34 and stores the information in the distributed ledger 200 of blockchain BC.

[0068] The viewing unit 12 is for viewing information such as detailed data, CI values, shipment volume, and evidence files that are not included in the blockchain management information D112. The viewing unit 12 includes a viewing request acceptance unit 121, a blockchain management information request unit 122, a blockchain management information acceptance unit 123, a query contact information acquisition unit 124, a data request unit 125, a data acceptance unit 126, a data confirmation unit 127, and a data display unit 128.

[0069] The access request receiving unit 121 receives access requests for information from users operating the value information management device 1. For example, the user inputs the product ID assigned to the target of the access request. The user can submit an access request to the access request receiving unit 121 by operating the input / output device 35. The information subject to the access request can be defined as information about a product assigned a predetermined product ID that is not included in the blockchain management information D112. For example, it can be said to be information included in the local management information D111 shown in Figure 11, but not included in the blockchain management information D112. Specifically, this includes detailed data (certificate data, GHG emissions, methodology, calculation data), destination latitude and longitude included in destination data, source latitude and longitude included in source data, CI value, shipment volume, and evidence file. This information is not stored in the distributed ledger 200, but only in the local server 2.

[0070] The blockchain management information request unit 122 requests blockchain management information D112 related to the product ID attached to the target of the viewing request entered by the user from the distributed ledger 200. The blockchain management information receiving unit 123 then receives the blockchain management information D112 related to the product ID attached to the target of the viewing request, which was stored in the distributed ledger 200. The operation of the blockchain management information request unit 122 and the blockchain management information receiving unit 123 is performed via communication between the processor 31 and the blockchain BC, and is therefore executed, for example, via the communication module 34.

[0071] The inquiry information acquisition unit 124 acquires inquiry information from the blockchain management information D112 received by the blockchain management information acceptance unit 123. An example of inquiry information may be an inquiry URL.

[0072] The data request unit 125 uses the inquiry information (inquiry URL) obtained by the inquiry information acquisition unit 124 to send a data viewing request. The viewing request may include, for example, the product ID for which viewing is requested or the company identifier of the company requesting viewing. The value information management device 1 that sends the data viewing request and the value information management device 1 that receives the data viewing request are different entities. For example, the value information management device 1b of company B sends the viewing request, and the value information management device 1a of company A receives the viewing request. Thus, since the operation of the data request unit 125 involves communication with an external party, it is executed, for example, via a communication module 34.

[0073] When a value information management device 1a receives a viewing request, if it can grant permission to view the data, it transmits the local management information D111 stored in the local server 2 to the value information management device 1b that made the viewing request. The data receiving unit 126 receives the data transmitted from the value information management device 1a that is being viewed. The operation of the data receiving unit 126 also involves communication with the outside world, and is therefore performed, for example, via the communication module 34.

[0074] The data verification unit 127 confirms that the local management information D111 transmitted from the value information management device 1a being viewed matches the blockchain management information D112 received by the blockchain management information receiving unit 123. This confirmation is based on the hash value contained in the blockchain management information D112. The hash value contained in the blockchain management information D112 is based on the hash value generation information D113 contained in the local management information D111. Therefore, the data verification unit 127 extracts the hash value generation information D113 from the local management information D111 transmitted from the value information management device 1a being viewed and inputs it into the hash function. As a result, a hash value is obtained. Next, the data verification unit 127 determines whether the hash value obtained by calculation matches the hash value contained in the blockchain management information D112. If the hash values ​​match, it can be confirmed that the blockchain management information D112 stored in the distributed ledger 200b is true. Specifically, it can be determined that the relationship between the post-shipment product ID and the shipping source product ID that constitutes the blockchain management information D112 is true. On the other hand, if the hash values ​​do not match, it is possible that the blockchain management information D112 stored in the distributed ledger 200 has been tampered with, or that the received data is different from the data registered on the blockchain.

[0075] The data display unit 128 displays blockchain management information D112 and / or local management information D111 transmitted from the value information management device 1a to the user. The data display unit 128 causes this information to be displayed on a display, which is an example of an input / output device 35. Examples of the screen that the data display unit 128 displays on the input / output device 35 are shown in Figures 5 and 6, as already described.

[0076] The access request authentication unit 13 is for determining whether or not to grant access when an access request is received. The access request authentication unit 13 includes an access request receiving unit 131, an authentication unit 132, and a data output unit 133.

[0077] The access request receiving unit 121 receives the access request sent from the access request source. The access request receiving unit 121 receives the transmitted access request, along with the attached product ID and hash value. Since the operation of the access request receiving unit 121 involves communication with the external value information management device 1, it is performed, for example, via the communication module 34.

[0078] The authentication unit 132 determines whether or not to permit the viewing request. The information and data for which a viewing request has been received are, in fact, undisclosed information not stored in the distributed ledger 200. Therefore, even if a viewing request is received, it cannot accept the request without restriction. Thus, the authentication unit 132 determines whether or not to permit the viewing request based on the viewing request and the information attached to it. For example, the authentication unit 132 may permit the viewing request if it can confirm that the requester is a consumer user of the target product.

[0079] Based on the authentication unit 132's determination that viewing is permitted, the data output unit 133 transmits the local management information D111 on the local server 2 that received the viewing request to the value information management device 1 that made the viewing request. The operation of the data output unit 133 also involves communication with the external value information management device 1, and is therefore executed, for example, via the communication module 34.

[0080] <Value information management method of the first embodiment> Figure 12 is a flowchart showing the registration process performed by the local management information processing unit 11. First, local management information is received (S12a). This operation is performed by the local management information receiving unit 111. Next, a hash value is calculated (S12b). This operation is performed by the hash value calculation unit 112. Next, the local management information D111 and the hash value are stored in the local server 2 (S12c). This operation is performed by the local management information storage unit 113 and the local server 2. Next, blockchain management information is prepared (S12d). This operation is performed by the blockchain management information preparation unit 114. Finally, the blockchain management information is stored in the distributed ledger 200 of the blockchain BC (S12e). This operation is performed by the blockchain management information storage unit 115.

[0081] Figure 13 is a flowchart showing the browsing process performed by the browsing unit 12 and the authentication process performed by the browsing request authentication unit 13. The value information management device 1 that performs the browsing process and the value information management device 1 that performs the authentication process are different devices. For example, the value information management device 1b that performs the browsing process belongs to company B, and the value information management device 1a that performs the authentication process belongs to company A.

[0082] First, Company B's value information management device 1b accepts a viewing request (S13a). This operation is performed by the viewing request acceptance unit 121 of Company B's value information management device 1b. Next, Company B's value information management device 1b requests blockchain management information (S13b). This operation is performed by the blockchain management information request unit 122 of Company B's value information management device 1b. Next, Company B's value information management device 1b accepts blockchain management information D112 (S13c). This operation is performed by the blockchain management information acceptance unit 123 of Company B's value information management device 1b. Next, Company B's value information management device 1b obtains query destination information (S13d). This operation is performed by the query destination information acquisition unit 124 of Company B's value information management device 1b. Next, Company B's value information management device 1b requests the query destination to view the data (S13e). This operation is performed by the data request unit 125 of Company B's value information management device 1b.

[0083] At this point, Company A's value information management device 1a, which has been requested to view the data, begins the authentication process.

[0084] First, Company A's value information management device 1a accepts the access request (S13f). This operation is performed by Company A's access request receiving unit 131 of Company A's value information management device 1a. Next, Company A's value information management device 1a determines whether access is permitted or not (S13g). This operation is performed by Company A's authentication unit 132 of Company A's value information management device 1a. If Company A's authentication unit 132 determines that access is permitted (S13g: YES), it retrieves the requested information from Company A's local server 2 and transmits it to Company B's value information management device 1b (S13h). On the other hand, if Company A's authentication unit 132 determines that access is not permitted (S13g: NO), it transmits a message to Company B's value information management device 1b indicating that access is not permitted (S13i).

[0085] At this point, the browsing process by Company B's value information management device 1b resumes.

[0086] First, Company B's value information management device 1b acquires data transmitted from Company A's value information management device 1a (S13j). This operation is performed by the data receiving unit 126 of Company B's value information management device 1b. Next, Company B's value information management device 1b determines whether the hash values ​​match (S13k). This operation is performed by the data verification unit 127 of Company B's value information management device 1b. Then, if the hash values ​​match, Company B's value information management device 1b displays the data transmitted from Company A's value information management device 1a. Conversely, if the hash values ​​do not match, Company B's value information management device 1b displays a message indicating that the data transmitted from Company A's value information management device 1a does not match the contents of the blockchain management information D112 obtained in step S13c.

[0087] <Use case of the first embodiment> Next, with reference to Figures 14 to 18, several use cases of the first embodiment of the value information management device, value information management system, value information management method, and value information management program P100 will be described. These use cases include the basic operations of the value information management device, such as data input and data display. Although these operations have already been described, they will be briefly illustrated again as an enumeration of the operations of the value information management device.

[0088] The first use case of the first embodiment is data input. As shown in Figure 14, first, user U14 inputs management data D141 via user interface 10S (S14a). Management data D141 may be understood to correspond to local management information D111 shown in Figure 11. User interface 10S may also be understood to mean value information management device 1. Next, user interface 10S calculates a hash value (S14b). Next, user interface 10S stores local information D142, which includes management data D141 and the hash value, in database V14 (S14c). Next, user interface 10S processes a portion of management data D141 and the hash value into blockchain registration format (S14d). Then, user interface 10S stores the information D143 processed into blockchain registration format in blockchain BC. The information D143 processed into blockchain registration format may be understood to correspond to blockchain management information D112 shown in Figure 11.

[0089] The second use case of the first embodiment is the verification of data stored in blockchain BC. As shown in Figure 15, first, user U15 operates the user interface 10S to request the retrieval of data stored in blockchain BC (S15a). Next, the user interface 10S queries blockchain BC for the requested data (S15b). Blockchain BC, upon receiving the query, sends the requested data to the user interface 10S. Next, the user interface 10S retrieves the data sent from blockchain BC (S15c). Finally, the user interface 10S displays the retrieved data (S15d).

[0090] The third use case of the first embodiment is the display of the product supply chain. As shown in Figure 16, first, user U16 operates the user interface 10S to request a search for the product supply chain (S16a). Next, the user interface 10S queries blockchain BC for data (S16b). Blockchain BC, upon receiving the query, sends the requested data to the user interface 10S. Next, the user interface 10S retrieves the data sent from blockchain BC (S16c). Next, the user interface 10S extracts only the supply chain data for the target product. This operation is the linking of pre-shipment product IDs and post-shipment product IDs. Finally, the user interface 10S displays the supply chain (S16e).

[0091] The fourth use case of the first embodiment is the request for detailed data. As shown in Figure 17, user U17 operates the user interface 10S to request the acquisition of detailed data for the target product (S17a). Next, the user interface 10S queries blockchain BC for data (S17b). Blockchain BC, upon receiving the query, sends the requested data to the user interface 10S. Next, the user interface 10S retrieves the data sent from blockchain BC (S17c). Next, the user interface 10S confirms the query destination for the target product (S17d). Next, the user interface 10S queries the target product management server V17a for detailed data (S17e). The target product management server V17a here can be understood as corresponding to the local server 2 mentioned above. The target product management server V17a, upon receiving the query, sends the requested detailed data to the user interface 10S. Next, the user interface 10S retrieves the data sent from the target product management server V17a (S17f). Next, the user interface 10S verifies the hash value. This operation can be understood as corresponding to the operation of the data verification unit 127 described above. Then, the user interface 10S stores the detailed data in the server V17b (S17h).

[0092] The fifth use case of the first embodiment is the retrieval and visualization of detailed supply chain history data. As shown in Figure 18, first, user U18 operates the user interface 10S to request the display of detailed product data associated with the target product (S18a). Next, the user interface 10S checks the supply chain of the target product (S18b). Next, the user interface 10S requests detailed product data associated with the target product (S18c). The server V18, upon receiving the request, transmits the requested detailed data. Next, the user interface 10S obtains the supply chain data associated with the target product (S18d). Next, the user interface 10S extracts latitude and longitude information from the detailed data (S18e). Next, the user interface 10S displays the product history data generated from the detailed data (S18f). Next, the user interface 10S performs plotting on map data from the latitude and longitude information (S18g). Next, the user interface 10S displays map data (S18h).

[0093] <Effects of the First Embodiment> The value information management device includes a local management information receiving unit 111 that receives first identification information attached to a first object accepted by a first user to identify the first object, second identification information attached to the second object when the first user passes the first object to a second user as a second object, and second value information relating to the second object; a hash value calculation unit 112 that calculates a hash value using the first identification information, the second identification information and the second value information; and a local management information storage unit 113 that stores blockchain management information including the hash value, the first identification information and the second identification information on the blockchain.

[0094] The value information management method includes the steps of: receiving first identification information attached to a first object accepted by a first user to identify the first object; second identification information attached to a second object when the first user passes the first object to a second user as a second object, and second value information relating to the second object; calculating a hash value using the first identification information, the second identification information and the second value information; and storing blockchain management information including the hash value, the first identification information and the second identification information on the blockchain.

[0095] The value information management program P100 causes the computer to function as a local management information receiving unit 111 that receives first identification information attached to a first object accepted by a first user and identifying the first object, second identification information attached to a second object when the first user passes the first object to a second user as a second object, and second value information relating to the second object; a hash value calculation unit 112 that calculates a hash value using the first identification information, second identification information and second value information; and a local management information storage unit 113 that stores blockchain management information including the hash value, first identification information and second identification information on the blockchain.

[0096] The value information management device 1, the traceability management system 100 which is a value information management system, the value information management method, and the value information management program P100 calculate a hash value using the first identification information, which is the pre-shipment product ID, the second identification information, which is the post-shipment product ID, and the second value information. Then, blockchain management information including the hash value, the pre-shipment product ID, and the post-shipment product ID is stored in the blockchain BC. As a result, the blockchain management information includes the hash value generated by the pre-shipment product ID and the post-shipment product ID, and by using this hash value, the relationship between the first object and the second object can be confirmed. Consequently, the reliability of the value information can be ensured even when the transfer of value is repeated among multiple participants.

[0097] The value information management device 1 includes a viewing request authentication unit 13 that determines whether or not to allow another user to view the value information stored in the local server 2, which is a value information storage unit. With this configuration, the user can control where the value information is made public. As a result, the confidentiality of the value information can be ensured.

[0098] The value information management device 1 includes contact information for requesting access to value information in the blockchain management information. With this configuration, a user who wishes to access value information can request access to the value information from a user who has the authority to disclose the value information.

[0099] The value information management device 1 includes a viewing unit 12 for requesting access to first value information relating to a first object. The viewing unit 12 includes a blockchain management information receiving unit 123 that acquires blockchain management information relating to the first object stored in blockchain BC, a query destination information acquisition unit 124 that extracts query destination information for obtaining first value information relating to the first object from the blockchain management information relating to the first object, and a data request unit 125 that requests permission from the authentication unit 132 for the user to access the local server 2 where the first value information is stored, based on the query destination information. With this configuration, a user who wishes to view value information can request access to the value information from a user who has the authority to disclose value information.

[0100] The viewing unit 12 of the value information management device 1 includes a data verification unit 127 that checks whether the hash value included in the blockchain management information relating to the first object matches the hash value obtained using the first value information and first identification information obtained by the viewing processing unit. With this configuration, it is possible to check whether the information stored in the blockchain has been tampered with.

[0101] <Second Embodiment> Next, with reference to Figures 19 to 22, the second embodiment of the value information management device, value information management system, value information management method, and value information management program P100 will be described. In the first embodiment, the value information management device 1 was owned by each participant involved in the supply chain. In other words, each participant involved in the supply chain individually owned a device that had the functions of registering information, requesting viewing, and authenticating viewing. In contrast, as shown in Figure 19, the value information management device of the second embodiment is owned by an administrator who is not directly involved in the supply chain. The management device 50, which is the value information management device owned by the administrator, has the functions of registering information and authenticating viewing. The administrator may be, for example, a third party not related to competition law.

[0102] According to the traceability management system 100A shown in Figure 19, participants involved in the supply chain store information in a distributed ledger 200 via the management device 50. Furthermore, participants involved in the supply chain can request to view detailed data from the management device 50, and if permitted, they can view the detailed data.

[0103] Figure 20 shows the user terminal device 40 and the functional blocks that make up the user terminal device 40, as well as the functional blocks that make up the management device 50, as shown in Figure 19.

[0104] The user terminal device 40 includes a local management information processing unit 41 and a browsing processing unit 42 as functional components implemented in the processor 31. The local management information processing unit 41 further includes a local management information input unit 411 and a local management information output unit 412. In the second embodiment, the user terminal device 40 does not have a function to calculate a hash value, a function to generate blockchain management information D112 including a hash value, or a function to store information in the distributed ledger 200 of blockchain BC. The user terminal device 40 has a function to transmit local management information D111 that it wishes to store to the management device 50. This function is implemented by the local management information output unit 412.

[0105] Similarly, the browsing processing unit 42 of the second embodiment has some of the functions of the value information management device 1 of the first embodiment, but does not have other functions. The browsing processing unit 42 has a browsing request receiving unit 421, a browsing request output unit 422, a data confirmation unit 423, and a data display unit 424. The browsing processing unit 42 of the second embodiment has a function to request the management device 50 to view detailed data, a function to confirm the detailed data transmitted from the management device 50, and a function to display the detailed data. The function to request the management device 50 to view detailed data is realized by the browsing request output unit 422. In other words, the browsing processing unit 42 of the second embodiment does not have a function to obtain query destination information from blockchain management information D112, nor a function to request the query destination value information management device to view detailed data.

[0106] Furthermore, the user terminal device 40 has the function to access its own distributed ledger 200 in blockchain BC. In other words, the user terminal device 40 can obtain blockchain management information D112 stored in the distributed ledger 200. This function makes it possible to monitor for tampering with the distributed ledger 200, as will be described later. It is also possible to monitor for tampering by the central management system.

[0107] The management device 50 includes a local management information processing unit 51 and a viewing request authentication unit 52 as functional components implemented on the processor 31. Furthermore, the management device 50 has a management server 53 for storing detailed data. In other words, in the first embodiment, the detailed data was held by each participant involved in the supply chain and stored in the value information management device 1, which had restricted access from the outside. In contrast, in the second embodiment, the detailed data is stored in the management server 53 of the management device 50. Similar to the first embodiment, access to the management server 53 is restricted from participants involved in the supply chain.

[0108] The local management information processing unit 51 includes a local management information receiving unit 510, a hash value calculation unit 511, a local management information storage unit 512, a blockchain management information preparation unit 513, and a blockchain management information storage unit 514. Since the specific details of these are the same as in the first embodiment, a detailed explanation will not be repeated.

[0109] The browsing request authentication unit 52 includes an authentication unit 521 and a data provision unit 522. The authentication unit 521 determines whether or not to allow browsing of the detailed data to be viewed, which is stored in the management server 53, in response to a browsing request sent from the user terminal device 40. The conditions for this determination may be the same as those for the authentication unit 132 in the first embodiment. If browsing is permitted, the browsing request authentication unit 52 sends the detailed data to the requesting user terminal device 40 via the data provision unit 522.

[0110] In the first embodiment, viewing detailed data required a two-step process: obtaining the contact information included in the blockchain management information D112, and then sending a viewing request to the contact. In contrast, in the second embodiment, since the management device 50 holds the detailed data, viewing the detailed data can be achieved simply by deciding whether or not to permit the viewing request.

[0111] <Value information management method according to the second embodiment> Figure 21 is a flowchart showing the registration process performed by the local management information processing unit 41 of the user terminal device 40 and the local management information processing unit 51 of the management device 50. First, local management information is received (S21a). This operation is performed by the local management information input unit 411 of the user terminal device 40. Next, the local management information is transmitted to the management device 50 (S21b). This operation is performed by the local management information output unit 412 of the user terminal device 40. Next, local management information D111 is received (S21c). This operation is performed by the local management information processing unit 51 of the management device 50. Next, a hash value is calculated (S21d). This operation is performed by the hash value calculation unit 511 of the management device 50. Next, local management information D111 and the hash value are stored in the management server 53 (S21e). This operation is performed by the local management information storage unit 113 of the management device 50 and the management server 53. Next, blockchain management information is prepared (S21f). This operation is performed by the blockchain management information preparation unit 513 of the management device 50. Then, the blockchain management information is stored in the distributed ledger 200 of blockchain BC (S21g). This operation is performed by the blockchain management information storage unit 514 of the management device 50.

[0112] Figure 22 is a flowchart showing the browsing and authentication processes performed by the browsing processing unit 42 of the user terminal device 40 and the browsing request authentication unit 52 of the management device 50. First, the browsing request is accepted (S22a). This operation is performed by the browsing request acceptance unit 421 of the user terminal device 40. Next, the browsing request is sent to the management device 50 (S22b). This operation is performed by the browsing request output unit 422 of the user terminal device 40.

[0113] At this point, the management device 50, which has been requested to view the data, starts the authentication process.

[0114] First, the management device 50 accepts the access request (S22c). Next, the management device 50 determines whether access is permitted or not (S22d). This operation is performed by the authentication unit 521 of the management device 50. If the authentication unit 521 of the management device 50 determines that access is permitted (S22d: YES), it retrieves the requested information from the management server 53 and sends it to the requesting user terminal device 40 (S22e). On the other hand, if the authentication unit 521 of the management device 50 determines that access is not permitted (S22d: NO), it sends a message to the requesting user terminal device 40 indicating that access is not permitted (S22f).

[0115] Then, the browsing process by the user terminal device 40 resumes.

[0116] First, the user terminal device 40 acquires the data transmitted from the management device 50 (S22g). Next, the user terminal device 40 determines whether the hash values ​​match (S22h). This operation is performed by the data verification unit 127 of the user terminal device 40. Then, if the hash values ​​match (S22h: YES), the user terminal device 40 displays the data transmitted from the management device 50 (S22j). Conversely, if the hash values ​​do not match (S22h: NO), the user terminal device 40 displays that the data transmitted from the management device 50 does not match the contents of the blockchain management information D112 acquired in another step (S22k).

[0117] <Use case of the second embodiment> Next, with reference to Figures 23 to 25, we will describe some use cases of the second embodiment, which is a value information management device, a value information management system, a value information management method, and a value information management program P100.

[0118] The first use case of the second embodiment is data storage. In the first use case, we assume that data storage is performed successfully. As shown in Figure 23(a), first, the user terminal device 40a requests the management device 50 to register transaction data (P3a1). Next, the management device 50 stores the transaction data transmitted from the user terminal device 40 in the management server 53 (P3a2). Next, the management device 50 stores the transaction data in the distributed ledger 200 managed by the management server 53 of the blockchain BC (P3a3). As a result, the transaction data is also shared with the distributed ledgers 200a and 200b managed by participants involved in the supply chain belonging to the blockchain BC. Next, the management device 50 notifies the user terminal device 40 that requested the registration of transaction data of the registration ID (P3a4). The registration request allows users to verify whether the data they requested to be registered has been correctly registered in BC by checking the hash value associated with this registration ID. In other words, it is possible to monitor data tampering by the central administrator. For example, if the hash value of the data originally requested to be registered was "3xxxxxxxx", but the hash value registered by the central administrator is "2xxxxxxxx", it is possible to detect the possibility that the data is being managed as different data.

[0119] The second use case of the second embodiment is also data storage. In the second use case, we assume that an error occurs due to insufficient inventory. As shown in Figure 23(b), first, the user terminal device 40a requests the management device 50 to register transaction data (P3b1). Next, the management device 50 checks the inventory quantity at the shipping source (P3b2). Let's assume that the check reveals that the inventory quantity is insufficient. Next, the management device 50 notifies the user terminal device 40, which requested the registration of transaction data, of an error message due to insufficient inventory (P3b3).

[0120] The third use case of the second embodiment is the granting of access rights. In the third use case, we assume that the granting of access rights is successfully performed. As shown in Figure 24(a), first, the user terminal device 40b requests the management device 50 to grant access rights (P4a1). Here, access can be understood as meaning accessing predetermined information on the management server 53 of the management device 50. The management device 50 confirms the relationship between the requesting user who requested the granting of access rights and the user who registered the data to be accessed (P4a2). For example, if the requesting user who requested the granting of access rights and the user who registered the data to be accessed match, the management device 50 may grant access rights to the requesting user. Then, the user terminal device 40 obtains the desired detailed data (P4a3).

[0121] The fourth use case of the second embodiment is data verification, which is performed following the third use case. As shown in Figure 24(b), the user terminal device 40 obtains the desired detailed data (P4a3) and then obtains a registration hash value from the distributed ledger 200b managed by the company (P4b4). Next, the user terminal device 40 calculates a hash value using the detailed data obtained from the management device 50. Then, the user terminal device 40 compares the registration hash value obtained from the distributed ledger 200 with the hash value obtained by calculation (P4b5). As a result, if a match is confirmed between these hash values, it can be confirmed that the information stored in the distributed ledger 200b in blockchain BC has not been tampered with. It is also possible to monitor for tampering by the central management system.

[0122] The fifth use case of the second embodiment is also data verification, which is performed following the third use case. As shown in Figure 25(a), the user terminal device 40 obtains the desired detailed data (P4a3) and then obtains a registered hash value from the distributed ledger 200b managed by the company (P4b4). Next, the user terminal device 40 calculates a hash value using the detailed data obtained from the management device 50. Then, the user terminal device 40 compares the registered hash value obtained from the distributed ledger 200 with the hash value obtained by calculation (P5a6). If it is confirmed that these hash values ​​do not match, it can be confirmed that the information stored in the distributed ledger 200 in blockchain BC has been tampered with. It is also possible to monitor for tampering by the central management system.

[0123] The sixth use case of the second embodiment is the granting of access rights. The sixth use case assumes that the granting of access rights was not performed successfully. As shown in Figure 25(b), first, the user terminal device 40 requests detailed data from the management device 50 (P5b1). Next, the management device 50 checks the data associated with the product ID (P5b2). Next, the management device 50 confirms that the requesting user does not have access rights. Then, the management device 50 sends an access error message to the requesting user terminal device 40 indicating that the user does not have access rights (P5b3).

[0124] <Effects of the second embodiment> The traceability management system 100A, which is a value information management system of the second embodiment, includes: a local management information output unit 412 that outputs a pre-shipment product ID that is attached to a first object accepted by the first user and identifies the first object, and a post-shipment product ID that identifies the second object and value information related to the second object, which is attached to the second object when the first user hands over the first object to the second user as the second object; a local management information receiving unit 510 that receives the pre-shipment product ID, post-shipment product ID and value information from the local management information output unit 412; a hash value calculation unit 511 that calculates a hash value using the pre-shipment product ID, post-shipment product ID and value information; and a blockchain management information storage unit 514 that stores blockchain management information including the hash value, pre-shipment product ID and post-shipment product ID on the blockchain. The local management information output unit 412 is managed by the first user. The local management information receiving unit 510, the hash value calculation unit 511 and the blockchain management information storage unit 514 are managed by an administrator separate from the first user and the second user.

[0125] <Examples> Figures 26 and 27 are examples of the operation screen of the value information management device 1. Figure 26 is an example of the data input screen used when inputting local management information in step S12a. In the example of Figure 26, the operation screen G36 displays windows for inputting the origin latitude and longitude, destination latitude and longitude, pre-shipment product ID, post-shipment product ID, CI value, shipment quantity, and data inquiry URL. The operation screen G36 also displays a window for uploading an audit trail file. Below these input sections, there is a button for recording data. By clicking this button, the entered data is stored in the local server 2 and the distributed ledger 200 of blockchain BC after predetermined processing. Furthermore, a hash value may be calculated in response to the click of the registration button and displayed below the registration button.

[0126] Figure 27 shows an example of a data entry screen used to request detailed data. Operation screen G27 displays windows for entering the product ID and the inquiry URL. After entering the information in these windows, click the "Request Information" button. The detailed data corresponding to the product ID will then be displayed below the button.

[0127] Although several embodiments of the present invention have been described above, the present invention is not limited to the embodiments described above. The present invention may be modified or applied to other claims without changing the gist of each claim. [Explanation of Symbols]

[0128] 1,1a,1b Value Information Management Device 2 Local Server 10S User Interface 11 Local Management Information Processing Unit 12. Reading Section 13 Access Request Authentication Section 30 Computers 40, 40a, 40b User terminal devices 41 Local Management Information Processing Unit 42 Browsing Processing Unit 50 Management device 51 Local Management Information Processing Unit 52 Access Request Authentication Section 53 Management Server 100,100A Traceability Management System 111 Local Management Information Reception Unit (Information Reception Unit) 112 Hash Value Calculation Unit 113 Local Management Information Storage Unit 114 Blockchain Management Information Preparation Department (Information Preparation Department) 115 Blockchain Management Information Storage Unit (Information Storage Unit) 121 Access Request Reception Section 122 Blockchain Management Information Request Department 123 Blockchain Management Information Reception Department 124 Contact Information Acquisition Department 125 Data Request Section 126 Data Reception Section 127 Data Verification Section 128 Data display section 131 Access Request Receiving Unit 132 Authentication Department 133 Data Output Section 200,200a, 200b distributed ledger 411 Local Management Information Input Section 412 Local Management Information Output Unit 421 Access Request Reception Section 422 Viewing Request Output Unit 423 Data Verification Section 424 Data display section 510 Local Management Information Reception Unit 511 Hash Value Calculation Unit 512 Local Management Information Storage Unit 513 Blockchain Management Information Preparation Department 514 Blockchain Management Information Storage Unit 521 Certification Department 522 Data Provision Department BC Blockchain D41 Detailed Data D43 Blockchain Registration Information D111 Local Administration Information D112 Blockchain Management Information D113 Hash value generation information P100 Value Information Management Program

Claims

1. An information receiving unit that receives first identification information attached to a first object accepted by a first user to identify the first object, and second identification information attached to the second object when the first user hands over the first object to a second user as a second object, and second value information relating to the second object, A hash value calculation unit that calculates a hash value using the first specific information, the second specific information, and the second value information, A value information management device comprising: an information storage unit that stores blockchain management information including the hash value, the first specific information and the second specific information on a blockchain.

2. The value information management device according to claim 1, further comprising an authentication unit that determines whether or not to allow the second user to view the value information storage unit that stores the second value information.

3. The value information management device according to claim 1 or 2, further comprising an information preparation unit that includes contact information for requesting access to the second value information in the blockchain management information.

4. The system includes a browsing processing unit for requesting access to first value information relating to the first object, The aforementioned browsing processing unit A blockchain management information receiving unit that acquires the blockchain management information relating to the first object stored in the blockchain, A query information acquisition unit extracts query information for obtaining first value information relating to the first object from the blockchain management information relating to the first object, The value information management device according to claim 2, further comprising: a browsing processing unit that requests the authentication unit permission for the first user to browse the value information storage unit where the first value information is stored based on the aforementioned inquiry information.

5. The aforementioned browsing processing unit The value information management device according to claim 4, further comprising a data verification unit that checks whether the hash value included in the blockchain management information relating to the first object matches the hash value obtained using the first value information and first identification information obtained by the viewing processing unit.

6. An information output unit outputs first identification information that identifies the first object and is attached to the first object accepted by the first user, and second identification information that identifies the second object and second value information relating to the second object, which is attached to the second object when the first user hands over the first object to the second user as a second object. An information receiving unit that receives the first specific information, the second specific information, and the second value information from the information output unit, A hash value calculation unit that calculates a hash value using the first specific information, the second specific information, and the second value information, The system includes an information storage unit that stores blockchain management information, including the hash value, the first specific information, and the second specific information, on the blockchain. The information output unit is managed by the first user, The information receiving unit, the hash value calculation unit, and the information storage unit are managed by an administrator separate from the first user and the second user in this value information management system.

7. A step of receiving first identification information attached to a first object accepted by the first user, which identifies the first object, and second identification information attached to the second object when the first user hands over the first object to the second user as a second object, which identifies the second object and second value information relating to the second object, A step of calculating a hash value using the first specific information, the second specific information, and the second value information, A value information management method comprising the step of storing blockchain management information, including the hash value, the first specific information and the second specific information, on a blockchain.

8. Computers, An information receiving unit that receives first identification information attached to a first object received by a first user to identify the first object, and second identification information attached to the second object when the first user hands over the first object to a second user as a second object, and second value information relating to the second object. A hash value calculation unit that calculates a hash value using the first specific information, the second specific information, and the second value information, A value information management program that functions as an information storage unit for storing blockchain management information, including the hash value, the first specific information, and the second specific information, on the blockchain.

Images