Information management method, information management device, and information management program

Abstract

Provided is an information management server that manages information provided by a plurality of suppliers (SR) forming a supply chain (SC). In an information management method performed by the information management server, item identification information (UID) to be attached to an item (IM) shipped from a supplier (SR) to identify the item (IM) is issued to a supplier terminal. A storage hash value (HVs) obtained by hashing history information (TRI) pertaining to the item (IM) is obtained together with the item identification information (UID) and is stored in a BC database (BDB) in association with the item identification information (UID).

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based on Patent Application No. 2022-47192 filed in Japan on March 23, 2022, and Patent Application No. 2022-112030 filed in Japan on July 12, 2022, and the contents of the base applications are incorporated by reference in their entirety. [Technical field]

[0002] The disclosure of this specification relates to information management technology. [Background technology]

[0003] Patent Document 1 describes a supply chain management method in which transaction records of items are acquired from traders constituting a supply chain, and a hash value obtained by hashing the acquired transaction records is returned to the trader. The hash value provided to the trader is attached to the item shipped from the trader. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. 2021 / 002226 Summary of the Invention

[0005] It is assumed that the type, format, and capacity of transaction records recorded by each trader will differ from one trader to another. Therefore, in a supply chain management method that acquires transaction records from individual traders, as in Patent Document 1, there is a risk that data processing for storing transaction records will become complicated due to the fact that the contents of the transaction records differ from one trader to another.

[0006] The present disclosure relates to an information management method capable of simplifying data processing for information management. , love information management device , and Information Management Programs The purpose is to provide.

[0007] In order to achieve the above object, one aspect disclosed herein is an information management method implemented by a computer (100c) for managing information provided by multiple reporters (SR) constituting a supply chain (SC), comprising: Verification data (Dd) for verifying a stored hash value (HVs) obtained by hashing history information (TRI) related to an item (IM) shipped from the reporter is provided to a destination terminal (50, 250) associated with the reporter (S11, S313), and a verification hash value (HVd) generated by a hashing process using the verification data is obtained from the destination terminal (S12, S315); Items shipped by the reporter To The item identification information (UID) that is attached and identifies the item in question, Departure line tip At the end Issued (S21~S26), Protection Pipe Hash Value The item identification information is acquired (S31). If the verification hash value is a correct value, it is determined that the stored hash value obtained from the destination terminal is a correct value (S35, S316). The stored hash value is stored in the database (BDB) in a state linked to the item identification information (S36). In the process executed by at least one processor (11), It is said to be an information management method that includes Also, one disclosed aspect is an information management method implemented by a computer (100c) for managing information provided from multiple reporters (SR) that make up a supply chain (SC), the method including the steps of issuing item identification information (UID) attached to an item (IM) shipped from the reporter and identifying the item to a destination terminal (50, 250) linked to the reporter (S21-S26), acquiring a stored hash value (HVs) obtained by hashing history information (TRI) related to the item together with the item identification information (S31), and storing the stored hash value in a database (BDB) in a state linked to the item identification information (S36), in which, in the step of issuing item identification information, the item identification information is issued to an intermediate layer terminal as an issue destination terminal operated in an intermediate layer (ML), and in the step of acquiring the stored hash value, the intermediate layer terminal acquires data to be stored (DSS) in which the item identification information is linked to the stored hash value generated by a reporter terminal operated by the reporter.

[0008] One disclosed aspect is an information management device that manages information provided by multiple reporters (SR) that make up a supply chain (SC), and includes an issuing unit (32) that issues item identification information (UID) that is attached to an item (IM) shipped from the reporter and identifies the item to an issuing destination terminal (50, 250) linked to the reporter, an acquiring unit (33) that acquires a stored hash value (HVs) that hashed history information (TRI) related to the item together with the item identification information, and a storage unit (34) that stores the stored hash value in a database (BDB) while being linked to the item identification information, a hash verification unit (31) that provides the destination terminal with verification data (Dd) for verifying the stored hash value obtained from the destination terminal, obtains from the destination terminal a verification hash value (HVd) generated by a hashing process using the verification data, and determines that the stored hash value obtained from the destination terminal is correct if the verification hash value is correct; The information management device is provided with the following. Also, one disclosed aspect is an information management device that manages information provided by multiple reporters (SR) that make up a supply chain (SC), and includes an issuing unit (32) that issues item identification information (UID) attached to an item (IM) shipped from the reporter and identifying the item to an issuing terminal (50, 250) linked to the reporter, an acquiring unit (33) that acquires a stored hash value (HVs) obtained by hashing historical information (TRI) related to the item together with the item identification information, and a storage unit (34) that stores the stored hash value in a database (BDB) while being linked to the item identification information, wherein the issuing unit issues the item identification information to an intermediate layer terminal as an issuing terminal operated in the intermediate layer (ML), and the acquiring unit acquires storage target data (DSS) in which the intermediate layer terminal links the item identification information to the stored hash value generated by a reporter terminal operated by the reporter. Another disclosed aspect is an information management program that is executed by a computer (100c) and manages information provided from a plurality of reporters (SR) that make up a supply chain (SC), and provides verification data (Dd) for verifying a stored hash value (HVs) obtained by hashing history information (TRI) related to an item (IM) shipped from the reporter to a destination terminal (50, 250) associated with the reporter (S11, S313), and obtains a verification hash value (HVd) generated by a hashing process using the verification data from the destination terminal (50, 250) (S12, S314). 15), issuing item identification information (UID) attached to an item shipped from the reporter and identifying the item to the destination terminal (S21-S26), acquiring a stored hash value (HVs) together with the item identification information (S31), determining that the stored hash value acquired from the destination terminal is correct if the verification hash value is correct (S35, S316), and storing the stored hash value in a database (BDB) linked to the item identification information (S36). Another disclosed aspect is an information management program that is implemented by a computer (100c) and manages information provided from multiple reporters (SR) that make up a supply chain (SC), and causes at least one processor (11) to execute processes including issuing item identification information (UID) that is attached to an item (IM) shipped from the reporter and identifies the item to a destination terminal (50, 250) linked to the reporter (S21-S26), acquiring a stored hash value (HVs) that hashed history information (TRI) related to the item together with the item identification information (S31), and storing the stored hash value in a database (BDB) in a state linked to the item identification information (S36).In the process of issuing item identification information, the item identification information is issued to an intermediate layer terminal that serves as an issue destination terminal operated in the intermediate layer (ML), and in the process of acquiring the stored hash value, the intermediate layer terminal acquires stored data (DSS) in which the item identification information is linked to the stored hash value generated by the reporter terminal operated by the reporter.

[0009] In these aspects, a stored hash value obtained by hashing history information related to an item is acquired together with previously issued item identification information, and is stored in a database in association with the item identification information. In this way, by hashing the history information before transmitting it, the information acquired from each reporter can be fixed. As a result, it is possible to simplify data processing for information management.

[0010] In addition, the reference numbers in parentheses in the claims merely show an example of the correspondence with the specific configurations in the embodiments described below, and do not limit the technical scope in any way. Furthermore, claims that are not explicitly stated in the claims may be combined together unless there is a particular problem with the combination. [Brief description of the drawings]

[0011] [Figure 1] 1 is a diagram showing an overall view of a traceability management system according to a first embodiment of the present disclosure. [Diagram 2] FIG. 1 is a diagram showing systems, terminals, etc. related to traceability management. [Diagram 3] FIG. 2 is a block diagram showing an electrical configuration of the traceability management system and a supplier terminal. [Figure 4] FIG. 2 is a diagram for explaining details of a hashing application. [Diagram 5] 10 is a flowchart showing details of an application distribution process performed by the application distribution server. [Figure 6] 13 is a flowchart showing details of an application verification process mainly performed by a hash verification unit of the information management server. [Figure 7] 13 is a flowchart showing details of an ID issuing process mainly performed by an issuing unit of the information management server. [Figure 8] 11 is a diagram for explaining details of item identification information and attached labels. FIG. [Figure 9] 13 is a flowchart showing details of a hash storage process performed by the information management server. [Figure 10] 13 is a flowchart showing details of an ID federation process performed by a manufacturer terminal or a supplier terminal, and an information management server. [Figure 11] 13 is a flowchart showing details of an ID verification process performed by a manufacturer terminal, a supplier terminal, an information management server, or the like. [Figure 12]13 is a flowchart showing details of an ID output process performed by a supplier terminal. [Figure 13] 13 is a flowchart showing details of a history disclosure process mainly performed by a disclosure processing unit of the information management server. [Figure 14] FIG. 11 is a diagram showing an overall picture of processing performed mainly by a traceability management system according to a second embodiment of the present disclosure. [Figure 15] FIG. 13 is a diagram showing an overall picture of processing performed mainly by a traceability management system according to a third embodiment of the present disclosure. [Figure 16] FIG. 13 is a diagram showing details of a query system included in a traceability management system of the third modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, a number of embodiments will be described with reference to the drawings. In addition, by assigning the same reference numerals to corresponding components in each embodiment, duplicated descriptions may be omitted. When only a part of the configuration is described in each embodiment, the configuration of the other embodiment described above can be applied to the other parts of the configuration. In addition to the combination of configurations explicitly stated in the description of each embodiment, configurations of multiple embodiments can be partially combined together even if not explicitly stated, as long as there is no particular problem with the combination.

[0013] First embodiment The supply chain SC in the first embodiment of the present disclosure shown in Fig. 1 is a connection between traders for delivering industrial products, agricultural products, marine products, etc. to end users US. The supply chain SC is constructed by including multiple suppliers SR and finished product manufacturers MF as traders. The final products PD supplied by the supply chain SC may be various goods such as automobiles, batteries, semiconductors, fresh food, marine products, food, flowers, medicines, and chemicals.

[0014] As a specific example, a supply chain SC for delivering industrial products to end users US includes material miners, material producers, processors, etc. as suppliers SR. Each supplier SR processes raw materials such as virgin materials and recycled materials, or (and) items IM, etc. delivered from a previous process supplier SR, and ships them as another item IM to a next process supplier SR or a finished product manufacturer MF. The supply chain SC may further include transporters and distributors related to the distribution of items IM and final products PD. In addition, the supply chain SC may further include end users US that use the final products PD, as well as secondary users U2 and recyclers RC that reuse, rebuild, recycle, dispose, etc. of the final products PD.

[0015] The supply chain SC is managed by an administrator ADM shown in Figures 1 and 2. The administrator ADM may be, for example, an agent entrusted with management operations by a finished product manufacturer MF, or an agency entrusted with management and audit operations by a supervisory agency having supervisory authority over the category to which the final product PD belongs. The administrator ADM operates a traceability management system 100 and manages various information recorded in the supply chain SC.

[0016] The traceability management system 100 can communicate with the supplier terminal 50, the manufacturer terminal 10a, the user terminal 10b, etc., through the network NW. If the final product PD (e.g., an automobile, etc.) has a communication function, the traceability management system 100 may also be able to communicate with the final product PD. The traceability management system 100 stores information acquired through the network NW in a state that is substantially impossible to tamper with. In addition, the traceability management system 100 collects information under the management of each supplier SR, etc., in response to a request from the administrator ADM (or supervisory agency), the end user US, the finished product manufacturer MF, etc., and discloses the information to the requester.

[0017] The supplier terminal 50 is an information processing device operated by the supplier SR. The supplier terminal 50 is linked to each individual supplier SR. The supplier terminal 50 accumulates history information TRI related to the item IM. The history information TRI is information such as from which trading company (previous process supplier SR) raw materials or parts are purchased, and when they were acquired. Furthermore, information related to costs, and the amount of greenhouse gas emissions (carbon footprint) emitted by the manufacture of the item IM, etc. may be recorded as the history information TRI.

[0018] The history information TRI is stored in the supplier terminal 50 and is disclosed to the outside depending on the situation. For example, if a defect occurs or there is a possibility that a defect occurs in the item IM or the final product PD, the history information TRI is provided to other traders or end users US, etc. through the administrator ADM by the information disclosure process (see FIG. 13) described below. The provided history information TRI is used for investigating the cause of the defect, etc. As described above, at least a part of the history information TRI becomes information for realizing the traceability of the item IM.

[0019] The supplier terminal 50 receives from the traceability management system 100 the issuance of unique identification information (hereinafter, item identification information UID) for identifying the item IM. The item identification information UID is a unique identification that does not overlap with other items (see FIG. 8). The item identification information UID may be issued not only to parts, but also to recycled materials, for example. The item identification information UID is attached to the item IM shipped from the supplier SR, and is delivered together with the item IM to the trader in the next process. The supplier terminal 50 associates a hash value (hereinafter, stored hash value HVs) generated from the history information TRI for a specific item IM with the issued item identification information UID, and uploads the hash value to the traceability management system 100.

[0020] The manufacturer terminal 10a is an information processing device operated by the finished product manufacturer MF. In an ID linking process (see FIG. 10) described later, the manufacturer terminal 10a generates information linking a final product PD shipped from the finished product manufacturer MF with one or more items IM used in the final product PD. Specifically, ID link information LI linking item identification information UID attached to the item IM with product identification information PID identifying the final product PD manufactured using the item IM is generated as linking information. The final product PD becomes an associated object related to the item IM. When multiple items IM are used in one final product PD, multiple pieces of ID link information LI are generated. The manufacturer terminal 10a uploads the generated one or more pieces of ID link information LI to the traceability management system 100.

[0021] The supplier terminal 50 also performs ID linking processing in the same manner as the manufacturer terminal 10a. The supplier terminal 50 generates ID link information LI that links the item identification information UID of the received item IM or recycled material with the item identification information UID of the item IM to be shipped. The supplier terminal 50 uploads the generated one or more pieces of ID link information LI to the traceability management system 100.

[0022] The user terminal 10b is an information processing device operated by the secondary user U2 or the recycler RC. For example, a smartphone or a tablet terminal can be used as the user terminal 10b. When the final product PD is disassembled at the recycler RC and the usage of the item IM used in the final product PD is changed, the user terminal 10b uploads the change information XI to the traceability management system 100.

[0023] Specifically, when the secondary user U2 discards the item IM or when the secondary user RC recycles the item IM into a recyclable material, the traceability management system 100 is notified of change information XI indicating the loss of the item IM. When the secondary user U2 reuses the item IM in another final product PD or when the item IM removed from the final product PD is used for another purpose, the traceability management system 100 is notified of change information XI requesting the correction or transfer of the ID link information LI. As an example, when a battery pack for driving removed from an electric vehicle is used as a replacement battery for another vehicle, or as a stationary storage battery or a backup storage battery in case of a power outage, the traceability management system 100 is notified of change information XI.

[0024] The final product PD collects operation information OI as the end user US uses the final product PD. As an example, if the final product PD is an electric vehicle, the operation information OI collected includes mileage, charge / discharge history, and current battery capacity (State of Health, SOH). The final product PD links the collected operation information OI to its own product identification information PID and uploads it to the traceability management system 100. At least one of the collection and uploading of the operation information OI may be performed by a user terminal 10b owned by the end user US.

[0025] Next, the traceability management system 100 and the supplier terminal 50 will be described in further detail with reference to FIGS.

[0026] The traceability management system 100 includes an application distribution server 100a and an information management server 100s. The application distribution server 100a and the information management server 100s are information processing devices mainly including a control circuit 100c. The control circuit 100c includes a processor 11, a RAM (Random Access Memory) 12, a storage unit 13, an input / output interface 14, and a bus connecting these, and functions as a computer that performs arithmetic processing. The processor 11 is hardware for arithmetic processing that is coupled to the RAM 12, and executes a program stored in the storage unit 13.

[0027] The application distribution server 100a functions as a server device that distributes the hashed application HAP. The hashed application HAP is an application program installed in each supplier terminal 50. The hashed application HAP performs a hashing process in each supplier terminal 50 based on a rule specified by the administrator ADM to hash the raw data including at least the history information TRI, and generates a stored hash value HVs. The raw data is the original data before the hashing process is performed. The hashed application HAP is periodically updated to enable maintenance of security in traceability management. The application distribution server 100a provides the latest hashed application HAP to each supplier terminal 50 by performing an application distribution process (see FIG. 5) in the control circuit 100c based on the application distribution program.

[0028] In the application distribution process, the application distribution server 100a determines whether or not there is an update trigger (S101). For example, the version information and expiration date of the hashed application HAP can be used as the update trigger. When the version of the hashed application HAP specified by the administrator ADM is updated based on the version information of the hashed application HAP (see FIG. 4), the application distribution server 100a activates the update trigger (S101: YES). The update trigger may also be activated when a supplier terminal 50 using an old version of the hashed application HAP that has become unusable based on the expiration date of the hashed application HAP is identified. Based on the activation of the update trigger, the application distribution server 100a transmits a notification requesting an application update to the supplier terminal 50 to be updated (S102).

[0029] After transmitting the update request notification, the application distribution server 100a waits for a reply from the supplier terminal 50 until a predetermined waiting time has elapsed or a timeout occurs due to a specified number of errors (S104: YES). When the application distribution server 100a receives a notification of update execution from the supplier terminal 50 that received the update request notification (S103: YES), the application distribution server 100a provides the supplier terminal 50 with the program data of the latest hashed application HAP (S105, see also the dashed arrow in FIG. 4).

[0030] Note that the version check of the hashed application HAP is not limited to being performed starting from the administrator ADM side, and may be performed starting from the supplier SR side (supplier terminal 50). Specifically, after starting the system, the supplier terminal 50 inquires of the application distribution server 100a or the information management server 100s about the validity of the hashed application HAP held by the supplier terminal 50. If the supplier terminal 50 receives a result of the inquiry indicating that the hashed application HAP is valid, the supplier terminal 50 generates and uploads a hash value, which will be described later. On the other hand, if the supplier terminal 50 receives a result of the inquiry indicating that the hashed application HAP is invalid, the supplier terminal 50 requests the application distribution server 100a to provide the latest hashed application HAP, and updates the hashed application HAP to the latest hashed application HAP.

[0031] Furthermore, the hashed application HAP may be distributed by, for example, a platform provider of an operating system that operates the supplier terminal 50. In such a case, the latest hashed application HAP is provided by the administrator ADM to the platform provider, and is distributed to each supplier terminal 50 from a server device operated by the platform provider.

[0032] The information management server 100s functions as an information management device that manages information related to the item IM. The storage unit 13 of the information management server 100s stores an information management program for causing the control circuit 100c to execute the information management method according to the present disclosure. The information management server 100s has functional units such as a hash verification unit 31, an issuing unit 32, an acquiring unit 33, and a storing unit 34 by executing the information management program by the processor 11 (see FIG. 3).

[0033] The hash verification unit 31 verifies the validity of the stored hash value HVs obtained from the supplier terminal 50. Specifically, the hash verification unit 31 performs an application verification process (see FIG. 6) to check whether the stored hash value HVs was generated by a hashing application HAP designated by the administrator ADM and whether the stored hash value HVs was generated correctly (see the solid arrow in FIG. 4).

[0034] The hash verification unit 31 can perform the application verification process at any timing. Specifically, the application verification process may be performed when the hashed application HAP is updated in the supplier terminal 50, when the item identification information UID is issued, when the stored hash value HVs is received, when a predetermined period of time has elapsed since the previous verification was performed, or the like.

[0035] In the application verification process, the hash verification unit 31 provides the supplier terminal 50 with verification data Dd by transmission (S11). The verification data Dd is dummy data that is input to the hashed application HAP in the supplier terminal 50 in place of the history information TRI. The hash verification unit 31 receives a hash value (hereinafter, verification hash value HVd) generated by a hashing process using the verification data Dd in the hashed application HAP from the supplier terminal 50 (S12, also see FIG. 4). The hash verification unit 31 obtains additional information AI (see FIG. 4) together with the verification hash value HVd. The additional information AI includes at least a character string indicating the provider of the hashed application HAP and the version of the hashed application HAP.

[0036] After transmitting the verification data Dd, the hash verification unit 31 waits for a reply of the verification hash value HVd until a predetermined waiting time has elapsed. If a timeout occurs (S13: YES) due to the elapse of the predetermined waiting time, the hash verification unit 31 makes an NG determination that the validity of the stored hash value HVs cannot be guaranteed (S18).

[0037] When the hash verification unit 31 receives the verification hash value HVd and the additional information AI (S12: YES), it determines whether or not an appropriate hashed application HAP is running on the supplier terminal 50 based on the additional information AI (S14, see also FIG. 4). For example, when an inappropriate hashed application HAP, such as an application of unknown origin or an old version that is no longer usable, is used on the supplier terminal 50 (S14: NO), the hash verification unit 31 makes an NG determination (S18).

[0038] When the hash verification unit 31 determines that the appropriate hashed application HAP is being used in the supplier terminal 50 (S14: YES), it calculates a hash value for comparison (S15, see also FIG. 4). The hash value for comparison is a value calculated when the verification data Dd is input to the hashed application HAP of the version indicated by the additional information AI.

[0039] The hash verification unit 31 compares the received verification hash value HVd with a comparison hash value to check whether the hashed application HAP is operating normally (S16, see also FIG. 4). If the verification hash value HVd is different from the comparison hash value (S16: NO), the hash verification unit 31 makes an NG determination (S18). On the other hand, if the verification hash value HVd is identical to the comparison hash value (S16: YES), the hash verification unit 31 determines that the hashed application HAP is operating normally in the supplier terminal 50 and that the validity of the stored hash value HVs can be guaranteed (S17). As described above, the hash verification unit 31 can verify the operation of the hashed application HAP without requesting the supplier terminal 50 to disclose the history information TRI.

[0040] The issuing unit 32 issues the above-mentioned item identification information UID (see also FIG. 8) to the supplier terminal 50 linked to each supplier SR by performing an ID issuing process (see FIG. 7). The item identification information UID is, for example, a 32-digit character string. The issuing unit 32 performs the ID issuing process in response to a request from, for example, a supplier SR (supplier terminal 50), and issues as many item identification information UIDs as the supplier SR requires. In addition to issuing such item identification information UIDs at any time, the issuing unit 32 can also perform batch processing in which a predetermined number of item identification information UIDs are issued in bulk in response to a request from the supplier terminal 50.

[0041] In the ID issuing process, the issuing unit 32 grasps information (hereinafter, application ID, see FIG. 8) that identifies an application (traceability management system 100) that manages information (S21). Furthermore, the issuing unit 32 grasps the issue date and time of the item identification information UID and the number of item identification information UIDs to be issued at one time (hereinafter, issue number) (S22).

[0042] The application ID is a value that does not change each time the item identification information UID is issued, and is a fixed character string that is set in advance. The application ID is information that identifies the issuer (administrator ADM), purpose, field of use, etc. of the item identification information UID. The application ID may be changed for each issuee (supplier SR). In this case, the application ID can also be used as information that identifies the issuee of the item identification information UID. The issue date and time and the number of issues are values ​​that change each time the item identification information UID is issued, in other words, they are variable information VI (see FIG. 8) that changes for each item IM. Such variable information VI may be used to increase the randomness of the item identification information UID. In addition, in order to compensate for the difficulty of use caused by excessive randomness, a part of the code used as the readable code CDs (see FIG. 8) described later (for example, multiple digits at the end) may be made continuous to improve workability.

[0043] The issuing unit 32 generates a hash value (hereinafter, referred to as an identification hash value HVi, see FIG. 8) by hashing original data including at least the application ID and variable information VI (S23). Furthermore, the issuing unit 32 sets a code version, a pattern flag, and an activation deadline of the item identification information UID (S24). The code version, the pattern flag, and the activation deadline are characteristic information CI (see FIG. 8) indicating the characteristics of the item identification information UID.

[0044] The code version is an identifier indicating, for example, the version of the item identification information UID. The pattern flag is an identifier specifying the scrambling rule used to generate the item identification information UID. By using the pattern flag, it is possible to understand the scrambling rule and decrypt the scrambling without accessing the information management server 100s. The activation deadline is information indicating the end of the period during which the item identification information UID can be validly used in the traceability management system 100. An item identification information UID that has passed the activation deadline cannot be handled by the information management server 100s or the hashing application HAP.

[0045] The issuing unit 32 generates item identification information UID using the application ID, variable information VI, identification hash value HVi, and characteristic information CI (S25). In detail, the issuing unit 32 converts the original data including the application ID and variable information VI and the identification hash value HVi into a fixed-length character string based on the scrambling rule corresponding to the pattern flag. By such scrambling process, a random character string different from the pre-conversion is generated without compromising the content before the conversion. Therefore, the application ID, variable information VI, and identification hash value HVi are embedded in the item identification information UID in a restorable (composite) state. In addition, the issuing unit 32 mixes the code version, pattern flag, and activation deadline into a predefined position (e.g., the beginning part) of the item identification information UID (character string). Furthermore, the issuing unit 32 mixes variable information VI such as the issue time and the number of issues into a predefined position (e.g., the end part) of the item identification information UID (character string). The issuing unit 32 transmits the generated item identification information UID to the supplier terminal 50 which is the source of the issuance request (S26). After the issuing unit 32 issues the item identification information UID, the hash verifying unit 31 may perform an application verification process (see FIG. 6).

[0046] The acquisition unit 33 acquires information transmitted from the supplier terminal 50. The storage unit 34 stores the information acquired by the acquisition unit 33 in a blockchain database (hereinafter, BC database, see also FIG. 16) BDB. The BC database BDB stores data to be stored, such as the stored hash value HVs, the associated information AI, and the ID link information LI, in a substantially tamper-proof state using the technology of the blockchain BC. As an example, the BC database BDB stores the acquired data to be stored as a transaction in a block of a private blockchain BC. The BC database BDB hashes information stored in one block and stores it in the next block, making it difficult to tamper with the data to be stored stored in each block. As another example, the BC database BDB may store a hash value generated from the data to be stored in a block of a consortium or public blockchain BC, making it substantially impossible to tamper with the data to be stored. In addition, as a configuration equivalent to the BC database BDB, a server (hereinafter, BC server) that stores the blockchain BC and a database server that stores other data to be stored may be provided separately. Furthermore, only the server that stores the blockchain BC may be operated.

[0047] The acquiring unit 33 and the storage unit 34 execute a hash storage process (see FIG. 9) to store the stored hash value HVs and the like acquired from the supplier terminal 50 in the BC database BDB. In the hash storage process, the acquiring unit 33 acquires the stored hash value HVs and the associated information AI and the like by receiving them from the supplier terminal 50 together with the item identification information UID (S31). For example, after the item identification information UID is issued, the acquiring unit 33 refers to the result of the most recent application verification process (see FIG. 6) and determines whether the hashed application HAP is operating normally in the supplier terminal 50 (S32).

[0048] If the most recent application verification process has been judged as NG (S32: NO), the storage unit 34 transmits an error notification to the supplier terminal 50 (S38) to notify that the storage of the stored hash value HVs is not possible. On the other hand, if the most recent application verification process has been judged as normal (S32: YES), the hash verification unit 31 performs the application verification process (see FIG. 6) again (S33). If the second application verification process has been judged as NG (S34: NO), an error notification is also transmitted to the supplier terminal 50 (S38). If the second application verification process has been judged as normal (S34: YES), that is, if the verification hash value HVd is a correct value, the hash verification unit 31 judges that the currently acquired stored hash value HVs is also a correct value (S35). The application verification process (S34) after receiving the stored hash value HVs may be omitted.

[0049] Based on the validation of the stored hash value HVs by the hash verification unit 31, the storage unit 34 stores the stored hash value HVs and the associated information AI, etc. in the BC database BDB in a state linked to the item identification information UID (S36). In addition, the storage unit 34 also stores an issue history indicating the issue destination (supplier SR) of the item identification information UID in the BC database BDB in a state linked to the item identification information UID. The storage unit 34 transmits a storage completion notification to notify the supplier terminal 50 of the completion of storage of the stored hash value HVs, etc. (S37).

[0050] The supplier terminal 50 is mainly configured with a control circuit 50c. The control circuit 50c includes a processor 51, a RAM 52, a storage unit 53, an input / output interface 54, and a bus connecting these, and functions as a computer that performs arithmetic processing. The processor 51 is hardware for arithmetic processing that is combined with the RAM 52, and executes an application program (hashing application HAP) stored in the storage unit 53. A display 56, a scanner 58, a printer 59, and the like are electrically connected to the input / output interface 54. Furthermore, an input device such as a keyboard may be connected to the supplier terminal 50, for example, for error processing, etc.

[0051] The display 56 is a display device mainly composed of a liquid crystal panel or an organic EL panel. The display 56 displays various images on the screen based on the display control by the control circuit 50c. For example, the display 56 displays an image presenting history information TRI based on the data to be provided, an image notifying error information received from the information management server 100s, and the like. The display 56 may have a touch panel function that accepts user operations.

[0052] The scanner 58 is a reading device that reads the attached label LB (see FIG. 8). The scanner 58 includes an area sensor that includes, for example, a two-dimensional array of CCD elements. The attached label LB is a paper medium or a film medium on which a two-dimensional code CDq and a readable code CDs are printed. The two-dimensional code CDq is, for example, a QR code (registered trademark). The two-dimensional code CDq records the item identification information UID. The readable code CDs is a character string of a predetermined length that corresponds to a part of the item identification information UID. As an example, the last seven digits of the item identification information UID are used as the readable code CDs and are written on the attached label LB in a readable state by the user of the supplier terminal 50. The scanner 58 reads the two-dimensional code CDq printed on the attached label LB and outputs the item identification information UID extracted from the two-dimensional code CDq to the control circuit 50c. The two-dimensional code CDq and the readable code CDs may be displayed on a display device such as a display and electronic paper. In this case, a display device such as a display or electronic paper corresponds to the attached label LB.

[0053] The printer 59 is an output device that outputs the attached label LB. The printer 59 acquires data of the two-dimensional code CDq and the readable code CDs generated from the new item identification information UID provided by the information management server 100s from the control circuit 50c. The printer 59 prints the two-dimensional code CDq and the readable code CDs on a paper medium (such as a sticker) and outputs it as an attached label LB. The attached label LB is attached to the outer surface of the item IM, for example, and is distributed together with the item IM. The location where the attached label LB is attached is not limited to the item body, and may be a package, a shipping tag, a wrapping, a certificate, or the like. Note that, instead of the attached label LB output on demand from the printer 59, an attached label LB that is printed and issued in advance by the administrator ADM and provided to the supplier SR may be distributed together with the item IM. The two-dimensional code CDq may be directly laser engraved or printed on the item IM. In this case, instead of the printer 59, a laser marker, an inkjet printer, or the like can be used as an output device.

[0054] Here, instead of the two-dimensional code CDq, a one-dimensional code such as a barcode recording the item identification information UID may be printed on the attached label LB. Furthermore, the item identification information UID may be recorded as electronic data on a recording medium such as an RFID (radio frequency identifier) ​​or a microchip attached to the item IM. Even in this form, the readable code CDs is printed on the outer surface of the recording medium or on a label or the like that contains the recording medium so that it can be read by the user.

[0055] Furthermore, in a case where the item identification information UID is recorded on an RFID or a microchip, the supplier terminal 50 includes a reader and a writer as a reading device and an output device. The reader reads out the item identification information UID recorded as electronic data on a storage medium and outputs it to the control circuit 50c. The writer writes the electronic data of the item identification information UID generated by the control circuit 50c to the storage medium.

[0056] The supplier terminal 50 has functional units such as an ID acquisition unit 61, an information receiving unit 62, a history grasping unit 63, a hash generation unit 64, an information transmission unit 65, and an ID output unit 66 (see FIG. 3) through execution of the hashing application HAP by the processor 51. The supplier terminal 50 performs ID federation processing (see FIG. 10), ID verification processing (see FIG. 11), and ID output processing (see FIG. 12) through the cooperation of the respective functional units. As described above, the ID federation processing is also performed by the manufacturer terminal 10a of the finished product manufacturer MF to which the item IM has been delivered. That is, the functional units equivalent to the ID acquisition unit 61, the information receiving unit 62, and the information transmission unit 65 are also implemented in the manufacturer terminal 10a.

[0057] The ID acquisition unit 61 is connected to the scanner 58. In the ID linking process (see FIG. 10), the ID acquisition unit 61 acquires data of item identification information UID from the scanner 58 that reads the label LB attached to the item IM delivered to the supplier SR (S41). The ID acquisition unit 61 checks whether the acquired item identification information UID is genuine information through an ID verification process (S42).

[0058] In the ID verification process (see FIG. 11), the ID acquisition unit 61 reads out the characteristic information CI (see FIG. 8) from the character string of the item identification information UID (S61). Specifically, the ID acquisition unit 61 acquires the code version, pattern flag, and activation deadline of the item identification information UID. The ID acquisition unit 61 determines whether the item identification information UID is a valid ID within the deadline based on the activation deadline (S62).

[0059] When the ID acquisition unit 61 determines that the item identification information UID has expired (S62: YES), it determines that the item identification information UID is an invalid ID (S68). In this case, a notification indicating that the item identification information UID is invalid (hereinafter, an invalid ID notification) is displayed on the display 56. The last seven digits of the invalid item identification information UID are displayed on the display 56 together with the invalid ID notification. This allows the user (worker) to identify the item IM to which the invalid item identification information UID is attached by finding the attached label LB that includes the same readable code CDs as the seven-digit character string.

[0060] When the ID acquisition unit 61 determines that the item identification information UID is a valid ID (S62: NO), it decrypts the scrambled item identification information UID based on the code version and pattern flag information. By decoding the item identification information UID in this way, the ID acquisition unit 61 reads information such as the application ID (S63 and S64).

[0061] The ID acquisition unit 61 uses the values ​​of the application ID, the issue date and time, and the number of issues to calculate a comparison hash value to be compared with the identification hash value HVi (S65). The comparison hash value is calculated by the same calculation method as the generation process of the identification hash value HVi in the issuing unit 32.

[0062] The ID acquisition unit 61 compares the read identification hash value HVi with the comparison hash value (S66). If the identification hash value HVi is different from the comparison hash value (S66: NO), the ID acquisition unit 61 determines that the item identification information UID is an invalid ID (S68) and displays an invalid ID notification on the display 56. On the other hand, if the identification hash value HVi is identical to the comparison hash value (S66: YES), the ID acquisition unit 61 determines that the item identification information UID is a legitimate ID (S67).

[0063] Here, a detailed determination function for determining whether the item identification information UID is valid or invalid may be provided by the traceability management system 100. In this case, the supplier terminal 50 refers to the determination result notified by the traceability management system 100 and determines whether the item identification information UID is a legitimate ID or not. Furthermore, the above ID verification process may be performed by the manufacturer terminal 10a. For example, the manufacturer terminal 10a performs the ID verification process at the timing of acquiring the item identification information UID of the item IM delivered to the finished product manufacturer MF, and determines whether the item identification information UID of the item IM is a legitimate ID or not.

[0064] The information receiving unit 62 requests the issuing unit 32 to issue an item identification information UID to be attached to the item IM shipped from the supplier SR. The information receiving unit 62 acquires the item identification information UID issued by the issuing unit 32 by receiving it from the information management server 100s in the ID linking process (see FIG. 10) (S43). The information receiving unit 62 generates ID link information LI that links the received new item identification information UID to the item identification information UID acquired from the received item IM (S44). In addition, the information receiving unit 62 receives the verification data Dd (see FIG. 4) from the hash verification unit 31 that performs the application verification process (see FIG. 6). Note that when the ID linking process is performed in the manufacturer terminal 10a, the product identification information PID is acquired as another ID to be linked to the item identification information UID (S43).

[0065] The history grasping unit 63 acquires the history information TRI generated by the supplier SR. The history grasping unit 63 may automatically acquire data that becomes the history information TRI from another server device installed at the base of the supplier SR, or may acquire data manually input by a user as the history information TRI. The history grasping unit 63 stores the history information TRI in the supplier database SDB in a state in which it is linked to the item identification information UID acquired by the ID acquisition unit 61. The information stored in the supplier database SDB is only the history information TRI, in other words, only the original data of the information to be hashed. Information that is not stored in the supplier database SDB may be deleted after confirmation of the intention of deletion is performed each time. Furthermore, the history grasping unit 63 extracts information linked to the specified item identification information UID from the history information TRI accumulated in the supplier database SDB based on a request from the information management server 100s that performs a history disclosure process (see FIG. 13) described later.

[0066] The hash generation unit 64 prepares pre-processed data to include the history information TRI grasped by the history grasping unit 63. The hash generation unit 64 hashes the pre-processed data to generate a stored hash value HVs. In addition, when the information receiving unit 62 receives verification data Dd (see FIG. 4), the hash generation unit 64 prepares pre-processed data including the verification data Dd instead of the history information TRI. The hash generation unit 64 hashes the pre-processed data including the verification data Dd to generate a verification hash value HVd (see FIG. 4). Furthermore, in conjunction with the generation of the stored hash value HVs and the verification hash value HVd, the hash generation unit 64 further generates additional information AI (see FIG. 4) including version information of the hashed application HAP that performed the hashing process.

[0067] The information transmitting unit 65 sequentially transmits the stored hash value HVs, the verification hash value HVd, and the associated information AI generated by the hash generating unit 64 to the acquiring unit 33. In addition, the information transmitting unit 65 transmits the ID link information LI and each ID linked by this ID link information LI to the acquiring unit 33 in the ID linking process (see FIG. 10) (S45). Each ID and the ID link information LI are acquired by the acquiring unit 33 (S51) and stored in the BC database BDB by the storage unit 34 (S52). Then, a notification indicating the completion of accumulation of the ID link information LI is provided from the storage unit 34 to the information receiving unit 62 (S53 and S46).

[0068] The ID output unit 66 is connected to the printer 59. The ID output unit 66 causes the printer 59 to output an attached label LB by performing an ID output process (see FIG. 12). The ID output unit 66 acquires data of the item identification information UID received by the information receiving unit 62 (S71). The ID output unit 66 generates a two-dimensional code CDq (see FIG. 8) in which the item identification information UID is recorded, and a readable code CDs (see FIG. 8) obtained by cutting out a part of the item identification information UID (S72 and S73). The ID output unit 66 outputs print data including the two-dimensional code CDq and the readable code CDs to the printer 59 (S74), and causes the printer 59 to print the attached label LB.

[0069] As described above, in a case where the attached label LB on which the item identification information UID is printed is provided by the manager ADM, the ID output unit 66 and the printer 59 do not need to be provided in the supplier terminal 50. In this case, the ID output process in the supplier terminal 50 is also omitted.

[0070] Next, the details of the information disclosure performed by the traceability management system 100 will be further described. The information management server 100s also functions as an information providing device that provides information related to the item IM. The storage unit 13 of the information management server 100s further stores an information providing program for causing the control circuit 100c to perform the information providing method according to the present disclosure. The information management server 100s further has a disclosure processing unit 35 as a functional unit by executing the information providing program by the processor 11.

[0071] The disclosure processing unit 35 enables the provision of history information TRI by performing a history disclosure process (see FIG. 13). The disclosure processing unit 35 receives a disclosure request for the history information TRI from the manufacturer terminal 10a, the user terminal 10b, etc. (S131). The disclosure request includes product identification information PID or item identification information UID as information specifying the final product PD or item IM that is the subject of the request. The disclosure processing unit 35 refers to the BC database BDB, extracts ID link information LI related to the specified product identification information PID or item identification information UID, and sets at least one item identification information UID that is to be collected in the history information TRI (S132).

[0072] The disclosure processing unit 35 refers to the issuance history of the BC database BDB and identifies the supplier SR requesting the provision of the history information TRI. The disclosure processing unit 35 transmits a request for providing the history information TRI together with the item identification information UID to the supplier terminal 50 of the identified supplier SR (S133). The disclosure processing unit 35 acquires the history information TRI returned from the supplier terminal 50 based on the provision request (S134).

[0073] The disclosure processing unit 35 grasps the version information of the hashing application HAP used in the hashing process of the acquired history information TRI (S135). The version information may be extracted from the BC database BDB, or may be received from the supplier terminal 50 together with the history information TRI. The disclosure processing unit 35 performs hashing process of the acquired history information TRI by the same hashing process as the hashing application HAP indicated by the version information, and calculates a hash value for comparison (S136).

[0074] The disclosure processing unit 35 extracts the stored hash value HVs associated with the item identification information UID from the BC database BDB (S137), and compares the stored hash value HVs with the recalculated comparison hash value (S138). If the comparison hash value is different from the stored hash value HVs (S138: NO), an error notification indicating the possibility that the history information TRI has been tampered with is sent to the requester of the disclosure request and the recipient of the information request (S140). On the other hand, if the comparison hash value is identical to the stored hash value HVs (S138: YES), the disclosure processing unit 35 presumes that the history information TRI has not been tampered with.

[0075] If there are multiple item identification information UIDs for which history information TRI is to be collected, the disclosure processing unit 35 repeats the processes of S133 to S138. Upon completing verification of all history information TRI, the disclosure processing unit 35 provides the collected history information TRI to the requester of the disclosure request (S139).

[0076] In the first embodiment described so far, a storage hash value HVs obtained by hashing history information TRI related to an item IM is acquired together with previously issued item identification information UID. The storage hash value HVs is then stored in the BC database BDB in association with the item identification information UID. In this way, by hashing the history information TRI and then transmitting it, the information acquired from each supplier SR, specifically, the capacity, data length, etc., can be fixed. As a result, data processing for information management can be simplified.

[0077] In more detail, the type, format, and capacity of the file recorded in the history information TRI recorded by each supplier SR differ from supplier SR to supplier SR. In addition, the management items and granularity recorded as the history information TRI may change each time or over time. Furthermore, it is expected that the number and order of steps in the processing of the item IM, etc., may also change over time. It is also expected that there may be cases where it becomes necessary to build the traceability management system 100 at a stage where the recording method of the history information TRI has not been determined at each supplier SR.

[0078] Therefore, in the information management method according to the first embodiment, a method is adopted in which the stored hash value HVs is stored in a state linked to the previously issued item identification information UID. Therefore, even if the type, format, capacity, etc. of the file in which the history information TRI is recorded differs for each supplier SR, the information management server 100s can handle fixed-length data, i.e., hash values, regardless of the state of the history information TRI for each supplier SR. As a result, even if the management items and granularity of the history information TRI change in the supplier SR, it is not necessary to change the processing content to be performed by the information management server 100s. Furthermore, even at a stage where the recording method of the history information TRI is not yet determined in the supplier SR, the traceability management system 100 can be constructed.

[0079] Additionally, in the information management method according to the first embodiment, at the stage when the history information TRI is recorded, the history information TRI is kept secret from anyone outside the supplier SR. Then, when an incident or the like occurs, a disclosure request is made only to the relevant supplier SR, and the history information TRI necessary for responding to the incident is collected in the information management server 100s. In addition, it is possible to easily and clearly verify that there is no difference between the collected history information TRI and the time of registration. Therefore, a highly convenient information management method can be provided to each trader.

[0080] In the application verification process (see FIG. 6) of the first embodiment, verification data Dd for verifying the stored hash value HVs is provided to the supplier terminal 50. Then, the verification hash value HVd generated by the hashing process using the verification data Dd is acquired by the hash verification unit 31. If the verification hash value HVd is a correct value, the hash verification unit 31 determines that the stored hash value HVs acquired from the supplier terminal 50 is a correct value. According to this verification method, the information management server 100s can verify that the generation of the stored hash value HVs by the hashing application HAP is operating correctly in the supplier terminal 50 without requesting the supplier terminal 50 to disclose the history information TRI. Therefore, even if the data processing for information management is simplified, the validity of the data stored in the information management server 100s can be guaranteed.

[0081] Furthermore, in the first embodiment, a hashing application HAP that performs hashing processing is provided to the supplier terminal 50. In this way, the use of the hashing application HAP designated by the administrator ADM is forced, so that the hashing application HAP can be updated at any timing of the administrator ADM. As a result, security is easily maintained, and the risk of tampering with the history information TRI can be further reduced.

[0082] Additionally, in the first embodiment, information indicating the version of the hashing application HAP that performed the hashing process in the supplier terminal 50 is included in the additional information AI transmitted to the information management server 100s. Therefore, even if the contents of the hashing process are changed for each version, the information management server 100s can correctly prepare a comparison hash value for verifying the stored hash value HVs, etc. As a result, it becomes easier to maintain security while simplifying data processing.

[0083] In the first embodiment, the variable information VI that changes for each item IM and the identification hash value HVi that is obtained by hashing the original data including the variable information VI are embedded in the item identification information UID. This makes it easier to avoid duplication of the item identification information UID. In addition, the validity of the item identification information UID can be easily and reliably determined in each terminal under the management of the traceability management system 100.

[0084] Furthermore, in the first embodiment, characteristic information CI such as a code version and a pattern flag is embedded in the item identification information UID. This characteristic information CI is excluded from the original data to be hashed and scrambled. Therefore, each terminal that acquires the item identification information UID can extract the identification hash value HVi and variable information VI from the item identification information UID based on the contents of the characteristic information CI. As a result, each terminal can more reliably identify that the item identification information UID is a legitimate ID issued by the administrator ADM.

[0085] In addition, in the first embodiment, a readable code CDs corresponding to a part of the item identification information UID is written on the attached label LB attached to the item IM. If such a readable code CDs is displayed on the attached label LB, even if an error occurs in one of the multiple item identification information UIDs, the user can visually identify the attached label LB that is the subject of the error. As a result, the convenience of information management can be further improved.

[0086] In the first embodiment, the stored hash values ​​HVs and the like are stored in a BC database BDB that uses the technology of the blockchain BC. As a result, the possibility of tampering with the stored hash values ​​HVs is further reduced. As a result, the accuracy of the history information TRI disclosed in response to a disclosure request can be more reliably guaranteed.

[0087] Furthermore, in the first embodiment, the information management server 100s acquires ID link information LI linking item identification information UID attached to the item IM with product identification information PID from the finished product manufacturer MF to which the item IM is delivered. The ID link information LI is stored in the BC database BDB. By accumulating such ID link information LI, the BC database BDB can reliably record the connection of the item IM from the raw materials to the final product PD. Therefore, by referring to the ID link information LI, the information management server 100s can identify all the request destinations to which the disclosure of the history information TRI is requested. As a result, highly accurate information disclosure is possible.

[0088] Additionally, in the first embodiment, the stored hash value HVs generated from the history information TRI is not recorded in the two-dimensional code CDq. Of the stored hash value HVs and the item identification information UID, only the item identification information UID is recorded in the two-dimensional code CDq. Therefore, the amount of data recorded in the two-dimensional code CDq can be reduced. As a result, the size of the two-dimensional code CDq can be reduced.

[0089] In addition, the item identification information UID of the first embodiment records an application ID and an activation expiration date, etc. With this information, it is possible to easily identify the application used for information management and to easily check the expiration date of the item identification information UID, etc. As a result, the convenience of information management can be further improved.

[0090] In the above embodiment, the manufacturer terminal 10a corresponds to the "delivery terminal", the supplier terminal 50 corresponds to the "issuance destination terminal", the control circuit 100c corresponds to the "computer", and the information management server 100s corresponds to the "information management device". The BC database BDB corresponds to the "database", the human readable code CDs corresponds to the "character string", the hashing application HAP corresponds to the "application", the attached label LB corresponds to the "attachment medium", and the ID link information LI corresponds to the "linking information". Furthermore, the supplier SR corresponds to the "reporter", the finished product manufacturer MF corresponds to the "delivery", the final product PD corresponds to the "related object", and the product identification information PID corresponds to the "related identification information". In addition, the supplier SR of the next process may correspond to the "supplier," the supplier terminal 50 of the next process may correspond to the "supplier terminal," another item IM may correspond to the "related item," and another item identification information UID may correspond to the "related identification information."

[0091] Second Embodiment The second embodiment of the present disclosure shown in FIG. 14 is a modified example of the first embodiment. In the supplier terminal 50 of the second embodiment, a general-purpose hash function (hereinafter, general-purpose hash function HF) is used for hashing processing instead of the hashing application HAP (see FIG. 4). The general-purpose hash function HF is used to calculate the storage hash value HVs and the verification hash value HVd in the supplier terminal 50, similar to the hashing application HAP. The general-purpose hash function HF may be prepared by the supplier SR, or may be specified by the administrator ADM (information management server 100s). When the general-purpose hash function HF is prepared by the supplier SR, the supplier terminal 50 transmits a notification indicating the general-purpose hash function HF to be used to the information management server 100s. By using the general-purpose hash function HF instead of the hashing application HAP, the transparency of data processing is improved from the perspective of the reporter such as the supplier SR.

[0092] The application distribution server 100a performs an application distribution process for providing a data generation application LAP to the middle layer terminal 250, instead of the application distribution process (see FIG. 5) for providing a hashed application HAP to the supplier terminal 50. In the application distribution process, the application distribution server 100a provides the program data of the latest data generation application LAP to the middle layer terminal 250 based on the occurrence of a predetermined update trigger (see FIG. 5 and S105 in FIG. 14).

[0093] The middle layer terminal 250 is an information processing device operated by the middle layer ML. The middle layer ML exists independently of the administrator ADM and the supplier SR. The middle layer ML ensures the transparency of information from the supplier SR. The middle layer ML may be prepared by the administrator ADM, or may be prepared by one or more supplier SRs. Furthermore, if the transparency is ensured and an agreement is made between the administrator ADM, the supplier SR (reporter), and the supervisory agency (auditor), the middle layer ML may be installed in a part of the environment belonging to the administrator ADM or the supplier SR. In a form in which a plurality of supplier SRs are linked to one middle layer ML, even if the transparency of information is ensured by using the universal hash function HF, the information of other supplier SRs cannot be viewed. Since the middle layer ML exists linked to the supplier SR, the middle layer terminal 250 is also a terminal linked to the supplier SR.

[0094] The intermediate layer terminal 250 is connected to the application distribution server 100a, the information management server 100s, the supplier terminal 50, and the like so as to be able to communicate with them. The intermediate layer terminal 250, like the supplier terminal 50, is mainly configured with a control circuit. The control circuit includes a processor, a RAM, a storage unit, an input / output interface, and a bus connecting these, and functions as a computer that performs arithmetic processing. The intermediate layer terminal 250 executes a data generation application LAP by the processor. The data generation application LAP causes the intermediate layer terminal 250 to perform a process of acquiring item identification information UID issued by the ID issuing process (see FIG. 7) from the issuing unit 32 (see FIG. 3), and a process of generating transmission data DSS including the item identification information UID. The intermediate layer terminal 250 can store a predetermined number of item identification information UIDs issued collectively by the batch processing by the issuing unit 32.

[0095] The middle layer terminal 250 is connected to a data logger 259. The data logger 259 records a transmission log of the transmission data DSS transmitted from the middle layer terminal 250. The data logger 259 provides a backup of the transmission data DSS transmitted to the information management server 100s to the supplier terminal 50 together with the transmission log. The transmission log records information indicating what content of data was transmitted to which destination.

[0096] The data logger 259 has a checker function. The data logger 259 checks whether the transmission data DSS transmitted to the information management server 100s (storage unit 34) and the supplier terminal 50 are identical in content. The data logger 259 records information indicating that the transmission data DSS transmitted to the storage unit 34 and the supplier terminal 50 are identical in content in a transmission log provided to the supplier terminal 50.

[0097] Next, the hash verification process performed by the hash verification unit 31 and a series of data storage processes for storing the stored hash values ​​HVs and the like in the databases BDB and SDB will be described in detail in order.

[0098] The hash verification process corresponds to the application verification process (see FIG. 6) of the first embodiment. In the hash verification process, it is checked whether the universal hash function HF is operating normally. The hash verification process is periodically performed by the hash verification unit 31. In the hash verification process, the hash verification unit 31 provides verification data Dd to the supplier terminal 50 by transmission (S11). The verification data Dd is transmitted to the universal hash function HF by the supplier terminal 50. The hash verification unit 31 acquires a verification hash value HVd generated from the verification data Dd by a hashing process using the universal hash function HF from the supplier terminal 50 (S12).

[0099] The hash verification unit 31 transmits the verification data Dd to a hash function that is the same as the universal hash function HF used in the supplier terminal 50, and calculates a hash value for comparison (S15). The hash verification unit 31 compares the received verification hash value HVd with the comparison hash value to determine whether the universal hash function HF is operating normally in the supplier terminal 50 (S16). If the verification hash value HVd is the same as the comparison hash value (S16: YES), the hash verification unit 31 determines that the universal hash function HF is operating normally (S17). In this case, the hash verification unit 31 presumes that the validity of the stored hash value HVs can be guaranteed.

[0100] The data storage process is performed by cooperation between the supplier terminal 50, the middle layer terminal 250, and the information management server 100s. The supplier terminal 50 transmits the unprocessed data including the history information TRI (see FIG. 1) to the universal hash function HF (S81) in the hash generation unit 64 (see FIG. 3), and generates a stored hash value HVs. The supplier terminal 50 transmits the stored hash value HVs from the information transmission unit 65 (see FIG. 3) to the middle layer terminal 250 (S82).

[0101] The middle layer terminal 250 acquires the stored hash value HVs transmitted from the supplier terminal 50 by reception (S91). The middle layer terminal 250 prepares one of the item identification information UIDs acquired in advance from the issuing unit 32 as the item identification information UID to be linked to the stored hash value HVs. Furthermore, the middle layer terminal 250 generates additional information AI to be added to the stored hash value HVs. The additional information AI includes application information related to the data generation application LAP and item information related to the item IM (see FIG. 1). The application information includes information indicating the version of the data generation application LAP currently in operation, information indicating the application provider, and the like. The item information includes information indicating the type of item IM linked to the stored hash value HVs, information indicating the supplier SR, and the like.

[0102] The middle layer terminal 250 generates transmission data DSS by processing to link the item identification information UID with the stored hash value HVs and the additional information AI (S92). The middle layer terminal 250 transmits the transmission data DSS to the storage unit 34 via the data logger 259 (S93). In addition, the middle layer terminal 250 also provides the supplier terminal 50 with transmission data DSS having the same content as that transmitted to the storage unit 34. At this time, the data logger 259 records a transmission log of the transmission data DSS.

[0103] In the data storage process, the information management server 100s executes steps similar to those in the hash storage process (see FIG. 9) of the first embodiment. Specifically, the information management server 100s acquires the transmission data DSS by receiving it from the middle layer ML at the acquisition unit 33 (see FIG. 3) (S31). The storage unit 34 refers to the verification result in the hash verification process, and if it is determined that the universal hash function HF is operating normally (S32: YES), it determines that the currently acquired stored hash value HVs is a correct value (S35). Based on the confirmation of the validity of the transmission data DSS including the stored hash value HVs, the storage unit 34 stores the stored hash value HVs and the associated information AI, etc. in the BC database BDB in a state linked to the item identification information UID (S36).

[0104] The supplier terminal 50 prepares a backup of the transmission data DSS by receiving information from the data logger 259 via the information receiving unit 62 (S83). The supplier terminal 50 associates the transmission data DSS and the transmission log as the backup with the history information TRI (see FIG. 1) and stores them in the supplier database SDB (S84).

[0105] The second embodiment described so far also has the same effect as the first embodiment, and since the information sent from a reporter such as a supplier SR to an administrator ADM is converted to a fixed length by hashing, it is possible to simplify data processing for information management.

[0106] Additionally, in the second embodiment, item identification information is issued to the middle layer terminal 250 as an issue destination terminal operated in the middle layer ML. Then, the information management server 100s acquires transmission data DSS in which the middle layer terminal 250 links the item identification information UID to the stored hash value HVs generated by the supplier SR and which is operated by the supplier SR. As described above, if the data generation process linking the stored hash value HVs and the item identification information UID is performed in the middle layer ML, it becomes unnecessary to force the supplier SR to use the hashing application HAP. As a result, the transparency of information processing is improved, and it becomes possible to lower the psychological hurdle of introducing the traceability management system 100.

[0107] In the second embodiment, the supplier terminal 50 is provided with transmission data DSS having the same contents as the item identification information UID and the storage hash value HVs stored in the BC database BDB. The transmission data DSS provided to the supplier terminal 50 is then stored as a backup in the supplier database SDB operated by the supplier SR. Therefore, if the administrator ADM steals the transmission data DSS (data to be stored), the occurrence of such stealing can be verified using the backup on the supplier SR side. As a result, the administrator ADM and the reporter can share the fact that no unauthorized data extraction has occurred, which can further improve the transparency of information processing.

[0108] In the second embodiment, the transmission data DSS corresponds to the “data to be stored” and the “reporter stored data”, and the supplier database SDB corresponds to the “reporter database”. In addition, the supplier terminal 50 corresponds to the “reporter terminal”, and the intermediate tier terminal 250 corresponds to the “destination terminal”.

[0109] Third embodiment The third embodiment of the present disclosure shown in FIG. 15 is a modified example of the second embodiment. In the third embodiment, the supplier terminal 50 also uses the universal hash function HF for hashing processing. Meanwhile, in the third embodiment, the application distribution server 100a, the middle layer ML, and the middle layer terminal 250 (see FIG. 14) are omitted. Therefore, the terminal to which the item identification information UID is issued is the supplier terminal 50, as in the first embodiment. Furthermore, in the third embodiment, the data storage processing including the hash verification processing is performed by cooperation between the supplier terminal 50 and the information management server 100s. The data storage processing of the third embodiment will be described in detail below.

[0110] The supplier terminal 50 requests the information management server 100s to generate verification data Dd (S381). When the information management server 100s receives the request sent by the supplier terminal 50 (S311), it determines whether or not to permit the request. If the request is from a pre-registered legitimate supplier terminal 50, the information management server 100s permits the request (S312) and provides the verification data Dd to the supplier terminal 50 (S313).

[0111] The information management server 100s prepares a hash function that is the same as the universal hash function HF presented in advance by the supplier terminal 50. Then, the information management server 100s transmits the verification data Dd transmitted to the supplier terminal 50 to the prepared hash function as well. As a result, a pair of hash values ​​for comparison is calculated (S314).

[0112] The supplier terminal 50 acquires the verification data Dd provided by the information management server 100s (S382). In addition, the supplier terminal 50 transmits the unprocessed data including the history information TRI (see FIG. 1) to the universal hash function HF (S383). The supplier terminal 50 calculates the first verification hash value HVd1 and the second verification hash value HVd2 in addition to the stored hash value HVs.

[0113] The first verification hash value HVd1 is a verification hash value HVd generated by a hashing process using the verification data Dd before the hashing process of the unprocessed data. The second verification hash value HVd2 is a verification hash value HVd generated by a hashing process using the verification data Dd before the hashing process of the unprocessed data. The supplier terminal 50 inputs the verification data Dd, the unprocessed data, and the verification data Dd in this order into the universal hash function HF to calculate the first verification hash value HVd1, the stored hash value HVs, and the second verification hash value HVd2. Note that the verification data Dd used to generate the verification hash values ​​HVd1 and HVd2 may have the same content or different content.

[0114] The supplier terminal 50 generates the additional information AI. The supplier terminal 50 links the first verification hash value HVd1, the stored hash value HVs, and the second verification hash value HVd2 with the additional information AI to the item identification information UID, and generates the transmission data DSS. In the transmission data DSS, the stored hash value HVs is sandwiched between the first verification hash value HVd1 and the second verification hash value HVd2. The supplier terminal 50 transmits the transmission data DSS to the information management server 100s (S384).

[0115] The information management server 100s acquires the transmission data DSS by receiving it from the supplier terminal 50 (S315). The information management server 100s compares the first verification hash value HVd1 and the second verification hash value HVd2 included in the transmission data DSS with a comparison hash value, and checks the accuracy of each of the verification hash values ​​HVd1 and HVd2. If both of the verification hash values ​​HVd1 and HVd2 are identical to the comparison hash value, the information management server 100s determines that the universal hash function HF is operating normally and that the validity of the stored hash value HVs can be guaranteed (S316).

[0116] The information management server 100s deletes the first verification hash value HVd1 and the second verification hash value HVd2 from the transmission data DSS based on the confirmation of the validity of the stored hash value HVs. The information management server 100s stores the storage target data, which is obtained by linking the item identification information UID with the incidental information AI and the stored hash value HVs, in the BC database BDB (S317).

[0117] The third embodiment described so far also has the same effects as the first and second embodiments, and allows for simplification of data processing for information management. In addition, in the third embodiment, the first verification hash value HVd1 and the second verification hash value HVd2 are acquired from the supplier terminal 50. Then, when the verification hash values ​​HVd1 and HVd2 before and after the stored hash value HVs are both correct values, the stored hash value HVs, which is the main body, is determined to be a correct value. Therefore, even if the universal hash function HF is used in the supplier terminal 50, the validity of the stored hash value HVs can be guaranteed.

[0118] (Other embodiments) Although several embodiments of the present disclosure have been described above, the present disclosure should not be construed as being limited to the above-described embodiments, and can be applied to various embodiments and combinations within the scope not departing from the gist of the present disclosure.

[0119] The form of the item identification information UID in the above embodiment, specifically, the number of digits of the character string, and the number and type of embedded information, etc., may be changed as appropriate. Furthermore, the identification hash value HVi and the variable information VI may not be scrambled. In addition, the readable code CDs may be omitted. Furthermore, an identifier that replaces the readable code CDs and is a symbol or the like that can be distinguished by the user may be written on the attached label LB, etc. Furthermore, the product identification information PID may also be issued to the finished product manufacturer MF by the information management server 100s, similar to the item identification information UID. In such a modified example, the finished product manufacturer MF also corresponds to the "reporter."

[0120] In the first modified example of the above embodiment, in addition to the item identification information UID, the storage hash value HVs is also recorded in the two-dimensional code CDq. Furthermore, on the attached label LB in the second modified example of the above embodiment, another two-dimensional code recording the storage hash value HVs is printed next to the two-dimensional code CDq recording the item identification information UID. As described above, the storage hash value HVs may also be distributed together with the item IM.

[0121] In the above embodiment, a request for information disclosure may be made from the upstream process side (upstream side) of the supply chain SC to the downstream process side (downstream side), or from the downstream side to the upstream side. A request for information disclosure to the upstream side makes it possible to track history information TRI of raw materials or parts used in an item IM or a final product PD when a defect occurs in the item IM or the final product PD. In contrast, a request for information disclosure to the downstream side makes it possible to identify an item IM or a final product PD in a downstream process in which the item IM is used when a defect is found in the item IM.

[0122] The traceability management system 100 of the third modified example of the above embodiment is divided into a record system and a query system 200 shown in Fig. 16. The record system is mainly configured with the information management server 100s (see Fig. 1) of the above embodiment. However, the configuration equivalent to the disclosure processing unit 35 is omitted from the information management server 100s of the record system.

[0123] On the other hand, the inquiry system 200 is a system corresponding to the disclosure processing unit 35 in the above embodiment, and performs history disclosure processing (see FIG. 13). The inquiry system 200 is composed of a collection server 200a, a BC database BDB, etc. The inquiry system 200 may be operated by an institution other than the management institution that manages the record system. As an example, the responsible business entity of the final product PD may be the management institution for the inquiry system 200.

[0124] The collection server 200a includes a reception unit 201, a data collating unit 202, and a data providing unit 203. The reception unit 201 receives a request for disclosure of the history information TRI from the inquiry terminal 110 of the inquirer IQ who requests the provision of the history information (S131). The inquiry terminal 110 may be the above-mentioned manufacturer terminal 10a and user terminal 10b. The inquiry terminal 110 may include not only the user terminal 10b operated by the secondary user U2 or the recycler RC, but also the user terminal 10b (end user terminal) owned by the above-mentioned end user US. In other words, the inquirer IQ may be any one of the finished product manufacturer MF, the secondary user U2, the recycler RC, and the end user US.

[0125] The inquirer IQ can make a start request using product identification information PID (e.g., a vehicle ID, etc.) that identifies the final product PD. The reception unit 201 receives the product identification information PID provided from the inquiry terminal 110, and identifies the item identification information UID from which the history information TRI is to be collected, from the product identification information PID (S132). Furthermore, the reception unit 201 identifies the stored hash value HVs associated with the set item identification information UID.

[0126] The reception function for receiving the product identification information PID may be installed in an external processing device different from the collection server 200a. On the other hand, the identification function for identifying the stored hash value HVs from the item identification information UID is installed inside the traceability management system 100 or the inquiry system 200.

[0127] Based on the item identification information UID identified by the reception unit 201, etc., the BC database BDB identifies the supplier SR requesting the provision of the history information TRI. The BC database BDB transmits a request for the history information TRI together with the item identification information UID to the supplier terminal 50 of the identified supplier SR (S133). Each supplier SR becomes a reporter that discloses the history information TRI. The supplier terminal 50 provides data such as the history information TRI stored in the supplier database SDB to the collection server 200a.

[0128] The data collating unit 202 acquires data such as the history information TRI returned from the supplier terminal 50 (S134). The data collating unit 202 cooperates with the BC database BDB to sequentially identify the upstream suppliers SR in the supply chain SC and collect the history information TRI. The data collating unit 202 performs a verification process (before-after check) to check whether the anteroposterior relationship of the hash values ​​is correctly established, and checks whether the acquired history information TRI has been tampered with (S135 to S138). The data collating unit 202 passes the history information TRI that has been confirmed not to have been tampered with to the data providing unit 203.

[0129] The data providing unit 203 generates data to be provided to the inquirer IQ by editing the verified history information TRI delivered from the data collating unit 202. The data providing unit 203 provides the generated data to be provided to the inquiry terminal 110 of the inquirer IQ, who is the source of the disclosure request (S139).

[0130] In the above embodiment, the issuance of item identification information UID to traders such as distributors may not be performed. A terminal linked to the distributor links the history information TRI recorded during the distribution process to the item identification information UID attached to the item IM being transported, and uploads it to the information management server 100s. As a result, the history information TRI during the distribution process is also stored in the BC database BDB in a state linked to the item identification information UID, and can be provided to each trader.

[0131] The data logger 259 used in the second embodiment can also be applied to the first and third embodiments. Specifically, the data logger 259 is connected to the supplier terminal 50, and records the item identification information UID and the stored hash value HVs transmitted from the supplier terminal 50. As a result, a backup whose identity with the data acquired by the information management server 100s is guaranteed can be stored in the supplier database SDB together with the history information TRI.

[0132] In the transmission data DSS of the third embodiment, the stored hash value HVs is sandwiched on both sides by the first verification hash value HVd1 and the second verification hash value HVd2. However, as long as security is ensured by the operation of the system, the stored hash value HVs does not need to be sandwiched on both sides by the verification hash values. Specifically, in the transmission data DSS of the fourth modification of the third embodiment, only the first verification hash value HVd1 at the front or only the second verification hash value HVd2 at the rear is attached to the stored hash value HVs.

[0133] Each function of the application distribution server 100a and the information management server 100s may be provided by one server device. The application distribution server 100a and the information management server 100s may be an on-premise server device physically managed by an administrator ADM or a platform provider, or may be a virtual configuration provided on a cloud. In addition, the BC database BDB and the supplier database SDB may also be built in a virtual file server provided on a cloud.

[0134] Various hash functions may be used to generate the storage hash value HVs, the verification hash value HVd, and the identification hash value HVi in the above embodiment. A hash function has the property that it does not output the same hash value from different inputs, and it is practically impossible to guess the input from the output hash value. If it has such a property, for example, encryption algorithms such as SHA-256, SHA-1, SHA-2, and SHA-3 can be used appropriately according to the required output length (number of bits). In addition, the hash functions that calculate each hash value may be the same as each other, or may be different from each other.

[0135] In the above embodiment, each function provided by the traceability management system 100 can be provided by software and hardware that executes it, software only, hardware only, or a complex combination of these. Similarly, each function provided by the supplier terminal 50, the manufacturer terminal 10a, the intermediate layer terminal 250, etc. can be provided by software and hardware that executes it, software only, hardware only, or a complex combination of these. When such functions are provided by electronic circuits as hardware, each function can also be provided by digital circuits including a large number of logic circuits, or analog circuits.

[0136] Each processor in the above embodiment may include at least one arithmetic core such as a central processing unit (CPU) and a graphics processing unit (GPU). Furthermore, the processor may further include an IP core having a field-programmable gate array (FPGA) and other dedicated functions.

[0137] The form of the non-transitory tangible storage medium employed as each storage unit in the above embodiment and storing each program related to the realization of the information management method of the present disclosure may be changed as appropriate. For example, the storage medium is not limited to a configuration provided on a circuit board, and may be provided in the form of a memory card or the like, inserted into a slot, and electrically connected to a computer bus. Furthermore, the storage medium may be an optical disk or a hard disk drive used as a source for copying or distributing programs to a computer.

[0138] The control unit and the method described herein may be implemented by a special-purpose computer having a processor programmed to execute one or more functions embodied in a computer program. Alternatively, the device and the method described herein may be implemented by a special-purpose hardware logic circuit. Alternatively, the device and the method described herein may be implemented by one or more special-purpose computers configured by a combination of a processor that executes a computer program and one or more hardware logic circuits. The computer program may also be stored in a computer-readable non-transitory tangible recording medium as instructions to be executed by the computer.

[0139] (Disclosure of technical ideas) This specification discloses multiple technical ideas described in the following multiple dependent claims. Some of the claims may be described in a multiple dependent form, where the subsequent claim alternatively refers to the preceding claim. Furthermore, some of the claims may be described in a multiple dependent form, where the subsequent claim alternatively refers to the preceding claim. The claims described in these multiple dependent forms define multiple technical ideas.

[0140] (Technical thought 1) An information management method for managing information provided by a plurality of reporters (SR) constituting a supply chain (SC), the method being implemented by a computer (100c), comprising: The process executed by at least one processor (11) includes: Issue item identification information (UID) attached to an item (IM) shipped from the reporter and identifying the item to a destination terminal (50, 250) associated with the reporter (S21 to S26); A stored hash value (HVs) obtained by hashing history information (TRI) related to the item is obtained together with the item identification information (S31); The stored hash value is stored in a database (BDB) in a state linked to the item identification information (S36); An information management method comprising the steps of: (Technical thought 2) providing the destination terminal with verification data (Dd) for verifying the stored hash value acquired from the destination terminal (S11, S313); A verification hash value (HVd) generated by a hashing process using the verification data is obtained from the destination terminal (S12, S315); If the verification hash value is a correct value, it is determined that the stored hash value obtained from the destination terminal is a correct value (S35, S316). The information management method according to technical idea 1 further includes the step of: (Technical Thought 3) An application (HAP) for performing the hashing process is provided to the destination terminal (S101 to S105); The information management method according to technical idea 2 further includes the step of: (Technical Thought 4) An information management method according to technical idea 3, in which the step of acquiring the stored hash value further acquires additional information including information indicating the version of the application that performed the hashing process. (Technical Thought 5) In the step of acquiring the verification hash value, a first verification hash value (HVd1) generated by the hashing process using the verification data before the hashing process of the history information, and a second verification hash value (HVd2) generated by the hashing process using the verification data after the hashing process of the history information are acquired from the destination terminal; An information management method according to technical idea 2, in which, in the step of determining the stored hash value, if the first verification hash value and the second verification hash value are both correct values, it is determined that the stored hash value obtained from the destination terminal is a correct value. (Technical Thought 6) In the step of issuing the item identification information, the item identification information is issued to an intermediate layer terminal as the issuing destination terminal operated in an intermediate layer (ML); In the step of acquiring the stored hash value, the intermediate layer terminal acquires data to be stored (DSS) linked to the item identification information by the stored hash value generated by the reporter terminal operated by the reporter, according to the information management method described in technical idea 1. (Technical Thought 7) providing reporter storage data having the same contents as the item identification information and the storage hash value stored in the database to the reporter terminal (S93); The reporter storage data is stored in a reporter database (SDB) operated by the reporter (S84); An information management method according to technical idea 6, comprising the steps of: (Technical Thought 8) An information management method according to any one of technical ideas 1 to 7, in which, in the step of issuing the item identification information, at least one variable information (VI) that changes for each item and an identification hash value (HVi) obtained by hashing original data including the variable information are embedded in the item identification information. (Technical Thought 9) In the step of issuing the item identification information, characteristic information (CI) indicating characteristics of the item identification information is embedded in the item identification information; The information management method according to technical idea 8, wherein the characteristic information is excluded from the original data. (Technical Thought 10) a character string (CDs) corresponding to a part of the item identification information is written in a readable state on an attachment medium (LB) that records the item identification information and is attached to the item (S73, S74); The information management method according to any one of Technical Ideas 1 to 8, further comprising the step of: (Technical Thought 11) The information management method according to any one of Technical Ideas 1 to 9, wherein in the step of storing in the database, the stored hash value is stored using a block chain (BC) technology. (Technical Thought 12) Acquire linking information (LI) linking the item identification information attached to the item with related identification information (PID) identifying a related object (PD) related to the item from a supplier terminal (10a) of a supplier (MF) to which the item is delivered (S51); The linking information is stored in the database (S52). The information management method according to any one of Technical Ideas 1 to 10, further comprising the step of: (Technical Thought 13) An information management device that manages information provided by a plurality of reporters (SR) constituting a supply chain (SC), an issuing unit (32) that issues item identification information (UID) attached to an item (IM) shipped from the reporter and that identifies the item to an issuing destination terminal (50, 250) associated with the reporter; an acquisition unit (33) that acquires a stored hash value (HVs) obtained by hashing history information (TRI) related to the item together with the item identification information; a storage unit (34) that stores the stored hash value in a database (BDB) in a state linked to the item identification information; An information management device comprising:

Claims

1. An information management method for managing information provided by a plurality of reporters (SR) constituting a supply chain (SC), the method being implemented by a computer (100c), comprising: providing verification data (Dd) for verifying a stored hash value (HVs) obtained by hashing history information (TRI) related to an item (IM) shipped from the reporter to a destination terminal (50, 250) associated with the reporter (S11, S313); A verification hash value (HVd) generated by a hashing process using the verification data is obtained from the destination terminal (S12, S315); Issue to the destination terminal an item identification information (UID) that is attached to the item shipped from the reporter and identifies the item (S21 to S26); The stored hash value is obtained together with the item identification information (S31); If the verification hash value is a correct value, it is determined that the stored hash value obtained from the destination terminal is a correct value (S35, S316); The stored hash value is stored in a database (BDB) in a state linked to the item identification information (S36). The information management method includes the steps of:

2. An application (HAP) for performing the hashing process is provided to the destination terminal (S101 to S105); 2. The information management method according to claim 1, further comprising the step of:

3. 3. The information management method according to claim 2, wherein in the step of acquiring the stored hash value, additional information including information indicating a version of the application that performed the hashing process is further acquired.

4. In the step of acquiring the verification hash value, a first verification hash value (HVd1) generated by the hashing process using the verification data before the hashing process of the history information, and a second verification hash value (HVd2) generated by the hashing process using the verification data after the hashing process of the history information are acquired from the destination terminal; An information management method as described in claim 1, in which, in the step of determining the stored hash value, if the first verification hash value and the second verification hash value are both correct values, it is determined that the stored hash value obtained from the destination terminal is a correct value.

5. An information management method for managing information provided by a plurality of reporters (SR) constituting a supply chain (SC), the method being implemented by a computer (100c), comprising: Issue item identification information (UID) attached to an item (IM) shipped from the reporter and identifying the item to a destination terminal (50, 250) associated with the reporter (S21 to S26); A stored hash value (HVs) obtained by hashing history information (TRI) related to the item is obtained together with the item identification information (S31); The stored hash value is stored in a database (BDB) in a state linked to the item identification information (S36). The process executed by at least one processor (11) includes the steps of: In the step of issuing the item identification information, the item identification information is issued to an intermediate layer terminal as the issuing destination terminal operated in an intermediate layer (ML), In the step of acquiring the stored hash value, the intermediate layer terminal acquires data to be stored (DSS) linking the item identification information to the stored hash value generated by a reporter terminal operated by the reporter, in this information management method.

6. providing reporter storage data having the same contents as the item identification information and the storage hash value stored in the database to the reporter terminal (S93); The reporter storage data is stored in a reporter database (SDB) operated by the reporter (S84).

6. The information management method according to claim 5, further comprising the steps of:

7. An information management method according to any one of claims 1 to 6, wherein in the step of issuing the item identification information, at least one variable information (VI) that changes for each item and an identification hash value (HVi) obtained by hashing original data including the variable information are embedded in the item identification information.

8. In the step of issuing the item identification information, characteristic information (CI) indicating characteristics of the item identification information is embedded in the item identification information; The information management method according to claim 7 , wherein the characteristic information is excluded from the original data.

9. A character string (CDs) corresponding to a part of the item identification information is written in a readable state on an attachment medium (LB) that records the item identification information and is attached to the item (S73, S74).

7. The information management method according to claim 1, further comprising the steps of:

10. The information management method according to any one of claims 1 to 6, wherein in the step of storing in the database, the stored hash value is stored using blockchain (BC) technology.

11. From a supplier terminal (10a) of a supplier (MF) to which the item is delivered, linking information (LI) linking the item identification information attached to the item with related identification information (PID) identifying a related object (PD) related to the item is acquired (S51); The linking information is stored in the database (S52).

7. The information management method according to claim 1, further comprising the steps of:

12. An information management device that manages information provided by a plurality of reporters (SRs) that constitute a supply chain (SC), an issuing unit (32) that issues item identification information (UID) attached to an item (IM) shipped from the reporter and that identifies the item to an issuing destination terminal (50, 250) associated with the reporter; an acquisition unit (33) that acquires a stored hash value (HVs) obtained by hashing history information (TRI) related to the item together with the item identification information; a storage unit (34) that stores the stored hash value in a database (BDB) in a state linked to the item identification information; a hash verification unit (31) that provides the destination terminal with verification data (Dd) for verifying the stored hash value obtained from the destination terminal, obtains from the destination terminal a verification hash value (HVd) generated by a hashing process using the verification data, and determines that the stored hash value obtained from the destination terminal is a correct value if the verification hash value is a correct value; An information management device comprising:

13. An information management device that manages information provided by a plurality of reporters (SRs) that constitute a supply chain (SC), an issuing unit (32) that issues item identification information (UID) attached to an item (IM) shipped from the reporter and that identifies the item to an issuing destination terminal (50, 250) associated with the reporter; an acquisition unit (33) that acquires a stored hash value (HVs) obtained by hashing history information (TRI) related to the item together with the item identification information; a storage unit (34) that stores the stored hash value in a database (BDB) in a state linked to the item identification information; Equipped with The issuing unit issues the item identification information to an intermediate layer terminal as the issuing destination terminal operated in an intermediate layer (ML), The acquisition unit is an information management device that acquires data to be stored (DSS) in which the intermediate layer terminal links the item identification information to the stored hash value generated by a reporter terminal operated by the reporter.

14. An information management program executed by a computer (100c) for managing information provided by a plurality of reporters (SRs) constituting a supply chain (SC), comprising: providing verification data (Dd) for verifying a stored hash value (HVs) obtained by hashing history information (TRI) related to an item (IM) shipped from the reporter to a destination terminal (50, 250) associated with the reporter (S11, S313); A verification hash value (HVd) generated by a hashing process using the verification data is obtained from the destination terminal (S12, S315); Issue to the destination terminal an item identification information (UID) that is attached to the item shipped from the reporter and identifies the item (S21 to S26); The stored hash value (HVs) is obtained together with the item identification information (S31); If the verification hash value is a correct value, it is determined that the stored hash value obtained from the destination terminal is a correct value (S35, S316); The stored hash value is stored in a database (BDB) in a state linked to the item identification information (S36). The information management program causes at least one processor (11) to execute a process including the steps of:

15. An information management program executed by a computer (100c) for managing information provided by multiple reporters (SRs) constituting a supply chain (SC), comprising: Issue item identification information (UID) attached to an item (IM) shipped from the reporter and identifying the item to a destination terminal (50, 250) associated with the reporter (S21 to S26); A stored hash value (HVs) obtained by hashing history information (TRI) related to the item is obtained together with the item identification information (S31); The stored hash value is stored in a database (BDB) in a state linked to the item identification information (S36). having at least one processor (11) execute a process including: In the process of issuing the item identification information, the item identification information is issued to an intermediate layer terminal as the issuing destination terminal operated in an intermediate layer (ML), In the process of acquiring the stored hash value, the intermediate layer terminal acquires the stored data (DSS) linked to the item identification information by the stored hash value generated by the reporter terminal operated by the reporter, in an information management program.

Images