Multi-Platform Integration Framework Using Canonical Data Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business technical solutions with tightly coupled business logic face challenges in efficiency and flexibility when modifying or upgrading, especially when dealing with disparate data sources and legacy software systems, which limits the ability to deliver updated products.

Innovation Solution

A method and system for integrating applications with distributed platforms and external services in a modular and reusable manner by receiving request messages, transforming data into target formats, and persisting it, using configuration files to map data to canonical objects, and outputting it to associated platforms, while allowing for lazy-loading and caching.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If business logic is tightly coupled with specific technical implementation, then the system can operate efficiently on a specific platform, but modifications and upgrades become difficult and time-consuming

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidflexibility for modifications
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the system into distinct layers: business logic layer and technical implementation layer. The business logic is separated from platform-specific code through the use of abstract base classes and interface definitions, allowing independent modification of each layer without affecting the other.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer consisting of abstract base classes and configuration files that mediate between business logic and technical implementation. This intermediary enables loose coupling by providing a standardized interface that shields business logic from technical changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If legacy software systems are upgraded to new technology platforms, then the system can access modern features and improved performance, but business logic modifications and regression testing are required

Engineering Contradiction:
Improvesystem accessibilityVSAvoidtime for testing and modification
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by defining abstract base classes and data mappings in advance, before platform-specific implementation details are needed. This allows business logic to be developed and tested independently of the target platform, reducing regression testing requirements during upgrades.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates universal business logic that can operate across multiple platforms through standardized interfaces and configuration-driven data mapping. The same business logic layer can serve different technical implementations, enabling seamless platform upgrades without business logic modifications.

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

3Adaptability or versatility

If data from disparate sources is integrated, then the system can provide comprehensive business solutions, but maintaining accessibility and usability becomes challenging

Engineering Contradiction:
Improvedata source integrationVSAvoidaccessibility and usability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent applies local quality by handling data transformation and mapping specific to each data source through configuration files and platform-specific adapters, while maintaining a unified view in the business logic layer. Each data source can have its own characteristics handled locally without affecting overall system usability.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent introduces data mapping and transformation layers as intermediaries between disparate data sources and the business logic. These intermediaries standardize data formats and structures, allowing comprehensive data integration while maintaining consistent accessibility and usability across all data sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20210026714A1Method and system for implementing a multi-platform framework for shared services
Publication Date: 2021.01.28 JPMORGAN CHASE BANK NA
  • US20210026714A1 patent drawing
  • US20210026714A1 patent drawing
  • US20210026714A1 patent drawing

AI summary

A method for integrating an application with a platform is provided. The method includes: receiving, from the application, a request message and at least one configuration file; extracting, from the request message, a first set of raw data; using information included in the configuration file to transform the extracted raw data into a target format and to persist the extracted raw data into a database; mapping a subset of the extracted raw data to a predetermined canonical object; and outputting the transformed data to a predetermined destination that is associated with the platform.