Schema Generation for Integration Mapping Tasks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large schemas in integration systems lead to long processing times and inefficient user interface experiences due to the need for complete schema generation and transfer, making mapping tasks cumbersome and time-consuming.

Innovation Solution

A method that generates a modified schema by analyzing historical mappings to identify frequently used mappings, removing unnecessary portions, and providing only the most commonly used properties and metadata, thus reducing schema size and improving efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If complete schemas are provided for all sources and target objects, then mapping accuracy is improved, but processing time and data transfer time increase

Engineering Contradiction:
Improvemapping accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent extracts only the necessary portions of schemas that are actually needed for the mapping task at hand, rather than providing complete schemas. This is achieved by analyzing historical mappings to identify commonly used properties and metadata, then generating modified schemas that contain only those essential elements, thereby reducing processing time while maintaining mapping accuracy.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the complete schema into multiple parts based on historical usage patterns. By dividing the schema into commonly used portions and less frequently used portions, the system can provide only the relevant segments for each mapping task, reducing overall processing time while preserving the accuracy needed for successful mappings.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If complete schemas are transferred over HTTPS, then all possible mapping options are available, but data transfer time increases

Engineering Contradiction:
Improvemapping optionsVSAvoiddata transfer time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent extracts and transfers only the essential portions of schemas that are actually needed for the specific mapping task, based on historical analysis. This reduces the size of data transferred over HTTPS while maintaining adaptability by including all commonly used mapping options that have been proven effective in historical mappings.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If large schemas with many hierarchical levels are presented in UI, then complete mapping capabilities are provided, but user experience and ease of operation deteriorate

Engineering Contradiction:
Improvemapping capabilitiesVSAvoiduser experience
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent extracts and presents only the relevant portions of schemas in the user interface, based on historical mapping analysis. This removes unnecessary hierarchical levels and properties from the UI display, making the interface more manageable and easier to navigate while preserving complete mapping capabilities through the modified schema that includes all commonly used mapping options.

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If complete schemas are processed before UI rendering, then all mapping properties are available, but pre-processing time increases

Engineering Contradiction:
Improvemapping propertiesVSAvoidpre-processing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential properties and metadata needed for UI rendering based on historical mapping patterns. This reduces the pre-processing time required before UI rendering by eliminating unnecessary schema elements, while maintaining adaptability by including all commonly used mapping properties that users are likely to need.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20240248885A1Generating schema
Publication Date: 2024.07.25 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US20240248885A1 patent drawing
  • US20240248885A1 patent drawing
  • US20240248885A1 patent drawing

AI summary

Embodiments of the present invention provide concepts for a method for generating a schema describing a first node for performing mapping tasks. The method comprises obtaining an output schema for the first node. The method further comprises extracting, from the output schema, configuration data for the first node, wherein the configuration data includes an object and an action associated with the first node. The method further comprises analyzing a dataset of historical mappings to identify previous mappings that reference the object, or the action associated with the first node. The method further comprises generating a modified output schema describing the first node based, at least in part, on the identified previous mappings and the output schema, wherein the modified output schema is devoid of at least one portion of output schema.