Generic Rule-Based Engine for Network Policy Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network management systems rely on undocumented 'nerd knobs' for implementing rules, leading to confusion, misuse, and high costs due to hardwired logic that requires frequent software modifications, making customization and troubleshooting difficult.
Innovation Solution
A generic rule-based system that allows operators to set arbitrary policies based on predefined events, conditions, and actions, stored in a memory accessible by the router operating system, enabling uniform and documented coding, and easy customization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If specific hardwired logic is used to implement rules, then the system can execute predefined actions reliably, but any modification requires new CLI or software modifications which increase cost and delay implementation
Solution Approach 1:
The patent implements a dynamic rule configuration system where operators can modify rules at runtime without requiring software recompilation or new CLI commands. The system transitions from static hardwired logic to dynamic configurable policies, allowing rules to be added, modified, or removed through a standardized interface that compiles into executable form without requiring core software changes.
Solution Approach 2:
The patent creates a universal rule configuration framework that can handle multiple types of network events, conditions, and actions through a single standardized system. Instead of having separate hardwired logic for each specific function, the system provides a general-purpose rule engine that can be configured to perform various network management tasks through uniform policy definitions.
2Adaptability or versatility
If undocumented 'nerd knobs' are used for implementing rules, then operators can customize network behavior, but the CLI becomes confusing and troubleshooting becomes difficult
Solution Approach 1:
The patent transforms the operational interface from obscure undocumented parameters to a structured system with documented event types, condition parameters, and action options. Operators interact with named concepts rather than hidden CLI switches, making the system self-documenting through the configuration structure itself while maintaining full customization capability.
Solution Approach 2:
The patent introduces a standardized rule configuration interface that acts as an intermediary between operator intent and system execution. This intermediary layer provides a uniform, documented way to express network policies without exposing operators to the complexity of underlying hardwired logic, while still enabling full customization through the rule definition mechanism.
3Adaptability or versatility
If frequent software modifications are made to implement new rules, then the system can adapt to new requirements, but costs increase and propagation through IOS is delayed
Solution Approach 1:
The patent pre-compiles rule definitions into executable form during system initialization or configuration loading, rather than requiring software re compilation for each rule change. The rule configuration language is translated into optimized executable code in advance, allowing rapid deployment of new rules without time-consuming software modification and propagation cycles.
Data Source
AI summary
A system and method for providing a rule based engine in a routing operating system. The system includes a set of predefined events, a set of predefined conditions and a set of predefined actions. An operator of an operating system may generate a new rule by selecting one of the predefined events, a predefined condition to be tested and an action to perform in response to an outcome of the test of the condition. The rule is then stored in memory by a router operating system and is performed when the predefined event occurs.