Source-to-Target Data Validation Using Hash, Schema, and Count Checks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in validating complete data sets during transfers between different databases and automating data comparison for multiple entities.

Innovation Solution

A system and method for data validation that detects data transfers between sources and targets, compares data using hashes, schema, and count comparisons, and outputs validation results, which can be used for corrective actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data validation is performed during transfer between different databases, then data accuracy and reliability are improved, but system complexity and processing time increase

Engineering Contradiction:
Improvedata accuracyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a data validation service as an intermediary component that sits between the source and target databases. This service receives data transfer requests, performs validation operations using multiple comparison techniques (hash comparison, schema validation, count verification), and returns validation results. By mediating the validation process, the system improves data accuracy while managing complexity through a dedicated validation layer rather than embedding complex validation logic throughout the entire data transfer system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The validation process is segmented into distinct operational phases: detecting data transfer, comparing source and target data using multiple independent methods (hash comparison, schema validation, count verification), and generating validation results. Each segmentation handles a specific aspect of validation, allowing the system to maintain high reliability through comprehensive checking while managing complexity by dividing the validation task into manageable, independent components that can be executed sequentially or in parallel.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If comprehensive data comparison is performed using multiple validation methods, then validation precision is improved, but processing time and computational resources increase

Engineering Contradiction:
Improvevalidation precisionVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements a multi-method validation approach where hash comparison, schema validation, and count verification are performed to different degrees of thoroughness. Hash comparison provides a quick partial validation for entire data sets, schema validation checks structural compliance, and count verification ensures record numbers match. By applying multiple validation methods with varying levels of depth, the system achieves high validation precision while avoiding the need to perform every possible check at maximum thoroughness, thus managing processing time more effectively.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary validation actions by first detecting data transfer events and initiating validation processes before complete data transfer concludes. The validation service proactively compares data using multiple methods during the transfer process rather than waiting for complete transfer, then performs comprehensive validation. This preliminary action allows the system to identify discrepancies early while maintaining high validation precision, reducing overall processing time by avoiding post-transfer validation delays.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If automated validation and corrective actions are implemented, then productivity is improved, but device complexity increases

Engineering Contradiction:
Improveautomation efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements automated feedback mechanisms where the validation service continuously monitors data transfer operations, compares source and target data using multiple validation methods, and automatically generates corrective actions based on validation results. When discrepancies are detected, the system provides feedback to relevant components to trigger automated corrective measures such as data retransfer, error logging, or alert generation. This feedback loop improves productivity by eliminating manual validation and correction steps while managing complexity through standardized feedback protocols and automated decision-making rules.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The validation service operates as a self-service system that autonomously detects data transfer events, performs comprehensive validation using hash comparison, schema validation, and count verification, identifies discrepancies, and generates corrective actions without requiring manual intervention. The system serves itself by automatically managing the entire validation and correction workflow, from initiation to resolution. This self-service capability improves productivity by automating what would otherwise require human operators while managing complexity through centralized automation logic that handles all validation and correction tasks independently.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12405928B1System, method, and computer program for data validation during transfer of data from source to target
Publication Date: 2025.09.02 AMDOCS DEV LTD
  • US12405928B1 patent drawing
  • US12405928B1 patent drawing
  • US12405928B1 patent drawing

AI summary

As described herein, a system, method, and computer program are provided for data validation during transfer of data from source to target. A transfer of data from a source to a target is detected. The data transferred from the source is compared to data at the target resulting from the transfer. The transfer is validated based on a result of the comparison. A result of the validation is output.