802.11-tutorial

802.11-tutorial - A Technical Tutorial on the IEEE 802.11...

Info iconThis preview shows pages 1–24. Sign up to view the full content.

View Full Document Right Arrow Icon
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 2
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 4
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 6
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 8
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 10
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 12
Background image of page 13

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 14
Background image of page 15

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 16
Background image of page 17

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 18
Background image of page 19

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 20
Background image of page 21

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 22
Background image of page 23

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 24
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: A Technical Tutorial on the IEEE 802.11 Protocol By Pablo Brenner Director of Engineering mm cmmmmm: © copyright BreezeCOM 1997 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mar-m; flmmaflmrmms Introduction The purpose of this document is to give technical readers a basic overview of the new 802.1 1 Standard, in such a way that they will be able to understand the basic concepts, the principle of operations, and some of the reasons behind some of the features and/0r components of the Standard. Obviously the document does not cover all the Standard, and does not provide enough information for the reader to implement an 802.1 1 compliant device (for this purpose the reader should read the Standard itself which is a several hundred pages document). This version of the document addresses mainly Functional and MAC aspects, a detailed description of the PHY layer will be provided in a following document. This version of the document is actualized to Draft 4.0 of the Standard. BreezeCom © copyright BreezeCOM 1997 Page 2 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 wreakifi flammwmrarmms IEEE 802.11 Architecture Architecture Components An 802.1 I LAN is based on a cellular architecture where the system is subdivided into cells, where each cell (called Basic Service Set or BSS, in the 802.11 nomenclature) is controlled by a Base Station (called Access Point, or in short AP). Even though that a wireless LAN may be formed by a single cell, with a single Access Point, (and as will be described later, it can also work without an Access Point), most installations will be formed by several cells, where the Access Points are connected through some kind of backbone (called Distribution System or DS), typically Ethernet, and in some cases wireless itself. The whole interconnected Wireless LAN including the different cells, their respective Access Points and the Distribution System, is seen to the upper layers of the OSI model, as a single 802 network, and is called in the Standard as Extended Service Set (ESS). The following picture shows a typical 802.11 LAN, with the components described previously: Distribution System The standard also defines the concept of a Portal, a Portal is a device that interconnects between an 802.11 and another 802 LAN. This concept is an abstract description of part of the functionality of a “translation bridge”. BreezeCom © copyright BreezeCOM 1997 Page 3 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mm cmmmmm: Even though the standard does not necessarily request so, typical installations will have the AP and the Portal on a single physical entity, and this is the case with BreezeCom’s AP which provides both functions. BreezeCom © copyright BreezeCOM 1997 Page 4 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 Witfliififi'fi fiammwmharmmfi IEEE 802.11 Layers Description As any 802x protocol, the 802.11 protocol covers the MAC and Physical Layer, the Standard currently defines a single MAC which interacts with three PHYS (all of them running at 1 and 2 Mbit/s) : 0 Frequency Hopping Spread Spectrum in the 2.4 GHz Band 0 Direct Sequence Spread Spectrum in the 2.4 GHZ Band, and 0 lnfraRed 802.2 Data Link 802.11 MAC Beyond the standard functionality usually performed by MAC Layers, the 802.11 MAC performs other functions that are typically related to upper layer protocols, such as Fragmentation, Packet Retransmitions, and Acknowledges. The MAC Layer The MAC Layer defines two different access methods, the Distributed Coordination Function and the Point Coordination Function: The Basic Access Method: CSMA/CA The basic access mechanism, called Distributed Coordination Function, is basically a Carrier Sense Multiple Access with Collision Avoidance mechanism (usually known as CSMA/CA). CSMA protocols are well known in the industry, where the most popular is the Ethernet, which is a CSMA/CD protocol (CD standing for Collision Detection). A CSMA protocol works as follows: A station desiring to transmit senses the medium, if the medium is busy (i.e. some other station is transmitting) then the station will defer its transmission to a later time, if the medium is sensed free then the station is allowed to transmit. These kind of protocols are very effective when the medium is not heavily loaded, since it allows stations to transmit with minimum delay, but there is always a chance of stations transmitting at the same time (collision), caused by the fact that the stations sensed the medium free and decided to transmit at once. BreezeCom © copyright BreezeCOM 1997 Page 5 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 Wfflffifi Samarymrafibfifi These collision situations must be identified, so the MAC layer can retransmit the packet by itself and not by upper layers, which would cause significant delay. In the Ethernet case this collision is recognized by the transmitting stations which go to a retransmission phase based on an exponential random backoff algorithm. While these Collision Detection mechanisms are a good idea on a wired LAN, they cannot be used on a Wireless LAN environment, because of two main reasons: 1. Implementing a Collision Detection Mechanism would require the implementation of a Full Duplex radio, capable of transmitting and receiving at once, an approach that would increase the price significantly. 2. On a Wireless environment we cannot assume that all stations hear each other (which is the basic assumption of the Collision Detection scheme), and the fact that a station willing to transmit and senses the medium free, doesn’t necessarily mean that the medium is free around the receiver area. In order to overcome these problems, the 802.11 uses a Collision Avoidance mechanism together with a Positive Acknowledge scheme, as follows: A station willing to transmit senses the medium, if the medium is busy then it defers. If the medium is free for a specified time (called DIFS, Distributed Inter Frame Space, in the standard) then the station is allowed to transmit, the receiving station will check the CRC of the received packet and send an acknowledgment packet (ACK). Receipt of the acknowledgment will indicate the transmitter that no collision occurred. If the sender does not receive the acknowledgment then it will retransmit the fragment until it gets acknowledged or thrown away after a given number of retransmissions. Virtual Carrier Sense In order to reduce the probability of two stations colliding because they cannot hear each other, the standard defines a Virtual Carrier Sense mechanism: A station willing to transmit a packet will first transmit a short control packet called RTS (Request To Send), which will include the source, destination, and the duration of the following transaction (i.e. the packet and the respective ACK), the destination station will respond (if the medium is free) with a response control Packet called CTS (Clear to Send), which will include the same duration information. All stations receiving either the RTS and/or the CTS, will set their Virtual Carrier Sense indicator (called NAV, for Network Allocation Vector), for the given duration, and will use this information together with the Physical Carrier Sense when sensing the medium. This mechanism reduces the probability of a collision on the receiver area by a station that is “hidden” from the transmitter, to the short duration of the RTS transmission, because the station will hear the CTS and “reserve” the medium as busy until the end of the transaction. The duration information on the RTS also protects the transmitter area from collisions during the ACK (by stations that are out of range from the acknowledging station). It should also be noted that because of the fact that the RTS and CTS are short frames, it also reduces the overhead of collisions, since these are recognized faster than it would be recognized if the whole packet was to be transmitted, (this is true if the packet is significantly bigger than the RTS, so the standard BreezeCom © copyright BreezeCOM 1997 Page 6 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 Witflilfifi'fi fiammwmhafihmfi allows for short packets to be transmitted without the RTS/CTS transaction, and this is controlled per station by a parameter called RTSThreshold). The following diagrams show a transaction between two stations A and B, and the NAV setting of their neighbors: G1=S|FS G3=DIFS CW=Contemion Window The NAV State is combined with the physical carrier sense to indicate the busy state of the medium. MAC Level Acknowledgments As mentioned earlier in this document, the MAC layer performs the Collision Detection by expecting the reception of an acknowledge to any transmitted fragment (exception to these are packets that have more than one destination, such as Multicasts, which are not acknowledged). Fragmentation and Reassembly Typical LAN protocols use packets of several hundreds of bytes (e. g Ethernet longest packet could be up to 1518 bytes long), on a Wireless LAN environment there are some reasons why it would be preferable to use smaller packets: 0 Because of the higher Bit Error Rate of a radio link , the probability of a packet to get corrupted increases with the packet size. 0 In case of packet corruption (either because of collision or noise), the smallest the packet the less overhead it causes to retransmit it. 0 On a Frequency Hopping system, the medium is interrupted periodically for hopping (in our case every 20 milliseconds), so the smaller the packet, the smaller the chance that the transmission will be postponed to after the dwell time. BreezeCom © copyright BreezeCOM 1997 Page 7 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mam; fiammarmrammfi On the other hand, it doesn’t make sense to introduce a new LAN protocol that cannot deal with packets of 1518 bytes which are used on Ethernet, so the committee decided to solve the problem by adding a simple fragmentation/reassembly mechanism at the MAC Layer. The mechanism is a simple Send—and—Wait algorithm, where the transmitting station is not allowed to transmit a new fragment until one of the following happens: I. Receives an ACK for the said fragment, or 2. Decides that the fragment was retransmitted too many times and drops the whole frame It should be noted that the standard does allow the station to transmit to a different address between retransmissions of a given fragment, this is particularly useful when an AP has several outstanding packets to different destinations and one of them does not respond. The following diagram shows a frame (MSDU) being divided to several fragments (MPDUs): MAC MAC MAC MAC Frame Body Frame Body Frame Body Frame Body Fragment 0 Fragment 1 Fragment 2 Fragment 3 Inter Frame Spaces The Standard defines 4 types of Inter Frame Spaces, which are use to provide different priorities: 0 SIFS - Which stands for Short Inter Frame Space, is used to separate transmissions belonging to a single dialog (e. g. Fragment-Ack), and is the minimum Inter Frame Space, and there is always at most one single station to transmit at this given time, hence having priority over all other stations. This value is a fixed value per PHY and is calculated in such a way that the transmitting station will be able to switch back to receive mode and be capable of decoding the incoming packet, on the 802.11 FH PHY this value is set to 28 microseconds 0 PIFS - Point Cooordination IFS, is used by the Access Point (or Point Coordinator, as called in this case), to gain access to the medium before any other station. This value is SIFS plus a Slot Time (defined in the following paragraph), i.e 78 microseconds. 0 DIFS - Distributed IFS, is the Inter Frame Space used for a station willing to start a new transmission, which is calculated as PIFS plus one slot time, i.e. 128 microseconds and 0 EIFS - Extended IFS, which is a longer IFS used by a station that has received a packet that could not understand, this is needed to prevent the station (who could not understand the duration information for the Virtual Carrier Sense) from colliding with a future packet belonging to the current dialog. BreezeCom © copyright BreezeCOM 1997 Page 8 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mam; fiammazmrarmms Exponential Backoff Algorithm Backoff is a well known method to resolve contention between different stations willing to access the medium, the method requires each station to choose a Random Number (n) between 0 and a given number, and wait for this number of Slots before accessing the medium, always checking whether a different station has accessed the medium before. The Slot Time is defined in such a way that a station will always be capable of determining if other station has accessed the medium at the beginning of the previous slot. This reduces the collision probability by half. Exponential Backoff means that each time the station chooses a slot and happens to collide, it will increase the maximum number for the random selection exponentially. The 802.11 standard defines an Exponential Backoff Algorithm, that must be executed in the following cases: 0 If when the station senses the medium before the first transmission of a packet, and the medium is busy, 0 After each retransmission, and 0 After a successful transmission The only case when this mechanism is not used is when the station decides to transmit a new packet and the medium has been free for more than DIFS. The following figure shows a schematic of the access mechanism: Immediate access when medium DIFS Contention Window is free >= DIFS Busy Medium I I ackoff—Window ‘7 Select Slot and Decrement Backoff as long ‘ ’ ‘ as medium is idle Next Frame Slot time BreezeCom © copyright BreezeCOM 1997 Page 9 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mam; flammwmrafihms How Does a Station Join an existing Cell (BSS)? When a station wants to access an existing BSS (either after power—up, sleep mode, or just entering the BSS area), the station needs to get synchronization information from the Access Point (or from the other stations when in ad—hoc mode, which will be discussed later). The station can get this information by one of two means: 1. Passive scanning: In this case the station just waits to receive a Beacon Frame from the AP, (the beacon frame is a periodic frame sent by the AP with synchronization information), or 2. Active Scanning: In this case the station tries to find an Access Point by transmitting Probe Request Frames, and waiting for Probe Response from the AP. The two methods are valid, and either one can be chosen according to the power consumption/performance tradeoff. The Authentication Process Once the station has found an Access Point, and decided to join its BSS, it will go through the Authentication Process, which is the interchange of information between the AP and the station, where each side proves the knowledge of a given password. The Association Process When the station is authenticated, then it will start the Association Process, which is the exchange of information about the stations and BSS capabilities, and which allows the DSS (the set of APs to know about the current position of the station). Only after the association process is completed, a station is capable of transmitting and receiving data frames. BreezeCom © copyright BreezeCOM 1997 Page 10 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 Mkefesfi flMMHflfbfiflhflfi Roaming Roaming is the process of moving from one cell (or BSS) to another without loosing connection. This function is similar to the cellular phones handover, with two main differences: 0 On a LAN system which is packet based, the transition from cell to cell may be performed between packet transmissions, as opposed to telephony where the transition may occur during a phone conversation, this makes the LAN roaming a little easier, but 0 On a voice system a temporary disconnection may not affect the conversation, While on a packet based environment it will reduce significantly the performance because retransmission would be performed by the upper layer protocols. The 802.11 standard does not define how should the roaming be performed, but defines the basic tools for that, this includes the active/passive scanning, and a re-association process, Where a station which is roaming from one Access Point to another will become associatted with the new onel. 1 The BreezeNet product line provides an enhanced roaming mechanism (under patent), which allows stations to roam at speeds of 60 Km/h without loosing nor duplicating packets. BreezeCom © copyright BreezeCOM 1997 Page 1 l A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 Mhfihfifi fimmaxmbarmms Keeping Synchronization Stations need to keep synchronization, this is needed for keeping hopping synchronized, and other functions like Power Saving. On an infrastructure BSS this is performed by all the stations updating their clocks according to the AP’s clock, using the following mechanism: The AP transmits periodic frames called Beacon Frames, these frames contain the value of the AP’s clock on the moment of the transmission (note that this is the moment when the transmission really occurs, and not when it is put in the queue for transmission, since the Beacon Frame is transmitted using the rules of CSMA, the transmission may be delayed significantly). The receiving stations check the value of their clock at the receiving moment, and correct it to keep synchronizing with the AP’s clock, this prevents clock drifting which could cause loss of synch after a couple of hours of operation. BreezeCom © copyright BreezeCOM 1997 Page 12 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mam; flammarmrarmms Security Security is one of the first concerns of people deploying a Wireless LAN, the 802.1 I committee has addressed the issue by providing what is called WEP (Wired Equivalent Privacy). The main concerns of users are that an intruder would not be able to: 0 Access the Network resources by using similar Wireless LAN equipment, and 0 Be able to capture the Wireless LAN traffic (eavesdropping) Preventing Access to Network Resources This is done by the use of an Authentication mechanism where a station needs to prove knowledge of the current key, this is very similar to the Wired LAN privacy, on the sense that an intruder needs to enter the premises (by using a physical key) in order to connect his workstation to the wired LAN. Eavesdropping Eavesdropping is prevented by the use of the WEP algorithm which is a Pseudo Random Number Generator initialized by a shared secret key. This PRNG outputs a key sequence of pseudo-random bits equal in length to the largest possible packet which is combined with the outgoing/incomming packet producing the packet transmitted in the air. The WEP algorithm is a simple algorithm based on RSA’s RC4 algorithm which has the following properties: 0 Reasonably strong: Brute—force attack to this algorithm is difficult because of the fact that every frame is sent with an Initialization Vector which restarts the PRNG for each frame. 0 Self Synchronizing: The algorithm synchronizes again for each message, this is needed in order to work on a connectionless environment, where packets may get lost (as any LAN). BreezeCom © copyright BreezeCOM 1997 Page 13 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 Mkefesfi fiammwmérarmmfi Power Saving Wireless LANs are typically related to mobile applications, and in this type of applications battery power is a scare resource, this is the reason why the 802.1 I standard directly addresses the issue of Power Saving and defines a whole mechanism to allow stations to go into sleep mode for long periods of time without loosing information. The main idea behind the Power Saving Mechanism is that the AP maintains an updated record of the stations currently working in Power Saving mode, and buffers the packets addressed to these stations until either the stations specifically require to get the packets by sending a polling request, or until they change their operation mode. The AP also transmits periodically (as part of its Beacon Frames) information about which Power Saving Stations have frames buffered at the AP, so these stations should wake up in order to receive one of these Beacon Frames, and if there is an indication that there is a frame stored at the AP waiting for delivery, then the station should stay awake and send a Poll message to the AP to get these frames. Multicasts and Broadcasts are stored by the AP, and transmitted at a pre-known time (each DTHVI), where all Power Saving stations who wish to receive this kind of frames should be awake. BreezeCom © copyright BreezeCOM 1997 Page 14 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 MEN ammmmam; Frame Types There are three main types of frames: 0 Data Frames: which are used for data transmission 0 Control Frames: which are used to control access to the medium (e.g. RTS, CTS, and ACK), and 0 Management Frames: which are frames that are transmitted the same way as data frames to exchange management information, but are not forwarded to upper layers. Each of these types is as well subdivided into different Subtypes, according to their specific function. BreezeCom © copyright BreezeCOM 1997 Page 15 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mam; fiammwmharmms Frame Formats All 802.1 1 frames are composed by the following components PLCP Header MAC Data Preamble This is PHY dependent, and includes: 0 Synch: An 80-bit sequence of alternating zeros and ones, which is used by the PHY circuitry to select the appropriate antenna (if diversity is used), and to reach steady-state frequency offset correction and synchronization with the received packet timing, and 0 SFD: A Start Frame delimiter which consists of the 16-bit binary pattern 0000 1100 1011 1101, which is used to define the frame timing. PL CP Header The PLCP Header is always transmitted at 1 Mbit/s and contains Logical information that will be used by the PHY Layer to decode the frame, and consists of: 0 PLCP_PDU Length Word: which represents the number of bytes contained in the packet, this is useful for the PHY to correctly detect the end of packet, 0 PLCP Signaling Field: which currently contains only the rate information, encoded in 0.5 MBps increments from 1 Mbit/s to 4.5 Mbit/s, and 0 Header Error Check Field: Which is a 16 Bit CRC error detection field MAC Data The following figure shows the general MAC Frame Format, part of the fields are only present on part of the frames as described later. Octets: 2 2 0 - 2312 4 6 6 6 2 6 Frame Duration/ Sequence Frame MAC Header BreezeCom © copyright BreezeCOM 1997 Page 16 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 whom ammmmam; Frame Control Field The Frame Control field contains the following information: B0 B1B2 BSB4 B7 BS B9 B10 B11 B12 B13 B14 B15 Protocol To From More Pwr More Bits: 2 2 4 1 1 1 1 1 1 1 1 Protocol Version This field consists of 2 bits which are invariant in size and placement across following versions of the 802.1 1 Standard, and will be used to recognize possible future versions. In the current version of the standard the value is fixed as 0. BreezeCom © copyright BreezeCOM 1997 Page 17 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mas-ms; fiflWMAififffiflhflfi Type and Subtype This 6 bits define the Type and SubType of the frame as indicated in the following table: Type Value Type Description Subtype Subtype Description b3 b2 Value b7 b6 b5 b4 -m_ -IE- Ill]- BreezeCom © copyright BreezeCOM 1997 Page 18 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mam; flammwmrarmms ToDS This bit is set to 1 when the frame is addressed to the AP for forwarding it to the Distribution System (including the case where the destination station is in the same BSS, and the AP is to relay the frame). The Bit is set to 0 in all other frames. FromDS This bit is set to 1 when th eframe is comming from the Distribution System. More Fragments This bit is set to 1 when there are more fragments belonging to the same frame following this current fragment. Retry This bit indicates that this fragment is a retransmission of a previously transmitted fragment, this will be used by the receiver station to recognize duplicate transmissions of frames that may occur when an Acknowledgment packet is lost. Power Management This bit indicates the Power Management mode that the station will be in after the transmission of this frame. This is used by stations which are changing state either from Power Save to Active or viceversa. More Data This bit is also used for Power Management and it is used by the AP to indicate that there are more frames buffered to this station. The station may decide to use this information to continue polling or even changing mode to Active. WEP This bit indicates that the frame body is encrypted according to the WEP algorithm Order This bit indicates that this frame is being sent using the Strictly-Ordered service class.2 2 The Strictly—Ordered Service Class is defined for users that cannot accept change of oredring between Unicast Frames and Multicast Frames (ordering of unicast frames to a specific address is always maintained). The only known protocol that would need this service class is DEC’s LAT. BreezeCom © copyright BreezeCOM 1997 Page 19 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 Wkem; fiflWMHflEHfififlfi Duration/ID This field has two meanings depending on the frame type: In Power-Save Poll messages this is the Station ID, and In all other frames this is the duration value used for the NAV Calculation. Address Fields A frame may contain up to 4 Addresses depending on the ToDS and FromDS bits defined in the Control Field, as follows: Address-1 is always the Recipient Address (i.e. the station on the BSS who is the immediate recipient of the packet), if ToDS is set this is the Address of the AP, if ToDS is not set then this is the address of the end-station. Address-2 is always the Transmitter Address (i.e. the station who is physically transmitting the packet), if FromDS is set this is the address of the AP, if it is not set then it is the address of the Station. Address-3 is in most cases the remaining, missing address, on a frame with FromDS set to 1, then the Address-3 is the original Source Address, if the frame has the ToDS set then Address 3 is the destination Address. Address-4 is used on the special case where a Wireless Distribution System is used, and the frame is being transmitted from one Access Point to another, in this case both the ToDS and FromDS bits are set, so both the original Destination and the original Source Addresses are missing. The following Table summarizes the usage of the different Addresses according to the ToDS and FromDS bits setting: m Address1 Address 2 Address 3 Address 4 n“ "- --_ BSSID Sequence Control The Sequence Control Field is used to represent the order of different fragments belonging to the same frame, and to recognize packet duplications, it consists of two subfields Fragment Number, and Sequence Number, which define the frame and the number of the fragment in the frame. CRC The CRC is a 32 bit field containing a 32-bit Cyclic Redundancy Check (CRC) BreezeCom © copyright BreezeCOM 1997 Page 20 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 Mkefesfi fiammarmérarmmfi Most Common Frames Format RTS Frame Format The RTS frame looks as follows: octets: 2 2 6 6 4 Frame Duration RA TA CRC Control MAC Header The RA of the RTS frame is the address of the STA, on the wireless medium, that is the intended immediate recipient of the next Data or Management frame. The TA shall be the address of the STA transmitting the RTS frame. The Duration value is the time, in microseconds, required to transmit the next Data or Management frame, plus one CTS frame, plus one ACK frame, plus three SIFS intervals. CTS Frame Format The CTS frame looks as follows: octets: 2 2 6 4 Frame Duration RA CRC Control ‘—> MAC Header The Receiver Address (RA) of the CTS frame is copied from the Transmitter Address (TA) field of the immediately previous RTS frame to which the CTS is a response. The Duration value is the value obtained from the Duration field of the immediately previous RTS frame, minus the time, in microseconds, required to transmit the CTS frame and its SIFS interval. BreezeCom © copyright BreezeCOM 1997 Page 21 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mar-am fimmmmrsrm; ACK Frame Format The ACK frame looks as follows:. octets: 2 2 5 4 Frame . <—> MAC Header The Receiver Address of the ACK frame is copied from the Address 2 field of the immediately previous frame. If the More Fragment bit was set to 0 in the Frame Control field of the previous frame, the Duration value is set to 0, otherwise the Duration value is obtained from the Duration field of the previous frame, minus the time, in microseconds, required to transmit the ACK frame and its SIFS interval. BreezeCom © copyright BreezeCOM 1997 Page 22 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 mmm; flmmaflmrmms Point Coordination Function (PCF) Beyond the basic Distributed Coordination Function, there is an optional Point Coordination Function, which may be used to implement time—bounded services, like voice or video transmission. This Point Coordination Function makes use of the higher priority that the Access Point may gain by the use of a smaller Inter Frame Space (PIFS). By using this higher priority access the Access Point issues polling requests to the stations for data transmission, hence controlling the medium access. In order to allow regular stations the capability to still access the medium, there is a provision that the Access Point must leave enough time for Distributed Access in between the PCF BreezeCom © copyright BreezeCOM 1997 Page 23 A Technical Tutorial on the IEEE 802.1 1 Standard 18 July, 1996 wheres; flmxamamrmms Ad-hoc Networks In certain circumstances the users will desire to build up Wireless LAN networks without an infrastructure (more specifically without an Access Point), this may include file transfer between two notebooks users, a coworkers meeting outside the office, etc. The 802.1 1 Standard addresses this need by the definition of an “ad—hoc” mode of operation, in this case there is no Access Point and part of its functionality is performed by the end—user stations (like Beacon Generation, synchronization, etc), and other functions are not supported (like frame—relaying between two stations not in range, or Power Saving). BreezeCom © copyright BreezeCOM 1997 Page 24 ...
View Full Document

Page1 / 24

802.11-tutorial - A Technical Tutorial on the IEEE 802.11...

This preview shows document pages 1 - 24. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online