Primary Goals: 

• O-DU high integration in Radio mode
• Initial access and Attach procedure testing in Radio mode
• DL and UL data path in FDD, 20 MHZ with 256 QAM and 64 QAM respectively
• Static TDD mode support with Numerology =1
• O1 enhancement
• Closed Loop Automation Use case support

D Feature Scope: 

. 1. Achieve UL and DL data flow using FDD mode on 20 MHz Bandwidth, Numerology = 0

 2.Support for static TDD mode with pattern “DDDDDDDSUU” on 100 MHz Bandwidth, Numerology = 1

• Evolve scheduler to support UL and DL scheduling of signaling and data messages on single spectrum in TDD mode
• Expand scheduler to support Frame structure according to numerology = 1
• Updates to cell broadcast for TDD and numerology = 1

3.Development activity for Closed Loop Automation use-case

• Support for cell stop and restart within O-DU High layers
• Support for cell stop and restart towards O-DU Low
• F1AP Enhancements towards O-CU indicating cell stop and restart

4.Integration

• Integration with O-DU Low in Radio mode
• Integration with CU

5.End to end testing support (O-RU<->O-DU-LOW<->O-DU-HIGH<->RSYS CU<->Viavi 5G Core )

6.O1 enhancements - by HCL

• CM Support
• Support for Closed Loop Automation use-case
• Support for Health Check use-case

Updated:  31st March 7th April 2021

JIRA: Epics Status below:

• https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
  • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
• https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
  • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
• https://jira.o-ran-sc.org/browse/ODUHIGH-186 - WIP
  • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
    • Basic code changes complete. Testing in progress for data path
• https://jira.o-ran-sc.org/browse/ODUHIGH-187 - WIP
  • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
    • Basic code changes complete. Testing to be done for data path
• https://jira.o-ran-sc.org/browse/ODUHIGH-264 - WIP
  • As an O-DU L2 developer, I want to add support for Mu1
    • Code changes at DU APP completed.
    • Code changes and testing completed for SSB.
    • Brainstorming for SIB1 in progress
• https://jira.o-ran-sc.org/browse/ODUHIGH-265 - WIP
  • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
    • Code changes at DU APP completed.
    • Code changes and testing completed for SSB.
    • Resource allocation design for SIB1 in progress
• https://jira.o-ran-sc.org/browse/ODUHIGH-266 - WIP
  • As an O-DU L2 developer, I want to add support for TDD mode
    • Code changes at DU APP completed.
    • Code changes and testing completed for SSB.
    • Brainstorming Resource allocation design for SIB1 in progress
• https://jira.o-ran-sc.org/browse/ODUHIGH-299 - WIP
  • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
    • Discussions on the O-DU PNF Registration and Activation process is ongoing
    • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress.
    • UE delete functionality under review
    • Cell delete functionality coding in progress
• https://jira.o-ran-sc.org/browse/ODUHIGH-267 - WIP
  • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
    • SSB transmission successful
    • Debugging issue with Sib1 transmission
• https://jira.o-ran-sc.org/browse/ODUHIGH-268 - WIP
  • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
    • Using Radisys commercial CU as a test fixture
    • Awaiting server allocation
• https://jira.o-ran-sc.org/browse/ODUHIGH-269 - TODO
  • As an O-DU L2 developer, I want to support End to End testing scenarios

Dependency/Blockers:

• O1 configuration for day-1 shall need to be completed to start with CLA.
• Server allocation to mount Radisys CU as a test fixture. Bare metal server preferred. 
• Unable to use valgrind with Intel libraries. Debugging issue with seg fault using Brute Force method.