Loose Coupling Metadata and Data for Distributed Networks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Distributed object systems in the energy industry face performance issues due to unreliable network connections and changing topologies, particularly when multiple users access and modify data simultaneously, leading to inefficiencies in data management and transfer.

Innovation Solution

Implementing a method that stores metadata and actual data separately, using globally unique identifiers and version tables, allowing metadata to be loosely coupled and independently managed, enabling efficient data transmission and version tracking across a distributed network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If complete object system is replicated to each node, then data availability is improved, but network bandwidth consumption and storage requirements increase significantly

Engineering Contradiction:

Improvedata availabilityVSAvoidnetwork bandwidth consumption

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the object system into two distinct parts: metadata (stored in the object store) and content data (stored in the content store). This segmentation allows selective replication of only metadata across nodes, while content data remains centralized or selectively distributed, thereby reducing network bandwidth consumption while maintaining data availability through metadata-driven access.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a content addressable store as an intermediary layer between the object store and content data. This intermediary enables efficient data retrieval and version management without requiring full replication of content data to each node, thus reducing network bandwidth consumption while preserving data availability through the intermediary's caching and routing capabilities.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Stability of the object's composition

If metadata and content data are stored together, then data consistency is simplified, but transfer efficiency decreases due to unnecessary data movement

Engineering Contradiction:

Improvedata consistencyVSAvoiddata transfer efficiency

Core Design Contradiction:

Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent segments the data structure into metadata (in object store) and content data (in content store), allowing independent management and transfer of each component. Metadata can be transferred efficiently to establish data consistency, while content data remains stationary or is transferred only when necessary, thereby improving data transfer efficiency without compromising consistency through the use of content identifiers and version tables.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts the content data from the metadata structure, storing content data separately in a content addressable store while maintaining references through content identifiers. This extraction allows metadata to be transferred independently and efficiently, while content data is accessed through the content addressable store, improving transfer efficiency while maintaining data consistency through the reference mechanism.

Inventive Principle:

Principle #2Taking out (Extraction)

3Ease of manufacture

If distributed object system uses traditional storage model, then implementation is simpler, but performance deteriorates under unreliable network conditions

Engineering Contradiction:

Improveimplementation simplicityVSAvoidsystem performance under unreliable network

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The patent segments the storage system into object store (metadata) and content store (data), with the object store being lightweight and suitable for distributed deployment even under unreliable network conditions. The content store can be more centralized or selectively distributed, providing resilience against network failures while maintaining implementation feasibility through the clear separation of concerns between metadata management and data storage.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a content addressable store as an intermediary that provides robust data access and version management capabilities. This intermediary layer handles network reliability issues by implementing content-based addressing and version control, allowing the system to maintain performance under unreliable network conditions while keeping the implementation relatively simple through the intermediary's standardized interface.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10657113B2Loose coupling of metadata and actual data

Publication Date: 2020.05.19 BAKER HUGHES CO

AI summary

An embodiment of a non-transitory computer-readable storage medium stores instructions which, when processed by a processor, cause the processor to implement a method of storing a data object. The method includes: storing as metadata a globally unique object identifier that identifies the object, and a version table having a relation to the globally unique object identifier, the object representing a data set; and storing the data set in a content table associated with the object, the content table having a relation to the version table, the data set configured to be transmitted from the content table to a node in a distributed network independent from the metadata, the content table including a globally unique content identifier that identifies the data set.