Design and implementation of the Node Identity Internetworking Architecture

Schütz, Simon; Abrahamsson, Henrik; Ahlgren, Bengt; Brunner, Marcus

doi:10.1016/j.comnet.2009.10.015

Cited by 9 publications

(11 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Node Identity Internetworking Architecture [17] provides an IS-based solution to separate identification with location by defining locator domains (LD), but does not explain the operation in ad-hoc networks and networks with disruptions. It is based on routing hints that are resolved at LDs and serve as source routing.…”

Section: Resultsmentioning

confidence: 99%

Naming for heterogeneous networks prone to episodic connectivity

Rais

Abdelmoula

Turletti

2011

2011 IEEE Wireless Communications and Networking Conference

View full text Add to dashboard Cite

Abstract-In this paper, we present a naming scheme for heterogeneous networks composed of infrastructure-based and infrastructure-less networks where nodes may be subject to intermittent connectivity. The proposed scheme aims at decoupling object identification from location and is designed to operate with status-quo Internet routing. We showcase the proposed naming scheme implemented on the ns-3 network simulator and demonstrate that nodes are able to receive messages in both infrastructure-based and infrastructure-less networks despite frequent disconnections and changing location identifiers (i.e., IP address), while visiting different networks.

show abstract

Section: Resultsmentioning

confidence: 99%

Naming for heterogeneous networks prone to episodic connectivity

Rais

Abdelmoula

Turletti

2011

2011 IEEE Wireless Communications and Networking Conference

View full text Add to dashboard Cite

show abstract

“…The Node ID Internetworking Architecture (NIIA) [170] organizes the network as a tree, and employs default routes to parent nodes to enable inter-domain routing. In addition, NIIA supports multiple registration of nodes in the tree (useful when there are multiple interfaces).…”

Section: Hierarchical Inter-domain Routing Architecture (Hidra)mentioning

confidence: 99%

“…Other proposals organize the network as a tree instead of implementing a hierarchy through administrative domains like HRA. The Node ID Internetworking Architecture (NIIA) [170] organizes the network as a tree. Routing inside domains uses locators and between domains it employs Node ID or default routes to parent nodes in the tree.…”

Section: Hierarchical Approachesmentioning

confidence: 99%

See 1 more Smart Citation

Multihoming: A Comprehensive Review

Sousa¹,

Pentikousis²,

Curado³

2013

Advances in Computers

View full text Add to dashboard Cite

“…ensuring that if a MN changes its point of attachment to the Internet, while in movement, no communication interruptions are perceived at the application level, and if such interruptions occur, they do not significantly degrade the Quality of Service (QoS) delivered at the proaches described in these proposals suggest a decoupling of the node identifier from its address (locator), e.g. GLI-Split [1], HIP [2,3], Hi3 [4], ILNP [5], LISP [6], MILSA [7], NIIA [8,9], RANGI [10]. These approaches usually comply with future Internet visions, requiring some radical changes in the network architecture.…”

Section: Introductionmentioning

confidence: 99%

A survey on handover management in mobility architectures

2016

View full text Add to dashboard Cite

This work presents a comprehensive and structured taxonomy of available techniques for managing the handover process in mobility architectures. Representative works from the existing literature have been divided into appropriate categories, based on their ability to support horizontal handovers, vertical handovers and multihoming. We describe approaches designed to work on the current Internet (i.e. IPv4-based networks), as well as those that have been devised for the "future" Internet (e.g. IPv6-based networks and extensions). Quantitative measures and qualitative indicators are also presented and used to evaluate and compare the examined approaches. This critical review provides some valuable guidelines and suggestions for designing and developing mobility architectures, including some practical expedients (e.g. those required in the current Internet environment), aimed to cope with the presence of NAT/firewalls and to provide support to legacy systems and several communication protocols working at the application layer. application level. While throughput remains a major goal of system design, the main concern of mobility architectures is how to best manage situations where a MN changes network. This event is currently referred to as handover (or handoff ).By default, current operating systems installed on smartphones adopt the following strategy for data transmission: one Network Interface Card (NIC) at a time is configured and employed to send data. If a WiFi network is available, the terminal switches to WiFi; otherwise a cellular network is utilized, if the latter is available too. During the handover, communications are interrupted. While the widespread use of current smartphones confirms that in general such a simple approach may be a viable solution, in some cases this strategy has some severe limitations. Just as an example (which is actually a true story), let us consider the case of an employee working in an institution/company composed of several buildings, all covered by a WiFi network (e.g. a researcher in a university campus). Suppose that the researcher is a commuter and, just before leaving for going home, he/she receives an important Voice over IP (VoIP) phone call. Since he needs to leave to take the last train home, he decides to answer the call using his/her mobile phone; today, there are plenty of smartphone apps that offer very efficient VoIP services. At that moment, the device is connected through WiFi, but when he gets out of the building, the WiFi signal is lost and the smartphone automatically switches to 4G without any handover management at the application level, thus experiencing a first communication interruption. While moving, he passes through other buildings (hence, within their WiFi coverage); as a consequence, the smartphone switches back to WiFi (i.e. a second communication interruption occurs), and then back to 4G (i.e. yet another communication interruption) and so on. One might suggest that the employee should turn off the WiFi NIC before leaving, thus using the cellular...

show abstract

Design and implementation of the Node Identity Internetworking Architecture

Cited by 9 publications

References 19 publications

Naming for heterogeneous networks prone to episodic connectivity

Naming for heterogeneous networks prone to episodic connectivity

Multihoming: A Comprehensive Review

A survey on handover management in mobility architectures

Contact Info

Product

Resources

About