6,294
edits
No edit summary |
|||
Line 193: | Line 193: | ||
Because there is a growing number of Open RAN labs targeted at solving integration and interoperability issues, we can expect those operators concerned with such problems to change their minds. That said, greenfield deployments will continue rising as Open RAN maturity approaches. The current projection indicates that Open RAN will achieve maturity by 2026<ref>https://www2.deloitte.com/content/dam/Deloitte/pt/Documents/technology-media-telecommunications/TEE/The-Open-Future-of-Radio-Access-Networks.pdf page.26</ref>. This is achievable considering that operators like 1&1, Rakuten, Dish, and DTT Docomo would have deployed it at scale in macro and MIMO settings. However, we don't expect Open RAN to replace traditional RAN completely since some operators would prefer a single vendor in some instances. As Patrick Lopez, Global VP of Product Management for 5G at NEC, notes, "I don't think Open RAN will replace all traditional RAN deployments. There will be a space for every type of RAN. In some cases, deploying a specialized, proprietary RAN system from one vendor will make sense. In most other cases, it will make more sense to have a multi-vendor implementation where you can use resource pooling."<ref>https://senzafili.com/wp-content/uploads/2022/12/SenzaFili_DD_ORAN_Ecosystem.pdf<nowiki/>page. 48</ref> | Because there is a growing number of Open RAN labs targeted at solving integration and interoperability issues, we can expect those operators concerned with such problems to change their minds. That said, greenfield deployments will continue rising as Open RAN maturity approaches. The current projection indicates that Open RAN will achieve maturity by 2026<ref>https://www2.deloitte.com/content/dam/Deloitte/pt/Documents/technology-media-telecommunications/TEE/The-Open-Future-of-Radio-Access-Networks.pdf page.26</ref>. This is achievable considering that operators like 1&1, Rakuten, Dish, and DTT Docomo would have deployed it at scale in macro and MIMO settings. However, we don't expect Open RAN to replace traditional RAN completely since some operators would prefer a single vendor in some instances. As Patrick Lopez, Global VP of Product Management for 5G at NEC, notes, "I don't think Open RAN will replace all traditional RAN deployments. There will be a space for every type of RAN. In some cases, deploying a specialized, proprietary RAN system from one vendor will make sense. In most other cases, it will make more sense to have a multi-vendor implementation where you can use resource pooling."<ref>https://senzafili.com/wp-content/uploads/2022/12/SenzaFili_DD_ORAN_Ecosystem.pdf<nowiki/>page. 48</ref> | ||
== Open-RAN Greenfield operators facing problems? == | |||
March 22, 2o23: | |||
* Rakuten has reported about $5 billion losses in its four years of entry into the telecom industry and has managed to capture only 5 million subscribers in a country with a popuation of 126 million<ref name=":1">https://www.lightreading.com/regulatorypolitics/1and1-dish-and-rakuten-add-up-to-greenfield-misery/d/d-id/783972</ref>. | |||
* At the beginning of 2023, 1&1 said it had managed to put up only three antenna sites for commercial use yet it has an obligation to launch 1,000 sites before the end of 2022. Its rivals are now using this failure to bully 1&1 with Deutsche Telecom's CEO arguing that 1&1 should not be allowed to participate in the upcoming sub-1GHz frequencies. Without these frequencies, 1&1 will require more sites to cover Germany.<ref name=":1" /> | |||
* Dish network had less than 30% population coverage as at October 2022. It has an obligation to reach 70% coverage by June 2023. The company said that it would achieve this with 15,000 sites. However, this would likely be insufficient as it will mean one site for every 22,000 people unlike Rakuten's network whose footprint ratio is one site for every 2,500 people. Its customer base dropped to 8 million at the end of December from 8.5 million and is forecasted to drop further following recent cypher attack.<ref name=":1" /> | |||
==References== | ==References== | ||
<references /> | <references /> |