02182nas a2200205   4500000000100000008004100001260001200042100001600054700001900070700001800089700001700107700001700124700001900141245009300160856004300253300000700296490000700303520165200310022001401962       2020                            d  c12/20201 aPere Millan1 aCarles Aliagas1 aCarlos Molina1 aRoc Meseguer1 aSergio Ochoa1 aRodrigo Santos00aPredicting Topology Propagation Messages in Mobile Ad Hoc Networks: The Value of History  uhttps://www.mdpi.com/1424-8220/20/1/24  a240 v203 aThe mobile ad hoc communication in highly dynamic scenarios, like urban evacuations or search-and-rescue processes, plays a key role in coordinating the activities performed by the participants. Particularly, counting on message routing enhances the communication capability among these actors. Given the high dynamism of these networks and their low bandwidth, having mechanisms to predict the network topology offers several potential advantages; e.g., to reduce the number of topology propagation messages delivered through the network, the consumption of resources in the nodes and the amount of redundant retransmissions. Most strategies reported in the literature to perform these predictions are limited to support high mobility, consume a large amount of resources or require training. In order to contribute towards addressing that challenge, this paper presents a history-based predictor (HBP), which is a prediction strategy based on the assumption that some topological changes in these networks have happened before in the past, therefore, the predictor can take advantage of these patterns following a simple and low-cost approach. The article extends a previous proposal of the authors and evaluates its impact in highly mobile scenarios through the implementation of a real predictor for the optimized link state routing (OLSR) protocol. The use of this predictor, named OLSR-HBP, shows a reduction of 40–55% of topology propagation messages compared to the regular OLSR protocol. Moreover, the use of this predictor has a low cost in terms of CPU and memory consumption, and it can also be used with other routing protocols.  a1424-8220