Status (9-8-20): Integration of KPIMON in progress, new xApps under design, QP-Driver updated to use new SDK for alarms and metrics.

Status (9-30-20): Samsung taking over integration and testing of KPIMON; Viavi simulator producing data - an update in the data content expected this week (UE throughput, UE ID); ML-model building started based on Viavi and other simulated data (QP, AD); new xApp repos requested (Signal Storm Protection, Load Prediction); bug fixes to HelloWorld, E2 AP/SM abstraction layer underway for HelloWorld.

Status(11-17-20): ML-xApps (QP,AD) code committed - dealing with merge issues. End to end testing and bug fixes underway.  E2AP/SM abstraction work for HelloWorld (C++) xApp completed. New repos created for HelloWorld in go and python (for Dawn).

Mission: Better manageability of, for example, E2 connections, the RIC platform as well as xApps via the xApp frameworks.

Primary Goals: Support operator-initiated health-check via E2 and be able to close all current or reject all future E2 connections. More manageability of the RIC platform and xApps, including, for example, platform statistics from E2 and A1 and more capabilities in the language-specific xApp frameworks and SDL (shared data layer).

Cherry release highlights (2020-12-01): We implemented the operator-initiated E2 connection health check. There is now more alignment in the level of support of various xapp framework and SDL features in python, c++ and go. For example: SDL (shared data layer) now also supports notifications in Python. The xApp framework for C++ now supports alarms, statistics and configuration management. xApps can now use SDL notifications for changes in connection states of E2 nodes. By confirming route updates before continuing we increased robustness in management of internal routes. We now also support using existing non-E2 protocols for communication with RAN. We also adapted the scaling implementation for E2 termination to the reversal of E2AP connection initiation introduced by E2AP 01.00. The E2 manager can now reject new E2 connections requests in addition to closing all E2 connections. E2 and A1 now provide platform statistics for their connections. 

Detailed list of JIRA items that we worked on in Cherry (requires LinuxFoundation login): Remaining open items: link  (1 items). Items that are marked as done: link (23 items). Moved out from Cherry: link (24 = 13 stretch goal items and 11 "normal items").

Status 2020-12-11:

HCL: RIC-360 done.

ATT: (e-mail sent): RIC-359 (likely postponed)

Status 2020-12-08:

HCL: DONE: RIC-149 (=RIC-362), RIC-509, RIC-109.  // delayed into Dawn: RIC-150 // RIC-360: Code submitted & Merged CLOSE once gerrit review in RIUC-678 is done (see open review https://gerrit.o-ran-sc.org/r/c/it/dep/+/5237)

ATT: (e-mail sent): RIC-359 (likely postponed)

Status 2020-11-24:

HCL: RIC-149, RIC-150, RIC-360, RIC-509. Ask if RIC-362 (duplicate of RIC-149) is already implemented by HCL.

Nokia: (1) stats related: RIC-422 posytponed to early Dawn. Related stats-items (RIC-33, RIC-126) postponed to later (likelly ZZZ_future). (2) submgr related RIC-76 and RIC-71 were postponed.

ATT: (e-mail sent): RIC-359 (likely postponed)

Status 2020-11-05: Remaining open items

RIC-56: I now moved all sub user storied for actual alarms as separate independent Epics. Can be tested with artiifical alarm or QP driver xApp alarm. The framework is ready. Marking RIC-56 as Done.

RIC-57: two subitems open (for Nune 2020-11-12 reminder sent) and one for Timo (RIC-104). Two e-mails sent. Result: RIC-104 (not yet done, move out of Cherry) Done

RIC-76:  e-mail sent as item 6 in bulk mail.

RIC-95: Completed (2020-11-12)

RIC-359: Queried status. 2020-11-12: Reminder sent

RIC-360, RIC-150. RIC-362, RIC-509: Reminder to subteam h1 sent.

RIC-363: e-mail send to Matti. 2020-11-12: reminder sent and Matti will close it with some conclusions. DONE

RIC-365 DONE. and remaining subuser stories (like RIC.429) moved to future work epic (RIC-681)

RIC-367 DONE and two subitems moved to Dawn RIC-682. xapp-framework python. e-mail sent we need to get the E2AP work done, and then we could extract one subitem as own epic and clsoe teh oevrall item.

RIC-422: e-mail send to Nune (bulk mail)

Status 2020-09-30: (a) I (PTL) am happy to see HCL doing work on Sonarqube for repos. Much more work done by HCL in context of benchmarking (simulator work), new helm and k8s version, Redis cluster suppor and testing, JIRA link for team H1  (b)  Samsung also doing key work items, e.g. for RIC-95 health check (with side affect of support for E2 SERVICE QUERY and related) - suffering from simulator support (RIC-372 already mentioned below), work started on demo (aka more elboarte hello world) xApp in go/python. (c) four items moved out of Cherry as already visible that not enough time: link . (d) 28 Cherry items = 4 moved out of Cherry + 10 done + 14 in progress or still to be started (e) Matti and Thoralf gave a presentation on RIC status in the virtual ONeS 2020 (link). Waiting for copyright/licensing results between O-RAN and O-RAN SC.

Status 2020-09-02: (a) I (PTL) am happy to see teams from Samsung and HCL joining the project with them actively working on capabilities related to the E2 simulator (actually in Alex' simulator project), more test automation (using the robotframework), benchmarking, SDL (shared data layer). (b) RIC-372 was the first commit from these new participants (c) we might be aiming for self-certification under LF's CII badge level "basic", (d) work on O1-related functions, like E2 and A1 statistics, or some alarms already done. (e) Adaptation to E2APv1.1 (likely released in November) only happening post-Cherry.

• The primary goal of Non-RT RIC is to support intelligent RAN optimization by providing policy-based guidance, ML model management and enrichment information to the near-RT RIC function so that the RAN can optimize, e.g., RRM under certain conditions.
• It can also perform intelligent radio resource management function in non-real-time interval (i.e., greater than 1 second).
• Non-RT RIC can use data analytics and AI/ML training/inference to determine the RAN optimization actions for which it can leverage SMO services such as data collection and provisioning services of the O-RAN nodes.
• Non-RT-RIC will define and coordinate rApps (Non-RT-RIC / SMO appliciations) to perform Non-RT-RIC tasks.
• Non-RT-RIC will also host the new R1 interface (between rApps and SMO services)

Cherry Feature Scope:

• A1 Policies:
  • A1 Policy Management Service (hosted in ONAP CCSDK)
  • A1 Policy Controller Adapter (hosted in ONAP CCSDK)
  • A1 Simulator / test stub (SIM project)
  • A1 Policy Control-Panel (PORTAL project)
  • Support A1-AP v2.0.
• A1 Enrichment Information
  • Initial version of A1 EI Job coordination function/service
• Deployment/Integration
  • Docker-based & OSC Kubernetes deployment & ONAP OOM Kubernetes deployment (Overlaps with SMO project)
• rApps
  • Very simple hello-world rApp
  • TrafficSteering usecase
  • Healthcheck usecase
• rApp support
  • Initial rApp catalogue/inventory
  • Initial approach with rApp packaging (overlaps with "common App" usecase, & SMO project)
• Requirement gathering & initial test/integration with ML supporting functions in NONRTRIC/SMO
• Requirement gathering & initial test/integration with data collection & coordination functions in NONRTRIC/SMO
• Requirement gathering & initial test/integration with CMDB (if progressed in ONAP), Topology & Inventory functions in SMO

Update - 06/October/2020

• Prototyping of the A1 enrichment Information coordination service is in progress.
• Initial prototype of rApp registration / catalogue function, Very simple hello-world rApp.
• Ongoing work to support O-RAN WG2 A1-P spec.
• A1 Policy Management Service and A1 Policy Controller Adapter hosted in ONAP CCSDK are getting ready for ONAP Guilin Milestone RC0.
• Other ongoing tasks: documentation, automated integration testing, CSIT, Run benchmark test in a cloud instance, Function Test environment refactoring, etc.

Update - 04/November/2020

• Initial rApp catalogue is mostly ready for first tests.
• A1 Enrichment Information job coordination function ready.
• Ongoing work on A1 EI job control in NONRTRIC Control Panel.
• A1-AP v2.0 (A1 Policy) is ready for implementation (Internal implementation already completed, now ready for release to the community)
• Integration of ONAP A1 Controller functions
• Extensions & evolution for NONRTRIC Control Panel & A1 SIM (version update, & gneral improvements)
• A1 Policy Management Bench-marking completed ... more info to follow
• Other ongoing tasks: documentation, automated integration testing, CSIT, Function Test environment refactoring, etc.

Update - 08/December/2020

• A1 Enrichment Information (EI) Coordination function ready for release
• Updated A1 EI job control in NONRTRIC Control Panel ready for release
• Updated A1 EI simulator integrated in A1 SIM
• Initial rApp catalog ready for release
• A1-AP v2.0 (A1 Policy) functionality in A1 Adapter, A1 Policy Management System, NONRTRIC Control Panel, and A1 SIM
• ONAP A1 Controller functions integrated
• General extensions & evolution for NONRTRIC functions (version update, & gneral improvements)
• HTTP Proxy support added for A1 Interface (Policy)
• Other ongoing project maintenance tasks: documentation, automated integration testing, Function Test environment refactoring, etc.
• Demo available at: 2020-12-04 - OSC NONRTRIC Cherry Demo

Primary Goals: 

• 2 servers. 2 AIO servers with HA (high availability), the controller functionality and storage functionality will be deployed at the 2 servers with standby-active mode managed by "service management". If one server or one service in one server has error, it will be switched from active to standby one to maintain the service availability.
• 2 AIO servers with additional worker node.

Cherry Feature Scope:  TODO

Cherry Feature Scope: 

• Automated CLM and SonarQube Scanning CI Jobs
• Improve CI for OSC projects
• Validate and and Test platform and use cases 

Status (28 Oct. 2020): 

• CLM scanning jobs:
  • done: A1 and python xApp-framework
  • Pending: Rest of the projects
• SonarQube scanning jobs:
  • 21 projects passed
  • 7 project failed
• OSC Lab internal CI pipeline:
  • Initiate works with O-DU-low CI 
• OSC Lab Testing and Validation
  • SMO Yang model tests completed.
  • VM created for TS use case validation.