A blockchain-based security management system for fire protection product data

Abstract

The application provides a kind of safety management system of fire-fighting product data based on blockchain, including data storage blockchain and data verification subsystem, when receiving product data to be verified, the data verification node that sends product data to be verified is determined as the first verification node;According to the number of upstream verification node, downstream verification node, same type verification node and second verification node corresponding to the first verification node, the verification coefficient corresponding to each data verification node is determined;Product data to be verified is sent to each data verification node except the first verification node, and the corresponding data verification confidence is obtained;According to each data verification confidence and its corresponding verification coefficient, the total verification confidence of product data to be verified is obtained;Product data to be verified and total verification confidence are stored in data storage blockchain, to ensure the security and authenticity of uploaded product data.

Description

Technical Field

[0001] The present invention relates to the field of fire protection product data management, and in particular to a blockchain-based security management system for fire protection product data. Background Art

[0002] During the production of fire protection products, data must be recorded at every stage of the production chain to ensure the safety of users and facilitate inspections by regulatory authorities. This allows for data traceability. Currently, this data is recorded through fire protection internet platforms or software. Users and manufacturers at various stages of production can exchange data on these platforms, but this data recording method is less secure and the authenticity of uploaded production data cannot be verified. Summary of the Invention

[0003] In view of the above technical problems, the technical solution adopted by the present invention is:

[0004] According to one aspect of the present application, a blockchain-based security management system for fire protection product data is provided, comprising a data storage blockchain and a data verification subsystem; the data verification subsystem is communicatively connected to the data storage blockchain; the data verification subsystem is connected to a plurality of data verification nodes, each data verification node corresponding to a product organization identifier, the product organization identifier being used to indicate the production organization to which the corresponding data verification node belongs in the production chain of the fire protection product;

[0005] The data verification subsystem described in this application is used to perform the following method:

[0006] Step S100: In response to receiving the product data to be verified, determining the data verification node that sent the product data to be verified as the first verification node;

[0007] Step S200: Determine, from among a plurality of data verification nodes, an upstream verification node and a downstream verification node corresponding to a first verification node based on a preset production organization relationship diagram; the production organization relationship diagram stores the association relationship between production organizations corresponding to each production link in the production chain of each fire protection product; the upstream verification node is a data verification node of a production organization corresponding to an upstream production link of the first verification node in the production chain of the fire protection product corresponding to the product data to be verified; the downstream verification node is a data verification node of a production organization corresponding to a downstream production link of the first verification node in the production chain of the fire protection product corresponding to the product data to be verified;

[0008] Step S300: Determine, based on the product organization identifiers of the plurality of data verification nodes, verification nodes of the same type as the first verification node and belonging to the same production organization as the first verification node;

[0009] Step S400: Determine a verification coefficient corresponding to each data verification node based on the number of upstream verification nodes, downstream verification nodes, verification nodes of the same type, and second verification nodes; the second verification node is the other data verification nodes among the plurality of data verification nodes, excluding the upstream verification nodes, downstream verification nodes, verification nodes of the same type, and the first verification node;

[0010] Step S500: Send the product data to be verified to each data verification node except the first verification node to obtain corresponding data verification confidence levels;

[0011] Step S600: Obtain the total verification confidence of the product data to be verified based on each data verification confidence and its corresponding verification coefficient;

[0012] Step S700: Store the product data to be verified and the total verification confidence in the data storage blockchain.

[0013] In an exemplary embodiment of the present application, the production organization relationship chart is determined by the following steps:

[0014] Step S201: Obtain the product identifications corresponding to several fire protection products produced by each data verification node during the historical period, and obtain a product identification list set A = (A1, A2, ..., A m ,...,A h );A m =(A m1 ,A m2 ,...,A mj ,...,A mk(m) ); where m = 1, 2, ..., h; h is the number of data verification nodes; A m is the product identification list corresponding to the mth data verification node; j = 1, 2, ..., k(m); k(m) is the number of fire protection products produced by the mth data verification node in the historical period; A mj The product ID corresponding to the j-th fire protection product produced by the m-th data verification node during the historical period;

[0015] Step S202: De-duplicate the product identification list set A to obtain several product identifications, and determine the de-duplicate product identification list B = (B1, B2, ..., B p ,...,B q ); where p = 1, 2, ..., q; q is the number of product identifiers obtained after deduplication; B p is the pth product ID obtained after deduplication;

[0016] Step S203, traverse the product identification list set A, if Am Including B p , then the mth data verification node is determined to be B p Corresponding product production nodes, to obtain several product production nodes corresponding to each product identifier;

[0017] Step S204: Obtain the product organization identifier corresponding to each product production node, and obtain a product organization identifier list set C = (C1, C2, ..., C p ,...,C q );C p =(C p1 ,C p2 ,...,C pn ,...,C pr(p) ); among them, C p is the product organization identification list corresponding to the p-th product identification; n=1,2,...,r(p); r(p) is the number of product production nodes corresponding to the p-th product identification; C pn The product organization identifier of the nth product production node corresponding to the pth product identifier;

[0018] Step S204: sorting the production node identifiers of the product production nodes corresponding to the multiple product organization identifiers in each product organization identifier list according to the preset production organization sequence corresponding to the multiple production links of the fire protection product, to obtain a corresponding multiple production node identifier list;

[0019] Step S205: Connecting multiple production node identifiers in each production node identifier list in sequence according to corresponding ranks to obtain a product organization relationship network of fire protection products corresponding to each product identifier;

[0020] Step S206: Integrate the product organization relationship networks of the q fire protection products to obtain a production organization relationship diagram.

[0021] In an exemplary embodiment of the present application, step S200 includes:

[0022] Step S210: Determine the fire protection product corresponding to the product data to be verified as the first fire protection product;

[0023] Step S220: Determine the product organization network corresponding to the first fire protection product in the production organization network diagram as the first product organization network;

[0024] Step S230: Determine the data verification node that is one rank before the first verification node in the first product organization relationship network as an upstream verification node;

[0025] Step S240: Determine a data verification node that is one rank behind the first verification node in the first product organization relationship network as a downstream verification node.

[0026] In an exemplary embodiment of the present application, step S300 includes:

[0027] Step S310: Obtain the product organization identifier corresponding to each data verification node except the first verification node, and obtain the first product organization identifier list D = (D1, D2, ..., D i ,...,D h-1 ); where i = 1, 2, ..., h-1; D i The product organization identifier corresponding to the i-th data verification node except the first verification node;

[0028] Step S320: traverse the first product organization identifier list D. If D i Same as D0, then D i The corresponding data verification node is determined to be a verification node of the same type; wherein D0 is the product organization identifier corresponding to the first verification node.

[0029] In an exemplary embodiment of the present application, step S400 includes:

[0030] Step S410: Determine the verification coefficient corresponding to the upstream verification node as u1 / ((h-1)×t1);

[0031] The verification coefficient corresponding to the downstream verification node is u2 / ((h-1)×t2);

[0032] The verification coefficient corresponding to the same type of verification node is u3 / ((h-1)×t3);

[0033] The verification coefficient corresponding to the second verification node is u4 / ((h-1)×t4);

[0034] Where t1 is the number of upstream verification nodes; t2 is the number of downstream verification nodes; t3 is the number of verification nodes of the same type; t4 is the number of second verification nodes; t1+t2+t3+t4=h-1;

[0035] u1 is the preset first verification index; u2 is the preset second verification index; u3 is the preset third verification index; u4 is the preset fourth verification index; u1+u2+u3+u4=h-1; u1>u2>u3>u4>0.

[0036] In an exemplary embodiment of the present application, step S500 includes:

[0037] Step S510, sending the product data to be verified to each data verification node except the first verification node, to obtain a direct data verification confidence of each data verification node verifying the product data to be verified according to the respective corresponding data verification rule, so as to determine a first data verification confidence list W=(W1, W2,..., W i ,...,W h-1 ); wherein W i is the direct data verification confidence of the i th data verification node except the first verification node verifying the product data to be verified;

[0038] Step S520, traversing the first data verification confidence list W, sending a verification result of a data verification of the product data to be verified by a data verification node of an upstream production link of the data verification node corresponding to W i to the data verification node corresponding to W i , to obtain an indirect data verification confidence of the data verification node corresponding to W i second verifying the verification result according to the corresponding data verification rule, so as to determine a second data verification confidence list Y=(Y1, Y2,..., Y i ,...,Y h-1 ); wherein Y i is the indirect data verification confidence of the second verification by the data verification node corresponding to W i .

[0039] Step S530, determining a target data verification confidence of each data verification node verifying the product data to be verified according to the first data verification confidence list W and the second data verification confidence list Y.

[0040] In an exemplary embodiment of the present application, step S530 comprises:

[0041] Step S531, determining a target data verification confidence list Z=(Z1, Z2,..., Z i ,...,Z h-1 ) according to the first data verification confidence list W and the second data verification confidence list Y; wherein Z i is the target data verification confidence of the data verification of the product data to be verified by the data verification node corresponding to W i ; Z i =(W i +Y i ) / 2.

[0042] In an exemplary embodiment of the present application, step S600 comprises:

[0043] Step S610: traverse the target data verification confidence list Z. If Z i The corresponding data verification node is the upstream verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u1 / ((h-1)×t1); if Z i The corresponding data verification node is the downstream verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u2 / ((h-1)×t2); if Z i If the corresponding data verification node is the same type of verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u3 / ((h-1)×t3); if Z i The corresponding data verification node is the second verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u4 / ((h-1)×t4);

[0044] Step S620: According to the data verification confidence and verification coefficient corresponding to each data verification node, the total verification confidence of the product data to be verified is determined as ∑ h-1 i＝1 (Z i ×T i ).

[0045] In an exemplary embodiment of the present application, step S700 includes:

[0046] Step S710: If the total verification confidence of the product data to be verified is greater than or equal to the preset verification confidence threshold, the product data to be verified and the total verification confidence are stored in the data storage blockchain.

[0047] In an exemplary embodiment of the present application, step S700 further includes:

[0048] Step S720: If the total verification confidence of the product data to be verified is less than the preset verification confidence threshold, an abnormal data identifier corresponding to the product data to be verified is generated, and the product data to be verified, the abnormal data identifier and the total verification confidence are stored in the data storage blockchain.

[0049] According to one aspect of the present application, a non-transitory computer-readable storage medium is provided, in which at least one instruction or at least one program is stored. The at least one instruction or the at least one program is loaded and executed by a processor to implement the method performed by the data verification subsystem included in the aforementioned blockchain-based fire product data safety management system.

[0050] According to one aspect of the present application, an electronic device is provided, including a processor and the aforementioned non-transitory computer-readable storage medium.

[0051] The present invention has at least the following beneficial effects:

[0052] The blockchain-based safety management system for fire protection product data of the present invention includes a data storage blockchain and a data verification subsystem. When the data verification subsystem receives the product data to be verified, it determines the data verification node that sends the product data to be verified as the first verification node, and determines the upstream verification node and the downstream verification node corresponding to the first verification node from a plurality of data verification nodes according to the production organization relationship diagram, and determines the same type of verification node of the production organization corresponding to the same production link as the first verification node according to the product organization identification of the plurality of data verification nodes, and determines the other data verification nodes after removing the upstream verification node, the downstream verification node, the same type verification node and the first verification node from the plurality of data verification nodes as the second verification node, and then determines the other data verification nodes after removing the upstream verification node, the downstream verification node, the same type verification node and the first verification node from the plurality of data verification nodes as the second verification node, and then determines the other data verification nodes according to the upstream verification node, the downstream verification node, the same type verification node and the product organization identification of the plurality of data verification nodes as the second verification node. The number of type verification nodes and second verification nodes is determined, and the verification coefficient corresponding to each data verification node is determined to determine the importance of verification of the product data to be verified by each data verification node, and then the product data to be verified is sent to each data verification node except the first verification node to obtain a corresponding number of data verification confidences to represent the verification results of the corresponding data verification nodes on the product data to be verified according to their respective verification rules. According to each data verification confidence and its corresponding verification coefficient, the total verification confidence of the product data to be verified is obtained, and the product data to be verified and the total verification confidence are stored in the data storage blockchain to ensure the security of the uploaded product data, and the product data is independently verified by data verification nodes of different organizational types to improve the authenticity of the uploaded product data. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0054] Figure 1 Schematic diagram of the method performed by the data verification subsystem included in the blockchain-based fire protection product data security management system provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0055] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making any creative efforts shall fall within the scope of protection of the present invention.

[0056] The blockchain-based security management system for fire protection product data described in this application is applied to a fire protection Internet platform or fire protection software, which includes a data storage blockchain and a data verification subsystem. The data verification subsystem is communicatively connected to the data storage blockchain. Several data verification nodes are connected to the data verification subsystem. Each data verification node corresponds to a product organization identifier, which is used to indicate the production organization to which the corresponding data verification node belongs in the production chain of fire protection products.

[0057] The data storage blockchain is used to store fire protection product data, which includes the production data of fire protection products. The production data includes the data of each production link in the production chain of fire protection products.

[0058] The data verification subsystem is used to verify and count the fire product data uploaded to the data storage blockchain, and upload the verification results obtained after statistics together with the fire product data to the data storage blockchain.

[0059] Each data verification node is connected to the data verification subsystem and the data storage blockchain. The data verification node is used to verify the fire product data to be uploaded to the data storage blockchain, and to view the fire product data that has been uploaded to the data storage blockchain. The production organization represented by the product organization identifier corresponding to each data verification node is the corresponding position of the manufacturer corresponding to the data verification node in the production chain of fire products. The production organization can be the provider of raw materials for fire products, the assembler of fire products, the manufacturer of fire products, etc.

[0060] Among them, such as Figure 1 As shown, the data verification subsystem described in this application is used to perform the following methods:

[0061] Step S100: In response to receiving the product data to be verified, determining the data verification node that sent the product data to be verified as the first verification node;

[0062] The product data to be verified is the fire product data to be uploaded to the data storage blockchain. Before uploading to the data storage blockchain, in order to ensure the authenticity of the uploaded data, the uploaded fire product data needs to be verified.

[0063] Step S200: Determine, from among a plurality of data verification nodes, an upstream verification node and a downstream verification node corresponding to a first verification node according to a preset production organization relationship diagram;

[0064] The production organization relationship diagram stores the association relationship between the production organizations corresponding to each production link in the production chain of each fire protection product, that is, the sequence of each production link in the production chain of each fire protection product, which is used to represent the complete production chain of fire protection products, making it easier to trace the production information of fire protection products in the future.

[0065] The upstream verification node is a data verification node of a production organization corresponding to the upstream production link of the first verification node in the production chain of the fire protection product corresponding to the product data to be verified.

[0066] The downstream verification node is a data verification node of a production organization corresponding to the downstream production link of the first verification node in the production chain of the fire protection product corresponding to the product data to be verified.

[0067] The production organization relationship chart is determined through steps S201 to S206:

[0068] Step S201: Obtain the product identifications corresponding to several fire protection products produced by each data verification node during the historical period, and obtain a product identification list set A = (A1, A2, ..., A m ,...,A h );A m =(A m1 ,A m2 ,...,A mj ,...,A mk(m) ); where m = 1, 2, ..., h; h is the number of data verification nodes; A m is the product identification list corresponding to the mth data verification node; j = 1, 2, ..., k(m); k(m) is the number of fire protection products produced by the mth data verification node in the historical period; A mj The product ID corresponding to the j-th fire protection product produced by the m-th data verification node during the historical period;

[0069] Step S202: De-duplicate the product identification list set A to obtain several product identifications, and determine the de-duplicate product identification list B = (B1, B2, ..., B p ,...,B q ); where p = 1, 2, ..., q; q is the number of product identifiers obtained after deduplication; B p is the pth product ID obtained after deduplication;

[0070] The p product identifiers after deduplication correspond to all fire-fighting products produced by all data verification nodes in the historical period.

[0071] Step S203, traversing the product identifier list set A, if A m includes B p , the mth data verification node is determined as the B p corresponding product production node, to obtain a plurality of product production nodes corresponding to each product identifier;

[0072] Step S204, obtaining the product organization identifier corresponding to each product production node, to obtain the product organization identifier list set C=(C1, C2,..., C p ,...,C q ); C p =(C p1 ,C p2 ,...,C pn ,...,C pr(p) ); wherein C p is the product organization identifier list corresponding to the pth product identifier; n=1, 2,..., r(p); r(p) is the number of product production nodes corresponding to the pth product identifier; C pn is the product organization identifier of the nth product production node corresponding to the pth product identifier.

[0073] Step S204, according to the order of the production organization corresponding to the plurality of production links of the fire-fighting product, the production node identifiers of the plurality of product production nodes corresponding to the plurality of product organization identifiers in each product organization identifier list are sorted to obtain a plurality of production node identifier lists corresponding thereto.

[0074] Step S205, sequentially connecting the plurality of production node identifiers in each production node identifier list according to the corresponding rank to obtain the product organization relationship network of the fire-fighting product corresponding to each product identifier.

[0075] The plurality of production node identifiers in each production node identifier list are sorted according to the positions of the respective production links on the production chain of the corresponding fire-fighting product, i.e. the production link with low rank is the previous production step of the production link with high rank.

[0076] Step S206, integrating the product organization relationship networks of the q fire-fighting products to obtain the production organization relationship diagram.

[0077] Further, step S200 includes steps S210-S240:

[0078] Step S210, determining the fire-fighting product corresponding to the to-be-verified product data as the first fire-fighting product;

[0079] Step S220: Determine the product organization network corresponding to the first fire protection product in the production organization network diagram as the first product organization network;

[0080] The first product organizational relationship network includes the sequential relationship of each production link in the production chain corresponding to the first fire protection product.

[0081] Step S230: Determine the data verification node that is one rank before the first verification node in the first product organization relationship network as an upstream verification node;

[0082] The upstream verification node is a data verification node corresponding to the preceding production step of the first verification node.

[0083] Step S240: Determine a data verification node that is one rank behind the first verification node in the first product organization relationship network as a downstream verification node.

[0084] The downstream verification node is a data verification node corresponding to a subsequent production step of the first verification node.

[0085] Step S300: Determine, based on the product organization identifiers of the plurality of data verification nodes, verification nodes of the same type as the first verification node and belonging to the same production organization as the first verification node;

[0086] The same type of verification node is a data verification node with the same production link as the first verification node.

[0087] Furthermore, step S300 includes steps S310 to S320:

[0088] Step S310: Obtain the product organization identifier corresponding to each data verification node except the first verification node, and obtain the first product organization identifier list D = (D1, D2, ..., D i ,...,D h-1 ); where i = 1, 2, ..., h-1; D i The product organization identifier corresponding to the i-th data verification node except the first verification node;

[0089] Step S320: traverse the first product organization identifier list D. If D i Same as D0, then D i The corresponding data verification node is determined to be a verification node of the same type; wherein D0 is the product organization identifier corresponding to the first verification node.

[0090] Step S400: Determine the verification coefficient corresponding to each data verification node based on the number of upstream verification nodes, downstream verification nodes, verification nodes of the same type, and second verification nodes;

[0091] The second verification node is other data verification nodes among the data verification nodes, excluding the upstream verification node, the downstream verification node, the same type verification node and the first verification node.

[0092] Further, step S400 includes step S410:

[0093] Step S410: Determine the verification coefficient corresponding to the upstream verification node as u1 / ((h-1)×t1);

[0094] The verification coefficient corresponding to the downstream verification node is u2 / ((h-1)×t2);

[0095] The verification coefficient corresponding to the same type of verification node is u3 / ((h-1)×t3);

[0096] The verification coefficient corresponding to the second verification node is u4 / ((h-1)×t4);

[0097] Where t1 is the number of upstream verification nodes; t2 is the number of downstream verification nodes; t3 is the number of verification nodes of the same type; t4 is the number of second verification nodes; t1+t2+t3+t4=h-1;

[0098] u1 is the preset first verification index; u2 is the preset second verification index; u3 is the preset third verification index; u4 is the preset fourth verification index; u1+u2+u3+u4=h-1; u1>u2>u3>u4>0.

[0099] In the production chain of fire protection products, the data verification nodes in the previous steps have greater credibility and accuracy in verifying the product data to be verified than the data verification nodes in the subsequent steps, followed by the same type of verification nodes and the second verification nodes. Therefore, different data verification nodes are classified and verified, and the verification coefficient corresponding to each type of data verification node is determined according to the number of data verification nodes of each type, so that the verification results obtained from the subsequent verification of the product data to be verified will be more accurate.

[0100] Step S500: Send the product data to be verified to each data verification node except the first verification node to obtain corresponding data verification confidence levels;

[0101] Furthermore, step S500 includes steps S510 to S530:

[0102] Step S510: Send the product data to be verified to each data verification node except the first verification node, and obtain the direct data verification confidence of each data verification node for verifying the product data according to its corresponding data verification rules, so as to determine the first data verification confidence list W = (W1, W2, ..., W i ,...,W h-1 ); where W i is the direct data verification confidence obtained by the i-th data verification node other than the first verification node for verifying the product data to be verified;

[0103] Each data verification node has its own corresponding data verification rules, which are preset for the data verification node or obtained based on historical verification results, and will not be repeated here.

[0104] Step S520: traverse the first data verification confidence list W and set W i The data verification node in the upstream production link of the corresponding data verification node verifies the data of the product to be verified and sends the verification result to W i In the corresponding data verification node, we get W i The corresponding data verification node performs secondary verification on the verification result according to the corresponding data verification rule to determine the second data verification confidence list Y=(Y1, Y2, ..., Y i ,...,Y h-1 ); where Y i W i The confidence level of indirect data verification obtained by secondary verification of the corresponding data verification node;

[0105] In order to further improve the credibility of data verification, it is necessary to conduct a secondary verification of the verification results, that is, to conduct a secondary verification of the verification results of the corresponding data verification nodes in the previous production link through the corresponding data verification nodes in the subsequent production link connected in sequence, so as to determine the accuracy of the verification of the product data to be verified by the corresponding data verification nodes in the previous production link.

[0106] Step S530: Determine the target data verification confidence level for each data verification node to perform data verification on the product data to be verified based on the first data verification confidence level list W and the second data verification confidence level list Y.

[0107] Wherein, step S530 includes step S531:

[0108] Step S531: Determine the target data verification confidence list Z = (Z1, Z2, ..., Z i ,...,Zh-1 ); where Z i W i The corresponding data verification node performs data verification on the target data of the product to be verified; Z i =(W i +Y i ) / 2.

[0109] Step S600: Obtain the total verification confidence of the product data to be verified based on each data verification confidence and its corresponding verification coefficient;

[0110] Furthermore, step S600 includes steps S610 to S620:

[0111] Step S610: traverse the target data verification confidence list Z. If Z i The corresponding data verification node is the upstream verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u1 / ((h-1)×t1); if Z i The corresponding data verification node is the downstream verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u2 / ((h-1)×t2); if Z i If the corresponding data verification node is the same type of verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u3 / ((h-1)×t3); if Z i The corresponding data verification node is the second verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u4 / ((h-1)×t4);

[0112] Step S620: According to the data verification confidence and verification coefficient corresponding to each data verification node, the total verification confidence of the product data to be verified is determined as ∑ h-1 i＝1 (Z i ×T i ).

[0113] Step S700: Store the product data to be verified and the total verification confidence in the data storage blockchain;

[0114] Furthermore, step S700 includes steps S710 to S720:

[0115] Step S710: If the total verification confidence of the product data to be verified is greater than or equal to the preset verification confidence threshold, the product data to be verified and the total verification confidence are stored in the data storage blockchain;

[0116] Step S720: If the total verification confidence of the product data to be verified is less than the preset verification confidence threshold, an abnormal data identifier corresponding to the product data to be verified is generated, and the product data to be verified, the abnormal data identifier and the total verification confidence are stored in the data storage blockchain.

[0117] The blockchain-based safety management system for fire protection product data of the present invention includes a data storage blockchain and a data verification subsystem. When the data verification subsystem receives the product data to be verified, it determines the data verification node that sends the product data to be verified as the first verification node, and determines the upstream verification node and the downstream verification node corresponding to the first verification node from a plurality of data verification nodes according to the production organization relationship diagram, and determines the same type of verification node of the production organization corresponding to the same production link as the first verification node according to the product organization identification of the plurality of data verification nodes, and determines the other data verification nodes after removing the upstream verification node, the downstream verification node, the same type verification node and the first verification node from the plurality of data verification nodes as the second verification node, and then determines the other data verification nodes after removing the upstream verification node, the downstream verification node, the same type verification node and the first verification node from the plurality of data verification nodes as the second verification node, and then determines the other data verification nodes according to the upstream verification node, the downstream verification node, the same type verification node and the product organization identification of the plurality of data verification nodes as the second verification node. The number of type verification nodes and second verification nodes is determined, and the verification coefficient corresponding to each data verification node is determined to determine the importance of verification of the product data to be verified by each data verification node, and then the product data to be verified is sent to each data verification node except the first verification node to obtain a corresponding number of data verification confidences to represent the verification results of the corresponding data verification nodes on the product data to be verified according to their respective verification rules. According to each data verification confidence and its corresponding verification coefficient, the total verification confidence of the product data to be verified is obtained, and the product data to be verified and the total verification confidence are stored in the data storage blockchain to ensure the security of the uploaded product data, and the product data is independently verified by data verification nodes of different organizational types to improve the authenticity of the uploaded product data.

[0118] An embodiment of the present invention further provides a computer program product comprising program code. When the program product is run on an electronic device, the program code is used to enable the electronic device to execute the steps of the method according to various exemplary embodiments of the present invention described above in this specification.

[0119] Moreover, although individual steps of the methods in the present disclosure are described in a particular order in the figures, this is not required or implied as to the order of execution of the steps, nor is it required that all of the steps be performed to achieve the desired result. Additionally or alternatively, certain steps can be omitted, combined into a single step, broken into multiple steps, and / or the like.

[0120] Through the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described herein can be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, a U disk, a mobile hard disk, etc.) or a network, and includes a plurality of instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the methods according to the embodiments of the present disclosure.

[0121] In the example embodiments of the present disclosure, an electronic device capable of implementing the above method is also provided.

[0122] Those skilled in the art can understand that each aspect of the present disclosure can be implemented as a system, a method or a program product. Therefore, each aspect of the present disclosure can be embodied in the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.), or an embodiment combining hardware and software aspects, which can be collectively referred to as "circuitry", "module" or "system".

[0123] The electronic device according to this embodiment of the present disclosure. The electronic device is merely an example, and should not impose any limitation on the functions and use range of the embodiments of the present disclosure.

[0124] The electronic device is in the form of a general computing device. The components of the electronic device can include, but are not limited to, the at least one processor described above, the at least one storage described above, and a bus connecting different system components, including the storage and the processor.

[0125] The storage stores program code that can be executed by the processor, so that the processor performs the steps according to various example embodiments of the present disclosure described in the "example method" section of the present specification.

[0126] The storage can include a readable medium in the form of a volatile storage, such as a random access memory (RAM) and / or a cache memory, and can further include a read-only memory (ROM).

[0127] The storage may also include a program / utility having a set (at least one) of program modules, such program modules including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0128] The bus may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures.

[0129] The electronic device may also communicate with one or more external devices (e.g., a keyboard, a pointing device, a Bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device, and / or any device that enables the electronic device to communicate with one or more other computing devices (e.g., a router, a modem, etc.). Such communication may be performed via an input / output (I / O) interface. Furthermore, the electronic device may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter.

[0130] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

[0131] In exemplary embodiments of the present disclosure, a computer-readable storage medium is also provided, on which is stored a program product capable of implementing the aforementioned methods of this specification. In some possible implementations, various aspects of the present invention may also be implemented in the form of a program product comprising program code. When the program product is executed on a terminal device, the program code is configured to cause the terminal device to execute the steps according to various exemplary embodiments of the present invention described in the "Exemplary Methods" section of this specification.

[0132] The program product may be implemented in any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0133] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0134] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0135] The program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, and the like, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a stand-alone software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0136] Furthermore, the above-described figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention and are not intended to be limiting. It is readily understood that the processes illustrated in the above-described figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0137] It should be noted that although several modules or units of the device for action execution are mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be concretized in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0138] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A blockchain-based security management system for fire protection product data, characterized in that: It includes a data storage blockchain and a data verification subsystem; the data verification subsystem is in communication with the data storage blockchain; the data verification subsystem is connected to a plurality of data verification nodes, each of which corresponds to a product organization identifier, and the product organization identifier is used to indicate the production organization to which the corresponding data verification node belongs in the production chain of fire protection products; The data verification subsystem is used to perform the following methods: Step S100: In response to receiving product data to be verified, determining a data verification node that sends the product data to be verified as a first verification node; Step S200: Determine, from among several data verification nodes, an upstream verification node and a downstream verification node corresponding to the first verification node based on a preset production organization relationship diagram; the production organization relationship diagram stores the association relationship between production organizations corresponding to each production link in the production chain of each fire protection product; the upstream verification node is a data verification node of a production organization corresponding to an upstream production link of the first verification node in the production chain of the fire protection product corresponding to the product data to be verified; the downstream verification node is a data verification node of a production organization corresponding to a downstream production link of the first verification node in the production chain of the fire protection product corresponding to the product data to be verified; Step S300: Determine, based on the product organization identifiers of the plurality of data verification nodes, verification nodes of the same type as the first verification node and belonging to the same production organization as the first verification node; Step S400: Determine a verification coefficient corresponding to each of the data verification nodes based on the number of the upstream verification nodes, the downstream verification nodes, the verification nodes of the same type, and the second verification nodes; the second verification nodes are the other data verification nodes among the data verification nodes, excluding the upstream verification nodes, the downstream verification nodes, the verification nodes of the same type, and the first verification node; Step S500: sending the product data to be verified to each of the data verification nodes except the first verification node to obtain corresponding data verification confidences; Step S600: Obtaining the total verification confidence of the product data to be verified based on each data verification confidence and its corresponding verification coefficient; Step S700: Store the product data to be verified and the total verification confidence in the data storage blockchain.

2. The blockchain-based fire protection product data security management system according to claim 1 is characterized in that: The production organization relationship diagram is determined by the following steps: Step S201: Obtain product identifications corresponding to several fire protection products produced by each data verification node during a historical period, and obtain a product identification list set A = (A1, A2, ..., A m ,...,A h );A m =(A m1 ,A m2 ,...,A mj ,...,A mk(m) ); where m = 1, 2, ..., h; h is the number of data verification nodes; A m is a list of product identifiers corresponding to the mth data verification node; j = 1, 2, ..., k(m); k(m) is the number of fire protection products produced by the mth data verification node in the historical period; A mj The product identifier corresponding to the j-th fire protection product produced by the m-th data verification node during the historical period; Step S202: De-duplicate the product identification list set A to obtain a number of product identifications, and determine a de-duplicate product identification list B = (B1, B2, ..., B p ,...,B q ); where p = 1, 2, ..., q; q is the number of product identifiers obtained after deduplication; B p is the pth product ID obtained after deduplication; Step S203, traverse the product identification list set A, if A m Including B p , then the mth data verification node is determined to be B p Corresponding product production nodes, to obtain several product production nodes corresponding to each product identifier; Step S204: Obtain the product organization identifier corresponding to each product production node, and obtain a product organization identifier list set C = (C1, C2, ..., C p ,...,C q );C p =(C p1 ,C p2 ,...,C pn ,...,C pr(p) ); among them, C p is the product organization identification list corresponding to the p-th product identification; n=1,2,...,r(p); r(p) is the number of product production nodes corresponding to the p-th product identification; C pn The product organization identifier of the nth product production node corresponding to the pth product identifier; Step S204: sorting the production node identifiers of the product production nodes corresponding to the multiple product organization identifiers in each of the product organization identifier lists according to the preset production organization sequence corresponding to the multiple production links of the fire protection product, to obtain a corresponding multiple production node identifier list; Step S205: Connecting the multiple production node identifiers in each of the production node identifier lists in sequence according to corresponding ranks to obtain a product organization relationship network of the fire protection products corresponding to each product identifier; Step S206: Integrate the product organization relationship networks of the q fire protection products to obtain a production organization relationship diagram.

3. The blockchain-based fire protection product data security management system according to claim 2 is characterized in that: The step S200 includes: Step S210: Determine the fire protection product corresponding to the product data to be verified as a first fire protection product; Step S220: Determine the product organization network corresponding to the first fire protection product in the production organization network as the first product organization network; Step S230: Determine the data verification node that is one rank before the first verification node in the first product organization relationship network as an upstream verification node; Step S240: Determine a data verification node that is one rank behind the first verification node in the first product organization relationship network as a downstream verification node.

4. The blockchain-based fire protection product data security management system according to claim 3 is characterized in that: The step S300 includes: Step S310: Obtain the product organization identifier corresponding to each of the data verification nodes except the first verification node, and obtain a first product organization identifier list D=(D1, D2, ..., D i ,...,D h-1 ); where i = 1, 2, ..., h-1; D i The product organization identifier corresponding to the i-th data verification node except the first verification node; Step S320: traverse the first product organization identifier list D. If D i Same as D0, then D i The corresponding data verification node is determined to be a verification node of the same type; wherein D0 is the product organization identifier corresponding to the first verification node.

5. The blockchain-based fire protection product data security management system according to claim 4 is characterized in that: The step S400 includes: Step S410: Determine the verification coefficient corresponding to the upstream verification node as u1 / ((h-1)×t1); The verification coefficient corresponding to the downstream verification node is u2 / ((h-1)×t2); The verification coefficient corresponding to the verification node of the same type is u3 / ((h-1)×t3); The verification coefficient corresponding to the second verification node is u4 / ((h-1)×t4); Where t1 is the number of upstream verification nodes; t2 is the number of downstream verification nodes; t3 is the number of verification nodes of the same type; t4 is the number of the second verification nodes; t1+t2+t3+t4=h-1; u1 is the preset first verification index; u2 is the preset second verification index; u3 is the preset third verification index; u4 is the preset fourth verification index; u1+u2+u3+u4=h-1; u1>u2>u3>u4>0.

6. The blockchain-based fire protection product data security management system according to claim 5 is characterized in that: The step S500 includes: Step S510: Send the product data to be verified to each of the data verification nodes except the first verification node, and obtain the direct data verification confidence of each data verification node verifying the product data to be verified according to its corresponding data verification rules, so as to determine the first data verification confidence list W = (W1, W2, ..., W i ,...,W h-1 ); where W i is the direct data verification confidence obtained by the i-th data verification node other than the first verification node verifying the product data to be verified; Step S520: traverse the first data verification confidence list W and set W i The data verification node in the upstream production link of the corresponding data verification node performs data verification on the product data to be verified and sends the verification result to W i In the corresponding data verification node, we get W i The corresponding data verification node performs secondary verification on the verification result according to the corresponding data verification rule to determine the second data verification confidence list Y=(Y1, Y2, ..., Y i ,...,Y h-1 ); where Y i W i The confidence level of indirect data verification obtained by secondary verification of the corresponding data verification node; Step S530: Determine the target data verification confidence level for each data verification node to verify the product data to be verified based on the first data verification confidence level list W and the second data verification confidence level list Y.

7. The blockchain-based fire protection product data security management system according to claim 6 is characterized in that: The step S530 includes: Step S531: Determine the target data verification confidence list Z=(Z1, Z2, ..., Z i ,...,Z h-1 ); where Z i W i The target data verification confidence level of the corresponding data verification node for verifying the product data to be verified; Z i =(W i +Y i ) / 2.

8. The blockchain-based fire protection product data security management system according to claim 7 is characterized in that: The step S600 includes: Step S610: traverse the target data verification confidence list Z. If Z i The corresponding data verification node is the upstream verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u1 / ((h-1)×t1); if Z i The corresponding data verification node is the downstream verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u2 / ((h-1)×t2); if Z i If the corresponding data verification node is the same type of verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u3 / ((h-1)×t3); if Z i The corresponding data verification node is the second verification node, then Z i The verification coefficient T of the corresponding data verification node i Determined as u4 / ((h-1)×t4); Step S620: Determine the total verification confidence of the product data to be verified as ∑ h-1 i＝1 (Z i ×T i ).

9. The blockchain-based fire protection product data security management system according to claim 8 is characterized in that: The step S700 includes: Step S710: If the total verification confidence of the product data to be verified is greater than or equal to a preset verification confidence threshold, the product data to be verified and the total verification confidence are stored in the data storage blockchain.

10. The blockchain-based fire protection product data security management system according to claim 9 is characterized in that: The step S700 further includes: Step S720: If the total verification confidence of the product data to be verified is less than a preset verification confidence threshold, an abnormal data identifier corresponding to the product data to be verified is generated, and the product data to be verified, the abnormal data identifier and the total verification confidence are stored in the data storage blockchain.

Images