has been a need to relax the fronthaul require- ments in order to enable the use of widely available transport networks such as packet- based Ethernet or E-band microwave. With such transport networks, bandwidth may be limited, jitter may be higher, and latencies may be on the order of several milliseconds. Cloud-RAN architecture is able to support different functional splits. Centralizing only a portion of the baseband functions and leaving the remaining functions at the remote sites would be a way to relax the fronthaul requirements. Depending on which functions are centralized, we will have different bandwidth, latency, and jitter requirements. In a C-RAN architecture, the RRHs are connected to the BBU pool through high-bandwidth transport links known as fronthaul. There are a few standard interface options between the RRH and BBU including CPRI, radio-over-Ethernet (RoE), and Ethernet. However, CPRI and its most recent version, eCPRI, are currently the most common technologies used by C-RAN equipment vendors. The fronthaul link is responsible for carrying the radio signals, typically over an OTN, using either digitized form based on protocols such as the CPRI, or in analog form through radio-over-fiber technology. The main advantage of digitized transmission is the reduced signal degradation, allowing data transmission over longer distances, offering higher degree of BBU centralization. The common fronthaul solution in C-RAN is to use dedicated fiber. However, centralization requires use of a large number of fiber links which are limited and expensive to deploy. Alternative solutions include the use of other transport technologies such as WDM and OTN, or even the transmission of fronthaul data wirelessly using micro- wave or mmWave frequency bands. CPRI imposes very strict requirements on the fronthaul network. These requirements make the fronthaul network very expensive to deploy, thereby offsetting the cost saving expected from C-RAN. It can therefore be argued that the fronthaul network could become the bo