Cisco Hyperlocation
The Cisco Hyperlocation radio module provides the following:
-
WSM Radio Module functions that are extended to:
-
802.11ac
-
Wi-Fi Transmit
-
WSM and RRM channel scanning that is extended to 20-MHz, 40-MHz, and 80-MHz channel bandwidth.
-
-
Expanded location functionality:
-
Low latency location optimized channel scanning
-
32-antenna angle of arrival (AoA)
Note
The download BlockAckReq (BAR)/ Block Ack (BA) uses 1/3 of airtime in the worst case scenario when there is only one AP to do the AoA location.
In a typical AoA location usage, there are 4 to 5 participating APs. These APs send BAR/BA in a round robin fashion and only 5 to 6 percent airtime is used. For each 250 ms of dwell time, the primary AP schedules a 4ms-burst of BAR/BA every 9 ms. Therefore, sufficient airtime is available to support voice and video unless there is a case of extreme overload.
-
-
Bluetooth Low Energy (BLE) capability
The Cisco Hyperlocation Radio Module is supported on Cisco Aironet 3600 and 3700 Series Access Points.
For more information about Cisco Hyperlocation, see the following documents:
Guidelines and Restrictions for Cisco Hyperlocation
-
Hyperlocation configurations are not supported on Cisco APs in Sniffer mode.
-
Cisco Hyperlocation in enabled state has an impact on performance where both radios of APs that do not have Cisco Hyperlocation module go off-channel for about 100 milliseconds every 3 seconds.
-
When Hyperlocation is enabled, a burst of BARs are sent for location purposes. This takes about 6 percent to 10 percent of airtime.
-
If submode wIPS is in enabled state, it is not possible to enable Hyperlocation or FastLocate.
This section contains the following subsections:
Cisco Hyperlocation in a High Availability Environment
The global and per AP-group Cisco Hyperlocation configuration is mirrored from primary to secondary controller. The secondary controller updates only the internal state and does not forward any configuration information to the APs.
For MSE message encryption, the controller generates an encryption key and sends it to the APs and to the MSE, which uses it for encryption and decryption as end clients. The secondary controller does not generate an encryption key and the AP and MSE use the actual key shared by the primary controller.
Cisco Hyperlocation Client Debug Tracing
The Cisco Hyperlocation Debug Client Tracing feature provides the ability to specify a client MAC address for detailed hyperlocation tracing. Enable this feature using the test dot11 halo-client-trace client-mac command. To disable this feature, use the test dot11 halo-client-trace 0000.0000.0000 command.
Configuring Cisco Hyperlocation
Configuring Cisco Hyperlocation for all APs (GUI)
Procedure
Step 1 |
Choose . |
Step 2 |
In the Hyperlocation Config Parameters section: |
Step 3 |
In the BLE Beacon Config Parameters section:
|
Step 4 |
Save the configuration. |
Configuring Cisco Hyperlocation for an AP (GUI)
Procedure
Step 1 |
Choose . |
Step 2 |
On the All APs page that is displayed, click the name of the access point for which you want to configure Cisco Hyperlocation. |
Step 3 |
Click the Advanced tab. This opens the window. |
Step 4 |
In the Hyperlocation Configuration section, from the Enable Hyperlocation drop-down list, choose AP Specific and then check the check box next to the drop-down list to enable Cisco Hyperlocation for the AP. |
Step 5 |
In the BLE Beacon Config Parameters section:
|
Step 6 |
Save the configuration. |
Configuring Cisco Hyperlocation for an AP Group (GUI)
Procedure
Step 1 |
Choose . |
Step 2 |
Click the AP group name. |
Step 3 |
Click the Location tab. |
Step 4 |
In the HyperLocation Config Parameters section, check the Enable Hyperlocation check box to enable Hyperlocation for the AP group. |
Step 5 |
Enter the Packet Detection RSSI Minimum (dBm) value. This is the minimum level at which a data packet can be heard by the WSM modules for use in location calculations. The default value is –100 dDm. We recommend that this value be increased if you want to have only strong signals used in calculating locations. |
Step 6 |
Enter the Scan Count Threshold for Idle Client Detection value. The Scan Count Threshold represents the number of off-channel scan cycles the APs will wait before sending a Block Acknowledgment Request (BAR) to idle clients. The default value of 10 corresponds to approximately 40s, depending on the number of channels in the off channel scan cycle. |
Step 7 |
Enter the IPv4 address of the NTP server. This is the IPv4 address of the NTP server that all APs that are involved in this calculation need to synchronize to. We recommend that you use the same NTP server as is used by the general controller infrastructure. The scans from multiple APs need to be synchronized for the location to be accurately calculated. |
Step 8 |
Save the configuration. |