A Safety Resource Allocation Mechanism against Connection Fault for Vehicular Cloud Computing

Tianpeng Ye, Zhou Su*, Jun Wu, Longhua Guo, Jianhua Li, Gaolei Li

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

11 Citations (Scopus)


The Intelligent Transportation System (ITS) becomes an important component of the smart city toward safer roads, better traffic control, and on-demand service by utilizing and processing the information collected from sensors of vehicles and road side infrastructure. In ITS, Vehicular Cloud Computing (VCC) is a novel technology balancing the requirement of complex services and the limited capability of on-board computers. However, the behaviors of the vehicles in VCC are dynamic, random, and complex. Thus, one of the key safety issues is the frequent disconnections between the vehicle and the Vehicular Cloud (VC) when this vehicle is computing for a service. More important, the connection fault will disturb seriously the normal services of VCC and impact the safety works of the transportation. In this paper, a safety resource allocation mechanism is proposed against connection fault in VCC by using a modified workflow with prediction capability. We firstly propose the probability model for the vehicle movement which satisfies the high dynamics and real-time requirements of VCC. And then we propose a Prediction-based Reliability Maximization Algorithm (PRMA) to realize the safety resource allocation for VCC. The evaluation shows that our mechanism can improve the reliability and guarantee the real-time performance of the VCC.

Original languageEnglish
Article number2747808
JournalMobile Information Systems
Publication statusPublished - 2016
Externally publishedYes

ASJC Scopus subject areas

  • Computer Science Applications
  • Computer Networks and Communications


Dive into the research topics of 'A Safety Resource Allocation Mechanism against Connection Fault for Vehicular Cloud Computing'. Together they form a unique fingerprint.

Cite this