Page 76 - sjsi
P. 76
Research Article: Althalji et al 76
complexity is high . Safaei (2022) [15] . The nodes to be aware of their current speed in case
research proposed ARMOR protocol by using a it changes . The related works showed there was
new parameter TTR to select the best parent a need for a protocol that supports mobility,
node that will stay the longest within the radio they worked on that but this led to an increase
range. TTR is calculated based on the node's in delay and overhead in the network. In this
speed and position, and it is added to the DIO research, new control message was proposed
message. A new timer was added to increase to make the nodes aware of parent node
the rate of sending DIO messages by the fixed movement to take into account the appropriate
node in order to introduce itself and to be time for changing the parent node without
selected as the parent node by the mobile waiting for the timer specified in standard RPL
nodes. The mobile nodes did not modify their protocol .
timer, but this is not suitable for its neighbor
Table 1: Related works
Protocol Proposed method Disadvanteges
mRPL[6] sent n DIS Increased overhead
ARPL[7] Used ETX, RSSI RSSI effect with obstacles
MT-RPL[8] Cross-layer protocol Relies on opportunistic forwarder
RRD [9] Used RSSI, Rank, and Dynamic Did not consider energy consumption
mRPL+ [10] Depend on overhearing Increased power consumption
EMA-RPL[11] Mobile node as leaf Did not support mobility
EKF-MRPL [12] Used kalman filter, RSSI RSSI effect with obstacles
FL-RPL [13] Used fuzzy logic, RSSI RSSI effect with obstacles
FA-RPL [14] Uesd firefly algorithm computational complexity is high
ARMOR [15] Used TTR parameter Increase the rate of sending DIO messages
Proposed approach granularity [16] . Since RPL control messages take
]3[
To develop a mechanism for detecting routing the following values .
adjacency failures caused by mobile nodes, a 0 |x00 | DODAG Information Solicitation (DIS)
new control message (Here) is proposed. Here 0 |x01 | DODAG Information Object (DIO)
control message is an ICMP information 0 |x02 | Destination Advertising Object (DAO)
message type about the state of the mobile 0 |x03 | DAO Acknowledgment (DAO - ACK) .
node, consists of an ICMPv6 header followed by So the suggested message HERE can be
a message body, as illustrated in Figure 2 . assigned a value of 4 .
ICMPv6 header 0 |x04 | HERE
•Type: 8-bit. it indicates the type of message. Checksum: The checksum field is used to detect
The type value for the HERE control message is data corruption in an ICMPv6 message [16] .
200 because IANA has defined an ICMPv6 Type
Number Registry, the values (0-127) are for
error messages, while the range (128-255) is for
information messages and the values 200 and
201 are reserved for private experimentation
[16] .
•(Code) depends on the type of message. It is
used to create an additional level of message
SJSI – 2023: VOLUME 1-1
