Abstract
Task-oriented caching in vehicular edge computing (VEC) has become a hot topic recently, which brings in many opportunities for capability limited vehicles and makes VEC task offloading and service provision more cost-effective. Most works on caching assisted task offloading in VEC focused mainly on the reuse of computation results and neglected the characteristics pertaining to VEC. In effect, task-oriented caching in VEC is time-sensitive, requiring multiple-choice and multi-granularity. We need to address the issues on different computing and storage capabilities between vehicles and edge server with their diverse applications. Therefore, caching enabled task offloading in VEC aims for exploitation and enhancement of the functions in edge computing. To investigate in depth the benefits of caching enabled task offloading in VEC, we first provide an architectural overview on caching enabled vehicular edge computing (CVEC). Then, we strive to address the most concerned issues, that is, where, what, how and when to cache the tasks in CVEC. Specifically, three caching strategies are introduced to address what to cache in CVEC. In addition, caching strategies are evaluated with respect to response latency and energy consumption at edge servers. Simulation results reveal that caching enabled task offloading in CVEC can remarkably improve the performance of VEC. We also take a look at the opportunities and discuss the challenges in CVEC to shed light on future research directions on CVEC.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.