Revving up VNDN: Efficient caching and forwarding by expanding content popularity perspective and mobility

Abstract

Network caching in Vehicular Named Data Networks (VNDN) has the potential to support latency-sensitive services, though given the massive amount of content generated by vehicles in a VNDN, it is challenging to cache sufficiently diverse content across the network for an acceptable hit ratio. Redundant interest transmissions can negatively impact network overhead, wasting network resources when retrieving duplicate content. In the literature, a caching decision is typically based on ongoing popularity, computed from a vehicle’s experience with requests received for individual content. This leads to each vehicle caching the most popular content. Instead, we group content into different categories. All content in a popular category of vehicular service (e.g., tourist information category) is cached equally, not just the most popular content within a category (e.g., information relating to a particular museum). This increases content diversity in the cache. Further, we posit that a service requester from a particular location at a specific time would be interested in the same category of service/application as other users from the same location/time. Leveraging this observation, we consider both forthcoming spatial/temporal and ongoing popularity of vehicular services when ranking their popularity. We also address network overhead with a mobility model that captures the communication duration between vehicles. This parameter, which has been overlooked in existing literature, enables the selection of an appropriate forwarder for content requests. We use ndnSIM VNDN with a mobility trace of Luxembourg city for simulation. Compared to an approach where individual content-wise popularity is computed, our scheme shows more than 100% improvement in cache hit ratio where the number of contents in the network varied between 104 and 105. Simultaneously, we also enhanced the diversity of content caching, while considering the trade-off between cache hit ratio and network overhead.