Wireless Client Balancing via Virtual RF Neighborhoods
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern wireless digital networks face imbalanced client load distribution among access nodes, leading to suboptimal network performance due to client devices selecting access nodes based on signal strength alone.
Innovation Solution
Access nodes and a controller collaborate to identify Virtual RF Neighborhoods, assess load balances, and redistribute clients by initially rejecting association requests to overloaded nodes, directing them to neighboring nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If client devices select access nodes based on signal strength alone, then connection simplicity is maintained, but client load becomes unbalanced among access nodes
Solution Approach 1:
The system performs preliminary load assessment and Virtual RF Neighborhood identification before client association. The controller pre-calculates load metrics for all access nodes and their Virtual RF Neighborhoods, and prepares rejection responses for overloaded nodes before clients attempt to connect, enabling load redistribution without increasing client device complexity
Solution Approach 2:
The controller acts as an intermediary between client devices and access nodes. It receives association requests, assesses load conditions, and selectively rejects requests from overloaded access nodes while redirecting clients to neighboring nodes with available capacity. This intermediary mechanism balances load without requiring changes to client device selection logic
2Productivity
If clients are redistributed to balance load across access nodes, then network performance is improved, but system complexity increases due to Virtual RF Neighborhood identification and load assessment mechanisms
Solution Approach 1:
The controller merges the load assessment, Virtual RF Neighborhood identification, and client redirection functions into a single centralized entity. Access nodes simply execute association requests and transmit rejection responses as instructed by the controller, avoiding the need for each node to independently perform complex load balancing calculations and neighborhood mappings
Solution Approach 2:
The system implements feedback loops where access nodes report their current load conditions to the controller, which then adjusts association request handling accordingly. The controller continuously monitors load metrics and dynamically modifies which access nodes accept or reject clients, creating a self-regulating load balancing system that adapts to changing network conditions
3Productivity
If overloaded access nodes reject association requests, then client load is redistributed to neighboring nodes, but connection establishment time increases for affected clients
Solution Approach 1:
The system applies preliminary anti-action by pre-identifying overloaded access nodes and preparing rejection responses before clients attempt to associate. The controller proactively determines which nodes should reject requests based on current load conditions, preventing clients from wasting time attempting to connect to overloaded nodes and enabling faster redirection to available nodes
Data Source
AI summary
Client balancing in a wireless digital network comprising a plurality of access nodes connected to a controller. Access nodes collect client density information and periodically report that client density information to the controller. The controller uses the client density information from the access nodes to compute Virtual RF Neighborhoods, identifying Virtual RF neighboring access nodes. Two access nodes are Virtual RF neighbors if a client which can connect to one access node can also connect to the other access node. The controller then identifies which nodes are overloaded by comparing the client loading of a target access node to the client loading of its Virtual RF neighbors. If an access node is identified as overloaded and selected for client balancing on a particular channel, it will initially refuse new association requests from client devices on that channel.