System and method for specifying rules for operational systems

Abstract

A method of controlling an operational system by a rules management system comprising a processor and a memory, and a computing apparatus comprising a processor and a memory are provided. The processor is programmed to execute rules from a rules repository stored on a memory in response to a request. The computing apparatus further comprises a high rules repository storing one or more high level rules, wherein each high level rule, when executed by the processor, modifies the effect of execution of one or more rules Rm in the rules repository; and a high rules conditions module that when executed by the processor identifies and executes the high level rules that apply to the request.

What is claimed is: 
     
         1 . A method of controlling a fraud prevention system by a rules management system comprising a memory storing instructions executed by a processor, the method comprising:
 providing, by the processor, one or more high level rules comprising a condition part and an effect part, wherein each of the high level rules, when executed, modifies the effect part of one or more rules in a rules repository stored in the memory;   validating, by a rule validation module implemented on the processor, that the one or more rules match the condition part of the one or more high level rules;   receiving, by a high rule conditions module implemented on the processor, a request to execute the one or more rules;   determining, by the high rule conditions module, the one or more high level rules apply to the request;   in response to determining the one or more high level rules apply to the request, identifying, by the rule validation module, one or more criteria indicating the one or more high level rules are not satisfied; and   in response to identifying the one or more criteria are not satisfied, preventing fraud at least by preventing the one or more high level rules from being deployed.   
     
     
         2 . The method of  claim 1 , further comprising:
 transmitting, by the rule validation module, a warning message to a rules management interface.   
     
     
         3 . The method of  claim 2 , wherein the preventing the one or more high level rules from being deployed and the transmitting the warning message collectively comprise a fraud prevention operation. 
     
     
         4 . The method of  claim 1 , wherein:
 the identified one or more criteria indicate the condition part, to be satisfied, of the one or more high level rules, and   identifying the one or more criteria are not satisfied comprises determining the condition part of the one or more high level rules is not satisfied.   
     
     
         5 . The method of  claim 1 , wherein preventing the one or more high level rules from being deployed comprises declining to execute the effect part of the one or more high level rules. 
     
     
         6 . The method of  claim 1 , further comprising verifying the provided one or more high level rules do not overlap or conflict with existing high level rules based on one high level rule of the one or more high level rules defining at least two required conditions,
 wherein no other high level rule of the one or more high level rules includes the defined at least two required conditions.   
     
     
         7 . The method of  claim 1 , further comprising:
 separating, by a rules parser, a high level rule of the one or more high level rules into the condition part and the effect part, and   sending, by the rules parser, the effect part to the rules repository and the condition part to the high rules condition module.   
     
     
         8 . A computing apparatus for controlling a fraud prevention system by a rules management system, the computing apparatus comprising:
 a processor;   a memory storing a rules repository, wherein the rules repository stores one or more high level rules comprising a condition part and an effect part, wherein each high level rule, when executed, modifies the effect part of one or more rules in the rules repository;   a rule validation module, implemented on the processor, configured to validate the one or more rules match the condition part of the one or more high level rules; and   a high rule conditions module, implemented on the processor, configured to:
 receive a request to execute the one or more rules, and 
 determine the one or more high level rules apply to the request, 
   wherein the rule validation module is further configured to:
 in response to the determination the one or more high level rules apply to the request, identify one or more criteria indicating the one or more high level rules are not satisfied; and 
 in response to the identification the one or more criteria are not satisfied, prevent fraud at least by preventing the one or more high level rules from being deployed. 
   
     
     
         9 . The computing apparatus of  claim 8 , wherein the rule validation module is further configured to:
 transmit a warning message to a rules management interface.   
     
     
         10 . The computing apparatus of  claim 9 , wherein the preventing the one or more high level rules from being deployed and the transmitting the warning message collectively comprise a fraud prevention operation. 
     
     
         11 . The computing apparatus of  claim 8 , wherein:
 the identified one or more criteria indicate the condition part, to be satisfied, of the one or more high level rules, and   to identify the one or more criteria are not satisfied, the rule validation module is further configured to determine the condition part of the one or more high level rules are not satisfied.   
     
     
         12 . The computing apparatus of  claim 8 , wherein, to prevent the one or more high level rules from being deployed, the rule validation module is further configured to decline to execute the effect part of the one or more high level rules. 
     
     
         13 . The computing apparatus of  claim 8 , wherein:
 the rule validation module is further configured to verify the provided one or more high level rules do not overlap or conflict with existing high level rules based on one high level rule of the one or more high level rules defining at least two required conditions, and   no other high level rule of the one or more high level rules includes the defined at least two required conditions.   
     
     
         14 . The computing apparatus of  claim 8 , further comprising a rules parser configured to:
 separate a high level rule of the one or more high level rules into the condition part and the effect part, and   send the effect part to the rules repository and the condition part to the high rules condition module.   
     
     
         15 . A rules management system for controlling a fraud prevention system by a rules management system, the system comprising:
 a processor; and   a memory comprising a rules repository, wherein the rules repository stores one or more high level rules comprising a condition part and an effect part, wherein each high level rule, when executed, modifies the effect part of one or more rules in the rules repository,   wherein the memory further comprises instructions that, when executed by the processor, cause the processor to:
 validate the one or more rules match the condition part of the one or more high level rules, 
 receive a request to execute the one or more rules, 
 determine the one or more high level rules apply to the request, 
 in response to the determination the one or more high level rules apply to the request, identify one or more criteria indicating the one or more high level rules are not satisfied, and 
 in response to the identification the one or more criteria are not satisfied, prevent fraud at least by preventing the one or more high level rules from being deployed. 
   
     
     
         16 . The rules management system of  claim 15 , wherein the processor is further configured to:
 transmit a warning message to a rules management interface,   wherein the preventing the one or more high level rules from being deployed and the transmitting the warning message collectively comprise a fraud prevention operation.   
     
     
         17 . The rules management system of  claim 15 , wherein:
 the identified one or more criteria indicate the condition part, to be satisfied, of the one or more high level rules, and   to identify the one or more criteria are not satisfied, the processor is further configured to determine the condition part of the one or more high level rules is not satisfied.   
     
     
         18 . The rules management system of  claim 15 , wherein, to prevent the one or more high level rules from being deployed, the processor is further configured to decline to execute the effect part of the one or more high level rules. 
     
     
         19 . The rules management system of  claim 15 , wherein:
 the processor is further configured to verify the provided one or more high level rules do not overlap or conflict with existing high level rules based on one high level rule of the one or more high level rules defining at least two required conditions, and   no other high level rule of the one or more high level rules includes the defined at least two required conditions.   
     
     
         20 . The rules management system of  claim 15 , wherein the processor is further configured to:
 separate a high level rule of the one or more high level rules into the condition part and the effect part.