/
ODU High Status

ODU High Status

Nov 17, 2021

Updated: 17 Nov 2021

JIRA: Epics Status below:

Updates from HCL:

Dependency/Blockers:

 Blocked for PTP grandmaster at OSC lab to start the end to end integration activities

 

 

Updated: 20 Oct 2021

JIRA: Epics Status below:

Updates from HCL:

Dependency/Blockers:

 Blocked for PTP grandmaster at OSC lab to start the end to end integration activities

 

Updated:  15th Sept 2021

JIRA: Epics Status below:

Updates from HCL:

Dependency/Blockers:

 Blocked for PTP grandmaster at OSC lab to start the end to end integration activities

Updated:  7th July 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 - Done

    • As an O-DU L2 developer, I want to add support for Mu1

      • Code changes at DU APP completed.

      • Resource allocation for SSB to msg5 completed

      • Code changes for UE registration flow in progress

      • Updates to k0, k1, k2 in progress

  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - Done

    • 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 to msg5 completed

      • Code changes for UE registration flow in progress

      • Updates to k0, k1, k2 in progress will be continued in E release

  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - Done

    • As an O-DU L2 developer, I want to add support for TDD mode

      • Code changes at DU APP completed.

      • Resource allocation for SSB to msg5 completed

      • Code changes for UE registration flow in progress

      • Updates to k0, k1, k2 in progress will be continued in E release (Irrespective of FDD or TDD stack)

  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - Done

    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case

      • 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. Call flow updated at 

        https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/Closed+Loop+Automation+Call+Flow+-+O-DU+High+APIs.

      • 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 is completed

      • Code changes for Config update over F1 interface is completed

      • O1 Integration for O-DU  for CLA is completed ( Cell stop and Cell restart)

      • Blocker : code segmentation is observed, analysis is going on (code optimization is required to be scoped in E release)

  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - Done

    • 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.

      • PDSCH for SIB1 is detected at L1 but L1 does not process it. Pointer is to check the PDSCH PDU parameters

      • Further debug sessions needed to close the ongoing issues.

      • There is no breakthrough even after several debug sessions with O-DU Low

      • SIB1 detection at L1 is successful. PHY.XML is updated with removing the hardware accelerator (<dpdkBasebandFecMode> from 1 to 0 to force the SW encoder)

      • For the CLA usecase, Cell stop request is received from O-DU high to low but O-DU low sends stop indication multiple times. This issue is fixed in L1 later binary 20.08. This binary update will happen in D-maintenance phase. 

  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - Done

    • 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 configured as per H/W and S/W requirements of Radisys CU

      • The Network interfaces and CentOS version needs to be revisited for the CU machine. This is achieved with limited OSC lab setup.

  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - Done

    • 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

      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.

      • Debug session is planned on 23rd June to achieve SSB and SIB1 transmission till UE simulator and then follow with RACH procedure.

      • Latest issue: the eCPRI packets differentiation between control plane and user plane through vlan id is supported by Intel, however O-RU support the packet differentiation based on eCPRI packet type. hence the fronthaul transmission validation is blocked.

      • Intel shall update the L1 package supporting C/U plane differentiation using eCPRI packet type in the D-release maintainance phase.

Updates from HCL:

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.

  • Intel/Viavi to confirm successful decoding of SSB/SIB1 at UE sim (TM500).

 

Updated:  30th June 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 - Done

    • As an O-DU L2 developer, I want to add support for Mu1

      • Code changes at DU APP completed.

      • Resource allocation for SSB to msg5 completed

      • Code changes for UE registration flow in progress

      • Updates to k0, k1, k2 in progress

  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - Done

    • 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 to msg5 completed

      • Code changes for UE registration flow in progress

      • Updates to k0, k1, k2 in progress will be continued in E release

  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - Done

    • As an O-DU L2 developer, I want to add support for TDD mode

      • Code changes at DU APP completed.

      • Resource allocation for SSB to msg5 completed

      • Code changes for UE registration flow in progress

      • Updates to k0, k1, k2 in progress will be continued in E release (Irrespective of FDD or TDD stack)

  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - Done

    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case

      • 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. Call flow updated at 

        https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/Closed+Loop+Automation+Call+Flow+-+O-DU+High+APIs.

      • 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 is completed

      • Code changes for Config update over F1 interface is completed

      • O1 Integration for O-DU  for CLA is completed ( Cell stop and Cell restart)

      • Blocker : code segmentation is observed, analysis is going on (code optimization is required to be scoped in E release)

  • 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.

      • PDSCH for SIB1 is detected at L1 but L1 does not process it. Pointer is to check the PDSCH PDU parameters

      • Further debug sessions needed to close the ongoing issues.

      • There is no breakthrough even after several debug sessions with O-DU Low

      • SIB1 detection at L1 is successful. PHY.XML is updated with removing the hardware accelerator (<dpdkBasebandFecMode> from 1 to 0 to force the SW encoder)

      • For the CLA usecase, Cell stop request is received from O-DU high to low but O-DU low sends stop indication multiple times. This issue is fixed in L1 later binary 20.08. This binary update will happen in D-maintenance phase. 

  • 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 configured as per H/W and S/W requirements of Radisys CU

      • The Network interfaces and CentOS version needs to be revisited for the CU machine.

  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - WIP

    • As an O-DU L2 developer, I want to support End to End testing scenarios