"ECS API", ":download:`link <../enrichment-coordinator-service/api/ecs-api.json>`", ":download:`link <../enrichment-coordinator-service/api/ecs-api.yaml>`"
-rAPP Catalogue
-==============
+Service Catalogue
+=================
The Non RT-RIC Service Catalogue provides a way for services to register themselves for other services to discover.
-See `RAC API <./rac-api.html>`_ for how to use the API.
+See `SC API <./rac-api.html>`_ for how to use the API.
.. csv-table::
:header: "API name", "|swagger-icon|", "|yaml-icon|"
:widths: 10,5, 5
- "RAC API", ":download:`link <../r-app-catalogue/api/rac-api.json>`", ":download:`link <../r-app-catalogue/api/rac-api.yaml>`"
+ "SC API", ":download:`link <../r-app-catalogue/api/rac-api.json>`", ":download:`link <../r-app-catalogue/api/rac-api.yaml>`"
Complementary tools
===================
For more information about it, see the README file in the use case's folder.
.. image:: ./images/healtcheck.png
+
+O-RU closed loop recovery
+-------------------------
+Non-RT RIC provides two implementation versions of the recovery part of the use case. One in the form of a python
+script, and one utilizing the Policy Framework.
+
+Script version
+++++++++++++++
+The script version consists of a python script that performs the tasks needed for the use case. There are also two
+simulators. One message generator that generates alarm messages, and one SDN-R simulator that recieves the config
+change messages sent from the script and responds with alarm cleared messages to MR.
+
+All parts are Dockerized and can be started as individual containers, in the same network, in Docker.