An Incrementally Deployable IP-Compatible-Information-Centric Networking Hierarchical Cache System

Abstract

The major advantage of information-centric networking (ICN) lies in in-network caching. Ubiquitous cache nodes reduce the user’s download latency of content and the drain of network bandwidth, which enables efficient content distribution. Due to the huge cost of updating an entire network infrastructure, it is realistic for ICN to be integrated into an IP network, which poses new challenges to design a cache system and corresponding content router. In this paper, we firstly observed that the behavior pattern of data requests based on a name resolution system (NRS) makes an ICN cache system implicitly form a hierarchical and nested structure. We propose a complete design and an analytical model to characterize an uncooperative hierarchical ICN caching system compatible with IP. Secondly, to facilitate the incremental deployment of an ICN cache system in an IP network, we designed and implemented a cache-supported router with multi-terabyte cache capabilities. Finally, the simulation and measurement results show the accuracy of proposed analytical model, the significant gains on hit ratio, and the access latency of the hierarchical ICN cache system compared with a flat cache system based on naming routing, as well as the high performance of the implemented ICN router.

The Yellow Active Queue Management Algorithm in ICN Routers Based on the Monitoring of Bandwidth Competition

“…With the increase of router cache capacity, cache hit rate and task concurrency will be improved greatly [11]. Therefore, the real-time bandwidth requirement of cache service traffic cannot be ignored and the conflict may occur at any time.…”

“…In the early research, the high cost Static Random-Access Memory (SRAM) limited the cache capacity of router to multi hundreds of megabytes (MB) [8]. Nowadays, researchers have carried out extensive studies on how to design content router with cache capacity of multi terabytes (TB) [9][10][11]. For example, in our previous study, in order to make the IP network evolve to ICN smoothly, we designed and implemented a router with huge cache capacity [11] through the latest storage performance development kit (SPDK) technology [12].…”

“…Once any packet is dropped in one node, the chunk that loss packet belongs to will be unable to cache in all the subsequent nodes on the transmission path with high probability, which reduces the utilization of router memory and link. Although the ICN transport protocol contains fast retransmission mechanism, in the heavy load network environment, the round-trip time (RTT) and the queuing delay in each router are enough to release the assembling space allocated from the router memory for this chunk in advance [11]. Many studies [14,15] believe that caching content as close to the network centric node with high betweenness as possible could achieve a large amount of benefit, such as high cache hit rate, lower traffic on link and cache eviction rate.…”

An Identifier and Locator Decoupled Multicast Approach (ILDM) Based on ICN

“…The ICN router [21] maintains both IP routing information and name forwarding information. Routers can forward ordinary IP packets based on the IP address and forward ICN packets based on the EID.…”

“…In routing-byname, the request is forwarded to an information provider based on the name alone, and then the provider sends the content to the requesting user along the reverse path of the request [20]. However, routing-by-name requires routers to store a large amount of routing states of information objects [21]. Lookup-by-name uses an infrastructure named the name resolution system (NRS) to map the names to locators (e.g., IP address) and then routes the request to one of the locators.…”