## 1 Introduction  
D2D communication systems are one of the fundamental elements of 5G and B5G mobile telecommunication networks. Unlike traditional cellular networks, with D2D communication technology, nodes can communicate with one another with or without the involvement of a base station [1]. Direct communication between devices nearby will achieve low latency and high throughput compared to the communication of devices through the nearest eNodeB, which can be congested due to high traffic load. The potential of D2D communication to transform next-generation cellular networks has resulted in the integration of the technology in many areas, including networks for public safety [2], proximity-based services [3], vehicular networks [4], multi-hop relaying [5], and cellular offloading [6]. Given the vigorous nature of D2D communications, routing protocols are an architecture necessary for implementing efficient D2D communication systems [7]. Therefore, the network's overall performance will be negatively affected if a wrong and ineffective routing protocol is used for D2D communication systems. Routing protocols serve as a critical architecture required for creating an effective D2D communication system due to the robust nature of D2D communication [7]. As a result, researchers have used different techniques to optimize the traditional routing protocols, focusing mainly on energy efficiency, scalability, reliability, and enhanced resource utilization [8; 9; 10]. A specific problem with D2D communication is the issue of wireless device relays and exhaustible energy sources. Therefore, energy efficiency and less overhead routing protocols are necessary to improve network performance. However, in outbound autonomous D2 Dcommunication, there is no central administrative body, and nodes control their mobility. This can lead to frequent changes in selected multipoint relay (MPR) and communication links, challenging traditional routing techniques [7; 11]. Conventionally, routing protocols for D2D/wireless devices are categorized as proactive, reactive and hybrid, depending on network structure, routing strategy, communication mode, and state of information [12; 13; 14]. Proactive or table-driven routing protocols store routing information in tables and require nodes to establish communication links in advance [15]. This allows nodes to maintain an updated network topology, making finding available routes to desired destinations easier. Proactive routing protocols like OLSR [15] and DSDV [16] are suitable for low-latency applications due to their quick connectivity and minimum delay. Reactive routing protocols are also known as on-demand routing techniques. Reactive routing techniques require nodes to create a path to a destination node only when needed [17; 18]. The most famous and widely used reactive protocols are the Ad Hoc On-Demand Distance Vector (AODV) [19] and Dynamic Source Routing (DSR) [20]. The general concept around hybrid routing techniques is to combine the idea of both reactive and proactive routing protocols with an effort to overcome some weaknesses. The most famous and widely used hybrid routing protocols are the Zone Routing Protocol (ZRP) [21] and hierarchical routing techniques [22]. The proactive routing protocol in OLSRv2 raises several difficulties, including those related to energy consumption, routing overhead, and the best choice of relays [23; 24; 25]. This is because link state processing, information base maintenance, and low battery energy nodes selected as multipoint relays experience a rapid power failure and create network partitions. Despite these challenges, proactive routing protocols remain vital for future communication technologies prioritizing low latency [26], which this paper thoroughly considers for OLSR modification. As stated earlier, link sensing, MPR nodes, and information base maintenance are both the strengths and Achilles' heels of OLSRv2 [24; 27; 28; 29]. The existing OLSRv2 specification assumes mobile devices have infinite memory, processing abilities, and ample storage.