Runtime Data Conversion Handler for Schema Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques for managing changes in data schema in computer applications are inefficient, requiring multiple data sets for each version of a program and not effectively utilizing storage resources, and struggle with backward and forward conversion during runtime execution.

Innovation Solution

A system that uses a serializer and a conversion handler to convert data schema during runtime execution, utilizing user-provided or automatic conversion information to transform data into compatible formats, allowing for efficient use of existing data sets and reducing storage burdens.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple independent data sets are loaded for each version of the computer program, then data compatibility with different program versions is achieved, but storage resource efficiency deteriorates and memory burden increases

Engineering Contradiction:
Improvedata compatibilityVSAvoidstorage resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple version-specific data sets into a single unified data set that can serve multiple program versions. Instead of maintaining separate data sets for each version, the system consolidates them into one shared data structure that all versions can access, thereby reducing storage resource consumption while maintaining data compatibility across versions.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified data set is designed to be universal and multi-functional, serving multiple program versions simultaneously. The data structure incorporates version identification and adaptive rendering capabilities, allowing the same data set to be appropriately interpreted and used by different program versions without requiring version-specific copies.

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

2Adaptability or versatility

If data conversion is performed during run-time execution, then flexibility in handling schema changes is improved, but system complexity increases

Engineering Contradiction:
Improveschema conversion flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by pre-defining conversion rules and data transformation logic during data set creation or compilation, before run-time execution. This allows the bulk of conversion complexity to be resolved in advance, reducing the actual run-time conversion overhead and simplifying the execution-phase system complexity while maintaining flexible schema adaptation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary conversion layer or adapter that mediates between the unified data set and the specific program version requirements. This intermediary component handles the schema conversion logic, isolating the complexity from both the data storage structure and the application logic, thereby managing system complexity while enabling flexible run-time conversion.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If version-specific data sets are maintained, then data accuracy for each program version is ensured, but backward and forward conversion efficiency deteriorates

Engineering Contradiction:
Improvedata accuracyVSAvoidconversion efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system employs parameter changes by incorporating version identification parameters and schema version tags within the unified data set structure. These parameters enable the system to dynamically adjust data rendering and conversion behavior based on the requesting program version, ensuring data accuracy for each version while avoiding the need for separate data sets, thereby maintaining high conversion efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10915507B1Data conversion handler for a run-time execution environment
Publication Date: 2021.02.09 AMAZON TECH INC
  • US10915507B1 patent drawing
  • US10915507B1 patent drawing
  • US10915507B1 patent drawing

AI summary

A method and apparatus for data conversion in a run-time execution environment are provided. In the method and apparatus, a data request specifying a second schema for requested data is received. A data portion is retrieved from a data store, whereby the retrieved data has a first schema. On a condition that the first schema and the second schema are determined to be different, the data portion is converted to the second schema to produce a converted data portion, whereby the conversion is performed based at least in part on data conversion information. The converted data portion is then provided to the run-time execution environment for use in a run-time execution of the computer program.