RPL Load Balancing in Internet of Things

Abstract

ABSTRACT:Â The wide address space provided by Internet Protocol version 6 (IPv6) lets any thing to be identified uniquely. consistency of the modified version of IPv6 protocol stack with smart objects, facilitated the Internet interconnection of the networks of smart objects and introduced Internet of things. A smart object is a small micro-electronic device that consists of a communication device, a small microprocessor and a sensor or an actuator. A network made of such devices is called low-power and lossy network. RPL routing protocol that is consistent to IPv6, is designed to be used in these kinds of networks. Load balancing is not considered in the RPL design process. Whenever RPL is used in large scale low-power and lossy networks some nodes will suffer from congestion and this problem severely degrades network performance. In this paper, we consider solutions provided to tackle RPL load balancing problems. Load balancing algorithms and protoclos are evaluated through simulation. We evaluate IETF RPL implementation and LB-RPL method with Contiki OS Java (COOJA) simulator. They are assessed comprehensively through metrics such as Packet delivery Ratio, Average End to End delay, and Gateway Throughput. LB-RPL improves RPL in terms of Packet delivery Ratio and throughput but increases Average End to End delay. Simulations results show that RPL load balancing needs extensive works to be performed yet.

DDSLA-RPL: Dynamic Decision System Based on Learning Automata in the RPL Protocol for Achieving QoS

“…The computational overload of this method is a bit high which can lead to early battery depletion. 2017 LB-RPL [27] In this method, the packet ready for transmission in the child node, is distributed among n parents. Also, if the parent is facing congestion, it latency's its packet transmission therefore the child removes the congested parent node from its list.…”

Proposing a new method for improving RPL to support mobility in the Internet of things

“…The DIO message is used to carry the relevant information and configuration parameters that enable a node to discover an RPL instance, join a specific DODAG, select a set of candidate parents according to its objective function (OF) and routeing information (e.g. RANK, DODAG ID) [19], and maintain the DODAG. Destination advertisement object (DAO): DAO messages are sent by each node to populate the routeing tables with prefixes of their children and to advertise their addresses and prefixes to their parents and the DODAG root so that the downward routes from the DODAG root to its associated nodes can be built. DODAG information solicitation (DIS): A newly joined node that does not have a route multicasts the DIS message to solicit a DIO from an RPL node. A node may use DIS to probe its neighbourhood for alongside DODAGs. DAO acknowledgement (DAO‐ACK): The DAO‐ACK is sent as a unicast packet by a DAO recipient to the DAO sender to acknowledge the reception of that DAO message. RPL uses an adaptive timer mechanism called the ‘trickle timer’ [20].…”

“…The DIO message is used to carry the relevant information and configuration parameters that enable a node to discover an RPL instance, join a specific DODAG, select a set of candidate parents according to its objective function (OF) and routeing information (e.g. RANK, DODAG ID) [19], and maintain the DODAG.…”

Weighted Sum Metrics – Based Load Balancing RPL Objective Function for IoT

“…Moreover, the implemented OFs contributing only a single metric for the routing process and the network performance of LLNs in highly dense or dynamic traffic are defective. Moreover, it is worth noting that the implemented OFs contribute only one metric to the operations of LLNs, which is highly defective in routing and load balancing performance on highly dense or dynamic traffic network instances [4].…”