Modulation, which is a Physical Layer function, is a process in which the radio transceiver prepares the digital signal within the NIC for transmission over the airwaves. Modulation is the process of adding data to a carrier by altering the amplitude, frequency, or phase of the carrier in a controlled manner. Knowing the many different kinds of modulations used with wireless LANs is helpful when trying to build a compatible network piece-by-piece.
Figure 8.9 shows the details of modulation and spreading code types used with Frequency Hopping and Direct Sequence wireless LANs in the 2.4 GHz ISM band. Differential Binary Phase Shift Keying (DBPSK), Differential Quadrature Phase Shift Keying (DQPSK), and Gaussian Frequency Shift Keying (GFSK) are the types of modulation used by 802.11 and 802.11b products on the market today. Barker Code and Complimentary Code Keying (CCK) are the types of spreading codes used in 802.11 and 802.11b wireless LANs.
As higher transmission speeds are specified (such as when a system is using DRS), modulation techniques change in order to provide more data throughput. For example, 802.11g and 802.11a compliant wireless LAN equipment specify use of orthogonal frequency division multiplexing (OFDM), allowing speeds of up to 54 Mbps, which is a significant improvement over the 11 Mbps specified by 802.11b. Figure 8.10 shows the modulation types used for 802.11a networks. The 802.11g standard provides backwards compatibility by supporting CCK coding and even supports packet binary convolution coding (PBCC) as an option. Bluetooth and HomeRF are both FHSS technologies that use GFSK modulation technology in the 2.4 GHz ISM band.
Orthogonal frequency division multiplexing (OFDM) is a communications technique that divides a communications channel into a number of equally spaced frequency bands. A subcarrier carrying a portion of the user information is transmitted in each band. Each subcarrier is orthogonal (independent of each other) with every other subcarrier, differentiating OFDM from the commonly used frequency division multiplexing (FDM).
The Certified Wireless Network Professional Training & Certification Program is intended for individuals who administer, install, design, and support IEEE 802.11 compliant wireless networks.
Thursday, October 29, 2009
Saturday, October 17, 2009
How Wireless LANs Communicate
Request to Send/Clear to Send (RTS/CTS)
There are two carrier sense mechanisms used on wireless networks. The first is physical carrier sense. Physical carrier sense functions by checking the signal strength, called the Received Signal Strength Indicator (RSSI), on the RF carrier signal to see if there is a station currently transmitting. The second is virtual carrier sense. Virtual carrier sense works by using a field called the Network Allocation Vector (NAV), which acts as a timer on the station. If a station wishes to broadcast its intention to use the network, the station sends a frame to the destination station, which will set the NAV field on all stations hearing the frame to the time necessary for the station to complete its transmission, plus the returning ACK frame. In this way, any station can reserve use of the network for specified periods of time. Virtual carrier sense is implemented with the RTS/CTS protocol.
The RTS/CTS protocol is an extension of the CSMA/CA protocol. As the wireless LAN administrator, you can take advantage of using this protocol to solve problems like Hidden Node (discussed in Chapter 9, Troubleshooting). Using RTS/CTS allows stations to broadcast their intent to send data across the network.
As you can imagine by the brief description above, RTS/CTS will cause significant network overhead. For this reason RTS/CTS is turned OFF by default on a wireless LAN. If you are experiencing an unusual amount of collisions on your wireless LAN (evidenced by high latency and low throughput) using RTS/CTS can actually increase the traffic flow on the network by decreasing the number of collisions. Use of RTS/CTS should not be done haphazardly. RTS/CTS should be configured after careful study of the network's collisions, throughput, latency, etc.
Figure 8.7 illustrates the 4-way handshake process used for RTS/CTS. In short, the transmitting station broadcasts the RTS, followed by the CTS reply from the receiving station, both of which go through the access point. Next, the transmitting station sends its data payload through the access point to the receiving station, which immediately replies with an acknowledgement frame, or ACK. This process is used for every frame that is sent across the wireless network.
Configuring RTS/CTS
There are three settings on most access points and nodes for RTS/CTS:
When RTS/CTS is turned on, every packet that goes through the wireless network is announced and cleared between the transmitting and receiving nodes prior to transmission, creating a significant amount of overhead and significantly less throughput. Generally, RTS/CTS should only be used in diagnosing network problems and when only very large packets are flowing across a congested wireless network, which is rare.
However, the “on with threshold” setting allows the administrator to control which packets (over a certain size - called the threshold) are announced and cleared to send by the stations. Since collisions affect larger packets more than smaller ones, you can set the RTS/CTS threshold to work only when a node wishes to send packets over a certain size. This setting allows you to customize the RTS/CTS setting to your network data traffic and optimize the throughput of your wireless LAN while preventing problems like Hidden Node.
Figure 8.8 depicts a DCF network using the RTS/CTS protocol to transmit data. Notice that the RTS and CTS transmissions are spaced by SIFS. The NAV is set with RTS on all nodes, and then reset on all nodes by the immediately following CTS.
There are two carrier sense mechanisms used on wireless networks. The first is physical carrier sense. Physical carrier sense functions by checking the signal strength, called the Received Signal Strength Indicator (RSSI), on the RF carrier signal to see if there is a station currently transmitting. The second is virtual carrier sense. Virtual carrier sense works by using a field called the Network Allocation Vector (NAV), which acts as a timer on the station. If a station wishes to broadcast its intention to use the network, the station sends a frame to the destination station, which will set the NAV field on all stations hearing the frame to the time necessary for the station to complete its transmission, plus the returning ACK frame. In this way, any station can reserve use of the network for specified periods of time. Virtual carrier sense is implemented with the RTS/CTS protocol.
The RTS/CTS protocol is an extension of the CSMA/CA protocol. As the wireless LAN administrator, you can take advantage of using this protocol to solve problems like Hidden Node (discussed in Chapter 9, Troubleshooting). Using RTS/CTS allows stations to broadcast their intent to send data across the network.
As you can imagine by the brief description above, RTS/CTS will cause significant network overhead. For this reason RTS/CTS is turned OFF by default on a wireless LAN. If you are experiencing an unusual amount of collisions on your wireless LAN (evidenced by high latency and low throughput) using RTS/CTS can actually increase the traffic flow on the network by decreasing the number of collisions. Use of RTS/CTS should not be done haphazardly. RTS/CTS should be configured after careful study of the network's collisions, throughput, latency, etc.
Figure 8.7 illustrates the 4-way handshake process used for RTS/CTS. In short, the transmitting station broadcasts the RTS, followed by the CTS reply from the receiving station, both of which go through the access point. Next, the transmitting station sends its data payload through the access point to the receiving station, which immediately replies with an acknowledgement frame, or ACK. This process is used for every frame that is sent across the wireless network.
Configuring RTS/CTS
There are three settings on most access points and nodes for RTS/CTS:
- Off
- On
- On with Threshold
When RTS/CTS is turned on, every packet that goes through the wireless network is announced and cleared between the transmitting and receiving nodes prior to transmission, creating a significant amount of overhead and significantly less throughput. Generally, RTS/CTS should only be used in diagnosing network problems and when only very large packets are flowing across a congested wireless network, which is rare.
However, the “on with threshold” setting allows the administrator to control which packets (over a certain size - called the threshold) are announced and cleared to send by the stations. Since collisions affect larger packets more than smaller ones, you can set the RTS/CTS threshold to work only when a node wishes to send packets over a certain size. This setting allows you to customize the RTS/CTS setting to your network data traffic and optimize the throughput of your wireless LAN while preventing problems like Hidden Node.
Figure 8.8 depicts a DCF network using the RTS/CTS protocol to transmit data. Notice that the RTS and CTS transmissions are spaced by SIFS. The NAV is set with RTS on all nodes, and then reset on all nodes by the immediately following CTS.
Tuesday, October 6, 2009
Interframe Spacing
Interframe spacing doesn’t sound like something an administrator would need to know; however, if you don’t understand the types of interframe spacing, you cannot effectively grasp RTS/CTS, which helps you solve problems, or DCF and PCF, which are manually configured in the access point. Both of these functions are integral in the ongoing communications process of a wireless LAN. First, we will define each type of interframe space (IFS), and then we will explain how each type works on the wireless LAN.
As we learned when we discussed beacons, all stations on a wireless LAN are timesynchronized. All the stations on a wireless LAN are effectively ‘ticking’ time in sync with one another. Interframe spacing is the term we use to refer to standardized time spaces that are used on all 802.11 wireless LANs.
Three Types of Spacing
There are three main spacing intervals (interframe spaces): SIFS, DIFS, and PIFS. Each type of interframe space is used by a wireless LAN either to send certain types of messages across the network or to manage the intervals during which the stations contend for the transmission medium. Figure 8.3 illustrates the actual times that each interframe space takes for each type of 802.11 technology.
Interframe spaces are measured in microseconds and are used to defer a station's access to the medium and to provide various levels of priority. On a wireless network, everything is synchronized and all stations and access points use standard amounts of time (spaces) to perform various tasks. Each node knows these spaces and uses them appropriately. A set of standard spaces is specified for DSSS, FHSS, and Infrared as you can see from Figure 8.3. By using these spaces, each node knows when and if it is supposed to perform a certain action on the network.
Short Interframe Space (SIFS)
SIFS is the shortest fixed interframe space. SIFS are time spaces before and after which the following types of messages are sent. The list below is not an exhaustive list.
Point Coordination Function Interframe Space (PIFS)
A PIFS interframe space is neither the shortest nor longest fixed interframe space, so it gets more priority than DIFS and less than SIFS. Access points use a PIFS interframe space only when the network is in point coordination function mode, which is manually configured by the administrator. PIFS are shorter in duration than DIFS (see Figure 8.3), so the access point will always win control of the medium before other contending stations in distributed coordination function (DCF) mode. PCF only works with DCF, not as a stand-alone operational mode so that, once the access point is finished polling, other stations can continue to contend for the transmission medium using DCF mode.
Distributed Coordination Function Interframe Space (DIFS)
DIFS is the longest fixed interframe space and is used by default on all 802.11-compliant stations that are using the distributed coordination function. Each station on the network using DCF mode is required to wait until DIFS has expired before any station can contend for the network. All stations operating according to DCF use DIFS for transmitting data frames and management frames. This spacing makes the transmission of these frames lower priority than PCF-based transmissions. Instead of all stations assuming the medium is clear and arbitrarily beginning transmissions simultaneously after DIFS (which would cause collisions), each station uses a random back off algorithm to determine how long to wait before sending its data.
The period of time directly following DIFS is referred to as the contention period (CP). All stations in DCF mode use the random back off algorithm during the contention period. During the random back off process, a station chooses a random number and multiplies it by the slot time to get the length of time to wait. The stations count down these slot times one by one, performing a clear channel assessment (CCA) after each slot time to see if the medium is busy. Whichever station's random back off time expires first, that station does a CCA, and provided the medium is clear, it then begins transmission.
Once the first station has begun transmissions all other stations sense that the medium is busy, and remember the remaining amount of their random back off time from the previous CP. This remaining amount of time is used in lieu of picking another random number during the next CP. This process assures fair access to the medium among all stations.
Once the random back off period is over, the transmitting station sends its data and receives back the ACK from the receiving station. This entire process then repeats. It stands to reason that most stations will chose different random numbers, eliminating most collisions. However, it is important to remember that collisions do happen on wireless LANs, but they cannot directly be detected. Collisions are assumed by the fact that the ACK is not received back from the destination station.
The Communications Process
When you consider the PIFS process described above, it may seem as though the access point would always have control over the medium, since the access point does not have to wait for DIFS, but the stations do. This would be true, except for the existence of what is called a superframe. A superframe is a period of time, and it consists of three parts:
1. Beacon
2. Contention Free Period (CFP)
3. Contention Period (CP)
A diagram of the superframe is shown in Figure 8.4. The purpose of the superframe is to allow peaceful, fair co-existence between PCF and DCF mode clients on the network, allowing QoS for some, but not for others.
Again, remember that PIFS, and hence the superframe, only occurs when
1. The network is in point coordination function mode
2. The access point has been configured to do polling
3. The wireless clients have been configured to announce to the access point that they are pollable
Therefore, if we start from a hypothetical beginning point on a network that has the access point configured for PCF mode, and the some of the clients are configured for polling, the process is as follows.
1. The access point broadcasts a beacon.
2. During the contention free period, the access point polls stations to see if any station needs to send data.
3. If a station needs to send data, it sends one frame to the access point in response to the access point’s poll
4. If a station does not need to send data, it returns a null frame to the access point in response to the access point’s poll
5. Polling continues throughout the contention free period
6. Once the contention free period ends and the contention period begins, the access point can no longer poll stations. During the contention period, stations using DCF mode contend for the medium and the access point uses DCF mode.
7. The superframe ends with the end of the CP, and a new one begins with the following CFP.
Think of the CFP as using a "controlled access policy" and the CP as using a "random access policy." During the CFP, the access point is in complete control of all functions on the wireless network, whereas during the CP, stations arbitrate and randomly gain control over the medium. The access point, in PCF mode, does not have to wait for the DIFS to expire, but rather uses the PIFS, which is shorter than the DIFS, in order to capture the medium before any client using DCF mode does. Since the access point captures the medium and begins polling transmissions during the CFP, the DCF clients sense the medium as being busy and wait to transmit. After the CFP the CP begins, during which all stations using DCF mode may contend for the medium and the access point switches to DCF mode.
Figure 8.5 illustrates a short timeline for a wireless LAN using DCF and PCF modes.
The process is somewhat simpler when a wireless LAN is only in DCF mode, because there is no polling and, hence, no superframe. This process is as follows:
1. Stations wait for DIFS to expire
2. During the CP, which immediately follows DIFS, stations calculate their random back off time based on a random number multiplied by a slot time
3. Stations tick down their random time with each passing slot time, checking the medium (CCA) at the end of each slot time. The station with the shortest time gains control of the medium first.
4. A station sends its data.
5. The receiving station receives the data and waits a SIFS before returning an ACK back to the station that transmitted the data.
6. The transmitting station receives the ACK and the process starts over from the beginning with a new DIFS.
As we learned when we discussed beacons, all stations on a wireless LAN are timesynchronized. All the stations on a wireless LAN are effectively ‘ticking’ time in sync with one another. Interframe spacing is the term we use to refer to standardized time spaces that are used on all 802.11 wireless LANs.
Three Types of Spacing
There are three main spacing intervals (interframe spaces): SIFS, DIFS, and PIFS. Each type of interframe space is used by a wireless LAN either to send certain types of messages across the network or to manage the intervals during which the stations contend for the transmission medium. Figure 8.3 illustrates the actual times that each interframe space takes for each type of 802.11 technology.
Interframe spaces are measured in microseconds and are used to defer a station's access to the medium and to provide various levels of priority. On a wireless network, everything is synchronized and all stations and access points use standard amounts of time (spaces) to perform various tasks. Each node knows these spaces and uses them appropriately. A set of standard spaces is specified for DSSS, FHSS, and Infrared as you can see from Figure 8.3. By using these spaces, each node knows when and if it is supposed to perform a certain action on the network.
Short Interframe Space (SIFS)
SIFS is the shortest fixed interframe space. SIFS are time spaces before and after which the following types of messages are sent. The list below is not an exhaustive list.
- RTS - Request-to-Send frame, used for reserving the medium by stations
- CTS - Clear-to-Send frame, used as a response by access points to the RTS frame generated by a station in order to ensure all stations have stopped transmitting
- ACK - Acknowledgement frame used for notifying sending stations that data arrived in readable format at the receiving station
Point Coordination Function Interframe Space (PIFS)
A PIFS interframe space is neither the shortest nor longest fixed interframe space, so it gets more priority than DIFS and less than SIFS. Access points use a PIFS interframe space only when the network is in point coordination function mode, which is manually configured by the administrator. PIFS are shorter in duration than DIFS (see Figure 8.3), so the access point will always win control of the medium before other contending stations in distributed coordination function (DCF) mode. PCF only works with DCF, not as a stand-alone operational mode so that, once the access point is finished polling, other stations can continue to contend for the transmission medium using DCF mode.
Distributed Coordination Function Interframe Space (DIFS)
DIFS is the longest fixed interframe space and is used by default on all 802.11-compliant stations that are using the distributed coordination function. Each station on the network using DCF mode is required to wait until DIFS has expired before any station can contend for the network. All stations operating according to DCF use DIFS for transmitting data frames and management frames. This spacing makes the transmission of these frames lower priority than PCF-based transmissions. Instead of all stations assuming the medium is clear and arbitrarily beginning transmissions simultaneously after DIFS (which would cause collisions), each station uses a random back off algorithm to determine how long to wait before sending its data.
The period of time directly following DIFS is referred to as the contention period (CP). All stations in DCF mode use the random back off algorithm during the contention period. During the random back off process, a station chooses a random number and multiplies it by the slot time to get the length of time to wait. The stations count down these slot times one by one, performing a clear channel assessment (CCA) after each slot time to see if the medium is busy. Whichever station's random back off time expires first, that station does a CCA, and provided the medium is clear, it then begins transmission.
Once the first station has begun transmissions all other stations sense that the medium is busy, and remember the remaining amount of their random back off time from the previous CP. This remaining amount of time is used in lieu of picking another random number during the next CP. This process assures fair access to the medium among all stations.
Once the random back off period is over, the transmitting station sends its data and receives back the ACK from the receiving station. This entire process then repeats. It stands to reason that most stations will chose different random numbers, eliminating most collisions. However, it is important to remember that collisions do happen on wireless LANs, but they cannot directly be detected. Collisions are assumed by the fact that the ACK is not received back from the destination station.
The Communications Process
When you consider the PIFS process described above, it may seem as though the access point would always have control over the medium, since the access point does not have to wait for DIFS, but the stations do. This would be true, except for the existence of what is called a superframe. A superframe is a period of time, and it consists of three parts:
1. Beacon
2. Contention Free Period (CFP)
3. Contention Period (CP)
A diagram of the superframe is shown in Figure 8.4. The purpose of the superframe is to allow peaceful, fair co-existence between PCF and DCF mode clients on the network, allowing QoS for some, but not for others.
Again, remember that PIFS, and hence the superframe, only occurs when
1. The network is in point coordination function mode
2. The access point has been configured to do polling
3. The wireless clients have been configured to announce to the access point that they are pollable
Therefore, if we start from a hypothetical beginning point on a network that has the access point configured for PCF mode, and the some of the clients are configured for polling, the process is as follows.
1. The access point broadcasts a beacon.
2. During the contention free period, the access point polls stations to see if any station needs to send data.
3. If a station needs to send data, it sends one frame to the access point in response to the access point’s poll
4. If a station does not need to send data, it returns a null frame to the access point in response to the access point’s poll
5. Polling continues throughout the contention free period
6. Once the contention free period ends and the contention period begins, the access point can no longer poll stations. During the contention period, stations using DCF mode contend for the medium and the access point uses DCF mode.
7. The superframe ends with the end of the CP, and a new one begins with the following CFP.
Think of the CFP as using a "controlled access policy" and the CP as using a "random access policy." During the CFP, the access point is in complete control of all functions on the wireless network, whereas during the CP, stations arbitrate and randomly gain control over the medium. The access point, in PCF mode, does not have to wait for the DIFS to expire, but rather uses the PIFS, which is shorter than the DIFS, in order to capture the medium before any client using DCF mode does. Since the access point captures the medium and begins polling transmissions during the CFP, the DCF clients sense the medium as being busy and wait to transmit. After the CFP the CP begins, during which all stations using DCF mode may contend for the medium and the access point switches to DCF mode.
Figure 8.5 illustrates a short timeline for a wireless LAN using DCF and PCF modes.
The process is somewhat simpler when a wireless LAN is only in DCF mode, because there is no polling and, hence, no superframe. This process is as follows:
1. Stations wait for DIFS to expire
2. During the CP, which immediately follows DIFS, stations calculate their random back off time based on a random number multiplied by a slot time
3. Stations tick down their random time with each passing slot time, checking the medium (CCA) at the end of each slot time. The station with the shortest time gains control of the medium first.
4. A station sends its data.
5. The receiving station receives the data and waits a SIFS before returning an ACK back to the station that transmitted the data.
6. The transmitting station receives the ACK and the process starts over from the beginning with a new DIFS.
Subscribe to:
Posts (Atom)