Service Chaining via SDN Microflow Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network architectures face challenges in efficiently steering packet traffic through multiple inline services due to vendor lock-in, complex configuration requirements, and high costs associated with traditional router designs, which limits flexibility and scalability.
Innovation Solution
A method and system for steering packet traffic using a microflow table and service chain identifier to determine the next service instance, allowing for load balancing and flexible service chaining across multiple virtual instances, decoupling service deployment from specific hardware and enabling programmable infrastructure within a cloud environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional monolithic router designs are used to meet increasing bandwidth demands, then network performance is improved, but device complexity and cost increase significantly
Solution Approach 1:
The patent segments the network infrastructure into multiple simplified switching elements instead of using a single monolithic router. Each switch handles basic forwarding with simplified logic, while a centralized controller manages complex routing decisions. This segmentation allows the system to scale bandwidth capacity by adding more simple switches rather than upgrading complex routers.
Solution Approach 2:
The patent introduces a centralized controller as an intermediary between the simplified switching elements and the network traffic. The controller receives forwarding rules from operators and distributes them to switches, managing complex routing logic centrally while keeping individual switches simple. This intermediary enables sophisticated network management without increasing the complexity of the forwarding plane devices.
2Ease of manufacture
If vendor-specific mechanisms are used for service chaining, then service deployment is simplified, but adaptability and flexibility decrease due to vendor lock-in
Solution Approach 1:
The patent creates a universal service chaining mechanism that works across multiple vendor components. The centralized controller uses a standardized interface to manage service chains across switches from different vendors, allowing operators to mix and match components freely. This universal approach maintains ease of service deployment through centralized management while eliminating vendor lock-in and increasing adaptability.
Solution Approach 2:
The patent changes the control parameter from vendor-specific proprietary protocols to a standardized, vendor-neutral control interface. The centralized controller communicates with switches using a universal protocol that abstracts away vendor-specific implementations, allowing the same service chaining logic to be applied across different hardware platforms without modification.
3Manufacturing precision
If detailed low-level configuration is used for packet delivery customization, then traffic handling precision is improved, but ease of operation decreases
Solution Approach 1:
The centralized controller acts as an intermediary that translates high-level operator intent into detailed low-level configuration rules. Operators simply specify their traffic handling requirements at a high level, and the controller automatically generates and distributes the necessary forwarding rules to the appropriate switches, eliminating the need for operators to manually configure complex low-level parameters.
Solution Approach 2:
The system implements feedback loops where the centralized controller monitors network traffic patterns and automatically adjusts forwarding rules to optimize traffic handling. This feedback mechanism maintains high precision in traffic handling while reducing operational complexity, as the system self-adjusts based on observed conditions rather than requiring manual reconfiguration.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system and method for steering traffic through a set of services is provided. A service path or service chain is assigned to a received packet based on a classification of the packet and correlation of the packet with a traffic flow. A new service chain identifier can be created if no such correlation exists. A next service type and a particular instance of the next service type can be determined in accordance with the service chain identifier. A next destination for the traffic can be set in accordance with the instance of the next service.