| elinuxhenrik | dbe5b8a | 2022-06-10 14:23:46 +0200 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. SPDX-License-Identifier: CC-BY-4.0 |
| 3 | .. Copyright (C) 2021 Nordix |
| 4 | |
| elinuxhenrik | 196cb83 | 2022-06-23 13:24:21 +0200 | [diff] [blame] | 5 | O-RU Fronthaul Recovery Use Case |
| 6 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| elinuxhenrik | dbe5b8a | 2022-06-10 14:23:46 +0200 | [diff] [blame] | 7 | |
| 8 | ************ |
| 9 | Introduction |
| 10 | ************ |
| 11 | |
| 12 | This use case is a non-real-world closed-loop use case to demonstrate automated recovery when the front-haul connection between an O-DU and O-RU is reset. |
| 13 | An application in the NONRTRIC senses the fault from the O-RU (O1-FM) and initiates a NETCONF reset operation (O1-CM) using the OAM controller. |
| 14 | More details about the use case can be found on the O-RAN SC wiki: `RSAC <https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20878423>`_ and `OAM <https://wiki.o-ran-sc.org/display/OAM/Closed+loop+use+case>`_. |
| 15 | |
| 16 | Non-RT RIC provides multiple implementation versions of the recovery part of the use case. One in the form of a python |
| 17 | script, one utilizing the ONAP Policy Framework, and one Go version that utilizes Information Coordination Service (ICS). |
| 18 | |
| 19 | The code is available in the `use case repo <https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric%2Frapp%2Forufhrecovery.git;a=summary>`_ |
| 20 | |
| elinuxhenrik | 196cb83 | 2022-06-23 13:24:21 +0200 | [diff] [blame] | 21 | This product is a part of :doc:`NONRTRIC <nonrtric:index>`. |
| 22 | |
| elinuxhenrik | dbe5b8a | 2022-06-10 14:23:46 +0200 | [diff] [blame] | 23 | Standalone Script Solution |
| 24 | ++++++++++++++++++++++++++ |
| 25 | |
| 26 | The script version consists of a python script that performs the tasks needed for the use case. There are also two |
| 27 | simulators. One message generator that generates alarm messages, and one SDN-R simulator that receives the config |
| 28 | change messages sent from the script and responds with alarm cleared messages to MR. |
| 29 | |
| 30 | All parts are Dockerized and can be started as individual containers, in the same network, in Docker. |
| 31 | |
| 32 | ONAP Policy Solution |
| 33 | ++++++++++++++++++++ |
| 34 | |
| 35 | There is also another solution for performing the front-haul recovery that is based on `ONAP Policy Framework <https://wiki.onap.org/display/DW/Policy+Framework+Project>`_. |
| 36 | A TOSCA Policy has been created that listens to DMaaP Message Router, makes a decision on an appropriate remedy and then signals the decision as a configuration change message via |
| 37 | REST call to the OAM controller. |
| 38 | |
| 39 | There is a `docker-compose <https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric.git;a=tree;f=docker-compose/docker-compose-policy-framework>`_ available |
| 40 | in the nonrtric repo for bringing up the complete standalone version of ONAP Policy Framework. |
| 41 | |
| 42 | The detailed instructions for deploying and running this policy are provided in |
| 43 | the `wiki <https://wiki.o-ran-sc.org/display/RICNR/O-RU+Fronthaul+Recovery+usecase>`_. |
| 44 | |
| 45 | ICS Consumer Solution |
| 46 | +++++++++++++++++++++ |
| 47 | |
| 48 | The ICS Consumer solution is implemented in Go and instead of polling MR itself, it registers as a consumer of the "STD_Fault_Messages" job in ICS. |
| 49 | |
| 50 | O-DU Slice Assurance |
| 51 | -------------------- |
| 52 | |
| 53 | A very simplified closed-loop rApp use case to re-prioritize a RAN slice's radio resource allocation priority if sufficient throughput cannot be maintained. Not intended to to be 'real-world'. |
| 54 | |
| 55 | The Go implementation of the solution can be found in |
| 56 | this `link <https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric/rapp/ransliceassurance.git;a=tree;f=smoversion>`__. |