Schema-Agnostic Data Mapping for JSON Schema Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Information handling systems face challenges in processing and mapping data between different JSON data schemas, particularly when dealing with unspecified schemas from product suppliers and defined schemas used by data center services providers, which can lead to compatibility issues and increased complexity in data management and retrieval.

Innovation Solution

A method and system for performing data schema mapping operations, involving the receipt of product information in an unspecified JSON schema, identification of components within this schema, and mapping these components to corresponding components in a defined schema associated with a data center services provider, often linked to a relational database, using schema-agnostic data access APIs to facilitate seamless data integration and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data schema mapping operations are performed between unspecified JSON schemas from product suppliers and defined schemas used by data center services providers, then data integration and compatibility between various data sources are improved, but the complexity of processing and mapping data between different schemas increases

Engineering Contradiction:
Improvedata compatibilityVSAvoidprocessing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary data schema mapping layer that sits between the unspecified JSON schemas from product suppliers and the defined schemas used by data center services providers. This intermediary layer automatically performs schema validation, transformation, and mapping operations, shielding the complexity from both data sources and consumers while ensuring data compatibility and integration.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If schema-agnostic data access APIs are used to facilitate seamless data integration, then ease of operation and data retrieval are improved, but the complexity of implementing and maintaining the mapping operations increases

Engineering Contradiction:
Improvedata access easeVSAvoidimplementation complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the schema mapping and validation logic into a separate, reusable component that can be independently developed, tested, and maintained. This extracted mapping layer is then exposed through simple, schema-agnostic APIs, allowing data access to remain easy while the complex mapping operations are handled by the separated component.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If data components from unspecified JSON schemas are mapped to defined schemas associated with relational databases, then data management efficiency is improved, but the time required for schema validation and mapping operations increases

Engineering Contradiction:
Improvedata management efficiencyVSAvoidmapping operation time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary schema validation and mapping rule establishment before actual data processing operations. By pre-defining mapping rules, validation schemas, and transformation logic in advance, the system reduces the time required for runtime mapping operations while maintaining data management efficiency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12007960B2Methods make web and business application data access agnostic to schema variations and migrations
Publication Date: 2024.06.11 DELL PROD LP
  • US12007960B2 patent drawing
  • US12007960B2 patent drawing
  • US12007960B2 patent drawing

AI summary

A system, method, and computer-readable medium are disclosed for performing a data schema mapping operation. The data schema mapping operation includes receiving product information from a product supplier, the product information comprising a first document corresponding to a first data schema, the first data schema comprising an unspecified JavaScript Object Notation (JSON) schema; identifying a plurality of components within the first document corresponding to the first data schema, the plurality of components comprising JSON data elements; identifying a second plurality of components corresponding to a second data schema, the second data schema comprising a defined data schema, the second data schema being associated with a data center services provider, at least some of the second plurality of components being associated with a relational database; and, mapping a component of the document corresponding to the first data schema to a component corresponding to the second data schema.