Papers › Connected Vehicle Application Development Platform (CVDeP) for Edge-centric...
Connected Vehicle Application Development Platform (CVDeP) for Edge-centric Cyber-Physical Systems
Mhafuzul Islam, Mizanur Rahman, Sakib Mahmud Khan, Mashrur Chowdhury, Lipika Deka
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Connected vehicle (CV) application developers need a development platform to build, test and debug CV applications, such as safety, mobility, and environmental applications, in an edge-centric Cyber-Physical Systems. Our study objective is to develop and evaluate a scalable and secure CV application development platform (CVDeP) that enables the CV application developers to build, test and debug CV applications in real-time. CVDeP ensures that the functional requirements of the CV applications meet the latency requirements imposed by corresponding CV applications. We conducted a case study to evaluate the efficacy of CVDeP using two CV applications (one safety and one mobility application) and validated them through a field evaluation at the Clemson University Connected and Autonomous Vehicle Testbed (CU-CAVT). The analysis outcome proves the efficacy of CVDeP, which satisfies the functional requirements (e.g., latency, throughput) of a CV application while maintaining scalability, and security of the platform and applications.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections