Non-Realtime RIC
Space shortcuts
Page tree
Skip to end of metadata
Go to start of metadata

Coordinates


The Non-RealTime RIC (RAN Intelligent Controller) is an Orchestration and Automation function described by the O-RAN Alliance for non-real-time intelligent management of RAN (Radio Access Network) functions. The primary goal of the Non-RealTime RIC 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 functions in the RAN to achieve higher-level non-real-time objectives. NONRTRIC functions include service and policy management, RAN analytics and model-training for the near-RealTime RICs. The Non-RealTime RIC project provides concepts, specifications, architecture and reference implementations as defined and described by the O-RAN Alliance architecture.

The OSC NONRTRIC implementation will communicate with near-RealTime RIC elements in the RAN via the A1 interface. Using the A1 interface the OSC NONRTRIC will facilitate the provision of A1 Policies; monitor and provide basic feedback on policy state from near-RealTime RICs; provide A1 Enrichment Information as required by near-RealTime RICs; act as a hosting platform for rApps (Non-RealTime RIC applications); host the R1 interface between rApps and the underlying SMO and Non-RT-RIC platforms; and manage the exposure towards rApps of SMO platform functions, Non-RT-RIC platform functions, and the capabilities of other rApps.

The NONRTRIC functions partly leverage and extend some existing infrastructure from ONAP to support non-realtime control of the RAN (Radio Access Network).

All implementations will be demonstrated in open community labs to prove functionalities and to give feedback to the O-RAN working groups.

Functional view of OSC NONRTRIC

Non-RealTime-RIC functional view

The figure above shows a functional view of the Non-RealTime RIC function in OSC. Many of the functions will be supported by the underlying SMO platform.

Functional view of OSC NONRTRIC - Latest available functionality


The figure above shows the latest released functionality for the Non-RealTime RIC functions in OSC (F Release & ONAP Jakarta).

For more information see out F Release Developers Guide

Team

JIRA

GERRIT

Overlap with ONAP / SMO

The early vision for the O-RAN Non-RealTime RIC, and OSC NONRTRIC project, did not significantly differentiate between SMO platform and Non-RT RIC platform functions, where the main SMO requirements could be partly fulfilled by using a combination of OSC OAM, OSC NONRTRIC, and ONAP functions (See OAM Project: SMO - Service Management and Orchestration).

In the meeting from 2019-08-12 we clarified the (then) expected integration of ONAP and OSC OAM/NONRTRIC functionality.


Since then OSC has created an OSC SMO project.

In the NONRTRIC project we will reuse ONAP (and other open-source) functions where needed, and where necessary support changes upstream if needed. We strongly believe that open-source software should be reused where possible and appropriate, the maximize community participation and avoid community fragmentation. For example, we reuse and contribute to the A1 Policy Management functions in ONAP, which emerged from a merging of related activities in both OSC and ONAP. We also reuse numerous other ONAP functions, e.g. SDNC, Control Loop, Policy Framework, CPS, DMaaP, DCAE VES & PM functions, etc..

Requirements

News

Child Pages

Recent Changes

 Click here to expand...

Show More Please wait

  • No labels

12 Comments

  1. Tracy Van Brakle


    1. John Keeney

      A newer version of the proposal is now available:

  2. Tracy Van Brakle

  3. Farheen Cefalu

    Tracy Van Brakle , I am going to move the Non-real-time RIC pages into their own Space.  The space will be called Non-real-time RIC (NRTRIC).  You will be able to access these pages from the Projects link in the top navigation bar above.  I opened a ticket with LF to move these pages to that space.  Let me know if you agree with this. These pages are a good start.  Thank you! 

  4. Arindam Mondal

    Hello,

    I would like to know more about the R-APP and R-APP coordinator in Non-RT-RIC. What is the functionality it is supposed to perform? Is there any relation with x-APP in Near-RT-RIC? How it is going to be realized in ONAP?

    1. John Keeney

      Hi Arindam. We are currently working through some internal discussion on this. I will revert to the community when I have more detail. Thanks.

      1. Arindam Mondal

        Hello John Keeney,

        Thank you for your reply. 

        Also it would be wonderful If you could provide more details on implementation of A1 Policy Management Service in ONAP. Is there any discussion ongoing in community?

        I'm following this page: Release A

        1. John Keeney

          Hi Arindam.

          The A1 Policy Management Service is not implemented in ONAP. It is implemented here in OSC as part of this NONRTRIC project. The documentation and code is available here in our gerrit repo (nonrtric), the generated docs, and the intro given the Release A page.

          Thanks.


          Follow Up: December 2020

          The A1 Policy Management Service has since re-homed to ONAP CCSDK.

          It still forms a key part of the OSC NONRTRIC as seen in our Cherry Release.

          Please see https://wiki.onap.org/pages/viewpage.action?pageId=84672221 for more detail

          1. Arindam Mondal

            Hello John,

            According to the above "integration to ONAP architecture" , ONAP is going to play the role of NON-RT-RIC. In that case it also needs to implement the policy management function( which is already developed by OSC) in ONAP.

            Is there any plan to integrate the policy management agent code to ONAP? If that is the case then which module in ONAP is going to play the role.

            1. John Keeney

              Hi Arindam.

              ONAP most definitely plays a major role in the current OSC NONRTRIC work since ONAP forms the basis for the current OSC SMO.

              It is unclear if an A1 Policy Management Service is needed in ONAP. This is currently being discussed as part of the scoping discussions between ONAP and OSC.
              If an A1 Policy Management Service is required in ONAP we may consider proposing to upstream or maybe re-home this component into ONAP in the Guilan timeframe.

              The current OSC A1 Policy Management Service can be executed as a DCAE microservice.

              I invite you to join any discussions about the need for an A1 Policy Management Service in ONAP vs OSC, or alternatively using the released OSC service in ONAP. Any contribution from yourself or Samsung would be more than welcome.

              Thanks.
              John

              1. Arindam Mondal

                Hi John,

                Thank you for your invitation to join community meeting. We will deifinitely try to attend those meeting and have discussion.

  5. Mehmet Dengiz

    Hello,

    We want to develop rAPP for external SON solution. Could you share useful links for development rAPP?


    Thanks