Server device and traceability method

Patent metadata

Field	Value
Publication number	US-11436614-B2
Application number	US-202016927071-A
Country	US
Kind code	B2
Filing date	Jul 13, 2020
Priority date	Sep 25, 2019
Publication date	Sep 6, 2022
Grant date	Sep 6, 2022

Abstract

A server device stores data sent from a client device together with data identification information and stakeholder identification information that identifies a stakeholder operating the client device. A controller determines a number of stakeholders included in the data, and, in a case where the data stores information on stakeholders of a plurality of n organizations, leaves information on a specific stakeholder unrewritten and rewrites information of other stakeholders with optional information to generate n types of management data. The controller generates first hash value for each of the n types of management data, and controls n transactions including the first hash value to be issued to a blockchain, and transmits the transaction. The controller returns, in response to a browsing request specifying the data identification information and the stakeholder identification information from the client device, management data corresponding to the stakeholder identification information among the n types of management data.

First claim

What is claimed is:

1. A management system, comprising:
a server;
a plurality of client devices, which each include a processor and a memory, the client devices each connected to the server via a network; and
a plurality of nodes implementing a blockchain, the plurality of nodes connected to the plurality of client devices and the server via the network,
wherein a first client device of a first stakeholder of a plurality of stakeholders, is configured to:
obtain information from a first code of a first product of a first stakeholder,
obtain information from a second code of a second product of a second stakeholder,
generate data based on the obtained information,
generate a file name;
generate an extensible markup language (XML) file containing identification (ID) information of the first stakeholder and ID information of the second stakeholder, and
transmit to the server the XML file, the file name and the data,

wherein the server includes a storage device that stores the file name in association with the XML file and the data,
wherein the server is configured to:
delete ID information of the second stakeholder from the stored XML file and leave the ID information of the first stakeholder unchanged to generate first management data,
generate a first hash value for the first management data,
delete ID information of the first stakeholder from the stored XML file and leave the ID information of the second stakeholder unchanged to generate second management data,
generate a second hash value for the second management data,
transmit the generated first hash value and the second hash value to at least one node implementing the blockchain,
receive a browsing request specifying the file name and one of the first stakeholder identification information and the second stakeholder ID information from the client device, and
return to the client device one of first management data and second management data corresponding to the received one of the first stakeholder identification information and the second stakeholder ID information.

2. The server device according to claim 1 , wherein
the server is configured to generate a third hash value that is a combination of the first management data and the second management data.

3. The server device according to claim 1 , wherein
the client device includes a plurality of client devices corresponding to the plurality of stakeholders.

4. A traceability method by a system having a plurality of client devices, a server device, and plurality of nodes implementing a blockchain, comprising:
obtaining, by a first client device of a first stakeholder of a plurality of stakeholders, information from a first code of a first product of a first stakeholder;
obtaining, by the first client device, information from a second code of a second product of a second stakeholder;
generating, by the first client device, data based on the obtained information;
generating, by the first client device, a file name; and
generating, by the first client device, an extensible markup language (XML) file containing identification (ID) information of the first stakeholder and ID info of the second stakeholder;
transmitting, by the first client device, to the server the XML file, the file name and the data;
storing, by the server device, the file name in association with the XML file and the data;
deleting, by the server device, ID information of the second stakeholder from the stored XML file and leaving the ID information of the first stakeholder unchanged to generate first management data;
generating, by the server device, a first hash value for the first management data;
deleting, by the server device, ID information of the first stakeholder from the stored XML file and leaving the ID information of the second stakeholder unchanged to generate second management data;
generating, by the server device, a second hash value for the second management data;
transmitting, by the server device, the generated first hash value and the second hash value to at least one node implementing the blockchain;
receiving, by the server device, a browsing request specifying the file name and one of the first stakeholder identification information and the second stakeholder ID information from the client device; and
returning, by the server device and to the client device, one of first management data and second management data corresponding to the received one of the first stakeholder identification information and the second stakeholder ID information.

5. The traceability method according to claim 4 , wherein
generating a hash value which is a collection of the first hash value and the second hash value.

6. The traceability method according to claim 4 , wherein each of
the plurality of client devices is operated by a different user.

Assignees

• Hitachi Ltd

Inventors

• Hasegawa Manabu
• Furuya Naoki
• Kosaka Tadayoshi
• Jin Yusuke

Classifications

• Y02P90/30

  Computing systems specially adapted for manufacturing · CPC title

• G06Q30/014

  Providing recall services for goods or products · CPC title

• G06F16/2379

  Updates performed during online database operations; commit processing · CPC title

• G06Q10/087

  Inventory or stock management, e.g. order filling, procurement or balancing against orders · CPC title

• G06Q50/04

  Manufacturing · CPC title