Cloud controller for self-optimized networks

Abstract

A management system implemented in a cloud computing environment for automatically managing a plurality of Wi-Fi access points in a network can receive information from each of the plurality of Wi-Fi access points. The system can analyze the received information from each Wi-Fi access point to determine at least one operation condition of at least one Wi-Fi access and determine at least one new operation setting for the at least one Wi-Fi access point based on the analyzed information. The system can remotely configure the at least one Wi-Fi access point based on the at least one new operation setting.

Claims

1. In a management system implemented in a cloud computing environment, a method for automatically managing a plurality of Wi-Fi access points in a network, comprising: receiving, by the management system including memory and a processor configured to execute instructions stored in the memory, information from each of the plurality of Wi-Fi access points in the network; analyzing, by the management system, the received information from each Wi-Fi access point to determine at least one operation condition of at least one Wi-Fi access point, wherein the at least one Wi-Fi access point includes a first service set identifier (SSID) and a second SSID, wherein the first SSID is associated with a first number of devices, and wherein the second SSID is associated with a second number of devices; determining, by the management system, at least one new operation setting for the at least one Wi-Fi access point based on the analyzed information, wherein the at least one new operation setting identifies a third number of devices that are associated with the first SSID and a fourth number of devices that are associated with the second SSID, wherein the third number is different from the first number, and wherein the fourth number is different from the second number; configuring, by the management system, the at least one Wi-Fi access point based on the at least one new operation setting, whereby the at least one Wi-Fi access point is remotely configured by the management system; detecting inoperative Wi-Fi access points in the network; generating Wi-Fi access points neighbor maps based on location of each of the inoperative Wi-Fi access points in the network; and adjusting behavior of a neighboring operational access point based on the inoperative Wi-Fi access points.

2. The method of claim 1, wherein the information from each Wi-Fi access point in the network comprises at least one of a number of connected devices to each Wi-Fi access point, data rate information for each Wi-Fi access point, neighboring Wi-Fi AP maps, historical usage information, overall load, interference metrics, or device attachment attempts.

3. The method of claim 1, wherein the at least one new operation setting further comprises at least one of an operating channel, an operating frequency band, a modulation and coding scheme, or a transmission power setting.

4. The method of claim 1, further comprising: receiving, by the management system, a first encryption key for a first session between a first Wi-Fi access point and a first Wi-Fi enabled device; storing, by the management system, the first encryption key in a database implemented in the cloud computing environment; retrieving, by the management system, the first encryption key from the database; and providing, by the management system, the first encryption key to at least one of the first Wi-Fi access point, the first Wi-Fi enabled device, and a second Wi-Fi access point.

5. The method of claim 1, further comprising: terminating the first session between the first Wi-Fi access point and the first Wi-Fi enabled device based on at least one criterion; and enabling a second session between the first Wi-Fi enabled device and a second Wi-Fi access point in range of the first Wi-Fi enabled device.

6. The method of claim 5, wherein the at least one criterion comprises data rate information corresponding to the first session.

7. The method of claim 6, wherein a data rate corresponding to the second session is higher than a data rate corresponding to the first session.

8. The method of claim 1, wherein the management system is configured to communicate with each Wi-Fi access point through a radio resource management (RRM) profile.

9. The method of claim 1, further comprising generating statistical information for the plurality of Wi-Fi access points in the network.

10. A system for automatically managing a plurality of Wi-Fi access points in a network, the system comprising a processor and a memory, the processor configured to run a module stored in the memory that is configured to cause the processor to: receive information from each of the plurality of Wi-Fi access points in the network; analyze the received information from each Wi-Fi access point to determine at least one operation condition of at least one Wi-Fi access point, wherein the at least one Wi-Fi access point includes a first service set identifier (SSID) and a second SSID, wherein the first SSID is associated with a first number of devices, and wherein the second SSID is associated with a second number of devices; determine at least one new operation setting for the at least one Wi-Fi access point based on the analyzed information, wherein the at least one new operation setting identifies a third number of devices that are associated with the first SSID and a fourth number of devices that are associated with the second SSID, wherein the third number is different from the first number, and wherein the fourth number is different from the second number; configure the at least one Wi-Fi access point based on the at least one new operation setting, whereby the at least one Wi-Fi access point is remotely configured by the system; detect inoperative Wi-Fi access points in the network; generate Wi-Fi access points neighbor maps based on location of each of the inoperative Wi-Fi access points in the network; and adjust behavior of a neighboring operational access point based on the inoperative Wi-Fi access points.

11. The system of claim 10, wherein the information from each Wi-Fi access point in the network comprises at least one of a number of connected devices to each Wi-Fi access point, data rate information for each Wi-Fi access point, neighboring Wi-Fi AP maps, historical usage information, overall load, interference metrics, or device attachment attempts.

12. The system of claim 10, wherein the at least one new operation setting comprises at least one of an operating channel, an operating frequency band, a modulation and coding scheme, or a transmission power setting.

13. The system of claim 10, wherein the processor is further configured to: receive a first encryption key for a first session between a first Wi-Fi access point and a first Wi-Fi enabled device; store the first encryption key in a database implemented in the cloud computing environment; retrieve the first encryption key from the database; and provide the first encryption key to at least one of the first Wi-Fi access point, the first Wi-Fi enabled device, and a second Wi-Fi access point.

14. The system of claim 10, wherein the processor is further configured to: terminate the first session between the first Wi-Fi access point and the first Wi-Fi enabled device based on at least one criterion; and enable a second session between the first Wi-Fi enabled device and a second Wi-Fi access point in range of the first Wi-Fi enabled device.

15. The system of claim 14, wherein the at least one criterion comprises data rate information corresponding to the first session.

16. The system of claim 15, wherein a data rate corresponding to the second session is higher than a data rate corresponding to the first session.

17. The system of claim 10, wherein the processor is further configured to communicate with each Wi-Fi access point through a radio resource management (RRM) profile.

18. The system of claim 10, wherein the processor is further configured to generate statistical information for the plurality of Wi-Fi access points in the network.

19. A non-transitory computer readable medium having executable instructions operable to cause an apparatus to: receive information from each of the plurality of Wi-Fi access points in the network; analyze the received information from each Wi-Fi access point to determine at least one operation condition of at least one Wi-Fi access point, wherein the at least one Wi-Fi access point includes a first service set identifier (SSID) and a second SSID, wherein the first SSID is associated with a first number of devices, and wherein the second SSID is associated with a second number of devices; determine at least one new operation setting for the at least one Wi-Fi access point based on the analyzed information, wherein the at least one new operation setting identifies a third number of devices that are associated with the first SSID and a fourth number of devices that are associated with the second SSID, wherein the third number is different from the first number, and wherein the fourth number is different from the second number; configure the at least one Wi-Fi access point based on the at least one new operation setting, whereby the at least one Wi-Fi access point is remotely configured by the system; detect inoperative Wi-Fi access points in the network; generate Wi-Fi access points neighbor maps based on location of each of the inoperative Wi-Fi access points in the network; and adjust behavior of a neighboring operational access point based on the inoperative Wi-Fi access points.

20. The non-transitory computer readable medium of claim 19, wherein the executable instructions are operable to further cause the apparatus to: receive a first encryption key for a first session between a first Wi-Fi access point and a first Wi-Fi enabled device; store the first encryption key in a database implemented in the cloud computing environment; retrieve the first encryption key from the database; and provide the first encryption key to at least one of the first Wi-Fi access point, the first Wi-Fi enabled device, and a second Wi-Fi access point.

Description

BRIEF DESCRIPTION OF DRAWINGS

(1) The accompanying drawings, which are incorporated in and constitute part of this specification, and together with the description, illustrate and serve to explain the principles of various example embodiments.

(2) FIG. 1 shows an exemplary implementation of a hotspot network.

(3) FIG. 2 shows an exemplary implementation of a hotspot network, in accordance with some embodiments.

(4) FIG. 3 shows exemplary optimization elements of a system for automatically managing Wi-Fi access points, in accordance with some embodiments.

(5) FIGS. 4 and 5 show exemplary implementations of a hotspot network with different components for automatically managing Wi-Fi access points, in accordance with some embodiments.

(6) FIG. 6 shows exemplary components of a system for automatically managing Wi-Fi access points, in accordance with some embodiments.

(7) FIG. 7 shows an exemplary method for automatically managing Wi-Fi access points when a user moves in and out of range of Wi-Fi access points, in accordance with some embodiments.

(8) FIG. 8 shows an exemplary high level message exchange for automatically managing Wi-Fi access points when a user moves in and out of range of Wi-Fi access points, in accordance with some embodiments.

(9) FIGS. 9a-9c show exemplary message exchange for automatically managing Wi-Fi access points when a user moves in and out of range of a Wi-Fi access point, in accordance with some embodiments.

(10) FIG. 10 shows an exemplary method for automatically managing Wi-Fi access points in a Wi-Fi network, in accordance with some embodiments.

DETAILED DESCRIPTION

(11) In the following description, numerous specific details are set forth regarding the systems and methods of the disclosed subject matter and the environment in which such systems and methods may operate, etc., in order to provide a thorough understanding of the disclosed subject matter. It will be apparent to one skilled in the art, however, that the disclosed subject matter may be practiced without such specific details, and that certain features, which are well known in the art, are not described in detail in order to avoid unnecessary complication of the disclosed subject matter. In addition, it will be understood that the embodiments provided below are exemplary, and that it is contemplated that there are other systems and methods that are within the scope of the disclosed subject matter.

(12) FIG. 1 shows an arrangement of two hotspot access points (AP) in a hotspot network. Specifically, FIG. 1 shows a hotspot network 100 in which a user can use a device 102, for example, a smartphone, to connect via Wi-Fi to a home hotspot Wi-Fi AP 104. The hotspot network also includes an outdoor public hotspot Wi-Fi AP 108, where one or more user devices 122 can connect to when they are within the range of the outdoor public hotspot Wi-Fi AP 108. The hotspot network 100 also includes hotspot core network 114, which can include a Wi-Fi Access Gateway (WAG) 116, an authentication, authorization, and accounting (AAA) services database/server 118, and cloud services 120, which can include for example, parental controls, content filtering, malware detection, and internet security. Home hotspot Wi-Fi AP 104 and outdoor public hotspot 108 can communicate with hotspot core network 114 via communication channels 110 and 112, respectively. Communication channels 110 and 112 can include any appropriate communication means, for example, Ethernet over Generic Routing Encapsulation (EoGRE). WAG 116 can also communicate with roaming partner network 122. A roaming network can include for example any network that a user can connect to when roaming in an area outside the coverage of his network. For example, when a Comcast “Xfinity®” Wi-Fi customer goes to Europe, he can connect to a Wi-Fi network operating in Europe, for example, the Boingo Wi-Fi network.

(13) In the arrangement illustrated in FIG. 1, a user can manually manage his home hotspot Wi-Fi AP 104 to efficiently utilize the network resources. For example, the user can manually associate some devices to the 2.4 GHz frequency network and other devices to the 5 GHz frequency network and can spread out the channels to minimize interference and increase the data rate. This can be possible because the number of Wi-Fi hotspot AP in a house is small, typically one or two, and because the number of devices connected to the network is also relatively small.

(14) However, the entire hotspot network, for example Comcast's “Xfinity®” hotspot network, can have millions of access points. Managing all APs in a hotspot network cannot happen manually. According to aspects of the invention, a management system that can be implemented in a cloud service running in a data center can connect to every hotspot Wi-Fi AP of a particular hotspot network and can automatically manage and configure the hotspot Wi-Fi APs to efficiently utilize the hotspot resources.

(15) This is illustrated in FIG. 2, which shows an exemplary implementation of a hotspot network, in accordance with embodiments of the present invention. Specifically, FIG. 2 shows a hotspot network 200 in which a user can use a device 206, for example, a smartphone, to connect via Wi-Fi to home hotspot Wi-Fi AP 202. Access point 202 can be configured to offer both an open Service Set Identifier (SSID) and a secure SSID. A user can connect a first device 206 to the Wi-Fi network through the open SSID and can connect a second device 208 to the Wi-Fi network through the secure SSID. The user can alternatively use the same device to connect to the Wi-Fi network through using either SSIDs. Similarly, the outdoor public hotspot Wi-Fi AP 204 has been configured to offer both a secure SSID and an open SSID. A user can connect device 210 to the Wi-Fi network through the secure SSID and another user can connect device 212 to the Wi-Fi network through the open SSID. Alternatively, the same user can use a device to connect to the Wi-Fi network using either SSIDs.

(16) The hotspot network of FIG. 2 also includes hotspot core network 218, which can include WAG 220, which communicates with AAA services database/server 222 through AAA proxy/Key cache database 224. Hotspot core network 218 can also include management system 230, which can communicate with AAA proxy/Key cache database 224. Management system 230 can also communicate with the hotspot APs through a profile 232, for example a TR-069/181 radio resource management (RRM) profile. AAA proxy/Key cache database 224 can also communicate with the hotspots APs through a networking protocol 234, for example, the remote authentication dial in user service (RADIUS) networking protocol. WAG 220 can also connect to cloud services 226 and roaming partner network 228. Home hotspot Wi-Fi AP 202 and outdoor public hotspot 204 can communicate with hotspot core network 218 via communication channels 214 and 216, respectively. Communication channels 214 and 216 can include any appropriate means, for example, Ethernet over Generic Routing Encapsulation (EoGRE).

(17) According to embodiments of the present invention, using the RRM profile, the management system 230 can remotely manage and tune the APs in the hotspot network. For example, using the RRM profile the management system 230 can detect dead APs, channel collisions, and load imbalances. Management system 230 can also make power adjustments to the hotspot network APs. Details of the RRM profile are provided in section 8, Appendix G of U.S. Provisional Application No. 61/941,135, the contents of which are incorporated herein in their entirety. Details of the RRM profile are also provided below.

(18) FIG. 3 generally at 300 shows exemplary features implemented by the disclosed management system 308. For example, management system 308 can implement radio optimization 302, secure mobility 304, and analytics collection 306. The management system 308 can implement these features to automatically manage and optimize Wi-Fi APs.

(19) Radio optimization 302 can include channel spacing, band steering, SSID steering, transmit power adjusting, and modulation and coding scheme (MCS) threshold setting. For example, if two Wi-Fi hotspots are operating at a first channel, e.g., channel 1, the disclosed management system can automatically change the operating channel of one of the Wi-Fi hotspots to a second channel, e.g., channel 11, to minimize interference. Similarly, if two Wi-Fi hotspots are connected to user devices on the same frequency band, e.g., 2.4 GHz, the disclosed management system can automatically move one of the Wi-Fi hotspots to a different frequency band, e.g., 5 GHz, to reduce the interference between the two sessions. Moreover, the disclosed management system can automatically move different devices to different SSIDs to increase the data rate of the entire hotspot network. According to aspects of the invention, another optimization relates to adjusting the transmission power of two neighboring Wi-Fi APs. If, for example, the management system detects that one Wi-Fi AP causes interference to a user device that communicates with a neighboring AP, then the management system can reduce the transmit power of the first Wi-Fi AP, to shrink the hotspot area of the first AP and consequently to minimize the interference.

(20) A characteristic of Wi-Fi user devices, e.g., smartphones, is that they try to connect and maintain a connection with a particular Wi-Fi access point as long as they can. For example, once a Wi-Fi user device connects to a particular AP, it remains attached to the same AP, even after the connection conditions have changed, e.g., after the user has moved far from the AP. This is the situation, even when there are better options available, e.g., a different AP is closer to the user device and can offer better connection. The disclosed management system can be aware of the state of all Wi-Fi APs in the network and can implement policies that can increase the total data rate of the hotspot network. For example, a policy can specify that if a Wi-Fi AP cannot maintain a particular data rate with a connected Wi-Fi user device, it can disconnect from the user device, if there are other APs in the area of the user device that it can connect to and can provide better data rate.

(21) As discussed above, the disclosed management system can steer the Wi-Fi environment to provide optimum data rates to user devices connected to a hotspot network. In addition, the management system can enhance mobility in environments where users can frequently move, e.g., office buildings. Secure mobility 304 can include mobility enhancements such as, “dead” AP detection, mobility optimizations, and automatic neighbor relations. The disclosed management system can be aware of the “dead” Wi-Fi access points, e.g., inoperative APs, and can, therefore, adjust the behavior of neighboring operating APs, e.g., increase the transmit power, to compensate for the “dead” APs.

(22) In addition, when a user device moves from one Wi-Fi AP to another Wi-Fi AP within a secure Wi-Fi network, re-attachment should happen as quickly as possible to avoid any latencies and interruption of service. According to aspects of the disclosure, the management system can cache authentication keys for a particular session between a Wi-Fi AP and a user device. When the user device attaches to a different Wi-Fi AP, then the management system can pass the cached authentication keys to the new session. Accordingly, the time to re-authenticate can reduce significantly for user devices that move among various APs. For example, the system can implement Opportunistic Key Caching (OKC) or 802.11 FT for authentication between multiple APs.

(23) According to aspects of the disclosure, the management system can be aware of the location of each Wi-Fi AP and can automatically create neighboring Wi-Fi AP maps.

(24) According to aspects of the disclosure, every hotspot can send updated information on particular configurable time intervals, for example, every minute, with current Wi-Fi environment and conditions. For example, the Wi-Fi APs can send information relating to the number of connected devices, the corresponding data rates, neighboring Wi-Fi AP maps, historical usage information, overall load, interference metrics, and device attachment attempts. Analytics collection 306 can include generating statistical data and analytics that can provide insight on how the hotspot network behaves, and then can make the adjustments to the hotspot Wi-Fi APs by processing the information that is received from all Wi-Fi APs.

(25) FIG. 4 shows an exemplary implementation of a Wi-Fi hotspot network, in accordance with some embodiments. Specifically, FIG. 4 shows illustrative components of a hotspot network 400, which can include one or more public Wi-Fi APs 402, one or more Wi-Fi APs 404 in residential buildings (multi-dwelling units or MDUs), a cloud environment 406 that can include a management system 408 according to embodiments of the invention, a database with AP neighboring lists 410, a AAA proxy server 412 that can connect to a AAA server 414, a database 416 that can store cached authentication keys, Programmable Data plane Control (PDC) layer 420, and Subscriber Service Control (SSC) entity 422.

(26) As discussed above, management system 408 can communicate with the hotspot APs through a profile, for example a TR-069/181 radio resource management (RRM) profile. For example, FIG. 4 shows management system 408 communicating with public Wi-Fi APs 402 and residential Wi-Fi APs 404 through profiles 424 and 426, respectively. Public Wi-Fi APs 402 and residential Wi-Fi APs 404 can also communicate with packet data protocol (PDP) entity 418 through communication channels 428 and 430, respectively, which can be, for example, EoGRE channels. PDP entity 418 can communicate with cloud 406 through PDC entity 420.

(27) FIG. 5 shows another exemplary implementation of a Wi-Fi hotspot network, in accordance with some embodiments. Specifically, FIG. 5 shows illustrative components of a hotspot network 500, which can include management system 502 in communication with Wi-Fi APs 510 via communication profiles 514. Management system 502 can also communicate with database 506 that can store neighbor lists of all Wi-Fi APs in the hotspot network and through a virtualized network function (VNF) entity 504 with a WAG/AAA proxy server 508. Database 506 can also communicate with VNF entity 504 and WAG/AAA proxy server 508. Management system 502 can maintain a repository of network and user session statistics collected from the Wi-Fi APs in the hotspot network, which can be leveraged for data analysis. For example, management system can communicate with a web server and provide analytics relevant to the operation of the hotspot network on a web browser 512.

(28) FIG. 6 generally at 600 illustrates exemplary architectural details of the disclosed management system. Specifically, FIG. 6 shows management system 602, WAG 604, neighbor groups 606, 608, and 610, AAA database/server 614, neighbor map/key cache database 624, and SSC entity 622. Management system 602 can comprise a TR-069 transport entity 620, a mobility orchestration entity 618, and a AAA proxy server 616. Database 624, which can be implemented in a cloud environment, can store the neighbor maps of all Wi-Fi APs in the hotspot network, as well as, authentication keys for each session between a user device and the connected Wi-Fi AP. Database 624 can communicate with TR-069 transport entity 620, mobility orchestration entity 618, and AAA proxy server 616.

(29) When user device 612 is within a particular neighbor group, for example, neighbor group 606, it can connect to a Wi-Fi AP within the group. The particular session will be authenticated, for example, through WAG 604 and AAA database 614. The authentication keys for the particular session can be saved into database 624 and can be re-used when user device has moved into a different neighbor group, for example, neighbor group 608 or 610.

(30) This is illustrated in FIG. 7. User device 702 can be at location 704, which is serviced by Wi-Fi AP 706. During that session, authentication keys are generated (step 1) and can be cached, for example, in WAG 710. For example, WAG 710 can comprise a Key Cache 712, which can communicate with AAA database/server 714 and can store the authentication keys for all session in the hotspot network. If user device 702 moves (step 2) to a different location, for example, location 718, it may no longer be serviced by Wi-Fi AP 706. Instead it can be near Wi-Fi AP 720 and will attempt to connect to it (step 3). When the session is established, Wi-Fi AP 720 will attempt to authenticate user device 702 (step 4). The authentication keys for this new session can be provided from Key Cache 712 (step 5), which would decrease the time to authenticate user device 702. Persons skilled in the art would understand that the design and location of Key Cache 712 can be implementation specific. For example, a key cache can be implemented inside the WAG or alternatively can be implemented outside.

(31) According to aspects of the disclosure, FIG. 8 illustrates an exemplary message exchange 800 when a user device moves between different hotspot locations. Specifically, FIG. 8 shows user device 802, source Access Point/Home Gateway (AP/HGW) 804, target AP/HGW 806, WAG/AAA proxy server 808, and AAA database/server 810. When user device 802 is in range of source AP/HGW 804, it can send an association request 812. Source AP/HGW 804 can respond back with an association response 814. The session can be authenticated (step 816), for example, through 802.1x EAP encapsulation and RADIUS re-encapsulation. Persons skilled in the art would understand that a Pairwise Master Key ID (PMKID) is an ephemeral “authentication” key that can be generated by an access point. PMKID can be shared by the Access Point to the WAG so that the WAG can cache it and reuse when the device moves to another AP in the future (step 818). When a PMKID is generated, it can be cached (step 820) in WAG/AAA Proxy server 808.

(32) User device 802 can move to a location in range of target AP/HGW 806 (step 822). User device 802 can send a re-association request 824 to target AP/HGW 806 (step 824). Target AP/HGW 806 can send a RADIUS Access Request 826 to WAG/AAA Proxy 808, which in turn can respond with the cached PMKID (828). When target AP/HGW 806 receives the cached PMKID, it can match it with the new session (step 830) and can send to user device 802 a re-association success message 832. Because the PMKID is retrieved from the cached location and not the AAA server 810, the overhead on the AAA server 810 can be reduced.

(33) According to alternative aspects, FIGS. 9a-9c show an exemplary message exchange 900 for automatically managing Wi-Fi access points when a user moves in and out of range of Wi-Fi access points.

(34) Specifically, FIGS. 9a-9c show user device 902, AP 904, WAG/AAA proxy server 906, and AAA database/server 908. As illustrated in FIG. 9a at 910, initially there are no keys cached in either the user device 902 or AP 904. Then user device 902 can send an Association Request (step 912) to AP 904, which can return an Association Response (step 914) to user device 902. When user device 902 receives the Association Response (step 914), it can send to AP 904 a 802.1X EAP Request (step 916). Then AP 904 sends a RADIUS Access Request (step 918) to WAG/AAA Proxy server 906, which in turn forwards the RADIUS Access Request to AAA server 908 (step 920). The EAP Authentication Protocol can authenticate user device 902 (step 922) and the AAA server 908 can send a RADIUS Access Accept message back to the WAG/AAA Proxy server 906 (step 924).

(35) When WAG/AAA Proxy server 906 receives the RADIUS Access Accept message, it caches the authentications keys for the particular session (step 926) and transfers the RADIUS Access Accept keys to AP 904 (step 928). AP 904 can then send an EAP success message to user device 902 (step 930). User device 902 and AP 904 can then perform a four-way handshake (step 932) where AP 904 can deliver the PMKID for the security association of PMK in the first message of the four-way exchange, as illustrated in FIG. 9b. Specifically, four messages including keys can be exchanged between user device 902 and AP 904 (step 934). After the four-way handshake, AP 904 can send the PMKID using RADIUS accounting and WAG 906 can associate the cached keys with the PMKID (936). Specifically, AP 904 can send a RADIUS Accounting Request to WAG/AAA Proxy server 906 (step 938), which in turn can send the RADIUS Accounting Request to AAA server 908 (step 940). AAA server 908 can send back a RADIUS Accounting Response (step 942) and WAG/AAA Proxy server 906 can forward the RADIUS Accounting Response to AP 904 (step 944).

(36) As illustrated in FIG. 9c, when user device 902 re-associates with AP 904, it can avoid the 802.1x authentication while the PMK is valid (946). Specifically, user device 902 can send to AP 904 a Re-association Request including the PMKID count and PMKID list (step 948). AP 904 can forward the request to WAG/AAA Proxy 906 (step 950), which can return a RADIUS Access Accept message with the cached keys (step 952). Once AP 904 receives the RADIUS Access Accept, it can send a Re-association Response to user device 902. According to aspects of the disclosure, AP 904 can avoid a new 802.1x authentication by sending the keys to user device 902 using a four-way handshake (step 956). Specifically, four messages including keys can be exchanged between user device 902 and AP 904 (step 958).

(37) FIG. 10 shows an exemplary method 1000 for automatically managing Wi-Fi access points in a Wi-Fi network. The disclosed method can receive information from each Wi-Fi access points in the network (step 1002). Then the method can analyze the received information from each Wi-Fi access point to determine at least one operation condition of at least one Wi-Fi access (step 1004) and determine at least one new operation setting for the at least one Wi-Fi access point based on the analyzed information (step 1006). Finally, the method can configure the at least one Wi-Fi access point based on the at least one new operation setting (step 1008).

(38) Details of the RRM profile are described below.

(39) TABLE-US-00001 MUST/ New Parameters SHOULD proposed Read or list requirement parameters Datatype Write Description WiFi MUST Radio supported R Total number of entries in the WiFi Number Of Radio table Entries SSID supported R Total number of entries in the Number Of WiFiSSID table Entries Access Point supported R Total number of entries in the WiFi Number Of AP table Entries WIFI Radio MUST WIFI Radio supported Id (key) WIFI Radio supported W Enables or disables a radio Enable WIFI Radio supported R The current operational state of the Status radio. Enumeration of: Up/Down/Unknown/Dormant/ NotPresent/LowerLayerDown/Error (OPTIONAL) When Enable is false then Status SHOULD normally be Down (or NotPresent or Error if there is a fault condition on the interface). When Enable is changed to true then Status SHOULD change to Up if and only if the interface is able to transmit and receive network traffic; it SHOULD change to Dormant if and only if the interface is operable but is waiting for external actions before it can transmit and receive network traffic (and subsequently change to Up if still operable when the expected actions have completed); it SHOULD change to LowerLayerDown if and only if the interface is prevented from entering the Up state because one or more of the interfaces beneath it is down; it SHOULD remain in the Error state if there is an error or other fault condition detected on the interface; it SHOULD remain in the NotPresent state if the interface has missing (typically hardware) components; it SHOULD change to Unknown if the state of the interface can not be determined for some reason. WIFI Radio supported R Max PHY bitrate supported by this Max Bit interface (in Mbps) Rate WIFI Radio supported R Frequency band at which the radio Supported can operate. Enumeration of 2.4 Ghz Frequency and 5 Ghz Bands WIFI Radio supported W The value MUST be a member of Operating the list reported by the Frequency SupportedFrequencyBands Band parameter. Indicates the frequency band at which the radio is operating. If the radio supports multiple bands, and OperatingFrequencyBand is changed, then all parameters whose value is not valid for the new frequency band (e.g. Channel) MUST be set to a valid value (according to some CPE vendor- specific behavior). WIFI Radio supported R List items indicate which IEEE Supported 802.11 standards this Radio Standards instance can support (should simultaneously, in the frequency include band specified by which OperatingFrequencyBand. Each list optional item is an enumeration of: a parts of the ([802.11a-1999]), b ([802.11b- standard are 1999]), ([802.11g-2003]) and n supported) ([802.11n-2009]). Each value indicates support for the indicated standard. If OperatingFrequencyBand is set to 2.4 GHz, only values b, g, n are allowed. If OperatingFrequencyBand is set to 5 GHz, only values a, n are allowed. WIFI Radio supported W Each list item MUST be a member Operating of the list reported by the Standards SupportedStandards parameter. List items indicate which IEEE 802.11 standard this Radio instance is configured for. Eg: If the OperatingFrequencyBand is 2.4 GHz, then b, g, n are allowed. WIFI Radio supported R List items represent possible radio Possible channels for the wireless standard Channels (a, b, g, n) and the regulatory domain. WIFI Radio supported R List items represent channels that Channels In the radio determines to be currently Use in use (including any that it is using itself). WIFI Radio supported W The current radio channel being Channel used by the connection. If AutomaticChannelSelection is used, the value of of this MUST be the channel chosen by the ACS procedure. Depends on the RegulatoryDomain and the OperatingFrequencyBand. WIFI Radio supported R Indicates if the ACS is supported by Auto the radio Channel Supported WIFI Radio supported W Enable or disable the ACS. Auto Enabling it ensures that a channel Channel MUST be selected automatically Enable and MAY be changed subsequently. Should be false if the Wifi Radio Channel has a channel value in it. WIFI Radio supported W Channel Bw of 20 Mhz, 40 Mhz or Operating auto Channel Bandwidth WIFI Radio supported W This is the secondary extension Extension channel position applicable when Channel the OperatingChannelBandwidth is set to 40 Mhz or auto. Enumeration of AboveControlChannel, BelowControlChannel or auto to be used. WIFI Radio supported W Guard interval between the OFDM Guard symbols with an enumeration of Interval 400 ns, 800 ns or auto WIFI Radio supported W Values from 0-15 MUST be MCS supported WIFI Radio SHOULD R List items represent supported Transmit transmit power levels as percentage Power of full power. For example, Supported “0, 25, 50, 75, 100”. A-1 item indicates auto mode (automatic decision by CPE). Auto mode allows the Radio to adjust transmit power accordingly. For example, this can be useful for power-save modes such as EU- CoC, where the Radio can adjust power according to activity in the CPE. WIFI Radio MUST W Indicates the current Transmit Transmit power being used. It MUST be one Power of the values from the RadioTransmitPowerSupported. WIFI Radio supported R Indicates of 802.11h is supported. IEEE80211h Can be true only when the radio Supported operates in 5 Ghz. (a or n) WIFI Radio supported W Indicates of 802.11h is enabled on IEEE80211h this radio. Can be true only when Enabled the radio operates in 5 Ghz. (a or n) WIFI Radio supported W 802.11d regulatory domain. Regulatory Domain WIFI Radio SHOULD New Unsigned Both RSSI signal level at which CS/CCA Carrier int detects a busy condition. Enable Sense APs to increase minimum Threshold in sensitivity to avoid detecting busy use condition from multiple/weak Wi-Fi sources in dense Wi-Fi environments. Wifi Carrier SHOULD New Unsigned R CS ranges supported by the radio Sense int Threshold range supported WIFI Radio SHOULD New Unsigned R Fraction of the time AP senses a Stats int busy channel or transmits frames. Channel Provides visibility into channel Utilization capacity. RTS/CTS SHOULD New String W fixing the RTS/CTS paramters exchange Frame SHOULD New Unsigned W Fixing the frame aggregation level Aggregation int depending on how dense the level network is. Example-if the network is not congested, then a large number of frames can be aggregated and sent. Throughput SHOULD New Unsigned R Expressed in mbps int Traffic SHOULD New String R Quality (HTTP, TCP) of an STA WIFI SSID MUST Throughput statistics for this Stats interface WIFI SSID supported R The total number of bytes Stats Bytes transmitted out of the interface, Sent including framing characters. WIFI SSID supported R The total number of bytes received Stats Bytes on the interface, including framing Received characters. WIFI SSID supported R The total number of packets Stats Packets transmitted out of the interface. Sent WIFI SSID supported R The total number of packets Stats Packets received on the interface. Received WIFI SSID supported R The total number of outbound Stats Errors packets that could not be Sent transmitted because of errors. WIFI SSID supported R The total number of inbound Stats Errors packets that contained errors Received preventing them from being delivered to a higher-layer protocol. WIFI SSID supported R The total number of packets Stats Unicast requested for transmission which Packets Sent were not addressed to a multicast or broadcast address at this layer, including those that were discarded or not sent. WIFI SSID supported R The total number of received Stats Unicast packets, delivered by this layer to a Packets higher layer, which were not Received addressed to a multicast or broadcast address at this layer. WIFI SSID supported R The total number of outbound Stats packets which were chosen to be Discard discarded even though no errors had Packets Sent been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. WIFI SSID supported R The total number of inbound Stats packets which were chosen to be Discard discarded even though no errors had Packets been detected to prevent their being Received delivered. One possible reason for discarding such a packet could be to free up buffer space. WIFI SSID supported R The total number of packets that Stats higher-level protocols requested for Multicast transmission and which were Packets Sent addressed to a multicast address at this layer, including those that were discarded or not sent. WIFI SSID supported R The total number of received Stats packets, delivered by this layer to a Multicast higher layer, which were addressed Packets to a multicast address at this layer. Received WIFI SSID supported R The total number of packets that Stats higher-level protocols requested for Broadcast transmission and which were Packets Sent addressed to a broadcast address at this layer, including those that were discarded or not sent. WIFI SSID supported R The total number of received Stats packets, delivered by this layer to a Broadcast higher layer, which were addressed Packets to a broadcast address at this layer. Received WIFI SSID supported R The total number of packets Stats received via the interface which Unknown were discarded because of an Proto unknown or unsupported protocol. Packets Received WIFI MUST A table of the devices currently Associated associated with the AP Device WIFI supported R Associated Device Id WIFI supported R MAC addr of the associated device Associated Device MAC Address WIFI supported R True if the associatedDevice has Associated authenticated, else false. Device Authentication State WIFI supported R The data transmit rate in kbps that Associated was most recently used for Device Last transmission from the access point Data to the associated device. Downlink Rate WIFI supported R The data transmit rate in kbps that Associated was most recently used for Device Last transmission from the associated Data Uplink device to the access point. Rate WIFI supported R An indicator of radio signal strength Associated of the uplink from the associated Device device to the access point, measured Signal in dBm, as an average of the last Strength 100 packets received from the device. WIFI supported R The number of packets that had to Associated be re-transmitted, from the last 100 Device packets sent to the associated Retransmissions device. Multiple re-transmissions of the same packet count as one. Max Packet SHOULD New Unsigned W Indicates the number of packets to Retry count int be retransmitted to have an upper limit. WIFI supported R Whether or not this node is Associated currently present in the Wi-Fi Device network Active WIFI MUST New Unsigned R Total number of users associated at Associated int any point in time Device count Max number SHOULD New Unsigned W specifies the maximum number of of associated int STAs associated at any point in STAs for time. admission control WIFI SSID MUST The SSIDPolicy object defines the Policy configuration of policies, behaviors and event thresholds controlled per SSID. WIFI SSID supported Both The ANPI parameter indicates the Policy ANPI threshold to report the Average Threshold Noise plus Interference. The value −100 indicates no threshold, and events of this type are not generated WIFI SSID supported Both The LowReceivedPowerThreshold Policy Low parameter indicates the power level Received threshold to generate an event Power whenever the station received Threshold power is below the threshold. The value −100 indicates no threshold, and events of this type are not generated WIFI SSID supported Both The Policy Low LowPowerDeniedAccessThreshold Power parameter indicates the power level Denied threshold to deny client Access association whenever the station Threshold received power is below the threshold. The value −100 indicates no threshold, and events of this type are not generated. WIFI SSID supported Both The Policy Low LowerPowerDissasociationThreshold Power parameter indicates the threshold Dissasociation to report Disassociation due to low Threshold power. The Wi-Fi GW should refuse associations when the power level is below this RSSI level. The value −100 indicates no threshold, and events of this type are not generated. WiFI SHOULD New string Both Specifies the beacon MCS to be Beacon used MCS level in use Wifi Beacon MUST New string R Specifies all the beacon MCSs MCS levels supported supported WIFI Client SHOULD The ClientStats object contains Stats accumulative statistics for each client station served by the Wi-Fi GW. A station is reported only after it is associated for the first time. WIFI Client possibly key Stats Interval WIFI Client possibly key ID of the single client MAC address Stats Id WIFI Client possibly R MAC address of the associated Stats Device client device MAC Address WIFI Client possibly R The FramesSent parameter indicates Stats Frames the total number of frames Sent transmitted out of the interface. For conventional 802.11 MAC ([802.11a], [802.11b], and [802.11g]) this counter corresponds to the total of MSDUs being transmitted. For High Throughput transmissions this corresponds to the A-MSDU. The value of this counter may be reset to zero when the CPE is rebooted. WIFI Client possibly R This indicates the total number of Stats Data MSDU frames marked as duplicates Frames Sent and non duplicates acknowledged. Ack The value of this counter may be reset to zero when the CPE is rebooted. WIFI Client possibly R This indicates the total number of Stats Data MSDU frames retransmitted out of Frames Sent the interface(i.e., marked as No Ack duplicate and non-duplicate) and not acknowledged, but does not exclude those defined in the DataFramesLost parameter. The value of this counter may be reset to zero when the CPE is rebooted. WIFI Client possibly R This indicates the total number of Stats Data MSDU frames retransmitted out of Frames Lost the interface that were not acknowledged and discarded for reaching max number of retransmissions. The value of this counter may be reset to zero when the CPE is rebooted WIFI Client possibly R This indicates the total number of Stats Frames frames received by the Wi-Fi Received interface. For conventional 802.11 MAC ([802.11a], [802.11b], and [802.11g]) this counter corresponds to the total of MSDUs being transmitted. For High Throughput transmissions (n), this corresponds to A-MSDUs and MSDUs. The value of this counter may be reset to zero when the CPE is rebooted. WIFI Client possibly R This indicates the total number of Stats Data frames received by the Wi-Fi Frames interface. For conventional 802.11 Received MAC ([802.11a], [802.11b], and [802.11g]) this counter corresponds to the total of MSDUs being transmitted. For High Throughput transmissions (n), this corresponds to A-MSDUs and MSDUs. The value of this counter may be reset to zero when the CPE is rebooted. WIFI Client possibly R This indicates the total number of Stats Data duplicated frames received on this Frames interface. The value of this counter Duplicate may be reset to zero when the CPE Received is rebooted WIFI Client possibly R This indicates the total number of Stats Probes probes received. Received WIFI Client possibly R This indicates the total number of Stats Probes probes rejected. Rejected WIFI Client possibly R This indicates the energy observed Stats RSSI at the antenna receiver for a current (total and transmission. per stream) WIFI Client possibly R This indicates the signal strength Stats SNR received from a client compared to distribution the noise received. (total and per stream) WIFI Client possibly R Total number of client dissociations Stats Disassociations WIFI Client possibly R Total number of client Stats authentication failures Authentication Failures WIFI Client possibly R Indicates the last time the client was Stats Last associated Time Association WIFI Client possibly R This indicates the last time the Stats Last client disassociated from the Time interface. The all zeros value Disassociation indicates the client is currently associated. AP Neighbor Neighbor information known Stats (new through channel scans. object: APs whose beacons can be heard) AP MUST New string R The current SSID of the neighbor Neighbor SSID AP MUST New string R The current channel and bandwidth Neighbor in which the neighboring AP is Current operating Channel and Bandwidth AP SHOULD New string R The signal strength at which packets Neighbor from the neighboring AP are RSSI received at the measuring AP, in terms of dbm

(40) The subject matter described herein can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them. The subject matter described herein can be implemented as one or more computer program products, such as one or more computer programs tangibly embodied in an information carrier (e.g., in a machine readable storage device), or embodied in a propagated signal, for execution by, or to control the operation of, data processing apparatus (e.g., a programmable processor, a computer, or multiple computers). A computer program (also known as a program, software, software application, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file. A program can be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

(41) The processes and logic flows described in this specification, including the method steps of the subject matter described herein, can be performed by one or more programmable processors executing one or more computer programs to perform functions of the subject matter described herein by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus of the subject matter described herein can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

(42) Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processor of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of nonvolatile memory, including by way of example semiconductor memory devices, (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks, (e.g., internal hard disks or removable disks); magneto optical disks; and optical disks (e.g., CD and DVD disks). The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

(43) To provide for interaction with a user, the subject matter described herein can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, (e.g., a mouse or a trackball), by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. For example, feedback provided to the user can be any form of sensory feedback, (e.g., visual feedback, auditory feedback, or tactile feedback), and input from the user can be received in any form, including acoustic, speech, or tactile input.

(44) The subject matter described herein can be implemented in a computing system that includes a back end component (e.g., a data server), a middleware component (e.g., an application server), or a front end component (e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described herein), or any combination of such back end, middleware, and front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.

(45) It is to be understood that the disclosed subject matter is not limited in its application to the details of construction and to the arrangements of the components set forth in the following description or illustrated in the drawings. The disclosed subject matter is capable of other embodiments and of being practiced and carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein are for the purpose of description and should not be regarded as limiting.

(46) As such, those skilled in the art will appreciate that the conception, upon which this disclosure is based, may readily be utilized as a basis for the designing of other structures, methods, and systems for carrying out the several purposes of the disclosed subject matter. It is important, therefore, that the claims be regarded as including such equivalent constructions insofar as they do not depart from the spirit and scope of the disclosed subject matter.

(47) Although the disclosed subject matter has been described and illustrated in the foregoing exemplary embodiments, it is understood that the present disclosure has been made only by way of example, and that numerous changes in the details of implementation of the disclosed subject matter may be made without departing from the spirit and scope of the disclosed subject matter, which is limited only by the claims which follow.