The OAM project focus on the following topics:
Provide complete implementation for OAM functions (FCAPS).
The following Specifications needs to be considered for software updates:
https://orandownloadsweb.azurewebsites.net/specifications
O-RAN O1 Interface specification for O-CU-UP and O-CU-CP 3.0 - July 2022
O-RAN.WG5.O-CU-O1.0-v03.00
O-RAN O1 Interface for O-CU-UP and O-CU-CP - YANG Models 3.0 - July 2021
O-RAN.WG5.O-CU-O1.0-YANGs-v03.00
O-RAN O1 Interface specification for O-DU 2.0 - July 2021
O-RAN.WG5.MP.0-v02.00
O-RAN O1 Interface for O-DU 4.0 - YANG Models - July 2022
O-RAN.WG5.MP.0-YANGs-v04.00
O-RAN O1 Interface for O-DU 4.0 - configuration tables - July 2022
O-RAN.WG5.MP.0-AnnexD-v04.00
Function | Source of Data model O-RAN-SC Status: 2020-10-07 |
---|---|
Fault | 3GPP: _3gpp-common-fm (Fallback from Bronze RFC8632: ietf-alarms) |
Configuration | (see next lines) |
| O-RAN-FH: RFC8343: ietf-interfaces |
| (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 |
| Open: o-ran-user-management |
Inventory (hardware) | RFC8348: ietf-hardware,yang and iana-hardware.yang Open: only for O-RU and O-DU; O-DU anyhow optional |
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 |