A unified data structure of name lookup for NDN data plane

Miaomiao Liu, Tian Song*, Yating Yang, Beichuan Zhang

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

7 Citations (Scopus)

Abstract

NDN data plane relays name-based packets by maintaining three tables: Content Store, Pending Interest Table and Forwarding Information Base. The three tables require similar but different schemes to be matched and updated in a nearly per-packet fashion, thus individual data structure is required for each table. In this work, we propose a unified data structure of name lookup for all three tables, namely CTrie, aiming at reducing the computational cost from three pipelined lookup rounds down to one unified round. CTrie extends the original Patricia trie to a combinational trie structure built from both component-based and byte-based hierarchical names. We compared CTrie with other approaches in speed and memory. The results show that CTrie runs 3.2 times faster and consumes about 38% memory than the current ones in terms of the whole data plane. CTrie fits for all application scenarios of NDN and especially well for IoT like lightweight-deployed scenarios.

Original languageEnglish
Title of host publicationICN 2017 - Proceedings of the 4th ACM Conference on Information Centric Networking
PublisherAssociation for Computing Machinery, Inc
Pages188-189
Number of pages2
ISBN (Electronic)9781450351225
DOIs
Publication statusPublished - 26 Sept 2017
Event4th ACM Conference on Information-Centric Networking, ICN 2017 - Berlin, Germany
Duration: 26 Sept 201728 Sept 2017

Publication series

NameICN 2017 - Proceedings of the 4th ACM Conference on Information Centric Networking

Conference

Conference4th ACM Conference on Information-Centric Networking, ICN 2017
Country/TerritoryGermany
CityBerlin
Period26/09/1728/09/17

Fingerprint

Dive into the research topics of 'A unified data structure of name lookup for NDN data plane'. Together they form a unique fingerprint.

Cite this