Data asset right management method and system based on unified data standard

Abstract

The application relates to the field of data asset management, and discloses a data asset right confirmation management method and system based on a unified data standard. The method comprises the following steps: standard ownership information and data domain verification information are respectively constructed for a plurality of data assets of a plurality of asset nodes, the standard ownership information comprises a plurality of right confirmation field information, and the data domain verification information comprises a plurality of data domain field information; the number of data assets in each data domain is acquired; when the number of first data assets in a first data domain is greater than a preset number, the first data domain is divided into a plurality of sub-data domains each comprising a plurality of first data assets; each sub-data domain corresponds to a plurality of sub-asset nodes; and the data domain field information in the data domain verification information of the sub-data assets is updated according to the ownership relationship between the sub-data assets and the sub-asset nodes. The application realizes standard and normative management of data and facilitates clear property right definition of data assets.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of data asset management, in particular to a data asset right management method and system based on unified data standards. BACKGROUND

[0002] With the advent of the digital era, data has become one of the most important assets for enterprises and individuals. Data asset righting refers to the process of determining the ownership of data assets and other related rights and interests of data assets. The righting of data assets not only concerns the security and privacy of data, but also directly affects the realization and distribution of the value of data. Traditional righting methods usually rely on contracts and legal declarations, but these methods are not flexible and efficient enough in the rapidly changing technical environment and complex transaction networks. Therefore, it is necessary to use advanced technical means to realize the righting of data assets.

[0003] In the process of data asset righting, it is necessary to clearly define the property rights of customers as data providers and enterprises as data collectors, but there is currently a lack of mature data property rights system and mechanism to define it. In addition, data involves multiple subjects such as individuals, enterprises, and government departments from the time of its generation, and the data mining, processing, and other re-creation processes will be associated with more subjects, and the ownership is inevitably multiple and difficult to divide. At the same time, the data management standards and specifications between enterprises are not unified, which reduces the usability, interoperability, and consistency of data, and easily forms data silos between enterprises. Therefore, due to the non-uniformity of data management standards and specifications between enterprises, it further exacerbates the difficulty of clearly defining the property rights of data in data use, leading to the difficulty of clearly defining the property rights of data assets in practice. SUMMARY

[0004] The purpose of the present application is to provide a data asset righting management method and system based on unified data standards, which solves the technical problems of difficult standard and specification management of data and difficult clear property right definition of data assets, and achieves the technical effects of standard and specification management of data and convenient clear property right definition of data assets.

[0005] This application provides a data asset ownership management method based on a unified data standard. The method includes: constructing standard ownership information and data domain verification information for multiple data assets of multiple asset nodes. The standard ownership information includes multiple ownership fields, and the data domain verification information includes multiple data domain fields. The ownership fields are used to determine the ownership information of the data assets, and the data domain fields are used to determine the data domain corresponding to the data assets. Specifically, based on the first ownership relationship between the first data asset and the first asset node and the second asset node, the first ownership field information in the first standard ownership information of the first data asset is determined, and based on the ownership relationship between the first data asset and the asset nodes in the corresponding data domain, the data domain fields in the data domain verification information of the first data asset are determined. The number of data assets in each data domain is obtained. When the number of first data assets in the first data domain is greater than a preset number, the first data domain is divided into multiple sub-data domains, each including multiple first data assets. Each sub-data domain corresponds to multiple sub-asset nodes, and the data domain fields in the data domain verification information of the sub-data assets are updated according to the ownership relationship between the sub-data assets and the sub-asset nodes.

[0006] In one possible implementation, when the number of first data assets in the first data domain exceeds a preset number, the first data domain is divided into multiple sub-data domains, each including multiple first data assets. This includes: when the number of first data assets in the first data domain exceeds the preset number, obtaining the number of ownership confirmation field information in the standard ownership information of each first data asset, and determining the range of ownership confirmation field information corresponding to the number of ownership confirmation field information in the standard ownership information of all first data assets; dividing the range of ownership confirmation field information into multiple sub-intervals, each sub-interval corresponding to a sub-data domain, and assigning all first data assets to the sub-data domains corresponding to the sub-intervals according to the number of ownership confirmation field information.

[0007] In another possible implementation, the method further includes: determining the first sub-data field corresponding to the first sub-interval where the number of rights confirmation field information is greater than or equal to a preset number, and determining the second sub-data field corresponding to the second sub-interval where the number of rights confirmation field information is less than a preset number; storing the standard ownership information and data domain verification information of the first data asset in the first sub-data field on a blockchain storage system, and storing the standard ownership information and data domain verification information of the first data asset in the second sub-data field on a non-blockchain storage system.

[0008] In another possible implementation, the method further includes: obtaining the node importance index of each asset node; determining the average number of ownership field information items for all first data assets in each sub-data domain; determining the average node importance index of all asset nodes corresponding to each sub-data domain; and determining the product of the average number of ownership field information items and the average node importance index for each sub-data domain as the data domain importance index for each sub-data domain; determining the first sub-data domain whose data domain importance index is greater than or equal to a preset data domain importance index; and determining the second sub-data domain whose data domain importance index is less than the preset data domain importance index; storing the standard ownership information and data domain verification information of the first data assets in the first sub-data domain on a blockchain storage system; and storing the standard ownership information and data domain verification information of the first data assets in the second sub-data domain on a non-blockchain storage system.

[0009] In another possible implementation, the data field information in the data field verification information of the first data asset is determined based on the ownership relationship between the first data asset and the asset nodes in the data field corresponding to the first data asset. This includes: determining the data field information in the data field verification information of the first data asset through an encryption algorithm, based on the attribute information of the first data asset, the attribute information of the asset nodes in the data field corresponding to the first data asset, and the ownership relationship information between the first data asset and the asset nodes in the data field corresponding to the first data asset.

[0010] In another possible implementation, the data field information in the data field verification information of the first data asset is determined by an encryption algorithm based on the attribute information of the first data asset, the attribute information of the asset nodes in the data field corresponding to the first data asset, and the ownership relationship information between the first data asset and the asset nodes in the data field corresponding to the first data asset. This includes: determining the data field information in the data field verification information of the first data asset based on the attribute information of the first data asset, the attribute information of the asset nodes in the data field corresponding to the first data asset, and the ownership percentage or usage right period between the first data asset and the asset nodes in the data field corresponding to the first data asset.

[0011] This application also provides a data asset ownership confirmation management system based on a unified data standard, including a unit for performing the method described in any of the above embodiments.

[0012] This application also provides a data asset ownership management system based on a unified data standard, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the method described in any of the preceding claims.

[0013] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any of the preceding claims.

[0014] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in any of the preceding claims.

[0015] The beneficial effects of the embodiments in this application compared with the prior art are:

[0016] This application provides a data asset ownership management method based on a unified data standard. The method includes: constructing standard ownership information and data domain verification information for multiple data assets across multiple asset nodes. The standard ownership information includes multiple ownership fields, and the data domain verification information includes multiple data domain fields. The ownership fields are used to determine the ownership information of the data assets, and the data domain fields are used to determine the data domain corresponding to the data assets. Specifically, based on the first ownership relationship between the first data asset and the first asset node and the second asset node, the first ownership field information in the first standard ownership information of the first data asset is determined. Based on the ownership relationship between the first data asset and the asset nodes in the corresponding data domain, the data domain fields in the data domain verification information of the first data asset are determined. The number of data assets in each data domain is obtained. When the number of first data assets in the first data domain exceeds a preset number, the first data domain is divided into multiple sub-data domains, each including multiple first data assets. Each sub-data domain corresponds to multiple sub-asset nodes. The data domain fields in the data domain verification information of the sub-data assets are updated based on the ownership relationship between the sub-data assets and the sub-asset nodes. The data asset ownership confirmation and management method based on unified data standards in this application embodiment can standardize the management of data asset ownership information and divide data assets into standardized data domains, thereby improving the efficiency of data asset management and ownership confirmation and facilitating efficient data asset transactions and ownership management in the future. At the same time, this application determines the data domain field information in the data domain verification information of the first data asset based on the ownership relationship between the first data asset and the asset nodes in the corresponding data domain, which can prevent the data domain verification information from being tampered with and further improve the security of data asset ownership information management. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a data asset ownership management method based on a unified data standard, provided for an embodiment of this application;

[0019] Figure 2 This is a schematic diagram of the data asset ownership confirmation process in the embodiments of this application;

[0020] Figure 3 This is a schematic diagram of the standard ownership information and data domain verification information constructed in the embodiments of this application;

[0021] Figure 4 A flowchart illustrating the second data asset ownership management method based on a unified data standard, provided in this application embodiment;

[0022] Figure 5 A flowchart illustrating the third data asset ownership management method based on a unified data standard, provided in this application embodiment;

[0023] Figure 6 A schematic diagram of the logical structure of a data asset ownership confirmation management system based on a unified data standard, provided for embodiments of this application;

[0024] Figure 7 This is a schematic diagram of the physical structure of a data asset ownership confirmation management system based on a unified data standard, provided as an embodiment of this application. Detailed Implementation

[0025] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0026] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0027] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0028] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0029] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0030] From the moment data is generated, it involves multiple entities, including individuals, businesses, and government departments. The data mining and processing processes further connect it to even more entities, inevitably leading to multiple and complex ownership structures that are difficult to define. Furthermore, the lack of standardized data management practices and specifications among enterprises reduces data usability, interoperability, and consistency.

[0031] Based on the above reasons, this application provides a data asset ownership management method based on a unified data standard. This method includes: constructing standard ownership information and data domain verification information for multiple data assets across multiple asset nodes. The standard ownership information includes multiple ownership confirmation fields, and the data domain verification information includes multiple data domain fields. The ownership confirmation fields are used to determine the ownership information of the data assets, and the data domain fields are used to determine the data domain corresponding to the data assets. Specifically, based on the first ownership relationship between the first data asset and the first asset node and the second asset node, the first ownership confirmation field information in the first standard ownership information of the first data asset is determined. Based on the ownership relationship between the first data asset and the asset nodes in the corresponding data domain, the data domain fields in the data domain verification information of the first data asset are determined. The number of data assets in each data domain is obtained. When the number of first data assets in the first data domain exceeds a preset number, the first data domain is divided into multiple sub-data domains, each including multiple first data assets. Each sub-data domain corresponds to multiple sub-asset nodes. The data domain fields in the data domain verification information of the sub-data assets are updated based on the ownership relationship between the sub-data assets and the sub-asset nodes. The data asset ownership confirmation and management method based on unified data standards in this application embodiment can standardize the management of data asset ownership information and divide data assets into standardized data domains, thereby improving the efficiency of data asset management and ownership confirmation and facilitating efficient data asset transactions and ownership management in the future. At the same time, this application determines the data domain field information in the data domain verification information of the first data asset based on the ownership relationship between the first data asset and the asset nodes in the corresponding data domain, which can prevent the data domain verification information from being tampered with and further improve the security of data asset ownership information management.

[0032] In some scenarios, the data asset ownership management method based on a unified data standard according to the embodiments of this application can be applied to data asset management, which can standardize the management of data asset ownership information and facilitate clear property rights definition of data assets.

[0033] The following describes in detail, with specific examples, a data asset ownership management method based on a unified data standard provided in the embodiments of this application.

[0034] Figure 1 A flowchart illustrating a data asset ownership management method based on a unified data standard, as provided in this application embodiment, is shown below. Figure 1 As shown, this method includes S110 to S120, and S110 to S120 will be described in detail below.

[0035] S110. For multiple data assets across multiple asset nodes, standard ownership information and data domain verification information are constructed respectively. The standard ownership information includes multiple ownership confirmation fields, and the data domain verification information includes multiple data domain fields. The ownership confirmation fields are used to determine the ownership information of the data assets, and the data domain fields are used to determine the data domains corresponding to the data assets. Specifically, based on the first ownership relationship between the first data asset and the first asset node and the second asset node, the first ownership confirmation field information in the first standard ownership information of the first data asset is determined, and based on the ownership relationship between the first data asset and the asset nodes in the data domain corresponding to the first data asset, the data domain fields in the data domain verification information of the first data asset are determined.

[0036] Figure 2 This is a schematic diagram of the data asset ownership confirmation process in the embodiments of this application, such as... Figure 2 As shown, during operation, an asset node can be a node where the ownership or right to use data assets needs to be clearly defined. Data assets can be data assets such as video, audio, and text.

[0037] like Figure 2 As shown, asset nodes can include asset node A, asset node B, and asset node C, and data assets can include data asset A1. Asset node A can have ownership of data asset A1, while asset nodes B and C can have usage rights to data asset A1. Additionally, other asset nodes can have other ownership rights to data asset A1, making the ownership structure of data asset A1 potentially complex in practice.

[0038] It should be noted that, as Figure 2 As shown, a data domain can correspond to multiple data assets or multiple asset nodes, and a data domain can correspond to the ownership relationships between multiple data assets and multiple asset nodes.

[0039] For example, an asset node can be a downstream enterprise that needs to clarify the ownership of data assets.

[0040] In operation, this application embodiment can construct standard ownership information and data domain verification information for multiple data assets of multiple asset nodes. The standard ownership information and data domain verification information are used for standardized management of data assets.

[0041] For example, standard ownership information and data domain verification information can be stored in JSON format data, and data assets can be managed in a standardized manner through standard ownership information and data domain verification information in a standardized JSON data format.

[0042] Figure 3 This is a schematic diagram of the standard ownership information and data field verification information constructed in the embodiments of this application, such as...Figure 3 As shown, standard ownership information may include multiple ownership confirmation fields. These fields are used to determine the ownership of data assets, and the ownership information of data assets is used to clarify the ownership, usage rights, and other ownership information of the data assets.

[0043] For example, such as Figure 3 As shown, for a data asset, there can be multiple ownership confirmation fields, and each ownership confirmation field is used to clarify the ownership relationship of the data asset.

[0044] For example, regarding the standard ownership information of asset node A, ownership confirmation field 1 can record that asset node A has the right to use data asset A1, and ownership confirmation field 2 can record that asset node B has the right to use data asset A1.

[0045] like Figure 3 As shown, data domain verification information can include multiple data domain field information. The data domain field information is used to determine the data domain corresponding to the data asset. The data domain can be a different logical area that divides the data asset logically. Through the data domain, different data assets can be distinguished, which improves the convenience and accuracy of data asset management and avoids errors in data asset management.

[0046] For example, a data domain can be different logical units in a data asset management system. By defining logical boundaries for different data assets, the accuracy of data asset management can be improved.

[0047] It should be noted that data domains can correspond to the same or different physical storage areas on the disk.

[0048] For example, such as Figure 3 As shown, there can be multiple data field entries, each used to determine the data field corresponding to the data asset. For example, such as... Figure 3 As shown, the data field verification information for asset node A can be used to clarify the data field corresponding to asset node A.

[0049] It should be noted that, as Figure 3 As shown, for the first data asset, the first data content can be the file content of the first data asset itself, or the physical storage address corresponding to the first data asset. In this embodiment of the application, it is only necessary to establish the correspondence between the first data asset and the first standard ownership information and the first data domain verification information.

[0050] In this embodiment of the application, when constructing standard ownership information, the first ownership field information in the first standard ownership information of the first data asset can be determined based on the first ownership relationship between the first data asset and the first asset node and the second asset node, thereby realizing the recording of the ownership relationship of the first data asset.

[0051] In this embodiment of the application, when constructing data domain verification information, the data domain field information in the data domain verification information of the first data asset can be determined according to the ownership relationship between the first data asset and the asset nodes in the data domain corresponding to the first data asset. The data domain field information contains the content of the ownership relationship between the first data asset and the asset nodes in the data domain corresponding to the first data asset. This enables mutual verification of the data domain field information and the ownership relationship between the first data asset and the asset nodes in the data domain corresponding to the first data asset, preventing tampering of the data domain field information and the ownership relationship between the first data asset and the asset nodes in the data domain corresponding to the first data asset, and improving data security.

[0052] S120. Obtain the number of data assets in each data domain. When the number of first data assets in the first data domain is greater than the preset number, divide the first data domain into multiple sub-data domains, each of which includes multiple first data assets. Each sub-data domain corresponds to multiple sub-asset nodes. Update the data domain field information in the data domain verification information of the sub-data assets according to the ownership relationship between the sub-data assets and the sub-asset nodes.

[0053] When managing data assets, the number of data assets in each data domain can be obtained. This allows for the rational management of data assets in each data domain based on the number of data assets in each domain, thereby improving the scientific nature of data asset management by data domain.

[0054] When the number of first data assets in the first data domain exceeds the preset number during operation, it indicates that the number of data assets in the first data domain is too large, which may cause data asset management errors and reduce data asset management efficiency. Therefore, the first data domain can be divided into multiple sub-data domains, each containing multiple first data assets. This achieves the purpose of reassigning multiple first data assets to multiple sub-data domains, thereby avoiding data asset management errors and effectively improving the efficiency of data asset management.

[0055] When multiple sub-data domains are defined, each sub-data domain also corresponds to multiple sub-asset nodes, thereby enabling the management of data assets and their corresponding sub-asset nodes through the sub-data domains.

[0056] After obtaining multiple sub-data domains, the data domain field information in the data domain verification information of the sub-data assets can be updated according to the ownership relationship between the sub-data assets and the sub-asset nodes. This update of the data domain field information ensures the security of the data asset ownership information.

[0057] The beneficial effects of the above implementation method are that it constructs standard ownership information and data domain verification information for multiple data assets of multiple asset nodes, improves the standardization of data asset ownership information storage, facilitates standardized and regulated data management, and facilitates clear property rights definition of data assets.

[0058] The beneficial effects of the above implementation method are that data assets are logically divided into different logical areas through data domains, and different data assets can be distinguished through data domains, thereby improving the convenience and accuracy of data asset management.

[0059] The beneficial effect of the above implementation method is that the data domain field information contains the ownership relationship between the first data asset and the asset nodes in the data domain corresponding to the first data asset, which can prevent the data domain field information, the ownership relationship between the first data asset and the asset nodes in the data domain corresponding to the first data asset from being tampered with, and improve the security of the ownership relationship record of the data asset.

[0060] The beneficial effect of the above implementation method is that when the number of data assets in the first data domain is too large, which may cause errors in data asset management and a decrease in data asset management efficiency, the purpose of reclassifying multiple first data assets into multiple sub-data domains can effectively improve the efficiency of data asset management.

[0061] The beneficial effect of the above implementation method is that after multiple primary data assets are reclassified into multiple sub-data domains, the data domain field information is updated, and the security of data asset ownership information is ensured through the updated data domain field information.

[0062] In some implementations, in S120 above, when the number of first data assets in the first data domain is greater than a preset number, the first data domain is divided into multiple sub-data domains, each including multiple first data assets, including S121 to S122. S121 to S122 will be explained in detail below.

[0063] S121. When the number of first data assets in the first data domain is greater than the preset number, obtain the number of ownership field information in the standard ownership information of each first data asset, and determine the range of ownership field information corresponding to the number of ownership field information in the standard ownership information of all first data assets.

[0064] When the number of first data assets in the first data domain is greater than the preset number, the number of ownership confirmation fields in the standard ownership information of each first data asset can be obtained. The number of ownership confirmation fields represents the number of ownership relationships existing in the first data asset, that is, the number of ownership confirmation fields can represent the popularity information of the first data asset.

[0065] After obtaining the number of ownership confirmation fields in the standard ownership information of each first data asset, the range of ownership confirmation field numbers corresponding to the number of ownership confirmation fields in the standard ownership information of all first data assets can be determined. The range of ownership confirmation field numbers is the range of variation of the number of ownership confirmation fields in all data assets in the first data domain.

[0066] For example, the range of the number of ownership field information for all data assets in the first data domain can be [5, 20], that is, the minimum number of ownership field information for all data assets in the first data domain is 5, and the maximum number of ownership field information for all data assets in the first data domain is 20.

[0067] S122. Divide the range of the number of rights confirmation field information into multiple sub-ranges, each sub-range corresponding to a sub-data field, and divide all first data assets into the sub-data fields corresponding to the sub-ranges according to the number of rights confirmation field information.

[0068] When dividing the first data domain, the range of the number of rights confirmation field information can be divided into multiple sub-ranges, each sub-range corresponding to a sub-data domain. All first data assets are then divided into the sub-data domains corresponding to the sub-ranges according to the number of rights confirmation field information. This achieves the purpose of re-dividing all first data assets into multiple sub-data domains. At the same time, it facilitates the separate management of all first data assets according to the level of the number of rights confirmation field information of all first data assets, thereby improving management efficiency.

[0069] For example, when the range of the number of information fields for confirming rights is divided into multiple sub-ranges, the range of the number of information fields for confirming rights [5, 20] can be divided into sub-ranges [5, 10], [10, 15] and [15, 20].

[0070] The beneficial effects of the above implementation method are that all primary data assets are reclassified into multiple sub-data domains according to the level of the number of ownership field information, and at the same time, it is convenient to manage all primary data assets separately according to the level of the number of ownership field information of all primary data assets, thereby improving management efficiency.

[0071] Figure 4 A flowchart illustrating the second data asset ownership management method based on a unified data standard, as provided in this application embodiment, is shown below. Figure 4As shown, the above method also includes S210 to S220, which will be described in detail below.

[0072] S210. Determine the first sub-data field corresponding to the first sub-interval where the number of rights confirmation field information is greater than or equal to a preset number, and determine the second sub-data field corresponding to the second sub-interval where the number of rights confirmation field information is less than a preset number.

[0073] After dividing all first data assets into sub-data fields corresponding to sub-intervals according to the number of rights confirmation field information, the first sub-data field corresponding to the first sub-interval with a number of rights confirmation field information greater than or equal to a preset number can be determined. The first sub-data field can be one or more. The second sub-data field corresponding to the second sub-interval with a number of rights confirmation field information less than a preset number can also be determined. The second sub-data field can also be one or more.

[0074] For example, the preset quantity can be 8 or 10.

[0075] S220. Store the standard ownership information and data domain verification information of the first data asset in the first sub-data domain on the blockchain storage system, and store the standard ownership information and data domain verification information of the first data asset in the second sub-data domain on a non-blockchain storage system.

[0076] After obtaining the first sub-data domain, it indicates that the number of ownership information fields for the data assets in the first sub-data domain is relatively large, meaning that the data assets in the first sub-data domain are highly popular and important. Therefore, the standard ownership information and data domain verification information of the first data assets in the first sub-data domain can be stored on the blockchain storage system to improve the storage security of the ownership information of the data assets in the first sub-data domain.

[0077] After obtaining the second sub-data domain, it is noted that the number of ownership information fields for data assets in the second sub-data domain is relatively large, indicating that the data assets in the second sub-data domain have low popularity and importance. Therefore, the standard ownership information and data domain verification information of the data assets in the second sub-data domain can be stored on a non-blockchain storage system, that is, the ownership information of the data assets in the second sub-data domain can be stored in the same way as ordinary storage to reduce data storage costs.

[0078] The beneficial effect of the above implementation method is that it stores the standard ownership information and data domain verification information of data assets in the first sub-data domain with high popularity and importance on the blockchain storage system, thereby improving the storage security of the ownership relationship of data assets in the first sub-data domain.

[0079] The beneficial effect of the above implementation method is that storing the standard ownership information and data domain verification information of data assets in the first sub-data domain with lower popularity and importance of data assets on a non-blockchain storage system can reduce the storage cost of data asset ownership relationships.

[0080] Figure 5 A flowchart illustrating the third data asset ownership management method based on a unified data standard provided in this application embodiment is shown below. Figure 5 As shown, the above method also includes S310 to S320, which will be described in detail below.

[0081] S310. Obtain the node importance index of each asset node, determine the average number of ownership field information of all first data assets in each sub-data domain, determine the average node importance index of all asset nodes corresponding to each sub-data domain, and determine the product of the average number of ownership field information and the average node importance index of each sub-data domain as the data domain importance index of each sub-data domain; determine the first sub-data domain whose data domain importance index is greater than or equal to the preset data domain importance index, and determine the second sub-data domain whose data domain importance index is less than the preset data domain importance index.

[0082] After dividing all the first data assets into sub-data domains corresponding to the sub-intervals according to the number of rights confirmation field information, the node importance index of each asset node can be obtained. The node importance index of an asset node represents the importance of the asset node. Then, the mean node importance index of all asset nodes corresponding to each sub-data domain can be determined. The mean node importance index represents the average node importance of all asset nodes corresponding to the sub-data domain.

[0083] At the same time, the average number of ownership field information for all first data assets in each sub-data domain can be determined. The average number of ownership field information represents the average number of ownership relationships for all first data assets in the sub-data domain, thus enabling the average number of field information to represent the popularity of data assets in the sub-data domain.

[0084] After obtaining the mean node importance index of all asset nodes corresponding to each sub-data domain and the mean number of ownership field information of all first data assets in each sub-data domain, the product of the mean number of ownership field information and the mean node importance index of each sub-data domain can be determined as the data domain importance index of each sub-data domain. The data domain importance index represents the importance of all data assets corresponding to the sub-data domain.

[0085] For example, the node importance index for each asset node can be set by the user.

[0086] During operation, a first sub-data domain with a data domain importance index greater than or equal to a preset data domain importance index can be identified, and a second sub-data domain with a data domain importance index less than the preset data domain importance index can be identified. The security requirements for the ownership relationship of data assets in the first sub-data domain are higher, while the security requirements for the ownership relationship of data assets in the second sub-data domain are lower.

[0087] S320. Store the standard ownership information and data domain verification information of the first data asset in the first sub-data domain on the blockchain storage system, and store the standard ownership information and data domain verification information of the first data asset in the second sub-data domain on a non-blockchain storage system.

[0088] After obtaining the data domain importance index corresponding to each sub-data domain, the standard ownership information and data domain verification information of the first data asset in the first sub-data domain can be stored on the blockchain storage system to ensure the security of the storage of the ownership relationship of the data assets corresponding to the sub-data domain with a higher data domain importance index.

[0089] Meanwhile, the standard ownership information and data domain verification information of the first data asset in the second sub-data domain can be stored on a non-blockchain storage system to store the ownership relationship of data assets in sub-data domains with low data domain importance index on a non-blockchain storage system, thereby reducing data storage costs.

[0090] The beneficial effects of the above implementation method are that by determining the product of the average number of ownership field information and the average node importance index corresponding to each sub-data domain as the data domain importance index corresponding to each sub-data domain, and allocating different storage methods for standard ownership information and data domain verification information of data assets according to the data domain importance index, the security of the ownership relationship storage of data assets is further improved, and the scientific nature of the data asset storage strategy is improved.

[0091] In some implementations, in S110 above, determining the data field information in the data field verification information of the first data asset based on the ownership relationship between the first data asset and the asset nodes in the data field corresponding to the first data asset includes: determining the data field information in the data field verification information of the first data asset based on the attribute information of the first data asset, the attribute information of the asset nodes in the data field corresponding to the first data asset, and the ownership relationship information between the first data asset and the asset nodes in the data field corresponding to the first data asset using an encryption algorithm.

[0092] When determining the data field information in the data field verification information of the first data asset, an encryption algorithm can be used to determine the data field information in the data field verification information of the first data asset based on the attribute information of the first data asset, the attribute information of the asset nodes in the data field corresponding to the first data asset, and the ownership relationship information between the first data asset and the asset nodes in the data field corresponding to the first data asset. This achieves encryption of the data field information in the data field verification information of the first data asset, and then the data field information of the first data asset can be verified based on the data field information in the data field verification information of the first data asset.

[0093] Specifically, the encryption algorithm can be a hash encryption algorithm.

[0094] For example, the attribute information of the first data asset may include attribute information such as the file type, size, and creation time of the first data asset.

[0095] For example, the attribute information of the asset node in the data domain corresponding to the first data asset may include the asset node's name, creation time, and other attribute information.

[0096] For example, the ownership relationship information between the first data asset and the asset nodes in the data domain corresponding to the first data asset can be an ownership relationship matrix or vector constructed based on the ownership relationship information between the first data asset and the asset nodes in the data domain corresponding to the first data asset. The ownership relationship matrix or vector uses preset numbers to represent the ownership relationship information between the first data asset and the asset nodes in the data domain corresponding to the first data asset. In this way, the ownership relationship matrix or vector can be used to encrypt and verify the data domain field information of the first data asset to ensure that the ownership relationship of the first data asset is not changed.

[0097] For example, after obtaining the data field information of the first data asset, this information can be stored on a verification server. When retrieving the ownership relationship of the first data asset stored locally, the data field information on the verification server and the locally stored information can be verified first. If the data field information on the verification server and the locally stored information are the same, it indicates that the locally stored information has not been tampered with. If the data field information on the verification server and the locally stored information are different, it indicates that the locally stored information has been tampered with, and the ownership of the first data asset can be re-established to ensure the reliability of the ownership relationship data.

[0098] The beneficial effect of the above implementation method is that, based on the attribute information of the first data asset, the attribute information of the asset node in the data domain corresponding to the first data asset, and the ownership relationship information between the first data asset and the asset node in the data domain corresponding to the first data asset, the data domain field information of the first data asset is verified and encrypted, which improves the security of the storage of the ownership relationship of the first data asset and can prevent data tampering.

[0099] In some implementations, an encryption algorithm is used to determine the data field information in the data field verification information of the first data asset based on the attribute information of the first data asset, the attribute information of the asset nodes in the data domain corresponding to the first data asset, and the ownership relationship information between the first data asset and the asset nodes in the data domain corresponding to the first data asset. This includes: using an encryption algorithm, the encryption algorithm is used to determine the data field information in the data field verification information of the first data asset based on the attribute information of the first data asset, the attribute information of the asset nodes in the data domain corresponding to the first data asset, and the ownership percentage or usage right period between the first data asset and the asset nodes in the data domain corresponding to the first data asset.

[0100] When determining the data field information in the data domain verification information of the first data asset, an encryption algorithm can be used to determine the data field information in the data domain verification information of the first data asset based on the attribute information of the first data asset, the attribute information of the asset nodes in the data domain corresponding to the first data asset, and the ownership percentage or usage right term between the first data asset and the asset nodes in the data domain corresponding to the first data asset. This allows the data field information to be verified by combining the ownership percentage or usage right term information between the first data asset and the asset nodes, thus preventing the percentage of ownership between the data asset and the asset nodes from being tampered with and improving the security of the ownership relationship of the data asset.

[0101] The beneficial effect of the above implementation method is that by combining the verification of the ownership percentage or usage percentage between data assets and asset nodes to the data domain field information, it is possible to prevent the ownership percentage between data assets and asset nodes from being tampered with.

[0102] This application also provides a data asset ownership confirmation management system based on a unified data standard, including a unit for performing the method described in any of the above embodiments.

[0103] Figure 6 A schematic diagram of the logical structure of a data asset ownership confirmation management system based on a unified data standard, provided as an embodiment of this application, is shown below. Figure 6As shown, the system 1 of this embodiment includes a processing unit 11, a storage unit 12, and a transceiver unit 13. The processing unit 11 is used to process data, the storage unit 12 is used to store data, and the transceiver unit 13 is used to send and receive data. The processing unit 11, the storage unit 12, and the transceiver unit 13 cooperate with each other to implement the above-described method. The beneficial effects brought by the embodiments of this application have been described in the above-described method and will not be repeated here.

[0104] This application also provides a data asset ownership management system based on a unified data standard, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the method described in any of the preceding claims.

[0105] Figure 7 A schematic diagram of the physical structure of a data asset ownership confirmation management system based on a unified data standard, provided as an embodiment of this application, is shown below. Figure 7 As shown, the system 2 of this embodiment includes: at least one processor 20 ( Figure 7 Only one processor 20, a memory 21, and a computer program 22 stored in the memory 21 and executable on the at least one processor 20 are shown. When the processor 20 executes the computer program 22, it implements the steps in any of the above method embodiments. The beneficial effects of the embodiments of this application have been described in the above methods and will not be repeated here.

[0106] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0107] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0108] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various method embodiments above.

[0109] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the above-described method embodiments.

[0110] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0111] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0112] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0113] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0114] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0115] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A data asset ownership management method based on a unified data standard, characterized in that, The method includes: Standard ownership information and data domain verification information are constructed for multiple data assets across multiple asset nodes. The standard ownership information includes multiple ownership confirmation fields, and the data domain verification information includes multiple data domain fields. The ownership confirmation fields are used to determine the ownership information of the data assets, and the data domain fields are used to determine the data domains corresponding to the data assets. Specifically, based on the first ownership relationship between the first data asset and the first asset node and the second asset node, the first ownership confirmation field information in the first standard ownership information of the first data asset is determined, and based on the ownership relationship between the first data asset and the asset nodes in the data domain corresponding to the first data asset, the data domain fields in the data domain verification information of the first data asset are determined. Obtain the number of data assets in each data domain. When the number of first data assets in the first data domain is greater than the preset number, divide the first data domain into multiple sub-data domains, each of which includes multiple first data assets. Each sub-data domain corresponds to multiple sub-asset nodes. Update the data domain field information in the data domain verification information of the sub-data assets according to the ownership relationship between the sub-data assets and the sub-asset nodes. When the number of first data assets in the first data domain is greater than the preset number, obtain the number of ownership confirmation field information in the standard ownership information of each first data asset, and determine the range of ownership confirmation field information corresponding to the number of ownership confirmation field information in the standard ownership information of all first data assets. The number of rights confirmation field information intervals is divided into multiple sub-intervals according to the data intervals. Each sub-interval corresponds to a sub-data field, and all first data assets are divided into the sub-data fields corresponding to the sub-intervals according to the number of rights confirmation field information.

2. The method as described in claim 1, characterized in that, The method further includes: Determine the first sub-data field corresponding to the first sub-interval where the number of rights confirmation field information is greater than or equal to a preset number, and determine the second sub-data field corresponding to the second sub-interval where the number of rights confirmation field information is less than a preset number; The standard ownership information and data domain verification information of the first data asset in the first sub-data domain are stored on the blockchain storage system, while the standard ownership information and data domain verification information of the first data asset in the second sub-data domain are stored on a non-blockchain storage system.

3. The method as described in claim 2, characterized in that, The method further includes: Obtain the node importance index for each asset node; determine the average number of ownership field information items for all first data assets in each sub-data domain; determine the average node importance index for all asset nodes corresponding to each sub-data domain; and determine the product of the average number of ownership field information items and the average node importance index for each sub-data domain as the data domain importance index for each sub-data domain; determine the first sub-data domain whose data domain importance index is greater than or equal to the preset data domain importance index; and determine the second sub-data domain whose data domain importance index is less than the preset data domain importance index. The standard ownership information and data domain verification information of the first data asset in the first sub-data domain are stored on the blockchain storage system, while the standard ownership information and data domain verification information of the first data asset in the second sub-data domain are stored on a non-blockchain storage system.

4. The method as described in claim 3, characterized in that, Based on the ownership relationship between the first data asset and the asset nodes in the corresponding data domain, the data domain field information in the data domain verification information of the first data asset is determined, including: By using an encryption algorithm, the data field information in the data field verification information of the first data asset is determined based on the attribute information of the first data asset, the attribute information of the asset node in the data field corresponding to the first data asset, and the ownership relationship information between the first data asset and the asset node in the data field corresponding to the first data asset.

5. The method as described in claim 4, characterized in that, Using an encryption algorithm, based on the attribute information of the first data asset, the attribute information of the asset nodes in the data domain corresponding to the first data asset, and the ownership relationship information between the first data asset and the asset nodes in the data domain corresponding to the first data asset, the data domain field information in the data domain verification information of the first data asset is determined, including: The encryption algorithm determines the data field information in the data field verification information of the first data asset based on the attribute information of the first data asset, the attribute information of the asset node in the data field corresponding to the first data asset, and the ownership percentage or usage right period between the first data asset and the asset node in the data field corresponding to the first data asset.

6. A data asset ownership confirmation and management system based on a unified data standard, characterized in that, Includes a unit for performing the method according to any one of claims 1 to 5.

7. A data asset ownership confirmation and management system based on a unified data standard, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 5.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 5.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images