Live Data Streaming for Business Rule Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for testing business rules in transaction authorization and decisioning systems face challenges such as high overhead costs, inaccurate representations of production environments, and risks to live customers due to the need for additional computing resources and manual creation of test cases, which can lead to incomplete or faulty testing.

Innovation Solution

A system that configures a test job to receive and execute new business rules using live production data in real-time, comparing test authorization determinations with production determinations to identify differences, and automatically releasing rules to production if within a threshold, thereby minimizing computing costs and ensuring accurate testing without impacting live production environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a stand-alone testing environment is used to test business rules, then testing can be performed, but significant overhead is required due to additional computing resources and data transformation needs

Engineering Contradiction:
Improvetesting accuracyVSAvoidcomputing resources
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the testing environment with the production environment by allowing test jobs to execute directly against live production data through a streaming data platform. This eliminates the need for separate testing infrastructure and data transformation processes, reducing computing overhead while maintaining testing accuracy through direct access to real production data streams.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The production environment is given multiple functions: it simultaneously handles live authorization decisions and business rule testing. The streaming data platform enables the same production data to serve both operational purposes and testing purposes, eliminating redundant infrastructure and reducing overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Measurement precision

If production data is used for testing, then accurate representation of real-time environment is achieved, but personal and sensitive information must be redacted

Engineering Contradiction:
Improvetesting accuracyVSAvoiddata processing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by establishing security protocols and data access controls before testing begins. The streaming data platform implements real-time data masking and access restrictions that protect sensitive information while allowing testing to proceed with accurate production data. This preliminary setup eliminates the need for post-hoc redaction while maintaining security.

Inventive Principle:
Principle #10Preliminary action

3Speed

If new business rules are released to beta environment with live production traffic, then real-time testing is achieved, but significant risks are posed to live customers and authorization determinations

Engineering Contradiction:
Improvetesting speedVSAvoidcustomer risk
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The patent segments the testing process from live customer impact by using a monitoring mode where test jobs execute against production data streams but do not actually affect customer authorizations. The system separates the data flow for testing from the decision flow for customers, allowing rapid testing while isolating customers from potential rule defects through architectural boundaries.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The streaming data platform acts as an intermediary that enables testing without exposing customers to risks. It captures production data for testing purposes while maintaining separate, protected pathways for actual authorization decisions. This intermediary layer allows the system to observe and test rule behavior with real data without allowing untested rules to directly impact customer transactions.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If manual test cases are created to test business rules, then comprehensive testing can be performed, but it is difficult and time consuming requiring technical expertise

Engineering Contradiction:
Improvetesting completenessVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service testing by automatically generating test cases from production data streams and rule definitions. The streaming platform continuously feeds real production transactions to the testing engine, which automatically executes rules against actual data without requiring manual test case creation. This self-service approach maintains comprehensive testing coverage while eliminating the time-consuming manual effort and specialized expertise previously required.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The testing process operates continuously by maintaining an ongoing stream of test executions against live production data. Rather than performing discrete, manual testing sessions, the system continuously processes production data through the testing engine, ensuring comprehensive coverage of all rule scenarios as they naturally occur in production without interruption or manual intervention.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS12093964B2Automated rules execution testing and release system
Publication Date: 2024.09.17 CAPITAL ONE SERVICES LLC
  • US12093964B2 patent drawing
  • US12093964B2 patent drawing
  • US12093964B2 patent drawing

AI summary

Systems, methods, apparatuses, and computer-readable media are provided for rules execution testing using live production data. Live production authorization requests may be received at a production computing device. Production authorization decisions may be determined at the production computing device for the live production authorization requests using a set of production rules. The production authorization requests, data used to arrive at the corresponding production authorization decisions, and/or the corresponding authorization decisions may be streamed in real-time to a test device. Test authorization decisions may be determined at the test device for the received live production authorization requests using the received data used to arrive at the production authorization decisions, and using a set of test rules. Production and test authorization decisions may be compared to determine decision differences. One or more user interfaces or reports may be generated for outputting the decision differences.