Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT)

Mission: E2 updates with first E2APv2.0 support and improvements in registration and subscription interface in xapp frameworks.

Original primary goals: RIC-878 A1 mediator testing in nanobot; RIC-860 xapp testing nanobot enhancements: wider coverage of functionality, e.g., Subscription deletion // RIC-849 Second step of reimplementation of A1 mediator in golang, excl. A1AP-EI  // RIC-714 support for DMS REST interface in addition to DMS CLI // RIC-698 Switch from Redis 5 to Redis 6 // partially done only RIC-704 E2 check, validate and define how various overload and disconnect case are handled, incl. checking highload-results from dawn;  RIC-886 Support two SCTP streams in same association for global (support functions) and functional procedures (ric services);  RIC-916 new reconnect timer in E2 to reject new connect for x seconds; RIC-888 interface so that xApps can only query E2SMs with a given OID; RIC-722 + RIC-867 base support for E2APv2.0 (same level of functionality as before) in e2t, e2m, submgr, and nodeb-rnib; RIC-638 Adapt configuration transfer capabilities as defined in E2AP v2.0; RIC-383 Epic: implement E2AP RESET as per E2APv2.0; RIC-445 SSH container/pod that includes a RIC CLI ; RIC-870 helm3 in default deployment and move ric platform deployment to ric-dep; RIC-815 ric-dep documentation only in ric-dep and it-dep only has references ; RIC-827 support deployment of ric platform in different k8s namespaces to allow two parallel installations // RIC-808 List subscriptions by xApp debug interface; RIC-375 Remove support for ASN.1 (over RMR) based subscription in subscription manager (incl. xapp modifications) // RIC-705 update xappframework for c++ to change in xApp registration  // RIC-642 Add REST subscription support in Python framework

Planned F release highlights

TODO

= high-level release notes (2022-05-18) below (note that the release image list is here: link)

  • we updated from E2APv1.1 to E2APv2.0 for the existing supported procedures. Additionally E2 configuration transfer procedures (in E2 setup and via explicit E2 Node Configuration Update) are now supported.
  • Enhancements in the handling of E2 disconnect+connect cycles and in SCTP stream handling
  • xApps can now query the list of RAN functions by E2SM OID (and nodeb ID)
  • The reimplementation of the A1 mediator in golang has proceeded, but is not yet ready and not yet replacing the existing python implementation
  • Switch from Redis 5 to Redis 6 - primarily due to Redis 5 EOL
  • The ric deployment is now possible without the it/dep repo
  • More information in the debug interface of the subscription manager (which had some small adaptations for E2APv2.0, but these changes are not visible to xApps using the E2 subscription manager REST interface)
  • bug fixes as per link. Bugs relevant to production (i.e., not test) code: RIC-903 DefaultUser setup fails when authentication is enabled for InfluxDB; RIC-895 missing static route entries for service update messages (from E2T to E2M and back); RIC-889 Subscription Manager Swagger YAML file is wrong; RIC-872 RMR routing statistic data printout crash; RIC-885 sdlgo multi-namespace SDL event namespace filter issue; RIC-880 Wrong date in sdl (C++) rpm spec file; RIC-873 SDLCLI get - writes wrongly results to stderr in success case; RIC-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak); RIC-869 SDLCLI healthcheck - Redis sentinel status is wrong

For the F release of the near-RT RIC we did only limited integration testing: only the use cases: deploy RIC, deploy xApp and make E2 connection were tested.

Filled in end-of-release checklist : Release criteria checklist - Release F

Status 2022-05-05: From the 28 epics planned (link) we implemented 9 (link). 7 items have been moved out of the F release, e.g, because of implementation delays (link). Incomplete items: 12 (link). Additionally we fixed 18 bugs and small implementation tasks (link)

F release source code, container images and deployment instructions

The list of container images for the F release (link)

Code coverage: Code coverage reports (current coverage and list of components that need to set up Jenkins job for auto-generation of the reports as part of CI)

...