Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Coordinates

Requirements:

...

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-352

...

Table of Contents

KEY INFORMATION

Gerrit: repo: https://gerrit.onap.org/r/admin/repos/ccsdk/oran

Meetings: ONAP/O-RAN-SC/SMO Meetings &  https://wiki.lf-o-ran-sc.atlassian.orgnet/wiki/displayspaces/RICNR/pages/15073287/Meetings & ONAP/O-RAN-SC/SMO Meetings

Docshttps://docs.onap.org/projects/onap-ccsdk-oran/en/latest/index.html?highlight=oran

Email List: ONAP "discuss" mailing list: onap-discuss@lists.onap.org

Related work in OSC: https://lf-o-ran-sc.atlassian.net/wiki/spaces/RICNR

JIRA (Epics):

  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-2475
  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-2476
  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-2991
  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-3229
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-3463
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-3617
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-3809
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-3909
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-3965
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-4024

Requirements (Older):

  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-38
    (Frankfurt)
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-352
    (Guilin)
  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-457
     (Honolulu
  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-722
    (Istanbul)
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-1045
    (Jakarta)
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-1256
    (Kohn)
  • Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-1391
    (London)

PROPOSALS BY RELEASE

The following table shows the progression of the O-RAN A1 Policy functions by release.

GUIDES & DOCS BY RELEASE

The following table shows the developer guides and documentation sites for the O-RAN A1 Policy functions.


DESCRIPTION


The O-RAN Alliance defines a new management interface "A1" for Radio Access Network (RAN) Management. This interface interconnects a new logical "Non-RealTime RAN Intelligent Controller (Non-RT-RIC)" function in the Service Management & Orchestration (SMO) layer with a new logical "Near-RealTime RAN Intelligent Controller (near-RT-RIC)" function in the RAN. This new A1 interface allows the Non-RT-RIC to provide Policy functions are an Orchestration and Automation set of Guidance to the RAN (near-RT-RIC) 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, can be found on the O-RAN Alliance Specifications portal

New functions to support A1 Policies have been added to ONAP. The A1 Policy functions are Orchestration and Automation functions for non-real-time intelligent management of RAN (Radio Access Network) functions. The primary goal of the A1 the A1 Policy functions is to support non-real-time radio resource management, higher layer procedure optimization, policy optimization in RAN, and providing guidance, parameters, policies and AI/ML models to support the operation of Near-RealTime RIC RIC (RAN Intelligent Controller) functions in the RAN to achieve higher-level non-real-time objectives. 

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, and model-training for the Near-RealTime RICs. The ONAP A1 Policy functions project work provides concepts, specifications, architecture and reference implementations for A1 Policy support as defined and described by the ONAP architecture.The A1 Policy functions implementation will communicate with Near-RealTime RIC elements in the RAN via the A1 interface. Using the A1 interface, the A1 Policy functions will facilitate the provision of policies for individual UEs or groups of UEs; monitor and provide basic feedback on policy state from near-RealTime RICs; provide enrichment information as required by Near-RealTime RICs; and facilitate ML model training, distribution and inference in cooperation with the Near-RealTime RICs. in the O-RAN architecture.

As shown in the Component Architecture diagram below, the A1 Policy functions exist within the ONAP eco-system, leveraging existing infrastructure to support non-real-time control of the RAN (Radio Access Network).

Functional view of ONAP A1 Policy functions

...

Image Added

The figure above shows a functional view of the A1 policy Policy functions in ONAP. Many of the functions will be supported by the underlying SMO platform.


GERRIT

...