What is Beacons?

Beacon frame is one of the management frames in IEEE 802.11 based WLANs. It contains all the information about the network. Beacon frames are transmitted periodically, they serve to announce the presence of a wireless LAN and to synchronise the members of the service set. Beacon frames are transmitted by the access point (AP) in an infrastructure basic service set (BSS). In IBSS network beacon generation is distributed among the stations. For the 2.4 GHz spectrum, when having more than 15 SSIDs on non-overlapping channels (or more than 45 in total), beacon frames start to consume significant amount of air time and degrade performance even when most of the networks are idle. Beacon frames consist of an 802.11 MAC header, body and FCS.[1] Some of the fields in the body are listed below.

• Timestamp After receiving the beacon frame all the stations change their local clocks to this time. This helps with synchronization.
• Beacon interval This is the time interval between beacon transmissions. The time at which a node (AP, station when in ad hoc or P2P GO mode) must send a beacon is known as Target Beacon Transmission Time (TBTT). Beacon interval expressed in Time Unit (TU). It is a configurable parameter in the AP and typically configured as 100 TU.[2]
• Capability information Capability information field spans to 16 bits and contains information about capability of the device/network. Type of network such as ad hoc or Infrastructure network is signaled in this field. Apart from this information, it announces the support for polling, as well as the encryption details.
• SSID
• Supported rates
• Frequency-hopping (FH) Parameter Set
• Direct-Sequence (DS) Parameter Set
• Contention-Free (CF) Parameter Set
• IBSS Parameter Set
• Traffic indication map (TIM) Infrastructure network access points send beacons at a defined interval, which is often set to a default 100 TU which is equivalent to 102.4 ms. In the case of an ad hoc network where there are no access points, a peer station is responsible for sending the beacon. After an ad hoc station receives a beacon frame from a peer, it waits a random amount of time. After that random timeout has elapsed, it will send a beacon frame unless another station has already sent one. In this way, the responsibility of sending beacon frames is rotated amongst all the peers in the ad hoc network, while ensuring that beacons will always be sent. Most access points allow the changing of the beacon interval. Increasing the beacon interval will cause the beacons to be sent less frequently. This reduces load on the network and increases throughput for clients on the network; however, it has the undesirable effect of delaying association and roaming processes as stations scanning for access points could potentially miss a beacon while scanning other channels. Alternatively, decreasing the beacon interval causes beacons to be sent more frequently. This increases load on the network and decreases throughput for users, but it does result in a quicker association and roaming process. An additional downside of decreasing the beacon interval is that stations in power save mode will consume more power as they must more frequently awake to receive beacons. Inspecting an idle network with packet-monitoring tools such as tcpdump or Wireshark would show that most traffic on the network consists of beacon frames, with a few non-802-11 packets mixed in, such as DHCP packets. If users joined the network, responses to each beacon would begin to appear, along with regular traffic generated by the users. Stations must schedule beacon transmission at the nominal beacon interval. However, the transmission may suffer some delays due to the channel access. Like other frames, beacons must follow the CSMA/CA algorithm. This means that if the channel is busy (e.g., another station is currently sending a frame) when the beacon needs to be sent, it must wait. This means that the actual beacon interval may differ from the nominal beacon interval.[3] However, stations are able to compensate for this difference by inspecting the timestamp in the beacon frame when it is finally sent.