Coordinates
- PTL: John Keeney
- Wiki: https://wiki.o-ran-sc.org/display/RICNR
- JIRA: https://jira.o-ran-sc.org/projects/NONRTRIC/issues
- Code / Gerrit:
- nonrtric : https://gerrit.o-ran-sc.org/r/admin/repos/q/filter:nonrtric
- portal/nonrtric-controlpanel : https://gerrit.o-ran-sc.org/r/admin/repos/portal/nonrtric-controlpanel
- sim/a1-interface : https://gerrit.o-ran-sc.org/r/admin/repos/sim/a1-interface
- Docs:
- nonrtric : https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric
- portal/nonrtric-controlpanel : https://docs.o-ran-sc.org/projects/o-ran-sc-portal-nonrtric-controlpanel
- sim/a1-interface : https://docs.o-ran-sc.org/projects/o-ran-sc-sim-a1-interface
- Email List:
- OSC "discuss" mailing list: https://lists.o-ran-sc.org/g/discuss: discuss@lists.o-ran-sc.org
- Please use hashtag #nonrtric
- Meetings: https://wiki.o-ran-sc.org/display/RICNR/Meetings
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
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 G Release Developers Guide
Team
- PTL: John Keeney
- Committers: John Keeney Patrik Buhr Björn Magnusson Kevin Timoney Yennifer Chacon
JIRA
GERRIT
- nonrtric : https://gerrit.o-ran-sc.org/r/admin/repos/q/filter:nonrtric
- portal/nonrtric-controlpanel : https://gerrit.o-ran-sc.org/r/admin/repos/portal/nonrtric-controlpanel
- sim/a1-interface : https://gerrit.o-ran-sc.org/r/admin/repos/sim/a1-interface
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
-
NONRTRIC Status Update to TOC
See TOC Minutes (2023-05-18) and Slides for more information -
H-Release: Demonstration: "LCM of ASD-based CNFs using ONAP CNFM function in Standalone mode"
See Video (HD), Video (SD) and Slides for more information -
H-Release: Demonstration: "CAPIF for Service Registration & Service Discovery"
See Video (HD), Video (SD) and Slides for more information -
NONRTRIC functions released in OSC G Maintenance Release
See Release G for more information -
NONRTRIC functions released in OSC G Release
See Release G for more information -
G-Release: Demonstration: "Deploying & Running NONRTRIC platform and App"
See Demo for more information -
NONRTRIC Project: Update to O-RAN Face-to-face meeting in Madrid
Slides: 20221020 ORAN F2F - NONRTRIC Update - John Keeney.pdf -
G-Release: Demonstration: "Enforcing Service Exposure for rApps"
See Demo for more information -
G-Release: Demonstration: "PM Collection & Delivery to rApps"
See Demo for more information -
NONRTRIC functions released in OSC F Maintenance Release
See Release F for more information -
O-RAN Alliance WG 2 Status update
WG 2 wiki: Meeting notes
Slides: OSC-2022.08.04-WG2-I-OSC-NONRTRIC-ShortStatus-JohnKeeney-v01.pdf -
NONRTRIC functions released in OSC F Release
See Release F for more information -
NONRTRIC functions released in OSC E Release
See Release E for more information -
O-RAN Alliance WG 2 Status update
WG 2 wiki: Meeting notes
Slides: OSC-2021.11.25-WG2-I-OSC-NONRTRIC-ShortStatus-JohnKeeney-v01.pdf -
NONRTRIC functions released in OSC D Release
See Release D for more information -
O-RAN Alliance WG 2 Status update
WG 2 wiki: Meeting notes
Slides: OSC-2021.04.29-WG2-I-OSC-NONRTRIC-ShortStatus-JohnKeeney-v01.pdf -
OSC NONRTRIC achieves a "Passing" grade for CII Best Practices Badging Program
-
Demo of OSC NONRTRIC & ONAP A1 functions at LFN Developer & Testing Forum - Feb 2021
Slides & Video: 2021-02-03 - ONAP: Demo: O-RAN A1 Policy & Non-RealTime-RIC automated test/demo environment -
O-RAN Alliance WG 2 Status update
WG 2 wiki: Meeting notes
Slides: OSC-2021.01.21-WG2-I-OSC-NONRTRIC-ShortStatus-JohnKeeney-v01.pdf
NONRTRIC functions released in OSC Cherry Release
See Release C for more information
Demo of OSC Cherry Release functionality:
Slides & Video: 2020-12-04 - OSC NONRTRIC Cherry Demo
O-RAN Alliance WG 2 Status update
WG 2 wiki: Meeting notes
Slides: OSC-2020.09.03-WG2-I-OSC-NONRTRIC-Status-JohnKeeney-v01.pdf
NONRTRIC functions demonstrated in O-RAN Virtual Exhibition
"Non-RT RIC based Quality of Experience (QoE) modification"
NONRTRIC functions released in OSC Bronze Release
See Release B for more information
O-RAN Alliance WG 2 Status update
WG 2 wiki: Meeting notes
Slides: OSC-2020.05.28-WG2-I-OSC-NONRTRIC-Status-JohnKeeney-v01.pdf
Demo & Status after Amber Maintenance Release
Slides: Amber+ NONRTRIC Function demo
Demo Recording: it-weekly-20200304-2.mp4
NONRTRIC functions extended in OSC Amber Maintenance Release
See Release A 1.1 - Maintenance for more information
O-RAN Alliance WG 2 Status update
WG 2 wiki: Meeting notes
Slides: 20200123 OSC NONRTRIC Jan23 WG2 ShortStatus - John Keeney.pdf
NONRTRIC functions released in OSC Amber Release
See Release A for more information
O-RAN Costa Rica F2F meeting: NONRTRIC Status Update
Slides: 20191003 WG2 ORANSC NONRTRIC Status - John Keeney.pdf
O-RAN Alliance WG 2 Status update
WG 2 wiki: Meeting notes
Slides: 20190822 ORAN WG2 OSC-NONRTRIC Status 20190822.pdf
First PoC Conducted
Slides & recording: Link to PoC read-out recording
Second PoC Conducted
OOF_PCI_Dublin_POC_Demo_20190724_v_2.0.pptx
Updated Project Proposal
RICnon-RT_OSC_project_proposal.pdf
Child Pages
- Project Scopes
- NONRTRIC Development Guide
- Operations and Management
- Meetings
- NONRTRIC: Requirements
- NONRTRIC: Project events
- Benchmark tests
- Function Test
12 Comments
Tracy Van Brakle
John Keeney
A newer version of the proposal is now available:
Tracy Van Brakle
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!
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?
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.
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
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
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.
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
Arindam Mondal
Hi John,
Thank you for your invitation to join community meeting. We will deifinitely try to attend those meeting and have discussion.
Mehmet Dengiz
Hello,
We want to develop rAPP for external SON solution. Could you share useful links for development rAPP?
Thanks