Validation Rule Management Across Shared Replicated Database Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Financial institutions face risks due to delayed transaction posting times and unshared knowledge among entities, allowing customers to exploit these delays for fraudulent activities like over-borrowing, as existing validation systems rely on third-party services that are time-consuming and lack real-time replication of validation rules across nodes.

Innovation Solution

Implementing a method to automatically manage validation rules across a shared replicated database, where each entity controls the creation and replication of validation rules at the time of transaction, ensuring real-time validation and prevention of fraudulent activities by replicating these rules across all nodes in the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If entities use separate databases without real-time sharing, then each entity can independently manage its transactions, but customers can exploit the lack of shared knowledge to engage in fraudulent activities like over-borrowing

Engineering Contradiction:
Improvetransaction validation reliabilityVSAvoidtransaction information sharing
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent merges separate entity databases into a shared replicated database system where multiple entities access a common data source. This combining of previously separate information systems enables real-time visibility of customer transactions across entities, preventing over-borrowing by ensuring all entities see the same customer credit information simultaneously.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system implements feedback mechanisms where validation rules are automatically applied and results are immediately reflected across all nodes. When one entity validates a transaction against customer credit limits, this validation information feeds back to other entities in real-time, allowing them to adjust their validation decisions based on the latest customer transaction status.

Inventive Principle:
Principle #23Feedback

2Reliability

If entities implement real-time validation rule replication across all nodes, then fraudulent activities can be prevented, but system complexity and implementation difficulty increase

Engineering Contradiction:
Improvefraud prevention capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal validation rule system that serves multiple entities simultaneously through a single shared database. Rather than implementing separate validation systems at each entity, one multi-functional validation framework handles credit checks, transaction limits, and fraud prevention for all participating entities, reducing overall system complexity despite the distributed architecture.

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

Solution Approach 2:

The system uses database replication to create copies of the shared database at each node, allowing entities to access local copies for fast validation while maintaining data consistency. This copying approach enables real-time validation without requiring complex inter-node communication for every transaction check, simplifying the system architecture while maintaining fraud prevention capabilities.

Inventive Principle:
Principle #26Copying

3Reliability

If third-party validation services are used, then validation rules can be established, but transaction processing time increases due to delayed posting and lack of real-time replication

Engineering Contradiction:
Improvevalidation rule enforcementVSAvoidtransaction processing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the validation rule enforcement functionality from external third-party services and embeds it directly into the shared database system at each entity node. This extraction eliminates the need for external validation requests and delays, allowing entities to enforce validation rules independently and immediately using locally stored validation logic and customer transaction data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary validation by pre-loading validation rules and customer transaction histories into the shared replicated database before transactions occur. This preliminary preparation allows entities to conduct instant validation checks without real-time external service calls, significantly improving transaction processing speed while maintaining reliable validation rule enforcement.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10114854B2Validation rule management across entities
Publication Date: 2018.10.30 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10114854B2 patent drawing
  • US10114854B2 patent drawing
  • US10114854B2 patent drawing

AI summary

One embodiment provides a method of automatically managing a validation rule across a shared replicated database, the method including: utilizing at least one processor to execute computer code that performs the steps of: receiving, at a database, a first transaction associated with a user, wherein the database is associated with a node of a network comprising a plurality of nodes and wherein each of the plurality of nodes is associated with a different entity; the database being shared and replicated among the plurality of nodes; receiving, at the database, a validation rule associated with the first transaction, wherein the validation rule comprises at least one condition associated with the user; and automatically replicating the validation rule throughout the plurality of nodes. Other aspects are described and claimed.