Polymorphic Storage Device Kernel Routing Packets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data storage systems, particularly NoSQL databases, suffer from redundant mapping layers and inefficiencies due to the blurring boundaries between persistent storage, volatile storage, and processing, leading to bottlenecks and resource wastage.

Innovation Solution

A polymorphic storage device (PSD) with a kernel and interface layer that receives packets from a host computer, routes them to applications, and reconfigures hardware to transform into different device types via a device control interface, eliminating redundant mappings and enhancing performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional mapping layers (key-LBA and LBA-PBA) are used in NoSQL database systems, then compatibility with conventional storage interfaces is maintained, but device complexity and resource consumption increase due to redundant implementations

Engineering Contradiction:
ImprovecompatibilityVSAvoidmapping layers
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the mapping functionality from the host computer and consolidates it into the storage device's firmware. The flash translation layer (FTL) in the storage device performs both key-LBA and LBA-PBA mapping operations, eliminating the need for redundant mapping layers in the host. This extraction principle reduces overall system complexity while maintaining compatibility.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent merges multiple mapping functions into a single integrated flash translation layer within the storage device firmware. Instead of having separate key-LBA mapping in the host and LBA-PBA mapping in the storage device, both mapping operations are combined into one FTL component, reducing redundancy and simplifying the system architecture.

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If firmware updates are required to transform storage devices into different device types, then device functionality can be changed, but loss of time and reduced productivity occur due to update requirements

Engineering Contradiction:
Improvedevice transformationVSAvoidfirmware update time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements dynamic reconfiguration of the storage device through runtime loading of different application containers and firmware configurations. Instead of requiring firmware updates to change device types, the system dynamically loads appropriate applications and configuration parameters, allowing the storage device to transform into different device types (e.g., SSD, HDD, RAID) without time-consuming firmware update cycles.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent prepares multiple application containers and configuration sets in advance, stored within the device. When transformation is needed, the system simply switches to a pre-prepared configuration rather than performing firmware updates. This preliminary preparation eliminates update time while enabling device type transformation.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If multiple redundant mapping layers are implemented in host and storage device, then address translation functionality is ensured, but resource consumption and bottlenecks increase

Engineering Contradiction:
Improveaddress translationVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts mapping operations from the host computer's CPU and memory resources and relocates them to the storage device's dedicated firmware. The FTL in the storage device handles all address translation using the storage device's own resources, eliminating the resource consumption burden from the host system while ensuring reliable address translation.

Inventive Principle:
Principle #2Taking out (Extraction)

4Stability of the object's composition

If conventional storage devices with fixed functionality are used, then device stability is maintained, but adaptability to different applications and workloads is limited

Engineering Contradiction:
Improvedevice stabilityVSAvoidapplication flexibility
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal storage device platform that can function as different device types through loading of various application containers. The same physical storage device can be configured to operate as an SSD, HDD, RAID array, or other storage configurations by loading appropriate firmware applications, providing multi-functionality while maintaining stable operation within each configured mode.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10423331B2Polymorphic storage devices
Publication Date: 2019.09.24 SAMSUNG ELECTRONICS CO LTD
  • US10423331B2 patent drawing
  • US10423331B2 patent drawing
  • US10423331B2 patent drawing

AI summary

A storage device includes an application container containing one or more applications; a polymorphic storage device (PSD) kernel configured to receive a plurality of packets including data, messages, and commands from a host computer, and route the plurality of packets to an application in the application container based on a command included in the plurality of packets; and a PSD interface layer configured to provide an interface between the one or more applications and the PSD kernel. The storage device can be transformed from a first type of storage device to a second type of storage device according to the control command received via the PSD control interface.