Network Operations Gateway Configuration Synchronization for Reliability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional on-premise computing infrastructure management systems face challenges such as network unavailability due to single point of failure, cascading failures, and security vulnerabilities from relying on a single Network Operations Gateway (NOG), leading to business disruption and potential financial losses.

Innovation Solution

Implementing a system with multiple Network Operations Gateway modules (NOG1 and NOG2) synchronized by a tag-based synchronization module, ensuring consistent configurations across the infrastructure, reducing manual intervention, and enhancing network reliability and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single Network Operations Gateway (NOG) is used for managing network infrastructure, then device complexity is reduced and ease of operation is improved, but reliability deteriorates due to single point of failure

Engineering Contradiction:

Improvenetwork availabilityVSAvoidsystem architecture

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system divides the single NOG into multiple NOG instances (first NOG and second NOG), each managing specific network devices. This segmentation eliminates the single point of failure while distributing management responsibilities across multiple independent instances.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Each NOG instance is assigned specific management responsibilities for particular network devices or regions. The first NOG manages certain devices while the second NOG manages others, creating localized management zones that improve reliability without requiring complete system redesign.

Inventive Principle:

Principle #3Local quality

2Reliability

If multiple Network Operations Gateway modules are deployed for improved reliability, then network availability is enhanced, but configuration synchronization complexity increases

Engineering Contradiction:

Improvenetwork availabilityVSAvoidconfiguration management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The synchronization module continuously monitors configuration states across multiple NOG instances and automatically detects discrepancies. When configuration drift is detected, the system initiates corrective synchronization actions to maintain consistency, creating a closed-loop feedback mechanism.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The synchronization module operates autonomously to reconcile configurations between NOG instances without requiring manual intervention. It automatically detects configuration differences and applies necessary corrections, enabling the system to self-maintain configuration consistency.

Inventive Principle:

Principle #25Self-service

3Productivity

If manual configuration management is used for simplicity, then ease of operation is maintained, but productivity decreases due to time-consuming manual interventions

Engineering Contradiction:

Improveconfiguration deployment speedVSAvoidoperational simplicity

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

Configuration changes are developed and validated in advance in a development environment before being automatically deployed to production NOG instances. This preliminary action enables rapid, error-free configuration deployment without requiring manual step-by-step execution.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system replaces manual mechanical configuration processes with automated software-based configuration management. Configuration changes are propagated automatically across NOG instances through digital synchronization, eliminating the need for manual configuration entry and reducing deployment time.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If a single NOG is used as a centralized management point, then ease of operation is improved, but security deteriorates due to attractive target for cyber-attacks

Engineering Contradiction:

Improvesecurity resilienceVSAvoidcentralized management

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The centralized NOG is segmented into multiple distributed NOG instances, each managing specific network devices. This distribution eliminates the single attractive target for attacks while maintaining centralized-like coordination through the synchronization module.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The synchronization module acts as an intermediary that coordinates between multiple NOG instances without requiring a single centralized management point. It enables centralized management functionality while distributing security risks across multiple instances.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentEP4645109A1Method and system for managing a computing infrastructure

Publication Date: 2025.11.05 OVH

Figure 1~2
Figure 3~4b
Figure 4c~4d

AI summary

A method (400) for managing configurations of a computing infrastructure involves accessing instructions that provision Network Operations Gateways with network devices and a synchronization module to reconcile their configurations. The synchronization module uses tags associated with objects in the network and sets of rules to detect and create Virtual Service Networks, replicating endpoints between gateways through data synchronization.