Nokia and Ericsson Bet on Interoperability: The Real Product Is the Automation Layer
On March 1, 2026, Nokia and Ericsson announced a collaboration that, at a glance, appears to be just another technical agreement: both will integrate into each other's automation application markets to accelerate the transition toward autonomous networks. Ericsson is entering Nokia’s SMO Marketplace, while Nokia joins Ericsson’s rApp Ecosystem, centered around its Intelligent Automation Platform. The explicit aim is to enable rApps (automation applications that interact via the R1 interface) to be distributed and executed in multi-vendor environments with less friction. No financial figures or quantified revenue goals were shared. The strategic signal lies elsewhere.
When two historic rivals decide to mutually "sell software," they are not celebrating industrial harmony; they are acknowledging a shift in the unit of value. In the transition from 5G to 6G, the bottleneck is no longer just coverage or radio capacity. It’s operation, meaning: how a network is deployed, optimized, and repaired in the face of growing complexity, multiple providers, and constant pressure to reduce operational costs.
The most significant phrase in the announcement is not "cooperation"; it is interoperability. The most relevant asset is not today’s catalog of rApps, but the right to define the landscape where they become "installable" tomorrow.
The Cold Agreement: Two Marketplaces, One Interface, the Same Goal
The facts, without any mythology. Nokia and Ericsson communicated a collaboration to advance intelligent automation in purpose-built networks, cloud RAN, and Open RAN. The mechanism is platform-based: Ericsson joins Nokia’s SMO Marketplace, and Nokia becomes a member of Ericsson’s rApp Ecosystem. Both commit to ensuring that rApps are available on each other's platforms, supporting compatibility through the R1 interface.
From Ericsson, Anders Vestergren, Head of Solution Area Network Management, framed the agreement as an enabler of "greater choice and flexibility" for communication service providers (CSPs) as they transition to autonomous networks, and as progress toward “fostering innovation using the R1 interface” and nurturing rApp ecosystems that work together. From Nokia, its CTO Ari Kynaslahti described it as progress towards delivering “the next generation of autonomous networks” by aligning open frameworks and intelligent operating models, accelerating the evolution of rApp environments to introduce capabilities more quickly, optimize with precision, and scale innovation across different scenarios. ABI Research, through Dimitris Mavrakis, provided an industry reading: convergence toward SMO as the automation architecture and expanded access and interoperability of rApps through R1-based standards.
There are no numbers. This limits direct financial inferences but does not hinder evaluating the economic logic behind the move. When an industry does not announce prices or volumes, it is usually negotiating something else: the control of the integration layer, the operational "operating system" that determines what gets installed, how it is monitored, and what data becomes essential.
In autonomous networks, the explicit promise is to advance toward Level 4 autonomy and beyond, where the network self-optimizes with minimal human intervention. That promise only materializes if the automation is portable across vendors and technologies. Therefore, the agreement is not just a technical detail; it is a bet on reducing the cost of coordination in a multi-vendor environment.
The Real Struggle: Less Vendor Dependence, More Standard Dependence
This type of collaboration addresses a problem that operators experience daily: automation often breaks down at the boundary between providers. Each manufacturer optimizes its own domain and stack, turning operation into an expensive puzzle. The narrative of “autonomous network” becomes smoke if each rApp only functions well in the walled garden of its creator.
By enabling rApps in both environments, Nokia and Ericsson are pushing a simple idea: automation should behave like distributable software, not like continual consultancy. In terms of market power, this shifts the center of gravity from equipment (radio and core as exclusive differentiation) to the orchestration and management layer where the decisions about what to automate and with what logic are made.
The strategic consequence for CSPs is clear: less vendor lock-in in the automation layer, at least in the direction suggested by the announcement. And for Nokia and Ericsson, the outcome is not altruistic: if the R1 standard and SMO architecture gain ground, the competitive game shifts to who offers better rApps, better operational governance, better automation performance, and better deployment speed.
This shift also redefines the type of defensible revenue. In hardware, value tends to compress due to competition, renewal cycles, and volume purchases. In operational software, value is captured through recurrence, updates, support, certifications, and a “catalog” effect where the new is installed over the existing. Their mutual exposure suggests they prefer a larger, more standardized market to two fiefdoms that hinder adoption due to friction.
This does not eliminate competition; it rationalizes it. Rivalry becomes more measurable: performance of rApps, reliability, operational security, and speed in taking automation from pilot to production.
Portfolio and Organizational Design: Cooperation Without Internal Surgery Doesn’t Scale
From a portfolio perspective, this announcement signals that Nokia and Ericsson are trying to balance two simultaneous tensions.
First, protect the current revenue engine. RAN remains core business, and the market does not forgive distractions. The collaboration does not renounce competition in radio; rather, it aims to ensure that multi-vendor operation does not stall projects, and that automation becomes a cross-selling argument.
Second, accelerate exploration without breaking exploitation. The rApps and SMO architecture exist in a zone where initial ROI is often ambiguous: distributed benefits, dependent on the customer environment, and long learning curves. This is where many corporations fail due to bureaucracy: they demand that an early initiative meets the same indicators as a mature product and kill it before it finds its repeatability.
The organizational risk does not lie in the announced technology, but in how it is governed. For the exchange of rApps to gain real traction, both companies must operate with a logic more akin to “platform product” than “integration project.” This requires concrete internal rules:
- Autonomy of the platform team to define roadmaps, compatibility, and certifications without becoming hostage to hardware priorities.
- Adoption and learning metrics (installations, stability, deployment times, incident reduction) over immediate margin metrics.
- Interface discipline: if R1 is the bridge, the natural temptation is to extend or interpret it in favor of one’s own interests. Interoperability is earned through restriction, not creativity.
There’s an additional nuance. When two giants enable interoperability, they also lower barriers for third parties. ABI Research mentions that this expands access and availability of rApps. In practice, that “third party” could be a partner… or a software competitor that captures value above manufacturers. If the standard thrives, manufacturers face an uncomfortable truth: their differentiation cannot merely be “being there”; it must be “being better” in a layer where the customer can compare and switch with less pain.
Bureaucracy has a high price. If Nokia and Ericsson turn the exchange of rApps into a cumbersome process of approvals, endless homologation, and crossover policies, the market will find shortcuts: integrators, parallel proprietary solutions, or closed automation by domain. For the agreement to be useful, it must translate into real-time operational time savings.
The 2026 Game Board: SMO as Architecture and the Pressure of AI-Driven Automation
The announcement aligns with a context that was already maturing: the industry is converging toward SMO as the long-term architecture for automation, while network operations become the major battlefield as the demand for AI workloads and more heterogeneous networks grows.
During the same MWC 2026 period, parallel signals of acceleration in automation and AI-RAN were noted. The briefing mentions Nokia's advancements with NVIDIA and deployments with various operators, as well as technology partner expansions to commercialize AI-RAN. It also mentioned that Ericsson highlighted its leadership in RAN automation at the event. Although these pieces are not part of the Nokia-Ericsson agreement, they do describe the climate: value is shifting towards operating networks as software systems, with more automation, more observability, and more continuous optimization capabilities.
In this climate, the collaboration has a practical reading: Nokia and Ericsson are buying an option so that if SMO and R1 consolidate, they do not get trapped in incompatible platforms. The cost of not doing so would be high: each multi-vendor pilot would become custom integration, eroding margins and lengthening sales cycles.
For CSPs, the incentive is equally concrete: capital expenditure on infrastructure is unjustified if operational expenditure balloons due to complexity. Automation based on rApps promises to tackle precisely that cost line, but only if it is installed and operated without excessive vendor dependence.
The implicit threat is execution. Real multi-vendor means coexisting with exceptions, versions, differing performance, and failures that no one wants to “own.” In autonomous networks, the perceived value isn’t in the demo; it’s in the quiet hours without incidents. That’s why the quality of operational design, support, and governance between companies becomes as relevant as formal compatibility.
The Movement That Matters: Turning Automation Into a Repeatable Product
The Nokia-Ericsson collaboration makes sense because it attempts to standardize where the industry loses money: the multi-vendor operation. Its merit will not be measured by press releases, but by the capacity for rApps to be deployed with minimal friction and consistent results in mixed networks.
From a portfolio standpoint, this seems like a serious attempt to finance exploration (automation and software) without squeezing the core (RAN infrastructure), avoiding letting innovation get trapped in artisanal projects. The feasibility hinges on a less glamorous discipline: interface governance, adoption metrics, and actual autonomy for platform teams to iterate without being subordinated to cycles and policies of the mature business.
