SDN Flow Distribution via Virtual Controller
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software defined network (SDN) flow distribution systems require per-connection state, which can lead to scalability issues and create single points of failure, making them inefficient in handling varying client traffic loads.
Innovation Solution
Implementing an SDN flow distribution method within network elements by using a controller that maps traffic flows onto target servers without requiring per-connection state, utilizing virtual machines and data storage with rules and server lists to modify packet destinations dynamically, allowing for resilient and scalable traffic management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a dedicated load balancer device is used to implement flow distribution, then flow distribution capability is provided, but system complexity increases and single points of failure are created
Solution Approach 1:
The patent extracts the load balancing functionality from a dedicated physical device and integrates it into virtual machine instances that run on standard server hardware. The load balancing logic is taken out of specialized hardware and implemented as software components (virtual machines) that can be deployed on commodity servers, reducing hardware complexity while maintaining flow distribution capabilities
Solution Approach 2:
The patent makes standard server hardware universal by enabling it to perform load balancing functions through virtual machine instances. Instead of requiring specialized load balancer devices, any standard server can be configured to provide load balancing services through software, making the infrastructure more versatile and reducing overall system complexity
2Reliability
If per-connection state is maintained in the network, then connection tracking is improved, but scalability is reduced and single points of failure are created
Solution Approach 1:
The patent segments the state maintenance function by separating connection tracking from the load balancing decision-making process. Connection state is maintained at the endpoint servers rather than in centralized network devices, while load balancing decisions are made based on segmented criteria that do not require full connection state, enabling both reliability and scalability
Solution Approach 2:
The patent introduces hash-based flow classification as an intermediary mechanism that connects packet forwarding with load balancing without requiring per-connection state in network devices. The hash function acts as a mediator that deterministically maps traffic flows to target servers based on packet characteristics, enabling scalability while maintaining connection consistency through the mathematical properties of hashing
3Adaptability or versatility
If configuration changes are made in traditional load balancers, then load balancing policies are updated, but existing flows are broken
Solution Approach 1:
The patent applies local quality by implementing configuration changes in a distributed manner across multiple virtual machine instances rather than in a centralized load balancer. Each virtual machine instance can be independently configured and updated, allowing configuration flexibility at the local level while maintaining overall system stability and flow continuity through the distributed architecture
Data Source
AI summary
Various embodiments provide a method and apparatus for providing SDN flow distribution without requiring per-connection state in the network. In particular, the SDN flow distribution is realized in network elements within the forwarding path of packets by providing in those network elements with a controller capable of mapping traffic flows onto a set of target servers.