18.11.2014 Views

Download - ijcer

Download - ijcer

Download - ijcer

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.

A comparative study of Broadcasting Protocols in VANET<br />

Table II: Data Forwarding Table<br />

In ordered to forward the data packet, a vehicle selects the next hop based on the direction if the<br />

location of destination is known. Table II represents data forwarding table maintained by every vehicle. Before<br />

forwarding any data packet the parameters of data forwarding table associated with the data packet are stored in<br />

the table. The vehicle searches for necessary information in data forwarding table to select the next hop<br />

whenever a data packet is received [3].<br />

III. STREETCAST PROTOCOL<br />

This protocol comprises of three components: relay-node selection, MRTS handshaking, and adaptive<br />

beacon control. It uses two units such as Roadside Unit (RSU) and OnBoard Units (OBUs). RSU can pick up<br />

relay nodes from its one-hop neighbors and disseminate packets over specified road segments. The selected<br />

OBRs upon receiving messages disseminate packets in their forward direction. The selected OBUs will reply<br />

ACKs to ensure reliability [2].<br />

A. Selection of Relay Nodes<br />

In order to reduce redundancy, we apply the Multi-Point Relay (MPR) broadcast strategy to reduce the<br />

number of relay nodes. Every OBU and RSU maintains the neighbor table. Each node in VANETs periodically<br />

broadcasts a “hello” beacon, which includes the node’s Dislocation and timestamp. When a node receives a<br />

“hello” beacon, it checks the digital street map and updates the neighbor information to its neighbor list. A<br />

neighbor is deleted from the table if no beacons are received from it for a period of time. Then the node with the<br />

optimal distance is picked from each neighbor list as a relay node.<br />

B. Multicast Request to Send<br />

We use MRTS to protect from collision. With MRTS mechanism, senders can send packets to multiple<br />

receivers simultaneously without worrying about collision and hidden-terminal problems. A sender transmits an<br />

MRTS and waits for CTSs from receiver. Nodes receiving MRTS frame set their NAVs (Network Allocation<br />

Vector) if they are not the relay nodes. Only relay nodes reply CTSs to the source following the order specified<br />

in the MRTS frame. Fig 2 illustrates the MRTS frame format [2].<br />

2 2 6 6 6 6 6 6<br />

FC Duration Src Ra1 Ra2 Ra3 Ra4 FCS<br />

FC: Frame Control<br />

Duration: NAV Duration<br />

Src: Source Address<br />

Ra1, Ra2, Ra3, Ra4: Receiver Address<br />

FCS: Frame Check Sequence<br />

Fig 2. MRTS Frame Format<br />

If transmission may fail due to loss of CTSs or ACKs. According to the number of received ACKs, a<br />

source can decide whether the transmission is successful or not, and re-initiate the MRTS procedure. If no CTS<br />

are received, then the source will directly re-initiate the MRTS procedure.<br />

C. Adaptive Beacon Control<br />

In urban areas, there could be thousands of vehicles moving across intersections in short period of time.<br />

If each vehicle keeps sending beacons, it will cause many collisions and failures. So, this protocol uses a beacon<br />

control mechanism to adjust beacon generation rate. The main function of beacons in this approach is to find the<br />

farthest neighbor in each direction for greedy forwarding. It is not necessary to let all nodes send beacons. There<br />

should be a proper number of nodes sending beacons.<br />

IV. ABBP PROTOCOL<br />

It is an adaptive broadcast protocol that is suitable for a wide range of mobility conditions. The main problem that a<br />

broadcast protocol must face is its adaptability to the very different vehicular arrangements in real scenarios. It should<br />

achieve high coverage of the network at the expense of as few transmissions as possible, regardless on whether the network<br />

is extremely dense or highly disconnected[1].<br />

ABBP is localized. Vehicles are assumed to be equipped with Global Positioning System (GPS) receivers. Periodic<br />

beacon messages are exchanged to update the vehicles’ local topology knowledge. The position of the sender is included<br />

within the beacons, which suffices to calculate a CDS (Connected Dominating Set) backbone after each beacon message<br />

round. The source node transmits the message. Upon receiving the message for the first time, each vehicle initializes two<br />

lists: list R containing all nodes believed to have received the message, and list N containing those neighbors in need of the<br />

www.<strong>ijcer</strong>online.com ||May ||2013|| Page 44

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

Saved successfully!

Ooh no, something went wrong!