Intent-Based Network Configuration Pull Model for Multi-Tenant SD-WAN

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current SDWAN networks face scalability issues with traditional configuration delivery mechanisms, leading to increased convergence times, resource wastage, and security vulnerabilities due to synchronous interactions between network controllers and edge devices, especially in large networks with multi-tenant configurations.

Innovation Solution

Implementing a pull model for configuration file delivery using a transaction ID and REST APIs, allowing asynchronous interactions between network controllers and devices, enabling efficient resource utilization and concurrent multi-tenant configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If traditional push-based configuration delivery mechanisms (SSH, netconf, RPC) are used, then configuration files can be delivered to network devices, but convergence time increases exponentially with network scale and controller resources are wasted

Engineering Contradiction:

Improveconfiguration convergence timeVSAvoidconfiguration deployment efficiency

Core Design Contradiction:

Loss of timeVSProductivity

Solution Approach 1:

The patent inverts the traditional push-based configuration delivery model by implementing a pull-based model where edge devices autonomously retrieve configuration files from the controller using REST APIs, eliminating the need for controller-initiated push operations and reducing controller resource consumption

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

Edge devices are empowered to self-serve by automatically pulling configuration files from the controller when needed, without requiring continuous controller intervention or monitoring, thereby improving deployment efficiency and reducing operational overhead

Inventive Principle:

Principle #25Self-service

2Reliability

If traditional synchronous configuration delivery is used, then configuration files are delivered to edge devices, but network exposure to security vulnerabilities increases due to extended convergence times

Engineering Contradiction:

Improvenetwork security postureVSAvoidconfiguration convergence duration

Core Design Contradiction:

ReliabilityVSDuration of action of moving object

Solution Approach 1:

The pull model enables continuous configuration synchronization where edge devices can autonomously retrieve updated configurations as needed, ensuring the network maintains an up-to-date security posture without extending convergence windows through controller-bound operations

Inventive Principle:

Principle #20Continuity of useful action

3Adaptability or versatility

If multi-tenant configurations are handled using traditional mechanisms, then multiple tenants can share control plane devices, but concurrency challenges arise when tenants attempt to change policy configurations simultaneously

Engineering Contradiction:

Improvemulti-tenant configuration supportVSAvoidconcurrency management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments configuration management by tenant, with each tenant's configuration operations independently pulled and processed by edge devices using transaction IDs, eliminating concurrency conflicts that would otherwise require complex coordination mechanisms

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Each tenant's configuration is treated as an independent copy with its own transaction ID, allowing multiple tenants to simultaneously retrieve and apply their respective configurations without interfering with each other, thereby simplifying concurrency management

Inventive Principle:

Principle #26Copying

4Manufacturing precision

If larger configuration files are delivered using traditional protocols, then complete network policies can be deployed, but resource wastage and convergence delays increase

Engineering Contradiction:

Improveconfiguration accuracyVSAvoidcontroller resource consumption

Core Design Contradiction:

Manufacturing precisionVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary configuration data that each edge device needs to pull, rather than pushing complete configuration files, thereby reducing network bandwidth consumption and controller resource usage while maintaining configuration accuracy

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS12568014B2Distribution of intent based network configuration of network devices including multi-tenant network devices

Publication Date: 2026.03.03 CISCO TECHNOLOGY INC

AI summary

Techniques and architecture are described for a pull model for obtaining and implementing config changes on network devices are described herein. A user submits intent configuration to the network controller that needs to be delivered to several network sites. The network controller generates a config file. The network controller sends a pull notification message to all network devices that need to retrieve the config file. This pull notification message only contains a corresponding transaction ID for each network device and a location for the network device to use to pull the config file. The network devices may utilize a HTTP REST API exposed by the network controller to obtain the config file from the network controller. The network devices may utilize a REST API exposed by the network controller to reply with statuses of the configuration transaction. The techniques and architecture may be applied to multi-tenant network devices.