Method, system and computer readable medium for calibration testing and traceability
By using distributed ledgers and hash functions in the calibration system to generate calibration-related digital records, the problem of inefficient storage and retrieval of calibration information is solved, and the safety, traceability and efficient storage of calibration information is realized, ensuring the calibration information Authenticity and integrity.
Patent Information
- Application Number
- CN201910857644.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-09-12
- Filing Date
- 2019-09-09
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2039-09-09
AI Technical Summary
The prior art has problems such as inefficiency and difficulty in verifying authenticity in the calibration information storage and retrieval process. Especially when the amount of information is large and the diversity of documents increases, it is difficult to store and verify calibration information in a scalable and orderly manner. authenticity.
Use distributed ledgers (such as blockchains) to generate and store calibration-related digital records, generate calibration parameter values and timestamp information through hash functions, ensure the integrity and traceability of calibration information, and in the calibration system and The calibration test signal is passed between the test devices to generate a system-level hash value.
It realizes the safe, traceable and efficient storage of calibration information, ensures the data integrity and authenticity of calibration information, reduces the labor intensity of manual review, and improves the retrieval efficiency of calibration information.
Smart Images

Figure HDA0002195751150000011 
Figure HDA0002195751150000021 
Figure HDA0002195751150000031
Abstract
Description
Technical Field
[0001] The subject matter described herein relates to distributed ledger applications. More specifically, the subject matter relates to methods, systems, and computer-readable media for calibration testing and traceability using a distributed ledger. Background Art
[0002] Manufacturers usually test and calibrate equipment for various purposes (such as government compliance and quality assurance). For example, manufacturers can use calibration equipment or laboratories to test that one or more pieces of equipment perform as expected and meet specific accuracy, which can be traced back to the National Metrology Institute (NMI) standard. In this example, the one or more pieces of equipment can also be calibrated or adjusted to improve performance or meet standards. After performing calibration, calibration information (such as, certificates, equipment involved in calibration, calibration settings, calibration operator details, calibration location, traceability documents and / or other related details) can be generated and stored for future review or inspection by manufacturers and / or other parties. With the increase of the amount of calibration information, calibration information may become more difficult to store in a scalable and orderly manner. Further, the retrieval of calibration information may require people to identify, approve and provide various documents, which can be time-consuming and labor-intensive. In addition, it may be difficult to verify the authenticity of the calibration information, for example, because the document may be forged and / or may lack, for example, a proof of authenticity from a trusted source.
[0003] Therefore, there is a need for methods, systems, and computer-readable media for calibration testing and traceability using a distributed ledger. Summary of the invention
[0004] Methods, systems, and computer-readable media for calibration testing and traceability using a distributed ledger are disclosed. A method is performed at a calibration system implemented using at least one processor. The method includes: generating a first digital record based on calibration of the calibration system using a calibration source; providing a copy of the first digital record to a first device under test (DUT); and providing a calibration test signal associated with the calibration of the first DUT, wherein the first DUT uses the first digital record to generate a second digital record based on the calibration of the first DUT.
[0005] A system includes a distributed ledger system implemented using at least one processor. The distributed ledger system is configured to: generate a first digital record based on calibration of a calibration system using a calibration source; provide a copy of the first digital record to a first device under test (DUT); and provide a calibration test signal associated with the calibration of the first DUT, wherein the first DUT uses the first digital record to generate a second digital record based on the calibration of the first DUT.
[0006] The subject matter described herein can be implemented in software in combination with hardware and / or firmware. For example, the subject matter described herein can be implemented in software executed by a processor. In an exemplary embodiment, the subject matter described herein can be implemented using a non-transient computer-readable medium in which computer-executable instructions are stored, and the computer-executable instructions control the computer to perform steps when executed by the processor of the computer. Exemplary computer-readable media suitable for implementing the subject matter described herein include non-transient devices, such as disk memory devices, chip memory devices, programmable logic devices, field programmable gate arrays, and application-specific integrated circuits. In addition, the computer-readable medium implementing the subject matter described herein can be located on a single device or computer platform or can be distributed on multiple devices or computer platforms.
[0007] This application includes the following implementation schemes:
[0008] 1. A method for calibration testing and traceability using a distributed ledger, the method comprising:
[0009] At a calibration system implemented using at least one processor:
[0010] generating a first digital record based on calibration of the calibration system using a calibration source;
[0011] providing a copy of the first digital record to a first device under test (DUT); and
[0012] A calibration test signal associated with calibration of the first DUT is provided, wherein the first DUT uses the first digital record to generate a second digital record based on the calibration of the first DUT.
[0013] 2. The method of item 1, wherein the first digital record includes a first hash value, wherein the first hash value is generated using a first hash function, the first hash function using a first calibration parameter value as input, wherein the first calibration parameter value is based on the calibration of the calibration system.
[0014] 3. The method of item 2, wherein the first hash function uses calibration source identification information, calibration system identification information, calibration routine information or timestamp information as input.
[0015] 4. The method of item 1, wherein the second digital record includes a second hash value, wherein the second hash value is generated using a second hash function, the second hash function using a second calibration parameter value and the first digital record as input, wherein the second calibration parameter value is determined based on the calibration of the first DUT.
[0016] 5. The method of claim 1, comprising:
[0017] The first digital record is stored in a distributed ledger.
[0018] 6. The method of claim 1 , wherein the second digital record is stored in a digital ledger by the first DUT, the calibration system, or another entity.
[0019] 7. The method of claim 1, wherein the first DUT comprises a sensor, an autonomous vehicle sensor, an avionics sensor, a network device, an Internet of Things (IoT) device, or software.
[0020] 8. The method of claim 1, comprising:
[0021] At the calibration system or system controller:
[0022] receiving a plurality of digital records associated with calibration of a plurality of DUTs in a related system, wherein the second digital record is one of the plurality of digital records, and wherein the first DUT is one of the plurality of DUTs in the related system;
[0023] generating a system-level hash value indicative of a calibration status of the associated system using the plurality of digital records; and
[0024] The system-level hash value or related digital record is stored in a distributed ledger.
[0025] 9. The method of claim 8, wherein the related system comprises an autonomous vehicle, a computer network, or an Internet of Things (IoT) network.
[0026] 10. A system for calibration testing and traceability using a distributed ledger, the system comprising:
[0027] at least one processor; and
[0028] A calibration system implemented using the at least one processor, wherein the calibration system is configured to:
[0029] generating a first digital record based on calibration of the calibration system using a calibration source;
[0030] providing a copy of the first digital record to a first device under test (DUT); and
[0031] A calibration test signal associated with calibration of the first DUT is provided, wherein the first DUT uses the first digital record to generate a second digital record based on the calibration of the first DUT.
[0032] 11. The system of claim 10, wherein the calibration system is configured to generate a first hash value using a first hash function, the first hash function using a first calibration parameter value as input, wherein the first calibration parameter value is based on the calibration of the calibration system, and wherein the first digital record includes the first hash value.
[0033] 12. The system of claim 11, wherein the first hash function uses calibration source identification information, calibration system identification information, calibration routine information, or timestamp information as input.
[0034] 13. The system of claim 12, wherein the first DUT is configured to generate a second hash value using a second hash function, the second hash function using a second calibration parameter value and the first digital record as input, wherein the second calibration parameter value is determined based on the calibration of the first DUT, and wherein the second digital record includes the second hash value.
[0035] 14. The system of claim 10, wherein the calibration system is configured to store the first digital record in a distributed ledger.
[0036] 15. The system of claim 14, wherein the distributed ledger is a blockchain.
[0037] 16. The system of claim 10, wherein the second digital record is stored in a digital ledger by the first DUT, the calibration system, or another entity.
[0038] 17. The system of claim 10, wherein the first DUT comprises a sensor, an autonomous vehicle sensor, an avionics sensor, a network device, an Internet of Things (IoT) device, or software.
[0039] 18. The system of claim 10, wherein the calibration system or system controller is configured to:
[0040] receiving a plurality of digital records associated with calibration of a plurality of DUTs in a related system, wherein the second digital record is one of the plurality of digital records, and wherein the first DUT is one of the plurality of DUTs in the related system;
[0041] generating a system-level hash value indicative of a calibration status of the associated system using the plurality of digital records; and
[0042] The system-level hash value or related digital record is stored in a distributed ledger.
[0043] 19. The system of claim 18, wherein the related system comprises an autonomous vehicle, a computer network, or an Internet of Things (IoT) network.
[0044] 20. A non-transitory computer readable medium having executable instructions stored thereon, the executable instructions embodied in the non-transitory computer readable medium, the executable instructions when executed by at least one processor of a calibration system causing the calibration system to perform the steps comprising:
[0045] generating a first digital record based on calibration of the calibration system using a calibration source;
[0046] providing a copy of the first digital record to a first device under test (DUT); and
[0047] A calibration test signal associated with calibration of the first DUT is provided, wherein the first DUT uses the first digital record to generate a second digital record based on the calibration of the first DUT.
[0048] As used herein, the term 'node' refers to at least one physical computing platform including one or more processors, a network interface, and memory.
[0049] As used herein, each of the terms 'engine' and 'module' refers to hardware for implementing one or more features described, and the engine and the module may also include software and / or firmware. BRIEF DESCRIPTION OF THE DRAWINGS
[0050] The subject matter described herein will now be explained with reference to the accompanying drawings, in which:
[0051] Figure 1 is a diagram illustrating an example computing environment for a distributed ledger enabled calibration system;
[0052] Figure 2 is a diagram showing calibration of a calibration system using a calibration source and generating a digital record related to the calibration of the calibration system;
[0053] Figure 3 is a diagram illustrating storing digital records related to calibration of a calibration system in a distributed ledger;
[0054] Figure 4 is a diagram showing sending a copy of a digital record associated with calibration of a calibration system from the calibration system to a device under test (DUT);
[0055] Figure 5 A diagram showing calibration of a DUT and generating a digital record related to the calibration of the DUT;
[0056] Figure 6 is a diagram illustrating storing digital records related to calibration of a DUT in a distributed ledger;
[0057] Figure 7 is a diagram illustrating an example system environment for generating a system-level hash value; and
[0058] Figure 8 is a diagram showing an example process for calibration testing and traceability using a distributed ledger. DETAILED DESCRIPTION
[0059] The subject matter described herein relates to methods, systems, and computer-readable media for calibration testing and traceability using distributed ledgers. When calibrating physical or virtual computing equipment or its components, it may be desirable to store calibration information (e.g., certificates, reports, calibration results, details about calibration, etc.) in a secure format. For example, a party (e.g., an auditor or manufacturer) may want to verify and check the traceability of calibration information for equipment or components in equipment. In this example, if the calibration information is stored and / or stored in multiple filing systems in various formats (e.g., paper documents and digital files), the retrieval of the calibration information can be time-consuming and resource-intensive, especially when people are needed. Further, the authenticity and accuracy of the calibration information may be difficult to verify, especially when the calibration information is stored in physical files (e.g., paper documents) or in unsafe digital files.
[0060] According to some aspects of the subject matter described herein, techniques, methods, systems and / or mechanisms may use one or more distributed ledgers (e.g., blockchains or Merkle tree data structures) to store one or more digital records (e.g., digital certificates and / or hash values) associated with calibration information or related data. For example, a distributed ledger according to some aspects described herein may include a block or portion of a digital record associated with calibration information of a unit (e.g., a calibration device, a system with multiple devices, or a calibration system). In this example, when the calibration system is calibrated using a calibration source, the calibration system may generate a first digital record, and the device under test calibrated using the calibration system may generate a second digital record based at least in part on the first digital record. Continuing with this example, because the digital record can be based on related digital records, because the blocks of the distributed ledger can be linked in an encrypted manner (e.g., modification of a block will require modification of subsequent blocks), and because the calibration information can be encrypted in an external data storage device, the data integrity of the calibration information is guaranteed and the calibration information is protected from unauthorized changes.
[0061] According to some aspects of the subject matter described herein, techniques, methods, systems and / or mechanisms can generate and store system-level digital records (e.g., digital certificates and / or hash values) associated with calibration of multiple components or elements of a system. For example, in an autonomous vehicle, a sensor controller can receive a digital certificate containing calibration information for various sensors in the autonomous vehicle. In this example, the sensor controller can generate a system-level digital certificate (e.g., a hash value generated using a SHA-3 function) based at least on digital certificates associated with various devices in the autonomous vehicle. In some embodiments, the system-level digital certificate can be stored in a distributed ledger and / or one or more data storage devices (e.g., a database or data storage system).
[0062] Reference will now be made in detail to example embodiments of the subject matter described herein, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or like parts.
[0063] Figure 1 is a diagram illustrating an example computing environment 100 for a distributed ledger enabled calibration system. Figure 1 , the computing environment 100 may include a CS 102 and one or more devices and / or systems under test (DUTs) 116. The CS 102 may represent any suitable one or more entities (e.g., one or more computing platforms, nodes, or devices) associated with testing or calibrating the DUTs 116 (e.g., manufacturing equipment). For example, the CS 102 may generate and send traffic to the DUTs 116 and / or receive traffic from the DUTs 116 and may analyze one or more aspects associated with the DUTs 116.
[0064] In some embodiments, CS 102 may include a stand-alone tool, test equipment, or software executed on one or more processors. In some embodiments, CS 102 may be a single device or node or may be distributed across multiple devices or nodes. In some embodiments, CS 102 may include one or more modules for performing various test-related functions. For example, CS 102 may include a signal generator for generating test waveforms, sending the test waveforms to DUT 116, receiving waveforms from DUT 116, and analyzing the performance and functionality of DUT 116.
[0065] The DUT 116 may be any suitable entity or entities (e.g., a device, system, or platform) for receiving, processing, forwarding, and / or sending one or more messages. In some embodiments, the DUT 116 may include network equipment, industrial equipment, or one or more devices tested and / or calibrated by the CS 102 to, for example, a national standard. For example, the DUT 116 may include a security device (e.g., a firewall or an intrusion protection system (IPS)) that inspects traffic (e.g., Internet Protocol (IP) packets and / or network communications) traversing the security device. In this example, compliance or certification testing may be performed to determine whether the DUT 116 meets the relevant compliance or certification standards.
[0066] The CS 102 may include a test controller (TC) 104, a distributed ledger manager (DLM) 106, a data storage device 108, one or more processors 110, and a memory 112. The TC 104 may be any suitable entity or entities (e.g., software executing on a processor, a field programmable gate array (FPGA), and / or an application specific integrated circuit (ASIC), or a combination of software, FPGA, and / or ASIC) for performing one or more aspects associated with testing or calibrating the DUT 116 and / or various aspects thereof.
[0067] In some embodiments, the TC 104 can be implemented using one or more processors 110 and / or memory 112. For example, the TC 104 can utilize one or more processors 110 (e.g., executing software stored in the memory 112) to generate test packets for multiple calibration routines or tests (e.g., flows or sessions). In another example, the TC 104 can also utilize one or more of the processors 110 to perform or initiate analysis involving test waveforms and / or associated responses from the DUT 116.
[0068] In some embodiments, TC 104 may include or provide at least one communication interface for communicating with an operator 114 (e.g., a management system or a human operator). For example, operator 114 may be any entity (e.g., an automated system or a device or system controlled or controllable by a human user) for selecting and / or configuring various aspects associated with calibration and / or generating or configuring calibration settings. In some embodiments, various user interfaces (e.g., application programming interfaces (APIs) and graphical user interfaces (GUIs)) may be available so that operator 114 can provide configuration information (e.g., tests to be performed, types of metrics or statistics to be generated and / or measured, and / or other settings) to CS 102 or TC 104 and / or for controlling (e.g., pausing, restarting, or stopping) a test or calibration session.
[0069] DLM 106 can be any suitable one or more entities (e.g., software executed on a processor, an ASIC, an FPGA, or a combination of software, an ASIC, and / or an FPGA) for performing one or more actions associated with storing, accessing, and managing information in one or more distributed ledgers or related data storage devices (e.g., data storage device 108). For example, DLM 106 can receive calibration information, or other related data can generate a digital signature (e.g., an integrity hash value) based on the calibration information. In this example, DLM 106 can add or store the calibration information and / or related digital signature in the distributed ledger, for example, using a blockchain client.
[0070] In some embodiments, the DLM 106 may communicate with the CS 102 and / or other related entities (e.g., the TC 104) to receive, process, or send calibration information and / or related data, such as access security keys for allowing entities to access and / or decrypt the calibration information. For example, the DLM 106 may receive calibration information or other related data from the CS 102 or TC 104, may generate a hash value of the calibration information, may store the hash value in a blockchain for verifying the calibration information (e.g., when the calibration information is later obtained from a data storage device by a third party), may also encrypt the calibration information using one or more encryption keys and store the calibration information in one or more data storage devices, such as the data storage device 108. In this example, the DLM 106 may also receive information requests from various entities and may provide access security keys and / or decrypted calibration information.
[0071] In some embodiments, the TC 104 and / or the DLM 106 may include functionality for accessing a data storage device 108 or other memory. The data storage device 108 may be any suitable entity or entities (e.g., a storage device, memory, non-transitory computer-readable medium, or storage system) for maintaining or storing information related to testing and / or calibration. In some embodiments, the data storage device 108 and / or memory may be located at the CS 102, at another node, or distributed across multiple platforms or devices.
[0072] In some embodiments, data storage device 108 may include one or more data storage devices for storing different types of calibration information. For example, some unencrypted data may be stored in a first data storage device, and other encrypted data may be stored in one or more data storage devices different from the first data storage device.
[0073] In some embodiments, the data storage device 108 may contain calibration information that can be used to audit or verify the traceability of a calibrated device, also referred to herein as traceability information. Example calibration information related to a calibration event or related equipment may include certification information, calibration settings, calibration results, equipment involved in the calibration, measurement reports, parties involved in the calibration, calibration location, and / or other details associated with the calibration.
[0074] In some embodiments, CS 102, DLM 106, and / or another entity may generate a first digital record (e.g., a hash-based digital certificate) based on calibration of CS 102 using a calibration source, may provide a copy of the first digital record to DUT 116, and may provide a calibration test signal associated with the calibration of DUT 116, wherein DUT 116 generates a second digital record based on the calibration of DUT 116 using the first digital record.
[0075] It should be understood that Figure 1 is for illustrative purposes only and may change, alter, add to or remove any of the above Figure 1 The various depicted entities, locations of entities, and / or functions of entities are described.
[0076] Figure 2 is a diagram illustrating the use of a calibration source 202 to calibrate a CS 102 and generate a digital record (e.g., a digital certificate 204 or an associated hash value) related to the calibration of the CS 102. In some embodiments, the calibration source 202 may represent a national metrology institute (NMI), such as the United Kingdom's National Physical Library (NPL) or the United States' National Institute of Standards and Technology (NIST).
[0077] refer to Figure 2 , the CS 102 may perform one or more predefined test routines for calibrating the CS 102. For example, the CS 102 may perform a calibration test routine involving the calibration source 202. In this example, in response to the calibration test routine (e.g., during and / or after completing the calibration test routine), the CS 102 may adjust or modify one or more calibration parameter values (e.g., device settings) within the CS 102. Continuing with this example, the calibrated parameter values may be used to calibrate the CS 102 so that the CS 102 complies with one or more standards associated with the calibration test routine.
[0078] In some embodiments, after performing a calibration or a portion thereof, the CS 102 or another entity may generate a digital certificate 204 indicating various details about the calibration performed or a portion thereof. In some embodiments, the digital certificate 204 may represent any digital record containing details about the calibration performed or a portion thereof (e.g., administrative data, calibration settings, calibration site, etc.). In some embodiments, the digital certificate 204 and / or the hash value therein may be generated using one or more hash functions and one or more inputs. For example, to generate the digital certificate 204 and / or the hash value therein, the hash function may use one or more criteria as input.
[0079] In some embodiments, input criteria to a hash function (e.g., a SHA-1, SHA-2, or SHA-3 function) that generates the digital certificate 204 and / or an associated hash value may include a post-calibration parameter value, calibration source identification information, calibration system identification information, calibration routine information, and / or timestamp information. For example, using various data as input, the CS 102 may use a SHA-256 function to generate a 256-bit hash value associated with a calibration of the CS 102 (e.g., completing one or more predefined calibration test routines involving the CS 102). In another example, using various data as input, the CS 102 may use a SHA-512 function to generate a 512-bit hash value associated with a calibration of the CS 102 (e.g., completing one or more predefined calibration test routines involving the CS 102).
[0080] It should be understood that Figure 2 is for illustrative purposes only and may change, alter, add to or remove any of the above Figure 2 The various depicted entities, locations of entities, and / or functions of entities are described.
[0081] Figure 3 30 is a diagram showing that a digital record (e.g., a digital certificate 300 or a related hash value) related to the calibration of a DUT is stored in a distributed ledger 302. Figure 3, after CS 102 generates digital certificate 204, CS 102 or DLM 106 may store or cause to be stored digital certificate 300 (e.g., a copy of digital certificate 204 or an encrypted version thereof) in distributed ledger 302. In some embodiments, digital certificate 204, its version (e.g., digital certificate 300) and / or other information may be stored in a storage device local to CS 102, such as data storage device 108 and / or may be stored in an external storage device accessible to CS 102 or DLM 106. For example, secure external storage is accomplished via a distributed ledger or blockchain. In this example, DLM 106 may be configured to provide blockchain client functionality such that DLM 106 may post digital certificate 600 as a blockchain transaction to distributed ledger 302. In some embodiments, DLM 106 or other relevant entities may perform various actions to cause a blockchain transaction to be added to a blockchain.
[0082] It should be understood that Figure 3 is for illustrative purposes only and may change, alter, add to or remove any of the above Figure 3 The various depicted entities, locations of entities, and / or functions of entities are described.
[0083] Figure 4 1 is a diagram showing a copy of a digital record related to calibration of CS 102 being sent from CS 102 to DUT 116. Figure 4 , CS 102 may send digital certificate 400 (e.g., a copy of digital certificate 204 or an encrypted version thereof) to DUT 116 prior to or while calibrating DUT 116. For example, a copy of the digital certificate hash value may be transmitted to DUT 116 before CS 102 completes a calibration test involving DUT 116 (e.g., an electronic sensor in an autonomous vehicle).
[0084] In certain embodiments, the DUT 116 may store the digital certificate 400 , and when calibration of the DUT 116 is complete, the DUT 116 may use the digital certificate 400 and other data to generate a digital certificate related to the calibration of the DUT 116 .
[0085] It should be understood that Figure 4 is for illustrative purposes only and may change, alter, add to or remove any of the above Figure 4 The various depicted entities, locations of entities, and / or functions of entities are described.
[0086] Figure 5 is a diagram illustrating calibrating a DUT 116 and generating a digital record (eg, a digital certificate 500 or a related hash value) related to the calibration of the DUT 116. Figure 5 , the DUT 116 may perform one or more predefined calibration test routines. For example, the CS 102 may facilitate a calibration test routine involving the DUT 116 by sending a test signal or responding to the DUT 116 during execution of the calibration test routine. In this example, in response to the calibration test routine (e.g., during and / or after completion of the calibration test routine), the DUT 116 may adjust or modify one or more calibration parameter values (e.g., device settings) within the DUT 116. Continuing with this example, the calibrated parameter values may be used to calibrate the DUT 116 so that the DUT 116 complies with one or more standards associated with the calibration test routine.
[0087] In some embodiments, after performing a calibration or a portion thereof, the DUT 116 or another entity may generate a digital certificate 500 indicating various details about the calibration performed or a portion thereof. In some embodiments, the digital certificate 500 may represent any digital record containing details about the calibration performed or a portion thereof. In some embodiments, the digital certificate 500 and / or the hash value therein may be generated using one or more hash functions and one or more inputs. For example, to generate the digital certificate 500 and / or the hash value therein, the hash function may use one or more criteria as input.
[0088] In some embodiments, input criteria to a hash function (e.g., a SHA-1, SHA-2, or SHA-3 function) that generates the digital certificate 500 and / or associated hash value may include the digital certificate 400 or associated data, post-calibration parameter values, calibration source identification information, calibration system identification information, calibration routine information, and / or timestamp information from the CS 102. For example, using the digital certificate 400 and various other data as inputs, the DUT 116 may use a SHA-256 function to generate a 256-bit hash value associated with calibration of the DUT 116 (e.g., completing one or more predefined calibration test routines involving the DUT 116).
[0089] It should be understood that Figure 5 is for illustrative purposes only and may change, alter, add to or remove any of the above Figure 5 The various depicted entities, locations of entities, and / or functions of entities are described.
[0090] Figure 6 is a diagram showing that a digital record (e.g., a digital certificate 600 or a related hash value) related to the calibration of a DUT is stored in a distributed ledger 302. Figure 6, after the DUT 116 generates the digital certificate 500, the DUT 116 or DLM 106 may store or cause the digital certificate 600 (e.g., a copy of the digital certificate 500 or an encrypted version thereof) to be stored in the distributed ledger 302. In some embodiments, the digital certificate 500, its version (e.g., the digital certificate 600), and / or other information may be stored in a storage device local to the DUT 116, such as the data storage device 502, and / or may be stored in an external storage device accessible to the DUT 116 or DLM 106. For example, the secure external storage is accomplished via a distributed ledger or blockchain. In this example, the DLM 106 may be configured to provide blockchain client functionality such that the DLM 106 may post the digital certificate 600 as a blockchain transaction to the distributed ledger 302. In some embodiments, the DLM 106 or other relevant entity may perform various actions to cause the blockchain transaction to be added to the blockchain.
[0091] It should be understood that Figure 6 is for illustrative purposes only and may change, alter, add to or remove any of the above Figure 6 The various depicted entities, locations of entities, and / or functions of entities are described.
[0092] Figure 7 is a diagram showing an example system environment 700 for generating a system-level hash value. The system environment 700 may represent various networks or related devices or systems, such as an IoT device or network, an autonomous vehicle or system therein (e.g., a sensor system), or another network or system. Figure 7 , the system environment 700 may include a system controller 702 , a distributed ledger 704 , and a plurality of DUTs 708A-C representing one or more devices, components, or equipment in the system environment 700 .
[0093] The system controller 702 may represent any suitable entity or entities (e.g., one or more computing platforms, nodes, or devices) associated with generating a system-level hash value or associated digital certificate 714. In some embodiments, the system controller 702 may include or utilize one or more modules, processors, communication interfaces, and / or memories, such as a data storage device 706.
[0094] In some embodiments, the system controller 702 may receive information and / or digital certificates 710A-C from various components or nodes within the system environment 700 and, using the information, may determine or generate information about the state of the system environment 700. For example, the system controller 702 may include one or more communication interfaces for receiving digital certificates 710A-C or other information from the DUTs 708A-C.
[0095] In some embodiments, the system controller 702 or a related entity may generate a system-level hash value and / or certificate 712. In such embodiments, the system-level hash value and / or certificate 712 may be based on a combination of some or all of the digital certificates 710A-C received from the DUTs 708A-C. For example, the system controller 702 or a related entity generates the certificate 712 using a hash function (e.g., a SHA-1, SHA-2, or SHA-3 function) that uses a hash value or information from the digital certificates 710A-C as input.
[0096] In some embodiments, the system controller 702 may include a data storage device 706 for storing the digital certificates 710A-C, the digital certificate 712, and / or other information. For example, after receiving the digital certificates 710A-C, the system controller 702 may store the digital certificates 710A-C and / or related information in the data storage device 706. In this example, after generating the digital certificate 714 using the digital certificates 710A-C, the system controller 702 may store the digital certificate 712 in the data storage device 706.
[0097] In some embodiments, the system controller 702 may include a DLM 106 for interacting with the distributed ledger 704, such as accessing data, storing data, or deleting data therein. For example, after generating the digital certificate 712, the DLM 106 may generate a transaction for adding the digital certificate 714 (e.g., a copy of the digital certificate 714 or an encrypted version thereof) to the distributed ledger 704.
[0098] In some embodiments, system controller 702 may be, for example, a sensor controller associated with an autonomous vehicle, industrial equipment, IoT system, or other device. In such embodiments, each of DUTs 708A-C may be a sensor associated with system environment 700 (e.g., an autonomous vehicle sensor, an avionics sensor, an Internet of Things (IoT) sensor, etc.).
[0099] It should be understood that Figure 7 is for illustrative purposes only and may change, alter, add to or remove any of the above Figure 7 The various depicted entities, locations of entities, and / or functions of entities are described.
[0100] Figure 8 800 is a diagram illustrating an example process 800 for calibration testing and traceability using a distributed ledger. In some embodiments, process 800 or portions thereof may be performed by or at CS 102, DLM 106, system controller 702, and / or another node or module. In some embodiments, process 800 may include steps 802, 804, and / or 806.
[0101] Referring to process 800, in step 802, a first digital record may be generated based on calibration of a calibration system using a calibration source. For example, after calibrating CS 102 using a reference signal from calibration source 202, CS 102 or a related entity may generate digital certificate 204 and store digital certificate 204 in data storage device 108.
[0102] In step 802, a copy of the first digital record can be provided to the first DUT. For example, CS 102 or a related entity can send digital certificate 400 (eg, a copy of digital certificate 204) to DUT 116.
[0103] In step 804, a calibration test signal associated with the calibration of the first DUT may be provided to the first DUT. In some embodiments, the first DUT generates a second digital record based on the calibration of the first DUT using the first digital record. For example, the CS 102 may send the calibration test signal when the DUT 116 performs a calibration test routine for calibrating the DUT 116. In this example, after the DUT 116 is calibrated using the calibration test routine, the DUT 116 or a related entity may generate a digital certificate 500, wherein the digital certificate 500 is generated using the digital certificate 400 or information therein.
[0104] In some embodiments, the first digital record may include a first hash value, wherein the first hash value may be generated using a first hash function (e.g., a SHA-256 function), the first hash function using a first calibration parameter value as an input, wherein the first calibration parameter value may be based on calibration of a calibration system.
[0105] In some embodiments, the first hash function uses calibration source identification information, calibration system identification information, calibration routine information, and / or timestamp information as input.
[0106] In some embodiments, the second digital record may include a second hash value, wherein the second hash value may be generated using a second hash function (e.g., a SHA-256 function), the second hash function using a second calibration parameter value and the first digital record as inputs, wherein the second calibration parameter value may be determined based on calibration of the first DUT.
[0107] In some embodiments, the first digital record may be stored in a distributed ledger, such as a blockchain.
[0108] In some embodiments, the second digital record may be stored in a digital ledger by the first DUT, the calibration system, or another entity.
[0109] In some embodiments, the first DUT may include a sensor, an autonomous vehicle sensor, an avionics sensor, a network device, an Internet of Things (IoT) device, or software.
[0110] In some embodiments, a calibration system or system controller may be configured to: receive multiple digital records associated with calibration of multiple DUTs in a related system (e.g., an autonomous vehicle, a computer network, or an IoT network), wherein the second digital record may be one of the multiple digital records, and wherein the first DUT may be one of the multiple DUTs in the related system; generate a system-level hash value using the multiple digital records, which hash value may indicate a calibration status of the related system; and store the system-level hash value or the related digital record in a distributed ledger.
[0111] In some embodiments, a system-level hash value or related digital record may be generated using a hash function that generates the same or greater number of bits than the individual DUTs. For example, the system-level hash value may be a 512-bit hash value, and the DUT hash value may be a 256-bit hash value.
[0112] It should be appreciated that process 800 is for illustrative purposes and that different and / or additional actions may be used. It should also be appreciated that the various actions described herein may be performed in a different order or sequence.
[0113] It should be noted that the CS 102, DLM 106, system controller 702, and / or the functionality described herein may constitute a special purpose computing device. Further, the CS 102, DLM 106, system controller 702, and / or the functionality described herein may improve the field of secure data storage technology, the field of calibration testing technology, the field of calibration traceability technology, and / or the field of calibration audit technology. For example, by using one or more distributed ledgers (e.g., one or more blockchains) and using hash-based digital certificates, calibration information may be stored in a secure and verifiably accurate format.
[0114] It should be understood that various details of the subject matter described herein can be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only and not for the purpose of limitation, as the subject matter described herein is defined by the claims.
Claims
1. A method for calibration testing and traceability using a distributed ledger, the method comprising: At a calibration system implemented using at least one processor: a) generating a first digital record based on calibration of the calibration system using a calibration source; b) providing a copy of said first digital record to a first device under test; as well as c) providing a calibration test signal associated with calibration of the first device under test, wherein the first device under test uses the first digital record to generate a second digital record based on the calibration of the first device under test, wherein the second digital record includes a second hash value, the second hash value is generated using a second hash function, the second hash function uses as input a second calibration parameter value and a copy of the first digital record, the second calibration parameter value is determined based on the calibration of the first device under test, and the second digital record is stored in a distributed ledger.
2. The method according to claim 1, wherein: The first digital record comprises a first hash value, wherein the first hash value is generated using a first hash function, the first hash function using as input a first calibration parameter value, wherein the first calibration parameter value is based on the calibration of the calibration system.
3. The method according to claim 2, wherein: The first hash function uses calibration source identification information, calibration system identification information, calibration routine information, or timestamp information as input.
4. The method according to claim 1, comprising: a) Storing the first digital record in a distributed ledger.
5. The method according to claim 1, wherein: The second digital record is stored in the distributed ledger by the first device under test, the calibration system, or another entity.
6. The method according to claim 1, wherein: The first device under test includes a sensor, an autonomous vehicle sensor, an avionics sensor, a network device, an Internet of Things (IoT) device, or software.
7. The method according to claim 1, comprising: At the calibration system or system controller: a) receiving a plurality of digital records associated with calibration of a plurality of devices under test in a related system, wherein the second digital record is one of the plurality of digital records, and wherein the first device under test is one of the plurality of devices under test in the related system; b) generating a system-level hash value indicative of a calibration status of the associated system using the plurality of digital records; and c) storing the system-level hash value or related digital record in the distributed ledger.
8. The method according to claim 7, wherein: The related systems include autonomous vehicles, computer networks, or Internet of Things (IoT) networks.
9. A system for calibration testing and traceability using a distributed ledger, the system comprising: at least one processor; as well as A calibration system implemented using the at least one processor, wherein the calibration system is configured to: generating a first digital record based on calibration of the calibration system using a calibration source; providing a copy of the first digital record to a first device under test; and Providing a calibration test signal associated with calibration of the first device under test, wherein the first device under test uses the first digital record to generate a second digital record based on the calibration of the first device under test, wherein the second digital record includes a second hash value, the second hash value is generated using a second hash function, the second hash function uses as inputs a second calibration parameter value and a copy of the first digital record, the second calibration parameter value is determined based on the calibration of the first device under test, and the second digital record is stored in a distributed ledger.
