Byte-Sequence Data Storage for Compact JSON Decoding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data storage methods in different data tables lead to increased maintenance workloads and inefficient storage and decoding of serialized JSON data, causing storage waste and poor decoding efficiency.

Innovation Solution

A data storage system that stores data as a byte sequence with a first section containing label items and a second section for data, using a maptree structure to organize field identifiers and position labels, enabling efficient encoding and decoding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data of different structures are stored in different data tables, then data structure flexibility is improved, but maintenance workload increases and scalability deteriorates

Engineering Contradiction:
Improvedata structure flexibilityVSAvoidmaintenance workload
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges data of different structures into a unified data table, eliminating the need for multiple separate tables. This consolidation reduces maintenance complexity while preserving structural flexibility through a standardized storage format that can accommodate diverse data types.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal data storage solution that can handle multiple data structures within a single table. The standardized format serves multiple functions by accommodating different data types and structures without requiring separate storage mechanisms, thereby improving scalability and reducing maintenance overhead.

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

2Ease of operation

If serialized JSON data is stored uniformly in a data table, then storage simplicity is improved, but storage space increases and decoding efficiency deteriorates

Engineering Contradiction:
Improvestorage simplicityVSAvoidstorage space
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent segments the data storage into distinct components: a standardized header section containing metadata and a body section containing the actual data. This segmentation allows for more efficient storage by eliminating redundant elements in serialized JSON while maintaining simplicity through a structured format that is easier to parse and decode.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If serialized JSON data is stored uniformly in a data table, then storage simplicity is improved, but decoding efficiency deteriorates

Engineering Contradiction:
Improvestorage simplicityVSAvoiddecoding efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent performs preliminary organization of data into a standardized format with predefined headers and structured sections before storage. This preliminary action includes adding metadata, organizing fields, and establishing a consistent structure that enables faster decoding and querying operations, thereby improving productivity without sacrificing storage simplicity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12360974B2Systems and methods for data storage
Publication Date: 2025.07.15 SHANGHAI UNITED IMAGING METAHEALTHCARE CO LTD
  • US12360974B2 patent drawing
  • US12360974B2 patent drawing
  • US12360974B2 patent drawing

AI summary

The present disclosure may provide systems and methods for data storage. The systems may store data of one or more fields as a byte sequence. The byte sequence may include a first section and a second section. The second section may be configured to store the data of the one or more fields. The first section may be configured to store one or more label items corresponding to the one or more fields. For one of the one or more label items and a corresponding field, the label item may include a field label of the corresponding field and a position label of the corresponding field. The position label of the corresponding field may be configured to identify a position where data of the corresponding field is stored in the second section.