Cloud Computing in VANETs: Architecture, Taxonomy, and Challenges

Ahmed Aliyu, Hanan Abdullah, Omprakash Kaiwartya, Yue Cao, Mohammed Usman, Sushil Kumar, Daya Lobiyal, S. R. Ram

Research output: Contribution to journalArticlepeer-review

53 Citations (Scopus)
11 Downloads (Pure)

Abstract

Cloud Computing in VANETs (CC-V) has been investigated into two major themes of research including Vehicular Cloud Computing (VCC) and Vehicle using Cloud (VuC). VCC is the realization of autonomous cloud among vehicles to share their abundant resources. VuC is the efficient usage of conventional cloud by on-road vehicles via a reliable Internet connection. Recently, number of advancements have been made to address the issues and challenges in VCC and VuC. This paper qualitatively reviews CC-V with the emphasis on layered architecture, network component, taxonomy, and future challenges. Specifically, a four-layered architecture for CC-V is proposed including perception, co-ordination, artificial intelligence and smart application layers. Three network component of CC-V namely, vehicle, connection and computation are explored with their cooperative roles. A taxonomy for CC-V is presented considering major themes of research in the area including design of architecture, data dissemination, security, and applications. Related literature on each theme are critically investigated with comparative assessment of recent advances. Finally, some open research challenges are identified as future issues. The challenges are the outcome of the critical and qualitative assessment of literature on CC-V.
Original languageEnglish
Pages (from-to)523-547
JournalIETE Technical Review
Volume35
Issue number5
Early online date23 Aug 2017
DOIs
Publication statusPublished - 2018

Keywords

  • Cloud Computing
  • Vehicular Ad-hoc Networks
  • Architecture
  • Taxonomy
  • Vehicular Cloud
  • Vehicle using Cloud

Fingerprint

Dive into the research topics of 'Cloud Computing in VANETs: Architecture, Taxonomy, and Challenges'. Together they form a unique fingerprint.

Cite this