IP Library Granted Patent US 10,374,814
Granted Patent B2
US 10,374,814 · App. 15/219,461 · Granted Aug 6, 2019

Access point cloud controller auto-discovery

Inventors: Rajeev Kumar Mishra (Bangalore, IN); Senthilraj Shanmugavadivel (Coimbatore, IN); Dominic Velikakath Peter (Bangalore, IN); Jeelan Basha Poola (Bangalore, IN)
Assignee: EXTREME NETWORKS, INC.
H04L12/18H04W24/02H04L67/12H04W88/08
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,374,814
App. No.
15/219,461
Granted
Aug 6, 2019
Kind
B2
Abstract

Access point cloud controller auto-discovery is provided. An access point, in communication with other access points, receives data indicative of whether each of other access points are managed using a cloud controller or a local controller. When the data is indicative that at least one of the other access points is managed using the cloud controller, the access point is configured to be cloud-controller-managed. When the data is indicative that none of the other access points is managed using the cloud controller, and when the data is further indicative that at least one of the other access points is managed using the local controller, the access point is configured to be local-controller-managed.

Claims (61)

1. An access point comprising:

a communication interface configured to communicate with one or more other access points;

a processor configured to:

receive, using the communication interface, data indicative of whether each of the one or more other access points is managed using a cloud controller or a local controller;

based on the data indicating that at least one of the one or more other access points is managed using the cloud controller, cause the access point to be cloud-controller-managed;

based on the data indicating that the one or more other access points is not managed using the cloud controller and that at least one of the one or more other access points is managed using the local controller, cause the access point to be local-controller-managed; and

based on the access point being a first access point in a network or the data indicating that the one or more other access points is not managed using the cloud controller or the local controller, initiate a discovery process to determine whether to cause the access point to be cloud-controller-managed or local-controller-managed.

2. The access point of claim 1 , wherein the processor is further configured to:

based on the data is indicative indicating that at least one of the one or more other access points is managed using the cloud controller and that at least one of the one or more other access points is managed using the local controller, cause the access point to be cloud-controller-managed.

3. The access point of claim 1 , wherein the processor is further configured to:

cause the access point to be cloud-controller-managed by:

using the communication interface to communicate with the cloud controller; and

receiving management parameters from the cloud controller.

4. The access point of claim 1 , further comprising:

a memory storing a network address of the cloud controller, wherein the processor is further configured to cause the access point to be cloud-controller-managed by using the communication interface to communicate with the cloud controller using the network address.

5. The access point of claim 1 , wherein the data comprises a network address of the cloud controller and wherein the processor is further configured to cause the access point to be cloud-controller-managed by using the communication interface to communicate with the cloud controller using the network address received in the data.

6. The access point of claim 1 , wherein the processor is further configured to:

cause the access point to be local-controller-managed by:

using the communication interface to communicate with a respective local controller in communication with the communication interface; and

receiving management parameters from the respective local controller.

7. The access point of claim 1 , wherein to receive the data from the one or more other access points, the processor is further configured to:

transmit a request for the data to the one or more other access points; and

receive the data from the one or more other access points in response to the request.

8. The access point of claim 1 , wherein the discovery process comprises:

based on a connection between the communication interface and a respective local controller, causing the access point to be local-controller-managed;

based on the connection not being between the communication interface and the respective local controller:

determining, using the communication interface, whether an identifier of the access point has been cloud controller associated; and

based on the determining, causing the access point to be cloud-controller-managed.

9. The access point of claim 8 , wherein the processor is further configured to:

based on the connection not being between the communication interface and the respective local controller and the determining, repeat the discovery process.

10. The access point of claim 1 , wherein the processor is further configured to:

communicate with the cloud controller based on the access point booting up; and

receive initial data from the cloud controller, wherein the initial data indicates whether the access point is to be cloud-controller-managed or local-controller-managed, the initial data superseding the data indicative of whether each of the one or more other access points are managed using the cloud controller or the local controller.

11. A method performed by an access point, the method comprising:

receiving, at a processor of the access point, through a communication interface configured to communicate with one or more other access points, data indicative of whether each of the one or more other access points are managed using a cloud controller or a local controller;

based on the data indicating that at least one of the one or more other access points is managed using the cloud controller, causing, using the processor, the access point to be cloud-controller-managed;

based on the data indicating that none of the one or more other access points is managed using the cloud controller and that at least one of the one or more other access points is managed using the local controller, causing, using the processor, the access point to be local-controller-managed; and

based on the access point being a first access point in a network or the data indicating that the one or more other access points is not managed using the cloud controller or the local controller, initiate a discovery process to determine whether to cause the access point to be cloud-controller-managed or local-controller-managed.

12. The method of claim 11 , further comprising:

based on the data indicating that at least one of the one or more other access points is managed using the cloud controller and that at least one of the one or more other access points is managed using the local controller, causing the access point to be cloud-controller-managed.

13. The method of claim 11 , further comprising:

causing the access point to be cloud-controller-managed by:

using the communication interface to communicate with the cloud controller; and

receiving management parameters from the cloud controller.

14. The method of claim 11 , wherein the access point further comprises a memory storing a network address of the cloud controller, and the method further comprises:

causing the access point to be cloud-controller-managed by using the communication interface to communicate with the cloud controller using the network address.

15. The method of claim 11 , wherein the data comprises a network address of the cloud controller, and the method further comprises:

causing the access point to be cloud-controller-managed by using the communication interface to communicate with the cloud controller using the network address received in the data.

16. The method of claim 11 , further comprising:

causing the access point to be local-controller-managed by using the communication interface to communicate with a respective local controller in communication with the communication interface: and

receiving management parameters from the respective local controller.

17. The method of claim 11 , wherein receiving the data from the one or more other access points further comprises

transmitting a request for the data to the one or more other access points; and

receiving the data from one or more other access points in response to the request.

18. The method of claim 11 , further comprising:

communicating with the cloud controller based on the access point booting up; and

receiving initial data from the cloud controller, wherein the initial data indicates whether the access point is to be cloud-controller-managed or local-controller-managed, the initial data superseding the data indicative of whether each of the one or more other access points are managed using the cloud controller or the local controller.

19. The access point of claim 1 , wherein to receive the data from the one or more other access points the processor is further configured to:

passively receive a message from the one or more other access points, wherein the message includes the data and comprises at least one of a broadcast or multicast message.

20. The method of claim 11 , wherein receiving the data from the one or more other access points further comprises:

passively receiving a message from the one or more other access points, wherein the message includes the data and comprises at least one of a broadcast or multicast message.

Assignments (10)
RELEASE OF PATENT AND TRADEMARK SECURITY INTEREST AT REEL/FRAME NO. 46050/0546 Recorded Jul 30, 2026
From: BANK OF MONTREAL, AS AGENT
To: EXTREME NETWORKS, INC.
Reel/Frame 076081/0088 →
SECURITY INTEREST Recorded Jul 29, 2026
From: EXTREME NETWORKS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 076078/0590 →
AMENDED SECURITY AGREEMENT Recorded Aug 18, 2023
From: EXTREME NETWORKS, INC.; AEROHIVE NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 064782/0971 →
SECURITY INTEREST Recorded May 1, 2018
From: EXTREME NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 046050/0546 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2018
From: SILICON VALLEY BANK
To: EXTREME NETWORKS, INC.
Reel/Frame 046051/0775 →
THIRD AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 044639/0300 →
SECOND AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Jul 14, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 043200/0614 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 8, 2016
From: SYMBOL TECHNOLOGIES, LLC
To: EXTREME NETWORKS, INC.
Reel/Frame 040579/0410 →
AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2016
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 040521/0762 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 26, 2016
From: MISHRA, RAJEEV KUMAR; SHANMUGAVADIVEL, SENTHILRAJ; PETER, DOMINIC VELIKAKATH; POOLA, JEELAN BASHA
To: SYMBOL TECHNOLOGIES, LLC
Reel/Frame 039257/0124 →
Continuity (1)
Related Publication 20180035274A1 · Feb 1, 2018