6,575
edits
Assessment of Open Ran: Difference between revisions
no edit summary
mNo edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
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 name=":3">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 name=":3">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. | ||
===Challenges of Open Ran=== | |||
1. Interoperability issues | |||
Multiple vendors can only be used in the network if their hardware and software solutions are compatible. Although O-Rance Alliance provides a platform for interoperability testing, such testing is not enough to ensure compatibility between different vendor solutions. Also, interoperability is a continuous process which is time consuming and expensive. For instance, interoperability testing should be done everytime there is a software update. | |||
==References== | ==References== | ||
<references /> | <references /> | ||