SDN Controller Flow Class Priority Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In software-defined networking (SDN) environments, applications installed on an SDN controller are not aware of each other's business logic, leading to potential conflicts in priorities when making flow table modifications, especially with dynamic changes in the network.
Innovation Solution
A method is introduced to register flow classes with an SDN controller, determine priorities based on other installed applications and services, modify priorities through an event-driven system by mapping priority keys to new values, and validate flow modification rules to ensure non-conflicting traffic management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If applications on SDN controller are allowed to independently make flow table modifications, then each application can operate autonomously according to its business logic, but priority conflicts occur between applications
Solution Approach 1:
The patent introduces an intermediary mechanism (priority registration and validation system) that mediates between multiple applications. The SDN controller acts as a mediator that receives priority registration requests from applications, validates them against existing priorities, and resolves conflicts before allowing flow table modifications. This prevents priority conflicts while maintaining application autonomy.
Solution Approach 2:
The patent implements feedback mechanisms where the SDN controller provides validation results to applications regarding their priority registration requests. When a priority conflict is detected, the system feedbacks information about the conflict to the application, allowing it to adjust its priority selection. This feedback loop ensures reliable priority management while preserving application independence.
2Device complexity
If static priorities are assigned to applications, then priority management is simple, but the system cannot adapt to dynamic changes in the SDN network
Solution Approach 1:
The patent implements dynamic priority management by allowing applications to register and modify their priorities at runtime based on changing network conditions and business logic requirements. The priority registration mechanism enables priorities to be dynamically adjusted without requiring system reconfiguration, balancing simplicity with adaptability.
Solution Approach 2:
The system allows priority parameters to be changed dynamically through the registration mechanism. Applications can request priority changes by submitting new registration requests with updated priority values, and the SDN controller validates and applies these changes. This enables the system to adapt to dynamic network conditions while maintaining manageable complexity through structured parameter control.
3Reliability
If applications are made aware of each other's business logic, then priority conflicts can be prevented, but system complexity increases
Solution Approach 1:
The patent merges the priority management functionality into the SDN controller itself, combining multiple applications' priority requirements into a unified validation system. Instead of making applications aware of each other's business logic directly, the controller consolidates priority information and handles conflict resolution centrally, preventing conflicts without increasing application-level complexity.
Solution Approach 2:
The priority registration and validation mechanism serves multiple applications simultaneously, providing a universal solution for priority management. The same mechanism handles priority registration, validation, and conflict resolution for all applications on the SDN controller, preventing priority conflicts without requiring application-specific complexity.
Data Source
AI summary
Modifying a priority for at least one flow class of an application includes registering flow classes for an application with a SDN controller, determining, with the SDN controller, a priority for each of the flow classes based on other installed applications and network services on the SDN controller, modifying, based on an event, the priority for at least one of the flow classes of the application by mapping a priority key associated with the priority to a new priority value, receiving, from the application, at least one flow modification rule using a priority key as the priority, and validating the at least one flow modification rule against registered parameters of at least one of the flow classes of the application to determine a flow of traffic based on the priority.