1. project name and team members:
Project: VANETs (Vehicular ad-hoc networks) and Road Technology
Team members: Georgia Ma, Eileen Eng, and Raghav Khurana
2. What's the problem? Why is it important?
The need for VANETs is growing due to the increasing number of smart vehicles on the road. Some of the major applications of VANETs include collision warning, security distance warning, driver assistance, dissemination of road information, mobile internet access, location awareness, and driverless vehicles. Improvement of these applications means less vehicular accidents and more convenience for current and future drivers.
As VANETs are considered as the subset of mobile ad-hoc networks (MANETs), it would be very expensive and difficult to install huge infrastructure on all roads and highways for inter-vehicle communication. The quick installation of ad hoc networks without involving any central authority or administration is another promising advantage of VANET.
Robust and effective security of these VANETs is also crucial as cyber attacks and breaches can have fatal consequences. Modern cars rely on hundreds of ECUs (Electronic Control Units), so integrating security measures into these subsystems can be challenging.
Current Challenges:
The high mobility of vehicles as network nodes
Reliable data transfer & low latency as the data being shared could be important for driver and passenger safety
Location based routing
Seamless switching
High Speed multicast data transfer
Maintaining QoS for envisioned applications
Security and privacy
Cost effectiveness/road infrastructure cost
3. What has been done? Why are they not sufficient? including any of your previous, other and ongoing projects too.
Modern VANETs have network protocol challenges due to the dynamic nature of V2I and V2V communications. Many existing VANETs solutions were initially developed by applying the principles of MANETs to the domain of vehicles. However, mobile devices, though mobile, do not move as fast or as far as vehicles do, which leads to many more unique issues, such as reliability and security, that VANETs technology faces. For example, cars travelling in the opposite direction at high speeds will only have short lived connections, so protocols must address these types of node characteristics.
4. What's your approach? Why can it do better or differently?
We are interested in the following areas in VANET’s implementation:
To address the issues of reliable data transfer & low latency in an environment with highly mobile vehicles:
Investigate V2I technologies, fast handoffs performance, and solutions to connection/network patchiness (like switching) to address the issues of reliable data transfer & low latency in an environment with highly mobile vehicles.
Investigate and compare the performance of different kinds of routing protocols for VANETs.
Comb through and compare various proposed methods to address the BER in VANET as accurate information delivery is critical to vehicle & passenger safety.
To address the reliability and application of smart road infrastructure:
Research the safety benefit of V2I communication with road infrastructure like stop signs, red lights etc.
To investigate security risks and solutions for smart vehicles and road infrastructure:
Explore existing solutions for concepts such as privacy, data integrity, data origin, authentication.
To look into the role of vehicle networks in achieving complete self driving cars and how the V2I and V2V communication is critical in achieving that goal:
Assess the costs, benefits, and drawbacks of implementing these types of architectures.
5. Expected deliverables and a rough biweekly time schedule
The deliverables for this project are:
Project outline: Feb 8
Log book (meetings and research findings): Throughout
Project update: Mar 8
Final presentation: Apr 5
Project report: Apr 12
6. Public website url; resources needed, references if any, etc
https://sites.google.com/view/vanetsandroadtechnology/home
7. Also post the proposal on the private brightspace -> discussion -> project thread
https://bright.uvic.ca/d2l/le/116343/discussions/threads/172910/View