<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.1 20151215//EN" "http://jats.nlm.nih.gov/publishing/1.1/JATS-journalpublishing1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" article-type="research-article" dtd-version="1.1">
<front>
<journal-meta>
<journal-id journal-id-type="pmc">CSSE</journal-id>
<journal-id journal-id-type="nlm-ta">CSSE</journal-id>
<journal-id journal-id-type="publisher-id">CSSE</journal-id>
<journal-title-group>
<journal-title>Computer Systems Science &#x0026; Engineering</journal-title>
</journal-title-group>
<issn pub-type="ppub">0267-6192</issn>
<publisher>
<publisher-name>Tech Science Press</publisher-name>
<publisher-loc>USA</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">19557</article-id>
<article-id pub-id-type="doi">10.32604/csse.2022.019557</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>ML-Fresh: Novel Routing Protocol in Opportunistic Networks Using Machine Learning</article-title>
<alt-title alt-title-type="left-running-head">ML-Fresh: Novel Routing Protocol in Opportunistic Networks Using Machine Learning</alt-title>
<alt-title alt-title-type="right-running-head">ML-Fresh: Novel Routing Protocol in Opportunistic Networks Using Machine Learning</alt-title>
</title-group>
<contrib-group content-type="authors">
<contrib id="author-1" contrib-type="author" corresp="yes">
<name name-style="western">
<surname>Garg</surname>
<given-names>Puneet</given-names>
</name>
<email>puneetgarg.er@gmail.com</email>
</contrib>
<contrib id="author-2" contrib-type="author">
<name name-style="western">
<surname>Dixit</surname>
<given-names>Ashutosh</given-names>
</name>
</contrib>
<contrib id="author-3" contrib-type="author">
<name name-style="western">
<surname>Sethi</surname>
<given-names>Preeti</given-names>
</name>
</contrib><aff><institution>Department of Computer Engineering, J. C. Bose University of Science and Technology, YMCA</institution>, <addr-line>Faridabad, 121006</addr-line>, <country>India</country></aff>
</contrib-group><author-notes><corresp id="cor1">&#x002A;Corresponding Author: Puneet Garg. Email: <email>puneetgarg.er@gmail.com</email></corresp></author-notes>
<pub-date pub-type="epub" date-type="pub" iso-8601-date="2021-08-28">
<day>28</day>
<month>8</month>
<year>2021</year>
</pub-date>
<volume>40</volume>
<issue>2</issue>
<fpage>703</fpage>
<lpage>717</lpage>
<history>
<date date-type="received">
<day>17</day>
<month>4</month>
<year>2021</year>
</date>
<date date-type="accepted">
<day>23</day>
<month>5</month>
<year>2021</year>
</date>
</history>
<permissions>
<copyright-statement>&#x00A9; 2021 Garg, Dixit and Sethi</copyright-statement>
<copyright-year>2021</copyright-year>
<copyright-holder>Garg, Dixit and Sethi</copyright-holder>
<license xlink:href="https://creativecommons.org/licenses/by/4.0/">
<license-p>This work is licensed under a <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</ext-link>, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="TSP_CSSE_19557.pdf"></self-uri>
<abstract>
<p>Opportunistic Networks (OppNets) is gaining popularity day-by-day due to their various applications in the real-life world. The two major reasons for its popularity are its suitability to be established without any requirement of additional infrastructure and the ability to tolerate long delays during data communication. Opportunistic Network is also considered as a descendant of Mobile <italic>Ad hoc</italic> Networks (Manets) and Wireless Sensor Networks (WSNs), therefore, it inherits most of the traits from both mentioned networking techniques. Apart from its popularity, Opportunistic Networks are also starting to face challenges nowadays to comply with the emerging issues of the large size of data to be communicated and blind forwarding of data among participating nodes in the network. These issues lower the overall performance of the network. Keeping this thing in mind, <italic>ML-Fresh</italic>-a novel framework has been proposed in this paper which focuses to overcome the issue of blind forwarding of data by maintaining an optimum path between any pair of participating nodes available in the OppNet using machine learning techniques viz. <italic>pattern prediction, decision tree prediction, adamic-adar</italic> method for complex networks. Apart from this, <italic>ML-Fresh</italic> also uses the history of successful encounters between a pair of communicating nodes for route prediction in the background. Simulation results prove that the ML-Fresh outperforms the existing framework of Opportunistic Networks on the grounds of standard Quality-of-Service (QoS) parameters.</p>
</abstract>
<kwd-group kwd-group-type="author">
<kwd>Opportunistic networks</kwd>
<kwd>artificial intelligence</kwd>
<kwd>machine learning</kwd>
<kwd>link prediction</kwd>
<kwd>routing protocols</kwd>
<kwd>QoS parameters</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec id="s1">
<label>1</label>
<title>Introduction</title>
<p>Owing to the hard efforts put by network science researchers, man today can communicate even beyond the planetary boundaries. Due to the significant growth in the networking domain, data communication has been possible in such areas where it once seemed impossible. Opportunistic Networks are the result of such momentous growth in a couple of years in the field of wireless networking [<xref ref-type="bibr" rid="ref-1">1</xref>].</p>
<p>According to some researchers, Opportunistic Networks inherited their basic traits from Mobile <italic>ad hoc</italic> Networks (MANETs) [<xref ref-type="bibr" rid="ref-2">2</xref>] and Wireless Sensor Networks (WSNs) [<xref ref-type="bibr" rid="ref-3">3</xref>,<xref ref-type="bibr" rid="ref-4">4</xref>]. Yuan et al. [<xref ref-type="bibr" rid="ref-5">5</xref>] suggested that Opportunistic Networks (OppNets) may be regarded as a part of Delay Tolerant Networks or Disruption Tolerant Networks. As the name itself indicates, this type of network is developed especially to tolerate long delays. There are various scenarios in real life like where this networking technique fits best. These scenarios may include Inter-Planetary communication, Disaster Management, War-Field situation, Space communications, etc.</p>
<p>Opportunistic Networks work on the principle of store-carry-and-forward i.e. the member node in the OppNet first stores the data which is supposed to be sent to some pre-decided node and send it to the desired location directly or through the intermediate node(s) [<xref ref-type="bibr" rid="ref-6">6</xref>]. The node stores the mentioned data until it gets a notification of the successful delivery to the destination. This feature makes the Opportunistic networks best suited for a situation like intermittent connection or connection failure.</p>
<p>According to Nayyar et al. [<xref ref-type="bibr" rid="ref-7">7</xref>], there is no standardized definition of Opportunistic Networks, but, based on Literature Survey, Opportunistic Networks may be described as a &#x201C;network of wirelessly connected nodes&#x201D;. Opportunistic networks do not require any specific infrastructure support for their establishment. Following Garg et al. [<xref ref-type="bibr" rid="ref-8">8</xref>], An Opportunistic Network can be formed using smartphones via Bluetooth or Wi-Fi. Similarly, using the basic connection feature available in the device to be connected, Opportunistic Networks may form various kinds of networks such as Acoustic Networks, Airborne Networks, Mobile Communication, Vehicular Networks, etc. Besides the mentioned networks, Opportunistic networks may also include all types of mentioned networks to form a single hybrid network with the help of necessary infrastructure to connect heterogeneous network devices. A general scenario of such a situation is depicted in <xref ref-type="fig" rid="fig-1">Fig. 1</xref>.</p>
<fig id="fig-1">
<label>Figure 1</label>
<caption>
<title>A general scenario of OppNet</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_19557-fig-1.png"/>
</fig>
<p>Apart from the above-mentioned traits, Opportunistic Networks has numerous applications in the real-life world; some of them are listed below:</p>
<p><italic>a) Support for Smart City:</italic> Saloni et al. [<xref ref-type="bibr" rid="ref-9">9</xref>] developed LASSO which is an android based app that connects a group of people in a city via Bluetooth/Wi-Fi for communication and tracking each other. This app worked well on a group of tourists in an unknown city and preventing them from miss that place.</p>
<p><italic>b) Under-water communication:</italic> Menon et al. [<xref ref-type="bibr" rid="ref-10">10</xref>] and Detweiller et al. [<xref ref-type="bibr" rid="ref-11">11</xref>] discussed the various methods to use Opportunistic Networks as a backbone networking technique for communicating above as well as underwater in sea region.</p>
<p><italic>c) Forest surveillance</italic>: Martonosi [<xref ref-type="bibr" rid="ref-12">12</xref>] developed a project named Zebranet under the Princeton University project to monitor the routine life of Zebra in the Forest using Opportunistic Networks as the backbone. This project may be extended to cover all animals residing in the forest for surveillance purposes.</p>
<p><italic>d) SWIM:</italic> Small et al. [<xref ref-type="bibr" rid="ref-13">13</xref>] elaborated an opportunistic network based on the concept of the Shared Wireless Info-station Model (SWIM) for data exchange over the long-range in ocean area. Initially, it was practiced by tying sensors on whales back and data was forwarded through the tied sensors and received successfully back on Info-Station.</p>
<p><italic>e) Inter-Planetary Communication:</italic> Wood et al. [<xref ref-type="bibr" rid="ref-14">14</xref>] described Saratoga, an opportunistic network-based routing protocol specifically designed for inter-planetary data communication. Currently, Saratoga is used by NASA for few years.</p>
<p><italic>f) Miscellaneous:</italic> Besides the above-mentioned applications, Opportunistic Networks have proved themselves highly beneficial in establishing Airborne Networks [<xref ref-type="bibr" rid="ref-15">15</xref>] and space operations [<xref ref-type="bibr" rid="ref-16">16</xref>].</p>
<sec id="s1_1">
<label>1.1</label>
<title>Categories of Routing Protocols</title>
<p>Although Opportunistic Networks have numerous routing protocols with different strategies and working styles, to make it in a standardized format, all available protocols are categorized on the ground of some standard parameters such as working strategy [<xref ref-type="bibr" rid="ref-17">17</xref>], data forwarding techniques, etc. Juyal et al. [<xref ref-type="bibr" rid="ref-18">18</xref>] classified routing protocols of Opportunistic Networks into six major categories which are depicted in <xref ref-type="fig" rid="fig-2">Fig. 2</xref>:</p>
<fig id="fig-2">
<label>Figure 2</label>
<caption>
<title>Classification of routing protocols in opportunistic networks</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_19557-fig-2.png"/>
</fig>
</sec>
<sec id="s1_2">
<label>1.2</label>
<title>Organization of Paper</title>
<p>This paper is categorized into five major sections. Section 1 is dedicated to the introduction of Opportunistic Networks (OppNets), their applications, and routing protocols. It primarily aims at the new researchers who do not have enough knowledge about the research work. The extensive research work in this arena is carried out in the next sections. Section 2 describes the motivation and recent research work that inspire authors towards the focused research. Section 3 explains the methodology and working strategy of the proposed work i.e., <italic>ML-Fresh</italic> followed by Section 4 which mentions the simulation and result in part of the research work carried out. Towards the end, Section 5 concludes the overall research work explained in this paper.</p>
</sec>
</sec>
<sec id="s2">
<label>2</label>
<title>Motivation</title>
<p>Recent research work proved through simulation that <italic>Fresh</italic> Protocol from the category of social-community-based routing protocols delivers the best performance on the criteria of standard QoS parameters [<xref ref-type="bibr" rid="ref-19">19</xref>,<xref ref-type="bibr" rid="ref-20">20</xref>]. It motivates for appending this discussed research for further improvisation in the <italic>Fresh</italic> Routing framework to get the best out of it. But, before discussing further research, a basic somehow of <italic>Fresh</italic> Routing protocol is explained to get a better understanding of the proposed methodology of <italic>ML-Fresh</italic> Protocol in this paper.</p>
<sec id="s2_1">
<label>2.1</label>
<title>Fresh Protocol</title>
<p>Fresh (i.e., FResher Encounter SearcH) Protocol was introduced by Ferriere et al. [<xref ref-type="bibr" rid="ref-21">21</xref>]. Initially, it was designed for Mobile <italic>Ad hoc</italic> Networks but soon it was also adapted for Opportunistic Networks with few updates as per the network standards. Despite its simplicity, <italic>Fresh</italic> protocol is well known for its efficient route discovery in dynamic network topology which makes it a good choice for real-life situations. In <italic>Fresh</italic> Protocol, every node keeps a record of its encounter with other nodes present in the network in the process of route discovery along with the age gradient. Instead of searching new path for the destination node every time, the node firstly searches the destination node or any intermediate node towards the destination node from its record along with the respective age gradient. After the successful search, the node prefers the path or intermediate node which has the least encounter age i.e., which has more recent encounter experience with the destination node.</p>
<p>Some key points of <italic>Fresh</italic> Routing Protocol are as follows:</p>
<p>a) <italic>Fresh</italic> Protocol does not require any geographic knowledge about the participating nodes in the network as it follows the concept of Euclidean Space.</p>
<p>b) <italic>Fresh</italic> Protocol follows the concept of age gradient i.e. the path between source and destination node depends upon encounter history. It means the selected path may or may not be the shortest path between two nodes i.e. a straight line between source node to destination node on Euclidean Space.</p>
<p>c) Each Node in <italic>Fresh</italic> Protocol maintains its encounter history with all other nodes of the network; therefore, it does not require a common clock for synchronization.</p>
<p>d) Overall performance of <italic>Fresh</italic> Protocol does not get affected by the heterogeneous velocities of nodes, although it creates some hurdle during route discovery.</p>
<p>e) The search criteria of route discovery in <italic>Fresh</italic> protocol are Omni-directional.</p>
</sec>
<sec id="s2_2">
<label>2.2</label>
<title>Pseudocode</title>
<p>Pseudocode of <italic>Fresh</italic> Protocol is as follows:</p>
<p> <italic> proc FRESH (S,D)</italic> &#x003D;</p>
<p> <italic>{</italic></p>
<p> <italic>   if (thisnode.ID &#x003D; D) then</italic></p>
<p> <italic>  {</italic></p>
<p> <italic>  replyToSource(S);</italic></p>
<p> <italic>  }</italic></p>
<p> <italic>  else</italic></p>
<p> <italic>  {</italic></p>
<p> <italic>  T :&#x003D; prevEncounterAge(D);</italic></p>
<p> <italic>  A :&#x003D; findNextAnchor (D, T);</italic></p>
<p> <italic>   if (A !&#x003D; D) then</italic></p>
<p> <italic>   notifyNextAnchor(A, D);</italic></p>
<p> <italic>  }</italic></p>
<p><italic>}</italic></p>
<p><italic>Fresh</italic> Protocol first searches the direct path between source node S and destination node D. If there is such path, it informs the source node otherwise it recursively searches intermediate node with the recent encounter with destination node D which can be used for data transmission from S towards D up to the point when data transmission is complete.</p>
</sec>
<sec id="s2_3">
<label>2.3</label>
<title>Literature Review</title>
<p>There have been various research attempts to make opportunistic routing better than the previous one. Some important efforts are listed below:</p>
<p>Sharma et al. [<xref ref-type="bibr" rid="ref-22">22</xref>] proposed a routing protocol named kROp(k&#x2011;Means clustering based routing protocol for opportunistic networks) which uses machine learning techniques in the background for next-hop selection in route discovery during data dissemination. The output delivered by kROp was compared with PRoPHET and other standard opportunistic routing protocols. Results proved kROp as the better option in terms of hop count and delivery probability.</p>
<p>Lakshmi et al. [<xref ref-type="bibr" rid="ref-23">23</xref>] introduced a novel routing model known as SPR (Socialized Proficient Routing) for OppNet using Machine Learning. In this model, intermediate nodes are chosen on the ground of human-social traits to maintain the robustness of the path being selected for data forwarding. Various ML-based classifiers such as Decision-Tree, Neural-Networks, and Support-Vector-Machine are used during the training phase. Simulation results proved good performance using standard parameters.</p>
<p>Kara et al. [<xref ref-type="bibr" rid="ref-24">24</xref>] proposed an algorithm known as position-based hybrid routing algorithm (PBHRA) to exploit the bandwidth and energy consumption at the maximum level. It was implemented in MATLAB and compared with some standard Table-driven and position-based algorithms. The comparative study explained PBHRA outperforms the other algorithms taken.</p>
<p>Lambrinos et al. [<xref ref-type="bibr" rid="ref-25">25</xref>] presented a novel algorithm that is motivated by location-based Social Networks. Programmable controllers were used for route discovery and data transmission. A Portion of Machine learning is also used for training datasets containing the location-based information of nodes present in the Opportunistic network. Implementation of this algorithm delivered good performance on standard parameters over traditional location-based Opportunistic Routing Protocols.</p>
<p>Sharma et al. [<xref ref-type="bibr" rid="ref-26">26</xref>] developed a history-based routing protocol that uses the history of encounters between two nodes for current path selection in Opportunistic Networks using reinforced learning. To simulate this concept, a real mobility trace from INFOCOM-2006 was taken. Simulation results show that this strategy worked efficiently.</p>
<p>Souza et al. [<xref ref-type="bibr" rid="ref-27">27</xref>] introduced the &#x201C;FriendShip and Acquaintanceship Forwarding&#x201D; (FSF) protocol that performs data forwarding based on the Social relationship between the communicating nodes. It was implemented on ONE Simulator to inspect its performance on Message Delivery. The Proposed Protocol scored good results over standard metrics.</p>
<p>Rashidibajgan et al. [<xref ref-type="bibr" rid="ref-28">28</xref>] efficiently explained the advantages of using the history of node movement and interaction with other nodes during data communication. They proposed a Privacy-Preserving History-Based (PPHB) routing algorithm for implementing their proposition. In this approach, Each node participating in the opportunistic Network maintains a <italic>History Table</italic> (HT) which contains geographic knowledge about the other nodes encountered during data dissemination and every node decides after looking up its History Table for the next data communication.</p>
<p>Huang et al. [<xref ref-type="bibr" rid="ref-29">29</xref>] present a new framework based on Kernel regression named PreKR based on the Kernel Regression Technique for Link Prediction in Opportunistic Networks during route discovery. This research aims to enhance the packet delivery ratio by reducing the time consumption in route discovery in a network with dynamic topology. Experimental results showed that the proposed framework outperforms the standard method by 25% with 90% accuracy.</p>
<p>Sharma et al. [<xref ref-type="bibr" rid="ref-30">30</xref>] introduced a reinforced learning-based approach named RLProph for Opportunistic Networks. Its primary objective was to maximize message delivery probability using machine learning and reinforced learning in the background. With the help of simulation, it had been proved that RLProph delivered better performance over standard QoS parameters.</p>
<p>Li et al. [<xref ref-type="bibr" rid="ref-31">31</xref>] presented a new Link Prediction Method named <italic>Combo-Pre</italic> using a combination of machine learning and standard prediction methods. Experimental results proved its superiority over the traditional link prediction methods.</p>
<p>Janku et al. [<xref ref-type="bibr" rid="ref-32">32</xref>] presented the benefits of using unsupervised learning in Cluster Opportunistic Networks. The authors designed a hierarchical routing algorithm with the combination of three different strategies for decision making in route prediction using unsupervised learning techniques of machine learning. Experimental results show its better performance than traditional approaches.</p>
<p>The research in the above-mentioned research papers indicates that there are lots of opportunities to get a better result if machine learning is used with Opportunistic Networks. Keeping this thing in mind, this paper proposes the new routing protocol using Machine Learning in the background as well as adopting the Fresh Routing protocol as the backbone technique.</p>
</sec>
</sec>
<sec id="s3">
<label>3</label>
<title>ML-Fresh</title>
<p>As discussed in previous sections of this paper, <italic>Fresh</italic> Protocol is observed as the best routing protocol among all the variety of routing protocols available in Opportunistic Networks [<xref ref-type="bibr" rid="ref-19">19</xref>]. Literature survey indicates the direction of incorporating machine learning in <italic>Fresh</italic> Protocol for better performance. Therefore, a new routing protocol known as <italic>ML-Fresh</italic> (Machine Learning enabled Fresh) Routing Protocol has been introduced.</p>
<p>Opportunistic Network involves blind forwarding of data to intermediate nodes to send it to the destination node, but, this blind forwarding deteriorates the overall performance of the Network due to unnecessary replication of single data which is supposed to be forwarded to a particular endpoint. This limitation can be removed by forwarding the data only to those nodes which are actual intermediate node during data transmission which can boost the delivery outcome by minimizing the delivery overhead of the whole network. This objective may be achieved by predicting the optimum suited path between source and destination node during data transmission.</p>
<p><italic>ML-Fresh</italic> is based on such methodology. It uses the combination of three prime machine learning methods to predict the route in the dynamic topology of Opportunistic Networks with aim of achieving the best prediction from available options. The Three Machine Learning techniques are Pattern Prediction [<xref ref-type="bibr" rid="ref-33">33</xref>,<xref ref-type="bibr" rid="ref-34">34</xref>], Decision Tree Prediction [<xref ref-type="bibr" rid="ref-35">35</xref>,<xref ref-type="bibr" rid="ref-36">36</xref>], and Adamic-Adar Method [<xref ref-type="bibr" rid="ref-37">37</xref>]. Besides these, <italic>ML-Fresh</italic> also takes inputs from the history of successful encounters between two endpoints as Dhurandher et al. [<xref ref-type="bibr" rid="ref-38">38</xref>] proved it as a crucial factor for efficient routing in Opportunistic Networks.</p>
<p>The functioning of <italic>ML-Fresh</italic> protocol may be classified into the following phases:<list list-type="alpha-lower"><list-item>
<p>Warm-up Phase</p></list-item><list-item>
<p>Preparation Phase</p></list-item><list-item>
<p>Prediction Phase</p></list-item><list-item>
<p>Decision Phase</p></list-item></list></p>
<p>It begins with the <italic>Warm-up Phase</italic> when participating nodes move as per the mobility model chosen and prepare their respective routing tables mentioning their recent encounter experience with other nodes. Like <italic>Fresh</italic> Protocol, <italic>ML-Fresh</italic> Protocol works on Euclidean space. The Formula for calculating Euclidean Distance (ED) [<xref ref-type="bibr" rid="ref-39">39</xref>] between each pair of nodes (a, b) in Set N is</p>
<p><disp-formula id="eqn-1">
<label>(1)</label>
<!--<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-1.png"/><tex-math id="tex-eqn-1"><![CDATA[$$ED = \; \sqrt {\mathop \sum \nolimits_{i = 1}^n {{\left( {{b_i} - \; {a_i}} \right)}^2}}$$]]></tex-math>--><mml:math id="mml-eqn-1" display="block"><mml:mi>E</mml:mi><mml:mi>D</mml:mi><mml:mo>&#x003D;</mml:mo><mml:mspace width="thickmathspace"></mml:mspace><mml:msqrt><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mi>i</mml:mi><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mi>n</mml:mi></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:msup><mml:mrow><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mrow><mml:msub><mml:mi>b</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow><mml:mo>&#x2212;</mml:mo><mml:mspace width="thickmathspace"></mml:mspace><mml:mrow><mml:msub><mml:mi>a</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:mrow><mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt></mml:math>
<!--</alternatives>--></disp-formula></p>
<p>Besides saving recent encounter experiences with other nodes like <italic>Fresh</italic> Protocol, each node keeps the record of its every successful encounter with other nodes additionally in <italic>ML-Fresh</italic>.</p>
<p>The <italic>preparation phase</italic> starts with pattern mining of links between two nodes that are still connected as per the current timestamp t<sub>i</sub>. It forwards such Links to the <italic>Active Updated Links Set</italic> block. It also transfers remaining Links for <italic>Threshold Validity Checks</italic> for validating their usage possibility for future use. After the Threshold check, such Links are categorized and forwarded into two categories. The first category contains those Links which were connected or active for some timestamp t<sub>j</sub> but is not updated as time varies. The second category covers all those links set which were connected for a very few time or never connected. All Links set covered in three different groups are forwarded for further processing in the Prediction Phase as shown in <xref ref-type="fig" rid="fig-3">Fig. 3</xref>.</p>
<p><italic>Prediction Phase</italic> contains three different kinds of Link prediction mechanisms on three different kinds of Links set supplied. Firstly, Links set which are updated as well as active as per current timestamp are processed for pattern prediction for future use and forwarded to the <italic>Decision Phase</italic>. It involves the calculation of the smallest route between two nodes in the network which are not connected directly. Secondly, Decision Tree Prediction is used to process those links set which are not currently updated but were connected sometimes. The decision Tree-based prediction method [<xref ref-type="bibr" rid="ref-35">35</xref>] is one of the most popular Machine Learning-based methods involving the probability of successful communication. After the processing of Decision Tree Prediction, Links set with higher success probability are forwarded further. Lastly, Adamic-Adar Method is used to process those Links set which were connected for a very few time or never connected. Adamic-Adar Method is a very popular method among Machine Learning based Link prediction methods for Complex Networks and is regarded as the best one among the available options [<xref ref-type="bibr" rid="ref-37">37</xref>].</p>
<fig id="fig-3">
<label>Figure 3</label>
<caption>
<title>Framework of ML-fresh</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_19557-fig-3.png"/>
</fig>
<p><italic>Decision Phase</italic> receives three different Links set as Input to the <italic>AI-Enabled Route Decider</italic>. It also takes input from the History of successful encounters between two nodes. After receiving all inputs, <italic>AI-Enabled Route Decider</italic> optimizes and predicts a safe and secure route between two endpoints during data communication.</p>
<p>The working mechanism of <italic>ML_Fresh</italic> between the source node <italic>S</italic> and destination node <italic>D</italic> is shown through the pseudocode written below:</p>
<p><italic>proc ML_FRESH (S,D)</italic> &#x003D;</p>
<p><italic>{</italic></p>
<p> <italic> if (thisnode.ID &#x003D; D) then</italic></p>
<p> <italic> {</italic></p>
<p> <italic>  replyToSource();</italic></p>
<p> <italic> }</italic></p>
<p> <italic>  else</italic></p>
<p> <italic>  {</italic></p>
<p> <italic>  P [] :&#x003D; pattern_prediction(S,D);</italic></p>
<p> <italic>  T [] :&#x003D; decision_tree(S,D);</italic></p>
<p> <italic>  A [] :&#x003D; adamic_adar(S,D);</italic></p>
<p> <italic>  H []:&#x003D; encounter_history(S,D);</italic></p>
<p> <italic>  R []:&#x003D; optimum_route(P,T,A,H);</italic></p>
<p> <italic>  }</italic></p>
<p><italic>}</italic></p>
<p><italic>ML-Fresh</italic> first searches whether the destination node <italic>D</italic> is in direct contact with source node <italic>S</italic> or not. If the two nodes are indirectly in contact, then, the communication starts directly through the If block otherwise four different functions viz. <italic>pattern_prediction(S, D), decision_tree(S, D), adamic_adar(S, D) and encounter_history(S, D)</italic> execute one by one. <italic>pattern_prediction(S, D)</italic> returns all active and updated intermediate node pairs between <italic>S</italic> and <italic>D</italic> to the array <italic>P</italic> using Machine Learning enabled Pattern Prediction mechanism. <italic>decision_tree(S, D)</italic> gives all active but un-updated intermediate node pairs between <italic>S</italic> and <italic>D</italic> to the array <italic>T</italic> using the probability-based decision tree method. <italic>adamic_adar(S, D)</italic> returns all intermediate nodes between <italic>S</italic> and <italic>D</italic> to array <italic>A</italic> using the Adamic-Adar method which is a prime technique for link prediction in complex networks. Moreover, <italic>encounter_history(S, D)</italic> returns the all node pairs between <italic>S</italic> and <italic>D</italic> from the history of successful encounters which involves routing between <italic>S</italic> and <italic>D</italic> to the array <italic>H</italic>. Lastly, all the intermediate node pairs obtained from four different functions described above are pass to <italic>optimum_route(P, T, A, H)</italic> through <italic>P, T, A, H. optimum_route(P, T, A, H)</italic> returns the exact and optimum path between S and D containing intermediate node pairs to the array <italic>R</italic> which can be retrieved for getting the optimized path.</p>
</sec>
<sec id="s4">
<label>4</label>
<title>Findings and Results</title>
<sec id="s4_1">
<label>4.1</label>
<title>Simulation Environment</title>
<p>The performance of the <italic>ML-Fresh</italic> has been evaluated in the Opportunistic Network Environment (ONE) Simulator. This simulator has been chosen because, in accordance with Kuppusamy et al. [<xref ref-type="bibr" rid="ref-40">40</xref>], ONE is the most popular simulator used by researchers for Opportunistic Networks. ONE [<xref ref-type="bibr" rid="ref-41">41</xref>] is a simulator that provides visual output as well as trace files which can be analyzed through a plotting tool like Graphviz. The main advantage of using ONE Simulator over other simulators is that it easily generates event logs of even difficult mobility scenarios which are very much closer to the real-life situation which makes it the most suitable tool for applying in this research.</p>
<p>The performance delivered by the <italic>ML-Fresh</italic> is compared with the performance delivered by <italic>Fresh</italic> Routing Protocol in Opportunistic Network under common parameters listed in the next sub-section.</p>
</sec>
<sec id="s4_2">
<label>4.2</label>
<title>Common Parameters during Simulation</title>
<p>Some parameters that have been kept constant to achieve comparative performance between <italic>Fresh</italic> Protocol and <italic>ML-Fresh</italic> Protocol have been described in <xref ref-type="table" rid="table-1">Tab. 1</xref>.</p>
<table-wrap id="table-1">
<label>Table 1</label>
<caption>
<title>Common parameters used during simulation</title>
</caption>
<table>
<colgroup>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>Parameters</th>
<th>Values</th>
</tr>
</thead>
<tbody>
<tr>
<td><bold>Simulation Area</bold></td>
<td>12,000 x 10,000 Sq. Meters (120 Square KMs)</td>
</tr>
<tr>
<td><bold>Simulation Time</bold></td>
<td>1 Week</td>
</tr>
<tr>
<td><bold>Movement Model</bold></td>
<td>Cluster Movement</td>
</tr>
<tr>
<td><bold>Time-To-Live (per Message)</bold></td>
<td>1 Day (1440 Minutes)</td>
</tr>
<tr>
<td><bold>Scenario Update Interval</bold></td>
<td>0.1 Second</td>
</tr>
<tr>
<td><bold>Communication Medium</bold></td>
<td>Bluetooth, Wi-Fi (High Speed)</td>
</tr>
<tr>
<td><bold>Bluetooth Interface Speed</bold></td>
<td>250 Kbps</td>
</tr>
<tr>
<td><bold>Bluetooth Interface Range</bold></td>
<td>10 Meters</td>
</tr>
<tr>
<td><bold>Bluetooth Interface Scan Interval</bold></td>
<td>32 Seconds</td>
</tr>
<tr>
<td><bold>Wi-Fi Interface Speed</bold></td>
<td>500 Kbps</td>
</tr>
<tr>
<td><bold>Wi-Fi Interface Range</bold></td>
<td>10 Meters</td>
</tr>
<tr>
<td><bold>Wi-Fi Interface Interval</bold></td>
<td>64 Seconds</td>
</tr>
<tr>
<td><bold>Node movement speed</bold></td>
<td>From 0.5 m/s to 1.5 m/s</td>
</tr>
<tr>
<td><bold>Transmission Range</bold></td>
<td>10 Meters</td>
</tr>
<tr>
<td><bold>Message Size</bold></td>
<td>From 500 KB to 1 MB</td>
</tr>
<tr>
<td><bold>Warm-Up period</bold></td>
<td>1 Hour (3600 Seconds)</td>
</tr>
<tr>
<td><bold>Operating System</bold></td>
<td>The Mentioned research is carried out on MS Windows 10 Platform, but, the ONE simulator is a Java-based application, therefore, its performance is independent of the platform being used.</td>
</tr>
<tr>
<td><bold>Initial Energy Provided</bold></td>
<td>10 Lacs Units</td>
</tr>
<tr>
<td><bold>Energy Consumed in Data Transmission</bold></td>
<td>0.10 Units</td>
</tr>
<tr>
<td><bold>Energy Consumed in Data Receiving</bold></td>
<td>0.07 Units</td>
</tr>
<tr>
<td><bold>Energy Consumed in Network Scanning for Data Communication</bold></td>
<td>0.05 Units</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s4_3">
<label>4.3</label>
<title>Performance Metrics</title>
<p>Following Performance Metrics are chosen for the evaluation of <italic>ML-Fresh</italic> with <italic>Fresh</italic> Protocol:</p>
<p><bold><italic>a) Average Energy Consumption:</italic></bold></p>
<p>It is the energy consumed by the whole network on the average ground. The primary objective of every network researcher is to reduce it up to the maximum extent. It is inversely proportional to the network lifetime as the participating nodes have limited power in general.</p>
<p>Mathematically, it can be denoted as:</p>
<p><disp-formula id="eqn-2">
<label>(2)</label>
<!--<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-2.png"/><tex-math id="tex-eqn-2"><![CDATA[$$\bi{\; }{\bi{E}_{\bi{Avg}}} = \displaystyle{{\mathop \sum \nolimits_{\bi{i} = 1}^{\bi{i} = \bi{n}} {\bi{E}_{\bi{Transmitte}{\bi{d}_{\bi{i\; \; }}}}} + \; \mathop \sum \nolimits_{\bi{i} = 1}^{\bi{i} = \bi{n}} {\bi{E}_{\bi{Recieve}{\bi{d}_{\bi{i\; \; }}}}} + \; \mathop \sum \nolimits_{\bi{i} = 1}^{\bi{i} = \bi{n}} {\bi{E}_{\bi{Sca}{\bi{n}_{\bi{i\; \; }}}}}} \over \bi{n}}$$]]></tex-math>--><mml:math id="mml-eqn-2" display="block"><mml:mspace width="thickmathspace"></mml:mspace><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">E</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">A</mml:mi><mml:mi mathvariant="bold-italic">v</mml:mi><mml:mi mathvariant="bold-italic">g</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mfrac><mml:mrow><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mo>&#x003D;</mml:mo><mml:mi mathvariant="bold-italic">n</mml:mi></mml:mrow></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">E</mml:mi><mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">T</mml:mi><mml:mi mathvariant="bold-italic">r</mml:mi><mml:mi mathvariant="bold-italic">a</mml:mi><mml:mi mathvariant="bold-italic">n</mml:mi><mml:mi mathvariant="bold-italic">s</mml:mi><mml:mi mathvariant="bold-italic">m</mml:mi><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mi mathvariant="bold-italic">t</mml:mi><mml:mi mathvariant="bold-italic">t</mml:mi><mml:mi mathvariant="bold-italic">e</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">d</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mspace width="thickmathspace"></mml:mspace><mml:mspace width="thickmathspace"></mml:mspace></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow><mml:mo>&#x002B;</mml:mo><mml:mspace width="thickmathspace"></mml:mspace><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mo>&#x003D;</mml:mo><mml:mi mathvariant="bold-italic">n</mml:mi></mml:mrow></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">E</mml:mi><mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">R</mml:mi><mml:mi mathvariant="bold-italic">e</mml:mi><mml:mi mathvariant="bold-italic">c</mml:mi><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mi mathvariant="bold-italic">e</mml:mi><mml:mi mathvariant="bold-italic">v</mml:mi><mml:mi mathvariant="bold-italic">e</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">d</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mspace width="thickmathspace"></mml:mspace><mml:mspace width="thickmathspace"></mml:mspace></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow><mml:mo>&#x002B;</mml:mo><mml:mspace width="thickmathspace"></mml:mspace><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mo>&#x003D;</mml:mo><mml:mi mathvariant="bold-italic">n</mml:mi></mml:mrow></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">E</mml:mi><mml:mrow><mml:mrow><mml:mi mathvariant="bold-italic">S</mml:mi><mml:mi mathvariant="bold-italic">c</mml:mi><mml:mi mathvariant="bold-italic">a</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mi mathvariant="bold-italic">n</mml:mi><mml:mrow><mml:mi mathvariant="bold-italic">i</mml:mi><mml:mspace width="thickmathspace"></mml:mspace><mml:mspace width="thickmathspace"></mml:mspace></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow></mml:mrow><mml:mi mathvariant="bold-italic">n</mml:mi></mml:mfrac></mml:mrow></mml:mstyle></mml:math>
<!--</alternatives>--></disp-formula></p>
<p><bold><italic>b) Load-Delivery Ratio</italic></bold>:</p>
<p>Load delivery ratio (LDR) is characterized as the proportion of data packets conveyed effectively to destination nodes and the total number of data packets produced for those destinations. LDR portrays the packet loss rate, which restricts the throughput of the network. The higher the delivery ratio, the better the performance of the routing protocol. LDR is determined as written below:</p>
<p><disp-formula id="eqn-3">
<label>(3)</label>
<!--<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-3.png"/><tex-math id="tex-eqn-3"><![CDATA[$${\rm LDR} = \displaystyle{{\mathop \sum \nolimits_{{\rm i} = 1}^{{\rm i} = {\rm n}} {{\rm M}_{{\rm recieve}{{\rm d}_{\rm i}}}}} \over {\mathop \sum \nolimits_{{\rm i} = 1}^{{\rm i} = {\rm n}} {{\rm M}_{{\rm sen}{{\rm t}_{\rm i}}}}}} \times 100$$]]></tex-math>--><mml:math id="mml-eqn-3" display="block"><mml:mrow><mml:mi mathvariant="normal">L</mml:mi><mml:mi mathvariant="normal">D</mml:mi><mml:mi mathvariant="normal">R</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mstyle scriptlevel="0" displaystyle="true"><mml:mrow><mml:mfrac><mml:mrow><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mrow><mml:mi mathvariant="normal">n</mml:mi></mml:mrow></mml:mrow></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">r</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">i</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">v</mml:mi><mml:mi mathvariant="normal">e</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">d</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow></mml:mrow><mml:mrow><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mrow><mml:mi mathvariant="normal">n</mml:mi></mml:mrow></mml:mrow></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">s</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">n</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:mfrac></mml:mrow><mml:mo>&#x00D7;</mml:mo><mml:mn>100</mml:mn></mml:mstyle></mml:math>
<!--</alternatives>--></disp-formula></p>
<p><bold><italic>c) Average Latency:</italic></bold></p>
<p>Average Latency is the average time consumed in the successful delivery of all messages transmitted between two endpoints during the complete network lifetime. High value of Latency is not considered desirable for a Good Network. The formula for its calculation is given below:</p>
<p><disp-formula id="eqn-4">
<label>(4)</label>
<!--<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-4.png"/><tex-math id="tex-eqn-4"><![CDATA[$${\rm Latenc}{{\rm y}_{{\rm Avg}}} = {\rm \; }\displaystyle{{\mathop \sum \nolimits_{{\rm i} = 1}^{{\rm i} = {\rm n}} {{\rm T}_{{\rm successful\; deliver}{{\rm y}_{\rm i}}}}} \over {\mathop \sum \nolimits_{{\rm i} = 1}^{{\rm i} = {\rm n}} {{\rm M}_{{\rm Deliver}{{\rm d}_{\rm i}}}}}}$$]]></tex-math>--><mml:math id="mml-eqn-4" display="block"><mml:mrow><mml:mi mathvariant="normal">L</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">t</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">n</mml:mi><mml:mi mathvariant="normal">c</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">y</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">A</mml:mi><mml:mi mathvariant="normal">v</mml:mi><mml:mi mathvariant="normal">g</mml:mi></mml:mrow></mml:mrow></mml:msub></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mrow><mml:mspace width="thickmathspace"></mml:mspace></mml:mrow><mml:mstyle scriptlevel="0" displaystyle="true"><mml:mrow><mml:mfrac><mml:mrow><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mrow><mml:mi mathvariant="normal">n</mml:mi></mml:mrow></mml:mrow></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">T</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">s</mml:mi><mml:mi mathvariant="normal">u</mml:mi><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">s</mml:mi><mml:mi mathvariant="normal">s</mml:mi><mml:mi mathvariant="normal">f</mml:mi><mml:mi mathvariant="normal">u</mml:mi><mml:mi mathvariant="normal">l</mml:mi><mml:mspace width="thickmathspace"></mml:mspace><mml:mi mathvariant="normal">d</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">l</mml:mi><mml:mi mathvariant="normal">i</mml:mi><mml:mi mathvariant="normal">v</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">r</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">y</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow></mml:mrow><mml:mrow><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mrow><mml:mi mathvariant="normal">n</mml:mi></mml:mrow></mml:mrow></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">D</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">l</mml:mi><mml:mi mathvariant="normal">i</mml:mi><mml:mi mathvariant="normal">v</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">r</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">d</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:mfrac></mml:mrow></mml:mstyle></mml:math>
<!--</alternatives>--></disp-formula></p>
<p><bold><italic>d) Error Rate:</italic></bold></p>
<p>Error Rate is the average number of lost messages during data transmission throughout the network lifetime. A good network has the least Error Rate. It can be calculated by the formula shown below:</p>
<p><disp-formula id="eqn-5">
<label>(5)</label>
<!--<alternatives>
<graphic mimetype="image" mime-subtype="png" xlink:href="eqn-5.png"/><tex-math id="tex-eqn-5"><![CDATA[$${\rm Error\; Rate} = {\rm \; }\displaystyle{{\mathop \sum \nolimits_{{\rm i} = 1}^{{\rm i} = {\rm n}} \left( {{{\rm M}_{{\rm create}{{\rm d}_{\rm i}}}} - {\rm \; }{{\rm M}_{{\rm Successfully\; delivere}{{\rm d}_{\rm i}}}}} \right)} \over {\mathop \sum \nolimits_{{\rm i} = 1}^{{\rm i} = {\rm n}} {{\rm M}_{{\rm create}{{\rm d}_{\rm i}}}}}}{\; \; \; \; \; }$$]]></tex-math>--><mml:math id="mml-eqn-5" display="block"><mml:mrow><mml:mi mathvariant="normal">E</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mi mathvariant="normal">o</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mspace width="thickmathspace"></mml:mspace><mml:mi mathvariant="normal">R</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">t</mml:mi><mml:mi mathvariant="normal">e</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mrow><mml:mspace width="thickmathspace"></mml:mspace></mml:mrow><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mfrac><mml:mrow><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mrow><mml:mi mathvariant="normal">n</mml:mi></mml:mrow></mml:mrow></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">t</mml:mi><mml:mi mathvariant="normal">e</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">d</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow><mml:mo>&#x2212;</mml:mo><mml:mrow><mml:mspace width="thickmathspace"></mml:mspace></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">S</mml:mi><mml:mi mathvariant="normal">u</mml:mi><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">s</mml:mi><mml:mi mathvariant="normal">s</mml:mi><mml:mi mathvariant="normal">f</mml:mi><mml:mi mathvariant="normal">u</mml:mi><mml:mi mathvariant="normal">l</mml:mi><mml:mi mathvariant="normal">l</mml:mi><mml:mi mathvariant="normal">y</mml:mi><mml:mspace width="thickmathspace"></mml:mspace><mml:mi mathvariant="normal">d</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">l</mml:mi><mml:mi mathvariant="normal">i</mml:mi><mml:mi mathvariant="normal">v</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mi mathvariant="normal">e</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">d</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:mrow><mml:mrow><mml:msubsup><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow><mml:mo>&#x003D;</mml:mo><mml:mrow><mml:mi mathvariant="normal">n</mml:mi></mml:mrow></mml:mrow></mml:msubsup><mml:mo>&#x2061;</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">t</mml:mi><mml:mi mathvariant="normal">e</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">d</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:mfrac></mml:mrow><mml:mrow><mml:mspace width="thickmathspace"></mml:mspace><mml:mspace width="thickmathspace"></mml:mspace><mml:mspace width="thickmathspace"></mml:mspace><mml:mspace width="thickmathspace"></mml:mspace><mml:mspace width="thickmathspace"></mml:mspace></mml:mrow></mml:mstyle></mml:math>
<!--</alternatives>--></disp-formula></p>
</sec>
<sec id="s4_4">
<label>4.4</label>
<title>Results</title>
<p>Following are the comparative analysis of the existing <italic>Fresh</italic> Protocol along with the <italic>ML-Fresh</italic> Protocol on the ground of mentioned parameters:</p>
<p><bold>a) <italic>Average Energy Consumption:</italic></bold></p>
<p>As depicted in <xref ref-type="fig" rid="fig-4">Fig. 4</xref>, The <italic>ML-Fresh</italic> exhibits a good performance over <italic>Fresh</italic> Protocol on the criteria of Average Energy consumed during data communication. It gives the best performance i.e., 71% better than <italic>Fresh</italic> protocol when the number of nodes is 200. In average count, <italic>ML-Fresh</italic> outperforms <italic>Fresh</italic> Protocol by 11.65% on the ground of mentioned parameter.</p>
<fig id="fig-4">
<label>Figure 4</label>
<caption>
<title>Protocols&#x2019; performance based on Average Energy Consumption versus Number of Nodes</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_19557-fig-4.png"/>
</fig>
<p><bold><italic>b) Load-Delivery Ratio:</italic></bold></p>
<p>The <italic>ML-Fresh</italic> proved itself beyond the expectations on the criteria of Load Delivery Ratio. Through <xref ref-type="fig" rid="fig-5">Fig. 5</xref>, it was observed during simulation of both protocols along with the varying number of node densities that Load delivery Ratio (LDR) decreases as node density increases in the case of <italic>Fresh</italic> Protocol. It starts with LDR&#x003D; 97.99 with node density of 100 and ends with LDR&#x003D; 7.91 with a node density of 1000. On the contrary, LDR remains around the same i.e. 95.8 (Average) with all different cases of node densities in the case of <italic>ML-Fresh</italic>.</p>
<fig id="fig-5">
<label>Figure 5</label>
<caption>
<title>Protocols&#x2019; performance based on Load Delivery Ratio versus Number of Nodes</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_19557-fig-5.png"/>
</fig>
<p><bold><italic>c) Average Latency:</italic></bold></p>
<p>After the simulation of both protocols with different Node Densities, It may be easily observed from <xref ref-type="fig" rid="fig-6">Fig. 6</xref>, <italic>Fresh</italic> Protocol possesses more Latency than the <italic>ML-Fresh</italic>. However, The Latency difference between the two mentioned protocols decreases gradually as the node density increases. However, the <italic>ML-Fresh</italic> Protocol leads <italic>Fresh</italic> Protocol by 42% on average.</p>
<fig id="fig-6">
<label>Figure 6</label>
<caption>
<title>Protocols&#x2019; performance based on Average Latency versus Number of Nodes</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_19557-fig-6.png"/>
</fig>
<p><bold><italic>d) Error Rate:</italic></bold></p>
<p>Error Rate of any protocol decides the possibility of successful delivery of the desired data packet to the destined node. Lesser the Error Rate, communication will be more safe and secure. As <xref ref-type="fig" rid="fig-7">Fig. 7</xref> is showing the clear huge difference between the Error Rate of <italic>Fresh</italic> Protocol and <italic>ML-Fresh</italic> Protocol, It may be easily concluded that on average, <italic>ML-Fresh</italic> has 19 times less Error Rate than <italic>Fresh</italic> Protocol.</p>
<fig id="fig-7">
<label>Figure 7</label>
<caption>
<title>Protocols&#x2019; performance based on Error Rate versus Number of Nodes</title>
</caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_19557-fig-7.png"/>
</fig>
</sec>
</sec>
<sec id="s5">
<label>5</label>
<title>Conclusion</title>
<p><italic>ML-Fresh</italic> protocol is inspired by <italic>Fresh</italic> Protocol which uses recent encounter experience for data transmission. <italic>ML-Fresh</italic> uses all three prime mechanisms from Machine Learning for Link Prediction in Opportunistic Networks. The simulation observations proved it as significant over <italic>Fresh</italic> Protocol. <italic>ML-Fresh</italic> delivered noteworthy performance on the ground of Average Energy Consumed, Load Delivery Ratio, Average Latency, and Error Rate. It is believed that <italic>ML-Fresh</italic> Protocol will motivate future researchers for further research.</p>
</sec>
</body>
<back>
<ack>
<p>The authors appreciate the J. C. Bose University of Science &#x0026; Technology, YMCA, Faridabad, India, for providing research resources and equipment to encourage research among research scholars and faculty members.</p>
</ack><fn-group>
<fn fn-type="other">
<p><bold>Funding Statement:</bold> The authors received no specific funding for this study.</p>
</fn>
<fn fn-type="conflict">
<p><bold>Conflicts of Interest:</bold> The authors declare that they have no conflicts of interest to report regarding the present study.</p>
</fn>
</fn-group>
<ref-list content-type="authoryear">
<title>References</title>
<ref id="ref-1">
<label>1</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>N.</given-names> 
<surname>Kaur</surname></string-name> and <string-name>
<given-names>G.</given-names> 
<surname>Mathur</surname></string-name>
</person-group>, &#x201C;
<article-title>Opportunistic networks: A review</article-title>,&#x201D; 
<source>IOSR Journal of Computer Engineering</source>, vol. 
<volume>18</volume>, no. 
<issue>2</issue>, pp. 
<fpage>20</fpage>&#x2013;
<lpage>26</lpage>, 
<year>2016</year>.</mixed-citation>
</ref>
<ref id="ref-2">
<label>2</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>N. S. S.</given-names> 
<surname>Farheen</surname></string-name> and <string-name>
<given-names>A.</given-names> 
<surname>Jain</surname></string-name>
</person-group>, &#x201C;
<article-title>Improved routing in manet with optimized multi path routing fine tuned with hybrid modeling</article-title>,&#x201D; 
<source>Journal of King Saud University-Computer and Information Sciences</source>, pp. 1&#x2013;8, 
<year>2020</year>.</mixed-citation>
</ref>
<ref id="ref-3">
<label>3</label><mixed-citation publication-type="book">
<person-group person-group-type="author"><string-name>
<given-names>P.</given-names> 
<surname>Sethi</surname></string-name>
</person-group>, &#x201C;<article-title>Swarm intelligence for clustering in wireless sensor networks</article-title>,&#x201D; in 
<source>Swarm Intelligence Optimization: Algorithms and Applications</source>. 
<publisher-loc>Hoboken, NJ, USA</publisher-loc>: 
<publisher-name>Wiley, Chapter 13</publisher-name>, pp. 
<fpage>263</fpage>&#x2013;
<lpage>273, </lpage>
<year>2020. </year><uri>https://onlinelibrary.wiley.com/doi/abs/10.1002/9781119778868.ch13</uri></mixed-citation>
</ref>
<ref id="ref-4">
<label>4</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>P.</given-names> 
<surname>Garg</surname></string-name>, <string-name>
<given-names>A.</given-names> 
<surname>Dixit</surname></string-name> and <string-name>
<given-names>P.</given-names> 
<surname>Sethi</surname></string-name>
</person-group>, &#x201C;
<article-title>Wireless sensor networks: an insight review</article-title>,&#x201D; 
<source>International Journal of Advanced Science and Technology</source>, vol. 
<volume>28</volume>, no. 
<issue>15</issue>, pp. 
<fpage>612</fpage>&#x2013;
<lpage>627</lpage>, 
<year>2019</year>.</mixed-citation>
</ref>
<ref id="ref-5">
<label>5</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>P.</given-names> 
<surname>Yuan</surname></string-name>, <string-name>
<given-names>L.</given-names> 
<surname>Fan</surname></string-name>, <string-name>
<given-names>P.</given-names> 
<surname>Liu</surname></string-name> and <string-name>
<given-names>S.</given-names> 
<surname>Tang</surname></string-name>
</person-group>, &#x201C;
<article-title>Recent progress in routing protocols of mobile opportunistic networks: A clear taxonomy, analysis and evaluation</article-title>,&#x201D; 
<source>Journal of Network and Computer Applications</source>, vol. 
<volume>62</volume>, pp. 
<fpage>163</fpage>&#x2013;
<lpage>170</lpage>, 
<year>2016</year>.</mixed-citation>
</ref>
<ref id="ref-6">
<label>6</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>C.</given-names> 
<surname>Prabha</surname></string-name>, <string-name>
<given-names>S.</given-names> 
<surname>Kumar</surname></string-name> and <string-name>
<given-names>R.</given-names> 
<surname>Khanna</surname></string-name>
</person-group>, &#x201C;
<article-title>Analysis of routing and forwarding protocols in opportunistic networks</article-title>,&#x201D; 
<source>Procedia Computer Science</source>, vol. 
<volume>85</volume>, pp. 
<fpage>891</fpage>&#x2013;
<lpage>898</lpage>, 
<year>2016</year>.</mixed-citation>
</ref>
<ref id="ref-7">
<label>7</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>A.</given-names> 
<surname>Nayyar</surname></string-name>, <string-name>
<given-names>R. S.</given-names> 
<surname>Batth</surname></string-name>, <string-name>
<given-names>D. B.</given-names> 
<surname>Ha</surname></string-name> and <string-name>
<given-names>G.</given-names> 
<surname>Sussendran</surname></string-name>
</person-group>, &#x201C;
<article-title>Opportunistic networks: Present scenario-a mirror review</article-title>,&#x201D; 
<source>International Journal of Communication Networks and Information Security</source>, vol. 
<volume>10</volume>, no. 
<issue>1</issue>, pp. 
<fpage>223</fpage>&#x2013;
<lpage>241</lpage>, 
<year>2018</year>.</mixed-citation>
</ref>
<ref id="ref-8">
<label>8</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>P.</given-names> 
<surname>Garg</surname></string-name>, <string-name>
<given-names>A.</given-names> 
<surname>Dixit</surname></string-name> and <string-name>
<given-names>P.</given-names> 
<surname>Sethi</surname></string-name>
</person-group>, &#x201C;
<article-title>Opportunistic networks: Protocols, applications &#x0026; simulation trends</article-title>,&#x201D; in <conf-name>Proceedings of the 4th Int. Conf. on Innovative Computing and Communication (ICICC)</conf-name>, 
<publisher-loc>New Delhi, India. </publisher-loc>
<year>2021</year>. </mixed-citation>
</ref>
<ref id="ref-9">
<label>9</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>M.</given-names> 
<surname>Saloni</surname></string-name>, <string-name>
<given-names>C.</given-names> 
<surname>Julien</surname></string-name>, <string-name>
<given-names>A. L.</given-names> 
<surname>Murphy</surname></string-name> and <string-name>
<given-names>G. P.</given-names> 
<surname>Picco</surname></string-name>
</person-group>, &#x201C;
<article-title>Lasso: A device-to-device group monitoring service for smart cities</article-title>,&#x201D; in <conf-name>Proc. of the International Smart Cities Conf. (ISC2)</conf-name>, 
<publisher-name>IEEE</publisher-name>, pp. 
<fpage>1</fpage>&#x2013;
<lpage>6</lpage>, 
<year>2017</year>. </mixed-citation>
</ref>
<ref id="ref-10">
<label>10</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>G.</given-names> 
<surname>Menon</surname></string-name> and <string-name>
<given-names>P. M. J.</given-names> 
<surname>Prathap</surname></string-name>
</person-group>, &#x201C;
<article-title>Comparative analysis of opportunistic routing protocols for underwater acoustic sensor networks</article-title>,&#x201D; in <conf-name>Proc. of the Int. Conf. On Emerging Technological Trends (ICETT)</conf-name>, pp. 
<fpage>1</fpage>&#x2013;
<lpage>5</lpage>, 
<year>2016</year>. </mixed-citation>
</ref>
<ref id="ref-11">
<label>11</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>C.</given-names> 
<surname>Detweiller</surname></string-name>, <string-name>
<given-names>I.</given-names> 
<surname>Vasilescu</surname></string-name> and <string-name>
<given-names>D.</given-names> 
<surname>Rus</surname></string-name>
</person-group>, &#x201C;
<article-title>An underwater sensor network with dual communications, sensing, and mobility</article-title>,&#x201D; in <conf-name>Proc. of the Oceans 2007</conf-name>, 
<publisher-loc>Europe</publisher-loc>, pp. 
<fpage>1</fpage>&#x2013;
<lpage>6</lpage>, 
<year>2007</year>. </mixed-citation>
</ref>
<ref id="ref-12">
<label>12</label><mixed-citation publication-type="book">
<person-group person-group-type="author"><string-name>
<given-names>M.</given-names> 
<surname>Martonosi</surname></string-name>
</person-group>, 
<source>The princeton ZebraNet project: sensor networks for wildlife tracking</source>. 
<publisher-name>Princeton University</publisher-name>, pp. 
<fpage>2</fpage>&#x2013;
<lpage>7</lpage>, 
<year>2004</year>.</mixed-citation>
</ref>
<ref id="ref-13">
<label>13</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>T.</given-names> 
<surname>Small</surname></string-name> and <string-name>
<given-names>Z. J.</given-names> 
<surname>Haas</surname></string-name>
</person-group>, &#x201C;
<article-title>The shared wireless infostation model: A new ad hoc networking paradigm (or where there is a whale, there is a way)</article-title>,&#x201D; in <conf-name>Proc. of the 4th ACM Int. Sym. On Mobile Ad Hoc Networking &#x0026; Computing</conf-name>, pp. 
<fpage>233</fpage>&#x2013;
<lpage>244</lpage>, 
<year>2003</year>. </mixed-citation>
</ref>
<ref id="ref-14">
<label>14</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>L.</given-names> 
<surname>Wood</surname></string-name>, <string-name>
<given-names>W. M.</given-names> 
<surname>Eddy</surname></string-name>, <string-name>
<given-names>W.</given-names> 
<surname>Ivancic</surname></string-name>, <string-name>
<given-names>J.</given-names> 
<surname>McKim</surname></string-name> and <string-name>
<given-names>C.</given-names> 
<surname>Jackson</surname></string-name>
</person-group>, &#x201C;
<article-title>Saratoga: a delay-tolerant networking convergence layer with efficient link utilization</article-title>,&#x201D; in <conf-name>Proc. of the International Workshop on Satellite and Space Communications</conf-name>, pp. 
<fpage>168</fpage>&#x2013;
<lpage>172</lpage>, 
<year>2007</year>. </mixed-citation>
</ref>
<ref id="ref-15">
<label>15</label><mixed-citation publication-type="other"><uri>https://www.airbornewirelessnetwork.com/index</uri>. 
<comment>asp#advantages (Accessed on Februray 10, 2021)</comment>.</mixed-citation>
</ref>
<ref id="ref-16">
<label>16</label><mixed-citation publication-type="other"><uri>https://www.nasa.gov/ mission_pages/ station/ research/ experiments/ explorer/ Investigation. html?#id &#x003D;717 </uri>
<comment>(Accessed on Februray 10, 2021)</comment>.</mixed-citation>
</ref>
<ref id="ref-17">
<label>17</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>M.</given-names> 
<surname>Alajeely</surname></string-name>, <string-name>
<given-names>R.</given-names> 
<surname>Doss</surname></string-name> and <string-name>
<given-names>A.</given-names> 
<surname>Ahmad</surname></string-name>
</person-group>, &#x201C;
<article-title>Routing protocols in opportunistic networks-a survey</article-title>,&#x201D; 
<source>IETE Technical Review</source>, vol. 
<volume>35</volume>, no. 
<issue>4</issue>, pp. 
<fpage>369</fpage>&#x2013;
<lpage>387</lpage>, 
<year>2018</year>.</mixed-citation>
</ref>
<ref id="ref-18">
<label>18</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>V.</given-names> 
<surname>Juyal</surname></string-name>, <string-name>
<given-names>N.</given-names> 
<surname>Pandey</surname></string-name> and <string-name>
<given-names>R.</given-names> 
<surname>Saggar</surname></string-name>
</person-group>, &#x201C;
<article-title>Impact of varying buffer space for routing protocols in delay tolerant networks</article-title>,&#x201D; in <conf-name>Proc. of the International Conf. on Communication and Signal Processing (ICCSP)</conf-name>, pp. 
<fpage>2152</fpage>&#x2013;
<lpage>2156</lpage>, 
<year>2016</year>. </mixed-citation>
</ref>
<ref id="ref-19">
<label>19</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>P.</given-names> 
<surname>Garg</surname></string-name>, <string-name>
<given-names>A.</given-names> 
<surname>Dixit</surname></string-name>, <string-name>
<given-names>P.</given-names> 
<surname>Sethi</surname></string-name> and <string-name>
<given-names>P. R.</given-names> 
<surname>Pinheiro</surname></string-name>
</person-group>, &#x201C;
<article-title>Impact of node density on the QoS parameters of routing protocols in opportunistic networks for smart spaces</article-title>,&#x201D; 
<source>Mobile Information Systems</source>, vol. 2020, pp. 1&#x2013;18, 
<year>2020</year>.</mixed-citation>
</ref>
<ref id="ref-20">
<label>20</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>P.</given-names> 
<surname>Garg</surname></string-name>, <string-name>
<given-names>A.</given-names> 
<surname>Dixit</surname></string-name> and <string-name>
<given-names>P.</given-names> 
<surname>Sethi</surname></string-name>
</person-group>, &#x201C;
<article-title>Performance comparison of fresh and spray &#x0026; wait protocol through one simulator</article-title>,&#x201D; 
<source>Information Technology in Industry</source>, vol. 
<volume>9</volume>, no. 
<issue>2</issue>, pp. 
<fpage>452</fpage>&#x2013;
<lpage>457</lpage>, 
<year>2021</year>.</mixed-citation>
</ref>
<ref id="ref-21">
<label>21</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>H.</given-names> 
<surname>Dubois-Ferriere</surname></string-name>, <string-name>
<given-names>M.</given-names> 
<surname>Grossglauser</surname></string-name> and <string-name>
<given-names>M.</given-names> 
<surname>Vetterli</surname></string-name>
</person-group>, &#x201C;
<article-title>Age matters: efficient route discovery in mobile ad hoc networks using encounter ages</article-title>,&#x201D; in <conf-name>Proc. of the 4th ACM Int. Sym. On Mobile Ad Hoc Networking &#x0026; Computing</conf-name>, pp. 
<fpage>257</fpage>&#x2013;
<lpage>266</lpage>, 
<year>2003</year>. </mixed-citation>
</ref>
<ref id="ref-22">
<label>22</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>D. K.</given-names> 
<surname>Sharma</surname></string-name>, <string-name>
<given-names>S. K.</given-names> 
<surname>Dhurandher</surname></string-name>, <string-name>
<given-names>D.</given-names> 
<surname>Agarwal</surname></string-name> and <string-name>
<given-names>K.</given-names> 
<surname>Arora</surname></string-name>
</person-group>, &#x201C;
<article-title>kROp: k-Means clustering based routing protocol for opportunistic networks</article-title>,&#x201D; 
<source>Journal of Ambient Intelligence and Humanized Computing</source>, vol. 
<volume>10</volume>, no. 
<issue>4</issue>, pp. 
<fpage>1289</fpage>&#x2013;
<lpage>1306</lpage>, 
<year>2019</year>.</mixed-citation>
</ref>
<ref id="ref-23">
<label>23</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>V. R. V.</given-names> 
<surname>Lakshmi</surname></string-name> and <string-name>
<given-names>G. K.</given-names> 
<surname>Thonnuthodi</surname></string-name>
</person-group>, &#x201C;
<article-title>Socialized proficient routing in opportunistic mobile network using machine learning techniques</article-title>,&#x201D; 
<source>International Journal of Intelligent Engineering and Systems</source>, vol. 
<volume>13</volume>, no. 
<issue>4</issue>, pp. 
<fpage>434</fpage>&#x2013;
<lpage>445</lpage>, 
<year>2020</year>.</mixed-citation>
</ref>
<ref id="ref-24">
<label>24</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>R.</given-names> 
<surname>Kara</surname></string-name>, <string-name>
<given-names>I.</given-names> 
<surname>Ozcelik</surname></string-name> and <string-name>
<given-names>H.</given-names> 
<surname>Ekiz</surname></string-name>
</person-group>, &#x201C;
<article-title>A new routing algorithm in MANETs: Position based hybrid routing</article-title>,&#x201D; 
<source>Scientific Research and Essays</source>, vol. 
<volume>5</volume>, no. 
<issue>3</issue>, pp. 
<fpage>328</fpage>&#x2013;
<lpage>338</lpage>, 
<year>2010</year>.</mixed-citation>
</ref>
<ref id="ref-25">
<label>25</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>L.</given-names> 
<surname>Lambrinos</surname></string-name> and <string-name>
<given-names>P.</given-names> 
<surname>Kosmides</surname></string-name>
</person-group>, &#x201C;
<article-title>Enhancing opportunistic networking using location based social networks</article-title>,&#x201D; in <conf-name>Proc. of the 8th ACM Int. Workshop on Hot Topics in Planet-scale mobile computing and online Social networking</conf-name>, pp. 
<fpage>19</fpage>&#x2013;
<lpage>24</lpage>, 
<year>2016</year>. </mixed-citation>
</ref>
<ref id="ref-26">
<label>26</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>D. K.</given-names> 
<surname>Sharma</surname></string-name>, <string-name>
<given-names>S.</given-names> 
<surname>Gupta</surname></string-name>, <string-name>
<given-names>S.</given-names> 
<surname>Malik</surname></string-name> and <string-name>
<given-names>R.</given-names> 
<surname>Kumar</surname></string-name>
</person-group>, &#x201C;
<article-title>Latency-aware reinforced routing for opportunistic networks</article-title>,&#x201D; 
<source>IET Communications</source>, vol. 
<volume>14</volume>, no. 
<issue>17</issue>, pp. 
<fpage>2981</fpage>&#x2013;
<lpage>2989</lpage>, 
<year>2020</year>.</mixed-citation>
</ref>
<ref id="ref-27">
<label>27</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>C.</given-names> 
<surname>Souza</surname></string-name>, <string-name>
<given-names>E.</given-names> 
<surname>Mota</surname></string-name>, <string-name>
<given-names>D.</given-names> 
<surname>Soares</surname></string-name>, <string-name>
<given-names>P.</given-names> 
<surname>Manzoni</surname></string-name>, <string-name>
<given-names>J.</given-names> 
<surname>Cano</surname></string-name> <etal>et al.</etal>
</person-group><italic>,</italic> &#x201C;
<article-title>FSF: Applying machine learning techniques to data forwarding in socially selfish opportunistic networks</article-title>,&#x201D; 
<source>Sensors</source>, vol. 
<volume>19</volume>, no. 
<issue>10</issue>, pp. 1&#x2013;26, 
<year>2019</year>.</mixed-citation>
</ref>
<ref id="ref-28">
<label>28</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>S.</given-names> 
<surname>Rashidibajgan</surname></string-name> and <string-name>
<given-names>R.</given-names> 
<surname>Doss</surname></string-name>
</person-group>, &#x201C;
<article-title>Privacy-preserving history-based routing in Opportunistic Networks</article-title>,&#x201D; 
<source>Computers &#x0026; Security</source>, vol. 
<volume>84</volume>, pp. 
<fpage>244</fpage>&#x2013;
<lpage>255</lpage>, 
<year>2019</year>.</mixed-citation>
</ref>
<ref id="ref-29">
<label>29</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>D.</given-names> 
<surname>Huang</surname></string-name>, <string-name>
<given-names>S.</given-names> 
<surname>Zhang</surname></string-name>, <string-name>
<given-names>P.</given-names> 
<surname>Hui</surname></string-name> and <string-name>
<given-names>Z.</given-names> 
<surname>Chen</surname></string-name>
</person-group>, &#x201C;
<article-title>Link pattern prediction in opportunistic networks with kernel regression</article-title>,&#x201D; in <conf-name>Proc. of the 7th Int. Conf. on Communication Systems and Networks (COMSNETS)</conf-name>, pp. 
<fpage>1</fpage>&#x2013;
<lpage>8</lpage>, 
<year>2015</year>. </mixed-citation>
</ref>
<ref id="ref-30">
<label>30</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>D. K.</given-names> 
<surname>Sharma</surname></string-name>, <string-name>
<given-names>J. J. P. C.</given-names> 
<surname>Rodrigues</surname></string-name>, <string-name>
<given-names>V.</given-names> 
<surname>Vashishth</surname></string-name>, <string-name>
<given-names>A.</given-names> 
<surname>Khanna</surname></string-name> and <string-name>
<given-names>A.</given-names> 
<surname>Chhabra</surname></string-name>
</person-group>, &#x201C;
<article-title>RLProph: A dynamic programming based reinforcement learning approach for optimal routing in opportunistic IoT networks</article-title>,&#x201D; 
<source>Wireless Networks</source>, vol. 
<volume>26</volume>, pp. 
<fpage>4319</fpage>&#x2013;
<lpage>4338</lpage>, 
<year>2020</year>.</mixed-citation>
</ref>
<ref id="ref-31">
<label>31</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>Y.</given-names> 
<surname>Li</surname></string-name> and <string-name>
<given-names>S.</given-names> 
<surname>Zhang</surname></string-name>
</person-group>, &#x201C;
<article-title>Combo-pre: A combination link prediction method in opportunistic networks</article-title>,&#x201D; in <conf-name>Proc. of the 24th Int. Conf. on Computer Communication and Networks (ICCCN)</conf-name>, pp. 
<fpage>1</fpage>&#x2013;
<lpage>6</lpage>, 
<year>2015</year>. </mixed-citation>
</ref>
<ref id="ref-32">
<label>32</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>L. S.</given-names> 
<surname>Jank&#x016F;</surname></string-name> and <string-name>
<given-names>K.</given-names> 
<surname>Hyniov&#x00E1;</surname></string-name>
</person-group>, &#x201C;
<article-title>Improvement of routing in opportunistic communication networks of vehicles by unsupervised machine learning</article-title>,&#x201D; in <conf-name>Proc. of the Int. Conf. on Engineering Applications of Neural Networks</conf-name>, pp. 
<fpage>412</fpage>&#x2013;
<lpage>423</lpage>, 
<year>2019</year>. </mixed-citation>
</ref>
<ref id="ref-33">
<label>33</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>D.</given-names> 
<surname>Huang</surname></string-name>, <string-name>
<given-names>S.</given-names> 
<surname>Zhang</surname></string-name>, <string-name>
<given-names>P.</given-names> 
<surname>Hui</surname></string-name> and <string-name>
<given-names>Z.</given-names> 
<surname>Chen</surname></string-name>
</person-group>, &#x201C;
<article-title>Link pattern prediction in opportunistic networks with kernel regression</article-title>,&#x201D; in <conf-name>Proc. of the 7th Int. Conf. on Communication Systems and Networks (COMSNETS)</conf-name>, pp. 
<fpage>1</fpage>&#x2013;
<lpage>8</lpage>, 
<year>2015</year>. </mixed-citation>
</ref>
<ref id="ref-34">
<label>34</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>X.</given-names> 
<surname>Cai</surname></string-name>, <string-name>
<given-names>J.</given-names> 
<surname>Shu</surname></string-name> and <string-name>
<given-names>M.</given-names> 
<surname>Al-Kali</surname></string-name>
</person-group>, &#x201C;
<article-title>Link prediction approach for opportunistic networks based on recurrent neural network</article-title>,&#x201D; 
<source>IEEE Access</source>, vol. 
<volume>7</volume>, pp. 
<fpage>2017</fpage>&#x2013;
<lpage>2025</lpage>, 
<year>2019</year>.</mixed-citation>
</ref>
<ref id="ref-35">
<label>35</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>S. B.</given-names> 
<surname>Chandanapalli</surname></string-name>, <string-name>
<given-names>E. S.</given-names> 
<surname>Reddy</surname></string-name> and <string-name>
<given-names>D. R.</given-names> 
<surname>Lakshmi</surname></string-name>
</person-group>, &#x201C;
<article-title>DFTDT: Distributed functional tangent decision tree for aqua status prediction in wireless sensor networks</article-title>,&#x201D; 
<source>International Journal of Machine Learning and Cybernetics</source>, vol. 
<volume>9</volume>, no. 
<issue>9</issue>, pp. 
<fpage>1419</fpage>&#x2013;
<lpage>1434</lpage>, 
<year>2018</year>.</mixed-citation>
</ref>
<ref id="ref-36">
<label>36</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>C. P.</given-names> 
<surname>Koushik</surname></string-name> and <string-name>
<given-names>P.</given-names> 
<surname>Vetrivelan</surname></string-name>
</person-group>, &#x201C;
<article-title>Heuristic relay-node selection in opportunistic network using RNN-LSTM based mobility prediction</article-title>,&#x201D; 
<source>Wireless Personal Communications</source>, vol. 
<volume>114</volume>, pp. 
<fpage>2363</fpage>&#x2013;
<lpage>2388</lpage>, 
<year>2020</year>.</mixed-citation>
</ref>
<ref id="ref-37">
<label>37</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>A.</given-names> 
<surname>Aleta</surname></string-name>, <string-name>
<given-names>M.</given-names> 
<surname>Tuninetti</surname></string-name>, <string-name>
<given-names>D.</given-names> 
<surname>Paolotti</surname></string-name>, <string-name>
<given-names>Y.</given-names> 
<surname>Moreno</surname></string-name> and <string-name>
<given-names>M.</given-names> 
<surname>Starnini</surname></string-name>
</person-group>, &#x201C;
<article-title>Link prediction in multiplex networks via triadic closure</article-title>,&#x201D; 
<source>Physical Review Research</source>, vol. 
<volume>2</volume>, no. 
<issue>4</issue>, pp. 042029-1&#x2013;042029-6, 
<year>2020</year>.</mixed-citation>
</ref>
<ref id="ref-38">
<label>38</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>S. K.</given-names> 
<surname>Dhurandher</surname></string-name>, <string-name>
<given-names>D. K.</given-names> 
<surname>Sharma</surname></string-name>, <string-name>
<given-names>I.</given-names> 
<surname>Woungang</surname></string-name> and <string-name>
<given-names>S.</given-names> 
<surname>Bhati</surname></string-name>
</person-group>, &#x201C;
<article-title>HBPR: history based prediction for routing in infrastructure-less opportunistic networks</article-title>,&#x201D; in <conf-name>Proc. of the 27th Int. Conf. on advanced information networking and applications (AINA)</conf-name>, pp. 
<fpage>931</fpage>&#x2013;
<lpage>936</lpage>, 
<year>2013</year>. </mixed-citation>
</ref>
<ref id="ref-39">
<label>39</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>Z.</given-names> 
<surname>Liao</surname></string-name>, <string-name>
<given-names>L.</given-names> 
<surname>Liu</surname></string-name> and <string-name>
<given-names>Y.</given-names> 
<surname>Chen</surname></string-name>
</person-group>, &#x201C;
<article-title>A novel link prediction method for opportunistic networks based on random walk and a deep belief network</article-title>,&#x201D; 
<source>IEEE Access</source>, vol. 
<volume>8</volume>, pp. 
<fpage>16236</fpage>&#x2013;
<lpage>16247</lpage>, 
<year>2020</year>.</mixed-citation>
</ref>
<ref id="ref-40">
<label>40</label><mixed-citation publication-type="journal">
<person-group person-group-type="author"><string-name>
<given-names>V.</given-names> 
<surname>Kuppusamy</surname></string-name>, <string-name>
<given-names>U.</given-names> 
<surname>Miriya</surname></string-name>, <string-name>
<given-names>A.</given-names> 
<surname>Udugama</surname></string-name> and <string-name>
<given-names>A.</given-names> 
<surname>F&#x00F6;rster</surname></string-name>
</person-group>, &#x201C;
<article-title>Evaluating forwarding protocols in opportunistic networks: Trends, advances, challenges and best practices</article-title>,&#x201D; 
<source>Future Internet</source>, vol. 
<volume>11</volume>, no. 
<issue>5</issue>, pp. 1&#x2013;26, 
<year>2019</year>.</mixed-citation>
</ref>
<ref id="ref-41">
<label>41</label><mixed-citation publication-type="conf-proc">
<person-group person-group-type="author"><string-name>
<given-names>A.</given-names> 
<surname>Ker&#x00E4;nen</surname></string-name>, <string-name>
<given-names>J.</given-names> 
<surname>Ott</surname></string-name> and <string-name>
<given-names>T.</given-names> 
<surname>K&#x00E4;rkk&#x00E4;inen</surname></string-name>
</person-group>, &#x201C;
<article-title>The ONE simulator for DTN protocol evaluation</article-title>,&#x201D; in <conf-name>Proc. of the 2nd Int. Conf. On Simulation Tools And Techniques</conf-name>, pp. 
<fpage>1</fpage>&#x2013;
<lpage>10</lpage>, 
<year>2009</year>. </mixed-citation>
</ref>
</ref-list>
</back>
</article>