Data Serialization Mapping System for Cross-Platform Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data-serialization technologies face challenges in efficiently mapping and transforming structured data between different systems and programming languages, leading to inconsistencies and inefficiencies in data interchange.

Innovation Solution

A system that generates mapping expressions and executable code to transform source payloads into destination payloads by associating source data-serialization elements with destination data-serialization elements, using a graphical user interface to visually display and validate mapping associations, and an integration server to perform transformations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual mapping methods are used to map data-serialization elements between source and destination, then flexibility in handling different serialization formats is improved, but time consumption and operational complexity increase

Engineering Contradiction:
Improvehandling different serialization formatsVSAvoidtime consumption for mapping
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically generating mapping expressions and executable code before actual data transformation is needed. The mapping relationships between source and destination data-serialization elements are pre-established through automated analysis of serialization formats, eliminating the need for manual mapping configuration during runtime.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary component that automatically generates mapping expressions and executable code between source and destination systems. This intermediary translates and adapts data-serialization elements without requiring direct manual intervention, thereby reducing time consumption while maintaining adaptability to different formats.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If automated mapping generation is implemented, then productivity and speed of data transformation are improved, but system complexity increases

Engineering Contradiction:
Improvespeed of data transformationVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the complex mapping process into distinct components: generation of mapping expressions, generation of executable code, and the actual transformation execution. This segmentation allows each component to be independently managed and optimized, reducing overall system complexity while maintaining high productivity in data transformation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates copies of mapping expressions and executable code that can be reused across multiple data transformation operations. Instead of rebuilding mapping logic each time, the system replicates proven mapping configurations, thereby increasing productivity without proportionally increasing system complexity.

Inventive Principle:
Principle #26Copying

3Reliability

If comprehensive validation of mapping associations is performed, then data accuracy and reliability are improved, but processing time increases

Engineering Contradiction:
Improvedata accuracyVSAvoidvalidation processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs validation of mapping associations in advance, during the generation phase of mapping expressions and executable code. By validating mappings before actual data transformation, the system ensures data accuracy while minimizing the time impact on production transformations, as the validation occurs during the initial setup rather than during each data processing operation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250005035A1Mapping data-serialization elements between a source and a destination
Publication Date: 2025.01.02 ORACLE INT CORP
  • US20250005035A1 patent drawing
  • US20250005035A1 patent drawing
  • US20250005035A1 patent drawing

AI summary

A system may display a Graphical User Interface including a source region presenting a plurality of source data-serialization elements and a destination region presenting a plurality of destination data-serialization elements. The system may receive a user input associating a first destination data-serialization element, of the plurality of destination data-serialization elements, and a first source data-serialization element of the plurality of source data-serialization elements. Responsive to receiving the user input, the system may generate and store a mapping expression that defines a mapping association between the first source data-serialization element and the first destination data-serialization element. The system may present in a mapping region of the GUI displayed concurrently with the source region and the destination region, a mapping element representing the mapping association between the first source data-serialization element and the first destination data-serialization element.