## 3 Proposed Solution
### Forwarding Strategy
#### 3.2.1 CreatePath and RemovePath Packet Forwarding  
To efficiently implement our mobility management scheme, we use two types of Inputs:  
(1) The CreatePath (CP) packet is an Input used to announce the producer's connection to the network, which includes a Cartesian coordinate representing the producer's location. Its purpose is to establish a path between the producer and Anchor and to notify the Anchors about the producer's location. This packet is specifically sent to the nearest Anchor in two scenarios:  
When a new producer connects to the network for the first time and when the MP cannot receive the Inputs after the handoff due to the failure to predict its destination coordinates. Like a regular Input structure, the CP packet uses a content name in the form of \"Anchorprefix/CreatePath/producerDataName\", where the \"Anchorprefix\" refers to the prefix advertised by the Anchors, \"producerDataName\" represents the name of the producer's data, while \"CreatePath\" serves as a special identifier that allows all routers to identify the packet as a request to establish the path between producer and an Anchor and handle it accordingly. Upon receiving the CP packet (step 0 in Figure 2), an intermediate router (e.g., R2 in Figure 2) creates a FIB entry using the incoming Face through which the CP packet arrives at the router and the extracted name from the CP packet name by removing the \"CreatePath\" identifier. This ensures that subsequent Inputs from consumers can be routed along the established path towards the producer without the intervention of an Anchor, particularly where the path between the MP and consumer is stretched to the Anchor (Inpts of consumer 1 in Figure 2). To avoid failures in establishing the path between the MP and Anchor, a CreatePathData (CPD) packet (step 1 in Figure 2) is used as an acknowledgment from the Anchor to the MP, confirming the receipt of the CP packet.  
(2) The RemovePath Packet is an Input that serves a dual purpose: (1) updating the FIB entry associated with the producer's data name in the Anchor with the producer's predicted location; (2) removing the outdated FIB entry in the routers along the path between the producer and the nearest Anchor that may have been created before. Like the CP packet, the RP packet uses the same content name format, \"Anchor prefix/RemovePath/producerDataName\", and includes the Cartesian coordinates representing the producer's predicted location where the MP will be present after handoff. When an MP starts moving from one Access point to another, it senses the degradation of the Received Signal Strength (RSS) quality in the current channel. As the MP moves out of range from the current PoA, the RSS quality continues to degrade. Once the RSS quality reaches a preset threshold (e.g., \(-75\) dBm), before initiating the process of selecting a new PoA, the MP sends the RP packet (step 2 in Figure 2) towards the nearest Anchor which contains the predicted coordinates of the next location. Upon receiving the RP packet, each router (e.g., R2 in Figure 2) along the path deletes the FIB entry associated with the MP and forwards the packet towards the Anchor. Once the Anchor receives the RP packet, it updates the FIB entry of the MP using the predicted coordinates included in the RP packet and propagates this information to Anchors.