IP Library Granted Patent US 10,517,018
Granted Patent B2
US 10,517,018 · App. 15/811,681 · Granted Dec 24, 2019

Load balancing for a cloud-based Wi-Fi controller based on local conditions

Inventors: Maria Valavan Savarimuthu (Sunnyvale, CA); Dinesh Raman (Milpitas, CA); Sanjay Gandotra (Santa Clara, CA)
Assignee: Fortinet, Inc.
H04W28/08H04L43/08H04L67/10H04L67/1029H04L67/1031H04W76/00H04W24/04H04W72/1231H04W72/1247H04W84/12
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,517,018
App. No.
15/811,681
Granted
Dec 24, 2019
Kind
B2
Abstract

Load balancing for cloud-based monitoring of Wi-Fi devices on local access networks is based on local conditions. Requests for connection are received from Wi-Fi devices of the plurality of WLANs exceed a threshold. An indication of at least one condition for each of the WLANs is also received either with the connection request or separately. Example conditions include, without limitation, a number of local connections, network security breaches, guaranteed service levels, local latency or congestion, power outages or reboots, and the like. In response, at least one Wi-Fi device is prioritized and scheduled based on a corresponding at least one condition.

Claims (37)

1. A computer-implemented method for load balancing in a cloud-based Wi-Fi controller device that remotely monitors access points for a plurality of WLANs (wireless local access networks) on a data communication network, the method comprising the steps of:

receiving, at a network interface of the cloud-based controller device coupled in communication to the data communication network, requests for connection from the access points of the plurality of WLANs, wherein the number of connection requests within a time period exceeds a threshold and wherein the connection requests concern monitoring data being reported upstream;

receiving an indication of at least one condition for each of the WLANs;

prioritizing at least one access point based on a corresponding at least one condition;

scheduling future connections for the access points based on the prioritizing;

receiving monitoring data from the access point in accordance with the scheduling; and

performing at least one action with respect to operation of the access point don a corresponding WLAN based on the monitoring data.

2. The method of claim 1 , wherein the number of connection requests within a time period exceeds a total capacity of connection requests.

3. The method of claim 1 , wherein the local conditions comprise at least one from the group of: a number of local connections, type of Wi-Fi device, a vulnerability detection, an intrusion detection, a rogue device detection, a power outage, a reboot, local latency, local congestion, and a change in a local condition surpassing a threshold.

4. The method of claim 1 , wherein the prioritizing is based on a service tier of an entity associated with the access point.

5. The method of claim 1 , further comprising:

receiving a local time of the Wi-Fi device;

receiving a flight time between the access point and the cloud-based Wi-Fi controller;

calculating a dispatch time for a connection request using the local time and the flight time; and

sending the dispatch time to the Wi-Fi device.

6. The method of claim 1 , wherein the received monitoring data is used as the indication of at least one condition for scheduling latter connections.

7. The method of claim 1 , further comprising:

activating a load balancing mode responsive to the number of requests within the time period exceeding the threshold.

8. The method of claim 1 , further comprising:

spawning more than one cloud-based Wi-Fi controller instance, wherein load balancing considers available connects across the more than one cloud-based Wi-Fi controller instance.

9. The method of claim 1 , wherein the access point operates according to at least one of IEEE 802.11n, IEEE 802.11 ac wave 2, and a Wi-Fi protocol that supports beamforming.

10. A non-transitory computer-readable medium storing source code that, when executed by a processor, performs a method load for balancing in a cloud-based Wi-Fi controller device that remotely monitors Wi-Fi devices for a plurality of WLANs (wireless local access networks), the method comprising the steps of:

receiving, at a network interface of the cloud-based controller device coupled in communication to the data communication network, requests for connection from the access points of the plurality of WLANs, wherein the number of connection requests within a time period exceeds a threshold and wherein the connection requests concern monitoring data being reported upstream;

receiving an indication of at least one condition for each of the WLANs;

prioritizing at least one access point based on a corresponding at least one condition;

scheduling future connections for the access points based on the prioritizing;

receiving monitoring data from the access point in accordance with the scheduling; and

performing at least one action with respect to operation of the access point on a corresponding WLAN based on the monitoring data.

11. A cloud-based Wi-Fi controller device that load balances while remotely Wi-Fi devices for a plurality of WLANs (wireless local access networks), the cloud-based Wi-Fi controller comprising:

a processor; and

a memory, storing:

a first module to receive, at a network interface of the cloud-based controller device coupled in communication to the data communication network, requests for connection from the access points of the plurality of WLANs, wherein the number of connection requests within a time period exceeds a threshold and wherein the connection requests concern monitoring data being reported upstream;

a second module to receive an indication of at least one condition for each of the WLANs;

a third module to receive at least one access point based on a corresponding at least one condition;

a fourth module to schedule future connections for the access points based on the prioritizing;

a fifth module to monitor data from the access point in accordance with the scheduling; and

a sixth module to perform at least one action with respect to operation of the access point on a corresponding WLAN based on the monitoring data.

Assignments (2)
MERGER Recorded Feb 28, 2018
From: MERU NETWORKS, INC.
To: FORTINET, INC
Reel/Frame 045474/0392 →
MERGER Recorded Jan 23, 2018
From: MERU NETWORKS, INC.
To: FORTINET, LLC
Reel/Frame 045112/0786 →
Continuity (5)
Continuation 14985293 · Dec 30, 2015
Continuation In Part 14813076 · Jul 29, 2015
Provisional Application 62099126 · Dec 31, 2014
Provisional Application 62098287 · Dec 30, 2014
Related Publication 20180176824A1 · Jun 21, 2018