...
The RIC platform has the following external interfaces
O1:
- Support for netconf "Hello exchange" (incl. capability exchange)
- Alarms as VES events as per RIC Alarm System
- get E2 stats (on number of packets over E2) via the path E2T->Prometheus->VESPA→(ONAP). Requires setting the environment variable VESMGR_PLT_CFG_FILE which contains the VESPA mapping for this path: Prometheus->VESPA
O2:
Support for O2 use case "Deploy xApp in near-RT RIC" in WG6's O-RAN orchestration use cases v2.0. This is done as per the CLI that is in this commit https://gerrit.o-ran-sc.org/r/c/ric-plt/appmgr/+/5816
A1:
(2021-05-25) Support for A1-Policy and A1-EI (RIC-129)
- Best checked from here: https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-a1/en/latest/user-guide-api.html
E2:
(2021-12-08-02) implementing all of E2APv1.1 (since E release), but see exception list below. Up to the D release (incl. D) we supported E2APv1.0. Note that E2APv1.1 is backwards compatible to E2APv1.0. So you can still connect with E2APv1.0 E2 nodes to the RIC. E2APv1.1 added three capabilities on top of E2APv1.0
- OID support in function definitions (RIC-640, implemented in E),
- configuration transfer capabilities (RIC-638, not in E (existing partial implementation will be further developed in F),
- support for multiple TNL associations (RIC-639, no concrete plan to implement)
0, excl. the three features added in E2APv1.1. Also no support for RIC-784 (timer handling in E2 control messages), RIC-785 (error indication handling), RIC-783 (support for control ack to selected xapps) and no E2 Reset (RIC-386+RIC-387).
In the F release we plan to support E2APv2.0 with the same level of functionality as in the E release, i.e., no implementation for the additional capabilities in E2APv2.0.
Xapp Frameworks
- Xapp frameworks in general: See xapp writers guide xApp_Writer_s_Guide_v2.pdf attached to this wiki page (Dawn onwards). The earlier xapp_Writer_s_guide.pdf is not to be used anymore. Generally, we are in the process of moving the app writing guide to https://docs.o-ran-sc.org.).
- Xapp framework for Go: as per link under "xApp framework for Go" in Near Realtime RAN Intelligent Controller (RIC)
- Xapp framework for python: as per link under "xApp framework for python" in Near Realtime RAN Intelligent Controller (RIC)
- Xapp framework for C++: as per link under "xApp framework for CXX" in Near Realtime RAN Intelligent Controller (RIC)
SDL API
RMR: Check the read-the-docs page: https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-lib-rmrsdl/en/latest/reluser-notesguide.html Additionally you might read RIC Message Router (RMR)Subscription manager
RMR: Check the read-the-docs page: https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-lib-submgrrmr/en/latest/userrel-notes.html Additionally you might read RIC Message Router (RMR)
Subscription managerguide.html and REST API: linkSDL API: https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-sdlsubmgr/en/latest/user-guide.html and REST API: link
Xapp onboarding and deployment: check section "RIC applications" in https://docs.o-ran-sc.org/projects/o-ran-sc-it-dep/en/latest/installation-guides.html#ric-applications on how to use the dms_cli to onboard and deploy xApps. Onboarding is the act of generating a Helm chart for the xApp from the its xApp descriptor. Using the generated helm chart (which is specific to a particular RIC instance) the xApp can be deployed.
...