# ICN-Oriented Mobility Support Method for Dynamic Allocation of Mobile Data Flows
## 1 Introduction  
With the explosive growth of mobile data traffic and the number of mobile devices, mobility support has become a long-standing problem and challenge in mobile Internet. How to provide more efficient data services for mobile users is a challenging problem. In the early stages of traditional TCP/IP network architecture design, mobility support was not considered. The IP address was given dual semantics. On the one hand, it was used as the identity identification of the mobile device to uniquely identify the device. On the other hand, it was used as the location identification of the mobile device to provide routing, addressing, and other functions. Therefore, the dual semantics of IP addresses has seriously limited the development of mobility management technology. In IP networks, the most famous protocol is Mobile Internet Protocol (MIP) [1; 2; 3] and its evolution [4; 5; 6; 7]. MIP maintains the binding relation by its Home Agent (HA). The data traffic sent to the MN will be sent to its Home Agent first, which will lead to triangular routing and a single point of failure. Protocols such as Host Identity Protocol (HIP) [8] and Identifier-Locator Network Protocol (ILNP) [9] maintain their binding relationship by relying on the host to process all mobility related signals. After the move, the mobile host notifies other hostsof its new locator in an end-to-end manner, which will take a lot of time. Therefore, these mobility support methods in IP networks cannot meet the needs of the rapidly growing number of mobile devices and mobile traffic. In order to better meet the needs of users, information-centric networking (ICN) [10; 11; 12] is proposed. Different from the end-to-end communication used in traditional IP networks, ICN focuses on the content object itself rather than the location. ICN names information by separating identity and location, replacing IP addresses with the corresponding name as an identifier in network transmissions [13]. By naming content at the network layer, ICN supports in-network caching, multicast, and mobility mechanisms to deliver content to users more efficiently [11]. ICN has two types of content discovery mechanisms, namely lookup-by-name and routing-by-name. ICN's feature of separating name and address and supporting name-based content discovery mechanisms can effectively solve the IP semantic overload problem. Thus, ICN has a natural advantage in supporting mobility. We divide the mobility support proposals in ICN into anchor-based proposals and anchorless proposals. Anchor-based proposals [14; 15; 16; 17; 18] are similar to MIP. Packets are always transmitted through anchor nodes, which will lead to problems such as mobile handoff path extension, single points of failure, and so on. Anchorless proposals [19; 20; 21; 22; 23; 24; 25; 26; 27] remove the anchor nodes, thus realizing optimization of the forwarding path to a certain extent and bringing better performance to the handover. With the rise of the mobile Internet, the Internet of Things, and the industrial Internet, various mobile applications that require low latency have emerged, such as augmented reality, intelligent vision applications, and online games. After the mobile route is optimized, the data transmission capability of the switching path will greatly affect mobile packet delay. With the development of network devices, each network device integrates multiple functions. A content producer device can provide consumers with multiple content services at the same time. Multiple data flows will be generated between consumers and producers. Existing anchorless mobility support methods do not consider the real-time network environment, such as the bandwidth of the switching path and the characteristics of different mobile data flows. The same optimization method is adopted for all mobile data flows, making the switching path singular. If the bandwidth of a single switching path cannot meet the transmission requirements of mobile data flows, it will cause network congestion.