# ICN-Oriented Mobility Support Method for Dynamic Allocation of Mobile Data Flows
## 3 How Can Dynamic Allocation Flows Be Realized in Mobility Support?
### Dafm  
Based on the ICN mobility support architecture, we propose a mobility support method for dynamically allocating mobile data flows (DAFM). Figure 1 shows the operation of the method to support mobility and achieve mobile data flow assignment. As shown in Figure 1, the consumer is requesting multiple forms of content published by the same producer, so multiple data flows are generated between the producer and the consumer. We record the data flow generated by the content as Flow1, Flow2... FlowF. The forwarding path of the original data flows is Producer->R1->R2->R3->API->Consumer. When a consumer moves from the area of the initial access router (R3) to the area of the new access router (R4), the original AP (API) will send a Mobile Event Message to the initial access router (R3), which carries the identifier of the consumer (EID0), the identifier of the content requested by the consumer (EID1, EID2... EIDF), and the rate of the corresponding data flow (Step 1). After the initial access router (R3) receives the Mobile Event Message, it will query the NRS for the consumer's latest network address (NA2) based on the consumer identifier (EID0) (Step 2). The initial access router (R3) receives the response from the NRS and learns the consumer's latest network address (NA2) (Step 3). The initial access router (R3) selects itself as the late-binding node to redirect the data flows (Step 4). At the same time, the initial access router (R3) constructs a Mobile Path Notification (MPN) to propagate to the producer's access router (R1) in the reverse direction of the original data flows (Step 5). In addition to announcing the latest EID-NA mapping relationship (EID0-NA2) of the consumer, the identification of the content (EID1, EID2... EIDF) requested by the consumer, and the corresponding data flow rate, the MPN also needs to contain information regarding the router node (e.g., the use of an MFT in the router) on the MPN propagation path, as well as the switching path information (e.g., the bandwidth of the switching path and the number of switching path hops) formed by each router acting as a late-binding node on the MPN propagation path. The producer's access router (R1) uses the late-binding node selection algorithm to select the switching path for data flows according to the various information carried by the MPN, thus completing the final selection of the late-binding node (Step 6). The producer's access router (R1) uses a Mobile Path Update (MPU) message to inform the corresponding router of the selection result for the late-binding node (Step 7). The selected router will update the MFT to redirect data flows according to the final late-binding node selection result (Step 8). In the example in Figure 1, R3 is selected to perform late-binding processing on Flow1. The switching path of Flow1 is Producer->R1->R2->R4->AP2->Consumer. R2 is selected to perform late-binding processing on Flow2. The switching path of Flow2 is Producer->R1->R2->R4->AP2->Consumer. R1 is selected to perform late-binding processing on other data flows. The switching path of other flows is Producer->R1->R4->AP2->Consumer. In this way, multiple data flows transmitted between producers and consumers will be allocated to multiple switching paths for transmission. Therefore, our solution is conducive to achieving network load balancing, improving packet forwarding, and improving mobile user performance.