Cherry Release updates Dawn Release Prelim Epics Rittwik

Cherry Release updates Dawn Release Prelim. Epics Rittwik Jana, David Kinsey and all PTLs 2020 -06 -22 | Page 1

Agenda Review the Cherry Release Project Status o Introduce the SMO project Review the Dawn Release Planning Discuss OSC Concerns with projects o O-CU Moving Forward o ONAP Alignment Discuss MVP and how it affects OSC Planning 2020 -06 -22 | Page 2

Cherry release update

2020 -06 -22 | Page 4

5 Cherry Release projects update O-CU • Partial O-CU-CP functions – Random Access and Bearer Establishment • Integration of the source code of OCU-CP and OCU-UP SMO PTL elected (Mahesh Jethanandani, VMWARE) Project repo creation, LCM steps 2 and 3 development • LCM Step 2 - Package Validation (Cherry) • LCM Step 3 - Catalog Package (Cherry) RICAPP • Updated KPIMON x. App – (Samsung) • Traffic steering x. App dev continues – AT&T • To be demonstrated in MWC-LA O-DU • O-DU low – O-DU high pairwise testing • O-DU / O-RU emulator pairwise testing • Good progress in OSC lab INF • Introduce high availability (HA) for O-Cloud deployment [Cherry] Non-RT RIC • ONAP architecture alignment for SMO/Non-RT RIC [Cherry] • A 1 enrichment information gathering [Cherry] • R-APP platform API [Cherry] Near-RT RIC • Automation of health check end-2 -end call flow • O 1 mediator to handle restart gracefully • E 2 Term and E 2 Manager: Adapt to E 2 spec • Extend A 1 Mediator to expose Prometheus endpoint for publishing counters OAM • Support for O 1 interface compliance SIM • E 2 Simulator update • UE level & Cell level KPIs generated for Traffic Steering • KPI Data store for ML training DOC © 2020 AT&T Intellectual Property. AT&T, Globe logo, and DIRECTV are registered trademarks and service marks of AT&T Intellectual Property 2020 -06 -22 | Page 5 and/or AT&T affiliated companies. All other marks are the property of their respective owners.

Dawn Preliminary Epics

2020 -06 -22 | Page 7

8 Dawn Release epics RICAPP • Security x. App – Signaling. Storm (Samsung) • Traffic steering flowover (ATT, Viavi) • Anomaly Detection (HCL) • Load. Prediction (CMCC) O-CU • F 1, E 1, Ng messages being supported (Cherry/Dawn) • E 2 AP support, E 2 support for Handover (Dawn) • O 1 interface for O-CU (Dawn) O-DU • O-DU low – O-DU high pairwise testing • O-DU high health check - get alarm list (Cherry/Dawn) SMO • LCM Step 1 - Create Application Package (Dawn) • LCM Step 2 - Package Validation (Cherry) • LCM Step 3 - Catalog Package (Cherry) • LCM Step 4 - Create Config (Dawn) • r. APP Deployment Scenario (Dawn) • x. APP Deployment Scenario (Dawn) • Testing of Data Models using SMO • 3 GPP models • FH models ORAN © 2020 AT&T Intellectual Property. AT&T, Globe logo, and DIRECTV are registered trademarks and service marks of AT&T Intellectual Property 2020 -06 -22 | Page 8 and/or AT&T affiliated companies. All other marks are the property of their respective owners. INF • O 2 MVP (spec) • Enable INF from IA arch to ARM arch. Non-RT RIC • A 1 -EI • R 1 interface • r. App specific packaging/catalog/registration Near-RT RIC • SDK package • x. App Manager via O 2 • A 1 -EI support • x. App to request/discover available enrichment info • CII security badging - common platform req OAM • Support for O 1 interface compliance • Resolve copyright issues with 3 GPP also on O-RAN level (WG 1) SIM • E 2 Simulator update • Open data repo to store synthetic E 2 data

SMO 2020 -06 -22 | Page 9

SMO project update (Cherry) — Testing of data models using SMO — 3 GPP & FH — Test framework to be setup in OSC lab — Anybody with VPN access can bring their configuration for testing — Satisfies LCM Step 4 – Create config — LCM Step 2 – Package validation — Dependent on an App package schema definition — Specification will be driven in WG 1 — App package schema descriptor — Proposal to be discussed in this F 2 F — With input from WG 2 and WG 3 on requirements — Should be finalized by the end of F 2 F — LCM Step 3 – Package catalog — Dependent on LCM Step 2 — LCM Step 2 & 3 are at risk of missing the Cherry release 2020 -06 -22 | Page 10

SMO Project Plan (Dawn) — Spill over from Cherry — LCM Step 4 – Create Config — Config can be created and tested with framework developed in Cherry — MVP — r. App deployment scenario — x. App deployment scenario 2020 -06 -22 | Page 11

SMO Testing of Data Models • SMO is collaborating with OAM project to test and drive the data models being published for the O-RAN solution. • These models could come from 3 GPP or from O-RAN itself. The models themselves will reside in the NETCONF server, e. g. in the near RT RIC, O-CU-UP, O-CU-CP, O-DU and the O-RU and will be requested • by the NETCONF client, e. g. the SMO at the time the NETCONF session is established. Thereafter, an application like Postman can drive the north bound APIs exposed by the SMO. 2020 -06 -22 | Page 12

Non-RT RIC 2020 -06 -22 | Page 13

Non-RT RIC Project (Cherry) • ONAP architecture alignment for SMO/Non-RT RIC • A 1 Policy Management Service hosted in ONAP CCSDK (Done) • A 1 Policy Controller Adapter hosted in ONAP CCSDK (Done) • A 1 Simulator / test stub (SIM project) • A 1 Policy Control-Panel (PORTAL project) • Support A 1 -AP v 2. 0. (In progress) • A 1 enrichment information coordination • Implementation of the A 1 enrichment Information coordination service (In progress) • R-APP platform API • r. Apps • Very simple hello-world r. App platform (In progress) 2020 -06 -22 | Page 14

Non-RT RIC Project (Dawn) • A 1 Enrichment Information • First version of A 1 Enrichment Information coordination service • R-APP platform API • r. App support • Initial r. App catalogue/inventory 2020 -06 -22 | Page 15

OAM 2020 -06 -22 | Page 16

OAM Project (Cherry) Primary Goals: — update OAM projects for latest O-RAN Specifications — O-RAN Operations and Maintenance Architecture Version 3. 0 - April 2020 — O-RAN Operations and Maintenance O 1 Interface Version 3. 0 - April 2020 — O-RAN Use Cases Detailed Specification 2. 0 - April 2020 — O-RAN Management Plane Specification Version 3. 0 and YANG Models Version 3. 0 - April 2020 — Draft WG 1 O 1 YANG models implemented and tested against the SIM implementation - not published in LNF repositories 2020 -06 -22 | Page 17 — support of the application LCM use case — Discussion about the details together with the SMO project — handover SMO artifacts to new SMO project Feature Scope: — Switch to Java 11 — Switch to Open. Daylight version Sodium. SR 4 (O 1 termination Net. Conf) — https only support for VES-Collector (O 1 termination VES) — full IPv 6 support Please see OAM Cherry page for further details

OAM Project (Dawn) Primary Goals: — Analysis of modifications due to the “November 2020 Train” OAM specifications. — Deployment of virtual network functions (O -RAN components) from catalogs — Interfacing with Acumos project for OAM related ML and AI — Information exchange with Non-RT-RIC via a message bus — Abstraction of Software Management for different interfaces (O 1, O 2) Feature Scope: — Certificate and public key management — Update of JAVA artifacts addressing security issues — Switch to Open. Daylight version Aluminum Please see OAM Dawn page for further details 2020 -06 -22 | Page 18

SIM 2020 -06 -22 | Page 19

SIM Project (Cherry) • O 1 Simulator enhancements • Underlying NETCONF Server upgrade (In Progress) • E 2 Simulator enhancements • Support for new E 2 messages (Done) • RIC Benchmarking with E 2 Simulator (In progress) • Support SMO project in setting up a framework for testing YANG models • OTF Integration of E 2 Simulator (need to clarify if feasible in Cherry or moves to Dawn) 2020 -06 -22 | Page 20

SIM Project (Dawn) — O 1 Simulator enhancements (maintain alignment with new models etc. ) — E 2 Simulator enhancements (possibly more E 2 messages support) — OTF integration support (for O 1 or E 2) 2020 -06 -22 | Page 21

Traffic Steering x. Apps (O-RAN SC Cherry Release) or UE y n Query est f io equ ict UE metrics Cell metrics n. R ed 2020 -06 -22 | Page 22 Query tio list TS x. App Write KPIMON E 2 CONTROL E 2 KPI Sub E 2 Term E 2 Simulator RIC Viavi Sim Data lic dic • A 1 Med Po Pre QP x. App Pr TS x. App • Finds UEs of interest (based on A 1 -P) • Receives predictions from QP x. App • Issues control instructions to steer traffic • QP driver x. App • Fetches metric data for use by QP x. App for UEs of interest • QP x. App • Predicts future throughput for UEs and makes these available to TS x. App KPIMON populates cell and UE metrics into the Redis databases E 2 Simulator sends metrics based on Viavi data Data update A 1 Traffic steering is really a suite of interacting x. Apps: QP driver x. App

O-DU 2020 -06 -22 | Page 23

O-DU testing in OSC lab [Cherry] — O-DU Low (Intel) and O-DU High (Radisys) pairwise testing [Cherry] — MVP configuration check between O-RU, ODU and O-CU [Cherry] — Support from Radisys for O-CU binary — Support from Viavi for O-RU emulator and 5 G SA core 2020 -06 -22 | Page 24

RICAPP 2020 -06 -22 | Page 25

RICAPP project update (Cherry) Main development items: • (New x. App) KPIMON (Samsung): • Testing and integration with near. RT-RIC and E 2 Simulator making steady progress. • (Enhanced x. App) QP (Qo. E Predictor) (AT&T/HCL) with real ML model: • ML training underway with Viavi simulator output • Alarms and metrics (O 1 -PM/FM): • Implemented in QP-driver x. Apps, others underway. • (New x. App) AD (Anomaly Detection) x. App (HCL): • Training with simulated data underway. • Demo video for MWC-LA for the traffic steering use case including Viavi RAN simulator, E 2 SIM, KPIMON, QP-D, QP, and TS x. Apps in preparation. Meeting minutes available at the following pages: https: //wiki. o-ran-sc. org/display/RICAPP+Meetings 2020 -06 -22 | Page 26

RICAPP project plan (Dawn) • New x. Apps: • Signaling Storm Protection (SSP)(Samsung) – implements initial steps towards the WG-1 use case. • Load Prediction (LP) (CMCC) – ML-based x. App augmenting the TS use case. • Hello. World (go version) (Samsung) – demo of the RIC SDK using go • Traffic steering use case enhancements: • Add E 2 CONTROL message to TS x. App (based on WG-3 E 2 SM) • Enhanced A 1 Policy, enhanced TS logic • Update x. Apps to use latest RIC SDK • Code coverage and other requirements. 2020 -06 -22 | Page 27

Near-RT RIC 2020 -06 -22 | Page 28

Cherry – Near-RT RIC status • • • First contributions from HCL and Samsung coming, e. g. in context of automated source code quality scans, benchmarking, E 2 simulator (E 2 node side) and testing automation. Samsung working on RIC-95 (E 2 health check based on E 2 Service Query) x. App demo apps in Go and python started Four items moved out of Cherry as already visible that not enough time: link 28 Cherry items = 4 moved out of Cherry + 10 done + 14 in progress or still to be started Presentation on RIC and RICAPP status in the virtual ONe. S 2020 (link). • • • Waiting for copyright/licensing results between O-RAN and O-RAN SC. Work on O 1 -related functions, like E 2 and A 1 statistics, or some alarms already done REST interface for subscriptions (provided by subscription manager, used by x. Apps) still work in progress Subscription manager keeps its data persisten over its restart is still work in progress E 2 manager now supports “bug red button” case with “close all E 2 connections” and “do not allow new E 2 connections” • Dropped from Cherry original plans: see next slide • 2020 -06 -22 | Page 29

Dawn – near-RT RIC candidates • • Adaptation to E 2 APv 1. 1 (likely released in November) only happening post-Cherry. • Dynamic scalability and failover • Exposing E 2 Node Configuration Update • E 2 SM OID support in internal E 2 SM function query interfaces SDK package, well documented interfaces to be used by x. Apps via x. App frameworks Extension in SDL support (all three languages (C++, go, python) A 1 -EI support (pending a stable or published specification) x. App to request/discover available enrichment info (pending a stable or published specification) CII security badging - common platform req • we might be aiming for self-certification under LF's CII badge level "basic", Updated LCM for x. App where x. Apps register with the platform as part of their startup. Dropped from Cherry original plans: • RIC-585 alarm for E 2 connection status change (remains only a RIC-internal event) • RIC-421 O 1 mediator graceful restart with O 1 data being persisted over restarts • RIC-114 time series database support • RIC-48 further studies on message bus options (NATS or other brokerless). g. RPC analysed, but not promising • RIC-203 Alarm for routing table update delays 2020 -06 -22 | Page 30

Near-RT RIC implementation 2020 -06 -22 | Page 31 Alarm Adapter Alarm library Anomaly. Detection x. App RIC x. App framework KPIMON x. App RIC x. App framework ASN. 1 Redis RAN RNIB Prometheus exporters VES Agent / VESPA Prometheus RIC x. App framework Traffic steering x. App RAN, i. e. g. NB/e. NB Routing Manager Various Extras (Nokia) RIC x. App framework REST E 2 Manager RIC Measurement campaign x. App REST Net conf REST Subscription Manager REST x. App and Config Manager A 1 Mediator O 1 Mediator RMR library Research data lake Helm charts REST API Gateway (Kong) A 1 REST O 1 O 2 (LCM) Auxiliary REC with ONAP-based GUI Image repo Redis x. App DBs (e. g. , UE RNIB) Trace&log Logging & Open. Tracing E 2 Termination Redis SDL + R-NIB API RIC x. App Framework (one per C++, Golang, Python) Akraino REC (Radio Edge Cloud) or other E 2

O-CU 2020 -06 -22 | Page 32

O-CU Release C Schedule and Progress • Contributed in Release B: O-CU-UP source code. • Plan for Release C: • part of O-CU-CP functions – Random Access and Bearer Establishment • demonstrate the packet filling function • Integrate the source code of OCU-CP and OCU-UP Finished functions for Release C: Functions Related F 1, Ng messages Random Access • • • INITIAL UL RRC MESSAGE TRANSFER DL RRC MESSAGE TRANSFER UL RRC MESSAGE TRANSFER Developing functions for Release C: Functions Bearer Establishment • • • Initial UE Message Initial Context Steup Request UE CONTEXT SETUP REQUEST UE CONTEXT SETUP RESPONSE BEARER CONTEXT SETUP REQUEST BEARER CONTEXT SETUP RESPONSE DL RRC MESSAGE TRANSFER Initial Context Setup Response UL RRC MESSAGE TRANSFER Up. Link NAS Transport Integration • Integration CP and UP source code Other requirements for Release C but no contributors now: Functions E 2 • • Support E 2 AP Support E 2 SM-KPM for traffic steering user cases Handover • Support Handover for traffic steering user cases O 1 • Support O 1 interface for O-CU CP/DU 2020 -06 -22 | Page 33 Related F 1, E 1, Ng messages

INF 2020 -06 -22 | Page 34

Infrastructure (INF) project update (Cherry) — Enable the 2 servers deployment scenario (AIO duplex) Done — 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. — Interoperability with O-DU Ongoing — OSC lab All the information is available at the following pages: https: //wiki. o-ran-sc. org/display/IN/INF+project+meetings https: //wiki. o-ran-sc. org/display/IN/INF+project+status 2020 -06 -22 | Page 35

Infrastructure (INF) project plan (Dawn) — Enable INF from IA arch to ARM arch. — O 2 interface for SMO to call MVP 2020 -06 -22 | Page 36

O 2 Proposal — Requires Initial Config as part of Config. Map — SMO receives YANG to build initial Config from onboarding — x. APP provides YANG and initial config to near-RT RIC as part of step 2 and 3 2020 -06 -22 | Page 37 37

Accepted Procedure based on Ericsson Proposal — https: //oranalliance. atlassian. net/wik i/download/attachments/106397773 /ERI. AO-2020. 08. 24 -WG 6 -CR-0003 Orchestration. Use. Casesv 02. docx? api=v 2 2020 -06 -22 | Page 38 38

ONAP / O-RAN alignment 1. 2. 3. 4. 5. 6. 7. Strategy to Downstream Non-RT RIC components into ONAP as an Add-on to ONAP SMO O 2 Cloud. Inventory APIs; Note this is just the first defined by the O 2 development others may follow. Cloud. Region to Location 1: 1 in ONAP; 1: * in O-RAN. Application LCM CI/CD in ONAP; Onboarding in O-RAN Need to Push for Config. DB capability; Has previously been low priority in O-RAN A 1 -EI support in the A 1 Adapter Continued evolution of Dynamic Data Collection (DDC) 2020 -06 -22 | Page 39 39

RSAC concerns • General lack of multi-company participation in projects • Single company projects plague OSC across most projects O-CU • O-CU is central to completing the O-RAN Stack • O-CU E 2 support is central to completing O-RAN Use Cases • To date we have: • Monolithic e. Node. B (for NSA approach) • O-CU seed code: Incomplete O-CU functionality • Unknown state of O-CU seed code for another company to resume work INT • Need volunteers to drive end-to-end integration or CI/CD tooling development 2020 -06 -22 | Page 40