Architecture and design of network of information mobile node
Résumé
Mobility management in a wireless environment has always been an important issue. There are many solutions proposed to target the problems faced by mobile nodes during mobility. The current Internet architecture is TCP/IP based and mobile nodes use Mobile IP or IP mobility, which is a protocol developed for mobile devices to roam from network to network maintaining their permanent IP addresses. However, with the inception of the idea of a network of interconnected objects, which generally termed as Internet of Things, motivated to have a new Internet architecture, where information supersedes the node centric concept of networking. Therefore, we have an information centric network than a node centric network like the contemporary Internet architecture. The project 4WARD is one such approach. In this work, the proposed solution for mobility management in network is presented in the form of a mobile node architecture in which the main components are introduced. In this abstract the core function of Virtual Node Layer (VNL) is presented. The three core entities (VNL, ILCTR (Inner locator Construction Router) and OLCTR (Outer Locator Construction Router)) within the transport layer are responsible for the mobility management of Network of Information Mobile Node (NetInf MN). NetInf MN exhibits features introduced in Locator Identifier Separation Protocol Mobile Node (LISP MN) plus innovative routing capabilities (ILCTR and OLCTR). In general, the basic contribution is to provide end host mobility in different mobility scnarios, while in particular, the idea focuses to provide mobility management in NetInf. The work presented here highlights the features of the NetInf MN architecture and VNL and is complemented with its working principle, advantages it exhibits and its supporting role in the NetInf MN architecture within the network. There are always certain criteria to follow whenever there is an issue of designing a Mobile IP protocol, architecture or framework because the basic idea in the end is to provide end host mobility. These criteria or constraints, force to address issues which in return can improve the overall performance in mobility management in terms of minimizing the latency during the handover stage, regular updates in terms of single or simultaneous movement of the hosts as well as managing the power in cases where the node is idle. In designing NetInf MN, all the parameters mentioned above are taken into account and a qualitative analysis of such parameters is planned for future work. Based on this analysis, we are going to develop a road map for further improvements in our proposal on which our simulation environment will be created.