CN112732703B - Metadata processing method, metadata processing apparatus, and readable storage medium - Google Patents

Abstract

The embodiment of the application provides a metadata processing method, a metadata processing device and a readable storage medium, wherein different types of metadata templates are maintained in a metadata system, under the condition that enterprise metadata templates uploaded by enterprises are received, similarity matching is carried out on each enterprise metadata item in the enterprise metadata templates and a standard metadata item in a first standard metadata template, a matching result is obtained, and for the enterprise metadata items successfully matched, marks and description information corresponding to the corresponding standard metadata items are fed back to the enterprises. And aiming at the enterprise metadata items which fail to be matched, distributing new identifications and defining new description information thereof, and feeding back the new identifications and the new description information to the enterprise. Therefore, the enterprise modifies the own enterprise metadata template according to the metadata template of the system standard, and further establishes the mapping relation between the local data and each standard data item in the first standard metadata template aiming at the local data so as to ensure that the data transmission can be accurately carried out.

Description

Metadata processing method, metadata processing device and readable storage medium

technical field

The present application relates to the data processing field of the Industrial Internet, and in particular, to a metadata processing method, a metadata processing device, and a readable storage medium.

Background technique

The Industrial Internet is a new application model of a new industrial ecology and key infrastructure that integrates a new generation of information and communication technology with the industrial economy. Intelligent development of enterprises.

Users rely on the industrial Internet identification analysis system to access the server that saves information about objects such as machines, raw materials, parts, and products, and realize the intelligent association of different owners, different places, and heterogeneous information through the industrial Internet identification, for information sharing and product life. Cycle management provides support. The industrial Internet data varies greatly due to the differences in the industry, type, scale, and product of the enterprises. At present, many industrial enterprises have their own metadata templates. The format is not uniform and the interoperability is poor. It is easy to form information islands, and there is no information. be used effectively.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a metadata processing method, a metadata processing device, and a readable storage medium, which are used to solve the problem of poor data interoperability caused by inconsistent metadata template formats in an industrial Internet system.

The embodiment of the first aspect of the present application provides a metadata processing method, which is applied to a metadata system, including:

receiving an enterprise metadata template uploaded by an enterprise, wherein the enterprise metadata template includes at least one enterprise metadata item configured by the enterprise;

Perform similarity matching between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template to obtain a matching result, wherein the matching result includes the first enterprise that has been successfully matched The metadata item and the second enterprise metadata item that failed to match;

Based on the matching result, feedback information is determined, wherein, for the first enterprise metadata item, the feedback information includes identification and description information of a standard data item matching the first enterprise metadata item, and for the first enterprise metadata item, the identification and description information are included in the feedback information. the second enterprise metadata item, add the second enterprise metadata item to the first standard metadata template, configure a new identifier and new description information for the second enterprise metadata item, and the feedback information Include the new identification and new description information;

The feedback information is sent to the enterprise, so that the enterprise establishes a mapping relationship between local data and each standard data item in the first standard metadata template based on the feedback information.

The embodiment of the second aspect of the present application provides a metadata processing apparatus, which is applied to a metadata system, including:

a receiving module, configured to receive an enterprise metadata template uploaded by an enterprise, wherein the enterprise metadata template includes at least one enterprise metadata item configured by the enterprise;

A matching module, configured to perform similarity matching between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template to obtain a matching result, wherein the matching result includes matching A successful first enterprise metadata item and a failed match for a second enterprise metadata item;

A determination module, configured to determine feedback information based on the matching result, wherein, for the first enterprise metadata item, the feedback information includes an identifier of a standard data item that matches the first enterprise metadata item and description information, for the second enterprise metadata item, adding the second enterprise metadata item to the first standard metadata template, and configuring a new identifier and new description information for the second enterprise metadata item, The feedback information includes the new identification and new description information;

A feedback module, configured to send the feedback information to the enterprise, so that the enterprise establishes a mapping relationship between local data and each standard data item in the first standard metadata template based on the feedback information.

Embodiments of a third aspect of the present application provide a metadata processing apparatus, which is applied to a metadata system. The metadata processing apparatus includes a processor, and the processor is configured to implement the foregoing first aspect when executing a computer program stored in a memory. The steps of the metadata processing method.

Embodiments of the fourth aspect of the present application provide a readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of the metadata processing method described in the foregoing first aspect embodiment .

In the technical solutions provided by the embodiments of the present application, different types of metadata templates are maintained in the metadata system, and when an enterprise metadata template uploaded by an enterprise is received, each enterprise metadata item in the enterprise metadata template is associated with The standard metadata items in the first standard metadata template are subjected to similarity matching, and a matching result is obtained. For the enterprise metadata items that are successfully matched, it means that the metadata item has been included in the first standard metadata template in the system. The tags and description information corresponding to the included standard metadata items are fed back to the enterprise. For the enterprise metadata items that fail to match, new identifiers and new description information are assigned to them, and fed back to the enterprise. In this way, the enterprise can clarify the differences between each enterprise metadata item in its own metadata template and each standard metadata item in the first standard metadata template through the feedback information, as well as the relevant description definitions, and convert its own enterprise metadata The template is modified according to the metadata template of the system standard, and then the mapping relationship between the local data and each standard data item in the first standard metadata template is established for the local data, so as to ensure that the data can be transmitted accurately and the data can be effectively stored. use.

Description of drawings

The drawings described herein are used to provide further understanding of the present application and constitute a part of the present application. The schematic embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the attached image:

FIG. 1 is a flowchart of a method for processing metadata according to a first embodiment of the present application;

FIG. 2 is a schematic diagram of an industrial Internet identification resolution system provided by the first embodiment of the present application;

3 is a schematic diagram of a set of standard metadata template data items provided by the first embodiment of the present application;

4 is a flowchart of the metadata system provided by the first embodiment of the present application for determining an enterprise to upload and match an enterprise template;

5 is a flowchart of similarity matching between enterprise metadata items in the enterprise metadata template and standard metadata items in the first standard metadata template provided by the first embodiment of the present application;

FIG. 6 is a flowchart of the identification query performed by the industrial Internet identification analysis system provided by the first embodiment of the present application;

FIG. 7 is a schematic diagram of updating a standard metadata template by forming a blockchain network by an industrial Internet identification resolution system provided by the first embodiment of the present application;

FIG. 8 is a schematic structural diagram of a metadata processing apparatus according to a second embodiment of the present application;

FIG. 9 is a schematic structural diagram of another metadata processing apparatus provided by a third embodiment of the present application.

Detailed ways

The technical solutions of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. If there is no conflict, the embodiments of the present application and the technical features in the embodiments may be combined with each other.

The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

Example

Referring to FIG. 1 , a first embodiment of the present invention provides a method for processing metadata, which is applied to a metadata system. The method includes the following steps:

S101: Receive an enterprise metadata template uploaded by an enterprise, wherein the enterprise metadata template includes at least one enterprise metadata item configured by the enterprise;

S102: Perform similarity matching between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template to obtain a matching result, wherein the matching result includes the first matching successfully an enterprise metadata item and a second enterprise metadata item that failed to match;

S103: Determine feedback information based on the matching result, wherein, for the first enterprise metadata item, the feedback information includes identification and description information of a standard data item matching the first enterprise metadata item, For the second enterprise metadata item, add the second enterprise metadata item to the first standard metadata template, configure a new identification and new description information for the second enterprise metadata item, and the feedback The information includes the new identification and new description information;

S104: Send the feedback information to the enterprise, so that the enterprise establishes a mapping relationship between local data and each standard data item in the first standard metadata template based on the feedback information.

Specifically, the metadata processing method provided in this embodiment is mainly applied to a metadata system, and the metadata system is applied to the international root node, recursive node, national top-level node, secondary node and enterprise node in the industrial Internet identification resolution system Any one or more combinations of the above, the recursive nodes, national top-level nodes, secondary nodes and enterprise nodes of the industrial Internet identification resolution system are all blockchain nodes.

Specifically, please refer to Fig. 2, the industrial Internet identification resolution system includes an international root node, a national top-level node, a second-level node, an enterprise node, and a recursive node. Among them, the international root node is the highest-level service node of the identification system, which is oriented to the global root zone data management and root resolution services. A country's top-level node refers to a node that provides identification code registration and identification resolution services for a country. A secondary node refers to a public service node for identification resolution within an industry or region, which can provide identification code registration and identification resolution services for the industry or region, and complete related identification business management, identification application docking, etc. Secondary nodes contain one or more servers. An enterprise node refers to an identification resolution service node within an enterprise, which can provide identification code registration and identification resolution services for a specific enterprise. The enterprise node also includes one or more identity resolution servers, and enterprise data is stored inside the enterprise node. The recursive node refers to the key entry facility that identifies the parsing system, is responsible for the routing function, routes the parsing request to the corresponding node, and can improve the overall service performance through technical means such as caching. Node deployment introduces blockchain architecture. Enterprise nodes, secondary nodes, and national top-level nodes are all in the blockchain, and the identification data service is on the blockchain nodes, that is, each node can provide corresponding identification resolution services. .

The contractor of each node is responsible for the registration of the logo in the logo domain of the node and the entry of the registered logo information. For example, the contractor of the secondary identification resolution node is responsible for the registration of the industry identification and the entry of the registered identification information. In this way, the registered identification information is stored in the identification resolution server corresponding to the secondary identification resolution node. .

Metadata templates are involved in the exchange of heterogeneous, heterogeneous and heterogeneous data in the Industrial Internet. Metadata template contains various metadata items. Metadata is a kind of electronic catalog. In order to achieve the purpose of cataloguing, it is necessary to describe and collect the content or characteristics of the data, so as to achieve the purpose of assisting data retrieval. For example: There is a student information record, which includes the fields name (name), age (age), gender (male), class (class), etc., then name, age, male, and class are metadata. From their descriptions, a data record of student information is generated. There are many companies involved in the Industrial Internet, and each company has its own meta-template, which is less versatile and has no unified standardization. This will lead to duplication of data uploaded to the system, or inconsistent definitions of metadata item names (for example, some companies Named "identity", and some companies named it "ID"), when the system requests data from the enterprise, the data cannot be obtained effectively due to inconsistent metadata templates. It is necessary to clean and unify to facilitate subsequent metadata template upload, master data upload, and analysis and supervision.

Further, the enterprise will upload its own enterprise metadata template to the metadata system, and after the metadata system receives the enterprise metadata template through step S101, it will determine the corresponding first standard metadata template. Specifically, it can be achieved through the following steps:

determining the target type to which the enterprise metadata template belongs, wherein the metadata system includes standard metadata templates corresponding to industry types and comprehensive types;

A first standard metadata template corresponding to the target type is determined.

Specifically, in this embodiment, the industrial Internet identification analysis involves data generated in the industrial Internet production and supply chain obtained through identification analysis. Divided into attribute data and event data. Attribute data refers to the data that describe the attribute characteristics inherent in the object and distinguish it from other entities. Event data refers to the data used to describe the changes of location, state, ownership, management rights, etc. recorded during the production, circulation, and use of industrial products. generated data. The metadata system maintains a universal and unified metadata template, covering a wide range and all industries, and specifies the description method, metadata model, core metadata description and core metadata extension principles and methods of identification resolution for the Industrial Internet.

For example, a typical standard metadata template maintained by the system is shown in Figure 3. As can be seen from Figure 3, the standard metadata templates maintained by the system include different types of data items, including event types and attribute types, and attribute types include personnel types, product types, machine types, material types, method types, and environment types. , and more detailed types of data items are set under different types. For example, the main data item, location data item and object data item are set under the product type. Enterprise, the corresponding production enterprise item also includes the name of the production enterprise, the unified code of the production enterprise, the registered address of the production enterprise, and the contact information of the production enterprise. By analogy, other types of metadata items and subordinate metadata items can also be deployed and configured in this form, and details are not described here in this embodiment. Of course, in the specific implementation process, more types of data items may also be configured according to actual needs, which are not limited in this embodiment. It should be noted that FIG. 3 is only a schematic diagram of a standard metadata template, and does not constitute a limitation on the standard metadata template. In the specific implementation process, the standard metadata template may also include more or less than the illustration. metadata item.

Further, Figure 3 shows that different types of data items have corresponding identifiers, and the standard metadata items in the standard metadata template are also configured with unique identifiers and corresponding description information. As shown in Figure 3, the standard metadata template The identification of the object data item included in it is 2.2. The corresponding description information contains the relevant definitions of the metadata item, such as: data type, data format, permission information, etc. During the specific implementation process, the description information can be configured according to actual needs, and this embodiment does not limit.

In order to be able to determine whether the enterprise metadata template uploaded by the enterprise is standardized, the system will determine the first standard metadata template for similarity matching. Specifically, in this embodiment, as shown in FIG. 2 , each enterprise node belongs to the corresponding secondary node, the secondary node may be a node in a region, and all enterprise nodes in the region belong to the maintenance of the secondary node, Each secondary node maintains different types of standard metadata templates, involving industry type and comprehensive type. The industry type includes standard metadata templates for various industries that enter the national economic classification, and the comprehensive type includes standard metadata templates for enterprises involved in multiple industries.

Further, please refer to FIG. 4, when an enterprise uploads a metadata template, the system can determine whether the enterprise is a secondary node enterprise, and if so, determine the first standard from the standard metadata template maintained by the secondary node to which it belongs. Metadata template. In the secondary node, based on the type of the enterprise, specifically, it is determined whether the enterprise is an industry type or a comprehensive enterprise, and then the corresponding first standard metadata template is determined according to the corresponding methods of the two types.

Further, to determine whether it is an industry type or a comprehensive type, the following methods can be used but not limited to:

The first: the enterprise chooses the method actively. Using the selected type of the enterprise as a target type, a first standard metadata template corresponding to the target type is determined.

Specifically, in this embodiment, when an enterprise uploads its own enterprise metadata template, it can select a type, including selecting an industry to which it belongs. If the enterprise selects a single industry, such as clothing, machinery, petroleum, automobile, etc. in Figure 4, it is necessary to judge whether there is a standard metadata template of the industry selected by the enterprise in the metadata database. It is used as the first standard metadata template to complete the uploading and matching of enterprise metadata. The standard metadata template of the selected industry has not been stored in the metadata database. According to the middle category of the national economic classification, the enterprise metadata template uploaded by the enterprise can be added as the industry standard metadata template.

If the type selected by the enterprise is a comprehensive type, it is necessary to judge whether there is a clear multi-industry category. In the judgment, the industry selected by the enterprise can be used as the basis for judgment. For example, an enterprise can select multiple industries to upload the enterprise metadata template. As shown in Figure 4, any two or more of clothing, machinery, petroleum, automobiles, etc., are determined to have clear multi-industry categories. Then, the standard metadata templates of each industry in the corresponding multiple industries are integrated as the first standard metadata template for matching. Alternatively, match the enterprise metadata template to the standard metadata template for each industry of your choice.

If there is no clear multi-industry category, the system will automatically determine it. A target type is determined based on the attribute information of the enterprise, and a first standard metadata template corresponding to the target type is determined.

Specifically, in this embodiment, when an enterprise uploads its own enterprise metadata template, it can use the basic attribute information such as "enterprise name" and "production and operation type" that the enterprise fills in when the enterprise registers the metadata system to perform network retrieval and retrieval. Search within the library. The relevant information of the production and operation of the enterprise, the industry it belongs to, etc. can be retrieved through the network. Further, the associated industry is determined, and the standard metadata templates corresponding to the associated industries are integrated to form a first standard metadata template. Alternatively, select the two industries with the highest similarity, and randomly extract 40% of the metadata respectively. In the remaining industries, randomly select 20% of the metadata to form the first standard metadata template, and then complete the upload and matching of the enterprise metadata template. In a specific implementation process, the above-mentioned ratio of random extraction may be configured according to actual needs, which is not limited in this embodiment.

For example, when iron and steel enterprise A uploads its own enterprise metadata template, the system finds out that iron and steel enterprise A belongs to the iron and steel industry through its enterprise name or code. Furthermore, the system can directly analyze the enterprise metadata according to the standard metadata template of the iron and steel industry. Template for similarity matching. The steel industry can also be considered as one of the associated industries. Or, the system finds that steel company A produces strip steel through its company name or code. Strip steel is usually used as a related production material in the industrial field. Therefore, the system will compare the enterprise metadata template according to the standard metadata template of the material class. Sexual match. You can also use the material industry as one of the associated industries. On the basis of obtaining multiple associated industries through retrieval, the standard metadata templates corresponding to the associated industries can be integrated to form a first standard metadata template. Alternatively, select the two industries with the highest similarity, and randomly extract 40% of the metadata respectively. In the remaining industries, randomly select 20% of the metadata to form the first standard metadata template, and then complete the upload and matching of the enterprise metadata template. In a specific implementation process, the above-mentioned ratio of random extraction may be configured according to actual needs, which is not limited in this embodiment.

Of course, it can also be directly based on the automatic matching method of standard metadata templates. Specifically, the similarity between the text information of the enterprise metadata template and the text information of each type of standard metadata template is determined, the target type is determined based on the similarity, and the first standard corresponding to the target type is determined Metadata template.

Specifically, in this embodiment, the system maintains different types of standard metadata templates, the standard metadata items of each standard metadata template are configured with description information, and the description information is set in the form of text. Therefore, each standard metadata template can be integrated to obtain Text information for standard metadata templates. Similarly, for the enterprise metadata template uploaded by the enterprise, the corresponding text information can also be integrated. Furthermore, the similarity between the text information can be obtained by means of semantic analysis, and the standard metadata template with the highest similarity is matched with the enterprise metadata template for the first standard metadata template. Alternatively, select the two standard metadata templates with the highest similarity to randomly extract 40% of the metadata, and randomly select 20% of the metadata from the remaining templates to form the first standard metadata template, and then complete the uploading and matching of the enterprise metadata template. match. In a specific implementation process, the above-mentioned ratio of random extraction may be configured according to actual needs, which is not limited in this embodiment.

Further, if the enterprise uploading the enterprise metadata template is not a second-level node enterprise, when uploading its own enterprise metadata template, the enterprise can use the "enterprise name", "production and operation type" that the enterprise filled in when the enterprise registered the metadata system, etc. Basic attribute information for network retrieval and in-library retrieval. The relevant information of the production and operation of the enterprise, the industry it belongs to, etc. can be retrieved through the network. Further, the associated industry is determined, and the standard metadata templates corresponding to the associated industries are integrated to form a first standard metadata template. Alternatively, select the two industries with the highest similarity, and randomly extract 40% of the metadata respectively. In the remaining industries, randomly select 20% of the metadata to form the first standard metadata template, and then complete the upload and matching of the enterprise metadata template. In the specific implementation process, the ratio of random extraction can be configured according to actual needs, which is not limited in this embodiment.

Further, after the first standard metadata template is determined, step S102 is performed to perform similarity matching between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template to obtain match results. Specifically, please refer to FIG. 5 , step S102 can be implemented by the following steps:

determining a feature vector of each of the enterprise metadata items and a feature vector of each of the standard metadata items based on a semantic analysis algorithm;

determining the similarity between each of the enterprise metadata items and each of the standard metadata items based on the feature vector of each of the enterprise metadata items and the feature vector of each of the standard metadata items;

If the similarity between the enterprise metadata item and the standard metadata item satisfies the threshold condition, the matching result is successful; if the similarity between the enterprise metadata item and the standard metadata item does not meet the threshold condition, the matching The result is a match failure.

Specifically, in this embodiment, a feature vector is formed after semantic analysis is performed on the name and description information of each enterprise metadata item in the enterprise metadata template uploaded by the enterprise. For each standard metadata item in the first standard metadata template, corresponding identification and description information are also configured in the system, and the description information includes relevant descriptions and definitions of the standard metadata item. Similarly, the feature vector of each standard metadata item can also be determined based on the semantic analysis algorithm. In this way, the similarity between the feature vectors of each enterprise metadata item and each standard metadata item can be calculated.

Further, according to the similarity between the feature vectors of each enterprise metadata item and each standard metadata item, if the similarity satisfies the threshold condition, the matching result is determined to be successful, and it is used as the first enterprise metadata that is successfully matched. item. For the remaining enterprise metadata items, it is determined that the matching result is a matching failure, and it is regarded as the second enterprise metadata item whose matching fails. The threshold condition may be greater than the preset threshold, and the preset threshold may be set to 90%, 95% and other values according to actual needs. In the specific implementation process, the preset threshold may be set according to actual needs. The embodiment is not limited.

For example, assume that the enterprise metadata template uploaded by Company A includes: the name of the manufacturing enterprise, the unified code of the manufacturing enterprise, the registered address of the manufacturing enterprise, the contact information of the manufacturing enterprise, and the country of the manufacturing enterprise.

The first standard metadata template of the product category maintained by the metadata system and corresponding to the enterprise metadata template uploaded by Company A includes: the name of the manufacturer, the unified code of the manufacturer, the registered address of the manufacturer, and the contact information of the manufacturer.

Assuming that the first standard metadata template is shown in Figure 3, it can be determined from Figure 3 that the identification information of each standard metadata item in the first standard metadata template includes: the name of the manufacturer is 2.1.1.1, and the unified code of the manufacturer is 2.1. 1.2, the registered address of the manufacturer is 2.1.1.3, and the contact information of the manufacturer is 2.1.1.4.

Further, according to step S102, it is determined that the similarity between the manufacturing enterprise name and the manufacturing enterprise name in the enterprise metadata template is greater than the preset threshold, and assuming that the preset threshold is 95%, then determine the "manufacturing enterprise name" in the enterprise metadata template. If the similarity with the "manufacturing company name" in the first standard metadata template is greater than 95%, the similarity matching is successful. Further, through step S103, the identifier 2.1.1.1 corresponding to the "production enterprise name" in the first standard metadata template is assigned to it. In addition, the feedback information also includes description information about the "name of the manufacturer", and the description information includes the correct standard metadata item name and related data definitions. In the same way, the identification of the "uniform code of manufacturing enterprises" in the first standard metadata template is determined as 2.1.1.2 in the same way. In the same way, the "registered address of the manufacturing enterprise" is identified as 2.1.1.3 in the first standard metadata template. For "manufacturing enterprise contact information", its identification in the first standard metadata template is determined as 2.1.1.4 in the same manner.

For "manufacturing enterprise country", if there is no standard metadata item in the first standard metadata template, it can be added to the first standard metadata template and configured with new identifiers 2.1.1.5 and new Description. The feedback information will also include the identification and description information of the metadata item, and mark it as a new metadata item, including: the name of the manufacturing enterprise is 2.1.1.1, the unified code of the manufacturing enterprise is 2.1.1.2, and the registered address of the manufacturing enterprise It is 2.1.1.3, the manufacturing company contact information is 2.1.1.4, and the manufacturing company country (new) is 2.1.1.5 (new).

Because the feedback information includes the relevant matching information for each enterprise metadata item in the enterprise metadata template, including the identification and description information of the correct standard metadata item that has been successfully matched, the description information includes the correct name and Therefore, based on the feedback information, the enterprise can correct the enterprise metadata items that have been matched successfully, but the similarity has not reached 100%, and there are inconsistencies, and it is consistent with the standard metadata items corresponding to the system. is 100%. And, according to each metadata item in the revised enterprise metadata template, the local data associated therewith is determined. In this way, when the metadata system requests the master data of standard metadata items from the enterprise, the enterprise can respond accurately and upload the data requested by the system to the system, so as to improve the circulation of data between enterprises, improve the utilization rate of data, and realize the relevant Object data lifecycle management and monitoring.

In this embodiment, for the industrial field, the data applied to product traceability mainly includes attribute data of the product (data obtained from industrial software, such as product brand), finished product data of the product (data collected on site such as rfid) . In order to realize data traceability, the metadata system unifies the metadata templates in the system according to the aforementioned method to realize data cleaning, after data cleaning. The data fields, data definitions, and mapping methods of different fields are clarified, so that the data of different enterprises in the upstream and downstream of the industrial chain can be exchanged.

In order to realize the management of the whole life cycle of the data object, the method of this embodiment further includes:

receiving first master data corresponding to the first standard metadata template uploaded by the enterprise based on the feedback information;

Based on the first master data, a second standard metadata template associated with the first standard metadata template is determined, and a mapping relationship between the first standard metadata template and the second standard metadata template is established.

Specifically, in the foregoing embodiments, it is introduced that the system maintains different types of standard metadata templates, including event types and attribute types, that is, dynamic types and static types. In the Industrial Internet, a product object may be associated with multiple companies. For example, the production company corresponds to the attribute type metadata template, while the transportation company and the operation company use the event type metadata template for the product object.

In this way, if the system obtains permission to obtain the first master data corresponding to the first standard metadata template uploaded by the enterprise based on the feedback information, it can determine the second standard metadata associated with the first standard metadata template based on the first master data template, to establish a mapping relationship between the first standard metadata template and the second standard metadata template. For example, iron and steel production enterprises, iron and steel distribution enterprises, and iron and steel users upload master data according to their corresponding standard metadata templates. The master data uploaded by iron and steel manufacturers based on the first standard metadata template includes the identification or production of iron and steel. Enterprise name, code, etc. If the steel distribution enterprise uploads the same steel logo or production enterprise name, code, etc. based on the second standard metadata template, establish the mapping relationship between the first standard metadata template and the second standard metadata template . In this way, when an authorized user conducts a query through the identification of iron and steel, both the first standard metadata template and the second standard metadata template can be fed back to the authorized user as query results. At the same time, if the authorized user has the right to access the local data of the enterprise, the enterprise corresponding to the first standard metadata template and the enterprise corresponding to the second standard metadata will also respectively feed back the corresponding data as the query result. In this way, the data between enterprises can be associated, and the management of the whole life cycle of object data can be realized.

Further, in this embodiment, the system may also pre-establish a mapping relationship between different types of standard metadata templates, such as a mapping relationship between a standard metadata template for a TV class and a standard metadata template for a TV screen. Alternatively, the mapping relationship between the standard metadata template of mineral raw materials and the standard metadata template of strip steel, etc., can be set according to actual needs in the specific implementation process, which is not limited in this embodiment.

The metadata system in this embodiment is mainly applied to recursive nodes, national top-level nodes, and secondary nodes in the industrial Internet identification resolution system. Each node can provide an entry for analysis and query, and the query method can be implemented through the following steps:

receiving a query request, where the query request includes an identifier to be queried;

sending the query request to the recursive node, so that the recursive node sends a parsing request to the country top-level node and the second-level node, respectively, so that the country top-level node and/or the second-level node Parse out the target metadata item corresponding to the identifier to be queried and the target enterprise node where the target metadata item is located;

receiving target master data corresponding to the target metadata item fed back by the target enterprise node;

The target metadata item and the target main data are fed back to the requester of the query request.

Specifically, in this embodiment, each enterprise node of the access system maintains its own data, and each secondary node, national top-level node, and enterprise node are provided with identification data services for users to query data. The identifiers in this embodiment may refer to the industrial Internet identifiers of items/equipment/machines, and may also refer to identifiers for other purposes, such as user identifiers, product type identifiers, etc. In the specific implementation process, they can be set according to actual needs. Here , which is not limited in this embodiment. The identification includes an identification code and a list of identification values. The identification code is equivalent to an "identity card" and is unique. It can also be said that an identification code represents an identification, or an object, equipment, machine, administrator, etc. behind the identification. Specifically, the identification code includes a prefix and a suffix, and the prefix and the suffix are separated by "/". For example, in the identification code 88.100.1/xxx, "88.100.1" is the prefix and "xxx" is the suffix. Other identifiers other than product type identifiers that characterize items/equipment/machines/users may be collectively referred to as "metadata identifiers", and multiple metadata identifiers of the same category are associated with the same product type identifier.

Further, please refer to FIG. 6 , a query request is received through the identification data service of the node, the query request includes the identification to be queried, the query request is sent to the recursive node, and the recursive node is configured with a routing function, and the parsing request is first It is sent to the corresponding secondary node, and the identification resolution function of the secondary node is mainly to provide public resolution services for the assigned identification. For the identification code allocated by the secondary node itself, the secondary node configures routing information corresponding to the allocated identification in its identification resolution function. When receiving an identification resolution request, if the secondary node saves information such as the route corresponding to the identification code, it will directly reply to the information such as the communication address of the enterprise node corresponding to the identification code and the corresponding target metadata item. If the secondary node does not have the identification code Corresponding routing and other information, the return information of the secondary node is empty.

If the return information of the secondary node is empty, the parsing request will be sent to the national top-level node for analysis, and then the target secondary node will be located through the national top-level node, and then the target secondary node will reply to the enterprise node communication address corresponding to the identification code and The corresponding target metadata item and other information, and then access the enterprise node according to the address. If the requester has access rights, the enterprise node feeds back the target metadata item and the corresponding target master data to the system, and the system sends the target metadata item and the corresponding target. The master data is fed back to the requester. At the same time, the standard metadata template involved in the identifier to be queried can also be fed back to the requester as the query result. In the specific implementation process, the query result may be configured according to actual needs, which is not limited in this embodiment.

Further, in this embodiment, please refer to FIG. 7 , the node deployment introduces a blockchain architecture, enterprise nodes, secondary nodes, and national top-level nodes are all in the blockchain, and the identification data service is on the blockchain nodes. Based on the characteristics of the blockchain system, the identification of each node is not easily tampered with to ensure data security. In addition, the query record can be stored in the corresponding node to realize information traceability, and based on the blockchain technology, the upload data terminal and the query data terminal can also be effectively authenticated to ensure data security.

Further, when the standard metadata template maintained in each node needs to be updated, the system initiates a voting event to each node in the blockchain network, and the voting event includes the first standard metadata template of the original version and the first standard metadata template of the new version. A metadata item of a standard metadata template. and the industry to which the first standard metadata template belongs. In order to make the nodes in the blockchain respond to the voting event and vote based on the consensus mechanism update. If the vote is passed, the update is performed and the update record is saved to the relevant blockchain node, so that the update record can be traced back. The blockchain-based voting mechanism is used to update the first standard metadata template. The voting results reflect the update willingness of most nodes in the blockchain, which can ensure that the update is fair and reasonable, and the upgrade and update are more optimized and accurate. The encryption of standard metadata templates in each node and the management of data rights can be determined by voting through the consensus mechanism in the blockchain network to ensure data security.

Referring to FIG. 8, a second embodiment of the present invention provides a metadata processing apparatus, which is applied to a metadata system, including:

A receiving module 801, configured to receive an enterprise metadata template uploaded by an enterprise, wherein the enterprise metadata template includes at least one enterprise metadata item configured by the enterprise;

A matching module 802, configured to perform similarity matching between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template to obtain a matching result, wherein the matching result includes The first enterprise metadata item that successfully matches and the second enterprise metadata item that fails to match;

A determination module 803, configured to determine feedback information based on the matching result, wherein, for the first enterprise metadata item, the feedback information includes an identifier of a standard data item that matches the first enterprise metadata item and description information, for the second enterprise metadata item, add the second enterprise metadata item to the first standard metadata template, and configure a new identification and new description information for the second enterprise metadata item , the feedback information includes the new identification and new description information;

The feedback module 804 is configured to send the feedback information to the enterprise, so that the enterprise establishes a mapping relationship between local data and each standard data item in the first standard metadata template based on the feedback information.

In an optional implementation manner, the matching module is specifically used for:

determining a feature vector of each of the enterprise metadata items and a feature vector of each of the standard metadata items based on a semantic analysis algorithm;

determining the similarity between each of the enterprise metadata items and each of the standard metadata items based on the feature vector of each of the enterprise metadata items and the feature vector of each of the standard metadata items;

If the similarity between the enterprise metadata item and the standard metadata item satisfies the threshold condition, the matching result is successful; if the similarity between the enterprise metadata item and the standard metadata item does not meet the threshold condition, the matching The result is a match failure.

In an optional implementation manner, the metadata processing apparatus further includes a determination module, and the determination module is specifically configured to:

Before performing similarity matching between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template, determine the target type to which the enterprise metadata template belongs, wherein, The metadata system includes standard metadata templates corresponding to industry types and comprehensive types;

A first standard metadata template corresponding to the target type is determined.

In an optional implementation manner, the determining module is specifically used for:

the selected type of said business as the target type; or

determine a target type based on attribute information of the business; or

Similarity between the textual information of the enterprise metadata template and the textual information of each type of standard metadata template is determined, and the target type is determined based on the similarity.

In an optional implementation manner, the metadata processing apparatus further includes a mapping module, and the mapping module is specifically configured to:

After sending the feedback information to the enterprise, receiving first master data corresponding to the first standard metadata template uploaded by the enterprise based on the feedback information;

Based on the first master data, a second standard metadata template associated with the first standard metadata template is determined, and a mapping relationship between the first standard metadata template and the second standard metadata template is established.

In an optional embodiment, the metadata system is applied to any one or more combinations of recursive nodes, national top-level nodes, and secondary nodes in the industrial Internet identification resolution system. The recursive nodes, national top-level nodes, secondary nodes and enterprise nodes are all blockchain nodes.

In an optional implementation manner, the metadata processing apparatus further includes a query module, and the determination module is specifically configured to:

receiving a query request, where the query request includes an identifier to be queried;

sending the query request to the recursive node, so that the recursive node sends a parsing request to the country top-level node and the second-level node, respectively, so that the country top-level node and/or the second-level node Parse out the target metadata item corresponding to the identifier to be queried and the target enterprise node where the target metadata item is located;

receiving target master data corresponding to the target metadata item fed back by the target enterprise node;

The target metadata item and the target main data are fed back to the requester of the query request.

The detailed process of data processing performed by the metadata processing apparatus in this embodiment has been described in detail in the foregoing first embodiment, and reference may be made to the content in the first embodiment, which will not be repeated in this embodiment.

Referring to FIG. 9, a third embodiment of the present invention provides an apparatus for processing metadata. The apparatus in this embodiment includes: a processor 901, a memory 902, and a device stored in the memory and running on the processor The computer program, such as the program corresponding to the metadata processing method in the first embodiment. When the processor executes the computer program, the steps in each metadata processing method in the first embodiment described above are implemented. Alternatively, when the processor executes the computer program, the functions of each module/unit in the apparatus of the second embodiment described above are implemented.

Exemplarily, the computer program may be divided into one or more modules/units, and the one or more modules/units are stored in the memory and executed by the processor to accomplish the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the computer device.

The metadata processing apparatus may include, but is not limited to, a processor and a memory. Those skilled in the art can understand that the schematic diagram 9 is only an example of a computer device, and does not constitute a limitation to the device. It may include more or less components than the one shown, or combine some components, or For example, the metadata processing apparatus may further include an input/output device, a network access device, a bus, and the like.

The so-called processor 901 may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), Off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The processor is the control center of the computer device, and uses various interfaces and lines to connect various parts of the entire computer device.

The memory 902 can be used to store the computer program and/or module, and the processor implements the computer program and/or module by running or executing the computer program and/or module stored in the memory and calling the data stored in the memory. Various functions of a computer device. The memory may mainly include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the storage data area may store Data created according to the usage of the mobile phone (such as audio data, video data, etc.), etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory such as hard disk, internal memory, plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card , a flash card (Flash Card), at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

Further, the processor 901 included in the metadata processing apparatus also has the following functions:

receiving an enterprise metadata template uploaded by an enterprise, wherein the enterprise metadata template includes at least one enterprise metadata item configured by the enterprise;

Perform similarity matching between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template to obtain a matching result, wherein the matching result includes the first enterprise that has been successfully matched The metadata item and the second enterprise metadata item that failed to match;

Based on the matching result, feedback information is determined, wherein, for the first enterprise metadata item, the feedback information includes identification and description information of a standard data item matching the first enterprise metadata item, and for the first enterprise metadata item, the identification and description information are included in the feedback information. the second enterprise metadata item, add the second enterprise metadata item to the first standard metadata template, configure a new identifier and new description information for the second enterprise metadata item, and the feedback information Include the new identification and new description information;

The feedback information is sent to the enterprise, so that the enterprise establishes a mapping relationship between local data and each standard data item in the first standard metadata template based on the feedback information.

Further, the processor 901 included in the metadata processing apparatus also has the following functions:

determining a feature vector of each of the enterprise metadata items and a feature vector of each of the standard metadata items based on a semantic analysis algorithm;

determining the similarity between each of the enterprise metadata items and each of the standard metadata items based on the feature vector of each of the enterprise metadata items and the feature vector of each of the standard metadata items;

If the similarity between the enterprise metadata item and the standard metadata item satisfies the threshold condition, the matching result is successful; if the similarity between the enterprise metadata item and the standard metadata item does not meet the threshold condition, the matching The result is a match failure.

Further, the processor 901 included in the metadata processing apparatus also has the following functions:

Before performing similarity matching between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template, determine the target type to which the enterprise metadata template belongs, wherein, The metadata system includes standard metadata templates corresponding to industry types and comprehensive types;

A first standard metadata template corresponding to the target type is determined.

Further, the processor 901 included in the metadata processing apparatus also has the following functions:

the selected type of said business as the target type; or

determine a target type based on attribute information of the business; or

Similarity between the textual information of the enterprise metadata template and the textual information of each type of standard metadata template is determined, and the target type is determined based on the similarity.

Further, the processor 901 included in the metadata processing apparatus also has the following functions:

After the sending the feedback information to the enterprise, receiving first master data corresponding to the first standard metadata template uploaded by the enterprise based on the feedback information;

Based on the first master data, a second standard metadata template associated with the first standard metadata template is determined, and a mapping relationship between the first standard metadata template and the second standard metadata template is established.

Further, the metadata system is applied to any one or more combinations of recursive nodes, national top-level nodes, and secondary nodes in the industrial Internet identification resolution system, and the recursive nodes, national top-level nodes, Both secondary nodes and enterprise nodes are blockchain nodes.

Further, the processor 901 included in the metadata processing apparatus also has the following functions:

receiving a query request, where the query request includes an identifier to be queried;

sending the query request to the recursive node, so that the recursive node sends a parsing request to the country top-level node and the second-level node, respectively, so that the country top-level node and/or the second-level node Parse out the target metadata item corresponding to the identifier to be queried and the target enterprise node where the target metadata item is located;

receiving target master data corresponding to the target metadata item fed back by the target enterprise node;

The target metadata item and the target main data are fed back to the requester of the query request.

The fourth embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored. If the functional units integrated in the metadata processing apparatus in the second embodiment of the present invention are implemented in the form of software functional units and When sold or used as a stand-alone product, it may be stored on a computer-readable storage medium. Based on this understanding, the present invention realizes all or part of the process in the metadata processing method of the first embodiment, and can also be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable In the storage medium, when the computer program is executed by the processor, the steps of the foregoing method embodiments can be implemented. Wherein, the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file or some intermediate form, and the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, removable hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable media may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer-readable media Electric carrier signals and telecommunication signals are not included.

Although preferred embodiments of the present invention have been described, additional changes and modifications to these embodiments may occur to those skilled in the art once the basic inventive concepts are known. Therefore, the appended claims are intended to be construed to include the preferred embodiment and all changes and modifications that fall within the scope of the present invention.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit and scope of the invention. Thus, provided that these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims (7)

1. A metadata processing method, applied to a metadata system, is characterized in that, comprising: receiving an enterprise metadata template uploaded by an enterprise, wherein the enterprise metadata template includes at least one enterprise metadata item configured by the enterprise; determining the target type to which the enterprise metadata template belongs, wherein the metadata system includes standard metadata templates corresponding to industry types and comprehensive types; Determine a first standard metadata template corresponding to the target type, wherein, if the target type is a comprehensive type, integrate the standard metadata templates of each industry in multiple industries corresponding to the comprehensive type as the target type The first standard metadata template; Perform similarity matching between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template to obtain a matching result, wherein the matching result includes the first enterprise that has been successfully matched The metadata item and the second enterprise metadata item that failed to match; Based on the matching result, feedback information is determined, wherein, for the first enterprise metadata item, the feedback information includes identification and description information of a standard data item matching the first enterprise metadata item, and for the first enterprise metadata item, the identification and description information are included in the feedback information. the second enterprise metadata item, add the second enterprise metadata item to the first standard metadata template, configure a new identifier and new description information for the second enterprise metadata item, and the feedback information Include the new identification and new description information; sending the feedback information to the enterprise, so that the enterprise establishes a mapping relationship between local data and each standard data item in the first standard metadata template based on the feedback information; receiving first master data corresponding to the first standard metadata template uploaded by the enterprise based on the feedback information; Based on the first master data, determine a second standard metadata template associated with the first standard metadata template, and establish a mapping relationship between the first standard metadata template and the second standard metadata template; Wherein, the metadata system is applied to any one or more combinations of recursive nodes, national top-level nodes, and secondary nodes in the industrial Internet identification resolution system, and the recursive nodes, national top-level nodes, Both the secondary node and the enterprise node are blockchain nodes in the blockchain network. When it is determined that the first standard metadata template needs to be updated, a voting event is initiated to each node in the blockchain network, so that the The nodes in the blockchain respond to the voting event, vote based on the consensus mechanism, and if the vote is passed, update the update records and save the update records to the relevant blockchain nodes. 2. The method according to claim 1, wherein the similarity matching is performed between each enterprise metadata item in the enterprise metadata template and the standard metadata item in the first standard metadata template, Get matching results, including: determining a feature vector of each of the enterprise metadata items and a feature vector of each of the standard metadata items based on a semantic analysis algorithm; determining the similarity between each of the enterprise metadata items and each of the standard metadata items based on the feature vector of each of the enterprise metadata items and the feature vector of each of the standard metadata items; If the similarity between the enterprise metadata item and the standard metadata item satisfies the threshold condition, the matching result is successful; if the similarity between the enterprise metadata item and the standard metadata item does not meet the threshold condition, the matching The result is a match failure. 3. The method according to claim 1, wherein the determining the target type to which the enterprise metadata template belongs comprises: the selected type of said business as the target type; or determine a target type based on attribute information of the business; or Similarity between the textual information of the enterprise metadata template and the textual information of each type of standard metadata template is determined, and the target type is determined based on the similarity. 4. The method according to claim 1, wherein the method further comprises: receiving a query request, where the query request includes an identifier to be queried; sending the query request to the recursive node, so that the recursive node sends a parsing request to the country top-level node and the second-level node, respectively, so that the country top-level node and/or the second-level node Parse out the target metadata item corresponding to the identifier to be queried and the target enterprise node where the target metadata item is located; receiving target master data corresponding to the target metadata item fed back by the target enterprise node; The target metadata item and the target main data are fed back to the requester of the query request. 5. A metadata processing device, applied to a metadata system, characterized in that, comprising: a receiving module, configured to receive an enterprise metadata template uploaded by an enterprise, wherein the enterprise metadata template includes at least one enterprise metadata item configured by the enterprise; a matching module for determining the target type to which the enterprise metadata template belongs, wherein the metadata system includes standard metadata templates corresponding to industry types and comprehensive types; determining the first standard metadata corresponding to the target type A data template, wherein, if the target type is a comprehensive type, the standard metadata templates of each industry in the multiple industries corresponding to the comprehensive type are integrated as the first standard metadata template; the enterprise metadata Perform similarity matching between each enterprise metadata item in the data template and the standard metadata item in the first standard metadata template to obtain a matching result, wherein the matching result includes the successfully matched first enterprise metadata item and the matching the failed second enterprise metadata item; A determination module, configured to determine feedback information based on the matching result, wherein, for the first enterprise metadata item, the feedback information includes an identifier of a standard data item that matches the first enterprise metadata item and description information, for the second enterprise metadata item, adding the second enterprise metadata item to the first standard metadata template, and configuring a new identifier and new description information for the second enterprise metadata item, The feedback information includes the new identification and new description information; a feedback module, configured to send the feedback information to the enterprise, so that the enterprise establishes a mapping relationship between local data and each standard data item in the first standard metadata template based on the feedback information; first master data corresponding to the first standard metadata template uploaded by the enterprise based on the feedback information; based on the first master data, determine second standard metadata associated with the first standard metadata template template, establishing a mapping relationship between the first standard metadata template and the second standard metadata template; Wherein, the metadata system is applied to any one or more combinations of recursive nodes, national top-level nodes, and secondary nodes in the industrial Internet identification resolution system, and the recursive nodes, national top-level nodes, Both the secondary node and the enterprise node are blockchain nodes in the blockchain network, and the determination module initiates a vote to each node in the blockchain network when it is determined that the first standard metadata template needs to be updated event, so that the nodes in the blockchain respond to the voting event, vote based on the consensus mechanism, and if the vote is passed, update and save the update records to the relevant blockchain nodes. 6. A metadata processing device, applied to a metadata system, characterized in that the metadata processing device comprises a processor, and when the processor is used to execute a computer program stored in a memory, the implementation as in claims 1-4 is realized. The steps of any one of the metadata processing methods. 7 . A readable storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the steps of the metadata processing method according to any one of claims 1 to 4 are implemented.

Images