IP Library › Granted Patent US 12,238,228
Granted Patent B2
US 12,238,228 · App. 17/625,938 · Granted Feb 25, 2025

Operational safety using a distributed ledger

Inventors: Koo Chee Hung (Stuttgart, DE); Kai Höfig (Rohrdorf, DE); Stefan Rothbauer (Augsburg, DE); Sebastian Schröck (Weil der Stadt, DE); Marian Marcel Vorderer (Rutesheim, DE); Marc Zeller (Munich, DE)
Assignee: Siemens Aktiengesellschaft
H04L9/50H04L9/3239H04L9/3247
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,238,228
App. No.
17/625,938
Granted
Feb 25, 2025
Kind
B2
Abstract

Provided is a device for ensuring safe operation of a technical system configured to generate a smart contract including a condition to be fulfilled for safe operation of a technical system, to store smart contract data of the smart contract in a distributed ledger, and to determine if the technical system fulfills the condition using the smart contract.

Claims (30)

1. A device for ensuring safe operation of a technical system, the device being configured to:

generate a smart contract including a condition, which is required to be fulfilled by the technical system for safe operation of the technical system;

store smart contract data of the smart contract which uniquely identifies the smart contract in a distributed ledger; and

determine if the technical system fulfills the condition using the smart contract, wherein the condition is a requirement according to an industry standard of the technical system and the smart contract is an operating permission of the technical system, further wherein the smart contract comprises at least one hazard element identifying a safety hazard of the technical system.

2. The device according to claim 1 , wherein the technical system comprises multiple technical subsystems, and wherein the device is further configured to:

obtain a subcondition for a technical subsystem to be fulfilled for safe operation of the technical subsystem;

generate a smart subcontract of the smart contract, which is to be fulfilled for the smart contract to be fulfilled, including the subcondition;

store smart subcontract data of the smart subcontract in the distributed ledger;

determine if the technical subsystem fulfills the subcondition using the smart subcontract.

3. The device according to claim 1 , further configured to:

store technical data of the technical system in the distributed ledger; and

determine if the technical system fulfills the condition using the smart contract based on the technical data.

4. The device according to claim 1 , wherein the at least one hazard element includes multiple hazard elements and the technical system is certified as safe when the multiple hazard elements are mitigated to an acceptable level.

5. The device according to claim 1 , wherein the at least one hazard element is associated with a measure, which is to be completed before safe operation of the technical system is ensured, and wherein the device is further configured to:

generate a smart measure contract including the measure to be fulfilled for the smart contract to be fulfilled;

store smart measure contract data in the distributed ledger; and

determine if the measure is completed using the smart measure contract.

6. The device according to claim 1 , wherein for the device is further configured to store a new hazard element in the smart contract in the distributed ledger.

7. The device according to claim 1 , wherein the smart contract comprises a risk quantification threshold, wherein fulfillment of the smart contract is determined based on a comparison of a risk quantification value associated with a hazard element included in the smart contract with the risk quantification threshold.

8. The device according to claim 1 , wherein the device is further configured to sign the smart measure contract by an entity responsible for performing the measure.

9. The device according to claim 1 , wherein the device is further configured to sign the technical data by an entity responsible the technical system.

10. The device according to claim 1 , wherein the device is further configured to sign the at least one smart contract, or smart subcontract, or smart measure contract additionally by a certification entity, after the respective smart contract has been fulfilled.

11. The device according to claim 10 , wherein the device is further configured to invalidate the signature of the smart contract or smart subcontract, when new technical data or a new hazard element has been stored in the distributed ledger.

12. The device according to claim 1 , wherein industry standard is an Environmental Health and Safety (EHS) industry standard of the technical.

13. The device according to claim 2 , wherein the technical system is a production line, and the technical subsystems are machines of the production line.

14. A method for ensuring safe operation of a technical system, comprising:

generating a smart contract including a condition, which is required to be fulfilled by the technical system for safe operation of the technical system;

storing smart contract data of the smart contract which uniquely identifies the smart contract, in a distributed ledger; and

determining if the technical system fulfills the condition using the smart contract, wherein the condition is a requirement according to an industry standard of the technical system and the smart contract is an operating permission of the technical system, further wherein the smart contract comprises at least one hazard element identifying a safety hazard of the technical system.

15. A computer program product having a non-transitory computer readable storage medium having instructions, which when executed by a processor, perform actions said computer program product comprising program code, which is to be executed by at least one processor, wherein executing the program code causes the at least one processor to carry out the method according to claim 14 .

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 27, 2022
From: HÖFIG, KAI; ROTHBAUER, STEFAN; ZELLER, MARC
To: SIEMENS AKTIENGESELLSCHAFT
Reel/Frame 060644/0745 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 27, 2022
From: HUNG, KOO CHEE; SCHRÖCK, SEBASTIAN; VORDERER, MARIAN MARCEL
To: ROBERT BOSCH GMBH
Reel/Frame 060645/0012 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 27, 2022
From: ROBERT BOSCH GMBH
To: SIEMENS AKTIENGESELLSCHAFT
Reel/Frame 060645/0125 →
Priority Claims (1)
EP 19187575 · Jul 22, 2019 · regional
Continuity (1)
Related Publication 20220271956A1 · Aug 25, 2022
References Cited (22)
US 20180005186A1 · Hunn · 2018 [cited by examiner]
US 20180117447A1 · Tran · 2018 [cited by examiner]
US 20190108140A1 · Deshpande · 2019 [cited by examiner]
US 20200074853A1 · Miller · 2020 [cited by examiner]
US 20200143937A1 · Wolber · 2020 [cited by examiner]
US 20200225643A1 · Tugbo · 2020 [cited by examiner]
US 20200358784A1 · Khaund · 2020 [cited by examiner]
US 20210349443A1 · Falk · 2021 [cited by examiner]
US 20220271956A1 · Hung · 2022 [cited by examiner]
EP 3355230A1 · 2018 [cited by examiner]
WO WO2020046797A1 · 2020 [cited by examiner]
Li et al., “Smart Transmission Grid: Vision and Framework”, IEEE Transactions On Smart Grid, vol. 1, No. 2, September (Year: 2010). [cited by examiner]
Swan, Melanie. Blockchain: Blueprint for a new economy. “O'Reilly Media, Inc.”, 2015. [cited by applicant]
Rimba, Paul, et al. “Comparing blockchain and cloud services for business process execution.” 2017, IEEE International Conference on Software Architecture (ICSA). IEEE, 2017. [cited by applicant]
Tschorsch, Florian, and Björn Scheuermann. “Bitcoin and beyond: A technical survey on decentralized digital currencies.” IEEE Communications Surveys & Tutorials 18.3 (2016): 2084-2123. [cited by applicant]
Yasaweerasinghelage, Rajitha, Mark Staples, and Ingo Weber. “Predicting latency of blockchain-based systems using architectural modelling and simulation.” 2017 IEEE International Conference on Software Architecture (ICS… [cited by applicant]
Nakamoto, Satoshi. “Bitcoin: A peer-to-peer electronic cash system.” (2017). [cited by applicant]
Xu, Xiwei, et al. “The blockchain as a software connector.” 2016 13th Working IEEE/IFIP Conference on Software Architecture (WICSA). IEEE, 2016. [cited by applicant]
Omohundro, Steve. “Cryptocurrencies, smart contracts, and artificial intelligence.” AI matters 1.2 (2014): 19-21. [cited by applicant]
Weber, Ingo, et al. “Untrusted business process monitoring and execution using blockchain.” International Conference on Business Process Management. Springer, Cham, 2016. [cited by applicant]
Wood, Gavin. “Ethereum: A secure decentralized generalized transaction ledger (eip-150 revision).” Online] Available: http://gavwood.com/paper.pdf (2016). [cited by applicant]
PCT International Search Report and Written Opinion of International Searching Authority mailed Oct. 19, 2020 corresponding to PCT International Application No. PCT/EP2020/070470 filed Jul. 20, 2020. [cited by applicant]