Protocol Endpoint Object Duality in Storage Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Implementing a protocol endpoint (PE) on a data storage system is complicated due to its differences from traditional volumes, requiring significant new code and reimplementation of features in the storage driver stack.

Innovation Solution

Implementing a PE as a LUN object that functions as a storage group object, using the same World Wide Name for indexing, to leverage existing features without major modifications, allowing access to virtual storage volumes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a PE is implemented as an entirely new object rather than as a LUN object, then additional PE features can be supported, but a lot of new code must be written to implement a new data structure

Engineering Contradiction:

ImprovePE features supportVSAvoidcode implementation

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by making the existing LUN object serve multiple functions - it acts as both a traditional volume object and a protocol endpoint object. By adding PE-specific fields and capabilities to the existing LUN data structure, the system can support PE features without creating a separate object type, thus avoiding the need to write extensive new code while still providing the required functionality

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of manufacture

If a PE is implemented as a LUN object without significant modification, then existing storage driver stack features can be utilized, but additional PE features cannot be fully supported

Engineering Contradiction:

Improveimplementation easeVSAvoidPE features support

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent applies segmentation by dividing the PE object into distinct functional components within the LUN data structure. It separates traditional volume fields from PE-specific fields (such as PE LUN UID, PE host group UID, and VVol mapping structures), allowing each segment to be independently managed and processed while maintaining the overall LUN object integrity

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies the nested doll principle by embedding PE-specific data structures within the existing LUN object framework. The PE fields are nested within the LUN data structure, and virtual volumes are nested within the PE object, creating a hierarchical organization that allows PE functionality to be contained within the traditional LUN object without requiring external or separate data structures

Inventive Principle:

Principle #7Nested doll (Nesting)

Data Source

PatentUS9940155B1Protocol endpoint object duality

Publication Date: 2018.04.10 EMC IP HLDG CO LLC

AI summary

Embodiments are directed to implementing the protocol endpoint (PE) as a LUN object without significant modification to also support additional features. In particular, since many of the additional features are similar to those already implemented within storage group objects, it would be desirable to implement a PE using both a LUN object and a storage group object linked together. This result may be accomplished by implementing the PE as a LUN object is used when certain features are being accessed and as a storage group object that is used when other features are being accessed. This linkage may be achieved by indexing both the storage group object and the LUN object representing the PE using the same World Wide Name.