# <center><i class="fa fa-edit"></i> A5: OSC SMO </center>
###### tags: `Assignment` `Wireless communication`
---
[TOC]
:::info
Study note about O-RAN Software Community Service Management and Orchestration (OSC SMO)

**Resources:**
[Cherry SMO](https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20875862)
[SMO - Service Management and Orchestration](https://wiki.o-ran-sc.org/display/OAM/SMO+-+Service+Management+and+Orchestration)
[O-RAN Architecture Description 3.0 - November 2020](https://www.o-ran.org/specification-access)
[O-RAN Operations and Maintenance Architecture 4.0 - November 2020](https://www.o-ran.org/specification-access)

:::

:::warning
The primary goal of the OSC SMO project:
- **Step 1:** Integrate different software artifacts for existing open-source projects;
- **Step 2:** Based on these resources, create a fully functional open-source Service Management and Orchestration (SMO).
:::

# What is SMO?

SMO stands for Service Management and Orchestration.

## About Open RAN managed functions

O-RAN managed functions include:
- Near-Real Time Radio Intelligent Controller (Near-RT RIC);
- O-RAN Central Unit – Control Plane (O-CU-CP);
- O-RAN Central Unit – User Plane (O-CU-UP);
- O-RAN Distributed Unit (O-DU);
- O-RAN Radio Unit (O-RU).

:::info
Information about each managed functions, please refer [here](https://hackmd.io/ZsLEJV8ITSm48H9scgfb3w)
:::

## Roles of SMO framework
>SMO in O-RAN architecture
:::success
In the O-RAN architecture, SMO framework is responsible for RAN domain management.

It must provide an integration fabric and data services for the O-RAN managed functions (shown above).

All O-RAN managed functions are expected to support the O1 interface when interfacing the SMO framework.
:::

# SMO Interfaces

The diagram below shows key interfaces in O-RAN architecture.


The SMO performs its functions/services through four key interfaces to the O-RAN Elements:

- **A1 Interface** between the Non-RT RIC in the SMO and the Near-RT RIC for RAN Optimization.
- **O1 Interface** between the SMO and the O-RAN Network Functions for FCAPS support.
- In the hybrid model, **Open Fronthaul M-plane interface** between SMO and O-RU for FCAPS support.
- **O2 Interface** between the SMO and the O-Cloud to provide platform resources and workload management.

:::danger
SMO, at this time, does not define any formal interface towards the Non-RT RIC.
:::

# SMO Capabilities

The key capabilities of the SMO that provide RAN support in O-RAN are:

- FCAPS interface to O-RAN managed functions (network functions);
- Non-Real Time RIC for RAN optimization;
- O-Cloud Management, Orchestration and Workflow Management.

## FCAPS to O-RAN Network Functions
FCAPS: Fault, Configuration, Accounting, Performance, Security. They are all the information needed for functions management.

:::success
**Supporting FCAPS for O1 interface:**

• Performance Management (PM)
• Configuration Management (CM)
• Fault Management (FM)
• File Management
• Communications Surveillance (Heartbeat)
• Trace
• Physical Network Function (PNF) Discovery
• PNF Software Management.

**Supporting FCAPS for Open Fronthaul M-Plane interface:**
• “Start-up” installation
• SW management
• Configuration management
• Performance management
• Fault Management
• File Management
:::

## Non-Real Time RIC for RAN optimization

SMO supports Non-RT RIC for RAN optimization.
:::success
The Non-RT RIC is comprised of two sub-functions:

• **Non-RT RIC Framework** – Functionality internal to the SMO Framework that logically terminates the A1 interface and exposes the required services to rApps through its R1 interface.

• **Non-RT RIC Applications (rApps)** – Modular applications that leverage the functionality exposed by the Non-RT RIC Framework to perform RAN optimization and other functions via the A1, O1, O2 and R1 interfaces.
:::

## O-Cloud Management, Orchestration and Workflow Management

The SMO utilizes the O2 interface to the O-Cloud to provide:
- The capability of managing the O-Clouds;
- Support for the orchestration of platform and application elements and workflow management.

:::success
The example functionalities should be supported in SMO:

• Discovery and administration of O-Cloud Resources
• Scale-In, Scale-Out for O-Cloud
• FCAPS (PM, CM, FM, Communication Surveillance) of O-Cloud
• Software Management of Cloud Platform
• Create, Delete Deployments and Associated Allocated O-Cloud Resources
• Scale-In, Scale-Out Deployments and Allocated O-Cloud Resources
• FCAPS (PM, FM) of Deployments and Allocated O-Cloud Resources
• Software Management of Deployments
:::

# SMO Functions

| SMO functions | Descriptions | Example |
| --- | ------------- | ---- |
| Inherent Non-RT RIC Framework Functionality | This functionality is definitively associated with the Non-RT RIC itself | The two interfaces “owned” by the Non-RT RIC: The A1 and R1 interfaces |
| Inherent O-RAN SMO Framework Functionality | This functionality is definitively not associated with the Non-RT RIC | The O1 and O2 interfaces |
| Implementation Variable Functionality | This functionality may or may not be associated with the Non-RT RIC. | An SMO provider is free to include this functionality in or exclude this functionality from a Non-RT RIC implementation |

# OSC SMO Use cases

In Open RAN project, SMO is intergrated in O-RAN Operations and Maintenance Architecture (OAM), which is developed by WG1.

:::info
The O-RAN OAM Architecture identifies management services, managed functions and managed elements supported in O-RAN, including the interworking between service management and orchestration (SMO) and other O-RAN components such as infrastructure management.
:::

End to End OAM Use Cases include:

- O-RAN Service Provisioning
- O-RAN Measurement Data Collection

## O-RAN Service Provisioning

:::warning
This use case focuses on network/element deployment.
:::

## O-RAN Measurement Data Collection

:::warning
This use case focuses on the Non-RT RIC requested measurement data collection and consumption, which are supported by SMO framework.
:::

This includes:
1. Measurement Data Collection Creation:


3. Measurement Data File Consumption:


3. Measurement Streaming Data Consumption: