The OAM project focus on the following topics:
Provide complete implementation for OAM functions (FCAPS).
Committed
- Topology Service for rApps
- Topology service image
- Enhanced rApp from D-Release (using OAM interfaces - OpenFronthaul, NETCONF, VES only)
- Visualization of the topology
- Topology information used for deployment
Under Discussion for F-Release:
- O2 interface
- … for App Deployment: CRD O2DMS
- … for xNF Deployment: TACKER O2DMS
- … for creating K8s Common Network Deployments
- Pre O2IMS Provisioning (Pre-Spec)
- O2DMS K8s Native Provisioning (Pre-Spec)
- … for O2IMS
- O2 IMS Inventory API
- Test automation based on ONAP python-sdk
- Integration of OpenWirelessLab in OPNFV/ONAP official labs with focus on O-RAN use cases
The result is a new lab icon in this page and pointing to the page mentioned in item #2
Specifications
The following Specifications needs to be considered for software updates:
https://www.o-ran.org/specification-access
- O-RAN Architecture Description 5.0 - July 2021
O-RAN.WG1.O-RAN-Architecture-Description-v05.00 - O-RAN Use Cases Detailed Specification 6.0 - July 2021
O-RAN.WG1.Use-Cases-Detailed-Specification-v06.00 - O-RAN Operations and Maintenance Architecture 5.0 - July 2021
O-RAN.WG10.OAM-Architecture-v05.00 - O-RAN Operations and Maintenance Interface 5.0 - July 2021
O-RAN.WG10.O1-Interface.0-v05.00 - O-RAN Management Plane Specification - YANG Models 7.0 - July 2021
O-RAN.WG4.MP-YANGs-v07.00 O-RAN O1 Interface specification for O-CU-UP and O-CU-CP - July 2021
O-RAN.WG5.O-CU-O1.0-v01.00O-RAN O1 Interface for O-CU-UP and O-CU-CP - YANG Models - July 2021
O-RAN.WG5.O-CU-O1.0-YANGs-v01.00O-RAN O1 Interface specification for O-DU 2.0 - July 2021
O-RAN.WG5.MP.0-v02.00O-RAN O1 Interface for O-DU 2.0 - YANG Models - July 2021
O-RAN.WG5.MP.0-YANGs-v02.00O-RAN O1 Interface for O-DU 2.0 - configuration tables - July 2021
O-RAN.WG5.MP.0-AnnexD-v02.00- O-RAN Management interfaces for Transport Network Elements 2.0 - July 2021 (O-RAN.WG9.XTRP-MGT.0-v02.00)
VES JSON-Schemas
- ONAP VES 7,2.1
- 3GPP TS 28.532 V16.6.0
- Annex B (Informative):
Guidelines for the integration of 3GPP MnS notifications with ONAP VES - A.1.1 OpenAPI document "provMnS.yaml" (CM-Notify)
- A.2.1 OpenAPI document "faultMnS.yaml" (FM)
- A.4.2 OpenAPI document "perfMnS.yaml" (PM - job changes)
- A.5.1 OpenAPI document "heartbeatNtf.yaml
- Annex B (Informative):
- O-RAN-SC PM-Measurement streaming
| 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 |