Live Rule Deployment with Automated Package Manager

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional rule deployment systems require significant time and manual intervention, making it difficult for rule writers to author and test new rules due to the lengthy process of populating data tables or databases, which can delay the deployment of rules necessary for fraud detection and network security.

Innovation Solution

A method and system for live rule deployment with a deployment log, allowing rule writers to initiate rule package updates without developer assistance, where a rules package manager automatically updates the rules engine with new packages, tracked for auditing and roll-back purposes, using a configuration service to identify and retrieve the latest rules package.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If developers manually populate data tables or databases before rule writers can author rules, then data accessibility for rule authoring is improved, but deployment time and complexity increase significantly

Engineering Contradiction:
ImproveRule authoring accessibilityVSAvoidDeployment time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system pre-populates data tables or databases with test data before rule writers need to author rules. This preliminary preparation eliminates the waiting period that previously existed, allowing rule writers to immediately access data and begin authoring rules without being blocked by development cycles.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A deployment server acts as an intermediary between the development environment and the rules engine. The deployment server receives rule packages from developers, automatically deploys them to the rules engine, and manages the data population process. This intermediary automates the previously manual process, reducing both time and complexity while maintaining data accessibility for rule writers.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If developers and engineers manually compile and deploy rules to servers, then deployment control and tracking are improved, but deployment complexity and manual intervention requirements increase

Engineering Contradiction:
ImproveDeployment controlVSAvoidDeployment process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The deployment server provides self-service functionality by automatically receiving rule packages from developers and deploying them to the rules engine without requiring manual intervention from developers or engineers. The system autonomously manages the deployment process, including package validation, transmission, and installation, while maintaining deployment logs for tracking and control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms through deployment logs that record each deployment event, including timestamps, package identifiers, and deployment status. This automated feedback loop provides reliable tracking and control of deployments without adding manual steps, allowing the system to monitor and manage the deployment process automatically.

Inventive Principle:
Principle #23Feedback

3Manufacturing precision

If rule deployment requires sequential manual steps involving multiple personnel, then deployment accuracy and verification are improved, but productivity and response time decrease

Engineering Contradiction:
ImproveDeployment accuracyVSAvoidRule update speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system replaces the mechanical process of manual rule deployment with an automated electronic system. The deployment server automatically transmits rule packages from the development environment to the rules engine, eliminating the need for manual copying, pasting, or configuration steps. This substitution maintains deployment accuracy through automated validation while dramatically increasing rule update speed and productivity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If developers populate data tables during development cycles, then data quality and completeness for rule testing are improved, but time to market for new rules increases

Engineering Contradiction:
ImproveData qualityVSAvoidTime to market
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary data population during the development cycle, preparing high-quality test data in advance. This allows rule writers to immediately begin authoring and testing rules with complete, accurate data without waiting for the traditional development cycle to conclude, thereby reducing time to market while maintaining data quality.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10152315B1Live rule deployment with deployment log
Publication Date: 2018.12.11 INTUIT INC
  • US10152315B1 patent drawing
  • US10152315B1 patent drawing
  • US10152315B1 patent drawing

AI summary

The invention relates to a method for live rule deployment with a deployment log. The method includes executing rules of a first rules package in response to one or more requests from applications. Also, the method includes receiving an identifier. The identifier is received from a configuration service, and the identifier identifies a location from which a latest rules package can be obtained. The method further includes determining, using the identifier, that a new rules package is available for deployment. Still yet, the method includes, in response to determining that the new rules package is available, requesting, using the location, a second rules package from a rules package manager. Further, the method includes receiving the second rules package from the rules package manager, and replacing the first rules package with the second rules package by deploying the second rules package.