Storage Configuration Retrieval Using Shared Hash-Based Common Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage systems face inefficiencies in response performance for configuration information acquisition due to limited CPU and memory usage, particularly when acquiring data with common elements, leading to increased memory and CPU loads, which deteriorate response performance.

Innovation Solution

A storage device that utilizes a processor and memory to record hash values of common data, groups resources with the same hash values, and acquires common data only once, reducing memory and CPU usage by eliminating redundant data processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the API server acquires all data of all resources including common data for each resource, then the configuration information acquisition is complete, but the amount of data held in memory increases and response performance decreases

Engineering Contradiction:
Improvecompleteness of configuration information acquisitionVSAvoidresponse performance of configuration information acquisition
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges common data from multiple resources into a single stored representation. The API server identifies common data across resources and stores it once in memory, then references it for multiple resources, reducing total memory usage while maintaining complete configuration information acquisition capability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal common data structure that serves multiple resources simultaneously. This common data is designed to be reusable across different resource types, allowing the system to efficiently handle configuration information for multiple resources without duplicating identical data portions.

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

2Ease of operation

If the API server holds acquired data in memory until response creation, then data is readily available for response generation, but memory area management complexity increases and response performance deteriorates

Engineering Contradiction:
Improvedata availability for response creationVSAvoidmemory area management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments configuration data into distinct common data and resource-specific data portions. Common data is stored separately in a dedicated memory structure, while resource-specific data is handled individually. This segmentation simplifies memory management by providing clear boundaries and organization for different data types.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a common data structure as an intermediary between the raw configuration information and the final response. This intermediary structure organizes and manages common data separately, acting as a buffer that simplifies the data flow and reduces the complexity of direct memory management during response creation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If the CPU executes data conversion processes for response creation, then the response is generated, but CPU usage increases and the number of simultaneously executable APIs is limited

Engineering Contradiction:
Improveresponse creation capabilityVSAvoidCPU usage
Core Design Contradiction:
ProductivityVSPower

Solution Approach 1:

The patent performs preliminary organization of configuration data into common and resource-specific portions during the data acquisition phase. By pre-structuring the data in memory with clear separations and references, the system reduces the amount of data conversion and processing required during response creation, thereby lowering CPU usage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses reference copying rather than full data copying for common data. Instead of duplicating common data for each resource, the system stores references or pointers to the common data structure, allowing multiple resources to share the same data without actual duplication. This significantly reduces the volume of data that requires CPU processing during response generation.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250348241A1Storage device and control method thereof
Publication Date: 2025.11.13 HITACHI VANTARA LTD
  • US20250348241A1 patent drawing
  • US20250348241A1 patent drawing
  • US20250348241A1 patent drawing

AI summary

A hash value recording database records a hash value of common data of each of resources, and an information acquisition efficiency improving service refers to the hash values of the common data recorded in the hash value recording database, groups a plurality of target resources from which configuration information is to be acquired into groups each having the same hash value of the common data, acquires common data of each of the groups, and acquires dynamic data of each of the resources.