Abstract
Wireless ad hoc/sensor networks (WASN) have seen increased application in three-dimensional (3D) environments, such as underwater and aerial scenarios. However, WASN may be fragmented or unable to connect continuously due to the harsh surrounding environment or high mobility. Therefore, restoring the network connectivity and transmit data in real time is very important. This paper focuses on the critical task of restoring network connectivity in 3D WASN, a complex issue given that existing connectivity restoration algorithms for two-dimensional environments are not directly applicable or become overly complicated in 3D contexts. We present a comprehensive analysis of the current research landscape, summarizing key findings related to various aspects of 3D WASN connectivity restoration. These aspects include the application environment (underwater, in the sky, and recovery disaster), opportunities for restoration (active, passive, and active/passive), implementation strategies (clustering and sleep scheduling), and resource constraints (node deployment and movement control). Our study also proposes a classification of connectivity restoration solutions for 3D WASN, identifying existing gaps and suggesting potential future research directions. By providing specific insights and a structured overview of the field, we aim to contribute to the ongoing development of robust and resilient 3D WASN.
Published Version (Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
More From: International Journal of Distributed Sensor Networks
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.