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 3 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. Necessary extensions have been made for it to communicate with the RAN-Sim Controller.
  • Each Netconf server will run as standalone process or in a Docker container.
  • The Netconf servers will be spawned by RAN-Sim 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.
  • Maximum number of cells connected to a Netconf server is configurable (currently configured as 16).

2.2. Handle inputs from RAN-Sim controller

  • 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 server to SDN-R 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 RAN-Sim Controller.
  • No labels