CSMA/CA: Carrier Sense Multiple Access with Collision Avoidance

In any wireless network where multiple stations share the same channel, coordination is essential. But wireless stations cannot rely on a centralized coordinator for every transmission decision—the overhead would be prohibitive. Instead, IEEE 802.11 implements a distributed timing architecture based on Interframe Spaces (IFS).

Interframe spaces are mandatory waiting periods between frames. They serve multiple critical functions:

1. Priority differentiation — Higher-priority traffic uses shorter IFS, gaining preferential access
2. Settling time — Allows the channel to clear between transmissions
3. Processing time — Gives receivers time to decode and prepare responses
4. Collision avoidance — Creates guard bands that reduce collision probability

The IFS system is elegant in its simplicity: by controlling when stations can transmit, it controls who transmits without requiring explicit coordination.

IEEE 802.11 defines multiple interframe spaces, each serving a specific purpose. The key insight is that shorter IFS means higher priority—a station waiting a shorter time will always transmit before a station waiting a longer time.

The Timing Relationship:

The different IFS values are mathematically related:

SIFS = Minimum turnaround time (hardware-dependent)
Slot Time = Propagation delay + CCA time + MAC processing

PIFS = SIFS + 1 × Slot Time
DIFS = SIFS + 2 × Slot Time
AIFS[AC] = SIFS + AIFSN[AC] × Slot Time
EIFS = SIFS + DIFS + ACKtime

This relationship ensures that:

• SIFS is always shorter than PIFS (by 1 slot)
• PIFS is always shorter than DIFS (by 1 slot)
• DIFS is the baseline for normal contention
• EIFS provides extended protection after errors

The Short Interframe Space (SIFS) is the shortest IFS and provides the highest priority. It's used for frames that are direct responses to previous frames—situations where the sender is expecting an immediate reply.

SIFS Values by PHY:

The SIFS duration is determined by hardware constraints—specifically, the time required for:

1. Receiving the last bit of the previous frame
2. Decoding the frame to determine if response is needed
3. Switching the transceiver from receive to transmit mode
4. Beginning transmission of the response

The SIFS Timing Window:

The receiver must begin transmitting the response within a tight window after SIFS:

[Data Frame Ends] ---(SIFS)---> [Response Must Begin]
                    10-16 μs

If the response begins too early, it may collide with the end of the previous frame or the receiver may not be ready. If it begins too late, other stations may sense the channel as idle and begin their own DIFS countdown.

Practical implementations provide a ±4 μs tolerance window for SIFS timing. Hardware manufacturers carefully tune their radio timing to meet this requirement.

The DCF Interframe Space (DIFS) is used by stations operating in Distributed Coordination Function (DCF) mode—the standard contention-based access method for 802.11. Any station with data to send must wait for DIFS after sensing the channel idle before beginning the backoff procedure.

DIFS Calculation:

DIFS = SIFS + (2 × Slot Time)

Why Two Slot Times?

DIFS includes two slot times above SIFS to provide:

1. One slot for propagation and detection — Ensures all stations detect any ongoing transmission before their DIFS expires
2. One slot as priority separation — Guarantees DIFS traffic never interferes with SIFS-priority traffic (like ACKs)

The DIFS/Backoff Dance:

Consider a typical scenario where the channel becomes idle after a transmission:

Time:    0     16μs   25μs   34μs   43μs   52μs   61μs
         ↓      ↓      ↓      ↓      ↓      ↓      ↓
Channel: [IDLE]-[SIFS]-[PIFS]-[DIFS]--[Slot 1]--[Slot 2]--[Slot 3]
                        ↑
                  DIFS completed - Backoff can begin

After DIFS:

• Station A has backoff = 2 slots: Will transmit at 52 μs (34 + 18)
• Station B has backoff = 5 slots: Will transmit at 79 μs (34 + 45)
• Station A wins; B freezes at 52 μs with 3 slots remaining

The Arbitration Interframe Space (AIFS) was introduced in IEEE 802.11e to enable Quality of Service (QoS) differentiation. Instead of all traffic using the same DIFS, different traffic categories use different AIFS values, providing priority-based access.

AIFS Calculation:

AIFS[AC] = SIFS + (AIFSN[AC] × Slot Time)

Where AIFSN (AIFS Number) is the number of slot times for each Access Category:

AIFS Priority Visualization:

Time after channel becomes idle:

0      16μs         34μs         43μs         79μs
|-------|-------------|-------------|-------------|
SIFS ends         VO/VI         Best Effort   Background
                  can start     can start     can start
                  backoff       backoff       backoff

If VO has backoff=0 and BE has backoff=0:
- VO transmits at 34 μs
- BE cannot transmit until after VO completes

Same-Priority Contention:

When two stations have frames in the same Access Category, they use the same AIFS. The random backoff then determines which transmits first. The combination of AIFS differentiation and random backoff provides both priority and fairness within priority classes.

The PCF Interframe Space (PIFS) is used by the Point Coordination Function (PCF), an optional centralized access mode in 802.11. PIFS provides priority between SIFS and DIFS, allowing the Point Coordinator (typically the Access Point) to seize the channel before normal DCF contention begins.

PIFS Calculation:

PIFS = SIFS + (1 × Slot Time)

PCF Operation:

In PCF mode, the network alternates between contention periods (CP) and contention-free periods (CFP):

1. Access Point sends Beacon — Contains information about CFP schedule
2. CFP begins — AP waits PIFS after channel idle, then sends CF-Poll to stations
3. Polled station responds — After SIFS with data or null frame
4. AP continues polling — Each poll-response uses SIFS/PIFS timing
5. CFP ends — AP sends CF-End, returning to normal DCF operation

PIFS for Channel Access Priority:

Beyond PCF, PIFS is also used in some special scenarios:

1. Beacon transmission — Access Points may use PIFS before beacons to ensure timely delivery
2. Channel switching — Some implementations use PIFS during channel switch announcements
3. HCCA (HCF Controlled Channel Access) — The 802.11e hybrid coordinator uses PIFS timing

Why One Slot Less Than DIFS?

PIFS provides exactly one slot time of priority over DCF stations. This is sufficient because:

• DCF stations must wait DIFS before backoff begins
• A station waiting only PIFS will always transmit before any DCF backoff counter reaches zero
• But PIFS doesn't interfere with SIFS-priority traffic (ACKs, CTS) which uses even shorter timing

The Extended Interframe Space (EIFS) is used when a station receives a frame that it cannot properly decode—indicated by a failed Frame Check Sequence (FCS). EIFS provides extra time to allow the intended communication to complete before the station attempts its own transmission.

EIFS Calculation:

EIFS = SIFS + DIFS + ACK_Tx_Time

Where ACK_Tx_Time is the time to transmit an ACK frame at the lowest mandatory rate:

For 802.11b, EIFS can exceed 300 μs because ACK at 1 Mbps takes much longer.

Why EIFS Exists:

Consider this scenario:

1. Station A transmits to the AP
2. Station B is too far from A to hear the transmission clearly (receives with errors)
3. Station B's received frame has FCS errors—it knows something was transmitted but not what
4. The AP successfully receives A's frame and will send ACK after SIFS
5. If B started normal DIFS countdown immediately, B might transmit and corrupt the ACK

EIFS solves this by making B wait longer:

[A's Frame ends]--SIFS--[AP's ACK]--DIFS--[Normal Contention]
        ↑                                          ↑
   B receives errors                          B can finally
   B starts EIFS                              contend

The EIFS duration is long enough to cover the worst-case ACK transmission, ensuring B doesn't corrupt the response it couldn't decode.

EIFS Recovery:

Once a station properly receives any valid frame (even if not addressed to it), EIFS mode ends and the station returns to normal DIFS operation. This prevents a single error from causing prolonged channel access delays.

Station state:
1. Receive frame with FCS error → Enter EIFS mode
2. Wait EIFS duration
3. Either:
   a. Receive valid frame → Exit EIFS, use normal DIFS
   b. EIFS expires → Can begin contention
4. Subsequent frames use normal IFS unless another error occurs

Let's examine how IFS values work together in typical 802.11 communication scenarios. Understanding these timing diagrams is essential for protocol analysis and troubleshooting.

Scenario 1: Simple Data-ACK Exchange (802.11a)

Station A             Access Point           Station B
    |                      |                     |
    |------ DATA --------->|                     |
    |       (500 μs)       |                     |
    |<----- SIFS (16μs) ---|                     |
    |<------ ACK ----------|                     |
    |       (44 μs)        |                     |
    |                      |                     |
    |<---- DIFS (34μs) --->|<---- DIFS (34μs) -->|
    |                      |                     |
    |<- Backoff countdown begins for both ->     |

Key Observations:

• ACK follows DATA after exactly SIFS (16 μs)
• After ACK ends, all stations wait DIFS before can contend
• During SIFS, no other station will transmit (SIFS < DIFS)
• The DATA-ACK is an atomic transaction

Scenario 2: RTS/CTS Exchange

Time (μs):  0    20    36    80    96   240   256   700   716   760
            |    |     |     |     |     |     |     |     |     |
            RTS  SIFS  CTS   SIFS  DATA  ...   ...   SIFS  ACK   DIFS
            (20μs)    (20μs)      (DATA frame transmission)

Station A:  [RTS]----[wait]-------[DATA]---------------[wait]-[done]
            ↓         ↑           ↓                    ↑
AP:         [receive]-[CTS]------[receive]------------[ACK]--[ready]
            ↓         ↓           ↓                    ↓
Stations    [NAV ====================================NAV expires]
B, C, D:    (Cannot transmit - NAV is set from RTS Duration field)

RTS/CTS Benefits:

• Protects long DATA frame from collision
• Hidden terminals hear CTS and set NAV
• Channel reserved for entire exchange

Scenario 3: QoS Priority with AIFS

Channel becomes idle at time T:

T                T+34μs        T+43μs        T+52μs        T+79μs
|-------------------|-------------|-------------|-------------|
                    AC_VO backoff  AC_BE could   AC_BK could
                    can begin      begin         begin

Assume:
- Voice station has backoff = 1 slot (waits until T+43μs)  
- Best Effort has backoff = 0 slots (would transmit at T+43μs)
- Background has backoff = 0 slots (would transmit at T+79μs)

Result: Voice and BE reach transmission time together at T+43μs
        This is an internal collision - handled by EDCA rules
        (typically lower AC backs off)

Better case:
- Voice has backoff = 0 → transmits at T+34μs
- All other stations freeze backoff
- Voice wins cleanly

AIFS ensures voice gets priority access even with identical backoff values to lower priority traffic.

We've comprehensively covered the interframe spacing mechanisms that orchestrate 802.11 channel access. Let's consolidate the key concepts:

What's Next:

Now that we understand the timing framework, the next page explores the Contention Window mechanism in detail. We'll examine how random backoff works, how the contention window grows after collisions, and how these mechanisms balance fairness with efficiency.