SDN Service Path Table Caching for Network Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing SDN-based networks, manual configuration of edge switches is required for service settings, leading to unnecessary latency and resource expenditure, as all incoming packets are forwarded to a service provider, even if they pass service rules, resulting in inefficiencies.
Innovation Solution
Implementing a network controller that manages network services by determining applicable services for packets, creating forwarding entries in a service path table, and updating these entries based on service results, allowing follow-on packets to be handled locally without reconfiguring edge switches or sending them to the service provider.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all incoming packets are forwarded to the service provider for service rule evaluation, then service security and policy compliance are ensured, but network latency increases and network resources are wasted
Solution Approach 1:
The system performs preliminary service rule evaluation on the first packet of each traffic flow by forwarding it to the service provider. The service provider evaluates the packet against service rules and returns service results. These results are then cached in a flow table at the edge switch, allowing subsequent packets in the same flow to be handled locally without repeated service provider interactions, thus reducing latency while maintaining security.
Solution Approach 2:
The system implements differentiated handling for different packets within the same traffic flow. The first packet receives full service provider evaluation, while follow-on packets are handled locally using cached service results. This local quality approach optimizes resource usage by applying comprehensive security checks only where necessary while enabling efficient local processing for subsequent packets.
2Reliability
If all incoming packets are forwarded to the service provider, then service rules are consistently applied, but unnecessary network resources are expended
Solution Approach 1:
The system extracts the service rule evaluation function from every packet processing operation and applies it selectively only to the first packet of each traffic flow. By separating the evaluation requirement from universal packet handling, the system maintains service rule compliance where necessary while eliminating redundant resource consumption for follow-on packets that can be handled using cached results.
Solution Approach 2:
Service rule evaluation is performed in advance on the first packet of each flow, and the results are cached for subsequent packets. This preliminary action ensures service rule compliance is established upfront, allowing follow-on packets to be processed locally without repeated resource-intensive service provider interactions.
3Reliability
If manual configuration is used for service settings at edge switches, then service provider control is maintained, but configuration updates require reconfiguring all edge switches manually
Solution Approach 1:
The system introduces a flow table as an intermediary layer between the service provider and edge switches. The service provider defines service rules and policies, which are then applied at the edge switch using cached results in the flow table. This intermediary mechanism maintains service provider control over service rules while enabling efficient local processing that eliminates the need for manual reconfiguration of all edge switches when service settings change.
Solution Approach 2:
Service rules and policies are pre-configured at the service provider level and cached in the flow table at edge switches. When service settings need to be updated, only the service provider configuration needs to be modified, and the changes are automatically reflected in subsequent packet processing without requiring manual reconfiguration of individual edge switches.
Data Source
AI summary
An example method embodiment for networking includes managing, by a network controller, network services for one or more network devices connected to the network controller. Managing network services includes receiving a packet in a traffic flow from a network device. The network device is one of the one or more network devices connected to the network controller. Managing network services further includes determining applicable services for the packet, transmitting the packet to a service provider in accordance with the applicable services for the packet, receiving, from the service provider, service results corresponding to the packet, and creating a forwarding entry providing instructions for handling the traffic flow in a service path table at the network device in accordance with the service results corresponding to the packet.