Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

O-DU High

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

  • Re-structure O1 module to run as a thread in ODU-High
  • CM Support - IP and Port configuration for DU, CU stub and RIC stub via Netconf interface
  • Support for Closed Loop Automation use-case

Updated: 

19th

26th May 2021

JIRA: Epics Status below:

.
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
      • Code changes for UE registration flow 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.
      • Resource allocation for SSB and SIB1 completed
.
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
      • Code changes for UE registration flow 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.
      • Resource allocation for SSB and SIB1 completed
.
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
      • Code changes for UE registration flow 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. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified.
      • UE delete functionality complete
      • Cell delete functionality complete
      • Issue with mis-coordination between cell delete and DL RRC message, resolved.
      • Code changes for CU Interaction under review
  • 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 , PDCCH is received but no PDSCH seen at O-DU low.
      • Awaiting inputs from Intel
  • 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
      • New VM to be configured as per H/W and S/
Wrequirements 327 In review
  • WIP
    • As an O-DU L2 developer, I want
to develop O-DU High Layers to support Closed Loop Automation Use-case
    • to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Awaiting input from Viavi

Updates from HCL:

269 WIP
  • In review
    • As an O-DU L2 developer, I want to
support End to End testing scenarios
  • Testing of broadcast messages at O-RU emulator set to begin
  • Awaiting input from Viavi TODO
    • WIP
      • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case

    Dependency/Blockers:

    • O1 configuration for day-1 shall need to be completed to start with CLA. However basic configuration e.g. cell state/operational state/admin state shall be supported initially. Use admin state as unlocked to validate the RU link failure.
    • Server(VM) configuration (H/W and S/W) to mount Radisys CU as a test fixture. 
    • Unable to use valgrind with Intel libraries. Debugging must be carried out with Alternate methods.
    • SIB1 PDSCH reached L1 but cannot be observed in logs. Awaiting response from Intel.
    • SSB reached O-RU. awaiting Awaiting analysis from Viavi.


    O-DU Low

    Primary Goals:  

    —Continue O-DU low and O-DU high pairwise test.

    —FAPI P7 massage integration -> Ongoing

    —Continue O-DU Low and O-RU emulator test.

    —Further CU plane testing -> Ongoing

    —Continue E2E test with UE simulator.

    —Support the UE attachment test

    —Development activity for Closed Loop Automation use-case

    —Support and test for cell stop and restart within O-DU High layers


    D Release Feature Scope: 

    PTL: @Zhimin Yuan
    • Status


    ...