# OPMSS: Optimal Producer Mobility Support Solution for Named Data Networking
## 1 Introduction  
Based on Internet protocol (IP) architecture, the Internet has achieved exceptional success since its establishment, particularly with the advent of overlays such as peer-to-peer networking, web applications, wireless sensor networking, mobile networking, the Internet of Things (IoT), vehicular networking and content distribution networking. However, the nature of Internet use is rapidly changing from being host-based and emphasizing point-to-point connection to being content-centric and emphasizing the sharing of information. Moreover, the IP architecture is becoming complex due to integration overlays that result in ineffective content distribution, delays, insecurity, and high bandwidth consumption attributable to increased user demand. Named data networking (NDN) is the prominent architecture under the umbrella of information-centric networking (ICN), which is designed as a clean-slate Internet architecture to replace the current IP Internet architecture [1]. The named data networking was proposed to offer vast advantages, especially with the advent of new content distributions in IoT, 5G and vehicular networking. Fundamentally, NDN supports content consumer mobility due to the consumer-driven design principles and nature of in-network catching capabilities. Named data networking (NDN) architecture is recognized as a potential content-centric paradigm for wired and wireless domains. Its novel concepts, such as security, in-network caching, hierarchical naming or namespace, named content, and name-based routing, suit the requirements of IoT [2]. Moreover, the architecture has the potentialfor efficient data dissemination and interconnecting billions of heterogeneous objects in an IoT network. Despite the benefits of NDN in an IoT network, the mobility perspective must be studied, and a concrete solution to support mobile IoT must be found [2]. If mobile nodes are no longer reachable in IoT, the problem will worsen, as the mobile frequencies in intelligent transportation and eHealth applications are very important [2]. In addition, the services that are based on NDN with blockchain technology can be applied in IoT for secured data management. Decoupling senders and receivers, in-network caching, and the hop-by-hop transmission characteristics of NDN enable it to support 5G networks [3]. The result of the potentiality is shown by information-centric networking (ICN), such as security, mobility, energy efficiency, and in-network caching, which are considered important in the 5G telecommunication network [4]. In addition, ICN is promoted as a framework for virtual function provisioning and named content retrieval in 5G [3]. The encouraging results of ICN have motivated certain technical specification organizations to promote ICN as an enabler of 5G, which evolved from 4G core network architecture focus on radio access networks, as an overlay on network function virtualization, and software-defined networking infrastructure [5]. However, in adapting 4G, the drawbacks of IP architecture, which include tunneling technology to support mobility, high signaling cost, security challenges, and the lack of multihoming support, were inherited. Therefore, the inherent benefit of ICN with the support of name-based networking, security, in-network storage, in-network caching, and mobility is the ability to solve the inherited problems of the 5G network. In addition, the mobility management involved in network slicing-based 5G is challenging due to the high density and high mobility of devices [6]. Consequently, the mobility support and in-network caching characteristics of NDN emerged in the architecture as promising candidates to integrate into 5G [7]. NDN supports consumer mobility without additional mechanisms by using certain characteristics, such as its consumer-driven nature and in-network caching [8; 9; 10]. NDN design principles inherently support content consumer mobility; for example, when the physical location of a consumer changes, there is no effect on the data plane, unlike with IP [7].