Verizon’s Nationwide EIC Rollout Is the Moment Open RAN Automation Grows Up—and the xApp Dream Takes a Back Seat

On November 3, Verizon and Ericsson confirmed what had been rumored for weeks: the operator will deploy the Ericsson Intelligent Controller (EIC) nationwide across the United States, beginning before the end of 2026. The EIC is the central component of Ericsson’s Intelligent Automation Platform (EIAP), and Verizon plans to use it to run rApps—non-real-time RAN automation applications—including several developed jointly with Ericsson: Cell Anomaly Detector, Root Cause Explainer, and Anomaly General Optimizer. Verizon’s VP of network planning, Matt Butz, framed the move as a step toward Level 4 cognitive automation and, eventually, 6G readiness.

On the surface, this is another vendor-operator press release. But look closer, and you’ll see something more significant: the first large-scale, nationwide commercial deployment of an open, standards-based RAN automation platform by a major US operator. And it’s happening not through the near-real-time RIC and xApps that have dominated Open RAN hype cycles, but through the non-real-time RIC, the SMO, and rApps. That distinction matters enormously for the future of Open RAN.

The rApp Reality Check

For years, the Open RAN narrative has been dominated by the near-real-time RIC and xApps—the applications that sit within the 10-millisecond to 1-second control loop and enable fine-grained, near-real-time optimization. The vision was compelling: a vibrant ecosystem of third-party xApps, each solving a specific RAN problem, all interoperable across vendors. But that vision has largely failed to materialize. As SNS Telecom & IT noted in a recent report, reluctance among distributed unit (DU) and central unit (CU) vendors has held back adoption of xApps and the near-RT RIC. The reasons are both technical and commercial: vendors are protective of their baseband differentiation, and the interfaces needed for true multi-vendor xApp portability remain immature.

Meanwhile, the non-real-time RIC and rApps have quietly gained traction. These applications operate on timescales of seconds to minutes—think policy-based traffic steering, anomaly detection, energy savings, and root-cause analysis. They don’t require the tight latency guarantees of xApps, and they can be deployed on standard cloud infrastructure. More importantly, they can deliver tangible operational benefits without requiring a wholesale replacement of the RAN vendor’s baseband software.

Verizon’s EIC deployment is the clearest validation yet of this shift. The operator isn’t waiting for the xApp ecosystem to mature. It’s going with what works today: rApps on an open platform that supports multi-vendor, multi-technology environments. And it’s not just consuming Ericsson’s rApps—it’s developing its own, a signal that operators want to own the automation layer rather than cede it entirely to vendors.

The Numbers Behind the Shift

SNS Telecom & IT’s market data provides useful context. The firm projects that global spending on SMO, RIC, and d/x/rApps will grow at a CAGR of approximately 40% between 2026 and 2030, reaching more than $660 million in annual investments by the end of the decade. That’s a significant chunk of change, and it’s growing fast. By contrast, the broader RAN automation market—including traditional SON, AI-for-RAN upgrades, and Open RAN automation—is expected to grow at a more modest CAGR of around 9%. The message is clear: the action is in Open RAN automation, and within that, the SMO and non-real-time RIC are leading the charge.

Separately, SNS estimates that AI-enabled RAN automation and optimisation—the AI-for-RAN segment—will reach $1.1 billion by 2030, growing at a 9% CAGR. That’s a healthy market, but it’s smaller than the Open RAN automation segment and growing more slowly. The implication is that the industry’s appetite for AI in the RAN is real, but the biggest near-term opportunity lies in the standards-based automation frameworks that Open RAN has championed—not in proprietary AI add-ons.

Why Verizon’s Move Is a Bellwether

Verizon has long been viewed as a cautious adopter of Open RAN. Unlike some European operators that have made bold commitments to multi-vendor disaggregated RAN, Verizon has taken a more measured approach, prioritizing performance and reliability. Its decision to deploy EIC nationwide is therefore a strong signal that the platform is mature enough for prime time.

But there’s a nuance: EIC is an Ericsson product, and while it supports open interfaces and multi-vendor environments, Verizon’s initial deployment will likely be heavily Ericsson-centric. That’s not a criticism—it’s a pragmatic path. Operators don’t need to rip and replace their entire RAN to benefit from open automation. They can overlay an open automation platform on top of their existing infrastructure, gain operational efficiencies, and gradually introduce multi-vendor elements as the ecosystem matures.

This is exactly the kind of brownfield-first approach that Open RAN advocates have been calling for. The purists may scoff at the lack of full disaggregation, but the pragmatists understand that transformation happens incrementally. Verizon’s EIC rollout is a blueprint for how to introduce Open RAN principles without betting the farm on a greenfield build.

The xApp Dream Deferred

None of this is to say that xApps are dead. The recently proposed E3 interface, which provides a standardized mechanism for dApps to directly interface with Open RAN baseband nodes for closed-loop control beyond the 10-millisecond latency limits of xApps, is generating interest. As SNS notes, E3 could enable lower-layer performance optimization, geolocation, integrated sensing, spectrum sharing, and interference cancellation in 5G and future 6G deployments. That’s a big deal.

But E3 is still in the proposal stage, and commercial deployments are years away. In the meantime, the industry is voting with its feet: rApps and the non-real-time RIC are where the near-term action is. Verizon’s deployment reinforces that reality.

There’s also a competitive dynamic at play. Some vendors are pursuing proprietary AI-enabled, real-time optimization capabilities as software upgrades to existing RAN platforms, sold via subscription licensing. These solutions may not be standards-based, but they can deliver results today. Operators facing pressure to reduce costs and improve efficiency are unlikely to wait for the perfect open solution when a proprietary one is available now. The risk is that the industry fragments into a collection of vendor-specific automation silos, undermining the long-term promise of Open RAN.

That’s why Verizon’s choice of an open platform—even if initially Ericsson-centric—is significant. It keeps the door open for multi-vendor automation in the future. It also puts pressure on other vendors to support open interfaces, lest they be locked out of Verizon’s automation layer.

The Level 4 Autonomy Endgame

Verizon’s stated goal is to reach Level 4 cognitive automation—essentially, networks that can operate autonomously within defined boundaries, with human oversight only for exceptions. That’s an ambitious target, and it won’t be achieved overnight. But the EIC deployment is a foundational step. By centralizing automation in a non-real-time RIC, Verizon can collect data from across its RAN, apply AI/ML models, and orchestrate actions across multiple vendors and technologies. That’s the prerequisite for any serious autonomy strategy.

SNS Telecom & IT notes that many operators aim to achieve L4 autonomy for high-impact scenarios such as energy savings, traffic optimization, fault management, service assurance, and special event management by 2030. Verizon’s timeline appears to be aligned with that industry consensus. The operator hasn’t announced a specific date for L4, but the nationwide EIC rollout beginning in 2026 puts it on a credible path.

The Competitive Landscape

Verizon isn’t alone in pursuing open RAN automation. AT&T has been working with Ericsson and others on similar initiatives, and T-Mobile has its own AI-RAN ambitions. In Europe, Deutsche Telekom, Vodafone, and Orange have all launched Open RAN automation trials. But Verizon’s nationwide commitment is the largest and most concrete deployment to date. It sets a benchmark that other operators will be measured against.

Interestingly, Verizon’s move comes as the broader RAN market is showing signs of stabilization after years of decline. According to recent Dell’Oro data, the RAN market has seen three consecutive quarters of growth, but the real story is that Open RAN’s fate hinges on AI economics. Verizon’s EIC deployment is a bet that AI-driven automation can deliver the operational savings needed to justify further investment in RAN infrastructure. If it succeeds, it could accelerate the adoption of open automation across the industry.

The Skeptical View

Of course, there are reasons to be skeptical. Verizon’s deployment is still Ericsson-heavy, and the rApps it’s deploying—Cell Anomaly Detector, Root Cause Explainer, Anomaly General Optimizer—are relatively basic compared to the vision of a vibrant third-party rApp ecosystem. The operator says it will develop its own rApps, but building a robust internal software development capability is easier said than done. Many operators have tried and failed to become software companies.

There’s also the question of ROI. Verizon hasn’t disclosed the financial terms of the deal or the expected savings. Without hard numbers, it’s difficult to assess whether the EIC deployment will pay for itself. The operator’s stock was down slightly on the day of the announcement, suggesting that investors are taking a wait-and-see approach.

And then there’s the xApp question. By prioritizing rApps, Verizon is effectively conceding that the near-real-time RIC isn’t ready for prime time. That’s a pragmatic choice, but it also means that the most innovative part of the Open RAN vision—the ability to run third-party xApps from a diverse ecosystem—remains unfulfilled. If the industry settles for rApps and proprietary AI upgrades, the Open RAN movement risks becoming just another vendor lock-in story with a standardized veneer.

The Verdict

Verizon’s nationwide EIC rollout is the most significant Open RAN automation deployment of 2026. It validates the non-real-time RIC and rApps as commercially viable, sets a benchmark for other operators, and provides a pragmatic path to Level 4 autonomy. But it also exposes the gap between the Open RAN dream and reality: xApps and the near-RT RIC are still waiting in the wings, and the industry’s embrace of proprietary AI upgrades threatens to fragment the automation layer.

The next 12 to 18 months will be telling. If Verizon can demonstrate tangible operational savings and begin onboarding third-party rApps, it will build momentum for a more open automation ecosystem. If it retreats into an Ericsson-only silo, the promise of Open RAN automation will be diminished. For now, the message is clear: rApps are ready, xApps are not, and the path to autonomous networks runs through the non-real-time RIC. Operators would be wise to take note—and to demand that their vendors support open interfaces every step of the way.

Sources

• Verizon and Ericsson team up to integrate AI into RAN automation | MarketScreener
• Verizon commences roll-out of AI RAN optimisations through Ericsson Intelligent Controller - Telecompaper
• What’s up with… Verizon, Deutsche Telekom, ETSI, The Future of RAN | TelecomTV
• SMO/RIC-based RAN automation gains momentum (Reader Forum)
• AI-enabled RAN automation and optimisation a US$1.1 billion market, says SNS Telecom & IT | IoT Now News & Reports