Routing Configuration Templates for Enterprise Cloud Interconnects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of network configurations in connecting enterprise sites to cloud service providers becomes unmanageable due to the increasing number of virtualized network functions that need to be combined in various combinations, making the traditional brute force approach of hand-crafted individual configurations unsustainable.
Innovation Solution
The implementation of a set of interconnection routing configuration templates that can be applied recursively to provide a consistent and scalable approach for configuring network segments, allowing for automated configuration of routers to establish connectivity between enterprise sites and cloud service providers, using a routing configuration server with processor and memory to apply specific templates for different types of cloud service providers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If hand-crafted individual configurations are used for network segments, then network connectivity can be established, but the complexity of network configurations becomes unmanageable
Solution Approach 1:
The patent segments the network configuration into standardized templates that can be independently defined and reused. Each template represents a modular unit of network segment configuration, allowing complex end-to-end connectivity to be built from manageable, pre-defined components rather than hand-crafting entire configurations.
Solution Approach 2:
The patent creates universal routing configuration templates that can be applied across multiple network segments and scenarios. These templates serve multiple functions: defining routing behavior, establishing connectivity patterns, and ensuring consistent configuration across different network segments, eliminating the need for unique hand-crafted configurations for each segment.
2Adaptability or versatility
If numerous virtualized functions are inserted in arbitrary combinations, then service flexibility is improved, but the brute force approach of hand-crafted configurations is no longer viable
Solution Approach 1:
The patent performs preliminary action by pre-defining routing configuration templates that encapsulate common network segment configurations. These templates are prepared in advance with all necessary routing parameters and logic, so that during deployment, service chains can be rapidly instantiated by selecting and applying appropriate templates rather than crafting configurations from scratch for each virtualized function combination.
Solution Approach 2:
The patent implements nesting by allowing routing configuration templates to contain nested sub-templates or parameter sets that can be recursively applied. This enables complex service chains with multiple virtualized functions to be constructed by nesting simpler configuration patterns within more comprehensive templates, maintaining flexibility while reducing deployment complexity.
3Productivity
If routing configuration templates are applied recursively, then deployment scalability is improved, but configuration standardization is required
Solution Approach 1:
The patent enables recursive application of routing configuration templates by designing them with parameterized variables that can be dynamically instantiated. The same template structure can be reused across different network segments with different parameter values (such as network segment identifiers, routing protocol parameters, or cloud service provider-specific settings), allowing rapid scalable deployment without creating new configurations for each segment.
Data Source
AI summary
In a network service provider environment, a number of interconnection routing configuration templates provide a consistent approach for configuring associated interconnect network segments between enterprise network customer sites and cloud service providers. At least two types of configuration template are used to create at least two types of routing arrangement: a first template for creating an “unconstrained” routing arrangement having “any to any” connections; and a second template for creating a “partitioned” routing arrangement in which traffic between partitions must be operated on by a virtual network function. Additionally, the “partitioned” routing arrangement may use either a shared VPN or a segregated VPN facing the cloud service providers. The use of the interconnection routing configuration templates may be automated. The interconnection routing configuration templates can be applied in a recursive fashion to different parts of the end-to-end connectivity.