Multi-Dimensional Data Storage for Time Series Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems managing large volumes of time series data, such as IoT networks, face scalability limitations due to hardware constraints and high costs, often requiring distributed software architectures that complicate data processing and storage.

Innovation Solution

A scalable data processing and management architecture using a multi-dimensional data storage structure with time-ordered data partitions and sequence numbers for parallel processing and efficient data operations, allowing for streamlined data ingestion, storage, and retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If distributed software architectures are implemented to manage large volumes of time series data, then scalability is improved, but system complexity increases

Engineering Contradiction:
ImprovescalabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides time series data into discrete time intervals (buckets) and further segments them into manageable partitions. Each partition contains data for a specific time range and can be independently processed, stored, and queried. This segmentation enables horizontal scalability by allowing data to be distributed across multiple nodes while maintaining simple, consistent access patterns within each partition.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces multiple dimensions for organizing time series data: time intervals (buckets), device identifiers, and metric types. By adding these dimensional layers, the system achieves scalability without increasing operational complexity, as each dimension provides an independent axis for data organization and query optimization.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If data is stored in time-ordered partitions, then data retrieval efficiency is improved, but storage structure complexity increases

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoidstorage structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Data is pre-organized into time-ordered partitions and buckets during the ingestion phase. This preliminary organization enables efficient range queries and time-based filtering without requiring complex sorting or scanning operations at query time. The partitioning structure is established in advance, allowing rapid data retrieval while maintaining a systematic storage layout.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If parallel processing is implemented during data ingestion and retrieval, then processing speed is improved, but coordination complexity increases

Engineering Contradiction:
Improveprocessing speedVSAvoidcoordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments data into independent partitions that can be processed in parallel across multiple compute nodes. Each partition is self-contained with its own time range and data set, eliminating the need for complex inter-node coordination during processing. This segmentation enables straightforward parallelization while maintaining data consistency through independent processing of discrete units.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12093286B2Time series data management systems and methods
Publication Date: 2024.09.17 INTERTRUST TECH CORP
  • US12093286B2 patent drawing
  • US12093286B2 patent drawing
  • US12093286B2 patent drawing

AI summary

This disclosure relates to, among other things, scalable data processing, storage, and/or management systems and methods. Certain embodiments disclosed herein provide for a multi-dimensional data storage structure that may facilitate parallel processing of data during both data ingestion and data retrieval and/or access processes involving one or more storage layers In various embodiments, sequence number schemes associated with ingested data records may allow for improved management of data stored in one or more layers (e.g., hot and/or cold data storage layers).