Information management method and information management device

Abstract

The invention relates to an information management method and an information management apparatus. A reporter terminal (50) manages information collected by a vendor (SR) under the management of an administrator (ADM). In an information management method implemented by a reporter terminal (50), transmission data based on reporter data prepared by a supplier (SR) side is transmitted to an information recording server (100r) associated with an administrator (ADM). In addition, a backup of the transmission data is prepared, and confirmation information for confirming that the backup has not been changed is also prepared. The backup is stored in a reporter database (SDB) together with the confirmation information.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on Japanese Patent Application No. 2022-102989 filed in Japan on June 27, 2022, the contents of which are incorporated herein by reference in their entirety. Technical Field

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

[0004] In the supply chain management system disclosed in Patent Document 1, information such as delivery records of items acquired by traders constituting the supply chain is sent to a data management server of a manager managing the supply chain. As a result, transaction records in the supply chain can be accumulated in a manner that is difficult to tamper with.

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

[0006] In the supply chain management system of Patent Document 1, each trader can keep a backup of the transmitted data in its own database. However, if the backup on the trader side is changed, it is difficult to confirm whether there is any change. Summary of the invention

[0007] The present disclosure aims to provide an information management method and an information management device capable of confirming that a backup has been changed.

[0008] In order to achieve the above-mentioned purpose, a disclosed method is set as an information management method, which is implemented by a computer and manages information collected by reporters under the management of an administrator (ADM), wherein, in the processing executed by at least one processor, the following steps are included: sending sending data based on reporter data prepared by the reporter side to a sending destination associated with the administrator; preparing a backup of the sending data; further preparing confirmation information for confirming that the backup has not been changed; and storing the backup together with the confirmation information in the reporter's database.

[0009] In addition, one disclosed method is set as an information management device, which is an information management device for managing information obtained by a reporter under the management of an administrator, wherein the device comprises: a data sending unit, which sends sending data based on reporter data prepared by the reporter side to a sending destination associated with the administrator; and a data storage unit, which prepares a backup of the sending data, further prepares confirmation information for confirming that the backup has not been changed, and stores the backup together with the confirmation information in the reporter's database.

[0010] In these methods, confirmation information for confirming that the backup of the transmitted data has not been altered is prepared and stored in the database of the reporter together with the backup. Therefore, by using the confirmation information, it is possible to confirm that the backup has been altered.

[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 there is no particular hindrance in the combination, the combination of claims 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 according to the first embodiment of the present disclosure.

[0013] Figure 2 This is a block diagram showing the electrical structure of systems and terminals related to traceability management.

[0014] Figure 3 This is a diagram showing an overall picture of main processes performed by the information recording server and the reporter terminal.

[0015] Figure 4 This is a flowchart showing the details of the reporter process performed by the reporter terminal.

[0016] Figure 5 This is a diagram showing an example of a backup stored in a reporter database.

[0017] Figure 6 This is a diagram showing an example of confirmation data stored in the reporter database.

[0018] Figure 7 is with Figure 8 A diagram showing a pattern of a process for generating confirmation data.

[0019] Figure 8 is with Figure 7 A diagram showing a pattern of a process for generating confirmation data.

[0020] Fig. 9 is with Figure 7 A diagram showing another mode of the process of generating confirmation data.

[0021] Fig.10 is with Fig.11 The following is a diagram showing still another mode of the process of generating confirmation data.

[0022] Fig.11 is with Fig.10 The following is a diagram showing still another mode of the process of generating confirmation data.

[0023] Fig.12 This is a diagram showing an example of an intention confirmation record recorded when a backup is changed.

[0024] Fig.13 It is a diagram showing an overall image of main processing performed in the second embodiment. DETAILED DESCRIPTION

[0025] 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.

[0026] (First Embodiment)

[0027] Figure 1 The supply chain SC in the first embodiment of the present disclosure is a link 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 supplied by the supply chain SC may be various items such as automobiles, batteries, semiconductors, fresh food, aquatic products, food, flowers, pharmaceuticals, and chemicals.

[0028] As an 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 virgin 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 related to the circulation of items IM and the final product. In addition, the supply chain SC may also include the end user US who uses the final product, as well as secondary users U2 and recyclers RC who reuse, refurbish, recycle, and discard the final product.

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

[0030] The traceability management system 100 can communicate with the reporter terminal 50, the manufacturer terminal 10a, and the user terminal 10b through the network. When the final product (for example, a car, etc.) has a communication function, the traceability management system 100 can also communicate with the final product. The traceability management system 100 saves the information obtained through the network in a substantially tamper-proof state by utilizing the information management of the blockchain BC technology. In addition, the traceability management system 100 collects information under the management of various suppliers SR, etc. according to the requests of the manager ADM (or supervisory agency), the end user US, and the finished product manufacturer MF, and discloses it to the request source.

[0031] The reporter terminal 50 is an information processing device used by the supplier SR. The reporter terminal 50 is associated with each supplier SR. The reporter terminal 50 accumulates historical information TRI related to the project IM. The historical information TRI includes 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 by the manufacture of the project IM can also be recorded as historical information TRI.

[0032] The historical information TRI is kept by the reporter terminal 50 and disclosed to the outside according to the situation. For example, when a project IM or a final product has a certain defect or is likely to have a defect, the historical information TRI is provided to other traders, the finished product manufacturer MF or the end user US through the manager ADM. The provided historical information TRI is used for the investigation of the cause of the defect, etc. As described above, at least a part of the historical information TRI becomes information for realizing the traceability of the project IM.

[0033] The reporter terminal 50 receives the issuance of inherent identification information (hereinafter referred to as project identification information UID) for identifying the project IM from the traceability management system 100. The project identification information UID is a unique identifier (unique identification) that does not repeat each other. As an example, the project identification information UID is set to a 32-bit string. The project identification information UID can be issued not only for parts, etc., but also for recycled materials, etc. The project identification information UID is attached to the project IM shipped from the supplier SR and delivered to the trader of the next process together with the project IM. For a specific project IM, the reporter terminal 50 associates the hash value HV generated based on the original data containing the historical information TRI with the issued project identification information UID, and uploads it to the traceability management system 100.

[0034] The manufacturer terminal 10a is an information processing device operated by the finished product manufacturer MF. The manufacturer terminal 10a generates link information LI (refer to Figure 1 ). The manufacturer terminal 10a uploads the product identification information PID, the item identification information UID, and the link information LI to the traceability management system 100.

[0035] The user terminal 10b is an information processing device used by the end user US, 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 user terminal 10b is used by the secondary user U2 or the recycler RC, the user terminal 10b transmits the change information XI (refer to Figure 1 ) is uploaded to the traceability management system 100. For example, the traceability management system 100 is notified of change information XI indicating the disappearance of item IM, or change information XI requesting modification or transfer of link information LI, and the like.

[0036] The manufacturer terminal 10a and the user terminal 10b can use the product identification information PID or the item identification information UID to request the disclosure of the historical information TRI related to the final product or item IM from the traceability management system 100. The manufacturer terminal 10a and the user terminal 10b obtain the historical information TRI from the traceability management system 100 and display it on a display, etc. As described above, the end user US, the secondary user U2, the recycler RC, and the finished product manufacturer MF can use the manufacturer terminal 10a or the user terminal 10b as the query terminal 10c to browse the historical information TRI.

[0037] Next, based on Figure 1 to Figure 3 , further describing the detailed contents of the traceability management system 100 and the reporter terminal 50.

[0038] The traceability management system 100 has an application distribution server 100a, an information recording server 100r, and an information query server 100i. Each server 100a, 100r, and 100i is an information processing device 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 functions as a computer that performs 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.

[0039] The application distribution server 100a functions as a server device for distributing hashed applications HAP. The hashed application HAP is an application program installed in each reporter terminal 50. In each reporter terminal 50, the hashed application HAP performs a hashing process of hashing the reporter data containing at least historical information TRI based on the rules specified by the administrator ADM, and generates a hash value HV. The hashed application HAP maintains security in traceability management through regular updates. In addition, the distribution of the hashed application HAP can also be implemented by the platform vendor of the operating system that enables the reporter terminal 50 to operate.

[0040] The information recording server 100r functions as an information management device on the manager ADM side that manages information related to the project IM. The information recording server 100r manages various information collected by suppliers SR and the like under the management of the manager ADM and submitted to the manager ADM side. The information recording server 100r includes a distribution unit 31 and a storage unit 32 and other functional units (see FIG. 1 ). Figure 2 ).

[0041] The issuing unit 31 issues item identification information UID (see Figure 3 S11). The issuing unit 31 implements ID issuance processing according to the request from the supplier SR (reporter terminal 50), and issues the number of project identification information UIDs required by the supplier SR. The issuing unit 31 can implement at least one of batch processing for collectively issuing a specified amount of project identification information UIDs, processing for issuing project identification information UIDs at any time, and processing for post-issuing project identification information UIDs. In detail, when receiving a request based on the production plan of the supplier SR on the reporter side, the issuing unit 31 pre-issues a certain number of required project identification information UIDs according to such a request. In addition, the issuing unit 31 receives a number issuance request for the project identification information UID each time the storage object data in the supplier SR is generated, and issues the project identification information UID on demand according to the request. In addition, the issuing unit 31 post-issues the project identification information UID for data that is uploaded by the reporter terminal 50 (hash value HV) and is not associated with the project identification information UID. In this case, a notification of the allocation record of the project identification information UID is received on the manager ADM side, and the uploaded data is stored through the processing described later.

[0042] The storage unit 32 stores the information obtained from the reporter terminal 50 in the blockchain database (hereinafter referred to as the BC database) BDB by implementing the data storage processing. The BC database BDB uses the technology of the blockchain BC to store the storage object data such as the hash value HV associated with the project identification information UID and the additional data in a substantially tamper-proof state. As an example, the BC database BDB stores the acquired storage object data as a transaction in a block of a private or consortium 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, the form of the blockchain BC is not limited to private and consortium types. In another example, a public blockchain BC is used. Specifically, the BC database BDB makes the storage object data substantially tamper-proof by storing the hash value generated based on the storage object data in the block of the public blockchain BC.

[0043] The storage unit 32 verifies the legitimacy of the hash value HV obtained from the reporter terminal 50 during the data storage process. However, the original data used to generate the hash value HV in the reporter terminal 50, that is, the history information TRI, etc., is not provided to the information recording server 100r. Therefore, when the correct hashing application HAP is used in the reporter terminal 50 and the hashing application HAP operates normally, the storage unit 32 determines that the hash value HV is a correct value.

[0044] Specifically, the storage unit 32 checks the version of the hashing application HAP running in the reporter terminal 50 based on the application information (described later) of the additional data acquired from the reporter terminal 50 (see Figure 3 S51) When an inappropriate hashed application HAP such as an application of unknown origin or an old version that is no longer usable is used in the reporter terminal 50, the storage unit 32 makes an NG determination indicating that the legitimacy of the hash value HV cannot be ensured.

[0045] When an appropriate hashing application HAP is used in the reporter terminal 50, the storage unit 32 further checks whether the hashing application HAP is operating normally (see Figure 3S52). The information recording server 100r provides the reporter terminal 50 with pseudo data for verification that is input into the hashed application HAP instead of the historical information TRI. The storage unit 32 obtains a hash value for verification based on the pseudo data from the reporter terminal 50. When the hash value for verification is a correct value, the storage unit 32 determines that the hashed application HAP is operating normally and the legitimacy of the hash value HV can be guaranteed. In this case, the storage unit 32 stores the hash value HV and the additional data in the BC database BDB (refer to Figure 3 S53) Based on the above, the custody object data is registered in the blockchain BC.

[0046] The information inquiry server 100i is a server device that implements the disclosure processing of the historical information TRI to the inquirer who uses the manufacturer terminal 10a and the user terminal 10b as the inquiry terminal 10c. Specifically, when the information inquiry server 100i receives a disclosure request from the inquiry terminal 10c, it determines the item identification information UID that is the collection object of the historical information TRI based on the product identification information PID or the item identification information UID obtained together with the disclosure request. The information inquiry server 100i determines the supplier SR (reporter terminal 50) who requests the provision of the historical information TRI based on the determined item identification information UID. The information inquiry server 100i sends a request for the provision of the historical information TRI to each determined reporter terminal 50, and receives the provision of the original data of the historical information TRI from each reporter terminal 50. The information inquiry server 100i confirms whether the historical information TRI obtained from each reporter terminal 50 has been tampered with. The information inquiry server 100i generates the data for provision using the historical information TRI that has been confirmed to be untampered, and provides the generated data for provision to the inquiry terminal 10c that is the request source of the disclosure request.

[0047] The above information recording server 100r and information query server 100i can be local server devices physically managed by the administrator ADM or platform providers, or can be virtual structures set up on the cloud. That is, the above-mentioned functional units are not limited to being built in the control circuit 100c, but can be built in a third-party server commissioned by the administrator ADM or platform providers. In addition, the BC database BDB can also be built in a virtual file server set up on the cloud.

[0048] The reporter terminal 50 is a structure mainly composed of a control circuit 50c, and is electrically connected to a display 56, a scanner 57, and a printer 58. At least a part of the display 56, the scanner 57, and the printer 58 may be a structure integrated with the reporter terminal 50. In addition, an input device such as a keyboard may be connected to the reporter terminal 50 for error processing, etc.

[0049] 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 performed by the control circuit 50c. For example, the display 56 displays an image showing the history information TRI based on the provision data, an image notifying the error information received from the information recording server 100r, etc. The display 56 may also have a touch panel function for receiving user operations.

[0050] The scanner 57 reads the additional label LB (see Figure 1 ) is a reading device. The scanner 57 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 is 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 scanner 57 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 can be displayed on a display device such as a display and electronic paper, or can be directly engraved or printed on the project IM using a laser marker or an inkjet printer.

[0051] The printer 58 is an output device that outputs the additional label LB. The printer 58 prints the two-dimensional code CDq based on the item identification information UID provided from the information recording server 100r 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. In addition, instead of the additional label LB output on demand from the printer 58, the additional label LB printed and issued in advance by the manager ADM and sent to the supplier SR may be circulated together with the item IM. In addition, in the case where the two-dimensional code CDq is directly engraved or printed on the item IM, the above-mentioned laser marker or the like can be used as an output device instead of the printer 58.

[0052] The control circuit 50c of the reporter terminal 50 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 that performs calculation processing. The processor 51 is hardware for calculation processing combined with the RAM 52. The storage unit 53 stores information management programs and hashing applications HAP on the reporter side. The reporter terminal 50 has functional units such as a data collection unit 61, an information receiving unit 62, an ID output unit 63, a data generation unit 64, a data transmission unit 65, and a data management unit 66 by executing the programs and applications stored in the storage unit 53 (see Figure 2 ). The reporter terminal 50 implements the reporter processing by cooperation of each functional unit (refer to Figure 4 ).

[0053] The data collection unit 61 acquires data of the item identification information UID from the scanner 57 that reads the attached label LB of the item IM delivered to the supplier SR. In addition, the data collection unit 61 prepares the reporter data as the hashed target data in the reporter processing (see Figure 4 S31). The reporter data is information prepared by the supplier SR through collection, and is information related to the item IM shipped from the supplier SR. In addition to the historical information TRI, the reporter data also includes product information indicating the type of the item IM (product) shipped, and batch information indicating the batch of the product, etc. (refer to Figure 5 ) The data collection unit 61 may automatically acquire the reporter data from other server devices at the base of the supplier SR, or may acquire the reporter data manually input by the staff of the supplier SR according to a predetermined management process.

[0054] The information receiving unit 62 requests the issuing unit 31 to issue the item identification information UID attached to the item IM shipped from the supplier SR. The information receiving unit 62 receives the item identification information UID issued based on the issuance request from the issuing unit 31 (see Figure 3 S12). The information receiving unit 62 collects the received project identification information UID group and provides the project identification information UID to the ID output unit 63 and the data generating unit 64 according to the factory delivery of the project IM. In addition, the information receiving unit 62 obtains pseudo data for determining the normal operation of the hashed application HAP from the information recording server 100r and provides it to the data generating unit 64.

[0055] The ID output unit 63 is connected to the printer 58. The ID output unit 63 causes the printer 58 to output the additional label LB. The ID output unit 63 generates a two-dimensional code CDq on which the item identification information UID is recorded, using the data of the item identification information UID provided from the information receiving unit 62. The ID output unit 63 outputs the print data including the two-dimensional code CDq to the printer 58, and causes the printer 58 to print the additional label LB. In addition, as described above, in the method in which the additional label LB printed with the item identification information UID is provided by the manager ADM, the ID output unit 63 and the printer 58 may not be provided in the reporter terminal 50.

[0056] The data generation unit 64 generates transmission data to be uploaded to the information recording server 100r using the reporter data collected by the data collection unit 61. In the reporter process, the data generation unit 64 transmits the reporter data including the history information TRI to the hashing application HAP and generates a hash value HV (see Figure 3 as well as Figure 4 S32). Furthermore, the data generation unit 64 generates additional data to be added to the hash value HV (see S33). The data generation unit 64 prepares application information related to the hashed application HAP and project information related to the project IM as additional data. The application information includes, for example, information indicating the version of the hashed application HAP in operation, information indicating the provider of the hashed application HAP, and the like.

[0057] The data generation unit 64 obtains the item identification information UID from the information receiving unit 62. The data generation unit 64 generates the transmission data by associating the hash value HV and the additional data with the obtained item identification information UID (see S34). The hash value HV and the additional data included in the transmission data are displayed on the display 56 for the staff's confirmation (see S35). At this time, the staff may be asked whether they agree to the transmission.

[0058] The data transmission unit 65 controls the transmission of information from the reporter terminal 50 to the information recording server 100r. For example, the data transmission unit 65 transmits a hash value based on dummy data to the information recording server 100r. In addition, in the reporter process, the data transmission unit 65 transmits transmission data based on the reporter data to the information recording server 100r as the transmission destination associated with the manager ADM (see Figure 3 as well as Figure 4 S36).

[0059] The data sending unit 65 is connected to the data recorder 59. The data recorder 59 records the sending log of the data sent to the information recording server 100r. The data recorder 59 provides the backup of the sending data sent to the information recording server 100r together with the sending log to the data management unit 66. Information indicating what content of data was sent to which sending destination is recorded in the sending log. In addition, the function of the data recorder 59 may not be set on the supplier SR side. It can also be set in a shared area set up according to the negotiation between the supplier SR and the manager ADM. In addition, the function of the data recorder 59 may also be set in a part of the area (traceability management system 100) on the manager side set up according to the negotiation between the supplier SR and the manager ADM.

[0060] The data recorder 59 includes a checker unit 69. The checker unit 69 checks whether the transmission data having the same content as the backup has been transmitted to the information recording server 100r. The checker unit 69 records information indicating that the backup provided to the data management unit 66 and the transmission data transmitted to the information recording server 100r have the same content in the transmission log provided to the data management unit 66. In the checker unit 69, only when it is determined that the two data have the same content, the data recorder 59 normally ends the data transmission. When it is determined that the two data do not have the same content, the data recorder 59 may also send an error notification to at least one of the information recording server 100r and the data management unit 66.

[0061] The data management unit 66 is connected to the reporter database SDB. The data management unit 66 manages the data stored in the reporter database SDB. The reporter database SDB stores reporter data that is the original data of the transmission data, such as historical information TRI. The reporter database SDB may be a local storage device set up at the base of the supplier SR, or a storage device on the cloud. The data management unit 66 performs processing related to the storage of information in the reporter database SDB and the extraction of information from the reporter database SDB.

[0062] The data management unit 66 obtains the transmission log of the transmission data from the data logger 59 in the reporter process (see Figure 4 S37) In addition, the data management unit 66 obtains information from the data recorder 59 to prepare a backup of the transmission data (see Figure 3 as well as Figure 4S38). In addition, the data management unit 66 also prepares confirmation information for confirming that the backup has not been changed (refer to S39). The confirmation information is information related to the illegal prevention function set in the reporter terminal 50. The data management unit 66 generates the file number and hashed data described later as confirmation information. The data management unit 66 associates the backup, confirmation information, and transmission log with the reporter data and stores them in the reporter database SDB (refer to S40).

[0063] The data management unit 66 receives the request for providing information from the information inquiry server 100i. Figure 1 ) in the post-process side (downstream side), the supplier SR and the finished product manufacturer MF, as well as the manager ADM and the supervisory agency of the supply chain SC, implement the provision request. The end user US, the secondary user U2 and the recycler RC can also be the implementers of the provision request. The provision request is implemented for the purpose of requesting the disclosure of historical information TRI related to the project IM, confirming the legality of the disclosed information, and other purposes. The data management department 66 grasps the project identification information UID notified together with the provision request, and extracts the historical information TRI (reporter data) associated with the project identification information UID from the reporter database SDB. The data management department 66 provides the extracted historical information TRI, etc. to the information query server 100i.

[0064] Next, based on Figure 5 to Figure 12 , refer to Figure 1 to Figure 3 , further explains the details of the backup and confirmation information stored in the reporter database SDB.

[0065] The data management unit 66 assigns a file number to the backup of the transmission data generated based on the reporter data. The file number is a continuous management number of a specified number of digits and is confirmation information used to confirm that the backup has not been deleted. The data management unit 66 sets the backup assigned with the file number as management data. In the management data, a file number is associated with the project identification information UID, additional data including project information and application information, and a hash value HV. The data management unit 66 generates the accumulation data stored in the reporter database SDB by combining the management data with the reporter data as the original data of the backup (refer to Figure 5 ).

[0066] The data management unit 66 also generates hashed data by hashing the backup (management data) using a hash function. The hashed data is confirmation information used to confirm that the contents of the backup have not been tampered with. The data management unit 66 may use either the hashing application HAP or a hash function different from the hashing application HAP (for example, SHA-256, etc.) in generating the hashed data. The data management unit 66 generates a value obtained by hashing the file number, the project identification information UID, the additional data, and the hash value HV as hashed data (see Figure 6 ).

[0067] In order to improve security, the data management unit 66 can hash the reporter data and the backup combination to generate hashed data. The data management unit 66 independently inputs the reporter data, file number, additional data, project identification information UID, and hash value HV into the hash function to obtain the hashed values. In addition, the data management unit 66 divides the hashed values ​​into two parts (see Figure 7 ).

[0068] Here, in the following description, the first half and the second half of the value obtained by hashing the reporter data are recorded as "bao-01" and "bao-02", respectively, and the first half and the second half of the value obtained by hashing the file number are recorded as "wen-01" and "wen-02", respectively. In addition, the first half and the second half of the value obtained by hashing the additional data are recorded as "fu-01" and "fu-02", respectively, and the first half and the second half of the value obtained by hashing the item identification information UID are recorded as "u-01" and "u-02", respectively. Furthermore, the first half and the second half of the value obtained by hashing the hash value HV are recorded as "h-01" and "h-02", respectively.

[0069] The data management unit 66 further hashes a character string formed by combining other hashed values ​​based on the hashed value of the reporter data (see Figure 8)。Specifically, the value obtained by inputting the string obtained by arranging "Report - 01", "Document - 01", "Report - 02", "Document - 02" in order into a hash function is set as the value of the file number after hashing. Similarly, the value obtained by inputting the string obtained by arranging "Report - 01", "Appendix - 01", "Report - 02", "Appendix - 02" in order into a hash function is set as the value of the additional data after hashing. In addition, the value obtained by inputting the string obtained by arranging "Report - 01", "U - 01", "Report - 02", "U - 02" in order into a hash function is set as the value of the item identification information UID after hashing. And, the value obtained by inputting the string obtained by arranging "Report - 01", "H - 01", "Report - 02", "H - 02" in order into a hash function is set as the value of the hash value HV after hashing. The data management unit 66 combines each hashed value (hashed data) with the reporter data and stores it as confirmation data in the reporter database SDB.

[0070] The data management unit 66 changes the content of the process of hashing the reporter data based on a prescribed trigger. The data management unit 66 changes the method of dividing the hashed value, the arrangement method of the divided values (strings), and the method of hashing the rearranged values, etc. based on a prescribed trigger. The data management unit 66 changes the hashing process mode, for example, based on the elapse of a prescribed period, a change in date and time, or a change in the version of the hashing application HAP, etc., as the prescribed trigger. The data management unit 66 records a mode identifier indicating the applied hashing process mode in the confirmation data (refer to Figure 8 ). For convenience, the above hashing process is set as the hashing process of "Mode 1".

[0071] Here, another mode of the hashing process implemented in the data management unit 66 will be further described. In the hashing process of "Mode 2" (refer to Fig. 9 ), the values obtained by hashing "Report - 01" and "Document - 01", and the values obtained by hashing "Report - 02" and "Document - 02" are generated respectively. Then, the Merkle Root of each value is set as the value of the file number after hashing. Similarly, the Merkle Root of "Report - 01" and "Appendix - 01", and "Report - 02" and "Appendix - 02" is set as the value of the additional data after hashing. In addition, the Merkle Root of "Report - 01" and "U - 01", and "Report - 02" and "U - 02" is set as the value of the item identification information UID after hashing. And, the Merkle Root of "Report - 01" and "H - 01", and "Report - 02" and "H - 02" is set as the value of the hash value HV after hashing.

[0072] Also, in the hashing process of "Mode 3", the data management unit 66 performs individual hashing on the reporter data, file number, additional data, item identification information UID, and hash value HV, and divides each hashed value into four parts (refer to Fig.10 ). Through such processing, "Report - 01" to "Report - 04" and "Document - 01" to "Document - 04" are prepared.

[0073] The data management unit 66 reorganizes the divided values in ascending order and inputs them into the hash function to generate each hashed value. Specifically, the value obtained by inputting the string arranged in the order of "Report - 01", "Document - 01", "Report - 02", "Document - 02", "Report - 03", "Document - 03", "Report - 04", "Document - 04" into the hash function is set as the hashed value of the file number (refer to Fig.11 ). The data management unit 66 also performs the same hashing process on the additional data, item identification information UID, and hash value HV to generate the hashed values for each item.

[0074] The data management unit 66 can verify whether the management data (backup) stored in the reporter database SDB has changed by comparing it with the hashed confirmation data (refer to Figure 6 ). In the confirmation data, the management data is hashed for each value (item), so the data management unit 66 can detect which part has been tampered with. Specifically, in the verification process of the management data, the data management unit 66 hashes each value of the management data through the same hashing process as when generating the hashed data. The data management unit 66 checks whether each hashed value is different from the values saved as the confirmation data.

[0075] As an example, when only the item identification information UID in the management data is tampered with, the hash value of the item identification information UID recalculated from the management data is different from the value of the item identification information UID registered in the confirmation data. The data management unit 66 determines the tampering location of the management data based on such a difference in values.

[0076] As another example, when the reporter data is tampered with, the hash values of all items recalculated are different from the values registered in the confirmation data. Therefore, when all the recalculated values do not match the values in the confirmation data, the data management unit 66 estimates that the possibility of tampering with the reporter data is relatively high.

[0077] The data management unit 66 prohibits editing of the accumulated data in principle in order to prevent forgery disguised as negligence. When the data management unit 66 makes any changes to the accumulated data, it implements the staff's intention confirmation and adds an intention confirmation record recording the details of the applied changes to the accumulated data. The intention confirmation record records the content of the change action (e.g., clearing, etc.), the date and time of the change, the reason for the change (e.g., stoppage of shipment and damage during transportation, etc.), and the staff who made the change (see Fig.12 ). The data management unit 66 starts the change record processing based on the start of the staff's change operation, and grasps the content of the change applied to the accumulated data (backup). The data management unit 66 generates an intention confirmation record based on the grasped change content. The data management unit 66 associates the generated intention confirmation record with the accumulated data including the backup and saves it in the reporter database SDB.

[0078] In the first embodiment described so far, confirmation information for confirming that the backup of the transmission data (management data) has not been altered is prepared and stored in the reporter database SDB together with the backup. Therefore, by using the confirmation information, it is possible to confirm that the backup has been altered.

[0079] In addition, in the first embodiment, a backup of the transmission data is retained on the supplier SR side as the reporter. Therefore, in the case where there is an extraction of the transmission data (storage object data) by the manager ADM, the backup on the reporter side can be used to verify the occurrence of such extraction. And, if it is possible to verify that the backup on the reporter side has not been changed using confirmation information, it is also possible to prove that there is no extraction of the transmission data by the manager ADM based on the backup on the reporter side and the confirmation information. Based on the above, it is possible to share between the manager ADM and the reporter that there is no illegal data extraction.

[0080] In addition, in the first embodiment, as confirmation information, a file number that is a continuous management number is assigned to the backup stored in the reporter database SDB. Therefore, even if the backup stored in the reporter database SDB is deleted together with the reporter data, the reporter terminal 50 can detect the deletion of the backup based on the discontinuity of the file number. Based on the above, it can be confirmed that illegal data deletion has not been performed, so the accumulated data accumulated in the reporter database SDB can be used as evidence for monitoring the record maintenance status.

[0081] In the first embodiment, hashed data is generated as confirmation information by hashing the backup using a hash function. Therefore, even if a specific item of the backup stored in the reporter database SDB is changed, tampering can be detected by comparison with the hashed confirmation data.

[0082] Furthermore, in the first embodiment, the values ​​of each item of the backup are independently hashed in the confirmation data table. Therefore, in the verification process of the backup (management data), based on the comparison of the hash value recalculated for verification and the hashed value registered in the confirmation data, it is possible to determine which item of the management data has been tampered with.

[0083] Furthermore, in the first embodiment, hashed data is generated by combining the reporter data and the backup and hashing them. Therefore, it is also possible to confirm whether tampering has occurred in the reporter data stored in the reporter database SDB using the hashed data of the backup.

[0084] In addition, in the first embodiment, the content of the process of hashing the backup is changed arbitrarily or periodically. If such a mode change is performed, the tolerance to leakage and speculation is improved. Therefore, it is possible to avoid the situation where the backup and the hashed data are tampered with to match each other, and the tampering detection of the backup using the hashed data cannot function. As a result, the security level of the backup is maintained at a high level.

[0085] In the first embodiment, the data management unit 66 acquires a transmission log that records that transmission data having the same content as the backup has been transmitted to the transmission destination. The data management unit 66 stores the transmission log in the database together with the backup. Therefore, based on the transmission log, it can be proved that the transmission data on the manager ADM side has not been extracted in a form that the supplier SR (transmission side) does not want or does not understand.

[0086] Furthermore, in the first embodiment, when a change is made to the backup, an intention confirmation record recording the content of the change made to the backup is associated with the backup and saved. In this way, by recording the change content on the basis of making the intention confirmation clear, it is possible to distinguish between the deletion of the backup caused by negligence and the deletion of the backup intentionally with malicious intent. In this way, if the history of changes can be tracked, it will be more effective to accumulate data as evidence for monitoring the record maintenance status.

[0087] In the first embodiment, the reporter terminal 50 corresponds to the "information management device", the control circuit 50c corresponds to the "computer", and the data management unit 66 corresponds to the "data storage unit". In addition, the reporter database SDB corresponds to the "database", the information recording server 100r corresponds to the "sending destination", and the intention confirmation record corresponds to the "change record".

[0088] (Second Embodiment)

[0089] exist Fig.13In the reporter terminal 50 of the second embodiment of the present disclosure shown in FIG. 1 , it is possible to detect the misappropriation of the history information TRI by the supplier SR. Fig.13 , refer to Figure 1 , Figure 2 as well as Figure 4 , and the details of the operations of the data collection unit 61 and the data generation unit 64 in the reporter processing of the second embodiment are described.

[0090] The data collection unit 61 prepares reporter data including historical main data and historical original data (refer to S31). The historical main data is information recorded on the supplier SR side, and includes product information, batch information, and historical information TRI, etc., similar to the reporter data of the first embodiment. The historical main data is the object of detection of whether it is copied and misappropriated. The historical original data is information attached to the historical main data. The historical original data includes, for example, information indicating the date and time when the historical main data is generated or registered. The content of the historical original data changes according to the timing of creation.

[0091] The data generator 64 acquires the history main body data and the history raw data as the reporter data from the data collector 61. The data generator 64 calculates a first hash value obtained by hashing the pre-processed data not including the history raw data and a second hash value obtained by hashing the pre-processed data including at least the history raw data.

[0092] Specifically, the data generation unit 64 sends the history main body data to the hashing application HAP (see Figure 4 as well as Fig.13 S32) to generate a first hash value. Furthermore, the data generation unit 64 sends the history original data to the hashing application HAP (refer to S32) to generate a second hash value. The data generation unit 64 may also generate a second hash value by sending pre-processed data including both the history main body data and the history original data to the hashing application HAP.

[0093] The data generation unit 64 generates transmission data (see S34) by associating the first hash value, the second hash value, and the additional data with the item identification information UID acquired from the information receiving unit 62. Based on the above, the transmission data including the first hash value and the second hash value is transmitted to the information recording server 100r via the data recorder 59. In addition, the backup including the first hash value and the second hash value is stored in the reporter database SDB as management data.

[0094] In the second embodiment described so far, the confirmation information is also stored in the reporter database SDB together with the backup, so that the same effect as the first embodiment is achieved, and it is possible to confirm that the backup has been changed.

[0095] In addition, in the second embodiment, the reporter data prepared by the data collection unit 61 includes the history main body data recorded on the supplier SR side and the history original data attached to the history main body data. Furthermore, the data management unit 66 generates a first hash value obtained by hashing the history main body data using a hash function and a second hash value obtained by hashing the pre-processing data including at least the history original data using a hash function as information included in the transmission data.

[0096] As described above, if the main body of history data separated from the original history data is hashed to generate the first hash value, when the main body of history data is copied and misappropriated to another project IM, the first hash values ​​associated with a plurality of project identification information UIDs are the same value. Therefore, by monitoring whether the first hash values ​​are different from each other, it is possible to detect the illegal misappropriation of the main body of history data of a malicious supplier SR.

[0097] In addition, since the second hash value based on the historical original data is generated separately from the first hash value and stored in the BC database BDB and the reporter database SDB, it is also possible to verify the tampering of the historical original data. In addition, the process of detecting data misappropriation can be implemented by the information recording server 100r that obtains the sent data, or it can be implemented by the data management unit 66 when the backup is saved.

[0098] (Other Embodiments)

[0099] 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.

[0100] In the first embodiment described above, the process of combining the reporter data and the backup and hashing them may be omitted. For example, in the first variant of the embodiment described above, only the assignment of consecutive file numbers is performed. On the contrary, in the second variant of the embodiment described above, the assignment of file numbers is omitted, and only the process of registering the hashed value of the backup in the confirmation data table is performed.

[0101] The method of the item identification information UID in the above-mentioned embodiment can be appropriately changed. Specifically, the number of digits of the character string, the amount and type of information embedded in the item identification information UID, etc. can be appropriately changed. In addition, a one-dimensional code such as a barcode recording the item identification information UID can be printed on the additional label LB instead of the two-dimensional code CDq. In addition, the item identification information UID can also be recorded as electronic data in a recording medium such as an RFID (radio frequency identifier) ​​or a microchip attached to the item IM.

[0102] In a modified example in which the item identification information UID is recorded in an RFID or microchip, a reader and a writer are connected to the reporter terminal 50 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 to the storage medium.

[0103] The generation of the hash value HV 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).

[0104] In the above-mentioned embodiment, each function provided by the reporter terminal 50 and each server 100r, 100i may be provided by software and hardware executing the software, only by software, only by hardware, or by a combination thereof. When such functions are provided by an electronic circuit as hardware, each function may be provided by a digital circuit including a plurality of logic circuits or an analog circuit.

[0105] 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 other IP cores with dedicated functions.

[0106] The form of the storage medium (non-transitory tangible storage medium) used as each storage unit of the above-mentioned embodiment and storing each program related to the implementation of the information management method of the present disclosure can also 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 a CD and a hard disk drive, etc., which serve as the basis for copying the program to the computer.

[0107] 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.

[0108] (Disclosure of technical ideas)

[0109] 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.

[0110] (Technical Thought 1)

[0111] An information management method is implemented by a computer (50c) and manages information collected by a reporter (SR) under the management of a manager (ADM), wherein:

[0112] In the process executed by at least one processor (51), the following steps are included:

[0113] Sending the transmission data based on the reporter data prepared by the reporter side to the transmission destination (100r) associated with the manager (S36);

[0114] Prepare a backup of the above-mentioned sending data (S38);

[0115] Further preparing confirmation information for confirming that the backup has not been changed (S39); and

[0116] The backup is stored in the reporter's database (SDB) together with the confirmation information (S40).

[0117] (Technical Thought 2)

[0118] According to the information management method described in technical idea 1, a continuous management number is given to the backup stored in the database as the confirmation information.

[0119] (Technical Thought 3)

[0120] According to the information management method described in the technical idea 1 or 2, hashed data is generated as the confirmation information by hashing the backup using a hash function.

[0121] (Technical Thought 4)

[0122] According to the information management method described in technical idea 3, the hashed data is generated by hashing the reporter data and the backup combination.

[0123] (Technical Thought 5)

[0124] The information management method according to technical idea 3 or 4 further includes the following step: changing the content of the process of hashing the backup.

[0125] (Technical Thought 6)

[0126] The information management method according to any one of technical ideas 1 to 5 further comprises the following steps: obtaining a sending log (S37) recording that the sending data having the same content as the backup has been sent to the sending destination,

[0127] In the step of storing the backup, the sending log is stored in the database together with the backup.

[0128] (Technical Thought 7)

[0129] According to the information management method described in any one of technical ideas 1 to 6, the reporter data includes the historical main body data recorded on the reporter side and the historical original data attached to the historical main body data.

[0130] The above-mentioned information management method also includes the following steps: generating a first hash value after hashing the above-mentioned historical main data using a hash function, and a second hash value after hashing the pre-processed data containing at least the above-mentioned historical original data using a hash function, as the information included in the above-mentioned sending data (S32).

[0131] (Technical Thought 8)

[0132] The information management method according to any one of technical ideas 1 to 7 further comprises the following steps: when a change is applied to the backup, a change record recording the content of the change applied to the backup is associated with the backup and stored in the database.

[0133] (Technical Thought 9)

[0134] An information management device is an information management device for managing information acquired by a reporter (SR) under the management of a manager (ADM), comprising:

[0135] A data transmission unit (65) transmits transmission data based on the reporter data prepared by the reporter side to a transmission destination (100r) associated with the manager; and

[0136] The data storage unit (66) prepares a backup of the transmission data, further prepares confirmation information for confirming that the backup has not been changed, and stores the backup together with the confirmation information in the reporter's database (SDB).

Claims

1. An information management method implemented by a computer (50c) and managing information collected by a reporter (SR) under the management of a manager (ADM), wherein: In the process executed by at least one processor (51), the following steps are included: Sending the transmission data based on the reporter data prepared by the reporter side to the transmission destination (100r) associated with the manager (S36); Prepare a backup of the above-mentioned sending data (S38); Further preparing confirmation information for confirming that the backup has not been changed (S39); as well as The backup is stored in the reporter's database (SDB) together with the confirmation information (S40).

2. The information management method according to claim 1, wherein: As the confirmation information, a serial management number is given to the backup stored in the database.

3. The information management method according to claim 1, wherein: As the confirmation information, hashed data is generated by hashing the backup using a hash function.

4. The information management method according to claim 3, wherein: The hashed data is generated by combining the reporter data and the backup and hashing them.

5. The information management method according to claim 3, wherein: It also includes the following steps: The content of the process of hashing the above backup is changed.

6. The information management method according to any one of claims 1 to 5, wherein: It also includes the following steps: Acquire a transmission log recording that the transmission data having the same contents as the backup has been transmitted to the transmission destination (S37), In the step of storing the backup, the sending log is stored in the database together with the backup.

7. The information management method according to any one of claims 1 to 5, wherein: The reporter data includes the main historical data recorded on the reporter side and the original historical data attached to the main historical data. The above information management method further comprises the following steps: A first hash value obtained by hashing the history main body data using a hash function and a second hash value obtained by hashing pre-processed data including at least the history raw data using a hash function are generated as information included in the transmission data (S32).

8. The information management method according to any one of claims 1 to 5, wherein: It also includes the following steps: When a change is made to the backup, a change record recording the content of the change made to the backup is associated with the backup and stored in the database.

9. An information management device for managing information acquired by a reporter (SR) under the management of a manager (ADM), wherein: have: A data transmission unit (65) transmits transmission data based on the reporter data prepared by the reporter side to a transmission destination (100r) associated with the manager; as well as The data storage unit (66) prepares a backup of the transmission data, further prepares confirmation information for confirming that the backup has not been changed, and stores the backup together with the confirmation information in the reporter's database (SDB).

Images