...

• Release E planning:
  • HW-C++: Shraboni agreed to update HW-C++ to call new subscription API in xApp framework-C++ (if HCL agrees to update it)
  • HW-python/go: Attempt to address documentation missing on readthedocs - email bounced.
  • RC: Meeting with Mavenir was delayed by Mavenir (to next week)
  • LP: issue integrating with Torch
  • MassiveMIMO xApp: possibly in E Release
  • QP/AD: (add load prediction and potentially geo-location as features)
  • Bouncer: start working on again.
  • Possible other contributions:
    
    • Geo-location (Viavi) - still waiting for final word from Viavi - the Viavi simulator may just provide location in inFlux directly (without an xApp in this release)
    • Network slicing: Nothing expected from RICAPP (but we can do something if we have the cycles)
  • Integration (Viavi simulator, KPIMON, AD, QP, LP, TS, RC)
    • The expectations of KPIMON and RC need to be specified exactly for Viavi to know what needs to be provided
• Open networking presentation - input?
• RICAPP PTL role:
  • OSC (Jack Murray) suggested we determine the new PTL within the project (RICAPP)
  • For continuity of the project, ideally the new RICAPP PTL would come from the current RICAPP committers and active participants
  • The new PTL should be elected by the current RICAPP committers (voting details to be determined)
  • Some project members have expressed interest!
  • Next step:
    • Candidates prepare candidate statement: name, company, experience with open source project, background in the RICAPP project, mission statement
    • Candidate statements posted on RICAPP wiki
    • Deadline: Sept 3rd.
    • Voting details determined by next meeting (Sept 7) and voting happens after the next meeting.
• OSC lab access problem (Subhash) - Matti will email Rich - problem resolved (account had expired).

2021-08-03:

Status:

• Release E planning:
  • HW (python, go, C++):
    • Do they need to use the REST interface for E2 subscription? (dependency on xApp framework work - under discussion)
    • Add new features (python JIRA tickets already there, go to be added).
    • Document now showing in readthedocs - Matti will send email
  • 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 and create a new name space for predictions
    • Implement AI model for video related prediction (VM size got very large)
  • QP/AD:
    
    • Integrate load prediction with QP - let's discuss
    • Integration with Viavi simulator - TBD.
  • Bouncer:
    • Robustness of platform and additional E2 messages
    • Possible use of REST interface for subscription
  • 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 - Matti will reach out to Rittwik
  • Integration (Viavi simulator, KPIMON, AD, QP, LP, TS, RC)
    • 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
    • Enhancement of the Anomaly detection and traffic steering use case with potentially geo-location to be determined
• RICAPP PTL role: Some folks have expressed interest - Matti will find out about the process.
• Open networking presentation - input

...