...

The updated architecture of the RAN-Simulator for ONAP Dublin is illustrated below.

Image RemovedImage Added

2. Netconf server

...

2.2. Handle inputs from RAN-Sim controller

• Netconf server sends a nbrlist-change notification will be sent by Netconf server notification to SDN-R based on the trigger from RAN-Sim Controller (, when a cell's neighbor list is updated).
• netconfNetconf server sends a netconf-config-change notification will be sent by Netconf server to SDN-R when triggered by RAN-Sim Controller, when a cell's PCI value is updated.
• Netconf server sends an alarm message to VES Collector for collision/confusion (and clearing) when triggered by the RAN-Sim Controller.
• Netconf server sends PM data to VES Collector when triggered by the RAN-Sim Controller.
• PM and FM data formats are provided below.

2.3. Handle inputs from SDN-R

• The Netconf server will be able to accept 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 forward same forwards it to RAN-Sim Controller.

3. RANSim Controller

• This is a Springboot based micro-service
• RAN topology of ~2000 cells to be simulated is defined into a Config 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 confusion
  3. Update neighbor list to simulate collision or confusion (in the table view)
  4. Receive the new phy-cell-id set by SDN-R (after PCI optimization, or otherwise)
  5. Start/Stop the network simulation
• MariaDB will be used as the Config DB to store the topology
• Robot scripts will drive the test sequences
• 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.