The use of this site and the content contained therein is governed by the Terms of Use. When you use this site you acknowledge that you have read the Terms of Use and that you accept and will be bound by the terms hereof and such terms as may be modified from time to time.
All text, graphics, audio, design and other works on the site are the copyrighted works of nasscom unless otherwise indicated. All rights reserved.
Content on the site is for personal use only and may be downloaded provided the material is kept intact and there is no violation of the copyrights, trademarks, and other proprietary rights. Any alteration of the material or use of the material contained in the site for any other purpose is a violation of the copyright of nasscom and / or its affiliates or associates or of its third-party information providers. This material cannot be copied, reproduced, republished, uploaded, posted, transmitted or distributed in any way for non-personal use without obtaining the prior permission from nasscom.
The nasscom Members login is for the reference of only registered nasscom Member Companies.
nasscom reserves the right to modify the terms of use of any service without any liability. nasscom reserves the right to take all measures necessary to prevent access to any service or termination of service if the terms of use are not complied with or are contravened or there is any violation of copyright, trademark or other proprietary right.
From time to time nasscom may supplement these terms of use with additional terms pertaining to specific content (additional terms). Such additional terms are hereby incorporated by reference into these Terms of Use.
Disclaimer
The Company information provided on the nasscom web site is as per data collected by companies. nasscom is not liable on the authenticity of such data.
nasscom has exercised due diligence in checking the correctness and authenticity of the information contained in the site, but nasscom or any of its affiliates or associates or employees shall not be in any way responsible for any loss or damage that may arise to any person from any inadvertent error in the information contained in this site. The information from or through this site is provided "as is" and all warranties express or implied of any kind, regarding any matter pertaining to any service or channel, including without limitation the implied warranties of merchantability, fitness for a particular purpose, and non-infringement are disclaimed. nasscom and its affiliates and associates shall not be liable, at any time, for any failure of performance, error, omission, interruption, deletion, defect, delay in operation or transmission, computer virus, communications line failure, theft or destruction or unauthorised access to, alteration of, or use of information contained on the site. No representations, warranties or guarantees whatsoever are made as to the accuracy, adequacy, reliability, completeness, suitability or applicability of the information to a particular situation.
nasscom or its affiliates or associates or its employees do not provide any judgments or warranty in respect of the authenticity or correctness of the content of other services or sites to which links are provided. A link to another service or site is not an endorsement of any products or services on such site or the site.
The content provided is for information purposes alone and does not substitute for specific advice whether investment, legal, taxation or otherwise. nasscom disclaims all liability for damages caused by use of content on the site.
All responsibility and liability for any damages caused by downloading of any data is disclaimed.
nasscom reserves the right to modify, suspend / cancel, or discontinue any or all sections, or service at any time without notice.
For any grievances under the Information Technology Act 2000, please get in touch with Grievance Officer, Mr. Anirban Mandal at data-query@nasscom.in.
A radio access network (RAN) consists of radio base stations with large antennas. It provides the critical technology to securely connect users, mobile phones or enterprises, to the mobile network over radio waves. It also acts as a bridge to access all the critical applications on the web.
The Conventional RAN Technology:
Traditional D-RAN Architecture
The traditional RAN infrastructure involves a Radio Unit (RU) and a Baseband Unit (BBU) along with the mobile devices/user equipment (UE). The RU transmits, receives, and converts the signals for the RAN base station. The RU communicates with the Baseband Unit (BBU) after receiving signal information from the antennas using the Common Public Radio Interface (CPRI). The BBU takes this signal information and processes to forward it to the core network. Finally, data returns to the user via the reverse process.
Thus, operators need to densify the network by adding more infrastructure to improve a cell's operational capacity within conventional D-RAN architectures. However, this results in increased CAPEX as additional Base Stations need to be deployed, and each BS has an associated Radio Resource Unit (RRH) and Baseband Unit (BBU). Furthermore, the processing resources of a BBU cannot be shared among other RRHs.
Open RAN:
The current RAN technology is provided as a hardware and software integrated platform. Open RAN standards enable creating a multi-vendor RAN solution that utilizes open interfaces between hardware and software & hosting software that controls and updates networks in the cloud. The architecture promises a host of benefits for network operators and infrastructure providers, including supply chain diversity, solution elasticity, new capabilities leading to increased competition within the market, and facilitation of innovative use cases.
Open RAN Architecture Components:
Open RAN looks to enable operators to mix and match components within the RAN and facilitate interoperability between RAN equipment from different vendors. In an Open RAN environment, the RAN is separated into three main building blocks:
The Radio Unit (RU): Component through which radio frequency signals are transmitted, received, amplified, and digitized. It is located/integrated into the antenna
The Distributed Unit (DU): Sits close to the RU and runs the RAN Intelligent Controller (RIC), MAC, and parts of the PHY layer. This logical node includes a subset of the eNB/gNB functions, depending on the functional split option, and the CU controls its operation.
The Centralised Unit (CU): It is a logical node that includes the gNB functions like transfer of user data, mobility control, RAN sharing (MORAN), positioning, session management, etc. The CU controls the operation of several DUs over the mid-haul interface.
The fundamental tenet of Open RAN is enabling operators to be able to cherry-pick best-of-breed vendors for different components like the radio, centralized unit (CU), distributed unit (DU), etc.
Open RAN Adoption:
A multitude of converging factors are encouraging Open RAN adoption:
Reduction in upfront capital deployment costs
Lower OPEX through automation
Greater innovation
Increased vendor diversity
Pioneered by the likes of Rakuten & Dish, who are showcasing greenfield deployments in Open RAN, incumbent vendors are also looking to embrace Open RAN for their networks in 2021-22. This list includes but is not limited to companies such as AT&T, Verizon, BT, Orange, Reliance Jio, MTN, NTT DoCoMo, and others.
Open RAN Standards:
The two most pertinent organizations working on Open RAN standards are the O-RAN Alliance & the TIP (Telecom Infra Project). The O-RAN Alliance has the mandate to define specifications to make different blocks within the architecture work seamlessly. TIP is more deployment & execution-oriented. These organizations are also continually sponsoring plugfests to support verification, testing, and integration of disaggregated RAN components. Innovation-driven by AI & ML is expected to help operators with bandwidth-heavy applications, and the RAN intelligent controllers (RICs) will play a focal role in this. Solutions like Radio Resource Management (RRM) & Self Organizing Networks (SON) can be implemented using AI/ML technologies.
Needless to say, to realize the promise of Open RAN, operators will have to count on system integrators to make disparate components come together cohesively and to address interoperability.
With cloudification & automation driving innovation in Open RAN, operators would need to diversify in-house talent and become more adept in software engineering, cloud-native architectures, and not just systems engineering.
O-RAN Challenges
Some of the key challenges which need to be addressed while considering O-RAN are interoperability, ownership, accountability.
With Open RANs, operators and integrators need to initially confirm that the technology works together before it goes into a live network.
One of the other challenges post-deployment is the ownership of an issue when it occurs and who solves it. In a traditional single-vendor network, when problems arise, operators can work with the single concerned vendor to resolve them. But with an Open RAN network, they would have to work alongside multiple vendors when a problem arises.
Also, ensuring interoperability, testing, and integration for the whole O-RAN ecosystem can be an arduous task.
From the security perspective, ORAN can potentially face similar security-related issues as most other virtual architectures. The disaggregation of various functions could increase the RAN threat surface. Additionally, the increase in IoT devices also increases the probability of potential attacks due to compromised devices.
Commercial O-RAN Solutions:
O-RAN ALLIANCE has specified a Minimum Viable Plan (MVP) Towards Commercial O-RAN Solutions. It will help O-RAN ecosystem players prioritize delivering a minimum viable set of end-to-end O-RAN solutions applicable in any commercial network.
The first release of the MVP includes already published specifications and additional work items for:
Open fronthaul between O-RU and O-DU, enabling multi-vendor interoperability.
Open transport will help define xhaul transport and proposes the best practices of deploying WDM and IP technologies in xhaul.
Open stack provides a software reference design for O-CU/O-DU architecture
Open cloud presents an O-Cloud reference design for real-life deployment recommendations.
Open hardware offers hardware reference designs for different cell configurations and open fronthaul gateway to accelerate the use of white-box
Open Testing and Integration Centers (OTICs) brings and sets testing and integration criteria to ensure consistency across O-RAN products and solutions.
Support for O-RAN by System-on-Chip (SoC) Vendors
O-RAN, SOC providers, Operators, OEMs, and solution providers are all essential partners in creating the Open Wireless Network as a Platform. The open and flexible 5G standards are driving the new development of highly customized hardware.
Mavenir and Xilinx announced their partnership to bring 4G/5G O-RAN massive MIMO (mMIMO) solutions to speed up Open RAN deployments. Xilinx is a member of the O-RAN Alliance and is a contributor to the 3GPP specifications for 5G mobile networks, and offers silicon that supports multiple standards, bands, carriers, and sub-networks for Open RAN
ArrayComm, a provider of a physical layer (PHY) software and hardware components for LTE and 5G base stations, selected Keysight's integrated test portfolio to validate O-RAN radio and distributed units
Airtel announced that they would utilize the Qualcomm 5G RAN platforms to roll out virtualized and Open RAN-based 5G networks.
Conclusion:
The market-based competition will ensure the merits of technical performance and competitiveness of solutions from different vendors in the Open RAN market. The freedom of the market would prevail, and 3GPP and O-RAN will co-exist and share several vital technological features – whether complement and competing with each other. The operators will have the freedom to choose from either technology.
That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.
When we talk about ‘ impact’, its elusive nature invites us to explore its many facets in our professional and personal lives. Whether it's a transformative moment at work, a personal milestone, or a broader societal shift, impact leaves a lasting…
In today's volatile business landscape, the ability to recover from unforeseen events—such as a ransomware attack, natural disaster, or database corruption—can determine the survival of a company. Ensuring your IT systems are resilient and can…
Legacy systems often hinder organizations embarking on their digital transformation journey. These outdated yet essential pieces of hardware and software keep operations running but struggle to integrate with newer technologies. For companies…
The evolving landscape of managed IT services is shaped by emerging technologies and trends that are redefining how businesses manage and optimize their IT operations. This blog explores the key trends in managed IT services and the strategic…
“Everything old is new again” may be relevant when it comes to some trends, but it’s definitely not the case with technology—and no one feels that pain more than companies running legacy systems that were state-of-the-art 10 years ago. Lotus Notes…
All low-code platforms allow users to build software applications without writing tens of thousands lines of code—but not all low-code platforms are created equal, and that’s one of the reasons low-code is frequently misunderstood. Because low-code…
