CN116796931A - Asynchronous nested rule time sequence triggering method and system - Google Patents
Asynchronous nested rule time sequence triggering method and system Download PDFInfo
- Publication number
- CN116796931A CN116796931A CN202311085906.3A CN202311085906A CN116796931A CN 116796931 A CN116796931 A CN 116796931A CN 202311085906 A CN202311085906 A CN 202311085906A CN 116796931 A CN116796931 A CN 116796931A
- Authority
- CN
- China
- Prior art keywords
- rule
- processing container
- data
- rules
- post
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000006243 chemical reaction Methods 0.000 claims description 15
- 230000008569 process Effects 0.000 claims description 15
- 238000013500 data storage Methods 0.000 claims description 5
- 238000007781 pre-processing Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 238000000638 solvent extraction Methods 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/06—Electricity, gas or water supply
Abstract
The invention provides an asynchronous nested rule time sequence triggering method and system, comprising the following steps: obtaining a configuration file according to a service demand configuration rule; dividing rules in the configuration file into common rules and nested rules; the nesting rule is divided into an independent common rule, a preposed rule and a postposed rule; loading the common rules and the independent common rules into a common rule processing container; loading the pre-rules into a pre-rules processing container; loading the post rule into a post rule processing container; inputting the source data into a common rule processing container, and determining whether the trigger condition of the rule is met; inputting source data into the pre-rule processing container to obtain an intermediate data set; inputting the source data and the intermediate data set into a post rule processing container, and determining whether the trigger condition of the rule is satisfied; the data dependence of the nesting rule is decoupled, the judgment of the nesting rule is asynchronous, the rule execution efficiency is improved, and the rule judgment execution time is shortened.
Description
Technical Field
The invention relates to the technical field of automation, in particular to an asynchronous nested rule time sequence triggering method and system.
Background
With the continuous deep construction of large overhaul and large operation systems, 220kV and above voltage class substations have fully stepped into unattended and centralized monitoring operation modes. In order to adapt to an unattended operation mode of the substation, the unattended operation of the substation is emphasized in recent years, the technical standard system of the unattended operation substation is further perfected according to the related standard of the existing unattended operation substation, the technical requirements of the unattended operation are standardized, and the construction of the unattended operation substation is guided. In a substation along a railway, the method is suitable for an unattended mode of the substation. The auxiliary monitoring system deployed in the substation can periodically collect relevant monitoring data for various switches, on-line monitoring and other devices in the substation, such as: current, voltage, switching state of the device, etc. The technician configures rules in the rule engine that monitor the data triggering event, and the technician is notified after the rules are triggered.
The existing nested rule triggering mode is to input result data generated by the nested rule into a rule which is used for the result data subsequently in a data collecting mode. The following rules have two ways in the processing mode of judging whether the rules are triggered or not: one is not to distinguish the source of the data, namely: judging whether the data of the data area at the current moment triggers a rule or not, wherein in the mode, under the condition that the source data is continuously input and the rule judgment is asynchronous, the data version is very easy to be inconsistent, so that the judgment result is wrong; the other mode is to serialize nested data, the mode can ensure the consistency of data versions, but the influence on the performance is extremely large, particularly in the multi-level nested rule, the follow-up rule needs to wait for the result of the sequential judgment execution of the pre-rule, the performance is low, and the data backlog is easy to generate. Therefore, the existing nested rule time sequence triggering technology has low performance, long time consumption and easy error. The rule using the nested data cannot determine whether the nested rule can be triggered, and can only poll or wait for event triggering or overtime, so that the subsequent data judgment can be blocked, and the performance is low; the data generated by the nested rule trigger can be confused in the subsequent rule judgment, so that the subsequent rule judgment result is wrong. Meanwhile, because the nested trigger result data used by the subsequent rule is asynchronous, the data versions used in the subsequent rule are inconsistent, and the subsequent rule judgment error is also caused.
In view of this, the invention provides a method and a system for triggering asynchronous nested rule time sequence, which decouples the data dependence of the nested rule, asynchronously normalizes the judgment of the nested rule, improves the efficiency of rule execution and shortens the time of rule judgment execution. The correctness of the data used for judging by the nested rules is ensured, and the correctness of the rule judging result is ensured. The complexity of the nesting rule judgment logic writing is reduced, and the aim of simplifying the complicated nesting rule configuration is fulfilled. The method solves the problems of low execution efficiency of the nesting rules and high error rate of judgment results caused by inconsistent data versions.
Disclosure of Invention
The invention aims to provide an asynchronous nested rule time sequence triggering method, which comprises the following steps: obtaining a configuration file according to a service demand configuration rule; dividing rules in the configuration file into common rules and nested rules; dividing the nesting rule into an independent common rule, a preposed rule and a postposed rule; loading the common rules and the independent common rules into a common rule processing container; loading the pre-rules into a pre-rules processing container; loading the post rule into a post rule processing container; inputting source data into the common rule processing container, and determining whether a trigger condition of a rule is met; inputting the source data into the pre-rule processing container to obtain an intermediate data set; and inputting the source data and the intermediate data set into the post rule processing container, and determining whether the trigger condition of the rule is met.
Furthermore, the common rule processing container, the front rule processing container and the rear rule processing container are all execution units for independently receiving data, processing the data and realizing rule judgment.
Further, inputting source data into the normal rule processing container, and determining whether a trigger condition of a rule is satisfied, including: after the common rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic; if the rule triggering condition is met, directly triggering an alarm, and sending event data to the service; and if the common rule processing container has no triggerable rule, not processing.
Further, inputting the source data into the pre-rule processing container to obtain an intermediate data set, including: after the preposed rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic; and if the rule is met, executing a trigger logic, and recombining the generated result data and the source data triggering the rule into the intermediate data group and pushing the intermediate data group to the post-rule processing container.
Further, inputting the source data and the intermediate data set into the post-rule processing container, determining whether a trigger condition of a rule is satisfied, including: after the post-arranged rule processing container receives the source data or the intermediate data set, starting multithreading, splitting the intermediate data set into a common rule source data format, and performing preprocessing conversion to obtain a plurality of conversion data; inserting/updating the plurality of conversion data into the data storage area in the post-rule processing container; triggering a rule judging method in the post rule processing container, and executing rule judgment; if rules are matched in the post rule processing container, triggering event data are pushed to a service system; if no rule is matched, the process is ended.
The invention aims to provide an asynchronous nested rule time sequence triggering system which comprises a configuration file acquisition module, a configuration file dividing module, a nested rule dividing module, a loading module and a triggering module; the configuration file acquisition module is used for acquiring a configuration file according to a service demand configuration rule; the configuration file dividing module is used for dividing rules in the configuration file into common rules and nested rules; the nesting rule dividing module is used for dividing the nesting rule into an independent common rule, a preposed rule and a postposition rule; the loading module is used for loading the common rules and the independent common rules into a common rule processing container; loading the pre-rules into a pre-rules processing container; loading the post rule into a post rule processing container; the trigger module is used for inputting source data into the common rule processing container and determining whether the trigger condition of the rule is met or not; inputting the source data into the pre-rule processing container to obtain an intermediate data set; and inputting the source data and the intermediate data set into the post rule processing container, and determining whether the trigger condition of the rule is met.
Furthermore, the common rule processing container, the front rule processing container and the rear rule processing container are all execution units for independently receiving data, processing the data and realizing rule judgment.
Further, inputting source data into the normal rule processing container, and determining whether a trigger condition of a rule is satisfied, including: after the common rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic; if the rule triggering condition is met, directly triggering an alarm, and sending event data to the service; and if the common rule processing container has no triggerable rule, not processing.
Further, inputting the source data into the pre-rule processing container to obtain an intermediate data set, including: after the preposed rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic; and if the rule is met, executing a trigger logic, and recombining the generated result data and the source data triggering the rule into the intermediate data group and pushing the intermediate data group to the post-rule processing container.
Further, inputting the source data and the intermediate data set into the post-rule processing container, determining whether a trigger condition of a rule is satisfied, including: after the post-arranged rule processing container receives the source data or the intermediate data set, starting multithreading, splitting the intermediate data set into a common rule source data format, and performing preprocessing conversion to obtain a plurality of conversion data; inserting/updating the plurality of conversion data into the data storage area in the post-rule processing container; triggering a rule judging method in the post rule processing container, and executing rule judgment; if rules are matched in the post rule processing container, triggering event data are pushed to a service system; if no rule is matched, the process is ended.
The technical scheme of the embodiment of the invention has at least the following advantages and beneficial effects:
processing the preposition rule by setting a preposition rule processing container to obtain an intermediate data set; and then the intermediate data set is sent to a post-rule processing container, so that the consistency of the data version used by the nesting rule in judgment can be ensured.
The common rule and the nested rule are mutually isolated, so that the process of processing the common rule and the nested rule is prevented from being mixed, the processing efficiency is improved, and the error rate of parallel execution of the rules is reduced.
The nested rules can be executed in parallel, so that the rule execution efficiency is greatly improved.
The nesting rule is divided into an independent common rule, a preposed rule and a postposed rule, so that the multilevel nesting rule does not influence the execution efficiency and the accuracy.
The common rule processing container is used for processing the common rule and the independent common rule, the front rule processing container is used for processing the front rule and the rear rule processing container is used for processing the rear rule, so that the resource allocation executed by the common rule and the nested rule can be independently controlled, and the resource waste is avoided.
Drawings
FIG. 1 is an exemplary schematic diagram of an asynchronous nested rule timing triggering method provided by some embodiments of the present invention;
FIG. 2 is an exemplary flow chart of a process flow for a pre-rules processing container provided by some embodiments of the present invention;
FIG. 3 is an exemplary block diagram of an asynchronous nested rule timing trigger system according to some embodiments of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Fig. 1 is an exemplary schematic diagram of an asynchronous nested rule timing triggering method according to some embodiments of the present invention. As shown in fig. 1, the process 100 may include the following:
and according to the service demand configuration rule, obtaining a configuration file.
A business requirement may refer to a specific description of functions and characteristics associated with achieving a particular business objective or business process. For example, the business requirements may be related functions and characteristics of an unattended, centrally monitored operational model for implementing a substation. In some embodiments, rules may be configured at the interface as per traffic needs. The configuration file is used to store configuration information for the system components. For example, the substation may be unmanned to monitor configuration information of the system.
Rules in the configuration file are divided into common rules and nested rules.
The general rule may refer to a rule that directly generates alarm data using source data. For example, the general rule generates event data. Nested rules may refer to rules having a hierarchical structure. For example, one or more conditions for a subsequent triggering rule are that a rule that is composed of result data and source data that are generated after triggering by other rules may be considered a nested rule. In some embodiments, common rules and nested rules may be distinguished by identifying the structure or manner in which the rules operate. If no nesting rules exist, no processing is required.
The nested rules are divided into independent common rules, preposed rules and postamble rules.
The independent common rule is similar to the common rule, and refers to a rule for directly generating alarm data by utilizing source data in a nested rule. The pre-rule refers to a rule that generates intermediate data. For example, the pre-rules generate data for subsequent use, rather than directly generating event data. The post rule refers to a rule for generating alarm data using intermediate data and source data. For example, the post-rules generate event data. In some embodiments, the individual normal rules, pre-rules, and post-rules may be distinguished by identifying the function of multiple rules within a nested rule.
And loading the common rule and the independent common rule into a common rule processing container.
The normal rule processing container may refer to an execution unit that receives source data independently and processes and determines rules for the source data.
And loading the pre-rules into a pre-rule processing container.
The pre-rule processing container may refer to an execution unit that receives source data independently, processes the source data, and determines to generate intermediate data.
And loading the post rule into a post rule processing container.
The post rule processing container may refer to an execution unit that receives source data and intermediate data independently, and processes and determines the received data.
And inputting the source data into the common rule processing container, and determining whether the trigger condition of the rule is met.
The source data may refer to the raw data acquired. For example, the acquired voltage, current, and switching data of the substation. In some embodiments, inputting source data into the generic rule processing container, determining whether a trigger condition for a rule is satisfied, includes: after the common rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic; if the rule triggering condition is met, directly triggering an alarm, and sending event data to the service; and if the common rule processing container has no triggerable rule, not processing. For example, the common rule is to receive the source data in full and to execute the rule judgment trigger logic independently in the common rule processing container. And after the judgment triggering logic is executed, if the rule triggering condition is met, automatically triggering a rule event, and notifying the service to execute the corresponding service logic.
And inputting the source data into the pre-rule processing container to obtain an intermediate data set.
Intermediate data may refer to temporary data or partial results generated during processing. For example, the acquired source data are the voltage and current of the substation, and the power obtained by the voltage and current can be regarded as intermediate data. The intermediate data set includes source data and intermediate data. Taking the above voltage and current as an example, the intermediate data set consists of voltage, current and power. In some embodiments, inputting the source data into the pre-rules processing container to obtain an intermediate data set includes: after the preposed rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic; and if the rule is met, executing a trigger logic, and recombining the generated result data and the source data triggering the rule into the intermediate data group and pushing the intermediate data group to the post-rule processing container. For example, the pre-rules receive the full amount of data and independently execute the predicate trigger logic in the pre-rules processing container. If the trigger condition is met, the data triggering the rule and the data needing to be generated are recombined into a data set, and the data is pushed to a post-rule data receiving processor. For more on the pre-rules processing container, see fig. 2 and its associated description.
And inputting the source data and the intermediate data set into the post rule processing container, and determining whether the trigger condition of the rule is met.
In some embodiments, inputting the source data and the intermediate data set into the post-rules processing container, determining whether a trigger condition for a rule is satisfied comprises: after the post-arranged rule processing container receives the source data or the intermediate data set, starting multithreading, splitting the intermediate data set into a common rule source data format, and performing preprocessing conversion to obtain a plurality of conversion data; inserting/updating the plurality of conversion data into the data storage area in the post-rule processing container; triggering a rule judging method in the post rule processing container, and executing rule judgment; if rules are matched in the post rule processing container, triggering event data are pushed to a service system; if no rule is matched, the process is ended. For example, the post rule receives the total source data and the result data generated by the pre rule, analyzes the data set recombined by the pre rule, inserts the data set into the post rule processing container in batches, triggers a rule judgment once after loading one data set, judges whether the data in the current post rule processing container meets the triggering condition, automatically triggers a rule event if the data meets the triggering condition, and notifies the service to execute corresponding service logic.
Fig. 2 is an exemplary flow chart of a process flow of a pre-rules processing container provided by some embodiments of the invention. As shown in fig. 2, the flow 200 includes the following:
the source data is pulled, i.e., the source data is acquired.
The source data is processed.
Judging whether the data key exists or not; the key refers to a key for accessing and locating unique identification data.
If the data key exists, the data corresponding to the key in the pre-processor (i.e., pre-rule processing container) is updated.
If the data key does not exist, inserting the data into the preprocessor;
after updating the data corresponding to the key in the preprocessor or inserting the data into the preprocessor, judging whether rules are matched;
if the rules are matched, processing rule calculation logic;
assembling result data and source data of trigger rules;
pushing the assembled dataset to a post-processor (i.e., post-rule processing container).
FIG. 3 is an exemplary block diagram of an asynchronous nested rule timing trigger system according to some embodiments of the present invention. As shown in fig. 3, system 300 includes a profile acquisition module 310, a profile partitioning module 320, a nested rule partitioning module 330, a loading module 340, and a triggering module 350.
The profile obtaining module 310 is configured to obtain a profile according to the service requirement configuration rule. For more details on the profile acquisition module 310, see FIG. 1 and its associated description.
The profile dividing module 320 is configured to divide rules in the profile into a common rule and a nested rule. For more details on the profile partitioning module 320, see FIG. 1 and its associated description.
The nesting rule dividing module 330 is configured to divide the nesting rule into an independent normal rule, a pre-rule, and a post-rule. For more details on the nested rule partitioning module 330, see FIG. 1 and its associated description.
The loading module 340 is configured to load the normal rule and the independent normal rule into a normal rule processing container; loading the pre-rules into a pre-rules processing container; and loading the post rule into a post rule processing container. For more details on the load module 340, see FIG. 1 and its associated description.
The trigger module 350 is configured to input source data into the normal rule processing container, and determine whether a trigger condition of a rule is satisfied; inputting the source data into the pre-rule processing container to obtain an intermediate data set; and inputting the source data and the intermediate data set into the post rule processing container, and determining whether the trigger condition of the rule is met. For more details on the trigger module 350, see FIG. 1 and its associated description.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. An asynchronous nested rule timing triggering method, comprising:
obtaining a configuration file according to a service demand configuration rule;
dividing rules in the configuration file into common rules and nested rules;
dividing the nesting rule into an independent common rule, a preposed rule and a postposed rule;
loading the common rules and the independent common rules into a common rule processing container;
loading the pre-rules into a pre-rules processing container;
loading the post rule into a post rule processing container;
inputting source data into the common rule processing container, and determining whether a trigger condition of a rule is met;
inputting the source data into the pre-rule processing container to obtain an intermediate data set;
and inputting the source data and the intermediate data set into the post rule processing container, and determining whether the trigger condition of the rule is met.
2. The asynchronous nested rule timing triggering method of claim 1, wherein the normal rule processing container, the pre-rule processing container, and the post-rule processing container are each execution units that independently receive data and process the data and implement rule judgment.
3. The asynchronous nested rule timing triggering method of claim 1, wherein inputting source data into the normal rule processing container, determining whether a triggering condition of a rule is satisfied, comprises:
after the common rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic;
if the rule triggering condition is met, directly triggering an alarm, and sending event data to the service;
and if the common rule processing container has no triggerable rule, not processing.
4. The asynchronous nested rule timing triggering method of claim 1, wherein inputting the source data into the pre-rule processing container results in an intermediate data set comprising:
after the preposed rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic;
and if the rule is met, executing a trigger logic, and recombining the generated result data and the source data triggering the rule into the intermediate data group and pushing the intermediate data group to the post-rule processing container.
5. The asynchronous nested rule timing triggering method of claim 1, wherein inputting the source data and the intermediate data set into the post-rule processing container, determining whether a triggering condition of a rule is satisfied, comprises:
after the post-arranged rule processing container receives the source data or the intermediate data set, starting multithreading, splitting the intermediate data set into a common rule source data format, and performing preprocessing conversion to obtain a plurality of conversion data;
inserting/updating the plurality of conversion data into the data storage area in the post-rule processing container;
triggering a rule judging method in the post rule processing container, and executing rule judgment;
if rules are matched in the post rule processing container, triggering event data are pushed to a service system; if no rule is matched, the process is ended.
6. An asynchronous nested rule time sequence triggering system is characterized by comprising a configuration file acquisition module, a configuration file dividing module, a nested rule dividing module, a loading module and a triggering module;
the configuration file acquisition module is used for acquiring a configuration file according to a service demand configuration rule;
the configuration file dividing module is used for dividing rules in the configuration file into common rules and nested rules;
the nesting rule dividing module is used for dividing the nesting rule into an independent common rule, a preposed rule and a postposition rule;
the loading module is used for loading the common rules and the independent common rules into a common rule processing container; loading the pre-rules into a pre-rules processing container; loading the post rule into a post rule processing container;
the trigger module is used for inputting source data into the common rule processing container and determining whether the trigger condition of the rule is met or not; inputting the source data into the pre-rule processing container to obtain an intermediate data set; and inputting the source data and the intermediate data set into the post rule processing container, and determining whether the trigger condition of the rule is met.
7. The asynchronous nested rule timing triggering system of claim 6, wherein the normal rule processing container, the pre-rule processing container, and the post-rule processing container are each execution units that independently receive data and process the data and implement rule decisions.
8. The asynchronous nested rule timing triggering system of claim 6 wherein inputting source data into the normal rule processing container, determining whether a triggering condition for a rule is satisfied comprises:
after the common rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic;
if the rule triggering condition is met, directly triggering an alarm, and sending event data to the service;
and if the common rule processing container has no triggerable rule, not processing.
9. The asynchronous nested rule timing triggering system of claim 6, wherein inputting the source data into the pre-rule processing container results in an intermediate data set comprising:
after the preposed rule processing container receives the source data, starting multithreading to perform data processing and rule judging logic;
and if the rule is met, executing a trigger logic, and recombining the generated result data and the source data triggering the rule into the intermediate data group and pushing the intermediate data group to the post-rule processing container.
10. The asynchronous nested rule timing triggering system of claim 6 wherein inputting the source data and the intermediate data set into the post-rule processing container determines whether a triggering condition for a rule is satisfied, comprising:
after the post-arranged rule processing container receives the source data or the intermediate data set, starting multithreading, splitting the intermediate data set into a common rule source data format, and performing preprocessing conversion to obtain a plurality of conversion data;
inserting/updating the plurality of conversion data into the data storage area in the post-rule processing container;
triggering a rule judging method in the post rule processing container, and executing rule judgment;
if rules are matched in the post rule processing container, triggering event data are pushed to a service system; if no rule is matched, the process is ended.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311085906.3A CN116796931B (en) | 2023-08-28 | 2023-08-28 | Asynchronous nested rule time sequence triggering method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311085906.3A CN116796931B (en) | 2023-08-28 | 2023-08-28 | Asynchronous nested rule time sequence triggering method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116796931A true CN116796931A (en) | 2023-09-22 |
| CN116796931B CN116796931B (en) | 2023-11-07 |
Family
ID=88040159
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311085906.3A Active CN116796931B (en) | 2023-08-28 | 2023-08-28 | Asynchronous nested rule time sequence triggering method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116796931B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20010054861A (en) * | 1999-12-08 | 2001-07-02 | 이계철 | Method for processing asynchronous parallel rule in active database |
| US20030161459A1 (en) * | 2002-02-28 | 2003-08-28 | Mcblain Thomas Joseph | Outbound call rules routing |
| US20060179028A1 (en) * | 2005-02-04 | 2006-08-10 | Charles Bram | Rules-based system architecture and systems using the same |
| US20070150330A1 (en) * | 1999-12-30 | 2007-06-28 | Mcgoveran David O | Rules-based method and system for managing emergent and dynamic processes |
| US20100138842A1 (en) * | 2008-12-03 | 2010-06-03 | Soren Balko | Multithreading And Concurrency Control For A Rule-Based Transaction Engine |
| CN101986646A (en) * | 2010-11-01 | 2011-03-16 | 中兴通讯股份有限公司 | XML (extensible markup language)-based broadband SIP (session initiation protocol) service trigger/configuration method and service trigger |
| CN102222019A (en) * | 2011-05-19 | 2011-10-19 | 西南交通大学 | Wavelet and wavelet packet multi-core parallel computation method based on OpenMP (open multi-processing) |
| CN109656453A (en) * | 2018-12-20 | 2019-04-19 | 树根互联技术有限公司 | Rule editing method, apparatus and equipment |
| US20210241205A1 (en) * | 2020-01-31 | 2021-08-05 | Gigawarp Technologies LLC | System for allocating and deploying resources based on a logical ruleset |
| CN114666780A (en) * | 2020-12-22 | 2022-06-24 | 中兴通讯股份有限公司 | Service nesting rule configuration method and device and service triggering method |
| CN114816170A (en) * | 2021-01-29 | 2022-07-29 | 腾讯科技（北京）有限公司 | Rule scheme generation method, device, medium and electronic equipment |
| CN115910317A (en) * | 2022-09-08 | 2023-04-04 | 杭州数垚科技有限公司 | Method for constructing clinical test execution engine based on rule configuration and related device |
-
2023
- 2023-08-28 CN CN202311085906.3A patent/CN116796931B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20010054861A (en) * | 1999-12-08 | 2001-07-02 | 이계철 | Method for processing asynchronous parallel rule in active database |
| US20070150330A1 (en) * | 1999-12-30 | 2007-06-28 | Mcgoveran David O | Rules-based method and system for managing emergent and dynamic processes |
| US20030161459A1 (en) * | 2002-02-28 | 2003-08-28 | Mcblain Thomas Joseph | Outbound call rules routing |
| US20060179028A1 (en) * | 2005-02-04 | 2006-08-10 | Charles Bram | Rules-based system architecture and systems using the same |
| US20100138842A1 (en) * | 2008-12-03 | 2010-06-03 | Soren Balko | Multithreading And Concurrency Control For A Rule-Based Transaction Engine |
| WO2012058907A1 (en) * | 2010-11-01 | 2012-05-10 | 中兴通讯股份有限公司 | Service triggering configuration method and service trigger for broadband sip service based on xml |
| CN101986646A (en) * | 2010-11-01 | 2011-03-16 | 中兴通讯股份有限公司 | XML (extensible markup language)-based broadband SIP (session initiation protocol) service trigger/configuration method and service trigger |
| CN102222019A (en) * | 2011-05-19 | 2011-10-19 | 西南交通大学 | Wavelet and wavelet packet multi-core parallel computation method based on OpenMP (open multi-processing) |
| CN109656453A (en) * | 2018-12-20 | 2019-04-19 | 树根互联技术有限公司 | Rule editing method, apparatus and equipment |
| US20210241205A1 (en) * | 2020-01-31 | 2021-08-05 | Gigawarp Technologies LLC | System for allocating and deploying resources based on a logical ruleset |
| CN114666780A (en) * | 2020-12-22 | 2022-06-24 | 中兴通讯股份有限公司 | Service nesting rule configuration method and device and service triggering method |
| CN114816170A (en) * | 2021-01-29 | 2022-07-29 | 腾讯科技（北京）有限公司 | Rule scheme generation method, device, medium and electronic equipment |
| CN115910317A (en) * | 2022-09-08 | 2023-04-04 | 杭州数垚科技有限公司 | Method for constructing clinical test execution engine based on rule configuration and related device |
Non-Patent Citations (1)
| Title |
|---|
| MICROSOFT: "创建嵌套触发器", Retrieved from the Internet <URL:https://learn.microsoft.com/zh-cn/sql/relational-databases/triggers/create-nested-triggers?view=sql-server-ver16&redirectedfrom-MSDN> * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116796931B (en) | 2023-11-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108415789B (en) | Node fault prediction system and method for large-scale hybrid heterogeneous storage system | |
| CN110958136A (en) | Deep learning-based log analysis early warning method | |
| CN101176072B (en) | Method and system for managing schedules for monitored resources | |
| CN104966172A (en) | Large data visualization analysis and processing system for enterprise operation data analysis | |
| Khoshgoftaar et al. | Data mining for predictors of software quality | |
| CN103186603A (en) | Method, system and equipment for determining influence of SQL statements on performance of key businesses | |
| Ye et al. | Passenger flow prediction in bus transportation system using ARIMA models with big data | |
| CN112580961A (en) | Power grid information system based operation risk early warning method and device | |
| CN112183656A (en) | SCADA data frequent item set mining method in power grid fault | |
| CN110969375A (en) | Intelligent substation alarm processing method and device, terminal and storage medium | |
| CN113268403A (en) | Time series analysis and prediction method, device, equipment and storage medium | |
| CN116796931B (en) | Asynchronous nested rule time sequence triggering method and system | |
| CN109740770A (en) | Unit exception processing method, device, computer equipment and storage medium | |
| CN109445304A (en) | A kind of intelligent fault analysis system and method based on cab signal | |
| CN105892957B (en) | A kind of distributed transaction execution method based on Dynamic Program Slicing | |
| CN112613790A (en) | Cooperative data processing method, device and medium applied to multi-station fusion environment | |
| CN104155130A (en) | Comprehensive test intelligent interpretation system for small satellite | |
| CN115880116A (en) | Task scheduling method, system, readable storage medium and computer equipment | |
| CN116108276A (en) | Information recommendation method and device based on artificial intelligence and related equipment | |
| CN110287114A (en) | A kind of method and device of database script performance test | |
| CN104850484A (en) | Bitmap analysis based automatic determination method for character terminal interactive state | |
| CN104301388A (en) | Large running system monitoring and analyzing management system | |
| CN113076217A (en) | Disk fault prediction method based on domestic platform | |
| CN104346246A (en) | Failure prediction method and device | |
| CN113807704A (en) | Intelligent algorithm platform construction method for urban rail transit data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |