Cloud Network Automation via Topology Modeling and ZTP

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual and time-consuming process of setting up and managing complex cloud networks, such as CLOS networks, is challenging due to the need for individual configuration of numerous devices from different vendors, leading to scalability issues and increased complexity as the network size grows.

Innovation Solution

A centralized Network Deployment System (NDS) automates network configuration and management using a network model that encapsulates topology, component information, and configurations, enabling Zero Touch Provisioning (ZTP) for device provisioning without human intervention, and is vendor-agnostic to simplify the process across different network components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration is used for each network device, then individual device control is precise, but the setup time and operational complexity increase significantly

Engineering Contradiction:
Improvenetwork setup easeVSAvoidsetup time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system pre-configures network devices by provisioning templates and configuration files that are prepared in advance. The Network Deployment System automatically applies these pre-prepared configurations to devices during deployment, eliminating the need for manual real-time configuration and significantly reducing setup time while maintaining operational precision.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Network devices perform self-configuration through Zero Touch Provisioning (ZTP). When devices are deployed, they automatically discover their network position, retrieve appropriate configuration files, and apply settings without human intervention. This self-service approach dramatically reduces setup time while the centralized NDS maintains control through automated validation.

Inventive Principle:
Principle #25Self-service

2Productivity

If network size increases to meet processing demands, then processing capability improves, but management complexity increases

Engineering Contradiction:
Improveprocessing capabilityVSAvoidnetwork management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments network management into distinct functional layers: the centralized Network Deployment System handles high-level topology management and policy enforcement, while individual devices handle local configuration application. This segmentation allows the system to scale processing capability without proportionally increasing management complexity, as each segment operates independently with clear responsibilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The Network Deployment System acts as an intermediary between network administrators and individual devices. It provides a simplified interface for managing large-scale networks by automatically translating high-level network models into device-specific configurations, thereby maintaining manageable complexity even as network size and processing capability increase.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If vendor-specific configurations are used, then device compatibility is ensured, but system adaptability to different vendors decreases

Engineering Contradiction:
Improvedevice compatibilityVSAvoidvendor agnosticism
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system employs universal configuration templates and standardized network models that can be applied across multiple vendor devices. The Network Deployment System maintains a library of vendor-specific provisioning templates that are automatically selected based on device identification, allowing a single unified system to manage diverse vendor equipment reliably while maintaining vendor-agnostic design principles.

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

Data Source

PatentUS11290332B2System and method for modelling cloud networks for automation
Publication Date: 2022.03.29 ORACLE INT CORP
  • US11290332B2 patent drawing
  • US11290332B2 patent drawing
  • US11290332B2 patent drawing

AI summary

The present is directed to systems, methods, and devices for modelling cloud networks for automation, The system can include a computing network including at least one transit router and a plurality of switches. The system can include at least one server that can access model information for the computing network, and set up the computing network based upon the model information. Setting up the computing network can include creating a topology database, and building the computing network based on the topology database. The topolopgy data can be created by creating switches at each layer in the computing network, mapping links connecting the switches, each link connecting a pair of switches, creating Border Gateway Protocol (“BGP”) routing for both an underlay network and an overlay network, creating a topology graph of the computing network, and generating Zero Touch Provisioning (“ZTP”) links.