...
- This is a Springboot based micro-service.
- RAN topology of ~2000 cells to be simulated is defined into a Config configuration DB.
- RAN Simulator spawns the netconf servers based on this topology.
- Exposes following rest APIs for GUI to:
- Retrieve the current topology
- Update phy-cell-id of a cell to simulate collision or confusion
- Update neighbor list to simulate collision or confusion (in the table view)
- Receive the new phy-cell-id set by SDN-R (after PCI optimization, or otherwise)
- Start/Stop the network simulation
- 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 Config configuration DB to store the topologyRobot 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.
4. RAN-Sim GUI
4.1. Assumptions
- For initial setup, an input file containing foll. info shall be used
- Cell Id
- PNF name (though this has really no relevance to the GUI)
- Cell position = {0,1,2,3} 0=>no sectors, 1-3 denotes sectors
- PCI value
- (x,y) = mapping to a co-ordinate on the canvas from (lat,long)
- Neighbor list (ordered list of (cell id, PCI))
- Canvas view and ‘on-click’ views possible
- Editable contents: neighbor list (in graphical view), PCI value (in graphical view)
- Maximum 3 cells in a single location
- All cells are assumed to be of same size, i.e., path loss, etc. are not considered.
- Option provided for user to pause before seeing the changed PCI values.
- Only 1 iteration of PCI/neighbor list change will be performed.
4.2. Illustration of GUI
4.2.1. Canvas view when a neighbor list of a cell is updated
4.2.2. Canvas view when a neighbor list of a second cell is updated (OOF is not yet triggered)
4.2.3. Details of a particular cell (on click view)
