blob: df0966ca9d72fc49313bd4476599c3a5336bb106 [file] [log] [blame]
maximessone6b4d272019-10-31 13:26:13 +01001.. This work is licensed under a Creative Commons Attribution 4.0 International License.
2.. SPDX-License-Identifier: CC-BY-4.0
3
4
5..please write your project overview
6..please delete this content after editing
7
8
9Non-RT RIC Overview
10===================
11
12Find detailed description of what Non-RT RIC is on this `page`_.
13
14.. _page: https://wiki.o-ran-sc.org/display/RICNR/
15
16A-release architecture
17----------------------
18
19The architecture is as shown on the following picture:
20
21.. image:: ./images/architecture.png
22 :scale: 50 %
23
24The A1 controller is located in SDNC, an ONAP component. It communicates with ORAN via the A1 interface with the Near-RT RIC simulator.
25
26On the other end, it is accessible via a dashboard, that allows to interact with policies. The dashboard itself is split into the backend and the frontend, and can be deployed following the instructions on the `human interfaces page`_.
27
28.. _human interfaces page: ./human-interfaces.html
29
30Requirements for the Non-RT RIC project
31---------------------------------------
32
33There are functional requirements emitted by O-RAN WG2 for the Non-RT RIC, which are the following:
34
351. Non-RT RIC shall support data retrieval and analysis; the data may include performance, configuration or other data related to the application (recommended data shown in required data section for different use cases).
362. Non-RT RIC shall support relevant AI/ML model training based on the data in 1. for non-real-time optimization of configuration parameters in RAN or Near-RT RIC, as applicable for the use case.
373. Non-RT RIC shall support relevant AI/ML model training based on the data in 1. for generating/optimizing policies and intents to guide the behavior of applications in Near-RT RIC or RAN, as applicable for the use case.
384. Non-RT RIC shall support training of relevant AI/ML models based on the data in 1. to be deployed/updated in Near-RT RIC as required by the applications.
395. Non-RT RIC shall support performance monitoring and evaluation.
406. Non-RT RIC shall support a fallback mechanism to prevent drastic degradation/fluctuation of performance, e.g. to restore to the previous policy or configuration.
41
42The non-functional requirements are the following ones:
43
441. Non-RT RIC shall not update the same policy or configuration parameter for a given near-RT RIC or RAN function more often than once per second.
452. Non-RT RIC shall be able to update policies in several near-RT RICs.
46
47Moreover, there are functional requirements regarding the A1 interface:
48
491. A1 interface shall support communication of policies/intents from Non-RT RIC to Near-RT RIC.
502. A1 interface shall support AI/ML model deployment and update from Non-RT RIC to Near-RT RIC.
513. A1 interface shall support communication of enrichment information from Non-RT RIC to Near-RT RIC.
524. A1 interface shall support feedback from Near-RT RIC for monitoring AI/ML model performance.
535. A1 interface shall support the policy/intents feedback from Near-RT RIC to Non-RT RIC.
54
maximesson780b2bf2019-11-12 16:09:02 +010055.. _a1_policy_procedure:
56
maximessone6b4d272019-10-31 13:26:13 +010057A1 policy procedure
58-------------------
59
60As for A-release, the methods are as follows:
61
62+---------------------+--------------------------+--------------------------+
63| A1 policy procedure | Single policy method | Multiple policies method |
64+---------------------+--------------------------+--------------------------+
65| Create policy | PUT | |
66+---------------------+--------------------------+--------------------------+
67| Query policy | GET | GET (sequence of \*) |
68+---------------------+--------------------------+--------------------------+
69| Update policy | PUT | |
70+---------------------+--------------------------+--------------------------+
71| Delete policy | DELETE | |
72+---------------------+--------------------------+--------------------------+
73| Notify policy | POST | POST |
maximesson780b2bf2019-11-12 16:09:02 +010074+---------------------+--------------------------+--------------------------+