Content deleted Content added
→RRTS: move ref out of heading |
|||
(6 intermediate revisions by 4 users not shown) | |||
Line 1:
{{Short description|Slotted medium access control protocol widely used in ad hoc networks}}
'''Multiple Access with Collision Avoidance for Wireless''' ('''MACAW''')<ref name="MACAW">{{cite journal|author=Vaduvur Bharghavan|title=MACAW: A Medium Access Protocol for Wireless LAN's|url=http://pdos.csail.mit.edu/decouto/papers/bharghavan94.pdf|version=In the Proc. ACM SIGCOMM Conference (SIGCOMM '94), August 1994, pages 212-225|date=1994-08-01|accessdate=2007-01-18|display-authors=etal}}</ref> is a slotted [[medium access control]] (MAC) protocol widely used in [[ad hoc network]]s.<ref name="SMAC_1">{{cite journal |author=Wei Ye|title=An Energy-Efficient MAC Protocol for Wireless Sensor Networks |url=http://www.isi.edu/~weiye/pub/smac_infocom.pdf|version=INFOCOM 2002|date=2002-06-01|accessdate=2006-11-26 |archiveurl = https://web.archive.org/web/20061104045110/http://www.isi.edu/~weiye/pub/smac_infocom.pdf |archivedate = 2006-11-04|display-authors=etal}}</ref> Furthermore, it is the foundation of many other
== Principles of operation ==
[[
Assume that node A has data to transfer to node B. Node A initiates the process by sending a ''Request to Send'' frame (RTS) to node B. The destination node (node B) replies with a ''Clear To Send'' frame (CTS). After receiving CTS, node A sends data. After successful reception, node B replies with an acknowledgement frame (ACK). If node A has to send more than one data fragment, it has to wait a random time after each successful data transfer and compete with adjacent nodes for the medium using the RTS/CTS mechanism.<ref name="MACAW"/>
Line 21 ⟶ 22:
MACAW is a [[non-persistent]] [[slotted]] protocol, meaning that after the medium has been busy, for example after a CTS message, the station waits a random time after the start of a time slot before sending an RTS. This results in fair access to the medium. If for example nodes A, B and C have data fragments to send after a busy period, they will have the same chance to access the medium since they are in transmission range of each other.
=== RRTS ===
Source:<ref name="MACAW"/> Node D is unaware of the ongoing data transfer between node A and node B. Node D has data to send to node C, which is in the transmission range of node B. D initiates the process by sending an RTS frame to node C. Node C has already deferred its transmission until the completion of the current data transfer between node A and node B (to avoid [[co-channel interference]] at node B). Hence, even though it receives RTS from node D, it does not reply back with CTS. Node D assumes that its RTS was not successful because of collision and hence proceeds to ''back off'' (using an [[exponential backoff]] algorithm).
Line 38 ⟶ 41:
==Ongoing research==
Additional back-off algorithms have been developed and researched to improve performance.<ref name=Miao>{{cite book|author1=
=== Unsolved problems ===
MACAW does not generally solve the [[exposed terminal problem]]. Assume that node G has data to send to node F in our example. Node G has no information about the ongoing data transfer from A to B. It initiates the process by sending an RTS signal to node F. Node F is in the transmission range of node A and cannot hear the RTS from node G, since it is exposed to [[co-channel interference]]. Node G assumes that its RTS was not successful because of collision and hence backs off before it tries again. In this case, the solution provided by the RRTS mechanism will not improve the situation much since the DATA frames sent from B are rather long compared to the other frames. The probability that F is exposed to transmission from A is rather high. Node F has no idea about any node interested in initiating data transfer to it, until G happens to transmit an RTS in between transmissions from A.
Furthermore, MACAW might not behave normally in [[
== See also ==
Line 49 ⟶ 52:
== References ==
{{Reflist}}
{{Channel access methods}}
|