Improving the performance by message broadcasting in VANETS Online publication date: Thu, 18-May-2017
by M. Sakthi Ganesh; P. Venkata Krishna
International Journal of High Performance Computing and Networking (IJHPCN), Vol. 10, No. 3, 2017
Abstract: In vehicular adhoc networks, messages are broadcast by active mobile nodes spontaneously to all the neighbourhood nodes within the connectivity range. These important messages may have severe delay and are time sensitive. The main aim of this work is to broadcast the safety message, to avoid the packet collision or to reduce the packet loss so that the efficiency of the network is improved and these can be analysed using different protocols in vehicular adhoc network. In typical carrier sense multiple accesses the users that content with channel access do not seem to be suitable for this application. Protocol sequence is the method we are following to broadcast the safety message. 0s and 1s are the protocol sequences used. When each user in the network reads the 0s and 1s they transmit the packet in the time slot. It does not require time synchronisation between the mobile nodes. We compare the delay performance with dedicated short range communication protocol, ALOHA type random access scheme, and zone routing protocol. By arranging the data packets a hard assurance of delay might be achieved. The delay in the network reduces in zone routing protocol.
Online publication date: Thu, 18-May-2017
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of High Performance Computing and Networking (IJHPCN):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email firstname.lastname@example.org