On an 802.11 network, why do stations use CSMA/CA to avoid collisions instead of detecting them as classic shared Ethernet did?
answer
- a radio cannot hear while it talks
- collisions happen at the receiver
- defer, then a random backoff
- the ACK is the only verdict
basics
~20 sAn 802.11 radio cannot listen while it transmits, and a collision happens at the receiver, which the sender may not hear. So Wi-Fi senses the medium, defers, waits a random backoff and treats a missing ACK as failure.
solid answer
~50 sCollision detection needs a transmitter to compare what it sends with what it hears on the medium. A radio's own transmission drowns its receiver, so an 802.11 station cannot do that, and the collision that matters happens at the receiver: two stations that cannot hear each other can both see a clear channel and still collide at the access point. So the 802.11 MAC avoids collisions instead, with **physical carrier sense**, the **NAV** (virtual carrier sense from the `Duration` field), interframe spaces and a **random backoff** from a contention window. The sender learns the outcome only from the acknowledgement, an **ACK** that returns a SIFS after an individually addressed frame; no ACK means a retransmission from a larger window. The price is overhead on every frame, one reason a Wi-Fi link falls well short of its PHY rate.
go deeper
Remember the two reasons: a radio cannot listen while it transmits, and the collision happens at the receiver. Then name the ACK as how the sender learns the result.
Walk through carrier sense, the DIFS wait, the random backoff and the ACK after a SIFS, and say why a missing ACK triggers a retransmission from a wider window.
Show what follows operationally: retries as the symptom, the ambiguity of a lost ACK, unacknowledged group-addressed frames, and why contention grows with the number of stations on a channel.
Frame airtime as the scarce resource the MAC shares: every frame pays a fixed contention cost, so design choices that cut contenders per channel matter more than raw link rate.
## Two ways to share one medium Any network where several stations share one medium needs a rule for who talks when. Classic half-duplex Ethernet on a shared segment used **CSMA/CD** (carrier sense multiple access with collision detection): listen, transmit, and abort with a jam signal the moment you hear your frame being trampled. The wired details belong with Ethernet. The IEEE 802.11 MAC keeps the first half of that idea, **carrier sense**, and replaces detection with **collision avoidance**: **CSMA/CA**. ## Why an 802.11 radio cannot detect a collision Collision detection rests on two assumptions that do not hold on a radio channel: - **The sender cannot listen while it talks.** A radio's own transmission is many orders of magnitude stronger at its own antenna than any distant station's signal, so its receiver is effectively deaf while it transmits. A typical 802.11 radio is half duplex: it switches between transmitting and receiving. - **The collision that matters happens at the receiver.** What decides success is the mix of signals arriving at the receiver. The sender may hear a clean channel locally while another station, out of its range, is talking into the same access point. This is the **hidden-node** case. - **A lost frame has many causes.** Fading, interference from non-802.11 sources and a weak signal destroy frames just as a collision does, so even a sender that could listen would learn little. ## What CSMA/CA does instead Every station follows the same procedure before sending a frame: 1. **Carrier sense.** The medium counts as busy if the radio's clear channel assessment detects energy or a decodable preamble (physical carrier sense), or if its **NAV**, a timer loaded from the `Duration` field of frames it overheard, is still running (virtual carrier sense). 2. **Defer.** Wait until the medium has been idle for a **DIFS** (with WMM, an AIFS that differs per traffic category, covered with WMM). 3. **Back off.** If the medium was busy, draw a random number of slots between 0 and the **contention window** and count down only while the medium stays idle, freezing the counter whenever someone else transmits. 4. **Transmit the whole frame.** There is no abort halfway through; the sender cannot tell that anything went wrong. 5. **Wait for the ACK.** The receiver of an individually addressed frame answers with an **ACK** after a **SIFS**, the shortest gap, so no contender can slip in first. No ACK means the sender retransmits, sets the `Retry` bit, and backs off from a larger window. ## The ACK is the only collision signal Because nothing is detected on the air, the acknowledgement carries all the information the sender gets: - **A missing ACK is ambiguous.** The sender cannot tell a collision from a weak signal or interference. Rate adaptation that reads every lost ACK as poor signal can step down to a slower rate, which makes each frame longer and more exposed to the next collision. - **Group-addressed frames from the AP are not acknowledged.** Broadcast and multicast frames the access point sends into its cell get no ACK and therefore no retry; a collision loses them silently. (A client's broadcast travels first to the AP as an individually addressed frame, which is acknowledged.) - **Aggregated frames** are confirmed with a block acknowledgement instead of one ACK each; that mechanism is covered with the 802.11 frame types. ## CSMA/CD and CSMA/CA side by side | Aspect | Classic shared Ethernet (CSMA/CD) | 802.11 (CSMA/CA) | |---|---|---| | Listen while sending | Yes; abort and jam on collision | No; the whole frame is sent | | Where a collision is visible | On the wire, at the sender | Only at the receiver | | Evidence of success | No collision during the frame | An ACK after a SIFS | | When backoff happens | After a detected collision | Before sending into a busy medium, and after a missing ACK | | Stations out of each other's range | Not on a correctly built segment | Normal: the hidden node | ## What it means for the WLAN you run - **Airtime, not bandwidth, is the scarce resource.** Every frame pays for deferral, backoff, its preamble and the ACK, and the channel is half duplex, which is one reason a Wi-Fi link falls well short of its PHY rate. - **More contenders on one channel mean more wasted slots.** Two stations whose backoff counters reach zero in the same slot still collide, and the chance grows with the number of active stations sharing the channel, whichever cell they belong to. - **Retries are the symptom to measure.** A rising share of frames with the `Retry` bit set, concentrated on particular clients or directions, is where a contention problem shows first.
- If CSMA/CA avoids collisions, why do collisions still happen on a busy 802.11 channel?Avoidance lowers the odds; it does not remove them. Two stations can draw backoff counts that reach zero in the same slot, and the chance rises with the number of active stations on the channel. Hidden stations collide too, because each sees an idle medium at its own position. In both cases the only evidence is the missing ACK, followed by a retransmission from a wider contention window.
- Why are multicast frames that an 802.11 access point sends into its cell less reliable than unicast frames?Group-addressed frames from the AP are not acknowledged, so the MAC has no way to know they were lost and never retries them. They are also sent at a rate every station in the cell can decode, usually a low one, which costs airtime. A collision or a burst of interference simply loses the frame, leaving recovery to higher layers.
- Why can lost ACKs make an 802.11 station lower its data rate even when its signal is strong?The sender cannot tell why an ACK is missing. Rate adaptation that treats every lost ACK as poor signal steps down to a more robust, slower rate. When the real cause is collisions, the slower rate makes each frame longer, so it overlaps other transmissions more often, which can make the retry problem worse rather than better.
- Wi-Fi stations detect collisions while transmitting, just as stations on a shared Ethernet hub did.
- CSMA/CA prevents every collision, so any retry must be caused by interference.
- A missing ACK proves that a collision happened.
- Multicast frames from the access point are acknowledged and retried like unicast frames.
- An 802.11 station backs off only after it has detected a collision.