Model-Driven Data Integration Architecture for Platform Interoperability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current data integration technologies lack interoperability and a common reference architecture, leading to inefficiencies in migrating integration processes across different platforms, resulting in data fragmentation and high computational costs due to the rigidity of existing solutions.

Innovation Solution

A method utilizing model-driven common reference data integration architecture and primitive foundational components to compose platform-specific integration tools, enabling easy migration by modeling data at multiple abstraction levels, translating queries, and representing data flow graphs for seamless integration across various technologies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If proprietary integration technologies are used, then specific integration functions are achieved, but interoperability between different platforms is lost

Engineering Contradiction:

Improveintegration function reliabilityVSAvoidplatform interoperability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a common reference architecture as an intermediary layer between proprietary integration technologies and data sources. This reference architecture acts as a mediator that enables interoperability while preserving the reliability of specific integration functions through standardized interfaces and abstraction layers.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the integration system into distinct layers: a platform-independent common reference architecture layer and platform-specific implementation layers. This segmentation allows each layer to be optimized independently, maintaining reliability at the implementation level while achieving interoperability at the reference architecture level.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If integration processes are migrated between platforms, then adaptability to different technologies is improved, but time and effort consumption increase

Engineering Contradiction:

Improveplatform migration capabilityVSAvoidmigration time and effort

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent creates a platform-independent representation of integration processes through the common reference architecture. This representation serves as a copy that can be transported between platforms without requiring complete recreation, significantly reducing migration time and effort while maintaining adaptability.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent establishes a standardized common reference architecture in advance that defines universal interfaces and data models. This preliminary action enables seamless migration between platforms by ensuring that integration processes are designed to work with the reference architecture from the beginning, eliminating the need for extensive rework during migration.

Inventive Principle:

Principle #10Preliminary action

3Ease of operation

If ad-hoc quick-fix solutions are implemented, then immediate problems are resolved, but data fragmentation and inconsistencies increase

Engineering Contradiction:

Improvequick implementationVSAvoiddata consistency

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent makes the common reference architecture universal and multi-functional, capable of handling various integration scenarios through standardized mechanisms. This allows quick-fix solutions to be implemented using the same reference architecture rather than ad-hoc approaches, ensuring data consistency while maintaining ease of operation.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Reliability

If synchronization mechanisms are added to prevent data inconsistencies, then data reliability is improved, but system complexity increases

Engineering Contradiction:

Improvedata consistencyVSAvoidsynchronization system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The common reference architecture acts as an intermediary that centralizes synchronization and consistency management. By handling data consistency through the reference architecture layer rather than through complex point-to-point synchronization mechanisms, the system achieves reliable data consistency with reduced overall complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10606861B2Method for building data integration tools to facilitate interoperability of data integration solutions among data integration platforms

Publication Date: 2020.03.31 TATA CONSULTANCY SERVICES LTD

AI summary

A method facilitating interoperability across the integrating platforms is provided by composing purpose specific integrating tools using conceptual modeling framework and a set of primitive foundational components. The model driven architecture provides easy migration from one solution architecture to another. Also, the present invention discloses a method to migrate from one implementation to another using set of composed purpose specific integration tools.