Gateway Peer Connection Remediation via Failure Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In computing environments, the connection between active and standby gateways can become unstable, leading to data-path loss and instability in establishing the active gateway in a peered configuration.

Innovation Solution

A method is implemented where a first gateway monitors failure information associated with a peer connection with a second gateway and determines when the failure information satisfies certain criteria. Upon satisfaction of these criteria, the gateway initiates a remediation period that stops connection attempts, and after the remediation period expires, it attempts to reestablish the peer connection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If connection attempts are continuously made to establish peer connection between gateways, then connection reliability is improved, but system stability deteriorates due to fluctuating gateway status and data-path loss

Engineering Contradiction:
Improvepeer connection reliabilityVSAvoidgateway status stability
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The patent implements periodic connection attempts with a remediation period inserted after detecting a threshold number of failures. This periodic action pattern (attempt → monitor → pause if failures exceed threshold → retry after remediation period) prevents continuous unstable connection attempts while maintaining eventual connection reliability, directly resolving the contradiction between connection reliability and gateway status stability.

Inventive Principle:
Principle #19Periodic action

2Reliability

If multiple connection attempts are made to ensure peer connection establishment, then connection establishment success is improved, but data-path loss increases due to unstable connections

Engineering Contradiction:
Improvepeer connection establishmentVSAvoiddata-path loss
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The patent applies preliminary anti-action by implementing a preventive mechanism that stops connection attempts when a threshold of failures is detected, before further data-path loss can occur. The remediation period acts as a preventive measure that anticipates potential data loss from unstable connections and proactively halts connection attempts, thereby reducing data-path loss while preserving essential connection establishment capability.

Inventive Principle:
Principle #9Preliminary anti-action

3Stability of the object's composition

If connection attempts are stopped during remediation period, then gateway status stability is improved, but connection establishment time increases

Engineering Contradiction:
Improvegateway status stabilityVSAvoidconnection establishment time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-defining a remediation period duration and connection attempt thresholds before failures occur. This allows the system to quickly determine when to pause and when to retry without complex real-time decisions, maintaining gateway status stability while minimizing connection establishment time through pre-configured parameters that optimize the balance between stability and speed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250080402A1Limiting peer connection attempts based on failures in peer connection
Publication Date: 2025.03.06 VMWARE INC
  • US20250080402A1 patent drawing
  • US20250080402A1 patent drawing
  • US20250080402A1 patent drawing

AI summary

Described herein are systems, methods, and software to manage connection attempts between gateways. In one implementation, a first gateway monitors failure information associated with a peer connection with a second gateway and determines when the failure information satisfies criteria. When the failure information satisfies criteria, the first gateway notifies the second gateway and a management service of the failure and initiates a remediation period for communications associated with the peer connection. In response to the expiration of the remediation period, the first gateway initiates a connection attempt with the second gateway.