A cross-domain heterogeneous data security management and control method

Through blockchain technology, the data security is determined using domain identification and collection object identification, which solves the problem of cross-domain heterogeneous data security management and realizes the security control and alarm mechanism of cross-domain data.

CN112069534BActive Publication Date: 2024-11-15YANGZHOU ZHIHUI INTERNET INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010774716.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-08-04
Publication Date
2024-11-15
Estimated Expiration
2040-08-04

AI Technical Summary

Technical Problem

How to effectively manage and control the security of cross-domain heterogeneous data, especially when the data volume is large and the structural differences are large.

Method used

The security of data is determined through a pre-established blockchain using domain identification and collection object identification. Blocks in the blockchain are uniquely identified by domain identification, and nodes are uniquely identified by collection object identification. If the data is not secure, Make an alarm.

Benefits of technology

It realizes security control of cross-domain heterogeneous data, ensures the security of data between different domains and collection objects, and prevents data leakage and unauthorized access.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112069534B_ABST
    Figure CN112069534B_ABST
Patent Text Reader

Abstract

The present invention relates to a method for cross-domain heterogeneous data security management and control, the method comprising: obtaining the domain identifier of the data to be controlled, the collection object identifier of the data to be controlled, and the data structure of the data to be controlled; based on the domain identifier of the data to be controlled, the collection object identifier of the data to be controlled, and the data structure of the data to be controlled, determining whether the data to be controlled is safe through a pre-established blockchain; the block in the blockchain uses the domain identifier as a unique identifier, and the node in the block uses the collection object identifier as a unique identifier; if it is not safe, an alarm is issued. The method provided by the present invention can perform security management and control on cross-domain heterogeneous data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a cross-domain heterogeneous data security management and control method. Background Art

[0002] In recent years, with the rapid development of science and technology and the advancement of informatization, the amount of data accumulated by human society has greatly increased, and the amount of data collection, storage, processing and dissemination has also increased day by day. At the same time, with the development of business and the construction of systems, the amount of data is also increasing, and the structural differences are becoming greater and greater. How to control the security of cross-domain heterogeneous data has become a more concerned issue at present. Summary of the invention

[0003] 1. Technical issues to be resolved

[0004] In order to solve the above problems, the present invention provides a cross-domain heterogeneous data security management and control method.

[0005] (II) Technical solution

[0006] In order to achieve the above object, the main technical solutions adopted by the present invention include:

[0007] A cross-domain heterogeneous data security management and control method, the method comprising:

[0008] S101, obtaining the domain identifier of the data to be controlled, the collection object identifier of the data to be controlled, and the data structure of the data to be controlled;

[0009] S102, based on the domain identifier of the data to be controlled, the collection object identifier to which the data to be controlled belongs, and the data structure of the data to be controlled, determining whether the data to be controlled is safe through a pre-established blockchain; a block in the blockchain uses the domain identifier as a unique identifier, and a node in the block uses the collection object identifier as a unique identifier;

[0010] S103: If it is unsafe, an alarm is issued.

[0011] Optionally, the process of establishing the blockchain includes:

[0012] S201, whenever data is collected for a new collection object, the domain where the collection object is located, the collection object identifier, and the data structure of the collection data are obtained;

[0013] S202, determining whether there is a block corresponding to the domain where the collection object is located in the blockchain;

[0014] S203, if it does not exist, then establishing a block corresponding to the domain where the collection object is located in the blockchain, and based on the data structure of the collection data, establishing a node with the collection object identifier as a unique identifier in the block corresponding to the domain where the collection object is located;

[0015] S204: If it exists, based on the data structure of the collected data, a node with the collection object identifier as a unique identifier is established in the block corresponding to the domain where the collection object is located.

[0016] Optionally, in S203, establishing a block corresponding to the domain where the collection object is located in the blockchain specifically includes:

[0017] A new block is added to the end of the blockchain, the unique identifier of the new block is the identifier of the domain where the collection object is located, and the first node of the new block is the topological structure of the domain where the collection object is located.

[0018] Optionally, in S203 and / or S204, based on the data structure of the collected data, establishing a node with the collection object identifier as a unique identifier in the block corresponding to the domain where the collection object is located specifically includes:

[0019] S301, determining whether there is a node with the collection object identifier as a unique identifier in the block corresponding to the domain where the collection object is located;

[0020] S302, if there is a node uniquely identified by the acquisition object identifier, then if the data structure stored in the node uniquely identified by the acquisition object identifier is different from the data structure of the acquisition data, then the data structure of the acquisition data is added to the node uniquely identified by the acquisition object identifier;

[0021] S303: If there is no node with the acquisition object identifier as a unique identifier, a node with the acquisition object identifier as a unique identifier is established in a block corresponding to the domain where the acquisition object is located.

[0022] Optionally, the nodes in the block are multidimensional arrays;

[0023] The data structure of adding the collected data to the node with the collection object identifier as the unique identifier in S302 specifically includes:

[0024] A new dimension is created in the node where the acquisition object identifier is a unique identifier, and the data structure of the acquisition data is stored in the dimension.

[0025] Optionally, in S303, establishing a node with the collection object identifier as a unique identifier in the block corresponding to the domain where the collection object is located specifically includes:

[0026] S303-1, obtaining the first node of the block corresponding to the domain where the collection object is located;

[0027] S303-2, obtaining the topological structure of the first node;

[0028] S303-3, determining the topological relationship between the collection objects in the domain where the collection object is located according to the topological structure, and determining the collection objects that have a direct connection relationship with the collection object based on the topological relationship;

[0029] S303-4, sending a verification request to the acquisition object with the direct connection relationship, wherein the verification request includes the acquisition object identifier and a random number, so that the acquisition object with the direct connection relationship feeds back a verification result based on the verification request;

[0030] S303-5, if the verification result is normal, a new node is created at the end of the block corresponding to the domain where the collection object is located. The unique identifier of the new node is the collection object identifier. A new dimension is created in the new node, and the data structure of the collection data is stored in the dimension.

[0031] Optionally, the S303-4 specifically includes:

[0032] A verification request is sent to the acquisition object with a direct connection relationship, wherein the verification request includes the acquisition object identifier, so that the acquisition object with a direct connection relationship determines the permission relationship between itself and the acquisition object based on the acquisition object identifier, hash maps the random number, sends the mapped value to the acquisition object, accepts the storage structure of the mapped value fed back by the acquisition object, and feeds back the permission relationship, the mapped value, and the storage structure of the mapped value as a verification result.

[0033] Optionally, the method for determining whether the verification result in S303-5 is normal is:

[0034] S401, obtaining the permission relationship, mapped value and storage structure of the mapped value fed back by all directly connected collection objects;

[0035] S402, merging the permission relationships fed back by all directly connected acquisition objects to obtain a permission list between all directly connected acquisition objects and the acquisition object;

[0036] S403, obtaining a list of permissions related to the collection object from the collection object;

[0037] S404: If the list obtained in S403 is the same as the list obtained in S402, and the storage structure of the mapped values ​​fed back by all directly connected collection objects is the same, and the hash values ​​fed back by all directly connected collection objects are XORed, and the result obtained is 0 or 1, then the verification result is judged to be normal.

[0038] Optionally, the S102 specifically includes:

[0039] S102-1, determining whether there is a block in the pre-established blockchain that has a domain identifier to which the data to be controlled belongs as a unique identifier;

[0040] S102-2, if there is no block with the domain identifier to which the data to be controlled belongs as a unique identifier, it is determined that the data to be controlled is unsafe;

[0041] S102-3, if there is a block uniquely identified by the domain identifier of the data to be controlled, determine whether there is a node uniquely identified by the collection object identifier of the data to be controlled in the block uniquely identified by the domain identifier of the data to be controlled;

[0042] S102-4, if there is no node with the collection object identifier of the data to be controlled as a unique identifier, it is determined that the data to be controlled is unsafe;

[0043] S102-5, if there is a node uniquely identified by the collection object identifier to which the data to be controlled belongs, then when the node uniquely identified by the collection object identifier to which the data to be controlled belongs stores a data structure identical to the data structure of the data to be controlled, the data to be controlled is determined to be safe; when the node uniquely identified by the collection object identifier to which the data to be controlled belongs does not store a data structure identical to the data structure of the data to be controlled, the data to be controlled is determined to be unsafe.

[0044] Optionally, when the node with the collection object identifier of the data to be controlled as the unique identifier does not store a data structure identical to the data structure of the data to be controlled in S102-5, determining that the data to be controlled is unsafe specifically includes:

[0045] When the node with the collection object identifier of the data to be controlled as the unique identifier does not store the same data structure as the data structure of the data to be controlled, then

[0046] Obtain the topological structure of the first node of the block corresponding to the domain identifier to which the data to be controlled belongs;

[0047] Determine a second collection object according to the topological structure, where the second collection object is a collection object that has a direct connection relationship with the collection object to which the data to be managed belongs;

[0048] Sending the collection object identifier of the to-be-controlled data to the second collection object, so that the second collection object can feedback the most recent time of data interaction between the second collection object and the collection object to which the to-be-controlled data belongs according to the collection object identifier of the to-be-controlled data;

[0049] An identity authentication request is sent to the second collection object that is closest in time, so that the second collection object that is closest in time performs identity authentication on the collection object to which the data to be managed belongs according to the following formula:

[0050] S=Δt*(up-down) / max{up,down};

[0051] If the identity authentication result is greater than the preset threshold, the data to be controlled is determined to be safe; if the identity authentication result is not greater than the preset threshold, the data to be controlled is determined to be unsafe;

[0052] Where S is the identity authentication result, Δt is the minimum time difference between the second most recent collection and the collection object to which the data to be controlled belongs for data interaction, up is the maximum flow rate for the second most recent collection to interact with the collection object to which the data to be controlled belongs, and down is the minimum flow rate for the second most recent collection to interact with the collection object to which the data to be controlled belongs.

[0053] (III) Beneficial effects

[0054] The beneficial effects of the present invention are as follows: based on the domain identifier of the data to be controlled, the collection object identifier to which the data to be controlled belongs, and the data structure of the data to be controlled, whether the data to be controlled is safe is determined through a pre-established blockchain. The blocks in the blockchain use the domain identifier as a unique identifier, and the nodes in the blocks use the collection object identifier as a unique identifier. If it is unsafe, an alarm is issued, thereby realizing safe control of cross-domain heterogeneous data. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 A flowchart of a cross-domain heterogeneous data security management and control method provided in accordance with an embodiment of the present application. DETAILED DESCRIPTION

[0056] In order to better explain the present invention and facilitate understanding, the present invention is described in detail below through specific implementation modes in conjunction with the accompanying drawings.

[0057] In recent years, with the rapid development of science and technology and the advancement of informatization, the amount of data accumulated by human society has greatly increased, and the amount of data collection, storage, processing and dissemination has also increased day by day. At the same time, with the development of business and the construction of systems, the amount of data is also increasing, and the structural differences are becoming greater and greater. How to control the security of cross-domain heterogeneous data has become a more concerned issue at present.

[0058] Based on this, the present invention provides a method for secure management and control of cross-domain heterogeneous data. Based on the domain identifier of the data to be controlled, the collection object identifier to which the data to be controlled belongs, and the data structure of the data to be controlled, whether the data to be controlled is safe is determined through a pre-established blockchain. The blocks in the blockchain use the domain identifier as a unique identifier, and the nodes in the blocks use the collection object identifier as a unique identifier. If it is unsafe, an alarm is issued, thereby realizing secure management and control of cross-domain heterogeneous data.

[0059] The cross-domain heterogeneous data security management and control method of the present invention is implemented based on blockchain. The blockchain is composed of multiple blocks, each of which stores the data of a domain, that is, the number of blocks in the blockchain is the same as the number of domains managed by the method of the present invention, each block corresponds to a domain, and each block is uniquely identified by the domain identifier.

[0060] For any block, it includes multiple nodes, each node stores all the data collected by a collection object, and the nodes in the block are uniquely identified by the collection object identifier.

[0061] In addition, for any block, its first node is the topological structure of the domain corresponding to the block. That is to say, for n collection objects in a domain, there are n+1 blocks in the blockchain corresponding to the domain. The first block stores the topological structure of the domain, and the remaining n blocks correspond to the collection objects one by one, respectively storing the data collected by the corresponding collection objects.

[0062] In addition, the nodes in the block are a multidimensional array, and each dimension stores a data structure for collecting data.

[0063] Based on this blockchain, data from different domains are stored in different blocks, data collected by different collection objects are stored in different nodes, and data of different data structures collected by the same collection object are stored in different dimensions of the node. This structure can facilitate subsequent cross-domain heterogeneous data security management and control.

[0064] The process of establishing a blockchain is as follows:

[0065] S201, whenever data is collected for a new collection object, the domain where the collection object is located, the collection object identifier, and the data structure of the collection data are obtained.

[0066] S202, determining whether there is a block in the blockchain corresponding to the domain where the collection object is located.

[0067] S203, if it does not exist, then create a block corresponding to the domain where the collection object is located in the blockchain, and based on the data structure of the collected data, create a node with the collection object identifier as the unique identifier in the block corresponding to the domain where the collection object is located.

[0068] S203: Since no data of this domain has been stored in the current blockchain, two steps are required. The first is to establish a block corresponding to the domain to store the data in the domain. The second is to establish a node in the newly established block to store the data collected by the collection object.

[0069] Specifically, 1) the process of establishing a block corresponding to the domain where the collection object is located in the blockchain is as follows:

[0070] A new block is added to the end of the blockchain. The unique identifier of the new block is the identifier of the domain where the collection object is located, and the first node of the new block is the topological structure of the domain where the collection object is located.

[0071] 2) Based on the data structure of the collected data, the process of establishing a node with the collection object identifier as the unique identifier in the block corresponding to the domain where the collection object is located is as follows:

[0072] S301, determining whether there is a node with a collection object identifier as a unique identifier in a block corresponding to the domain where the collection object is located.

[0073] S302, if there is a node with the collection object identifier as the unique identifier, if the data structure stored in the node with the collection object identifier as the unique identifier is different from the data structure of the collection data, then the data structure of the collection data is added to the node with the collection object identifier as the unique identifier.

[0074] S302 is for the situation where the data collected by the collection object has been stored in the current blockchain. This situation does not meet the premise of S203, because when entering step S203, it is assumed that the data corresponding to the domain has not been stored, so it is impossible to store the data collected by the collection object. In order to maintain the integrity of the solution, only a brief description is given here. For detailed explanation, please refer to the corresponding part in S204.

[0075] S303: If there is no node with the collection object identifier as the unique identifier, a node with the collection object identifier as the unique identifier is established in the block corresponding to the domain where the collection object is located.

[0076] S303 is for the case where the data collected by the collection object has not been stored in the current blockchain. The specific implementation process is as follows:

[0077] S303-1, obtain the first node of the block corresponding to the domain where the collection object is located.

[0078] S303-2, obtaining the topological structure of the first node.

[0079] S303-3, determining the topological relationship between the collection objects in the domain where the collection object is located according to the topological structure, and determining the collection objects that have a direct connection relationship with the collection object based on the topological relationship.

[0080] S303-4, sending a verification request to the acquisition object with a direct connection relationship, the verification request including the acquisition object identifier and a random number, so that the acquisition object with a direct connection relationship feeds back a verification result based on the verification request.

[0081] Specifically, a verification request is sent to a collection object with a direct connection relationship, and the verification request includes a collection object identifier, so that the collection object with a direct connection relationship determines the permission relationship between itself and the collection object based on the collection object identifier, hash maps the random number, and sends the mapped value to the collection object, and accepts the storage structure of the mapped value fed back by the collection object, and feeds back the permission relationship, the mapped value, and the storage structure of the mapped value as a verification result.

[0082] For example, after sending a verification request to a collection object with a direct connection relationship, and the verification request includes the collection object identifier, 1) the collection object with a direct connection relationship determines the permission relationship between it and the collection object based on the collection object identifier, hash maps the random number, and sends the mapped value to the collection object; 2) after receiving the mapped value, the collection object determines the storage structure for storing the value, and feeds back the storage structure to the collection object with a direct connection relationship; 3) the collection object with a direct connection relationship accepts the storage structure of the mapped value fed back by the collection object, and feeds back the permission relationship, the mapped value, and the storage structure of the mapped value as the verification result.

[0083] S303-5, if the verification result is normal, a new node is created at the end of the block corresponding to the domain where the collection object is located. The unique identifier of the new node is the collection object identifier. A new dimension is created in the new node, and the data structure of the collection data is stored in the dimension.

[0084] The verification process is as follows:

[0085] S401, obtaining the permission relationship, mapped value and storage structure of the mapped value fed back by all directly connected collection objects.

[0086] S402: Merge the permission relationships fed back by all directly connected acquisition objects to obtain a permission list between all directly connected acquisition objects.

[0087] S403, obtaining a list of entities with which the collection object has an authority relationship from the collection object.

[0088] S404: If the list obtained in S403 is the same as the list obtained in S402, and the storage structure of the mapped values ​​fed back by all directly connected collection objects is the same, and the hash values ​​fed back by all directly connected collection objects are XORed, and the result obtained is 0 or 1, then the verification result is judged to be normal.

[0089] S204: If it exists, based on the data structure of the collected data, a node with the collection object identifier as a unique identifier is established in the block corresponding to the domain where the collection object is located.

[0090] S204 For any data in this domain that has been stored in the current blockchain, it is only necessary to establish a node corresponding to the collection object. The specific establishment process is:

[0091] S301, determining whether there is a node with a collection object identifier as a unique identifier in a block corresponding to the domain where the collection object is located.

[0092] S302, if there is a node with the collection object identifier as the unique identifier, if the data structure stored in the node with the collection object identifier as the unique identifier is different from the data structure of the collection data, then the data structure of the collection data is added to the node with the collection object identifier as the unique identifier.

[0093] If the node corresponding to the collection object has been established, the collected data structure may be different. Therefore, it will be determined whether the data structure stored in the node with the collection object identifier as the unique identifier is the same as the data structure of the collected data. If they are not the same, the data structure of the collected data will be added to the node with the collection object identifier as the unique identifier.

[0094] When adding the data structure of the collected data to the node with the collection object identifier as the unique identifier, since the nodes in the block are a multidimensional array, a new dimension can be created in the node with the collection object identifier as the unique identifier to store the data structure of the collected data.

[0095] S303: If there is no node with the collection object identifier as the unique identifier, a node with the collection object identifier as the unique identifier is established in the block corresponding to the domain where the collection object is located.

[0096] Specifically,

[0097] S303-1, obtain the first node of the block corresponding to the domain where the collection object is located.

[0098] S303-2, obtaining the topological structure of the first node.

[0099] S303-3, determining the topological relationship between the collection objects in the domain where the collection object is located according to the topological structure, and determining the collection objects that have a direct connection relationship with the collection object based on the topological relationship.

[0100] S303-4, sending a verification request to the acquisition object with a direct connection relationship, the verification request including the acquisition object identifier and a random number, so that the acquisition object with a direct connection relationship feeds back a verification result based on the verification request.

[0101] Specifically, a verification request is sent to a collection object with a direct connection relationship, and the verification request includes a collection object identifier, so that the collection object with a direct connection relationship determines the permission relationship between itself and the collection object based on the collection object identifier, hash maps the random number, and sends the mapped value to the collection object, and accepts the storage structure of the mapped value fed back by the collection object, and feeds back the permission relationship, the mapped value, and the storage structure of the mapped value as a verification result.

[0102] S303-5, if the verification result is normal, a new node is created at the end of the block corresponding to the domain where the collection object is located. The unique identifier of the new node is the collection object identifier. A new dimension is created in the new node, and the data structure of the collection data is stored in the dimension.

[0103] The method for determining whether the verification result is normal is as follows:

[0104] S401, obtaining the permission relationship, mapped value and storage structure of the mapped value fed back by all directly connected collection objects.

[0105] S402: Merge the permission relationships fed back by all directly connected acquisition objects to obtain a permission list between all directly connected acquisition objects.

[0106] S403, obtaining a list of entities with which the collection object has an authority relationship from the collection object.

[0107] S404: If the list obtained in S403 is the same as the list obtained in S402, and the storage structure of the mapped values ​​fed back by all directly connected collection objects is the same, and the hash values ​​fed back by all directly connected collection objects are XORed, and the result obtained is 0 or 1, then the verification result is judged to be normal.

[0108] Based on the above blockchain, see Figure 1 The implementation process of a cross-domain heterogeneous data security management and control method provided by the present invention is as follows:

[0109] S101, obtaining the domain identifier to which the data to be controlled belongs, the collection object identifier to which the data to be controlled belongs, and the data structure of the data to be controlled.

[0110] S102, based on the domain identifier of the data to be controlled, the collection object identifier to which the data to be controlled belongs, and the data structure of the data to be controlled, determine whether the data to be controlled is safe through a pre-established blockchain.

[0111] Among them, the blocks in the blockchain are uniquely identified by the domain identifier, and the nodes in the block are uniquely identified by the collection object identifier.

[0112] Specifically,

[0113] S102-1, determine whether there is a block in the pre-established blockchain that uses the domain identifier to which the data to be controlled belongs as a unique identifier.

[0114] S102-2: If there is no block with the domain identifier to which the data to be controlled belongs as a unique identifier, it is determined that the data to be controlled is not safe.

[0115] S102-3, if there is a block with the domain identifier of the data to be controlled as a unique identifier, determine whether there is a node with the collection object identifier of the data to be controlled as a unique identifier in the block with the domain identifier of the data to be controlled as a unique identifier.

[0116] S102-4: If there is no node with the collection object identifier of the data to be controlled as the unique identifier, it is determined that the data to be controlled is not safe.

[0117] S102-5, if there is a node with the collection object identifier of the data to be managed as the unique identifier, then

[0118] (1) When a data structure identical to the data structure of the data to be controlled is stored in a node whose unique identifier is the collection object identifier to which the data to be controlled belongs, it is determined that the data to be controlled is safe.

[0119] (2) When the node with the collection object identifier to which the data to be controlled belongs as the unique identifier does not store a data structure identical to the data structure of the data to be controlled, it is determined that the data to be controlled is unsafe.

[0120] For the case (2), it is also possible that, when the node with the collection object identifier of the data to be controlled as the unique identifier does not store the same data structure as the data structure of the data to be controlled,

[0121] Get the topological structure of the first node of the block corresponding to the domain identifier to which the data to be controlled belongs.

[0122] Determine the second acquisition object according to the topological structure.

[0123] Among them, the second collection object is a collection object that has a direct connection relationship with the collection object to which the data to be controlled belongs.

[0124] Send the collection object identifier of the data to be controlled to the second collection object.

[0125] The purpose of sending the collection object identifier of the data to be controlled to the second collection object is to enable the second collection object to feedback the most recent time of data interaction between the second collection object and the collection object to which the data to be controlled belongs according to the collection object identifier of the data to be controlled.

[0126] · Send an identity verification request to the second collection object that is most recently acquired.

[0127] The purpose of sending the identity authentication request to the second collection object at the latest time is to enable the second collection object at the latest time to authenticate the collection object to which the controlled data belongs according to the following formula:

[0128] S=Δt*(up-down) / max{up,down}.

[0129] If the identity authentication result is greater than the preset threshold, the data to be controlled is determined to be safe. If the identity authentication result is not greater than the preset threshold, the data to be controlled is determined to be unsafe.

[0130] Where S is the identity authentication result, Δt is the minimum time difference between the second most recent collection and the collection object to which the data to be controlled belongs for data interaction, up is the maximum flow of data interaction between the second most recent collection and the collection object to which the data to be controlled belongs, and down is the minimum flow of data interaction between the second most recent collection and the collection object to which the data to be controlled belongs.

[0131] S103: If it is unsafe, an alarm is issued.

[0132] After the alarm, if the data to be controlled is confirmed to be safe, the blockchain construction process can be re-executed to establish blocks, nodes, data structures, etc. corresponding to the data to be controlled, so that it can be used as safe data later.

[0133] Beneficial effects: Based on the domain identifier of the data to be controlled, the collection object identifier of the data to be controlled and the data structure of the data to be controlled, the security of the data to be controlled is determined through a pre-established blockchain. The blocks in the blockchain use the domain identifier as a unique identifier, and the nodes in the blocks use the collection object identifier as a unique identifier. If it is unsafe, an alarm is issued, thereby realizing secure control of cross-domain heterogeneous data.

[0134] It should be clear that the present invention is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present invention.

[0135] It should also be noted that the exemplary embodiments mentioned in the present invention describe some methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiments, or in a different order from the embodiments, or several steps can be performed simultaneously.

[0136] Finally, it should be noted that the above-described embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some or all of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A cross-domain heterogeneous data security management and control method, It is characterized in that The method comprises: S101, obtaining the domain identifier of the data to be controlled, the collection object identifier of the data to be controlled, and the data structure of the data to be controlled; S102, based on the domain identifier of the data to be controlled, the collection object identifier to which the data to be controlled belongs, and the data structure of the data to be controlled, determining whether the data to be controlled is safe through a pre-established blockchain; a block in the blockchain uses the domain identifier as a unique identifier, and a node in the block uses the collection object identifier as a unique identifier; The S102 specifically includes: S102-1, determining whether there is a block in the pre-established blockchain with the domain identifier of the data to be controlled as a unique identifier; S102-2, if there is no block with the domain identifier to which the data to be controlled belongs as a unique identifier, it is determined that the data to be controlled is unsafe; S102-3, if there is a block uniquely identified by the domain identifier of the data to be controlled, determine whether there is a node uniquely identified by the collection object identifier of the data to be controlled in the block uniquely identified by the domain identifier of the data to be controlled; S102-4, if there is no node with the collection object identifier of the data to be controlled as a unique identifier, it is determined that the data to be controlled is unsafe; S102-5, if there is a node uniquely identified by the collection object identifier to which the data to be controlled belongs, when the node uniquely identified by the collection object identifier to which the data to be controlled belongs stores a data structure identical to the data structure of the data to be controlled, it is determined that the data to be controlled is safe; when the node uniquely identified by the collection object identifier to which the data to be controlled belongs does not store a data structure identical to the data structure of the data to be controlled, it is determined that the data to be controlled is unsafe; S103, if it is unsafe, an alarm is issued; The process of establishing the blockchain includes: S201, whenever data is collected for a new collection object, the domain where the collection object is located, the collection object identifier, and the data structure of the collection data are obtained; S202, determining whether there is a block corresponding to the domain where the collection object is located in the blockchain; S203, if it does not exist, then establishing a block corresponding to the domain where the collection object is located in the blockchain, and based on the data structure of the collection data, establishing a node with the collection object identifier as a unique identifier in the block corresponding to the domain where the collection object is located; S204: If it exists, based on the data structure of the collected data, a node with the collection object identifier as a unique identifier is established in the block corresponding to the domain where the collection object is located.

2. The method according to claim 1, It is characterized in that In S203, establishing a block corresponding to the domain where the collection object is located in the blockchain specifically includes: A new block is added to the end of the blockchain, the unique identifier of the new block is the identifier of the domain where the collection object is located, and the first node of the new block is the topological structure of the domain where the collection object is located.

3. The method according to claim 2, It is characterized in that The step of establishing a node with the acquisition object identifier as a unique identifier in the block corresponding to the domain where the acquisition object is located based on the data structure of the acquisition data in S203 and / or S204 specifically includes: S301, determining whether there is a node with the collection object identifier as a unique identifier in the block corresponding to the domain where the collection object is located; S302, if there is a node uniquely identified by the acquisition object identifier, then if the data structure stored in the node uniquely identified by the acquisition object identifier is different from the data structure of the acquisition data, then the data structure of the acquisition data is added to the node uniquely identified by the acquisition object identifier; S303: If there is no node with the acquisition object identifier as a unique identifier, a node with the acquisition object identifier as a unique identifier is established in a block corresponding to the domain where the acquisition object is located.

4. The method according to claim 3, It is characterized in that The nodes in a block are multidimensional arrays; The data structure of adding the collected data to the node with the collection object identifier as the unique identifier in S302 specifically includes: A new dimension is created in the node where the acquisition object identifier is a unique identifier, and the data structure of the acquisition data is stored in the dimension.

5. The method according to claim 3, It is characterized in that The step of establishing a node with the collection object identifier as a unique identifier in the block corresponding to the domain where the collection object is located in S303 specifically includes: S303-1, obtaining the first node of the block corresponding to the domain where the collection object is located; S303-2, obtaining the topological structure of the first node; S303-3, determining the topological relationship between the collection objects in the domain where the collection object is located according to the topological structure, and determining the collection objects that have a direct connection relationship with the collection object based on the topological relationship; S303-4, sending a verification request to the acquisition object with the direct connection relationship, wherein the verification request includes the acquisition object identifier and a random number, so that the acquisition object with the direct connection relationship feeds back a verification result based on the verification request; S303-5, if the verification result is normal, a new node is created at the end of the block corresponding to the domain where the collection object is located. The unique identifier of the new node is the collection object identifier. A new dimension is created in the new node, and the data structure of the collection data is stored in the dimension.

6. The method according to claim 5, It is characterized in that The S303-4 specifically includes: A verification request is sent to the acquisition object with a direct connection relationship, wherein the verification request includes the acquisition object identifier, so that the acquisition object with a direct connection relationship determines the permission relationship between itself and the acquisition object based on the acquisition object identifier, hash maps the random number, sends the mapped value to the acquisition object, accepts the storage structure of the mapped value fed back by the acquisition object, and feeds back the permission relationship, the mapped value, and the storage structure of the mapped value as a verification result.

7. The method according to claim 5, It is characterized in that The method for determining whether the verification result in S303-5 is normal is: S401, obtaining the permission relationship, mapped value and storage structure of the mapped value fed back by all directly connected collection objects; S402, merging the permission relationships fed back by all directly connected acquisition objects to obtain a permission list between all directly connected acquisition objects and the acquisition object; S403, obtaining a list of permissions related to the collection object from the collection object; S404: If the list obtained in S403 is the same as the list obtained in S402, and the storage structure of the mapped values ​​fed back by all directly connected collection objects is the same, and the hash values ​​fed back by all directly connected collection objects are XORed, and the result obtained is 0 or 1, then the verification result is judged to be normal.

8. The method according to claim 1, It is characterized in that In S102-5, when the node with the collection object identifier of the data to be controlled as the unique identifier does not store the same data structure as the data structure of the data to be controlled, determining that the data to be controlled is unsafe specifically includes: When the node with the collection object identifier of the data to be controlled as the unique identifier does not store the same data structure as the data structure of the data to be controlled, then Obtain the topological structure of the first node of the block corresponding to the domain identifier to which the data to be controlled belongs; Determine a second collection object according to the topological structure, where the second collection object is a collection object that has a direct connection relationship with the collection object to which the data to be managed belongs; Sending the collection object identifier of the to-be-controlled data to the second collection object, so that the second collection object can feedback the most recent time of data interaction between the second collection object and the collection object to which the to-be-controlled data belongs according to the collection object identifier of the to-be-controlled data; An identity authentication request is sent to the second collection object that is closest in time, so that the second collection object that is closest in time performs identity authentication on the collection object to which the data to be managed belongs according to the following formula: S=Δt*(up-down) / max{up, down}; If the identity authentication result is greater than the preset threshold, the data to be controlled is determined to be safe; if the identity authentication result is not greater than the preset threshold, the data to be controlled is determined to be unsafe; Where S is the identity authentication result, Δt is the minimum time difference between the second most recent collection and the collection object to which the data to be controlled belongs for data interaction, up is the maximum flow rate for the second most recent collection to interact with the collection object to which the data to be controlled belongs, and down is the minimum flow rate for the second most recent collection to interact with the collection object to which the data to be controlled belongs.