Skip to end of metadata
Go to start of metadata


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 NONRTRIC 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 NONRTRIC implementation will communicate with near-RealTime RIC elements in the RAN via the A1 interface. Using the A1 interface the NONRTRIC 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. 

As shown in the Component Architecture diagram below, the NONRTRIC exists within the ONAP eco-system, leveraging existing infrastructure 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 function in OSC (Amber+ Release & ONAP Frankfurt).

For more information see out Bronze Release Developers Guide

Integration into ONAP

In the meeting from 2019-08-12 we clarified the expected integration of ONAP and OSC OAM/NONRTRIC functionality. Note the O1 and A1 interfaces and protocols.






Child Pages


  File Modified
PNG File non-rt-ric-netconf-component-architecture.png Jun 26, 2019 by Martin Skorupski
Microsoft Word Document RIC non-RT_OSC_project_proposal_20-June-2019.docx Jul 03, 2019 by Tracy Van Brakle
PDF File 2019-06-O-RAN-SC-PoC#01-Intro-1.pdf Jul 09, 2019 by Tracy Van Brakle
PDF File RICnon-RT_OSC_project_proposal.pdf Jul 17, 2019 by John Keeney
Microsoft Powerpoint Presentation OOF_PCI_Dublin_POC_Demo_20190724_v_2.0.pptx Jul 26, 2019 by Tracy Van Brakle
PNG File NONRTRIC-FunctionalView.png Feb 27, 2020 by John Keeney
PNG File NONRTTIC-AmberFunctionalView.png Feb 27, 2020 by John Keeney
PNG File o-ran-onap-integration-Aug2019.png Feb 27, 2020 by John Keeney
PNG File o-ran-onap-integration-Dec2019.png Feb 27, 2020 by John Keeney
PDF File OSC-2020.05.28-WG2-I-OSC-NONRTRIC-Status-JohnKeeney-v01.pdf Jun 12, 2020 by John Keeney
PDF File 20200123 OSC NONRTRIC Jan23 WG2 ShortStatus - John Keeney.pdf Jun 12, 2020 by John Keeney
PDF File 20190822 ORAN WG2 OSC-NONRTRIC Status 20190822.pdf Jun 12, 2020 by John Keeney

  • No labels


    1. A newer version of the proposal is now available:

  1. 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! 

  2. 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. 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. 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. 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.


          1. 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. 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.


              1. Hi John,

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