NTT DOCOMO and Nokia’s SMO Interop: A Blueprint for Autonomous Multi-Vendor RAN

On August 22, 2026, Nokia Bell Labs announced a collaboration between NTT DOCOMO and Nokia to integrate their respective Service Management and Orchestration (SMO) platforms—OREX and Nokia’s SMO framework—both compliant with Open RAN standards. The partnership aims to leverage AI and automation to manage and optimize RAN across multiple radio technology generations and multi-vendor environments. This is not just another vendor partnership; it’s a concrete step toward the autonomous RAN that the industry has been promising for years. For engineers and architects, this announcement provides a rare glimpse into how two major players plan to operationalize AI-driven RAN management in a multi-vendor world.

The SMO: The Brain of Open RAN

To appreciate the significance of this collaboration, we must revisit the role of the SMO in an Open RAN architecture. The O-RAN Alliance defines the SMO as the entity responsible for the management and orchestration of RAN elements, encompassing network functions, resources, and services. It provides the framework for fault, configuration, accounting, performance, and security (FCAPS) management, as well as service lifecycle management. Crucially, the SMO hosts the Non-Real-Time RAN Intelligent Controller (Non-RT RIC), which enables AI-driven policies and optimization applications (rApps) to run on top of the network.

In a multi-vendor Open RAN deployment, the SMO becomes the linchpin that ties together components from different suppliers. It must abstract the underlying hardware and software, expose standardized interfaces, and ensure that optimization decisions are made based on a holistic view of the network. The challenge is that each vendor’s SMO has historically been proprietary, leading to silos and limiting the true multi-vendor interoperability that Open RAN promises. The NTT DOCOMO/Nokia collaboration directly addresses this by integrating two major SMO platforms.

OREX: NTT DOCOMO’s Open RAN Experience

NTT DOCOMO has been a pioneer in Open RAN, launching its OREX (Open RAN Experience) platform in 2021. OREX is designed to accelerate the adoption of Open RAN by providing a set of tools, blueprints, and a partner ecosystem. It includes an SMO that is aligned with O-RAN specifications, enabling operators to manage multi-vendor RAN components. OREX has been instrumental in NTT DOCOMO’s own 5G Open RAN deployment, which uses equipment from multiple vendors, including Fujitsu, NEC, and Nokia.

The OREX SMO is built on cloud-native principles, with microservices and containerized components. It provides a unified management plane that can handle 4G, 5G, and future 6G radio technologies. The platform supports the O-RAN standard interfaces, such as the A1 interface for policy-based guidance from the Non-RT RIC to the Near-RT RIC, and the O1 interface for FCAPS management. By making OREX available to other operators, NTT DOCOMO aims to democratize Open RAN management, offering a reference implementation that others can adopt.

Nokia’s SMO: A Multi-Generation Management Platform

Nokia’s SMO framework is part of its broader Network Operations and Management portfolio. It is designed to manage not only Open RAN but also traditional RAN, providing a smooth migration path. Nokia’s SMO is built on its CloudBand platform, which provides the underlying NFV infrastructure and orchestration. It supports the O-RAN interfaces and integrates with Nokia’s RAN Intelligent Controller (RIC) products, including both Non-RT RIC and Near-RT RIC.

Nokia has been a vocal proponent of AI-driven network management, and its SMO incorporates machine learning for predictive maintenance, energy optimization, and traffic steering. The SMO also supports closed-loop automation, where insights from analytics trigger policy changes without human intervention. Nokia’s SMO is deployed in numerous networks worldwide, and its integration with OREX could set a precedent for how operators and vendors collaborate on multi-vendor management.

The Integration: What Does It Mean?

The announcement states that the two SMO platforms will “work together,” leveraging AI and automation to manage and optimize the RAN across multiple radio technology generations and multi-vendor environments. While the specifics of the integration are not detailed, we can infer several technical aspects:

1. Interoperability via Standard Interfaces: The integration likely leverages O-RAN standard interfaces, such as O1 and A1, to enable the two SMOs to exchange information and coordinate actions. For example, OREX might handle the management of certain RAN elements while Nokia’s SMO manages others, with a shared view of network state.

2. Unified Data Lake: For AI to be effective, it requires access to vast amounts of data from across the network. The integration may involve a common data lake or data sharing mechanism that allows both SMOs to access the same telemetry, configuration, and performance data. This would enable AI models trained on one platform to be deployed on the other, or for joint optimization of network resources.

3. Cross-SMO rApp Deployment: The Non-RT RIC in each SMO can host rApps that provide optimization services. The integration could allow rApps to be deployed across both SMOs, enabling a wider range of optimization scenarios. For instance, an energy-saving rApp from Nokia could run on OREX and control radios from other vendors, as long as the interfaces are standardized.

4. Hierarchical Management: In some deployments, it may be beneficial to have a hierarchical SMO structure, where one SMO acts as a master and the other as a slave. This could be useful in scenarios where an operator uses OREX for one region and Nokia’s SMO for another, but wants central oversight.

The collaboration is not just about technology; it’s also a strategic move. NTT DOCOMO and Nokia are both members of the O-RAN Alliance and have been involved in various Open RAN trials. By partnering, they can accelerate the maturity of their respective SMO platforms and demonstrate to the market that multi-vendor management is not just a theory but a practical reality.

The Road to Autonomous RAN

The ultimate goal of this collaboration is to achieve autonomous RAN—a network that can self-configure, self-optimize, and self-heal with minimal human intervention. The integration of SMO platforms is a critical milestone on this path because it enables the orchestration of AI-driven automation across a multi-vendor environment.

In an autonomous RAN, the SMO continuously collects data from the network, analyzes it using AI algorithms, and takes actions to improve performance, efficiency, and reliability. For example, the SMO could detect an anomaly in a cell’s performance and automatically adjust parameters to mitigate the issue. Or it could predict a traffic surge in a particular area and proactively allocate resources.

NTT DOCOMO and Nokia have both been working on autonomous network initiatives. NTT DOCOMO has its “Autonomous Network” vision, which aims to achieve Level 4 autonomy (out of 5) by 2030. Nokia has its “Autonomous Networks” portfolio, which includes AI-powered solutions for network management. This collaboration brings these efforts together, creating a unified approach to autonomy.

Challenges and Considerations

While the integration of SMO platforms is promising, it is not without challenges. Here are some issues that engineers and architects should consider:

1. Data Governance: When two SMOs share data, questions arise about data ownership, privacy, and security. Operators will need to define clear data governance policies to ensure compliance with regulations and protect sensitive information.

2. Latency: The Non-RT RIC operates on timescales of seconds or more, but some optimization actions require near-real-time responses. The integration must ensure that the communication between SMOs does not introduce unacceptable latency.

3. Conflict Resolution: If both SMOs are making decisions about the same network resources, there is a risk of conflicting actions. The integration must include mechanisms for conflict resolution, perhaps through a priority scheme or a common policy framework.

4. Vendor Lock-in: While the goal is multi-vendor interoperability, there is a risk that the integration becomes so tight that it creates a new form of lock-in. Operators must ensure that the integrated SMO can still work with other vendors’ components.

5. Complexity: Managing a multi-vendor SMO integration adds complexity to network operations. Operators will need skilled personnel who understand both platforms and the interfaces between them.

The Bigger Picture: SMO as a Differentiator

The SMO is becoming a key differentiator for operators and vendors alike. As networks become more complex and AI-driven, the SMO is the platform that enables intelligent automation. The NTT DOCOMO/Nokia collaboration signals that SMO interoperability is a competitive advantage, not just a nice-to-have.

For Open RAN operators, this news reinforces the importance of choosing SMO platforms that are truly open and interoperable. It also highlights the need for industry-wide standards and testing to ensure that different SMOs can work together seamlessly.

The collaboration may also pave the way for other vendors to follow suit. If NTT DOCOMO and Nokia can demonstrate a successful integration, other SMO providers may be encouraged to open up their platforms to enable similar partnerships. This would be a significant step toward the ultimate goal of a fully open, multi-vendor RAN ecosystem.

Technical Deep Dive: How the Integration Could Work

Let’s hypothesize on the technical implementation of the integration. Both OREX and Nokia’s SMO are built on cloud-native architectures, so the integration likely involves RESTful APIs and event-driven messaging. The O-RAN Alliance has defined the O2 interface for communication between the SMO and the cloud infrastructure, but for SMO-to-SMO communication, there is no standardized interface yet. This integration might set a precedent for such an interface.

One possible architecture is to have a central SMO that aggregates data from multiple sub-SMOs. For example, NTT DOCOMO could deploy OREX as the top-level SMO for its network, with Nokia’s SMO as a sub-SMO for specific domains (e.g., a region or a set of cells). The top-level SMO would handle end-to-end optimization, while the sub-SMO handles local optimization.

Alternatively, the integration could be peer-to-peer, with each SMO responsible for its own domain but sharing data and policies through a common bus. This would be more distributed and resilient, but requires robust synchronization mechanisms.

Another aspect is the use of the O-RAN A1 interface. The A1 interface is used between the Non-RT RIC (inside the SMO) and the Near-RT RIC. In a multi-SMO scenario, a policy defined in one SMO might need to be enforced in the other SMO’s domain. This could be achieved by having the Non-RT RIC in one SMO send A1 policies to the Near-RT RIC in the other SMO’s domain, assuming the Near-RT RIC is accessible.

What This Means for Engineers

For engineers working on Open RAN deployments, this collaboration offers several takeaways:

• Expect more SMO integration efforts: As the industry moves toward autonomous networks, SMO interoperability will become a common requirement. Engineers should design their networks with this in mind, using standardized interfaces and open APIs.
• AI models need to be portable: For AI to work across different SMOs, models should be portable and not tied to a specific vendor’s platform. This may involve using common ML frameworks and ensuring that data formats are compatible.
• Testing is crucial: Before deploying integrated SMOs, operators should conduct rigorous testing to ensure that the integration works as expected. This includes testing for performance, security, and resilience.
• Skills development: Managing a multi-vendor SMO environment requires a diverse skill set. Engineers should invest in learning about different SMO platforms and the O-RAN standards.

Conclusion

The NTT DOCOMO and Nokia SMO integration is a significant milestone in the evolution of Open RAN. It demonstrates that the industry is moving from siloed management to a more collaborative, AI-driven approach. For Open RAN operators, this is a signal that the future of RAN management is multi-vendor and autonomous. While challenges remain, the potential benefits—reduced operational costs, improved performance, and faster innovation—are too significant to ignore.

As we look ahead, we can expect to see more partnerships like this, as operators and vendors realize that no single company can deliver the full promise of Open RAN alone. The SMO is the battleground where these partnerships will be forged, and the winners will be those who can offer the most open, intelligent, and interoperable solutions.

Sources

• Nokia Bell Labs Facebook Post
• Nokia’s Blog: Building autonomous RAN together: NTT DOCOMO and Nokia’s SMO journey