| maximesson | e6b4d27 | 2019-10-31 13:26:13 +0100 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. SPDX-License-Identifier: CC-BY-4.0 |
| elinuxhenrik | 0a4c38b | 2020-04-14 10:59:36 +0200 | [diff] [blame] | 3 | .. Copyright (C) 2020 Nordix |
| maximesson | e6b4d27 | 2019-10-31 13:26:13 +0100 | [diff] [blame] | 4 | |
| elinuxhenrik | c7a0d73 | 2020-02-04 14:49:59 +0100 | [diff] [blame] | 5 | Requirements for the Non-RT RIC project |
| elinuxhenrik | 6208ce8 | 2020-11-18 15:15:07 +0100 | [diff] [blame] | 6 | ======================================= |
| maximesson | e6b4d27 | 2019-10-31 13:26:13 +0100 | [diff] [blame] | 7 | |
| 8 | Find detailed description of what Non-RT RIC is on this `page`_. |
| 9 | |
| 10 | .. _page: https://wiki.o-ran-sc.org/display/RICNR/ |
| 11 | |
| maximesson | e6b4d27 | 2019-10-31 13:26:13 +0100 | [diff] [blame] | 12 | There are functional requirements emitted by O-RAN WG2 for the Non-RT RIC, which are the following: |
| 13 | |
| elinuxhenrik | c7a0d73 | 2020-02-04 14:49:59 +0100 | [diff] [blame] | 14 | #. 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). |
| 15 | #. 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. |
| 16 | #. 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. |
| 17 | #. 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. |
| 18 | #. Non-RT RIC shall support performance monitoring and evaluation. |
| 19 | #. 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. |
| maximesson | e6b4d27 | 2019-10-31 13:26:13 +0100 | [diff] [blame] | 20 | |
| 21 | The non-functional requirements are the following ones: |
| 22 | |
| maximesson | f217fff | 2020-04-09 15:16:04 +0200 | [diff] [blame] | 23 | #. 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. |
| 24 | #. Non-RT RIC shall be able to update policies in several Near-RT RICs. |
| maximesson | e6b4d27 | 2019-10-31 13:26:13 +0100 | [diff] [blame] | 25 | |
| 26 | Moreover, there are functional requirements regarding the A1 interface: |
| 27 | |
| elinuxhenrik | c7a0d73 | 2020-02-04 14:49:59 +0100 | [diff] [blame] | 28 | #. A1 interface shall support communication of policies/intents from Non-RT RIC to Near-RT RIC. |
| 29 | #. A1 interface shall support AI/ML model deployment and update from Non-RT RIC to Near-RT RIC. |
| 30 | #. A1 interface shall support communication of enrichment information from Non-RT RIC to Near-RT RIC. |
| 31 | #. A1 interface shall support feedback from Near-RT RIC for monitoring AI/ML model performance. |
| 32 | #. A1 interface shall support the policy/intents feedback from Near-RT RIC to Non-RT RIC. |