CHAPTER 2: LITERATURE REVIEW

2.1 Introduction

This chapter is about current article review that is similar to the project that will
be developed. A proper plan on how this project can be conducted and the features
that have to be added in order to make this project reliable can be review from previous
article or journal. In addition, there are some findings from the Internet and books that
is contribute to this project. During the analysis at the beginning of the project, the
related software in this project is determined and the components or devices used in
this project is decided. Futhermore, the function and the concept are easily to
understand.

2.2 Overview of VANET

A Vehicular Ad-Hoc Network or VANET is a sub form of Mobile Ad-Hoc Network

or MANET that provides communication between vehicles and between vehicles and
road-side base stations with an aim of providing efficient and safe transportation. A
vehicle in VANET is an intelligent mobile node capable of communicating with its
neighbours and other vehicles in the network. VANET introduces more challenges
aspects as compare to MANET because of high mobility of nodes and fast topology
changes in VANET. Various routing protocols have been designed and presented by
researchers after considering the major challenges involved in VANETs This paper
provides a survey of routing protocols for VANET. It covers application areas,
challenges and security issues prevailing in VANETs.
2.2.1 Type of Routing Protocol for VANET

There are several traditional wireline networks and some ideas of them
are used in ad- hoc networks. Some of the traditional approaches:

1. Distance Vector: In this each node broadcast the information to its

neighbors instead of broadcasting it to all to monitor the cost of
outgoing links and to keep the estimation of shortest distance to
every node in the network. This information can then be used to
recalculate routing table using shortest path algorithm.
2. Link State: Every node maintains cost per each link of the entire
topology. Each node periodically floods the link costs of outgoing
links to all the other nodes in the network. Nodes update their records
and apply shortest path algorithm to choose the next hop.
3. Source Routing: Packets travel along the complete path pre-
decided at the source.
4. Flooding: Source distributes information among neighbors who
again send this info to their neighbors and so on. Using sequence
numbers for packets, a node is able to send packet only once.
2.3 Overview of Ad-hoc on-Demand Distance Vector (AODV)

The Ad-hoc On-Demand Distance Vector (AODV) routing protocol is designed

for use in ad-hoc mobile networks and the most commonly used topology-based
routing protocol for VANET. During the route discovery process AODV broadcasts
route request message (RREQ). It creates many unused routes between a source and
a destination node. AODV does not interfere if the routes are valid between the source
and the destination. AODV uses Route Requests (RREQs), Route Replies (RREPs),
Route Errors (RERRs) messages to find and establish the connection between source
and the destination. The greater the sequence number, the fresher is the route.

In Ad-Hoc On-Demand Distance Vector (AODV), routing tables are maintained to

avoid those entries of nodes that do not exist in the route from source to destination.
In AODV managing routing table information handled with the destination sequence
numbers. When nodes in the network detects that a route is not valid anymore for
communication it deletes all the related entries from the routing table for those invalid
routes. And sends the RREP to current active neighboring nodes that route is not valid
anymore for communication. AODV maintains only the loop free routes.

2.4 Overview of Vehicular Communication

2.4.1 Vehicle to Vehicle

Vehicle-to-Vehicle or V2V, is an ad-hoc network of vehicles, not involving

any infrastructure, so vehicles can communicate directly. In this communication
vehicles can even track other far-off vehicles. Vehicles have a DSRC trans
receiver placed on board through which they will disseminate the data and also
track other vehicles. In this manner vehicles could share and receive
information among them. Thus, if there is a collision ahead on the road and the
driver is not able to see the car ahead could transmit the information and the
driver behind it can know about the situation and can take necessary steps. The
V2V systems would be smart enough to handle the request themselves if the
driver does not respond to the warnings. The main purpose is to provide safety
to drive passengers and drivers.
2.4.2 Vehicle to Infrastructure

Vehicle-to-Infrastructure or V2I is a communication between vehicles

(i.e. nodes) and Road Infrastructure. So for this kind of communication
integrated communication system under the roads called Vehicle Infrastructure
Integration (VII) is required. It is an initiative fostering research for a series of
technologies linking road vehicles to their surroundings. This technology draws
on several disciplines, including computer science, electrical engineering,
automotive engineering and almost every other discipline. VII is specifically for
road transport, although similar technologies are under development are in
place for other modes of transport. For example, in Planes, ground-based
beacons are used for automated guidance, that allows the autopilot to fly the
plane without human intervention. In highway engineering, enhancing the
safety of a roadway improves the overall efficiency. VII targets improvements
in both safety and efficiency. VII is that branch of engineering that deals with
the study and implementation of a series of techniques to achieve
communication among vehicles and infrastructure bases in order to improve
road safety.

2.5 Existing Project Review

The existing application and project are the research subject and be a guideline
to this project. There are selected project that had been choose because of their
features and technologies used are suit with the development of this system. In this
section, there are explanations on all the features provide on each application. All the
information be a guideline and improve the features in this project.
2.5.1 VANET Connectivity Analysis

In this paper, the researchers provide a thorough analysis of the

connectivity of such networks by leveraging on well-known results of
percolation theory. By means of simulations, they study the influence of a
number of parameters, including vehicle density, proportion of equipped
vehicles, and radio communication range. They also study the influence of
traffic lights and roadside units. Their results provide insights on the behaviour
of connectivity. They believe this paper to be a valuable framework to assess
the feasibility and performance of future applications relying on vehicular
connectivity in urban scenarios. They provide a framework for the study of
vehicular connectivity in urban scenarios, and they show the use of percolation
theory for that purpose. They provide an extensive set of simulations that reveal
the impact of main vehicle and transportation parameters and factors, such as
vehicle density, traffic light, “background” vehicle traffic (in the case of low
market penetration rate for vehicular communications), and RSUs that can
facilitate vehicle connectivity. These investigations result in a range of
interesting findings, among which they summarize there the basic ones.

2.5.2 Vehicular Ad hoc Network (VANETs): A Review (2015)

For this paper, the researchers mentioned the entities that related to
VANET and also, they highlight the characteristics of VANET communication.
Besides, they also provide the components that is needed of VANET which is
divided into three different parts which is the vehicle itself, infrastructure and
communication channel. Along with these components of VANET, there also
will be various types of communication technique are used in VANET such as
Vehicle to Vehicle (V2V), Vehicle to Infrastructure (V2I), and Cluster to Cluster
(C2C).

The researchers also differentiate a few routing protocols for VANET.

Various protocols have been proposed by researchers so far that are based on
some category. Given below is the category wise analysis of protocols already
proposed for VANET.
 Table 2.1: Comparison of Routing Protocols for VANET Connectivity

Besides, the researchers also had listed a few types of application of

VANET especially in commercial applications which is for use in safety
application like traffic signal warnings, traffic monitoring and even
entertainment.
2.5.3 Analysis of VANET Geographic Routing Protocols on Real City Map (2017)
In this paper, two geographic routing protocols Anchor based Street and
Traffic Aware Routing (A-STAR) and Greedy Perimeter Stateless Routing
(GPSR) protocols are evaluated on real city map. Simulation of VANETs on real
map scenarios provide accurate results and also useful to design and deploy
VANETs in real world. Real world mobility model is important because it reflects
real-world performance of protocols considered. Analysis of performance is
carried in terms of throughput, packet delivery ratio, packet loss and average
delay. Simulation of protocols is carried by varying density of nodes. A-STAR
showed better performance on real city map over GPSR because A-STAR
adopted Street awareness method of routing whereas GPSR works on Greedy
forwarding and Routing around the perimeter methods.

2.5.4 Performance Analysis of a Hierarchical Structured VANET (2013)

In this paper, the researchers extend the technique of integrating Mobile

IP with a MANET into a VANET. In their considered VANET, a collection of
roadside gateways is deployed with each roadside gateway clusters a number
of vehicles nearby to form a small-scale local VANET. They apply DSDV routing
protocol with the Mobile IP to support communications for intra and inter local
VANETs. We study the feasibility of this architecture and evaluate its
transmission delay and delivery ratio. We further investigate the influence of
key network configuration parameters including network density, node mobility,
and number of gateways on performance measures.
2.5.5 Analysis of VANET Technologies (2017)

The researchers highlight that the Rapid Development in wireless

communication technologies and Vehicles have increased the growth of
Intelligent Transport System (ITS) which solves various vehicular transportation
problems like traffic congestion, shortest routing, accident etc. Vehicular Ad-
Hoc Network (VANET), is an integral part of ITS in which moving vehicles are
connected and communicate through wireless technology. Wireless
communication technologies play a major role in providing Vehicle-to-Vehicle
(V2V) and Vehicle-to Infrastructure (V2I) communication in VANET. This paper
surveys some of the key vehicular wireless access technology standards which
serve as a base for supporting both safety and non-safety applications and their
comparisons.
2.6 Critical Analysis

The table 2.2 is a review of the differences in the literature review

Table 2.2: Critical Analysis

Title VANET Vehicular Ad Analysis of Performance Analysis of Real Time

Connectivity Hoc VANET Analysis of a VANET Traffic Alert
Analysis Networks Geographic Hierarchical Technologies Using VANET
(VANETs): A Routing Structured
Kafsi, M., Review Protocols on VANET Reshma, S.,
Papadimitrat Real City & Prakash,
os, P., Chadha, D. Map Computing, C. (2017)
Dousse, O., (2015) S., Zhu, W.,
Alpcan, T., & Kaur, H. Zhang, Q., &
Hubaux, J. (2017) Fong, A. C.
(n.d.). M. (2013)

Routing Mathematical Various, as Traffic Aware Destination- Short, Ad-hoc On-

Protocol calculation shown in Routing (A- Sequence medium and Demand
Involved Table 2.1 STAR), Distance- long-range Distance
Greedy Vector protocol Vector
Perimeter (DSDV) (AODV)
Stateless
Routing
(GPSR)

Tools SUMO - SUMO, NS-2 Mathematical - SUMO, NS-2

calculation
 CHAPTER 3: RESEARCH METHODOLOGY

3.1 Introduction

This section will discuss the methodology adopted in this project. There are
numbers of methodologies can be adopted in the development of this project. The
methodologies that have been produce will be used in helping to develop a good
project and it will become much easier to implement. It will also help to determine
which method is suitable and easy to implement with the project that are intending to
be develop. A Waterfall Model methodology will be selected to be a guide throughout
this project progress. However, to ensure all tasks are defined and done accordingly,
the Work Breakdown Structure (WBS) is developed. WBS is a key project deliverable
that organizes the work into manageable sections. It visually defines the scope into
manageable portions that a project team can understand, as each level of the WBS
provides further definition and details.

Furthermore, the requirement of hardware and software will be listed for this
ongoing project. The listed hardware and software that are required will then be list in
the budget and costing. The hardware and software will be listed in details such as its
model, price, and quantity.
3.2 Research Method

Waterfall Model is a sequential design process that are used in software

development processes. It is very simple to understand and use. In a waterfall model,
each phase must be completed fully before the next phase can begin. This type of
model is basically used for the project which is small and there are no uncertain
requirements. At the end of each phase, a review takes place to determine if the
project is on the right path and whether or not to continue or discard the project. In this
model the testing starts only after the development is complete. Moreover, in waterfall
model phases does not have any overlap.

Define problem statement, objectives, project scope & project outcome

Initiation

Research & Research previous related project & analyse them by comparing their approach
Analysis

Planning Determine what software and hardware should be used for the project

Design the project’s network topology. Identify Methodology

Design Model to be used & finalize the budget and costing

Implement
If problem occurred, fix it again

Building the network architecture

and topology into simulator
Testing

The completed project is tested

Documentation

Collect the data and analyse them

Maintainence

Monitor and solve if any error(s) detected

Figure 3.1: The Waterfall Model

3.2.1 Initiation

The first place is initiation. This phase is deciding the title and brainstorm
about the project. Also, a few things are identified such as:

i. Objective
ii. Problem statement
iii. Project scope
iv. Project expected outcome
v. Limitation of project

3.2.2 Research and Analysis

The second phase are research and analysis. In this phase, research
about previous project is important for this project. Through research, the
student have discover what software were involved for this research such as
Simulation of Urban Mobility (SUMO) and Network Simulator (NS-2) which used
to simulate traffic across designed road map and trace the packets generated
along the simulation respectively.

3.2.3 Planning

In planning phase, the Work Breakdown Structure (WBS) is created to

define the total scope of the project. The timeline of the project is determined in
this phase. Furthermore, embedded software and hardware are decided based
on the research that already made before.

3.2.4 Implement

In implementation phase, all the hardware and software will be installed.

After the complete install, the simulation software will be used to simulate the
traffic as well as packet tracing using SUMO and NS-2 respectively. In order to
complete the project, every packet generated across the simulation will be
recorded for analysis purpose.
3.2.5 Testing
In this phase, the student need to have enough data to do analysis and
final report when there is no error found during the implementation. If any error
occurs, the process will need to revert back to design and check the
configuration whether it is correct or not. The testing will be done when the
simulation is successful. The result will always update every time doing the
testing.

3.2.6 Documentation

In this phase, documentation was done after testing phase has

completed. Documentation will update every time when there is changes in the
project. Every result that displayed will insert into documentation as a reference.

3.2.7 Maintenance

The last phase of the project is maintenance. In this phase, we would

need to monitor and solve any error(s) occurred. Issues may vary such as
wrong configuration, wrong placement of connection nodes and so on.
3.3 List of Resources

The project requires the following hardware and software. Table 3.1 shows the
hardware and Table 3.2 shows the software requirement.

Table 3.1: Hardware Requirement

Type of Requirement Item
Hardware Requirement • Laptop

Table 3.2: Software Requirement

Type of Requirement Item
Software Requirement • SUMO
• NS-2

3.4 Budget and Costing