Overview of O-RAN SC Bronze Release Objectives and Timelines
The content delves into the objectives of the OSC Bronze release focusing on end-to-end RAN communications and traffic steering use cases. It highlights the key elements of the Bronze release like health checks, RAN ecosystem connectivity, and timelines for bi-annual releases. Additionally, it discusses the ambitious plans of connecting various O-RAN managed functions for a complete ecosystem. The document provides insights into the health check use case, traffic steering flow, and aligning Non-RT RIC functions. The ultimate goal is to achieve a comprehensive end-to-end RAN ecosystem while acknowledging the need for potential future enhancements and adaptations.
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. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
OSC Bronze update Rittwik Rittwik Jana, Jana, AT&T AT&T 1
OSC Bronze Objectives Timeline Use cases Traffic Steering Health Check 2
OSC Bronze Objectives End-to-End RAN communications (integrated functions) While the Amber release was about have a representative development across almost all O-RAN Managed Functions, the Bronze release focus is about connecting those elements together for a complete end-to-end RAN ecosystem. This is an ambitious plan and some functionality may be partially implemented in Bronze with the intent to complete in the Cherry release. Planning: RSAC_Bronze_release_planning.xlsx RSAC_Bronze_Use Case-Traffic Steering QoE.doc RSAC_Bronze_HealthCheck_UseCase.docx 3
OSC Bronze timelines Two releases per year around Jun-5 and Dec-1 4
OSC Bronze Health check use case The key objective is that all O-RAN elements (SMO, non-RT RIC, near-RT RIC, xApps, O-CU, O-DU, O-RU) shall do the following: Perform self-health-checks Support on-demand health-checks and queries Report alarms, alerts and other data based on health-check results 4 flows defined https://wiki.o-ran-sc.org/display/RSAC/Health-Check+Use+Case Flow #1 RIC Self-Health-Check Flow #2 O1 RIC Heartbeat, Health Retrieval and On-Demand Health-Check Flow #3 A1 RIC Heartbeat and Policy Health-Check Flow #4 O1 Managed Function Health-Check 5
OSC Bronze Traffic Steering Flow Over E2 xApps Near-RT RIC CUCP DU E2 Term CUUP KPM TS (1) E2 SUBSCRIPTION (Trigger) Multiple Subscriptions for different E2 Nodes, Metrics (3) E2 INDICATION (REPORT) Periodic Indication Messages for different E2 Nodes, Metrics Choose UEs to optimize, Predict QoE based on features, Choose UE to act on (6) E2 CONTROL (7) Response 6
OSC Bronze at a glance Non-RT RIC PTL John Keeney https://oranalliance.atlassian.net/wiki/spaces/NonRTRIC/pages/205127681/O- RAN+SC+OSC+material O-RAN WG2 Alignment WG2 - A1 spec Liaising with near-RealTime RIC project to align toward Release 1.X spec Providing feedback on improving implementability of spec Providing feedback on possible improvements/simplifications to spec Aiming for complete alignment but some pragmatic compromises might be required Non-RealTime RIC function Aligned with WG2 s objectives/ambitions for Non-RealTime RIC Function Still at a very early stage . Started with A1 mediation/controller function and A1 policy management service Additional functionality at discussion/architecture/design stage Use-cases Requirements from OSC use cases are influencing/guiding development roadmap 7
OSC Bronze at a glance Near-RT RIC (PTL, Thoralf Czichy) WG3_2020.02.14_Nokia_Alignment with OSC workv0.3.pdf WG3 E2AP v1 specifications are now being folded into Bronze E.g., E2 SETUP from RAN to RIC 8
OSC Bronze at a glance O-DU High (PTL, Sachin Srivastava) O-DU High activities for Traffic Steering use case Establish SCTP connection with RIC Implement below E2AP messages E2AP Setup Request E2AP Setup Response RIC Subscription Request RIC Subscription Response RIC Indication Content of RIC indication message can be emulated - PRB usage data will either always be fixed in source code or read from an input file and to be sent over E2 interface Due to lack of testing with UE given the state of the infrastructure. Testing of O-DU High and RIC to be done by INT team O-DU High Health check use case may be deferred to Cherry release 9
OSC Bronze at a glance O-DU Low (PTL, Zhimin Yuan) Interface between L1 and Front haul, adopt WG4 specification Enhance O-DU Front Haul Library Title Description O-DU FH library provides the APIs for L1 application to be used to communicate with O-RU. Enhance current O-DU Front Haul features 1. Support category B 2. Support block floating point compression and decompression 3. Changes and optimizations needed to support MassiveMIMO Develop the CI/CD infrastructure for O-DU FH Lib (need OSC/ LF help) 1. IP scan 2. Unit test passing 3. Code quality checking(code coverage, klocwork report) Finish the integration additional one O-RU vendor Meet the WG4 test specification requirements, pass the unit test and integration with one third party O-RU vendors. [ODU-A-F315] Develop O-DU L1 binary create L1 application binary with configuration to be used under different configuration (e.g. different Tx/Rx antennas, layers) in public GitHub/GitLab, provide linker for OSC. test with L2 application and white box hardware OSC release B Title Description Acceptance Criteria Source Develop L1/L2 FAPI Interface Library Create L1/L2 Interface APIs based on FAPI specification. The APIs are used by the L2/L1 to configure, transmit and receive FAPI massage, it will based on share memory. Test L1 and test L2 will be created to test the interface, message will comply with FAPI spec. Integration and validation plan need to be aligned with O-DU High project. OSC release B Title Description Acceptance Criteria Acceptance Criteria Source OSC release B Source 10
OSC Bronze at a glance RICAPP (PTL, Matti Hiltunen) Traffic Steering Component Interaction and xApps being developed RMR (QOE-PRED-REQ) RMR (A1 POLICY: group id) QP driver xApp QP xApp RMR (QOE-PREDICTION) RMR (TS-UE-LIST, list) SDL get SDL get cell UE SDL get TS xApp metrics metrics SDL update KPIMON E2 CONTROL E2Term E2 REPORTS CU- UP CU- CP DU 11
OSC Bronze at a glance OAM (PTL, Martin Skorupski) O1 component architecture Integration into SMO OAM status https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=14221985 34 OAM epics being worked on https://wiki.o-ran-sc.org/display/OAM/2020-01-27+OAM+Meeting+notes SMO component epics 12
OSC Bronze at a glance SIM (PTL, Alex Stancu) O1 interface simulator done in Amber Needs to be enhanced in Bronze for Health-Check Use Case A1 interface simulator to be moved from NONRTRIC project in Bronze E2 interface simulator to be moved from INT project in Bronze UE simulator To be provided in Bronze Need software-only simulator, to support Traffic Steering Use Case To be decided how to approach Viavi able to provide something? O-CU Simulator might be needed for end-to-end testing SIM project status - https://wiki.o-ran- sc.org/display/SIM/2020-02- 17+Status+Report 13
OSC Bronze at a glance INF (PTL, Xiaohua Zhang) Provide an open source refence implementation of O-Cloud complying with WG6 specifications. Use it as the edge cloud to be able to run vO-DU and vO-CU services on it. Bronze Feature Scope: Based on release Amber, support the ARM based system. Align with requirement of the O-Cloud, add more services such as fault management , configuration management , software management , host management and service management. Improve the automation by adopting the ansible, and integrate with INT project. 8 epics 14
OSC Bronze at a glance INT (PTL, Lusheng Ji) 15
OSC Bronze at a glance O-CU (PTL, Yingying) Project goals: The O-CU project provides reference implementation according to the O-RAN WG8 documents. In addition we provide the implementation of RRC SDAP PDCP and F1AP module and API between them. Integrated eNB function The O-CU should target an initial software deliverable with limited and necessary functionality, i.e. RRC, SDAP, PDCP, F1AP according to the <Base Station O-DU and O-CU Software Architecture and APIs> in O-RAN alliance. E2 interface. O-CU shall implement a basic E2 interface in the future release. 16
OSC Bronze at a glance DOC (PTL, Weichen Ni) 17
Backup 18
