Service Template Orchestration for WAN Policy Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing SDN solutions cannot orchestrate WAN side services effectively due to the inability to utilize service policies as parameters during service provisioning, limiting their applicability in scenarios requiring dynamic configuration.
Innovation Solution
A method and apparatus that incorporate service attributes, policies, and parameters into a unified service template for WAN side services, allowing dynamic configuration and orchestration by an orchestrator and controller, enabling the inclusion of service policies in the service provisioning process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If service policies are excluded from service template parameters in SDN orchestration, then the existing SDN solution maintains its simplicity and parameter-based orchestration capability, but WAN side services cannot be effectively orchestrated due to inability to incorporate service policies
Solution Approach 1:
The service template is segmented into distinct components: service attributes (existing parameters), service policies (new inclusion), and service configurations (generated output). This segmentation allows each component to serve its specific function while maintaining overall system organization and manageability.
Solution Approach 2:
The patent adds a new dimension to the service template by incorporating service policies as a separate configurable element alongside traditional service attributes. This dimensional expansion transforms the template from a parameter-only structure to a multi-layered structure that can accommodate both parameters and policies, enabling WAN side service orchestration without compromising existing SDN capabilities.
2Productivity
If service policies are converted to service configurations during orchestration, then WAN side services can be provisioned dynamically, but the conversion process increases the complexity of the orchestration workflow
Solution Approach 1:
Service policies are predefined and incorporated into the service template before orchestration execution. This preliminary preparation allows the conversion from policies to configurations to occur automatically during the orchestration process itself, rather than requiring separate manual conversion steps, thereby improving provisioning efficiency while keeping the process manageable.
Solution Approach 2:
The service template acts as an intermediary structure that bridges service policies and service configurations. It provides a standardized format for expressing policies and automatically translates them into executable configurations, simplifying the conversion process and reducing orchestration workflow complexity.
3Adaptability or versatility
If service policies are included as part of the service template options, then dynamic configuration of WAN side services is enabled, but the template structure becomes more complex requiring additional fields and options
Solution Approach 1:
The service template structure is segmented into clearly defined sections: service attributes for basic parameters, service policies for configuration rules, and service configurations for generated outputs. This segmentation provides a systematic organization that manages complexity through structured decomposition.
Solution Approach 2:
The service template is designed as a universal structure that can accommodate both traditional SDN service attributes and new service policies. This multi-functional template can serve various service types and orchestration scenarios, providing flexibility and adaptability while maintaining a consistent, manageable structure through standardized field definitions.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
This application belongs to the field of service orchestration and discloses a service orchestration method and apparatus, and a service provisioning method and apparatus. The method includes: obtaining a service template, where the service template includes the following options: a service attribute used to describe a service, a service policy used to configure the service, and a service parameter that can be filled in by a user; obtaining a service identity, a service attribute, and a service policy that are entered by an operator and a default service parameter; filling in the options of the service template with the service attribute and the service policy that are entered by the operator and the default service parameter; associating the service template that is filled in with the service identity; and storing the service template that is associated with the service identity in a service type library, and publishing the service template to the user.