Neighbor Discovery++: A Low-Overhead Address Auto-configuration to Enable Robust Internet of Things Architectures

Neighbor Discovery ++− a Scalable and Robust Address Auto-Configuration for Future Internet of Things Networks

“…The results showed that ND++ achieved good performance in small network set-ups. Hence, we followed with a simulation-based evaluation to observe ND++ behavior in medium-and large-scale networks under diversified networking conditions [26], [27], [29]- [31]. This study enabled us to improve ND++ algorithmic schemes and behavior as well as to identify the most flexible and network-independent protocol set-up.…”

“…To address the above challenges, we have proposed Neighbor Discovery++ [24]- [27] for the IPv6-based MANET networks. This solution not only extends the range of the ND protocol, making it capable of reaching all MANET nodes during AAC, but also focuses on flooding optimization.…”

“…The particular ND++ set-up has strong impact on the protocol overhead and performance. Our previous investigations have identified the most accurate parameter values [27], [29]- [31], so that ND++ is capable of addressing the needs of diversified network types and sizes. Figure 3 presents the execution (in time) of the DAD++ procedure and the parallel MPR processes performed by a given node for the exemplary network situation.…”

“…In order to overcome these issues, we propose an extension to ND protocol -the Neighbor Discovery ++ (ND++) [24]- [27]. Through this approach we have managed to incorporate one of the well-performing flooding control mechanisms based on the Multipoint Relay (MPR) concept [28] into the DAD process.…”

“…In our previous works on this topic [24]- [27], [29]- [31], we proposed initial ND++ set-up and performed baseline evaluation of ND++. We presented a proof-of-concept evaluation of ND++ in the real-world testbed platform [25] and followed with an initial simulation-based evaluation [26], [27], [29]- [31]. All scenarios investigated to date considered a situation where a single node was starting DAD for a new IPv6 address in static MANET network setups (without mobility).…”