Network Storage Continuity Confirmation via Protocol Hierarchy Merging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for confirming continuity between a host computer and a network storage device are cumbersome and complex, especially when multiple devices and volumes are involved, requiring users to manually input identifiers across different protocol hierarchies, which complicates failure diagnosis and handling.

Innovation Solution

A method that accepts device and volume identifiers from a user in a higher host protocol hierarchy, automatically specifying network identifiers using a storage management table, and sequentially executing continuity confirmations in network and host protocols, with results outputting the accessibility status of the volume.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual continuity confirmation is performed in each protocol hierarchy, then continuity status can be confirmed, but the operation becomes complicated and time-consuming

Engineering Contradiction:
Improvecontinuity confirmation accuracyVSAvoidoperation complexity
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The patent combines multiple continuity confirmation operations across different protocol hierarchies (network communication protocol and host protocol) into a single integrated confirmation process. The continuity confirmation unit automatically executes confirmations in both hierarchies and aggregates the results, allowing users to perform one operation instead of multiple separate operations, thus reducing operational complexity while maintaining comprehensive continuity verification.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs automatic continuity confirmation without requiring user intervention in each protocol hierarchy. The continuity confirmation unit autonomously executes confirmation in the network communication protocol, then automatically proceeds to confirm continuity in the host protocol, and finally determines overall continuity status. This self-service mechanism eliminates the need for users to manually specify identifiers and execute multiple confirmation commands.

Inventive Principle:
Principle #25Self-service

2Reliability

If multiple identifiers are specified manually, then continuity can be confirmed, but the number of operations increases with more devices and volumes

Engineering Contradiction:
Improvecontinuity confirmation reliabilityVSAvoidconfirmation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically obtaining necessary identifiers (such as network identifiers and volume identifiers) before executing continuity confirmation. The continuity confirmation unit retrieves identifiers from stored configuration information or previous operations, so users don't need to manually specify them each time. This preliminary preparation reduces the number of operations required and accelerates the confirmation process while maintaining reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The continuity confirmation unit is designed to handle multiple devices and volumes universally through a single interface. Instead of requiring separate manual operations for each device-volume combination, the unit can process multiple confirmations systematically using stored configuration data, reducing operational time while ensuring comprehensive coverage of all devices and volumes.

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

3Difficulty of detecting and measuring

If sequential confirmation in multiple hierarchies is performed, then accurate failure diagnosis is possible, but the process becomes complex

Engineering Contradiction:
Improvefailure detection accuracyVSAvoidconfirmation process complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The patent segments the continuity confirmation process into distinct hierarchical levels (network communication protocol level and host protocol level), with each level handled by dedicated processing logic. The continuity confirmation unit executes confirmation in the network layer first, then separately executes confirmation in the host protocol layer, and finally integrates results. This segmentation allows accurate failure localization to specific layers while presenting a simplified unified interface to users, reducing perceived complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The continuity confirmation unit acts as an intermediary that manages the complexity of multi-hierarchy confirmation. It automatically coordinates the sequential execution of confirmations across different protocol layers, interprets results from each layer, and synthesizes overall continuity status. This intermediary function shields users from the complexity of multiple hierarchies while maintaining accurate failure detection capabilities through systematic layered verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7562109B2Connectivity confirmation method for network storage device and host computer
Publication Date: 2009.07.14 RAKUTEN GROUP INC
  • US7562109B2 patent drawing
  • US7562109B2 patent drawing
  • US7562109B2 patent drawing

AI summary

The present invention decreases the burden of operation required for specifying the continuity status and the cause of failure of a network storage device. A host computer accepts the specification of the device identifier, that is an identifier of the network storage device in the host protocol which positions in a higher hierarchy than the network communication protocol, and a volume identifier, that is an identifier of the volume. Then based on the specified device identifier, the host computer specifies the network identifier, that is an identifier of the network storage device in the network communication protocol. And continuity is confirmed in the network communication protocol in which the specified network identifier is the destination. Also continuity is confirmed in the host protocol in which the device identifier is the destination. And the volume specified by the volume identifier is accessed.