Intent-Driven Cloud Branches via SDN Templates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network technologies face challenges such as insufficient bandwidth, high bandwidth costs, application downtime, poor service performance, complex operations, and security issues, particularly in deploying and managing remote branches in software-defined networks, which are time-consuming and costly.
Innovation Solution
The implementation of intent-driven network branches using a software-defined network (SDN) architecture, where a branch network design template and software packages are used to automatically provision and configure network services and resources, enabling efficient and dynamic deployment of virtual machines, virtual network functions, and service chains based on specified intent.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If manual deployment methods are used for remote branches, then deployment accuracy and customization can be achieved, but deployment time and operational complexity increase significantly
Solution Approach 1:
The patent applies preliminary action by creating branch templates that pre-define network configurations, policies, and service settings. These templates are prepared in advance and can be automatically instantiated when a branch is deployed, eliminating the need for manual configuration during deployment while ensuring accuracy and consistency with enterprise standards.
Solution Approach 2:
The patent uses copying by allowing branch templates to be replicated and instantiated multiple times across different locations. Once a template is created with the desired configuration, it can be copied to deploy identical or customized branches rapidly, reducing deployment time while maintaining configuration accuracy through template-driven consistency.
2Stability of the object's composition
If traditional network architecture is used, then existing infrastructure can be maintained, but scalability and adaptability to cloud services are limited
Solution Approach 1:
The patent applies universality by designing a branch template system that can accommodate multiple service types and configurations within a unified framework. The templates support various network services, security policies, and application requirements, allowing the same infrastructure to adapt to different cloud service needs while maintaining stability through standardized template-based deployment.
Solution Approach 2:
The patent implements dynamics by enabling branch templates to be dynamically instantiated, modified, and scaled based on operational needs. Branches can be quickly deployed, updated, or terminated by manipulating templates, allowing the network infrastructure to adapt flexibly to changing cloud service requirements while maintaining structural stability through the template framework.
3Reliability
If more network services are provisioned at remote branches, then service performance and functionality improve, but deployment complexity and resource requirements increase
Solution Approach 1:
The patent applies preliminary action by pre-configuring service chains and networking settings within branch templates. Complex service configurations, including multiple virtual network functions and service chains, are prepared in advance in the template, so they can be automatically instantiated without manual configuration during deployment, reducing complexity while maintaining service performance.
Solution Approach 2:
The patent uses merging by combining multiple service configurations, policies, and networking settings into a single unified branch template. This consolidation allows complex service stacks to be managed as one cohesive unit, reducing deployment complexity while ensuring all necessary services are provisioned together with consistent configurations.
Data Source
AI summary
Methods, systems, and non-transitory computer-readable media are provided for deploying intent-driving cloud branches. An example method can include obtaining, by one or more controllers in a software-defined network (SDN), a branch network design template for deploying a remote branch in the SDN, wherein the branch network design template defines networking settings for a plurality of services to be provisioned at the remote branch; obtaining, by the one or more controllers, a plurality of software packages for the plurality of services to be provisioned at the remote branch; and based on the branch network design template and the plurality of software packages, provisioning, by the one or more controllers, the plurality of services at the remote branch and a network connectivity of the plurality of services.