Service Model Flow Table Configuration for SDN Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current SDN technologies face low conversion efficiency and high development and maintenance costs when converting PTN service configuration into TTP flow table configuration.
Innovation Solution
Introducing a service model to map attributes of a forwarding device's flow table, determining changes in the service model caused by configuration changes, and generating flow entries to simplify and universalize flow table configuration, thereby reducing complexity and costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If PTN service configuration is converted into TTP flow table configuration using existing methods, then the flow table can be configured, but the conversion efficiency is low and development and maintenance costs are high
Solution Approach 1:
The patent introduces a service model as an intermediary layer between the PTN service configuration and the TTP flow table configuration. The service model defines abstract service characteristics and behaviors that can be mapped to both the service configuration and the flow table, thereby simplifying the conversion process and reducing complexity. This intermediary model enables automated generation of flow table configurations from service configurations without requiring complex manual conversion processes.
Solution Approach 2:
The service model is designed to be universal and platform-independent, capable of representing various service types and their characteristics in a unified manner. By defining service behaviors and characteristics at the model level rather than at the specific implementation level, the same service model can be used across different service configurations and map to different flow table implementations, thereby improving conversion efficiency and reducing development costs.
2Adaptability or versatility
If service configuration is directly mapped to flow table configuration, then configuration can be achieved, but the complexity of flow table configuration increases and universality is reduced
Solution Approach 1:
The patent segments the configuration process into distinct layers: the service configuration layer, the service model layer, and the flow table configuration layer. Each layer has its own characteristics and rules, and the service model acts as an abstract representation that separates the service logic from the implementation details. This segmentation allows the service configuration to remain simple and universal while the flow table configuration is generated automatically from the service model, reducing complexity.
Solution Approach 2:
The service model serves as an intermediary that decouples the service configuration from the flow table configuration. By defining service characteristics and behaviors in the model layer, the system achieves universality at the service level while automatically generating specific flow table configurations at the implementation level, thereby reducing the complexity of flow table configuration and improving adaptability.
3Reliability
If individual manufacturers develop dedicated operating systems and hardware for each service, then service characteristics are optimized, but development and maintenance costs increase
Solution Approach 1:
The service model provides a universal framework that can represent various service characteristics and behaviors in a platform-independent manner. Instead of requiring individual manufacturers to develop dedicated operating systems and hardware for each service, the service model enables a standardized approach where service logic is defined once and can be mapped to different underlying implementations, thereby reducing development and maintenance costs while maintaining service optimization.
Solution Approach 2:
The service model acts as an intermediary layer that separates service logic from hardware implementation details. This allows service characteristics to be optimized at the model level without requiring manufacturer-specific operating systems or hardware for each service. The service model can be mapped to different hardware platforms and implementations, reducing the need for duplicate development and maintenance efforts across manufacturers.
Data Source
Figure 1~2
Figure 3(a)~3(b)
Figure 4
AI summary
Disclosed are method and device for driving a flow table by service configuration. The method includes: mapping attributes concerned by a flow table of a forwarding device to a service model to complete registration of the flow table on the service model; determining a change in a related object of the service model caused by a change in service configuration, and mapping the change in the related object of the service model to a corresponding flow table and driving the flow table to generate a flow entry.