SMO
Service Management and Orchestration: O-RAN management framework hosting the non-RT RIC and managing O-RAN nodes via O1 and O2 interfaces.
The SMO is the management umbrella over an O-RAN deployment — the layer that operates, configures, and orchestrates everything else. It hosts the non-RT RIC (and its rApps), and it reaches the rest of the network through a couple of distinct interfaces: O1 for FCAPS-style management of the RAN nodes (fault, configuration, performance, the day-to-day operational data), and O2 toward the underlying cloud platform (the O-Cloud) that the RAN functions actually run on.
Drawing that line between O1 and O2 is worth getting straight. O1 manages the network functions — the O-CU, O-DU, near-RT RIC themselves. O2 manages the infrastructure they're deployed on — provisioning compute, lifecycle of the virtualised resources. The SMO ties both together so an operator can, in principle, run a multi-vendor RAN from one management plane. In practice the SMO often overlaps with or sits beside an operator's existing OSS and orchestration stack, which is part of why its exact boundaries vary between deployments. Where the SMO sits against the RIC and the models that make one worth running is covered in O-RAN RIC and xApps.
Related terms
Want to truly understand SMO? Learn it in context.
SMO is taught inside our O-RAN & Open Networks course with diagrams and worked examples. The first module is free with an account; labs, TelcoMentor and the rest of the curriculum are on Pro.
- Free to join
- First module of every course
- No card needed
- TELCOMA since 2009
Get one 5G/LTE engineering deep-dive a fortnight
One thing explained properly every other Tuesday — a real failure, and the lab or trace where you work it yourself. No spam, no marketing, just engineering. Unsubscribe in one click.