# US 2019/0171361 A1 · Memory fabric software implementation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0171361 A1
- Document ID: US20190171361A1
- Status: Published application
- Kind: A1
- Application number: 16/269,833
- Filed: 2019-02-07
- Published: 2019-06-06
- Earliest claimed: 2016-12-07
- Assignees: Ultrata, LLC
- Applicants: Ultrata, LLC
- Inventors: Steven J. Frank; Larry Reback
- Web page: https://patentgrep.com/patent/US20190171361A1

## CPC

- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0662: {Virtualisation aspects}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 12/0223: {User address space allocation, e.g. contiguous or non contiguous base addressing}
- G06F 12/0646: {Configuration or reconfiguration}
- G06F 12/1072: Decentralised address translation, e.g. in distributed shared memory systems
- G06F 13/00: Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units (interface circuits for specific input/output devices G06F3/00 {; multiprogram control therefor G06F9/46}; multiprocessor systems G06F15/16 )
- G06F 16/1847: {specifically adapted to static storage, e.g. adapted to flash memory or SSD}
- G06F 2212/214: Solid state disk
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

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.

## Claims

### Claim 1

A hardware-based processing node of an object memory fabric, the hardware-based processing node comprising:
a memory module comprising a hardware component installed in the hardware-based processing node storing and managing one or more memory objects within a object-based memory space, wherein:
each memory object is created natively within the memory module through a namespace of the memory fabric,
each memory object is accessed by applications executing on the hardware-based processing node using a single memory reference instruction without Input/Output (I/O) instructions by the applications,
each memory object is managed by the memory module through the namespace of the memory fabric at a single memory layer without distinction between volatile memory and non-volatile storage, and
the memory module provides to the applications an interface layer below an application layer of a software stack, the interface layer comprising one or more storage managers compiled into the hardware of the memory module.

### Claim 2 (depends on 1)

The hardware-based processing node of claim 1, wherein the one or more storage managers further provide an interface between the object-based memory space and an operating system executed by a processor and control, at a hardware layer, portions of the object-based memory space visible to a virtual address space and physical address space of the processor.

### Claim 3 (depends on 2)

The hardware-based processing node of claim 2, wherein the one or more storage managers provide an alternate object memory based storage transparent to a FileSystem, database, or other software using the interface layer.

### Claim 4 (depends on 2)

The hardware-based processing node of claim 2, wherein the operating system comprises Linux or Security-Enhanced Linux (SELinux).

### Claim 5 (depends on 2)

The hardware-based processing node of claim 2, wherein the interface layer provides access to the object-based memory space to one or more applications executing in the application layer of the software stack access.

### Claim 6 (depends on 5)

The hardware-based processing node of claim 5, wherein the interface layer provides access to the object-based memory space through memory allocation functions of the operating system.

### Claim 7 (depends on 2)

The hardware-based processing node of claim 2, wherein the interface layer comprises an object-based memory specific version of a library file of the operating system.

### Claim 8 (depends on 1)

The hardware-based processing node of claim 1, wherein the one or more storage managers utilize a format and addressing of the object-based memory space.

### Claim 9 (depends on 1)

The hardware-based processing node of claim 1, wherein the one or more storage managers comprise at least one database manager.

### Claim 10 (depends on 1)

The hardware-based processing node of claim 1, wherein the one or more storage managers comprise at least one graph database manager.

### Claim 11 (depends on 1)

The hardware-based processing node of claim 1, wherein the one or more storage managers comprise at least one filesystem manager.

### Claim 12 (depends on 1)

The hardware-based processing node of claim 1, wherein the one or more storage managers comprise at least one direct storage manager providing direct access of the memory fabric to an application modified to utilize an object-based memory fabric specific version of a library file of the operating system.

### Claim 13 (depends on 1)

The hardware-based processing node of claim 1, wherein the hardware-based processing node comprises a Dual In-line Memory Module (DIMM) card, the DIMM card further comprising a Field Programmable Gate Array (FPGA) into which the one or more memory managers are compiled.

### Claim 14 (depends on 1)

The hardware-based processing node of claim 1, wherein the hardware-based processing node comprises a commodity server and wherein the memory module comprises a Dual In-line Memory Module (DIMM) card installed within the commodity server, the DIMM card further comprising a Field Programmable Gate Array (FPGA) into which the one or more memory managers are compiled.

### Claim 15 (depends on 1)

The hardware-based processing node of claim 1, wherein the hardware-based processing node comprises a mobile computing device.

### Claim 16 (depends on 1)

The hardware-based processing node of claim 1, wherein the hardware-based processing node comprises a single chip.

### Claim 17

An object memory fabric comprising:
a plurality of hardware-based processing nodes, each hardware-based processing node comprising:
a memory module comprising a hardware component installed in the hardware-based processing node storing and managing one or more memory objects within an object-based memory space, wherein each memory object is created natively within the memory module through a namespace of the memory fabric, each memory object is accessed by applications executing on the hardware-based processing node using a single memory reference instruction without Input/Output (I/O) instructions by the applications, each memory object is managed by the memory module through the namespace of the memory fabric at a single memory layer without distinction between volatile memory and non-volatile storage, and wherein the memory module provides to the applications an interface layer below an application layer of a software stack, the interface layer comprising one or more storage managers compiled into the hardware of the memory module;
a node router communicatively coupled with each of the one or more memory modules of the node and adapted to route memory objects or portions of memory objects between the one or more memory modules of the node; and
one or more inter-node routers communicatively coupled with each node router, wherein each of the plurality of nodes of the object memory fabric is communicatively coupled with at least one of the inter-node routers and adapted to route memory objects or portions of memory objects between the plurality of nodes.

### Claim 18 (depends on 17)

The object memory fabric of claim 17, wherein the one or more storage managers further provide an interface between the object-based memory space and an operating system executed by a processor and control, at a hardware layer, portions of the object-based memory space visible to a virtual address space and physical address space of the processor.

### Claim 19 (depends on 18)

The object memory fabric of claim 18, wherein the one or more storage managers provide an alternate object memory based storage transparent to a FileSystem, database, or other software using the interface layer.

### Claim 20 (depends on 18)

The object memory fabric of claim 18, wherein the operating system comprises Linux or Security-Enhanced Linux (SELinux).

### Claim 21 (depends on 18)

The object memory fabric of claim 18, wherein the interface layer provides access to the object-based memory space to one or more applications executing in the application layer of the software stack access.

### Claim 22 (depends on 21)

The object memory fabric of claim 21, wherein the interface layer provides access to the object-based memory space through memory allocation functions of the operating system.

### Claim 23 (depends on 18)

The object memory fabric of claim 18, wherein the interface layer comprises an object-based memory specific version of a library file of the operating system.

### Claim 24 (depends on 17)

The object memory fabric of claim 17, wherein the one or more storage managers utilize a format and addressing of the object-based memory space.

### Claim 25 (depends on 17)

The object memory fabric of claim 17, wherein the one or more storage managers comprise at least one database manager.

### Claim 26 (depends on 17)

The object memory fabric of claim 17, wherein the one or more storage managers comprise at least one graph database manager.

### Claim 27 (depends on 17)

The object memory fabric of claim 17, wherein the one or more storage managers comprise at least one filesystem manager.

### Claim 28 (depends on 17)

The object memory fabric of claim 17, wherein the one or more storage managers comprise at least one direct storage manager providing direct access of the memory fabric to an application modified to utilize an object-based memory fabric specific version of a library file of the operating system.

### Claim 29 (depends on 17)

The object memory fabric of claim 17, wherein memory objects are created and managed equivalently from any hardware-based processing node of the object memory fabric without a centralized storage manager or memory fabric class library.

### Claim 30 (depends on 17)

The object memory fabric of claim 17, wherein at least one hardware-based processing node comprises a Dual In-line Memory Module (DIMM) card, the DIMM card further comprising a Field Programmable Gate Array (FPGA) into which the one or more memory managers are compiled.

### Claim 31 (depends on 17)

The object memory fabric of claim 17, wherein at least one hardware-based processing node comprises a commodity server and wherein the memory module comprises a Dual In-line Memory Module (DIMM) card installed within the commodity server, the DIMM card further comprising a Field Programmable Gate Array (FPGA) into which the one or more memory managers are compiled.

### Claim 32 (depends on 17)

The object memory fabric of claim 17, wherein at least one hardware-based processing node comprises a mobile computing device.

### Claim 33 (depends on 17)

The object memory fabric of claim 17, wherein at least one hardware-based processing node comprises a single chip.

### Claim 34

A method for interfacing an object-based memory fabric with software executing on one or more nodes of the object-based memory fabric, the method comprising:
creating, by a memory module of a hardware-based processing node of the object-based memory fabric, each memory object natively within the memory module through a namespace of the memory fabric, wherein the memory module comprises a hardware component installed in the hardware-based processing node,
accessing, by applications executing on the hardware-based processing node, each memory object using a single memory reference instruction without Input/Output (I/O) instructions applications,
managing, by the memory module of the hardware-based processing node, each memory object within the memory module through the namespace of the memory fabric and at a single memory layer without distinction between volatile memory and non-volatile storage, and
providing, by the memory module of the hardware-based processing node, an interface layer to the applications, the interface layer below an application layer of a software stack, the interface layer comprising one or more storage managers compiled into the hardware of the memory module.

### Claim 35 (depends on 34)

The method of claim 34, further comprising providing, by the memory module of the hardware-based processing node through the one or more storage managers, an interface between the object-based memory space and an operating system executed by a processor and controlling, by the memory module of the hardware-based processing node through the one or more storage managers at a hardware layer, portions of the object-based memory space visible to a virtual address space and physical address space of the processor.

### Claim 36 (depends on 35)

The method of claim 35, further comprising providing, by the memory module of the hardware-based processing node through the one or more storage managers, an alternate object memory based storage transparent to a FileSystem, database, or other software using the interface layer.

### Claim 37 (depends on 35)

The method of claim 35, wherein the operating system comprises Linux or Security-Enhanced Linux (SELinux).

### Claim 38 (depends on 35)

The method of claim 35, further comprising providing, by the memory module of the hardware-based processing node through the interface layer, access to the object-based memory space to one or more applications executing in the application layer of the software stack access.

### Claim 39 (depends on 38)

The method of claim 38, further comprising providing, by the memory module of the hardware-based processing node through the interface layer, access to the object-based memory space through memory allocation functions of the operating system.

### Claim 40 (depends on 35)

The method of claim 35, wherein the interface layer comprises an object-based memory specific version of a library file of the operating system.

### Claim 41 (depends on 34)

The method of claim 34, wherein the one or more storage managers utilize a format and addressing of the object-based memory space.

### Claim 42 (depends on 34)

The method of claim 34, wherein the one or more storage managers comprise at least one of a database manager, a graph database manager, or a filesystem manager.
