Versions Compared

Key

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

...

  • Netconf server accepts phy-cell-id update trigger from SDN-R and forwards itto RAN-Sim Controller.
  • Netconf server accepts neighbor list (HO allowed) update trigger from SDN-R and forwards it to RAN-Sim Controller.

3.

...

RAN-Sim Controller

  • This is a Springboot based micro-service.
  • RAN topology of ~2000 cells to be simulated is defined into a configuration DB.
  • RAN Simulator spawns the netconf servers based on this topology.
  • Exposes following rest APIs for GUI to:
    1. Retrieve the current topology
    2. Update phy-cell-id of a cell to simulate collision or confusionconfusion (this will also result in an alarm being sent to SDN-R via Netconf server).
    3. Update neighbor list to simulate collision or confusion (in the table view) (this will also result in an alarm being sent to SDN-R via Netconf server).
    4. Receive the new phy-cell-id set by SDN-R (after PCI optimization, or otherwise)
    5. Start/Stop the network simulation
    6. Start/stop generation of PM data for the network. Flexibility to specify which cell(s) should have poor/bad performance.
  • MariaDB will be used as the configuration DB to store the topology.
  • RAN-Sim Controller shall also send a alarm clear notification upon collision/confusion getting resolved due to PCI update(s) and/or ANR update(s) from SDN-R (received from Netconf server).
  • Web GUI will show the current topology, phy-cell-id collision/confusions (using different color codes), ran-neighbor-list.
  • Basic pictorial representation will be provided, improvements will be a stretch goal.

...