Industrial data consanguinity display method, system and equipment and storage medium

Abstract

The invention provides an industrial data consanguinity display method, system and device and a storage medium, the method comprises the steps that different types of metadata about industrial data in the industrial production process are obtained, the types of the metadata comprise collection data, processing data and application data, the processing data is obtained by performing data processing on the collection data, and the application data is obtained by performing data processing on the application data; the application data is obtained from an application using the acquisition data and / or the processing data; constructing a blood relationship node corresponding to each type of metadata; according to the dependency relationship among the collection data, the processing data and the application data, the blood relationship among different blood relationship nodes is determined, and the dependency relationship is used for representing flow paths among various types of metadata; and constructing a blood relationship graph based on the blood relationship nodes and the blood relationship so as to complete blood relationship display of the industrial data. Thus, in the use process of the industrial data, if data exception exists, the source of the exception can be quickly and accurately traced through the blood relationship graph, and the troubleshooting difficulty and cost are reduced.

Description

Technical Field

[0001] The present application relates to the technical field of software development, and in particular, to a method, system, device, and storage medium for displaying the lineage of industrial data. Background Art

[0002] With the rapid development of modern industrial intelligent manufacturing, in industrial production, the production data of equipment has become a decisive factor driving industrial manufacturing processes and production management decisions, covering not only every link of product generation but also multi-dimensional information such as equipment operation, energy consumption efficiency, and maintenance records. However, with the wide application of technologies such as the Internet of Things (IoT), big data, and cloud computing, the collection frequency, storage scale, and processing complexity of industrial production data have all shown explosive growth, posing unprecedented challenges to the accuracy, timeliness, and traceability of data.

[0003] In related technologies, most conventional data management tools are limited to the level of enterprise internal information systems. However, for industrial data in the production process, due to its temporal nature and often being closely related to specific production events or equipment states, conventional methods are difficult to penetrate into the details of data collection, transmission, and processing in the industrial field, that is, it is impossible to trace from the information system of application data to the collection gateway, industrial equipment, etc. As a result, when data problems occur, it is impossible to quickly and accurately trace back to the source, greatly increasing the difficulty and cost of problem troubleshooting. Therefore, how to effectively track the lineage of industrial data and display it, so as to trace the root cause of data anomalies in a timely and accurate manner is crucial. Summary of the Invention

[0004] To provide a basic understanding of some aspects of the disclosed embodiments, a simple summary is given below. This summary is not a comprehensive review, nor is it intended to identify key / important elements or delineate the scope of protection of these embodiments, but rather serves as a preface to the subsequent detailed description.

[0005] In view of the above-mentioned disadvantages of the prior art, the present application discloses a method, system, device, and storage medium for displaying the lineage of industrial data to solve the above technical problem of how to quickly and accurately trace back to the root cause of industrial data anomalies.

[0006] First aspect, the present application provides a method for displaying the lineage of industrial data. The method includes: obtaining metadata of different types regarding industrial data during the industrial production process, where the types of the metadata include acquisition data, processing data, and application data. The processing data is obtained by processing the acquisition data, and the application data is obtained from applications that use the acquisition data and / or the processing data; constructing lineage nodes corresponding to each type of the metadata; determining the lineage relationships between different lineage nodes according to the dependency relationships between the acquisition data, the processing data, and the application data, where the dependency relationships are used to represent the flow paths between various types of the metadata; and constructing a lineage relationship graph based on the lineage nodes and the lineage relationships to complete the display of the lineage of the industrial data.

[0007] In an embodiment of the present application, the constructing lineage nodes corresponding to each type of the metadata includes: respectively converting different types of the metadata according to a predefined data structure to determine the general information and extended information of each metadata. The general information includes a unique identifier, a name, and a type, and the extended information is custom information; constructing a lineage node of the same metadata according to the general information and the extended information, where the lineage node has a unique identifier.

[0008] In an embodiment of the present application, before determining the lineage relationships between different lineage nodes, it further includes: obtaining the data flow paths and data flow rules between different types of the metadata; parsing according to the data flow paths and the data flow rules to determine the dependency relationships between the acquisition data, the processing data, and the application data, where the acquisition data includes device data, gateway data, and measurement point data, and the processing data includes aggregation point data and task point data.

[0009] In an embodiment of the present application, the dependency relationships include a first dependency relationship, a second dependency relationship, and a third dependency relationship; the determining the lineage relationships between different lineage nodes includes: dividing each of the lineage nodes to determine the lineage nodes of each type, where the types of the lineage nodes include device nodes, gateway nodes, measurement point nodes, aggregation nodes, task nodes, and application nodes; constructing the lineage relationships between different types of the lineage nodes according to the first dependency relationship, the second dependency relationship, and the third dependency relationship, where the first dependency relationship is used to determine the dependency relationships between device nodes, gateway nodes, and measurement point nodes, the second dependency relationship is used to determine the dependency relationships between measurement point nodes, aggregation nodes, and task nodes, and the third dependency relationship is used to determine the dependency relationships between measurement point nodes, aggregation nodes, task nodes respectively and the application node.

[0010] In an embodiment of the present application, constructing a blood relationship graph based on the blood relationship nodes and the blood relationship includes: defining each of the blood relationship nodes as a graph node of the blood relationship graph, and defining the blood relationship between the blood relationship nodes as an edge of the blood relationship graph; constructing the blood relationship graph based on the graph nodes and the edges, and the blood relationship graph is a directed acyclic graph.

[0011] In an embodiment of the present application, after constructing the blood relationship graph based on the blood relationship nodes and the blood relationship, it further includes: monitoring a database storing the blood relationship nodes and the blood relationship; if a change event of the blood relationship nodes or the blood relationship is monitored, then in response to the change event, synchronously updating the blood relationship graph, and the change event includes addition, modification, and deletion.

[0012] In an embodiment of the present application, after constructing the blood relationship graph based on the blood relationship nodes and the blood relationship, it further includes: designating any one of the blood relationship nodes as a starting node; traversing the blood relationship graph based on the starting node to implement blood relationship tracing of the starting node, and visually displaying the traversal result.

[0013] In a second aspect, the present application provides a blood relationship display system for industrial data, and the system includes: an industrial data acquisition module, configured to acquire metadata of different types regarding industrial data in an industrial production process, and the types of the metadata include acquisition data, processing data, and application data, the processing data is obtained by processing the acquisition data, and the application data is obtained from an application using the acquisition data and / or the processing data; a blood relationship node construction module, configured to construct blood relationship nodes corresponding to each type of the metadata; a blood relationship determination module, configured to determine the blood relationship between different blood relationship nodes according to the dependency relationship between the acquisition data, the processing data, and the application data, and the dependency relationship is used to represent the flow path between various types of the metadata; a blood relationship display module, configured to construct a blood relationship graph based on the blood relationship nodes and the blood relationship to complete the blood relationship display of the industrial data.

[0014] In a third aspect, the present application further provides an electronic device, including: a processor, a memory, and a communication bus; the communication bus is used to connect the processor and the memory; the processor is configured to execute a computer program stored in the memory to implement the blood relationship display method for industrial data as described in the above embodiments.

[0015] In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor of a computer, the computer is enabled to execute the method as described in the above embodiments.

[0016] Advantages of the present application: The present application proposes a method, system, device, and storage medium for displaying the lineage of industrial data. By obtaining various types of metadata regarding industrial data during the industrial production process, namely, the acquisition data, processing data, and application data generated from the data acquisition of industrial field devices to data application, then constructing lineage nodes corresponding to each type of industrial data, and determining the lineage relationships between different lineage nodes, a lineage relationship graph is constructed based on the lineage nodes and lineage relationships to complete the display of the lineage of industrial data. In this way, the lineage of industrial data can be comprehensively and accurately traced through the lineage relationship graph. That is to say, during the use of industrial data, if there is data anomaly, the root cause of the anomaly can be quickly and accurately traced through the lineage relationship graph, and it can be traced from the business system of application data to the acquisition gateway, industrial devices, etc., reducing the difficulty and cost of troubleshooting, which is of great significance for improving the efficiency and level of industrial intelligent manufacturing.

[0017] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and cannot limit the present application. Brief Description of the Drawings

[0018] The drawings herein are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts. In the drawings:

[0019] Figure 1 is a flowchart of a method for displaying the lineage of industrial data shown in an exemplary embodiment of the present application;

[0020] Figure 2 is a schematic diagram of a lineage relationship shown in an exemplary embodiment of the present application;

[0021] Figure 3 is a block diagram of a system for displaying the lineage of industrial data shown in an exemplary embodiment of the present application;

[0022] Figure 4 is a schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application shown in an exemplary embodiment of the present application. Detailed Embodiments

[0023] The embodiments of the present application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present application from the content disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present application. It should be understood that the preferred embodiments are only for illustrating the present application, rather than for limiting the protection scope of the present application.

[0024] It should be noted that the diagrams provided in the following embodiments only illustrate the basic concept of the present application in a schematic manner. Therefore, only the components related to the present application are shown in the diagrams, rather than being drawn according to the number, shape, and size of the components in actual implementation. The form, quantity, and proportion of each component in actual implementation can be arbitrarily changed, and the layout form of its components may also be more complex.

[0025] In the following description, a large number of details are explored to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0026] Please refer to Figure 1 , which is a flowchart of a method for displaying the lineage of industrial data shown in an exemplary embodiment of the present application. As Figure 1 shown, in an exemplary embodiment, the method for displaying the lineage of industrial data at least includes steps S110 to S140, which are introduced in detail as follows:

[0027] Step S110: Obtain metadata of different types regarding industrial data in the industrial production process. The types of metadata include collected data, processed data, and application data. The processed data is obtained by processing the collected data, and the application data is obtained from applications that use the collected data and / or the processed data.

[0028] In an embodiment of the present application, industrial data is time-series data that changes continuously over time. Among them, the collected data includes device data, gateway data, and measurement point data. Device data is the metadata of data collection devices installed in the industrial site or production environment. The devices can be sensors, instruments, data acquisition cards, etc. The device data at least includes information such as the ID (identifier), name, type, installation location, and device status of the device; Gateway data comes from the metadata of the gateway. The gateway is used to aggregate, convert, and transmit the data collected by multiple devices. The gateway data at least includes information such as the ID, name, type, gateway status, and data forwarding rules of the gateway; Measurement point data is the metadata at the measurement points that need to be monitored or measured during the actual industrial production process. The measurement points are associated with the data collection devices and serve as the source and identifier of the data collected by the data collection devices. Each measurement point corresponds to a specific physical quantity or state (such as temperature, pressure, flow rate, etc.). The measurement point data at least includes information such as the ID, name, type, measurement range, accuracy, and collection frequency of the measurement point.

[0029] In an embodiment of the present application, the processed data is the metadata obtained by processing the metadata of the device. The processed data includes aggregated point data and task point data. The aggregated point data is the meta-information of the aggregated point positions. An aggregated point position is formed by merging multiple measurement points to perform downsampling or aggregation processing on the data corresponding to the measurement points, reducing the data volume and improving the processing efficiency. The aggregated point data at least includes information such as the ID, name, aggregation rule (such as calculating the average value, maximum value, minimum value, etc. over a period of time), and time window of the aggregated point position; Task point data is the metadata of the task points that need to perform specific operations or checks during the data processing. It at least includes information such as the ID, name, and task description of the task point. The task point depends on the data of the measurement point and / or aggregated point as input. In addition, the processed data also includes the rule operation information of multiple measurement points, which at least includes operation rules, measurement points participating in the operation, operation results, etc. The processed data also includes the real-time stream calculation task information during the data processing, which is used to perform complex calculation tasks based on real-time data. These tasks may involve data filtering, aggregation, pattern recognition, etc., and at least include information such as task name, task description, input data source, processing logic, and output result. In addition, based on the rule operation information and real-time stream calculation task information, the mapping relationship between the measurement points, aggregated point positions, and task points can be mined, which is crucial for understanding the data flow path.

[0030] In an embodiment of the present application, the application data is the metadata of the application. The application can be tools such as industrial reports and industrial dashboards for displaying industrial data, and can display the data obtained from the measurement points, aggregated point positions, and task points. Its metadata at least includes information such as application ID, name, type, and data source.

[0031] Step S120: Construct lineage nodes corresponding to each type of metadata.

[0032] Specifically, convert different types of metadata respectively according to a predefined data structure, determine the general information and extended information of each metadata. The general information includes a unique identifier, a name, and a type, and the extended information is custom information. Construct lineage nodes of the same metadata according to the general information and the extended information. Each lineage node has a unique identifier.

[0033] In an embodiment of the present application, the defined data structure includes at least general information and extended information. Taking device data as an example, the general information of device data includes the identifier, name, and type of the device, and the extended information of the device may include the installation location, device status, etc. In this way, the general information of the metadata includes a unique identifier and a type. Through the identifier, the corresponding metadata can be quickly located, avoiding data duplication and confusion. Through the type, the metadata can be quickly classified and summarized. Moreover, converting different types of metadata into a unified standard improves the flexibility and efficiency of subsequent data processing. In addition, use the identifier and type of the metadata as the unique identifier of the lineage node. Each lineage node is mapped to the metadata with the same identifier. For example, a device node with an identifier of 1 is mapped to the device data, and so on. If there are multiple lineage nodes with the same identifier, they are distinguished by type. In this way, through the identifier and type of the metadata, it is helpful to quickly construct lineage nodes. When problems occur in industrial data, the metadata related to the root cause of the problem can also be quickly located through the lineage nodes, greatly improving the efficiency of data retrieval and processing.

[0034] Step S130: Determine the lineage relationship between different lineage nodes according to the dependency relationship between the collected data, processed data, and applied data. The dependency relationship is used to represent the flow path between various types of metadata.

[0035] In an embodiment of the present application, obtain the data flow path and data flow rule between different types of metadata; perform parsing according to the data flow path and data flow rule to determine the dependency relationship between the collected data, processed data, and applied data.

[0036] In an embodiment of the present application, the data flow path and data flow rules cover the flow and conversion relationships among various types of metadata involved in the entire process of industrial data from collection to application. It not only includes the flow path and conversion rules among measurement point data, aggregation point data, and task point data extracted from the rule operation information and real-time stream calculation task information in the processing data, but also includes the flow path and conversion rules among device data, measurement point data, and gateway data, as well as the flow path and conversion rules between measurement point data, aggregation point data, task point data and application data respectively. According to the data flow path and data flow rules, the dependency relationships among the collected data, processed data, and application data obtained by parsing are divided into indirect dependency relationships and direct dependency relationships, that is, a certain piece of metadata indirectly or directly depends on another piece or multiple pieces of metadata.

[0037] Specifically, each lineage node is divided to determine the lineage nodes of each type. The types of lineage nodes include device nodes, gateway nodes, measurement point nodes, aggregation nodes, task nodes, and application nodes; the lineage relationships between different types of lineage nodes are constructed according to the first dependency relationship, the second dependency relationship, and the third dependency relationship. Among them, the first dependency relationship is used to determine the dependency relationship among device nodes, gateway nodes, and measurement point nodes, the second dependency relationship is used to determine the dependency relationship among measurement point nodes, aggregation nodes, and task nodes, and the third dependency relationship is used to determine the dependency relationship between each of the measurement point nodes, aggregation nodes, task nodes and application nodes.

[0038] Please refer to Figure 2 , which is a schematic diagram of a lineage relationship shown in an exemplary embodiment of the present application. As Figure 2 shown, the types of lineage nodes involved in the lineage relationship include device nodes (Device), gateway nodes (Gateway), measurement point nodes (MeasurePoint), aggregation nodes (AggregatePoint), task nodes (TaskPoint), and application nodes (App), and the level of the lineage relationship is 6. Figure 2Root in it represents the start of the blood relationship nodes. The levels where device nodes are located include Device1, Device2, Device3, and Device4. The levels where gateway nodes are located include Gateway1 and Gateway2. The levels where measurement point nodes are located include MeasurePoint1, MeasurePoint2, MeasurePoint3, and MeasurePoint4. The levels where aggregation nodes are located include AggregatePoint1 and AggregatePoint2. The levels where task nodes are located include TaskPoint1 and TaskPoint2. The levels where application nodes are located include App1, App2, App3, and App4. Among them, there is a direct dependency relationship between the blood relationship nodes connected by adjacent levels, and there is an indirect dependency relationship between the blood relationship nodes connected by one level apart.

[0039] In an embodiment of the present application, the blood relationship at least includes the identifiers and types owned by the blood relationship nodes at the starting point of the blood relationship, the identifiers and types owned by the blood relationship nodes flowing from the starting point, and the extended information related to the connection of these blood relationship nodes, that is, custom information.

[0040] By the above method, constructing blood relationship nodes and blood relationships corresponding to different types of metadata can clearly determine the source (such as device data) and flow of metadata, making it easier to discover and solve data quality problems. At the same time, the classification of blood relationship nodes also helps in tracing industrial data. When problems occur in industrial data, it can quickly locate the problem, and the efficiency of problem troubleshooting is high.

[0041] Step S140, constructing a blood relationship graph based on the blood relationship nodes and blood relationships to complete the blood relationship display of industrial data.

[0042] Specifically, each blood relationship node is defined as a graph node of the blood relationship graph, and the blood relationship between each blood relationship node is defined as an edge of the blood relationship graph; constructing a blood relationship graph based on the graph nodes and edges, and the blood relationship graph is a directed acyclic graph.

[0043] In an embodiment of the present application, add_node (a method or function used to add a new node to a graph in a graph data structure or related algorithm library) can be used to add graph nodes and edges to construct a directed acyclic graph of industrial data blood relationship. As Figure 3 shown, it is an example of a directed acyclic graph.

[0044] In an embodiment of the present application, the database storing blood relationship nodes and blood relationships is monitored; if a change event of a blood relationship node or blood relationship is monitored, then in response to the change event, the blood relationship graph is synchronously updated, and the change events include addition, modification, and deletion.

[0045] In an embodiment of the present application, listening for change events and synchronously updating the lineage graph can promptly reflect changes in the lineage relationship, ensuring the accuracy and timeliness of the lineage graph and facilitating expansion.

[0046] Each lineage node and lineage relationship are stored in a database in the form of tables, and the database is an optional relational database. To implement listening for the two tables storing lineage nodes and lineage relationships in the database, triggers can be set for the two tables. When data in each table changes, the triggers will capture these change events. Additionally, the CDC function provided by the database (such as binlog in MySQL, Change Data Capture in Oracle, etc.) can be used to capture data changes and convert them into events, or through methods such as polling and differential detection, event sourcing, etc. The specific implementation method of listening is not limited here.

[0047] Specifically, any lineage node is specified as the starting node; based on the starting node, the lineage graph is traversed to achieve lineage tracing for the starting node, and the traversal results are visually displayed.

[0048] In an embodiment of the present application, since the lineage graph is an acyclic graph, breadth-first traversal (BFS) can be used for traversal. Each lineage node (i.e., graph node) has a unique identifier, which is the identifier carried by the corresponding industrial data. First, an empty queue is created, and the starting node is added to the queue. At this time, the starting node is at the front end of the queue. The starting node is taken out from the front end of the queue as the current node, and each child node of the current node (i.e., the graph node that has a direct connection with and points to the current node) is added to the end of the queue. It is judged whether the current node has been visited through the identifier. If the current node has been visited, the current node is skipped. If the current node has not been visited, it is marked as visited, and a path is constructed to record the node; then, continue to take out the graph node from the front end of the queue as the current node and repeat the above steps until the queue is empty and all graph nodes have been visited, obtaining the paths from the starting node to each graph node. In this way, for each visited graph node, it can be analyzed which other graph nodes it may affect or which other graph nodes may affect it. Therefore, visualizing the traversal results can display each lineage node and the lineage relationships between them.

[0049] Please refer to Figure 3 for the block diagram of the lineage display system of industrial data shown in an exemplary embodiment of the present application. As Figure 3As shown in the figure, in an exemplary embodiment, the industrial data lineage display system at least includes an industrial data acquisition module 310, an encoding and translation module 320, a lineage relationship determination module 330, and a lineage display module, which are introduced in detail as follows:

[0050] The industrial data acquisition module 310 is used to obtain metadata of different types regarding industrial data during the industrial production process. The types of metadata include acquisition data, processed data, and application data. The processed data is obtained by processing the acquisition data, and the application data is obtained from applications that use the acquisition data and / or the processed data;

[0051] The lineage node construction module 320 is used to construct lineage nodes corresponding to each type of metadata;

[0052] The lineage relationship determination module 330 is used to determine the lineage relationships between different lineage nodes according to the dependency relationships among the acquisition data, processed data, and application data. The dependency relationships are used to represent the flow paths among various types of metadata;

[0053] The lineage display module 340 is used to construct a lineage relationship graph based on the lineage nodes and the lineage relationships to complete the display of the industrial data lineage.

[0054] It should be noted that the industrial data lineage display system provided in the above embodiment and the industrial data lineage display method provided in the above embodiment belong to the same concept. The content of the operations performed by each module has been described in detail in the method embodiment, and will not be repeated here.

[0055] The industrial data lineage display method and system provided in this application have the following advantages: By obtaining various types of metadata regarding industrial data during the industrial production process, that is, the acquisition data, processed data, and application data generated from the data acquisition of industrial field devices to the data application process, then constructing lineage nodes corresponding to each type of industrial data, and determining the lineage relationships between different lineage nodes, and constructing a lineage relationship graph based on the lineage nodes and the lineage relationships to complete the display of the industrial data lineage. In this way, through the lineage relationship graph, the industrial data lineage can be traced comprehensively and accurately. That is to say, during the use of industrial data, if there is data abnormality, the root cause of the abnormality can be quickly and accurately traced through the lineage relationship graph, and it can be traced from the business system of the application data to the acquisition gateway, industrial equipment, etc., reducing the difficulty and cost of troubleshooting, which is of great significance for improving the efficiency and level of industrial intelligent manufacturing.

[0056] This application also provides an electronic device, including: a processor, a memory, and a communication bus; the communication bus is used to connect the processor and the memory; the processor is used to execute the computer program stored in the memory to implement the industrial data lineage display method as in the above embodiment.

[0057] Please refer to Figure 4 , which shows a schematic structural diagram of a computer system of an electronic device suitable for implementing the embodiments of the present application. It should be noted that Figure 4 the shown computer system 400 of the electronic device is only an example, and should not impose any limitation on the functions and usage scope of the embodiments of the present application.

[0058] As Figure 4 shown, the computer system 400 includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 402 or the program loaded from the storage section 408 into the random access memory (RAM) 403, such as executing the method in the above embodiments. In the RAM 403, various programs and data required for system operation are also stored. The CPU 401, ROM 402, and RAM 403 are connected to each other via a bus 404. The input / output (I / O) interface 405 is also connected to the bus 404.

[0059] The following components are connected to the I / O interface 405: an input section 406 including a keyboard, a mouse, etc.; an output section 407 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN (Local Area NetworK) card, a modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 409 as required. A removable medium 411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 410 as required, so that the computer program read from it can be installed into the storage section 408 as required.

[0060] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication part 409, and / or installed from the removable medium 411. When the computer program is executed by the central processing unit (CPU) 401, various functions defined in the system of the present application are executed.

[0061] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor of the computer, the computer is caused to execute the method for configuring a rule engine for early warning as described above. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist alone without being assembled into the electronic device.

[0062] It should be noted that the computer-readable medium shown in the embodiments of the present application may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. The computer-readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable computer program. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium, and the computer-readable medium may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The computer program included on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0063] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Among them, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code, and the above-mentioned module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order from that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, as well as the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0064] The units described in the embodiments of the present application can be implemented in software or in hardware, and the described units can also be provided in a processor. Among them, the names of these units do not, in some cases, constitute a limitation on the unit itself.

[0065] The above embodiments are only used to exemplarily illustrate the principles and effects of the present application, rather than to limit the present application. Any person familiar with this technology can modify or change the above embodiments without departing from the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by those of ordinary skill in the art within the technical field without departing from the spirit and technical idea disclosed in the present application should still be covered by the claims of the present application.

Claims

1. A method for displaying the lineage of industrial data, characterized in that: The method comprises: Acquire different types of metadata about industrial data in an industrial production process, where the types of metadata include collected data, processed data, and application data, where the processed data is obtained by processing the collected data, and the application data is obtained from an application that uses the collected data and / or the processed data; Constructing a lineage node corresponding to each type of metadata; Determine the blood relationship between different blood nodes according to the dependency relationship between the collected data, the processed data and the application data, wherein the dependency relationship is used to characterize the flow path between the metadata of each type; A blood relationship graph is constructed based on the blood relationship nodes and the blood relationship to complete the blood relationship display of the industrial data.

2. The method for displaying the lineage of industrial data according to claim 1, characterized in that: The step of constructing the bloodline node corresponding to each type of metadata includes: Converting the metadata of different types according to a predefined data structure respectively, and determining general information and extended information of each metadata, wherein the general information includes a unique identifier, a name and a type, and the extended information is user-defined information; A lineage node of the same metadata is constructed according to the general information and the extended information, and the lineage node has a unique identifier.

3. The method for displaying the lineage of industrial data according to claim 1, characterized in that: Before determining the blood relationship between different blood nodes, the method further includes: Obtaining data flow paths and data flow rules between metadata of different types; Parsing is performed according to the data flow path and the data flow rules to determine the dependency relationship between the collected data, the processed data and the application data, wherein the collected data includes device data, gateway data, and measurement point data, and the processed data includes aggregation point data and task point data.

4. The method for displaying the lineage of industrial data according to claim 3 is characterized in that: The dependency relationship includes a first dependency relationship, a second dependency relationship and a third dependency relationship; The determining of the blood relationship between different blood nodes includes: Divide each of the lineage nodes to determine the lineage nodes of each type, where the types of the lineage nodes include device nodes, gateway nodes, measurement point nodes, aggregation nodes, task nodes, and application nodes; The blood relationship between different types of blood nodes is constructed according to the first dependency, the second dependency and the third dependency, wherein the first dependency is used to determine the dependency between device nodes, gateway nodes and measuring point nodes, the second dependency is used to determine the dependency between measuring point nodes, aggregation nodes and task nodes, and the third dependency is used to determine the dependency between measuring point nodes, aggregation nodes, task nodes and the application nodes.

5. The method for displaying the lineage of industrial data according to claim 1, characterized in that: The step of constructing a blood relationship graph based on the blood relationship nodes and the blood relationship comprises: Each of the bloodline nodes is defined as a graph node of the bloodline relationship graph, and the bloodline relationship between the bloodline nodes is defined as an edge of the bloodline relationship graph; The blood relationship graph is constructed based on the graph nodes and the edges, and the blood relationship graph is a directed acyclic graph.

6. The method for displaying the lineage of industrial data according to any one of claims 1 to 4, characterized in that: After constructing the blood relationship graph based on the blood relationship nodes and the blood relationship, the method further includes: Monitoring a database storing the bloodline nodes and the bloodline relationships; If a change event of the bloodline node or the bloodline relationship is monitored, the bloodline relationship graph is synchronously updated in response to the change event, and the change event includes addition, modification and deletion.

7. The method for displaying the lineage of industrial data according to any one of claims 1 to 4, characterized in that: After constructing the blood relationship graph based on the blood relationship nodes and the blood relationship, the method further includes: Designate any of the bloodline nodes as a starting node; The blood relationship graph is traversed based on the starting node to achieve blood relationship tracing of the starting node, and the traversal results are visualized.

8. A lineage display system for industrial data, characterized in that: The system comprises: An industrial data acquisition module is used to acquire different types of metadata about industrial data in an industrial production process, wherein the types of metadata include acquired data, processed data, and application data. The processed data is obtained by processing the acquired data, and the application data is obtained from an application that uses the acquired data and / or the processed data. A lineage node construction module, used to construct a lineage node corresponding to each type of metadata; A blood relationship determination module, used to determine the blood relationship between different blood relationship nodes according to the dependency relationship between the collected data, the processed data and the application data, wherein the dependency relationship is used to characterize the flow path between the metadata of each type; A lineage display module is used to construct a lineage relationship diagram based on the lineage nodes and the lineage relationships to complete the lineage display of the industrial data.

9. An electronic device, characterized in that: include: processor, memory, and communications bus; The communication bus is used to connect the processor and the memory; The processor is configured to execute the computer program stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is used to make a computer execute the method according to any one of claims 1 to 7.

Images