## 3 Proposed Solution
### Distributed Anchor Design  
In the DMMS, distributed synchronized Anchors are strategically placed throughout the network. These Anchors act as rendezvous nodes between consumers and producers, where the Anchor redirects consumers' Inputs toward the producer when a direct path is not found toward the producer with minimal path stretch. Each Anchor operates as a regular NDN router with the same functionalities and maintains the same structure with a slight modification to the FIB entries. This modification includes two additional fields, namely \"coordinates\" and \"seq\". The \"coordinates\" field is used to store the coordinates of the producer's location or the predicted one, while the \"seq\" field is a sequence number used to maintain the consistency of the producer's coordinate information among Anchors and prevent forwarding loops during producer's notification message propagation (e.g., AnchorA's FIB in Figure 1). Regarding the inconsistencies in the producer's coordinates among Anchors, they can be shared in real time by implementing synchronization protocols designed for distributed dataset synchronization in NDN, such as ChronoSync [26], VectorSync [27], or PSync [28]. Alternatively, a producer's handoff-driven mechanism is used to minimize unnecessary network traffic. When a producer handoff event occurs, it sends a special Inpt with a sequence number that serves as a unique identifier for the update, incremented with each handoff. This Inpt is then propagated to Anchors in the network to ensure that updates are applied in the correct order. Like the IP anycast mechanism, the Anchors in the DMMS share and advertise the same routing prefix through the routing protocol within the network, which allows consumers to efficiently discover and connect with the nearest Anchor, regardless of their specific location within the network. Furthermore, to ensure the reachability of MP in the network, each MP is assigned a unique hierarchical name for its data, which uses the same Anchor prefix. We present in Figure 1 a comprehensive architecture concept. After an MP connects to a new PoA, it establishes a path between itself and the nearest Anchor. To request data from this MP, the consumer sends an Inpt containing the MP data name (e.g., in Figure 1, the producer data name is \"Anchor/accident/hassan2\"). Once an intermediate router receives the Inpt, it checks its FIB to determine the Face with the longest prefix match. If a matched FIB entry to this Inpt is found, then the Inpt will be forwarded to the MP without the intervention of the Anchor (e.g., in Figure 1, the Inpts of consumer 3 will be forwarded along R2 and R1 without reaching the Anchor). If a matched FIB entry does not exist, then the Inpt will be forwarded to the nearest Anchor. The Anchor then checks its FIB to determine the strategy to forward the Inpt, either using the NDN's default forwarding (e.g., in Figure 1, the Inpts of consumer 2 at AnchorA will be forwarded along the path AnchorA \(\longrightarrow\) R2 \(\longrightarrow\) R1 \(\longrightarrow\) PoA \(\longrightarrow\) producer) or using the location-based forwarding strategy (e.g., in Figure 1, the Inpts of consumer 2 at AnchorB will be forwarded using location-based forwarding). In fact, using Anchors in the network has a significant impact on increasing the path stretching between consumers and MPs compared to an Anchor-less approach. However, strategically positioned Anchors can effectively reduce the number of hops that the Inpts  
Figure 1: Anchor-based distributed mobility management architecture. need to traverse to reach the MP, thereby minimizing latency and improving content delivery efficiency. The problem of selecting Anchor placements that can manage the producer mobility in a dense network can be viewed as a variant of the well-known k-center or p-median problems, which are optimization problems that involve selecting a subset of locations from a larger set of potential locations.