IPv6 Multicast Forwarding in RPL-Based Wireless Sensor Networks
read more
Citations
Challenging the IPv6 Routing Protocol for Low-Power and Lossy Networks (RPL): A Survey
The Internet of Things: a security point of view
RPL-Based Routing Protocols in IoT Applications: A Review
A survey on routing protocols supported by the Contiki Internet of things operating system
Toward Improved RPL: A Congestion Avoidance Multipath Routing Protocol with Time Factor for Wireless Sensor Networks
References
RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
The Constrained Application Protocol (CoAP)
A scalable location service for geographic ad hoc routing
Transmission of IPv6 Packets over IEEE 802.15.4 Networks
Multicast operation of the ad-hoc on-demand distance vector routing protocol
Related Papers (5)
Frequently Asked Questions (15)
Q2. What is the trade-off in order to achieve the aforementioned improvements?
The trade-off in order to achieve the aforementioned improvements, is a decrease in packet delivery ratio (increased packet loss), compared to TM which is by design more reliable.
Q3. What are some examples of services which can benefit by multicast forwarding?
Examples of services which can benefit by multicast include service discovery [2,21], network management and publish/subscribe schemes.
Q4. Why does TM forward multicast messages to all parts of the network?
Due to lack of topology maintenance and group registrations, TM forwards all multicast messages to all parts of the network, irrespective of whether they are needed or not.
Q5. What is the effect of network density on the consumption of datagrams?
Consumption due to listening and reception fluctuates slightly more than in the line topology, while network density has a positive effect in total consumption.
Q6. What is the realistic scenario of duty cycled networks?
In the more realistic scenario of duty-cycled networks the authors observe that, in order to minimize delay and packet loss Imin should be configured to a value higher than the CCI.
Q7. How does TM’s performance and energy consumption change?
The authors have demonstrated that TM’s performance and energy consumption are very sensitive to changes in the value of its configuration parameter Imin, with the optimal depending on the choice of underlying duty cycling algorithm.
Q8. Why is SMRF able to deliver more packets than TM?
Since packet trains indirectly mitigate the hidden terminal problem, the performance of SMRF’s (0 , 1) configuration is comparable to the delivery ratio exhibited when Spread >
Q9. What is the percentage of datagrams getting delivered out of order?
The percentage of datagrams getting delivered out-of-order is lower over NullRDC than over ContikiMAC, with low Imin values performing better than their high counterpats.
Q10. What is the impact of routing table size on scalability?
routing table size has an impact on scalability with increasing network size [32] even when the table only lists a single next hop per destination.
Q11. How many bytes of RAM is used in the configuration of the Contiki OS?
In the version of the Contiki OS used for this research, each entry in the IPv6 routing table occupies approximately 48 bytes of RAM, the exact number depending on the hardware platform and toolchain.
Q12. What is the significant factor in the case of TM?
per-node energy consumption is lower with SMRF, with radio transmissions being the most significant factor in the case of TM.
Q13. What happens when a packet is added to the cache?
Upon reception of a multicast datagram, a node inspects the multicast option and, if the packet is new, it gets added to the cache.
Q14. What is the metric for a packet delivery ratio?
Investigating the behaviour of TM for different Imin values, the authors observe that packet delivery ratio can vary between perfect (0% loss) and extremely poor.
Q15. Why is the radio on/off cycle controlled by the duty cycling algorithm?
The reason is that Radio on/off cycles are controlled by the duty cycling algorithm and are thus unrelated to the behaviour of upper layers in the stack.