# Guidelines towards Information-Driven Mobility Management
## 2 Related Work  
Mobility management comprises a wide set of related work, including an extensive set of proposals that has been developed to support mobility from the perspective of different OSI Layers [3]. Out of the available solutions, IP-based solutions are today the basis of mobility management in cellular and wireless environments. The most recent evolution of such category of solutions concerns distributed mobility management and is being steered by the _Internet Engineering Task Force (IETF) Distributed Mobility Management (DMM)_ Working Group [4]. Decentralisation of IP-based mobility management relates mostly with the integration of these approaches in large-scale heterogeneous environments (such as 5G) as well as with support towards flatter networking architectures [5]. The debate on decentralisation covers a wide set of topics, including decoupling of data and control planes, better management of mobility anchor points, etc.  
ICN introduced a relevant simplification, namely information-centricity instead of host-reachability. The capability to store status and data in routers (_store-and-forward_) provides the grounds to better support mobility of devices in a network. In this context, a thorough overview on mobility aspects for one of the existing ICN architectures, NDN, was provided by [PERSON] et al. [2]. The authors approached advantages and disadvantages in different scenarios with the aim of further assisting the support of mobility. Their analysis is compared to IP-based approaches in terms of architectural design. [PERSON] et al. provided a global overview on the NDN design and mobility support, alerting to the need to consider a better support for producer mobility [6]. In fact, most related work has focused on improving producer mobility, i.e., supporting movement of devices that provide data. [PERSON] et al. provided a relevant overview on mobility support, in particular for environments focused on the interoperability of ICN and IP, proposing an anchor-less solution to support mobility coupled to a routing protocol [7]. Kite is a mobility solution for NDN which exploits NDN forwarding state to keep track of moving producers and their whereabouts. Kite follows IP-based approaches by considering a \"rendezvous point\" which assists in tracing where data are, while the producer performs reattachment to a new location [8].  
[PERSON] et al. described the steps towards a reference model for mobility-driven networks, debating on evolutionary principles such as the decoupling of service and device entity, for vertical handovers, and entity/locator identifiers, for horizontal handovers [9]. [PERSON] et al. provided a survey on ICN mobility issues from an architectural perspective, highlighting potential benefits brought by the ICNnetworking semantics [10]. Our paper closely follows the line of work that is focused on assisting in further evolving mobility management in an interoperable way, by learning from prior approaches, while at the same time by trying to keep the beneficial properties of ICN design (content-centricity). A contribution of our work is a clarification on different functional aspects of an abstract model of mobility management derived from prior learning. A second contribution is a clarification on the different functional entities (mobile node and correspondent node) and where they fit ICN architectures. A third contribution concerns an analysis of current mobility management approaches, and guidelines to assist a consolidated design of future mobility management approaches.