Terminal Rule Engine Device for Localized Service Stability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The global application of rule operations in existing technologies leads to high risks during rule operation or update, as it burdens server resources and affects service stability, resulting in unreliable operation results that can cause negative effects across all terminals.
Innovation Solution
A terminal rule engine device is deployed on each terminal, featuring an interface module, management module, and operation module, which manages a device-level or user-level rule set using device or user identifiers to independently operate and update rules, reducing the risk by localizing rule operations and updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If rules are operated globally in the server, then service coverage is improved, but system reliability deteriorates
Solution Approach 1:
The patent segments the global rule operation system into terminal-level independent rule engines. Each terminal maintains its own rule set and execution context, isolating failures to individual terminals rather than propagating system-wide. This segmentation preserves service coverage while improving reliability through localized failure containment.
Solution Approach 2:
The patent implements copying by deploying rule engine instances to each terminal. Instead of a single centralized rule execution, multiple terminal-based rule engines copy the rule evaluation functionality locally. This allows independent operation at each terminal while maintaining consistent service coverage across the system.
2Extent of automation
If rules are operated globally in the server, then centralized control is improved, but server resource burden increases
Solution Approach 1:
The patent extracts rule execution functionality from the server and deploys it to terminals. By taking out the computational burden of rule evaluation from centralized servers and placing it at terminal level, the system reduces server resource consumption while maintaining automated rule operation capabilities.
Solution Approach 2:
Terminals perform self-service by executing rules locally using their own resources. Each terminal independently evaluates rules and determines service processing actions without requiring continuous server intervention. This self-service approach significantly reduces server resource burden while maintaining automated control.
3Ease of operation
If rules are operated globally in the server, then uniform policy application is improved, but operational risk increases
Solution Approach 1:
The patent segments policy application into terminal-level independent executions. While maintaining uniform rule definitions, each terminal independently executes rules with its own state and context. This segmentation limits operational risk to individual terminals while preserving consistent policy application across the system.
Solution Approach 2:
The patent implements prior cushioning by isolating terminal rule execution environments. Before failures can propagate system-wide, the independent terminal contexts act as a cushion, containing operational risks and preventing them from affecting other terminals or the overall system stability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present application discloses a terminal rule engine device and a terminal rule operation method, to alleviate a problem that the risk is relatively high during rule operation or rule update due to a global application of a rule operation method in the existing technology. The device is located on a terminal and includes an interface module, a management module, and an operation module. The interface module receives a rule operation request of a service. The management module manages a rule set of the service obtained from a server based on a device identifier and/or a user identifier corresponding to the terminal. The operation module, in response to the request received by the interface module, obtains a rule corresponding to the request from the rule set managed by the management module, generates a rule tree based on the obtained rule, obtains service data related to the rule tree, and determines an operation result of the rule based on the rule tree and the service data.