Abstract
|
RPL, an IPv6-based ""Routing Protocol for Low Power and Lossy Network,"" addresses the popularisation of various real-time IoT (Internet of Things) applications designed to meet the varied requirements for sensor networks designed to support the unique characteristics of Low power and lossy Networks (LLNs). The hardest problems in the LLNs are considered to be data routing and traffic prioritisation. Numerous studies have demonstrated that Standard RPL performs very poorly to meet the Network Layer QoS requirements for the IoT network created by linking nodes that operate on a single instance's common objective function. It has a significant influence/effect on the claims of RPL in numerous scenarios for IoT applications, such as LLN with Multiple Instances for Supporting the Routing of Heterogeneous Data and traffic. To address this concern, we propose to build RPL with Multiple Instances within a single network which meets the demand for diverse data traffic and further enhances the performance of practical real-time applications. We built Multiple Instances (Traffic Classes) on the Contiki Operating System (OS), an open-source operating system for building the Internet of Things. To support the QoS differentiation at the network layer, the proposed Multi-Instance RPL defines three instances for three different types of data traffic classes. Each instance will demonstrate a different traffic class by adapting various Objective Functions, such as Objective Function 0 (OF0) and Minimum Rank with Hysteresis Objective Function (MRHOF), which select the appropriate routing metrics to choose the most suitable route for each RPL instance. Through simulations for three crucial routing performance indicators like Average Packet Delivery Ratio, Average delay and Average Energy Consumption, the effectiveness of the proposed mechanism is investigated. The obtained results outperform the standard RPL with an increased/ improved Packet delivery ratio and much lower latency for the priority traffic. Furthermore, we continue by stating that the results are much better if the NullRDC protocol is considered for Priority Traffic Class to meet the demands of High reliability and delay-constrained traffic.
|