Versions Compared

Key

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

...

Status:

  • Release E planning:
    • HW (python, go, C++):
      • Do they need to use the REST interface for E2 subscription?
    • RC:
      • Talks underway about Mavenir contributing a new xApp that implements the E2SM RC CONTROL message for UE handover request
      • The current TS xApp would call the new RC xApp (jnstead of the REST call to the Viavi E2 simulator)
    • LP:
      • Consume data from inFlux (done?) and create a new name space for predictions
    • Anomaly Detection and traffic steering use case:
    • QP/AD:
      • Integrate load prediction with QP?
    • Possible other contributions
      • Geo-location (Viavi) - need to get the final word from Viavi
      • Network slicing: Multiple interested parties but what needs to be implemented still unclear
    • Integration (Viavi simulator, KPIMON, AD, QP, LP, TS, RC)
      • Coordinate
      Need to coordinate
      • between Viavi simulator and KPIMON xApp on which metrics and how are communicated using E2SM KPM
      • Need to discuss with E2SM KPM experts on the intended way of communicating signal strength measurements
      Viavi still considering providing a simple open source geo-location xApp
    • Interest on RAN slicing xApp from HCL and academic partners
      • Enhancement of the Anomaly detection and traffic steering use case with
      load prediction and
      • potentially geo-location to be determined
  • RICAPP PTL role: Some folks have expressed interest - Matti will find out about the process.

...