In this section two solutions are described that can support content migration due to user mobility.
The first content migration solution is accomplished without using mobility
prediction, see upper part of Fig. 4.
The second content migration support solution is accomplished using mobility
prediction, see lower part of Fig. 4.
The content migration procedure that is not using mobility prediction can be
described using the following steps:
• Step 1: Client establishes a connection to CCN router 2
• Step 2: CCN router 2 sends the client information containing node ID and interface ID to MSM.
• Step 3: Client sends the Interest message via the CCN router 2.
When the CCN router 2 receives the Interest message, a look-up is performed on its CS, PIT, and FIB sequentially.
In this case, the matching information is only found in its FIB that informs the Interestmessage has to be forwarded to the interface pointing to CCN router 1.
• Step 4: CCN router 1 receives the Interest messagefrom CCN router 2 and does the same procedure performed by CCN router 2.
After performing look-up on its CS and PIT, and if no matching information is
found, it checks its local FIB.
• Step 5: The CCN router 1’s FIB causes that the Interest
message to be forwarded to the interface pointing to the
source.
• Step 6: When the source receives the Interest message, it looks-up on its CS. When the matching content is found, it sends the content/data using the Data message
as the response for the Interest message through the arrival interface of Interest to the CCN router 1.
• Step 7: Before the requested Data is received by CCN router 2, the client moves to another location and terminates its connection with CCN router 2.
• Step 8: When the CCN router 1 receives the Data message forwards it to the CCN router 2, based on its PIT, and stores it in its cache.
• Step 9: After the handover procedure is completed, the client establishes a new connection with CCN router 3.
• Step 10: CCN router 3 sends the client information containing node ID and interface ID to MSM.
• Step 11: MSM determines that client has been moved, because it receives client information from two different routes.
• Step 12: MSM informs SO to notify ICN Manager about the client’s location changing.
• Step 13: ICN Manager starts to configure PIT in the CCN router 2 to be able to forward the Data message to the CCN router 3.
• Step 14: ICN Manager also starts to configure PIT in the CCN router 3 to be able to forward Data message to the client.
• Step 15: CCN router 2 sends the Data message to the CCN router 3 based on its PIT and stores it in its cache.
• Step 16: CCN router 3 sends the Data message to the client based on its PIT and stores it in its cache.