Cooperative Resource Allocation and Scheduling for 5G eV2X Services

Nestor Bonjorn, Fotios Foukalas*, Ferran Canellas Cruz, Paul Pop

*Corresponding author for this work

Research output: Contribution to journalJournal articleResearchpeer-review

1137 Downloads (Pure)


In this paper, a cooperative solution for vehicle-to-everything (V2X) communications is proposed and presented, which can guarantee reliability and latency requirements for 5G enhanced V2X (eV2X) services. Cooperation is useful for both in-coverage and out-of-coverage vehicular communications scenarios. The proposed solution relies on the sidelink (SL) device-to-device (D2D) communications for V2X communications. In this work, we first provide a performance evaluation of SL D2D V2X communications in terms of resource allocation and scheduling. The resource allocation is known as mode 3 and 4 SL D2D communications and the scheduling is using a semi-persistent scheduling (SPS) approach. Simulation results are obtained in order to identify and highlight the reliability trade-offs considering different payload sizes and SPS parameters. In the sequel, a cooperative solution that decreases transmission collision probability is devised and presented, which is able to significantly improve the reliability of future 5G enhanced vehicle-to-everything (eV2X) communications. Different application scenarios are simulated to obtain results that can guarantee the latency also requirements per 5G eV2X use case as specified in 3GPP Rel.16 towards ultra reliable and low latency communications (URLLC).
Original languageEnglish
JournalIEEE Access
Pages (from-to)58212-58220
Number of pages10
Publication statusPublished - 2019


  • Sidelink device-to-devic
  • 5G enhanced V2X (eV2X) services
  • V2V communications
  • Resource allocation
  • Scheduling
  • Cooperative ultra reliable and low latency communications

Fingerprint Dive into the research topics of 'Cooperative Resource Allocation and Scheduling for 5G eV2X Services'. Together they form a unique fingerprint.

Cite this