ONAP3 GPP ORAN Alignment use case ONAP Frankfurt

ONAP/3 GPP & ORAN Alignment use case ONAP Frankfurt 5 G use case September, 2019 AT&T, Nokia Sensitivity: Internal & Restricted

O-RAN Target Architecture for Disaggregated Radio Network Inventory Design Orchestration RAN Analytics, model training & control (RIC non-RT) Configuration Policy O 1 Orchestration & Automation (e. g. ONAP/MANO), NMS A 1 O 1 A 1: RAN Intelligent Controller (RIC) near -RT E 2 Applications Layer VNF Mgmt 3 rd party APP Radio Connection Mgmt Interference Mgmt Qo. S Mgmt. Mobility Mgmt Trained Model Modular CU SW Radio-Network Information Base E 2 Multi-RAT CU Protocol Stack VIM CU-CP RRC PDCP-C 3 GPP E 1 CU-UP SDAP PDCP-U NFVI Platform: Virtualization layer and COTS platform CU HW 3 GPP F 1 RAN DU: RLC/MAC/PHY-high NGFI-I Sensitivity: Internal & Restricted RAN RRU: PHY-low/RF 2

Use case 1: Onboarding SDNC with A 1 adaptor Design time 2 Compose BP CDS 1 Get model 3 Store CBA file SDC • Impact 4 Publish CBA file Controller blueprint u. Service Model for A 1 adaptor and DMaa. P agent Blueprint processor platform SDNC(-R) DMaa. P agent for A 1 adaptor Module requiring development Run time 5 Send self service request SO A 1 adaptor - SDNC(-R) need to have A 1 adaptor and corresponding N/B interface (e. g. DMaa. P) - CDS need to be able to configure SDNC(-R) with such required components • Question - To publish BP and request self service, do we need SDC / SO? Or can we do with CDS only? Sensitivity: Internal & Restricted 3

Use case 2: Creating and sending A 1 policy OSC (O-RAN software community) code 1 Compose A 1 policy RIC dashboard • Impact A 1 mediator 2 Send A 1 policy 3 Send A 1 policy Blueprint processor platform SDNC(-R) DMaa. P agent for A 1 adaptor - SDNC (-R) need to have A 1 adaptor implemented - RIC dashboard currently communicates with A 1 mediator. With this use case, RIC dashboard need to talk to SDNC - A 1 mediator need to align with O-RAN WG 2 spec • Discussion - RIC dashboard can be replaced by VID GUI? Sensitivity: Internal & Restricted 4

Use case 3: conflict resolution of O 1 and A 1 (possibly for later release) Policy Request conflict resolution Request decision DCAE CLC DMaa. P SDNC(-R) VES collector Collected data Analytic u. S Generic DMaa. P agent for Netconf/Yang DMaa. P agent for A 1 adaptor Netconf module A 1 adaptor O 1 -CM O 1 -PM A 1 • Impact - Whole closed loop need to be built (analytic u. S, policy, CLC, SDNC) Sensitivity: Internal & Restricted 5

Use case 4: Storing A 1 policy OSC (O-RAN software community) code config. DB 1 Compose A 1 policy RIC dashboard 2 Store A 1 policy store A 1 Policy model • Impact - RIC dashboard currently stores A 1 policy internally. With this use case, RIC dashboard need to communicates with config. DB - Config. DB needs to have relevant schema? • Further follow-up use cases might be needed (e. g. management of A 1 policy, etc. ) Sensitivity: Internal & Restricted 6

Next steps • Decide which use cases to pursue for Frankfurt • Talk to each component’s PTL • Create JIRA tickets Sensitivity: Internal & Restricted 7

Contacts & resources • SDNC(-R) – Dan Timoney/Martin Skorupski • CDS – Yuriy Malakov • Config DB – Joanne Liu-Rudel • Non. RTRIC in OSC – John Keeney • RIC dashboard in OSC – Christopher Lott - https: //gerrit. o-ran-sc. org/r/portal/ric-dashboard; a=summary • A 1 mediator in OSC – Tommy Carpenter - https: //gerrit. o-ran-sc. org/r/admin/repos/ric-plt/a 1 • A 1 Modeling – Kevin Skaggs - https: //oranalliance. atlassian. net/wiki/spaces/UCOA/pages/182616067/Informa tion+Model+Contributions Sensitivity: Internal & Restricted 8

s Thank You! Sensitivity: Internal & Restricted

O-RAN O 1 & A 1 Specifications: • O-RAN Alliance has defined OA&M specifications (called O 1) for disaggregated Radio Access Network. - It leverages 3 GPP as much as possible Specifications are management frame neutral It covers FCAP functions (Fault, Configuration, Performance, etc. ) O 1 specifications also cover software upgrade • O-RAN also introduce a new interface called A 1. - A 1 interface is an open logical interface between non-RT RIC functionality in the Orchestration/management platform and near-RT RIC functionality in RAN of O-RAN architecture. - A 1 interface should enable a multi-vendor environment, and is independent of specific implementation of the Orchestration/management platform, non-RT RIC, and near-RT RIC. - A 1 interface should enable policy-based guidance of radio resource management and control functions or applications that are internal to the near-RT RIC. Sensitivity: Internal & Restricted

OA&M Architecture for Disaggregated RAN Service Management & Orchestration (e. g. ONAP) Non-Real Time RIC A 1 O 1* Infrastructure Management Framework Near-Real Time RAN Intelligent Controller (RIC) E 2 O-CU-CP E 1 O-CU-UP O 1 O 1 F 1 -c F 1 -u O-DU O 1 Open Fronthaul Interface VIM O-RU ~Nf. Vi O 1 Infrastructure – COTS / White Box / Peripheral Hardware & Virtualization layer Virt Sensitivity: Internal & Restricted Whitebox H/W 11

ONAP/3 GPP & O-RAN Alignment Work • Provisioning Management - Three New CM VES notifications notify. MOICreation, notify. MOIDeletion, notify. MOIAttribute. Value. Change. • Fault Supervision - Align existing VES fault event or create new VES fault 3 gpp event to support harmonization work in TS 28. 532. • Performance Assurance/File Management - Modify the change. Identifier field name of the file. Ready event to filetype indicating the type of file that is ready for upload (call trace, log, certificate, beamforming etc. ) or add a new field file. Type for this purpose Sensitivity: Internal & Restricted

ONAP/3 GPP & O-RAN Alignment Work • PNF Registration - ONAP modifications to support the addressing of MEs behind a NAT - Potential modification of pnf. Registration event when 3 GPP completes harmonization activity. • PNF SW Management - Ensure O-RAN PNF Software Management can be supported in ONAP • O 1 PNF Software Management specifies the order, behavior, input and output for each step. • O-RAN needs ONAP to support workflow order, events, and steps specified in the O 1. • Order and behavior of steps is different in ONAP proposals in Frankfurt; e. g. pre-check, update AAI, post-check. - Definition of additional Notifications (VES events) • reset. Reason Notification • software. Activate Notification • download. File Notification Sensitivity: Internal & Restricted

ONAP/3 GPP & O-RAN Alignment Work • A 1 Interface introduction - A 1 interface between Non-Real Time RIC and the Near Real Time RIC to transmit Policy and optimization information to the Near Real Time RIC and carry responses (e. g. policy applied, couldn’t be applied etc) - A 1 interface to be defined by WG 2 in O-RAN in September. - Evaluation of impact to follow Sensitivity: Internal & Restricted

Status • Evaluating Project impacts for the work items • Prioritizing work items to be addressed in Frankfurt Sensitivity: Internal & Restricted

Goals for Frankfurt • A 1 Interface Introduction • Fault Assurance alignment of fault event to fault 3 gpp • file. Ready field name change or the addition of a new field to specify the file. Type. • CM notification events defined in VES, supported in DCAE and DMaa. P Sensitivity: Internal & Restricted

Controller Design Studio Data Flow 1 B. Jenkins Builds and Deploy to Maven Repo GIT 1 A. User registers Model Types, & Reusable Dictionaries 1 C. Auto load Model Types, & Reusable Dictionaries MAVEN 2 B. Enrich, Validate CBA file 2 A. User create CBA file Dmaa. P CBA Listener 2 D. Test CBA file 2 C. Test Deploy CBA file SDC 3 B. Publish CBA file 4 A. Send Self Service Request 4 H. Consume Self Service Response 4 F. Return Self Service Response DMaa. P 4 G. Publish Self Service Response 3 D. Persist CBA file 3 C. Consume CBA file Self Service Rest / GRPC API DMaa. P CB DB Blueprint Processor Platform Controller Design Studio 3 A. Store CBA file SO Controller Blueprints Microservice 1 D. Store Model Types, & Reusable Dictionaries Dmaa. P Publisher Sensitivity: Internal & Restricted 4 B. Retrieve CBA file BP MS Groovy Executor Component Ansible Executor Component Resource Resolution Component Netconf Executor Component Python Executor Component Restconf Executor Component 4 C. Execute CBA Directed Graph Executor 4 D. Execute CBA Components Component Executor