Event occurrence detection method and apparatus, electronic device, and storage medium

Abstract

The present disclosure relates to the technical field of oil refining information processing, and provides an event occurrence detection method and device, electronic equipment and a storage medium. The method comprises the following steps: when a start judgment instruction for a target coking device is detected, a target configuration file corresponding to the start judgment instruction is acquired, wherein the target configuration file comprises current coking tower identification information, a plurality of event judgment information matched with the current coking tower identification information, and a plurality of real-time updated coking variable information matched with each event judgment information; at least one target event generation information is generated based on the plurality of coking variable information and a judgment model corresponding to the event judgment information; and each target event generation information is sent to a target receiving end. Through the above steps, the collection and use efficiency of each delayed coking device for the event occurrence can be greatly improved.

Description

Technical Field

[0001] This disclosure relates to the field of oil refining information processing technology, and in particular to methods, apparatus, electronic devices and storage media for detecting incidents. Background Technology

[0002] Delayed coking units are key processing units in oil refineries for increasing light oil yields and producing petroleum coke. They transform heavy, low-value oil products such as vacuum residue, atmospheric residue, viscous residue, heavy crude oil, heavy fuel oil, and coal tar into high-value liquid and gaseous products through deep thermal cracking reactions, while simultaneously generating petroleum coke. A delayed coking unit includes two delayed coking fractionation towers (referred to as raw coke towers) used to alternately produce petroleum coke. Due to variations in continuous variables such as atmospheric temperature and cooling water temperature, as well as differences in processes and operating habits, the timing of events differs in each delayed coking unit.

[0003] In the existing technology, relevant information about the occurrence of events in each delayed coking unit is collected manually. However, due to the large variety and quantity of data on the occurrence of events, the efficiency of data collection or use is extremely low. Summary of the Invention

[0004] In view of this, the present disclosure provides an event detection method, apparatus, electronic device and storage medium to solve the problem in the prior art that the collection or use efficiency of various data is extremely low due to the large number and variety of event data.

[0005] A first aspect of this disclosure provides an event detection method, comprising:

[0006] When a start judgment command for the target coking device is detected, the target configuration file corresponding to the start judgment command is obtained. The target configuration file includes the current coking tower identification information, multiple event judgment information that match the current coking tower identification information, and multiple real-time updated coking variable information that match each event judgment information.

[0007] Based on multiple focal variable information and the judgment model corresponding to the event judgment information, at least one target event generation information is generated;

[0008] Each target event generates information and sends it to the target receiver.

[0009] In some embodiments, based on multiple focal variable information and a judgment model corresponding to the event judgment information, at least one target event generation information is generated, including:

[0010] Obtain the event judgment identifier information for each event judgment;

[0011] Based on the preset association between event judgment identifier information and judgment model, obtain the judgment model corresponding to each event judgment identifier information;

[0012] Import the multiple generation variables corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one target event generation information.

[0013] In some embodiments, multiple focus variable information corresponding to each event judgment information is imported into a judgment model corresponding to the event judgment model to generate at least one target event generation information, including:

[0014] Import the multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result;

[0015] When each initial event judgment result indicates that it has occurred, target event generation information is generated based on the initial event judgment result, and at least one target event generation information is obtained.

[0016] In some embodiments, after importing the focus variable information from each matched event judgment information into the corresponding judgment model and generating at least one event judgment result, the method further includes:

[0017] When the event judgment result indicates that the event has occurred, obtain the duplicate identification flag of the corresponding event judgment information;

[0018] When the duplicate identification flag indicates that it is enabled, obtain the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time;

[0019] Generate the current event interval based on the current event occurrence time and the previous event occurrence time;

[0020] When the time interval between the current events is not greater than the event time interval threshold, the event judgment result is represented as "not occurred".

[0021] In some embodiments, when a start determination command for the target focusing device is detected, the target configuration file corresponding to the start determination command is obtained, including:

[0022] When a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained;

[0023] Perform a legality check on the original configuration file to obtain the configuration check results;

[0024] When the configuration check result indicates that it is correct, the original configuration file is identified as the target configuration file.

[0025] In some embodiments, the method further includes:

[0026] When the event judgment result corresponding to the preset end event indicates that it has occurred, change the current coking tower identification information.

[0027] A second aspect of this disclosure provides an event detection apparatus, comprising:

[0028] The acquisition module is configured to acquire the corresponding target configuration file when a start judgment command for the target coking device is detected. The target configuration file includes the current coking tower identification information, multiple event judgment information, and multiple real-time updated coking variable information.

[0029] The generation module is configured to generate at least one target event generation information based on the current coking tower identification information, multiple event judgment information, multiple coking variable information, and a preset judgment configuration file. The judgment configuration file includes multiple judgment models, each of which is used to generate the corresponding target event generation information.

[0030] The sending module is configured to send the information generated by each target event to the target receiver.

[0031] In some embodiments, based on multiple focal variable information and a judgment model corresponding to the event judgment information, at least one target event generation information is generated, including:

[0032] Obtain the event judgment identifier information for each event judgment;

[0033] Based on the preset association between event judgment identifier information and judgment model, obtain the judgment model corresponding to each event judgment identifier information;

[0034] Import the multiple generation variables corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one target event generation information.

[0035] In some embodiments, multiple focus variable information corresponding to each event judgment information is imported into a judgment model corresponding to the event judgment model to generate at least one target event generation information, including:

[0036] Import the multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result;

[0037] When each initial event judgment result indicates that it has occurred, target event generation information is generated based on the initial event judgment result, and at least one target event generation information is obtained.

[0038] In some embodiments, after importing the focus variable information from each matched event judgment information into the corresponding judgment model and generating at least one event judgment result, the method further includes:

[0039] The second acquisition module is configured to acquire a duplicate identification identifier of the corresponding event judgment information when the event judgment result indicates that the event has occurred.

[0040] The third acquisition module is configured to acquire the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time when the duplicate identification flag indicates that it has been enabled;

[0041] The second generation module is configured to generate the current event occurrence time interval based on the current event occurrence time and the previous event occurrence time;

[0042] The module is configured to indicate that the event judgment result is "not occurred" when the current event occurrence time interval is not greater than the event occurrence time interval threshold.

[0043] In some embodiments, when a start determination command for the target focusing device is detected, the target configuration file corresponding to the start determination command is obtained, including:

[0044] When a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained;

[0045] Perform a legality check on the original configuration file to obtain the configuration check results;

[0046] When the configuration check result indicates that it is correct, the original configuration file is identified as the target configuration file.

[0047] In some embodiments, the apparatus further includes:

[0048] The module is configured to change the current coking tower identifier information when the event judgment result corresponding to the preset end event indicates that the event has occurred.

[0049] A third aspect of this disclosure provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the steps implemented by the processor when executing the computer program include:

[0050] When a start judgment command for the target coking device is detected, the target configuration file corresponding to the start judgment command is obtained. The target configuration file includes the current coking tower identification information, multiple event judgment information that match the current coking tower identification information, and multiple real-time updated coking variable information that match each event judgment information.

[0051] Based on multiple focal variable information and the judgment model corresponding to the event judgment information, at least one target event generation information is generated;

[0052] Each target event generates information and sends it to the target receiver.

[0053] In some embodiments, based on multiple focal variable information and a judgment model corresponding to the event judgment information, at least one target event generation information is generated, including:

[0054] Obtain the event judgment identifier information for each event judgment;

[0055] Based on the preset association between event judgment identifier information and judgment model, obtain the judgment model corresponding to each event judgment identifier information;

[0056] Import the multiple generation variables corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one target event generation information.

[0057] In some embodiments, multiple focus variable information corresponding to each event judgment information is imported into a judgment model corresponding to the event judgment model to generate at least one target event generation information, including:

[0058] Import the multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result;

[0059] When each initial event judgment result indicates that it has occurred, target event generation information is generated based on the initial event judgment result, and at least one target event generation information is obtained.

[0060] In some embodiments, after importing the focus variable information from each matched event judgment information into the corresponding judgment model and generating at least one event judgment result, the method further includes:

[0061] When the event judgment result indicates that the event has occurred, obtain the duplicate identification flag of the corresponding event judgment information;

[0062] When the duplicate identification flag indicates that it is enabled, obtain the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time;

[0063] Generate the current event interval based on the current event occurrence time and the previous event occurrence time;

[0064] When the time interval between the current events is not greater than the event time interval threshold, the event judgment result is represented as "not occurred".

[0065] In some embodiments, when a start determination command for the target focusing device is detected, the target configuration file corresponding to the start determination command is obtained, including:

[0066] When a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained;

[0067] Perform a legality check on the original configuration file to obtain the configuration check results;

[0068] When the configuration check result indicates that it is correct, the original configuration file is identified as the target configuration file.

[0069] In some embodiments, the method further includes:

[0070] When the event judgment result corresponding to the preset end event indicates that it has occurred, change the current coking tower identification information.

[0071] A fourth aspect of this disclosure provides a computer-readable storage medium storing a computer program, the steps of which, when executed by a processor, include:

[0072] When a start judgment command for the target coking device is detected, the target configuration file corresponding to the start judgment command is obtained. The target configuration file includes the current coking tower identification information, multiple event judgment information that match the current coking tower identification information, and multiple real-time updated coking variable information that match each event judgment information.

[0073] Based on multiple focal variable information and the judgment model corresponding to the event judgment information, at least one target event generation information is generated;

[0074] Each target event generates information and sends it to the target receiver.

[0075] In some embodiments, based on multiple focal variable information and a judgment model corresponding to the event judgment information, at least one target event generation information is generated, including:

[0076] Obtain the event judgment identifier information for each event judgment;

[0077] Based on the preset association between event judgment identifier information and judgment model, obtain the judgment model corresponding to each event judgment identifier information;

[0078] Import the multiple generation variables corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one target event generation information.

[0079] In some embodiments, multiple focus variable information corresponding to each event judgment information is imported into a judgment model corresponding to the event judgment model to generate at least one target event generation information, including:

[0080] Import the multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result;

[0081] When each initial event judgment result indicates that it has occurred, target event generation information is generated based on the initial event judgment result, and at least one target event generation information is obtained.

[0082] In some embodiments, after importing the focus variable information from each matched event judgment information into the corresponding judgment model and generating at least one event judgment result, the method further includes:

[0083] When the event judgment result indicates that the event has occurred, obtain the duplicate identification flag of the corresponding event judgment information;

[0084] When the duplicate identification flag indicates that it is enabled, obtain the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time;

[0085] Generate the current event interval based on the current event occurrence time and the previous event occurrence time;

[0086] When the time interval between the current events is not greater than the event time interval threshold, the event judgment result is represented as "not occurred".

[0087] In some embodiments, when a start determination command for the target focusing device is detected, the target configuration file corresponding to the start determination command is obtained, including:

[0088] When a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained;

[0089] Perform a legality check on the original configuration file to obtain the configuration check results;

[0090] When the configuration check result indicates that it is correct, the original configuration file is identified as the target configuration file.

[0091] In some embodiments, the method further includes:

[0092] When the event judgment result corresponding to the preset end event indicates that it has occurred, change the current coking tower identification information.

[0093] Beneficial effects

[0094] The beneficial effects of the embodiments disclosed herein compared with the prior art include at least the following: by acquiring the current coking tower identification information, multiple event judgment information, and multiple real-time updated coking variable information of the target configuration file corresponding to each delayed coking unit, and generating target event generation information, the efficiency of each delayed coking unit in collecting and using the events that occur can be greatly improved. Attached Figure Description

[0095] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only for this embodiment. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0096] Figure 1 This is a schematic diagram of an application scenario of the event detection method provided according to the embodiments of this disclosure;

[0097] Figure 2 This is a flowchart of a second embodiment of an event detection method provided according to the present disclosure;

[0098] Figure 3 This is a flowchart of a third embodiment of another event detection method provided according to the embodiments of this disclosure;

[0099] Figure 4 This is a simplified structural diagram of an event detection device provided according to an embodiment of the present disclosure;

[0100] Figure 5 This is a schematic diagram of an electronic device provided according to an embodiment of the present disclosure. Detailed Implementation

[0101] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0102] It should also be noted that, for ease of description, only the parts relevant to this disclosure are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0103] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different systems, devices, modules or units, and are not used to limit the order of functions performed by these systems, devices, modules or units or their interdependencies.

[0104] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0105] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0106] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0107] Example 1:

[0108] Figure 1 This is a schematic diagram of an application scenario of the event detection method according to Embodiment 1 of this disclosure.

[0109] exist Figure 1 In application scenarios:

[0110] First, when a start judgment command for the target coking device is detected, the computing device 101 can obtain the target configuration file 102 corresponding to the start judgment command. The target configuration file includes the current coking tower identification information 103, multiple event judgment information 104 matching the current coking tower identification information, and multiple real-time updated coking variable information 105 matching each event judgment information.

[0111] Secondly, the computing device 101 can generate at least one target event generation information 107 based on multiple generation variable information 105 and a judgment model 106 corresponding to the event judgment information 104.

[0112] Finally, the computing device 101 can send the information 107 generated for each target event to the target receiving end.

[0113] It should be noted that the aforementioned computing device 101 can be either hardware or software. When the computing device is hardware, it can be implemented as a distributed cluster consisting of multiple servers or terminal devices, or as a single server or a single terminal device. When the computing device is software, it can be installed within the hardware devices listed above. It can be implemented as, for example, multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are made here.

[0114] It should be understood that Figure 1 The number of computing devices shown is merely illustrative. Any number of computing devices can be used depending on implementation needs.

[0115] Example 2:

[0116] Continue to refer to Figure 2 The diagram illustrates flow 200 of a second embodiment of the event detection method according to this disclosure. This method can be implemented by... Figure 1 The event detection method is executed by the computing device 101. The method includes the following steps:

[0117] Step 201: When a start judgment command for the target coking device is detected, the target configuration file corresponding to the start judgment command is obtained. The target configuration file includes the current coking tower identification information, multiple event judgment information matching the current coking tower identification information, and multiple real-time updated coking variable information matching each event judgment information.

[0118] In some optional implementations, the execution body of the event detection method (such as...) Figure 1 The computing device 101 shown can be connected to the target device via a wired or wireless connection. Then, when a start judgment command for the target coking device is detected, the target configuration file corresponding to the start judgment command is obtained. The target configuration file includes the current coking tower identification information, multiple event judgment information matching the current coking tower identification information, and multiple real-time updated coking variable information matching each event judgment information.

[0119] It should be noted that the aforementioned wireless connection methods may include, but are not limited to, 3G / 4G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other currently known or future wireless connection methods.

[0120] The "Start Judgment Command" can refer to the command used to initiate the event monitoring method. The "Target Configuration File" can refer to an electronic file used to store the relevant tools or methods for determining whether an event has occurred. This configuration file can be an XML file.

[0121] The current coking tower identification information refers to the coking tower where the coking process is currently occurring. Since the delayed coking unit includes two delayed coking fractionation towers (referred to as coking towers) used to alternately produce petroleum coke, events corresponding to different coking towers will occur as the two towers switch. As an example, assuming coking towers A and B, if the current coking tower identification indicates that tower A is running, then the triggering of various events in coking tower B is determined. Conversely, if the current coking tower identification indicates that tower B is running, then the triggering of various events in coking tower A is determined.

[0122] Event judgment information refers to relevant information about processing steps or methods used to determine whether an event has occurred. Event judgment information can include preset ordinary thresholds, interval thresholds, etc. An ordinary threshold can refer to a threshold consisting of a single data point. For example, an ordinary threshold can be 0.5, 1, 15.32, etc., set as needed. An interval threshold can refer to a combination of upper and lower thresholds. For example, an interval threshold can be between 0 and 0.5, where 0 is the lower threshold and 0.5 is the upper threshold; an interval threshold can also be between -13.15 and 688.5, where -13.15 is the lower threshold and 68.5 is the upper threshold. It should be noted that when using interval thresholds, one can determine whether the data is within the interval threshold range (i.e., greater than the lower threshold and less than the upper threshold); or one can determine whether the data is outside the interval threshold range (i.e., less than the lower threshold or greater than the upper threshold). Furthermore, whether the threshold data is used as the basis for judgment when using ordinary and interval thresholds is specified as needed and is not restricted here. As an example, when the standard threshold is 0.5, you can use "greater than 0.5" or "greater than or equal to 0.5" as the judgment condition. The upper and lower thresholds of the interval threshold are similar to those of the fixed threshold.

[0123] Event judgment information may also include a judgment model. A judgment model can refer to using a preset calculation formula to calculate the input event variables and obtain a result used to determine whether an event has occurred.

[0124] Coking variable information refers to the data or related information needed for various events in the coking tower. This information can be automatically acquired through a DCS (Distributed Control System) or manually acquired through the corresponding data acquisition equipment of the coking tower. The coking variable information can be the actual collected data. For example, the coking variable information can be real-time data such as 0.5, 1.55, or 135. The coking variable information can also represent state information. For example, if one of the control valves in the coking tower has three different states, the coking variable information can be 1, 2, and 3 representing the three different states; it can also be state 1, state 2, and state 3; or it can be first case, second case, and third case, set as needed, without specific restrictions here.

[0125] In addition, the focus variable information can include data for a preset number of update cycles. The focus variable information can not only store the most recently updated data, but also store data calculated backward for a preset number of update cycles. The preset number is a positive integer, and its size can be set differently according to different focus variable information, without specific restrictions here. As an example, the focus variable information can include the most recently updated data such as DataA, then the data of its previous cycle can be recorded as DataA[1], and the data of the previous N cycles can be recorded as DataA[N]. The data of each cycle can also be set in other ways, without specific restrictions here.

[0126] The update cycle can refer to the preset duration for updating all focal variable information once. As an example, the update cycle can be 30 seconds, 46 seconds, 1 minute, 1 minute and 30 seconds, or other durations, which can be set as needed, without specific restrictions here.

[0127] Step 202: Based on multiple target variable information and the judgment model corresponding to the event judgment information, generate at least one target event generation information.

[0128] In some optional implementations, the aforementioned execution entity can generate at least one target event generation information based on multiple focus variable information and a judgment model corresponding to the event judgment information.

[0129] A judgment model can refer to a model that uses a pre-defined formula to calculate the input key variable information and obtain a result to determine whether an event has occurred. As an example, a judgment model could be:

[0130] R1 = DataB[1] > DataC && DataB <DataC / 5

[0131] Here, R1 can represent the result, which is Boolean data; DataB and DataC are two different key variables; && can indicate that the conditions on both sides must be met simultaneously.

[0132] As another example, the judgment model can be:

[0133] R2=DataD[1]>DataE&&sinDataD <sin(DataE / )5OR

[0134] R2 = DataD[3] > DataE && DataD <DataE / 5OR

[0135] R2=|DataF[1]-DataF|>|DataG[1]-DataG|&&DataF <DataG / 10OR

[0136] R2 = DataF[3] > DataG && DataF <DataG / 10

[0137] In this context, R2 represents the result, which is Boolean data. DataD, DataE, DataF, and DataG are four different key variables. && indicates that both expressions must be satisfied simultaneously, while OR indicates that only one condition needs to be satisfied.

[0138] It should be noted that the calculation methods for the judgment model can include: arithmetic operations, absolute value, exponentiation, logarithms (natural logarithm, common logarithm), trigonometric functions (sine, cosine, tangent, cotangent), power functions, hyperbolic functions (hyperbolic sine, hyperbolic cosine, hyperbolic tangent, hyperbolic cotangent), random number generation, logical functions (AND, OR, XOR, XNOR, conditional assignment), statistical functions (maximum and minimum values, median, mean, standard deviation), etc., which can be set as needed, and no specific restrictions are made here.

[0139] In some preferred implementations, the judgment model can be set in the above configuration file, which makes the running speed faster and increases the running speed of this disclosure.

[0140] In some preferred implementations, the decision model can also be set outside the configuration file. For example, multiple decision models can be set in a single model file, so that each event decision information in different configurations uses the corresponding decision model in the aforementioned model file. This setting allows the decision model to be free from being hardcoded into the configuration file, forming a usage pattern similar to object-oriented programming. It enables event decision information with the same decision conditions to correspond to the same model file, reducing the amount of code written, thereby reducing the number of code errors, and also increasing the practicality and security of this disclosure.

[0141] In actual operation, configuration files typically need to be written to the DCS system, which is usually installed in multiple locations on the coking tower, making the installation process quite complex. Model files, however, can be set in any other location and can be connected for data calculation. Therefore, setting the judgment model outside the configuration file allows changes to event judgment information to be made only by modifying the model file, without needing to modify the configuration file itself. This eliminates the need to retrieve, modify, and reinstall the configuration file, significantly reducing the workload and greatly increasing the practicality of this disclosure.

[0142] The target event generation information refers to the information generated based on the judgment result of whether an event has occurred. When the event has been judged to have occurred, information indicating that the event has occurred can be generated. Conversely, when the event has been judged not to have occurred, information indicating that the event has not occurred can be generated. As an example, when the event has been judged to have occurred, the target event generation information can be set to 1; when the event has not occurred, the target event generation information can be set to 0. As another example, when the event has been judged to have occurred, the target event generation information can be set to "true"; when the event has not occurred, the target event generation information can be set to "false". The settings can be configured as needed, without specific restrictions.

[0143] Step 203: Send the information generated for each target event to the target receiver.

[0144] In some alternative implementations, the aforementioned executing entity may send the information generated by each target event to the target receiving end.

[0145] The target receiving end can refer to the end used to display the target event generation information, or it can refer to the end used to import the target event generation information into preset processing steps and obtain new results.

[0146] As an example, the target receiver can have target event data corresponding to the target event generation information, and this target event data can be a positive integer. When the target event generation information indicates that an event has occurred, the target event data can be incremented by 1.

[0147] As another example, the target receiver can also store each recorded piece of information indicating that an event has occurred as a data entry in the database. The way the target receiver uses the information generated by the target event is configured as needed, and no specific restrictions are imposed here.

[0148] The beneficial effects of one of the above-described embodiments of this disclosure include at least the following: by acquiring the current coking tower identification information, multiple event judgment information, and multiple real-time updated coking variable information of the target configuration file corresponding to each delayed coking unit, and generating target event generation information, the efficiency of each delayed coking unit in collecting and using the events that occur can be greatly improved.

[0149] Example 3:

[0150] Continue to refer to Figure 3 The flowchart 300 of a third embodiment of the event detection method according to the present disclosure is shown. This method can be performed by... Figure 1 The event detection method is executed by the computing device 101.

[0151] Step 301: When a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained.

[0152] The original configuration file includes the current coking tower identification information, multiple event judgment information matching the current coking tower identification information, and multiple real-time updated coking variable information matching each event judgment information.

[0153] In some optional implementations, the execution body of the event detection method (such as...) Figure 1 The computing device 101 shown can be connected to the target device via a wired or wireless connection. Then, when a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained. The original configuration file includes the current coking tower identification information, multiple event judgment information matching the current coking tower identification information, and multiple real-time updated coking variable information matching each event judgment information.

[0154] It should be noted that the aforementioned wireless connection methods may include, but are not limited to, 3G / 4G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other currently known or future wireless connection methods.

[0155] The "start judgment command" can refer to the command used to initiate the event monitoring method. The "original configuration file" can refer to the electronic file used to store the relevant tools or methods for determining whether an event has occurred. This configuration file can be an XML file.

[0156] The current coking tower identification information refers to the coking tower where the coking process is currently occurring. Since the delayed coking unit includes two delayed coking fractionation towers (referred to as coking towers) used to alternately produce petroleum coke, events corresponding to different coking towers will occur as the two towers switch. As an example, assuming coking towers A and B, if the current coking tower identification indicates that tower A is running, then the triggering of various events in coking tower B is determined. Conversely, if the current coking tower identification indicates that tower B is running, then the triggering of various events in coking tower A is determined.

[0157] Event judgment information refers to relevant information about processing steps or methods used to determine whether an event has occurred. Event judgment information can include preset ordinary thresholds, interval thresholds, etc. An ordinary threshold can refer to a threshold consisting of a single data point. For example, an ordinary threshold can be 0.5, 1, 15.32, etc., set as needed. An interval threshold can refer to a combination of upper and lower thresholds. For example, an interval threshold can be between 0 and 0.5, where 0 is the lower threshold and 0.5 is the upper threshold; an interval threshold can also be between -13.15 and 688.5, where -13.15 is the lower threshold and 68.5 is the upper threshold. It should be noted that when using interval thresholds, one can determine whether the data is within the interval threshold range (i.e., greater than the lower threshold and less than the upper threshold); or one can determine whether the data is outside the interval threshold range (i.e., less than the lower threshold or greater than the upper threshold). Furthermore, whether the threshold data is used as the basis for judgment when using ordinary and interval thresholds is specified as needed and is not restricted here. As an example, when the standard threshold is 0.5, you can use "greater than 0.5" or "greater than or equal to 0.5" as the judgment condition. The upper and lower thresholds of the interval threshold are similar to those of the fixed threshold.

[0158] Event judgment information may also include a judgment model. A judgment model can refer to using a preset calculation formula to calculate the input event variables and obtain a result used to determine whether an event has occurred.

[0159] Coking variable information refers to the data or related information needed for various events in the coking tower. This information can be automatically acquired through a DCS (Distributed Control System) or manually acquired through the corresponding data acquisition equipment of the coking tower. The coking variable information can be the actual collected data. For example, the coking variable information can be real-time data such as 0.5, 1.55, or 135. The coking variable information can also represent state information. For example, if one of the control valves in the coking tower has three different states, the coking variable information can be 1, 2, and 3 representing the three different states; it can also be state 1, state 2, and state 3; or it can be first case, second case, and third case, set as needed, without specific restrictions here.

[0160] In addition, the focus variable information can include data for a preset number of update cycles. The focus variable information can not only store the most recently updated data, but also store data calculated backward for a preset number of update cycles. The preset number is a positive integer, and its size can be set differently according to different focus variable information, without specific restrictions here. As an example, the focus variable information can include the most recently updated data such as DataA, then the data of its previous cycle can be recorded as DataA[1], and the data of the previous N cycles can be recorded as DataA[N]. The data of each cycle can also be set in other ways, without specific restrictions here.

[0161] The update cycle can refer to the preset duration for updating all focal variable information once. As an example, the update cycle can be 30 seconds, 46 seconds, 1 minute, 1 minute and 30 seconds, or other durations, which can be set as needed, without specific restrictions here.

[0162] Step 302: Perform a validity check on the original configuration file to obtain the configuration check results.

[0163] In some optional implementations, the aforementioned execution entity can perform a validity check on the original configuration file and obtain the configuration check result.

[0164] Legality checks may include, but are not limited to, checking one of the following: checking whether the thresholds in the original configuration file are accurate (such as whether the ordinary threshold data is correct, whether the interval threshold data is correct, and whether the upper and lower limit thresholds conform to the corresponding relationship, etc.), checking whether the correlation between the event judgment information and the judgment model is correct, or checking whether the data source of the coking variable information is accurate, etc. These are not listed one by one, but the variables or judgment rules used for coking tower event judgment are all within the scope of the check.

[0165] The validity check result can refer to the corresponding result of the validity check. The validity check result can indicate "correct" or "incorrect". As an example, the validity check can be "yes" and "no", or "1" and "0", or "Y" and "N", whichever needs to be set, without specific restrictions here.

[0166] Step 303: When the configuration check result indicates that it is correct, the original configuration file is determined as the target configuration file.

[0167] In some alternative implementations, when the configuration check result indicates that the configuration file is correct, the aforementioned execution entity can identify the original configuration file as the target configuration file.

[0168] Step 304: Obtain the event judgment identifier information for each event judgment information.

[0169] In some optional implementations, the aforementioned execution entity may obtain event judgment identifier information for each event judgment information.

[0170] Event judgment identifier information can refer to identifier information associated with the judgment model. Event judgment identifier information can be any one or more combinations of Chinese characters, English letters, numbers, symbols, and symbols from other languages, and can be set as needed without specific restrictions.

[0171] Step 305: Based on the preset association between event judgment identifier information and judgment model, obtain the judgment model corresponding to each event judgment identifier information.

[0172] In some optional implementations, the aforementioned execution entity can obtain the judgment model corresponding to each event judgment identifier based on the preset association between event judgment identifier information and judgment model.

[0173] A judgment model can refer to a model that uses a pre-defined formula to calculate the input key variable information and obtain a result to determine whether an event has occurred. As an example, a judgment model could be:

[0174] R1 = DataB[1] > DataC && DataB <DataC / 5

[0175] Here, R1 can represent the result, which is Boolean data; DataB and DataC are two different key variables; && can indicate that the conditions on both sides must be met simultaneously.

[0176] As another example, the judgment model can be:

[0177] R2=DataD[1]>DataE&&sinDataD <sin(DataE / )5OR

[0178] R2 = DataD[3] > DataE && DataD <DataE / 5OR

[0179] R2=|DataF[1]-DataF|>|DataG[1]-DataG|&&DataF <DataG / 10OR

[0180] R2 = DataF[3] > DataG && DataF <DataG / 10

[0181] In this context, R2 represents the result, which is Boolean data. DataD, DataE, DataF, and DataG are four different key variables. && indicates that both expressions must be satisfied simultaneously, while OR indicates that only one condition needs to be satisfied.

[0182] It should be noted that the calculation methods for the judgment model can include: arithmetic operations, absolute value, exponentiation, logarithms (natural logarithm, common logarithm), trigonometric functions (sine, cosine, tangent, cotangent), power functions, hyperbolic functions (hyperbolic sine, hyperbolic cosine, hyperbolic tangent, hyperbolic cotangent), random number generation, logical functions (AND, OR, XOR, XNOR, conditional assignment), statistical functions (maximum and minimum values, median, mean, standard deviation), etc., which can be set as needed, and no specific restrictions are made here.

[0183] In some preferred implementations, the judgment model can be set in the above configuration file, which makes the running speed faster and increases the running speed of this disclosure.

[0184] In some preferred implementations, the judgment model can also be set outside the configuration file. For example, multiple judgment models can be set in a single model file, so that each event judgment information in different configurations uses the corresponding judgment model in the aforementioned model file. This setting allows the judgment model to be free from being hardcoded into the configuration file, forming an object-oriented usage pattern; it also allows event judgment information with the same judgment conditions to correspond to the same model file, reducing the amount of code writing, thereby reducing the number of code errors, and increasing the practicality and security of this disclosure.

[0185] In actual operation, configuration files typically need to be written to the DCS system, which is usually installed in multiple locations on the coking tower, making the installation process quite complex. Model files, however, can be set in any other location and can be connected for data calculation. Therefore, setting the judgment model outside the configuration file allows changes to event judgment information to be made only by modifying the model file, without needing to modify the configuration file itself. This eliminates the need to retrieve, modify, and reinstall the configuration file, significantly reducing the workload and greatly increasing the practicality of this disclosure.

[0186] The target event generation information refers to the information generated based on the judgment result of whether an event has occurred. When the event has been judged to have occurred, information indicating that the event has occurred can be generated. Conversely, when the event has been judged not to have occurred, information indicating that the event has not occurred can be generated. As an example, when the event has been judged to have occurred, the target event generation information can be set to 1; when the event has not occurred, the target event generation information can be set to 0. As another example, when the event has been judged to have occurred, the target event generation information can be set to "true"; when the event has not occurred, the target event generation information can be set to "false". The settings can be configured as needed, without specific restrictions.

[0187] Step 306: Import the multiple dynamic variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result.

[0188] In some optional implementations, the aforementioned execution entity can import multiple key variable information corresponding to each event judgment information into a judgment model corresponding to the event judgment model to generate at least one initial event judgment result.

[0189] Step 307: When the initial event judgment result indicates that the event has occurred, the corresponding event judgment information is checked repeatedly to update the initial event judgment result.

[0190] In some optional implementations, when the initial event judgment result indicates that an event has occurred, the aforementioned execution entity can perform repeated checks on the corresponding event judgment information and update the initial event judgment result through the following steps:

[0191] Step 1: Obtain the duplicate identification identifier for the corresponding event judgment information.

[0192] Duplicate identification markers can refer to markers used to identify whether an event needs to be verified repeatedly within a short period of time.

[0193] Step 2: When the duplicate identification flag indicates that it is enabled, obtain the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time.

[0194] The time interval threshold refers to the time limit value corresponding to each event judgment information. The current event occurrence time refers to the time that occurred, as indicated by the judgment result of the current event judgment information. The previous event occurrence time refers to the time that occurred, as indicated by the judgment result of the previous event judgment information.

[0195] Step 3: Generate the current event time interval based on the current event occurrence time and the previous event occurrence time.

[0196] The current event time interval can refer to the time difference between the current event occurrence and the previous event occurrence.

[0197] Step 4: When the time interval between the current events is not greater than the event time interval threshold, the initial event judgment result is represented as "not occurred".

[0198] Step 5: When the time interval between the current events is greater than the event time interval threshold, the initial event judgment result is marked as "occurred".

[0199] Step 308: When each initial event judgment result indicates that it has occurred, target event generation information is generated based on the initial event judgment result, and at least one target event generation information is obtained.

[0200] In some optional implementations, when each initial event judgment result indicates that an event has occurred, the aforementioned execution entity can generate target event generation information based on the initial event judgment result, thereby obtaining at least one target event generation information.

[0201] Step 309: Send the information generated for each target event to the target receiver.

[0202] In some alternative implementations, the aforementioned executing entity may send the information generated by each target event to the target receiving end.

[0203] The target receiving end can refer to the end used to display the target event generation information, or it can refer to the end used to import the target event generation information into preset processing steps and obtain new results.

[0204] As an example, the target receiver can have target event data corresponding to the target event generation information, and this target event data can be a positive integer. When the target event generation information indicates that an event has occurred, the target event data can be incremented by 1.

[0205] As another example, the target receiver can also store each recorded piece of information indicating that an event has occurred as a data entry in the database. The way the target receiver uses the information generated by the target event is configured as needed, and no specific restrictions are imposed here.

[0206] Step 310: When the event judgment result corresponding to the preset end event indicates that it has occurred, change the current coking tower identification information.

[0207] In some optional implementations, when the event judgment result corresponding to the preset end event indicates that it has occurred, the aforementioned execution entity can change the current coking tower identification information.

[0208] The termination event can refer to the last one or several events of a preset monitoring tower. Since the time interval between the last few events is small, each termination event can be represented as a termination event. When the event judgment result corresponding to the preset termination event indicates that it has occurred, the current tower identifier information can be changed, and the detection of event information corresponding to another tower can begin.

[0209] All of the above-mentioned optional technical solutions can be combined in any way to form the optional implementation methods of this application, and will not be described in detail here.

[0210] Example 4:

[0211] The following are embodiments of the apparatus disclosed herein, which can be used to execute embodiments of the method disclosed herein. For details not disclosed in the apparatus embodiments of this disclosure, please refer to the embodiments of the method disclosed herein.

[0212] Further reference Figure 4 As an implementation of the above figures and methods, this disclosure provides an embodiment of an event detection device. This device embodiment is similar to... Figure 2 This corresponds to the second embodiment described above.

[0213] like Figure 4 As shown, the event detection device 400 of this embodiment includes:

[0214] The acquisition module 401 is configured to acquire the corresponding target configuration file when a start judgment command for the target coking device is detected. The target configuration file includes the current coking tower identification information, multiple event judgment information, and multiple real-time updated coking variable information.

[0215] The generation module 402 is configured to generate at least one target event generation information based on the current coking tower identification information, multiple event judgment information, multiple coking variable information, and a preset judgment configuration file. The judgment configuration file includes multiple judgment models, each of which is used to generate the corresponding target event generation information.

[0216] The sending module 403 is configured to send the information generated by each target event to the target receiver.

[0217] In some preferred implementations, at least one target event generation information is generated based on multiple focus variable information and a judgment model corresponding to the event judgment information, including:

[0218] Obtain the event judgment identifier information for each event judgment;

[0219] Based on the preset association between event judgment identifier information and judgment model, obtain the judgment model corresponding to each event judgment identifier information;

[0220] Import the multiple generation variables corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one target event generation information.

[0221] In some preferred implementations, multiple focus variables corresponding to each event judgment information are imported into a judgment model corresponding to the event judgment model to generate at least one target event generation information, including:

[0222] Import the multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result;

[0223] When each initial event judgment result indicates that it has occurred, target event generation information is generated based on the initial event judgment result, and at least one target event generation information is obtained.

[0224] In some preferred implementations, after importing multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result, the method further includes:

[0225] The second acquisition module is configured to acquire a duplicate identification identifier of the corresponding event judgment information when the event judgment result indicates that the event has occurred.

[0226] The third acquisition module is configured to acquire the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time when the duplicate identification flag indicates that it has been enabled;

[0227] The second generation module is configured to generate the current event occurrence time interval based on the current event occurrence time and the previous event occurrence time;

[0228] The module is configured to indicate that the event judgment result is "not occurred" when the current event occurrence time interval is not greater than the event occurrence time interval threshold.

[0229] In some preferred implementations, when a start judgment command for the target focusing device is detected, the target configuration file corresponding to the start judgment command is obtained, including:

[0230] When a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained;

[0231] Perform a legality check on the original configuration file to obtain the configuration check results;

[0232] When the configuration check result indicates that it is correct, the original configuration file is identified as the target configuration file.

[0233] In some preferred implementations, the event detection device further includes:

[0234] The module is configured to change the current coking tower identifier information when the event judgment result corresponding to the preset end event indicates that the event has occurred.

[0235] The beneficial effects of one of the above-described embodiments of this disclosure include at least the following: by acquiring the current coking tower identification information, multiple event judgment information, and multiple real-time updated coking variable information of the target configuration file corresponding to each delayed coking unit, and generating target event generation information, the efficiency of each delayed coking unit in collecting and using the events that occur can be greatly improved.

[0236] It is understandable that the modules described in the device 400 are similar to those in the reference. Figure 2 The steps in the described method correspond accordingly. Therefore, the operations, features, and beneficial effects described above for the method also apply to device 400 and the modules contained therein, and will not be repeated here.

[0237] Example 5:

[0238] like Figure 5 As shown, the electronic device 500 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the electronic device 500. The processing unit 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0239] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 5 Each box shown can represent a device or multiple devices as needed.

[0240] Specifically, according to this embodiment, the process described in the above-mentioned flowchart can be implemented as a computer software program. For example, this embodiment includes a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. In this embodiment, the computer program can be downloaded and installed from a network via communication device 509, or installed from storage device 508, or installed from ROM 502. When the computer program is executed by processing device 501, the following steps can be performed:

[0241] When a start judgment command for the target coking device is detected, the target configuration file corresponding to the start judgment command is obtained. The target configuration file includes the current coking tower identification information, multiple event judgment information that match the current coking tower identification information, and multiple real-time updated coking variable information that match each event judgment information.

[0242] Based on multiple focal variable information and the judgment model corresponding to the event judgment information, at least one target event generation information is generated;

[0243] Each target event generates information and sends it to the target receiver.

[0244] In some optional implementations, at least one target event generation information is generated based on multiple focus variable information and a judgment model corresponding to the event judgment information, including:

[0245] Obtain the event judgment identifier information for each event judgment;

[0246] Based on the preset association between event judgment identifier information and judgment model, obtain the judgment model corresponding to each event judgment identifier information;

[0247] Import the multiple generation variables corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one target event generation information.

[0248] In some optional implementations, multiple generation variable information corresponding to each event judgment information is imported into a judgment model corresponding to the event judgment model to generate at least one target event generation information, including:

[0249] Import the multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result;

[0250] When each initial event judgment result indicates that it has occurred, target event generation information is generated based on the initial event judgment result, and at least one target event generation information is obtained.

[0251] In some optional implementations, after importing the focus variable information from each matched event judgment information into the corresponding judgment model and generating at least one event judgment result, the following is also included:

[0252] When the event judgment result indicates that the event has occurred, obtain the duplicate identification flag of the corresponding event judgment information;

[0253] When the duplicate identification flag indicates that it is enabled, obtain the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time;

[0254] Generate the current event interval based on the current event occurrence time and the previous event occurrence time;

[0255] When the time interval between the current events is not greater than the event time interval threshold, the event judgment result is represented as "not occurred".

[0256] In some optional implementations, when a start judgment command for the target focusing device is detected, the target configuration file corresponding to the start judgment command is obtained, including:

[0257] When a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained;

[0258] Perform a legality check on the original configuration file to obtain the configuration check results;

[0259] When the configuration check result indicates that it is correct, the original configuration file is identified as the target configuration file.

[0260] It should be noted that the computer-readable medium described above in this embodiment can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this embodiment, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this embodiment, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0261] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0262] The aforementioned computer-readable medium may be included in the aforementioned device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to perform the following steps:

[0263] When a start judgment command for the target coking device is detected, the target configuration file corresponding to the start judgment command is obtained. The target configuration file includes the current coking tower identification information, multiple event judgment information that match the current coking tower identification information, and multiple real-time updated coking variable information that match each event judgment information.

[0264] Based on multiple focal variable information and the judgment model corresponding to the event judgment information, at least one target event generation information is generated;

[0265] Each target event generates information and sends it to the target receiver.

[0266] In some optional implementations, at least one target event generation information is generated based on multiple focus variable information and a judgment model corresponding to the event judgment information, including:

[0267] Obtain the event judgment identifier information for each event judgment;

[0268] Based on the preset association between event judgment identifier information and judgment model, obtain the judgment model corresponding to each event judgment identifier information;

[0269] Import the multiple generation variables corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one target event generation information.

[0270] In some optional implementations, multiple generation variable information corresponding to each event judgment information is imported into a judgment model corresponding to the event judgment model to generate at least one target event generation information, including:

[0271] Import the multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result;

[0272] When each initial event judgment result indicates that it has occurred, target event generation information is generated based on the initial event judgment result, and at least one target event generation information is obtained.

[0273] In some optional implementations, after importing the focus variable information from each matched event judgment information into the corresponding judgment model and generating at least one event judgment result, the following is also included:

[0274] When the event judgment result indicates that the event has occurred, obtain the duplicate identification flag of the corresponding event judgment information;

[0275] When the duplicate identification flag indicates that it is enabled, obtain the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time;

[0276] Generate the current event interval based on the current event occurrence time and the previous event occurrence time;

[0277] When the time interval between the current events is not greater than the event time interval threshold, the event judgment result is represented as "not occurred".

[0278] In some optional implementations, when a start judgment command for the target focusing device is detected, the target configuration file corresponding to the start judgment command is obtained, including:

[0279] When a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained;

[0280] Perform a legality check on the original configuration file to obtain the configuration check results;

[0281] When the configuration check result indicates that it is correct, the original configuration file is identified as the target configuration file.

[0282] Computer program code for performing the operations of this embodiment can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—and conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0283] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0284] The modules described in this embodiment can be implemented in software or hardware. The described modules can also be located in a processor, for example, they can be described as:

[0285] The acquisition module is configured to acquire the corresponding target configuration file when a start judgment command for the target coking device is detected. The target configuration file includes the current coking tower identification information, multiple event judgment information, and multiple real-time updated coking variable information.

[0286] The generation module is configured to generate at least one target event generation information based on the current coking tower identification information, multiple event judgment information, multiple coking variable information, and a preset judgment configuration file. The judgment configuration file includes multiple judgment models, each of which is used to generate the corresponding target event generation information.

[0287] The sending module is configured to send the information generated by each target event to the target receiver.

[0288] In some preferred implementations, at least one target event generation information is generated based on multiple focus variable information and a judgment model corresponding to the event judgment information, including:

[0289] Obtain the event judgment identifier information for each event judgment;

[0290] Based on the preset association between event judgment identifier information and judgment model, obtain the judgment model corresponding to each event judgment identifier information;

[0291] Import the multiple generation variables corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one target event generation information.

[0292] In some preferred implementations, multiple focus variables corresponding to each event judgment information are imported into a judgment model corresponding to the event judgment model to generate at least one target event generation information, including:

[0293] Import the multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result;

[0294] When each initial event judgment result indicates that it has occurred, target event generation information is generated based on the initial event judgment result, and at least one target event generation information is obtained.

[0295] In some preferred implementations, after importing multiple critical variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment model to generate at least one initial event judgment result, the method further includes:

[0296] The second acquisition module is configured to acquire a duplicate identification identifier of the corresponding event judgment information when the event judgment result indicates that the event has occurred.

[0297] The third acquisition module is configured to acquire the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time when the duplicate identification flag indicates that it has been enabled;

[0298] The second generation module is configured to generate the current event occurrence time interval based on the current event occurrence time and the previous event occurrence time;

[0299] The module is configured to indicate that the event judgment result is "not occurred" when the current event occurrence time interval is not greater than the event occurrence time interval threshold.

[0300] In some preferred implementations, when a start judgment command for the target focusing device is detected, the target configuration file corresponding to the start judgment command is obtained, including:

[0301] When a start judgment command for the target coking device is detected, the original configuration file corresponding to the start judgment command is obtained;

[0302] Perform a legality check on the original configuration file to obtain the configuration check results;

[0303] When the configuration check result indicates that it is correct, the original configuration file is identified as the target configuration file.

[0304] In some preferred implementations, the event detection device further includes:

[0305] The module is configured to change the current coking tower identifier information when the event judgment result corresponding to the preset end event indicates that the event has occurred.

[0306] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0307] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. An event detection method, characterized in that, Applied to computer equipment, including: When a start judgment command for the target coking device is detected, the target configuration file corresponding to the start judgment command is obtained. The target configuration file is an XML file. The target configuration file includes the current coking tower identification information, multiple event judgment information matching the current coking tower identification information, and multiple real-time updated coking variable information matching each event judgment information. The coking variable information is the data needed in each event of the coking tower. The coking variable information includes current data collected from DCS according to a preset update cycle and data from at least one historical cycle. Based on the multiple coking variable information and the judgment model corresponding to the event judgment information, at least one target event generation information is generated, wherein the judgment model is a pre-configured executable calculation logic used to calculate the input coking variable information to determine whether a process event has occurred. Send the information generated for each target event to the target receiving end; The step of generating at least one target event generation information based on the multiple focal variable information and the judgment model corresponding to the event judgment information includes: obtaining event judgment identifier information for each event judgment information; obtaining a judgment model corresponding to each event judgment identifier information according to a preset association relationship between the event judgment identifier information and the judgment model; importing multiple focal variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment identifier information to generate at least one initial event judgment result; when the initial event judgment result indicates that it has occurred, obtaining a duplicate identification identifier for the corresponding event judgment information; when the duplicate identification identifier indicates that it has been enabled, obtaining the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time; generating the current event occurrence time interval based on the current event occurrence time and the previous event occurrence time; when the current event occurrence time interval is not greater than the event occurrence time interval threshold, indicating that the initial event judgment result has not occurred; when each initial event judgment result indicates that it has occurred, generating target event generation information based on the initial event judgment result to obtain the at least one target event generation information. When a start judgment command for the target coking device is detected, the step of acquiring the target configuration file corresponding to the start judgment command includes: when a start judgment command for the target coking device is detected, acquiring the original configuration file corresponding to the start judgment command; performing a validity check on the original configuration file to obtain a configuration check result; and when the configuration check result indicates that it is correct, determining the original configuration file as the target configuration file. The legality check includes: checking whether the thresholds in the original configuration file are accurate, checking whether the correlation between the event judgment information and the judgment model is correct, and checking whether the data source of the focus variable information is accurate.

2. The method according to claim 1, characterized in that, The method further includes: When the event judgment result corresponding to the preset end event indicates that it has occurred, the current coking tower identification information is changed.

3. An event information detection device, characterized in that, Applied to computer equipment, including: The acquisition module is configured to acquire the corresponding target configuration file when a start judgment command for the target coking device is detected. The target configuration file includes the current coking tower identification information, multiple event judgment information, and multiple real-time updated coking variable information. The coking variable information is the data required in each event of the coking tower. The coking variable information includes current data collected from DCS according to a preset update cycle and data from at least one historical cycle. The generation module is configured to generate at least one target event generation information based on the current coking tower identification information, the multiple event judgment information, the multiple coking variable information, and a preset judgment configuration file. The judgment configuration file includes multiple judgment models, each of which is used to generate the corresponding target event generation information. The judgment model is a pre-configured executable calculation logic used to calculate the input coking variable information to determine whether a process event has occurred. The sending module is configured to send each target event generation information to the target receiving end; The step of generating at least one target event generation information based on the multiple focal variable information and the judgment model corresponding to the event judgment information includes: obtaining event judgment identifier information for each event judgment information; obtaining a judgment model corresponding to each event judgment identifier information according to a preset association relationship between the event judgment identifier information and the judgment model; importing multiple focal variable information corresponding to each event judgment information into the judgment model corresponding to the event judgment identifier information to generate at least one initial event judgment result; when the initial event judgment result indicates that it has occurred, obtaining a duplicate identification identifier for the corresponding event judgment information; when the duplicate identification identifier indicates that it has been enabled, obtaining the corresponding event occurrence time interval threshold, the current event occurrence time, and the previous event occurrence time; generating the current event occurrence time interval based on the current event occurrence time and the previous event occurrence time; when the current event occurrence time interval is not greater than the event occurrence time interval threshold, indicating that the initial event judgment result has not occurred; when each initial event judgment result indicates that it has occurred, generating target event generation information based on the initial event judgment result to obtain the at least one target event generation information. When a start judgment command for the target coking device is detected, the step of acquiring the target configuration file corresponding to the start judgment command includes: when a start judgment command for the target coking device is detected, acquiring the original configuration file corresponding to the start judgment command; performing a validity check on the original configuration file to obtain a configuration check result; and when the configuration check result indicates that it is correct, determining the original configuration file as the target configuration file. The legality check includes: checking whether the thresholds in the original configuration file are accurate, checking whether the correlation between the event judgment information and the judgment model is correct, and checking whether the data source of the focus variable information is accurate.

4. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in claim 1 or 2.

5. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in claim 1 or 2.

Images