6,575
edits
mNo edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
Although Open Ran can do without Virtual Ran (vRan) and Cloud Ran(cRan), their addition to the network will enable the operator to reap its full benefits<ref name=":0" />. Virtualization is the separation of hardware and software features. On the other hand, Cloud Ran refers to the realization of RAN functions over a generic computing platform instead of visiting a network site. Any RAN performance issues can cause havoc to the customer; hence its operations need to be handled via a data center approach<ref name=":2" />. This is accomplished via virtualization and cloud-native architecture. It should also be noted that the RAN’s flexibility will not be fully achieved without virtualization. | Although Open Ran can do without Virtual Ran (vRan) and Cloud Ran(cRan), their addition to the network will enable the operator to reap its full benefits<ref name=":0" />. Virtualization is the separation of hardware and software features. On the other hand, Cloud Ran refers to the realization of RAN functions over a generic computing platform instead of visiting a network site. Any RAN performance issues can cause havoc to the customer; hence its operations need to be handled via a data center approach<ref name=":2" />. This is accomplished via virtualization and cloud-native architecture. It should also be noted that the RAN’s flexibility will not be fully achieved without virtualization. | ||
Reduces reliance on one vendor | ===Reduces reliance on one vendor=== | ||
Open Ran eliminates reliance on one vendor. This was common in single vendor deployments; hence fixing issues were prone to take a long time. With multi-vendor deployments, an issue affecting the network falls on all parties involved<ref>https://www.parallelwireless.com/wp-content/uploads/Parallel-Wireless-e-Book-Everything-You-Need-to-Know-about-Open-RAN.pdf</ref>. This protects the operator's investment and reduces adverse impact on the end-user. | Open Ran eliminates reliance on one vendor. This was common in single vendor deployments; hence fixing issues were prone to take a long time. With multi-vendor deployments, an issue affecting the network falls on all parties involved<ref>https://www.parallelwireless.com/wp-content/uploads/Parallel-Wireless-e-Book-Everything-You-Need-to-Know-about-Open-RAN.pdf</ref>. This protects the operator's investment and reduces adverse impact on the end-user. | ||