Cloud Data Ingestion Accelerator for Automated Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data ingestion systems into cloud computing environments are time-consuming, often relying on manual processes, and face challenges with latency, accuracy, and complexity, particularly in ensuring timely and scalable data ingestion with appropriate metadata handling.

Innovation Solution

The introduction of an ingestion accelerator, a utility script that automates validation and population of technical settings within an ingestion framework, reducing validation time from days to hours, and enabling scalable, accurate, and efficient data ingestion through automated validation tasks and modular pipeline management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual processes are used for data ingestion, then accuracy can be maintained through human review, but the ingestion time increases significantly and scalability is limited

Engineering Contradiction:
Improveingestion accuracyVSAvoidingestion time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system implements self-service through automated validation rules and metadata extraction that perform ingestion verification without human intervention. The accelerator automatically validates data quality, checks metadata completeness, and enforces governance policies, replacing manual review processes while maintaining accuracy standards.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Manual mechanical review processes are replaced with automated computational validation systems. The accelerator uses algorithmic validation rules, pattern matching, and automated metadata extraction to perform functions previously requiring human analysts, thereby reducing ingestion time while preserving accuracy through systematic automated checking.

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

2Productivity

If automated systems are used for data ingestion, then processing speed and scalability improve, but errors can be propagated quickly and complexity increases

Engineering Contradiction:
Improveingestion speedVSAvoiderror propagation risk
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback through automated validation rules that check data quality metrics, metadata completeness, and governance policy compliance during ingestion. Validation results provide feedback that can trigger alerts, rollback failed ingestions, or require manual review before proceeding, preventing error propagation while maintaining high-speed automated processing.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The accelerator prepares validation rules, metadata schemas, and governance policies in advance before ingestion begins. This beforehand cushioning ensures that validation frameworks are ready to catch errors immediately, preventing problematic data from being ingested and propagated through the system, thereby maintaining reliability at scale.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Measurement precision

If comprehensive validation is performed on all data, then ingestion accuracy improves, but the time required for validation increases

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

Solution Approach 1:

The system applies partial validation by prioritizing critical validation rules for high-risk data types and less stringent validation for low-risk data. The accelerator performs essential validation checks on all data while applying comprehensive validation only where necessary, balancing accuracy requirements with time constraints through selective validation intensity.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

Different validation strictness levels are applied to different data types, sources, and destinations based on their risk profiles and business requirements. Critical financial data receives comprehensive validation while less sensitive operational data receives streamlined validation, optimizing the balance between accuracy and speed through localized validation quality adjustments.

Inventive Principle:
Principle #3Local quality

4Adaptability or versatility

If cloud computing resources are provisioned on-demand, then scalability is improved, but coordination complexity and provisioning time increase

Engineering Contradiction:
ImprovescalabilityVSAvoidprovisioning complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The accelerator implements universal provisioning templates that can be applied across multiple cloud environments and data types. These templates encapsulate common validation rules, metadata requirements, and governance policies that work across diverse scenarios, reducing provisioning complexity while maintaining scalability through reusable standardized configurations.

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

Solution Approach 2:

Validation frameworks, metadata schemas, and governance policies are prepared and validated in advance before actual data ingestion begins. This preliminary action ensures that provisioning complexity is resolved beforehand, allowing on-demand cloud resources to be allocated and configured quickly without ad-hoc complexity during the ingestion process itself.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250094406A1System and Method for Ingesting Data onto Cloud Computing Environments
Publication Date: 2025.03.20 THE TORONTO DOMINION BANK
  • US20250094406A1 patent drawing
  • US20250094406A1 patent drawing
  • US20250094406A1 patent drawing

AI summary

A system, device and method are provided for ingesting data onto cloud computing environments. The illustrative method includes providing an accelerator in a cloud computing environment for ingestion of data into the cloud computing environment. The method includes automatically, with the accelerator (1) verifying that one or more templates defining ingestion parameters are populated on the cloud computing environment, (2) verifying that resources in a target destination in the cloud computing environment have been provisioned, (3) populating, based on the one or more templates, and with a pipeline of tasks, one or more configuration reference destinations for transforming raw data into a format compatible with the provisioned target destination. The method includes ingesting a data file into the verified target destination in the cloud computing environment based on the verified one or more templates and populated configuration reference destinations.