OSC Cherry Release ORAN Software Community 2020 06

OSC Cherry Release O-RAN Software Community 2020. 06. 08 Rittwik Jana, David Kinsey (RSAC) 1

Agenda • Virtual meeting schedule • • • Kick-off discussion on Cherry Release: 8 -10 AM EST, June 8, Monday OSC-TIFG: Emulation SW discussion: 9 -10 AM EST, June 11, Thursday Bronze release coming soon [5 min] • What did we do in Bronze? • Cherry Release planning epics highlight [10 min] • PTLs to present cherry-picked epics [5 -10 mins each] • Non-RT RIC, Near-RT RIC, RICAPP, O-DU high, O-DU low, O-CU, INF, OAM, SIM, INT, DOC • Others (ongoing): • • 2 OAI collaboration: still unclear currently; ITU-T invitation: collaboration on the ITU-T Challenge Competition, discussion kicked off; OSC logo: pending OSC-TIFG discussions regarding emulator (short term and long term plans)

O-RAN SC Bronze update • Bronze release coming soon • • • Planned release date: June 14 PR under preparation: statement input from Nokia, Ericsson and Wind. River; Key features/highlights • Two E 2 E use cases: traffic steering and health check • O-DU-LOW successfuly passed the internal review • O-DU-HIGH: E 2 initiation and setup; subset of E 2 messages to support traffic steering • Near-RT RIC: (from pre-spec. to be) compliant with E 2 spec. v 1. 0, E 2 setup/failure, x. APP onboarding etc. • x. APP: various x. APPs for traffic steering, management, KPI monitoring etc. • Non-RT RIC: A 1 flow implementation and test; policy mangement with GUI • INF: Container-based O-Cloud design with real-time support of ARM-based realtime Kubernetes cluster • OAM: health check on O 1 flow • SIM: E 2 simulator enhancement implemented, e. g. E 2 ingest data pipeline from trace file • INT: CI/CD pipeline, OTF integration, Deployment artifact automation 3 3

OSC Cherry Release 4 4

OSC Cherry Release • - OSC Cherry Release epics https: //wiki. o-ran-sc. org/display/RSAC/Release+Cherry Use cases: Two end to end use cases demonstrating functionality for Traffic Steering and Health Check. The end to end use cases will continue to be developed further for the Bronze maintenance and Cherry release o Traffic Steering use case Continue Developing Traffic Steering (TS) and Quality Prediction (QP) x. Apps using ML Develop E 2 data ingest pipeline from E 2 simulator to perform traffic steering analytics o Health-check use case near-RT RIC self-check Flow #1 [Bronze – partial, to be completed in Cherry] O 1 near-RT RIC health-check [Bronze – partial, to be completed in Cherry] A 1 near-RT RIC health-check [Bronze] O-DU and O-CU health-check Flow #4 [Cherry] - O-CU o Put more focus on O-CU for Cherry o Interfacing with O-DU High and implement health-check compliance o Alignment needed with WG 8 - O-DU LOW (Intel flex. RAN) Continue O-RU stub testing with RU Simulator [Bronze maintenance] Interface with O-DU HIGH [Cherry] - O-DU HIGH (Radisys) o Subscription request/response/indication message support for Traffic Steering use case [Bronze] 5 o E 2 initialization and setup between O-DU and near-RT RIC [Bronze] o Implement O 1 health check [Cherry] OSCWG 8 Teams (O-RU emulator, O -DU low and O-DU high) working to agree on a minimum viable configuration 5

OSC Cherry Release Near-RT RIC o RAN initiated E 2 SETUP with E 2 nodes compliant with WG 3 E 2 specification v 1. 0 [Bronze] o x. App Framework enhancement [Cherry] o HA in all components [Cherry] o RIC time-series DB [Cherry] o Platform alarming functionality (e. g. , E 2 connection loss, msg overload, etc. ) [Cherry] Non-RT RIC o Construction of an A 1 policy management service (Policy Agent) [Bronze] o Policy Management GUI and Control Panel to view A 1 policies [Bronze] o Construction of A 1 controller and controller APIs [Bronze] o A 1 Flow (Healthcheck #3) implemented and tested [Bronze] o ONAP architecture alignment for SMO/Non-RT RIC [Cherry] o A 1 enrichment information gathering [Cherry] o R-APP platform API [Cherry] OSC- WGs 1, 2, 3, 6 6 6

OSC Cherry Release RICAPP o Construction of TS, MCx. App for measurement campaign, Hello. World [Bronze] o Continue development of various x. Apps for traffic steering (TS, QP, etc. ) using Machine Learning [Cherry] o Continue development of KPIMON x. App (from Samsung) for ingesting E 2 data and computing KPIs from realistic simulator (Viavi) [Cherry] o RIC SDK to support O 1 PM/FM/CM and A 1 -P [Cherry] OSCo Alignment needed with WG 3 E 2 SM for TS WG 3 OAM o Health check O 1 flow #2 implemented [Bronze] o Alignment needed with WG 1 on Information and Data models for alarms – mismatch found in Bronze testing between near-RT RIC and OAM projects o SMO Deployment based on ONAP Guilin o Epics - https: //wiki. onap. org/display/DW/Guilin OSCWG 1 7 7

INF o Real time platform to deploy O-DU for Intel and ARM architecture [Bronze] o Introduce high availability (HA) [Cherry] o Epics – https: //wiki. o-ran-sc. org/display/IN/Release+C+-+POR SIM o Enhancements to E 2 Simulator o RAN initiated E 2 SETUP [Bronze] o E 2 Data ingest pipeline from trace files [Bronze] o Introduce commercial Simulator into E 2 data pipeline [Cherry] o Key UE level & Cell level KPIs generated for Traffic Steering INT o Partial CI/CD pipeline, Deployment artifact automation, OTF integration DOC o Work in progress 8 8

INF • Bronze release, the O-Cloud deployment scenario uses a single server, AIO (all-in-one) • Intel Arch (IA) Kubernetes cluster • IA Starling. X enabled O-Cloud reference • ARM Kubernetes cluster • Cherry release, will extend deployment scenario to the following: • 2 servers. 2 AIO servers with HA (high availability) • Controller functionality and storage functionality will be deployed on 2 servers with standby-active mode. If one server or one service in one server fails, it will be switched from active to standby to maintain service availability. • 2 AIO servers with additional worker node • ARM Starling. X enabled O-Cloud reference • Epics – https: //wiki. o-ran-sc. org/display/IN/Release+C+-+POR • Start interoperability testing with the following components: • O-DU LOW [Bronze] • O-DU HIGH • O-CU Alignment with O-RAN WG 6 Orchestration and Cloudification specifications • Cloud Architecture and Deployment Scenarios v 02. 00 (O-RAN. WG 6. CAD-v 02. 00) • Cloud Platform Reference Design for Deployment Scenario B v 01. 00 (O-RAN. WG 6. CLOUD-REF-B-v 01. 00) • Orchestration Use Cases and Requirements for O-RAN Virtualized RAN v 01. 00 (O-RAN. WG 6. ORCH-USE-CASESv 01. 00) 9 9

O-RU, O-DU LOW, O-DU HIGH unified profile for Cherry 10 10

Other items • Discussions with Viavi for integration into OSC testing lab Proposal from Viavi to EC regarding short term and long term plans OAI collaboration: still unclear currently; ITU-T invitation: collaboration on the ITU-T Challenge Competition, discussion kicked off; OSC logo: pending • • • 11 11