Versions Compared

Key

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

...

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


Image RemovedImage Added

2. Netconf server

...

  • Honeycomb simulator shall be used to simulate the Netconf server. Suitable Necessary extensions will be have been made for it to communicate with the RANSim RAN-Sim Controller.
  • Each netconf Netconf server will run as standalone process or in a Docker container.
  • The netconf Netconf servers will be spawned by RANSim RAN-Sim Controller based on the topology specified.
  • Python scripts and client will seed the initial configuration for each Node.
  • Each netconf Netconf server can send a mount request to SDN-R when it is spawned.
  • Maximum number of cells connected to a Netconf server is configurable (currently configured as 16).

2.2. Handle inputs from RAN-Sim controller

...

2.3. SDN-R -> RAN-Sim controller flow

...

  • nbrlist-change notification will be sent by Netconf server to SDN-R based on the trigger from RAN-Sim Controller (when a cell's neighbor list is updated).
  • netconf-config-change notification will be sent by netconf Netconf server to SDN-R based on the trigger from RANSim Controller.The netconf when triggered by RAN-Sim Controller, when a cell's PCI value is updated.

2.3. Handle inputs from SDN-R

  • The Netconf server will be able to accept phy-cell-id update trigger from SDN-R and forward same to RANSim Controller.Maximum number of cells connected to a netconf server is configurable (currently configured as 16)RAN-Sim Controller.