Hierarchical Data Containers Embedded in Objects

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional hierarchical data structures in parent-child type data tables are inefficient for storage and reconstruction, leading to performance degradation and unsuitability for embedding in objects, particularly in database storage, and result in inefficient versioning due to the need for extensive storage of historical data.

Innovation Solution

The implementation of hierarchical containers that can be embedded within objects, allowing for dynamic definitions and associations, enabling efficient storage and versioning by treating hierarchical relationships as traits within a composite data object, eliminating the need for external data structures and allowing for flexible database models.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If hierarchical data structures are stored in parent-child type data tables, then the data can be organized in a traditional hierarchical format, but the reconstruction time increases linearly with the number of nodes (O(n) queries required)

Engineering Contradiction:

Improvehierarchical data organizationVSAvoidreconstruction time

Core Design Contradiction:

Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent embeds hierarchical container data structures directly within composite data objects, nesting the hierarchical structure inside the object itself rather than storing it externally in separate tables. This allows the hierarchical relationship to be reconstructed in constant time O(1) by simply accessing the embedded container, eliminating the linear reconstruction time problem of traditional parent-child tables.

Inventive Principle:

Principle #7Nested doll (Nesting)

2Stability of the object's composition

If parent-child relationships are stored in external tables, then the hierarchical structure can be maintained, but the data structure becomes unsuitable for embedding in objects

Engineering Contradiction:

Improvehierarchical relationshipVSAvoidembeddability in objects

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent merges the hierarchical container data structure with the composite data object by embedding the container directly within the object. This combination allows the hierarchical structure to be both maintained and embedded in objects simultaneously, making the data suitable for object-oriented programming and eliminating the need for external table storage.

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If the entire historical data structure is maintained for versioning, then past versions can be examined, but extensive storage is required

Engineering Contradiction:

Improveversioning capabilityVSAvoidstorage requirements

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent creates snapshots of hierarchical container data structures at different versions, storing only the necessary version information rather than maintaining entire historical data structures. This copying approach allows versioning capability while significantly reducing storage requirements by only preserving essential version metadata.

Inventive Principle:

Principle #26Copying

4Quantity of substance

If traditional tabular implementations are used for hierarchical data, then the data can be stored in databases, but performance degradation occurs for large values of n

Engineering Contradiction:

Improvedata storage capacityVSAvoidperformance

Core Design Contradiction:

Quantity of substanceVSProductivity

Solution Approach 1:

The patent transitions from traditional two-dimensional tabular storage to a multi-dimensional embedded structure where hierarchical containers are nested within composite objects. This dimensional change allows constant-time O(1) access to hierarchical data regardless of the number of nodes, eliminating performance degradation for large datasets while maintaining storage capacity.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS10169376B2System and method of hierarchical data containers

Publication Date: 2019.01.01 DELL EMC

AI summary

A method, article of manufacture, and apparatus for managing a computing environment, such as a cloud data repository. In some embodiments, such may include modifying an object or a component of an object at runtime and storing the modified object or modified component of an object in a storage device. In some embodiments, the component of an object being modified may include traits. In some embodiments, traits may be hierarchical data structures, including hierarchical data structures having more than one version. These hierarchical data structures may also contain or be associated with metadata, and may also make up the metadata of a host object. Embodiments provide that policies may be applied to these traits.