Abstract
Content centric networks offer better response time and resilience to failures by caching the content in the network routers. Owing to the limited capacity of caches and the quest for maximizing the utilization of available caches has lead to many interesting caching techniques. While on-path caching is a commonly adopted caching technique to reduce content access latency, it does not guarantee better cache hit ratio when considered across multiple receivers in the network. In this paper, we present eNCache which is a cooperative caching method that cooperates among the routers in the neighborhood to improve overall performance. It retains the simplicity of on-path caching and makes caching, routing (queries and replies) decisions by interacting with off-path routers in the neighborhood. We present the working of eNCache with algorithms for request handling and caching decisions at every router. We also formalize the interaction between a router and its neighbors by providing an extension to the Named Data Networking Interest packet structure. We evaluate and compare the performance of eNCache with other popular on-path caching strategies by performing simulations on standard RocketFuel Internet Service Provider (ISP) topologies using a discrete event simulator. We also compare the performance of a variant of enhanced NCache, i.e.,eNCache with hash based off-path caching methods. Our simulation results show that eNCache has reduced latency, better cache hit ratio and diversity.
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.