Abstract
In this paper, we characterize the channel for fifth-generation (5G) millimeter-wave (mmWave) railway communications. In order to involve the railway features in the channel models, we realize extensive ray-tracing simulations in the 60 GHz band with 8 GHz bandwidth in realistic mmWave railway scenarios. The four angular spreads - azimuth angular spread of arrival (ASA) and departure (ASD), elevation angular spread of arrival (ESA) and departure (ESD) - are extracted and analyzed in detail. This angular domain information together with our previous work on path loss exponent, shadow factor, Ricean K-factor, and root-mean-square (RMS) delay spread, characterize the 5G mmWave railway channel comprehensively. The two parameter tables can be input into the standard channel models.
Links
BibTeX (Download)
@inproceedings{8644076,
title = {Realistic Channel Characterization for 5G Millimeter-Wave Railway Communications},
author = {Ke Guan and Danping He and Bo Ai and Andrej Hrovatz and Junhyeong Kim and Zhangdui Zhong and Thomas K\"{u}rner},
doi = {10.1109/GLOCOMW.2018.8644076},
year = {2018},
date = {2018-12-01},
urldate = {2018-12-01},
booktitle = {2018 IEEE Globecom Workshops (GC Wkshps)},
pages = {1-6},
abstract = {In this paper, we characterize the channel for fifth-generation (5G) millimeter-wave (mmWave) railway communications. In order to involve the railway features in the channel models, we realize extensive ray-tracing simulations in the 60 GHz band with 8 GHz bandwidth in realistic mmWave railway scenarios. The four angular spreads - azimuth angular spread of arrival (ASA) and departure (ASD), elevation angular spread of arrival (ESA) and departure (ESD) - are extracted and analyzed in detail. This angular domain information together with our previous work on path loss exponent, shadow factor, Ricean K-factor, and root-mean-square (RMS) delay spread, characterize the 5G mmWave railway channel comprehensively. The two parameter tables can be input into the standard channel models.},
keywords = {mmWave},
pubstate = {published},
tppubtype = {inproceedings}
}