Information management method and information management device

Abstract

The invention provides an information management method and an information management device. An information management server manages information provided from a plurality of suppliers (SR) constituting a supply chain (SC). In an information management method implemented by an information management server, item identification information (UID), which is added to an item (IM) delivered from a supplier (SR) and identifies the item (IM), is issued to a supplier terminal. Furthermore, a storage hash value (HVs) obtained by hashing history information (TRI) associated with the item (IM) is acquired together with the item identification information (UID), and is stored in a BC database (BDB) in a state of being associated with the item identification information (UID).

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority of Japanese Patent Application No. 2022-47192 filed in Japan on March 23, 2022, and Japanese Patent Application No. 2022-112030 filed in Japan on July 12, 2022, and the contents of the basic applications are incorporated by reference in their entirety. Technical Field

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

[0004] Patent Document 1 describes a supply chain management method that obtains transaction records of items from traders constituting a supply chain and returns a hash value of the acquired transaction records to the traders. The hash value provided to the traders is attached to the items shipped from the traders.

[0005] Patent Document 1: International Publication No. 2021 / 002226

[0006] Assuming that the types, formats, and volumes of transaction records recorded by each trader are different, there is a concern that the data processing of storing transaction records may become complicated due to the different contents of transaction records of each trader in the supply chain management method of acquiring transaction records from each trader as in Patent Document 1. Summary of the invention

[0007] An object of the present disclosure is to provide an information management method and an information management device capable of simplifying data processing for information management.

[0008] In order to achieve the above-mentioned purpose, a disclosed method is an information management method, which is implemented by a computer and manages information provided by multiple reporters constituting a supply chain. The processing performed by at least one processor includes the following steps: issuing item identification information attached to an item shipped from a reporter and identifying the item to an issuance destination terminal associated with the reporter; obtaining a custody hash value obtained by hashing historical information associated with the item together with the item identification information; and storing the custody hash value in a database in a state of being associated with the item identification information.

[0009] Another disclosed method is an information management device that manages information provided by multiple reporters that constitute a supply chain, and comprises: an issuance unit that issues item identification information that is attached to an item shipped from a reporter and identifies the item to an issuance destination terminal associated with the reporter; an acquisition unit that acquires, together with the item identification information, a storage hash value that is hashed into historical information associated with the item; and a storage unit that stores the storage hash value in a database in a state in which it is associated with the item identification information.

[0010] In these methods, a storage hash value obtained by hashing the historical information associated with the project is obtained together with the pre-issued project identification information, and is stored in the database in a state of being associated with the project identification information. In this way, the information obtained from each reporter can be fixed by the process of sending the hashed historical information. As a result, the data processing for information management can be simplified.

[0011] In addition, the reference numbers in brackets in the claims are only an example of the corresponding relationship with the specific structure in the embodiment described later, and do not limit the technical scope in any way. In addition, as long as the combination does not particularly cause obstacles, the combination of claims that are not clearly shown in the claims can also be performed. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0013] Figure 2 This is a diagram showing systems and terminals related to traceability management.

[0014] Figure 3 It is a block diagram showing the electrical structure of the traceability management system and the supplier terminal.

[0015] Figure 4 It is a diagram for explaining the details of hashing application.

[0016] Figure 5 This is a flowchart showing the details of the application distribution process performed by the application distribution server.

[0017] Figure 6 This is a flowchart showing the details of the application verification process mainly performed by the hash verification unit of the information management server.

[0018] Figure 7 This is a flowchart showing the details of the ID issuance process mainly performed by the issuing unit of the information management server.

[0019] Figure 8This is a diagram for explaining the details of item identification information and attached labels.

[0020] Fig. 9 This is a flowchart showing the details of the hash storage process performed by the information management server.

[0021] Fig.10 This is a flowchart showing the details of the ID cooperation process performed by the manufacturer terminal or supplier terminal and the information management server.

[0022] Fig.11 This is a flowchart showing the details of the ID verification process performed by a manufacturer terminal, a supplier terminal, or an information management server.

[0023] Fig.12 This is a flowchart showing the details of the ID output process performed by the provider terminal.

[0024] Fig.13 This is a flowchart showing the details of the history disclosure processing mainly performed by the disclosure processing unit of the information management server.

[0025] Fig.14 This is a diagram showing an overall picture of the processing mainly performed by the traceability management system according to the second embodiment of the present disclosure.

[0026] Fig.15 This is a diagram showing an overall picture of processing mainly performed by the source tracing management system according to the third embodiment of the present disclosure.

[0027] Fig.16 This is a diagram showing the details of the query system included in the traceability management system of Modification 3. DETAILED DESCRIPTION

[0028] Hereinafter, a plurality of embodiments are described based on the accompanying drawings. In addition, there is a case where the same reference numerals are marked on the corresponding constituent elements in each embodiment, and repeated descriptions are omitted. In the case where only a part of the structure is described in each embodiment, the structure of other embodiments previously described can be applied to the other parts of the structure. In addition, not only the combination of structures clearly shown in the description of each embodiment, but also the structures of multiple embodiments can be partially combined with each other even if not clearly shown, as long as the combination does not particularly cause an obstacle.

[0029] (First Embodiment)

[0030] Figure 1The supply chain SC in the first embodiment of the present disclosure is a connection between traders for delivering industrial products, agricultural products, and aquatic products to end users US. The supply chain SC is constructed by including a plurality of suppliers SR and finished product manufacturers MF as traders. The final products PD supplied by the supply chain SC may be various items such as automobiles, batteries, semiconductors, fresh food, aquatic products, food, flowers, pharmaceuticals, and chemicals.

[0031] As a specific example, in the supply chain SC for delivering industrial products to the end user US, material miners, material producers, and processors are included as suppliers SR. Each supplier SR processes raw materials such as pure materials and recycled materials or (as well as) items IM delivered from the supplier SR of the previous process, and ships them as other items IM to the supplier SR of the next process or the finished product manufacturer MF. The supply chain SC may also include transporters and sellers associated with the circulation of items IM and final products PD. In addition, the supply chain SC may also include end users US who use the final product PD, secondary users U2 and recyclers RC who reuse, refurbish, recycle, and discard the final product PD.

[0032] Supply Chain SC Figure 1 and Figure 2 The manager ADM shown is managed. The manager ADM can be, for example, an agent that has been entrusted with management business by the finished product manufacturer MF, or an agency that has been entrusted with management and inspection business by a supervisory authority that has supervisory authority over the category to which the final product PD belongs. The manager ADM uses the traceability management system 100 to manage various information recorded in the supply chain SC.

[0033] The traceability management system 100 can communicate with the supplier terminal 50, the manufacturer terminal 10a, and the user terminal 10b through the network NW. When the final product PD (for example, a car, etc.) has a communication function, the traceability management system 100 can also communicate with the final product PD. The traceability management system 100 saves the information obtained through the network NW in a state that cannot be tampered with in essence. In addition, the traceability management system 100 collects information under the management of various suppliers SR, etc. according to the request of the manager ADM (or supervisory agency), the end user US, the finished product manufacturer MF, etc., and discloses it to the request source.

[0034] The supplier terminal 50 is an information processing device operated by the supplier SR. The supplier terminal 50 is associated with each supplier SR. The supplier terminal 50 accumulates historical information TRI associated with the item IM. The historical information TRI is information such as from which trading company (the supplier SR of the previous process) the raw materials or parts were purchased, when the raw materials or parts were obtained, etc. In addition, information related to costs and the amount of greenhouse gas emissions (carbon footprint) emitted due to the manufacture of the item IM can also be recorded as the historical information TRI.

[0035] The historical information TRI is stored in the supplier terminal 50 and disclosed to the outside according to the situation. For example, if a certain defect occurs in the project IM or the final product PD or there is a possibility of a defect, the historical information TRI is disclosed to the outside through the information disclosure process described later (see Fig.13 ), through the manager ADM, provide historical information TRI to other traders or end users US, etc. The provided historical information TRI is used for investigation of the cause of the bad situation, etc. As described above, at least a part of the historical information TRI is information for realizing the traceability of the project IM.

[0036] The supplier terminal 50 receives the issuance of unique identification information (hereinafter referred to as item identification information UID) for identifying the item IM from the traceability management system 100. The item identification information UID is a unique identifier (unique identification) that does not overlap with each other (see Figure 8 ). For example, it is also possible to issue item identification information UID not only to parts, etc., but also to issue item identification information UID to recycled materials, etc. The item identification information UID is attached to the item IM shipped from the supplier SR and delivered to the trader of the next process together with the item IM. For a specific item IM, the supplier terminal 50 will associate the hash value generated based on the historical information TRI (hereinafter referred to as the storage hash value HVs) with the issued item identification information UID and upload it to the traceability management system 100.

[0037] The manufacturer terminal 10a is an information processing device operated by the product manufacturer MF. The manufacturer terminal 10a is used in the ID cooperation process described later (see Fig.10), information is generated to associate the final product PD shipped from the finished product manufacturer MF with one or more items IM used by the final product PD. Specifically, ID link information LI is generated as association information to associate the item identification information UID attached to the item IM with the product identification information PID for identifying the final product PD manufactured using the item IM. The final product PD is an associated object associated with the item IM. In the case where a final product PD uses multiple items IM, multiple ID link information LI are generated. The manufacturer terminal 10a uploads the generated one or more ID link information LI to the traceability management system 100.

[0038] In addition, in the supplier terminal 50, the ID cooperation process is also implemented in the same manner as in the manufacturer terminal 10a. The supplier terminal 50 generates ID link information LI that associates the item identification information UID of the received item IM or the recycled material with the item identification information UID of the shipped item IM. The supplier terminal 50 uploads the generated one or more ID link information LI to the traceability management system 100.

[0039] The user terminal 10b is an information processing device used 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 recycler RC disassembles the final product PD and changes the usage of the item IM used in the final product PD, the user terminal 10b uploads the change information XI to the traceability management system 100.

[0040] Specifically, when the secondary user U2 discards the item IM or the recycler RC recycles it as a recycling material, the traceability management system 100 is notified of the change information XI indicating that the item IM has disappeared. In addition, when the secondary user U2 reuses the item IM in other final products PD or uses the item IM taken out of the final product PD for other purposes, the change information XI requesting the correction or transfer of the ID link information LI is notified. As an example, when the battery pack for driving taken out of an electric vehicle is used as a replacement battery for other vehicles or when it is used as a fixed battery or a backup battery for power outages, the traceability management system 100 is notified of the change information XI.

[0041] The final product PD collects operation information OI as the end user US uses it. As an example, when the final product PD is an electric vehicle, the driving distance, charge and discharge history, and the current value of the battery capacity (State of Health, SOH) are collected as the operation information OI. The final product PD associates its own product identification information PID with the collected operation information OI and uploads it to the traceability management system 100. In addition, at least one of the collection and uploading of the operation information OI may also be implemented by the user terminal 10b held by the end user US.

[0042] Next, based on Figure 1 to Figure 4 The details of the traceability management system 100 and the supplier terminal 50 are described below.

[0043] The traceability management system 100 has 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 with a control circuit 100c as the main body. The control circuit 100c has a processor 11, a RAM (Random Access Memory) 12, a storage unit 13, an input and output interface 14, and a bus connecting them, etc., and acts as a computer for performing calculation processing. The processor 11 is hardware for calculation processing combined with the RAM 12, and executes the program stored in the storage unit 13.

[0044] The application distribution server 100a functions as a server device that distributes hashed applications HAP. The hashed application HAP is an application program installed in each supplier terminal 50. The hashed application HAP performs a hashing process of hashing the pre-processing data including at least the historical information TRI in each supplier terminal 50 based on the rules specified by the administrator ADM, and generates and stores a hash value HVs. The pre-processing data is the original data before the hashing process is performed. The hashed application HAP can maintain security in traceability management through regular updates. The application distribution server 100a performs application distribution processing in the control circuit 100c based on the application distribution program (refer to Figure 5 ) is implemented to provide the latest hashing application HAP to each supplier terminal 50.

[0045] The application distribution server 100a determines whether there is an update trigger during the application distribution process (S101). For example, the version information and validity period of the hashed application HAP can be used as an update trigger. When the application distribution server 100a updates the version of the hashed application HAP specified by the administrator ADM based on the version information of the hashed application HAP (see Figure 4), the update trigger is validated (S101: Yes). In addition, the update trigger may be validated in the case where a vendor terminal 50 using an old version of the hashed application HAP that cannot be used is determined based on the validity period of the hashed application HAP. Based on the validation of the update trigger, the application distribution server 100a sends a notification requesting an application update to the vendor terminal 50 that is the target of the update (S102).

[0046] After sending the update request notification, the application distribution server 100a waits for a reply from the supplier terminal 50 until a predetermined waiting time has passed or a predetermined number of errors have occurred and the timeout occurs (S104: Yes). If the application distribution server 100a receives a notification of update implementation from the supplier terminal 50 that has received the update request notification (S103: Yes), it provides the supplier terminal 50 with the latest program data of the hashed application HAP (S105, also refer to Figure 4 dashed arrow).

[0047] In addition, the version confirmation of the hashed application HAP is not limited to the case where it is implemented from the administrator ADM side, and can also be implemented from the supplier SR side (supplier terminal 50). Specifically, after the system is started, the supplier terminal 50 inquires the validity of the hashed application HAP held by the application distribution server 100a or the information management server 100s. In the case of receiving the inquiry result indicating that the hashed application HAP is valid, the supplier terminal 50 implements the generation and upload of the hash value described later. On the other hand, in the case of receiving the inquiry result 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 implements the update to the latest hashed application HAP.

[0048] Alternatively, for example, the hashed application HAP may be distributed by a platform of an operating system that operates the vendor terminal 50. In such a system, the latest hashed application HAP is provided from the manager ADM to the platform and distributed to each vendor terminal 50 from a server device operated by the platform.

[0049] The information management server 100s functions as an information management device that manages information associated with the project IM. The storage unit 13 of the information management server 100s stores an information management program for causing the control circuit 100c to implement the information management method of the present disclosure. The information management server 100s includes functional units such as a hash verification unit 31, an issuing unit 32, an acquiring unit 33, and a storage unit 34 (see FIG. 1 ). Figure 3 ).

[0050] The hash verification unit 31 verifies the legitimacy of the stored hash value HVs obtained from the supplier terminal 50. Specifically, the hash verification unit 31 performs application verification processing (see Figure 6 ) to confirm whether the stored hash value HVs is generated by the hashing application HAP specified by the administrator ADM and whether the stored hash value HVs is generated correctly (refer to Figure 4 solid arrow).

[0051] The hash verification unit 31 can perform application verification processing at any timing. Specifically, the application verification processing can be performed when the vendor terminal 50 updates the hashed application HAP, when the item identification information UID is issued, when the stored hash value HVs is received, when a predetermined period has passed since the last verification, etc.

[0052] The hash verification unit 31 transmits the verification data Dd to the supplier terminal 50 in the application verification process (S11). The verification data Dd is pseudo data that is input to the hashing application HAP in place of the history information TRI at the supplier terminal 50. The hash verification unit 31 receives a hash value (hereinafter referred to as verification hash value HVd) generated by the hashing process using the verification data Dd in the hashing application HAP from the supplier terminal 50 (see also S12). Figure 4 ). The hash verification unit 31 obtains the additional information AI together with the verification hash value HVd (refer to Figure 4 ). The supplementary information AI includes at least the provider of the hashing application HAP and a character string indicating the version of the hashing application HAP.

[0053] After sending the verification data Dd, the hash verification unit 31 waits for a reply to verify the hash value HVd until a predetermined waiting time has passed. If the hash verification unit 31 times out due to the predetermined waiting time (S13: Yes), it makes an NG determination (S18) indicating that the legitimacy of storing the hash value HVs cannot be guaranteed.

[0054] When the hash verification unit 31 receives the verification hash value HVd and the supplementary information AI (S12: YES), it determines whether the appropriate hashing application HAP is running in the vendor terminal 50 based on the supplementary information AI (see also S14). Figure 4 ). For example, when an inappropriate hashed application HAP such as an application of unknown origin or an old version that cannot be used is used in the vendor terminal 50 (S14: No), the hash verification unit 31 performs an NG determination (S18).

[0055] When the hash verification unit 31 determines that an appropriate hashing application HAP is used in the vendor terminal 50 (S14: Yes), it calculates a hash value for comparison (see also S15). Figure 4 ) The hash value for comparison is a value calculated when the verification data Dd is input into the hashed application HAP of the version indicated by the supplementary information AI.

[0056] The hash verification unit 31 compares the received verification hash value HVd with the comparison hash value in order to check whether the hashed application HAP is operating normally (see also S16). Figure 4 ). When the verification hash value HVd is different from the hash value for comparison (S16: No), the hash verification unit 31 performs an NG determination (S18). On the other hand, when the verification hash value HVd is the same as the hash value for comparison (S16: Yes), the hash verification unit 31 determines that the hashed application HAP is operating normally in the supplier terminal 50, and is in a state where the legitimacy of the storage of the hash value HVs can be guaranteed (S17). As described above, the hash verification unit 31 can perform operation verification of the hashed application HAP without requesting the supplier terminal 50 to disclose the historical information TRI.

[0057] The issuing unit 32 performs ID issuance processing (see Figure 7 ) and issue the above-mentioned item identification information UID to the supplier terminal 50 associated with each supplier SR (refer to Figure 8 ). The project identification information UID is, for example, a 32-bit character string. The issuing unit 32 implements ID issuance processing, for example, based on a request from the supplier SR (supplier terminal 50), and issues the number of project identification information UIDs required by the supplier SR. In addition to such timely issuance of project identification information UID, the issuing unit 32 can also implement batch processing of issuing a specified number of project identification information UIDs in a batch according to a request from the supplier terminal 50.

[0058] The issuing unit 32 obtains information (hereinafter referred to as application ID, see Figure 8 )(S21). Then, the issuing unit 32 grasps the issuing date of the item identification information UID and the number of item identification information UIDs issued in batch at one time (hereinafter referred to as the issuing number) (S22).

[0059] The application ID is a value that does not change each time the project identification information UID is issued, and is a pre-set fixed character string. The application ID is information that identifies the issuer (administrator ADM), purpose, and field of use of the project identification information UID. The application ID can also be changed for each issuer (supplier SR). In this case, the application ID can also be used as information to identify the issuer of the project identification information UID. The issuance date and issuance quantity are values ​​that change each time the project identification information UID is issued. In other words, they are variable information VI that changes for each project IM (refer to Figure 8 ). Such variable information VI can also be used to improve the randomness of the item identification information UID. In addition, in order to compensate for the difficulty of use caused by excessive randomness, the readable code CDs (see Figure 8 ) is made continuous to improve operability.

[0060] The issuing unit 32 generates a hash value (hereinafter referred to as an identification hash value HVi, see Figure 8 )(S23). Then, the issuing unit 32 sets the code version, mode flag, and activation period of the project identification information UID (S24). The code version, mode flag, and activation period are characteristic information CI indicating the characteristics of the project identification information UID (see Figure 8 ).

[0061] The code version is, for example, an identifier indicating the version of the project identification information UID. The mode flag is an identifier that specifies the scrambling rule used to generate the project identification information UID. By using the mode flag, it is possible to understand the scrambling rule and descramble the decoding without accessing the information management server 100s. The activation deadline is information indicating the end of the period during which the project identification information UID can be effectively used in the traceability management system 100. The project identification information UID that has exceeded the activation deadline cannot perform operations based on the information management server 100s and the hashing application HAP.

[0062] The issuing unit 32 generates the project identification information UID (S25) using the application ID, the change information VI, the identification hash value HVi and the characteristic information CI. In detail, the issuing unit 32 converts the original data including the application ID and the change information VI and the identification hash value HVi into a fixed-length character string based on the scrambling rule corresponding to the mode flag. Through such scrambling processing, it is possible to generate a chaotic character string different from that before the conversion without damaging the content before the conversion. Therefore, the application ID, the change information VI and the identification hash value HVi are embedded in the project identification information UID in a state that can be restored (compounded). In addition, the issuing unit 32 mixes the code version, the mode flag and the activation period at a predetermined position (for example, the beginning part) of the project identification information UID (character string). In addition, the issuing unit 32 mixes the change information VI such as the issuance time and the issuance quantity at a predetermined position (for example, the end part) of the project identification information UID (character string). The issuing unit 32 sends the generated project identification information UID to the supplier terminal 50 as the request source for issuance (S26). After the issuing unit 32 issues the item identification information UID, the hash verification unit 31 may perform application verification processing (see Figure 6 ).

[0063] The acquisition unit 33 acquires the information sent from the supplier terminal 50. The storage unit 34 stores the information acquired by the acquisition unit 33 in the blockchain database (hereinafter referred to as BC database, also referred to as Fig.16 )BDB. The BC database BDB uses the technology of the blockchain BC to store the storage object data such as the storage hash value HVs, the accompanying information AI and the ID link information LI in a state that cannot be tampered with in reality. As an example, the BC database BDB stores the acquired storage object data as a transaction in the block of the private blockchain BC. The BC database BDB makes it difficult to tamper with the storage object data stored in each block by hashing the information stored in one block and storing it in the next block. In addition, as another example, the BC database BDB can also make the storage object data substantially tamper-proof by storing the hash value generated according to the storage object data in the block of the alliance or public blockchain BC. In addition, a server for storing the blockchain BC (hereinafter referred to as the BC server) and a database server for storing other storage object data can also be independently set up as a structure equivalent to the BC database BDB. In addition, it is also possible to use only the server for storing the blockchain BC.

[0064] The acquisition unit 33 and the storage unit 34 perform hash storage processing (see Fig. 9), and stores the stored hash value HVs etc. obtained from the supplier terminal 50 in the BC database BDB. In the hash storage process, the acquisition unit 33 obtains the stored hash value HVs and the accompanying information AI etc. together with the project identification information UID received from the supplier terminal 50 (S31). The acquisition unit 33 refers to the most recent application verification process (reference Figure 6 ) results, it is determined whether the hashing application HAP is operating normally in the provider terminal 50 (S32).

[0065] If an NG determination is made in the most recent application verification process (S32: No), the storage unit 34 sends an error notification (S38) to the supplier terminal 50, notifying that the storage of the hash value HVs cannot be performed. On the other hand, if a normal determination is made in the most recent application verification process (S32: Yes), the application verification process of the hash verification unit 31 is performed again (see Figure 6 )(S33). When an NG determination is made in the second application verification process (S34: No), an error notification is also sent to the supplier terminal 50 (S38). When a normal determination is made in the second application verification process (S34: Yes), that is, when the verification hash value HVd is a correct value, the hash verification unit 31 determines that the stored hash value HVs obtained this time is also a correct value (S35). In addition, the application verification process (S34) after receiving the stored hash value HVs may be omitted.

[0066] Based on the fact that the legitimacy of the stored hash value HVs is confirmed in the hash verification unit 31, the storage unit 34 stores the stored hash value HVs and the additional information AI in the BC database BDB in a state of being associated with the project identification information UID (S36). In addition, the storage unit 34 also stores the issuance history indicating the issuance destination (supplier SR) of the project identification information UID in the BC database BDB in a state of being associated with the project identification information UID. The storage unit 34 sends a storage completion notification to the supplier terminal 50 to notify that the storage of the stored hash value HVs is completed (S37).

[0067] The supplier terminal 50 is a structure with a control circuit 50c as the main body. The control circuit 50c includes a processor 51, a RAM 52, a storage unit 53, an input / output interface 54, and a bus connecting them, and functions as a computer for performing calculation processing. The processor 51 is hardware for calculation processing combined with the RAM 52, and executes the application program (hashing application HAP) stored in the storage unit 53. A display 56, a scanner 58, and a printer 59 are electrically connected to the input / output interface 54. In addition, an input device such as a keyboard may be connected to the supplier terminal 50 for error processing, etc.

[0068] 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 of the control circuit 50c. For example, the display 56 displays an image showing the historical information TRI based on the provision data, an image notifying the error information received from the information management server 100s, etc. The display 56 may also have a touch panel function for accepting user operations.

[0069] The scanner 58 reads the additional label LB (see Figure 8 ) is a reading device. The scanner 58 is, for example, a structure including an area sensor in which CCD elements are arranged in two dimensions. The additional 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 project identification information UID is recorded in the two-dimensional code CDq. The readable code CDs is a character string of a specified length, which corresponds to a part of the project identification information UID. As an example, the last 7 bits of the project identification information UID are used as the readable code CDs, and are recorded on the additional label LB in a state readable by the user of the supplier terminal 50. The scanner 58 reads the two-dimensional code CDq printed on the additional label LB, and outputs the project identification information UID extracted from the two-dimensional code CDq to the control circuit 50c. In addition, the two-dimensional code CDq and the readable code CDs can also be displayed on a display device such as a display and electronic paper. In this case, the display device such as a display and electronic paper is equivalent to the additional label LB.

[0070] The printer 59 is an output device that outputs the additional label LB. The printer 59 obtains the data of the two-dimensional code CDq and the readable code CDs generated according to the new item identification information UID provided from 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 (sticker, etc.) and outputs it as an additional label LB. The additional label LB is, for example, affixed to the outer surface of the item IM and circulated together with the item IM. The affixing location of the additional label LB is not limited to the item body, but may also be a packaging box, a label, a package, and a certification document. In addition, instead of the additional label LB output on demand from the printer 59, the manager ADM may print and issue it in advance, and the additional label LB sent to the supplier SR may be circulated together with the item IM. In addition, the two-dimensional code CDq may be directly laser engraved or printed on the item IM. In this case, a laser marker or an inkjet printer may be used as an output device instead of the printer 59.

[0071] Here, a one-dimensional code such as a barcode recording the item identification information UID may be printed on the additional label LB instead of the two-dimensional code CDq. 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. In such a method, the readable code CDs may also be printed on the outer surface of the recording medium or on a label containing the recording medium in a user-readable manner.

[0072] In addition, in the method of recording the item identification information UID by RFID or microchip, the supplier terminal 50 is equipped with a reader and a writer as a reading device and an output device. The reader reads the item identification information UID recorded as electronic data in the 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 into the storage medium.

[0073] The provider terminal 50 includes functional units such as an ID acquisition unit 61, an information reception unit 62, a history grasping unit 63, a hash generation unit 64, an information transmission unit 65, and an ID output unit 66 by executing the hashing application HAP by the processor 51 (see Figure 3 The supplier terminal 50 implements ID cooperation processing by cooperation of each functional unit (refer to Fig.10 )、ID verification processing (refer to Fig.11 ) and ID output processing (refer to Fig.12 ). In addition, as described above, the ID cooperation process is also implemented by the manufacturer terminal 10a of the finished product manufacturer MF to which the item IM is delivered. That is, the manufacturer terminal 10a is also equipped with functional units corresponding to the ID acquisition unit 61, the information receiving unit 62, and the information sending unit 65.

[0074] The ID acquisition unit 61 is connected to the scanner 58. Fig.10 ), the ID acquisition unit 61 acquires data of the item identification information UID from the scanner 58 that reads the additional label LB of the item IM delivered to the supplier SR (S41). The ID acquisition unit 61 confirms whether the acquired item identification information UID is legitimate information through ID verification processing (S42).

[0075] In the ID verification process (refer to Fig.11 ), the ID acquisition unit 61 reads the characteristic information CI from the character string of the item identification information UID (refer to Figure 8)(S61). Specifically, the ID acquisition unit 61 acquires the code version, mode flag, and activation period of the project identification information UID. The ID acquisition unit 61 determines whether the project identification information UID is an ID within the valid period based on the activation period (S62).

[0076] When the ID acquisition unit 61 determines that the validity period of 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 referred to as an ID invalid notification) is displayed on the display 56. The last 7 digits of the invalid item identification information UID are displayed on the display 56 together with the ID invalid notification. Thus, the user (operator) can identify the item IM to which the invalid item identification information UID is attached by finding the attached label LB containing the same readable code CDs as the 7-digit character string.

[0077] When the ID acquisition unit 61 determines that the project identification information UID is a valid ID (S62: No), it decodes the encrypted project identification information UID based on the code version and mode flag information. By decoding the project identification information UID, the ID acquisition unit 61 reads information such as the application ID (S63 and S64).

[0078] The ID acquisition unit 61 calculates a comparative hash value to be compared with the identification hash value HVi using the application ID, the issuance time, and the issuance quantity (S65). The comparative hash value is calculated by the same calculation method as the generation process of the identification hash value HVi in the issuing unit 32.

[0079] The ID acquisition unit 61 compares the read identification hash value HVi with the hash value for comparison (S66). When the identification hash value HVi is different from the hash value for comparison (S66: No), the ID acquisition unit 61 determines that the item identification information UID is an invalid ID (S68), and displays an ID invalidation notification on the display 56. On the other hand, when the identification hash value HVi is the same as the hash value for comparison (S66: Yes), the ID acquisition unit 61 determines that the item identification information UID is a legitimate ID (S67).

[0080] Here, a detailed determination function for determining the validity and invalidity of the item identification information UID can be provided by the traceability management system 100. In this case, the supplier terminal 50 refers to the determination result notified from the traceability management system 100 to determine whether the item identification information UID is a regular ID. In addition, the above-mentioned ID verification process can be implemented by the manufacturer terminal 10a. For example, the manufacturer terminal 10a implements the ID verification process at the timing of obtaining 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 regular ID.

[0081] The information receiving unit 62 requests the issuing unit 32 to issue the item identification information UID attached to the item IM shipped from the supplier SR. The information receiving unit 62 performs ID cooperation processing (see Fig.10 ), the information receiving unit 62 obtains the item identification information UID issued by the issuing unit 32 by receiving it from the information management server 100s (S43). The information receiving unit 62 generates ID link information LI (S44) that associates the received new item identification information UID with the item identification information UID obtained from the received item IM. In addition, the information receiving unit 62 performs application verification processing (refer to Figure 6 ) receives the verification data Dd (see Figure 4 ). In addition, when the ID linkage process is performed by the manufacturer terminal 10a, the product identification information PID is acquired as another ID to be associated with the item identification information UID (S43).

[0082] The history grasping unit 63 obtains the history information TRI generated by the supplier SR. The history grasping unit 63 may automatically obtain the data that becomes the history information TRI from other server devices installed at the base of the supplier SR, or may obtain the data manually input by the user as the history information TRI. The history grasping unit 63 stores the history information TRI in the supplier database SDB in a state of being associated with the item identification information UID obtained 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 hashed information. The information not stored in the supplier database SDB can be deleted after the intention to delete is confirmed each time. In addition, the history grasping unit 63 is based on the historical disclosure processing (refer to Fig.13 )'s request to the information management server 100s, extracts information associated with the designated item identification information UID from the historical information TRI stored in the supplier database SDB.

[0083] The hash generation unit 64 prepares the pre-processing data in a manner that includes the history information TRI acquired by the history acquisition unit 63. The hash generation unit 64 hashes the pre-processing data to generate a stored hash value HVs. Figure 4 ), the hash generation unit 64 prepares pre-processing data including the verification data Dd instead of the history information TRI. The hash generation unit 64 generates a verification hash value HVd (see Figure 4 ). In addition, the hash generation unit 64 generates the storage hash value HVs and the verification hash value HVd, and further generates the supplementary information AI (see Figure 4 ).

[0084] The information transmission unit 65 sequentially transmits the storage hash value HVs, the verification hash value HVd, and the additional information AI generated by the hash generation unit 64 to the acquisition unit 33. In addition, the information transmission unit 65 performs ID cooperation processing (see Fig.10 ), the ID link information LI and each ID associated with the ID link information LI are sent to the acquisition unit 33 (S45). Each ID and the ID link information LI are acquired by the acquisition unit 33 (S51), and stored in the BC database BDB through the storage unit 34 (S52). Then, a notification indicating that the accumulation of the ID link information LI is completed is provided from the storage unit 34 to the information receiving unit 62 (S53 and S46).

[0085] The ID output unit 66 is connected to the printer 59. Fig.12 ), and the printer 59 outputs the additional label LB. The ID output unit 66 obtains the 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 (refer to Figure 8 ) and readable code CDs with a portion of the project identification information UID cut out (refer to Figure 8 )(S72 and S73). The ID output unit 66 outputs the 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 additional label LB.

[0086] In the method in which the additional label LB printed with the item identification information UID is issued from the manager ADM as described above, the ID output unit 66 and the printer 59 may not be provided in the supplier terminal 50. In this case, the ID output process in the supplier terminal 50 is also omitted.

[0087] Next, the details of the information disclosure implemented by the traceability management system 100 are further described. The information management server 100s also functions as an information providing device that provides information associated with the project IM. The storage unit 13 of the information management server 100s also stores an information providing program for enabling the control circuit 100c to implement the information providing method disclosed in the present invention. The information management server 100s executes the information providing program through the processor 11, and also has a disclosure processing unit 35 as a functional unit.

[0088] The disclosure processing unit 35 performs the history disclosure processing (see Fig.13 ), the historical information TRI can be provided. The disclosure processing unit 35 receives a disclosure request for the historical information TRI from the manufacturer terminal 10a and the user terminal 10b, etc. (S131). The disclosure request is accompanied by product identification information PID or project identification information UID as information specifying the final product PD or project IM that is the object of the request. The disclosure processing unit 35 refers to the BC database BDB, extracts the ID link information LI associated with the specified product identification information PID or project identification information UID, and sets at least one project identification information UID that is the collection object of the historical information TRI (S132).

[0089] The disclosure processing unit 35 refers to the issuance history of the BC database BDB to determine the supplier SR who requests the provision of the historical information TRI. The disclosure processing unit 35 sends the provision request of the historical information TRI together with the item identification information UID to the supplier terminal 50 of the determined supplier SR (S133). The disclosure processing unit 35 obtains the historical information TRI returned from the supplier terminal 50 based on the provision request (S134).

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

[0091] The disclosure processing unit 35 extracts the stored hash value HVs associated with the project identification information UID from the BC database BDB (S137), and compares the stored hash value HVs with the recalculated comparison hash value (S138). When the comparison hash value is different from the stored hash value HVs (S138: No), an error notification indicating the possibility that the historical information TRI has been tampered with is sent to the request source of the disclosure request and the request destination of the information provision (S140). On the other hand, when the comparison hash value is the same as the stored hash value HVs (S138: Yes), the disclosure processing unit 35 estimates that the historical information TRI has not been tampered with.

[0092] When there are a plurality of item identification information UIDs to be collected for the history information TRI, the disclosure processing unit 35 repeats the processes of S133 to S138. When the disclosure processing unit 35 completes the verification of all the history information TRI, it provides the collected history information TRI to the request source of the disclosure request (S139).

[0093] In the first embodiment described so far, the stored hash value HVs obtained by hashing the historical information TRI associated with the project IM is obtained together with the pre-issued project identification information UID. And the stored hash value HVs is stored in the BC database BDB in a state of being associated with the project identification information UID. In this way, according to the processing sent after the historical information TRI is hashed, the information obtained from each supplier SR, specifically, the capacity and data length, etc. can be fixed. As a result, the data processing for information management can be simplified.

[0094] In detail, the historical information TRI recorded by each supplier SR is different in type, format, and capacity of the file recorded by each supplier SR. In addition, the management items and granularity recorded as the historical information TRI may also change each time or over time. In addition, it is assumed that the number and order of processes for processing the item IM also change over time. In addition, it is also assumed that at a stage where the recording method of the historical information TRI in each supplier SR is uncertain, it is necessary to build a traceability management system 100.

[0095] Therefore, in the information management method of the first embodiment, a method of storing and keeping the hash value HVs in a state of establishing an association with the previously issued item identification information UID is adopted. Therefore, even if the type, format, and capacity of the file recording the historical information TRI for each supplier SR are different, the information management server 100s can process the fixed-length data such as the hash value regardless of the state of the historical information TRI for each supplier SR. Based on the above, even if the management items and granularity of the historical information TRI in the supplier SR change, there is no need to change the processing content implemented by the information management server 100s. In addition, the traceability management system 100 can be constructed at a stage where the recording method of the historical information TRI in the supplier SR is uncertain.

[0096] In addition, in the information management method of the first embodiment, at the stage where the historical information TRI is recorded, the historical information TRI is hidden from the outside of the supplier SR. Moreover, when an event occurs, a public request is made only to the related supplier SR, and the historical information TRI required to deal with the event is collected by the information management server 100s. In addition, it is also possible to easily and clearly verify that the collected historical information TRI is not different from the login time. Therefore, a highly convenient information management method can be provided to each trader.

[0097] In addition, in the application verification process of the first embodiment (see Figure 6 ), the verification data Dd for verifying the stored hash value HVs is provided to the supplier terminal 50. And, the verification hash value HVd generated by hashing the verification data Dd is obtained by the hash verification unit 31. When the verification hash value HVd is a correct value, the hash verification unit 31 determines that the stored hash value HVs obtained from the supplier terminal 50 is a correct value. According to such a verification method, the information management server 100s can verify that the generation of the stored hash value HVs by the hashing application HAP is correctly operated in the supplier terminal 50 without requesting the supplier terminal 50 to disclose the historical information TRI. Therefore, even if the data processing for information management is simplified, the legitimacy of the data stored in the information management server 100s can be guaranteed.

[0098] Furthermore, in the first embodiment, a hashing application HAP that performs hashing processing is provided to the vendor terminal 50. In this way, by forcing the use of the hashing application HAP specified by the manager ADM, the hashing application HAP can be updated at any timing of the manager ADM. As described above, since security is easily maintained, the risk of tampering of the history information TRI can be further reduced.

[0099] In addition, in the first embodiment, the additional information AI sent to the information management server 100s includes information indicating the version of the hashing application HAP that has been hashed in the vendor terminal 50. Therefore, even if the content of the hashing process is changed for each version, the information management server 100s can correctly prepare a hash value for comparison such as the verification and storage hash value HVs. As a result, it becomes easier to maintain security and simplify data processing at the same time.

[0100] In addition, in the first embodiment, the change information VI that changes according to each project IM and the identification hash value HVi obtained by hashing the original data containing the change information VI are embedded in the project identification information UID. Therefore, it is easy to avoid duplication of the project identification information UID. In addition, in each terminal under the management of the traceability management system 100, the legitimacy of the project identification information UID can be easily and reliably determined.

[0101] Furthermore, in the first embodiment, characteristic information CI such as a code version and a mode flag is embedded in the project identification information UID. The characteristic information CI is removed from the original data to be hashed and scrambled. Therefore, each terminal etc. that has acquired the project identification information UID can extract the identification hash value HVi and the change information VI etc. from the project identification information UID based on the content of the characteristic information CI. Based on the above, each terminal can more reliably recognize that the project identification information UID is a regular ID issued by the administrator ADM.

[0102] In addition, in the first embodiment, the readable code CDs corresponding to a part of the item identification information UID is recorded on the additional label LB attached to the item IM. If such readable code CDs are displayed on the additional label LB, even if one item identification information UID among a plurality of item identification information UIDs is wrong, the user can identify the additional label LB that is the wrong object by visual observation. As a result, the convenience of information management can be further improved.

[0103] In addition, in the first embodiment, the hash value HVs is stored in the BC database BDB using the blockchain BC technology. Based on the above, the possibility of tampering with the stored hash value HVs can be further reduced. As a result, the correctness of the historical information TRI disclosed according to the disclosure request can be more reliably guaranteed.

[0104] Furthermore, in the first embodiment, the information management server 100s obtains the ID link information LI that associates the item identification information UID attached to the item IM with the 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. Based on the accumulation of such ID link information LI, the connection of the item IM from the raw materials to the final product PD can be reliably recorded in the BC database BDB. Therefore, the information management server 100s can determine the request destination for the disclosure of the request history information TRI without omission by referring to the ID link information LI. As a result, information disclosure with higher accuracy can be performed.

[0105] In addition, in the first embodiment, the storage hash value HVs generated based on the historical information TRI is not recorded in the two-dimensional code CDq. Only the storage hash value HVs and the item identification information UID in the item identification information UID are 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.

[0106] In addition, the item identification information UID of the first embodiment records the application ID and activation period, etc. Based on such information, it is easy to identify the application used for information management and confirm the expiration of the item identification information UID, etc. As a result, the convenience of information management can be further improved.

[0107] In the above-mentioned embodiment, the manufacturer terminal 10a is equivalent to the "deliverer terminal", the supplier terminal 50 is equivalent to the "issuing destination terminal", the control circuit 100c is equivalent to the "computer", and the information management server 100s is equivalent to the "information management device". In addition, the BC database BDB is equivalent to the "database", the readable code CDs is equivalent to the "character string", the hashed application HAP is equivalent to the "application", the additional label LB is equivalent to the "additional medium", and the ID link information LI is equivalent to the "related information". In addition, the supplier SR is equivalent to the "reporter", the finished product manufacturer MF is equivalent to the "deliverer", the final product PD is equivalent to the "related object", and the product identification information PID is equivalent to the "related identification information". In addition, the supplier SR of the next process may be equivalent to the "deliverer", the supplier terminal 50 of the next process may be equivalent to the "deliverer terminal", other items IM may be equivalent to the "related object", and other item identification information UID may be equivalent to the "related identification information".

[0108] (Second Embodiment)

[0109] Fig.14The second embodiment of the present disclosure shown in FIG. 1 is a modified example of the first embodiment. In the provider terminal 50 of the second embodiment, HAP is applied instead of hashing (see Figure 4 ), a universal hash function (hereinafter referred to as universal hash function HF) is used for hashing processing. The universal hash function HF is the same as the hashing application HAP, and the calculation of the stored hash value HVs and the verification hash value HVd is implemented in the supplier terminal 50. The universal hash function HF can be prepared by the supplier SR, or it can be specified by the administrator ADM (information management server 100s). In the case where the universal hash function HF is prepared by the supplier SR, the supplier terminal 50 sends a notification indicating the universal hash function HF used to the information management server 100s. By using the universal hash function HF instead of the hashing application HAP, the transparency of data processing is improved from the perspective of the reporter side such as the supplier SR.

[0110] The application distribution server 100a replaces the application distribution process (see Figure 5 ), and implements application distribution processing of providing the data generation application LAP to the middle-layer terminal 250. In the application distribution processing, the application distribution server 100a provides the latest program data of the data generation application LAP to the middle-layer terminal 250 based on the generation of a predetermined update trigger ( Figure 5 and Fig.14 Refer to S105).

[0111] The middle layer terminal 250 is an information processing device operated by the middle layer ML. The middle layer ML exists independently of the manager ADM and the supplier SR. The middle layer ML ensures the transparency of information from the supplier SR. The middle layer ML can be prepared by the manager ADM or by one or more supplier SRs. Furthermore, as long as transparency is ensured and the manager ADM, the supplier SR (reporter), and the supervisory agency (inspector) reach an agreement, the middle layer ML can also be set in a part of the environment belonging to the manager ADM or the supplier SR. In a method in which multiple supplier SRs are associated with one middle layer ML, even if the transparency of information is ensured by using a general hash function HF, the information of other supplier SRs cannot be read. Since the middle layer ML exists in association with the supplier SR, the middle layer terminal 250 also becomes a terminal associated with the supplier SR.

[0112] The middle-layer terminal 250 is connected to the application distribution server 100a, the information management server 100s, and the supplier terminal 50 in a communicable manner. The middle-layer terminal 250 is similar to the supplier terminal 50 in that it is mainly composed of a control circuit. The control circuit includes a processor, a RAM, a storage unit, an input / output interface, and a bus connecting them, and functions as a computer that performs calculation processing. The middle-layer terminal 250 executes the data generation application LAP through the processor. The data generation application LAP enables the middle-layer terminal 250 to perform the data generation from the issuing unit 32 (see Figure 3 ) Get the ID issued by the process (refer to Figure 7 ) and the process of generating the transmission data DSS including the item identification information UID. The intermediate terminal 250 can store a predetermined number of item identification information UIDs issued in batch processing by the issuing unit 32.

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

[0114] The data recorder 259 has a checker function. The data recorder 259 checks that the transmission data DSS sent to the information management server 100s (storage unit 34) and the supplier terminal 50 have the same content. The data recorder 259 records information indicating that the transmission data DSS sent to the storage unit 34 and the supplier terminal 50 have the same content in the transmission log provided to the supplier terminal 50.

[0115] Next, each detail of a series of data storage processes such as the hash verification process performed by the hash verification unit 31 and the storage and preservation of the hash value HVs in each of the databases BDB and SDB will be described in order.

[0116] The hash verification process is equivalent to the application verification process of the first embodiment (see Figure 6 ) is processed. In the hash verification process, the universal hash function HF is checked to see if it 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 the verification data Dd to the supplier terminal 50 by sending (S11). The verification data Dd is sent to the universal hash function HF by the supplier terminal 50. The hash verification unit 31 obtains the verification hash value HVd generated from the verification data Dd by the hashing process using the universal hash function HF from the supplier terminal 50 (S12).

[0117] The hash verification unit 31 sends the verification data Dd to the same hash function as the universal hash function HF used in the supplier terminal 50, and calculates the hash value for comparison (S15). The hash verification unit 31 determines whether the universal hash function HF is operating normally in the supplier terminal 50 by comparing the received verification hash value HVd with the hash value for comparison (S16). When the verification hash value HVd is the same as the hash value for comparison (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 estimates that the legitimacy of the storage of the hash value HVs can be guaranteed.

[0118] The data storage process is implemented by the cooperation of the supplier terminal 50, the intermediate terminal 250 and the information management server 100s. The supplier terminal 50 generates data by the hash generating unit 64 (see Figure 3 ), will include historical information TRI (refer to Figure 1 ) is sent to the general hash function HF (S81) to generate a stored hash value HVs. The supplier terminal 50 sends the pre-processing data of the general hash function HF (S81) from the information sending unit 65 (refer to Figure 3 ) sends the stored hash value HVs to the intermediate terminal 250 (S82).

[0119] The middle-layer terminal 250 receives and obtains the storage hash value HVs sent from the supplier terminal 50 (S91). The middle-layer terminal 250 prepares one of the item identification information UIDs obtained in advance from the issuing unit 32 as the item identification information UID associated with the storage hash value HVs. In addition, the middle-layer terminal 250 generates additional information AI attached to the storage hash value HVs. The additional information AI includes application information associated with the data generation application LAP and information associated with the item IM (refer to Figure 1 ) The application information includes information indicating the version of the data generation application LAP in operation and information indicating the application provider. The project information includes information indicating the type of project IM associated with the storage hash value HVs and information indicating the supplier SR.

[0120] The middle-layer terminal 250 generates the transmission data DSS by processing (S92) to establish a relationship between the stored hash value HVs and the additional information AI and the item identification information UID. The middle-layer terminal 250 sends the transmission data DSS to the storage unit 34 via the data recorder 259 (S93). In addition, the middle-layer terminal 250 also provides the supplier terminal 50 with the transmission data DSS having the same content as the transmission data sent to the storage unit 34. At this time, the transmission log of the transmission data DSS is recorded by the data recorder 259.

[0121] In the data storage process, the information management server 100s performs the hash storage process similar to the first embodiment (see Fig. 9 ) The same steps. Specifically, the information management server 100s obtains the information through the acquisition unit 33 (refer to Figure 3 ) obtains the transmission data DSS by receiving it from the middle layer ML (S31). When the storage unit 34 determines that the universal hash function HF is operating normally with reference to the verification result of the hash verification process (S32: Yes), it determines that the storage hash value HVs obtained this time is a correct value (S35). Based on the fact that the legitimacy of the transmission data DSS including the storage hash value HVs is confirmed, the storage unit 34 stores the storage hash value HVs and the additional information AI in the BC database BDB in a state of being associated with the item identification information UID (S36).

[0122] The supplier terminal 50 receives information from the data recorder 259 through the information receiving unit 62, and prepares a backup of the transmission data DSS (S83). The supplier terminal 50 sends the transmission data DSS and the transmission log and history information TRI (see Figure 1 ) establishes an association and stores it in the supplier database SDB (S84).

[0123] The second embodiment described so far also has the same effect as the first embodiment. Since the information sent from the reporter such as the supplier SR to the manager ADM is fixed in length by hashing, data processing for information management can be simplified.

[0124] In addition, in the second embodiment, the project identification information is issued to the intermediate layer terminal 250 which is the issuing destination terminal operated by the intermediate layer ML. Moreover, the sending data DSS in which the intermediate layer terminal 250 associates the project identification information UID with the storage hash value HVs generated by the supplier SR operated by the supplier SR is obtained through the information management server 100s. As described above, if the data generation processing that associates the storage hash value HVs with the project identification information UID is implemented in the intermediate layer ML, the supplier SR does not have to be forced to use the hashing application HAP. As a result, the transparency of information processing is improved, so the psychological barriers to introducing the traceability management system 100 can be reduced.

[0125] In addition, in the second embodiment, the 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 is provided to the supplier terminal 50. Furthermore, the transmission data DSS provided to the supplier terminal 50 is stored as a backup in the supplier database SDB operated by the supplier SR. Therefore, in the case where the manager ADM extracts the transmission data DSS (storage object data), the backup on the supplier SR side can be used to verify the occurrence of such extraction. As a result, the data that has not been illegally extracted can be shared between the manager ADM and the reporter, so the transparency of information processing can be further improved.

[0126] In the second embodiment, the transmission data DSS corresponds to "storage target data" and "reporter storage 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 terminal 250 corresponds to the "issuance destination terminal".

[0127] (Third Embodiment)

[0128] Fig.15 The third embodiment of the present disclosure shown is a modified example of the second embodiment. In the third embodiment, the general hash function HF is also used in the hashing process in the vendor terminal 50. On the other hand, in the third embodiment, the application distribution server 100a, the middle layer ML and the middle layer terminal 250 (see Fig.14 ). Therefore, the terminal that becomes the issuing destination of the item identification information UID is the supplier terminal 50 as in the first embodiment. In addition, in the third embodiment, the data storage process including the hash verification process is implemented by the cooperation of the supplier terminal 50 and the information management server 100s. The details of the data storage process of the third embodiment are described below.

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

[0130] The information management server 100s prepares a hash function identical to the universal hash function HF presented in advance from the provider terminal 50. The information management server 100s then sends the verification data Dd sent to the provider terminal 50 to the prepared hash function. Thus, a set of hash values ​​for comparison is calculated (S314).

[0131] The supplier terminal 50 obtains the verification data Dd provided by the information management server 100s (S382). In addition, the supplier terminal 50 sends a data including the history information TRI (refer to Figure 1 ) before processing (S383). The supplier terminal 50 stores the hash value HVs and also calculates a first verification hash value HVd1 and a second verification hash value HVd2.

[0132] The first verification hash value HVd1 is a verification hash value HVd generated by hashing the verification data Dd before hashing the pre-processed data. The second verification hash value HVd2 is a verification hash value HVd generated by hashing the verification data Dd before hashing the pre-processed data. The supplier terminal 50 inputs the verification data Dd, the pre-processed data, and the verification data Dd into the general hash function HF in the order of calculating the first verification hash value HVd1, the storage hash value HVs, and the second verification hash value HVd2. In addition, the verification data Dd used to generate the verification hash values ​​HVd1 and HVd2 may be the same content or different content.

[0133] The supplier terminal 50 generates the supplementary information AI. The supplier terminal 50 associates the first verification hash value HVd1, the storage hash value HVs, and the second verification hash value HVd2 with the supplementary information AI and the item identification information UID, and generates the transmission data DSS. In the transmission data DSS, the storage 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).

[0134] The information management server 100s obtains 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 the hash value for comparison, and performs a correctness check on each verification hash value HVd1 and HVd2. When each verification hash value HVd1 and HVd2 is the same as the hash value for comparison, the information management server 100s determines that the universal hash function HF is operating normally and the legitimacy of the stored hash value HVs can be guaranteed (S316).

[0135] 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 legitimacy of the storage hash value HVs. The information management server 100s stores the storage object data in the BC database BDB by associating the additional information AI and the storage hash value HVs with the item identification information UID (S317).

[0136] In the third embodiment described so far, the same effect as the first and second embodiments is achieved, and data processing for information management can be simplified. In addition, in the third embodiment, the first verification hash value HVd1 and the second verification hash value HVd2 are obtained from the supplier terminal 50. Moreover, when the verification hash values ​​HVd1 and HVd2 before and after the storage hash value HVs are all correct values, it is determined that the storage hash value HVs as the main body is the correct value. Therefore, even if the universal hash function HF is used in the supplier terminal 50, the legitimacy of the storage hash value HVs can be guaranteed.

[0137] (Other embodiments)

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

[0139] The form of the item identification information UID of the above-mentioned embodiment can be appropriately changed. Specifically, the number of bits of the character string and the number and type of embedded information can be appropriately changed. Furthermore, the scrambling of the identification hash value HVi and the change information VI may not be implemented. In addition, the readable code CDs may be omitted. Furthermore, an identifier that becomes the readable code CDs and is a symbol that can be distinguished by the user may be recorded in an additional label LB or the like. In addition, the product identification information PID is also the same as the item identification information UID, and can be issued to the finished product manufacturer MF through the information management server 100s. In such a modified example, the finished product manufacturer MF is also equivalent to a "reporter".

[0140] In the first modification 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, in the additional label LB of the second modification of the above embodiment, another two-dimensional code recording the storage hash value HVs is printed in parallel with the two-dimensional code CDq recording the item identification information UID. As described above, the storage hash value HVs may also be circulated together with the item IM.

[0141] In the above-mentioned embodiment, the request for information disclosure can be implemented from the front process side (upstream side) of the supply chain SC to the back process side (downstream side), or it can be implemented from the downstream side to the upstream side. According to the request for information disclosure to the upstream side, when a defect occurs in the project IM or the final product PD, the historical information TRI of the raw materials or parts used in them can be tracked. On the other hand, according to the request for information disclosure to the downstream side, when a defect is found in the project IM, the project IM or the final product PD that has been regulated in the back process of the project IM can be determined.

[0142] The traceability management system 100 of the modified example 3 of the above embodiment is divided into a recording system and Fig.16 The query system 200 shown in FIG. 1 is a recording system based on the information management server 100s (see Figure 1 However, the structure corresponding to the disclosure processing unit 35 is omitted from the information management server 100s of the recording system.

[0143] On the other hand, the query system 200 is a system equivalent to the disclosure processing unit 35 of the above-mentioned embodiment, and performs history disclosure processing (see Fig.13 ). The query system 200 is composed of a collection server 200a and a BC database BDB. The query system 200 may also be operated by an organization different from the management organization that manages the record system. As an example, the responsible operator of the final product PD may become the management organization of the query system 200.

[0144] The collection server 200a includes an accepting unit 201, a data checking unit 202, and a data providing unit 203. The accepting unit 201 accepts a public request for historical information TRI from the query terminal 110 of the queryer IQ who requests the provision of historical information (S131). The query terminal 110 may be the manufacturer terminal 10a and the user terminal 10b mentioned above. The query terminal 110 includes not only the user terminal 10b operated by the secondary user U2 or the recycling company RC, but also the user terminal 10b (terminal user terminal) owned by the terminal user US mentioned above. That is, the queryer IQ may be any one of the finished product manufacturer MF, the secondary user U2, the recycling company RC, and the terminal user US.

[0145] The inquirer IQ can implement a start request using product identification information PID (e.g., vehicle ID, etc.) for identifying the final product PD. The receiving unit 201 receives the product identification information PID provided from the inquiry terminal 110, and determines the item identification information UID to be collected for the historical information TRI based on the product identification information PID (S132). Furthermore, the receiving unit 201 determines the storage hash value HVs associated with the set item identification information UID.

[0146] In addition, the function of accepting product identification information PID may be provided in an external processing device different from the collection server 200a. On the other hand, the function of determining the stored hash value HVs based on the item identification information UID is provided inside the traceability management system 100 or the query system 200.

[0147] The BC database BDB determines the supplier SR who requests the provision of the historical information TRI based on the item identification information UID determined by the receiving unit 201, etc. The BC database BDB sends the request for provision of the historical information TRI together with the item identification information UID to the supplier terminal 50 of the determined supplier SR (S133). Each supplier SR becomes a reporter for public disclosure of the historical information TRI. The supplier terminal 50 provides the data such as the historical information TRI stored in the supplier database SDB to the collection server 200a.

[0148] The data checking unit 202 obtains data such as the historical information TRI returned from the supplier terminal 50 (S134). The data checking unit 202 cooperates with the BC database BDB to sequentially determine the supplier SR that is the upstream side in the supply chain SC and collect the historical information TRI. The data checking unit 202 implements the verification process (Before-After check) to determine whether the before-after relationship of the hash value is correctly established, and confirms whether the acquired historical information TRI has not been tampered with (S135-S138). The data checking unit 202 hands over the historical information TRI that can be confirmed to have not been tampered with to the data providing unit 203.

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

[0150] In the above-mentioned embodiment, it is also possible not to implement the issuance of item identification information UID to traders such as distributors. The terminal associated with the distributor associates the historical information TRI recorded in the circulation process with the item identification information UID attached to the item IM in transportation, and uploads it to the information management server 100s. Thus, the historical information TRI in the circulation process is also accumulated in the BC database BDB in a state of being associated with the item identification information UID, and can be provided to each trader.

[0151] The data recorder 259 used in the second embodiment can also be applied to the first embodiment and the third embodiment. Specifically, the data recorder 259 is connected to the supplier terminal 50, and records the item identification information UID and the storage hash value HVs sent from the supplier terminal 50. As a result, a backup that ensures the identity with the data obtained by the information management server 100s can be stored in the supplier database SDB together with the history information TRI.

[0152] In the transmission data DSS of the third embodiment, the storage hash value HVs is sandwiched by the first verification hash value HVd1 and the second verification hash value HVd2 on both sides. However, if security can be ensured by the operation of the system, the storage hash value HVs may not be sandwiched by the verification hash value on both sides. Specifically, in the transmission data DSS of the variation 4 of the third embodiment, only the first verification hash value HVd1 in front or only the second verification hash value HVd2 in the back is attached to the storage hash value HVs.

[0153] The functions of the application distribution server 100a and the information management server 100s may also be provided by a single server device. In addition, the application distribution server 100a and the information management server 100s may be internally deployed server devices that are physically managed by the administrator ADM or the platform, or may be virtual structures set up in the cloud. In addition, the BC database BDB and the supplier database SDB may also be constructed in a virtual file server set up in the cloud.

[0154] The generation of the stored hash value HVs, the verification hash value HVd, and the identification hash value HVi of the above-mentioned embodiment can utilize various hash functions. The hash function has the characteristic that the same hash value will not be output according to different inputs, and the input cannot be inferred from the output hash value. If it has such a characteristic, for example, encryption algorithms such as SHA-256, SHA-1, SHA-2, and SHA-3 can be appropriately used according to the required output length (number of bits). In addition, the hash functions for calculating each hash value can be the same or different from each other.

[0155] In the above-mentioned embodiment, each function provided by the traceability management system 100 can also be provided by software and hardware that executes the software, or only by software, or only by hardware, or by a combination of them. Similarly, each function provided by the supplier terminal 50, the manufacturer terminal 10a, and the intermediate layer terminal 250, etc. can also be provided by software and hardware that executes the software, or only by software, or only by hardware, or by a combination of them. In the case of providing such functions by electronic circuits as hardware, each function can also be provided by a digital circuit containing multiple logic circuits, or an analog circuit.

[0156] Each processor in the above-mentioned embodiments may be a structure including at least one CPU (Central Processing Unit) and GPU (Graphics Processing Unit) and other computing cores. In addition, the processor may also include an FPGA (Field-Programmable Gate Array) and an IP core with other dedicated functions.

[0157] The form of the storage medium (non-transitory tangible storage medium) used as each storage unit of the above-mentioned embodiment to store each program associated with the implementation of the information management method of the present disclosure can be appropriately changed. For example, the storage medium is not limited to a structure provided on a circuit substrate, and can be a structure provided in the form of a memory card, etc., inserted into a socket, and electrically connected to the bus of the computer. In addition, the storage medium can also be an optical disk and a hard disk drive used as a copy basis or distribution source for copying programs to a computer.

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

[0159] (Disclosure of technical ideas)

[0160] This specification discloses multiple technical ideas recorded in the following multiple items. Some items are recorded by selectively referring to the multiple dependent forms of the previous items in the subsequent items. In addition, some items are recorded by referring to the multiple dependent forms of other multiple dependent forms (a multiple dependent form referring to another multiple dependent form). These items recorded in multiple dependent forms define multiple technical ideas.

[0161] (Technical Thought 1)

[0162] An information management method is implemented by a computer (100c) to manage information provided by a plurality of reporters (SR) constituting a supply chain (SC).

[0163] The process performed by at least one processor (11) comprises the following steps:

[0164] issuing item identification information (UID) to an issuing destination terminal (50, 250) associated with the reporter, wherein the item identification information is attached to an item (IM) shipped from the reporter to identify the item (S21-S26);

[0165] Acquiring a storage hash value (HVs) together with the item identification information, wherein the storage hash value is a hash of history information (TRI) associated with the item (S31); and

[0166] The stored hash value is stored in the database (BDB) in a state associated with the item identification information (S36).

[0167] (Technical Thought 2)

[0168] The information management method according to technical idea 1 further comprises the following steps: providing verification data (Dd) to the issuing destination terminal, wherein the verification data is used to verify the stored hash value obtained from the issuing destination terminal (S11, S313);

[0169] acquiring, from the issuing destination terminal, a verification hash value (HVd) generated by hashing the verification data (S12, S315); and

[0170] When the verification hash value is a correct value, it is determined that the stored hash value acquired from the issuing destination terminal is a correct value (S35, S316).

[0171] (Technical Thought 3)

[0172] According to the information management method described in the technical idea 2, the method further includes the step of providing the application program (HAP) for performing the hashing process to the issuing destination terminal (S101 to S105).

[0173] (Technical Thought 4)

[0174] According to the information management method described in technical idea 3, in the step of acquiring the stored hash value, additional information is also acquired, and the additional information includes information indicating a version of the application program that has been subjected to the hashing process.

[0175] (Technical Thought 5)

[0176] According to the information management method described in technical idea 2, in the step of obtaining the verification hash value, a first verification hash value (HVd1) and a second verification hash value (HVd2) are obtained from the issuing destination terminal, wherein the first verification hash value is generated by using the hashing process of the verification data before the hashing process of the historical information, and the second verification hash value is generated by using the hashing process of the verification data after the hashing process of the historical information,

[0177] In the step of determining the stored hash value, when both the first verification hash value and the second verification hash value are correct values, it is determined that the stored hash value obtained from the issuing destination terminal is a correct value.

[0178] (Technical Thought 6)

[0179] According to the information management method described in technical idea 1, in the step of issuing the item identification information, the item identification information is issued to an intermediate layer terminal as the issuance destination terminal operated in the intermediate layer (ML),

[0180] In the step of acquiring the storage hash value, storage object data (DSS) is acquired, wherein the storage object data is data in which the intermediate terminal associates the item identification information with the storage hash value generated by the reporter terminal used by the reporter.

[0181] (Technical Thought 7)

[0182] The information management method according to technical idea 6 includes the following steps: providing the reporter storage data having the same content as the item identification information and the storage hash value stored in the database to the reporter terminal (S93); and

[0183] The reporter-stored data is stored in a reporter database (SDB) used by the reporter (S84).

[0184] (Technical Thought 8)

[0185] According to the information management method recorded in any one of technical ideas 1 to 7, in the step of issuing the above-mentioned project identification information, at least one change information (VI) according to each change of the above-mentioned project and an identification hash value (HVi) obtained by hashing the original data containing the above-mentioned change information are embedded in the above-mentioned project identification information.

[0186] (Technical Thought 9)

[0187] According to the information management method described in technical idea 8, in the step of issuing the item identification information, characteristic information (CI) is embedded in the item identification information, wherein the characteristic information represents the characteristic of the item identification information.

[0188] The above-mentioned characteristic information is removed from the above-mentioned original data.

[0189] (Technical Thought 10)

[0190] According to the information management method recorded in any one of technical ideas 1 to 8, it also includes the following steps: recording a character string (CDs) corresponding to a part of the above-mentioned project identification information in a readable state on an additional medium (LB) that records the above-mentioned project identification information and is attached to the above-mentioned project (S73, S74).

[0191] (Technical Thought 11)

[0192] According to the information management method described in any one of technical ideas 1 to 9, in the step of storing in the above-mentioned database, the above-mentioned storage hash value is stored using blockchain (BC) technology.

[0193] (Technical Thought 12)

[0194] The information management method according to any one of technical concepts 1 to 10, further comprising the steps of: acquiring related information (LI) from a deliverer terminal (10a) of a deliverer (MF) that delivers the item, wherein the related information (LI) is information that associates the item identification information attached to the item with related identification information (PID) that identifies a related object (PD) associated with the item (S51); and

[0195] The above-mentioned related information is stored in the above-mentioned database (S52).

[0196] (Technical Thought 13)

[0197] An information management device is an information management device for managing information provided by a plurality of reporters (SR) constituting a supply chain (SC), comprising:

[0198] an issuing unit (32) for issuing item identification information (UID) to an issuing destination terminal associated with the reporter, wherein the item identification information is attached to an item (IM) shipped from the reporter to identify the item (50, 250);

[0199] an acquisition unit (33) for acquiring a stored hash value (HVs) together with the item identification information, wherein the stored hash value is obtained by hashing the history information (TRI) associated with the item; and

[0200] The storage unit (34) stores the stored hash value in a database (BDB) in a state of being associated with the item identification information.

Claims

1. An information management method, implemented by a computer (100c), for managing information provided by a plurality of reporters (SR) constituting a supply chain (SC), wherein: The process performed by at least one processor (11) comprises the following steps: issuing item identification information (UID) to an issuing destination terminal (50, 250) associated with the reporter, wherein the item identification information is attached to an item (IM) shipped from the reporter to identify the item (S21-S26); Acquiring a storage hash value (HVs) together with the item identification information, wherein the storage hash value is a hash of history information (TRI) associated with the item (S31); and The stored hash value is stored in the database (BDB) in a state associated with the item identification information (S36).

2. The information management method according to claim 1, wherein: It also includes the following steps: providing verification data (Dd) to the issuing destination terminal, wherein the verification data is used to verify the stored hash value obtained from the issuing destination terminal (S11, S313); acquiring, from the issuing destination terminal, a verification hash value (HVd) generated by hashing the verification data (S12, S315); and When the verification hash value is a correct value, it is determined that the stored hash value acquired from the issuing destination terminal is a correct value (S35, S316).

3. The information management method according to claim 2, wherein: It also includes the following steps: The application program (HAP) for performing the hashing process is provided to the issuing destination terminal (S101 to S105).

4. The information management method according to claim 3, wherein: In the step of acquiring the stored hash value, additional information is further acquired, the additional information including information indicating a version of the application program that has been subjected to the hashing process.

5. The information management method according to claim 2, wherein: In the step of obtaining the verification hash value, a first verification hash value (HVd1) and a second verification hash value (HVd2) are obtained from the issuing destination terminal, wherein the first verification hash value is generated by using the hashing process of the verification data before the hashing process of the history information, and the second verification hash value is generated by using the hashing process of the verification data after the hashing process of the history information, In the step of determining the stored hash value, when both the first verification hash value and the second verification hash value are correct values, it is determined that the stored hash value obtained from the issuing destination terminal is a correct value.

6. The information management method according to claim 1, wherein: In the step of issuing the item identification information, the item identification information is issued to a middle layer terminal as the issuing destination terminal operated in a middle layer (ML). In the step of acquiring the storage hash value, storage object data (DSS) is acquired, wherein the storage object data is data in which the intermediate terminal associates the item identification information with the storage hash value generated by the reporter terminal used by the reporter.

7. The information management method according to claim 6, wherein: The following steps are included: Providing the reporter storage data having the same contents as the project identification information and the storage hash value stored in the database to the reporter terminal (S93); as well as The reporter-stored data is stored in a reporter database (SDB) used by the reporter (S84).

8. The information management method according to any one of claims 1 to 7, wherein: In the step of issuing the item identification information, at least one change information (VI) according to each change of the item and an identification hash value (HVi) obtained by hashing original data including the change information are embedded in the item identification information.

9. The information management method according to claim 8, wherein: In the step of issuing the item identification information, characteristic information (CI) is embedded in the item identification information, wherein the characteristic information indicates the characteristics of the item identification information. The above-mentioned characteristic information is removed from the above-mentioned original data.

10. The information management method according to any one of claims 1 to 7, wherein: It also includes the following steps: A character string (CDs) corresponding to a part of the item identification information is recorded in a readable state on an additional medium (LB) that records the item identification information and is attached to the item (S73, S74).

11. The information management method according to any one of claims 1 to 7, wherein: In the step of storing in the above-mentioned database, the above-mentioned hash value is stored using the blockchain (BC) technology.

12. The information management method according to any one of claims 1 to 7, wherein: It also includes the following steps: acquiring, from a deliverer terminal (10a) of a deliverer (MF) that delivers the item, associated information (LI), wherein the associated information (LI) is information associating the item identification information attached to the item with associated identification information (PID) identifying a related object (PD) associated with the item (S51); and The above-mentioned related information is stored in the above-mentioned database (S52).

13. An information management device for managing information provided by a plurality of reporters (SR) constituting a supply chain (SC), comprising: The issuing unit (32) issues the item identification information (UID) to the issuing destination terminal associated with the reporter, wherein: The item identification information is attached to the item (IM) shipped from the reporter and is used to identify the item (50, 250); an acquisition unit (33) for acquiring a stored hash value (HVs) together with the item identification information, wherein the stored hash value is obtained by hashing the history information (TRI) associated with the item; and The storage unit (34) stores the stored hash value in a database (BDB) in a state of being associated with the item identification information.

Images