Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

1. Architecture

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


2. Netconf server

The Netconf server functionality implemented for the Casablanca PoC shall be enhanced for Dublin. For completeness, the entire functionality available in Dublin is summarized below (including the implementation done for Casablanca).

2.1. Introduction

  • Honeycomb simulator shall be used to simulate the Netconf server. Suitable extensions will be made for it to communicate with the RANSim Controller.
  • Each netconf server will run as standalone process or in a Docker container.
  • The netconf servers will be spawned by RANSim Controller based on the topology specified.
  • Python scripts and client will seed the initial configuration for each Node.
  • Each netconf server can send a mount request to SDN-R when it is spawned.

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


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

  • ran-neighbor-list update notification will be sent by netconf server to SDN-R based on the trigger from RANSim Controller.
  • 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).
  • No labels