## 2 Background and Literature Review
### Review of NDN Mobility  
The author of the study [5] introduced a brand-new networking model called ICN. Through this review, they look at several crucial aspects, such as techniques for naming as well as routing, along with in-network caching options, and so on, as well as characteristics that distinguish the benefit of actually implementing ICN, unresolved research issues, and fresh appeal in this field. We provide a user mobility NDN communication model in the scheme [17] where interest and data packets are transferred with a single transaction unit. The link for transactions would be established through the mobility link service (MLS) suggested in this article, which operates in NDN. Due to the regularly shifting locations of users, the fundamental help of MLS is in reusing the existing connection regarding a transaction as compared to starting a new  
Figure 3: Software-defined networks model [20]. connection. The current connection is damaged if a consumer changes their position away from the adjacent node, and the data cannot be entirely received owing to handover. Therefore, in this instance, the connection is reinstated rather than being established anew, and fresh content requests are made to the original new NAR. As a result, the data for the remaining material was delivered by the prior NAR to the NDN producer, who then forwarded it toward the new NAR, which was requested by the user already [17]. The transaction is carried out using an IP-based architecture, as designated in the literature [22], which generates a simulation atmosphere for the NDN model to analyze performance in case of a mobile consumer changing their position between points to check the rate of generation for the interest packets leveraging and employing ndnSIM within the NS3 simulator. An interest packet generated by a mobile user is initially wrapped with an IP header and sent to the NDN node through the associated AP. The packet is de-encapsulated and routed on the NDN layer when it gets an NDN node, which takes away the IP header from the packet. Additionally, the NDN node delivers IP header-encapsulated data packets to mobile users and returns them [22]. The technique will be explained in more depth for the SDN setting when utilizing OpenFlow, as explained in [23], where a method is provided that is based on hashing content names with the address field inside IP packets. OpenFlow 1.0 and User Datagram Protocol (UDP) are used to implement this method. The UDP packet's payload contains the NDN packets that have been encapsulated. Interest and data packets are assigned to two separate port numbers. As a result, the switches may operate with both NDN and IP structures. This creates the routers prepared to detect these two NDN packets with further identification of IP packets from packets in NDN. There is no need in OpenFlow for directing packet payloads, hence NDN routers must be able to conduct longest prefix matching (LPM) on packet names. Consequently, the names are (encrypted), i.e., hashed and added to the packet header's IP field. The authors in [24] demonstrate how the prediction of location can be utilized to perform the anchorless management of mobility and to guarantee a seamless handover for the producer with real-time communication for a multi-media environment. The results show that the methodology reduces round-trip time and handover latency. In [25], authors enhanced and optimized a popular scheme for an anchor-based approach via an arrangement of multi-layer anchor nodes based on network topology in a hierarchical way, which is known as an anchor chain. Moreover, the interest packets are forwarded toward the producer, which also pass by it. As the producer changes its location, the newly produced anchor chain can reuse the prior forwarding route to guide further interests according to the modified location for the producer as well, as to reduce the drop rate of the interest packets.