---
# System prepended metadata

title: M-Plane
tags: [WG4]

---

# M-Plane 
###### tags: `WG4`
[WG4 overview](https://hackmd.io/fsvGLtXiQ0ael62w5LvNBg)
## Top level functional description, terminology, including hybrid,  hierarchical


The Lower-Layer Split M-plane (LLS-M) facilitates the `initialization`, `configuration` and `management` of the O-RU to support the stated functional split.

### The Lower-Layer Split (LLS)



- lls-C/U/S
- lls-M

    The Lower-Layer Split M-plane (LLS-M) facilitates the initialization, configuration and management of the O-RU to support the stated functional split

### [NETCONF](https://hackmd.io/KRliuRioS1yHU2OGDkvVug)

- client: O-DU
- server: O-RU

![](https://i.imgur.com/wb0fD3B.png)

---
### M-Plane architecture model


**Hierarchical model**

the O-RU is managed entirely by **`one or more O-DU(s)`** using  a NETCONF based M-Plane interface.

**Hybrid model**

the hybrid architecture enables `one or more direct logical interface(s)` between management system(s) and O-RU in addition to a logical interface between O-DU and the O-RU. It should be noted that the NETCONF clients connecting to the O-RU may be of different classes (e.g. O-DU and SMO).

O-DU and SMO

![](https://i.imgur.com/I9LrV35.png)


## M-Plane functional description

**[Start up installation](https://hackmd.io/sXSBRsnCSGWbpkxssBdxRg)**

`Start up` installation specifies the establishment of M-plane connection between O-RU and NETCONF client such as O-DU and NMS.




**[Software Management](https://hackmd.io/J3IItNsIQ6m3KHeoYSKFWw)**
- software download
- installation
- validation
- activation of new SW

**[Configuration management](https://hackmd.io/k8g_7bShR5-MWx9s4iGdVQ)**

- Retrieve Resource State
- Modify Resource State
- Modify Parameters and Retrieve Parameters.

NETCONF `get-config` and `edit-config` RPCs shall be used for configuration parameter retrieval and updates at the O-RU

**[Performance management](https://hackmd.io/k6VfaMGbTliJmjS3dMpIkg)**

Performance management describes the measurements and counters used to collect data related to O-RU operations. The purpose of Performance Management is optimizing the operation of the O-RU.

**The measurement results are reported by two options:**

1. **YANG Notification:**

    This option uses the stats definition of YANG model per measurement group. In this case, `get rpc` and/or `notification` will be used

2. **File Upload:**

    This option uses the file upload procedure defined in File management. The measurement results are saved to a data file periodically.

**[Fault Management](https://hackmd.io/dJflWeulS5KKfTgmyKnFmg)**

Fault management is responsible for sending alarm notifications to the NETCONF Client. Fault Management allows alarm notifications to be disabled or enabled as well as alarm subscription.

**[File Management](https://hackmd.io/D4oJ0BWSQJ2D6lIExW2KKw?view)**

File management allows the O-RU Controller to trigger an O-RU to perform upload of files stored on O-RU to O-RU Controller. The O-RU may provide different kinds of files and retrieved files can be used for various purposes. Simultaneous multiple file upload operations can be supported under the same sFTP connection between O-RU to O-DU/SMO


## Interface
[O-RU to O-DU Interface Management](https://hackmd.io/4LGRuYTJRBS9zTAWfAsOTg?view)



**Over NETCONF**

1. Configuration Management
2. Async Notifications

**Over Json/REST**

1. Async Notifications

![](https://i.imgur.com/ldw0aEB.png)


### Security

---

The M-Plane security shall be supported using the SSHv2 layer in accordance with RFC 6242 .

TLS 1.2 in accordance with RFC 7589 [41] may be optionally supported.

![](https://i.imgur.com/9c1Zigi.png)