Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 75 Next »

Updated:  23rd 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://wiki.o-ran-sc.org/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)
  • 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
      • 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.

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.
  • Viavi to confirm successful decoding of SSB/SIB1 at UE sim (TM500).


Updated:  16th 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 - WIP
    • 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 - 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 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-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 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-299 - WIP
    • 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://wiki.o-ran-sc.org/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
  • 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
  • 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
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.

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.
  • SIB1 PDSCH is detected at L1 but cannot be processed at L1.  Debug sessions to be continued to address this. This is blocker to acheieve radio mode integration.
  • Viavi to confirm successful decoding of SSB at UE sim (TM500).


Updated:  9th 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 - WIP
    • 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 - 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 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-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 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-299 - WIP
    • 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://wiki.o-ran-sc.org/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 under review
      • Code changes for Config update over F1 interface is completed
  • 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.
  • 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
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.

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.
  • SIB1 PDSCH is detected at L1 but cannot be processed at L1.  Debug sessions to be continued to address this.
  • Viavi to confirm successful decoding of SSB at UE sim (TM500).

Updated:  2nd 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 - WIP
    • 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 - 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 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-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 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-299 - WIP
    • 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://wiki.o-ran-sc.org/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 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/W requirements of Radisys CU
  • 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
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.

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.
  • SIB1 PDSCH reached L1 but cannot be observed in logs. Awaiting response from Intel.
  • Viavi to confirm successful decoding of SSB at UE sim (TM500).


Updated:  26th May 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.
      • 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-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/W requirements of Radisys CU
  • 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
      • Testing of broadcast messages at O-RU emulator set to begin
      • Awaiting input from Viavi

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.
  • SIB1 PDSCH reached L1 but cannot be observed in logs. Awaiting response from Intel.
  • SSB reached O-RU. awaiting analysis from Viavi.


Updated:  19th May 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-247 - Done
    • As an O-DU L2 developer, I want to Establish Netconf session for O1 interface for CM
  • https://jira.o-ran-sc.org/browse/ODUHIGH-297 - Done
    • As an O-DU L2 developer, I want to Establish Netconf session for O1 interface for CM
  • https://jira.o-ran-sc.org/browse/ODUHIGH-322 - Done
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
  • 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.
      • Resource allocation for SSB and SIB1 completed.
      • Msg1 to msg4 changes completed.
      • Resource table optimization in process
      • Reviewing other layers for relevant changes
  • 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
  • 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
  • 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
      • 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 of Radisys CU
  • https://jira.o-ran-sc.org/browse/ODUHIGH-327 - In review
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
  • 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
      • Testing of broadcast messages at O-RU emulator set to begin
      • Awaiting input from Viavi
  • https://jira.o-ran-sc.org/browse/ODUHIGH-328 - 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 analysis from Viavi.


Updated:  12th May 2021

JIRA: Epics Status below:

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 allocation to mount Radisys CU as a test fixture. Bare metal server preferred. 
  • 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.

Updated:  28th 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.
      • Resource allocation for SSB and SIB1 completed.
      • RACH allocation 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.
      • RACH allocation 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.
      • RACH allocation 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 under review
      • 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 w,r.t error observed at O-DU Low
  • 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. 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 allocation to mount Radisys CU as a test fixture. Bare metal server preferred. 
  • Unable to use valgrind with Intel libraries. Debugging must be carried out with Alternate methods.


Updated:  21st 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.
      • Resource allocation for SIB1 under review
  • 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 for SIB1 under review
  • 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.
      • Resource allocation for SIB1 under review
  • 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 under review
      • Cell delete functionality under review
      • Code changes for CU Interaction 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 w,r.t symbol allocation/overlapping
  • 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. 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 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.

Updated:  14th 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.
      • Resource allocation for SIB1 under review
  • 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 for SIB1 under review
  • 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.
      • Resource allocation for SIB1 under review
  • 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 clarifed.
      • UE delete functionality under review
      • Cell delete functionality under review
      • Code changes for CU Interaction 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. However basic configuration e.g. cell state/operational state/admin state shall be supported initially.
  • 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.

Updated:  7th April 2021

JIRA: Epics Status below:

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.


Updated:  31st March 2021

JIRA: Epics Status below:

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. 


Updated:  24th March 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.
  • SSB integration testing with O-DU Low in Radio mode. Awaiting debug session with Intel.


Updated:  17th March 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.


Updated:  10th March 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.

Updated:  03 March 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.

Updated:  24 February 2021

JIRA: Epics Status below:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA.

Updated:  17 February 2021

JIRA: Epics Status below:


Updated: 16 December 2020

Documentation and release related activities for Cherry release have been completed

Jira: EPICS Status below:

Dependency/Blockers:

  • Custom Yang files will be used for Dev activity.
  • FAPI files being used provided by INTEL, which is not completely in-line with the latest released version from SCF.



Updated: 9 December 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • Custom Yang files will be used for Dev activity.
  • FAPI files being used provided by INTEL, which is not completely in-line with the latest released version from SCF.



Updated: 2 December 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • Custom Yang files will be used for Dev activity.
  • FAPI files being used provided by INTEL, which is not completely in-line with the latest released version from SCF.


Updated: 25 November 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • Custom Yang files will be used for Dev activity.
  • FAPI files being used provided by INTEL, which is not completely in-line with the latest released version from SCF.


Updated: 18 November 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • HCL unable to merge O1 code into master branch.
  • Custom Yang files will be used for Dev activity.
  • FAPI files being used provided by INTEL, which is not completely in-line with the latest released version from SCF.


Updated: 11 November 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • Custom Yang files will be used for Dev activity.
  • FAPI files being used provided by INTEL, which is not completely in-line with the latest released version from SCF.


Updated: 4 November 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • Custom Yang files will be used for Dev activity but will not be checked-in to public repo.




Updated: 28 October 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • 3GPP Yang files will be used for Dev activity but will not be checked-in to public repo.



Updated: 14 October 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • in timer mode, Intel expects another prelim msg to be sent from O-DU High before config.REQ. This must be added to O-DU High referring to Intel's test stub(testMac).
  • 3GPP Yang files will be used for Dev activity but will not be checked-in to public repo.


Updated: 7 October 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • Code committer privileges not enabled for HCL committers yet.
  • Memory issues on enabling WLS
  • 3GPP Yang files will be used for Dev activity but will not be checked-in to public repo.


Updated: 30 September 2020

Jira: EPICS Status below:

Dependency/Blockers:

  • Code committer privileges not enabled for new committers yet.
  • Issues with linking O-DU high with O-DU low WLS and DPDK libraries.
  • 3GPP Yang files will be used for Dev activity but will not be checked-in to public repo.


Updated: 23 September 2020

Jira: EPICS Status below:

Dependency:

  • 3GPP Yang files will be used for Dev activity but will not be checked-in to public repo.


Updated: 16 September 2020

Jira: EPICS Status below:

Dependency:

  • Unable to install lib-sctp on Intel server to proceed with compilation.
  • 3GPP Yang files will be used for Dev activity but will not be checked-in to public repo.


Updated: 9 September 2020

Jira: EPICS Status below:

Dependency:

  • Integration with O-DU Low not started since ATT servers are not accessible.
  • 3GPP Yang files will be used for Dev activity but will not be checked-in to public repo.


Updated: 2 September 2020

Jira: EPICS Status below:

Dependency:

  • Integration with O-DU Low not started since ATT servers are unavailable
  • 3GPP Yang files will be used for Dev activity but will not be checked-in to public repo.


Updated: 26 August 2020

Jira: EPICS Status below:

Blocker:

  • Lack of clarity on usage of 3gpp Yang files for CM due to copyright issues

Dependency:

  • Integration with O-DU Low not started since ATT servers are unavailable


Updated: 12 August 2020

Jira: EPICS Status below:


Dependency:

  • Integration with O-DU Low not started since ATT servers are unavailable
  • Clarity on using netconf/VES for alarm notification as part of on-demand Health check



Updated: 13 May 2020

Jira: EPICS  Status is mentioned below:

Risks:

  • E2SM Specification baseline is still not available while the development is being done using below draft specifications.
    • ORAN WG3.E2AP v01.00
    • ORAN WG3.E2SM v01.00
  • WLS, FAPI interface files baseline - FAPI interface development is dependent on this. 
  • UE Attach Scenario development - Completed till msg-2,

Status:

Raised 18 change requests in WG8 AAD Specification; Already presented to the WG8 Task groups to be addressed in subsequent releases of the document.

O-DU High layers (MAC, RLC, and app):

  • Re-align seed code to 3GPP Release 15.3.0 - Done (completed for all the messages until msg-2)
  • Align seed code to WG8 AAD specification and interfaces - MAC - RLC Interface is done, RLC-F1AP interface is partially done (completed for all the data path messages)
  • 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
    • Cell Broadcast procedure - WIP
    • UE attach - WIP

F1-U interface development - Done

E2 Traffic Steering implementation based on draft specification - Done (with some limitations due to specifications)

F1-C interface enhancement:  Done (procedures identified for bronze released is done)

  • 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 - WIP (based on Intel FAPI 1.0.5 version)

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 of test infrastructure i.e UE or UE simulator, O-RU, O-CU, and core components.

===========

Updated: 23 April 2020

Jira: EPICS  Status is mentioned below:

Risks:

  • E2SM Specification baseline is still not available while the development is being done using below draft specifications.
    • ORAN WG3.E2AP v01.00
    • ORAN WG3.E2SM v01.00
  • WLS, FAPI interface files baseline - FAPI interface development is dependent on this. 
  • UE Attach Scenario development - Completed till msg-2,

Status:

Raised 18 change requests in WG8 AAD Specification; Already presented to the WG8 Task groups to be addressed in subsequent releases of the document.

O-DU High layers (MAC, RLC, and app):

  • Re-align seed code to 3GPP Release 15.3.0 - Done (completed for all the messages until msg-2)
  • Align seed code to WG8 AAD specification and interfaces - MAC - RLC Interface is done, RLC-F1AP interface is partially done (completed for all the data path messages)
  • 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
    • Cell Broadcast procedure - WIP
    • UE attach - WIP

F1-U interface development - Done

E2 Traffic Steering implementation based on draft specification - Done (with some limitations due to specifications)

F1-C interface enhancement:  Done (procedures identified for bronze released is done)

  • 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 - WIP (based on Intel FAPI 1.0.5 version)

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 of test infrastructure i.e UE or UE simulator, O-RU, O-CU, and core components.

===========

Updated: 10 April 2020

Risks:

  • E2SM Specification baseline is still not available while the development is being done using draft specifications
  • WLS, FAPI interface files baseline - FAPI interface development is dependent on this. 
  • UE Attach Scenario development - in medium risk due to the effort needed to complete the development

Status:

Raised 16 changes in WG8 AAD Specification; working with Ganesh to get them addressed in the next release of the document.

O-DU High layers (MAC, RLC, and app):

  • Re-align seed code to 3GPP Release 15.3.0 - WIP
  • Align seed code to WG8 AAD specification and interfaces - MAC - RLC Interface is done, RLC-F1AP interface is WIP
  • 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
    • Cell Broadcast procedure - WIP
    • UE attach - Open

F1-U interface development - Done

E2 Traffic Steering implementation based on draft specification - Done (with some limitations due to specifications)

F1-C interface enhancement:  Done (procedures identified for bronze released is done)

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

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 of test infrastructure i.e UE or UE simulator, O-RU, O-CU, and core components.



======

Updated: 26 March 2020

Risks:

  • E2SM Specification baseline is still not available while the development is being done using draft specifications
  • WLS, FAPI interface files baseline - FAPI interface development is dependent on this
  • UE Attach Scenario development - in medium risk due to the effort needed to complete the development

Status:

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

E2 Traffic Steering implementation based on draft specification - WIP

F1-C interface enhancement:  Done

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

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 of test infrastructure i.e UE or UE simulator, O-RU, O-CU, and core components.


  • No labels