SDN Controller Templates for Faster Multi-Vendor Service Instantiation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In modern communications networks, service instantiation and management are labor-intensive processes due to vendor-specific equipment, leading to long lead times, intertwined service and network configurations, and complex changes that require iterative testing, resulting in delayed and obsolete deployments.
Innovation Solution
A software defined network controller that separates control and data planes, uses templates and directed graphs to automate service creation, and supports multi-vendor environments, enabling rapid service instantiation and management through abstraction layers and cloud orchestration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If vendor-specific equipment is used for service instantiation, then service functionality can be provided, but service deployment time increases and productivity decreases
Solution Approach 1:
The patent segments service functionality into standardized network functions that can be independently deployed and composed. By breaking down vendor-specific monolithic services into modular network functions with standardized interfaces, the system enables flexible service creation without requiring custom vendor equipment for each service, thus improving deployment speed while maintaining adaptability.
Solution Approach 2:
The patent implements a universal service instantiation framework that can accommodate multiple vendor equipment through standardized interfaces and abstraction layers. This universal approach allows the same service deployment mechanism to work across different vendor equipment, eliminating the need for vendor-specific manual configuration processes and significantly improving productivity.
2Adaptability or versatility
If control plane and data plane are integrated, then vendor equipment can provide services, but service and network configurations become intertwined increasing complexity
Solution Approach 1:
The patent applies segmentation by separating the control plane from the data plane, allowing independent management of service logic and network forwarding. This separation enables service configurations to be defined independently from network equipment configurations, reducing the intertwining complexity while maintaining the ability to provision services across multiple vendors.
3Reliability
If iterative testing is performed for service deployment, then service reliability can be ensured, but deployment time increases and services may become obsolete
Solution Approach 1:
The patent implements preliminary action through automated service templates and pre-configured network function compositions. By preparing service definitions, resource allocations, and configuration templates in advance, the system enables rapid service deployment without requiring extensive iterative testing and manual configuration, thus reducing deployment lead time while maintaining reliability through automated validation.
4Adaptability or versatility
If manual service creation process is used, then service can be defined and deployed, but labor intensity increases and deployment efficiency decreases
Solution Approach 1:
The patent implements self-service automation where the system automatically generates service configurations, allocates resources, and deploys network functions based on high-level service definitions. This automation eliminates the need for manual handoffs between product managers, system engineers, and software designers, significantly reducing labor intensity while maintaining service creation capability.
Data Source
AI summary
Concepts and technologies are disclosed herein for providing and using a software defined network controller. A software defined network controller can be provided by a computing system that includes a processor. A service model that represents a service can be obtained. A network model that represents network resources that support the service can be obtained. Resources that support the service can be determined. Templates can be accessed to identify templates that relate to the resources. The templates identified can be assembled to obtain a template-based representation of the service. The template-based representation can be executed to determine if the service is ready for deployment.