Cloud Network Topology Testing via Dynamic Orchestration API

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network development and testing tools are limited by static configuration files that require the entire network topology to be taken down for modifications, and they only support process simulations that are not directly deployable on physical routers and switches, lacking flexibility and realism in virtual router and switch simulations.

Innovation Solution

A cloud-hosted sandbox environment with a unified API allows network developers to configure and test network topologies dynamically, using software images for virtual network elements that can emulate physical routers and switches, enabling flexible configuration and testing without requiring the network to be taken down, and ensuring that the test environment matches real-world topologies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static configuration files are used to define network topology, then the system structure is simple, but any modification requires taking down the entire topology

Engineering Contradiction:
Improvenetwork topology modification capabilityVSAvoidconfiguration modification efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent transforms the static configuration file system into a dynamic one by introducing an orchestration layer that can programmatically configure and reconfigure network elements. This layer enables runtime modifications to network topology without requiring complete system shutdown, allowing dynamic adaptation while maintaining operational continuity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The orchestration layer acts as an intermediary between the control plane and data plane, mediating configuration changes. It receives high-level configuration instructions and translates them into specific actions for individual network elements, enabling modular and non-disruptive topology modifications.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If process simulations are used for virtual routers and switches, then the system complexity is reduced, but the simulations are not directly deployable on physical devices

Engineering Contradiction:
Improvedeployment readinessVSAvoidsimulation system complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent creates virtual copies of physical network devices that run simplified software images. These virtual instances replicate the essential behavior of physical routers and switches, allowing testing and development in a controlled environment while maintaining compatibility with actual deployment scenarios.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system allows dynamic adjustment of software image parameters and device configuration settings. By modifying software parameters rather than rewriting entire simulation models, the system can adapt virtual devices to match physical device behavior, bridging the gap between simulation and deployment.

Inventive Principle:
Principle #35Parameter changes

3Manufacturing precision

If the entire network topology is taken down for configuration updates, then configuration accuracy is ensured, but testing time and operational continuity are lost

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidtopology downtime
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The orchestration layer performs preliminary validation and verification of configuration changes before applying them to the network. Configuration instructions are checked for consistency and correctness in advance, ensuring accuracy while enabling incremental updates that maintain network operation throughout the process.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If multiple interfaces are required for network development and testing, then functionality is comprehensive, but ease of operation is reduced

Engineering Contradiction:
Improvedevelopment capabilityVSAvoidinterface usability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent merges multiple development and testing interfaces into a single unified orchestration layer. This consolidated interface provides comprehensive control over network element configuration, software image management, and topology modification, eliminating the need to switch between multiple tools while maintaining full functionality.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The orchestration layer is designed as a universal platform that performs multiple functions: configuring network elements, managing software images, validating configurations, and coordinating deployments. This multi-functional approach consolidates previously separate tools into a single system that handles the entire development and testing workflow.

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

Data Source

PatentUS9838294B2Network development and testing as a cloud service
Publication Date: 2017.12.05 CISCO TECHNOLOGY INC
  • US9838294B2 patent drawing
  • US9838294B2 patent drawing
  • US9838294B2 patent drawing

AI summary

Presented herein are techniques to receive configuration instructions for elements of a network topology to be simulated and tested. In response to receiving and in accordance with the configuration instructions, a plurality of software images (for a plurality of virtual network elements of the network topology) are configured via an Application Programming Interface (API). The plurality of software images run in a cloud host. In response to receiving and in accordance with the configuration instructions, data is configured via the API, which represents one or more connections between the virtual network elements. A plurality of software images for the plurality of virtual network elements is then executed in accordance with the data representing the connections, for development and testing of the network topology.