WO2023181883A1 - 情報管理方法、及び情報管理装置 - Google Patents

情報管理方法、及び情報管理装置 Download PDF

Info

Publication number
WO2023181883A1
WO2023181883A1 PCT/JP2023/008328 JP2023008328W WO2023181883A1 WO 2023181883 A1 WO2023181883 A1 WO 2023181883A1 JP 2023008328 W JP2023008328 W JP 2023008328W WO 2023181883 A1 WO2023181883 A1 WO 2023181883A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
hash value
item
identification information
item identification
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2023/008328
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
達哉 岡部
陽彦 並木
貴一 村上
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Denso Corp
Original Assignee
Denso Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Denso Corp filed Critical Denso Corp
Priority to EP23774482.6A priority Critical patent/EP4498305A4/en
Priority to CN202380028667.XA priority patent/CN119137614A/zh
Priority to JP2024509940A priority patent/JP7619523B2/ja
Publication of WO2023181883A1 publication Critical patent/WO2023181883A1/ja
Priority to US18/890,569 priority patent/US20250016001A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/083—Shipping
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/083—Shipping
    • G06Q10/0833—Tracking

Definitions

  • the disclosure in this specification relates to information management technology.
  • Patent Document 1 describes a supply chain management method that acquires transaction records of items from traders forming a supply chain and returns hash values obtained by hashing the acquired transaction records to the traders.
  • the hash value provided to the trader is attached to the item shipped by the trader.
  • the present disclosure aims to provide an information management method and an information management device that can simplify data processing for information management.
  • an information management method that is implemented by a computer and manages information provided from a plurality of reporters forming a supply chain, the method comprising: In the process to be executed, item identification information that is attached to the item shipped by the reporter and identifies the item is issued to the issuing terminal linked to the reporter, and a storage hash is created by hashing the history information related to the item.
  • the information management method includes the steps of acquiring a value together with item identification information, and storing the archived hash value in a database in a state linked to the item identification information.
  • one disclosed aspect is an information management device that manages information provided from a plurality of reporters configuring a supply chain, the information management device including an item identifier attached to an item shipped from the reporter to identify the item.
  • An issuing unit that issues information to the destination terminal linked to the reporter, an acquisition unit that obtains a storage hash value obtained by hashing history information related to the item together with item identification information, and
  • the information management device includes a storage unit that stores stored hash values in a database.
  • a storage hash value obtained by hashing history information related to an item is acquired together with item identification information issued in advance, and stored in a database in a state linked to the item identification information.
  • the information acquired from each reporter can be fixed.
  • data processing for information management can be simplified.
  • FIG. 1 is a diagram showing an overall image of a traceability management system according to a first embodiment of the present disclosure.
  • 1 is a diagram showing a system, terminals, etc. related to traceability management.
  • FIG. 2 is a block diagram showing the electrical configuration of a traceability management system and a supplier terminal.
  • FIG. 3 is a diagram for explaining details of a hashing application. It is a flowchart showing details of application distribution processing performed by an application distribution server. It is a flowchart showing details of application verification processing mainly performed by the hash verification unit of the information management server. 12 is a flowchart showing details of ID issuing processing mainly executed by the issuing unit of the information management server.
  • FIG. 3 is a diagram for explaining details of item identification information and attached labels.
  • FIG. 3 is a flowchart showing details of hash storage processing performed by the information management server. It is a flowchart showing details of ID collaboration processing performed by a manufacturer terminal or a supplier terminal and an information management server. It is a flowchart showing details of ID verification processing performed by a manufacturer terminal, a supplier terminal, an information management server, or the like. It is a flowchart which shows the details of ID output processing performed by a supplier terminal. 12 is a flowchart showing details of history disclosure processing mainly performed by the disclosure processing unit of the information management server.
  • FIG. 7 is a diagram showing an overall image of processing mainly performed by a traceability management system according to a second embodiment of the present disclosure.
  • FIG. 7 is a diagram showing an overall image of processing mainly performed by the traceability management system according to the third embodiment of the present disclosure.
  • 12 is a diagram showing details of an inquiry system included in a traceability management system according to modification 3.
  • the supply chain SC in the first embodiment of the present disclosure shown in FIG. 1 is a connection between traders for delivering industrial products, agricultural products, marine products, etc. to end users US.
  • the supply chain SC is constructed by including a plurality of supplier SRs and finished product manufacturers MF as traders.
  • the final products PD supplied by the supply chain SC may be various articles, such as automobiles, batteries, semiconductors, fresh foods, marine products, foods, flowers, medicines, and chemicals.
  • a supply chain SC for delivering industrial products to end users US
  • material miners, material producers, processors, etc. are included as suppliers SR.
  • Each supplier SR processes raw materials such as virgin materials and recycled materials, or (and) item IM etc. delivered from the previous process supplier SR, and sends it to the next process supplier SR as a separate item IM. Or ship it to the finished product manufacturer MF.
  • the supply chain SC may further include carriers, distributors, etc. related to distribution of the item IM and the final product PD.
  • the end user US who uses the final product PD the secondary user U2 who reuses, rebuilds, recycles and disposes of the final product PD, the recycler RC, etc. are further included in the supply chain SC. good.
  • the supply chain SC is managed by the administrator ADM shown in FIGS. 1 and 2.
  • the administrator ADM may be, for example, an agent entrusted with management duties by the finished product manufacturer MF, or an agent entrusted with management and audit duties by a supervisory authority that has supervisory authority over the category to which the final product PD belongs. It may also be an agency.
  • the administrator ADM operates the traceability management system 100 and manages various information recorded in the supply chain SC.
  • the traceability management system 100 can communicate with the supplier terminal 50, manufacturer terminal 10a, user terminal 10b, etc. through the network NW. If the final product PD (for example, a car, etc.) has a communication function, the traceability management system 100 may also be able to communicate with the final product PD.
  • the traceability management system 100 stores information acquired through the network NW in a state that cannot be tampered with in practice. In addition, the traceability management system 100 collects information under the control of individual supplier SRs, etc. in response to requests from the administrator ADM (or regulatory agency), end user US, finished product manufacturer MF, etc. to be disclosed.
  • the supplier terminal 50 is an information processing device operated by the supplier SR.
  • the supplier terminal 50 is linked to each supplier SR.
  • the supplier terminal 50 accumulates history information TRI related to the item IM.
  • the history information TRI is information such as what kind of trading company (previous process supplier SR) the raw materials or parts are purchased from, and when they were acquired. Furthermore, information related to cost, the amount of greenhouse gas emissions (carbon footprint) emitted by manufacturing the item IM, etc. may be recorded as history information TRI.
  • the history information TRI is stored at the supplier terminal 50 and disclosed externally depending on the situation. For example, if a problem occurs or is likely to occur in the item IM or the final product PD, the history information TRI will be sent to other traders through the administrator ADM through the information disclosure process (see Figure 13) described below. Or provided to the end user US, etc. The provided history information TRI is used for investigating the cause of a malfunction, etc. As described above, at least part of the history information TRI becomes information for realizing traceability of the item IM.
  • 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 identification that does not overlap with each other (see FIG. 8). Item identification information UID may be issued, for example, not only for parts but also for recycled materials.
  • the item identification information UID is attached to the item IM shipped from the supplier SR, and delivered together with the item IM to the next process transaction partner.
  • the supplier terminal 50 associates a hash value generated from the history information TRI (hereinafter referred to as a stored hash value HVs) with the issued item identification information UID, and uploads it to the traceability management system 100.
  • a hash value generated from the history information TRI hereinafter referred to as a stored hash value HVs
  • the manufacturer terminal 10a is an information processing device operated by a finished product manufacturer MF.
  • the manufacturer terminal 10a collects information that links the final product PD shipped from the finished product manufacturer MF and one or more items IM used in the final product PD. generate.
  • ID link information LI that links the item identification information UID attached to the item IM and the product identification information PID that identifies the final product PD manufactured using the item IM is used as linking information. generated.
  • the final product PD becomes a related entity related to the item 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.
  • the ID cooperation process is also carried out at the supplier terminal 50 in the same way as at the manufacturer terminal 10a.
  • the supplier terminal 50 generates ID link information LI that links the item identification information UID of the received item IM or recycled material with the item identification information UID of the item IM to be shipped.
  • the supplier terminal 50 uploads the generated one or more ID link information LI to the traceability management system 100.
  • the user terminal 10b is an information processing device operated by the secondary user U2 or the recycling company RC.
  • a smartphone, a tablet terminal, or the like can be used as the user terminal 10b.
  • the user terminal 10b uploads the change information XI to the traceability management system 100.
  • the traceability management system 100 is notified of change information XI indicating the disappearance of the item IM. .
  • the ID link information LI Change information XI requesting modification or transfer is notified.
  • the traceability management system 100 Change information XI is notified.
  • the final product PD collects operational information OI as it is used by the end user US.
  • operational information OI As an example, when the final product PD is an electric vehicle, the mileage, charging/discharging history, current value of battery capacity (State of Health, SOH), etc. are collected as operating information OI.
  • the final product PD links its own product identification information PID to the collected operating information OI and uploads it to the traceability management system 100. Note that at least one of collecting and uploading the operating information OI may be performed by the user terminal 10b owned by the end user US.
  • the traceability management system 100 includes an application distribution server 100a and an information management server 100s.
  • the application distribution server 100a and the information management server 100s are information processing devices mainly including a control circuit 100c.
  • the control circuit 100c includes a processor 11, a RAM (Random Access Memory) 12, a storage unit 13, an input/output interface 14, a bus connecting these, and the like, and functions as a computer that performs arithmetic processing.
  • the processor 11 is hardware for arithmetic processing coupled with the RAM 12 and executes a program stored in the storage unit 13.
  • the application distribution server 100a functions as a server device that distributes the hashed application HAP.
  • the hashing application HAP is an application program installed on each supplier terminal 50.
  • the hashing application HAP performs a hashing process in each supplier terminal 50 to hash the unprocessed data including at least the history information TRI based on the rules specified by the administrator ADM, and generates a stored hash value HVs.
  • the unprocessed data is the original data before hashing processing is performed.
  • the hashing application HAP enables maintenance of security in traceability management through regular updates.
  • the application distribution server 100a provides the latest hashed application HAP to each supplier terminal 50 by implementing application distribution processing (see FIG. 5) in the control circuit 100c based on the application distribution program.
  • the application distribution server 100a determines whether there is an update trigger in the application distribution process (S101). For example, the version information and expiration date of the hashing application HAP can be used as an update trigger. Based on the version information of the hashing application HAP, the application distribution server 100a enables the update trigger when the version of the hashing application HAP specified by the administrator ADM is updated (see FIG. 4) (S101: YES). . Furthermore, the update trigger may be activated when a supplier terminal 50 using an old version of the hashing application HAP that is no longer usable is identified based on the expiration date of the hashing application HAP. . Based on the activation of the update trigger, the application distribution server 100a transmits a notification requesting an update of the application to the supplier terminal 50 to be updated (S102).
  • the application distribution server 100a 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 elapses or a specified number of errors occur, resulting in a timeout (S104: YES).
  • the application distribution server 100a receives the update implementation notification from the supplier terminal 50 that has received the update request notification (S103: YES)
  • the application distribution server 100a provides the program data of the latest hashed application HAP to the supplier terminal 50 (S105, FIG. (see also dashed arrow).
  • the version confirmation of the hashing application HAP is not limited to being performed starting from the administrator ADM side, but may be performed starting from the supplier SR side (supplier terminal 50).
  • the supplier terminal 50 inquires of the application distribution server 100a or the information management server 100s about the validity of the hashed application HAP that it has.
  • the supplier terminal 50 When receiving an inquiry result indicating that the hashing application HAP is valid, the supplier terminal 50 generates and uploads a hash value, which will be described later.
  • the supplier terminal 50 requests the application distribution server 100a to provide the latest hashing application HAP, and updates to the latest hashing application HAP. Implement.
  • the hashing application HAP may be distributed, for example, by a platformer of an operating system that operates the supplier terminal 50.
  • the latest hashing application HAP is provided from the administrator ADM to the platformer, and distributed to each supplier terminal 50 from a server device operated by the platformer.
  • the information management server 100s functions as an information management device that manages information related to item 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 according to the present disclosure.
  • the information management server 100s has functional units such as a hash verification unit 31, an issuance unit 32, an acquisition unit 33, and a storage unit 34 by executing an information management program by the processor 11 (see FIG. 3).
  • the hash verification unit 31 verifies the validity of the stored hash value HVs obtained from the supplier terminal 50. Specifically, by implementing the application verification process (see FIG. 6), the hash verification unit 31 determines whether the stored hash value HVs was generated by the hashing application HAP specified by the administrator ADM, and whether the stored hash value HVs is Check whether it has been generated correctly (see the solid line arrow in Figure 4).
  • the hash verification unit 31 can perform application verification processing at any timing. Specifically, when the hashing application HAP is updated on the supplier terminal 50, after the item identification information UID is issued, after the stored hash value HVs is received, and when a predetermined period of time has passed since the previous verification. For example, application verification processing may be performed.
  • the hash verification unit 31 provides verification data Dd to the supplier terminal 50 by transmission (S11).
  • the verification data Dd is dummy data that is input to the hashing application HAP at the supplier terminal 50 instead of the history information TRI.
  • the hash verification unit 31 receives a hash value (hereinafter referred to as verification hash value HVd) generated by hash processing using the verification data Dd in the hashing application HAP by receiving it from the supplier terminal 50 (S12). (See also 4).
  • the hash verification unit 31 acquires the verification hash value HVd as well as additional information AI (see FIG. 4).
  • the supplementary information AI includes at least a character string indicating the provider of the hashing application HAP and the version of the hashing application HAP.
  • the hash verification unit 31 After transmitting the verification data Dd, the hash verification unit 31 waits for a reply of the verification hash value HVd until a predetermined waiting time has elapsed.
  • the hash verification unit 31 times out (S13: YES) due to the elapse of a predetermined waiting time, the hash verification unit 31 makes an NG determination to the effect that the validity of the stored hash value HVs cannot be guaranteed (S18).
  • the hash verification unit 31 determines whether or not an appropriate hashing application HAP is running on the supplier terminal 50 based on the supplementary information AI. (S14; see also FIG. 4). For example, if an inappropriate hashing application HAP, such as an application of unknown origin or an old version that is no longer usable, is used on the supplier terminal 50 (S14: NO), the hash verification unit 31 makes an NG determination. Execute (S18).
  • the hash verification unit 31 determines that an appropriate hashing application HAP is being used in the supplier terminal 50 (S14: YES)
  • the hash verification unit 31 calculates a hash value for comparison (S15, also see FIG. 4).
  • the hash value for comparison is a value calculated when the verification data Dd is input into the hashing application HAP of the version indicated by the supplementary information AI.
  • the hash verification unit 31 compares the received verification hash value HVd with a hash value for comparison in order to check the normal operation of the hashing application HAP (S16, also see FIG. 4). If the verification hash value HVd is different from the comparison hash value (S16: NO), the hash verification unit 31 makes an NG determination (S18). On the other hand, if the verification hash value HVd is the same as the hash value for comparison (S16: YES), the hash verification unit 31 determines that the hashing application HAP is operating normally on the supplier terminal 50 and that the stored hash value HVs is the same as the hash value for comparison (S16: YES). It is determined that the state is such that legitimacy can be guaranteed (S17). As described above, the hash verification unit 31 can verify the operation of the hashing application HAP without requesting the supplier terminal 50 to disclose the history information TRI.
  • the issuing unit 32 issues the above-mentioned item identification information UID (see also FIG. 8) to the supplier terminal 50 linked to each supplier SR by implementing the ID issuing process (see FIG. 7).
  • the item identification information UID is, for example, a 32-digit character string.
  • the issuing unit 32 performs ID issuing processing in response to a request from, for example, a supplier SR (supplier terminal 50), and issues the number of item identification information UIDs required by the supplier SR.
  • the issuing unit 32 can perform batch processing in which a predetermined number of item identification information UID are issued at once in response to a request from the supplier terminal 50.
  • the issuing unit 32 grasps information (hereinafter, application ID, see FIG. 8) that identifies the application (traceability management system 100) that performs information management (S21). Furthermore, the issuing unit 32 grasps the issue date and time of the item identification information UID and the number of item identification information UIDs to be issued at one time (hereinafter referred to as the number of issues) (S22).
  • the application ID is a value that does not change each time the item identification information UID is issued, and is a fixed character string set in advance.
  • the application ID is information that identifies the issuer (administrator ADM), purpose, field of use, etc. of the item identification information UID.
  • the application ID may be changed for each issuer (supplier SR). In this case, the application ID can also be used as information for identifying the issuer of the item identification information UID.
  • the issue date and time and the number of issues are values that change each time the item identification information UID is issued; in other words, they become variable information VI (see FIG. 8) that changes for each item IM.
  • the randomness of the item identification information UID may be increased by using such variation information VI.
  • the issuing unit 32 generates a hash value (hereinafter, identification hash value HVi, see FIG. 8) by hashing the original data including at least the application ID and the variation information VI (S23). Further, the issuing unit 32 sets the code version, pattern flag, and activation deadline of the item identification information UID (S24).
  • the code version, pattern flag, and activation deadline are characteristic information CI (see FIG. 8) that indicates the characteristics of item identification information UID.
  • the code version is, for example, an identifier indicating the version of the item identification information UID.
  • the pattern flag is an identifier that specifies the scrambling rule used to generate the item identification information UID. By using the pattern flag, it is possible to understand the scrambling rules and perform decoding to descramble without accessing the information management server 100s.
  • the activation deadline is information indicating the end of the period in which the item identification information UID can be effectively used in the traceability management system 100. Item identification information UID whose activation period has passed cannot be handled by the information management server 100s and the hashing application HAP.
  • the issuing unit 32 generates item identification information UID using the application ID, variation information VI, identification hash value HVi, and characteristic information CI (S25). Specifically, the issuing unit 32 converts the original data including the application ID and the variation information VI and the identification hash value HVi into a fixed-length character string based on the scrambling rule corresponding to the pattern flag. This scrambling process generates a disordered character string that is different from before conversion, without damaging the original content. Therefore, the application ID, the variation information VI, and the identification hash value HVi are embedded in the item identification information UID in a restorable (combined) state.
  • the issuing unit 32 mixes the code version, pattern flag, and activation deadline into a predefined position (for example, at the beginning) of the item identification information UID (character string). Further, the issuing unit 32 mixes variable information VI such as the issuing time and the number of issues into a predefined position (for example, the end portion) of the item identification information UID (character string). The issuing unit 32 transmits the generated item identification information UID to the supplier terminal 50 that is the issuing request source (S26). After the issuing unit 32 issues the item identification information UID, the hash verification unit 31 may perform application verification processing (see FIG. 6).
  • the acquisition unit 33 acquires information transmitted from the supplier terminal 50.
  • the storage unit 34 stores the information acquired by the acquisition unit 33 in a blockchain database (hereinafter, BC database, see also FIG. 16) BDB.
  • BC database BDB uses blockchain BC technology to store data to be stored, such as storage hash values HVs, supplementary information AI, and ID link information LI, in a state that cannot be substantially tampered with.
  • the BC database BDB stores the acquired storage target data as a transaction in a block of the private blockchain BC.
  • the BC database BDB makes it difficult to tamper with the data stored in each block by hashing information stored in one block and storing it in the next block.
  • the BC database BDB stores hash values generated from data to be stored in blocks of a consortium type or public blockchain BC, making it virtually impossible to tamper with the data to be stored. good.
  • a server for storing blockchain BC hereinafter referred to as a BC server
  • a database server for storing other data to be stored may be separately provided. Furthermore, only the server that stores blockchain BC may be operated.
  • the acquisition unit 33 and storage unit 34 store the stored hash value HVs etc. acquired from the supplier terminal 50 in the BC database BDB by performing hash storage processing (see FIG. 9).
  • the acquisition unit 33 acquires the stored hash value HVs, the supplementary information AI, etc. together with the item identification information UID by receiving it from the supplier terminal 50 (S31).
  • the acquisition unit 33 refers to the result of the latest application verification process (see FIG. 6) and determines whether the hashing application HAP is operating normally on the supplier terminal 50. A judgment is made (S32).
  • the storage unit 34 sends an error notification to the supplier terminal 50 (S38), and the storage hash value HVs cannot be stored. to notify you of this.
  • the most recent application verification process has determined normality (S32: YES)
  • the application verification process see FIG. 6
  • an error notification is sent to the supplier terminal 50 (S38).
  • the hash verification unit 31 If normality is determined in the application verification process again (S34: YES), that is, if the verification hash value HVd is a correct value, the hash verification unit 31 also stores the stored hash value HVs acquired this time. It is determined that the value is correct (S35). Note that the application verification process (S34) after receiving the stored hash value HVs may be omitted.
  • the storage unit 34 stores the stored hash value HVs and the accompanying information AI, etc. in the BC database BDB in a state linked to the item identification information UID. It is stored (S36). In addition, the storage unit 34 also stores an issuance history indicating the issuer (supplier SR) of the item identification information UID in the BC database BDB in a state linked to the item identification information UID. The storage unit 34 transmits a storage completion notification to the supplier terminal 50, which notifies the completion of storage of the storage hash value HVs, etc. (S37).
  • the supplier terminal 50 has a configuration mainly including a control circuit 50c.
  • the control circuit 50c includes a processor 51, a RAM 52, a storage unit 53, an input/output interface 54, a bus connecting these, and the like, and functions as a computer that performs arithmetic processing.
  • the processor 51 is hardware for arithmetic processing coupled with the RAM 52, and executes an application program (hashing application HAP) stored in the storage unit 53.
  • a display 56, a scanner 58, a printer 59, etc. are electrically connected to the input/output interface 54. Further, an input device such as a keyboard may be connected to the supplier terminal 50, for example, for error handling.
  • the display 56 is a display device mainly including a liquid crystal panel or an organic EL panel.
  • the display 56 displays various images on the screen based on display control by the control circuit 50c.
  • the display 56 displays an image presenting history information TRI based on the data for provision, an image notifying error information received from the information management server 100s, and the like.
  • the display 56 may have a touch panel function that accepts user operations.
  • the scanner 58 is a reading device that reads the attached label LB (see FIG. 8).
  • the scanner 58 includes, for example, an area sensor formed by a two-dimensional array of CCD elements.
  • the attached label LB is a paper medium or a film medium on which a two-dimensional code CDq, a readable code CDs, etc. are printed.
  • the two-dimensional code CDq is, for example, a QR code (registered trademark).
  • Item identification information UID is recorded in the two-dimensional code CDq.
  • the readable code CDs is a character string of a predetermined length, and is a character string corresponding to a part of the item identification information UID.
  • the last seven digits of the item identification information UID are used as a readable code CDs, and written on the attached 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 attached label LB, and outputs the item identification information UID extracted from the two-dimensional code CDq to the control circuit 50c.
  • the two-dimensional code CDq and the readable code CDs may be displayed on a display device such as a display or electronic paper. In this case, a display device such as a display and electronic paper corresponds to the attached label LB.
  • the printer 59 is an output device that outputs the attached label LB.
  • the printer 59 acquires data of a two-dimensional code CDq and a readable code CDs generated from the new item identification information UID provided by the information management server 100s from the control circuit 50c.
  • the printer 59 prints the two-dimensional code CDq and the readable code CDs on a paper medium (such as a sticker) and outputs it as an attached label LB.
  • the attached label LB is attached to the outer surface of the item IM, for example, and distributed together with the item IM.
  • the location where the attached label LB is attached is not limited to the item itself, but may be on a package, a tag, a wrapping, a certificate, or the like.
  • an attached label LB printed and issued in advance by the administrator ADM and supplied to the supplier SR may be distributed together with the item IM.
  • the two-dimensional code CDq may be laser engraved or printed directly on the item IM.
  • a laser marker, an inkjet printer, or the like can be used as the output device.
  • a one-dimensional code such as a barcode recording the item identification information UID may be printed on the attached label LB.
  • 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.
  • the readable code CDs is printed on the outer surface of the recording medium or on a label containing the recording medium so that it can be read by the user.
  • the supplier terminal 50 includes a reader and a writer as a reading device and an output device.
  • the reader reads item identification information UID recorded as electronic data on the storage medium and outputs it to the control circuit 50c.
  • the writer writes electronic data of the item identification information UID generated by the control circuit 50c onto the storage medium.
  • the supplier terminal 50 has functional units such as an ID acquisition unit 61, an information reception unit 62, a history understanding 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 performs ID cooperation processing (see FIG. 10), ID verification processing (see FIG. 11), and ID output processing (see FIG. 12) through cooperation between each functional unit.
  • ID cooperation processing see FIG. 10
  • ID verification processing see FIG. 11
  • ID output processing see FIG. 12
  • the ID collaboration process is also performed by the manufacturer terminal 10a of the finished product manufacturer MF to which the item IM has been delivered. That is, functional units corresponding to the ID acquisition unit 61, information reception unit 62, and information transmission unit 65 are also implemented in the manufacturer terminal 10a.
  • the ID acquisition unit 61 is connected to the scanner 58. In the ID cooperation process (see FIG. 10), the ID acquisition unit 61 acquires data of item identification information UID from the scanner 58 that has read the attached label LB of the item IM delivered to the supplier SR (S41). The ID acquisition unit 61 checks whether the acquired item identification information UID is legitimate information by ID verification processing (S42).
  • the ID acquisition unit 61 reads characteristic information CI (see FIG. 8) from the character string of the item identification information UID (S61). Specifically, the ID acquisition unit 61 acquires the code version, pattern flag, and activation deadline of the item identification information UID. The ID acquisition unit 61 determines whether the item identification information UID is an ID within a valid period based on the activation period (S62).
  • the ID acquisition unit 61 determines that the item identification information UID has expired (S62: YES), it determines that the item identification information UID is an invalid ID (S68). In this case, a notification indicating that the item identification information UID is invalid (hereinafter referred to as ID invalidation notification) is displayed on the display 56. The last seven digits of the invalid item identification information UID are displayed on the display 56 together with the ID invalidation notification. Thereby, the user (worker) can identify the item IM to which the invalid item identification information UID is attached by finding the attached label LB that includes the 7-digit character string and the same readable code CDs.
  • the ID acquisition unit 61 determines that the item identification information UID is a valid ID (S62: NO), it decodes the scrambled item identification information UID based on the code version and pattern flag information. By decoding the item identification information UID, the ID acquisition unit 61 reads information such as the application ID (S63 and S64).
  • the ID acquisition unit 61 calculates a comparison hash value to be compared with the identification hash value HVi using the application ID, issue date and time, and number of issues (S65).
  • the hash value for comparison is calculated by the same calculation method as the generation process of the identification hash value HVi in the issuing unit 32.
  • the ID acquisition unit 61 compares the read identification hash value HVi with a hash value for comparison (S66). If 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. let On the other hand, if the identification hash value HVi is the same as the comparison hash value (S66: YES), the ID acquisition unit 61 determines that the item identification information UID is a regular ID (S67).
  • a detailed determination function for determining whether the item identification information UID is valid or invalid may be provided by the traceability management system 100.
  • the supplier terminal 50 refers to the determination result notified from the traceability management system 100 and determines whether the item identification information UID is a regular ID.
  • the above ID verification process may be implemented by the manufacturer terminal 10a.
  • the manufacturer terminal 10a performs ID verification processing at the timing of acquiring the item identification information UID of the item IM delivered to the finished product manufacturer MF, and determines whether the item identification information UID of the item IM is a regular ID. do.
  • the information receiving unit 62 requests the issuing unit 32 to issue item identification information UID to be attached to the item IM shipped from the supplier SR.
  • the information receiving unit 62 acquires the item identification information UID issued by the issuing unit 32 by receiving it from the information management server 100s in the ID cooperation process (see FIG. 10) (S43).
  • the information receiving unit 62 generates ID link information LI that links the received new item identification information UID to the item identification information UID acquired from the received item IM (S44).
  • the information receiving unit 62 receives verification data Dd (see FIG. 4) from the hash verification unit 31 that performs application verification processing (see FIG. 6). Note that when the ID collaboration process is performed at the manufacturer terminal 10a, the product identification information PID is acquired as another ID to be linked to the item identification information UID (S43).
  • the history grasping unit 63 acquires the history information TRI generated by the supplier SR.
  • the history grasping unit 63 may automatically acquire data serving as the history information TRI from another server device installed at the base of the supplier SR, or may acquire 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 where it is linked to the item identification information UID acquired by the ID acquisition unit 61.
  • the information stored in the supplier database SDB is only the history information TRI, in other words, only the original data of the information to be hashed. Information that is not stored in the supplier database SDB may be deleted after confirming the intention of deletion each time.
  • the history grasping unit 63 selects a specified item identification from the history information TRI accumulated in the supplier database SDB based on a request from the information management server 100s that implements a history disclosure process (see FIG. 13) to be described later. Extract the information linked to the information UID.
  • the hash generating unit 64 prepares the unprocessed data so as to include the history information TRI grasped by the history grasping unit 63.
  • the hash generation unit 64 hashes the unprocessed data and generates a storage hash value HVs.
  • the hash generation unit 64 prepares unprocessed data that includes the verification data Dd instead of the history information TRI.
  • the hash generation unit 64 generates a verification hash value HVd (see FIG. 4) by hashing the unprocessed data including the verification data Dd.
  • the hash generation unit 64 further generates supplementary information AI (see FIG. 4) that includes version information of the hashing application HAP that hashed the hashing process.
  • the information transmitting unit 65 sequentially transmits the storage hash value HVs, the verification hash value HVd, and the supplementary information AI generated by the hash generating unit 64 to the acquiring unit 33.
  • the information transmitting unit 65 transmits the ID link information LI and each ID linked by the ID link information LI to the acquiring unit 33 in the ID linking process (see FIG. 10). S45).
  • Each ID and ID link information LI are acquired by the acquisition unit 33 (S51), and stored in the BC database BDB by the storage unit 34 (S52). Then, a notification indicating the completion of storage of the ID link information LI is provided from the storage unit 34 to the information receiving unit 62 (S53 and S46).
  • the ID output unit 66 is connected to the printer 59.
  • the ID output unit 66 causes the printer 59 to output the attached label LB by performing ID output processing (see FIG. 12).
  • the ID output section 66 acquires data of the item identification information UID received by the information reception section 62 (S71).
  • the ID output unit 66 generates a two-dimensional code CDq (see FIG. 8) recording the item identification information UID and a readable code CDs (see FIG. 8) obtained by cutting out a part of the item identification information UID (S72 and S73). ).
  • the ID output unit 66 outputs print data including the two-dimensional code CDq and readable code CDs to the printer 59 (S74), and causes the printer 59 to print the attached label LB.
  • the ID output unit 66 and the printer 59 do not need to be provided in the supplier terminal 50. In this case, ID output processing at the supplier terminal 50 is also omitted.
  • the information management server 100s also functions as an information providing device that provides information related to item IM.
  • the storage unit 13 of the information management server 100s further stores an information providing program for causing the control circuit 100c to implement the information providing method according to the present disclosure.
  • the information management server 100s further includes a disclosure processing unit 35 as a functional unit, which is caused by the processor 11 executing the information providing program.
  • the disclosure processing unit 35 enables the provision of history information TRI by implementing history disclosure processing (see FIG. 13).
  • the disclosure processing unit 35 receives a request for disclosure of history information TRI from the manufacturer terminal 10a, the user terminal 10b, etc. (S131).
  • Product identification information PID or item identification information UID is attached to the disclosure request as information specifying the final product PD or item IM that is the subject of the request.
  • the disclosure processing unit 35 refers to the BC database BDB, extracts ID link information LI related to the designated product identification information PID or item identification information UID, and extracts at least one item identification information LI that is a target for collecting history information TRI.
  • a UID is set (S132).
  • the disclosure processing unit 35 refers to the issuance history of the BC database BDB and identifies the supplier SR that requests provision of the history information TRI.
  • the disclosure processing unit 35 transmits a request for providing history information TRI along with item identification information UID to the supplier terminal 50 of the specified supplier SR (S133).
  • the disclosure processing unit 35 acquires the history information TRI returned from the supplier terminal 50 based on the provision request (S134).
  • the disclosure processing unit 35 grasps the version information of the hashing application HAP used for the hashing process of the acquired history information TRI (S135).
  • the version information may be extracted from the BC database BDB or may be received from the supplier terminal 50 together with the history information TRI.
  • the disclosure processing unit 35 performs hashing processing on the acquired history information TRI by the same hashing processing as the hashing application HAP indicated by the version information, and calculates a hash value for comparison (S136).
  • the disclosure processing unit 35 extracts the stored hash value HVs associated with the item identification information UID from the BC database BDB (S137), and compares the stored hash value HVs with the recalculated hash value for comparison (S138). If the hash value for comparison is different from the stored hash value HVs (S138: NO), an error notification indicating that the history information TRI may have been tampered with is sent to the requester of the disclosure request, the requestee of information provision, etc. S140). On the other hand, if the hash value for comparison is the same as the stored hash value HVs (S138: YES), the disclosure processing unit 35 estimates that the history information TRI has not been tampered with.
  • the disclosure processing unit 35 repeats the processes of S133 to S138. When the disclosure processing unit 35 completes the verification of all the historical information TRI, it provides the collected historical information TRI to the requester of the disclosure request (S139).
  • the storage hash value HVs obtained by hashing the history information TRI related to the item IM is acquired together with the item identification information UID issued in advance. Then, the storage hash value HVs is stored in the BC database BDB in a state where it is linked to the item identification information UID. In this way, according to the process of hashing the history information TRI and then transmitting it, the information acquired from each supplier SR, specifically, the capacity, data length, etc., can be fixed. As a result, data processing for information management can be simplified.
  • the history information TRI recorded in each supplier SR has different types, formats, capacities, etc. of recorded files for each supplier SR.
  • the management items, granularity, etc. recorded as history information TRI may also change from time to time or over time.
  • the number and order of processing steps for processing the item IM, etc. will also change over time. It is also assumed that there may be a need to construct the traceability management system 100 at a stage when the recording method of the historical information TRI has not been determined in each supplier SR.
  • the information management server 100s stores a fixed-length hash value, regardless of the form of the history information TRI for each supplier SR. Can handle formatted data. According to the above, even if the management items, granularity, etc. of the history information TRI change in the supplier SR, there is no need to change the processing content performed by the information management server 100s. Furthermore, the traceability management system 100 can be constructed even at the stage where the recording method of the history information TRI is not determined in the supplier SR.
  • the historical information TRI is kept secret from the outside of the supplier SR.
  • a disclosure request is made only to the relevant supplier SR, and history information TRI necessary for responding to the incident is collected in the information management server 100s.
  • it can be easily and clearly verified that there is no difference in the collected history information TRI from the time of registration. Therefore, a highly convenient information management method can be provided to each transactor.
  • verification data Dd for verifying the stored hash value HVs is provided to the supplier terminal 50.
  • the hash verification unit 31 obtains a verification hash value HVd generated by hashing processing using the verification data Dd. If 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.
  • the information management server 100s does not request the supplier terminal 50 to disclose the history information TRI, and the generation of the stored hash value HVs by the hashing application HAP is operating correctly on the supplier terminal 50. You can verify that. Therefore, even if data processing for information management is simplified, the validity of the data stored in the information management server 100s can be ensured.
  • a hashing application HAP that performs hashing processing is provided to the supplier terminal 50.
  • the hashing application HAP can be updated at any timing of the administrator ADM. According to the above, since security is easily maintained, the risk of tampering with historical information TRI can be further reduced.
  • information indicating the version of the hashing application HAP that hashed on the supplier terminal 50 is included in the supplementary information AI transmitted to the information management server 100s. Therefore, even if the contents of the hashing process are changed for each version, the information management server 100s can correctly prepare hash values for comparison to verify the stored hash values HVs and the like. According to the above, it becomes easier to maintain security and simplify data processing.
  • the variation information VI that changes for each item IM and the identification hash value HVi obtained by hashing the original data including the variation information VI are embedded in the item identification information UID. Therefore, duplication of item identification information UID can be easily avoided. In addition, the validity of the item identification information UID can be easily and reliably determined in each terminal under the management of the traceability management system 100.
  • characteristic information CI such as a code version and a pattern flag is embedded in the item identification information UID.
  • This characteristic information CI is excluded from the original data to be hashed and scrambled. Therefore, each terminal etc. that has acquired the item identification information UID can extract the identification hash value HVi, the variation information VI, etc. from the item identification information UID based on the contents of the characteristic information CI. According to the above, each terminal can more reliably identify that the item identification information UID is a regular ID issued by the administrator ADM.
  • a readable code CDs corresponding to a part of the item identification information UID is written on the attached label LB attached to the item IM. If these readable codes CDs are displayed on the attached label LB, even if one of the multiple item identification information UIDs causes an error, the user can visually identify the attached label LB that is the target of the error. can. As a result, the convenience of information management can be further improved.
  • the stored hash values HVs and the like are stored in a BC database BDB that uses blockchain BC technology. According to the above, the possibility of tampering with the stored hash value HVs is further reduced. As a result, the correctness of the history information TRI disclosed in the disclosure request can be more reliably guaranteed.
  • the information management server 100s receives ID link information LI that links the item identification information UID attached to the item IM and the product identification information PID from the finished product manufacturer MF to which the item IM is delivered. get.
  • the ID link information LI is stored in the BC database BDB. According to such accumulation of ID link information LI, the connection of items IM from raw materials to final products PD can be reliably recorded in the BC database BDB. Therefore, by referring to the ID link information LI, the information management server 100s can identify all requests for disclosure of history information TRI. As a result, highly accurate information disclosure becomes possible.
  • the storage hash value HVs generated from the history information TRI is not recorded in the two-dimensional code CDq.
  • the storage hash value HVs and the item identification information UID only the item identification information UID is recorded in the two-dimensional code CDq. Therefore, the amount of data recorded on the two-dimensional code CDq can be reduced. As a result, the size of the two-dimensional code CDq can be reduced.
  • the item identification information UID of the first embodiment records an application ID, an activation deadline, and the like. According to such information, it is possible to easily identify the application used for information management, confirm the expiration of the item identification information UID, etc. As a result, the convenience of information management can be further improved.
  • the manufacturer terminal 10a corresponds to a "supplier terminal”
  • the supplier terminal 50 corresponds to a "destination terminal”
  • the control circuit 100c corresponds to a "computer”
  • the information management server 100s corresponds to a "destination terminal.” corresponds to "information management device”.
  • the BC database BDB corresponds to a "database”
  • the readable code CDs corresponds to a "character string”
  • the hashing application HAP corresponds to an "application”
  • the attached label LB corresponds to an "attached medium”
  • the ID The link information LI corresponds to "linking information”.
  • the supplier SR corresponds to the "reporter”
  • the finished product manufacturer MF corresponds to the "deliverer”
  • the final product PD corresponds to "related items”
  • the product identification information PID corresponds to "related identification information.”
  • the supplier SR of the next process corresponds to a "supplier”
  • the supplier terminal 50 of the next process corresponds to a "supplier terminal”
  • another item IM corresponds to a "related item”
  • another item IM corresponds to a "related item”.
  • the identification information UID may correspond to "related identification information.”
  • the second embodiment of the present disclosure shown in FIG. 14 is a modification of the first embodiment.
  • a general-purpose hash function (hereinafter referred to as general-purpose hash function HF) is used for the hashing process instead of the hashing application HAP (see FIG. 4).
  • the general-purpose hash function HF calculates the storage hash value HVs and the verification hash value HVd at the supplier terminal 50, similarly to the hashing application HAP.
  • the general-purpose hash function HF may be prepared by the supplier SR, or may be specified by the administrator ADM (information management server 100s).
  • the supplier terminal 50 transmits a notification indicating the general-purpose hash function HF to be used to the information management server 100s.
  • the general-purpose hash function HF instead of the hashing application HAP, the transparency of data processing improves from the perspective of the reporter, such as the supplier SR.
  • the application distribution server 100a performs an application distribution process of providing the data generation application LAP to the middle-tier terminal 250 instead of the application distribution process of providing the hashed application HAP to the supplier terminal 50 (see FIG. 5).
  • the application distribution server 100a provides the program data of the latest data generation application LAP to the intermediate layer terminal 250 based on the occurrence of a predetermined update trigger (see S105 in FIGS. 5 and 14).
  • the middle layer terminal 250 is an information processing device operated by the middle layer ML.
  • the middle layer ML is independent from the administrator ADM and the supplier SR.
  • For the middle layer ML transparency of information from the supplier SR is ensured.
  • the middle tier ML may be prepared by an administrator ADM and may be prepared by one or more suppliers SR. Furthermore, if transparency is ensured and agreement has been reached among the administrator ADM, supplier SR (reporter), supervisory authority (auditor), etc., the middle layer ML will contact the administrator ADM or supplier SR. It may be installed in a part of the environment to which it belongs.
  • the middle layer terminal 250 is also a terminal linked to the supplier SR.
  • the middle layer terminal 250 is communicably connected to the application distribution server 100a, the information management server 100s, the supplier terminal 50, and the like.
  • the middle layer terminal 250 like the supplier terminal 50, has a configuration mainly including a control circuit.
  • the control circuit includes a processor, a RAM, a storage unit, an input/output interface, a bus connecting these, and the like, and functions as a computer that performs arithmetic processing.
  • the middle layer terminal 250 executes the data generation application LAP by a processor.
  • the data generation application LAP performs a process of acquiring the item identification information UID issued by the ID issuing process (see FIG. 7) from the issuing unit 32 (see FIG. 3), and a process of generating transmission data DSS including the item identification information UID.
  • the intermediate layer terminal 250 executes the following.
  • the intermediate layer terminal 250 is capable of storing a predetermined number of item identification information UIDs that are collectively issued through batch processing by the issuing unit 32.
  • the middle layer terminal 250 is connected to a data logger 259.
  • the data logger 259 records a transmission log of transmission data DSS transmitted from the intermediate layer terminal 250.
  • the data logger 259 provides the supplier terminal 50 with a backup of the transmission data DSS transmitted to the information management server 100s, together with the transmission log.
  • the transmission log records information indicating what kind of data was transmitted to which destination.
  • the data logger 259 has a checker function.
  • the data logger 259 checks that the transmitted data DSS transmitted to the information management server 100s (storage unit 34) and the supplier terminal 50 have the same content.
  • the data logger 259 records information indicating that the transmission data DSS transmitted to the storage unit 34 and the supplier terminal 50 have the same content in a transmission log provided to the supplier terminal 50.
  • the hash verification process is a process equivalent to the application verification process (see FIG. 6) of the first embodiment.
  • the hash verification process it is checked whether the general-purpose hash function HF is operating normally.
  • the hash verification process is periodically performed by the hash verification unit 31.
  • the hash verification unit 31 provides verification data Dd to the supplier terminal 50 by transmission (S11).
  • the verification data Dd is sent to the general-purpose hash function HF at the supplier terminal 50.
  • the hash verification unit 31 acquires the verification hash value HVd generated from the verification data Dd from the supplier terminal 50 by hashing processing using the general-purpose hash function HF (S12).
  • the hash verification unit 31 transmits the verification data Dd to the same hash function as the general-purpose hash function HF used in the supplier terminal 50, and calculates a hash value for comparison (S15).
  • the hash verification unit 31 determines whether the general-purpose hash function HF is operating normally in the supplier terminal 50 by comparing the received verification hash value HVd with a hash value for comparison (S16). If the verification hash value HVd is the same as the comparison hash value (S16: YES), the hash verification unit 31 determines that the general-purpose hash function HF is operating normally (S17). In this case, the hash verification unit 31 estimates that the validity of the stored hash value HVs can be guaranteed.
  • the data storage process is carried out by cooperation between the supplier terminal 50, the middle-tier terminal 250, and the information management server 100s.
  • the hash generation unit 64 (see FIG. 3) of the supplier terminal 50 sends the unprocessed data including the history information TRI (see FIG. 1) to the general-purpose hash function HF (S81) to generate a storage hash value HVs.
  • the supplier terminal 50 transmits the stored hash value HVs from the information transmitting unit 65 (see FIG. 3) to the intermediate layer terminal 250 (S82).
  • the intermediate layer terminal 250 receives and acquires the stored hash value HVs transmitted from the supplier terminal 50 (S91).
  • the intermediate 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 to be associated with the stored hash value HVs.
  • the intermediate layer terminal 250 generates supplementary information AI to be added to the stored hash value HVs.
  • the supplementary information AI includes application information related to the data generation application LAP and item information related to the item IM (see FIG. 1).
  • the application information includes information indicating the version of the data generation application LAP in operation, information indicating the application provider, and the like.
  • the item information includes information indicating the type of item IM linked to the stored hash value HVs, information indicating the supplier SR, and the like.
  • the intermediate layer terminal 250 generates transmission data DSS through a process of linking the item identification information UID with the storage hash value HVs and the accompanying information AI (S92).
  • the intermediate layer terminal 250 transmits the transmission data DSS to the storage unit 34 via the data logger 259 (S93).
  • the intermediate layer terminal 250 also provides the supplier terminal 50 with transmission data DSS having the same content as that transmitted to the storage unit 34 .
  • the data logger 259 records a transmission log of the transmission data DSS.
  • the information management server 100s performs the same steps as the hash storage process (see FIG. 9) of the first embodiment in the data storage process. Specifically, the information management server 100s uses the acquisition unit 33 (see FIG. 3) to acquire the transmission data DSS by receiving it from the middle layer ML (S31).
  • the storage unit 34 refers to the verification result in the hash verification process, and if it is determined that the general-purpose hash function HF is operating normally (S32: YES), the storage unit 34 determines that the stored hash value HVs acquired this time is the correct value. It is determined that there is one (S35).
  • the storage unit 34 Based on the validity of the transmission data DSS including the stored hash value HVs, the storage unit 34 stores the stored hash value HVs and the accompanying information AI, etc. in the BC database BDB in a state linked to the item identification information UID. (S36).
  • the supplier terminal 50 prepares to back up the transmission data DSS by receiving the information from the data logger 259 by the information receiving unit 62 (S83).
  • the supplier terminal 50 stores the backup transmission data DSS and transmission log in the supplier database SDB in association with the history information TRI (see FIG. 1) (S84).
  • the second embodiment described so far has the same effect as the first embodiment, and the information sent from the reporter such as the supplier SR to the administrator ADM is made into a fixed length by hashing, so information management is improved. This makes it possible to simplify data processing.
  • item identification information is issued to the middle layer terminal 250 as the destination terminal operated by the middle layer ML.
  • the information management server 100s acquires transmission data DSS in which the intermediate layer terminal 250 has linked the item identification information UID to the storage hash value HVs generated by the supplier SR operated by the supplier SR.
  • the data generation process that links the stored hash value HVs and the item identification information UID is performed in the middle layer ML, there is no need to force the supplier SR to use the hashing application HAP.
  • the transparency of information processing improves, making it possible to lower the psychological hurdles for introducing the traceability management system 100.
  • the supplier terminal 50 is provided with transmission data DSS having the same content as the item identification information UID and stored hash value HVs stored in the BC database BDB.
  • 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, if the administrator ADM extracts the transmitted data DSS (data to be stored), the occurrence of such extraction can be verified using the backup on the supplier SR side. As a result, the administrator ADM and the reporter can share the fact that no unauthorized data extraction has been carried out, thereby further improving the transparency of information processing.
  • the transmission data DSS corresponds to "data to be stored” and "data stored by the reporter”
  • the supplier database SDB corresponds to the "reporter database”.
  • the supplier terminal 50 corresponds to a "reporter terminal”
  • the intermediate layer terminal 250 corresponds to a "destination terminal”.
  • the third embodiment of the present disclosure shown in FIG. 15 is a modification of the second embodiment.
  • the supplier terminal 50 uses the general-purpose hash function HF for hashing processing.
  • the application distribution server 100a, the middle layer ML, and the middle layer terminal 250 are omitted. Therefore, the terminal to which the item identification information UID is issued is the supplier terminal 50, as in the first embodiment.
  • data storage processing including hash verification processing is performed through cooperation between the supplier terminal 50 and the information management server 100s. The details of the data storage process of the third embodiment will be explained below.
  • the supplier terminal 50 requests the information management server 100s to generate verification data Dd (S381).
  • the information management server 100s obtains the request transmitted by the supplier terminal 50 (S311), it determines whether or not to permit the request. If the request is from a legitimate supplier terminal 50 registered in advance, the information management server 100s permits the request (S312) and provides verification data Dd to the supplier terminal 50 (S313).
  • the information management server 100s prepares the same hash function as the general-purpose hash function HF presented in advance from the supplier terminal 50.
  • the information management server 100s also sends the verification data Dd sent to the supplier terminal 50 to the prepared hash function. As a result, a set of hash values for comparison is calculated (S314).
  • the supplier terminal 50 acquires the verification data Dd provided from the information management server 100s (S382). In addition, the supplier terminal 50 transmits unprocessed data including history information TRI (see FIG. 1) to the general-purpose hash function HF (S383). In addition to the stored hash value HVs, the supplier terminal 50 calculates a first verification hash value HVd1 and a second verification hash value HVd2.
  • the first verification hash value HVd1 is a verification hash value HVd generated by a hashing process using the verification data Dd before hashing the unprocessed data.
  • the second verification hash value HVd2 is a verification hash value HVd generated by a hashing process using the verification data Dd before hashing the unprocessed data.
  • the supplier terminal 50 inputs the verification data Dd, unprocessed data, and verification data Dd into a general-purpose hash function HF in this order, and obtains a first verification hash value HVd1, a stored hash value HVs, and a second verification hash value HVd2. calculate. Note that the verification data Dd used to generate the verification hash values HVd1 and HVd2 may have the same content or may have different content.
  • the supplier terminal 50 generates supplementary information AI.
  • the supplier terminal 50 generates transmission data DSS by linking the first verification hash value HVd1, the storage hash value HVs, and the second verification hash value HVd2, together with the accompanying information AI, to the item identification information UID.
  • the stored hash value HVs is sandwiched between the first verification hash value HVd1 and the second verification hash value HVd2.
  • the supplier terminal 50 transmits the transmission data DSS to the information management server 100s (S384).
  • the information management server 100s acquires the transmission data DSS by receiving it from the supplier terminal 50 (S315).
  • the information management server 100s compares the first verification hash value HVd1 and the second verification hash value HVd2 included in the transmission data DSS with a hash value for comparison, and checks whether each verification hash value HVd1, HVd2 is correct. If the verification hash values HVd1 and HVd2 are both the same as the comparison hash value, the information management server 100s determines that the general-purpose hash function HF is operating normally and that the validity of the stored hash value HVs can be guaranteed. It is determined that there is one (S316).
  • the information management server 100s Based on the confirmation of the validity of the stored hash value HVs, the information management server 100s deletes the first verification hash value HVd1 and the second verification hash value HVd2 from the transmission data DSS.
  • the information management server 100s stores storage target data in which the item identification information UID is associated with the accompanying information AI and the storage hash value HVs in the BC database BDB (S317).
  • the third embodiment described so far also has the same effects as the first and second embodiments, and it is possible to simplify data processing for information management. Additionally, in the third embodiment, the first verification hash value HVd1 and the second verification hash value HVd2 are acquired from the supplier terminal 50. Then, when the verification hash values HVd1 and HVd2 surrounding the stored hash value HVs are both correct values, it is determined that the main stored hash value HVs is the correct value. Therefore, even if the general-purpose hash function HF is used at the supplier terminal 50, the validity of the stored hash value HVs can be ensured.
  • the aspect of the item identification information UID in the above embodiment specifically, the number of digits of the character string, the number and type of embedded information, etc. may be changed as appropriate. Furthermore, the identification hash value HVi and the variation information VI do not need to be scrambled. Additionally, the readable code CDs may be omitted. Further, a symbol or the like that can be recognized by the user and is an identifier in place of the readable code CDs may be written on the attached label LB or the like. Further, the product identification information PID may also be issued to the finished product manufacturer MF by the information management server 100s, similarly to the item identification information UID. In these modified examples, the finished product manufacturer MF also corresponds to the "reporter."
  • the storage hash value HVs is also recorded in the two-dimensional code CDq. Further, on the attached label LB of the second modification of the above embodiment, another two-dimensional code is printed with the stored hash value HVs, in a position parallel to the two-dimensional code CDq which records the item identification information UID. . As described above, the stored hash value HVs may also be distributed together with the item IM.
  • a request for information disclosure may be made from the front process side (upstream side) to the post process side (downstream side) of the supply chain SC, or from the downstream side to the upstream side.
  • the request for information disclosure to the upstream side if a problem occurs in the item IM or the final product PD, it becomes possible to trace the historical information TRI of the raw materials or parts used in the item IM or the final product PD.
  • the request for information disclosure to the downstream side when a defect is found in the item IM, it becomes possible to specify the item IM in the subsequent process or the final product PD for which this item IM is specified.
  • the traceability management system 100 of the third modification of the above embodiment is divided into a recording system and an inquiry system 200 shown in FIG. 16.
  • the recording system is mainly configured with the information management server 100s (see FIG. 1) of the above embodiment.
  • the configuration corresponding to the disclosure processing unit 35 is omitted from the information management server 100s of the recording system.
  • the inquiry system 200 is a system corresponding to the disclosure processing unit 35 of the above embodiment, and executes history disclosure processing (see FIG. 13).
  • the inquiry system 200 includes a collection server 200a, a BC database BDB, and the like.
  • the inquiry system 200 may be operated by an organization different from the management organization that manages the record system.
  • the entity responsible for the final product PD may serve as the management organization for the inquiry system 200.
  • the collection server 200a includes a reception section 201, a data comparison section 202, and a data provision section 203.
  • the reception unit 201 receives a request for disclosure of history information TRI from the inquiry terminal 110 of the inquirer IQ who requests provision of history information (S131).
  • the inquiry terminal 110 may be the manufacturer terminal 10a and the user terminal 10b described above.
  • the inquiry terminal 110 may include not only the user terminal 10b operated by the secondary user U2 or the recycling company RC, but also the user terminal 10b (end user terminal) owned by the end user US described above. That is, the inquirer IQ may be any of the finished product manufacturer MF, the secondary user U2, the recycler RC, and the end user US.
  • the inquirer IQ can carry out an initiation request using product identification information PID (for example, vehicle ID, etc.) that identifies the final product PD.
  • product identification information PID for example, vehicle ID, etc.
  • the receiving unit 201 receives the product identification information PID provided from the inquiry terminal 110, and specifies the item identification information UID from which the history information TRI is to be collected from the product identification information PID (S132). Furthermore, the reception unit 201 identifies the stored hash value HVs related to the set item identification information UID.
  • reception function that receives the product identification information PID may be installed in an external processing device different from the collection server 200a.
  • a specific function for identifying the stored hash value HVs from the item identification information UID is installed inside the traceability management system 100 or the inquiry system 200.
  • the BC database BDB Based on the item identification information UID specified by the reception unit 201 etc., the BC database BDB specifies the supplier SR that requests provision of the history information TRI.
  • the BC database BDB transmits a request to provide the history information TRI along with the item identification information UID to the supplier terminal 50 of the specified supplier SR (S133).
  • Each supplier SR becomes a reporter who discloses historical information TRI.
  • the supplier terminal 50 provides data such as history information TRI accumulated in the supplier database SDB to the collection server 200a.
  • the data matching unit 202 acquires data such as history information TRI returned from the supplier terminal 50 (S134).
  • the data matching unit 202 cooperates with the BC database BDB, sequentially identifies upstream supplier SRs in the supply chain SC, and collects history information TRI.
  • the data matching unit 202 performs a verification process (Before-After check) to determine whether the context of the hash values is correctly established, and checks whether the acquired history information TRI has been tampered with (S135). ⁇ S138).
  • the data matching unit 202 delivers the history information TRI that has been confirmed not to have been tampered with to the data providing unit 203.
  • the data providing unit 203 generates data to be provided to the inquirer IQ by editing the verified history information TRI passed from the data matching unit 202.
  • the data providing unit 203 provides the generated provision data to the inquiry terminal 110 of the inquirer IQ who is the requester of the disclosure request (S139).
  • the item identification information UID does not need to be issued to a trader such as a distributor.
  • the terminal linked to the distributor links the history information TRI recorded during the distribution process to the item identification information UID attached to the item IM being transported, and uploads it to the information management server 100s.
  • the history information TRI in the distribution process is also stored in the BC database BDB in a state linked to the item identification information UID, and can be provided to each transaction person.
  • the data logger 259 used in the second embodiment is also applicable to the first and third embodiments. Specifically, the data logger 259 is connected to the supplier terminal 50 and records the item identification information UID, storage hash value HVs, etc. transmitted from the supplier terminal 50. As a result, a backup whose identity with the data acquired by the information management server 100s is guaranteed can be stored in the supplier database SDB together with the history information TRI.
  • the stored hash value HVs is sandwiched between the first verification hash value HVd1 and the second verification hash value HVd2 on both sides.
  • the stored hash value HVs does not need to be sandwiched between verification hash values on both sides.
  • only the first verification hash value HVd1 at the front or only the second verification hash value HVd2 at the rear is attached to the stored hash value HVs.
  • Each function of the application distribution server 100a and the information management server 100s may be provided by one server device. Further, the application distribution server 100a and the information management server 100s may be on-premises server devices physically managed by an administrator ADM or a platformer, or may be virtual configurations provided on the cloud. You can. In addition, the BC database BDB and supplier database SDB may also be constructed in a virtual file server provided on the cloud.
  • hash functions may be used to generate the storage hash value HVs, verification hash value HVd, and identification hash value HVi in the above embodiment.
  • a hash function has the property that it never outputs the same hash value from different inputs, and that it is virtually impossible to infer the input from the output hash values. With these characteristics, encryption algorithms such as SHA-256, SHA-1, SHA-2, and SHA-3 can be used as appropriate depending on the required output length (number of bits). be.
  • the hash functions used to calculate each hash value may be the same or different.
  • each function provided by the traceability management system 100 can be provided by software and hardware that executes it, only software, only hardware, or a complex combination thereof.
  • each function provided by the supplier terminal 50, the manufacturer terminal 10a, the middle layer terminal 250, etc. may also be provided by software and hardware that executes it, only software, only hardware, or a complex combination thereof. Available. If these functions are provided by electronic circuits as hardware, each function can also be provided by digital circuits that include multiple logic circuits, or by analog circuits.
  • Each processor in the above embodiments may include at least one arithmetic core such as a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit). Furthermore, the processor may further include an FPGA (Field-Programmable Gate Array), an IP core with other dedicated functions, and the like.
  • arithmetic core such as a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit).
  • the processor may further include an FPGA (Field-Programmable Gate Array), an IP core with other dedicated functions, and the like.
  • the form of the storage medium (non-transitory tangible storage medium) that is adopted as each storage unit in the above embodiments and stores each program related to realizing the information management method of the present disclosure may be changed as appropriate.
  • the storage medium is not limited to a configuration provided on a circuit board, but may be provided in the form of a memory card or the like, inserted into a slot portion, and electrically connected to a computer bus.
  • the storage medium may be an optical disk, a hard disk drive, or the like used as a source for copying or distributing a program to a computer.
  • control unit and its method described in this disclosure may be implemented by a dedicated computer comprising a processor programmed to perform one or more functions embodied by a computer program.
  • the apparatus and techniques described in this disclosure may be implemented with dedicated hardware logic circuits.
  • the apparatus and techniques described in this disclosure may be implemented by one or more special purpose computers configured by a combination of a processor executing a computer program and one or more hardware logic circuits.
  • the computer program may also be stored as instructions executed by a computer on a computer-readable non-transitory tangible storage medium.
  • (Technical thought 1) An information management method that is implemented by a computer (100c) and manages information provided from a plurality of reporters (SR) constituting a supply chain (SC), the method comprising: The processing executed by at least one processor (11) includes: Issue item identification information (UID) that is attached to the item (IM) shipped from the reporter and identifies the item to the destination terminal (50, 250) linked to the reporter (S21 to S26); Obtaining a stored hash value (HVs) obtained by hashing history information (TRI) related to the item together with the item identification information (S31); storing the stored hash value in a database (BDB) in a state linked to the item identification information (S36); An information management method that includes the steps of (Technical thought 2) providing verification data (Dd) for verifying the stored hash value obtained from the issuing terminal to the issuing terminal (S11, S313); Obtaining a verification hash value (HVd) generated by hashing processing using the verification data from the issuing terminal
  • the item identification information is issued to a middle layer terminal as the issuing destination terminal operated in a middle layer (ML),
  • the intermediate layer terminal links the item identification information to the stored hash value generated by the reporter terminal operated by the reporter; The information management method described in Technical Idea 1 to obtain the information.
  • the information management method described in Technical Idea 6 includes the step of (Technical Thought 8) In the step of issuing the item identification information, at least one variation information (VI) that changes for each item and an identification hash value (HVi) obtained by hashing original data including the variation information are used as the item identification information.
  • An information management device that manages information provided by multiple reporters (SR) that constitute a supply chain (SC), an issuing unit (32) that issues item identification information (UID) that is attached to an item (IM) shipped from the reporter and identifies the item to a destination terminal (50, 250) linked to the reporter; , an acquisition unit (33) that acquires a stored hash value (HVs) obtained by hashing history information (TRI) related to the item together with the item identification information; a storage unit (34) that stores the stored hash value in a database (BDB) in a state linked to the item identification information;
  • An information management device comprising:

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Strategic Management (AREA)
  • Development Economics (AREA)
  • Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
PCT/JP2023/008328 2022-03-23 2023-03-06 情報管理方法、及び情報管理装置 Ceased WO2023181883A1 (ja)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP23774482.6A EP4498305A4 (en) 2022-03-23 2023-03-06 Information management method and information management device
CN202380028667.XA CN119137614A (zh) 2022-03-23 2023-03-06 信息管理方法和信息管理装置
JP2024509940A JP7619523B2 (ja) 2022-03-23 2023-03-06 情報管理方法、情報管理装置、及び情報管理プログラム
US18/890,569 US20250016001A1 (en) 2022-03-23 2024-09-19 Information management method and information management device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP2022-047192 2022-03-23
JP2022047192 2022-03-23
JP2022-112030 2022-07-12
JP2022112030 2022-07-12

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/890,569 Continuation US20250016001A1 (en) 2022-03-23 2024-09-19 Information management method and information management device

Publications (1)

Publication Number Publication Date
WO2023181883A1 true WO2023181883A1 (ja) 2023-09-28

Family

ID=88100624

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/008328 Ceased WO2023181883A1 (ja) 2022-03-23 2023-03-06 情報管理方法、及び情報管理装置

Country Status (5)

Country Link
US (1) US20250016001A1 (https=)
EP (1) EP4498305A4 (https=)
JP (1) JP7619523B2 (https=)
CN (1) CN119137614A (https=)
WO (1) WO2023181883A1 (https=)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7587875B1 (ja) 2023-05-30 2024-11-21 東洋システム株式会社 再利用二次電池管理方法及び再利用二次電池管理システム
JP7634915B1 (ja) 2024-01-11 2025-02-25 株式会社ゼロボード 情報処理システム、情報処理方法及びプログラム

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021002226A1 (ja) 2019-07-02 2021-01-07 株式会社デンソー サプライチェーン管理方法、サプライチェーン管理プログラム、サプライチェーン管理システム、及び取引記録表示プログラム
JP2021509518A (ja) * 2018-02-22 2021-03-25 アイディーロジック インク．Ｉｄｌｏｇｉｑ Ｉｎｃ． サプライチェーンの製品ユニットの安全なシリアル化方法
JP2021140413A (ja) * 2020-03-04 2021-09-16 富士フイルムビジネスイノベーション株式会社 印刷制御装置、印刷装置、印刷制御システム及びプログラム
JP2021174419A (ja) * 2020-04-30 2021-11-01 株式会社日立製作所 情報収集管理システム、計算機、及び情報収集管理方法
JP2021174102A (ja) * 2020-04-21 2021-11-01 清水建設株式会社 施工情報管理システム、施工情報管理方法及びプログラム

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11615374B2 (en) * 2018-08-24 2023-03-28 Iq Universe Inc. Provenance and illicit product control system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021509518A (ja) * 2018-02-22 2021-03-25 アイディーロジック インク．Ｉｄｌｏｇｉｑ Ｉｎｃ． サプライチェーンの製品ユニットの安全なシリアル化方法
WO2021002226A1 (ja) 2019-07-02 2021-01-07 株式会社デンソー サプライチェーン管理方法、サプライチェーン管理プログラム、サプライチェーン管理システム、及び取引記録表示プログラム
JP2021140413A (ja) * 2020-03-04 2021-09-16 富士フイルムビジネスイノベーション株式会社 印刷制御装置、印刷装置、印刷制御システム及びプログラム
JP2021174102A (ja) * 2020-04-21 2021-11-01 清水建設株式会社 施工情報管理システム、施工情報管理方法及びプログラム
JP2021174419A (ja) * 2020-04-30 2021-11-01 株式会社日立製作所 情報収集管理システム、計算機、及び情報収集管理方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7587875B1 (ja) 2023-05-30 2024-11-21 東洋システム株式会社 再利用二次電池管理方法及び再利用二次電池管理システム
JP2024171391A (ja) * 2023-05-30 2024-12-12 東洋システム株式会社 再利用二次電池管理方法及び再利用二次電池管理システム
JP7634915B1 (ja) 2024-01-11 2025-02-25 株式会社ゼロボード 情報処理システム、情報処理方法及びプログラム
JP2025108928A (ja) * 2024-01-11 2025-07-24 株式会社ゼロボード 情報処理システム、情報処理方法及びプログラム

Also Published As

Publication number Publication date
JPWO2023181883A1 (https=) 2023-09-28
JP7619523B2 (ja) 2025-01-22
US20250016001A1 (en) 2025-01-09
EP4498305A1 (en) 2025-01-29
EP4498305A4 (en) 2025-03-05
CN119137614A (zh) 2024-12-13

Similar Documents

Publication Publication Date Title
JP7215581B2 (ja) サプライチェーン管理方法、サプライチェーン管理プログラム、取引記録蓄積方法、取引記録蓄積プログラム、取引記録表示方法、及び取引記録表示プログラム
US20250016001A1 (en) Information management method and information management device
US11271751B2 (en) Distributed data records
US9641342B2 (en) Tracking unitization occurring in a supply chain
US20230334609A1 (en) Information management method and non-transitory, computer readable, tangible storage medium storing information management program
JP6498123B2 (ja) サプライ・チェーン製品用のデジタル的に保護された電子タイトル
US11876894B2 (en) Method for controlling distribution of a product in a computer network and system
EP3227853A1 (en) Cryptographic verification of provenance in a supply chain
CN105096134A (zh) 用于验证数字实体及聚合对象来源的安全方案的系统及方法
CN115131037A (zh) 用于对商品窜货进行检测的方法及装置
CN114596165A (zh) 一种用于理财产品登记、销售、管理的区块链系统和方法
CN117710068B (zh) 基于人工智能的临时供应商核验方法、装置及设备
US20250130901A1 (en) Information management method and information management device
EP4446963A1 (en) Information processing method, information processing program, and information processing device
US20250005464A1 (en) Information processing method, storage medium producing method, and information accumulating method
CN110378079B (zh) 基于原创作品的信息处理、保护、销售方法及装置
HK40037024A (en) A method for controlling distribution of a product in a computer network and system
CN119067680A (zh) 一种基于区块链的防伪溯源系统及方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23774482

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024509940

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202380028667.X

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2023774482

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2023774482

Country of ref document: EP

Effective date: 20241023