Controller IP Selection for Multi-Port AP Traffic Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Ethernet switches are unable to effectively distribute encapsulated data packets with the same outer IP header across multiple physical ports, limiting the downstream throughput of access points in centralized WLAN architectures.

Innovation Solution

A method and apparatus that select a controller IP address based on client device identifiers to encapsulate packets, allowing Ethernet switches to distribute traffic across multiple physical ports by varying the outer header, thereby utilizing multiple ports within an Ether-channel.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If Ethernet switches receive encapsulated data packets with the same outer IP header, then the packets are transmitted through a single physical port, but the downstream throughput of the access point is limited

Engineering Contradiction:
Improvedownstream throughput of access pointVSAvoidtraffic distribution capability
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent changes the outer IP header parameters (source IP address or destination IP address) of encapsulated packets to create variability. By modifying these IP address parameters, the Ethernet switch can perform load balancing across multiple physical ports in the Ether-channel, thereby increasing the downstream throughput of the access point from single-port limitations to multi-port aggregated bandwidth.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If the controller uses a single controller IP address for all packets, then the encapsulation process is simple, but the Ethernet switch cannot distribute traffic across multiple physical ports

Engineering Contradiction:
Improvetraffic distribution across physical portsVSAvoidcontroller IP address selection and encapsulation process
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The controller performs preliminary actions by pre-selecting different controller IP addresses from its pool of IP addresses before encapsulating packets. This preliminary selection based on packet characteristics enables the Ethernet switch to distribute traffic across multiple physical ports without requiring complex real-time decision-making during packet transmission.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the controller's IP address pool into multiple distinct controller IP addresses. Each packet can be assigned to a different controller IP address segment, allowing the Ethernet switch to differentiate and distribute packets across multiple physical ports in the Ether-channel, thereby increasing throughput.

Inventive Principle:
Principle #1Segmentation

3Productivity

If Ethernet switches use traditional load balancing methods with identical outer IP headers, then the switching process is straightforward, but the downstream throughput remains limited to single port capacity

Engineering Contradiction:
Improvedownstream throughputVSAvoidload balancing effectiveness
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent modifies the outer IP header parameters of encapsulated packets to enable effective load balancing. By changing source or destination IP addresses in the outer header, the Ethernet switch can recognize packet diversity and distribute traffic across multiple physical ports, thereby increasing downstream throughput while maintaining straightforward switching operations.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9300586B2Apparatus, system and method for load balancing traffic to an access point across multiple physical ports
Publication Date: 2016.03.29 HEWLETT PACKARD ENTERPRISE DEV LP
  • US9300586B2 patent drawing
  • US9300586B2 patent drawing
  • US9300586B2 patent drawing

AI summary

A method for load balancing traffic from controller to destination access point (AP) via switch across multiple physical ports starts with controller receiving a packet from a source client device that is destined for destination client device associated with destination AP. The controller may select, based on an identifier associated with source or destination client device, a first or a second controller IP address. Controller may encapsulate the packet to generate an encapsulated packet including an outer header that includes the selected controller IP address. Controller may transmit the encapsulated packet to the switch that may distribute traffic to destination AP across multiple physical ports based on the selected controller IP address. Controller may also select a destination port based on destination client device of a packet and may encapsulate the packet using CAPWAP to generate an encapsulated packet including the destination port in a header of the encapsulated packet.