Driving RAN Intelligent Control with Akraino Oliver Spatscheck

  • Slides: 8
Download presentation
Driving RAN Intelligent Control with Akraino Oliver Spatscheck Don Fendrick

Driving RAN Intelligent Control with Akraino Oliver Spatscheck Don Fendrick

What is the RIC? Objective: customize RAN functionality for regional resource optimization or new

What is the RIC? Objective: customize RAN functionality for regional resource optimization or new services Policy ML Analytics App App RIC platform External data sources/lakes RAN control plane offload Region 1 e. NB E 2 protocol Multi vendor RAN optimization/customization apps App App RIC platform Region 2 g. NB What? Area-wide data and controls Why? Customize RAN with short time-to-market for: q UE/cell/DU/CU level L 1/L 2/L 3 measurements v Efficient resource usage – improve customer experience and optimize spectral efficiency by using policies/ML to tailor RAN for unique spectrum position and geography based on holistic area-wide network view q UE locations and predicted trajectory q UE context info(video, voice, non-GBR data) q Per-UE policy-driven control of band/cell/bearer selection, admission control, handover, scheduler v New RAN services – customize RAN behavior for the needs of specific verticals. E. g. , create RAN slices for drones, connected cars, Io. T, etc.

RAN Intelligent Controller – a new function introduced by O-RAN Latency for Control Use

RAN Intelligent Controller – a new function introduced by O-RAN Latency for Control Use cases AI Wireless Domain Management >> 1 s A 1 AI RAN Intelligent Controller (RIC) 10 -100 ms Qo. S optimization Slicing optimization Mobility optimization Real-time RAN CU-CP DU 3 GPP E 1 ORAN NGF-I CU-UP RRU RAN Intelligent Controller Network Intelligenc e Policy Enforcement Handover Optimisation Resource Assurance Radio-Link Management Resource Control Load Balancing 3 rd Party application RAN Data Analytics & AI Platform E 2 O 1 Advanced SON Slicing Policy - AI/ML for Programmability - Platform made avail in Open Source - A 1: intent based interface E 2: RAN closed loop O 1: for data collection and control

Why RIC? The RIC takes customization into the RAN Network Optimization • Fine grain

Why RIC? The RIC takes customization into the RAN Network Optimization • Fine grain network optimization customized for each environment Smart factory/industrial Io. T • • Carve out private 5 G slice/namespace for business customer on industrial campus Security services Connected Car • Quality of Service enforcement to provide low latency and/or high bandwidth to vehicle applications Shipping, Logistics, Tracking, Asset Management • Lowering power of Io. T devices to enhance battery life Health Care • Enforce highest level of network security for sensitive medical data 4

AT&T & Nokia are driving ORAN/RIC/Akraino in a co-creation partnership welcoming community engagement. A

AT&T & Nokia are driving ORAN/RIC/Akraino in a co-creation partnership welcoming community engagement. A 1 -C Nokia and AT&T Open. Source Co-create Future Community contribution AT&T independent development Nokia Applications AT&T Applications 3 rd party Applications Open Source RIC Platform E 2 Nokia 5 G RAN Nokia independent commercial development 3 rd party RAN Open Source CI/CD Strategic Importance: Akraino is Edge Solution blueprint reusable for Telco, Enterprise and Io. T Use cases Akraino Edge Middleware, SDKs and apps enable 3 rd party ecosystem play

Driving success in the radio edge through a “cloud appliance” approach Challenge: individual workloads

Driving success in the radio edge through a “cloud appliance” approach Challenge: individual workloads drive far edge cloud business cases leading to platform bootstrap problem. Strategy: “Cloud appliances” allow an edge cloud to be built up incrementally one workload at a time. Package each workload like an appliance, but allowing reuse of common cloud tooling and centralized management. O-RAN radio edge workloads Dashboard O 1 RIC v. CU Orchestration Regional edge cloud manager Dashboard RIC ”cloud appliance” O 1 v. CU v. BBU Integrator Node and workload LCM tooling v. BBU “cloud appliance” … Virt OS OS OSHW HW HW Radio edge cloud node (REC) Nodes scaled to individual workload Other workloads MEC, Cache, Video, Gaming ….

Join us now! • RIC code released as part of O-RAN LF project •

Join us now! • RIC code released as part of O-RAN LF project • REC code released as part of Akraino • Join now! Public