6,575
edits
Assessment of Open Ran: Difference between revisions
m
no edit summary
No edit summary |
mNo edit summary |
||
| Line 13: | Line 13: | ||
Open Ran has received a lot of interest from telcos due to its many expected benefits. Its ability to expand into other areas, such as automation and virtualization, makes industry players want to deploy it as soon as possible. Below are its main benefits. | Open Ran has received a lot of interest from telcos due to its many expected benefits. Its ability to expand into other areas, such as automation and virtualization, makes industry players want to deploy it as soon as possible. Below are its main benefits. | ||
===It eliminates vendor lock-in=== | ===1. It eliminates vendor lock-in=== | ||
[[File:Parallel Wireless chart.png|thumb|https://www.parallelwireless.com/wp-content/uploads/Parallel-Wireless-e-Book-Everything-You-Need-to-Know-about-Open-RAN.pdf]] | [[File:Parallel Wireless chart.png|thumb|https://www.parallelwireless.com/wp-content/uploads/Parallel-Wireless-e-Book-Everything-You-Need-to-Know-about-Open-RAN.pdf]] | ||
Vendor lock-in is when the network operator is restricted to only one vendor. For instance, in vendor lock-in, the player supplying the hardware should be the same one supplying the software. As illustrated by the Parallel Wireless chart below, Open Ran removes such vendor lock-ins<ref name=":0" />. With Open Ran, an operator can add software from vendor B to hardware from vendor A and vice versa being true. | Vendor lock-in is when the network operator is restricted to only one vendor. For instance, in vendor lock-in, the player supplying the hardware should be the same one supplying the software. As illustrated by the Parallel Wireless chart below, Open Ran removes such vendor lock-ins<ref name=":0" />. With Open Ran, an operator can add software from vendor B to hardware from vendor A and vice versa being true. | ||
===It provides flexibility=== | ===2. It provides flexibility=== | ||
Open Ran provides flexibility in many ways<ref name=":0" />. First, it enables the vendor to choose its hardware and software supplier. This improves the quality of the network. Secondly, it enables the vendor to choose the timeline of various deployments within the Open Ran architecture. For example, the operator can start with a single vendor and then initiate multi-vendor deployments later. Similarly, the operator can choose whether to deploy visualization and automation immediately or wait until the first phase pays off first. Thirdly, Open Ran enables the operator to optimize the network to meet their needs, unlike when the vendor provided a single optimized solution. | Open Ran provides flexibility in many ways<ref name=":0" />. First, it enables the vendor to choose its hardware and software supplier. This improves the quality of the network. Secondly, it enables the vendor to choose the timeline of various deployments within the Open Ran architecture. For example, the operator can start with a single vendor and then initiate multi-vendor deployments later. Similarly, the operator can choose whether to deploy visualization and automation immediately or wait until the first phase pays off first. Thirdly, Open Ran enables the operator to optimize the network to meet their needs, unlike when the vendor provided a single optimized solution. | ||
===Increases diversity=== | ===3. Increases diversity=== | ||
Open Ran removes the monopolistic behavior that has dominated the industry for a long-time. Traditionally, the supply of hardware and software products was shared among three players, namely Ericsson, Nokia, and Huawei<ref name=":1" />. This made the closed network solution supplied by these vendors expensive. However, Open Ran will create diversity as Dr. Femi Adeyemi, Head of Wireless at Fujitsu Network Communications<ref name=":0" />, said, “The entrance barriers are low, and many new players can enter the environment. But the exit barriers are also low. A wide ecosystem forces vendors to be competitive.” Competition among the different vendors will necessitate innovation in an effort to stay relevant in the market. His words were echoed by Peter Claydon, President of Picocom<ref name=":0" />, who said, “Open RAN can democratize the ecosystem by lowering the barriers to entry and allowing more players to enter the market.” With more players, supply of hardware and software solutions will increase, resulting in lower prices. | Open Ran removes the monopolistic behavior that has dominated the industry for a long-time. Traditionally, the supply of hardware and software products was shared among three players, namely Ericsson, Nokia, and Huawei<ref name=":1" />. This made the closed network solution supplied by these vendors expensive. However, Open Ran will create diversity as Dr. Femi Adeyemi, Head of Wireless at Fujitsu Network Communications<ref name=":0" />, said, “The entrance barriers are low, and many new players can enter the environment. But the exit barriers are also low. A wide ecosystem forces vendors to be competitive.” Competition among the different vendors will necessitate innovation in an effort to stay relevant in the market. His words were echoed by Peter Claydon, President of Picocom<ref name=":0" />, who said, “Open RAN can democratize the ecosystem by lowering the barriers to entry and allowing more players to enter the market.” With more players, supply of hardware and software solutions will increase, resulting in lower prices. | ||
===Enables automation=== | ===4. Enables automation=== | ||
Open Ran introduces complexity that did not exist in traditional Ran<ref name=":2">https://www2.deloitte.com/content/dam/Deloitte/pt/Documents/technology-media-telecommunications/TEE/The-Open-Future-of-Radio-Access-Networks.pdf</ref>. This will encourage the operator to deploy various automation features such as Ran Intelligent Controller (RIC), which manages the APIs deployed in the network. RIC leverages analytics and AI/ML, hence resolving issues within the shortest time possible. | Open Ran introduces complexity that did not exist in traditional Ran<ref name=":2">https://www2.deloitte.com/content/dam/Deloitte/pt/Documents/technology-media-telecommunications/TEE/The-Open-Future-of-Radio-Access-Networks.pdf</ref>. This will encourage the operator to deploy various automation features such as Ran Intelligent Controller (RIC), which manages the APIs deployed in the network. RIC leverages analytics and AI/ML, hence resolving issues within the shortest time possible. | ||
===Enables the operator to add virtualization and cloud to its architecture=== | ===5. Enables the operator to add virtualization and cloud to its architecture=== | ||
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=== | ===6. 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 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. | ||
=== 7. Encourages collaboration in the network === | |||
An issue within the network affects all parties involved. Since each vendor would want to protect their reputation, teamwork is created. This allows for automation such as continuous integrations(CI) and continuous deployments(CD), making deployment and fixing errors fast and reliable<ref name=":32">https://www.parallelwireless.com/wp-content/uploads/Parallel-Wireless-e-Book-Everything-You-Need-to-Know-about-Open-RAN.pdf</ref>. Also, CI/CD will foster innovations in that many individuals will work on Open Ran. | |||
===Challenges of Open Ran=== | ===Challenges of Open Ran=== | ||
===1. Integration=== | ===1. Integration=== | ||
| Line 47: | Line 51: | ||
=== 5. Security issues === | === 5. Security issues === | ||
Deployment of multi-vendor solutions increases cyber attacks<ref name=":12">https://www.ifri.org/sites/default/files/atoms/files/velliet_open_ran_2022_us.pdf</ref>. This is acknowledged by a US Government Agency, which wrote, “the attack surface of the network expands considerably.” Although with more vendors come more eyes monitoring security vulnerabilities, the operator ends up incurring more security costs. | Deployment of multi-vendor solutions increases cyber attacks<ref name=":12">https://www.ifri.org/sites/default/files/atoms/files/velliet_open_ran_2022_us.pdf</ref>. This is acknowledged by a US Government Agency, which wrote, “the attack surface of the network expands considerably.” Although with more vendors come more eyes monitoring security vulnerabilities, the operator ends up incurring more security costs. | ||
=== 6. Scalability === | |||
As indicated above, most Open Ran deployments have been carried out in rural and low-density areas, which is troubling because it has yet to be known whether it will support clients' needs in high-density areas. For instance, although NTT Docomo claims its Open Ran deployment in Japan was successful, its deployment was mainly in rural areas, except for some deployments in metropolitan areas of Tokyo<ref>https://www.telecomtv.com/content/open-ran-summit-20/keynote-executive-interview-sadayuki-abeta-40209/</ref>. | |||
=== Open Ran Can Reduce Costs By How Much? === | |||
Cost savings in Open Ran depend on many factors. For instance, an operator can save on the total cost of ownership(TCO) by choosing cheap vendors and proprietary solutions instead of COTs hardware. Adding visualization and cloud-native architecture will also help the vendor reduce maintenance costs. In general, cost savings can only be achieved if the operator chooses the most efficient options offered by Open Ran. But there have been testimonies confirming that Open Ran indeed reduces costs<ref>https://www2.deloitte.com/content/dam/Deloitte/pt/Documents/technology-media-telecommunications/TEE/The-Open-Future-of-Radio-Access-Networks.pdf</ref>. For example, Rakuten said it reduced CAPEX by 40% when it deployed Open Ran instead of traditional Ran. A report by Deloitte indicates that Open Ran can reduce CAPEX and OPEX by up to 50% and 35%, respectively. | |||
==References== | ==References== | ||
<references /> | <references /> | ||