Featured Story
Intel and telcos left in virtual RAN limbo by rise of AI RAN
A multitude of general-purpose and specialist silicon options now confronts the world's 5G community, while Intel's future in telecom remains uncertain.
To prosper, O-RAN automation software developers need clear routes to market and standardized development environments.
The RAN environment constantly evolves, with ever changing capacity and performance demands, interference issues and fluctuating coverage. To manage this complexity and scale, operators need AI-powered RAN automation and tooling that enable self-healing, self-configuration and self-optimization.
The O-RAN Alliance RAN Intelligent Controller (RIC), part of the service management and orchestration (SMO) framework, offers operators the potential for cohesive multi-vendor capabilities. To date, live deployments are limited, though RAN automation platform and app development are progressing. rApps is advancing faster than xApps with support from larger vendors such as Ericsson and Samsung. Other companies like Fujitsu, Nokia and Qualcomm (Cellwize) are now deeply engaged in developing RAN automation software and platforms.
A healthy RAN developer ecosystem is advantageous for innovation, providing optionality and exploiting specialist expertise that larger vendors lack. But, technical and commercial challenges remain. In December 2024, the National Telecommunications and Information Administration (NTIA) announced $450m in funding in its third notice of funding opportunity (NOFO 3) to accelerate this sector, targeting software innovation (especially the RIC) and integration automation to reduce multi-vendor integration costs.
In this blog, I consider how to streamline and nurture the development of RAN automation apps such as rApps, centralized self-organizing networks (C-SON) and software tooling, including digital twin technology. I also discuss RAN automation software routes to market and the potential for marketplaces. These will be critical for active developer ecosystems.
RAN automation software marketplaces
Operators traditionally drive the engagement and procurement of software and tools, establishing 1:1 relationships between themselves and automation technology providers like C-SON app and tool vendors. Recently developed software automation solutions, such as RIC r/xApps, represent a significant technology shift and sizable opportunity that requires a new commercial model.
RAN app marketplaces and directories look to centralize a wide variety of apps from multiple vendors in standardized, reliable packages with a secure experience. Establishing new relationship models between the platform/marketplace, vendors and operators takes time. Until RAN automation stacks evolve, operators will continue to lead engagement and unify vendor partnerships.
In October 2024, Ericsson launched its first rApp directory containing network evolution, deployment, optimization, healing and automation, and AI foundation software of its own and from third parties (AirHop, Aira Technologies, Infovista, TECTWIN, VIAVI, Zinkworks, etc.). The directory provides information about commercially available apps. It also signals the beginning of more focused marketplaces driven by the SMO and RIC vendors, as well as an evolution from early developer portals.
Operators and developers must watch out for platform lock-in. Directories and marketplaces are potentially powerful. However, operators should retain control to avoid large vendors becoming gatekeepers, an important step to support developer/operator relationships and build app diversity. Open automation project communities, such as the O-RAN Software Community and Telecom Infra Project, can support this but tend to be technically focused, not commercial.
The RAN software developer community
C-SON introduced automated performance and QoS and RAN capacity improvements. But, due to its proprietary nature (RAN vendor app dependency) and slower automation intervals (around 15 minutes), it has limitations when faced with today's demanding RAN requirements.
A healthy developer ecosystem is vital to supporting mature O-RAN technology. Several large operators, including AT&T, TELUS and Vodafone, have already started to deploy the technology. Early O-RAN developer portals have kick-started software development and communities.
The developer ecosystem consists of SMO and RIC vendors, operators and third parties (traditional C-SON developers, test vendors, IT consulting companies porting existing tools, startups, universities, new AI entrants, etc.). Community creation relies on vendor outreach, operator-led engagements and technology scouting. And overcoming challenges, such as O-RAN standards immaturity, multi-vendor interoperability, streamlining development, testing and onboarding, is critical to minimizing barriers and maintaining a thriving ecosystem.
Some of the key enablers for the RAN automation software developer ecosystem include the following:
Specification maturity: O-RAN Alliance SMO and RIC standards development is a work in progress. Currently, vendor-specific workarounds are still required for some undefined interface services and API specifications (e.g., within O1, O2 and R1, legacy adapters support, etc.). Supporting O-RAN working groups to define priority interface capabilities marked "for further study" should be a top priority for operators and vendors. In the meantime, workarounds are a necessary evil.
Open source code and tooling: Software development, code storage, tooling and developer integration testing should align with the latest architectures specified by the O-RAN Alliance. The developer ecosystem (operators, vendors, and third-party developers) should use open source to avoid the complexity of software integration, which adds cost. Sharing seed code and knowledge can also align and fast-track app development and the ecosystem.
Developer portals: SMO and RIC vendors, such as Nokia, Fujitsu, Juniper Networks, Ericsson and Samsung, provide spaces for creation, reference datasets and code snippets, training, etc. Developing a single r/xApps version to run on multiple vendor platforms and differing operator environments is not trivial. Still, removing the burden of writing and maintaining multiple versions is crucial. Vendor platforms must implement standardized O-RAN Alliance-compliant SDKs and common APIs.
RAN data: Access to suitable RAN network data is complex, variable between networks and often not widely shared by operators. Data composition is also changeable and may be encoded differently. Synthetic or simulated data may provide an alternative, but not the level of accuracy or variation of differing operator network environments and conditions. Developers need relationships with operators and access to shared real datasets to increase development accuracy. The industry must accelerate the definition of standardized data model formats.
To prosper, O-RAN automation software developers need clear routes to market and standardized development environments. SMO and RIC vendors must work with operators to encourage and nurture third-party developers, standardize developer environments, remove barriers and unify engagement so members can showcase and monetize their innovations.
Live O-RAN technology deployments and government-led acceleration funding like NOFO 3 are catalysts for deeper innovation and commercial deployment. Successful vendor-led directories will include strong operator partnerships and open communication channels to innovate, solve problems and replicate real RAN environments. These trends mark a significant shift from initial O-RAN developer portals assisting with proof-of-concept, technology evaluation, and plugfest activities. Thus, app and tool developers must not overlook the importance of forming strong relationships with operators to develop and build the apps they will ultimately use.
Read more about:
Heavy Reading ResearchYou May Also Like