O-RAN Open Source Community (OSC)

Programming tomorrow’s 5G networks today

The anatomy of a flexible RAN Intelligent Controller (RIC) and its applications

Rittwik Jana
AT&T Labs Research
rjana@research.att.com
2020-06-22 | Page 1
Agenda
 Overview of OSC

 OSC releases and features

 AI/ML use cases in OSC

2020-06-22 | Page 2
O-RAN SC wiki – wiki.o-ran-sc.org

2020-06-22 | Page 3
ORAN-SC Workflow Request to resolve standard/OSC variance
in cases where code diverges from spec
Test specs
TOC prioritizes and TIFG
negotiates with O-RAN Recommended spec/design
on behalf of OSC TOC features for inclusion in
S/W committee selects Req. Comm. (RSAC)
particular release WG1
requests from WG1
based on available - Define O-RAN end-to-end priority use case/MVP
Release planning -
resources and timelines Select/recommend features from each WG
to be included in a particular use case
OSC - Coordinate between WGs to ensure
Pre-standards AAL required specs are available by certain date
development and O-DU
code contributions Design/
spec O-CU O-RAN
O-RAN xApps CU, DU, RUWG
RIC 7,8
OS Wiki VIM, NMS
Sim O-RAN WG software
WG 5,6
RIC O-RAN Specs/
releases to O-RAN for WG 3,4 Architecture/
testing end-to-end use cases
WG 1,2 Reference design
Use Contribute

WG contributions from O-RAN

members (non OSC)
Engage other
open source
communities

2020-06-22 | Page 4
OSC Projects and Structure
Technical Operating Committee (TOC) Company Name Alternate

Requirements & Software Arch. Committee (RSAC) AT&T Jack Murray Co-
Chair
Projects China Mobile Jinri Huang Co-Chair Weichen Ni
Deutsche Telekom  David Streibl Ondřej Hudousek
Non-real-time RIC (A1 Interface) (NONRTRIC) Ericsson John-Paul Lane John Keeney
Near real-time RIC Platform (E2 Interface) (RICP) NTT DOCOMO Masafumi Masuda Anil Umesh
Near Real-time RIC X-APPs (RICAPP) Nokia Juha Oravainen Thoralf Czichy
OAM (O-1 Interface) Orange William Diego Vincent Danno
O-RAN Central Unit (OCU) Radisys Ganesh Sachin Srivastava
Shenbagaraman
O-DU High
Verizon Viswanath Kumar Kristen Young
O-DU Low Skand Priya
Simulation (SIM)
Infrastructure (INF)
Integration and Test (INT)
Documentation (DOC)
Service Mgmt. and Orchestration (SMO)

AT&T Proprietary (Restricted)

2020-06-22 | Page 5 Only for use by authorized individuals or any above-designated team(s) within the AT&T
companies and not for general distribution
OSC Project PTLs

2020-06-22 | Page 6
OSC status

2020-06-22 | Page 7
Control loops in O-RAN Training
Cache

SMO
Legend
3rd Party Apps RAN Intelligent
O-RAN / xRAN Defined Interfaces at the edge Design Inventory Policy Configuration Controller
**To be standardized by SDO non-RT RIC
3GPP Defined Interfaces
A1
5G RAN Loop 3: > 0.5 sec
RAN Intelligent Controller, near-RT RIC
(policies, orchestration,
Application Layer SON)
3rd Party App Radio Connection Mgt. Mobility Mgt. Radio Network
Loop 1: per TTI/ QoS Mgt. Interference Mgt. Trained Model Information
msec resource Base
scheduling Data Distribution Bus API
Data from eNB Plug-in/
E2 (PM/FM) Mediator
DU: F1 CU-CP RRC CU-UP SDAP
RRU: E2
RLC/MAC/
PHY-low/ RF PDCP-C E1 PDCP-U
PHY-high
Standard / Open HW Design NFVI Platform: Virtualization Layer and COTS Platform

Loop 2: 10 – 500
msecs (resource
eNB optimization)
eNB

Cell Sites Edge Cloud Central Cloud

2020-06-22 |Presentation
Page 8 title / Month XX, 2020 / © 2020 AT&T Intellectual Property - AT&T Proprietary (Internal Use Only)
ML workflow
Deploy
2 Untrained
Model
Service Package
ML Modeler Data 6 model, set
Training
Training Broker - Designer policies
ML Model
Design Cache DB
Data ML
1 Model Catalog Broker
Model
ML Designer Trained
Runner
4 Upload Trained Non-RT RIC Model
DMaaP
Model
ML Training Hosts* ML models (loop 3)
(Train & Retrain Models) ML model Docker
Catalog Image
Design File
Studio 5

Publish to O1 (CM, deploy models)

Non-RT RIC A1 (policies for models)
ML models (loop 1)
Download to
ML models (loop 2) 5G
7 RIC, O-DU,
O-RU Base Stations
O1 (FM, PM)
RIC
8
E2
Collect

3 O-CU-CP O-CU-UP O-DU O-RU

Mid Haul Open Front
* ML Training host can be part of non-RT RIC or can executed offline Haul

Select Training
Data Lake Real Time Data
Data
Collector
O1 (PM data to ML training host)

2020-06-22 | Page 9
OSC End-to-end control loop use case: Traffic Steering
Non-RT
RIC

QOE-PRED-REQ Closed loop control

A1 POLICY
QP driver QP
xApp xApp

UE
QOE-PREDICTION • ML based Traffic Steering algorithm
-L
IS
T
• ML model trained and loaded in QoE predictor
TS xApp
cell UE (Traffic • Initial POLICY from non-RT RIC
metrics metrics Steering)

• Measurement data collected from E2 nodes

E2 CONTROL
KPIMON “HO UE”
xApp • QoE prediction and Traffic Steering analytics in near-RT RIC

E2Term • CONTROL action to E2 node to handoff user from Cell A to Cell B’

E2 REPORTS Near-RT RIC
• Multi-vendor example
CU- CU-
DU UP CP
• OSC Cherry Release (Dec 2020)
• https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20876303

2020-06-22 | Page 10
AT&T demonstrates Open Interface Trial

AT&T currently conducting multiple innovative trials with vendor

partners

Addressing UE specific differentiation via

A1 – Policy guided QoS nudging use case
E2 – Advanced Traffic Steering use case

O1, O2 – Life cycle management of rApps and xApps using SMO

2020-06-22 | Page 11
Bronze release (June 2020)
O-RAN SC Bronze Release Summary
Code Contributed: Over 3 million lines of Code
 
Contributors: Individual Authors 67; Commits 1,432; Repos 40

Companies- AT&T, Radisys Corporation, Intel Corporation, Nokia

Corporation, Ericsson AB, Wind River, Highstreet Technologies,
Commscope, Institute of Computing Technologies, Nordix, Samsung,
HCL, Linux Foundation
 
Interfaces: A1, O1, E2, FAPI, TR-69

Test Cases

Getting Started Guide

https://wiki.o-ran-sc.org/pages/viewpage.action?
pageId=20874827

Software Developers Kit (SDK)

https://wiki.o-ran-sc.org/display/ORANSDK/O-
RAN+Application+SDK
2020-06-22 | Page 13
O-RAN SC Bronze Metrics
Linux Foundation Analytics OSC Lines of Code changed
https://lfanalytics.io/projects/o-ran

AT&T 1378725
Radisys Corporation 528749
Intel Corporation 475765
Nokia Corporation 393275
Ericsson AB 126859
Wind River 120494
Highstreet Technologies 98607
AT&T
Comscope 45663 Radisys Corporation
Institute of Computing 20432 Intel Corporation
Technologies, Chinese Nokia Corporation
Ericsson AB
Academy of Sciences Wind River
Nordix 2586 Highstreet Technologies
Comscope
China Mobile 311 Institute of Computing Technologies, Chinese Academy of Sciences
Nordix
China Mobile

2020-06-22 | Page 14
O-RAN SC Bronze Testing Framework

Relationship between OSC projects

Deployment of OSC in the OSC Integration and Testing lab
and O-RAN architecture components

2020-06-22 | Page 15
Cherry release update
2020-06-22 | Page 17
Cherry Release projects update
O-CU INF
• Partial O-CU-CP functions – Random Access and Bearer Establishment • Introduce high availability (HA) for O-Cloud deployment [Cherry]
• Integration of the source code of OCU-CP and OCU-UP
Non-RT RIC
• ONAP architecture alignment for SMO/Non-RT RIC [Cherry]
SMO • A1 enrichment information gathering [Cherry]
PTL elected (Mahesh Jethanandani, VMWARE) • R-APP platform API [Cherry]
Project repo creation, LCM steps 2 and 3 development
• Near-RT RIC
LCM Step 2 - Package Validation (Cherry)
• Automation of health check end-2-end call flow
• LCM Step 3 - Catalog Package (Cherry) • O1 mediator to handle restart gracefully
• E2Term and E2Manager: Adapt to E2 spec
RICAPP • Extend A1 Mediator to expose Prometheus endpoint for
• Updated KPIMON xApp – (Samsung) publishing counters
• Traffic steering xApp dev continues – AT&T
OAM
• To be demonstrated in MWC-LA
• Support for O1 interface compliance

O-DU SIM
• O-DU low – O-DU high pairwise testing • E2 Simulator update
• O-DU / O-RU emulator pairwise testing • UE level & Cell level KPIs generated for Traffic Steering
• KPI Data store for ML training
• Good progress in OSC lab
DOC
© 2020 AT&T Intellectual Property. AT&T, Globe logo, and DIRECTV are registered trademarks and service marks of
2020-06-22 | PageProperty
AT&T Intellectual 18 and/or AT&T affiliated companies. All other marks are the property of their respective owners.
D Preliminary Epics
2020-06-22 | Page 20
 D Release epics
RICAPP
INF
• rApp/xApp SDK – create application package
• LCM Step 1 - Create Application Package(Dawn)
• O2 MVP (spec)
• Security xApp – SignalingStorm (Samsung) • Enable INF support for ARM arch.
• Traffic steering flowover (ATT, Viavi)
• Anomaly Detection (HCL) Non-RT RIC
• LoadPrediction (CMCC)
• A1-EI
O-CU • R1 interface
• F1, E1, Ng messages being supported (Cherry/Dawn) • rApp specific packaging/catalog/registration
• E2AP support, E2 support for Handover (Dawn)
• O1 interface for O-CU (Dawn)
Near-RT RIC
O-DU
• SDK package
• O-DU low – O-DU high pairwise testing • xApp Manager via O2
• O-DU high health check - get alarm list (Cherry/Dawn) • A1-EI support
• Test setup, reset,start,stop using Netconf • xApp to request/discover available enrichment info
O-RU
• CII security badging - common platform req
— Failure detection and recovery use case
OAM
• Support for O1 interface compliance
SMO
• Model validation and feedback
• LCM Step 2 - Package Validation (Cherry)
• LCM Step 3 - Catalog Package (Cherry)
• Resolve copyright issues with 3GPP also on O-RAN level (WG1)
• LCM Step 4 - Create Config (Dawn)
• rAPP Deployment Scenario  (Dawn) SIM
• xAPP Deployment Scenario (Dawn) • E2 Simulator update
• Testing of Data Models using SMO
• 3GPP models
• Open data repo to store synthetic E2 data
• FH models ORAN
© 2020 AT&T Intellectual Property. AT&T, Globe logo, and DIRECTV are registered trademarks and service marks of
2020-06-22 | PageProperty
AT&T Intellectual 21 and/or AT&T affiliated companies. All other marks are the property of their respective owners.
SMO

2020-06-22 | Page 22
SMO project update (C release)
— Testing of data models using SMO
— 3GPP & 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 WG1
— App package schema descriptor
— Proposal to be discussed in this F2F
— With input from WG2 and WG3 on requirements
— Should be finalized by the end of F2F
— 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 23
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
— rApp deployment scenario
— xApp deployment scenario

— Event Capturing
— VES Fault events
— Decouple VES from Dmaap: Develop VES northbound adaptor to SMO data bus (Kafka, RabbitMQ, db
log)

2020-06-22 | Page 24
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 3GPP 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 25
Non-RT RIC

2020-06-22 | Page 26
 NRT-RIC Project (Cherry)
• ONAP architecture alignment for SMO/Non-RT RIC
• A1 Policy Management Service hosted in ONAP CCSDK (Done)
• A1 Policy Controller Adapter hosted in ONAP CCSDK (Done)
• A1 Simulator / test stub (SIM project)
• A1 Policy Control-Panel (PORTAL project)
• Support A1-AP v2.0. (In progress)

• A1 enrichment information coordination

• Implementation of the A1 enrichment Information coordination service (In progress)

• R-APP platform API

• rApps
• Very simple hello-world rApp platform (In progress)

2020-06-22 | Page 27
NRT-RIC (Dawn)
− C release completed
A1 Policy as part of A1-AP v02.00
 ONAP alignment with Guilin completed - ongoing maintenance and evolution for next releases
A1 EI (Enrichment Information) coordination function is ready for use
rApp modeling and packaging
 Initial implementation of inventory, modeling and packaging (aligned with ONAP)
R1 implementation –hosted in Non-RT-RIC project and send requirements to SMO project

− D release
 Initial rApp framework and R1 interface (strong alignment with ONAP)
 Requirements for A1 AI/ML implementation
 Initial requirements towards SMO project for following functions:
 Data management, common models for O1, topology/inventory and xApp management
 New end-to-end use case ‘O-RU failure detection and recovery’ is proposed
 Ericsson is considering an rApp (to exercise O1) for this use case
 ONAP Honolulu execution phase (Align with OSC Dawn requirements)

2020-06-22 | Page 28
OAM

2020-06-22 | Page 29
OAM Project (Cherry)
Primary Goals:
— update OAM projects for latest O-RAN — support of the application LCM use case
Specifications — Discussion about the details together with
— O-RAN Operations and Maintenance the SMO project
Architecture Version 3.0 - April 2020 — handover SMO artifacts to new SMO project
(preparation for O-eNB support)

— O-RAN Operations and Maintenance

Interface Version 3.0 - April 2020 Feature Scope:
(support of fileReady event and 3GPP-PM-xml file upload and parsing — Switch to Java11
and translation into VES domain “perf3gpp”)
— Switch to OpenDaylight version Sodium-SR4
— O-RAN Use Cases Detailed Specification
(O1 termination NetConf)
2.0 - April 2020
— https only support for VES-Collector (O1
— O-RAN Management Plane Specification
termination VES)
Version 3.0 and YANG Models Version
3.0 - April 2020 — full IPv6 support
— Draft WG1 O1 yang models implemented and
tested against the SIM implementation - not Please see OAM Cherry page for further details
published in LNF repositories
2020-06-22 | Page 30
OAM Project (Dawn)
Primary Goals: Feature Scope:
— Analysis of modifications due to the — Certificate and public key management
“November 2020 Train” OAM specifications. — Update of JAVA artifacts addressing security
— Deployment of virtual network functions (O- issues
RAN components) from catalogs — Switch to OpenDaylight version Aluminum
— 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 (O1, O2)

Please see OAM Dawn page for further details

2020-06-22 | Page 31
SIM

2020-06-22 | Page 32
 SIM Project (Cherry)
— O1 Simulator enhancements
— Underlying NETCONF Server upgrade (In Progress)
— E2 Simulator enhancements
— Support for new E2 messages: ServiceQuery, ServiceUpdate (Done)
— RIC Benchmarking with E2 Simulator (In progress)
— E2 Simulator: replaying KPIs for Traffic Steering Use Case (to be demoed in MWC-LA)
— Support SMO project in setting up a framework for testing YANG models
— OTF Integration of E2 Simulator (need to clarify if feasible in Cherry or moves to Dawn)
O1 NETCONF/YANG
interface
NETCONF/YANG
Interface for controlling the simulation Simulated
spawns network
function
O1
Simulator … O1 NETCONF/YANG
interface
Manager
Simulated
network docker
function container

2020-06-22 | Page 33
SIM Project (Dawn)
— O1 Simulator enhancements (maintain alignment with new models etc.)
— E2 Simulator enhancements (possibly more E2 messages support)
— OTF integration support (for O1 or E2)

2020-06-22 | Page 34
Traffic Steering xApps (O-RAN SC Cherry Release)
QP driver Data update QP
Traffic steering is really a suite of interacting xApp
A1Med
xApp
xApps: Pre
• TS xApp dic
tion

Pr
• Finds UEs of interest (based on A1-P) Re

ed
que

y
Query

c
ict
s

oli
• Receives predictions from QP xApp t fo

io
rU

P
n
• Issues control instructions to steer traffic El

A1
ist
• QP driver xApp
Query
• Fetches metric data for use by QP xApp Cell UE TS xApp
for UEs of interest metrics metrics
• QP xApp Write
• Predicts future throughput for UEs and
makes these available to TS xApp KPIMON
E2 CONTROL
KPIMON populates cell and UE metrics into the
Redis databases
E2 Simulator sends metrics based on Viavi data E2 KPI Sub
E2Term Near-RT RIC

E2 Simulator Viavi Sim Data

2020-06-22 | Page 35
OTF and O-RAN

2020-06-22 | Page 36
O-RU

2020-06-22 | Page 37
Close Loop Automation (Proposed)
6 Link 5b Integration/OTF
Non-RT RIC Monitor 1
Test Strategy MB VTH
SMO
DMaaP
OA
5a 11
M VES
NETCONF
Collector Assumptions
1. O-RU was managed asynchronously with O-DU by M-
Near-Real-Time RAN Intelligent Controller Plane or O1
2. O-RU link down indicates link down through M-Plane
or O1
3. Link Monitor App could be SMO or Non-RT RIC; not
O-CU-CP embedded is VES collector.
4. OTF can collect, log, compare DMaaP messages to to
E2 E1
7 validate success.
O1
O-CU-UP Preconditions
1. Devices are deployed and configured for Closed Loop
flows
F1-c 10
F1-u Flow
1,7, 8. OTF requests OAM NETCONF to configure O-DU High to turn off
O-DU High Link simulating a failure event. O-DU High send stop.request to stop O-DU
low
8 4. O-RU detects unexpected link state change and issues VES alert.
5. OTF sees failure and begins to search for clear. NRT-RIC sees failure event
O-DU Low 4 6, 2. NRT-RIC issues re-active O-RU
6, 7, 8. NRT-RIC issues config change to set link to active, O-DU High send
Open Fronthaul
2 start.request to O-DU low
10,11 O-DU High sends Alert Clear to SMO which sends to OTF which
O-RU O-RU
FH-Mplane
2020-06-22 | Page 38 passes the test case.
38
O-DU Low

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

2020-06-22 | Page 40
O-DU Low project update (Cherry)
— Further developed/verified FAPI with testmac stub and commercial thirty party  Done
— Verified FAPI implementation with commercial thirty party -> Ongoing
— P5 massage -> Done
— P7 masge -> Done
— Stability -> ongoing
— Deployed O-DU low SW in OSC INF platform -> Ongoing
— compile and test with testmac stub -> Done(OSC lab)
— Further validation with E2E environment -> Ongoing
— O-DU low and O-DU high pairwise test -> Ongoing
— O-DU low and O-RU emulator test -> not start

2020-06-22 | Page 41
O-DU Low project plan (Dawn)
— Continue O-DU low and O-DU high pairwise test.
— Continue O-DU Low and O-RU emulator test.
— Continue E2E test with UE simulator.

2020-06-22 | Page 42
O-DU High

2020-06-22 | Page 43
O-DU High Cherry Release Achievements
• Lines of Code added (manually added code)
• Cherry Release - ~9 KLOC
• Achieving UE Attach
• Enabled F1-C and F1-U interface with CU
• All physical channels Enabled – PDSCH, PDCCH,
PUSCH, PUCCH, PRACH
• Logical channels Enabled - UL CCCH, DL CCCH, UL
DCCCH, DL DCCH
• Transport Channels Enabled – UL SCH, DL SCH
• MSG-1 to MSG-5 - All messages enabled and tested with
CU Stub
• Security mode command, RRC reconfiguration messages
to be tested
• Development of basic scheduler for single UE – FDD, mu-
0, 20 MHz B/W configuration
• Developed FAPI based interface towards O-DU Low
• Enabled code support for all short PRACH Formats – to
provide more flexibility to the UE
2020-06-22 | Page 44
• Developed Phy stub, CU stub and RIC stub for internal testing.
• Pair-wise testing (between ODU-High and O-DU Low)
• Completed bring up of ODU in AT&T lab and validation
• Successfully tested O-DU High functionality using
test stubs on ATT servers
• Aligned with FAPI files released by O-DU Low as part of
Bronze Release
• Testing of P5 messages in progress with O-DU Low
running in timer mode
• Integration with Radisys CU Product
• Due to absence of O-CU, internal integration till msg-5
with Radisys CU accomplished
• O1 interface – Developed by HCL
• Code completion of Health Check use-case(get-alarm
list )
• Design for supporting CM in progress
O-DU High Bring up and Single UE ATTACH – Accomplished Flows
• DU Bring up
• F1 Setup Req/Rsp
• GNB DU Config Update/Ack
• Cell UP
• Cell Broadcast comprising of MIB, SIB1
• FAPI DL TTI.request (O-DU High -> Phy Stub)
• FAPI Tx Data.request(O-DU High -> Phy Stub)
• RACH Indication
• FAPI RACH.indication(Phy Stub->O-DU High)
• Rach Response
• FAPI DL TTI.request (O-DU High -> Phy Stub)
• FAPI Tx Data.request(O-DU High -> Phy Stub)
• FAPI UL TTI.request (O-DU High -> Phy Stub)
• RRC Setup request
• FAPI Rx Data.indication(Phy Stub -> O-DU High)
• FAPI CRC.indication(Phy Stub -> O-DU High)
• F1AP Initial UL RRC Direct Transfer(O-DU High -> CU
Stub)
2020-06-22 | Page 45
• RRC Setup
• F1AP DL RRC Direct Transfer(CU Stub -> O-DU High)
• FAPI DL TTI.request (O-DU High -> Phy Stub)
• FAPI Tx Data.request (O-DU High -> Phy Stub)
• FAPI UL TTI.request (O-DU High -> Phy Stub)
• SR Indication
• FAPI UCI.indication (Phy Stub -> O-DU High)
• UE UL grant
• FAPI UL DCI.request (O-DU High -> Phy Stub)
• Short BSR
• FAPI Rx Data.indication (Phy Stub -> O-DU High)
• FAPI CRC.indication (Phy Stub -> O-DU High)
• UE UL grant
• FAPI UL DCI.request (O-DU High -> Phy Stub)
• RRC Setup Complete (UE ->ODU)
• FAPI Rx Data.indication (Phy Stub -> O-DU High)
• FAPI CRC.indication (Phy Stub -> O-DU High)
• UL RRC Direct Transfer(ODU -> CU Stub)
O-DU High Bring up and Single UE ATTACH – Testing in Progress
• NAS message exchanges
• NAS Message exchanges(CU Stub -> O-DU High)
• NAS message exchanges(O-DU High -> Phy Stub)
• NAS Message exchanges(Phy Stub -> O-DU High)
• NAS message exchanges(O-DU High -> CU Stub)
• Security Mode Command
• Security Mode Command (CU Stub -> O-DU High)
• Security Mode Command(O-DU High->Phy Stub)
• Security Mode Complete
• Security Mode Complete(Phy Stub -> O-DU High)
• Security Mode Complete(O-DU High -> CU Stub)
2020-06-22 | Page 46
• RRC Reconfiguration
• RRC Reconfiguration(CU Stub -> O-DU High)
• RRC Reconfiguration(O-DU High ->Phy Stub)
• RRC Reconfiguration Complete
• RRC Reconfiguration Complete(Phy Stub -> O-DU High)
• RRC Reconfiguration Complete(O-DU High -> CU Stub)
• UE Registration Complete
• UE Registration Complete(Phy Stub -> O-DU High)
• UE Registration Complete(O-DU High -> CU Stub)
 O-DU High – Tentative plan for Dawn Release
1. O-DU High Dev 7. HO and Traffic steering call flow
• UL and DL basic data testing (using current configuration • O-DU High Dev
FDD, mu0 etc.) • Support for Measurement reports for enabling HO
2. Support for Mu=1, 100 MHz B/W • E2 enhancements
3. Support for TDD • Support for including real time info in RIC indication.
4. Integration • Support for periodic reporting of RIC indication.
• Integration with O-DU Low. • Support for E2 initiated HO of signaling path.
• Integration with CU. • Support for E2 initiated HO with Basic Data.
5. End to end testing support (ORU-ODULOW-ODUHIGH-RSYS • F1 enhancements
CU+Viavi 5G Core ) • Support for additional F1AP messages to achieve HO
6. O1 enhancements - by HCL 8. Support for HARQ retransmission
• CM Support for all parameters.
• Implementation of other flows of Health Check use-case.

2020-06-22 | Page 47
Dependencies/ Open Items
• Copyright issue resolution for 3GPP Yang files.
• Published E2/O1 specifications.
• Handling of negative responses

2020-06-22 | Page 48
RICAPP

2020-06-22 | Page 49
RICAPP project update (Cherry)
Main development items:
• (New xApp) KPIMON (Samsung):
• Testing and integration with nearRT-RIC and E2 Simulator making steady progress.
• (Enhanced xApp) QP (QoE Predictor) (AT&T/HCL) with real ML model:
• ML training underway with Viavi simulator output
• Alarms and metrics (O1-PM/FM):
• Implemented in QP-driver xApps, others underway.
• (New xApp) AD (Anomaly Detection) xApp (HCL):
• Training with simulated data underway.
• Demo video for MWC-LA for the traffic steering use case including Viavi RAN simulator, E2 SIM,
KPIMON, QP-D, QP, and TS xApps in preparation.

Meeting minutes available at the following pages:

https://wiki.o-ran-sc.org/display/RICA/RICAPP+Meetings

2020-06-22 | Page 50
RICAPP project plan (Dawn)
• New xApps:
• Signaling Storm Protection (SSP)(Samsung) – implements initial steps towards the WG-1 use case.
• Load Prediction (LP) (CMCC) – ML-based xApp augmenting the TS use case.
• HelloWorld (go version) (Samsung) – demo of the RIC SDK using go

• Traffic steering use case enhancements:

• Add E2 CONTROL message to TS xApp (based on WG-3 E2 SM)
• Enhanced A1 Policy, enhanced TS logic

• Update xApps to use latest RIC SDK

• Code coverage and other CII badging requirements

• SDK sub-project

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

2020-06-22 | Page 52
 Near-RT RIC (Cherry)
• First contributions from HCL and Samsung coming, e.g. in context of automated source code quality scans, benchmarking, E2
simulator (E2 node side) and testing automation.
• Samsung working on RIC-95 (E2 health check based on E2 Service Query)
• xApp 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 ONeS 2020 (link).

• Waiting for copyright/licensing results between O-RAN and O-RAN SC.

• Work on O1-related functions, like E2 and A1 statistics, or some alarms already done
• REST interface for subscriptions (provided by subscription manager, used by xApps) still work in progress
• Subscription manager keeps its data persisten over its restart is still work in progress
• E2 manager now supports “bug red button” case with “close all E2 connections” and “do not allow new E2 connections”

• Dropped from Cherry original plans: see next slide

2020-06-22 | Page 53
Dawn – Near-RT RIC candidates
• Adaptation to E2APv1.1 (likely released in November) only happening post-Cherry.
• Dynamic scalability and failover
• Exposing E2 Node Configuration Update
• E2SM OID support in internal E2SM function query interfaces
• SDK package, well documented interfaces to be used by xApps via xApp frameworks
• Extension in SDL support (all three languages (C++,go, python)
• A1-EI support (pending a stable or published specification)
• xApp 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 xApp where xApps register with the platform as part of their startup.
• Dropped from Cherry original plans:
• RIC-585 alarm for E2 connection status change (remains only a RIC-internal event)
• RIC-421 O1 mediator graceful restart with O1 data being persisted over restarts
• RIC-114 time series database support
• RIC-48 further studies on message bus options (NATS or other brokerless). gRPC analysed, but not promising
• RIC-203 Alarm for routing table update delays

2020-06-22 | Page 54
Near-RT RIC implementation
Helm charts Research
Image repo
data lake
RIC
xApp and Config

REST
Measurement campaign xApp
Auxiliary REC with ONAP-based GUI

Manager Various Extras

RIC xApp framework

RAN, i.e. gNB/eNB

(Nokia)

REST
A1 Mediator
O1 AnomalyDetection xApp

REST
VES Agent /
API Gateway (Kong)

conf O1 Mediator RIC xApp framework VESPA

Net
REST

Subscription
REST

KPIMON xApp
Manager Prometheus
A1 RIC xApp framework
REST

E2 Manager
Traffic steering xApp Logging &

REST
RIC xApp framework OpenTracing
REST

Routing Manager

Redis RAN RNIB

Redis xApp DBs
E2 Termination
E2
REST
O2 (LCM)

Alarm Adapter (e.g., UE RNIB)

RMR library Alarm library ASN.1 Prometheus exporters Trace&log Redis SDL + R-NIB API

RIC xApp Framework (one per C++, Golang, Python)

Akraino REC (Radio Edge Cloud) or other

2020-06-22 | Page 55
O-CU

2020-06-22 | Page 56
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: Developing functions for Release C (not tested):

Functions Related F1, Ng messages Functions Related F1, E1, Ng messages

Random Access • INITIAL UL RRC MESSAGE TRANSFER Bearer • Initial UE Message

• DL RRC MESSAGE TRANSFER Establishment • Initial Context Steup Request
• UL RRC MESSAGE TRANSFER • UE CONTEXT SETUP REQUEST
• UE CONTEXT SETUP RESPONSE
• BEARER CONTEXT SETUP REQUEST
Release D but no contributors now: • BEARER CONTEXT SETUP RESPONSE
• DL RRC MESSAGE TRANSFER
Functions • Initial Context Setup Response
• UL RRC MESSAGE TRANSFER
E2 • Support E2AP • UpLink NAS Transport
• Support E2SM-KPM for traffic steering user cases Integration • Integration CP and UP source code
Handover • Support Handover for traffic steering user cases

O1 • Support O1 interface for O-CU CP/DU

• O-CU test Setup, Start/Stop/Reset, Init.
2020-06-22 | Page 57
config
INF

2020-06-22 | Page 58
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 59
Infrastructure (INF) project plan (Dawn)
— Enable INF proj. to support ARM arch.

— INF-193 - INF-D-03 Implement the O2 interface as per MVP

— INF-172 - INF-D-01 Enable the 2 AIO severs with additional worker nodes deployment scenario (IN
PROGRESS)
— INF-173 - INF-D-02 Enable the AIO for ARM (STRETCH GOAL ）

2020-06-22 | Page 60
 O2 Proposal

—Requires Initial Config as part of

ConfigMap
— SMO receives YANG to build initial
Config from onboarding
— xAPP provides YANG and initial config
to near-RT RIC as part of step 2 and 3
2020-06-22 | Page 61
61
Accepted Procedure based on Ericsson Proposal

—https://oranalliance.atlassian.net/wiki
/download/attachments/106397773/
ERI.AO-2020.08.24-WG6-CR-0003-Orc
hestrationUseCases-v02.docx?api=v2

2020-06-22 | Page 62
62
INT

2020-06-22 | Page 63
63
Integration (INT) project update (Cherry)
— Automate CLM scanning for all project repos
— Jenkins jobs are created for a1 and python xapp-framework

— Automate SonarQube scanning for all project repos

— 21 projects passed
— 7 projects failed

— Validate and testing end-to-end use cases

2020-06-22 | Page 64
Integration (INT) project plan (Dawn)
• Automate E2E and regression testing with OTF

• Score reporting for CII best practices badging

• Validation and Testing for SMO and O-CU

• CI jobs for project scanning (SonarQube + Nexus lifecycle)

• Supports for Dawn use cases

• O-RU setup using OTF VTH for Viavi

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

2020-06-22 | Page 66
66
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 E2 support is central to completing O-RAN Use Cases
• To date we have:
• Monolithic eNodeB (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 67
O1/A1 use case – D release
Modify Fronthaul parameters via O-DU using O1- Other items:
CM. What is the role of A1 here?
11/24, Tue 10 am EST Documentation
Provide project doc to PTL for wiki
INF – O1 use case to show HA capability; Failure in CII badging
INF; Will it cause O-DU to reset and reestablish https://wiki.o-ran-sc.org/display/ORAN/Core+Infras
connections? Switchover call flow tructure+Initiative+%28CII%29+Badging
Xiaohua to setup call

Conflict Management use case where rApp via Cherry release help to Felix
SMO is providing O1-CM control to E2 node while John K and Felix to meet re A1-EI
xApp is providing E2 control messages A1 healthcheck; enrichment data flowing inside
a healthcheck

App package validation demo – Mahesh/Harish

2020-06-22 | Page 68