You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 44 Next »

  Bronze release page for the O-RAN Software community   

Welcome to the Bronze release page for the O-RAN Software community          

This page contains all the information specific to the Bronze release and frozen code (code freeze = Jun-14, 2020) and documentation. The main trunk will continue on to support future releases.

This is the second release and is in partnership with the O-RAN Alliance. The specification and software are being worked at the same time and the software is considered pre-specification software.

The projects have limited capabilities which will increase over future releases.

See Requirements and Software Architecture under Committees and Projects for more details on current activities.

Second release capabilities include contributions under the following projects:

  • Non-Real-time RIC (A1 Interface) (NONRTRIC)
  • Near Realtime RAN Intelligent Controller Platform (E2 Interface) (RIC-PLT)
  • Near Real-time RIC X-APPs (RICAPP)
  • OAM (O1 Interface)
  • O-RAN Central Unit (OCU)
  • O-DU High
  • O-DU Low
  • Dashboard (OAM)
  • Simulators (SIM)
  • Infrastructure (INF)
  • Integration and Test (INT)
  • Documentation (DOC)

Get Bronze

  • Source code: Release Date:  
  • Per-repository details:  Release Date:  

Documentation

Table of Projects

Bronze Release Timeline

Bronze Timeline

Learn Bronze

Near real-time RIC X-APPs (RICAPP)

Primary Goals: This includes open source sample xAPPs and platform applications that can we used for integration, testing, and demonstrations.

Bronze Feature Scope: Support Bronze use cases by developing and evolving existing xApps. For the traffic steering use case, we are extending the existing KPIMON xApp and developing new TS, QP, and QP Driver xApps using the different programming langauges supported by the RIC platform. For the health check use case we are developing a demo xApp that supports the A1 health check and extending existing xApps with more thorough liveness checking from K8s and new statistics/alarming APIs provided by the RIC platform.

Jira: Count of Epics, User Stories, Tasks, and Issues:  Getting issues...

Near Realtime RAN Intelligent Controller Platform (E2 Interface) (RIC-PLT)

Primary Goals: Develop platform for xApp hosting with stable APIs for xApps using RIC's E2 interface, xApp management interface and other auxiliary xApp interfaces, like a database storage interface.
Bronze Feature Scope: Adapting RIC from pre-spec to WG3's first formal E2 protocol specification (for communication with RAN nodes, like CU/DU). Implement netconf-based O1. Enhance RIC's messaging solution (RMR) to achieve higher throughput, various health check capabilities including a capability to ping E2 nodes via E2 and to do a health check of the A1 interface, better failure handling in various components, ...

Status 2020-03-04

  • Jira: 61 epics: link (requires free LinuxFoundation account). Items that we worked on already before the first formal development are marked as Bronze-R3 in JIRA "fix release" (13 = 5 (in progress) + 8 (done)) and the ones to be worked on during the five three-week sprints in Bronze-R4 Feb-3 to May-17 (48 = 7 (in progress) + 1 (done) + 40 (not yet started)). For useful near-RT RIC JIRA links check §8 in Jira usage conventions.
  • Legal aspects related to automatically using WG3 ASN.1 of E2APv1.0 still open. Thoralf to send information to Jinri by Friday this week.
  • Samsung's Arun started working RIC-203 and RIC-95
  • Demos of sprint D2 (Feb-23 - Mar-12) planned for Thursday, Mar-12, 9am ET (note special summer time adjustments in this week in other locations). Thoralf will add event to groups.io calendar. After this demo every three weeks some date & time.

Non-Real-time RIC (A1 Interface) (NONRTRIC)

Primary Goals:

The primary goal of Non-RT RIC is to support intelligent RAN optimization by providing policy-based guidance, ML model management and enrichment information to the near-RT RIC function so that the RAN can optimize, e.g., RRM under certain conditions.
It can also perform intelligent radio resource management function in non-real-time interval (i.e., greater than 1 second).
Non-RT RIC can use data analytics and AI/ML training/inference to determine the RAN optimization actions for which it can leverage SMO services such as data collection and provisioning services of the O-RAN nodes.

Bronze Feature Scope:
Initial design and start implementation of NONRTRIC Platform.
Continue evolution of A1 interface.
Continue evolution of A1 Policy Management functions.
Modeling and implementation of the Non-RealTime RIC aspects of the "Health Check" and "Traffic Steering" use cases

Jira: Count of Epics ( Getting issues... ), User Stories, Tasks, and Issues:  Getting issues...


OAM (O1 Interface)

Primary Goals: Implementation of O-RAN Alliance OAM Architecture and Interface Specifications.
Bronze Feature Scope: Modeling and implementation of the Health Check use case and Deployment of an SMO.

Jira: Count of Epics ( Getting issues... ) , User Stories, Tasks, and Issues:  Getting issues...

O-RAN Central Unit (OCU)

Primary Goals: 

The O-CU project provides 5G SA 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.

Basic CU functions defined in O-RAN WG8

Support E2E use case defined in O-RAN

Bronze Feature Scope: 

F1

  • support Interface Management procedures
  • support UE Context Management procedures
  • support RRC Message Transfer procedures
  • support System Information Procedures

SDAP

  • support transfer of user plane data;
  • support mapping between a QoS flow and a DRB for both DL and UL;
  • support marking QoS flow ID in both DL and UL packets;
  • support reflective QoS flow to DRB mapping for the UL SDAP data PDUs.


PDCP

  • support transfer of data (user plane or control plane);
  • support maintenance of PDCP SNs;
  • support header compression and decompression using the ROHC protocol;
  • support ciphering and deciphering;
  • support integrity protection and integrity verification;
  • support timer based SDU discard;
  • support reordering and in-order delivery;
  • support out-of-order delivery;

RRC

  • support Broadcast of system information;
  • support RRC connection control;


Ng

  • support PDU Session Management Procedures
  • support UE Context Management Procedures
  • support Transport of NAS Messages Procedures
  • support Interface Management Procedures


E1

  • support Interface Management procedures
  • support Bearer Context Management procedures


PTL: user-a934b

Jira: Count of Epics, User Stories, Tasks, and Issues:

OCU-1 - Getting issue details... STATUS   F1

OCU-2 - Getting issue details... STATUS  SDAP

OCU-3 - Getting issue details... STATUS  PDCP

OCU-4 - Getting issue details... STATUS  RRC

OCU-5 - Getting issue details... STATUS  Ng

OCU-6 - Getting issue details... STATUS  E1


O-DU High

Primary Goals:  Develop Amber release code to enhance O-DU layers source code

Bronze Feature Scope: 

  • O-DU High layers (MAC, RLC and app):
    • Re-align seed code to 3GPP Release 15.3.0
    • Align seed code to WG8 AAD specification and interfaces
    • Implementation of cell broadcast procedure and UE attach procedure (SA mode)
      for FDD mode and FR1 (Numerology = 0, Bandwidth = 20 MHz) and basic scheduler APIs for single UE and single HARQ transmission
  • F1-U interface development
  • F1-C interface enhancement: 
    • Support for following additional F1AP messages:
      • Initial UL RRC Message Transfer
      • UL/DL RRC Message Transfer
      • UE Context Setup Request/Response
    • Enhance F1AP messages:
      • F1AP Setup Request/Response
      • GNB DU Config Update
  • Basic FAPI messages Implementation

Out of Scope:

  • Use cases – Traffic Steering, Health Check related messages and call flows
  • TDD functionality, NSA
  • End to end testing

Limitations/Dependencies:

  • FAPI Implementation – Dependency on O-DU Low to open source WLS files, interface files
  • Testing: Currently only some unit testing can be done due to lack test infrastructure i.e UE or UE simulator, O-RU, O-CU and core components.

Jira: EPICS are mentioned below:

O-DU Low

Primary Goals: The O-RAN-SC-ODU LOW project provides reference implementation of ODU-LOW according to the O-RAN AAD specification (WG8) documents. The reference design will follow the open interface toward ODU HIGH, RRU and Accelerator, provide physical layer signal processing functionality according to ORAN specification and 3GPP .
Bronze Feature Scope: enhance O-RAN FH interface lib, develop FAPI API, deliver O-DU Low full functionality binary 
PTL: @Zhimin Yuan
Jira: Count of Epics, User Stories, Tasks, and Issues:

Epics

Planning

Develop L1/L2 FAPI Interface API

1.Develop the L1/L2 FAPI API files

2.Develop the interface parse software for O-DU low software

Develop O-DU Low binary

1.Upstream the O-DU low binary file with typical test cases

2.Provide loader for OSC to download  and test

Enhance O-RAN Front Haul Library

1.Develop new features, include support category B, Support block floating point compression and decompression

2.Develop the CI/CD infrastructure according to O-RAN requirement

O-DU interface with accelerator

Depend on the specification definition(TBD)

Limitations/Dependencies:

  • L1 binary license agreement – dependent on the agreement of the L1 binary release
  • ICC usage agreement – it'll affact FAPI lib, O-RAN FH lib compilation and execution. it'll affact L1 binary execution

Simulators (SIM)

Primary Goals: Providing software simulators which are needed by the other projects.
Bronze Feature Scope: Support both the Health Check and the Traffic Steering use cases.

Jira: Count of Epics, User Stories, Tasks, and Issues:  Getting issues...

Blockers: need resources for E2 Simulator enhancements for supporting Traffic Steering use case

Infrastructure (INF)

Primary Goals: 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 , configuraiton management , software management , host management and service management. Improve the automation by adopting the ansible, and integrate with INT project.

Jira: Count of Epics, User Stories, Tasks, and Issues:

INF project EPICs in Release B

Integration and Test (INT)

Primary Goals:  CICD, integration and deployment of O-RAN SC developed software, software testing.
Bronze Feature Scope:  1. CICD to support software static analysis and quality reporting, and integrated testing for Near RT RIC; 2. "One-click" deployment of Non RT RIC, OAM, and Near RT RIC, and simulators for supporting the Bronze use cases; 3. Deployment and integration of other components; 4. Integrated testing and use case flow testing.

PTL:  user-d3360

Jira: Count of Epics, User Stories, Tasks, and Issues: Getting issues...

Documentation (DOC)

Primary Goals: Bronze release documentation for OSC and developers
Bronze Feature Scope: 

Improve current documentation skeleton and content, make documentation more understandable for readers.

Focusing on integration documentation, the new feature of Bronze release.

Jira: Count of Epics, User Stories, Tasks, and Issues:


  • No labels