Introducing routing guidance name in content-centric networking

Yao Hu, Shigeki Goto

    Research output: Contribution to journalArticle

    Abstract

    This paper proposes a name-based routing mechanism called Routing Guidance Name (RGN) that offers new routing management functionalities within the basic characteristics of CCN. The proposed mechanism names each CCN router. Each router becomes a Data Provider for its name. When a CCN Interest specifies a routerès name, it is forwarded to the target router according to the standard mechanism of CCN. Upon receiving an Interest, each router reacts to it according to RGN. This paper introduces a new type of node called a Scheduler which calculates the best routes based on link state information collected from routers. The scheduler performs its functions based on RGN. This paper discusses how the proposed system builds CCN FIB (Forwarding Information Base) in routers. The results of experiments reveal that RGN is more efficient than the standard CCN scheme. It is also shown that the proposal provides mobility support with short delay time. We explain a practical mobile scenario to illustrate the advantages of the proposal.

    Original languageEnglish
    Pages (from-to)2596-2605
    Number of pages10
    JournalIEICE Transactions on Communications
    VolumeE97B
    Issue number12
    DOIs
    Publication statusPublished - 2014 Dec 1

    Fingerprint

    Routers
    Time delay
    Experiments

    Keywords

    • CCN
    • FIB
    • ICN
    • Routing guidance name
    • Scheduler

    ASJC Scopus subject areas

    • Electrical and Electronic Engineering
    • Computer Networks and Communications
    • Software

    Cite this

    Introducing routing guidance name in content-centric networking. / Hu, Yao; Goto, Shigeki.

    In: IEICE Transactions on Communications, Vol. E97B, No. 12, 01.12.2014, p. 2596-2605.

    Research output: Contribution to journalArticle

    Hu, Yao ; Goto, Shigeki. / Introducing routing guidance name in content-centric networking. In: IEICE Transactions on Communications. 2014 ; Vol. E97B, No. 12. pp. 2596-2605.
    @article{7aee3788735047b691fc77b610f2c2e9,
    title = "Introducing routing guidance name in content-centric networking",
    abstract = "This paper proposes a name-based routing mechanism called Routing Guidance Name (RGN) that offers new routing management functionalities within the basic characteristics of CCN. The proposed mechanism names each CCN router. Each router becomes a Data Provider for its name. When a CCN Interest specifies a router{\`e}s name, it is forwarded to the target router according to the standard mechanism of CCN. Upon receiving an Interest, each router reacts to it according to RGN. This paper introduces a new type of node called a Scheduler which calculates the best routes based on link state information collected from routers. The scheduler performs its functions based on RGN. This paper discusses how the proposed system builds CCN FIB (Forwarding Information Base) in routers. The results of experiments reveal that RGN is more efficient than the standard CCN scheme. It is also shown that the proposal provides mobility support with short delay time. We explain a practical mobile scenario to illustrate the advantages of the proposal.",
    keywords = "CCN, FIB, ICN, Routing guidance name, Scheduler",
    author = "Yao Hu and Shigeki Goto",
    year = "2014",
    month = "12",
    day = "1",
    doi = "10.1587/transcom.E97.B.2596",
    language = "English",
    volume = "E97B",
    pages = "2596--2605",
    journal = "IEICE Transactions on Communications",
    issn = "0916-8516",
    publisher = "Maruzen Co., Ltd/Maruzen Kabushikikaisha",
    number = "12",

    }

    TY - JOUR

    T1 - Introducing routing guidance name in content-centric networking

    AU - Hu, Yao

    AU - Goto, Shigeki

    PY - 2014/12/1

    Y1 - 2014/12/1

    N2 - This paper proposes a name-based routing mechanism called Routing Guidance Name (RGN) that offers new routing management functionalities within the basic characteristics of CCN. The proposed mechanism names each CCN router. Each router becomes a Data Provider for its name. When a CCN Interest specifies a routerès name, it is forwarded to the target router according to the standard mechanism of CCN. Upon receiving an Interest, each router reacts to it according to RGN. This paper introduces a new type of node called a Scheduler which calculates the best routes based on link state information collected from routers. The scheduler performs its functions based on RGN. This paper discusses how the proposed system builds CCN FIB (Forwarding Information Base) in routers. The results of experiments reveal that RGN is more efficient than the standard CCN scheme. It is also shown that the proposal provides mobility support with short delay time. We explain a practical mobile scenario to illustrate the advantages of the proposal.

    AB - This paper proposes a name-based routing mechanism called Routing Guidance Name (RGN) that offers new routing management functionalities within the basic characteristics of CCN. The proposed mechanism names each CCN router. Each router becomes a Data Provider for its name. When a CCN Interest specifies a routerès name, it is forwarded to the target router according to the standard mechanism of CCN. Upon receiving an Interest, each router reacts to it according to RGN. This paper introduces a new type of node called a Scheduler which calculates the best routes based on link state information collected from routers. The scheduler performs its functions based on RGN. This paper discusses how the proposed system builds CCN FIB (Forwarding Information Base) in routers. The results of experiments reveal that RGN is more efficient than the standard CCN scheme. It is also shown that the proposal provides mobility support with short delay time. We explain a practical mobile scenario to illustrate the advantages of the proposal.

    KW - CCN

    KW - FIB

    KW - ICN

    KW - Routing guidance name

    KW - Scheduler

    UR - http://www.scopus.com/inward/record.url?scp=84924409459&partnerID=8YFLogxK

    UR - http://www.scopus.com/inward/citedby.url?scp=84924409459&partnerID=8YFLogxK

    U2 - 10.1587/transcom.E97.B.2596

    DO - 10.1587/transcom.E97.B.2596

    M3 - Article

    VL - E97B

    SP - 2596

    EP - 2605

    JO - IEICE Transactions on Communications

    JF - IEICE Transactions on Communications

    SN - 0916-8516

    IS - 12

    ER -