From: JohnKeeney Date: Tue, 25 Jun 2024 14:19:37 +0000 (+0100) Subject: Update NONRTRIC info on Project page. X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=commitdiff_plain;h=refs%2Fchanges%2F16%2F13016%2F1;p=doc.git Update NONRTRIC info on Project page. Issue-ID: NONRTRIC-972 Change-Id: If63eb9fda630656c1ef913cbd61bfeef06216568 Signed-off-by: JohnKeeney --- diff --git a/docs/projects.rst b/docs/projects.rst index 5652458..a2b741d 100644 --- a/docs/projects.rst +++ b/docs/projects.rst @@ -61,15 +61,16 @@ More detailed function documentation can be found as follow: Non-RealTime RAN Intelligent Controller (NONRTRIC) -------------------------------------------------- -Non-RT RIC focus on feature functionality of A1-interface (consumer and provider), and closed-loop use cases. The Non-RT RIC project will also work together with the OAM project to align activities on a case-by-case base for O1 interfaces. Project should focus on use cases supported in ONAP. The work should be sponsored in O-RAN and initial code contributions in O-RAN SC. Interoperability with ONAP should be aligned between the standards and will follow initial contributions in this project. +The O-RAN Non-RT RIC provides functionality for the A1-interface, R1-interface, and closed-loop use cases. The O-RAN SC NONRTRIC project works together with the OAM project, SMO project, AI/ML FW project and SIM project to align activities for O1 & O2 interfaces, and to provide consolidated SMO functionality. The Non-RT RIC project also provides capabilities to support rApps (Non-RT RIC Apps) and the R1 Interface. More detailed function documentation can be found as follow: -* :doc:`A1 Interface Simulator ` * :doc:`Non-RT RIC Components ` +* :doc:`A1 Interface Simulator ` * :doc:`Non-RT RIC Control Panel ` + Operations and Maintenance (OAM) -------------------------------- The O-RAN-SC-OAM project provides reference implementation according to the O-RAN OAM (WG1) documents. In addition we provide a common MnS-Consumer for development and module test purposes. The assumption is that the projects for the ManagedElements can concentrate on the more important user-plane.