Storage Subsystem Zone Segmentation for Data Protection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current solid-state storage solutions lack the ability to segment storage arrays into zones with different access control and security parameters, limiting the implementation of vendor-specific commands and storage algorithms on a per-zone basis.

Innovation Solution

The storage subsystem is segmented by defining segment parameters and storing them separately from user data, allowing for independent configuration of access levels, security features, and vendor-specific commands for each zone, using physical or logical block addresses to define non-overlapping sections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the storage subsystem is segmented into multiple zones with different access control parameters, then data protection and security are improved, but device complexity increases due to the need for separate segment definitions and parameters storage

Engineering Contradiction:

Improvedata protectionVSAvoidsegment management structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The storage array is divided into multiple segments or zones, each with independent access control parameters. This segmentation allows different portions of the storage subsystem to have different security levels and access restrictions, enabling fine-grained data protection without requiring separate physical storage devices.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Segment definitions and segment parameters are stored in separate locations within the storage subsystem, acting as intermediary structures that manage access control. The controller uses these stored definitions and parameters to mediate access requests to different segments, providing a systematic approach to managing complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If vendor-specific commands are implemented for specific segments, then storage algorithm efficiency is improved, but ease of operation deteriorates due to the need for custom commands

Engineering Contradiction:

Improvestorage algorithm efficiencyVSAvoidcommand interface

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

Different segments of the storage array can have different characteristics and support different vendor-specific commands tailored to their specific storage algorithms and access patterns. This local customization allows optimization for specific workloads while maintaining standard interface compatibility for general operations.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The storage subsystem maintains compatibility with standard ATA commands while also supporting vendor-specific commands for optimized operations. The segment management structure allows the same physical storage device to serve multiple functions with different access modes and command sets depending on the segment being accessed.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Measurement precision

If segment definitions and parameters are stored separately from user data, then access control precision is improved, but loss of information increases due to additional storage locations required

Engineering Contradiction:

Improveaccess control precisionVSAvoidstorage space overhead

Core Design Contradiction:

Measurement precisionVSLoss of information

Solution Approach 1:

Segment definitions and segment parameters are stored within the storage subsystem itself, merging the metadata management functions with the storage device. This integration eliminates the need for external management systems and reduces overall information loss by keeping all necessary data within the existing storage infrastructure.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The segment definitions and parameters are stored in dedicated locations within the storage subsystem's addressable space, utilizing the existing storage dimensions efficiently. This approach avoids adding physical storage overhead by organizing data in the logical address space already provided by the storage device.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS8127048B1Systems and methods for segmenting and protecting a storage subsystem

Publication Date: 2012.02.28 WESTERN DIGITAL TECHNOLOGIES INC

AI summary

A storage subsystem comprises a set of zone definitions that uses physical block addresses to divide a memory array in the storage subsystem into zones or segments. A set of zone parameters defines user access modes and security levels for each of the segments. Defining zones for the memory array provide flexibility and increased protection for data stored in the memory array. For example, data of one zone can be quickly erased without affecting data stored in other zones and critical data can be stored in read-only zones to prevent inadvertent overwrite.