to set up a WSN that contains many Low-power nodes (sensors) and is expected to work well for a long time, the following Design Principles (DPs) can be used:
· DP1: Energy Efficient Design with an energy-aware static routing
This DP consists of designing WSN so that Low-Power Nodes (LPNs) do not serve as forwarders (routers) of transit / foreign data. It should be noted that the LPNs are not installed on the "important and heavily loaded" static routes in the WSN.
· DP2: Reduction of power consumption in LPNs thanks to load-controlled power supply
To maximize battery life, LPNs spend most of their time in a "sleep" mode and then consume little power. Often they are "awakened" periodically according to a fixed communication plan to perform their functions. To increase battery life, the internal timer of the microcontroller (MCU) in LPNs may be load-controlled so that LPNs consume less power. This means a load-dependent power supply of LPNs. For more information about a load-dependent power supply, see my answer to Q1.
· DP3: Use of the IoT Routing Protocol RPL with Energy-aware Metrics
The RPL is intended for use in WSNs with LPNs. For this reason, RPL can also use so-called energy-aware metrics, which take into account the energy state of bateries in LPNs. Such metrics cause the optimal routes in WSNs to not pass through the low power nodes. The RPL thus contributes to extending the lifetime of a WSN with LPNs. This goal can be achieved with the help of RPL and with the objective function MRHOF. The RPL option "DAG Metric Container" is very important for this; see RFC 6550 and RFC 6551 (sections 2.1 (Fig. 1) and 3.2)). In this container you can specify the details of routing metric / constraint types. For you, the Node-based metrics - RE (Remaining Energy) and MLT (Maximum Life Time) - are important.
· DP4: Self-Healing WSN with redundancy nodes
A WSN as at IoT part should be able to repair or even avoid some node failures due to energy shortage, as well as various faulty situations. The RPL can help with energy-aware metrics. There are two principles of self-healing: reactive self-healing and proactive self-healing.
In reactive self-healing, an attempt is made to identify and locate the faulty system components. Then an attempt is made to compensate for the failed functions as far as possible. To enable reactive self-healing in a WSN, some redundancy (redundant nodes, redundant wireless connections) must be "built-in" in the WSN. Reactive self-healing in a WSN means that fault tolerance or even fault tolerance can be activated.
Proactive self-healing attempts to monitor and manage a WSN to prevent possible overloads or failures of system components.
Self-healing in a WSN can be supported using the RPL routing protocols. See my presentation of RPL - and there are the Figures 8361, 8363 and 8366.
· DP 5: WSN with Fault Tolerance
In a WSN with RPL, several DODAGs can overlap. Some important nodes may be part of several DODAGs, so these nodes can be accessed via the Internet via several Border Routers. This would lead to Fault Tolerance. The Figures 008361 and 008363 in my work RPL can help you. See my answer to the question Q6.
My answers to questions Q1, Q2, ..., Q6 can help you.