Create and define a profile's bluetooth configuration. The access points utilize a built-in Bluetooth chip for specific Bluetooth functional behaviors in a WiNG managed network. Both Bluetooth classic and Bluetooth low energy (BLE) technology are supported.
WiNG model access points support Bluetooth beaconing to emit either iBeacon or Eddystone-URL beacons. The access point‘s Bluetooth radio periodically sends non-connectable, undirected low-energy (LE) advertisement packets. These advertisement packets are short and sent on Bluetooth advertising channels that conform to already-established iBeacon and Eddystone-URL standards. However, portions of the advertising packet are customizable via the Bluetooth radio interface configuration context.
To define a Bluetooth radio interface configuration:
Description | Define a 64 character maximum description for the access point‘s Bluetooth radio to differentiate this radio interface from other Bluetooth supported radio‘s that might be members of the same RF Domain |
Admin Status | Select Enabled or Disabled to activate or deactivate support for Bluetooth beacon transmission on the selected access point |
Radio Mode | Use the drop-down list box to configure the access
point's Bluetooth radio functional mode. The options
include:
|
Transmit Period | Use the spinner control to set the Bluetooth radio‘s beacon transmission period from 100 to 10,000 milliseconds. As the defined period increases, so does the CPU processing time and the number packets incrementally transmitted (typically one per minute) |
Transmit Pattern | Use the drop-down list box to set the beacon‘s
transmission pattern. The options include:
|
Transmit Power | Use the spinner control to set the Bluetooth radio's le-beacon transmit power. This determines how far a beacon can transmit data. Set a value between -15 to 31 dBM. |
Antenna | Select between internal or external antenna options |
Calibration Signal Strength | Set the Eddystone Beacon measured calibration signal strength, from -127 dBm to 127 dBm, at 0 meters. Mobile devices can approximate their distance to beacons based on received signal strength. However, distance readings can fluctuate since they depend on several external factors. The closer you are to a beacon, the more accurate the reported distance. This setting is the projected calibration signal strength at 0 meters. The default setting is -19 dBm |
Transmit URL1 | Type a 64-character maximum Eddystone-URL1. The URL must be 17 characters or less once auto-encoding is applied. URL encoding is used when placing text in a query string to avoid confusion with the URL itself. It is typically used when a browser sends data to a web server |
Transmit URL2 | Type a 64-character maximum Eddystone-URL2. The URL must be 17 characters or less once auto-encoding is applied. URL encoding is used when placing text in a query string to avoid confusion with the URL itself. It is typically used when a browser sends data to a web server |
Calibration Signal Strength | Set the iBeacon measured calibration signal strength, from -127 dBm to 127 dBm, at 1 meter. Mobile devices can approximate their distance to beacons based on received signal strength. However, distance readings can fluctuate since they depend on several external factors. The closer you are to a beacon, the more accurate the reported distance. This setting is the projected calibration signal strength at 1 meter. The default setting is -60 dBm |
Major Number | Set the iBeacon major value from 0 to 65,535. Major values identify and distinguish groups. For example, each beacon on a specific floor in a building could be assigned a unique major value. The default value is 1,111 |
Minor Number | Set the iBeacon minor value from 0 to 65, 535. Minor values identify and distinguish individual beacons. Minor values help identify individual beacons within a group of beacons assigned a major value. The default setting is 2,222 |
UUID | Define a 32 hex character maximum Universally Unique
IDentifier (UUID). The UUID classification contains 32
hexadecimal digits, split into 5 groups, separated by dashes
– for example, f2468da6-5fa8-2e84-1134-
bc5b71e0893e . The UUID distinguishes iBeacons
in the network from all other beacons in networks outside of
your direct administration |