Event tracking system and method based on industrial field message bus

Abstract

The invention provides an event tracking system and method based on an industrial field message bus, and relates to the technical field of production process control, and the system comprises a message bus configuration module, an event management module, a data asset binding module, an OT algorithm engine module, an event resume module, a delay module and an event publishing module. The method is applied to real-time data management, tracking and analysis of an industrial site, and based on unified data asset management, tracking events generated based on industrial real-time data and data preprocessing based on the events are communicated.

Description

Technical Field

[0001] The present invention relates to the technical field of production process control, and in particular to an event tracking system and method based on an industrial field message bus. Background Art

[0002] Industrial production often has a relatively complex process path. In the entire process path, there are generally several important process processes that need to be focused on, such as hot rolling steel biting and steel throwing in steel production. These important industrial processes are called "events", and the most commonly used in steel production is "material tracking events". The generation of "material tracking events" is closely related to production operations and requires complex and accurate production signal tracking to generate. After the event is generated, it needs to be pushed to several process processing programs and data analysis tools in real time to make real-time judgments on the steady state of production, and to issue alarm information in a timely manner or adjust process parameters in real time. Therefore, the real-time, accuracy, reliability, and ease of use of the event tracking process are very important.

[0003] Existing technologies related to event tracking include, for example, the invention patent with publication number CN103995849A, which discloses an event tracking method and system suitable for public opinion information processing. The method includes obtaining documents related to the event; determining the number of stages of the event based on the number of documents obtained; and clustering the obtained documents based on the similarity of the content to obtain document clusters corresponding to each stage of the event, wherein the total number of document clusters is the same as the number of stages of the event.

[0004] The existing conventional event system in the steel industry belongs to the underlying collection system. The existing event flow logic is limited to L1 layer related applications, with deep logic coupling and single functions. It is difficult to hot update and expand event types and event processing logic. There is no unified organization page for event types, and it is difficult for external applications to follow up production progress in real time through events.

[0005] At the same time, the existing industrial field event bus applications developed based on ICE have the following defects: the event logic is deeply coupled with the ICE application, and the subsequent event callback processing logic requires additional code development and deployment, with high development thresholds and deployment difficulties, and insufficient real-time performance. For users who have no experience in PLC project development, it is difficult to carry out secondary development based on the existing event system. Summary of the invention

[0006] In view of the defects in the prior art, the present invention provides an event tracking system and method based on an industrial field message bus.

[0007] According to an event tracking system and method based on an industrial field message bus provided by the present invention, the scheme is as follows:

[0008] In a first aspect, the present invention provides an event tracking system based on an industrial field message bus, the message bus configuration module, the event management module, the data asset binding module, the OT algorithm engine module, the event publishing module and the delay module;

[0009] Among them, the message bus configuration module: connects the event component to the message bus of the industrial site and configures the message bus. After the configuration is completed, the consumer of the event component starts and monitors the events generated on the bus and connects to the event management module;

[0010] Event management module: screens and filters events sent on the bus, parses event content, classifies and manages events, and enters the data asset binding module or OT algorithm engine module;

[0011] Data asset binding module: bind data assets to preheat data through the interface or import and export functions;

[0012] OT algorithm engine module: Through interface operation or import and export functions, bind the data preprocessing rules and rule triggering events of the OT algorithm engine to perform rule calculations. If the rules need to generate related events, they are synchronously sent to the message bus through the event publishing module;

[0013] Event publishing module: It publishes events to the configured message bus and provides corresponding external microservices.

[0014] Delay module: Based on the delayed task pool of the time wheel structure, the time accuracy is configured to meet the user's needs for delayed execution of warm-up operations and rule execution operations of data assets bound to the event when the event is triggered.

[0015] Preferably, the system further comprises: an event history module: recording the name of the event, the triggering time, and the execution of the rules bound to the event after each event is triggered, for analysis of abnormality analysis;

[0016] This module can analyze the triggering history of events through the event history query page. With the filtering and sorting functions, users can quantitatively analyze the triggering frequency and triggering results of a single event.

[0017] Preferably, the event history module is also provided with a timing and quantitative clearing logic to delete the history before a certain period and the history exceeding the quantity limit.

[0018] Preferably, in the message bus configuration module, the message bus selects a commonly used message bus middleware that has been deployed in industrial projects; and uses a unified event format to shield the processing logic of different message middleware from secondary developers.

[0019] Preferably, the events in the event management module are divided into trigger events and periodic events;

[0020] The trigger event needs to configure the event content template, and after receiving the corresponding event in the message bus, the event content is parsed according to the template;

[0021] The periodic event needs to configure the trigger period. After the configuration is completed, a timed task is added to the timed task framework used by the component to trigger the event regularly and execute the subsequent work triggered by the event.

[0022] Preferably, in the data asset binding module, when a data preheating event is triggered, a data preheating operation is performed on all data assets bound under the event, specifically including:

[0023] Parameter configuration module: configure query parameters. When binding data assets of real-time data sources, you need to select the time range for data preheating. When data preheating is triggered, the data within the time range is found and stored in the cache.

[0024] When binding relational databases, time series databases, and microservice data sources, you need to configure query parameters. When subsequent events are triggered, the query parameters required in the query conditions of the data assets are taken out from the data preheating event and transmitted to the data preheating component in the data asset binding module.

[0025] Time configuration module: configure the delay time. For data assets that need to be preheated after a delay, configure the delay time on the interface.

[0026] Query cache module: When an event is triggered, the event component completes the query event range of the real-time data source and passes the event parameters to the data preheating component. After the data preheating component generates complete query conditions based on the event parameters, it implements the query and cache of the preheated data through the data source module.

[0027] Preferably, the OT algorithm engine module includes: being able to select a delay time for rule execution when binding rules, and utilizing a delay module to adapt to scenarios where delayed execution of event-bound rules is required.

[0028] Preferably, in the delay module, when a user binds data assets and rules under an event, the user can configure the delay time of the corresponding assets and rules:

[0029] When an event is triggered, the backend queries the cache for the data assets and rule information bound to the event;

[0030] For data assets, the real-time data source needs to calculate and replace the query parameter timestamp. After completing the parameter processing, all data assets and rules are grouped according to the delay time, and the corresponding tasks are generated.

[0031] Data preheating and rule execution tasks are placed in the corresponding time grid according to the logic of the time wheel and the delay time. After waiting for the predetermined delay time, the task will be awakened by the advancement pointer of the time wheel and execute the specific preheating and execution logic within the task.

[0032] Preferably, a data preprocessing component is set in the event publishing module, and a microservice is published through the event component, and the relevant states including feature extraction completion and alarm generated during the rule execution are published to the bus in the form of events, forming a loop;

[0033] After calculating the feature value, feature extraction writes the feature value into the corresponding data asset using the primary key as the key for data archiving or as input for other rules.

[0034] In a second aspect, the present invention further provides an event tracking method based on an industrial field message bus, the method comprising:

[0035] Step S1: The underlying L1 control system or other system publishes events to the message bus;

[0036] Step S2: the event tracking system configures the event bus to be connected through the message bus configuration module and connects to the corresponding message bus;

[0037] Step S3: configuring the subject to be monitored and the events to be processed under the corresponding monitored subject in the event management module;

[0038] Step S4: configure the data assets that need to be preheated when the event is triggered through the data asset binding module;

[0039] Step S5: configuring the OT algorithm engine rules that need to be triggered and executed when the event is triggered through the OT algorithm engine module;

[0040] Step S6: The message queue consumer of the message bus configuration module pulls the events on the message bus, filters the events that need attention according to the configuration in the event management module, and generates subsequent processing tasks according to the configuration information, and publishes them to the delay module;

[0041] Step S7: Delay the task according to the delay time configured for each task through the delay module, and submit the task to the corresponding component when the set time arrives; for the configured data assets, process the query conditions during data asset preheating according to the parameters in the event, generate data asset preheating tasks, and submit them to the data preheating component; for the bound OT algorithm engine rules, generate corresponding rule execution tasks and submit them to the rule engine;

[0042] Step S8: The needs of other components to publish events are published to the message bus connected to the message bus configuration module through the event publishing module.

[0043] Compared with the prior art, the present invention has the following beneficial effects:

[0044] 1. Through the standardized event structure designed by the present invention, event producers and consumers can use the message bus to transmit events of unified structure, and use the event tracking system with easy-to-use interface and standardized and unified to complete the subsequent event analysis and event post-processing, which greatly reduces the development workload and difficulty of event senders and receivers, realizes the hierarchical management of production line-theme-category of events, and provides help for the classification management of hundreds of events in a specific industrial site;

[0045] 2. The event tracking system involved in the present invention provides a complete set of event management and history tracing functions. Through the application of the present invention, event types can be predefined, production events can be configured, and event classification management can be performed as needed. Hundreds of events on an edge node can be classified into different categories, which is convenient for vertical management and control of the project;

[0046] 3. The present invention can query the transmission and execution history of all events through the history tracing function. By tracing back the history, it is relatively convenient to view the timing information and abnormal information of event triggering and subsequent tasks, which is convenient for on-site problem location;

[0047] 4. The present invention provides a unified event management page based on the relevant characteristics of the underlying events. It summarizes on-site events through three levels: production line-topic-event, which is convenient for application personnel to organize, query, and revise related events, and provides a channel for connecting subsequent functional modules, overcoming the problems of difficult event organization and difficult function connection, and achieving good results in the subsequent data governance process.

[0048] Other beneficial effects of the present invention will be explained in the specific implementation manner through the introduction of specific technical features and technical solutions. Through the introduction of these technical features and technical solutions, those skilled in the art should be able to understand the beneficial technical effects brought about by the technical features and technical solutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0050] Figure 1 This is a schematic diagram of the entire process of event triggering;

[0051] Figure 2 Schematic diagram of the data preheating process;

[0052] Figure 3 It is a schematic diagram of the time wheel algorithm;

[0053] Figure 4A schematic diagram of the execution thread pool. DETAILED DESCRIPTION

[0054] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0055] The embodiment of the present invention provides an event tracking system based on an industrial field message bus. The event tracking system is connected to the industrial field message bus through the message bus configuration module. The event management module screens and filters the events sent on the bus, parses the event content, and generates corresponding subsequent processing tasks, including but not limited to docking with the data asset module to preheat the data of the data assets bound to the event; docking with the OT algorithm engine module to perform corresponding rule calculations. If the rules need to generate related events, they are synchronously sent to the message bus through the event publishing module. The process is recorded through the event history module to ensure traceability. The delay module is used to control the delayed execution of subsequent tasks of event docking, and can achieve interleaved execution of related logic.

[0056] Reference Figure 1 As shown, the system includes: a message bus configuration module, an event management module, a data asset binding module, an OT algorithm engine module, an event history module, a delay module and an event publishing module.

[0057] Message bus configuration module: The present invention is compatible with commonly used message buses in industrial sites, such as Apache Kafka, RabbitMQ, etc. The event component is connected to the message bus in the industrial site through the message bus configuration module to realize real-time monitoring and message publishing. The message bus selects the commonly used message bus middleware that has been deployed in the industrial project (Apache Kafka is taken as an example in this article, and the application can select other message middleware, such as Rabbit MQ, etc., according to application requirements and site conditions). Using a unified event format, the processing logic of different message middleware is shielded from secondary developers, simplifying the development workload.

[0058] After the message bus is configured, the consumer of the event component will be started, listen to the events generated on the bus, and connect to the event management module.

[0059] Event management module: defines the hierarchical classification logic of production line-topic (-classification), and the application can classify and manage events according to the actual situation on site. Through the event management module, users can manage on-site events according to different production line numbers and event topic classifications. Users only need to customize production lines and event topics, and newly added and deleted event topics will be automatically updated to the event consumer's listening topic configuration, without manual operation.

[0060] Events are divided into trigger events and periodic events. Trigger events require the configuration of event content templates, and after receiving the corresponding events in the message bus, the event content is parsed according to the template (the events described in this article use the steel coil number as the primary key). Periodic events require the configuration of the trigger cycle. After the configuration is completed, a scheduled task will be added to the scheduled task framework used by the component to trigger the event regularly and execute the subsequent work of the event triggering.

[0061] In addition to the message bus channel, the event triggering also provides a REST-style microservice interface, and users can trigger events at any time according to the application scenario. The event management module provides complete import and export functions, allowing users to easily migrate events and binding relationships configured in the environment.

[0062] Data asset binding module: In order to improve the efficiency of data preprocessing rule execution, it is necessary to preload data for event-triggered rules, which is called "data preheating". Data preheating preloads the data of the data assets corresponding to the rules into the cache according to the predefined query conditions. When the rules are subsequently executed, the values ​​are directly read from the cache, which greatly improves the efficiency of reading values. The event module provides management and execution functions for data assets and data preheating events.

[0063] The data asset binding module in the event module can realize the binding of data assets and data preheating events through the interface or through the import and export functions. When the data preheating event is triggered, the data preheating operation will be performed on all data assets bound to the event.

[0064] 1) Configure query parameters. When binding data assets of real-time data sources, you need to select the time range for data preheating. When data preheating is triggered, the data within the time range will be found and stored in the cache. When binding relational databases, time series databases, and microservice data sources, you need to configure query parameters. When subsequent event management is triggered, the event module will extract the query parameters required in the query conditions of the data assets from the data preheating event and transmit them to the data preheating component.

[0065] 2) Configure the delay time. For data assets that require delayed preheating, the delay time can be configured on the interface.

[0066] 3) When an event is triggered, the event component completes the query event range of the real-time data source and passes the event parameters to the data preheating component. After the data preheating component generates complete query conditions based on the event parameters, it implements the query and cache of preheated data through the data asset module. Figure 2 shown.

[0067] Data asset module: data asset configuration, management, and data flow module, which stores all data asset information managed in the platform. The event module connects to the data asset module through the data asset binding module. When the data is preheated, the query conditions and data asset list of the time are passed in to perform data query and archiving functions of the data assets.

[0068] OT algorithm engine module: Through interface operations, you can also use the import and export functions to bind OT algorithm engine rules to rule triggering events. When an OT algorithm engine rule event is triggered, the OT algorithm engine module will be connected to execute all OT algorithm engine rules bound to the event.

[0069] When an event is triggered, the parameters attached to the event will be passed to the OT algorithm engine module to obtain the main information such as the steel coil number, pass number and other accompanying information of the current event. The parameters passed by the event can also be used as input parameters of the OT algorithm engine rules.

[0070] When binding rules, you can also select the delay time for rule execution. Use the delay module to adapt to scenarios where you need to delay the execution of event-bound rules.

[0071] OT algorithm engine module: It has hundreds of operators related to data analysis, calculation, feature extraction, operation, process analysis, etc., and provides a data analysis tool module with a graphical editor. The data analysis, feature extraction, alarm detection and other related rules generated by the OT algorithm engine module need to be driven by the event system for calculation.

[0072] Event history module: The event history module will record the event name, trigger time, and execution status of the rules bound to the event after each event is triggered, which will be used for abnormal analysis. Through the event history query page, the trigger history of the event is analyzed. With the filtering and sorting functions, users can quantitatively analyze the trigger frequency and trigger results of a single event. In order to save space, the event history table has a partitioning function, and is set with timed and quantitative clearing logic. The history partitions before a certain period will be deleted, and the deletion will not affect the history writing and query of the new partition.

[0073] Delay module: The delay module is based on the delay task pool of the time wheel structure implemented by itself, refer to Figure 3As shown, the time precision is configurable to meet the needs of users to delay the warm-up operation and rule execution operation of the data assets bound to the event when the event is triggered. When users bind data assets and rules under an event, they can configure the delay time of the corresponding assets and rules.

[0074] (1) When an event is triggered, the backend will query the cache for the data assets and rule information bound to the event.

[0075] (2) For data assets, the real-time data source needs to calculate and replace the query parameter timestamp. After completing the parameter processing, all data assets and rules will be grouped according to the delay time and generate corresponding tasks.

[0076] (3) Data preheating and rule execution tasks will be placed in the corresponding time grid according to the logic of the time wheel and the delay time. After waiting for the predetermined delay time, the task will be "woken up" by the advancement pointer of the time wheel and execute the specific preheating and execution logic in the task. Figure 4 shown.

[0077] Event publishing module: The event publishing module provides the function of publishing events to the configured message bus and provides corresponding external microservices. The OT algorithm engine module publishes microservices through event components, and publishes the feature extraction completion, alarm and other states generated during the execution of the calculation rules to the bus in the form of events, forming a loop. After calculating the feature value, the calculation rules of the OT algorithm engine module will also use the primary key (currently the steel coil number) as the key to write the feature value into the corresponding data asset for data archiving or as input for other rules.

[0078] Implementation principle:

[0079] The event tracking system is connected to the industrial field message bus through the message bus configuration module. After successfully connecting to the message bus, configure the topics that need to be monitored and the trigger events that need to be processed under the topics in the event management module. The event tracking system will consume and parse the event information in the corresponding topics, and filter the events registered in the event management system. Configure periodic events and corresponding trigger periods in the event management module. This step will register the corresponding timed triggers in the platform. In the data asset binding module, bind the data assets that need to be preheated with the events, and in the OT algorithm engine module, bind the OT algorithm engine rules that need to be triggered with the events. During the execution of the OT algorithm engine rules, events or alarms may be generated, which are published through the event publishing module.

[0080] The present invention also provides an event tracking method based on an industrial field message bus, referring to Figure 1 As shown, the method includes:

[0081] Step S1: The underlying L1 control system or other system publishes events to the message bus;

[0082] Step S2: the event tracking system configures the event bus to be connected through the message bus configuration module and connects to the corresponding message bus;

[0083] Step S3: configuring the subject to be monitored and the events to be processed under the corresponding monitored subject in the event management module;

[0084] Step S4: configure the data assets that need to be preheated when the event is triggered through the data asset binding module;

[0085] Step S5: configuring the OT algorithm engine rules that need to be triggered and executed when the event is triggered through the OT algorithm engine module;

[0086] Step S6: The message queue consumer of the message bus configuration module pulls the events on the message bus, filters the events that need attention according to the configuration in the event management module, and generates subsequent processing tasks according to the configuration information, and publishes them to the delay module;

[0087] Step S7: Delay the task according to the delay time configured for each task through the delay module, and submit the task to the corresponding component when the set time arrives; for the configured data assets, process the query conditions during data asset preheating according to the parameters in the event, generate data asset preheating tasks, and submit them to the data preheating component; for the bound OT algorithm engine rules, generate corresponding rule execution tasks and submit them to the rule engine;

[0088] Step S8: The needs of other components to publish events are published to the message bus connected to the message bus configuration module through the event publishing module.

[0089] Specifically, after the event tracking system is connected to the industrial field message bus, the topics that need to be monitored and the trigger events that need to be processed under the topics are configured in the event management module. The event tracking system will consume and parse the event information in the corresponding topics, and filter the events registered in the event management system. Configure periodic events and corresponding trigger periods in the event management module. This step will register the corresponding timing triggers in the platform and generate periodic events according to the set time. After capturing a specific event, the event management module parses the event and generates subsequent tasks. In the data asset binding module, for each registered event, it can be bound to the data asset that needs to be preheated when the event is triggered. If there is a need for delayed preheating, the delay time can be configured at the same time. In the OT algorithm engine module, the modules in the OT algorithm engine can be bound to events. If there is a need for delayed execution of rules, the delay time can also be configured.

[0090] When a specific event is triggered, the event management module first parses the event information, compares it with the event template, and parses the parameters attached to the event. If the event content meets the requirements, the specific tasks bound to the event will be retrieved. For bound data assets, the parameters required for preheating of each data asset will be sorted out, and the data asset preheating task will be submitted directly to the corresponding processing module or to the delay queue according to the delay time set for the asset. For bound rules, the event module packages the parameters attached to the event with the rules, and chooses to submit them directly to the rule engine executor or to the delay queue according to the set delay time.

[0091] When the tasks in the delay queue of the delay module reach the set time, the tasks will be submitted to the corresponding module. The event publishing module also provides a publishing interface. If an event or alarm needs to be published in the OT algorithm engine rules, the content will be published to the message bus through the publishing interface for consumption and processing by the units that subscribe to events and alarms.

[0092] The embodiment of the present invention provides an event tracking system and method based on an industrial field message bus, which is applied to real-time data management, tracking and analysis at industrial sites. Based on unified data asset management, it connects tracking events generated based on industrial real-time data and event-based data preprocessing.

[0093] Those skilled in the art know that, in addition to realizing the system and its various devices, modules, and units provided by the present invention in a purely computer-readable program code, it is entirely possible to realize the same functions in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system and its various devices, modules, and units provided by the present invention can be considered as a hardware component, and the devices, modules, and units included therein for realizing various functions can also be regarded as structures within the hardware component; the devices, modules, and units for realizing various functions can also be regarded as both software modules for realizing the method and structures within the hardware component.

[0094] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. An event tracking system based on industrial field message bus, characterized in that: include: Message bus configuration module, event management module, data asset binding module, OT algorithm engine module, event publishing module and delay module; Among them, the message bus configuration module: connects the event component to the message bus of the industrial site and configures the message bus. After the configuration is completed, the consumer of the event component starts and monitors the events generated on the bus and connects to the event management module; Event management module: screens and filters events sent on the bus, parses event content, classifies and manages events, and enters the data asset binding module or OT algorithm engine module; Data asset binding module: bind data assets to preheat data through the interface or import and export functions; OT algorithm engine module: Through interface operation or import and export functions, bind the data preprocessing rules and rule triggering events of the OT algorithm engine to perform rule calculations. If the rules need to generate related events, they are synchronously sent to the message bus through the event publishing module; Event publishing module: It publishes events to the configured message bus and provides corresponding external microservices. Delay module: A delayed task pool based on a time wheel structure with time accuracy configured to meet the needs of users to delay the preheating and rule execution of data assets bound to an event when an event is triggered.

2. The event tracking system based on industrial field message bus according to claim 1 is characterized in that: The system also includes: an event history module: recording the name of the event, the triggering time, and the execution of the rules bound to the event after each event is triggered, for analysis of abnormalities; This module can analyze the triggering history of events through the event history query page. With the filtering and sorting functions, users can quantitatively analyze the triggering frequency and triggering results of a single event.

3. The event tracking system based on industrial field message bus according to claim 2 is characterized in that: The event record module is also provided with a timing and quantitative clearing logic to delete records before a certain period and records exceeding the quantity limit.

4. The event tracking system based on industrial field message bus according to claim 1, characterized in that: In the message bus configuration module, the message bus selects the commonly used message bus middleware that has been deployed in industrial projects; a unified event format is used to shield the processing logic of different message middleware from secondary developers.

5. The event tracking system based on industrial field message bus according to claim 1, characterized in that: Events in the event management module are divided into trigger events and periodic events; The trigger event needs to configure a template for the event content, and after receiving the corresponding event in the message bus, the event content is parsed according to the template; The periodic event needs to configure the trigger period. After the configuration is completed, a timed task is added to the timed task framework used by the component to trigger the event regularly and execute the subsequent work triggered by the event.

6. The event tracking system based on industrial field message bus according to claim 1, characterized in that: In the data asset binding module, when a data preheating event is triggered, a data preheating operation is performed on all data assets bound under the event, specifically including: Parameter configuration module: configure query parameters. When binding data assets of real-time data sources, you need to select the time range for data preheating. When data preheating is triggered, the data within the time range is found and stored in the cache. When binding relational databases, time series databases, and microservice data sources, you need to configure query parameters. When subsequent events are triggered, the query parameters required in the query conditions of the data assets are taken out from the data preheating event and transmitted to the data preheating component in the data asset binding module. Time configuration module: configure the delay time. For data assets that need to be preheated after a delay, configure the delay time on the interface. Query cache module: When an event is triggered, the event component completes the query event range of the real-time data source and passes the event parameters to the data preheating component. After the data preheating component generates complete query conditions based on the event parameters, it implements the query and cache of the preheated data through the data source module.

7. The event tracking system based on industrial field message bus according to claim 1, characterized in that: The OT algorithm engine module includes: when binding rules, the delay time of rule execution can be selected, and the delay module is used to adapt to the scenario where the rules of event binding need to be delayed.

8. The event tracking system based on industrial field message bus according to claim 1, characterized in that: In the delay module, when users bind data assets and rules under events, they can configure the delay time of the corresponding assets and rules: When an event is triggered, the backend queries the cache for the data assets and rule information bound to the event; For data assets, the real-time data source needs to calculate and replace the query parameter timestamp. After completing the parameter processing, all data assets and rules are grouped according to the delay time, and the corresponding tasks are generated. Data preheating and rule execution tasks are placed in the corresponding time grid according to the logic of the time wheel and the delay time. After waiting for the predetermined delay time, the task will be awakened by the advancement pointer of the time wheel and execute the specific preheating and execution logic within the task.

9. The event tracking system based on industrial field message bus according to claim 1, characterized in that: The event publishing module is provided with a data preprocessing component, and a microservice is published through the event component, and the related states including feature extraction completion and alarm generated during the rule execution are published to the bus in the form of events, forming a loop; After calculating the feature value, feature extraction writes the feature value into the corresponding data asset using the primary key as the key for data archiving or as input for other rules.

10. An event tracking method based on an industrial field message bus, characterized in that: An event tracking system based on an industrial field message bus according to any one of claims 1 to 9, comprising: Step S1: The underlying L1 control system or other system publishes events to the message bus; Step S2: the event tracking system configures the event bus to be connected through the message bus configuration module and connects to the corresponding message bus; Step S3: configuring the subject to be monitored and the events to be processed under the corresponding monitored subject in the event management module; Step S4: configure the data assets that need to be preheated when the event is triggered through the data asset binding module; Step S5: configuring the OT algorithm engine rules that need to be triggered and executed when the event is triggered through the OT algorithm engine module; Step S6: The message queue consumer of the message bus configuration module pulls the events on the message bus, filters the events that need attention according to the configuration in the event management module, and generates subsequent processing tasks according to the configuration information, and publishes them to the delay module; Step S7: Delay the task according to the delay time configured for each task through the delay module, and submit the task to the corresponding component when the set time arrives; for the configured data assets, process the query conditions during data asset preheating according to the parameters in the event, generate data asset preheating tasks, and submit them to the data preheating component; for the bound OT algorithm engine rules, generate corresponding rule execution tasks and submit them to the rule engine; Step S8: The needs of other components to publish events are published to the message bus connected to the message bus configuration module through the event publishing module.

Images