Storage System Interface for Consistent Component Interaction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of storage systems, with varying components and protocols, makes it challenging to design management applications and client interfaces that can consistently operate across different storage systems, as each component may support unique functionalities and implement standard protocols differently.

Innovation Solution

A storage system interface is developed, which uses a storage system model that includes entity models representing storage system components. These entity models encapsulate attributes and operations, allowing for hierarchical relationships and dynamic configuration, enabling components to interact with storage systems without needing detailed knowledge of specific implementations. The interface generates a storage system model on demand, determining attributes and operations as needed, and traverses the hierarchy to find implementations, simplifying operations and handling requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If detailed knowledge of specific storage system implementations is required, then operation precision can be improved, but device complexity and ease of operation deteriorate

Engineering Contradiction:
Improveoperation precisionVSAvoidinterface complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent introduces a storage system interface as an intermediary layer between management applications and storage system components. This interface uses entity models to represent storage components abstractly, allowing applications to interact with standardized interfaces rather than detailed implementation specifics. The intermediary resolves the contradiction by providing consistent, simplified access points that mask the underlying complexity of different storage implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal storage system interface that can interact with multiple types of storage components (storage controllers, storage devices, storage pools) through a common set of entity models and operations. This multi-functional interface allows a single management application to work across different storage system implementations without requiring detailed knowledge of each specific component type, thereby reducing interface complexity while maintaining operational precision.

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

2Ease of manufacture

If standard protocols are used, then ease of manufacture is improved, but adaptability deteriorates due to manufacturer extensions and variations

Engineering Contradiction:
Improveprotocol standardizationVSAvoidfunctionality consistency
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent segments the storage system interface into hierarchical entity models (e.g., storage system, controller, device, pool) with standardized operations at each level. This segmentation allows standard protocols to be implemented at the base level while enabling extensions and variations at higher levels through inheritance and composition. Management applications interact with the standardized upper-level interfaces, achieving both protocol standardization and adaptability to manufacturer-specific extensions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a dynamic interface where entity models can be generated on-demand based on the actual storage system configuration. The interface adapts its behavior based on the specific storage components detected, allowing it to maintain consistency with standard protocols while automatically adjusting to handle manufacturer extensions and variations. This dynamic generation resolves the contradiction by making the interface both standardized and adaptable.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If components are added or replaced in existing storage systems, then adaptability is improved, but device complexity worsens due to varying functionalities and firmware versions

Engineering Contradiction:
Improvecomponent flexibilityVSAvoidcomponent variation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary action by pre-defining a comprehensive set of entity models that represent possible storage components and their relationships before the actual storage system is configured. These pre-defined models include standard operations and attributes that can accommodate various component types and firmware versions. When components are added or replaced, the system matches them against the pre-defined models, allowing the interface to handle component flexibility without increasing operational complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating virtual representations (entity models) of physical storage components. Instead of directly managing the actual components with their varying functionalities, the system creates standardized copies (entity models) that represent the components' abstract characteristics. This copying approach allows the interface to handle component variations uniformly, as all physical components are represented by their corresponding entity model copies, thereby maintaining simplicity despite component flexibility.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11847319B2Storage system interface
Publication Date: 2023.12.19 NETAPP INC
  • US11847319B2 patent drawing
  • US11847319B2 patent drawing
  • US11847319B2 patent drawing

AI summary

A request to generate a storage system model is received. The storage system model represents at least a portion of a storage system. In response to receiving the request, a storage system interface configuration is loaded. The storage system interface configuration comprises an attribute of an entity model. The attribute corresponds to an attribute of a storage system entity of the storage system. Further in response to receiving the request, the entity model is identified as representing the storage system entity. In response to identifying the entity model as representing the storage system entity, the entity model is instantiated.