O-RAN Software Community June 2020 Updates
O
S
C
C
h
e
r
r
y
R
e
l
e
a
s
e
O-RAN Software Community
2020.06.08
Rittwik Jana, David Kinsey (RSAC)
Agenda
•
Virtual meeting schedule
•
Kick-off discussion on Cherry Release: 8-10AM EST, June 8, Monday
•
OSC-TIFG: Emulation SW discussion: 9-10AM 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):
•
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 WindRiver;
•
Key features/highlights
•
Two E2E use cases: traffic steering and health check
•
O-DU-LOW successfuly passed the internal review
•
O-DU-HIGH: E2 initiation and setup; subset of E2 messages to support traffic steering
•
Near-RT RIC: (from pre-spec. to be) compliant with E2 spec. v1.0, E2 setup/failure, xAPP onboarding etc.
•
xAPP: various xAPPs for traffic steering, management, KPI monitoring etc.
•
Non-RT RIC: A1 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 O1 flow
•
SIM: E2 simulator enhancement implemented, e.g. E2 ingest data pipeline from trace file
•
INT: CI/CD pipeline, OTF integration, Deployment artifact automation
O
S
C
C
h
e
r
r
y
R
e
l
e
a
s
e
•
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) xApps using
ML
Develop E2 data ingest pipeline from E2 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]
O1 near-RT RIC health-check [Bronze – partial, to be completed in Cherry]
A1 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 WG8
-
O-DU LOW
(Intel flexRAN)
-
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]
o
E2 initialization and setup between O-DU and near-RT RIC [Bronze]
o
Implement O1 health check [Cherry]
O
S
C
C
h
e
r
r
y
R
e
l
e
a
s
e
Teams (O-RU emulator, O-
DU low and O-DU high)
working to agree on a
minimum viable
configuration
O
S
C
-
W
G
8
Near-RT RIC
o
RAN initiated E2 SETUP with E2 nodes compliant with WG3 E2 specification v1.0 [Bronze]
o
xApp Framework enhancement [Cherry]
o
HA in all components [Cherry]
o
RIC time-series DB [Cherry]
o
Platform alarming functionality (e.g., E2 connection loss, msg overload, etc.) [Cherry]
Non-RT RIC
o
Construction of an A1 policy management service (Policy Agent) [Bronze]
o
Policy Management GUI and Control Panel to view A1 policies [Bronze]
o
Construction of A1 controller and controller APIs [Bronze]
o
A1 Flow (Healthcheck #3) implemented and tested [Bronze]
o
ONAP architecture alignment for SMO/Non-RT RIC [Cherry]
o
A1 enrichment information gathering [Cherry]
o
R-APP platform API [Cherry]
O
S
C
C
h
e
r
r
y
R
e
l
e
a
s
e
O
S
C
-
W
G
s
1
,
2
,
3
,
6
RICAPP
o
Construction of TS, MCxApp for measurement campaign, HelloWorld [Bronze]
o
Continue development of various xApps for traffic steering (TS, QP, etc.) using
Machine Learning [Cherry]
o
Continue development of KPIMON xApp (from Samsung) for ingesting E2 data
and computing KPIs from realistic simulator (Viavi) [Cherry]
o
RIC SDK to support O1 PM/FM/CM and A1-P [Cherry]
o
Alignment needed with WG3 E2SM for TS
OAM
o
Health check O1 flow #2 implemented [Bronze]
o
Alignment needed
with WG1 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
O
S
C
C
h
e
r
r
y
R
e
l
e
a
s
e
O
S
C
-
W
G
1
O
S
C
-
W
G
3
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 E2 Simulator
o
RAN initiated E2 SETUP [Bronze]
o
E2 Data ingest pipeline from trace files [Bronze]
o
Introduce commercial Simulator into E2 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
•
Bronze release, the O-Cloud deployment scenario uses a single server, AIO (all-in-one)
•
Intel Arch (IA) Kubernetes cluster
•
IA StarlingX 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 StarlingX 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 WG6 Orchestration and Cloudification specifications
•
Cloud Architecture and Deployment Scenarios v02.00 (O-RAN.WG6.CAD-v02.00)
•
Cloud Platform Reference Design for Deployment Scenario B v01.00 (O-RAN.WG6.CLOUD-REF-B-v01.00)
•
Orchestration Use Cases and Requirements for O-RAN Virtualized RAN v01.00 (O-RAN.WG6.ORCH-USE-CASES-v01.00)
I
N
F
O
-
R
U
,
O
-
D
U
L
O
W
,
O
-
D
U
H
I
G
H
u
n
i
f
i
e
d
p
r
o
f
i
l
e
f
o
r
C
h
e
r
r
y
O
t
h
e
r
i
t
e
m
s
•
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
The O-RAN Software Community provides updates on the Cherry Release, Bronze release preparations, key features, use cases, and ongoing collaborative discussions and plans. Topics include E2E use cases, RIC compliance, xAPP development, health checks, infrastructure design, and emulator discussions. The agenda, Cherry Release planning, and various epics and tasks are highlighted, showcasing the progress and upcoming milestones within the O-RAN ecosystem.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
OSC Cherry Release O-RAN Software Community 2020.06.08 Rittwik Jana, David Kinsey (RSAC) 1 1
Agenda Virtual meeting schedule Kick-off discussion on Cherry Release: 8-10AM EST, June 8, Monday OSC-TIFG: Emulation SW discussion: 9-10AM 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): 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) 2 2
O-RAN SC Bronze update Bronze release coming soon Planned release date: June 14 PR under preparation: statement input from Nokia, Ericsson and WindRiver; Key features/highlights Two E2E use cases: traffic steering and health check O-DU-LOW successfuly passed the internal review O-DU-HIGH: E2 initiation and setup; subset of E2 messages to support traffic steering Near-RT RIC: (from pre-spec. to be) compliant with E2 spec. v1.0, E2 setup/failure, xAPP onboarding etc. xAPP: various xAPPs for traffic steering, management, KPI monitoring etc. Non-RT RIC: A1 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 O1 flow SIM: E2 simulator enhancement implemented, e.g. E2 ingest data pipeline from trace file INT: CI/CD pipeline, OTF integration, Deployment artifact automation 3 3 3
OSC Cherry Release 4 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) xApps using ML Develop E2 data ingest pipeline from E2 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] O1 near-RT RIC health-check [Bronze partial, to be completed in Cherry] A1 near-RT RIC health-check [Bronze] O-DU and O-CU health-check Flow #4 [Cherry] - O-CU OSC- WG8 o o o Put more focus on O-CU for Cherry Interfacing with O-DU High and implement health-check compliance Alignment needed with WG8 Teams (O-RU emulator, O- DU low and O-DU high) working to agree on a minimum viable configuration - O-DU LOW (Intel flexRAN) - 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] o E2 initialization and setup between O-DU and near-RT RIC [Bronze] o Implement O1 health check [Cherry] 5 5
OSC Cherry Release Near-RT RIC o RAN initiated E2 SETUP with E2 nodes compliant with WG3 E2 specification v1.0 [Bronze] o xApp Framework enhancement [Cherry] o HA in all components [Cherry] o RIC time-series DB [Cherry] o Platform alarming functionality (e.g., E2 connection loss, msg overload, etc.) [Cherry] Non-RT RIC o Construction of an A1 policy management service (Policy Agent) [Bronze] o Policy Management GUI and Control Panel to view A1 policies [Bronze] o Construction of A1 controller and controller APIs [Bronze] o A1 Flow (Healthcheck #3) implemented and tested [Bronze] o ONAP architecture alignment for SMO/Non-RT RIC [Cherry] o A1 enrichment information gathering [Cherry] o R-APP platform API [Cherry] OSC- WGs 1, 2, 3, 6 6 6
OSC Cherry Release RICAPP o o Construction of TS, MCxApp for measurement campaign, HelloWorld [Bronze] Continue development of various xApps for traffic steering (TS, QP, etc.) using Machine Learning [Cherry] Continue development of KPIMON xApp (from Samsung) for ingesting E2 data and computing KPIs from realistic simulator (Viavi) [Cherry] RIC SDK to support O1 PM/FM/CM and A1-P [Cherry] Alignment needed with WG3 E2SM for TS o o o OSC- WG3 OAM o o Health check O1 flow #2 implemented [Bronze] Alignment needed with WG1 on Information and Data models for alarms mismatch found in Bronze testing between near-RT RIC and OAM projects SMO Deployment based on ONAP Guilin o Epics - https://wiki.onap.org/display/DW/Guilin OSC- WG1 o 7 7
INF o o Real time platform to deploy O-DU for Intel and ARM architecture [Bronze] Introduce high availability (HA) [Cherry] o Epics https://wiki.o-ran-sc.org/display/IN/Release+C+-+POR SIM o Enhancements to E2 Simulator o RAN initiated E2 SETUP [Bronze] o E2 Data ingest pipeline from trace files [Bronze] Introduce commercial Simulator into E2 data pipeline [Cherry] o Key UE level & Cell level KPIs generated for Traffic Steering o 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 StarlingX 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 StarlingX 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 WG6 Orchestration and Cloudification specifications Cloud Architecture and Deployment Scenarios v02.00 (O-RAN.WG6.CAD-v02.00) Cloud Platform Reference Design for Deployment Scenario B v01.00 (O-RAN.WG6.CLOUD-REF-B-v01.00) Orchestration Use Cases and Requirements for O-RAN Virtualized RAN v01.00 (O-RAN.WG6.ORCH-USE-CASES-v01.00) 9 9
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
