...
The RIC platform has the following external interfaces
E2
...
(2021-12-08) 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
...
https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-sdl/en/latest/user-guide.html
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 as per A1APv3.0 and A1APv3.1. Note that the A1 mediator in the RIC platform is independent of A1TD (A1 type definitions) and passes them as opaque blobs to xApps.
...