SDN Controller Service Chaining via Application Type Registry
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In software-defined networks (SDNs), naive service chaining lacks awareness of the applications being chained, leading to potential interference, inefficient resource usage, and duplication of core functions, which affects performance and computation resources.
Innovation Solution
Implementing a service-aware SDN controller with a service data table that associates applications with types, allowing for optimized chaining by defining the order of application types and using service insertion points to manage interactions and synergies between applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If naïve chaining of applications is used in SDN, then service chain configuration is simple and flexible, but applications may interfere with each other and performance deteriorates
Solution Approach 1:
The patent introduces an SDN controller as an intermediary between applications in the service chain. The controller maintains a service data table that tracks application types and their interactions, mediating the chaining process to prevent harmful interactions while maintaining configuration flexibility. The controller inserts service chain entries based on application type compatibility, acting as a mediator that ensures reliable application interactions without sacrificing adaptability.
2Loss of time
If naïve chaining of applications is used in SDN, then service chain setup is quick, but computation resources are wasted due to duplication of core functions
Solution Approach 1:
The patent implements a service data table in the SDN controller that maintains a registry of application types and their core functions. When configuring service chains, the controller checks this table to identify and prevent duplication of core functions across applications. This universal tracking mechanism allows quick service chain setup while avoiding computation resource waste by ensuring each core function is executed only once in the service chain.
3Ease of operation
If application order is not controlled in service chaining, then configuration is easier, but application interference increases and performance decreases
Solution Approach 1:
The patent changes the parameter of service chain configuration from uncontrolled application ordering to controlled ordering based on application types. The SDN controller uses the service data table to determine the optimal order of applications in the service chain, considering their types and potential interactions. This parameter change maintains ease of operation by automating the ordering process while significantly improving productivity by preventing application interference and optimizing processing efficiency.
Data Source
AI summary
A method and a software defined network (SDN) controller for chaining applications in a SDN. A service data table is created in the SDN controller. In the service data table a plurality of applications are associated with a plurality of application types. Furthermore, at least one service chain is created in the SDN controller. The at least one service chain defines an order of application types running on the SDN controller. At least one application is registered to the service chain based on its application type as associated with the application in the service data table.