Abstract
Millimeter-wave (mm-wave) technologies are the main driver to deliver the multiple-Gbps promise in next-generation wireless access networks. However, the GHz-bandwidth potential must coexist with a harsh propagation environment. While strong attenuations can be compensated by directional antenna arrays, the severe impact of obstacle blockages can only be mitigated by smart resource allocation techniques. Multi-connectivity, as multiple mm-wave links from a mobile device to different base stations, is one of them. However, the higher reliability provided by several access alternatives can be fully exploited only if uncorrelated link statuses are guaranteed. Therefore, spatial diversity must be enforced. Moreover, since interposing obstacles can block a link, short access links allow reducing the link unavailability probability. Smart base-station selections can be made once the network is deployed, however, our results show that much better results are achievable if spatial diversity and link-length aspects are directly included in the network planning phase. In this article, we propose an mm-wave access network planning framework that considers base-station spatial diversity, link lengths, and achievable user throughput, according to channel conditions and network congestion. The comparison against traditional k-coverage approaches shows that our approach can obtain much better access reliability, thus providing higher robustness to random obstacles and self-blockage phenomena.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
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.