Test run adjustment strategy compilation and operation method and system based on rule engine
By using a rule-based strategy development method, the test strategy for aero-engines is modularized and automated, which solves the problem of insufficient experience of test personnel, enables rapid and accurate anomaly identification and handling, and improves the efficiency and accuracy of the test process.
Patent Information
- Application Number
- CN202511662407.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-13
- Publication Date
- 2026-02-13
AI Technical Summary
In the current process of testing aircraft engines, the limited experience of the test personnel makes it difficult to quickly and accurately identify abnormal situations, and the lack of a unified and standardized adjustment strategy leads to low efficiency in identifying and handling abnormal situations.
A rule engine-based test run adjustment strategy development method is adopted, which divides the strategy into four modules: trigger timing, adjustment calculation, result handling, and troubleshooting plan. The rule engine automatically identifies anomalies and provides handling plans, and the system achieves automated operation by utilizing the rule base and multi-signal input source data.
It enables rapid and accurate identification of anomalies and provision of corresponding handling solutions during aero-engine testing, improving the efficiency and accuracy of identification and handling, and ensuring the standardization and automated operation of the strategy.
Smart Images
Figure CN121524873A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of aircraft engine test strategies, and in particular to a method and system for developing and implementing test adjustment strategies based on a rules engine. Background Technology
[0002] Test run adjustment strategies are primarily used to identify abnormal conditions during aero-engine testing and to provide corresponding handling measures and troubleshooting solutions. These include situations such as unqualified performance indicators, abnormal pressure signals, and even engine oil leaks or fires. However, current test run adjustment strategies rely on manual identification and execution, which exposes certain defects and shortcomings in actual test run processes.
[0003] First, individual test operators have limited experience in handling various abnormal situations and cannot identify all abnormalities during the test run. Test run adjustment strategies are highly variable; even the same parameter failure can lead to dozens of solutions depending on the switches and parameter variations, resulting in different handling measures and troubleshooting plans. Furthermore, the relevant work experience and years of service of test operators are highly correlated; those unfamiliar with these situations will find it difficult to adopt the optimal handling measures and troubleshooting plans.
[0004] Secondly, it is difficult for test operators to guarantee the speed and accuracy of manually identifying abnormal situations during the test run. During the test run, there are numerous types and quantities of various switching quantities, continuous parameters, and index quantities, and there are more than ten monitors displaying monitoring data. It is difficult for humans to quickly and effectively identify all abnormal situations, so state adjustments often have to be carried out after the machine has stopped and additional calculations have been performed.
[0005] Furthermore, there are currently no unified standards for test personnel regarding the calculation, handling measures, and troubleshooting solutions for test adjustment strategies. For example, when performance indicators fail to meet standards, the situation is inherently extremely complex. Different test personnel may use different adjustment methods and calculation formulas for different controller parameters, resulting in different adjustment results. Therefore, it is necessary to develop a universal adjustment solution. Summary of the Invention
[0006] Purpose of the invention: The purpose of this invention is to provide a method and system for developing and implementing test and adjustment strategies based on a rule engine.
[0007] Technical solution: The method for developing and implementing test drive adjustment strategies based on a rule engine, as described in this invention, includes the following steps:
[0008] Step 1: Develop standardized process documents for the strategies, dividing strategies with different content into four modules: trigger timing, adjustment calculation, result handling, and troubleshooting plan.
[0009] Step 2: Before bench testing, confirm the technical status of each accessory, record the initial status of adjustable parts and the parameter information of the controller before testing, and enter them into the strategy system; after completing the compilation of strategy content data, a rule file that can be used for automated operation of the strategy will be formed.
[0010] Step 3: Save all completed policy rule files into the rule base and select which policy entries to enable during the next test run;
[0011] Step 4: At the start of the test run, the strategy system receives data from multiple signal input sources on the test bench, such as the data acquisition system, engine controller, and video sensing system, via UDP communication. The rule engine automatically identifies whether the real-time data is abnormal. If an abnormality is found, a pop-up window triggers the strategy that meets the corresponding triggering conditions and provides the prepared strategy handling operation and troubleshooting plan. If there is no abnormality, it runs continuously in the background without interfering with the test run process.
[0012] Furthermore, the different strategies in step 1 include security strategies, fault strategies, backup adjustment strategies, and online adjustment strategies, which are managed hierarchically. Security strategies have the highest trigger priority, followed by fault strategies, backup adjustment strategies have the third highest trigger priority, and online adjustment strategies have the lowest trigger priority.
[0013] Furthermore, in step 1, the trigger timing module serves as an entry condition for a strategy rule, which is jointly determined by the content of the basic event and the judgment event.
[0014] Furthermore, in step 1, the adjustment calculation module is a module that calculates the adjustment amount information of different accessory units through the engine operating state characteristic parameters. The specific output result depends on the content of the calculation events in the selected backup adjustment strategy and online adjustment strategy.
[0015] Furthermore, in step 1, the result processing module is responsible for providing strategy processing options, which are determined by the content of the result event.
[0016] Furthermore, in step 1, the troubleshooting solution module is responsible for providing supplementary inspection procedures after strategy identification, which are determined by the content of the troubleshooting work.
[0017] Furthermore, in step 1, the complex strategy parameter indicators are divided into five categories: data acquisition channel symbols, secondary calculation scripts, data acquisition curve interpretation indicators, XY oscilloscope curves, and data acquisition performance calculation indicators. Information maintenance databases are established for each category to manage and version control the detailed fields of the indicators, thereby enabling quick selection when editing strategies.
[0018] Furthermore, the strategy that has been edited and published in step 2 will have its strategy rule file automatically sent to the rule base when the test drive begins. After the test drive begins, it will receive data from multiple signal input sources on the test bench, including the data acquisition system, engine controller, and intelligent sensing system, through a message subscription consumption mechanism.
[0019] Furthermore, in step 3, the rule engine periodically traverses all policy rules in the rule base. Policies that meet the triggering conditions will provide corresponding handling results and troubleshooting solutions according to the edited content. High-priority policies cover low-priority policies, and the final results are displayed and selected by the user in a pop-up window.
[0020] The test adjustment strategy compilation and operation system based on rule engine described in this invention includes a strategy standardization compilation module and an automated operation module;
[0021] The strategy standardization compilation module is used to compile standardized process documents for strategies. It divides strategies with different contents into four modules: trigger timing, adjustment calculation, result handling, and troubleshooting plan. Before the test run, the module uses the parameter indicators, adjustable parts and controller parameter information of the strategy to be entered according to the actual status of the test bench equipment to complete the compilation of strategy content, and then forms a rule file that can be used for the automated operation of the strategy.
[0022] The automated strategy operation module stores all compiled and activated strategy rule files into the rule library, receives multi-signal input data from the test bench data acquisition system, engine controller, and intelligent sensing system, and automatically identifies and triggers strategies that meet the corresponding trigger conditions through the rule engine, providing the compiled strategy handling operations and troubleshooting solutions.
[0023] Beneficial effects: Compared with the prior art, the present invention has the following significant advantages:
[0024] This invention ensures the rapid response and accuracy of intervention in the test run after an anomaly is identified by taking targeted measures and corresponding troubleshooting methods. Without relying on manual judgment of changes in a large number of monitoring parameter combinations, it makes the strategy standardization process and the test run debugging strategy that runs automatically during the test run more standardized, faster and more accurate. Attached Figure Description
[0025] Figure 1 Flowchart of strategy editing steps;
[0026] Figure 2 Standardize the module system block diagram for the strategy;
[0027] Figure 3 This is a data flow diagram of the parameter indicator library within the strategy editing content;
[0028] Figure 4This is a data flow diagram of the test program library within the strategy editing content. Detailed Implementation
[0029] The technical solution of the present invention will be further described below with reference to the accompanying drawings.
[0030] This invention provides software and method for developing and running test adjustment strategies based on a rule engine, including a standardized strategy development module and an automated operation module.
[0031] The strategy standardization module is used to compile standardized process documents for strategies. It divides strategies with different content into four modules: trigger timing, adjustment calculation, result handling, and troubleshooting plan. It uses the parameter indicators, adjustable parts and controller parameters entered before the test run based on the actual status of the test bench equipment to complete the compilation of strategy content, and then forms a rule file that can be used for the automated operation of the strategy.
[0032] The strategy automation operation module stores all completed and activated strategy rule files into the rule library, receives data from multiple signal input sources such as the test bench data acquisition system, engine controller, and intelligent sensing system, and automatically identifies and triggers strategies that meet the corresponding trigger conditions through the rule engine, providing the compiled strategy handling operations and troubleshooting solutions.
[0033] The test operation strategies are divided into four types: safety strategies, fault strategies, backup adjustment strategies, and online adjustment strategies, managed hierarchically with decreasing trigger priority. When multiple strategies are triggered simultaneously during the test operation, or when a new strategy is triggered while the current strategy is being processed, the highest priority strategy will override the previous one, allowing test personnel to handle it first. Safety strategies have the highest trigger priority and generally include serious accident scenarios such as aircraft engine fires, oil leaks, and personnel intrusion during the test operation. Fault strategies have the next highest trigger priority and include situations such as data acquisition system parameter exceeding limits and switch quantity failures. Backup adjustment strategies have the third highest trigger priority and encompass all strategies where problems can be resolved by adjusting adjustable components. Online adjustment strategies have the lowest trigger priority and encompass all strategies where problems can be resolved by modifying controller Flash parameters.
[0034] The process of developing test drive strategies is standardized, and strategy rule files are generated, specifically including:
[0035] Based on standardization principles, strategies with different content are uniformly divided into four modules: trigger timing, adjustment calculation, result handling, and troubleshooting plan. When developing a strategy, the trigger timing module serves as an entry condition for a strategy rule, determined by the content of the basic event and the judgment event. The adjustment calculation module calculates the adjustment information provided by the strategy, determined by the content of the calculation event selectable in backup adjustment strategies and online adjustment strategies; it is also the most important module in these two types of strategies. The result handling module provides the options for strategy handling methods, determined by the content of the result event. The troubleshooting plan module provides supplementary checking procedures after strategy identification, determined by the content of the troubleshooting work. During strategy development, different events are combined and connected according to the strategy development rules, and the specific content of each event is edited to ultimately form the desired strategy functionality.
[0036] Use custom forms to create judgment formulas. Implement simple judgment logic using existing component elements, and implement complex judgment logic using custom script logic. Combine and concatenate judgment formulas with four logical conditions, namely "AND", "OR", "left parenthesis", and "right parenthesis", according to the rules of logical expressions to generate standardized strategy triggering timing content.
[0037] Use a custom form to create a calculation formula, fill in common items such as adjustable parts, Flash parameters, maximum and minimum adjustment amounts, upper and lower adjustment limits, number of decimal places to retain in the result, affected parameter indicators, ideal values of parameter indicators, and unit changes of parameter indicators, and write script code to implement the adjustment amount calculation logic.
[0038] The complex strategy parameters are divided into five categories: data acquisition channel symbols, secondary calculation scripts, data acquisition curve interpretation indicators, XY oscilloscope curves, and data acquisition performance calculation indicators. Information maintenance databases are established for each category to persistently manage and version control the detailed fields of the indicators, so that they can be quickly selected when editing strategies.
[0039] The influence relationship between adjustable components and parameter indicators in the backup adjustment strategy is bound to a database. When editing the backup strategy, select the adjustable component and the parameter indicator that the adjustable component is bound to, and the entered calculation-related information will be automatically completed.
[0040] The Flash parameter information in the online adjustment strategy is stored in a database and maintained. When editing the online strategy calculation event, the base version value information of the selected Flash parameter can be viewed. When writing the online adjustment calculation script, the base version value and the upper and lower limits of the parameter can be obtained to participate in the calculation of the adjustment amount.
[0041] The strategy results are maintained in different levels. The processing fields, such as processing measures, default processing procedures, manual operation buttons, and voice alarm content, can be edited. When editing the content of the strategy result event, the matching strategy level is selected, and the rest of the information is automatically filled in.
[0042] The strategy results are maintained in different levels. The processing fields, such as processing measures, default processing procedures, manual operation buttons, and voice alarm content, can be edited. When editing the content of the strategy result event, the matching strategy level is selected, and the rest of the information is automatically filled in.
[0043] Select the test program module to form a strategy troubleshooting work library. When editing the strategy troubleshooting plan, you can select multiple troubleshooting tasks to execute in sequence.
[0044] Once a strategy that has been edited and published is enabled, its strategy rule file will be automatically sent and stored in the rule base at the start of the test drive. After the test drive begins, the system receives data from multiple signal input sources, such as the data acquisition system, engine controller, and intelligent sensing system on the test bench, through a message subscription consumption mechanism. The rule engine periodically traverses all strategy rules in the rule base. Strategies that meet the trigger conditions will provide corresponding handling results and troubleshooting solutions according to the edited content. High-priority strategies override low-priority strategies. The final results are displayed and selected by the user through a pop-up window.
[0045] Example 1: Develop a backup adjustment strategy for "a certain data acquisition and interpretation indicator failing" and implement the strategy automatically. The specific strategy development method is as follows... Figure 1 As shown, it specifically includes:
[0046] Step 1: In the basic event, use the judgment script formula and logical connectors to form the strategy trigger condition. For example... Figure 2 As shown, the process of using the judgment script formula in basic events specifically includes:
[0047] Step 101: In the data acquisition interpretation index library, add a new data acquisition interpretation index, and enter its interpretation curve name, boundary range type, and limiting conditions, such as... Figure 3 As shown, the added data acquisition and interpretation indicators become parameter indicators, which are used in basic events, judgment events, and calculation events;
[0048] Step 102: Using the custom form function, select the "Basic Judgment Formula" type, and drag and drop the component to create the "Data Collection Judgment Indicator" judgment formula;
[0049] Specifically, the aforementioned custom form functionality can be implemented through V-Form2 custom form plugins, which allow users to quickly build forms, implement form interactions, and collect data using a rich set of plugin components. Custom functions can be created using the form's event handlers, leveraging existing data collection and interpretation indicator library interfaces to obtain all enabled, latest-version data collection and interpretation indicators.
[0050] Step 103: In the basic event, drag the created "data acquisition interpretation index" interpretation formula, fill in the input content in its form to form the unqualified range of the data acquisition interpretation index, and save the basic event content.
[0051] Step 2: In the judgment event, drag the created "Data Acquisition Judgment Indicator" judgment formula, fill in the input content in its form to form the unsafe range of the data acquisition judgment indicator, and save the judgment event content.
[0052] Step 3: In the calculation event, use the calculation script formula to compose a strategy to adjust the calculation. For example... Figure 2 As shown, the process of using calculation script formulas in a calculation event specifically includes:
[0053] Step 301: In the adjustable parts information database, add a new adjustable parts information data, and enter its adjustable parts name, adjustable parts type, maximum and minimum adjustment amount, adjustment upper and lower limits, etc.
[0054] Step 302: Using the custom form function, select the "Calculation Formula" type, drag and drop the component to create the "Backup Adjustment Calculation" calculation formula;
[0055] Step 303: In the backup adjustment rule library, add a new backup adjustment rule data, and enter the binding relationship between its adjustable components and parameter indicators for use in event calculation;
[0056] Step 304: In the calculation event, drag the created "Backup Adjustment Calculation" calculation formula, select the adjustable components and parameter indicators that need to be adjusted, and fill in the input content in the form to form the adjustment calculation scheme of the backup strategy, and save the calculation event content.
[0057] Step 4: In the result event section, edit the result handling details of the strategy. For example... Figure 4 As shown, the process specifically includes:
[0058] Step 401: Enter a data entry in the test procedure table, filling in the test procedure name and the corresponding SN code;
[0059] Step 402: Enter a data entry into the strategy level maintenance library, and fill in the strategy type, default handling method, handling button and other attributes. The source of the default handling method is all the test programs that have been entered in the test program table.
[0060] Step 403: In the result event, select the created policy level. Its details will be automatically supplemented according to the maintenance information in the policy level maintenance library to form the result processing content of the backup policy, and save the result event content.
[0061] Step 5: In the troubleshooting plan, edit the troubleshooting plan content of the strategy. For example... Figure 2As shown, first enter a piece of data into the troubleshooting work library, fill in the troubleshooting work name, select the corresponding test program, and then select the created troubleshooting work in the troubleshooting plan. Its details will be automatically supplemented according to the maintenance information of the troubleshooting work library to form the troubleshooting plan of this backup strategy. Save the troubleshooting plan content.
[0062] Step 6: Connect the basic events, judgment events, calculation events, result events, and troubleshooting solutions according to the strategy compilation rules, and save the strategy.
[0063] Step 7: Publish and enable the backup adjustment strategy for "a certain data acquisition and interpretation indicator is unqualified".
[0064] Step 8: Use the rule engine to automatically run the backup adjustment for "a certain data acquisition and interpretation index is unqualified" during the test run. When this strategy is triggered, choose to perform the adjustment according to the given adjustment amount, or choose the disposal button to perform other test run procedures.
[0065] Specifically, the aforementioned rule engine could be the Drools rule engine, which separates the business decision-making part of the application and uses predefined semantic modules to write business logic. Test data is injected into the rule engine, and using the Drools rule engine's if-then structure, policy rules that meet the if condition will execute the then statement part, calculate the adjustment amount, and issue the policy handling method and troubleshooting plan.
[0066] Example 2: An online adjustment strategy for "a certain XY oscilloscope curve is unqualified" is developed and its automatic operation is implemented. This example differs from Example 1 in the content of steps one and three, and step two is omitted; the rest of the process is the same as in Example 1.
[0067] Step 1: In the basic event, use the judgment script formula and logical connectors to form the strategy trigger condition. For example... Figure 2 As shown, the process of using the judgment script formula in basic events specifically includes:
[0068] Step 101: In the XY oscilloscope curve library, add a new XY oscilloscope curve data, and enter its attributes such as XY oscilloscope curve name, calculation type, safe range coordinate points, qualified range coordinate points, and target line coordinate points, etc. Figure 3 As shown, the added XY oscilloscope curves become parameter indicators, used in basic events, judgment events, and calculation events;
[0069] Step 102: Using the custom form function, select the "Script Interpretation Formula" type, drag and drop the component to create the "XY Oscilloscope Curve" interpretation formula, and write its script logic code;
[0070] Step 103: In the basic event, drag the created "XY Oscilloscope Curve" interpretation formula, fill in the input content in its form to form the unqualified range of the XY oscilloscope curve, and save the basic event content.
[0071] Step 3: In the calculation event, use the calculation script formula to compose a strategy to adjust the calculation. For example... Figure 2 As shown, the process of using calculation script formulas in a calculation event specifically includes:
[0072] Step 301: Using the custom form function, select the "Calculation Formula" type, and drag and drop the component to create the "Online Curve Adjustment" calculation formula;
[0073] Step 302: In the online parameter maintenance library, add a new online parameter data and enter its Flash parameter name, type, base version value, adjustment upper and lower limits, etc.
[0074] Step 303: In the calculation event, drag the created "Online Curve Adjustment" calculation formula, select the online parameters and XY oscilloscope curves to be adjusted, and fill in the input content in the form to form the adjustment calculation scheme of the online strategy, and save the calculation event content.
[0075] Example 3: A "engine oil leak" safety strategy is developed and its automatic operation is implemented. The difference between this example and Example 1 is the content of step one, and steps two and three are deleted. The other processes are the same as in Example 1.
[0076] Step 1: In the basic event, use the judgment calculation script formula and logical connectives to form the strategy triggering condition. For example... Figure 2 As shown, the specific uses of the judgment calculation script formula in basic events include:
[0077] Step 101: Using the custom form function, select the "Basic Judgment Formula" type, and drag and drop the component to create the "Intelligent Sensing" judgment formula;
[0078] Step 102: In the basic event, drag the created "Intelligent Sensing" interpretation formula, fill in the input content in its form, and save the basic event content;
[0079] Example 4: Compile a fault strategy for "symbol over-limit of a certain data acquisition channel" and implement the automatic operation of the strategy. The difference between this example and Example 3 is the content of step one, while the other processes are the same as in Example 3.
[0080] Step 1: In the basic event, use the judgment calculation script formula and logical connectives to form the strategy triggering condition. For example... Figure 2 As shown, the specific uses of the judgment calculation script formula in basic events include:
[0081] Step 101: Using the custom form function, select the "Basic Interpretation Formula" type, and drag and drop the component to create the "Data Acquisition Channel Symbol" interpretation formula;
[0082] Step 102: In the basic event, drag the created "data acquisition channel symbol" interpretation formula, fill in the input content in its form, and save the basic event content.
Claims
1. A method for developing and implementing a test run adjustment strategy based on a rule engine, characterized in that, Includes the following steps: Step 1: Develop standardized process documents for the strategies, dividing the strategies of different content into four modules: trigger timing, adjustment calculation, result handling, and troubleshooting plan. Step 2: Before conducting bench testing, confirm the technical status of each accessory, record the initial status of adjustable parts and the parameter information of the controller before testing, and enter them into the strategy information. After the strategy content data is compiled, a rule file that can be used for the automated operation of the strategy is formed. Step 3: After the rule files are generated, save all the completed policy rule files into the rule library, manually select the policy entries that need to be mounted and run in the next test run, and enable them. Step 4: At the start of the test run, data from multiple signal input sources, including the data acquisition system, engine controller, and video sensing system on the test bench, are received via UDP communication. The rule engine automatically identifies whether the real-time data is abnormal. If an abnormality is found, a pop-up window triggers the strategy that meets the corresponding triggering conditions and provides the pre-compiled strategy handling operation and troubleshooting solution. If there is no abnormality, it runs continuously in the background without interfering with the test run process.
2. The method for developing and implementing a test drive adjustment strategy based on a rule engine according to claim 1, characterized in that, The different strategies in step 1 include security strategies, fault strategies, backup adjustment strategies, and online adjustment strategies, which are managed hierarchically. Security strategies have the highest trigger priority, followed by fault strategies, backup adjustment strategies have the third highest trigger priority, and online adjustment strategies have the lowest trigger priority.
3. The method for developing and implementing a test drive adjustment strategy based on a rule engine according to claim 1, characterized in that, In step 1, the trigger timing module serves as an entry condition for a strategy rule, and is jointly determined by the content of the basic event and the judgment event.
4. The method for developing and implementing a test drive adjustment strategy based on a rule engine according to claim 1, characterized in that, In step 1, the adjustment calculation module is a module that calculates the adjustment amount information of different accessory units through the engine operating status characteristic parameters. The specific output result depends on the selected backup adjustment strategy and the calculation event content in the online adjustment strategy.
5. The method for developing and implementing a test drive adjustment strategy based on a rule engine according to claim 1, characterized in that, In step 1, the result processing module is responsible for providing strategy processing options, which are determined by the content of the result event.
6. The method for developing and implementing a test drive adjustment strategy based on a rule engine according to claim 1, characterized in that, In step 1, the troubleshooting solution module is responsible for providing supplementary inspection procedures after strategy identification, which are determined by the content of the troubleshooting work.
7. The method for developing and implementing a test drive adjustment strategy based on a rule engine according to claim 1, characterized in that, In step 1, the complex strategy parameter indicators are divided into five categories: data acquisition channel symbols, secondary calculation scripts, data acquisition curve interpretation indicators, XY oscilloscope curves, and data acquisition performance calculation indicators. Information maintenance databases are established for each category to manage the detailed fields of the indicators and control versioning, thereby supporting quick selection when editing strategies.
8. The method for developing and implementing a test drive adjustment strategy based on a rule engine according to claim 1, characterized in that, The strategy edited and published in step 2 will have its strategy rule file automatically sent to the rule base when the test run begins. After the test run begins, it will receive data from multiple signal input sources on the test bench, including the data acquisition system, engine controller, and intelligent sensing system, through a message subscription consumption mechanism.
9. The method for developing and implementing a test drive adjustment strategy based on a rule engine according to claim 1, characterized in that, In step 3, the rule engine periodically traverses all policy rules in the rule base. Policies that meet the triggering conditions will provide corresponding handling results and troubleshooting solutions according to the edited content. High-priority policies will cover low-priority policies, and the final results will be displayed and selected by the user in a pop-up window.
10. A test run adjustment strategy development and operation system based on a rule engine, characterized in that, This includes a standardized strategy development module and an automated execution module; The strategy standardization compilation module is used to compile standardized process documents for strategies. It divides strategies with different contents into four modules: trigger timing, adjustment calculation, result handling, and troubleshooting plan. It uses the parameter indicators, adjustable parts and controller parameter information entered before the test run based on the actual status of the test bench equipment to complete the compilation of strategy content, thereby forming a rule file that can be used for the automated operation of the strategy. The automated strategy operation module stores all compiled and activated strategy rule files into the rule library, receives multi-signal input data from the test bench data acquisition system, engine controller, and intelligent sensing system, and automatically identifies and triggers strategies that meet the corresponding trigger conditions through the rule engine, providing the compiled strategy handling operations and troubleshooting solutions.