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

Abstract

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

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data asset management method, device, electronic device, medium, and program product. Background Art

[0002] Business assets are data assets generated during the implementation or development of a business, such as business process diagrams and business requirements analysis documents. Currently, when designing a business process for a new requirement, it is usually necessary to refer to existing business assets to determine the duplication of existing business assets with existing business assets. It is also necessary to determine whether the current requirement can form a new business asset, that is, to identify whether it is a new business asset. However, the business asset management solutions in related technologies are limited by the knowledge reserves or language expression habits of business tasks or technical support personnel, making it difficult to accurately describe the inherent business logic or demand content of business assets, resulting in inaccurate business asset identification. Summary of the Invention

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

[0004] In a first aspect, an embodiment of the present application provides a data asset management method, comprising: Performing a relevance query on at least one data node on the blockchain, wherein the relevance query is used to query the relevance between the asset to be managed and the digital asset pre-stored on the data node; Obtaining a query result for the relevance query fed back by the at least one data node; The asset type of the asset to be managed is determined based on the query result through blockchain consensus, and the asset type includes: new asset type, existing asset type and abnormal asset type.

[0005] Optionally, before performing a relevance query on at least one data node on the blockchain, the method further includes: In a case where the asset to be managed is a data asset based on demand, allocating a first identifier to the asset to be managed; If a directory exists in the requirement document of the asset to be managed, reading directory structure information of the asset to be managed; When the directory name in the directory structure information matches the meta-asset, assigning first serial number information to the asset to be managed based on the directory structure information, where the meta-asset is a basic business asset in the blockchain; Constructing a first asset array corresponding to the asset to be managed based on the first identifier, the first serial number information, and the second identifier of the meta-asset; Among them, the first serial number information includes the first directory level serial number and the first natural paragraph serial number in the directory structure information, and the first sequential serial number for matching the asset to be managed with the meta-asset, and the first natural paragraph serial number includes the paragraph number of the text content in the requirement document of the asset to be managed.

[0006] Optionally, the method further includes: In the event that the directory name in the directory structure information does not match the meta-asset, it is confirmed that the directory existing in the asset to be managed is invalid, and the meta-asset is an asset pre-stored on the blockchain and associated with the basic business asset of the asset to be managed.

[0007] Optionally, the method further includes: If no directory exists in the requirements document of the asset to be managed and the text content of the requirements document matches the meta-asset, or if the directory name in the directory structure information does not match the meta-asset, assigning second serial number information to the asset to be managed; Constructing a second asset array corresponding to the asset to be managed based on the first identifier, the second serial number information, and the second identifier of the meta-asset; Among them, the second serial number information includes a second directory level serial number, a second natural paragraph serial number and a second sequential serial number for matching the asset to be managed with the meta-asset, the second directory level serial number is the 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 the paragraph number of the text content in the requirement document.

[0008] Optionally, determining the asset type of the asset to be managed based on the query result through blockchain consensus includes: If 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, determining that the asset type of the to-be-managed asset is the newly added asset type or the existing 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 results corresponding to each second data node are consistent, it is determined that the asset type of the asset to be managed is the abnormal asset type.

[0009] 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 a sequential serial number for matching the asset to be managed with the meta-asset, wherein the meta-asset is an asset pre-stored on the blockchain and associated with the basic business asset of the asset to be managed; The association query request is at least used to obtain a first query result, and the first query result is used to express a verification result of whether the first identifier is consistent with a third identifier of the digital asset pre-recorded by the data node.

[0010] Optionally, determining whether the asset type of the to-be-managed asset is the newly added asset type or the existing asset type includes at least one of the following: If the first query result shows that the first identifier is consistent with the third identifier, determining that the asset type of the asset to be managed is a stock asset type in the blockchain; 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 asset to be managed is a new asset type in the blockchain.

[0011] Optionally, the method further includes: Get the first ratio, the second ratio and the third ratio; Among them, the first ratio is the ratio of the sequence number information in the asset array to be identical to the sequence number information in the target information, the second ratio is the ratio of the document content in the requirement document of the asset to be managed to match the asset content in the target information, and the third ratio is the ratio of the document content and sequence number information in the requirement document of the asset to be managed to completely correspond to the basic business asset content and sequence number information in the target information; the target information includes the meta-asset content and sequence number information recorded on the data block storing the meta-asset in the blockchain.

[0012] Optionally, the method further comprises at least one of the following: When the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the existing asset type, returning the asset to be managed to the requester who initiated the management request for the asset to be managed; If the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the newly added asset type, returning to the requesting party the existing assets in the blockchain that are consistent with the asset to be managed; When the first ratio is less than the first threshold value and the second ratio is greater than or equal to a second threshold value, confirming that the asset type of the to-be-managed asset is a first other type; When the first ratio is less than the first threshold value and the third ratio is greater than or equal to the third threshold value, confirming that the asset type of the to-be-managed asset is a second other type; Among them, the first other type is an asset type that has the same asset content as the existing assets in the blockchain but has a different asset structure; the second other type is an asset type that has the same asset structure as the existing assets in the blockchain but has a different asset content.

[0013] Optionally, the method further includes: If the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be modified, construct a first private chain in the blockchain according to the order of version numbers generated when receiving the management request for the asset to be managed, and store the asset to be managed on the first private chain; If the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be deleted, construct a second private chain in the blockchain according to the order of the version numbers, and adjust the serial number information of the subsequently received asset to be managed after the deletion of the asset to be managed is completed; 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 build an asset chain.

[0014] Optionally, connecting the target node and the data node associated with the meta-asset of the asset to be managed to build an asset chain includes: Sending the asset array and the version number corresponding to the asset to be managed to the data node associated with the meta-asset in sequence according to the sequence number of the meta-asset; According to the sequence number of the meta-asset, the data nodes associated with the target node and the meta-asset are connected to build the asset chain.

[0015] In a second aspect, an embodiment of the present application further provides a data asset management device, comprising: A first sending module is configured to perform a relevance query on at least one data node on the blockchain, wherein the relevance query is configured to query the relevance between the asset to be managed and the digital asset pre-stored on the data node; A first receiving module, configured to obtain a query result for the relevance query fed back by the at least one data node; The first determination module is used to determine the asset type of the asset to be managed based on the query result through blockchain consensus, where the asset type includes: new asset type, existing asset type and abnormal asset type.

[0016] In a third aspect, an embodiment of the present application provides an electronic device comprising: a processor, a memory, and a program stored on the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the data asset management method as described in any one of the first aspects are implemented.

[0017] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the data asset management method as described in any one of the first aspects are implemented.

[0018] In a fifth aspect, an embodiment of the present application further provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the steps of the data asset management method as described in any one of the first aspects.

[0019] In an embodiment of the present application, a relevance query request is sent to each data node on the blockchain to query the relevance of the asset to be managed with the digital assets pre-stored on the data node. Subsequently, according to the consensus principle of the blockchain, the asset type of the asset to be managed is determined based on the query structure fed back by each data node. The asset type specifically includes newly added asset type, existing asset type, and abnormal asset type. It can be seen that the embodiment of the present application can accurately describe the inherent business logic or demand content of the data asset to be managed through the relevance query and consensus mechanism of the blockchain, thereby achieving accurate classification of data assets and improving the efficiency of data asset management. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1 Schematic diagram of the data asset management system used in the data asset management method in the embodiment of the present application; Figure 2 is a flow chart of a data asset management method in an embodiment of the present application; Figure 3 is a schematic diagram of a data asset management device in an embodiment of the present application; Figure 4 It is a schematic diagram of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0022] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0023] 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 are described in detail below through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0024] It is worth mentioning that a data asset management method in an embodiment of the present application can be applied to a business asset verification model in a data asset management system.

[0025] Specifically, if Figure 1 As shown, 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 asset editing module primarily provides operations such as querying and editing (e.g., adding and modifying) data assets, such as business assets. Compared to traditional asset editing modules, the asset editing module in this embodiment of the present application can interact with the asset chain construction module, the asset chain verification module, and other modules. The meta-asset module contains meta-assets, which are the basic units of data assets and are used to describe and store basic information about business requirements or business functions. Meta-assets can generally be divided into two categories: assets based on basic business units and assets based on demand units. Demand-based assets contain each other and also contain assets based on basic business units. The asset chain module describes and records the business relationships of assets using blockchain data structures and controls changes to the asset chain through smart contracts. The asset chain construction module can create business assets that comply with the business asset chain rules based on the business relationships defined by the assets, or control changes to existing assets. The business asset verification module can initiate a verification query to the business asset chain based on the key information of the asset, thereby obtaining accurate identification and prompts of the business asset chain. Therefore, 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.

[0026] See Figure 2 , Figure 2 This is a flowchart of a data asset management method in an embodiment of the present application, which specifically includes the following steps: Step 101: Perform a relevance query on at least one data node on the blockchain, wherein the relevance query is used to query the relevance between the asset to be managed and the digital asset pre-stored on the data node.

[0027] It is understood that after the requester of an asset to be managed completes data asset editing through the asset editing module, such as adding or modifying an asset, and obtains the asset chain for the asset to be managed, the asset verification module can initiate a verification broadcast of the asset chain for the asset to be managed, triggering a relevance query on the asset chain on the blockchain. The relevance query may include the identification information of the asset to be managed, the identification information of the underlying business assets of the asset to be managed, and the structural information of the asset to be managed. Thus, each data node that receives the relevance query matches the identification information and structural information of the asset to be managed with the assets pre-stored in the data node, obtains a matching result, and sends the matching result as the query result to the asset verification module. The asset verification module then further identifies and classifies the asset to be managed based on the query result.

[0028] 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 relationship between the nodes are constructed as chain data according to the blockchain principle to be stored to obtain a data asset chain. Thus, the embodiment of the present application can clearly describe the key data and its structure within the blockchain, and can clearly describe the access or call relationship of different assets to be managed to the same data node. For example, the product development requirements of the operator will include a description of the basic functions, public services, basic prices, basic resources, personalized services and other data involved in the product. In the traditional mode, this information is usually described in a text coupled together. However, through the embodiment of the present application, not only can the demand content 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 nodes of the above-mentioned asset chain, the correlation between the assets to be managed and the node data is calculated. The asset verification module can judge the repetitiveness and similarity of the assets to be managed and the assets in the blockchain according to the correlation, solving the problem that the traditional mode uses single features such as tags and directories for identification and prompting, resulting in low accuracy, thereby more efficiently and accurately realizing the identification and prompting of data assets.

[0029] Optionally, before performing a relevance query on at least one data node on the blockchain, the method further includes: In a case where the asset to be managed is a data asset based on demand, allocating a first identifier to the asset to be managed; If a directory exists in the requirement document of the asset to be managed, reading directory structure information of the asset to be managed; When the directory name in the directory structure information matches the meta-asset, assigning first serial number information to the asset to be managed based on the directory structure information, where the meta-asset is a basic business asset in the blockchain; Constructing a first asset array corresponding to the asset to be managed based on the first identifier, the first serial number information, and the second identifier of the meta-asset; Among them, the first serial number information includes the first directory level serial number and the first natural paragraph serial number in the directory structure information, and the first sequential serial number for matching the asset to be managed with the meta-asset, and the first natural paragraph serial number includes the paragraph number of the text content in the requirement document of the asset to be managed.

[0030] Optionally, the method further includes: In the event that the directory name in the directory structure information does not match the meta-asset, it is confirmed that the directory existing in the asset to be managed is invalid, and the meta-asset is an asset pre-stored on the blockchain and associated with the basic business asset of the asset to be managed.

[0031] It's worth noting that, because foundational business assets are universal, standardized, and stable business components, they typically don't directly correspond to specific business needs. Instead, they serve as "building blocks" for other business assets. Foundational business assets (such as payment interfaces, identity authentication services, and basic pricing rules) typically have fixed data structures. Foundational business assets are universal components reused by multiple demand assets, and their core value lies in their direct accessibility. Therefore, for data assets based on foundational business units, structural analysis is not required; simply assigning them a unique identifier (ID) is sufficient.

[0032] In some embodiments, a unique identifier, i.e., a first identifier, can be assigned to each business asset based on demand. Furthermore, demand assets describe specific business scenarios and typically include references to underlying business assets, and may also include other demand assets. Their structure is complex and highly dynamic, necessitating structural analysis to extract key data nodes and ensure the accuracy and traceability of the asset chain.

[0033] In an embodiment of the present application, when the asset to be managed is a data asset based on demand, the directory structure information of the asset to be managed can be read to determine whether the directory structure information meets the description requirements of the asset chain in the blockchain, that is, to determine whether the directory name matches the existing business meta-asset in the blockchain.

[0034] The directory structure information may include directory names, directory hierarchical relationships, and other information, including directory hierarchical numbers (e.g., "1.1," "2.3"), segment numbers (e.g., "1st segment," "2nd segment"), and matching sequence numbers (e.g., "1st match," "2nd match"), etc. For example, the requirement document "5G Package Design Requirements" contains the following directory structure: 1. Rate design 1.1 Basic Price Rules 1.2 Package Rates 2. Resource Allocation 2.1 Basic resource configuration 3. Service Configuration 3.1 Public Service Call By reading the above directory structure information, we can obtain the directory level number (such as "1.1", "2.1") and the natural segment number (such as "Segment 1").

[0035] In one specific embodiment, the directory name can be matched with the name of a meta-asset (basic business asset) in the blockchain. If the directory name and meta-asset name match successfully, the serial number is assigned; if the match fails, a message indicating that the directory is invalid is displayed. For example, the directory name "Basic Price Rules" matches the meta-asset ID B456 (Basic Price Rules). The directory name "Public Service Calls" matches the meta-asset ID D012 (Public Service Asset). If the directory name "Resource Allocation" does not match a meta-asset, a message indicating that the directory is invalid is displayed.

[0036] Furthermore, the first serial number information can be assigned to the asset to be managed. The first serial number information can be composed of three parts, including the directory level serial number, the natural segment serial number and the matching sequence serial number. The first serial number information can be used to identify the reference position of the meta-asset in the required asset to ensure a clear structure of the asset chain.

[0037] For example, the first serial number information that can be assigned to the directory "1.1 Basic Price Rules" in the asset to be managed is: Directory level number: "1.1"; Paragraph number: "Paragraph 1"; Matching sequence number: "1st match".

[0038] For the directory "3.1 Public Service Call" in the assets to be managed, the first serial number information that can be assigned to it is: Directory level number: "3.1"; Paragraph number: "Paragraph 2"; Matching sequence number: "2nd match".

[0039] Therefore, in this embodiment of the application, the first identifier (demand asset ID), the first sequence information (directory level, natural segment, matching order), and the meta-asset's second identifier (basic business asset ID) can be combined into a first asset array. The meta-asset's second identifier can be the unique ID of the underlying business asset, used to associate the demand asset with the underlying business asset.

[0040] In this way, the above embodiment achieves precise management of demand assets through directory structure parsing, meta-asset matching and asset array construction. It ensures the accuracy of the reference relationship through dynamic matching of directory structure and meta-asset. It can also form clear chain data through the three-level serial number structure and asset array. It can also convert the reference relationship between demand assets and meta-assets into an asset array and store it in the blockchain. By utilizing the immutability of the blockchain, it ensures the integrity and security of the asset chain, thereby significantly improving the management efficiency and accuracy of business assets.

[0041] Optionally, the method further includes: If no directory exists in the requirements document of the asset to be managed and the text content of the requirements document matches the meta-asset, or if the directory name in the directory structure information does not match the meta-asset, assigning second serial number information to the asset to be managed; Constructing a second asset array corresponding to the asset to be managed based on the first identifier, the second serial number information, and the second identifier of the meta-asset; Among them, the second serial number information includes a second directory level serial number, a second natural paragraph serial number and a second sequential serial number for matching the asset to be managed with the meta-asset, the second directory level serial number is the 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 the paragraph number of the text content in the requirement document.

[0042] In some embodiments, if a directory does not exist in the requirements document or the directory name in the directory structure information does not match the meta-asset, a second serial number is assigned to the asset to be managed. In one specific embodiment, the requirements document can be checked to see if it contains a directory structure (e.g., a table of contents in a Word document or chapter headings in a PDF). If the directory does not exist, the asset verification module can directly read the text content of the requirements document and attempt to match it with the meta-asset in the blockchain. If a match is successful, the second serial number is assigned to the asset to be managed. In another specific embodiment, the directory structure information in the requirements document can be parsed to check if the directory name matches the meta-asset name in the blockchain. If the match fails (e.g., the directory name is "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, and attempts to match it with the meta-asset. If a match is successful, the second serial number is assigned to the asset to be managed.

[0043] For example, the requirements document "5G Package Design Requirements" has no table of contents, but its text includes "Basic Pricing Rules" and "Public Service Calls." The asset verification module matches meta-assets B456 (Basic Pricing Rules) and D012 (Public Service Assets) and assigns a second sequence number to the asset to be managed, "5G Package Design Requirements."

[0044] For example, the requirements document contains a directory called "Resource Allocation," but there's no corresponding meta-asset in the blockchain. The asset verification module ignores the directory name and directly reads the text, matching it to meta-asset C789 (Basic Resource Allocation) and assigning it a second serial number.

[0045] Furthermore, the first identifier (ID of the asset to be managed), the second sequence number information (directory level sequence number, natural segment sequence number, matching sequence 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 sequence number information includes: Second directory level sequence number: the directory level sequence number in the meta-asset that matches the text content of the requirements document (for example, "1.1"); Second paragraph number: the paragraph number of the text content in the requirements document (for example, "Paragraph 1"); Second order number: The order in which the demand asset is matched with the meta asset (e.g., "1st match").

[0046] Thus, the above embodiment allows meta-assets to be matched based on text content when directories are missing or names don't match, ensuring complete asset identification. By designing the second serial number information to include directory levels, natural paragraphs, and matching order, it can dynamically adapt to structural changes in the requirements document, avoiding confusion caused by duplicate directory levels or paragraph numbers and improving the accuracy of the asset chain. Furthermore, the reference relationship between the required assets and meta-assets is converted into an asset array and stored in the blockchain, leveraging the blockchain's immutability to ensure the integrity and security of the asset chain.

[0047] Step 102: Obtain a query result for the relevance query fed back by the at least one data node.

[0048] In some embodiments, after triggering a blockchain "relevance query," the asset verification module enters a waiting phase, awaiting query results from data nodes in the blockchain network. This relevance query verifies the relevance of the asset to be managed with underlying business assets in the blockchain, ensuring data consistency.

[0049] It's understood that a relevance query, or rather, the relevance query contract, is part of a blockchain smart contract and is used to execute the asset chain's validation logic. If the first identifier of the asset being managed matches the identifier of an existing asset recorded in the node data, it indicates a relevance query for existing assets (i.e., existing assets on the blockchain). If they don't match, it indicates a relevance query for a newly added asset.

[0050] For existing assets, you can further verify that the meta-asset ID and meta-asset serial number recorded in the data block of the chain where the asset ID is located are consistent with the requested content. For newly added assets, you can search the blockchain using the meta-asset ID and meta-asset serial number to determine whether there are any duplications or conflicts.

[0051] The above query results may include a verification result of whether the first identifier is consistent with the third identifier of the digital asset pre-recorded by each data node, and may also include a first proportion of data nodes whose meta-asset serial number is consistent with the serial number of the asset to be managed, a second proportion of data nodes whose meta-asset content is consistent with the content of the asset to be managed, and a third proportion of data nodes whose meta-asset serial number and content are consistent with the serial number and content of the meta-asset serial number.

[0052] Therefore, the asset verification module can preliminarily verify whether the asset type of the asset to be managed is an existing asset type or a new asset type through the verification result of whether the first identifier is consistent with the third identifier of the digital asset pre-recorded by each data node, and can further determine whether the asset type of the asset to be managed is any one of the new asset type, existing asset type and abnormal asset type through the first ratio, the second ratio or the third ratio.

[0053] Step 103: Determine the asset type of the asset to be managed based on the query result through blockchain consensus, where the asset type includes: new asset type, existing asset type, and abnormal asset type.

[0054] It should be noted that blockchain consensus, that is, dynamically determining the type of assets to be managed (new assets, existing assets, or abnormal assets) based on correlation query results (such as the proportion of identical serial numbers, the proportion of identical assets, and the proportion of complete correspondence between assets and serial numbers), is essentially to ensure the consistency and immutability of asset type determination through the collaboration of distributed nodes in the blockchain network.

[0055] Blockchain consensus is the process by which data nodes in a blockchain network reach consensus on data or status through pre-set rules (e.g., majority voting, PoW / PoS, etc.). In this implementation, blockchain consensus can verify the credibility of query results. This ensures that asset type determination is independent of a single node by leveraging feedback from multiple nodes (e.g., proportionality data), thus preventing data tampering or misjudgment. It can also determine asset type through consensus rules (e.g., majority rule) based on statistical results (e.g., proportionality data) from node feedback.

[0056] In the embodiment of the present application, a relevance query request is sent to each data node on the blockchain to query the relevance of the asset to be managed with the digital assets pre-stored on the data node. Then, according to the consensus principle of the blockchain, the asset type of the asset to be managed is determined based on the query structure fed back by each data node. The asset type specifically includes newly added asset type, existing asset type, and abnormal asset type. It can be seen that the embodiment of the present application can accurately describe the inherent business logic or demand content of the data asset to be managed through the relevance query and consensus mechanism of the blockchain, thereby achieving accurate classification of data assets and improving the efficiency of data asset management.

[0057] Optionally, determining the asset type of the asset to be managed based on the query result through blockchain consensus includes: If 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, determining that the asset type of the to-be-managed asset is the newly added asset type or the existing 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 results corresponding to each second data node are consistent, it is determined that the asset type of the asset to be managed is the abnormal asset type.

[0058] In some embodiments, the determination rules for different asset types can be pre-set according to business needs. For example: Newly added asset type: If the exact correspondence between assets and serial numbers is less than 50%, and the same asset ratio is less than 50%, then it is considered a newly added asset; Stock asset type: If the proportion of complete correspondence between assets and serial numbers is greater than or equal to 90%, and the proportion of identical assets is greater than or equal to 90%, it is determined to be a stock asset; Abnormal asset type: If the node results vary greatly (for example, some nodes return a high ratio, while others return a low ratio), the asset is considered abnormal.

[0059] Furthermore, if more than 50% of the data nodes consider the asset to be newly added, it is considered a newly added asset. If more than 50% of the data nodes consider the asset to be an existing asset, it is considered an existing asset. If the node results vary significantly (for example, some nodes return a high percentage, while others return a low percentage), it is considered an abnormal asset. In this way, the smart contract on the blockchain automatically calculates and outputs the asset type based on preset rules (such as thresholds), without the need for human intervention.

[0060] In this way, the embodiment of the present application uses the blockchain consensus mechanism to ensure that the type of assets to be managed does not rely on a single node, but is determined through the consensus results of multiple nodes to ensure that the data cannot be tampered with. Smart contracts and preset rules (such as majority voting and threshold judgment) are used to ensure the fairness and consistency of the judgment results, effectively improving the credibility, transparency and efficiency of asset chain management, realizing the accurate classification of data assets, and improving the efficiency of data asset management.

[0061] 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 a sequential serial number for matching the asset to be managed with the meta-asset, wherein the meta-asset is an asset pre-stored on the blockchain and associated with the basic business asset of the asset to be managed; The association query request is at least used to obtain a first query result, and the first query result is used to express a verification result of whether the first identifier is consistent with a third identifier of the digital asset pre-recorded by the data node.

[0062] In some embodiments, the relevance query request carries an asset array corresponding to the asset to be managed, and its structure is as follows: First ID: The unique ID of the asset to be managed (e.g., A123), used to uniquely identify the asset (e.g., the asset in demand); Sequence number information, including: Directory level sequence number: the directory level of the meta-asset referenced in the demand asset; Natural paragraph sequence number: the number of the text paragraph that references the meta-asset in the demand asset; Matching sequence number: the order in which the asset to be managed matches the meta-asset (e.g., the first match); Second identifier of meta-asset: The unique identifier of the basic business asset pre-stored on the blockchain (such as B456), which indicates the meta-asset referenced by the asset to be managed.

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

[0064] The aforementioned association query request carries an asset array, which is used to verify the association between the asset to be managed and the meta-assets stored on the blockchain. This query can verify whether the first identifier is consistent with the third identifier (such as the meta-asset ID) of the digital asset pre-recorded by the data node. For example, if the ID of the asset to be managed is A123 and A123 already exists in the data node, an update logic may be triggered; if not, it may be processed as a newly added asset. The consistency of the first and third identifiers can also be verified. If they are consistent, the asset to be managed may already exist, requiring further verification of their reference relationships (such as the meta-asset ID and sequence number). If they are inconsistent, the asset to be managed is newly added, requiring the creation of a new chain or the updating of the asset chain.

[0065] It is understood that the first query result is the data node's response to the association query request, used to verify whether the first identifier of the asset to be managed is consistent with the third identifier of the digital asset stored on the blockchain. For example, whether the first identifier (the ID of the asset to be managed) matches the third identifier (the ID of the digital asset stored on the data node). If the first identifier of the asset to be managed is A123, and the third identifier of the digital asset stored on the data node is also A123, a consistent result is returned; otherwise, an inconsistent result is returned.

[0066] In this way, the embodiment of the present application can record the reference relationship (directory level, paragraph position, matching order) between the assets to be managed and the meta-assets through the asset array, ensuring the accuracy of the asset chain and ensuring that the reference relationship between the assets to be managed and the meta-assets is accurate.

[0067] Optionally, determining whether the asset type of the to-be-managed asset is the newly added asset type or the existing asset type includes at least one of the following: If the first query result shows that the first identifier is consistent with the third identifier, determining that the asset type of the asset to be managed is a stock asset type in the blockchain; 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 asset to be managed is a new asset type in the blockchain.

[0068] In some embodiments, if the first identifier (the first identifier of the asset to be managed, e.g., A123) matches the third identifier (the identifier of a digital asset already stored on the blockchain, e.g., A123), this indicates that the asset to be managed already exists on the blockchain. This allows the asset type to be determined as an existing asset, and further verification can be performed to verify whether its reference (e.g., meta-asset ID and sequence number) is consistent with the request. For example, if the asset to be managed has an ID of A123 and A123 already exists in the data node, it is determined to be an existing asset. The asset verification module can check whether the referenced meta-asset ID (e.g., B456) and sequence number (e.g., 1.1-1-1) are consistent with the request, ensuring the accuracy of the asset chain.

[0069] In some other embodiments, the inconsistency between the first and third identifiers indicates that the asset does not yet exist in the blockchain. The asset type of the asset to be managed is determined to be a newly added asset type and must be added to the blockchain's asset chain. For example, if 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 newly added asset. The asset management module may add the asset to be managed and its referenced meta-asset information (e.g., B456 and 1.1-1-1) to the asset chain.

[0070] In this way, the embodiment of the present application can ensure the accuracy of asset type determination through the unique matching of the first identifier and the third identifier, quickly distinguish new assets from existing assets, and ensure the credibility of the asset type determination result.

[0071] Optionally, the method further includes: Get the first ratio, the second ratio and the third ratio; Among them, the first ratio is the ratio of the sequence number information in the asset array to be identical to the sequence number information in the target information, the second ratio is the ratio of the document content in the requirement document of the asset to be managed to match the asset content in the target information, and the third ratio is the ratio of the document content and sequence number information in the requirement document of the asset to be managed to completely correspond to the basic business asset content and sequence number information in the target information; the target information includes the meta-asset content and sequence number information recorded on the data block storing the meta-asset in the blockchain.

[0072] In some embodiments, in blockchain asset chain management, three key ratios (first ratio, second ratio, and third ratio) can be used to evaluate the degree of match with the target information stored in the blockchain (i.e., the data block content and serial number information of the meta-asset).

[0073] The first ratio is the ratio of the sequence number information in the asset array (including the directory level sequence number, natural segment sequence number, and matching sequence number) to the sequence number information in the target information (the sequence number information of the meta-asset data block record in the blockchain). Specifically, to calculate the first ratio, we can traverse all the sequence number information in the asset array, compare them one by one with the sequence number information in the target information, and then calculate the ratio of the number of matching sequence number information to the total number of sequence number information, and get: .

[0074] For example, if the sequence numbers in the asset array are 1.1-1-1 and 3.1-2-2, and the sequence numbers in the target data are 1.1-1-1 and 3.1-2-2, the first ratio is 100% (a perfect match). If only 1.1-1-1 matches in the target data, the first ratio is 50%.

[0075] The second ratio mentioned above refers to the ratio of matches between the document content in the requirements document for the asset to be managed and the asset content in the target information (the data block content of the meta-asset in the blockchain). The document content in the requirements document can be understood as the textual content such as the business logic and functional requirements described in the required asset. The asset content in the target information can be understood as the textual content such as the business logic and functional description recorded in the data block of the meta-asset in the blockchain. Specifically, to calculate the second ratio, textual similarity analysis (such as cosine similarity, edit distance, keyword matching, etc.) can be performed on the content of the requirements document and the target information, and the ratio of the amount of matching textual content to the total amount of textual content can be calculated to obtain: .

[0076] For example, if the requirements document contains "Basic Pricing Rules" and the target asset contains "Basic Pricing Rules," the second ratio would be 100% (a complete match). If the target asset contains "Basic Pricing Strategy," the second ratio might be 70% (a partial match).

[0077] As for the third ratio, that is, the ratio of the document content and serial number information in the requirements document of the assets to be managed to completely correspond to the basic business asset content and serial number information in the target information. It can be understood that completely corresponding means that the document content and serial number information of the requirements document must be completely consistent with the asset content and serial number information of the target information. Specifically, to calculate the third ratio, you can traverse each serial number information and document content in the asset array, compare them one by one with the asset content and serial number information in the target information, and count the ratio of the number of completely matching asset array entries to the total number of asset array entries, and get: .

[0078] For example, if the asset array entry is {"asset_id": "A123", "meta_asset_id": "B456","meta_asset_seq": "1.1-1-1"}, and the target asset is B456 and the sequence number is 1.1-1-1, the third ratio is 100% (a perfect match). If the target asset is B457, the third ratio is 0% (a perfect mismatch).

[0079] In this way, embodiments of the present application can verify the asset chain structure through the first ratio, ensuring that the meta-asset serial number referenced by the asset to be managed is consistent with the meta-asset serial number stored in the blockchain. Embodiments of the present application can also verify the consistency of business logic through the second ratio, ensuring that the content of the requirements document for the asset to be managed is consistent with the business logic of the meta-asset. Embodiments of the present application can also verify the integrity of the asset chain through the third ratio, ensuring that the reference relationship and content of the asset to be managed are completely consistent with the meta-asset stored in the blockchain.

[0080] Optionally, the method further comprises at least one of the following: When the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the existing asset type, returning the asset to be managed to the requester who initiated the management request for the asset to be managed; If the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the newly added asset type, returning to the requesting party the existing assets in the blockchain that are consistent with the asset to be managed; When the first ratio is less than the first threshold value and the second ratio is greater than or equal to a second threshold value, confirming that the asset type of the to-be-managed asset is a first other type; When the first ratio is less than the first threshold value and the third ratio is greater than or equal to the third threshold value, confirming that the asset type of the to-be-managed asset is a second other type; Among them, the first other type is an asset type that has the same asset content as the existing assets in the blockchain but has a different asset structure; the second other type is an asset type that has the same asset structure as the existing assets in the blockchain but has a different asset content.

[0081] In some embodiments, if the first ratio (serial number information matching ratio) is greater than or equal to a first threshold and the asset to be managed is determined to be an existing asset (i.e., the asset ID already exists in the blockchain), the asset verification module may return the asset to the requester. This can be understood as a high degree of serial number matching, indicating that the asset chain structure is consistent with the meta-asset stored in the blockchain, and no further verification is required. In this case, the reference to the existing asset already exists, and the asset can be returned directly. For example, if the serial number of the asset to be managed, A123, exactly matches the meta-asset serial number of A123 in the blockchain, and the asset type is an existing asset, the asset verification module may directly return the asset to the requester.

[0082] In another embodiment, if the first ratio is greater than or equal to the first threshold, but the asset to be managed is determined to be newly added (i.e., the asset ID does not exist in the blockchain), the requesting party may be returned an existing asset on the blockchain that matches the asset to be managed. A high degree of match in the sequence number information, but a mismatch in the asset ID, may indicate an error in the asset ID input or a conflict in the asset chain reference. The asset verification module can use this matching sequence number information to locate an existing asset on the blockchain that matches the structure of the asset to be managed, providing the requesting party with a reference. For example, if the sequence number of asset A124 matches the meta-asset sequence number of A123 on the blockchain, but the asset ID does not match, the asset verification module may return A123 as a reference.

[0083] In another embodiment, if the first ratio (sequence number information matching ratio) is less than a first threshold, but the second ratio (document content matching ratio) is greater than or equal to a second threshold, the asset type of the asset to be managed can be determined to be the first other type (same asset content but different asset structure). A low sequence number match but a high document content match indicates that the business logic of the assets is consistent, but there are differences in the reference relationships or structure (e.g., different directory hierarchies or section numbering). The content of the requirements document is consistent with the meta-asset, but the referenced sequence information does not match. For example, the document content of the asset to be managed A125 is consistent with the meta-asset B456, but the sequence number information (e.g., 1.1-1-1) is inconsistent with the 1.1-2-1 stored in the blockchain, resulting in the system determining it as the first other type.

[0084] In another embodiment, if the first ratio is less than the first threshold, but the third ratio (complete correspondence ratio) is greater than or equal to the third threshold, the asset type of the asset to be managed can be confirmed to be a second other type (same asset structure, but different asset content). Here, the serial number information has a low match, but the document content and the serial number information completely correspond, indicating that the asset reference relationship is consistent, but there are differences in the business logic (such as different functional descriptions). For example, the asset chain structure is consistent with the meta-asset, but the content of the requirements document is inconsistent with the meta-asset. For example, the serial number information of the asset to be managed A126 is consistent with the meta-asset B456, but the document content (such as "basic price rules") and the meta-asset content (such as "basic price strategy") differ, and the system determines it as the second other type.

[0085] It should be noted that the first "other" type mentioned above can be when the asset content is the same (e.g., the requirements document content and the meta-asset are consistent), but the asset structure is different (e.g., the referenced serial number information is different). For example, the requirements document content is "Basic Price Rules", but the referenced serial number information is 1.1-1-1, while the meta-asset serial number stored in the blockchain is 1.1-2-1. The second "other" type mentioned above can be when the asset structure is the same (e.g., the referenced serial number information is consistent), but the asset content is different (e.g., the requirements document content and the meta-asset are inconsistent). For example, the referenced serial number information is 1.1-1-1, but the requirements document content is "Basic Price Strategy", while the meta-asset content is "Basic Price Rules".

[0086] It will be appreciated that the first, second, and third thresholds described above can be dynamically adjusted based on business needs. In the above embodiment, the combination of ratio thresholds and asset types enables precise asset classification (existing assets, newly added assets, first other type, second other type). Ratio analysis can also be used to identify structural or content differences within asset chains, supporting dynamic updates and optimization of asset chains. This allows for the return of different results based on asset type (e.g., directly returning the asset, returning a reference asset, or indicating the type of difference), improving user operation efficiency and accuracy.

[0087] In this way, the above embodiment of the present application can achieve dynamic management of the asset chain through the combination of ratio threshold and asset type, thereby improving the accuracy, flexibility and user operation efficiency of asset chain management.

[0088] Optionally, the method further includes: If the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be modified, construct a first private chain in the blockchain according to the order of version numbers generated when receiving the management request for the asset to be managed, and store the asset to be managed on the first private chain; If the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be deleted, construct a second private chain in the blockchain according to the order of the version numbers, and adjust the serial number information of the subsequently received asset to be managed after the deletion of the asset to be managed is completed; 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 build an asset chain.

[0089] It should be noted that in blockchain asset chain management, the processing logic for different operations (modification, deletion, and addition) of existing assets and new assets can be used to achieve dynamic updates and data consistency of the asset chain through version number management and private chain construction.

[0090] In some embodiments, if an asset is a stock asset (i.e., the asset ID already exists in the blockchain) and a modification is required, a first private chain can be constructed within the blockchain based on the version number sequence. Alternatively, the modified asset to be managed can be stored on the first private chain. Version number management involves generating a new version number (e.g., V1.0, V1.1) for each modification to the stock asset, ensuring traceability of the modification history. The version number sequence (e.g., increasing) identifies the update path of the asset chain. For private chain construction, the first private chain is a separate chain within the blockchain network, specifically used to store modified asset data. This private chain ensures that modifications do not affect the original asset chain while preserving historical versions. For example, if the original version of asset A123 is V1.0 and is modified to V1.1, the system constructs a private chain, Chain_A123_V1.1, within the blockchain to store the modified asset data. In this way, this embodiment ensures that the modification history of the asset chain is traceable through version number management. At the same time, the construction of the private chain allows independent updates of assets, avoiding direct modification of the main chain data.

[0091] In another embodiment, if an asset is a stock asset and needs to be deleted, a second private chain can be constructed within the blockchain based on the order of its version numbers. After the deletion is complete, the sequence numbers of subsequently received assets to be managed are adjusted. This second private chain can be used to record metadata about the deletion operation (such as the deletion time, operator, and reason). The deletion operation does not directly remove the asset from the main chain; instead, the deletion status is recorded via the private chain. After the deletion, the sequence number information of subsequent assets (such as directory level and section number) must be reassigned to avoid conflicts with the deleted asset's sequence number. For example, if the sequence number 1.1-1-1 of asset A123 is deleted, the sequence numbers of subsequent assets may be adjusted to 1.1-2-1. For example, after asset A123 is deleted, the system constructs a private chain, Chain_A123_Delete, within the blockchain to record the deletion information and adjust the sequence numbers of subsequent assets (e.g., 1.1-2-1). In this way, this embodiment can record deletion operations 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 in the asset chain.

[0092] In another embodiment, when the asset type is a newly added asset (i.e., the asset ID does not exist in the blockchain), a target node can be created on the blockchain to store the asset to be managed. Specifically, the target node can be connected to the data nodes associated with the meta-asset to build an asset chain. A target node is a new node in the blockchain network, specifically used to store the newly added asset's data. The creation of the node is subject to verification by the blockchain consensus mechanism (such as Proof-of-Work / Proof-of-Stake) to ensure data legitimacy. A data node is a node in the blockchain that stores meta-asset information (such as the asset ID, meta-asset ID, and serial number information). By connecting the target node and the data node, a reference relationship in the asset chain is established. For example, newly added asset A124 is created as target node Node_A124 and connected to data node Node_B456 (meta-asset information), forming asset chains A124 and B456. In this way, by connecting the data nodes, this embodiment of the present application ensures the accurate reference relationship between the newly added asset and the meta-asset. Furthermore, the creation of the target node and the construction of the asset chain are automatically completed by the blockchain network, requiring no human intervention.

[0093] It is understood that the order of the version numbers (e.g., increasing) is used to identify the update path of the asset chain, ensuring the traceability of modification and deletion operations. Furthermore, the first private chain (for modification operations) and the second private chain (for deletion operations) are independent chains within the blockchain network, used to store metadata for specific operations. The construction of private chains must be verified through blockchain consensus mechanisms (e.g., smart contracts) to ensure data consistency.

[0094] It's also worth noting that the connection between the target node and the data node is automatically established through the blockchain's smart contract, ensuring accurate reference relationships within the asset chain. Furthermore, after a deletion operation, the serial numbers of subsequent assets are reassigned to avoid conflicts with the deleted asset's serial numbers. For example, if the serial number 1.1-1-1 of asset A123 is deleted, the serial numbers of subsequent assets may be adjusted to 1.1-2-1.

[0095] Optionally, connecting the target node and the data node associated with the meta-asset of the asset to be managed to build an asset chain includes: Sending the asset array and the version number corresponding to the asset to be managed to the data node associated with the meta-asset in sequence according to the sequence number of the meta-asset; According to the sequence number of the meta-asset, the data nodes associated with the target node and the meta-asset are connected to build the asset chain.

[0096] In some embodiments, meta-assets may be stored in a hierarchical structure (e.g., directory hierarchy, paragraph numbering, matching order, etc.) within the blockchain and must be processed sequentially according to their logical sequence numbers (e.g., from highest to lowest or from left to right). The asset array contains metadata about the asset to be managed, such as the asset's primary identifier, the meta-asset's secondary identifier, and sequence information (directory hierarchy, paragraph number, matching order number). The version number can be used to identify the asset chain version (e.g., V1.0, V1.1), ensuring traceability of the asset chain's modification history. Specifically, the sequence numbers of the meta-assets are traversed. For example, if the meta-assets have sequence numbers 1.1-1-1, 1.1-2-1, and 1.2-1-1, they are processed sequentially in hierarchical order. The asset array and version number are sent to the data node associated with the meta-asset. Each data node (the node storing the meta-asset information) receives the asset array and version number and verifies its association with the meta-asset. For example, if the sequence 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 version number V1.0 are sent to the corresponding data node.

[0097] Furthermore, target nodes and data nodes can be connected according to the order of the meta-asset numbers to build an asset chain. The target node can be the storage node for the newly added asset (e.g., Node_A124). The data node can be the node that stores meta-asset information (e.g., Node_B456). Thus, by connecting the target node and the data node, a reference relationship in the asset chain is formed (e.g., A124 → B456).

[0098] Specifically, nodes can be connected in order of meta-asset serial numbers. For example, if the meta-asset serial numbers are 1.1-1-1 and 1.1-2-1, the target node Node_A124 is connected to the data nodes Node_B456 and Node_C012, respectively. Subsequently, through the blockchain's smart contract or consensus mechanism, the reference relationship between the target node and the data node is written to the blockchain. For example, asset chain A124 → B456 (meta-asset B456's serial number is 1.1-1-1); asset chain A124 → C012 (meta-asset C012's serial number is 1.1-2-1).

[0099] It's understandable that the hierarchical structure of serial numbers (e.g., 1.1-1-1) must strictly adhere to business rules to ensure accurate reference relationships within the asset chain. For example, directory level 1.1 corresponds to "Basic Business," section number 1 corresponds to "Pricing Rules," and matching order 1 corresponds to "First Reference." Furthermore, the construction of the asset chain must be verified through blockchain consensus mechanisms (e.g., smart contracts) to ensure the legitimacy of reference relationships. For example, smart contracts may check the association between target nodes and data nodes to prevent incorrect connections.

[0100] In this way, the embodiment of the present application ensures data consistency by sending the asset array and version number in the order of the meta-asset serial number, and builds the reference relationship of the asset chain by connecting the target node and the data node, thereby effectively improving the flexibility, data consistency and traceability of asset chain management.

[0101] Please refer to Figure 3 , Figure 3 FIG. 1 is a schematic diagram of a data asset management device according to an embodiment of the present application. The data asset management device 200 specifically includes: A first sending module 201 is configured to perform a relevance query on at least one data node on the blockchain, wherein the relevance query is configured to query the relevance between the asset to be managed and the digital asset pre-stored on the data node; A first receiving module 202 is configured to obtain a query result for the relevance query fed back by the at least one data node; The first determination module 203 is configured to determine the asset type of the asset to be managed based on the query result through blockchain consensus, where the asset type includes: a newly added asset type, an existing asset type, and an abnormal asset type.

[0102] Optionally, before performing a relevance query on at least one data node on the blockchain, the data asset management device 200 further includes: A first allocation module is configured to allocate a first identifier to the asset to be managed when the asset to be managed is a data asset with demand as a unit; A first reading module is configured to read directory structure information of the asset to be managed if a directory exists in the requirement document of the asset to be managed; a second allocation module, configured to allocate first serial number information to the asset to be managed based on the directory structure information when a directory name in the directory structure information matches a meta-asset, wherein the meta-asset is a basic business asset in the blockchain; A first building module, configured to build a first asset array corresponding to the asset to be managed based on the first identifier, the first serial number information, and the second identifier of the meta-asset; Among them, the first serial number information includes the first directory level serial number and the first natural paragraph serial number in the directory structure information, and the first sequential serial number for matching the asset to be managed with the meta-asset, and the first natural paragraph serial number includes the paragraph number of the text content in the requirement document of the asset to be managed.

[0103] Optionally, the data asset management device 200 further includes: The first confirmation module is used to confirm that the directory existing in the asset to be managed is invalid when the directory name in the directory structure information does not match the meta-asset, and the meta-asset is an asset pre-stored on the blockchain and associated with the basic business asset of the asset to be managed.

[0104] Optionally, the data asset management device 200 further includes: a third allocation module, configured to allocate second serial number information to the asset to be managed if no directory exists in the requirement document of the asset to be managed and the text content of the requirement document matches the meta-asset, or if the directory name in the directory structure information does not match the meta-asset; A second building module is configured to build a second asset array corresponding to the asset to be managed based on the first identifier, the second serial number information, and the second identifier of the meta-asset; Among them, the second serial number information includes a second directory level serial number, a second natural paragraph serial number and a second sequential serial number for matching the asset to be managed with the meta-asset, the second directory level serial number is the 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 the paragraph number of the text content in the requirement document.

[0105] Optionally, the first determining module 203 includes: A first determining unit is configured to determine whether the asset type of the to-be-managed asset is the newly added asset type or the existing asset type, if 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 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 results corresponding to each second data node are consistent.

[0106] 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 a sequential serial number for matching the asset to be managed with the meta-asset, wherein the meta-asset is an asset pre-stored on the blockchain and associated with the basic business asset of the asset to be managed; The association query request is at least used to obtain a first query result, and the first query result is used to express a verification result of whether the first identifier is consistent with a third identifier of the digital asset pre-recorded by the data node.

[0107] Optionally, the first determining unit is used for at least one of the following: If the first query result shows that the first identifier is consistent with the third identifier, determining that the asset type of the asset to be managed is a stock asset type in the blockchain; 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 asset to be managed is a new asset type in the blockchain.

[0108] Optionally, the data asset management device 200 further includes: Get the first ratio, the second ratio and the third ratio; Among them, the first ratio is the ratio of the sequence number information in the asset array to be identical to the sequence number information in the target information, the second ratio is the ratio of the document content in the requirement document of the asset to be managed to match the asset content in the target information, and the third ratio is the ratio of the document content and sequence number information in the requirement document of the asset to be managed to completely correspond to the basic business asset content and sequence number information in the target information; the target information includes the meta-asset content and sequence number information recorded on the data block storing the meta-asset in the blockchain.

[0109] Optionally, the data asset management device 200 further includes at least one of the following: a first returning module, configured to return the asset to be managed to a requester that initiates a management request for the asset to be managed, if the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the stock asset type; a second returning module, configured to return to the requesting party, if the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the newly added asset type, existing assets in the blockchain that are consistent with the asset to be managed; a second confirmation module, configured to confirm that the asset type of the to-be-managed assets is a first other type when the first ratio is less than the first threshold and the second ratio is greater than or equal to a second threshold; a third confirmation module, configured to confirm that the asset type of the to-be-managed assets is a second other type when the first ratio is less than the first threshold and the third ratio is greater than or equal to a third threshold; Among them, the first other type is an asset type that has the same asset content as the existing assets in the blockchain but has a different asset structure; the second other type is an asset type that has the same asset structure as the existing assets in the blockchain but has a different asset content.

[0110] Optionally, the data asset management device 200 further includes: A third construction module is configured to, when the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be modified, construct a first private chain in the blockchain according to the order of version numbers generated when receiving the management request for the asset to be managed, and store the asset to be managed on the first private chain; an information adjustment module, configured to, if the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be deleted, construct a second private chain in the blockchain according to the order of the version numbers, and, upon completing the deletion process of the asset to be managed, adjust the serial number information of the subsequently received asset to be managed; The fourth construction module is used to create a target node for storing the asset to be managed on the blockchain when the asset type of the asset to be managed is the newly added asset type, and connect the target node and the data node associated with the meta-asset of the asset to be managed to build an asset chain.

[0111] Optionally, the fourth building block includes: An information sending unit, configured to sequentially send the asset array and the version number corresponding to the asset to be managed to the data node associated with the meta-asset according to the sequence number of the meta-asset; A link construction unit is configured to connect the data nodes associated with the target node and the meta-asset according to the sequence number of the meta-asset to construct the asset chain.

[0112] The data asset management device 200 provided in the embodiment of the present application can execute the above Figure 1 The method embodiment shown in the figure can be used to implement the data asset management device 200 in the embodiment of the present application. Its implementation principle and technical effect are similar to those of Figure 1 The method embodiment shown is not described in detail here.

[0113] The present application also provides an electronic device. Since the principle of solving the problem of the electronic device is similar to the system upgrade method in the present application, the implementation of the electronic device can refer to Figure 1 The implementation of the method shown in FIG. 1 is omitted for repetition. Figure 4 As shown, the electronic device of the embodiment of the present application includes: a processor 310, which is used to read the program in the memory 320 and execute the following process: Performing a relevance query on at least one data node on the blockchain, wherein the relevance query is used to query the relevance between the asset to be managed and the digital asset pre-stored on the data node; Obtaining a query result for the relevance query fed back by the at least one data node; The asset type of the asset to be managed is determined based on the query result through blockchain consensus, and the asset type includes: new asset type, existing asset type and abnormal asset type.

[0114] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform the following steps: In a case where the asset to be managed is a data asset based on demand, allocating a first identifier to the asset to be managed; If a directory exists in the requirement document of the asset to be managed, reading directory structure information of the asset to be managed; When the directory name in the directory structure information matches the meta-asset, assigning first serial number information to the asset to be managed based on the directory structure information, where the meta-asset is a basic business asset in the blockchain; Constructing a first asset array corresponding to the asset to be managed based on the first identifier, the first serial number information, and the second identifier of the meta-asset; Among them, the first serial number information includes the first directory level serial number and the first natural paragraph serial number in the directory structure information, and the first sequential serial number for matching the asset to be managed with the meta-asset, and the first natural paragraph serial number includes the paragraph number of the text content in the requirement document of the asset to be managed.

[0115] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform the following steps: In the event that the directory name in the directory structure information does not match the meta-asset, it is confirmed that the directory existing in the asset to be managed is invalid, and the meta-asset is an asset pre-stored on the blockchain and associated with the basic business asset of the asset to be managed.

[0116] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform the following steps: If no directory exists in the requirements document of the asset to be managed and the text content of the requirements document matches the meta-asset, or if the directory name in the directory structure information does not match the meta-asset, assigning second serial number information to the asset to be managed; Constructing a second asset array corresponding to the asset to be managed based on the first identifier, the second serial number information, and the second identifier of the meta-asset; Among them, the second serial number information includes a second directory level serial number, a second natural paragraph serial number and a second sequential serial number for matching the asset to be managed with the meta-asset, the second directory level serial number is the 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 the paragraph number of the text content in the requirement document.

[0117] Optionally, the processor 310 is further configured to read a program in the memory 320 and execute the following steps: If 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, determining that the asset type of the to-be-managed asset is the newly added asset type or the existing 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 results corresponding to each second data node are consistent, it is determined that the asset type of the asset to be managed is the abnormal asset type.

[0118] 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 a sequential serial number for matching the asset to be managed with the meta-asset, wherein the meta-asset is an asset pre-stored on the blockchain and associated with the basic business asset of the asset to be managed; The association query request is at least used to obtain a first query result, and the first query result is used to express a verification result of whether the first identifier is consistent with a third identifier of the digital asset pre-recorded by the data node.

[0119] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform at least one of the following steps: If the first query result shows that the first identifier is consistent with the third identifier, determining that the asset type of the asset to be managed is a stock asset type in the blockchain; 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 asset to be managed is a new asset type in the blockchain.

[0120] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform the following steps: Get the first ratio, the second ratio and the third ratio; Among them, the first ratio is the ratio of the sequence number information in the asset array to be identical to the sequence number information in the target information, the second ratio is the ratio of the document content in the requirement document of the asset to be managed to match the asset content in the target information, and the third ratio is the ratio of the document content and sequence number information in the requirement document of the asset to be managed to completely correspond to the basic business asset content and sequence number information in the target information; the target information includes the meta-asset content and sequence number information recorded on the data block storing the meta-asset in the blockchain.

[0121] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform at least one of the following steps: When the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the existing asset type, returning the asset to be managed to the requester who initiated the management request for the asset to be managed; If the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the newly added asset type, returning to the requesting party the existing assets in the blockchain that are consistent with the asset to be managed; When the first ratio is less than the first threshold value and the second ratio is greater than or equal to a second threshold value, confirming that the asset type of the to-be-managed asset is a first other type; When the first ratio is less than the first threshold value and the third ratio is greater than or equal to the third threshold value, confirming that the asset type of the to-be-managed asset is a second other type; Among them, the first other type is an asset type that has the same asset content as the existing assets in the blockchain but has a different asset structure; the second other type is an asset type that has the same asset structure as the existing assets in the blockchain but has a different asset content.

[0122] Optionally, the processor 310 is further configured to read a program in the memory 320 and perform the following steps: If the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be modified, construct a first private chain in the blockchain according to the order of version numbers generated when receiving the management request for the asset to be managed, and store the asset to be managed on the first private chain; If the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be deleted, construct a second private chain in the blockchain according to the order of the version numbers, and adjust the serial number information of the subsequently received asset to be managed after the deletion of the asset to be managed is completed; 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 build an asset chain.

[0123] Optionally, the processor 310 is further configured to read a program in the memory 320 and execute the following steps: Sending the asset array and the version number corresponding to the asset to be managed to the data node associated with the meta-asset in sequence according to the sequence number of the meta-asset; According to the sequence number of the meta-asset, the data nodes associated with the target node and the meta-asset are connected to build the asset chain.

[0124] The electronic device provided in the embodiment of the present application can perform the above Figure 1 The implementation principle and technical effects of the method embodiment shown are similar, and will not be described in detail in this embodiment.

[0125] The present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned Figure 1 The various processes of the data asset management method embodiment in the embodiment can achieve the same technical effect and are not described here in detail to avoid repetition. 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.

[0126] The embodiment of the present application further provides a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the above Figure 1 The various processes of the data asset management method embodiment can achieve the same technical effect. To avoid repetition, they will not be described here.

[0127] In the several embodiments provided in this application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection of some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0128] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may be physically included separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0129] The above-mentioned integrated unit implemented as a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to perform some of the steps of the sending and receiving methods described in various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0130] The above is a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles described in the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A data asset management method, characterized in that: include: Performing a relevance query on at least one data node on the blockchain, wherein the relevance query is used to query the relevance between the asset to be managed and the digital asset pre-stored on the data node; Obtaining a query result for the relevance query fed back by the at least one data node; The asset type of the asset to be managed is determined based on the query result through blockchain consensus, and the asset type includes: new asset type, existing asset type and abnormal asset type.

2. The method according to claim 1, characterized in that Before performing a relevance query on at least one data node on the blockchain, the method further includes: In a case where the asset to be managed is a data asset based on demand, allocating a first identifier to the asset to be managed; If a directory exists in the requirement document of the asset to be managed, reading directory structure information of the asset to be managed; When the directory name in the directory structure information matches the meta-asset, assigning first serial number information to the asset to be managed based on the directory structure information, where the meta-asset is a basic business asset in the blockchain; Constructing a first asset array corresponding to the asset to be managed based on the first identifier, the first serial number information, and the second identifier of the meta-asset; Among them, the first serial number information includes the first directory level serial number and the first natural paragraph serial number in the directory structure information, and the first sequential serial number for matching the asset to be managed with the meta-asset, and the first natural paragraph serial number includes the paragraph number of the text content in the requirement document of the asset to be managed.

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

4. The method according to claim 2 or 3, characterized in that The method further comprises: If no directory exists in the requirements document of the asset to be managed and the text content of the requirements document matches the meta-asset, or if the directory name in the directory structure information does not match the meta-asset, assigning second serial number information to the asset to be managed; Constructing a second asset array corresponding to the asset to be managed based on the first identifier, the second serial number information, and the second identifier of the meta-asset; Among them, the second serial number information includes a second directory level serial number, a second natural paragraph serial number and a second sequential serial number for matching the asset to be managed with the meta-asset, the second directory level serial number is the 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 the paragraph number of the text content in the requirement document.

5. The method according to claim 1, 2 or 3, characterized in that: The determining, through blockchain consensus and based on the query result, the asset type of the asset to be managed includes: If 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, determining that the asset type of the to-be-managed asset is the newly added asset type or the existing 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 results corresponding to each second data node are consistent, it is determined that the asset type of the asset to be managed is the abnormal asset type.

6. The method according to claim 5, characterized in that 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 a sequential serial number for matching the asset to be managed with the meta-asset, wherein the meta-asset is an asset pre-stored on the blockchain and associated with the basic business asset of the asset to be managed; The association query request is at least used to obtain a first query result, and the first query result is used to express a verification result of whether the first identifier is consistent with a third identifier of the digital asset pre-recorded by the data node.

7. The method according to claim 6, characterized in that Determining whether the asset type of the to-be-managed asset is the newly added asset type or the existing asset type includes at least one of the following: If the first query result shows that the first identifier is consistent with the third identifier, determining that the asset type of the asset to be managed is a stock asset type in the blockchain; 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 asset to be managed is a new asset type in the blockchain.

8. The method according to claim 7, characterized in that The method further comprises: Get the first ratio, the second ratio and the third ratio; Among them, the first ratio is the ratio of the sequence number information in the asset array to be identical to the sequence number information in the target information, the second ratio is the ratio of the document content in the requirement document of the asset to be managed to match the asset content in the target information, and the third ratio is the ratio of the document content and sequence number information in the requirement document of the asset to be managed to completely correspond to the basic business asset content and sequence number information in the target information; the target information includes the meta-asset content and sequence number information recorded on the data block storing the meta-asset in the blockchain.

9. The method according to claim 8, characterized in that The method further comprises at least one of the following: When the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the existing asset type, returning the asset to be managed to the requester who initiated the management request for the asset to be managed; If the first ratio is greater than or equal to a first threshold and the asset type of the asset to be managed is the newly added asset type, returning to the requesting party the existing assets in the blockchain that are consistent with the asset to be managed; When the first ratio is less than the first threshold value and the second ratio is greater than or equal to a second threshold value, confirming that the asset type of the to-be-managed asset is a first other type; When the first ratio is less than the first threshold value and the third ratio is greater than or equal to the third threshold value, confirming that the asset type of the to-be-managed asset is a second other type; Among them, the first other type is an asset type that has the same asset content as the existing assets in the blockchain but has a different asset structure; the second other type is an asset type that has the same asset structure as the existing assets in the blockchain but has a different asset content.

10. The method according to claim 8, characterized in that The method further comprises: If the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be modified, construct a first private chain in the blockchain according to the order of version numbers generated when receiving the management request for the asset to be managed, and store the asset to be managed on the first private chain; If the asset type of the asset to be managed is the existing asset type and the asset to be managed needs to be deleted, construct a second private chain in the blockchain according to the order of the version numbers, and adjust the serial number information of the subsequently received asset to be managed after the deletion of the asset to be managed is completed; 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 build an asset chain.

11. The method according to claim 10, characterized in that The step of connecting the target node and the data node associated with the meta-asset of the asset to be managed to build an asset chain includes: Sending the asset array and the version number corresponding to the asset to be managed to the data node associated with the meta-asset in sequence according to the sequence number of the meta-asset; According to the sequence number of the meta-asset, the data nodes associated with the target node and the meta-asset are connected to build the asset chain.

12. A data asset management device, characterized in that: Applied to a Redis server, the device includes: A first sending module is configured to perform a relevance query on at least one data node on the blockchain, wherein the relevance query is configured to query the relevance between the asset to be managed and the digital asset pre-stored on the data node; A first receiving module, configured to obtain a query result for the relevance query fed back by the at least one data node; The first determination module is used to determine the asset type of the asset to be managed based on the query result through blockchain consensus, where the asset type includes: new asset type, existing asset type and abnormal asset type.

13. An electronic device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the data asset management method according to any one of claims 1 to 11.

14. A computer-readable storage medium for storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the data asset management method according to any one of claims 1 to 11 are implemented.

15. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps in the data asset management method according to any one of claims 1 to 11.

Images