Changes between Version 4 and Version 5 of 802.11/MAC/Support_HW


Ignore:
Timestamp:
Jun 19, 2015, 11:43:58 AM (9 years ago)
Author:
chunter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 802.11/MAC/Support_HW

    v4 v5  
    2323== MAC CFG Tx Core A ==
    2424
    25 The Tx Core A is fundamentally different than Tx Core B in that its transmission can be qualified on medium idleness. Additionally, it is the transmission state that is capable of honoring a post-Tx timeout interval in which a reception is expected by the MAC state. The DCF implementation uses this core for three different purposes:
     25Tx Core A is capable of honoring a post-Tx timeout interval in which a reception is expected by the MAC state. The DCF implementation uses this core for three different purposes:
    2626
    27 1. Transmission and retransmission of MPDU frames
    28 1. Transmission and retransmission of RTS frames
    29 1. Transmission of CTS frames
     271. Transmission of "short" MPDU frames (i.e. MPDUs that required no RTS medium reservation)
     281. Transmission of RTS frames
     291. Transmission of "long" MPDU frames (i.e. MPDUs that were preceded by an RTS/CTS handshake)
    3030
    31 The unifying trait of each of the above transmissions is a condition on medium idleness prior to each. Furthermore, each of the above transmissions utilizes a post-Tx timeout window during which a response is expected.
     31The unifying trait of each of the above transmissions is the need for a post-Tx timeout window during which a response is expected.
    3232
    3333=== Implementation Details ===
    3434
     35[[Image(tx_core_a.png, width=1000)]]
     36
     37The above image gives a more detailed view on the state machine implemented in Tx Core A. Prior to actually transmitting, the core is capable of starting a backoff or deferring to an already running backoff when the medium is not idle. Alternatively, it can wait for a deterministic interval before transmitting. This interval is defined by either the '''postRxTimer1''' or '''postTxTimer1''' timers described above.
     38
     39For the DCF implementation, short MPDU and RTS transmissions do not employ the green deterministic-wait state. These transmission do employ the purple and blue backoff deferral states. Long MPDU transmissions, however, must occur a deterministic SIFS interval after the previous CTS reception. As such, these transmissions use the green deterministic-wait states.
     40
    3541== MAC CFG Tx Core B ==
    3642
     43The Tx Core B is simpler than Tx Core A. After a transmission is complete, the core is done and does not need to start any kind of post-Tx timeout interval. Optionally, Tx Core B can condition its transmission on medium idleness. The DCF implementation uses this core for two purposes:
     44
     451. Transmission of CTS frames
     461. Transmission of ACK frames
     47
     48Both of the above transmissions have the common trait of being "fire and forget." They are slightly different from one another in that ACK frames must be transmitted regardless of perceived medium busyness. This is not the case for CTS frames, which are only sent when the medium is deemed idle.
     49
    3750=== Implementation Details ===
     51
     52[[Image(tx_core_b.png, width=1000)]]
     53
     54Like Tx Core A, the green section of the above state machine forces the core to wait for a deterministic amount of time prior to a transmission. The DCF uses this to schedule CTS and ACK transmissions a SIFS interval after the previous reception. The CTS case additionally instructs the core to condition transmission on medium idleness.