blob: d0bb5b33860c3d7ba544bedbaae41a5009622bb6 [file] [log] [blame]
demx8as62493dbc2019-11-13 23:57:47 +01001.. This work is licensed under a Creative Commons Attribution 4.0 International License.
2.. SPDX-License-Identifier: CC-BY-4.0
3.. Copyright (C) 2019 highstreet technologies and others
4
5OAM Operation and Maintenance Overview
6======================================
7
demx8as653c4f572020-06-14 10:22:57 +02008The O-RAN SC OAM project provides administrative and operator
demx8as62493dbc2019-11-13 23:57:47 +01009functions for O-RAN components, such as Near-Realtime-RAN-Inelegent-Controller,
10O-RAN Centralized Unit, O-RAN Distributed Unit and O-RAN Radio Unit.
11
12The project follows the specifications for the O1 interface as provided by
13O-RAN Working Group1.
14
demx8as653c4f572020-06-14 10:22:57 +020015The O-RAN-SC OAM project adds features and functions to the OpenDaylight-based ONAP
16controller 'CCSDK/SDNC'. It is built on the Common Controller Framework
17to control and manage O-RAN managed elements and O-RAN managed functions.
18
19.. figure:: ./_static/o-ran-architecture.png
20 :alt: SDN-R in ONAP
21
22 SDN-R in ONAP
23
demx8as62493dbc2019-11-13 23:57:47 +010024
25Project Resources
26-----------------
27
demx8as62bb02ea2020-06-13 13:47:30 +020028The project uses the following Linux Foundation resources:
demx8as62493dbc2019-11-13 23:57:47 +010029
demx8as62bb02ea2020-06-13 13:47:30 +020030* The source code is maintained in this Gerrit:
demx8as62493dbc2019-11-13 23:57:47 +010031 `<https://gerrit.o-ran-sc.org/r/admin/repos/oam>`_
32
demx8as62bb02ea2020-06-13 13:47:30 +020033* The build (CI) jobs are in this Jenkins:
demx8as62493dbc2019-11-13 23:57:47 +010034 `<https://jenkins.o-ran-sc.org/view/oam/>`_
35
demx8as62bb02ea2020-06-13 13:47:30 +020036* Issues are tracked in this Jira:
demx8as62493dbc2019-11-13 23:57:47 +010037 `<https://jira.o-ran-sc.org/projects/OAM/>`_
38
demx8as62bb02ea2020-06-13 13:47:30 +020039* Project information is available in this Wiki:
demx8as62493dbc2019-11-13 23:57:47 +010040 `<https://wiki.o-ran-sc.org/display/OAM/Operations+and+Maintenance>`_
41
42
43Scope
44-----
45
46According to the O-RAN-SC-OAM-Architecture document all ManagedElements
47(near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the
48O1-interface.
49
50The O-RAN-OAM-interface specification defines
51
52- a NetConf-Server for Configuration Management (CM) and
53- a http-client for Fault Managment (FM), Performance Management (PM) and other
54 events on each Management-Service-Provider (MnS-Provider) running on the
55 ManagedElement (ME).
56
57THe O-RAN-SC-OAM project provides reference implementation according to the
58O-RAN OAM (WG1) documents. In addition we provide a common MnS-Consumer for
59development and module test purposes. The assumption is that the projects
60for the ManagedElements can concentrate on the more important user-plane.
61
62Of cause each project needs its own OAM repo to address the specific needs
63of the ManagedElement.