6,294
edits
Assessment of Open Ran: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
[[File:Open RAN IMAGE.png|thumb|330x330px|https://www.ifri.org/sites/default/files/atoms/files/velliet_open_ran_2022_us.pdf<nowiki/>page.10]] | [[File:Open RAN IMAGE.png|thumb|330x330px|https://www.ifri.org/sites/default/files/atoms/files/velliet_open_ran_2022_us.pdf<nowiki/>page.10]] | ||
As shown in figure 2, the Open Ran architecture disaggregates the BBU into DU and CU using the 3rd Generation Partnership Project (3GPP) standards and creates open interfaces between them. The open interfaces enable the operator to incorporate many vendors into its network, as we will discuss further in this report. However, it should be noted that this is not the only work of the Open Ran architecture. With Open Ran deployment, the operator benefits from its many other features. | As shown in figure 2, the Open Ran architecture disaggregates the BBU into DU and CU using the 3rd Generation Partnership Project (3GPP) standards and creates open interfaces between them. The open interfaces enable the operator to incorporate many vendors into its network, as we will discuss further in this report. However, it should be noted that this is not the only work of the Open Ran architecture. With Open Ran deployment, the operator benefits from its many other features. | ||
== Overview == | == Overview == | ||
{| class="wikitable" | |||
|+ | |||
!Bullish | |||
!Bear | |||
|- | |||
|Eliminates vendor lock-ins | |||
|Integration is challenging | |||
|- | |||
|Provides flexibility | |||
|Interoperability issues | |||
|- | |||
|Makes the ecosystem diverse | |||
|COTs hardware consume more power than proprietary solutions | |||
|- | |||
|Reduces maintenance costs | |||
|Performance has not been fully proven | |||
|- | |||
|Fixing of errors will be fast | |||
|More cyber attack surface | |||
|- | |||
|Reduces reliance on one vendor | |||
|It is yet to be known whether Open RAN will support clients in high-density areas | |||
|- | |||
|Encourages ecosystem's collaboration | |||
|Multiple vendors are hard to manage | |||
|- | |||
|Integration is easier in greenfield deployments | |||
| | |||
|- | |||
|Soon operators will be able to use COTs hardware alternatives | |||
| | |||
|- | |||
|Industry is working on more testing solutions that will fix interoperability challenges | |||
| | |||
|- | |||
|More eyes monitoring cyber security issues | |||
| | |||
|- | |||
|Trade-off between benefits and costs is positve(40% reduction in costs) | |||
| | |||
|- | |||
|Almost all the telecommunications operators are bullish on it | |||
| | |||
|- | |||
|Governments are in support of Open RAN | |||
| | |||
|} | |||
==Benefits of Open Ran== | ==Benefits of Open Ran== | ||