...
The RIC platform has the following external interfaces. Note that additional per-component documentation can be found here: link
E2
(20212023-1206-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.030) Since the F release we support E2APv2.0. The older protocol versions - E2APv1.1 and E2AP1.0 - are not supported anymore (use old OSC near-RT RIC releases if needed (The E release has E2APv1.1 and is backwards compatible with E2APv1.0); or upgrade). Some features that are worthwhile to point out as supported:
- OID support in function definitions (RIC-640, implemented in E, Added in E2APv1.1),
- configuration transfer capabilities (RIC-638, not in E (existing partial implementation will be further developed implemented in F),
- support for multiple TNL associations (RIC-639, no concrete plan to implement)
...
Not supported
- no RIC-784 (timer handling in E2 control messages),
- no RIC-785 (error indication handling),
- no RIC-783 (support for control ack to selected xapps)
...
- no E2 Reset (RIC-386+RIC-387)
...
- In submgr we only support Subscriptions with single actions (RIC-75).
...
- No support for multiple TNL associations (RIC-639).
Note that the RIC platform is generally independent of E2SMs (E2 service models) and E2APv1.0, 1.1, 2.0 work with the various E2SMs as there are no dependencies.
...