<?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">23609</article-id>
<article-id pub-id-type="doi">10.32604/csse.2022.023609</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Gray-Hole Attack Minimization in IoMT with 5G Based D2D Networks</article-title><alt-title alt-title-type="left-running-head">Gray-Hole Attack Minimization in IoMT with 5G Based D2D Networks</alt-title><alt-title alt-title-type="right-running-head">Gray-Hole Attack Minimization in IoMT with 5G Based D2D Networks</alt-title>
</title-group>
<contrib-group content-type="authors">
<contrib id="author-1" contrib-type="author" corresp="yes">
<name name-style="western"><surname>Balaji</surname><given-names>V.</given-names></name><email>bv0089@srmist.edu.in</email>
</contrib>
<contrib id="author-2" contrib-type="author">
<name name-style="western"><surname>Selvaraj</surname><given-names>P.</given-names></name>
</contrib><aff><institution>Department of Computing Technologies, College of Engineering and Technology, Faculty of Engineering and Technology, SRM Institute of Science and Technology</institution>, <addr-line>Kattankulathur, 603203, Tamilnadu</addr-line>, <country>India</country></aff>
</contrib-group><author-notes><corresp id="cor1">&#x002A;Corresponding Author: V. Balaji. Email: <email>bv0089@srmist.edu.in</email></corresp></author-notes>
<pub-date pub-type="epub" date-type="pub" iso-8601-date="2022-01-18"><day>18</day>
<month>01</month>
<year>2022</year></pub-date>
<volume>42</volume>
<issue>3</issue>
<fpage>1289</fpage>
<lpage>1303</lpage>
<history>
<date date-type="received"><day>14</day><month>9</month><year>2021</year></date>
<date date-type="accepted"><day>15</day><month>10</month><year>2021</year></date>
</history>
<permissions>
<copyright-statement>&#x00A9; 2022 Balaji and Selvaraj</copyright-statement>
<copyright-year>2022</copyright-year>
<copyright-holder>Balaji and Selvaraj</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_23609.pdf"></self-uri>
<abstract>
<p>Reliable transmission is vital to the success of the next generation of communications technologies and Fifth Generation (5G) networks. Many sensitive applications, such as eHealth and medical services, can benefit from a 5G network. The Internet of Medical Things (IoMT) is a new field that fosters the maintenance of trust among various IoMT Device to Device (D2D) modern technologies. In IoMT the medical devices have to be connected through a wireless network and constantly needs to be self-configured to provide consistent and efficient data transmission. The medical devices need to be connected with sophisticated protocols and architecture to handle the synergy of the monitoring devices. Today, one of the commonly used algorithms in D2D communication is the Optimized Link State Routing protocol (OLSR). The OLSR is considerably good at effectively utilizing the bandwidth and reserving the paths. One of the major attack against the OLSR is the Node isolation attack, also known as the Gray hole denial of service attack. The Gray hole attack exploits the vulnerabilities present with sharing the topological information of the network. The attackers may use this topological information to maliciously disconnect the target nodes from the existing network and stops rendering the communication services to the victim node. Hence, considering the sensitivity and security concerns of the data used in e-Health applications, these types of attacks must be detected and disabled proactively. In this work, a novel Node Authentication (NA) with OLSR is proposed. The simulation experiments illustrated that the proposed protocol has an excellent Packet Delivery Ratio, minimal End-End delay, and minimal Packet loss when compared to the Ad-hoc On-Demand Distance Victor (AODV) protocol and the proposed authentication scheme was able to protect the OLSR protocol from a node isolation attack.</p>
</abstract>
<kwd-group kwd-group-type="author">
<kwd>5G</kwd>
<kwd>AODV</kwd>
<kwd>D2D</kwd>
<kwd>IoMT</kwd>
<kwd>OLSR</kwd>
<kwd>security issues</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec id="s1">
<label>1</label>
<title>Introduction</title>
<p>The Internet of Things (IoT) is a network of devices that includes mobile devices, wearable electronics, and other things. They have a unique Internet address (IP) that allows them to communicate with neighbouring network entities (e.g., smart home users). The sensors and sophisticated Application Programming Interfaces (APIs) are used to connect and share data over the Internet [<xref ref-type="bibr" rid="ref-1">1</xref>]. The Internet of Medical Things (IoMT) is another sort of IoT communication ecosystem. In contrast to traditional function-specific embedded devices, an IoT device is a domain-specific microcomputer. It consists of medical devices/sensors and software that are required to connect them with the servers/virtualized storage arrays. In [<xref ref-type="bibr" rid="ref-2">2</xref>] IoT based smart healthcare systems, the monitoring devices needs to be connected over the Internet. The support for the wireless communication technologies (such as the 5G network) are also integrated into protocols that are operating the medical devices, to enable smoother Device-to-Device (D2D) communication, which is the IoMT communication environment&#x2019;s base.</p>
<p>The D2D communication network is one of 5G&#x2019;s core technologies (D2D), a collection of medical devices that can communicate wirelessly with one another without relying on a centralised infrastructure or authority. A chain of intermediate nodes is used to transport data packets from one device to another. For UDP (User Datagram Packet) based network packet transfer, a variety of routing methods is available. The majority of these algorithms can be classified as proactive and reactive routing protocols.</p>
<sec id="s1_1">
<label>1.1</label>
<title>Concerns in Reactive Routing Protocols</title>
<p>AODV and Dynamic Source Routing protocol (DSR) are the reactive protocol which finds a route only when it is needed. Regardless of the routing technique, the ability of all nodes to be recognised by other nodes, even while in motion, is one of D2D&#x2019;s most significant needs and a key component of its success. Because of the frequent topological changes, these methods differ from normal routing algorithms used in traditional networks. At times the route that was persistent between the two medical devices can be broken. This may happen due to the mobility of the intermediate nodes. With the various other reasons, the medical nodes can be connected and disconnected from the network at any time, which might disrupt the network connectivity and the expected level of network performance. These are the major security breaches that possibly affect the performance of the internet connected medical applications.</p>
</sec>
<sec id="s1_2">
<label>1.2</label>
<title>Concerns in Proactive Routing Protocols</title>
<p>Every medical node in a proactive protocol, such as OLSR (Optimized Link State Routing Protocol) and Destination-Sequenced Distance Vector Routing protocol (DSDV) keeps track of all possible network destinations and the best routes to reach. This is one of the major concerns when accounting the security breaches available for the internet connected medical applications.</p>
<p>One of the most often used algorithms presently is the OLSR. Although OLSR is very effective at utilising bandwidth and calculating paths, it is vulnerable to a variety of attacks like black hole attack, gray hole attack, Denial of Service (DoS) attack etc. Because OLSR relies on network node collaboration, it is vulnerable to a few collaborating malicious nodes. However, in some cases the route might be disrupted merely by a single intruder node that causes route failure. Communication delay, link spoofing, flooding, wormhole, replay, black-hole, collusion mis-relay, and denial-of-service attacks are all instances of attacks.</p>
<p>The OLSR protocol follows a network overhead-reduction enhancement-based routing approach, in contrast to the traditional Link-State Routing protocol. On the other hand, the original LSR makes use of a flooded topology. Due to various inconsistencies these routing algorithms could reveal the existence of an attack but not the attacker. In Raffo et al. [<xref ref-type="bibr" rid="ref-3">3</xref>] presented a methodology for minimising the vulnerabilities and improving the security of the OLSR routing protocol from intruders and malicious nodes. The HELLO and TC messages are digitally signed by each node. These signatures will be used by the other nodes that wish to validate their own HELLO and TC messages. This technique is effective, but it comes at a cost of huge overhead; in addition to the specific OLSR overhead.</p>
<p>Hence signing messages takes a significant amount of computation, which becomes a cumulative component as the network expands in size for the scalability. Another concern is that the network loses its spontaneity because in order to share public keys, all nodes must know each other before hand the connection is established. This restricts the network from naturally growing to the large number of nodes at a given time and location, which is an important concern in 5G based medical D2D communication.</p>
</sec>
<sec id="s1_3">
<label>1.3</label>
<title>Concerns in Node Isolation Attack</title>
<p>An attacker node performs a node isolation attack by pretending to be a fictitious node and broadcasting a TC message to the victim node, claiming to have a node adjacent to reach all of the victim node&#x2019;s two hop neighbours. As a result, the victim node selects the attacker node as its single MPR node, to which it relays data. The packets might not make it to the destination node, though. As shown in <xref ref-type="fig" rid="fig-1">Fig. 1</xref> below.</p>
<fig id="fig-1">
<label>Figure 1</label>
<caption>
<title>Node isolation attack</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-1.png"/>
</fig>
<p>That the attacker node &#x2018;a&#x2019; sends the TC message {v, 2, 3, 1, Fa} to the victim node &#x2018;v&#x2019;. Since the message includes all of the two hop neighbours the victim node has very less possibilities to reject the attacker message. Therefore, it chooses the attacker node as its lone MPR. As a result, the attacker node can simply isolate the victim node from the rest of the network, resulting in a clusters of network partition. Because Node 2 is not identified as the MPR, it can continue to exchange data with the victim, but it will not disseminate that data.</p>
<p>The organization of this research article is preceded in such a way that the related research articles are analyzed in <xref ref-type="sec" rid="s2">Section 2</xref> with a detailed illustration in <xref ref-type="sec" rid="s3">Section 3</xref>. The performance analysis is performed in <xref ref-type="sec" rid="s4">Section 4</xref> with a conclusion in <xref ref-type="sec" rid="s5">Section 5</xref>.</p>
</sec>
</sec>
<sec id="s2">
<label>2</label>
<title>Related Works</title>
<p>IoT technologies are being developed and implemented at a rapid pace, security concerns in IoT devices are only likely to get worse. In the instance of the Internet of Medical Things (IoMT), which is concerned with the communication and control of advanced medical devices, it becomes a very severe issue. Different types of IoT malware are continually being developed. These new malwares have the potential to disrupt IoMT connection and even manipulate smart medical devices. The conventional threat identification methods are insufficient for detecting and analysing the threats in IoT/IoMT networks.</p>
<sec id="s2_1">
<label>2.1</label>
<title>Multi-Hop D2D Communication Networks: A Secure Routing Solution</title>
<p>In fact, the security solutions are interoperable, to promote the backward and future compatibility. The lightweight protocol proposed by Liu et al. [<xref ref-type="bibr" rid="ref-4">4</xref>] in combines end to end and digital signature authentication. This integration of authentication is carried out on the existing AODV. Because a multi-hop D2D network is essentially an ad hoc network based on multi-hop D2D, Ad hoc network routing protocol is frequently referred to as &#x201C;multi-hop D2D network routing protocol&#x201D;.</p>
</sec>
<sec id="s2_2">
<label>2.2</label>
<title>Device to Device Network Routing Protocol with Multiple Hops</title>
<p>According to Venkatesan et al. [<xref ref-type="bibr" rid="ref-5">5</xref>] operational mechanisms, ad hoc routing protocols are divided into three types: i) table-driven routing protocols, ii) passive routing protocols and iii) hybrid routing systems. Based on diverse network designs, ad hoc network routing protocols can be divided into flat and hierarchical routing systems. The majority of contemporary ad hoc network routing systems are variations on traditional ad hoc network routing approaches. Network Service Quality and resilience are two enhancement indicators. In [<xref ref-type="bibr" rid="ref-6">6</xref>] Istikmal et al. proposed an AODV Signal-To-Noise Ratio (SNR)-Selective Routing (SR) protocol in the reverse routing process, selective routing depending on the SNR threshold; In Tata et al. [<xref ref-type="bibr" rid="ref-7">7</xref>] suggested an upgraded AODV protocol that is a selective ad hoc on-demand multipath distance vector method based on load balancing. The majority of studies on reliable route in multi-hop D2D network technologies are currently focused on improving the original ad hoc routing protocol, and it focuses on specific attack strategies.</p>
</sec>
<sec id="s2_3">
<label>2.3</label>
<title>Defending Against DoS Attacks Using Secure Routing Protocols</title>
<p>In multi-hop Device to Device networks, denial of service (DoS) threats is widespread; As a result, DoS attacks can be mitigated using hash functions and other mechanisms for authenticating the source of data packets. In Patil et al. [<xref ref-type="bibr" rid="ref-8">8</xref>] presented a better ALERT protocol utilizing pseudonym of node location methodology to withstand DoS attacks. Node trust is also used by academics to detect fraudulent nodes and defend against various attacks. In Kumar et al. [<xref ref-type="bibr" rid="ref-9">9</xref>] created a DoS-resistant AODV protocol. According to the proposed protocol, dummy and false packets are transmitted between the source and destination nodes. This bogus transmission is carried out in order to determine the node&#x2019;s trustworthiness and detect any fraudulent nodes. Researchers have also offered secure routing methods for certain DoS threats. In Marimuthu et al. [<xref ref-type="bibr" rid="ref-10">10</xref>] proposed an Extended Optimized Link State Routing protocol that works on the authentication mechanism to resist certain categories of DOS attacks.</p>
</sec>
<sec id="s2_4">
<label>2.4</label>
<title>Prevention of Black Hole Attacks with Secure Routing Protocols</title>
<p>Researchers also have investigated different types of methods to safeguard from black hole attacks which are presumed to be one of the most frequent attacks. The route discovery process in the dynamic source routing protocol along with the RREP packets are optimal which makes it resistant to black hole attacks. To prevent black hole attacks, Deshmukh et al. [<xref ref-type="bibr" rid="ref-11">11</xref>] included an authenticity value in the Route Reply (RREP) packet in DSR protocol. In Bhardwaj [<xref ref-type="bibr" rid="ref-12">12</xref>] suggested methods to check the packets in order to confirm the route authentication. The old reactive routing system AODV can assist to protect from malicious attacks by discovering malicious routes and malicious nodes. In the AODV protocol Singh et al. [<xref ref-type="bibr" rid="ref-13">13</xref>] suggested to prevent black hole attacks, a blacklist flag and routing identities are used to identify hostile nodes. The Chengetanai [<xref ref-type="bibr" rid="ref-14">14</xref>] protocol mitigates the black hole attack in the AODV routing protocol by verifying that the packet&#x2019;s timestamp satisfies the destination timestamp. To avoid black hole attacks, in Yadav et al. [<xref ref-type="bibr" rid="ref-15">15</xref>] demonstrated an approach in which, the destination node decides the legitimacy of the RREQ response path based on the criteria in a reliable AODV routing protocol. They have provided a methodology where in the route is made secure by using encryption which helps to prevent black hole attacks.</p>
</sec>
<sec id="s2_5">
<label>2.5</label>
<title>Prevention of Gray Hole and Worm Hole Attacks with Secure Routing Protocols</title>
<p>Only a limited number of routing protocols have been developed expressly for grey hole and wormhole attacks. To determine the applicable secure routes, online packet data calculation devices and parameters are used, In Kumar et al. [<xref ref-type="bibr" rid="ref-9">9</xref>] discovered Data packet transmission rates that are abnormally high on some nodes. This technique can withstand a variety of attacks since nodes with abnormal packet data available bandwidth may be plotting a black hole, grey hole, or wormhole attack. The major objective of the proposed research work is to mitigate the gray hole attack in the 5G oriented Internet of Medical Technology applications.</p>
</sec>
</sec>
<sec id="s3">
<label>3</label>
<title>Proposed Methodology</title>
<p>The proposed framework for the minimization of Gray-Hole Attack in 5G based IoMT applications is discussed in this section. The Network Model, identification of Neighbor and Multi Point Relay (MPR) and Secure Routing Strategy are the essential components in the proposed attack mitigation system.</p>
<sec id="s3_1">
<label>3.1</label>
<title>Proposed Architecture</title>
<p>In Optimized Link State Routing Protocol based networks, node authentication is a technique used to particularly handle a DoS attack known as node isolation attack. We assign a unique key to each unique node to improve node and network security. When sending data packets from source to destination, the node will validate the key value. If the key value is found to be correct, the packet will be successfully transmitted. It detects malicious nodes attempting to manipulate Topology Control (TC) messages using just the victim&#x2019;s internal data. Hence based on the authentication the Multi-point Relay Nodes (MPRs) will be permitted and they will be avoided in case of MPR node path with invalid authentication. To establish a new MPR node that can be accessed via alternate routes, a novel approach, known as Node Authentication (NA), is proposed. The proposed approach is based on each node&#x2019;s own information gained during ordinary routing, as well as the use of virtual (fictitious) nodes. The overall system flow diagram is defined in <xref ref-type="fig" rid="fig-2">Fig. 2</xref> below. By avoiding the fictitious node, the victim node is able to arrive at their destination in a secure environment.</p>
<fig id="fig-2">
<label>Figure 2</label>
<caption>
<title>Flow diagram of the proposed node authentication scheme</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-2.png"/>
</fig>
</sec>
<sec id="s3_2">
<label>3.2</label>
<title>Modules of the Proposed Node Authentication Scheme</title>
<p>The modules present in the proposed Node Authentication Scheme are as follows:<list list-type="order"><list-item>
<p>Model of a network</p></list-item><list-item>
<p>Neighbor and Multi Point Relay (MPR)</p></list-item><list-item>
<p>Secure routing approach</p></list-item></list></p>
<sec id="s3_2_1">
<label>3.2.1</label>
<title>Model of a Network</title>
<p>A 5G wireless network instance with &#x2018;N&#x2019; number of nodes is considered in the Network Animator (NAM) animator&#x2019;s 2D plane. The deployed nodes are aware of their location and can communicate directly with their neighbors. Through multi-hop communications, the entire network is fully connected. Every node has a set maximum and minimum transmission range R. The communication between nodes is organised like a tree, with the destination at the edge. In this communication tree, data is exchanged via the nodes as shown in the <xref ref-type="fig" rid="fig-3">Fig. 3</xref> given below.</p>
<fig id="fig-3">
<label>Figure 3</label>
<caption>
<title>Setting up the network model in the NAM simulator</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-3.png"/>
</fig>
</sec>
<sec id="s3_2_2">
<label>3.2.2</label>
<title>Neighbour and Multi-Point Relay (MPR)</title>
<p>The equation for the computation of distance between the each node&#x2019;s one hop neighbours is as follows:</p>
<p><disp-formula id="eqn-1"><label>(1)</label>
<mml:math id="mml-eqn-1" display="block"><mml:mi>D</mml:mi><mml:mi>i</mml:mi><mml:mi>s</mml:mi><mml:mi>t</mml:mi><mml:mi>a</mml:mi><mml:mi>n</mml:mi><mml:mi>c</mml:mi><mml:mi>e</mml:mi><mml:mo>=</mml:mo><mml:msqrt><mml:mrow><mml:msup><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mrow><mml:mi mathvariant="normal">x</mml:mi></mml:mrow></mml:mrow><mml:mn>2</mml:mn><mml:mo>&#x2212;</mml:mo><mml:mrow><mml:mrow><mml:mi mathvariant="normal">x</mml:mi></mml:mrow></mml:mrow><mml:mn>1</mml:mn><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mn>2</mml:mn></mml:msup></mml:mrow><mml:mo>+</mml:mo><mml:mrow><mml:msup><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mrow><mml:mi mathvariant="normal">y</mml:mi></mml:mrow></mml:mrow><mml:mn>2</mml:mn><mml:mo>&#x2212;</mml:mo><mml:mrow><mml:mrow><mml:mi mathvariant="normal">y</mml:mi></mml:mrow></mml:mrow><mml:mn>1</mml:mn><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt></mml:math>
</disp-formula></p>
<p>The energy of the neighboring node is determined using the <xref ref-type="disp-formula" rid="eqn-2">Eq. (2)</xref>.</p>
<p><disp-formula id="eqn-2"><label>(2)</label>
<mml:math id="mml-eqn-2" display="block"><mml:mi>R</mml:mi><mml:mrow><mml:msub><mml:mi>E</mml:mi><mml:mrow><mml:mi>A</mml:mi><mml:mi>V</mml:mi><mml:mi>G</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mfrac><mml:mrow><mml:mi>R</mml:mi><mml:mrow><mml:msub><mml:mi>E</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:mrow><mml:mi>N</mml:mi></mml:mfrac></mml:mrow></mml:math>
</disp-formula></p>
<p>The shortest path among any two nodes are determined using <xref ref-type="disp-formula" rid="eqn-3">Eq. (3)</xref>.</p>
<p><disp-formula id="eqn-3"><label>(3)</label>
<mml:math id="mml-eqn-3" display="block"><mml:mrow><mml:msub><mml:mi>x</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:msub><mml:mi>x</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow><mml:mo>/</mml:mo></mml:mrow><mml:msubsup><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>n</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mi>N</mml:mi></mml:msubsup><mml:mrow><mml:msubsup><mml:mi>x</mml:mi><mml:mi>n</mml:mi><mml:mn>2</mml:mn></mml:msubsup></mml:mrow></mml:math>
</disp-formula></p>
<p>If the estimated distance between nodes is much less than or equivalent to 250 m range, they are considered neighbours and are listed together. The two hop neighbours of a node are also calculated and added to a list in the same way. This list is sorted by unique nodes and, if present, removes itself from the list. The MPRs (Multi Point Relays) are then found using the sorted list. An MPR is defined as a node in a sorted list that has more than two neighbours as shown in the <xref ref-type="fig" rid="fig-4">Fig. 4</xref> given below.</p>
<fig id="fig-4">
<label>Figure 4</label>
<caption>
<title>Flow diagram of the neighbour and multi-point relay (MPR)</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-4.png"/>
</fig>
</sec>
<sec id="s3_2_3">
<label>3.2.3</label>
<title>Secure Routing Approach</title>
<p>By utilising a fictional node and authenticating Topology Control (TC) messages, secure routing in a Medial D2D network can be achieved, bypassing a DoS attacker [<xref ref-type="bibr" rid="ref-16">16</xref>]. As the TC message delivered by the attacker may have inconsistencies due to the fact that it may not be sent by the attacker&#x2019;s original neighbours, we have to check the TC messages to locate the attacker nodes. As the MPR nodes are used to find the shortest routing path, the attackers can be filtered out. We utilized the NA-OLSR routing to arrive at the secure routing path as shown in the <xref ref-type="fig" rid="fig-5">Fig. 5</xref> given below.</p>
<fig id="fig-5">
<label>Figure 5</label>
<caption>
<title>Secure routing approach</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-5.png"/>
</fig>
<p>We have taken the MPR list to check if it contains any fictious attackers, or any fictious nodes. In case of fictious attackers or nodes found it will be removed from the list. Once after the removal of anomalies the shortest route to the destination has been found. The path is provided for routing UDP packets using the NA-OLSR protocol.</p>
</sec>
</sec>
</sec>
<sec id="s4">
<label>4</label>
<title>Simulation Setup</title>
<p>The built-in NA-OLSR module in the Network Simulator (NS2) was used. It was enhanced to support node authentication using the protocol described above. Most simulation value sets were run a total of _1,000 times, with the average results presented. The movement was 1.5&#x2013;2 m/s (5.4&#x2013;7.2 km/h) where applicable and broadcast range was roughly 250 m. A series of simulations were used to verify the efficiency of node authentication against Gray-hole attacks [<xref ref-type="bibr" rid="ref-17">17</xref>]. In a 750 m &#x00D7; 1000 m space, a randomised network topology with a fluctuating number of nodes was employed, with network density ranging from 30 to 100 nodes.</p>
<p>The Simulated sessions which have no communication between its components were rejected, and the estimated outcome was ignored. Three predetermined nodes were used in each simulation. There is a victim, source node, and an attacker that sends messages to the victim. The target nodes which are assumed to be as victims and source nodes are positioned randomly. The simulation settings are such that the victim nodes and the nodes from where the attack [<xref ref-type="bibr" rid="ref-18">18</xref>] originates are separated by a minimum of two hops distance. This limitation is demonstrated by the fact that one-hop neighbours are virtually secured from attackers, rendering all additional protection redundant.</p>
<sec id="s4_1">
<label>4.1</label>
<title>Results and Discussion</title>
<p>This section explains the experiment used to efficiently evaluate the proposed system&#x2019;s accuracy and performance in comparison to the approaches specified.</p>
<sec id="s4_1_1">
<label>4.1.1</label>
<title>Node Initialization</title>
<p>A total of 40 medical nodes have been added to the 5G wireless network. The NA-OLSR routing protocol were configured. With Constant Bit Rate (CBR) traffic, the Nam animation is specified for a size of 1500 &#x00D7; 1500 pixels. The snapshot of the scenario of 40 nodes is shown in <xref ref-type="fig" rid="fig-6">Fig. 6</xref> given below.</p>
<fig id="fig-6">
<label>Figure 6</label>
<caption>
<title>Node initialization</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-6.png"/>
</fig>
</sec>
<sec id="s4_1_2">
<label>4.1.2</label>
<title>Single Hop Neighbour Detection</title>
<p>Distance calculation algorithms are used to identify the one hop neighbour for each node.</p>
<p><disp-formula id="eqn-4"><label>(4)</label>
<mml:math id="mml-eqn-4" display="block"><mml:mi>d</mml:mi><mml:mo>=</mml:mo><mml:msqrt><mml:mrow><mml:msup><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mrow><mml:mi mathvariant="normal">x</mml:mi></mml:mrow></mml:mrow><mml:mn>2</mml:mn><mml:mo>&#x2212;</mml:mo><mml:mrow><mml:mrow><mml:mi mathvariant="normal">x</mml:mi></mml:mrow></mml:mrow><mml:mn>1</mml:mn><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mn>2</mml:mn></mml:msup></mml:mrow><mml:mo>+</mml:mo><mml:mrow><mml:msup><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mrow><mml:mi mathvariant="normal">y</mml:mi></mml:mrow></mml:mrow><mml:mn>2</mml:mn><mml:mo>&#x2212;</mml:mo><mml:mrow><mml:mrow><mml:mi mathvariant="normal">y</mml:mi></mml:mrow></mml:mrow><mml:mn>1</mml:mn><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt></mml:math>
</disp-formula></p>
<p>The nodes are deemed neighbours and are put in a list if the distance estimated is below or equivalent to 250 m range. Neighbour detection from node 0 to node 39 is shown in the <xref ref-type="fig" rid="fig-7">Fig. 7</xref> given below.</p>
<fig id="fig-7">
<label>Figure 7</label>
<caption>
<title>Neighbour detection</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-7.png"/>
</fig>
</sec>
<sec id="s4_1_3">
<label>4.1.3</label>
<title>Two Hop Neighbour Detection</title>
<p>The Nodes&#x2019; two hop neighbours were calculated, for example, if node 0&#x2019;s neighbours are 4, 5, 6, then the neighbour nodes of 4, 5, 6 are assumed to be node 0&#x2019;s two hop neighbours and are added to a list as shown in the <xref ref-type="fig" rid="fig-8">Fig. 8</xref> given below.</p>
<fig id="fig-8">
<label>Figure 8</label>
<caption>
<title>Two hop neighbour detection</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-8.png"/>
</fig>
</sec>
<sec id="s4_1_4">
<label>4.1.4</label>
<title>MPR (Multi Point Relay) Selection</title>
<p>The two-hop neighbour list is sorted by unique nodes, and if node 0 is available in the list, it is removed. The loop is run, and the two hop neighbours of each node with unique neighbours are obtained. This sorted list is then used to look for Multi Point Relays. An MPR is defined as a node in a sorted list which has more than two neighbours as shown in the <xref ref-type="fig" rid="fig-9">Fig. 9</xref> given below.</p>
<fig id="fig-9">
<label>Figure 9</label>
<caption>
<title>MPR (Multi Point Relay) selection</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-9.png"/>
</fig>
</sec>
<sec id="s4_1_5">
<label>4.1.5</label>
<title>Evaluating the Keys and TC Message</title>
<p>Every node gets its own key. The key value is checked by the node during the transport of data packets from the origin to destination device. If the value of the key is correct, then the packet will be successfully transmitted as shown in the <xref ref-type="fig" rid="fig-10">Fig. 10</xref> in the given below.</p>
<fig id="fig-10">
<label>Figure 10</label>
<caption>
<title>Evaluating the keys</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-10.png"/>
</fig>
<p>The TC messages exchanged by relay nodes and attacker nodes [<xref ref-type="bibr" rid="ref-19">19</xref>]; From the above <xref ref-type="fig" rid="fig-10">Fig. 10</xref> the details of the attacker node can be found (For ex: For the Node 14 its neighbour is 34, 10, 13, 15, 17). The attacker may send fictitious TC message to isolate the victim node from the network as shown in <xref ref-type="fig" rid="fig-11">Fig. 11</xref> given below.</p>
<fig id="fig-11">
<label>Figure 11</label>
<caption>
<title>Fictitious TC message</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-11.png"/>
</fig>
</sec>
<sec id="s4_1_6">
<label>4.1.6</label>
<title>Finding Shortest Route to Destination</title>
<p>Considering a destination node and a source/victim node, the shortest route from source to Destination device was calculated. For example, if the source node is node 21 and the destination node is node 18, the MPRs of 21 are 39, 0, 3, 20, 22. We have taken the MPR list and checked to see if it contains any attacker, attacker fictious, and fictious nodes, and if found, they were removed from the list.</p>
<p>First, we computed the distance between 21 and 39 and stored it in variable &#x2018;g&#x2019;. Next, we calculated the distance between 21 and 0 and saved it in variable &#x2018;g1&#x2019;. Finally, we compared the distance between &#x2018;g&#x2019; and &#x2018;g1&#x2019; and chose the node with the lowest distance value as the relay node. Similarly, we calculated MPR for all 21 nodes and select the best one (for example, node 3) to act as a relay. Shown in the <xref ref-type="fig" rid="fig-12">Fig. 12</xref> in the given below.</p>
<fig id="fig-12">
<label>Figure 12</label>
<caption>
<title>Finding shortest route to destination</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-12.png"/>
</fig>
</sec>
<sec id="s4_1_7">
<label>4.1.7</label>
<title>Attack Detection</title>
<p>Consider a destination node and a source/victim node. For example, Let&#x2019;s pretend node 21 is the source and node 18 is the destination. We have taken the MPR list and check to see if it contains attacker, attacker fictious, and fictious node, if found it will be removed from the list. The relay&#x2019;s neighbours are then taken and the best one is found, and this cycle continues until we arrive at our target and find a way. The path shown in the <xref ref-type="fig" rid="fig-13">Fig. 13</xref> is for sending UDP packets using the NA-OLSR protocol as the routing protocol.</p>
<fig id="fig-13">
<label>Figure 13</label>
<caption>
<title>Attack detection</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_23609-fig-13.png"/>
</fig>
</sec>
</sec>
<sec id="s4_2">
<label>4.2</label>
<title>Experimental Analysis</title>
<p>We have used a 40-node setup in this scenario. For all scenarios, the sink packets were monitored for Packet Lost, Packet Delivery Ratio and End-to-end latency in order to calculate the performance of the communication network.</p>
<sec id="s4_2_1">
<label>4.2.1</label>
<title>Ratio of Packets Delivered</title>
<p>The performance of any routing protocol is measured by many parameters of which the packet delivery ratio is a significant indicator of the performance. The simulation settings used determine the protocol&#x2019;s reliability. The significant metrics to be taken into consideration are packet size, number of hops, available bandwidth, and network topology. The packet delivery ratio is the ratio of packets received at the destination to packets transmitted from the source. A sample of 1000 packets is transmitted over the network to determine the packet delivery ratio. The performance improvement is directly proportional to the packet delivery ratio as stated in <xref ref-type="table" rid="table-1">Tab. 1</xref> and computed from the formula given below.</p>
<p><disp-formula id="eqn-5"><label>(5)</label>
<mml:math id="mml-eqn-5" display="block"><mml:mtable columnalign="left" rowspacing=".5em" columnspacing="thickmathspace" displaystyle="true"><mml:mtr><mml:mtd><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>c</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>D</mml:mi><mml:mi>e</mml:mi><mml:mi>l</mml:mi><mml:mi>i</mml:mi><mml:mi>v</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mi>y</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>R</mml:mi><mml:mi>a</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>o</mml:mi><mml:mo>=</mml:mo><mml:mi mathvariant="normal">&#x03A3;</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mrow><mml:mi>T</mml:mi><mml:mi>h</mml:mi><mml:mi>e</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>t</mml:mi><mml:mi>o</mml:mi><mml:mi>t</mml:mi><mml:mi>a</mml:mi><mml:mi>l</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>n</mml:mi><mml:mi>u</mml:mi><mml:mi>m</mml:mi><mml:mi>b</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>o</mml:mi><mml:mi>f</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>p</mml:mi><mml:mi>a</mml:mi><mml:mi>c</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi><mml:mi>s</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:mi>e</mml:mi><mml:mi>i</mml:mi><mml:mi>v</mml:mi><mml:mi>e</mml:mi><mml:mi>d</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>b</mml:mi><mml:mi>y</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>a</mml:mi><mml:mi>l</mml:mi><mml:mi>l</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>d</mml:mi><mml:mi>e</mml:mi><mml:mi>s</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>n</mml:mi><mml:mi>a</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>o</mml:mi><mml:mi>n</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>n</mml:mi><mml:mi>o</mml:mi><mml:mi>d</mml:mi><mml:mi>e</mml:mi><mml:mi>s</mml:mi></mml:mrow><mml:mo>)</mml:mo></mml:mrow><mml:mrow><mml:mo>/</mml:mo></mml:mrow></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mi mathvariant="normal">&#x03A3;</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>T</mml:mi><mml:mi>h</mml:mi><mml:mi>e</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>t</mml:mi><mml:mi>o</mml:mi><mml:mi>t</mml:mi><mml:mi>a</mml:mi><mml:mi>l</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>a</mml:mi><mml:mi>m</mml:mi><mml:mi>o</mml:mi><mml:mi>u</mml:mi><mml:mi>n</mml:mi><mml:mi>t</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>o</mml:mi><mml:mi>f</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>p</mml:mi><mml:mi>a</mml:mi><mml:mi>c</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi><mml:mi>s</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>t</mml:mi><mml:mi>h</mml:mi><mml:mi>a</mml:mi><mml:mi>t</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>a</mml:mi><mml:mi>l</mml:mi><mml:mi>l</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>s</mml:mi><mml:mi>o</mml:mi><mml:mi>u</mml:mi><mml:mi>r</mml:mi><mml:mi>c</mml:mi><mml:mi>e</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>n</mml:mi><mml:mi>o</mml:mi><mml:mi>d</mml:mi><mml:mi>e</mml:mi><mml:mi>s</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>h</mml:mi><mml:mi>a</mml:mi><mml:mi>v</mml:mi><mml:mi>e</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>s</mml:mi><mml:mi>e</mml:mi><mml:mi>n</mml:mi><mml:mi>t</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mtd></mml:mtr></mml:mtable></mml:math>
</disp-formula></p>
<table-wrap id="table-1"><label>Table 1</label>
<caption>
<title>Comparison of PDR of AODV and NA-OLSR</title></caption>
<table><colgroup>
<col/>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>NODES</th>
<th>Existing system (AODV)<break/>units (%)</th>
<th>Proposed system (NA-OLSR)<break/>units (%)</th>
</tr>
</thead>
<tbody>
<tr>
<td>5</td>
<td>0.01128</td>
<td>0.02128</td>
</tr>
<tr>
<td>10</td>
<td>0.30223</td>
<td>0.70223</td>
</tr>
<tr>
<td>15</td>
<td>0.40223</td>
<td>0.70223</td>
</tr>
<tr>
<td>20</td>
<td>0.34096</td>
<td>0.68096</td>
</tr>
<tr>
<td>25</td>
<td>0.50863</td>
<td>0.80864</td>
</tr>
<tr>
<td>30</td>
<td>0.53750</td>
<td>0.72352</td>
</tr>
<tr>
<td>35</td>
<td>0.47466</td>
<td>0.76600</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>For 40 nodes the experiment was set to run for 10 s. It is calculated in bits per second (bit/s) and has a decent net connection channel capacity. While bypassing the attacker, the proposed framework has a high packet delivery ratio when compare to existing system.</p>
</sec>
<sec id="s4_2_2">
<label>4.2.2</label>
<title>End to End Delay</title>
<p>End-to-end delay is the average time it takes a packet to transit from its source to its destination across a network. The average end-to-end latency can be calculated by taking the mean of all successfully delivered messages&#x2019; end-to-end delays. As a result, the terms of throughput influences end-to-end latency. The probability of packet drops increases as the number of hops between a source and destination increases. The experiment was set to run for 10 s on node 40. In the existing system, the delay is high when the attacker is present in the routing path shown in <xref ref-type="table" rid="table-2">Tab. 2</xref>. It can be expressed mathematically as given below:</p>
<p><disp-formula id="eqn-6"><label>(6)</label>
<mml:math id="mml-eqn-6" display="block"><mml:mi>A</mml:mi><mml:mi>v</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mi>a</mml:mi><mml:mi>g</mml:mi><mml:mi>e</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>E</mml:mi><mml:mi>n</mml:mi><mml:mi>d</mml:mi><mml:mo>&#x2010;</mml:mo><mml:mi>t</mml:mi><mml:mi>o</mml:mi><mml:mo>&#x2010;</mml:mo><mml:mi>E</mml:mi><mml:mi>n</mml:mi><mml:mi>d</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>D</mml:mi><mml:mi>e</mml:mi><mml:mi>l</mml:mi><mml:mi>a</mml:mi><mml:mi>y</mml:mi><mml:mo>=</mml:mo><mml:mi>T</mml:mi><mml:mi>o</mml:mi><mml:mi>t</mml:mi><mml:mi>a</mml:mi><mml:mi>l</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>m</mml:mi><mml:mi>e</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>t</mml:mi><mml:mi>a</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>n</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>f</mml:mi><mml:mi>r</mml:mi><mml:mi>o</mml:mi><mml:mi>m</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>s</mml:mi><mml:mi>t</mml:mi><mml:mi>a</mml:mi><mml:mi>r</mml:mi><mml:mi>t</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>t</mml:mi><mml:mi>o</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>f</mml:mi><mml:mi>i</mml:mi><mml:mi>n</mml:mi><mml:mi>i</mml:mi><mml:mi>s</mml:mi><mml:mi>h</mml:mi><mml:mrow><mml:mo>/</mml:mo></mml:mrow><mml:mi>T</mml:mi><mml:mi>o</mml:mi><mml:mi>t</mml:mi><mml:mi>a</mml:mi><mml:mi>l</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>n</mml:mi><mml:mi>o</mml:mi><mml:mo>.</mml:mo><mml:mtext>&#xA0;</mml:mtext><mml:mi>o</mml:mi><mml:mi>f</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>p</mml:mi><mml:mi>a</mml:mi><mml:mi>c</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>s</mml:mi><mml:mi>e</mml:mi><mml:mi>n</mml:mi><mml:mi>t</mml:mi></mml:math>
</disp-formula></p>
<table-wrap id="table-2"><label>Table 2</label>
<caption>
<title>End to end delay</title></caption>
<table><colgroup>
<col/>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>NODES</th>
<th>Existing system (AODV)<break/>UNITS (M/S)</th>
<th>Proposed system (NA-OLSR)<break/>UNITS (M/S)</th>
</tr>
</thead>
<tbody>
<tr>
<td>5</td>
<td>1.58929</td>
<td>0.98929</td>
</tr>
<tr>
<td>10</td>
<td>1.00589</td>
<td>0.50598</td>
</tr>
<tr>
<td>15</td>
<td>0.50509</td>
<td>0.10589</td>
</tr>
<tr>
<td>20</td>
<td>0.60628</td>
<td>0.06198</td>
</tr>
<tr>
<td>25</td>
<td>0.80459</td>
<td>0.10467</td>
</tr>
<tr>
<td>30</td>
<td>0.50509</td>
<td>0.20583</td>
</tr>
<tr>
<td>35</td>
<td>0.60529</td>
<td>0.10532</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s4_2_3">
<label>4.2.3</label>
<title>Packet Loss</title>
<p>Packet loss is defined as the ratio of packets that has never made it to their destination to the number of packets originated by the source. It can be expressed mathematically as a formula shown in below</p>
<p><disp-formula id="eqn-7"><label>(7)</label>
<mml:math id="mml-eqn-7" display="block"><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>c</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>L</mml:mi><mml:mi>o</mml:mi><mml:mi>s</mml:mi><mml:mi>s</mml:mi><mml:mo>=</mml:mo><mml:mrow><mml:mfrac><mml:mrow><mml:mi>N</mml:mi><mml:mi>u</mml:mi><mml:mi>m</mml:mi><mml:mi>b</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>o</mml:mi><mml:mi>f</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>c</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi><mml:mi>s</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>s</mml:mi><mml:mi>e</mml:mi><mml:mi>n</mml:mi><mml:mi>t</mml:mi><mml:mo>&#x2212;</mml:mo><mml:mi>N</mml:mi><mml:mi>u</mml:mi><mml:mi>m</mml:mi><mml:mi>b</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>o</mml:mi><mml:mi>f</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>c</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi><mml:mi>s</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>R</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:mi>e</mml:mi><mml:mi>i</mml:mi><mml:mi>v</mml:mi><mml:mi>e</mml:mi><mml:mi>d</mml:mi></mml:mrow><mml:mrow><mml:mi>N</mml:mi><mml:mi>o</mml:mi><mml:mo>.</mml:mo><mml:mtext>&#xA0;</mml:mtext><mml:mi>o</mml:mi><mml:mi>f</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>P</mml:mi><mml:mi>a</mml:mi><mml:mi>c</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi><mml:mi>s</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi>S</mml:mi><mml:mi>e</mml:mi><mml:mi>n</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:mfrac></mml:mrow></mml:math>
</disp-formula></p>
<table-wrap id="table-3"><label>Table 3</label>
<caption>
<title>Packet loss</title></caption>
<table><colgroup>
<col/>
<col/>
<col/>
</colgroup>
<thead>
<tr>
<th>NODES</th>
<th>Existing system (AODV)<break/>UNITS (BYTES)</th>
<th>Proposed system (NA-OLSR)<break/>UNITS (BYTES)</th>
</tr>
</thead>
<tbody>
<tr>
<td>5</td>
<td>1000</td>
<td>960</td>
</tr>
<tr>
<td>10</td>
<td>6060</td>
<td>3460</td>
</tr>
<tr>
<td>15</td>
<td>4430</td>
<td>1430</td>
</tr>
<tr>
<td>20</td>
<td>6840</td>
<td>4940</td>
</tr>
<tr>
<td>25</td>
<td>10250</td>
<td>5250</td>
</tr>
<tr>
<td>30</td>
<td>6300</td>
<td>4970</td>
</tr>
<tr>
<td>35</td>
<td>7980</td>
<td>3990</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The packet drop in the initialization phase is depicted in the <xref ref-type="table" rid="table-3">Tab. 3</xref>. For node 40, the experiment lasted 10 s. When data transmission fails to reach its destination in a timely manner, it is referred to as packet drop. Packets are frequently dropped before reaching their destination. When there is a delay in bypassing the attacker, packet loss is observed to be moderately significant in Existing system.</p>
</sec>
</sec>
</sec>
<sec id="s5">
<label>5</label>
<title>Conclusion</title>
<p>Trust management is critical for providing a seamless and dependable communication process between the IoMT integrated eHealth network devices. In a big decentralized system, maintaining reliable communications among various devices is a difficult challenge. A novel method called Node Authentication (NA) with OLSR was presented for this purpose, and the proposed approach was able to mitigate the gray hole attack. The potency of the attack was increased when the attacker was permitted to follow the victim around. The information used to defend the 5G Device to Device (D2D) network was entirely based on the victim&#x2019;s knowledge. The use of a trustworthy third party is no longer necessary. Furthermore, the identical technology that was employed in the attack enhanced the level of protection. With the identification of the topology used and by promoting fictitious nodes, a node can able to detect the suspicious nodes and prevent them designating as a lone MPR, thus avoiding the attack&#x2019;s most key exploit.</p>
<p>This proposed OLSR-based attack mitigation approach could prevent Gray-hole as well as black-hole attacks. We have collected the packet details with a couple of points and also used the internal knowledge gathered by participating nodes, to analyse the node authentication mechanisms. One of the vital concerns is that a non-stop attacker may be attempting to modify network architecture in order to find the security breaches. Although undetected latent attackers could able to drop packets the chances of violating security with the exploits will be significantly reduced since there is no assurance that the routes may be passing through the attacker nodes. We assign a unique key to each independent node to improve node and network security. The node validates the key value when the data transmission from source to destination takes place. If key value found to be correct, the packet will be successfully transmitted. This modified key-based approach, would improve the network security and prevent most similar type of attacks, such as DDOS attempts. The key will be created using a hash function such as MD5 or SHA-1. The suggested approach takes into account the node security by assigning each node a unique key. While the node initialization, the unique key will be shared between nodes. The key will be validated before transmitting the packet to the next hop, boosting the overall network security. The performance analysis of the proposed system exhibits 98.23% of Packet Delivery Ratio and 10% of end to end transmission delay which is proven to be an outperforming performance when compared to the existing methodologies. In future, the proposed work can be extended by identifying the malicious devices at the initial stages and shall be isolated from the network.</p>
</sec>
</body>
<back><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>S.</given-names> <surname>Challa</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Wazid</surname></string-name>, <string-name><given-names>A. K.</given-names> <surname>Das</surname></string-name>, <string-name><given-names>N.</given-names> <surname>Kumar</surname></string-name>, <string-name><given-names>A. G.</given-names> <surname>Reddy</surname></string-name> <etal>et al.</etal></person-group><italic>,</italic> &#x201C;<article-title>Secure signature-based authenticated key establishment scheme for future IoT applications</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>5</volume>, no. <issue>1</issue>, pp. <fpage>3028</fpage>&#x2013;<lpage>3043</lpage>, <year>2017</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>T.</given-names> <surname>Li</surname></string-name>, <string-name><given-names>C.</given-names> <surname>Lee</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Weng</surname></string-name> and <string-name><given-names>S. J.</given-names> <surname>Chen</surname></string-name></person-group>, &#x201C;<article-title>A secure dynamic identity and chaotic maps based user authentication and key agreement scheme for e-healthcare systems</article-title>,&#x201D; <source>Journal of Medical Systems</source>, vol. <volume>40</volume>, no. <issue>11</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>10</lpage>, <year>2016</year>.</mixed-citation></ref>
<ref id="ref-3"><label>[3]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>D.</given-names> <surname>Raffo</surname></string-name>, <string-name><given-names>C.</given-names> <surname>Adjih</surname></string-name>, <string-name><given-names>T.</given-names> <surname>Clausen</surname></string-name> and <string-name><given-names>P.</given-names> <surname>Muhlethaler</surname></string-name></person-group>, &#x201C;<article-title>Securing OLSR using node locations</article-title>,&#x201D; in <conf-name>Proc. European Wireless Conf. 2005-Next Generation Wireless and Mobile Communications and Services</conf-name>, <publisher-loc>Nicosia, Cyprus</publisher-loc>, vol. <volume>5</volume>, pp. <fpage>1</fpage>&#x2013;<lpage>7</lpage>, <year>2005</year>. </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>H.</given-names> <surname>Liu</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Xia</surname></string-name> and <string-name><given-names>Q. T.</given-names> <surname>Wang</surname></string-name></person-group>, &#x201C;<article-title>Research on a secure and energy-efficient routing protocol for Ad Hoc networks</article-title>,&#x201D; <source>Journal of Physics</source>, vol. <volume>48</volume>, no. <issue>2</issue>, pp. <fpage>83</fpage>&#x2013;<lpage>88</lpage>, <year>2021</year>.</mixed-citation></ref>
<ref id="ref-5"><label>[5]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>T. P.</given-names> <surname>Venkatesan</surname></string-name>, <string-name><given-names>P.</given-names> <surname>Rajakumar</surname></string-name> and <string-name><given-names>A.</given-names> <surname>Pitchaikkannu</surname></string-name></person-group>, &#x201C;<article-title>A overview of proactive routing protocols in MANET</article-title>,&#x201D; in <conf-name>Proc. Int. Conf. on Communication Systems and Network Technologies</conf-name>, <publisher-loc>Bhopal, India</publisher-loc>, pp. <fpage>173</fpage>&#x2013;<lpage>177</lpage>, <year>2014</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>A.</given-names> <surname>Kurniawan</surname></string-name></person-group>, &#x201C;<article-title>Selective route based on SNR with cross-layer scheme in wireless ad hoc network</article-title>,&#x201D; <source>Journal of Computer Networks and Communications</source>, vol. <volume>25</volume>, pp. <fpage>1</fpage>&#x2013;<lpage>13</lpage>, <year>2017</year>.</mixed-citation></ref>
<ref id="ref-7"><label>[7]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>C.</given-names> <surname>Tata</surname></string-name> and <string-name><given-names>M.</given-names> <surname>Kadoch</surname></string-name></person-group>, &#x201C;<article-title>Secure multipath routing algorithm for device-to-device communications for public safety over LTE heterogeneous networks</article-title>,&#x201D; in <conf-name>Proc. Int. Conf. on Future Internet of Things and Cloud</conf-name>, <publisher-loc>Washington</publisher-loc>, vol. <volume>7</volume>, pp. <fpage>212</fpage>&#x2013;<lpage>217</lpage>, <year>2015</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>Patil</surname></string-name>, <string-name><given-names>N.</given-names> <surname>Marathe</surname></string-name> and <string-name><given-names>V.</given-names> <surname>Jethani</surname></string-name></person-group>, &#x201C;<article-title>Improved ALERT protocol in MANET with strategies to prevent DoS &#x0026; MITM attacks</article-title>,&#x201D; in <conf-name>Proc. Int. Conf. on Automatic Control and Dynamic Optimization Techniques</conf-name>, <publisher-loc>Pune, India</publisher-loc>, vol. <volume>21</volume>, pp. <fpage>372</fpage>&#x2013;<lpage>377</lpage>, <year>2017</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>J. A.</given-names> <surname>Kumar</surname></string-name> and <string-name><given-names>A.</given-names> <surname>Choorasiya</surname></string-name></person-group>, &#x201C;<article-title>A security enhancement of AODV routing protocol in mobile ad hoc network</article-title>,&#x201D; in <conf-name>Proc. Int. Conf. on Communication and Electronics Systems (ICCES)</conf-name>, <publisher-loc>Coimbatore, India</publisher-loc>, pp. <fpage>958</fpage>&#x2013;<lpage>964</lpage>, <year>2017</year>. </mixed-citation></ref>
<ref id="ref-10"><label>[10]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>M.</given-names> <surname>Marimuthu</surname></string-name> and <string-name><given-names>L.</given-names> <surname>Krishnamurthi</surname></string-name></person-group>, &#x201C;<article-title>Enhanced OLSR for defense against DoS attack in ad hoc networks</article-title>,&#x201D; <source>Journal of Communications and Networks</source>, vol. <volume>15</volume>, no. <issue>1</issue>, pp. <fpage>31</fpage>&#x2013;<lpage>37</lpage>, <year>2013</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>S. R.</given-names> <surname>Deshmukh</surname></string-name> and <string-name><given-names>N.</given-names> <surname>Chatur</surname></string-name></person-group>, &#x201C;<article-title>Secure routing to avoid black hole affected routes in MANET</article-title>,&#x201D; in <conf-name>Proc. Symp. on Colossal Data Analysis and Networking (CDAN)</conf-name>, <publisher-loc>Indore, India</publisher-loc>, vol. <volume>16</volume>, pp. <fpage>1</fpage>&#x2013;<lpage>4</lpage>, <year>2016</year>. </mixed-citation></ref>
<ref id="ref-12"><label>[12]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Bhardwaj</surname></string-name></person-group>, &#x201C;<article-title>Secure routing in DSR to mitigate black hole attack</article-title>,&#x201D; in <conf-name>Proc. Int. Conf. on Control, Instrumentation, Communication and Computational Technologies (ICCICCT)</conf-name>, <publisher-loc>Kaniyakumari, India</publisher-loc>, vol. <volume>13</volume>, pp. <fpage>985</fpage>&#x2013;<lpage>989</lpage>, <year>2014</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>K.</given-names> <surname>Singh</surname></string-name> and <string-name><given-names>S.</given-names> <surname>Sharma</surname></string-name></person-group>, &#x201C;<article-title>A new technique for AODV based secure routing with detection blackhole</article-title>,&#x201D; in <conf-name>Proc. IEEE Int. Conf. on Power, Control, Signals and Instrumentation Engineering</conf-name>, <publisher-loc>Washington, United Sates of America</publisher-loc>, vol. <volume>41</volume>, pp. <fpage>1528</fpage>&#x2013;<lpage>1534</lpage>, <year>2017</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>G.</given-names> <surname>Chengetanai</surname></string-name></person-group>, &#x201C;<article-title>Minimising black hole attacks to enhance security in wireless mobile ad hoc networks</article-title>,&#x201D; in <conf-name>IST-Africa Week Conf.</conf-name>, <publisher-loc>Washington, United States of America</publisher-loc>, vol. <volume>12</volume>, pp. <fpage>1</fpage>&#x2013;<lpage>7</lpage>, <year>2018</year>. </mixed-citation></ref>
<ref id="ref-15"><label>[15]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Yadav</surname></string-name>, <string-name><given-names>M. C.</given-names> <surname>Trivedi</surname></string-name>, <string-name><given-names>V. K.</given-names> <surname>Singh</surname></string-name> and <string-name><given-names>M. L.</given-names> <surname>Kolhe</surname></string-name></person-group>, &#x201C;<article-title>Securing AODV routing protocol against black hole attack in MANET using outlier detection scheme</article-title>,&#x201D; in <conf-name>Proc. 4th IEEE Uttar Pradesh Section Int. Conf. on Electrical, Computer and Electronics (UPCON)</conf-name>, <publisher-loc>United States of America</publisher-loc>, vol. <volume>26</volume>, pp. <fpage>1</fpage>&#x2013;<lpage>4</lpage>, <year>2017</year>. </mixed-citation></ref>
<ref id="ref-16"><label>[16]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>D.</given-names> <surname>Prabakaran</surname></string-name> and <string-name><given-names>S.</given-names> <surname>Ramachandran</surname></string-name></person-group>, &#x201C;<article-title>Multi-factor authentication for secured financial transactions in cloud environment</article-title>,&#x201D; <source>Computers, Materials &#x0026; Continua</source>, vol. <volume>70</volume>, no. <issue>1</issue>, pp. <fpage>1781</fpage>&#x2013;<lpage>1798</lpage>, <year>2022</year>.</mixed-citation></ref>
<ref id="ref-17"><label>[17]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>J. V.</given-names> <surname>Vadavi</surname></string-name> and <string-name><given-names>A. G.</given-names> <surname>Sugavi</surname></string-name></person-group>, &#x201C;<article-title>Detection of black hole attack in enhanced AODV protocol</article-title>,&#x201D; in <conf-name>Proc. Int. Conf. on Computing and Communication Technologies for Smart Nation (IC3TSN)</conf-name>, <publisher-loc>Gurgaon, India</publisher-loc>, pp. <fpage>118</fpage>&#x2013;<lpage>123</lpage>, <year>2017</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>D.</given-names> <surname>Nitnaware</surname></string-name> and <string-name><given-names>A.</given-names> <surname>Thakur</surname></string-name></person-group>, &#x201C;<article-title>Black hole attack detection and prevention strategy in DYMO for MANET</article-title>,&#x201D; in <conf-name>Proc. 3rd Int. Conf. on Signal Processing and Integrated Networks (SPIN)</conf-name>, <publisher-loc>Delhi, India</publisher-loc>, pp. <fpage>279</fpage>&#x2013;<lpage>284</lpage>, <year>2016</year>. </mixed-citation></ref>
<ref id="ref-19"><label>[19]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>M.</given-names> <surname>Ahmed</surname></string-name> and <string-name><given-names>M. A.</given-names> <surname>Hussain</surname></string-name></person-group>, &#x201C;<article-title>Performance of an IDS in an ad hoc network under black hole and gray hole attacks</article-title>,&#x201D; in <conf-name>Proc. Int. Conf. on Electronics, Communication and Instrumentation (ICECI)</conf-name>, <publisher-loc>Newyork, USA</publisher-loc>, pp. <fpage>1</fpage>&#x2013;<lpage>4</lpage>, <year>2014</year>. </mixed-citation></ref>
</ref-list>
</back>
</article>