Data asset management method and device, electronic equipment, medium and program product

Abstract

The application discloses a data asset management method and device, electronic equipment, medium and program product, and relates to the technical field of computers. The method comprises the following steps: performing relevance query on at least one data node on a block chain, wherein the relevance query is used for querying the relevance between a to-be-managed asset and a digital asset pre-stored in the data node; obtaining a query result of the relevance query fed back by the at least one data node; and determining an asset type of the to-be-managed asset based on the query result through block chain consensus, wherein the asset type comprises an added asset type, an inventory asset type and an abnormal asset type. The embodiment of the application can accurately describe the internal business logic or demand content of business assets, and improve the identification accuracy of business assets.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, and particularly relates to a data asset management method and device, electronic equipment, medium and program product. BACKGROUND

[0002] Business assets are data assets formed in the process of business implementation or business development, such as business process diagrams, business requirement analysis documents, etc. At present, when designing a new requirement business process, it is usually necessary to judge the repeated use of existing business assets and inventory business assets by referring to the existing business assets, and it is also necessary to judge whether the current requirement can form a new business asset, that is, whether it is a new business asset needs to be identified. However, the business asset management scheme in the related art is limited by the knowledge reserve or language expression habit of the business task or technical support personnel, and it is difficult to accurately describe the internal business logic or requirement content of the business asset, resulting in inaccurate business asset identification. SUMMARY

[0003] The embodiments of the present application provide a data asset management method and device, electronic equipment, medium and program product, which can improve the accuracy of business asset identification.

[0004] In a first aspect, the embodiments of the present application provide a data asset management method, comprising:

[0005] Performing an association query on at least one data node on a blockchain, the association query being used to query the association of a to-be-managed asset with a digital asset pre-stored in the data node;

[0006] Obtaining a query result for the association query fed back by the at least one data node;

[0007] Determining an asset type of the to-be-managed asset based on the query result through blockchain consensus, the asset type including a new asset type, an inventory asset type and an abnormal asset type.

[0008] Optionally, before the association query on the at least one data node on the blockchain, the method further comprises:

[0009] In the case that the to-be-managed asset is a data asset in units of requirements, assigning a first identifier to the to-be-managed asset;

[0010] In the case that there is a directory in the requirement document of the to-be-managed asset, reading directory structure information of the to-be-managed asset;

[0011] In a case where a directory name in the directory structure information matches a meta asset, first serial number information is assigned to the to-be-managed asset based on the directory structure information, and the meta asset is a basic business asset in the blockchain;

[0012] A first asset array corresponding to the to-be-managed asset is constructed based on the first identifier, the first serial number information, and a second identifier of the meta asset;

[0013] The first serial number information includes a first directory level serial number in the directory structure information, a first natural paragraph serial number, and a first order serial number in which the to-be-managed asset matches the meta asset, and the first natural paragraph serial number includes a paragraph number of text content of a requirement document of the to-be-managed asset.

[0014] Optionally, the method further includes:

[0015] In a case where a directory name in the directory structure information does not match a meta asset, it is confirmed that a directory existing in the to-be-managed asset is invalid, and the meta asset is an asset associated with a basic business asset of the to-be-managed asset and pre-stored on the blockchain.

[0016] Optionally, the method further includes:

[0017] In a case where a directory does not exist in a requirement document of the to-be-managed asset, and text content of the requirement document matches the meta asset, or in a case where a directory name in the directory structure information does not match the meta asset, second serial number information is assigned to the to-be-managed asset.

[0018] A second asset array corresponding to the to-be-managed asset is constructed based on the first identifier, the second serial number information, and a second identifier of the meta asset.

[0019] The second serial number information includes a second directory level serial number, a second natural paragraph serial number, and a second order serial number in which the to-be-managed asset matches the meta asset, the second directory level serial number is a directory level serial number in the meta asset that matches the text content of the requirement document, and the second natural paragraph serial number includes a paragraph number of the text content of the requirement document.

[0020] Optionally, the determining, by the blockchain consensus, the asset type of the to-be-managed asset based on the query result includes:

[0021] In a case where a number of first data nodes in the at least one data node is greater than or equal to a preset number, and the query result corresponding to each first data node is consistent, the asset type of the to-be-managed asset is determined to be the new asset type or the stock asset type.

[0022] In a case where a number of second data nodes in the at least one data node is less than the preset number, and the query result corresponding to each of the second data nodes indicates consistency, the asset type of the asset to be managed is determined as the abnormal asset type.

[0023] Optionally, the association query request carries an asset array corresponding to the asset to be managed, the asset array corresponding to the asset to be managed including a first identifier of the asset to be managed, serial number information, and a second identifier of a meta asset, the serial number information including a directory level serial number, a natural segment serial number, and an order serial number of matching of the asset to be managed and the meta asset, wherein the meta asset is an asset associated with a basic business asset of the asset to be managed and pre-stored on the blockchain.

[0024] The association query request is used at least to obtain a first query result, and the first query result is used to represent a verification result of whether the first identifier is consistent with a third identifier of a digital asset pre-recorded by the data node.

[0025] Optionally, the determination of the asset type of the asset to be managed as the newly-added asset type or the inventory asset type includes at least one of the following:

[0026] In a case where the first query result indicates that the first identifier is consistent with the third identifier, the asset type of the asset to be managed is determined as an inventory asset type in the blockchain.

[0027] In a case where the first query result indicates that the first identifier is inconsistent with the third identifier, the asset type of the asset to be managed is determined as a newly-added asset type in the blockchain.

[0028] Optionally, the method further includes:

[0029] obtaining a first proportion, a second proportion, and a third proportion;

[0030] The first proportion is a proportion of serial number information that is the same in the asset array and target information, the second proportion is a proportion of document content of a requirement document of the asset to be managed that matches asset content in the target information, and the third proportion is a proportion of the document content of the requirement document of the asset to be managed and serial number information that completely corresponds to basic business asset content and serial number information in the target information. The target information includes meta asset content and serial number information recorded on a data block in the blockchain that stores the meta asset.

[0031] Optionally, the method further includes at least one of the following:

[0032] in a case where the first proportion is greater than or equal to a first threshold value and the asset type of the asset to be managed is the inventory asset type, returning the asset to be managed to a requestor who initiates a management request for the asset to be managed;

[0033] in a case where the first proportion is greater than or equal to a first threshold value and the asset type of the asset to be managed is the inventory asset type, returning the asset to be managed to a requestor who initiates a management request for the asset to be managed;

[0034] in a case where the first proportion is less than the first threshold value and the second proportion is greater than or equal to a second threshold value, confirming that the asset type of the asset to be managed is a first other type;

[0035] in a case where the first proportion is less than the first threshold value and the third proportion is greater than or equal to a third threshold value, confirming that the asset type of the asset to be managed is a second other type;

[0036] The first other type is an asset type that has the same asset content as the existing asset in the blockchain but has a different asset structure, and the second other type is an asset type that has the same asset structure as the existing asset in the blockchain but has a different asset content.

[0037] Optionally, the method further comprises:

[0038] in a case where the asset type of the asset to be managed is the inventory asset type and modification needs to be performed on the asset to be managed, constructing a first private chain in the blockchain according to the order of version numbers generated when the management request for the asset to be managed is received, and storing the asset to be managed on the first private chain;

[0039] in a case where the asset type of the asset to be managed is the inventory asset type and the asset to be managed needs to be deleted, constructing a second private chain in the blockchain according to the order of the version numbers, and adjusting the serial number information of the asset to be managed received subsequently in a case where the deletion processing of the asset to be managed is completed;

[0040] in a case where the asset type of the asset to be managed is the inventory asset type, creating a target node for storing the asset to be managed on the blockchain, and connecting the target node and the data node associated with the meta asset of the asset to be managed to construct an asset chain.

[0041] Optionally, the connecting the target node and the data node associated with the meta asset of the asset to be managed to construct an asset chain comprises:

[0042] sending, in sequence according to the serial numbers of the meta assets, the asset array and the version number corresponding to the to-be-managed asset to the data nodes associated with the meta assets;

[0043] connecting, according to the serial numbers of the meta assets, the data nodes associated with the target node and the meta assets to construct the asset chain.

[0044] In a second aspect, the embodiments of the present application further provide a data asset management apparatus, comprising:

[0045] The first sending module is configured to perform an association query on at least one data node on a block chain, the association query being used to query the association of a to-be-managed asset with a digital asset pre-stored in the data node.

[0046] The first receiving module is configured to acquire a query result for the association query fed back by the at least one data node.

[0047] The first determining module is configured to determine, through a block chain consensus, an asset type of the to-be-managed asset based on the query result, the asset type including an added asset type, a stock asset type, and an abnormal asset type.

[0048] In a third aspect, the embodiments of the present application provide an electronic device, comprising a processor, a memory, and a program stored in the memory and executable on the processor, and the program, when executed by the processor, implements the steps of the data asset management method according to any one of the first aspect.

[0049] In a fourth aspect, the embodiments of the present application further provide a computer readable storage medium, and the computer readable storage medium stores a computer program, and the computer program, when executed by a processor, implements the steps of the data asset management method according to any one of the first aspect.

[0050] In a fifth aspect, the embodiments of the present application further provide a computer program product stored in a storage medium, and the computer program product is executed by at least one processor to implement the steps of the data asset management method according to any one of the first aspect.

[0051] In the embodiment of the present application, the association query request is sent to each data node on the blockchain to query the association between the to-be-managed asset and the digital asset pre-stored in the data node, and then the asset type of the to-be-managed asset is determined according to the query structure fed back by each data node according to the consensus principle of the blockchain. The asset type specifically includes a new asset type, a stock asset type and an abnormal asset type. It can be known that the embodiment of the present application can accurately describe the internal business logic or demand content of the to-be-managed data asset through the association query and consensus mechanism of the blockchain, realizes the accurate classification of the data asset, and improves the data asset management efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0052] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the description of the embodiments of the present application will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0053] Figure 1 is a schematic diagram of a data asset management system to which the data asset management method in the embodiment of the present application is applied;

[0054] Figure 2 is a flowchart of a data asset management method in the embodiment of the present application;

[0055] Figure 3 is a schematic diagram of a data asset management device in the embodiment of the present application;

[0056] Figure 4 is a schematic diagram of an electronic device in the embodiment of the present application. DETAILED DESCRIPTION

[0057] The technical solutions of the embodiments of the present application will be described clearly and completely in the following with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0058] The embodiments of the present application provide a data asset management method, device, electronic device, medium and program product. The embodiments of the present application will be described in detail below with reference to the drawings and through specific embodiments and application scenarios.

[0059] It is worth mentioning that the data asset management method in the embodiments of the present application can be applied to a business asset verification module in a data asset management system.

[0060] Specifically, as shown in Figure 1 The data asset management module includes an asset editing module, a meta asset module, an asset chain module, an asset chain construction module, and an asset verification module. The main function of the asset editing module is to provide query, editing (such as adding and changing), and other operations of business assets and other data assets. Compared with the traditional asset editing module, the asset editing module in the embodiment of the present application can interact with the asset chain construction module, the asset chain verification module, and the like. The meta asset module contains meta assets, which are the basic units of data assets and are used to describe and store basic information of business requirements or business functions. Meta assets can be generally divided into two categories: assets based on basic businesses and assets based on requirements. Assets based on requirements have a mutual inclusion relationship and also contain assets based on basic businesses. The asset chain module can describe and record the business relationship of assets through a block chain data structure and control changes to the asset chain through a smart contract. The asset chain construction module can create business assets that meet the business asset chain rules or control changes to existing assets according to the business relationship defined by the assets. The business asset verification module can initiate a verification query to the business asset chain according to the key information of the assets, thereby obtaining accurate identification and prompts of the business asset chain. Thus, the embodiment of the present application is specifically applied to the business asset verification module to achieve accurate identification and classification of the assets to be managed.

[0061] Please refer to Figure 2 , Figure 2 is a flowchart of a data asset management method in the embodiment of the present application, which specifically includes the following steps:

[0062] Step 101: Perform an association query on at least one data node on a block chain. The association query is used to query the association between the asset to be managed and the digital assets pre-stored in the data node.

[0063] It can be understood that when the requestor of the asset to be managed completes data asset editing, such as adding or modifying assets, through the asset editing module, and obtains the asset chain of the asset to be managed, the asset verification module can initiate a verification broadcast to the asset chain of the asset to be managed, triggering an association query on the asset chain of the block chain. The association query can include identification information of the asset to be managed, identification information of the basic business asset of the asset to be managed, and structure information of the asset to be managed. Thus, each data node receiving the association query matches the pre-stored assets in the data node based on the identification information and structure information of the asset to be managed, obtains a matching result, and sends the matching result as a query result to the asset verification module, which further identifies and classifies the asset to be managed according to the query result.

[0064] In the above steps, the data assets of the blockchain can be parsed in advance, the asset content structure of the data assets constituting the blockchain is split into multiple data nodes, and the multiple data nodes and the inter-node relationship are constructed into a chain data according to the principle of the blockchain to be stored, so as to obtain a data asset chain. Thus, the embodiments of the present application can clearly describe the key data and structure inside the blockchain, and can clearly describe the access or calling relationship of different to-be-managed assets to the same data node. For example, the product development needs of an operator can include the description of many data such as basic functions, public services, basic prices, basic resources, and individual services related to the product. In the traditional mode, these information is usually described in a piece of text coupled together, while through the embodiments of the present application, not only the requirement content can be clearly described, but also the relationship between other requirements and corresponding functions, services, resources, and prices can be clearly described. At the same time, based on the data node calculation of the asset chain, the asset verification module can judge the repeatability and similarity of the to-be-managed assets and the assets in the blockchain according to the relevance, so as to solve the problem of low accuracy caused by the use of single features such as tags and directories for recognition and prompting in the traditional mode, thereby more efficiently and accurately realizing the recognition and prompting of data assets.

[0065] Optionally, before the relevance query on the at least one data node on the blockchain, the method further comprises:

[0066] In the case that the to-be-managed asset is a data asset in units of requirements, a first identifier is allocated to the to-be-managed asset;

[0067] In the case that there is a directory in the requirement document of the to-be-managed asset, directory structure information of the to-be-managed asset is read;

[0068] In the case that the directory name in the directory structure information matches a meta asset, a first serial number information is allocated to the to-be-managed asset based on the directory structure information, and the meta asset is a basic business asset in the blockchain;

[0069] Based on the first identifier, the first serial number information, and a second identifier of the meta asset, a first asset array corresponding to the to-be-managed asset is constructed;

[0070] The first serial number information includes a first directory level serial number, a first natural paragraph serial number in the directory structure information, and a first order serial number of the matching of the to-be-managed asset and the meta asset, and the first natural paragraph serial number includes a paragraph number of the text content of the requirement document of the to-be-managed asset.

[0071] Optionally, the method further comprises:

[0072] In a case where the directory name in the directory structure information does not match the meta asset, it is confirmed that the directory existing in the to-be-managed asset is invalid, and the meta asset is an asset associated with a basic business asset of the to-be-managed asset and pre-stored on the blockchain.

[0073] It is worth mentioning that, since the basic business asset is a general, standardized and stable business component, it usually does not directly correspond to a specific business demand, but serves as a "building block" for other business assets. The basic business asset (such as a payment interface, an identity authentication service, a basic price rule, etc.) usually has a fixed data structure, and the basic business asset is a general component that is reused by multiple demand assets, and its core value lies in being directly callable. Therefore, for a data asset in units of basic business, it can not be structurally parsed, and only a unique identifier (ID) needs to be assigned.

[0074] In some embodiments, for a business asset in units of demand, a unique corresponding identifier, i.e., a first identifier, can be assigned. Further, the demand asset is a description for a specific business scenario, usually containing a reference to a basic business asset, and possibly containing other demand assets. Its structure is complex and dynamic, so structural parsing is needed to extract key data nodes to ensure the accuracy and traceability of the asset chain.

[0075] In the embodiments of the present application, in a case where the to-be-managed asset is a data asset in units of demand, the directory structure information of the to-be-managed asset can be read to determine whether the directory structure information meets the description requirements of the asset chain in the blockchain, i.e., whether the directory name matches the existing business meta asset in the blockchain.

[0076] The above directory structure information can include directory name, directory hierarchy relationship, etc., and can specifically include directory hierarchy sequence number (such as "1.1", "2.3"), natural paragraph sequence number (such as "1st paragraph", "2nd paragraph"), and matching order sequence number (such as "1st matching", "2nd matching"), etc. For example, the demand document "5G package design demand" contains the following directory structure:

[0077] 1. Tariff design

[0078] 1.1 Basic price rule

[0079] 1.2 Package tariff

[0080] 2. Resource allocation

[0081] 2.1 Basic resource configuration

[0082] 3. Service configuration

[0083] 3.1 Public service call

[0084] Reading the above directory structure information can obtain the directory level sequence number (for example, "1.1", "2.1") and the paragraph sequence number (for example, "1st paragraph").

[0085] In one specific embodiment, the directory name can be matched with the name of the meta asset (basic business asset) in the blockchain. If the directory name is successfully matched with the meta asset name, the sequence number is continued to be assigned; if the matching fails, it is prompted that the directory is invalid. For example, the directory name "basic price rule" is matched with the meta asset ID B456 (basic price rule). The directory name "public service call" is matched with the meta asset ID D012 (public service asset). If the directory name "resource allocation" is not matched with the meta asset, it is prompted that "the directory is invalid and is considered as non-existent directory".

[0086] Further, the first sequence number information can be assigned to the to-be-managed asset, and the first sequence number information can be composed of three parts, including the directory level sequence number, the paragraph sequence number and the matching sequence number, and the first sequence number information can be used to identify the reference position of the meta asset in the demand asset, so as to ensure the clear structure of the asset chain.

[0087] Exemplarily, for the directory "1.1 basic price rule" in the to-be-managed asset, the first sequence number information that can be assigned to it is:

[0088] The directory level sequence number is "1.1";

[0089] The paragraph sequence number is "1st paragraph";

[0090] The matching sequence number is "1st matching".

[0091] For the directory "3.1 public service call" in the to-be-managed asset, the first sequence number information that can be assigned to it is:

[0092] The directory level sequence number is "3.1";

[0093] The paragraph sequence number is "2nd paragraph";

[0094] The matching sequence number is "2nd matching".

[0095] Therefore, the first identifier (demand asset ID), the first sequence number information (directory level, paragraph, matching sequence) and the second identifier of the meta asset (basic business asset ID) can be combined into the first asset array. The second identifier of the meta asset can be the unique ID of the basic business asset, which is used to associate the demand asset with the basic business asset.

[0096] In this way, the above embodiment realizes accurate management of demand assets through directory structure analysis, meta-asset matching and asset array construction, ensures correct reference relationship through dynamic matching of directory structure and meta-asset, can form clear chain data through three-level serial number structure and asset array, and can further convert the reference relationship between demand assets and meta-asset into an asset array and store it in the blockchain, so as to ensure the integrity and security of the asset chain by using the tamper-proof nature of the blockchain, thereby significantly improving the management efficiency and accuracy of business assets.

[0097] Optionally, the method further comprises:

[0098] In the case that there is no directory in the demand document of the asset to be managed, and the text content of the demand document matches the meta-asset, or in the case that the directory name in the directory structure information does not match the meta-asset, a second serial number information is assigned to the asset to be managed;

[0099] A second asset array corresponding to the asset to be managed is constructed based on the first identifier, the second serial number information and a second identifier of the meta-asset;

[0100] The second serial number information includes a second directory level serial number, a second natural paragraph serial number and a second order serial number of the matching between the asset to be managed and the meta-asset, the second directory level serial number is a directory level serial number in the meta-asset matching the text content of the demand document, and the second natural paragraph serial number includes a paragraph number of the text content of the demand document.

[0101] In some embodiments, the second serial number information is assigned to the asset to be managed in the case that there is no directory in the demand document or the directory name in the directory structure information does not match the meta-asset. In one specific embodiment, it can be checked whether the demand document contains a directory structure (for example, the directory of a Word document or the chapter title of a PDF). If there is no directory, the asset verification module can directly read the text content of the demand document and attempt to match with the meta-asset in the blockchain. If the matching is successful, the second serial number information is assigned to the asset to be managed. In another specific embodiment, the directory structure information of the demand document can be analyzed to check whether the directory name matches the meta-asset name in the blockchain. If the matching fails (for example, the directory name is "resource allocation", but there is no corresponding meta-asset in the blockchain), the asset verification module will ignore the directory name, directly read the text content, and attempt to match with the meta-asset. If the matching is successful, the second serial number information is assigned to the demand asset.

[0102] Exemplarily, the requirement document "5G package design requirement" has no directory, but the text content contains "basic price rule" and "public service call". The asset verification module matches to meta asset B456 (basic price rule) and D012 (public service asset), and assigns the second serial number information to the to-be-managed asset "5G package design requirement".

[0103] Exemplarily, the requirement document contains the directory "resource allocation", but there is no corresponding meta asset in the blockchain. The asset verification module ignores the directory name, directly reads the text content, matches to meta asset C789 (basic resource configuration), and assigns the second serial number information.

[0104] Further, the first identifier (to-be-managed asset ID), the second serial number information (directory level serial number, natural paragraph serial number, matching order serial number), and the second identifier of the meta asset (basic business asset ID) can be combined into a second asset array. The structure of the second serial number information includes:

[0105] Second directory level serial number: the directory level serial number in the meta asset matched by the text content of the requirement document (for example, "1.1");

[0106] Second natural paragraph serial number: the paragraph number of the text content of the requirement document (for example, "paragraph 1");

[0107] Second order serial number: the order of matching the requirement asset and the meta asset (for example, "first matching").

[0108] In this way, through the above embodiments, the meta asset can be matched through the text content when the directory is missing or the name does not match, ensuring the integrity of asset identification. By designing the second serial number information to include the directory level, natural paragraph, and matching order, the structural changes of the requirement document can be dynamically adapted, avoiding confusion caused by repeated directory levels or paragraph numbers, and improving the accuracy of the asset chain. Moreover, the reference relationship between the requirement asset and the meta asset is converted into an asset array and stored in the blockchain, and the integrity and security of the asset chain are ensured by using the tamper-proof nature of the blockchain.

[0109] Step 102, obtaining the query result of the relevance query fed back by the at least one data node.

[0110] In some embodiments, after completing the triggering of the blockchain "relevance query", the asset verification module enters a waiting stage, waiting for the data nodes in the blockchain network to return the query result. The relevance query can verify the relevance of the to-be-managed asset and the basic business asset in the blockchain, ensuring data consistency.

[0111] It can be understood that the association query, that is, the association query contract, is part of the blockchain smart contract and is used to execute the verification logic of the asset chain. If the first identifier of the asset to be managed in the current request is consistent with the identifier of the existing asset recorded in the node data, it is an association query of the inventory asset (that is, the existing asset in the blockchain). If it is inconsistent, it is an association query of the new asset.

[0112] For the existing asset, it can be further verified whether the meta-asset ID and the meta-asset serial number recorded in the data block of the chain where the asset ID is located are consistent with the request content. For the new asset, the blockchain can be searched through the identification of the meta-asset and the serial number of the meta-asset to determine whether there is duplication or conflict.

[0113] The query result can include the verification result of whether the first identifier is consistent with the third identifier of the digital asset recorded by each data node in advance, or can include the first proportion of the data node whose meta-asset serial number is consistent with the serial number of the asset to be managed, the second proportion of the data node whose meta-asset content is consistent with the content of the asset to be managed, and the third proportion of the data node whose meta-asset serial number and content are consistent with the serial number and content of the meta-asset.

[0114] Therefore, the asset verification module can preliminarily verify whether the asset type of the asset to be managed is the inventory asset type or the new asset type through the verification result of whether the first identifier is consistent with the third identifier of the digital asset recorded by each data node in advance, and can further determine the asset type of the asset to be managed as any one of the new asset type, the inventory asset type and the abnormal asset type through the first proportion, the second proportion or the third proportion.

[0115] Step 103, determining the asset type of the asset to be managed based on the query result through blockchain consensus, the asset type including: new asset type, inventory asset type and abnormal asset type.

[0116] It should be noted that the blockchain consensus, that is, dynamically determining the type (new asset, inventory asset or abnormal asset) of the asset to be managed based on the association query result (for example, the same serial number proportion, the same asset proportion, and the complete asset and serial number corresponding proportion), the essence is to ensure the consistency and non-tamperability of the asset type determination through the cooperation of the distributed nodes of the blockchain network.

[0117] The blockchain consensus can be a process in which data nodes in the blockchain network reach an agreement on data or state through preset rules (such as majority voting, PoW / PoS, etc.). In the present embodiment, the credibility of the query result can be verified through the blockchain consensus, that is, through the feedback data (such as the proportion data) of multiple nodes, it is ensured that the asset type determination does not depend on a single node, and data tampering or misjudgment is avoided. According to the statistical result (such as the proportion data) fed back by the nodes, the asset type can be determined through the consensus rule (such as the majority rule).

[0118] In the present embodiment, the association query request is sent to each data node on the blockchain to query the association between the asset to be managed and the digital asset pre-stored in the data node, and then the asset type of the asset to be managed is determined according to the query structure fed back by each data node according to the consensus principle of the blockchain. The asset type specifically includes a new asset type, a stock asset type, and an abnormal asset type. It can be seen that the present embodiment can accurately describe the internal business logic or demand content of the data asset to be managed through the association query and consensus mechanism of the blockchain, accurately classifies the data asset, and improves the data asset management efficiency.

[0119] Optionally, the asset type of the asset to be managed is determined based on the query result through the blockchain consensus, including:

[0120] In the case that the number of first data nodes in the at least one data node is greater than or equal to a preset number, and the query results corresponding to each of the first data nodes are consistent, the asset type of the asset to be managed is determined as the new asset type or the stock asset type.

[0121] In the case that the number of second data nodes in the at least one data node is less than the preset number, and the query results corresponding to each of the second data nodes are consistent, the asset type of the asset to be managed is determined as the abnormal asset type.

[0122] In some embodiments, the determination rules of different asset types can be pre-set according to business needs. For example:

[0123] New asset type: if the proportion of the asset corresponding to the serial number is less than 50%, and the proportion of the same asset is less than 50%, the asset is determined as a new asset;

[0124] Stock asset type: if the proportion of the asset corresponding to the serial number is greater than or equal to 90%, and the proportion of the same asset is greater than or equal to 90%, the asset is determined as a stock asset;

[0125] Abnormal asset type: if the node result difference is large (for example, some nodes return a high proportion and some nodes return a low proportion), the asset is determined as an abnormal asset.

[0126] Further, if more than 50% of the data nodes think that the asset is a newly added asset, it is determined to be a newly added asset. If more than 50% of the data nodes think that the asset is a stock asset, it is determined to be a stock asset. If the node results differ greatly (for example, some nodes return a high proportion and some return a low proportion), it is determined to be an abnormal asset. In this way, the smart contract on the blockchain automatically calculates and outputs the asset type according to the preset rules (such as threshold), without human intervention.

[0127] In this way, the embodiments of the present application use the blockchain consensus mechanism to determine the type of the asset to be managed, which does not depend on a single node, but through the consensus result of multiple nodes, ensures that the data is tamper-proof, and uses the smart contract and the preset rules (such as majority voting, threshold judgment) to ensure the fairness and consistency of the determination result, effectively improves the credibility, transparency and efficiency of the asset chain management, realizes the accurate classification of the data assets, and improves the data asset management efficiency.

[0128] Optionally, the association query request carries an asset array corresponding to the asset to be managed, and the asset array corresponding to the asset to be managed includes a first identifier of the asset to be managed, serial number information, and a second identifier of a meta asset. The serial number information includes a directory level serial number, a natural paragraph serial number, and a sequence serial number of matching the asset to be managed with the meta asset. The meta asset is an asset associated with the basic business asset of the asset to be managed and pre-stored on the blockchain.

[0129] The association query request is used at least to obtain a first query result, and the first query result is used to represent a verification result of whether the first identifier is consistent with a third identifier of a digital asset pre-recorded by the data node.

[0130] In some embodiments, the association query request carries an asset array corresponding to the asset to be managed, and the structure is as follows:

[0131] The first identifier: a unique identifier (such as A123) of the asset to be managed, used to uniquely identify the asset (such as a demand asset);

[0132] The serial number information includes: a directory level serial number: a directory level of referencing the meta asset in the demand asset; a natural paragraph serial number: a text paragraph number of referencing the meta asset in the demand asset; and a matching sequence serial number: a sequence (such as the first matching) of matching the asset to be managed with the meta asset.

[0133] The second identifier of the meta asset: a unique identifier (such as B456) of the basic business asset pre-stored on the blockchain, indicating the meta asset referenced by the asset to be managed.

[0134] In this way, the asset array can record the reference relationship (such as the directory level, the paragraph position, and the matching order) between the to-be-managed asset and the meta asset, and ensure the structured storage of the asset chain.

[0135] The above correlation query request carries an asset array, which is used to verify the correlation between the to-be-managed asset and the meta asset stored on the blockchain. It can be verified whether the first identifier is consistent with the third identifier (such as the meta asset ID) of the digital asset recorded in the data node in advance. For example, if the ID of the to-be-managed asset is A123, and A123 already exists in the data node, the update logic may be triggered; if it does not exist, it may be processed as a new asset. It can also be verified whether the first identifier is consistent with the third identifier: consistent, which means that the to-be-managed asset may already exist, and further checking of the reference relationship (such as the meta asset ID and the serial number) is required. Inconsistent means that the to-be-managed asset is a new asset, and a new chain or an asset chain needs to be created.

[0136] It can be understood that the first query result is the feedback of the data node to the correlation query request, which is used to verify whether the first identifier of the to-be-managed asset is consistent with the third identifier of the digital asset stored on the blockchain. For example, whether the first identifier (to-be-managed asset ID) matches the third identifier (digital asset ID stored in the data node). If the first identifier of the to-be-managed asset is A123, and the third identifier of the digital asset stored in the data node is A123, a consistent result is returned; otherwise, an inconsistent result is returned.

[0137] In this way, the asset array can record the reference relationship (such as the directory level, the paragraph position, and the matching order) between the to-be-managed asset and the meta asset, and ensure the structured storage of the asset chain.

[0138] Optionally, the determining that the asset type of the to-be-managed asset is the new asset type or the inventory asset type comprises at least one of the following:

[0139] In a case where the first query result shows that the first identifier is consistent with the third identifier, it is determined that the asset type of the to-be-managed asset is an inventory asset type in the blockchain.

[0140] In a case where the first query result shows that the first identifier is inconsistent with the third identifier, it is determined that the asset type of the to-be-managed asset is a new asset type in the blockchain.

[0141] In some embodiments, the first identifier (e.g., A123) is consistent with the third identifier (e.g., A123), indicating that the asset to be managed already exists in the blockchain. Thus, it can be determined that the asset type of the asset to be managed is the inventory asset type, and it can be further verified whether the reference relationship (e.g., the meta-asset ID and the serial number) is consistent with the request content. For example, the asset to be managed ID is A123, and A123 already exists in the data node. It is determined to be an inventory asset. The asset verification module can check whether the referenced meta-asset ID (e.g., B456) and the serial number (e.g., 1.1-1-1) are consistent with the request content to ensure the accuracy of the asset chain.

[0142] In yet other embodiments, the first identifier is inconsistent with the third identifier, indicating that the asset does not yet exist in the blockchain, and it is determined that the asset type of the asset to be managed is the new asset type, which needs to be added to the asset chain of the blockchain. For example, the first identifier of the asset to be managed is A124, and there is no A124 in the data node. It can be determined to be a new asset. The asset management module can add the asset to be managed and the referenced meta-asset information (e.g., B456 and 1.1-1-1) to the asset chain.

[0143] In this way, the embodiments of the present application can ensure the accuracy of the asset type determination by the unique matching of the first identifier and the third identifier, quickly distinguish between new assets and inventory assets, and ensure the credibility of the asset type determination result.

[0144] Optionally, the method further comprises:

[0145] obtaining a first proportion, a second proportion, and a third proportion;

[0146] The first proportion is the proportion of the serial number information in the asset array that is the same as the serial number information in the target information. The second proportion is the proportion of the document content of the demand document of the asset to be managed that matches the asset content in the target information. The third proportion is the proportion of the document content of the demand document of the asset to be managed and the serial number information that completely corresponds to the basic business asset content and the serial number information in the target information. The target information includes the meta-asset content and the serial number information recorded on the data block in which the meta-asset is stored in the blockchain.

[0147] In some embodiments, in the management of the asset chain of the blockchain, the matching degree with the target information (i.e., the data block content and the serial number information of the meta-asset) stored in the blockchain can be evaluated by three key proportions (i.e., the first proportion, the second proportion, and the third proportion).

[0148] The first proportion, i.e. the proportion of the sequence number information (including the directory level sequence number, the natural paragraph sequence number, and the matching order sequence number) in the asset array and the sequence number information (the sequence number information of the data block record of the meta asset in the blockchain) in the target information. Specifically, to calculate the first proportion, all the sequence number information in the asset array can be traversed, and the sequence number information in the target information can be compared one by one, and then the proportion of the number of matched sequence number information to the total number of sequence number information is calculated to obtain: .

[0149] For example, the sequence number information in the asset array is 1.1-1-1, 3.1-2-2, and the sequence number information in the target information is 1.1-1-1, 3.1-2-2. The first proportion is 100% (complete match). If only 1.1-1-1 in the target information is matched, the first proportion is 50%.

[0150] The second proportion, i.e. the proportion of the demand document content of the asset to be managed and the asset content (the data block content of the meta asset in the blockchain) in the target information. The demand document content can be understood as the text content of the business logic, functional requirements, etc. described in the demand asset. The asset content in the target information can be understood as the text content of the business logic, functional description, etc. of the data block record of the meta asset in the blockchain. Specifically, to calculate the second proportion, the demand document content and the target information content can be subjected to text similarity analysis (such as cosine similarity, edit distance, keyword matching, etc.), and the proportion of the number of matched text content to the total number of text content is calculated to obtain: .

[0151] For example, the demand document content is "basic price rule", and the asset content in the target information is "basic price rule". The second proportion is 100% (complete match). If the asset content in the target information is "basic price strategy", the second proportion can be 70% (partial match).

[0152] The third proportion, i.e. the proportion of the demand document content and the sequence number information of the asset to be managed and the asset content and the sequence number information of the basic business asset in the target information. It can be understood that the complete correspondence means that the document content and the sequence number information of the demand document must be completely consistent with the asset content and the sequence number information of the target information. Specifically, to calculate the third proportion, each sequence number information and the document content in the asset array can be traversed, and the asset content and the sequence number information in the target information can be compared one by one, and then the proportion of the number of completely matched asset array entries to the total number of asset array entries is calculated to obtain: .

[0153] Exemplarily, the asset array entry is {"asset_id": "A123", "meta_asset_id": "B456", "meta_asset_seq": "1.1-1-1"}, the asset content in the target information is B456, the serial number information is 1.1-1-1, and the third proportion is 100% (complete match). If the asset content in the target information is B457, the third proportion is 0% (complete mismatch).

[0154] In this way, the embodiment of the present application can verify the asset chain structure through the first proportion, ensure that the meta asset serial number referenced by the to-be-managed asset is consistent with the meta asset serial number stored in the blockchain. The embodiment of the present application can also verify the business logic consistency through the second proportion, ensure that the requirement document content of the to-be-managed asset is consistent with the business logic of the meta asset. The embodiment of the present application can also verify the integrity of the asset chain through the third proportion, ensure that the reference relationship and content of the to-be-managed asset are completely consistent with the meta asset stored in the blockchain.

[0155] Optionally, the method further comprises at least one of the following:

[0156] In the case that the first proportion is greater than or equal to the first threshold value and the asset type of the to-be-managed asset is the inventory asset type, the to-be-managed asset is returned to a requestor who initiates a management request of the to-be-managed asset;

[0157] In the case that the first proportion is greater than or equal to the first threshold value and the asset type of the to-be-managed asset is the newly-added asset type, the inventory asset consistent with the to-be-managed asset in the blockchain is returned to the requestor;

[0158] In the case that the first proportion is less than the first threshold value and the second proportion is greater than or equal to the second threshold value, it is confirmed that the asset type of the to-be-managed asset is a first other type;

[0159] In the case that the first proportion is less than the first threshold value and the third proportion is greater than or equal to the third threshold value, it is confirmed that the asset type of the to-be-managed asset is a second other type;

[0160] The first other type is an asset type with the same asset content as the existing asset in the blockchain, but with different asset structures, and the second other type is an asset type with the same asset structure as the existing asset in the blockchain, but with different asset content.

[0161] In some embodiments, the first proportion (the proportion of matching serial number information) is greater than or equal to the first threshold value, and the asset to be managed is determined to be an inventory asset (i.e., the asset ID already exists in the blockchain), and the asset verification module can return the asset to be managed to the requester. It can be understood that the matching degree of serial number information is high, which means that the asset chain structure is consistent with the meta-asset stored in the blockchain, and there is no need for further verification. At this time, the reference relationship of the inventory asset already exists, and the asset can be directly returned to the requester. For example, the serial number information of the asset to be managed A123 is completely matched with the serial number of the meta-asset A123 in the blockchain, and the asset type is an inventory asset, and the asset verification module can directly return the asset to the requester.

[0162] In yet another embodiment, the first proportion is greater than or equal to the first threshold value, but the asset to be managed is determined to be a new asset (i.e., the asset ID does not exist in the blockchain), and the inventory asset consistent with the asset to be managed in the blockchain can be returned to the requester. Among them, the matching degree of serial number information is high, but the asset ID is not matched, which may indicate that the asset ID is input incorrectly or there is a conflict in the asset chain reference relationship. The asset verification module can find the inventory asset consistent with the asset structure of the asset to be managed in the blockchain for the requester to refer to. For example, the serial number information of the asset to be managed A124 is matched with the serial number of the meta-asset A123 in the blockchain, but the asset ID is not consistent. The asset verification module can return A123 as a reference.

[0163] In yet another embodiment, the first proportion (the proportion of matching serial number information) is less than the first threshold value, but the second proportion (the proportion of matching document content) is greater than or equal to the second threshold value, and the asset type of the asset to be managed can be confirmed to be a first other type (the asset content is the same, but the asset structure is different). Among them, the matching degree of serial number information is low, but the matching degree of document content is high, which means that the business logic of the asset is consistent, but the reference relationship or structure is different (such as different directory levels, paragraph numbers). The demand document content is consistent with the meta-asset, but the serial number information referred to is not matched. For example, the document content of the asset to be managed A125 is consistent with the meta-asset B456, but the serial number information (such as 1.1-1-1) is not consistent with 1.1-2-1 stored in the blockchain, and the system is determined to be a first other type.

[0164] In yet another embodiment, the first proportion is less than the first threshold, but the third proportion (complete correspondence proportion) is greater than or equal to the third threshold, and it can be determined that the asset type of the asset to be managed is a second other type (the asset structure is the same, but the asset content is different). Wherein, the sequence number information matching degree is low, but the document content is completely corresponding to the sequence number information, which indicates that the reference relationship of the asset is consistent, but the business logic is different (for example, the function description is different). For example, the asset chain structure is consistent with the meta asset, but the demand document content is inconsistent with the meta asset. Illustratively, the sequence number information of the asset to be managed A126 is consistent with the meta asset B456, but the document content (such as "basic price rule") is different from the meta asset content (such as "basic price strategy"), and the system determines that it is a second other type.

[0165] It should be noted that the above first other type can be that the asset content is the same (for example, the demand document content is consistent with the meta asset), but the asset structure is different (for example, the referenced sequence number information is different). For example, the demand document content is "basic price rule", but the referenced sequence number information is 1.1-1-1, while the sequence number of the meta asset stored in the blockchain is 1.1-2-1. The above-mentioned second other type can be that the asset structure is the same (for example, the referenced sequence number information is consistent), but the asset content is different (for example, the demand document content is inconsistent with the meta asset). For example, the referenced sequence number information is 1.1-1-1, but the demand document content is "basic price strategy", and the meta asset content is "basic price rule".

[0166] It can be understood that the above-mentioned first threshold, second threshold and third threshold can be dynamically adjusted according to business needs. In the above-mentioned embodiment, the combination of the proportion threshold and the asset type can realize the accurate classification of the asset (stock asset, new asset, first other type, second other type). Through proportion analysis, the system can identify the structural difference or content difference of the asset chain, support the dynamic update and optimization of the asset chain. Thus, different results can be returned according to the asset type (such as directly returning the asset, returning the reference asset, and prompting the difference type), which improves the efficiency and accuracy of user operation.

[0167] In this way, the above-mentioned embodiments of the present application can realize the dynamic management of the asset chain through the combination of the proportion threshold and the asset type, and improve the accuracy, flexibility and user operation efficiency of the asset chain management.

[0168] Optionally, the method further comprises:

[0169] In the case that the asset type of the asset to be managed is the stock asset type, and the asset to be managed needs to be operated and modified, a first private chain is constructed in the blockchain according to the order of the version number generated when the management request of the asset to be managed is received, and the asset to be managed is stored on the first private chain;

[0170] In the case where the asset type of the asset to be managed is the inventory asset type and the asset to be managed needs to be deleted, a second private chain is constructed in the blockchain according to the order of the version numbers, and the serial number information of the subsequently received asset to be managed is adjusted in the case where the deletion process of the asset to be managed is completed.

[0171] In the case where the asset type of the asset to be managed is the newly added asset type, a target node for storing the asset to be managed is created on the blockchain, and the target node and the data node associated with the meta asset of the asset to be managed are connected to construct an asset chain.

[0172] It should be noted that in the management of the blockchain asset chain, the processing logic of different operations (modification, deletion, and addition) of the inventory asset and the newly added asset can be managed through the version number and the construction of the private chain to realize the dynamic update and data consistency of the asset chain.

[0173] In some embodiments, in the case where the asset type is an inventory asset (i.e., the asset ID already exists in the blockchain) and the asset needs to be modified, a first private chain can be constructed in the blockchain according to the order of the version numbers. The modified asset to be managed can also be stored on the first private chain. The version number management, i.e., a new version number (such as V1.0, V1.1) is generated each time the inventory asset is modified, to ensure that the modification history is traceable. The order of the version numbers (such as increment) is used to identify the update path of the asset chain. For the construction of the private chain, the first private chain is an independent chain in the blockchain network, which is specially used to store the modified asset data. The construction of the private chain ensures that the modification operation does not affect the original asset chain, while retaining the historical version. Illustratively, the original version of asset A123 is V1.0, and V1.1 is generated after modification. The system constructs a private chain Chain_A123_V1.1 in the blockchain to store the modified asset data. In this way, the present embodiment ensures that the modification history of the asset chain is traceable through the version number management, and the construction of the private chain allows the asset to be updated independently, avoiding direct modification of the main chain data.

[0174] In another embodiment, when the asset type is inventory asset and a deletion operation is required, a second private chain can be constructed in the blockchain according to the order of the version number. After the deletion processing is completed, the serial number information of the subsequently received assets to be managed is adjusted. The second private chain can be used to record the metadata of the deletion operation (such as deletion time, operator, and deletion reason). The deletion operation does not directly remove the asset from the main chain, but records the deletion state through the private chain. After the deletion operation, the serial number information (such as directory level, paragraph number) of the subsequent assets needs to be re-allocated to avoid conflicts with the serial number of the deleted asset. For example, if the serial number of asset A123 is 1.1-1-1, the serial number of the subsequent asset can be adjusted to 1.1-2-1. Illustratively, after asset A123 is deleted, the system constructs a private chain Chain_A123_Delete in the blockchain to record the deletion information and adjust the serial number of the subsequent asset (such as 1.1-2-1). In this way, the present embodiment can record the deletion operation through the private chain to ensure that the deletion history is traceable, and can also adjust the serial number information to avoid duplication or conflict of the asset chain.

[0175] In another embodiment, when the asset type is a new asset (i.e., the asset ID does not exist in the blockchain), a target node for storing the asset to be managed can be created on the blockchain. Specifically, the target node can be connected with the data node associated with the meta asset to construct an asset chain. The target node is a new node in the blockchain network, which is specifically used to store the data of the new asset. The creation of the node needs to be verified by the blockchain consensus mechanism (such as PoW / PoS) to ensure the legality of the data. The data node is a node in the blockchain that stores the meta asset information (such as asset ID, meta asset ID, and serial number information). By connecting the target node with the data node, the reference relationship of the asset chain is constructed. For example, the new asset A124 is created as the target node Node_A124 and connected to the data node Node_B456 (meta asset information) to construct the asset chain A124, B456. In this way, the present embodiment ensures the accurate reference relationship between the new asset and the meta asset by connecting the data nodes, and the creation of the target node and the construction of the asset chain are automatically completed by the blockchain network without human intervention.

[0176] It can be understood that the order of the version number (such as increment) is used to identify the update path of the asset chain to ensure the traceability of the modification and deletion operations. In addition, the first private chain (modification operation) and the second private chain (deletion operation) are independent chains in the blockchain network, which are used to store the metadata of the specific operation. The construction of the private chain needs to be verified by the blockchain consensus mechanism (such as smart contract) to ensure data consistency.

[0177] It is also worth mentioning that the connection between the target node and the data node is automatically completed by the smart contract of the blockchain, ensuring the accuracy of the reference relationship of the asset chain. In addition, after the deletion operation, the serial number information of the subsequent assets needs to be re-allocated to avoid conflicts with the serial numbers of the deleted assets. For example, after deleting the serial number 1.1-1-1 of asset A123, the serial numbers of the subsequent assets may be adjusted to 1.1-2-1.

[0178] Optionally, the connecting the data node associated with the meta-asset of the target node and the to-be-managed asset comprises:

[0179] According to the serial number order of the meta-asset, the asset array and the version number corresponding to the to-be-managed asset are sent to the data node associated with the meta-asset in sequence.

[0180] According to the serial number order of the meta-asset, the data node associated with the target node and the meta-asset is connected to construct the asset chain.

[0181] In some embodiments, the meta-asset can be stored in a hierarchical structure in the blockchain (such as directory hierarchy, paragraph number, matching order, etc.), and needs to be processed in logical order (such as from high to low or from left to right) according to its serial number. The asset array contains the metadata of the to-be-managed asset, such as the first identifier of the asset, the second identifier of the meta-asset, the serial number information (directory hierarchy, paragraph number, matching order number), etc. The version number can be used to identify the version of the asset chain (such as V1.0, V1.1), ensuring that the modification history of the asset chain is traceable. Specifically, the serial number order of the meta-asset is traversed, for example, the serial number of the meta-asset is 1.1-1-1, 1.1-2-1, 1.2-1-1, and is processed in hierarchical order in sequence. The asset array and the version number are sent to the data node associated with the meta-asset, and each data node (a node storing meta-asset information) receives the asset array and the version number, and verifies its association with the meta-asset. For example, if the serial number of the meta-asset is 1.1-1-1, the asset array {"asset_id": "A124", "meta_asset_id": "B456", "meta_asset_seq": "1.1-1-1"} and the version number V1.0 are sent to the corresponding data node.

[0182] Further, the target node and the data node can be connected according to the serial number order of the meta-asset to construct the asset chain. The target node can be a storage node of a new asset (such as Node_A124). The data node can be a node storing meta-asset information (such as Node_B456). Thus, by connecting the target node and the data node, a reference relationship of the asset chain is formed (such as A124→B456).

[0183] Specifically, the nodes can be connected in the order of the serial numbers of the meta assets, for example, the serial numbers of the meta assets are 1.1-1-1 and 1.1-2-1, and then the target node Node_A124 is connected with the data nodes Node_B456 and Node_C012 in turn. Subsequently, the reference relationship between the target node and the data nodes is written into the blockchain through the smart contract or the consensus mechanism of the blockchain. Exemplarily, the asset chain is A124→B456 (the serial number of the meta asset B456 is 1.1-1-1); and the asset chain is A124→C012 (the serial number of the meta asset C012 is 1.1-2-1).

[0184] It can be understood that the hierarchical structure of the serial numbers (such as 1.1-1-1) needs to strictly follow the business rules to ensure that the reference relationship of the asset chain is accurate. For example, the directory level 1.1 corresponds to “basic business”, the paragraph number 1 corresponds to “price rules”, and the matching order 1 corresponds to “first reference”. In addition, the construction of the asset chain needs to be verified through the consensus mechanism (such as the smart contract) of the blockchain to ensure the legality of the reference relationship. For example, the smart contract can check the relevance of the target node and the data node to prevent incorrect connection.

[0185] In this way, the embodiments of the present application ensure data consistency by sending the asset array and the version number in the order of the serial numbers of the meta assets, and effectively improve the flexibility, data consistency and traceability of asset chain management by connecting the target node with the data node to construct the reference relationship of the asset chain.

[0186] Please refer to Figure 3 , Figure 3 is one of the schematic diagrams of a data asset management device in the embodiments of the present application, and the data asset management device 200 specifically includes:

[0187] The first sending module 201 is configured to perform relevance query on at least one data node on the blockchain, and the relevance query is used to query the relevance of a to-be-managed asset and a digital asset pre-stored in the data node.

[0188] The first receiving module 202 is configured to obtain a query result for the relevance query fed back by the at least one data node.

[0189] The first determining module 203 is configured to determine the asset type of the to-be-managed asset based on the query result through blockchain consensus, and the asset type includes: a new asset type, a stock asset type and an abnormal asset type.

[0190] Optionally, before the relevance query on the at least one data node on the blockchain, the data asset management device 200 further includes:

[0191] The first allocation module is configured to allocate a first identifier to the asset to be managed in a case where the asset to be managed is a data asset in units of demand.

[0192] The first reading module is configured to read directory structure information of the asset to be managed in a case where a directory exists in a demand document of the asset to be managed.

[0193] The second allocation module is configured to allocate first serial number information to the asset to be managed based on the directory structure information in a case where a directory name in the directory structure information matches a meta asset, the meta asset being a basic business asset in the blockchain.

[0194] The first construction module is configured to construct a first asset array corresponding to the asset to be managed based on the first identifier, the first serial number information, and a second identifier of the meta asset.

[0195] The first serial number information includes a first directory level serial number in the directory structure information, a first natural paragraph serial number, and a first order serial number at which the asset to be managed matches the meta asset, and the first natural paragraph serial number includes a paragraph number of text content in the demand document of the asset to be managed.

[0196] Optionally, the data asset management apparatus 200 further includes:

[0197] The first confirmation module is configured to confirm that a directory existing in the asset to be managed is invalid in a case where a directory name in the directory structure information does not match a meta asset, the meta asset being an asset associated with a basic business asset of the asset to be managed and pre-stored on the blockchain.

[0198] Optionally, the data asset management apparatus 200 further includes:

[0199] The third allocation module is configured to allocate second serial number information to the asset to be managed in a case where no directory exists in a demand document of the asset to be managed and text content of the demand document matches the meta asset, or in a case where a directory name in the directory structure information does not match the meta asset.

[0200] The second construction module is configured to construct a second asset array corresponding to the asset to be managed based on the first identifier, the second serial number information, and a second identifier of the meta asset.

[0201] The second serial number information includes a second directory level serial number, a second natural paragraph serial number, and a second order serial number in which the to-be-managed asset is matched with the meta asset. The second directory level serial number is a directory level serial number in the meta asset matched with the text content of the requirement document. The second natural paragraph serial number includes a paragraph number of the text content of the requirement document.

[0202] Optionally, the first determining module 203 includes:

[0203] The first determining unit is configured to determine, when the number of the first data nodes in the at least one data node is greater than or equal to the preset number and the query results corresponding to each of the first data nodes are consistent, that the asset type of the to-be-managed asset is the newly-added asset type or the inventory asset type.

[0204] The second determining unit is configured to determine, when the number of the second data nodes in the at least one data node is less than the preset number and the query results corresponding to each of the second data nodes are consistent, that the asset type of the to-be-managed asset is the abnormal asset type.

[0205] Optionally, the association query request carries an asset array corresponding to the to-be-managed asset. The asset array corresponding to the to-be-managed asset includes a first identifier of the to-be-managed asset, serial number information, and a second identifier of a meta asset. The serial number information includes a directory level serial number, a natural paragraph serial number, and an order serial number in which the to-be-managed asset is matched with the meta asset. The meta asset is an asset associated with a basic business asset of the to-be-managed asset and pre-stored on the blockchain.

[0206] The association query request is used to obtain at least a first query result. The first query result is used to represent a verification result of whether the first identifier is consistent with a third identifier of a digital asset pre-recorded by the data node.

[0207] Optionally, the first determining unit is configured to perform at least one of the following:

[0208] When the first query result shows that the first identifier is consistent with the third identifier, it is determined that the asset type of the to-be-managed asset is an inventory asset type in the blockchain.

[0209] When the first query result shows that the first identifier is inconsistent with the third identifier, it is determined that the asset type of the to-be-managed asset is a newly-added asset type in the blockchain.

[0210] Optionally, the data asset management apparatus 200 further includes:

[0211] obtaining a first proportion, a second proportion and a third proportion;

[0212] The first proportion is a proportion of the asset array in which the serial number information is the same as the serial number information in the target information, the second proportion is a proportion of the demand document file content of the asset to be managed that matches the asset content in the target information, and the third proportion is a proportion of the demand document file content and serial number information of the asset to be managed that completely corresponds to the basic business asset content and serial number information in the target information. The target information includes the meta-asset content and serial number information recorded on the data block in which the meta-asset is stored in the blockchain.

[0213] Optionally, the data asset management apparatus 200 further comprises at least one of the following:

[0214] The first return module is configured to return the asset to be managed to a requestor who initiates a management request for the asset to be managed, when the first proportion is greater than or equal to a first threshold value and the asset type of the asset to be managed is the inventory asset type.

[0215] The second return module is configured to return an inventory asset consistent with the asset to be managed in the blockchain to the requestor when the first proportion is greater than or equal to the first threshold value and the asset type of the asset to be managed is the newly added asset type.

[0216] The second confirmation module is configured to confirm that the asset type of the asset to be managed is a first other type when the first proportion is less than the first threshold value and the second proportion is greater than or equal to a second threshold value.

[0217] The third confirmation module is configured to confirm that the asset type of the asset to be managed is a second other type when the first proportion is less than the first threshold value and the third proportion is greater than or equal to a third threshold value.

[0218] The first other type is an asset type that has the same asset content as the existing asset in the blockchain but has different asset structures, and the second other type is an asset type that has the same asset structure as the existing asset in the blockchain but has different asset content.

[0219] Optionally, the data asset management apparatus 200 further comprises:

[0220] The third construction module is configured to construct a first private chain in the blockchain according to the order of the version number generated when the management request for the asset to be managed is received, and store the asset to be managed on the first private chain when the asset type of the asset to be managed is the inventory asset type and the asset to be managed needs to be operated and modified.

[0221] The information adjustment module is used to construct a second private chain in the blockchain according to the version number order when the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be deleted, and to adjust the sequence number information of the subsequently received assets to be managed after the asset to be managed is deleted.

[0222] The fourth construction module is used to create a target node on the blockchain for storing the asset to be managed when the asset type of the asset to be managed is the newly added asset type, and to connect the target node and the data node associated with the meta-asset of the asset to be managed to construct an asset chain.

[0223] Optionally, the fourth building module includes:

[0224] The information sending unit is used to send the asset array and the version number corresponding to the asset to be managed to the data node associated with the asset in sequence according to the sequence number of the asset;

[0225] The link construction unit is used to connect the data nodes associated with the target node and the meta-asset according to the sequence number of the meta-asset, and construct the asset chain.

[0226] The data asset management device 200 provided in this application embodiment can perform the above-described... Figure 1 The method embodiments shown demonstrate that the data asset management device 200 in this application is similar in implementation principle and technical effect to... Figure 1 The method embodiment shown is not described in detail here.

[0227] This application also provides an electronic device. Since the principle by which this electronic device solves the problem is similar to the system upgrade method in this application, the implementation of this electronic device can be found elsewhere. Figure 1 The implementation of the method shown will not be repeated here. Figure 4 As shown, the electronic device according to an embodiment of this application includes: a processor 310, configured to read a program from a memory 320 and execute the following processes:

[0228] Perform a correlation query on at least one data node on the blockchain, the correlation query being used to query the correlation between the asset to be managed and the digital assets pre-stored on the data node;

[0229] Obtain the query results for the correlation query returned by the at least one data node;

[0230] Determine, through blockchain consensus, an asset type of the asset to be managed based on the query result, the asset type including: a newly-added asset type, a stock asset type, and an abnormal asset type.

[0231] Optionally, the processor 310 is further configured to read a program in the memory 320, and further perform the following steps:

[0232] In a case where the asset to be managed is a data asset in units of demand, assign a first identifier to the asset to be managed;

[0233] In a case where there is a catalog in a demand document of the asset to be managed, read catalog structure information of the asset to be managed;

[0234] In a case where a catalog name in the catalog structure information matches a meta asset, assign first serial number information to the asset to be managed based on the catalog structure information, the meta asset being a basic business asset in the blockchain;

[0235] Based on the first identifier, the first serial number information, and a second identifier of the meta asset, construct a first asset array corresponding to the asset to be managed;

[0236] The first serial number information includes a first catalog level serial number, a first natural paragraph serial number in the catalog structure information, and a first order serial number at which the asset to be managed matches the meta asset, and the first natural paragraph serial number includes a paragraph number of text content in the demand document of the asset to be managed.

[0237] Optionally, the processor 310 is further configured to read a program in the memory 320, and further perform the following steps:

[0238] In a case where a catalog name in the catalog structure information does not match a meta asset, confirm that a catalog existing in the asset to be managed is invalid, the meta asset being an asset associated with a basic business asset of the asset to be managed and pre-stored on the blockchain.

[0239] Optionally, the processor 310 is further configured to read a program in the memory 320, and further perform the following steps:

[0240] In a case where there is no catalog in a demand document of the asset to be managed, and text content of the demand document matches the meta asset, or in a case where a catalog name in the catalog structure information does not match the meta asset, assign second serial number information to the asset to be managed;

[0241] Based on the first identifier, the second serial number information, and a second identifier of the meta asset, construct a second asset array corresponding to the asset to be managed;

[0242] The second serial number information includes a second directory level serial number, a second natural paragraph serial number, and a second order serial number in which the to-be-managed asset is matched with the meta asset. The second directory level serial number is a directory level serial number in the meta asset matched with the text content of the requirement document. The second natural paragraph serial number includes a paragraph number of the text content of the requirement document.

[0243] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform the following steps:

[0244] In a case where a number of first data nodes in the at least one data node is greater than or equal to a preset number, and the query result corresponding to each first data node is consistent, the asset type of the to-be-managed asset is determined as the newly-added asset type or the inventory asset type.

[0245] In a case where a number of second data nodes in the at least one data node is less than the preset number, and the query result corresponding to each second data node is consistent, the asset type of the to-be-managed asset is determined as the abnormal asset type.

[0246] Optionally, the association query request carries an asset array corresponding to the to-be-managed asset. The asset array corresponding to the to-be-managed asset includes a first identifier of the to-be-managed asset, serial number information, and a second identifier of a meta asset. The serial number information includes a directory level serial number, a natural paragraph serial number, and an order serial number in which the to-be-managed asset is matched with the meta asset. The meta asset is an asset associated with a basic business asset of the to-be-managed asset and pre-stored on the blockchain.

[0247] The association query request is used to obtain at least a first query result. The first query result is used to represent a verification result of whether the first identifier is consistent with a third identifier of a digital asset pre-recorded by the data node.

[0248] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform at least one of the following steps:

[0249] In a case where the first query result shows that the first identifier is consistent with the third identifier, the asset type of the to-be-managed asset is determined as an inventory asset type in the blockchain.

[0250] In a case where the first query result shows that the first identifier is inconsistent with the third identifier, the asset type of the to-be-managed asset is determined as a newly-added asset type in the blockchain.

[0251] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform the following steps:

[0252] obtaining a first proportion, a second proportion and a third proportion;

[0253] The first proportion is a proportion of the serial number information in the asset array being the same as the serial number information in the target information, the second proportion is a proportion of the document content of the demand document of the asset to be managed matching the asset content in the target information, and the third proportion is a proportion of the document content of the demand document of the asset to be managed and the serial number information completely corresponding to the basic business asset content and the serial number information in the target information. The target information includes the meta-asset content and the serial number information recorded on the data block in which the meta-asset is stored in the blockchain.

[0254] Optionally, the processor 310 is further configured to read the program in the memory 320, and further perform at least one of the following steps:

[0255] In a case where the first proportion is greater than or equal to a first threshold value and the asset type of the asset to be managed is the inventory asset type, returning the asset to be managed to a requestor who initiates a management request for the asset to be managed;

[0256] In a case where the first proportion is greater than or equal to a first threshold value and the asset type of the asset to be managed is the newly added asset type, returning an inventory asset consistent with the asset to be managed in the blockchain to the requestor;

[0257] In a case where the first proportion is less than the first threshold value and the second proportion is greater than or equal to a second threshold value, confirming that the asset type of the asset to be managed is a first other type;

[0258] In a case where the first proportion is less than the first threshold value and the third proportion is greater than or equal to a third threshold value, confirming that the asset type of the asset to be managed is a second other type;

[0259] The first other type is an asset type having the same asset content as the existing asset in the blockchain but different asset structure, and the second other type is an asset type having the same asset structure as the existing asset in the blockchain but different asset content.

[0260] Optionally, the processor 310 is further configured to read the program in the memory 320, and further perform the following steps:

[0261] In a case where the asset type of the asset to be managed is the inventory asset type and the asset to be managed needs to be operated and modified, constructing a first private chain in the blockchain according to the order of the version number generated when the management request for the asset to be managed is received, and storing the asset to be managed on the first private chain;

[0262] In a case where the asset type of the asset to be managed is the inventory asset type and the asset to be managed needs to be deleted, a second private chain is constructed in the blockchain according to the order of the version numbers, and in a case where the deletion processing of the asset to be managed is completed, the serial number information of a subsequently received asset to be managed is adjusted;

[0263] In a case where the asset type of the asset to be managed is the newly added asset type, a target node for storing the asset to be managed is created on the blockchain, and the target node and the data node associated with the meta asset of the asset to be managed are connected to construct an asset chain.

[0264] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform the following steps:

[0265] According to the serial number order of the meta asset, the asset array and the version number corresponding to the asset to be managed are sequentially sent to the data node associated with the meta asset;

[0266] According to the serial number order of the meta asset, the asset chain is constructed according to the target node and the data node associated with the meta asset.

[0267] The electronic device provided by the embodiment of the application can perform the method shown in the above Figure 1 The implementation principle and technical effects of the method embodiment shown in the above are similar, and details are not described herein again.

[0268] The embodiment of the application further provides a computer readable storage medium, and the computer readable storage medium stores a computer program. Figure 1 The computer program is executed by a processor to implement each process of the data asset management method embodiment described above, and the same technical effects can be achieved. To avoid repetition, details are not described herein again. The computer readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0269] The embodiment of the application further provides a computer program / product, which is stored in a storage medium and is executed by at least one processor to implement each process of the data asset management method embodiment described above. Figure 1 The computer program / product is executed by at least one processor to implement each process of the data asset management method embodiment described above, and the same technical effects can be achieved. To avoid repetition, details are not described herein again.

[0270] In several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other manners. For example, the described device embodiments are merely illustrative. For example, the division of the units is only a logical function division. There can be another division manner for the actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, devices or units, and can be in electrical, mechanical or other forms.

[0271] In addition, each function unit in the embodiments of the present application can be integrated into a processing unit, or each unit can be physically separated, or two or more than two units are integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software function units.

[0272] The integrated unit implemented in the form of software function units can be stored in a computer readable storage medium. The above software function unit stored in a storage medium includes a plurality of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute part of the steps of the transceiving method described in the embodiments of the present application. The aforementioned storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0273] The above is the preferred embodiment of the present application. It should be pointed out that, for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, which should also be considered as the protection scope of the present application.

Claims

1. A data asset management method characterized by, The method comprises the following steps: performing a relevance query on at least one data node on a blockchain, the relevance query being used to query the relevance of a to-be-managed asset to a digital asset pre-stored in the data node; obtaining a query result for the relevance query fed back by the at least one data node; determining, through blockchain consensus, an asset type of the to-be-managed asset based on the query result, the asset type comprising: a newly-added asset type, a stock asset type, and an abnormal asset type; the step of determining, through blockchain consensus, the asset type of the to-be-managed asset based on the query result comprises: when the number of first data nodes in the at least one data node is greater than or equal to a preset number, and the query result corresponding to each of the first data nodes is consistent, determining that the asset type of the to-be-managed asset is the newly-added asset type or the stock asset type; when the number of second data nodes in the at least one data node is less than the preset number, and the query result corresponding to each of the second data nodes is consistent, determining that the asset type of the to-be-managed asset is the abnormal asset type; the relevance query request carries an asset array corresponding to the to-be-managed asset, the asset array corresponding to the to-be-managed asset comprising a first identifier of the to-be-managed asset, serial number information, and a second identifier of a meta asset, the serial number information comprising a directory level serial number, a natural paragraph serial number, and an order serial number in which the to-be-managed asset is matched with the meta asset, wherein the meta asset is an asset pre-stored on the blockchain and associated with a basic business asset of the to-be-managed asset; the relevance query request is used to obtain at least a first query result, the first query result being used to represent a verification result of whether the first identifier is consistent with a third identifier of a digital asset pre-recorded by the data node.

2. The method of claim 1, wherein, Before the step of performing the relevance query on the at least one data node on the blockchain, the method further comprises: when the to-be-managed asset is a data asset in units of demand, assigning a first identifier to the to-be-managed asset; when there is a directory in a demand document of the to-be-managed asset, reading directory structure information of the to-be-managed asset; when a directory name in the directory structure information matches a meta asset, assigning first serial number information to the to-be-managed asset based on the directory structure information, the meta asset being a basic business asset in the blockchain; based on the first identifier, the first serial number information, and a second identifier of the meta asset, constructing a first asset array corresponding to the to-be-managed asset; wherein the first serial number information comprises a first directory level serial number, a first natural paragraph serial number in the directory structure information, and a first order serial number in which the to-be-managed asset is matched with the meta asset, and the first natural paragraph serial number comprises a paragraph number of text content in a demand document of the to-be-managed asset.

3. The method of claim 2, wherein, The method further comprises: In a case where the directory name in the directory structure information does not match the meta asset, the directory existing in the asset to be managed is confirmed to be invalid, and the meta asset is an asset associated with a basic business asset of the asset to be managed and pre-stored on the blockchain.

4. The method according to claim 2 or 3, characterized in that, The method further includes: In a case where the directory does not exist in the requirement document of the asset to be managed, and the text content of the requirement document matches the meta asset, or in a case where the directory name in the directory structure information does not match the meta asset, a second serial number information is assigned to the asset to be managed; Based on the first identifier, the second serial number information, and a second identifier of the meta asset, a second asset array corresponding to the asset to be managed is constructed; The second serial number information includes a second directory level serial number, a second natural paragraph serial number, and a second order serial number in which the asset to be managed matches the meta asset, the second directory level serial number is a directory level serial number in the meta asset that matches the text content of the requirement document, and the second natural paragraph serial number includes a paragraph number of the text content of the requirement document.

5. The method of claim 1, wherein, The determination of the asset type of the asset to be managed as the new asset type or the inventory asset type includes at least one of the following: In a case where the first query result shows that the first identifier is consistent with the third identifier, it is determined that the asset type of the asset to be managed is the inventory asset type in the blockchain; In a case where the first query result shows that the first identifier is inconsistent with the third identifier, it is determined that the asset type of the asset to be managed is the new asset type in the blockchain.

6. The method of claim 5, wherein, The method further includes: Obtaining a first proportion, a second proportion, and a third proportion; The first proportion is a proportion of serial number information in the asset array that is the same as serial number information in target information, the second proportion is a proportion of document content of the requirement document of the asset to be managed that matches asset content in the target information, and the third proportion is a proportion of document content and serial number information of the requirement document of the asset to be managed that completely corresponds to basic business asset content and serial number information in the target information. The target information includes meta asset content and serial number information recorded on a data block in the blockchain that stores the meta asset.

7. The method of claim 6, wherein, The method further includes at least one of the following: In a case where the first proportion is greater than or equal to a first threshold value, and the asset type of the asset to be managed is the inventory asset type, the asset to be managed is returned to a requestor who initiates a management request for the asset to be managed; In a case where the first proportion is greater than or equal to a first threshold value, and the asset type of the asset to be managed is the new asset type, an inventory asset consistent with the asset to be managed in the blockchain is returned to the requestor; In a case where the first proportion is less than the first threshold value, and the second proportion is greater than or equal to a second threshold value, it is confirmed that the asset type of the asset to be managed is a first other type; In a case where the first proportion is less than the first threshold value and the third proportion is greater than or equal to a third threshold value, it is determined that the asset type of the asset to be managed is a second other type; The first other type is an asset type that is the same in asset content as an existing asset in the blockchain but different in asset structure, and the second other type is an asset type that is the same in asset structure as the existing asset in the blockchain but different in asset content.

8. The method of claim 6, wherein, The method further comprises: In a case where the asset type of the asset to be managed is the inventory asset type and modification is required for the asset to be managed, a first private chain is constructed in the blockchain according to the order of version numbers generated when the management request of the asset to be managed is received, and the asset to be managed is stored on the first private chain; In a case where the asset type of the asset to be managed is the inventory asset type and the asset to be managed needs to be deleted, a second private chain is constructed in the blockchain according to the order of the version numbers, and in a case where the deletion processing of the asset to be managed is completed, the serial number information of a subsequently received asset to be managed is adjusted; In a case where the asset type of the asset to be managed is the newly added asset type, a target node for storing the asset to be managed is created on the blockchain, and the target node and the data node associated with the meta asset of the asset to be managed are connected to construct an asset chain.

9. The method of claim 8, wherein, The connecting of the target node and the data node associated with the meta asset of the asset to be managed to construct the asset chain comprises: According to the serial number order of the meta asset, the asset array corresponding to the asset to be managed and the version number are sequentially sent to the data node associated with the meta asset; According to the serial number order of the meta asset, the data node associated with the target node and the meta asset is connected to construct the asset chain.

10. A data asset management apparatus, characterized by comprising: The device is applied to a Redis server and comprises: A first sending module configured to perform an association query on at least one data node on a blockchain, the association query being configured to query the association of an asset to be managed with a digital asset pre-stored in the data node; A first receiving module configured to obtain a query result for the association query fed back by the at least one data node; A first determining module configured to determine, through blockchain consensus, the asset type of the asset to be managed based on the query result, the asset type comprising a newly added asset type, an inventory asset type, and an abnormal asset type; The first determining module comprises: A first determining unit configured to determine, in a case where the number of first data nodes in the at least one data node is greater than or equal to a preset number and the query result corresponding to each first data node is consistent, that the asset type of the asset to be managed is the newly added asset type or the inventory asset type. The second determination unit is configured to determine that the asset type of the asset to be managed is the abnormal asset type when the number of second data nodes in the at least one data node is less than the preset number, and the query result corresponding to each second data node is consistent. The association query request carries an asset array corresponding to the asset to be managed, the asset array corresponding to the asset to be managed includes a first identifier of the asset to be managed, serial number information and a second identifier of a meta asset, the serial number information includes a directory level serial number, a natural segment serial number and an order serial number of matching the asset to be managed with the meta asset, and the meta asset is an asset associated with a basic business asset of the asset to be managed and pre-stored on the blockchain. The association query request is used to at least obtain a first query result, and the first query result is used to represent a verification result of whether the first identifier is consistent with a third identifier of a digital asset pre-recorded by the data node.

11. An electronic device, comprising: Comprising: A processor, a memory, and a program stored on the memory and executable on the processor, the program being executed by the processor to implement the steps in the data asset management method according to any one of claims 1 to 9.

12. A computer readable storage medium for storing a computer program, characterized in that, The computer program is executed by the processor to implement the steps in the data asset management method according to any one of claims 1 to 9.

13. A computer program product, characterised in that, The computer program is executed by the processor to implement the steps in the data asset management method according to any one of claims 1 to 9.

Images