Release Notes

This document provides the release notes for the sim/o1-interface project.

Version history







Alex Stancu

“H” Release



Alex Stancu

“G” Release



Alex Stancu

“F” Release



Alex Stancu

“E” release



Alex Stancu

“D” release



Alex Stancu

“D” release



Alex Stancu

“D” release



Alex Stancu

Cherry release



Alex Stancu

Cherry release



Alex Stancu

Bronze release



Alex Stancu

First draft - Amber


The O1 interface simulator is a framework that provides simulated network functions (NF) with a management plane exposed through a NETCONF/YANG interface, using YANG models defined in O-RAN.

Release Data

version 1.8.1

  • [feature-add] new O-RU feature: monitoring NETCONF connectivity.

version 1.6.1

  • [feature-add] new O-DU docker image containing 3GPP YANG models. This needs to be built locally!

version 1.5.2

  • [feature-add] new VES O1 PNF Registration (stndDefined) message available. It can be enabled by using ves-o1-pnf-registration feature name.

version 1.5.0

  • [feature-add] new topology-service image available, with latest YANG specifications from OAM project. It exposes a RESTCONF endpoint with specific topology information as configured.

version 1.4.3

  • [feature-add] aligned o-ran-sc-du-hello-world YANG model

  • [feature-add] o-ran-du standalone mode with subscription-streams and performance-management-jobs streamlined

  • [feature-add] dynamic VES template generation with parameters and functions for o-ran-du

version 1.4.1

  • [feature-add] network-function dynamic operational datastore: when running in network-function mode, after the initial datastore population, NTS subscribes to all populated modules changes (running datastore), and whenever changed are detected, the operational store is dynamically updated accordingly

version 1.4.0

  • [update] datastore population code revised and rearragned and simplified wherever possible with various fixes

version 1.3.7

  • [feature-add] add SDN Controller CallHome IP different than the SDN Controller RESTCONF port. This is defined as a new ENV variable: SDN_CONTROLLER_CALLHOME_IP

version 1.3.6

  • [feature-add] add support for hostname addressing instead of IP for SDN Controller and VES Collector. A hostname can be specified instead of the IP address. If the Port ENV variables (i.e. SDN_CONTROLLER_PORT and VES_ENDPOINT_PORT) are not set for the NF, the URL for addressing the SDN Controller and VES Collector will be constructed without it (e.g. http://sdn-controller-hostname/rests/data…). If the Port ENV variables are set, they will be used when constructing the URL (e.g. http://sdn-controller-hostname:8181/rests/data…).

version 1.3.5

  • [feature-add] add support for NETCONF CallHome via TLS. Please note that this works only with ODL Silicon and above, because of API changes in the ODL CallHome module. 4335 is the port for CallHome via TLS. If any other port is used, CallHome via SSH will be used.

version 1.2.3

  • [change] moved all NETCONF x-paths to xpath.h for easier management and cleaner codebase

  • [feature-add] Manager now automatically tries to pull missing images (last version) when not found, if DOCKER_REPOSITORY env var is set to a certain Docker repository; note that repository authentication currently not supported

  • [feature-add] log-rotation application; does not include supervisor redirected paths, not stderr; log is hard-coded at ~5000 lines per file

  • [feature-add] host-mapping is now available when running NF is running in standalone mode via the NTS_NF_MOUNT_POINT_ADDRESSING_METHOD variable

version 1.2.1

  • [fix] VES commmon header made uniform across all VES-related messages

version 1.2.0

  • [change] Default password of the NETCONF Server was changed to “netconf!”, to be complant with O-RAN requirements

  • [feature-add] NACM (NETCONF Access Control Module) default configuration is now according to O-RAN WG4 requirements instead of disabled, like before

  • [change] Do not expose sysrepo internal YANG models in the yang-schema-list

  • [change] Provide both IPv4 and IPv6 addresses (if available) in pnfRegistration message

  • [change] Change ietf-system default configuration and web-ui URL (now points to ConfigApp in SDN-R)

  • [fix] Correctly construct URL for SDN Controller and VES Collector when they are addressed via IPv6

version 1.0.3

  • [fixed] fixed issues where ODL could not parse the correct versions for yang files

version 1.0.2

  • [fixed] bug that occured when trying to start a wrong instance (bad docker-repository or docker-tag)

  • [fixed] when populating the fault-delay-list, if the sum of all the faults was 0, the network funciton kept on generating faults and crashed

version 1.0.1

  • [feature-add] added web-cut-through feature

  • [fixed] mount-point-addressing-method was mistakenly changing after starting

version 1.0.0 Initial release.

Feature Additions

  • IPv6 for the simulated devices

  • NETCONF CallHome for the simulated devices

  • Manual notification generation

  • Custom naming of the simulated devices

Bug Corrections

  • ssh-connections and tls-connections leafs are now removed from the simulator-config

  • fault-notification-delay-period has now the attribute ordered-by user


Software Deliverables

The following docker containers are the resulting artefacts of the sim-o1-project:

  • o-ran-sc/ntsim-manager - this image contains the NTS Manager, which handles the simulation environment;

  • o-ran-sc/ntsim-o-ran-fh - this image contains a simulated device which exposes a management interface via NETCONF/YANG, implementing the O1 FH interface specifications;

  • o-ran-sc/ntsim-x-ran - this image contains a simulated device which exposes a management interface via NETCONF/YANG, implementing the X-RAN Management interface.

  • o-ran-sc/ntsim-o-ran-ru-fh - this image contains a simulated device which exposes a management interface via NETCONF/YANG, implementing the O-RU FH YANG models, as per the November 2020 train;

  • o-ran-sc/ntsim-o-ran-du - this image contains a simulated device which exposes a management interface via NETCONF/YANG, implementing the O-DU YANG models;