JSON Structure Flattening for Faster Parsing With Less Redundancy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing JSON data processing methods that flatten hierarchical structures to improve parse performance often result in increased redundancy and user difficulty in maintaining and updating the data.

Innovation Solution

A method for optimizing JSON data structure by partially flattening data objects, preserving a hierarchical structure where necessary, using machine learning techniques to identify and selectively flatten or refrain from flattening based on similarity and user behavior.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If hierarchical JSON structures are flattened to improve parse performance, then processing speed is improved, but data redundancy increases and data maintenance becomes more difficult

Engineering Contradiction:
Improveparse performanceVSAvoiddata redundancy
Core Design Contradiction:
ProductivityVSLoss of substance

Solution Approach 1:

The patent applies partial flattening by selectively flattening only certain hierarchical levels or specific JSON objects based on analysis criteria, rather than flattening the entire structure. This partial action achieves performance improvement for critical paths while preserving hierarchical structure elsewhere to minimize redundancy

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent implements different structural treatments for different parts of the JSON data based on local characteristics. Some regions are flattened while others maintain hierarchy, creating local quality variations optimized for their specific access patterns and data characteristics

Inventive Principle:
Principle #3Local quality

2Productivity

If hierarchical JSON structures are flattened to improve parse performance, then processing speed is improved, but ease of operation deteriorates

Engineering Contradiction:
Improveparse performanceVSAvoiddata maintenance
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

By applying partial flattening rather than complete flattening, the patent maintains hierarchical structure in regions where data maintenance is frequent, thus preserving ease of operation for those critical sections while still achieving performance benefits in other areas

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent creates local quality variations where frequently accessed or maintained data retains hierarchical structure for ease of operation, while less frequently accessed data is flattened for performance optimization

Inventive Principle:
Principle #3Local quality

3Productivity

If complete flattening is applied to all JSON objects, then parse performance is improved, but unnecessary redundancy increases

Engineering Contradiction:
Improveparse performanceVSAvoidunnecessary redundancy
Core Design Contradiction:
ProductivityVSLoss of substance

Solution Approach 1:

The patent implements partial flattening by selectively applying the flattening operation only to certain JSON objects or hierarchical levels that meet specific criteria, avoiding complete flattening of all data and thus preventing unnecessary redundancy in regions where it is not needed

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the structural parameter (hierarchical vs. flat) selectively based on analysis results, applying different structural configurations to different parts of the data based on their access patterns, size, and importance characteristics

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12566778B2Optimizing JSON structure
Publication Date: 2026.03.03 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12566778B2 patent drawing
  • US12566778B2 patent drawing
  • US12566778B2 patent drawing

AI summary

Computer-implemented methods for optimizing the structure of JSON data are provided. Aspects include receiving first JavaScript Object Notation (JSON) data, where the first JSON data includes a plurality of data objects. Aspects also include generating, based on the first JSON data, second JSON data. The second JSON data includes one or more flattened data objects, where the one or more flattened data objects correspond to one or more first data objects of the first JSON data and are absent a hierarchical structure. The second JSON data includes one or more non-flattened data objects, where the one or more non-flattened data objects correspond to one or more second data objects of the first JSON data.