Information Management Method and Device for Measuring Equipment

Abstract

This specification provides a method and apparatus for information management of a measurement device, which is applied to a network system including multiple blockchains. The network system includes a data sender node device and a data management node device. The data sender node device is a node device of the first blockchain, and the data management node device is a node device of the second blockchain. The first blockchain stores a target deposit transaction sent by the data sender node device, and the target deposit transaction includes the device status information of the measurement device. The method includes: receiving a cross-chain management request from the data management node device for the device status information of the measurement device stored in the first blockchain; verifying whether the data management party has the management authority for the device status information of the measurement device; if so, obtaining the target deposit transaction and performing management on the device status information of the measurement device based on the target deposit transaction.

Description

Technical Field

[0001] One or more embodiments of this specification relate to the field of blockchain technology, and in particular, to a method and device for information management of measurement devices. Background Art

[0002] Measurement devices or apparatuses are widely used in various industries. During their life cycle processes such as production, logistics, installation, use, and maintenance, various device status information will be generated, and this various device status information is of crucial significance for the correct and normal use of the measurement devices. Currently, the security level of the storage management of this information is insufficient, there is a risk of abnormal information modification, and the application level of this information is not high.

[0003] Currently, the storage management methods for various status information of measurement devices usually include decentralized physical storage information management, information management based on databases or cloud storage. The decentralized physical storage information management method cannot efficiently retrieve information and perform multifunctional information applications, and the information may be lost due to the failure of storage devices; the information management based on databases or cloud storage improves the efficiency of information retrieval and application, but the security level of information management is still insufficient.

[0004] Existing measurement device information management methods based on blockchain usually require deploying all relevant parties during the life cycle of measurement devices, such as the production manufacturers, logistics companies, users, and maintenance parties of measurement devices, within the same blockchain. It is difficult to achieve privacy and security protection for the information uploaded by each relevant party, and due to the excessive amount of device status information data for evidence storage, the physical configuration requirements for each relevant party's node devices are increased. Summary of the Invention

[0005] In view of this, one or more embodiments of this specification provide a method and device for information management of measurement devices, a computer device, and a computer-readable storage medium.

[0006] To achieve the above object, one or more embodiments of this specification provide a method for information management of measurement devices, which is applied to a network system including multiple blockchains. The network system includes a data sending party node device and a data management party node device; the data sending party node device is a node device of the first blockchain, and the data management party node device is a node device of the second blockchain; the first blockchain stores a target evidence storage transaction sent by the data sending party node device, and the target evidence storage transaction includes the device status information of the measurement device; the method is executed by the node device of the first blockchain and includes:

[0007] Receiving a cross-chain management request from the data management party node device for the device status information of the measurement device stored in the first blockchain;

[0008] In response to the cross-chain management request, verify whether the data manager has the management authority for the device status information of the measurement device;

[0009] If so, obtain the target deposit transaction, and based on the target deposit transaction, perform the management of the device status information of the measurement device.

[0010] In another illustrated embodiment, the cross-chain management request is a request for cross-chain obtaining the device status information of the measurement device;

[0011] The performing the management of the device status information of the measurement device includes:

[0012] Cross-chain send the device status information of the measurement device to the data manager node device.

[0013] In another illustrated embodiment, a smart contract for managing the device status information is deployed on the first blockchain, and the processing logic corresponding to the contract code of the smart contract includes management authority verification logic;

[0014] In response to the cross-chain access request, verifying whether the data manager has the management authority for the device status information of the measurement device includes:

[0015] In response to the cross-chain access request, call the management authority verification logic in the smart contract to verify whether the data manager has the management authority for the device status information of the measurement device.

[0016] In another illustrated embodiment, the processing logic corresponding to the contract code of the smart contract further includes management logic for the device status information;

[0017] The obtaining the target deposit transaction and performing the management of the device status information of the measurement device based on the target deposit transaction includes:

[0018] After verifying that the data manager has the management authority for the device status information of the measurement device, further call the management logic for the device status information in the smart contract, obtain the target deposit transaction, and based on the target deposit transaction, perform the management of the device status information of the measurement device.

[0019] In another illustrated embodiment, the first blockchain and the second blockchain are different sub-chains belonging to the same consortium chain.

[0020] In another illustrated embodiment, the receiving the cross-chain access request from the data manager node device for the device status information of the measurement device stored on the first blockchain includes:

[0021] Receive, via the cross-chain relay device, a cross-chain access request from the data management party node device for the device status information of the measurement device stored in the first blockchain.

[0022] In another illustrated embodiment, the data sender node device includes one or more of a production record node device of the measurement device, or an initial calibration node device, or a measurement certification agency node device, or a logistics agency node device, or a user node device, or a maintenance party node device;

[0023] The target deposit transaction includes a unique identification code corresponding to the measurement device; the device status information includes one or more of raw material information, or production process information, or initial calibration information, or certification qualification information, or logistics circulation information, or device replication parameters, or abnormal status information, or measurement data record information, or maintenance record information, or electronic contract information related to the measurement device.

[0024] In another illustrated embodiment, the target deposit transaction includes the latest electronic lead seal code of the measurement device; the cross-chain management request includes the existing lead seal identification code of the measurement device;

[0025] The management logic of the device status information included in the processing logic corresponding to the contract code of the smart contract includes:

[0026] Step A, obtain the target deposit transaction;

[0027] Step B, based on the target deposit transaction, determine whether the latest lead seal identification code is the same as the existing lead seal identification code;

[0028] Step C, when the latest lead seal identification code is different from the existing lead seal identification code, send a preset prompt or alarm operation to the data management party node device across the chain.

[0029] In another illustrated embodiment, the target deposit transaction includes the latest calibration information of the measurement device; the cross-chain management request includes the existing calibration information of the measurement device;

[0030] The management logic of the device status information included in the processing logic corresponding to the contract code of the smart contract includes:

[0031] Step A, obtain the target deposit transaction;

[0032] Step B, based on the target deposit transaction, determine whether the latest calibration information is the same as the existing calibration information;

[0033] Step C, when the latest calibration information is different from the existing calibration information, send the latest calibration information across the chain to the data management party node device, so that the data management party node device can calibrate the measuring device based on the latest calibration information.

[0034] In another illustrated embodiment, the target deposit transaction includes the latest software program corresponding to the measuring device and the version number of the latest software program; the data management party node device is the measuring device; the cross-chain management request includes the version number of the current software program of the measuring device;

[0035] The management logic for the device status information included in the processing logic corresponding to the contract code of the smart contract includes:

[0036] Step A, obtain the target deposit transaction;

[0037] Step B, based on the target deposit transaction, compare whether the version number of the latest software program and the version number of the current software program differ by a preset number of levels;

[0038] Step C, if so, send the latest software program across the chain to the measuring device, so that the measuring device performs an upgrade of the software version.

[0039] In another illustrated embodiment, the target deposit transaction includes the first measurement result information of the measuring device; the cross-chain management request includes the second measurement result information of the measuring device;

[0040] The management logic for the device measurement information included in the processing logic corresponding to the contract code of the smart contract includes:

[0041] Step A, obtain the target deposit transaction;

[0042] Step B, based on the target deposit transaction, compare whether the first measurement result information and the second measurement result information are the same;

[0043] Step C, when the first measurement result information and the second measurement result information are different, send across the chain to the data management party node device the first measurement result information, or a preset prompt or alarm operation.

[0044] In another illustrated embodiment, the target deposit transaction includes the first device operation information of the measuring device; the cross-chain management request includes the second device operation information of the measuring device;

[0045] The management logic for the device operation information included in the processing logic corresponding to the contract code of the smart contract includes:

[0046] Step A, obtain the target certified transaction;

[0047] Step B, based on the target certified transaction, compare whether the first device operation information is the same as the second device operation information;

[0048] Step C, when the first device operation information is different from the second device operation information, cross-chain send to the data management party node device the first device operation information or a preset prompt or alarm operation.

[0049] Correspondingly, this specification also provides an information management device for a measurement device, which is applied to a network system including multiple blockchains. The network system includes a data sender node device and a data management party node device; the data sender node device is a node device of the first blockchain, and the data management party node device is a node device of the second blockchain; the first blockchain stores the target certified transaction sent by the data sender node device, and the target certified transaction includes the device status information of the measurement device; the device is applied to the node device side of the first blockchain and includes:

[0050] A receiving unit, configured to receive a cross-chain management request from the data management party node device for the device status information of the measurement device stored in the first blockchain;

[0051] A verification unit, configured to, in response to the cross-chain management request, verify whether the data management party has the management authority for the device status information of the measurement device;

[0052] An execution unit, configured to obtain the target certified transaction and, based on the target certified transaction, execute the management of the device status information of the measurement device.

[0053] In another illustrated embodiment, the cross-chain management request is a request to cross-chain obtain the device status information of the measurement device;

[0054] The execution unit is further configured to:

[0055] Obtain the target certified transaction and cross-chain send the device status information of the measurement device to the data management party node device.

[0056] In another illustrated embodiment, the first blockchain deploys a smart contract for managing the device status information, and the processing logic corresponding to the contract code of the smart contract includes a management authority verification logic;

[0057] The verification unit is further configured to:

[0058] In response to the cross-chain access request, call the management permission verification logic in the smart contract to verify whether the data manager has the management permission for the device status information of the measurement device.

[0059] In another illustrated embodiment, the processing logic corresponding to the contract code of the smart contract further includes the management logic for the device status information;

[0060] The execution unit is further configured to:

[0061] After verifying that the data manager has the management permission for the device status information of the measurement device, further call the management logic for the device status information in the smart contract to obtain the target deposit transaction, and based on the target deposit transaction, perform the management of the device status information of the measurement device.

[0062] In another illustrated embodiment, the first blockchain and the second blockchain are different sub-chains belonging to the same consortium chain.

[0063] In another illustrated embodiment, the receiving unit is further configured to:

[0064] Receive, through a cross-chain relay device, a cross-chain access request from the data manager node device for the device status information of the measurement device stored in the first blockchain.

[0065] In another illustrated embodiment, the data sender node device includes one or more of a production record node device of a measurement device, or an initial calibration node device, or a measurement certification agency node device, or a logistics agency node device, or a user node device, or a maintenance party node device;

[0066] The target deposit transaction includes a unique identification code corresponding to the measurement device; the device status information includes one or more of raw material information, or production process information, or initial calibration information, or certification qualification information, or logistics circulation information, or device replication parameters, or abnormal status information, or measurement data record information, or maintenance record information, or electronic contract information related to the measurement device.

[0067] In another illustrated embodiment, the target deposit transaction includes the latest electronic lead seal code of the measurement device; the cross-chain management request includes the existing lead seal identification code of the measurement device;

[0068] The management logic for the device status information included in the processing logic corresponding to the contract code of the smart contract includes:

[0069] Step A, obtain the target deposit transaction;

[0070] Step B: Based on the target deposit transaction, determine whether the latest seal identification code is the same as the existing seal identification code;

[0071] Step C: When the latest seal identification code is different from the existing seal identification code, send a preset prompt or alarm operation across the chain to the data management party node device.

[0072] In another illustrated embodiment, the target deposit transaction includes the latest calibration information of the measuring device; the cross-chain management request includes the existing calibration information of the measuring device;

[0073] The management logic of the device status information included in the processing logic corresponding to the contract code of the smart contract includes:

[0074] Step A: Obtain the target deposit transaction;

[0075] Step B: Based on the target deposit transaction, determine whether the latest calibration information is the same as the existing calibration information;

[0076] Step C: When the latest calibration information is different from the existing calibration information, send the latest calibration information across the chain to the data management party node device so that the data management party node device can calibrate the measuring device based on the latest calibration information.

[0077] In another illustrated embodiment, the target deposit transaction includes the latest software program corresponding to the measuring device and the version number of the latest software program; the data management party node device is the measuring device; the cross-chain management request includes the version number of the current software program of the measuring device;

[0078] The management logic of the device status information included in the processing logic corresponding to the contract code of the smart contract includes:

[0079] Step A: Obtain the target deposit transaction;

[0080] Step B: Based on the target deposit transaction, compare whether the version number of the latest software program differs from the version number of the current software program by a preset number of levels;

[0081] Step C: If so, send the latest software program across the chain to the measuring device so that the measuring device performs a software version upgrade.

[0082] In another illustrated embodiment, the target deposit transaction includes the first measurement result information of the measuring device; the cross-chain management request includes the second measurement result information of the measuring device;

[0083] The processing logic corresponding to the contract code of the smart contract includes the management logic for the device measurement information, including:

[0084] Step A, obtain the target deposit transaction;

[0085] Step B, based on the target deposit transaction, compare whether the first measurement result information and the second measurement result information are the same;

[0086] Step C, when the first measurement result information and the second measurement result information are different, cross-chain send to the data management party node device, including the first measurement result information, or a preset prompt or alarm operation.

[0087] In another illustrated embodiment, the target deposit transaction includes the first device operation information of the measurement device; the cross-chain management request includes the second device operation information of the measurement device;

[0088] The processing logic corresponding to the contract code of the smart contract includes the management logic for the device operation information, including:

[0089] Step A, obtain the target deposit transaction;

[0090] Step B, based on the target deposit transaction, compare whether the first device operation information and the second device operation information are the same;

[0091] Step C, when the first device operation information and the second device operation information are different, cross-chain send to the data management party node device, including the first device operation information or a preset prompt or alarm operation.

[0092] Correspondingly, this specification also provides a computer device, including: a memory and a processor; a computer program that can be run by the processor is stored on the memory; when the processor runs the computer program, it executes the information management method of the measurement device as described in the above embodiments.

[0093] Correspondingly, this specification also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is run by a processor, it executes the information management method of the measurement device as described in the above embodiments.

[0094] As can be seen from the above technical solutions, the information management method and device of the measurement device provided in this specification not only decentralize and store the device status information of the measurement device in the blockchain to prevent tampering; but also further increase the privacy and security of the device status information data based on the cross-chain information interaction technology of multiple blockchains, and reduce the physical configuration requirements for the node devices on each blockchain. Brief Description of the Drawings

[0095] Figure 1 is a schematic flowchart of a method for information management of a measuring device provided by an exemplary embodiment;

[0096] Figure 2 is a schematic flowchart of a method for calibration information management of a measuring device provided by another exemplary embodiment;

[0097] Figure 3 is a schematic flowchart of a method for electronic seal status management of a measuring device provided by another exemplary embodiment;

[0098] Figure 4 is a schematic flowchart of a method for measurement result verification management of a measuring device provided by another exemplary embodiment;

[0099] Figure 5 is a schematic flowchart of a method for device operation information management of a measuring device provided by another exemplary embodiment;

[0100] Figure 6 is a schematic diagram of an information management device for a measuring device provided by an exemplary embodiment;

[0101] Figure 7 is a hardware structure diagram of a device running the information management device embodiment of the measuring device provided in this specification. Detailed Embodiments

[0102] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all the embodiments consistent with one or more embodiments of this specification. On the contrary, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0103] It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily executed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step for description in other embodiments.

[0104] Measuring devices are widely used in various industries. The life cycle of a measuring device may include the production stage, logistics stage, installation stage, usage stage, maintenance stage, or a combination of any of the above multiple stages. During the life cycle of a measuring device, various device status information data can be generated, such as device production environment data generated during the production stage (including production parameters of devices such as temperature and humidity, acid-base conditions, processing machine tools, calibration parameters, etc.), logistics circulation data generated during the logistics stage (including time information for entering and leaving the logistics station, along-the-way environment information, abnormal logistics transfer information, etc.), adjustment and installation data generated during the installation stage (including electronic seal status, device calibration information, initial parameters, etc.), normal or abnormal usage data generated during the usage stage (including measurement data generated during normal usage, error messages when abnormalities occur, software information carried by the device, etc.), and information data generated during the maintenance stage (including maintenance records, accuracy information of the device after maintenance, software update version numbers, etc.).

[0105] The device status information generated during the life cycle of the above-mentioned measuring device is of great significance for the normal use of the measuring device. Currently, the storage management methods for various status information of measuring devices usually include decentralized physical storage information management, that is, the above-mentioned device status information is stored separately in the computing servers of manufacturers, logistics providers, and user clients, or the above-mentioned parties conduct cloud storage data management. The security level of the storage management of the above-mentioned device status information is insufficient, and there is a risk of abnormal data modification; moreover, the decentralized physical storage information management method cannot retrieve information efficiently and apply information with multiple functions, and the information may be lost due to the failure of the storage device. Further, decentralized physical storage is not conducive to the coordinated management and application of the above-mentioned device status information generated during the life cycle of the measuring device.

[0106] In the prior art, it is proposed to manage the information of measuring devices based on blockchain. Usually, all relevant parties during the life cycle of the measuring device, such as the production manufacturer, logistics company, user, and maintenance party, need to be deployed in the same blockchain. Since the device status information stored by each relevant party in the blockchain is backed up at each node device of the blockchain, it is difficult to achieve privacy and security protection for the information uploaded by each relevant party; moreover, due to the excessive amount of device status information data certified by each relevant party, the physical configuration requirements for each relevant party's node device are increased.

[0107] In view of this, this specification provides an information management method for measuring devices, which is applied to a network system including multiple blockchains; the network system includes a data sending party node device and a data management party node device; the data sending party node device is a node device of the first blockchain, and the data management party node device is a node device of the second blockchain.

[0108] The blockchain described in one or more embodiments of this specification may specifically refer to a P2P network system with a distributed data storage structure achieved by each node device through a consensus mechanism. The data within this blockchain is distributed within successive "blocks" that are connected in time. The subsequent block contains the data digest of the previous block, and depending on the specific consensus mechanism (such as POW, POS, DPOS, or PBFT, etc.), a full backup of the data of all or some nodes is achieved. Those skilled in the art are well aware that since the blockchain system operates under the corresponding consensus mechanism, it is very difficult for the data already included in the blockchain database to be tampered with by any arbitrary node. For example, in a blockchain using the Pow consensus, at least an attack with 51% of the computing power of the entire network is required to possibly tamper with the existing data. Therefore, the blockchain system has the characteristics of ensuring data security and preventing attack and tampering that cannot be compared with other centralized database systems. From this, it can be seen that in the embodiments provided in this specification, the data included in the distributed ledger of the blockchain will not be attacked or tampered with, thus ensuring the authenticity and fairness of data management or applications based on the data stored within the blockchain.

[0109] The network system including multiple blockchains described in one or more embodiments of this specification is a multi-chain system composed of the above-mentioned multiple blockchains. Data access or cross-chain invocation of smart contracts can be performed between each blockchain based on cross-chain interaction technology. This specification does not limit whether each blockchain constituting the above multi-chain system adopts the same underlying protocol. That is, the above first blockchain and second blockchain can be either homogeneous blockchains constructed based on the same blockchain underlying protocol or heterogeneous blockchains constructed based on different blockchain underlying protocols.

[0110] In practical applications, each relevant party involved in the life cycle of the measurement device (such as the manufacturer, logistics party, user, maintenance party, etc.) can construct their own blockchain based on their own physical hardware strength, or multiple parties that trust each other can cooperate to construct a blockchain including the node devices of these multiple parties. Or, relevant parties that do not have the need or strength to construct a blockchain can join the blockchain constructed by the relevant parties they trust.

[0111] Since each relevant party involved in the life cycle of the measurement device, such as the manufacturer, logistics party, user, maintenance party, etc., has the need to store the device status information of the measurement device in the blockchain and also has the need for information management based on the device status information stored in the blockchain, the data sender or data management party described in each embodiment of this specification can be any one of the relevant parties involved in the life cycle of the above measurement device.

[0112] Figure 1The process steps of an information management method for a measuring device provided by an exemplary embodiment of the present specification and executed by a node device in a first blockchain are illustrated, wherein the first blockchain stores a target evidence transaction sent by a data sender node device, and the target evidence transaction includes device status information of the measuring device.

[0113] This specification does not limit the specific type of measuring equipment. Equipment, devices or equipment and device modules that can perform measurement or calibration functions can be included in the scope of the measuring equipment described in this specification.

[0114] The life cycle of a measuring device includes multiple stages from the production to the retirement of the measuring device, such as the production stage, logistics stage, installation stage, use stage, maintenance stage, etc., or a combination of any of the above stages.

[0115] The equipment status information corresponding to the production stage of the measuring equipment may include: various production parameters recorded during the production process of the measuring equipment, such as the production date of the measuring equipment, production raw materials, production process, product serial number, production environment, production equipment parameters and other information data of various production links.

[0116] The equipment status information corresponding to the logistics stage of the measuring equipment may include information data generated by the measuring equipment during the circulation process after production, such as time and location information of entering and leaving the logistics station, environmental information along the way, abnormal logistics transit information, etc.; for more precise or expensive measuring equipment, the equipment status information in the logistics stage has a more important evidentiary significance in the traceability management of the measuring equipment.

[0117] Measuring equipment, especially large or precision measuring equipment, usually needs to be installed and debugged before being put into use. Therefore, the equipment status information corresponding to the installation phase of the measuring equipment may include calibration parameters required by the measuring equipment during the installation phase, or error probability parameters generated during the installation phase, installation status description, parameter backup or recovery information (such as factory setting parameters) and other data.

[0118] The equipment status information corresponding to the use stage of the measuring equipment may include any information data generated by the measuring equipment during use or required for reference (including images, temperature, three-dimensional dimensions, weight and other information collected by the measuring equipment), such as measurement data records generated by normal use, error information when an abnormality occurs (abnormal temperature, overload shock, etc.), measuring equipment operation information (which may include measuring equipment operator information, or operation location information, or operation time information, or operation content information, etc.), software information installed on the equipment, standard operating procedure (SOP) information data, etc.

[0119] The electronic seal information data of the measuring device is information data that reflects whether the measuring device has been subject to unknown unsealing, abnormal damage, or other behaviors. Therefore, the device status information corresponding to the usage stage may also include the electronic seal information data of the measuring device (or a specific component or module of the measuring device).

[0120] The performance index data of the measuring device also belongs to the device status information corresponding to the usage stage. Based on the specific type and attributes of the measuring device, the above device performance index data may include one or more of the following data: metrological performance index data, measurement accuracy index data, creep index data, measurement repeatability index data, operating environment index data, electromagnetic compatibility index data, etc.

[0121] When the measuring device is in use and operation, its operating status and measurement results are often affected by the operating environment. Therefore, the device status information corresponding to the usage node may also include device operating environment data, such as one or more of the following data: temperature, humidity, air pressure during device operation, load or load borne during device operation, impact received, inclination during device operation, etc.

[0122] The device status information corresponding to the maintenance stage of the measuring device may include any information data generated or referenced during the maintenance process of the measuring device, such as restoration data (factory setting data), fault detection program data, maintenance records, information of service personnel participating in the maintenance, maintenance time, identification of the maintenance device, and so on.

[0123] Therefore, in order to complete the blockchain storage of the device status information corresponding to each stage of the life cycle of the measuring device, the relevant parties corresponding to each stage of the life cycle of the measuring device: the manufacturer, the logistics party, the installer, the user, the maintenance party (usually the same as the installer) can all send target deposition transactions to the blockchain where they are located to store the above device status information.

[0124] It should be noted that in one or more embodiments provided in this specification, the above target deposition transaction may include device status information of one type or one life cycle stage, or may include device status information of multiple types or multiple life cycle stages; it may include the device status information of one measuring device, or may include the device status information of multiple devices; no limitation is made in this specification.

[0125] The above data sending party node device may be a computer device for managing the production, logistics, installation, use, or maintenance process of the measuring device, or a computer device communicatively connected to the measuring device, or the measuring device itself, and no limitation is made in this specification.

[0126] Further, in order to ensure the reliability and security of the status information of the device for uploading to the blockchain, the reliability of the measurement device of the data sender or the personnel of the information collection and sender can be enhanced based on authentication technology.

[0127] For example, when the personnel of the information collection and sender enter the relevant working area, they can be required to perform identity recognition and authentication. Specific identity recognition and authentication technologies can include pass identification, biological information recognition, etc. Or the identity authentication information of the relevant personnel of the information collection system (which can also be part of the above-mentioned target deposit and trading) can be uploaded to the above-mentioned first blockchain for storage.

[0128] Also, for the information that needs to be manually input by the data sender, it can only be used after being authenticated by an account and password. The data sender can develop an information collection system based on visual interfaces such as web pages, computers, or mobile APP clients, supporting various information input methods, such as scanning QR codes, image recognition, voice input, etc. The above-mentioned information collection system can also be docked with other information systems. The operator can input the corresponding information according to the item list displayed in the menu of other information systems, and the information can be input into the blockchain.

[0129] Also, when the measurement device is used as the above-mentioned data sender node device, the identity recognition information of the above-mentioned measurement device, such as physical information such as electronic seal codes, device models, device weights and dimensions (which can also be part of the above-mentioned target deposit and trading) can be sent to the blockchain for deposit. The first blockchain can also adopt a permission control strategy to only receive the target deposit transactions sent by the measurement devices that have passed the identity authentication.

[0130] When the target deposit transaction including the device status information of the measurement device is consensus-verified and passed by the node device of the first blockchain, the above-mentioned target deposit transaction is stored in the distributed database of the above-mentioned first blockchain. Any node device included in the first blockchain (including the data sender node device) can obtain the above-mentioned target deposit transaction from its backed-up first blockchain ledger.

[0131] Step 102, receiving a cross-chain management request from the data management party node device for the device status information of the measurement device stored in the first blockchain.

[0132] This specification does not limit the specific steps of the cross-chain interaction technology used to send the above-mentioned cross-chain management request.

[0133] In an illustrated embodiment, multiple blockchains can be cross-chain docked through a cross-chain relay device. The above-mentioned cross-chain relay device can be docked with multiple blockchains respectively through a bridging interface, and based on the implemented data transfer logic, complete the cross-chain data interaction between the multiple blockchains.

[0134] The cross-chain technology adopted in implementing the above cross-chain relay is not particularly limited in this specification. For example, in practical applications, multiple blockchains can be connected through cross-chain mechanisms such as side-chain technology and notary technology. After multiple blockchains are docked through cross-chain relay, the blockchains can read and authenticate data on other blockchains, and can also call smart contracts deployed on other blockchains through cross-chain relay.

[0135] It should be noted that cross-chain relay is only used to transfer data between multiple blockchains, and does not need to persistently store the transferred data, nor does it need to maintain the data state of the transferred data. In practical applications, cross-chain relay can be configured on devices, nodes, platforms, etc. outside the multiple blockchains it connects, or can also be configured on the node devices of the multiple blockchains it connects, which is not particularly limited in this specification.

[0136] In this embodiment, the above cross-chain management request is sent by the data management party node device to the node device of the first blockchain (including the data sender node device) through the cross-chain relay device. In particular, the above cross-chain relay device can be a common node device of the first blockchain and the second blockchain, and the data management party node device sends a management request for device status information to the node device of the first blockchain (including the data sender node device) by interacting with the common node device.

[0137] In another illustrated embodiment, the first blockchain and the second blockchain are different sub-chains belonging to the same consortium blockchain. The data management party node device belonging to the second blockchain can initiate a data management request to the first blockchain and send a cross-chain management request to the node device of the first blockchain based on the cross-chain data access mechanism setting of the consortium blockchain.

[0138] The specific request content of the above cross-chain management request is not limited in each embodiment provided in this specification. It can be a cross-chain data acquisition request to obtain the device status information of the measurement device stored in the first blockchain, or it can be a cross-chain data application request to implement application management of the above device status information in the node device of the first blockchain.

[0139] Step 104, in response to the cross-chain management request, verify whether the data management party has the management authority for the device status information of the measurement device.

[0140] The multi-chain system will set corresponding permission control mechanisms to manage management behaviors such as cross-chain data access or cross-chain data application of node devices in the system.

[0141] When the above first blockchain and second blockchain are different sub-chains belonging to the same consortium blockchain, based on the transaction read / write permission control mechanism of the consortium blockchain, the management permission of the data management party for the device installation information included in the target deposit transaction can be controlled by controlling the acquisition permission of the data management party node device for the target deposit transaction.

[0142] When the above first blockchain and second blockchain have no consortium relationship, upon application by the data management party node device through a cross-chain relay device, the management node (or data sending party node device) of the first blockchain can issue a digital certificate to the data management party with management permissions such as obtaining or applying device status information; when the data management party node device sends the above cross-chain management application to the management node (or data sending party node device) of the first blockchain through the cross-chain relay device, based on the digital certificate of the above data management party, it can be verified whether it has the management permission for the device status information.

[0143] In another illustrated embodiment, the first blockchain deploys a smart contract for managing the device status information, and the processing logic corresponding to the contract code of the smart contract includes a management permission verification logic;

[0144] Responding to the cross-chain access request, verifying whether the data management party has the management permission for the device status information of the measurement device includes:

[0145] Responding to the cross-chain access request, calling the management permission verification logic in the smart contract to verify whether the data management party has the management permission for the device status information of the measurement device.

[0146] Specifically, the process of verifying whether the data management party has the management permission for the device status information of the measurement device includes: verifying whether the public key corresponding to the data management party belongs to the user white list set by the smart contract and having the management permission for the device status information.

[0147] Step 106, if so, obtain the target deposit transaction sent by the data sending party node device to the first blockchain, and based on the target deposit transaction, perform the management of the device status information of the measurement device.

[0148] Based on the data storage settings of the first blockchain, the above target deposit transaction can be stored in the distributed ledger (such as a block) of the blockchain, or can be stored in the account storage space corresponding to the account of the above smart contract, which is not limited in this embodiment. For example, the smart contract can obtain the target deposit transaction based on the address (TXhash) of the target deposit transaction.

[0149] When the above cross-chain management request is a request for obtaining the device status information of the measurement device, the management of the device status information of the measurement device performed by the node device of the first blockchain is specifically manifested as: cross-chain sending the device status information of the measurement device to the node device of the data management party, so that the node device of the data management party performs further application of the device status information of the measurement device.

[0150] When the above cross-chain management request is an application management request for the device status information of the measurement device, in another illustrated embodiment, the processing logic corresponding to the contract code of the above smart contract further includes the management logic for the device status information; correspondingly, the management of the device status information of the measurement device performed by the node device of the first blockchain includes:

[0151] After verifying that the data management party has the management authority for the device status information of the measurement device, the node device of the first blockchain further calls the management logic for the device status information in the smart contract, obtains the target deposit transaction sent by the data sender node device to the first blockchain, and performs the management of the device status information of the measurement device based on the target deposit transaction.

[0152] The information management method for the measurement device provided by the above one or more embodiments not only decentralizes the storage of the device status information of the measurement device in the first blockchain to prevent tampering; but also manages the device status information based on the cross-chain information interaction technology of multiple blockchains, further enhancing the privacy and security of the device status information data and reducing the physical configuration requirements for the node devices on each blockchain. After obtaining the device status information, the node device of the data management party can not only perform application management of the above device status information locally on the node device of the data management party, but also call the smart contract deployed on the second blockchain and declaring the device status information management logic to quickly and fairly perform application management of the above device status information.

[0153] When the node device of the data management party of the second blockchain completes the management of the device status information of the measurement device through cross-chain call to the smart contract deployed on the first blockchain, compared with the centralized operation of the device status information management on the local of the node device of the data management party, the smart contract is called at any time in response to the cross-chain management request of the data management party, greatly improving the efficiency of the device status information management; and the smart contract execution has the advantages of low human intervention and decentralized authority, further increasing the fairness of the device status information management behavior.

[0154] As the measurement device circulates or is used, the content of the device status information stored in the distributed ledger of the first blockchain will continuously increase. Based on the status data of the measurement device, various analyses and applications of the device status information of the measurement device can be carried out. For example, big data analysis or artificial intelligence technology can be used for information analysis throughout the life cycle of the measurement device, or life cycle management content such as traceability tracking, usage calibration, seal status determination, and usage status diagnosis of the measurement device.

[0155] Those skilled in the art should know that, from the perspectives of the roles of the data sender and the data manager, the blockchain where the data sender is located is defined as the first blockchain, and the blockchain where the data manager is located is defined as the second blockchain; in actual use, a node device may act as both a data sender and a data manager. Therefore, the blockchain it belongs to is the first blockchain when it acts as a data sender and the second blockchain when it acts as a data manager.

[0156] Hereinafter, this specification will provide multiple implementation manners for information management of the measurement device based on the device status information included in the above-mentioned target evidence storage exchange.

[0157]

Information Query Management

[0158] From production to delivery to the user, a measurement device usually goes through links such as production, calibration, certification, and logistics. The device status information generated in these links will continuously be stored in the first blockchain where its corresponding data sender node device is located through different data sender node devices. For example, the production information recording node will send the raw material information (such as the material number) or production process information of the measurement device, the node responsible for calibrating the measurement device will send the initial calibration information of the measurement device, the measurement certification agency node will send the certification qualification information of the measurement device, and the logistics node will send the logistics circulation information of the measurement device.

[0159] Based on its own computer physical configuration and information security and privacy requirements, the above-mentioned production information recording node, the node responsible for calibrating the measurement device, the measurement certification agency node, and the logistics node can be within the same blockchain (i.e., the first blockchain described in the above-mentioned multiple implementation manners), or can be in multiple different blockchains (i.e., multiple first blockchains).

[0160] The measurement device user node device, as a data manager, can belong to the second blockchain system described in the above implementation manners; based on usage requirements, the measurement device user node device can initiate a cross-chain access request to the device status information stored in each of the above-mentioned first blockchains (as an implementation manner of the cross-chain management request).

[0161] For the convenience of the node devices of the above-mentioned first blockchains to query and retrieve the specific information requested by the node device of the measurement device user, the target deposit transactions stored in the above-mentioned first blockchains and the cross-chain access requests may include a unique identification code corresponding to the measurement device. Thus, after the node device of the first blockchain verifies that the measurement device user has the corresponding access permission (as an implementation method of the management permission), it retrieves based on the unique identification code of the measurement device and quickly sends the device status information requested for access across the chain to the node device of the measurement device user.

[0162] For example, the manufacturer, logistics agency, and measurement certification agency of the measurement device, as several parties that can trust each other, can build a blockchain (which can be used as the first blockchain) to store and share the status information of the measurement device. Before the measurement device is launched after development, it needs to pass relevant metrology regulations certification. Based on the measurement device information management method provided in the above embodiments of this specification, first, the manufacturer (as the data sender) configures the prototype of the measurement device that needs to be certified and sends the relevant configuration information to the first blockchain; then, the prototype to be certified is delivered to the third-party certification agency through logistics, and the logistics information generated during this process can also be uploaded to the above-mentioned first blockchain by the logistics agency (as the data sender). After receiving the measurement device prototype, the measurement certification agency conducts metrology regulations certification, and the certification result information of the measurement device can be uploaded to the above-mentioned first blockchain. The manufacturer node device in the first blockchain can query the certification information of the measurement device in real time and make relevant improvements and updates to the measurement device in a timely manner; when an enterprise purchases the measurement device, since the enterprise terminal may not be joined to the above-mentioned first blockchain but belongs to the second blockchain, the enterprise end node device can cross-chain access the certification result information stored in the first blockchain based on the measurement device information management method described in the above embodiments to identify the reliability and security of this measurement device.

[0163] Another example is that the first blockchain can also store the measurement device replication parameters sent by the measurement device manufacturer node device, so that the node device of the second blockchain can obtain the above device replication parameters after the cross-chain device replication application described in the above embodiments, thereby completing the replication of the measurement device.

[0164]

Managing the Calibration Information of Measurement Devices Based on Smart Contracts

[0165] During the use of the measurement device, the measurement device user needs to calibrate the measurement device regularly or as required based on the device management requirements. The first blockchain stores the calibration deposit transactions sent by the measurement device manufacturer or repairer, and the calibration deposit transactions include the latest calibration information of the measurement device; Figure 2Schematically shows the calibration information management process of a measurement device based on the measurement device management method provided in this specification. This process is executed by the node devices included in the first blockchain and includes:

[0166] Step 201: Receive a cross-chain calibration management request from the node device of the measurement device user (as the data management party) for the latest calibration information of the measurement device stored in the first blockchain. The above cross-chain calibration management request includes the existing calibration information of the measurement device and the smart contract address deployed in the first blockchain for calibration management.

[0167] Step 202: Invoke the management permission verification logic of the above smart contract for calibration management to verify whether the measurement device user has the management permission for the latest calibration information of the measurement device. If so, further invoke the calibration management logic of the above smart contract to obtain the above calibration deposit transaction, and based on the above calibration deposit transaction, judge whether the latest calibration information is the same as the existing calibration information.

[0168] Step 203: When the latest calibration information is the same as the existing calibration information, cross-chain send the prompt result that the calibration status of the measurement device is normal to the above measurement device user node device.

[0169] Step 204: When the latest calibration information is different from the existing calibration information, cross-chain send the latest calibration information to the above measurement device user node device so that the measurement device user can calibrate the measurement device based on the latest calibration information.

[0170] By initiating a cross-chain call to the smart contract deployed on the first blockchain through the node device of the data management party or the client installed on intelligent device terminals such as mobile phones, the calibration management of the measurement device can be automatically completed, saving the time and economic costs consumed by professional technicians for on-site calibration of the measurement device. Moreover, the operation results of the smart contract will be stored in the first blockchain in the form of transaction logs. Node devices of the first blockchain, such as measurement device manufacturers or repairers, can also accurately learn about the calibration status of the measurement device by listening to the operation results of the smart contract, so as to facilitate providing measurement device maintenance or repair suggestions for the measurement device user.

[0171]

Method for Managing Electronic Sealing Information of Measurement Devices Based on Smart Contracts

[0172] To ensure the safety or accuracy of the measuring device and prevent unauthorized opening or parameter changes of the measuring device, an electronic seal module is often set up to protect the measuring device. The electronic seal module (such as an RFID radio frequency chip) is configured with a unique seal identification code, which can correspond one-to-one with the identity identification such as the product serial number of the measuring device. In this embodiment, the first blockchain can store the seal identification code deposit transaction sent by the measuring device manufacturer or repairer, and this transaction includes the latest seal identification code of the measuring device.

[0173] Figure 3 Schematically shows the management process of the electronic seal information of the measuring device based on the measuring device management method provided in this specification. This process is executed by the node device included in the first blockchain and includes:

[0174] Step 301, receiving a cross-chain management request from the node device of the measuring device user or repairer (as the data management party) for the latest seal identification code of the measuring device stored in the first blockchain; the above cross-chain management request includes the existing seal identification code of the measuring device and the smart contract address deployed in the first blockchain for electronic seal information management;

[0175] Step 302, calling the management permission verification logic of the above-mentioned smart contract for electronic seal information management to verify whether the measuring device user or repairer has the management permission for the latest electronic seal code of the measuring device; if so, further calling the electronic seal information management logic of the above-mentioned smart contract to obtain the above-mentioned seal identification code deposit transaction; and based on the above-mentioned seal identification code deposit transaction, judging whether the latest seal identification code is the same as the existing seal identification code.

[0176] Step 303, if the latest seal identification code is the same as the existing seal identification code, cross-chain send the prompt result that the electronic seal status of the measuring device is normal to the above-mentioned measuring device user or repairer node device;

[0177] Step 304, if the latest seal identification code is different from the existing seal identification code, cross-chain send the latest seal identification code or a preset prompt or alarm information to the above-mentioned measuring device user or repairer node device, so that the measuring device user or repairer can know that the electronic seal status of the measuring device has undergone unauthorized changes.

[0178] By initiating a cross-chain call to the smart contract deployed on the first blockchain through the data management party node device or the client installed on intelligent device terminals such as mobile phones, the electronic seal information management of the measuring device can be automatically completed, saving the time and economic costs consumed by professional technicians for on-site comparison of the electronic seal codes of the measuring device. Moreover, the operation results of the smart contract will be stored in the first blockchain in the form of transaction logs. Node devices of the first blockchain, such as measuring device manufacturers or repairers, can also accurately learn the current electronic seal code status of the measuring device by listening to the operation results of the smart contract, so as to provide maintenance or repair suggestions for the measuring device users conveniently.

[0179]

Method for Managing Abnormal Status of Measuring Device

[0180] The manufacturer of the measuring device can build a manufacturer blockchain based on its own information security management requirements. As described in the above implementation manners, the above manufacturer blockchain may also include node devices such as logistics institutions, measuring device certification institutions, or repairers of the measuring device. The user of the measuring device can build a user blockchain (such as a private chain) based on its own information security management requirements, or join a multi-user blockchain formed by multiple measuring device users. The measuring device itself can also be used as a node device of the user blockchain and directly send the data information collected by the measuring device to the user blockchain during use.

[0181] Measuring devices are often equipped with various sensors to collect data signals or monitor the device usage environment status. During use, when the measuring device or the sensing module configured in the measuring device senses abnormal status information, such as abnormal temperature information, humidity information, shock information, etc., the above abnormal status information can be uploaded to the user blockchain where it is located in a transaction format, so as to perform blockchain evidence storage for the above abnormal status information.

[0182] When analyzing the faults of the measuring device, the manufacturer or repairer of the measuring device can initiate a cross-chain data access request to the user blockchain based on the information management method of the measuring device described in one or more of the above implementation manners. After the request permission is verified and passed, the abnormal status information cross-chain sent by the node device of the user blockchain can be received. In the above process, the user blockchain is the first blockchain described in the above implementation manners, and the manufacturer blockchain is the second blockchain described in the above implementation manners.

[0183] After obtaining the above abnormal status information, the manufacturer or repairer of the measuring device can perform preliminary probable fault analysis by performing big data analysis on these abnormal status information or combining relevant technologies such as artificial intelligence, and at the same time upload the above fault analysis results to the manufacturer blockchain.

[0184] After that, the node device of the measurement device user can initiate a cross-chain data access request to the manufacturer blockchain based on the information management method of the measurement device described in one or more of the above embodiments, and receive the fault analysis result information cross-chain sent by the node device of the manufacturer blockchain after the request permission is verified. In the above process, the manufacturer blockchain serves as the first blockchain described in the above embodiments, and the user blockchain is the second blockchain described in the above embodiments.

[0185] Through the above information management process, the user of the measurement device can obtain the analysis result (which may include coping strategies) of the abnormal fault of the measurement device without the presence of professional maintenance personnel; thus, it greatly saves the cost of fault analysis or maintenance of the measurement device by professional fault maintenance or analysis personnel on site.

[0186]

Software Version Upgrade Management Method for Measurement Devices Based on Smart Contracts

[0187] In another illustrated embodiment, the target deposit transaction stored in the first blockchain (such as the manufacturer blockchain) may include the latest software program corresponding to the measurement device and the version number of the latest software program, and a smart contract for software management of the measurement device is deployed inside the first blockchain.

[0188] The measurement device node in the second blockchain (such as the user blockchain) can regularly send a version management request to the first blockchain cross-chain. The version management request includes the version number of the current software program of the measurement device; after verifying that the measurement device has the preset version management permission, the smart contract obtains the target deposit transaction and compares the version number of the latest software program included in the target deposit transaction with the version number of the current software program; when the difference between the two version numbers reaches the preset level, it can send the latest software program to the measurement device node in the second blockchain cross-chain, so that the measurement device node performs software version upgrade.

[0189]

Measurement Result Verification Management Method for Measurement Devices Based on Smart Contracts

[0190] The information management method of the measurement device provided in this specification can also be used to store and verify measurement results. In another illustrated embodiment, the target deposit transaction stored in the first blockchain (such as the user blockchain) may include the first measurement result information obtained by the node device (as the data sender) of the first blockchain using a measurement device to measure a measurement object, and a smart contract for measurement result verification management of the measurement device is deployed inside the first blockchain.

[0191] Such as Figure 4As shown, the node devices in the second blockchain (such as another user blockchain) can use the same measurement device or the same type of measurement device to measure the same measurement object or the same type of measurement object to obtain the second measurement result information; and based on the above-mentioned second measurement result information, initiate a cross-chain measurement result management application to the node devices of the first blockchain to invoke the above-mentioned smart contract; after the smart contract verifies that the node devices of the second blockchain have the preset measurement result information management authority, obtain the above-mentioned target deposit transaction, and compare whether the first measurement result information and the second measurement result information included in the target deposit transaction are the same; when the first measurement result information and the second measurement result information are different, the first measurement result information, or a preset prompt or alarm operation, can be cross-chain sent to the above-mentioned node devices (as data management parties) in the second blockchain to prompt the node devices of the second blockchain that the measurement result of the measurement device they used for the measurement object is different from the measurement result of the same or similar measurement device used by other parties for the same measurement object or the same type of measurement object, so as to find the reason.

[0192]

Method for Managing Operation Information of Measurement Device Based on Smart Contract

[0193] The information management method of the measurement device provided in this specification can also be used to store and verify the operation information of the measurement device. In another illustrated embodiment, the target deposit transaction stored in the first blockchain (such as the above-mentioned user or manufacturer blockchain) may include the first device operation information when the node device (as the data sender) of the first blockchain uses a measurement device. The device operation information may include the input parameter range, temperature and humidity conditions, etc. of the operating device, and a smart contract for managing the operation information of the measurement device is deployed inside the first blockchain.

[0194] As Figure 5 shown, the node devices in the second blockchain (such as another user blockchain) can initiate a cross-chain measurement device operation information management application to the node devices of the first blockchain based on the second device operation information when using the same or the same type of measurement device to invoke the above-mentioned smart contract; after the smart contract verifies that the node devices of the second blockchain have the preset measurement device operation information management authority, obtain the above-mentioned target deposit transaction, and compare whether the first device operation information and the second device operation information included in the target deposit transaction are the same; when the first device operation information and the second device operation information are different, the first device operation information, or a preset prompt or alarm operation, can be cross-chain sent to the above-mentioned node devices (as data management parties) in the second blockchain to prompt the node devices of the second blockchain that the device operation information when they use the measurement device is different from the device operation information when other parties use the same or similar measurement device, so as to find the reason.

[0195] In particular, the above-mentioned first device operation information can be the operation information standard of the measuring device, which is sent to the first blockchain by the device manufacturer node device or the maintenance node device of the first blockchain for evidence storage; any device user of the second blockchain can, based on the cross-chain call of the above-mentioned smart contract, know whether its own operation of the measuring device meets the preset operation standard to improve the measurement accuracy.

[0196]

Electronic contract signing management method for measuring equipment

[0197] When the user of the measuring device purchases the measuring device from the manufacturer of the measuring device, it is usually necessary to sign a purchase contract. In another embodiment shown, the node device of the manufacturer of the measuring device belongs to the manufacturer blockchain described in the above embodiment, and the node device of the user of the measuring device belongs to the user blockchain described in the above embodiment.

[0198] The node device of the producer of the measuring device can send the electronic contract it signs to the manufacturer's blockchain where it is located; the node device of the user of the measuring device initiates a cross-chain access application to the above electronic contract, obtains the above electronic contract after the node device of the manufacturer's blockchain verifies that it has access rights to the above electronic contract, and sends the electronic contract signed by the user to the user's blockchain where it is located. At this time, the producer's node device can also initiate a cross-chain access application to the user's blockchain for the above electronic contract, and obtain the above electronic contract signed by both parties after the node device of the user's blockchain verifies that it has access rights to the above electronic contract.

[0199] Those skilled in the art may appreciate that the user of the measuring device may also sign an electronic contract first, and then obtain the electronic contract signed by both parties through two similar cross-chain access processes as described above.

[0200] The above-mentioned manufacturer blockchain and user blockchain can both be used as the first blockchain or the second blockchain to complete the signing process of the above-mentioned electronic contract; based on the blockchain's anti-tampering mechanism, the process nodes of the contract signing are stored as evidence.

[0201] Corresponding to the above-mentioned process implementation, the implementation method of this specification also provides an information management device 60 for the measuring device. The device 60 can be implemented by software, or by hardware or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, the CPU (Central Process Unit) of the device reads the corresponding computer program instructions into the memory and runs them. From the hardware level, in addition to Figure 7 In addition to the CPU, memory and storage shown, the device where the above-mentioned device is located usually also includes other hardware such as chips for sending and receiving wireless signals, and / or other hardware such as boards for realizing network communication functions.

[0202] As Figure 6 shown, this specification also provides an information management device 60 for a measurement device, which is applied to a network system including multiple blockchains. The network system includes a data sender node device and a data management node device; the data sender node device is a node device of the first blockchain, and the data management node device is a node device of the second blockchain; the first blockchain stores a target deposit transaction sent by the data sender node device, and the target deposit transaction includes the device status information of the measurement device; the device 60 is applied to the node device side of the first blockchain and includes:

[0203] A receiving unit 602, configured to receive a cross-chain management request from the data management node device for the device status information of the measurement device stored in the first blockchain;

[0204] A verification unit 604, configured to verify whether the data management party has the management authority for the device status information of the measurement device in response to the cross-chain management request;

[0205] An execution unit 606, configured to obtain the target deposit transaction and perform management on the device status information of the measurement device based on the target deposit transaction.

[0206] In another illustrated embodiment, the cross-chain management request is a request for cross-chain obtaining the device status information of the measurement device;

[0207] The execution unit 606 is further configured to:

[0208] Obtain the target deposit transaction and send the device status information of the measurement device cross-chain to the data management node device.

[0209] In another illustrated embodiment, a smart contract for managing the device status information is deployed on the first blockchain, and the processing logic corresponding to the contract code of the smart contract includes a management authority verification logic;

[0210] The verification unit 602 is further configured to:

[0211] In response to the cross-chain access request, call the management authority verification logic in the smart contract to verify whether the data management party has the management authority for the device status information of the measurement device.

[0212] In another illustrated embodiment, the processing logic corresponding to the contract code of the smart contract further includes a management logic for the device status information;

[0213] The execution unit 606 is further configured to:

[0214] After verifying that the data management party has the management authority for the device status information of the measurement device, further call the management logic for the device status information in the smart contract to obtain the target deposit transaction, and based on the target deposit transaction, execute the management of the device status information of the measurement device.

[0215] In another illustrated embodiment, the first blockchain and the second blockchain are different sub-chains belonging to the same consortium blockchain.

[0216] In another illustrated embodiment, the receiving unit 602 is further configured to:

[0217] Receive, through a cross-chain relay device, a cross-chain access request from the data management party node device for the device status information of the measurement device stored in the first blockchain.

[0218] In another illustrated embodiment, the data sender node device includes one or more of a production record node device of the measurement device, an initial calibration node device, a measurement certification agency node device, or a logistics agency node device;

[0219] The target deposit transaction includes a unique identification code corresponding to the measurement device; the device status information includes one or more of raw material information, production process information, initial calibration information, certification qualification information, logistics circulation information, or device replication parameters.

[0220] In another illustrated embodiment, the target deposit transaction includes the latest electronic lead seal code of the measurement device; the cross-chain management request includes the existing lead seal identification code of the measurement device;

[0221] The management logic for the device status information included in the processing logic corresponding to the contract code of the smart contract includes:

[0222] Step A, obtain the target deposit transaction;

[0223] Step B, based on the target deposit transaction, determine whether the latest lead seal identification code and the existing lead seal identification code are the same;

[0224] Step C, when the latest lead seal identification code and the existing lead seal identification code are different, send a preset prompt or alarm operation to the data management party node device across the chain.

[0225] In another illustrated embodiment, the target deposit transaction includes the latest calibration information of the measurement device; the cross-chain management request includes the existing calibration information of the measurement device;

[0226] The management logic for the device status information included in the processing logic corresponding to the contract code of the smart contract includes:

[0227] Step A, obtaining the target deposit transaction;

[0228] Step B, based on the target deposit transaction, determining whether the latest calibration information is the same as the existing calibration information;

[0229] Step C, when the latest calibration information is different from the existing calibration information, cross-chain sending the latest calibration information to the data management party node device, so that the data management party node device can calibrate the measurement device based on the latest calibration information.

[0230] In another illustrated embodiment, the target deposit transaction includes the latest software program corresponding to the measurement device and the version number of the latest software program; the data management party node device is the measurement device; the cross-chain management request includes the version number of the current software program of the measurement device;

[0231] The management logic for the device status information included in the processing logic corresponding to the contract code of the smart contract includes:

[0232] Step A, obtaining the target deposit transaction;

[0233] Step B, based on the target deposit transaction, comparing whether the difference between the version number of the latest software program and the version number of the current software program reaches a preset level;

[0234] Step C, if so, cross-chain sending the latest software program to the measurement device, so that the measurement device performs software version upgrade.

[0235] The specific implementation process of the functions and roles of each unit in the above device 60 can be specifically seen in the implementation process of the corresponding steps in the information management method of the measurement device executed by the node device of the above first blockchain. For the relevant parts, refer to the partial description of the method embodiment, and details will not be repeated here.

[0236] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical modules, that is, they may be located in one place or distributed to multiple network modules. Some or all of the units or modules can be selected according to actual needs to achieve the purpose of the solution in this specification. Those of ordinary skill in the art can understand and implement it without creative efforts.

[0237] The devices, units, and modules described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, and the specific form of the computer can be a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email transceiver, game console, tablet computer, wearable device, or a combination of any several of these devices.

[0238] Corresponding to the above method embodiments, the embodiments of this specification also provide a computer device, as Figure 7 shown, the computer device includes a memory and a processor. Among them, a computer program capable of being run by the processor is stored on the memory; when the processor runs the stored computer program, it executes each step of the information management method of the measurement device performed by the node device of the first blockchain in the embodiments of this specification. For a detailed description of each step of the information management method of the measurement device performed by the node device of the first blockchain, please refer to the previous content and will not be repeated.

[0239] Corresponding to the above method embodiments, the embodiments of this specification also provide a computer-readable storage medium, on which a computer program is stored, and when these computer programs are run by a processor, they execute each step of the information management method of the measurement device performed by the node device of the first blockchain in the embodiments of this specification. For a detailed description of each step of the information management method of the measurement device performed by the node device of the first blockchain, please refer to the previous content and will not be repeated.

[0240] The above are only the preferred embodiments of this specification and are not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of this specification shall be included within the scope of protection of this specification.

[0241] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0242] The memory may include non-permanent memory in the computer-readable medium, random access memory (RAM), and / or non-volatile memory in the form of, for example, read-only memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.

[0243] Computer-readable media include permanent and non-permanent, removable and non-removable media and can store information by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data.

[0244] Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0245] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0246] It will be appreciated by those skilled in the art that the embodiments of the present specification may be provided as methods, systems or computer program products. Therefore, the embodiments of the present specification may be implemented in the form of a complete hardware implementation, a complete software implementation or an implementation combining software and hardware. Moreover, the embodiments of the present specification may be implemented in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

Claims

1. An information management method for a measurement device, which is applied to a network system including multiple blockchains. The network system includes a data sender node device and a data management node device; the data sender node device is a node device of the first blockchain, and the data management node device is a node device of the second blockchain; the first blockchain stores a target deposit transaction sent by the data sender node device, and the target deposit transaction includes the device status information of the measurement device ； The method is executed by a node device of the first blockchain and includes: Receiving a cross-chain management request from the data management node device for the device status information of the measurement device stored in the first blockchain; In response to the cross-chain management request, verifying whether the data management party has the management authority for the device status information of the measurement device; If so, obtaining the target deposit transaction and, based on the target deposit transaction, performing management on the device status information of the measurement device; The first blockchain deploys a smart contract for managing the device status information, and the processing logic corresponding to the contract code of the smart contract includes a management authority verification logic; Responding to the cross-chain access request and verifying whether the data management party has the management authority for the device status information of the measurement device includes: In response to the cross-chain access request, calling the management authority verification logic in the smart contract to verify whether the data management party has the management authority for the device status information of the measurement device; The processing logic corresponding to the contract code of the smart contract further includes a management logic for the device status information; The obtaining the target deposit transaction and, based on the target deposit transaction, performing management on the device status information of the measurement device includes: After verifying that the data management party has the management authority for the device status information of the measurement device, further calling the management logic for the device status information in the smart contract, obtaining the target deposit transaction, and, based on the target deposit transaction, performing management on the device status information of the measurement device.

2. The method according to claim 1, wherein the cross-chain management request is a request for cross-chain obtaining the device status information of the measurement device; The performing management on the device status information of the measurement device includes: Cross-chain sending the device status information of the measurement device to the data management node device.

3. The method according to claim 1, wherein the first blockchain and the second blockchain are different sub-chains belonging to the same consortium chain.

4. The method according to claim 1, wherein the receiving the cross-chain access request from the data management node device for the device status information of the measurement device stored in the first blockchain includes: Receiving, through a cross-chain relay device, the cross-chain access request from the data management node device for the device status information of the measurement device stored in the first blockchain.

5. The method according to any one of claims 1 to 4, wherein the data sending party node device includes one or more of a production record node device of a measuring device, an initial calibration node device, a measurement certification agency node device, a logistics agency node device, a user node device, or a maintenance party node device; The target deposit transaction includes a unique identification code corresponding to the measuring device; the device status information includes one or more of raw material information, production process information, initial calibration information, certification qualification information, logistics circulation information, device replication parameters, abnormal status information, measurement data record information, maintenance record information, or electronic contract information related to the measuring device.

6. The method according to claim 1, wherein the target deposit transaction includes the latest electronic lead seal code of the measuring device; the cross-chain management request includes the existing lead seal identification code of the measuring device; The processing logic corresponding to the contract code of the smart contract includes a management logic for the device status information, including: Step A, obtaining the target deposit transaction; Step B, based on the target deposit transaction, determining whether the latest lead seal identification code is the same as the existing lead seal identification code; Step C, when the latest lead seal identification code is different from the existing lead seal identification code, cross-chain sending a preset prompt or alarm operation to the data management party node device.

7. The method according to claim 1, wherein the target deposit transaction includes the latest calibration information of the measuring device; the cross-chain management request includes the existing calibration information of the measuring device; The processing logic corresponding to the contract code of the smart contract includes a management logic for the device status information, including: Step A, obtaining the target deposit transaction; Step B, based on the target deposit transaction, determining whether the latest calibration information is the same as the existing calibration information; Step C, when the latest calibration information is different from the existing calibration information, cross-chain sending the latest calibration information to the data management party node device, so that the data management party node device can calibrate the measuring device based on the latest calibration information.

8. The method according to claim 1, wherein the target deposit transaction includes the latest software program corresponding to the measuring device and the version number of the latest software program; the data management party node device is the measuring device; the cross-chain management request includes the version number of the current software program of the measuring device; The processing logic corresponding to the contract code of the smart contract includes a management logic for the device status information, including: Step A, obtaining the target deposit transaction; Step B, based on the target deposit transaction, comparing whether the version number of the latest software program differs from the version number of the current software program by a preset number of levels; Step C, if so, cross-chain sending the latest software program to the measuring device, so that the measuring device performs a software version upgrade.

9. According to the method described in claim 1, the target deposit transaction includes the first measurement result information of the measurement device; the cross-chain management request includes the second measurement result information of the measurement device; The management logic for device measurement information included in the processing logic corresponding to the contract code of the smart contract includes: Step A, obtain the target deposit transaction; Step B, based on the target deposit transaction, compare whether the first measurement result information and the second measurement result information are the same; Step C, when the first measurement result information and the second measurement result information are different, cross-chain send to the data management party node device the first measurement result information, or a preset prompt or alarm operation.

10. According to the method described in claim 1, the target deposit transaction includes the first device operation information of the measurement device; the cross-chain management request includes the second device operation information of the measurement device; The management logic for the device operation information included in the processing logic corresponding to the contract code of the smart contract includes: Step A, obtain the target deposit transaction; Step B, based on the target deposit transaction, compare whether the first device operation information and the second device operation information are the same; Step C, when the first device operation information and the second device operation information are different, cross-chain send to the data management party node device the first device operation information or a preset prompt or alarm operation.

11. An information management device for a measurement device, applied to a network system including multiple blockchains, the network system including a data sender node device and a data management party node device; the data sender node device is a node device of the first blockchain, and the data management party node device is a node device of the second blockchain; the first blockchain stores a target deposit transaction sent by the data sender node device, and the target deposit transaction includes the device status information of the measurement device ； The device is applied to the node device side of the first blockchain and includes: A receiving unit, configured to receive a cross-chain management request from the data management party node device for the device status information of the measurement device stored in the first blockchain; A verification unit, configured to, in response to the cross-chain management request, verify whether the data management party has the management authority for the device status information of the measurement device; An execution unit, configured to obtain the target deposit transaction and, based on the target deposit transaction, execute the management of the device status information of the measurement device; The first blockchain deploys a smart contract for managing the device status information, and the processing logic corresponding to the contract code of the smart contract includes a management authority verification logic; The verification unit is further configured to: In response to the cross-chain access request, call the management authority verification logic in the smart contract to verify whether the data management party has the management authority for the device status information of the measurement device; The processing logic corresponding to the contract code of the smart contract further includes a management logic for the device status information; The execution unit is further configured to: After verifying that the data management party has the management authority for the device status information of the measurement device, further invoke the management logic for the device status information in the smart contract to obtain the target deposit transaction, and based on the target deposit transaction, perform the management of the device status information of the measurement device.

12. The device according to claim 11, wherein the cross-chain management request is a request for cross-chain obtaining the device status information of the measurement device; The execution unit is further configured to: Obtain the target deposit transaction, and cross-chain send the device status information of the measurement device to the data management party node device.

13. The device according to claim 11, wherein the first blockchain and the second blockchain are different sub-chains belonging to the same consortium chain.

14. The device according to claim 11, wherein the receiving unit is further configured to: Receive, through a cross-chain relay device, a cross-chain access request from the data management party node device for the device status information of the measurement device stored in the first blockchain.

15. The device according to any one of claims 11 to 14, wherein the data sender node device includes one or more of a production record node device of the measurement device, or an initial calibration node device, or a measurement certification agency node device, or a logistics agency node device, or a user node device, or a maintenance party node device; The target deposit transaction includes a unique identification code corresponding to the measurement device; the device status information includes one or more of raw material information, or production process information, or initial calibration information, or certification qualification information, or logistics circulation information, or device replication parameters, or abnormal status information, or measurement data record information, or maintenance record information, or electronic contract information related to the measurement device.

16. The device according to claim 11, wherein the target deposit transaction includes the latest electronic lead seal code of the measurement device; the cross-chain management request includes the existing lead seal identification code of the measurement device; The management logic for the device status information included in the processing logic corresponding to the contract code of the smart contract includes: Step A, obtain the target deposit transaction; Step B, based on the target deposit transaction, determine whether the latest lead seal identification code is the same as the existing lead seal identification code; Step C, when the latest lead seal identification code is different from the existing lead seal identification code, cross-chain send a preset prompt or alarm operation to the data management party node device.

17. The device according to claim 11, wherein the target deposit transaction includes the latest calibration information of the measurement device; the cross-chain management request includes the existing calibration information of the measurement device; The management logic for the device status information included in the processing logic corresponding to the contract code of the smart contract includes: Step A, obtain the target deposit transaction; Step B, based on the target deposit transaction, determine whether the latest calibration information is the same as the existing calibration information; Step C, when the latest calibration information is different from the existing calibration information, cross-chain send the latest calibration information to the data management party node device, so that the data management party node device can calibrate the measuring device based on the latest calibration information.

18. The device according to claim 11, wherein the target deposit transaction includes the latest software program corresponding to the measuring device and the version number of the latest software program; the data management party node device is the measuring device; the cross-chain management request includes the version number of the current software program of the measuring device; The management logic of the device status information included in the processing logic corresponding to the contract code of the smart contract includes: Step A, obtain the target deposit transaction; Step B, based on the target deposit transaction, compare whether the difference between the version number of the latest software program and the version number of the current software program reaches a preset level; Step C, if so, cross-chain send the latest software program to the measuring device, so that the measuring device performs software version upgrade.

19. The device according to claim 11, wherein the target deposit transaction includes the first measurement result information of the measuring device; the cross-chain management request includes the second measurement result information of the measuring device; The management logic of the device measurement information included in the processing logic corresponding to the contract code of the smart contract includes: Step A, obtain the target deposit transaction; Step B, based on the target deposit transaction, compare whether the first measurement result information is the same as the second measurement result information; Step C, when the first measurement result information is different from the second measurement result information, cross-chain send to the data management party node device the first measurement result information, or a preset prompt or alarm operation.

20. The device according to claim 11, wherein the target deposit transaction includes the first device operation information of the measuring device; the cross-chain management request includes the second device operation information of the measuring device; The management logic of the device operation information included in the processing logic corresponding to the contract code of the smart contract includes: Step A, obtain the target deposit transaction; Step B, based on the target deposit transaction, compare whether the first device operation information is the same as the second device operation information; Step C, when the first device operation information is different from the second device operation information, cross-chain send to the data management party node device the first device operation information, or a preset prompt or alarm operation.

21. A computer device comprising: a memory and a processor; a computer program that can be run by the processor is stored on the memory; when the processor runs the computer program, it executes the method according to any one of claims 1 to 10.

22. A computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 10 are implemented.

Images