Ad-Hoc & Sensor Networks IV Year II Sem
Ad-Hoc & Sensor Networks IV Year II Sem
Ad-Hoc & Sensor Networks IV Year II Sem
IV year II sem
INFORMATION TECHNOLOGY
UNIT - II
ISSUES IN DESIGNING A MAC PROTOCOL FOR AD HOC
WIRELESS NETWORKS
The main issues need to be addressed while designing a MAC protocol for ad hoc wireless
networks:
Bandwidth efficiency is defined at the ratio of the bandwidth used for actual data
transmission to the total available bandwidth. The MAC protocol for ad-hoc networks
should maximize it.
Quality of service support is essential for time- critical applications. The MAC protocol
The protocol should provide QoS support for real- time traffic.
The access delay, which refers to the average delay experienced by any packet
The protocol should minimize the effects of hidden and exposed terminal
problems.
The protocol must be scalable to largenetworks.
The protocol should have mechanisms for adaptive data rate control.
• Cannot provide QoS guarantees to sessions since nodes are not guaranteed
regular access to the channel.
Contention Based Protocols (contd..)
• Random access protocols can be further divided into two types:
A node that wins the contention to the channel can make use of the entire bandwidth.
This enables several nodes to simultaneously transmit data, each using a separate
channel.
MACAW: A Media Access Protocol for Wireless LANs
Once the sender receives the CTS packet without any error, it starts
transmitting the data packet.
If a packet transmitted by a node is lost, the node uses the binary
exponential back-off (BEB) algorithm to back off a random interval of
time before retrying.
RTS
CTS CTS
A B C
CTS
A B C
MACA
• This eliminates contention and hence long contention periods after every
successful transmission, at the same time providing a reasonably quick
escalation in the back-off values when the contention is high.
MACAW (contd..)
• MACAW implements per flow fairness as opposed to the per node fairness in
MACA.
• This is done by maintaining multiple queues at every node, one each for each
data stream, and running the back-off algorithm independently for each queue.
• In addition to the RTS and CTS control packets used in MACA, MACAW uses
another new control packet called acknowledgment (ACK) packet.
• In MACAW, after successful reception of each data packet, the receiver node
transmits an ACK packet.
• If the sender does not receive the ACK packet, it reschedules the same data
packet for transmission.
• The back-off counter is incremented if the ACK packet is not received by the
sender.
MACAW (contd..)
• If the ACK packet got lost in transmission, the sender would retry by transmitting an RTS for
the same packet.
• But now the receiver, instead of sending back a CTS, sends an ACK for the packet received,
and the sender moves on to transmit the next data packet
MACAW (contd..)
Summary MACAW
The MACAW protocol has been designed based on four main observations.
1. Congestion at the receiver node solved by using the RTS-CTS-DS-DATA-ACK exchange
mechanism.
2. Instead of characterizing back-off by a single back-off parameter, separate back-off
parameters have been introduced for each flow.
3. Learning about congestion at various nodes must be a collective enterprise. Therefore, the
notion of copying back-off values from overheard packets has been introduced in MACA.
4. The synchronization information needs to be propagated to the concerned nodes at
appropriate times. This is done in MACAW through the DS and RRTS packets.
Floor Acquisition Multiple
Access Protocols
(FAMA)
FAMA
• The floor acquisition multiple access (FAMA) protocols are based on a
channel access discipline which consists of a carrier-sensing operation
and a collision-avoidance between sender and receiver.
• At any given point of time, the control of the channel is assigned to only
one node, and this node is guaranteed to transmit one or more data
packets to different destinations without suffering from packet collisions.
FAMA (contd..)
• Carrier-sensing by the sender, followed by the RTS-CTS control packet
exchange, enables the protocol to perform as efficiently as MACA in the
presence of hidden terminals.
• The first uses ALOHA protocol for transmitting RTS packets, while the
second variant uses non-persistent CSMA.
CONTENTION-BASED
PROTOCOLS WITH RESERVATION
MECHANISMS
CONTENTION-BASED PROTOCOLS WITH
RESERVATION
MECHANISMS
• Once the bandwidth is reserved, the node gets exclusive access to the
reserved bandwidth.
• The channel is divided into fixed- and equal-sized frames along the time
axis.
• Each mini-slot can be further divided into two control fields, RTS/BI and
CTS/BI(BI stands for busy indication), as shown in the figure.
D-PRMA (contd..)
• The remaining (m - 1) minislots are granted to the node that wins the
contention.
• Also, the same slot in each subsequent frame can be reserved for this winning
terminal until it completes its packet transmission session.
• If no node wins the first minislot, then the remaining minislots are
continuously used for contention, until a contending node wins any minislot.
D-PRMA (contd..)
• Within a reserved slot, communication between the source and receiver
nodes takes place by means of either time division duplexing (TDD) or
frequency division duplexing (FDD).
• First Rule : The voice nodes are allowed to start contending from minislot 1 with
probability p = 1; Data nodes can start contending only with probability p < 1.
For the remaining (m - 1) minislots, both the voice nodes and the data nodes are
allowed to contend with probability p < 1.
D-PRMA (contd..)
• Second Rule :
If the node winning the minislot contention is a voice node, is it permitted to
reserve the same slot in each subsequent frame until the end of the session.
If a data node wins the contention, then it is allowed to use only one slot, that is, the
current slot, and it has to make fresh reservations for each subsequent slot.
• Nodes that are located within the radio coverage of the receiver should not be
permitted to transmit simultaneously
D-PRMA (contd..)
• In D-PRMA, when a node wins the contention in minislot 1, other terminals
must be prevented from using any of the remaining (m - 1) minislots in the
same slot for contention (requirement 1).
• Nodes contend for and reserve time slots by means of a distributed reservation
and handshake mechanism.
1. The receiver(s) of a flow must inform the potential source nodes about the
reserved slot on which it is currently receiving packets. Similarly, the source
node must inform the potential destination node(s) about interferences in
the slot.
• The first four minislots are used for transmitting control packets and are called
control minislots (CMS1, CMS2, CMS3, and CMS4).
• The fifth and last minislot, called data minislot (DMS), is meant for data
transmission.
• The data minislot is much longer than the control minislots as the control
packets are much smaller in size compared to data packets.
CATA (contd..)
• DPS protocol piggy-backs the priority tag of a node's current and head-of-
line packets on the control and data packets.
• The downstream nodes in the path to the destination increase the relative
priority of a packet in order to compensate for the excessive delays incurred
by the packet at the upstream nodes.
Distributed Priority Scheduling (contd..)
• The RTS packet transmitted by a ready node carries the priority tag/priority
index for the current DATA packet to be transmitted.
• On receiving the RTS packet, the intended receiver node responds with a CTS
packet.
• The receiver node copies the priority tag from the received RTS packet and
piggybacks it along with the source node id, on the CTS packet.
Distributed Priority Scheduling (contd..)
• Neighbor nodes receiving the RTS or CTS packets (including the hidden
nodes) retrieve the piggy-backed priority tag information and make a
corresponding entry for the packet to be transmitted, in their scheduling
tables (STs).
• The entries in the ST are ordered according to their priority tag values.
Distributed Priority Scheduling (contd..)
• When the source node transmits a DATA packet, its head-of-line packet information
(consisting of the destination and source ids along with the priority tag) is piggy-backed on
the DATA packet (head-of-line packet of a node refers to the packet to be transmitted next by
the node).
• This information is copied by the receiver onto the ACK packet it sends in response to the
received DATA packet.
• Neighbor nodes receiving the DATA or ACK packets retrieve the piggy-backed information
and update their STs accordingly.
• When a node hears an ACK packet, it removes from its ST any entry made earlier for the
corresponding DATA packet.
Figure. Piggy-backing and scheduling table update mechanism in DPS.