Fronthaul

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Materialscientist (talk | contribs) at 11:20, 29 November 2020 (Reverted edits by Dctg44 (talk): not providing a reliable source (WP:CITE, WP:RS) (HG) (3.4.10)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The fronthaul portion of a C-RAN (Cloud Radio Access Network) telecommunications architecture comprises the intermediate links between the centralized radio controllers and the radio heads (or masts) at the "edge" of a cellular network.[1]

In general it is coincident with the backhaul network, but subtly different. Technically in a C-RAN the backhaul data is only decoded from the fronthaul network at the centralised controllers, from where it is then transferred to the core network.

It comprises dedicated fibers carrying data in the CPRI or OBSAI format.[2] This fiber network is either owned or leased by the mobile network operator. In the UK for example BT Openworld owns a majority of the fiber network to radio masts. There are proposals to modify Ethernet to make it more suitable for the Fronthaul network.[3]

Recently, a novel wireless fronthaul solution has been proposed for ultra-dense small cell deployment where networked flying platforms (NFPs) such UAVs, drones, tethered balloon and high-altitude/medium-altitude/low-altitude platforms carrying FSO transceivers have been introduced as aerial hubs to aggregate the small cell traffic and offer connectivity to the core network.[4]

References

  1. ^ http://www.lightreading.com/what-the--bleep--is-fronthaul/a/d-id/707868
  2. ^ http://www.equicom.hu/wp-content/uploads/EXFO_anote310_Understanding-Basics-CPRI-Fronthaul-Technology_en.pd[permanent dead link]
  3. ^ http://www.ieee1904.org/3/meeting_archive/2015/02/tf3_1502_ashwood_1a.pdf
  4. ^ Alzenad, M.; Shakir, M. Z.; Yanikomeroglu, H.; Alouini, M.-S. (2018). "FSO-based vertical backhaul/fronthaul framework for 5G+ wireless networks". IEEE Communications. 56 (1): 218–224. arXiv:1607.01472. doi:10.1109/MCOM.2017.1600735.