Configurable ETL Framework for External Data Transformations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing ETL frameworks require developers to write custom code for each data transformation operation, limiting flexibility and scalability, and do not support new transformations without modifying the framework.

Innovation Solution

An ETL framework with reusable modules and configuration files that include variables and external command data, allowing execution of new transformations via SQL statements or external modules without modifying the framework, while imparting native properties to these modules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers write custom code for each ETL operation, then the framework can perform data transformations, but the complexity of the system increases and flexibility decreases

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

Solution Approach 1:

The patent uses templates to define ETL operations. Instead of writing custom code for each operation, developers create template definitions that can be reused and configured through configuration files. The system copies and instantiates these templates with specific parameters, eliminating the need to write repetitive custom code while maintaining flexibility.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent creates a universal ETL framework where a single template definition can serve multiple purposes through configuration files. The same template can be instantiated with different parameters to perform various data transformations, making the system multi-functional without requiring separate custom code for each operation.

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

2Adaptability or versatility

If the framework supports new data transformations, then functionality improves, but the framework requires modification which reduces stability

Engineering Contradiction:
ImprovefunctionalityVSAvoidframework stability
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent segments the ETL framework into distinct components: template definitions, configuration files, and execution engine. New data transformations can be added by creating new template definitions or configuration files without modifying the core framework code, thus maintaining framework stability while improving functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces configuration files as an intermediary layer between the framework and data transformations. This intermediary allows new transformations to be defined and configured without modifying the framework itself, enabling functionality expansion while preserving framework stability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If custom code is written for each ETL operation, then specific transformations can be performed, but developer effort and time increase

Engineering Contradiction:
Improvedeveloper efficiencyVSAvoiddevelopment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by creating template definitions that encapsulate common ETL operation patterns. These templates are prepared in advance and can be directly instantiated through configuration files, eliminating the need for developers to write custom code for each operation and significantly reducing development time.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If the framework is modified to support new transformations, then adaptability improves, but the risk of errors increases

Engineering Contradiction:
ImproveadaptabilityVSAvoiderror risk
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent extracts the transformation logic from the framework code into separate template definitions and configuration files. This extraction allows new transformations to be added without modifying the framework, thereby maintaining reliability while improving adaptability.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20250291810A1System and method for expanding a data transfer framework
Publication Date: 2025.09.18 THE TORONTO DOMINION BANK
  • US20250291810A1 patent drawing
  • US20250291810A1 patent drawing
  • US20250291810A1 patent drawing

AI summary

Apparatus and methods for expanding a data transfer framework are disclosed. Exemplary implementations may: provide an ETL framework comprising a plurality of ETL modules and comprising code including variables; obtain a configuration file including data values to replace the variables for executing selected ETL modules, and including external command data configured to execute a new data transformation external to and absent from the ETL framework, the external command data including a reference to an external module generated in relation to an external interface; and execute the one or more selected ETL modules based on the code, the data values and the external command data. Exemplary implementations provide a flexible and expandable ETL framework that enable a new type of data transformation that is not currently supported by the framework, without having to modify the framework. The framework may impart native properties and characteristics of the framework to the external module.