NVMe-oF Discovery Controller Connection Command

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing NVMe-oF systems face challenges in efficient discovery and registration of NVMe subsystems, particularly due to the end-node centric nature of Ethernet transports, which requires tedious and error-prone configuration processes and lacks automated registration capabilities, leading to connectivity issues and increased operational expenses.

Innovation Solution

The implementation of a Storage Fabric Services (StFS) component that provides a centralized discovery service, enabling NVMe hosts and subsystems to automatically discover and register with a discovery controller, facilitating access control and multipathing management, and supporting implicit registration for devices without explicit StFS client support.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration processes are used for NVMe subsystem registration, then configuration control is maintained, but configuration complexity and error rates increase

Engineering Contradiction:
Improveregistration accuracyVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The NVMe subsystem automatically performs registration with the discovery controller by sending an untagged connect command that contains its own identification information. This self-service mechanism eliminates manual configuration requirements, reduces errors, and simplifies the deployment process while maintaining registration accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The subsystem performs preliminary registration actions during the connection establishment phase, before actual data transfer begins. By embedding registration information in the initial connect command, the system prepares the discovery controller with necessary subsystem information in advance, avoiding later configuration steps.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If automated registration is implemented, then configuration time is reduced, but system complexity increases

Engineering Contradiction:
Improveconfiguration timeVSAvoidsystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The connect command serves multiple functions simultaneously: it establishes the connection between host and subsystem, and it carries registration information for the discovery controller. This multi-functionality reduces configuration time without requiring separate automated registration mechanisms, thereby avoiding increased system complexity.

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

Solution Approach 2:

The patent merges the connection establishment process with the registration process by combining their information streams. The untagged connect command from the subsystem is merged with discovery controller processing, allowing both connection and registration to occur in a single integrated operation rather than as separate steps.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If explicit StFS client support is required, then service control is improved, but device compatibility decreases

Engineering Contradiction:
Improveservice controlVSAvoiddevice compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The discovery controller acts as an intermediary that handles registration for subsystems regardless of whether they have explicit StFS client support. By mediating the registration process through the discovery controller, the system maintains service control while accepting diverse subsystem implementations, thereby improving device compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of requiring subsystems to actively initiate registration with the discovery controller, the system inverts the approach by allowing any connect command (including untagged ones) to trigger automatic registration. This inversion expands compatibility to include subsystems without explicit StFS client support while maintaining service control through the discovery controller's automatic processing.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS11489921B2Kickstart discovery controller connection command
Publication Date: 2022.11.01 DELL PROD LP
  • US11489921B2 patent drawing
  • US11489921B2 patent drawing
  • US11489921B2 patent drawing

AI summary

Multicast Domain Name System (mDNS)-based pull registration systems and methods facilitate discovery in communication networks, such as Storage Area Networks (SANs) that operate in non-volatile memory express over Fabric (NVMe-oF) environments. In various embodiments, this is accomplished by allowing a network entity (e.g., a Centralized Discovery Controller (CDC)) to use a pull registration to exchange discovery information with a storage subsystem (e.g., a storage array), advantageously, without requiring storage subsystem to possess complex functionalities present in existing designs.