You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 34
Next »
Note: Recording of meetings available here: Project meetings
2019-08-13
- Quick overview of the RICAPP project and its goals for Release Amber (by Rajesh Panta)
2019-08-27
- 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.
2019-09-10
- Review of one page status update for the O-RAN SC TOC
- Discussion on ideas for B Release
- Impacts of A1/O1/E2 standardization
- E2 Control messages
- xApp composition/chaining?
- Resiliency (xApp replication, for example)
- New xApp ideas/volunteers?
2019-09-24
- xApp updates:
- AC - mostly completed - documentation, persistence using SDL C++ library, A1-spec based policy guidance with support for multiple policy instances in progress
- MC - legal review completed, development can move back to LF, deployable xApp with some initial reports generated and sent using VES
- ML xApp - initial work, not a realistic working xApp in Amber release
- KPImon - repo created, feasibility analyzed
- UE Manager - moving to RIC platform project
- Discussion on open issues and release B ideas.
2019-10-08
- OAM repo discussion with Martin Skorupski
- xApp status update: AC, MC, KPI Mon
- ML xApp presentation (Guy Jacobson)
2019-10-22
- Release A Planning: Code freeze (Nov 2nd), only bug fixes and documentation after that
- Release A xApp status
- AC xApp: code, CI/CD/test coverage, some documentation done - implements pre-spec A1/E2
- MC xApp: code done, in repo soon - CI/CD, test coverage, and documentation to do
- ML xApp: sample code in repo - may not be a real xApp in Release A
- KPIMon xApp: repo created, sample message reviewed -
- xApps in Release B
- Multiple ML xApps for the Release B use case (Rittwik) - see https://oranalliance.atlassian.net/wiki/spaces/NonRTRIC/pages/235634729/WG2+F2F+4+San+Jose+Meeting-Oct.+2019
- Extensions of the current xApps
2019-11-05
- any news from any of the xApps?
- no news
2019-11-19
- Amber Release status for xApps
- Bronze Release planning:
- Traffic steering use case and xApps needed to support that (presentation by Gueyoung Jung )
2019-12-03
- Amber Release status for xApps - https://wiki.o-ran-sc.org/display/TOC/Project+Readiness+for+Amber+Release
- xApp documentation - already covered in RIC platform meeting
- Bronze Release - TS use case
- Other Bronze epics will be discussed in the next meeting
2019-12-17
- Any updates from team?
- Main developer of AC xApp is leaving AT&T
- Netsia - no resources available at the beginning of Bronze
- Bronze epics from RSAC team
2020-01-14
- Review of Bronze epics
- Open issues/questions
2020-01-21
- Review of traffic steering use case and xApps for the use case.
2020-02-04
- Plan and timeline for Bronze release
- Open questions?
2020-02-18
- Status update of Bronze release
- Open questions?
2020-03-03
- Still waiting for TOC to approve repo requests
- HelloWorld: version 2 ready - deployment/config, rmr + SDL
- TS/QP/QP Driver: Design, learning of xApp frameworks
- Python/C++ xApp frameworks under development (see gerrit)
- KPIMON: Dev will start this week (Samsung)
2020-03-17
- Finally a TOC approval for new xApp repos, repos created
- Status update (Matti)
- name-space and message schemas (Ron)
2020-03-31
- Sprint demo:
- Last one: MC xApp with simulator
- This week: QP-Driver and its use of the xApp python framework
- Traffic steering use case detailed documentation: Traffic Steering Use Case xApps
- Status update:
- Mock-up data created in TS-UE-NIB and TS-cell-NIB
- JSON payloads for messages between xApp defined and refined
- QP-driver code in repo, others hopefully soon
- Stretch goal: TS, QP-Driver, and QP exchanging RMR-messages with payload by the end of this sprint
- KPIMON: Anticipated completion May 3rd
2020-04-14
- Status update (Matti): RICAPP-04-14.pptx
2020-04-28
- Sprint demo: HelloWorld xApp
- Two week extension for xApp from O-RAN SC TOC
- Status
2020-05-12
- Status at code freeze:
- MC - done
- HW - done, needs documentation
- TS - done, needs documentation
- QP-Driver - done
- QP - unknown
- KPIMON - waiting for legal review