Skip to main content

TDD Reconfiguration

This flow illustrates how a rApp initiates a request to update TDD (Time Division Duplexing) configurations in the access network. The process involves interaction between the TDD rApp, OAM, and the gNB.

TDD flow

Overview​

A TDD configuration change is initiated by the TDD rApp developed on the top of BubbleRAN's rApp SDK. The rApp first queries the current network specification from the Non-RT RIC by providing a networkID. The Non-RT RIC responds with the corresponding networkSpec, which includes the existing TDD configuration.

Based on this information, the TDD rApp prepares an updated network specification reflecting the desired TDD parameters (e.g., updated DL/UL slot/symboles). This modified networkSpec is then submitted back to the OAM as part of an apply request.

The OAM pushes the new TDD configuration to the appropriate gNBs. As part of the update process, the gNB will be restarted to apply the new TDD settings. Once the update is complete, a confirmation is sent back to the TDD rApp.

Sequence of Operations​

  1. Get Network Specification

    • TDD rApp → OAM
    • Interface: R1 - SDK
    • Action: Send Get Network Request for a specific networkID
    • Response: Receive the current networkSpec describing the existing TDD configuration

  2. Modify TDD Configuration

    • Change TDD pattern and prepares a new networkSpec

  3. Apply Updated Configuration

    • TDD rApp → OAM
    • Action: Send Apply Network Request with the updated networkSpec for the same networkID
    • OAM → gNB: Executes the Update TDD configurations on the radio node

  4. Confirmation

    • OAM → TDD rApp
    • Action: Return Apply Network Response confirming the update

You can run the TDD reconfiguration rApp and observe this workflow in the rApp training lab.