Lectures

CSMA/CA Carrier sense - multiple access / collision avoidance.

  :CSMA/CA
  Listen for idle channel
  If channel idle
  Then
    Send "Request to Send" to access point to reserve a period of time
      on channel. Other devices see RTS request and wait.
      * The RTS is a single small packet, so minimizes the chance of collision 
        with another RTS.

    Access point hears the RTS and determines whether it wants to grant
      access (Clear to send, CTS) or not (no response).

    If "Clear To Send" received from Access point (within given time).
    Then
      Use channel to send frame of data.
      Send end of Frame. Other devices now know they can request channel.
      Goto :CSMA/CA
    
    Else
      * Possibly Access point is denying channel or RTS collided with another
        and got garbled, so Access point didn't respond. 

      Goto :CSMA/CA

    Endi-if
  End-if


By jjgarcia.tsc - https://commons.wikimedia.org/w/index.php?curid=12661157


  Access node will issue only one CTS on any channel. However it can
    be working several non-overlapping channels.

  While this may not completely eliminate collisions, it does reduce them
    but at the cost of additional handshaking overhead.

  Generally, faster network speeds and more access points also work to 
    limit collisions.


  If a transaction frame is small enough, it may be sent without using
    the RTS/CTS handshake. * Like a UDP packet at data-link level.

    Wikipedia list the RTS/CTS maximum packet size as 2347 octets.
    If the data to be sent fits in this limit, the node will just send
      the data of no other traffic sensed.

    The access point will either acknowledge receipt of packet or ignore it.


  If the data is large than a single RTS/CTS packet, then the node sends
    an estimate of the time needed to transmit the data and asks to reserve
    that time period.

  * Reservation system
 
  Instead a type of virtual network sense is implemented by including a
    timing counter, the Network Allocation Vector (NAV), in the RTS packet 
    that tell other nodes how long it needs to complete the transmission 
    transaction it is announcing. 
 
  The NAV includes time for the CTS, the Frame of data being sent, the
    Acknowledgment from the receiver, and any time spacing between 
    the various parts. The spacing is known as inter-frame space.

  The CTS reproduces a slightly reduced NAV to make sure all nodes
    heard the time reservation request.