05.01.2013 Views

Ad Hoc Networks : Technologies and Protocols - University of ...

Ad Hoc Networks : Technologies and Protocols - University of ...

Ad Hoc Networks : Technologies and Protocols - University of ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

210 Use <strong>of</strong> Smart Antennas in <strong>Ad</strong> <strong>Hoc</strong> <strong>Networks</strong><br />

node A’s signal now reaches node E <strong>and</strong> this would cause a collision at node E<br />

(between the data from B <strong>and</strong> the DRTS from A).<br />

The third problem that was identified in [6] was the problem <strong>of</strong> deafness. We<br />

once again refer to Figure 7.5. Consider the case wherein node D is sending<br />

data to node E via node B. The directional exchange <strong>of</strong> control messages might<br />

not be heard by node C. During the time that B is transmitting the message from<br />

D to E, node C might attempt to transmit a DRTS message to node B. However,<br />

since node B has beamformed in the direction <strong>of</strong> E, it is unable to receive the<br />

RTS. Hence, C does not receive a CTS response. In accordance to the IEEE<br />

802.11 MAC protcol policy, node C would then back <strong>of</strong>f. If node D were to<br />

have a continuous stream <strong>of</strong> packets destined for node E, this problem might<br />

repeat itself. Node C would continue to experience RTS failures <strong>and</strong> would<br />

increase its back-<strong>of</strong>f interval. This phenomenon, referred to as deafness, could<br />

therefore cause false link failures (C believes that the link to B has failed even<br />

if it has not) <strong>and</strong> unfairness in channel access.<br />

Finally, due to the higher gain <strong>of</strong> directional antennas, the shape <strong>of</strong> the regions<br />

where transmissions are blocked (referred to as silenced regions in [6]) are<br />

different for omni-directional <strong>and</strong> directional communications. When both are<br />

used, the silenced regions vary depending upon the traffic <strong>and</strong> the network topology.<br />

The authors <strong>of</strong> [6] do not examine this in detail in the paper. Quantifying<br />

the trade-<strong>of</strong>fs while using hybrid directional/omni-directional communications<br />

has still not been explored in detail.<br />

7.3.6 The Multi-hop RTS MAC Protocol (MMAC)<br />

Roy Choudhury et al attempt to to exploit the increased directional range via<br />

the Multi-hop RTS MAC protocol (MMAC) in [6]. The basic problems with<br />

hidden terminals <strong>and</strong> deafness still exist with the MMAC protocol. However,<br />

the authors claim that the benefits due to the exploitation <strong>of</strong> the increased range<br />

somewhat compensates for the other negative effects. To recap, if both the<br />

sender <strong>and</strong> the receiver are beamforming (i.e, both directional transmissions <strong>and</strong><br />

directional receptions are invoked) the antenna gain can be potentially much<br />

higher than in the case where they use directional transmissions but omnidirectional<br />

receptions or vice versa. In Figure 7.6 if all the nodes were listening<br />

omni-directionally, node A would be able to communicate (with a directional<br />

transmission) with only nodes D <strong>and</strong> B. However, if node E were to be receiving<br />

directionally, node A could communicate with node E.<br />

The basic idea in MMAC is to route an RTS message via multiple hops to the<br />

intended recipient asking the recipient to beamform in the direction <strong>of</strong> the originator<br />

<strong>of</strong> the RTS message. The neighbors <strong>of</strong> a node are divided into two types:<br />

(a) The Direction-Omni (DO) Neighbors are those neighbors <strong>of</strong> a node that can<br />

receive transmissions from the node even if they are in the omni-directional

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!