O-RAN SMO (Service Management and Orchestration) is the management and orchestration layer for Open RAN.
It coordinates the lifecycle, configuration, assurance, and optimization of O-RAN network functions and the cloud infrastructure they run on.
Responsibilities
- Orchestrate O-RAN network functions across the O-RAN O2 Interface.
- Manage O-RAN functions across the O-RAN O1 Interface.
- Host or integrate the Non-RT RIC for non-real-time optimization.
- Support rApps through the O-RAN R1 Interface.
- Provide policy, enrichment information, and ML model support toward the Near-RT RIC through the O-RAN A1 Interface.
- Collect telemetry and fault/performance data for closed-loop automation.
Timing
The SMO is not in the radio user-plane path. It operates on management and orchestration timescales, from seconds to minutes or longer.
Near-real-time control belongs to the Near-RT RIC over the O-RAN E2 Interface, while real-time radio processing remains in the O-DU and O-RU.
Related Interfaces
- O-RAN O1 Interface for FCAPS-style management of O-RAN functions.
- O-RAN O2 Interface for managing O-Cloud infrastructure and deployments.
- O-RAN A1 Interface for Non-RT RIC influence over the Near-RT RIC.
- O-RAN R1 Interface for rApps.
Anki
id: oran-smo-definition deck: Computer Science::Infrastructure::Telco tags: telco oran smo
Q: What is the O-RAN SMO? A: The O-RAN SMO is the service management and orchestration layer that manages O-RAN functions, orchestrates cloud resources, and supports non-real-time RAN optimization.