Virtual Cloud Private Network Deployment via Controller Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The provisioning and deployment of virtual cloud private network services are complex and error-prone, relying heavily on technical personnel and lacking efficiency and accuracy.
Innovation Solution
A method and apparatus that utilize a controller to create service and network instances, simplifying the deployment process by using service templates and APIs to automate configuration and deployment of virtual cloud private networks, reducing the need for manual network parameter setting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If service deployment is performed manually by technical personnel, then service quality and security can be ensured, but the deployment process is complex and error-prone
Solution Approach 1:
The system enables automated self-service deployment through the controller that automatically creates service instances, network instances, and configures network parameters without requiring manual technical personnel intervention. The automation engine parses service templates and generates configuration information automatically, reducing human error while maintaining service quality through standardized automated processes.
Solution Approach 2:
The patent transforms the deployment process by changing parameters from manual configuration to automated configuration. The controller automatically generates and configures network parameters such as VLAN IDs, IP addresses, and routing information based on service templates, converting a complex manual parameter-setting process into an automated parameter-generation process that reduces errors while maintaining reliability.
2Productivity
If manual configuration of network parameters is performed, then service deployment can be completed, but deployment workload is heavy and efficiency is low
Solution Approach 1:
The system implements preliminary action by pre-defining service templates that contain all necessary network configuration parameters and structures. Before actual deployment, the templates are prepared and validated, so that during deployment the controller can automatically instantiate services by simply referencing these pre-configured templates, dramatically reducing deployment time and workload without sacrificing configuration accuracy.
Solution Approach 2:
The patent uses copying by creating service instances that replicate the structure and configuration from service templates. Instead of manually configuring each service from scratch, the system copies proven configuration patterns from templates to new service instances, automatically generating network parameters, device configurations, and routing information, which significantly improves deployment efficiency while maintaining consistency and reducing errors.
3Extent of automation
If automated service deployment is implemented, then deployment efficiency is improved, but the system requires complex control mechanisms
Solution Approach 1:
The patent introduces an intermediary controller that mediates between the automated deployment requirements and the underlying network infrastructure. The controller serves as a smart intermediary that automatically parses service templates, generates configuration information, and manages the creation of service and network instances. This intermediary approach automates deployment while managing system complexity by centralizing control logic in the controller rather than distributing it across multiple complex components.
Data Source
AI summary
A method for deploying a service includes a controller that creates a service instance corresponding to a service, and creates, in the service instance, a first network instance and a second network instance that correspond to the service. The first network instance is a network instance corresponding to a first device, and the first network instance includes a device identifier of the first device. The second network instance is a network instance corresponding to a first cloud provider edge PE, and the second network instance includes a device identifier of the first cloud PE. The first cloud PE is for connecting to the first cloud.