Global Name Resolution Service Research Articles

GUID for Mobility First Architecture Supporting IoUT

The Mobility First network architecture is introduced to differentiate the human readable names with corresponding Global Unique Identifiers (GUIDs), and the dynamic network address locators. The human readable name can be managed and assigned to a unique GUID by Name Certification Services (NCSs). GUIDs assigned to network objects (Things) are mapped to a set of network addresses (NAs). Delay and Disruption Tolerant Network (DTN) is used in the Mobility First for efficient communication. GUIDs are assigned to Internet of Things (IoT) and Internet of Underwater Things (IoUT). Underwater things can collect the underwater data using sensors, underwater modem, underwater Medium Access Control (MAC) board and transducer etc. Internet of Underwater Things (IoUT) can communicate the changes in the ocean environment to the offshore IoT. Underwater things are constructive in offshore investigation, disaster anticipation, data gathering, assisted navigation, pollution checking and strategic inspection. To achieve these features, this paper proposes architecture with three layers. They are IoUT layer, DTN communication layer and IoT layer. IoUT layer gathers the information with the help of underwater things. DTN communication layer sends this information to IoT layer with help of Global Name Resolution Service (GNRS). Dynamic binding of names to address is done by GNRS. By using IoT layer ocean data can be broadcasted in different applications like scientific applications, military applications, industrial applications and civilian applications. Results are shown by using the GUID accessing based on popularity.

Hierarchical DHT-based name resolution for information-centric networks

Information-centric network (ICN) architectures are an increasingly important approach for the future Internet. Several ICN approaches are based on a flat object ID namespace and require some kind of global name resolution service to translate object IDs into network addresses. Building a world-wide NRS for a flat namespace with 1016 expected IDs is challenging because of requirements such as scalability, low latency, efficient network utilization, and anycast routing that selects the most suitable copies. In this paper, we present a general hierarchical NRS framework for flat ID namespaces. The framework meets those requirements by the following properties: The registration and request forwarding matches the underlying network topology, exploits request locality, supports domain-specific copies of binding entries, can offer constant hop resolution (depending on the chosen underlying forwarding scheme), and provides scoping of publications.Our general NRS framework is flexible and supports different instantiations. These instantiations offer an important trade-off between resolution-domain (i.e. subsystem) autonomy (simplifying deployment) and reduced latency, maintenance overhead, and memory requirements. To evaluate this trade-off and explore the design space, we have designed two specific instantiations of our general NRS framework: MDHT and HSkip. We have performed a theoretical analysis and a simulation-based evaluation of both systems. In addition, we have published an implementation of the MDHT system as open source. Results indicate that an average request latency of (well) below 100ms is achievable in both systems for a global system with 12 million NRS nodes while meeting our other specific requirements. These results imply that a flat namespace can be adopted on a global scale, opening up several design alternatives for information-centric network architectures.

MobilityFirst

This paper presents an overview of the MobilityFirst network architecture, currently under development as part of the US National Science Foundation's Future Internet Architecture (FIA) program. The proposed architecture is intended to directly address the challenges of wireless access and mobility at scale, while also providing new services needed for emerging mobile Internet application scenarios. After briefly outlining the original design goals of the project, we provide a discussion of the main architectural concepts behind the network design, identifying key features such as separation of names from addresses, public-key based globally unique identifiers (GUIDs) for named objects, global name resolution service (GNRS) for dynamic binding of names to addresses, storage-aware routing and late binding, content- and context-aware services, optional in-network compute layer, and so on. This is followed by a brief description of the MobilityFirst protocol stack as a whole, along with an explanation of how the protocol works at end-user devices and inside network routers. Example of specific advanced services supported by the protocol stack, including multi-homing, mobility with disconnection, and content retrieval/caching are given for illustration. Further design details of two key protocol components, the GNRS name resolution service and the GSTAR routing protocol, are also described along with sample results from evaluation. In conclusion, a brief description of an ongoing multi-site experimental proof-of-concept deployment of the MobilityFirst protocol stack on the GENI testbed is provided.