Object-Based Memory Fabric for Cloud Data Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current commodity hardware and software solutions are unable to meet the demands of Cloud Computing and Big Data environments due to the separation of processing, memory, and storage, leading to inefficiencies and limitations in performance and scalability.

Innovation Solution

An object-based memory fabric that manages memory objects at the memory layer, eliminating the distinction between processing, memory, and storage by providing a unified object memory space accessible through a standard operating system, allowing for transparent and dynamic management of object characteristics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If processing, memory, and storage are separated and managed by software, then each component can be managed independently, but system complexity increases and performance decreases

Engineering Contradiction:
ImproveIndependent management capabilityVSAvoidSoftware stack complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges processing, memory, and storage into a unified object-based memory fabric where all three functions are managed at the hardware level rather than through separate software layers. This consolidation eliminates the need for complex software stacks while maintaining independent manageability through hardware-controlled object operations.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent replaces software-based management mechanisms with hardware-based object management. Instead of using software to manage processing, memory, and storage separately, the system uses hardware object mechanisms that inherently provide unified management with simplified software interfaces.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If processing, memory, and storage are separated into different nodes, then scalability is improved, but data access overhead increases

Engineering Contradiction:
ImproveSystem scalabilityVSAvoidData access latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments data into objects that can be distributed across multiple nodes in a scalable manner. Each object is managed as a unit with its own metadata, allowing for efficient distribution and access while maintaining low latency through hierarchical object management that keeps frequently accessed objects local.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to object management, organizing objects into different levels (e.g., local objects, remote objects, cached objects). This dimensional organization allows the system to scale while maintaining fast access to frequently used objects through local caching and proximity-based management.

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

3Ease of operation

If standard software stacks are used, then compatibility is maintained, but performance optimization is limited

Engineering Contradiction:
ImproveSoftware compatibilityVSAvoidProcessing performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent introduces an object manager as an intermediary layer between standard software and the hardware object memory fabric. This mediator translates standard software memory operations into efficient hardware object operations, maintaining compatibility while enabling performance optimization through hardware-accelerated object management.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the fundamental parameters of memory management from byte-addressable virtual memory to object-based addressing with hardware support. This parameter change enables performance optimization through object-level operations while maintaining compatibility through transparent translation layers.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11899931B2Memory fabric software implementation
Publication Date: 2024.02.13 ULTRATA LLC
  • US11899931B2 patent drawing
  • US11899931B2 patent drawing
  • US11899931B2 patent drawing

AI summary

A hardware-based processing node of an object memory fabric can comprise a memory module storing and managing one or more memory objects within an object-based memory space. Each memory object can be created natively within the memory module, accessed using a single memory reference instruction without Input/Output (I/O) instructions, and managed by the memory module at a single memory layer. The memory module can provide an interface layer below an application layer of a software stack. The interface layer can comprise one or more storage managers managing hardware of a processor and controlling portions of the object-based memory space visible to a virtual address space and physical address space of the processor. The storage managers can further provide an interface between the object-based memory space and an operating system executed by the processor and an alternate object memory based storage transparent to software using the interface layer.