Mesh Network Remote Support Gateway Protocol

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing remote support gateway solutions for data centers are cumbersome to set up and configure, prone to errors, and often result in missed Service Level Agreements (SLAs) due to manual configuration requirements, leading to poor customer experience and increased costs for manufacturers/suppliers.

Innovation Solution

Automatically enabling remote support by forming a mesh network among compute, storage, and network assets using positioning beacons that wirelessly communicate and form a peer-to-peer network, allowing assets to connect directly to a remote support gateway with multi-hop redundancy and dynamic routing, reducing single points of failure and simplifying upgrades.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration is used for remote support gateway connections, then setup control and security can be maintained, but configuration complexity increases and SLA compliance decreases

Engineering Contradiction:
ImproveSLA complianceVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Assets automatically perform service discovery, route discovery, and configure their own connections to the remote support gateway without manual intervention. The system self-configures by discovering available gateways, establishing secure connections, and maintaining routing information autonomously

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-configures routing information and gateway credentials in routing data structures before connection is needed. Assets maintain ready-to-use routing tables with gateway information, enabling immediate connection when support is required without configuration delays

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If a centralized remote support gateway is used, then support management is simplified, but single points of failure increase and network coverage is limited

Engineering Contradiction:
Improvesupport managementVSAvoidsingle points of failure
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The centralized gateway system is segmented into multiple distributed gateway instances deployed across different network locations. Each gateway maintains independent routing information and can serve assets in its local area, eliminating single points of failure while maintaining simplified management through standardized protocols

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Assets use routing data structures as intermediaries to discover and connect to available gateways. The routing information acts as a mediator that guides assets to appropriate gateway instances, enabling flexible connection management without direct centralized control

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If manual gateway configuration is required, then security control is maintained, but setup time increases and errors increase

Engineering Contradiction:
Improveconnection consistencyVSAvoidsetup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Assets automatically discover gateways and configure connections without manual intervention. The system performs service discovery, authenticates with gateways, and establishes connections autonomously, eliminating setup time and configuration errors while maintaining security through automated credential verification

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements automated feedback loops where assets continuously discover available gateways, verify connection status, and update routing information. This feedback mechanism ensures consistent connections while eliminating manual configuration delays and errors

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11310718B2Wireless discovery, routing and advertisement protocol for secure remote services in a communication environment
Publication Date: 2022.04.19 EMC IP HLDG CO LLC
  • US11310718B2 patent drawing
  • US11310718B2 patent drawing
  • US11310718B2 patent drawing

AI summary

In a computing environment comprising a plurality of compute, storage and network assets, a method initiates at a given asset a join operation for the given asset to become a member of a mesh network formed by the plurality of compute, storage and network assets. A network neighbor data structure associated with the given asset is created/updated based on the join operation. The method initiates at the given asset a route discovery operation to identify one or more routes through the mesh network to enable the given asset to access a remote support gateway. A network routing data structure associated with the given asset is created/updated based on the route discovery operation. The given asset may also advertise at least a portion of its routing data structure to the compute, storage and network assets in the computing environment.