Schedule
The OAM project focus on the following topics:
Provide complete implementation for OAM functions (FCAPS).
INFO:
The list below needs to be updated using the yang data models provided by 3GPP:
https://forge.etsi.org/rep/3GPP/SA5/data-models/tree/master/yang-models
| Function | Source of Data model O-RAN-SC (to be aligned with O-RAN Alliance, 3GPP and SDOs) (Status: 2020-02-18: proposed) |
|---|---|
| Fault | RFC8632: ietf-alarms |
| Configuration | (see next lines) |
| RFC8343: ietf-interfaces,yang |
| (see next lines) |
-- Network Time Protocol | RFC7317: ietf-system,yang |
-- Precision Time Protocol | RFC8575: ietf-ptp,yang (check if new IEEE standard was adopted) |
| to be updated based on SDO progress |
| Accounting | not scope of O-RAN and O-RAN-SC - listed just for completeness of FCAPS |
| Performance | 3GPP-xml, file, VES |
Security | (see next lines) |
| RFC8446: Transport Layer Security |
| RFC7317: ietf-system,yang |
| Inventory (hardware) | RFC8348: ietf-hardware,yang and iana-hardware.yang and of cause o-ran-hardware@2019-07-03.yang for the O-RAN identities. |
| Software Management | Management interfaces:
Use case: Start with and xRan-fronthaul radio unit and perform and upgrade to an o-ru with the OpenFronthaul M-plane and upgrade further to an O-RU with an O-RAN/3GPP common O1 management interface. |
| Backup and restore | OpenROADM manifest file |
| xApp onboarding (from O1 point of view) | under development by WG2 and Near-RT-RIC project |
| Subscription for VES | RFC8639: ietf-subscribed-notifications augmented by opnfv-ves-push.yang Note: CR for 3GPP approved. |