Skip to end of metadata
Go to start of metadata

Note: Recording of meetings available here: Project meetings


  1. Quick overview of the RICAPP project and its goals for Release Amber (by Rajesh Panta)


  1. Status update on RICAPP epics for O-RAN Amber release: which ones will be completed for sure, completed likely, and which ones will move to Release B.


  1. Review of one page status update for the O-RAN SC TOC
  2. Discussion on ideas for B Release
    1. Impacts of A1/O1/E2 standardization
    2. E2 Control messages
    3. xApp composition/chaining?
    4. Resiliency (xApp replication, for example)
    5. New xApp ideas/volunteers?


  1. xApp updates:
    1. AC - mostly completed - documentation, persistence using SDL C++ library, A1-spec based policy guidance with support for multiple policy instances in progress
    2. MC - legal review completed, development can move back to LF, deployable xApp with some initial reports generated and sent using VES
    3. ML xApp - initial work, not a realistic working xApp in Amber release
    4. KPImon - repo created, feasibility analyzed
    5. UE Manager - moving to RIC platform project
  2. Discussion on open issues and release B ideas.


  1. OAM repo discussion with Martin Skorupski
  2. xApp status update: AC, MC, KPI Mon
  3. ML xApp presentation (Guy Jacobson)


  1. Release A Planning: Code freeze (Nov 2nd), only bug fixes and documentation after that
  2. Release A xApp status
    1. AC xApp: code, CI/CD/test coverage, some documentation done - implements pre-spec A1/E2
    2. MC xApp: code done, in repo soon - CI/CD, test coverage, and documentation to do
    3. ML xApp: sample code in repo - may not be a real xApp in Release A
    4. KPIMon xApp: repo created, sample message reviewed -
  3. xApps in Release B
    1. Multiple ML xApps for the Release B use case (Rittwik) - see
    2. Extensions of the current xApps


  1. any news from any of the xApps?
    1. no news


  1. Amber Release status for xApps
  2. Bronze Release planning:
    1. Traffic steering use case and xApps needed to support that (presentation by Gueyoung Jung )


  1. Amber Release status for xApps -
  2. xApp documentation - already covered in RIC platform meeting
  3. Bronze Release - TS use case
    1. Other Bronze epics will be discussed in the next meeting


  1. Any updates from team?
    1. Main developer of AC xApp is leaving AT&T
    2. Netsia - no resources available at the beginning of Bronze
  2. Bronze epics from RSAC team


  1. Review of Bronze epics
  2. Open issues/questions


  1. Review of traffic steering use case and xApps for the use case.


  1. Plan and timeline for Bronze release
  2. Open questions?


  1. Status update of Bronze release
  2. Open questions?


  1. Still waiting for TOC to approve repo requests
  2. HelloWorld: version 2 ready - deployment/config, rmr + SDL
  3. TS/QP/QP Driver: Design, learning of xApp frameworks
    1. Python/C++ xApp frameworks under development (see gerrit)
  4. KPIMON: Dev will start this week (Samsung)


  1. Finally a TOC approval for new xApp repos, repos created
  2. Status update (Matti)
  3. name-space and message schemas (Ron)


  1. Sprint demo:
    1. Last one: MC xApp with simulator
    2. This week: QP-Driver and its use of the xApp python framework
  2. Traffic steering use case detailed documentation: Traffic Steering Use Case xApps
  3. Status update:
    1. Mock-up data created in TS-UE-NIB and TS-cell-NIB
    2. JSON payloads for messages between xApp defined and refined
    3. QP-driver code in repo, others hopefully soon
    4. Stretch goal: TS, QP-Driver, and QP exchanging RMR-messages with payload by the end of this sprint
    5. KPIMON: Anticipated completion May 3rd


  1. Status update (Matti): RICAPP-04-14.pptx


  1. Sprint demo: HelloWorld xApp
  2. Two week extension for xApp from O-RAN SC TOC
  3. Status


  1. Status at code freeze:
    1. MC - done
    2. HW - done, needs documentation
    3. Traffic steering use case xApps:
      1. TS - done, testing in progress, needs documentation
      2. QP-Driver - done, testing in progress
      3. QP - unknown
      4. KPIMON - waiting for legal review


  1. Bronze status:
    1. MC - done,
    2. HW - being tested,
    3. TS-QP-driver-QP: being tested,
    4. KPIMON - legal review, hopefully in maintenance release
  2.  Cherry plan:
    1. Utilize new RIC SDK APIs: alarms, logging, config change, A1-P
    2. Extend the TS use case: E2 CONTROL, real ML model, integration with more realistic simulator


  1. Bronze status:
    1. TS use case xApps (TS, QP-D,QP) ready, tested, and released, KPIMON delayed until maintenance release due to legal review (+ testing required)
    2. HW demo and MC xApp also ready, tested and released
  2.  Cherry progress:
    1. Planning underway for the extension to the traffic steering use case, WG-3 spec will likely arrive late but we will try to accommodate it if possible
    2. QP-D: raises and cancels alarms (SDL availability) - first RIC component to raise an alarm
    3. In progress: all open source xApps using RIC SDK APIs for O1-PM/FM (alarms/metrics), O1-CM (configuration) and A1-P (policy intent).


  1. Bronze and Bronze maintenance status update.
    1. Bronze done with 5 xApps
    2. Waiting for Samsung KPIMON and Viavi simulator output for the maintenance release.
  2. Cherry progress.
  3. How to contribute:
    1. Help with an existing xApp (Find an unassigned user story here and contact me)
    2. Suggest a new xApp idea/.
  4. HCL is interested in contributing to the ML pipeline in xApp (QP) - followup by email
  5. Idea on how infra metrics could be used in xApps was discussed - in the O-RAN  architecture they should be only exposed to nonRT RIC, need to think if RIC's own infra metrics could be somehow used by xApps.


  1. Bronze Maintenance status:
    1. Received extension from TOC, still waiting for KPIMON and Viavi simulator trace file
  2. Cherry progress:
    1. HelloWorld (C++) user stories available to anybody interested
    2. Discussions on new xApps:
      1. HCL (Matti set up a call Wed morning at 9am ET - 6:30pm India)
      2. Samsung (to be discussed)
    3. Still pruning epics and user stories
  3. James ChinaMobile: new xApp idea - will reach out to Matti by email


  1. Bronze Maintenance status:
    1. Received KPIMON code and was able to build image and run, problem with SubManager supporting KPM E2SM blocked completion of use case. Full TS use case delayed to Cherry Release.
  2. Cherry progress:
    1. Existing user stories (HelloWorld, QP-Driver) available for anybody interested
    2. Discussions on new xApp ideas with HCL, ChinaMobile, and Samsung - licensing details to be determined, then Matti will request new repos. (see slides: RICAPP-20-08-04.pptx)
    3. Rittwik will follow up with Viavi on data.


  1. Cherry status:
    1. TS use case: Hope that we will get data from Viavi RAN simulator very soon (for E2 SIM as well as training xApps).
    2. KPIMON xApp (Samsung): SubManager bug has been fixed - still exploring why E2 submission request does not complete.
    3. AD xApp (HCL): Repo requested from OSC TOC, approvals by email, LF repo creation request submitted, meeting to review design soon.
    4. HelloWorld xApp: HCL will take some user stories
    5. QP: HCL will provide alternative ML model (Matti will create separate user stories)
    6. ChinaMobile decision on license.
    7. Matti will send UE/cell schema to Neeraj Gupta.
    8. Akash will email Matti about HelloWorld xApp.
  2. Discussion soon with Samsung about Cherry xApp work.


  1. Cherry status:
    1. HCL updates (Ramesh) - Matti will set up a meeting on Thursday. Include Subhash.
    2. Viavi software has been installed - Matti will follow up see how we can share data.
    3. KPIMON xApp (Samsung): Issues with RIC platform (routing etc) and E2 Simulator have been resolved, KPIMON receives E2 REPORT messages but fails to process them (maybe simulator payload issue).
    4. AD xApp (HCL): Repo created, waiting for data (Viavi)
    5. MC xApp (AT&T): Integrated with SonarCloud - we will share hints after we get it fully working.
    6. HelloWorld xApp: User stories available: code coverage/sonar, integration with C++ framework (alarms, metrics, config), simulator extension - Matti will assign
    7. QP xApp (AT&T, HCL): Waiting for data - discuss on Thursday.
    8. TS xApp: HCL (Vaishali) attempted to test A1 policy - waiting for guidance from Ron.
    9. Any updates from ChinaMobile - final decision this week.
    10. Does KPIMON collect other information than Ron's schema - Matti will check.
  2. Discussion soon with Samsung about Cherry xApp work.


  1. Cherry status:
    1. Viavi simulator has been installed - hopefully we can share data any day now!
    2. KPIMON xApp (Samsung): KPIMON receives E2 REPORT messages but fails to process it - close to resolution.
    3. Load Predictor (ChinaMobile): Agreement on license, waiting data + Matti will request a repo.
    4. Signal Storm Protection (Samsung): Ironing out details - Cherry goal to implement simple detection.
    5. HelloWorld xApp: Work will resume on abstracting E2AP and HelloWorld E2 SM as C++ objects.
    6. Anomaly Detection (AD): Meeting with HCL, waiting for data. Trying different algorithms with sample data.


  1. Cherry status:
    1. Viavi simulator: we can receive data from the simulator but all the fields are not there yet (e.g., UE throughput/PRB usage, UE ID) - Viavi is working on an updated version hopefully this week. Share with Subhash and Neeraj.
    2. QP xApp: Simple ML model trained to predict signal strength using Viavi data (that being only relevant input data available).
    3. KPIMON xApp (Samsung): Samsung has taken over the integration testing using E2 Simulator - Beijing team on vacation this week.
    4. Load Predictor (ChinaMobile):  Repo request sent to TOC.
    5. Signal Storm Protection (Samsung):  Repo request sent to TOC, use case presented in WG-1 UCTG.
    6. HelloWorld xApp: Subscription related bug fixed by Samsung, E2 AP/SM abstraction designed and implementation in progress.
    7. Anomaly Detection (AD - HCL): Updates from Neeraj. Demo in 2.5 weeks?
    8. Akash, Vaishali: New message type - Matti will add two message types, coordinate with Ron on message format. Need to check Routing Manager. Matti will schedule a meeting with Neeraj later this week.


  1. Hello world (HW) python and go repos requested (Samsung) - waiting for TOC approvals
  2. Load Prediction (LP) and Signal Storm Protection (SSP) repos approved by TOC - waiting for LF
    1. Meeting with James about LP tomorrow.
  3. Viavi simulator updated - now producing all requested fields, simulates UE mobility - waiting for legal issues at Viavi before sharing output. LF recommends new repo for the simulator data.
  4. KPIMON: Debugging session last night - new versions of SubMan, RM, etc disappeared from nexus staging
  5. AD: Message types added, demo this week!
  6. vF2F slides for RICAPP (Matti)


  1. Hello world (HW) python and go repos approved by TOC (Samsung) and repo creation requested  - waiting for LF
  2. HW (C++) now includes C++ classes for E2AP (to be moved to C++ framework) + E2 HW SM, subscription flow works, adding unit tests
  3. Load Prediction (LP) and Signal Storm Protection (SSP) repos create and LP discussed with James (ChinaMobile)
  4. Viavi simulator updated - legal issues at Viavi resolved. Requested SIM PTL (Alex) to request a repo.
  5. KPIMON: Works with E2 SIM now - detailed testing underway + unit testing, documentation, xapp descriptor - Matti will reach out
  6. QP: Adding ML model still underway (AT&T, HCL - working on that, meeting soon)
  7. AD demoed at sprint demo (HCL)
    1. - files being checked in right now, issue with interaction with TS, RM config update to be checked in, e2e test for Cherry release, Sunil will replace Neeraj from HCL
  8. Matti will send WG-1 use case document to Ramesh (for network slicing documentation)


  1. Traffic steering use case video at the demo meeting last week.
  2. Hello world (HW) python and go repos created (Samsung)
    1. get started in Cherry, issues with JJBs/info.yaml, Subhash needs help from xapp go framework (Nune - Matti emailed Subhash and Nunel)
  3. HelloWorld (C++) user stories completed with regard to E2AP/E2SM wrapping classes.
  4. Viavi simulator: Repo created in SIM project, either Viavi or AT&T will commit simulator output data set
  5. KPIMON: Still some cleanup to do (Ron reported a bug) + documentation, unit tests etc
  6. AD xApp:
    1. Trained ML model cannot be committed to LF (size limit) - alternative plan?
    2. First patch of code submitted - O-RAN job builder verification step missing
  7. QP: Still waiting for AT&T version to be submitted? Could HCL submit theirs first? HCL will submit theirs by Friday.
  • No labels