elinuxhenrik | 02cb601 | 2022-04-04 13:07:36 +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 |
JohnKeeney | 94fdf47 | 2024-06-28 15:51:18 +0100 | [diff] [blame] | 3 | .. Copyright (C) 2021-2023 Nordix Foundation |
| 4 | .. Copyright (C) 2024: OpenInfra Foundation Europe. All rights reserved. |
| 5 | |
| 6 | O-RAN A1 Interface |
| 7 | ~~~~~~~~~~~~~~~~~~ |
| 8 | |
| 9 | The O-RAN Alliance defines a new management interface "A1" for Radio Access Network (RAN) Management. This interface interconnects a new logical |
| 10 | "Non-RealTime RAN Intelligent Controller (Non-RT-RIC)" function in the Service Management & Orchestration (SMO) layer with a new logical "Near-RealTime |
| 11 | RAN Intelligent Controller (near-RT-RIC)" function in the RAN. This new A1 interface allows the Non-RT-RIC to provide Policy Guidance to the RAN (near-RT-RIC) |
| 12 | to steer its operation. These policies are defined by the O-RAN Alliance as "A1 Policies". The specifications for the A1 Interface, including A1 Policy support, |
| 13 | can be found on the O-RAN Alliance Specifications website. |
| 14 | |
| 15 | The A1 Policy functions are Orchestration and Automation functions for non-real-time intelligent management of RAN functions. The primary goal of the A1 Policy |
| 16 | functions is to support non-real-time radio resource management, higher layer procedure optimization, policy optimization in RAN, and providing guidance, |
| 17 | parameters, policies and AI/ML models to support the operation of Near-RealTime RIC (RAN Intelligent Controller) functions in the RAN to achieve |
| 18 | higher-level non-real-time objectives. |
| 19 | |
| 20 | A1 Policy functions form part of a Non-Realtime RIC as defined by O-RAN Alliance. Non-Realtime RIC functions include service and policy management, RAN analytics, |
| 21 | and model-training for the Near-RealTime RICs. The ONAP & O-RAN-SC A1 Policy work provides concepts, specifications, architecture and reference implementations |
| 22 | for A1 Policy support as defined and described in the O-RAN architecture. |
elinuxhenrik | 02cb601 | 2022-04-04 13:07:36 +0200 | [diff] [blame] | 23 | |
| 24 | A1 Policy Management Service (from ONAP CCSDK) |
| 25 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 26 | |
JohnKeeney | 94fdf47 | 2024-06-28 15:51:18 +0100 | [diff] [blame] | 27 | The A1 Policy Management Service is a microservice which maintains a transient repository of: |
elinuxhenrik | 02cb601 | 2022-04-04 13:07:36 +0200 | [diff] [blame] | 28 | |
JohnKeeney | 94fdf47 | 2024-06-28 15:51:18 +0100 | [diff] [blame] | 29 | * All A1 policies instances in the network. Each policy is targeted to a near-RT-RIC instance and is owned by a 'service' (e.g., rApps or the NONRTRIC Dashboard). |
| 30 | * All near-RT-RICs in the network. |
| 31 | * All Policy types supported by each near-RT-RIC. |
elinuxhenrik | 02cb601 | 2022-04-04 13:07:36 +0200 | [diff] [blame] | 32 | |
JohnKeeney | 94fdf47 | 2024-06-28 15:51:18 +0100 | [diff] [blame] | 33 | The service provides : |
elinuxhenrik | 02cb601 | 2022-04-04 13:07:36 +0200 | [diff] [blame] | 34 | |
JohnKeeney | 94fdf47 | 2024-06-28 15:51:18 +0100 | [diff] [blame] | 35 | * Unified REST API for managing A1 Policies in all near-RT-RICs. |
| 36 | * Compliant with O-RAN R1 specification for A1-Policy Management (R1-AP v5.0, with additional features & fixes) |
| 37 | * Synchronized view of A1 Policy instances for each rAPP |
| 38 | * Synchronized view of A1 Policy instances in each near-RT-RIC |
| 39 | * Synchronized view of A1 Policy types supported by each near-RT-RIC |
| 40 | * Lookup service to find the near-RT-RIC to control resources in the RAN as defined in O1 (e.g. which near-RT-RIC should be accessed to control a certain CU or DU, which in turn controls a certain cell). |
| 41 | * Monitors all near-RT-RICs and maintains data consistency, e.g. recovery from near-RT-RIC restarts |
| 42 | * Support for different Southbound APIs to the near-RT-RICs (different versions of the A1-P and other similar APIs). |
| 43 | * HTTPS can be configured to use a supplied certificate/private key and to validate peers towards a list of trusted CAs/certs. |
| 44 | * HTTP proxy support for tunneling HTTP/HTTPS connections. |
| 45 | * Fine-grained access-control - with new optional callouts to an external auth function |
| 46 | * Fine-grained monitoring metrics, logging & call tracing can be configured |
elinuxhenrik | 02cb601 | 2022-04-04 13:07:36 +0200 | [diff] [blame] | 47 | |
JohnKeeney | 94fdf47 | 2024-06-28 15:51:18 +0100 | [diff] [blame] | 48 | See also A1 Policy Management Service in ONAP: `Wiki <https://wiki.onap.org/display/DW/O-RAN+A1+Policies+in+ONAP>`_, :doc:`Documentation<onapa1policymanagementservice:index>`. |
elinuxhenrik | 02cb601 | 2022-04-04 13:07:36 +0200 | [diff] [blame] | 49 | |
| 50 | Implementation: |
| 51 | |
| 52 | * Implemented as a Java Spring Boot application. |
| 53 | |
elinuxhenrik | b3eae52 | 2022-06-23 10:31:09 +0200 | [diff] [blame] | 54 | This product is a part of :doc:`NONRTRIC <nonrtric:index>`. |