Thursday School : CRAN Makes sites Cheaper. Today I’m sharing modelling how CRAN reduces costs from our very successful Cambridge Wireless Ltd session yesterday. I used the word ‘pooling’ several times, and here is an example of why a baseband pool is smaller that the equivalent DRAN deployment. The coloured dots represent levels of users at different times of day in different locations. Traditionally each site would have capacity for it’s own peak. But the peaks are at different times so the same Baseband Compute Pool covering the Bridge during rush hour could be used for the arrival of the Brittany Ferry, and residential eMBB in evenings. This is known as Elasticity pooling. Studies have shown at least 16% pooling benefit. There are additional pooling benefits be removing 'rounding-up' elements associated with DRAN BBU (you cannot put '1.3' BBU on a site) by allocating the appropriate resources within a pool of - say - 30-50 sites. #EveryDaysaSchoolDay #Telecommunications #BeautifulInfrastructure #Statistics #5ginnovation Previous Post: https://lnkd.in/dytFcQYy
I’m willing to forgive the tautology in the first sentence in exchange for another thought-proving Thursday in the cellular classroom
Paul - Great inputs on these concepts. Thanks for the invite yesterday! Sorry I couldn't stay longer.
Global Lead - RAN Systems Architect 5G at Dell Technologies
1 年As discussed Paul - CRAN can work but the Fronthaul Transport needs to match the one way latency reqs from the DU function to the RU over approx. 110microseconds and deliver timing accuracy to +/- 10ns with nanosecond phase needed between adjacent RUs on a common DU and adjacent RUs on adjacent DUs - basically means an upgrade to the entire access transport for the coverage area. I covered this in my presentation at ITSF 2023 in Antwerp. In addition, the DU/CU s/w needs to be able to pool across sites according to traffic patterns, where today there is … room for improvement. Hence, most MNOs are looking at Central CU.. an edge cloud at the pre-aggregation level and hosting the Near-RT RIC at the same site with the associated x.Apps due to the 10ms RTT latency limitation on those apps. The DU sits at the cell site or close by for a group of densification small cells… as we are deploying in Milton Keynes.