Skip to content
Themistoklis Anagnostopoulos edited this page Sep 3, 2020 · 8 revisions

South Bound Interface

South Bound Components

  • VIMs: Register the VIMs in each location of the platform that will be used in each location for hosting network services as part of network slices
  • NFVOs: Register the NFVOs in the platform that will be responsible for the management of the network services
  • WIM (Optional): Register the WIM in the platform that will be responsible for managing the Transport Network part of the Slice. If no WIM is added during a slice creation phase, the slice will still be created, but the Transport Network will not be configured
  • EMS (Optional): Register the EMSs that will be responsible for configuring the RAN functions that will be part of the Slice. If no EMS is added during a slice creation phase, the slice will still be created, but the RAN functions will not be configured
  • PDUs (Optional): Register the PDUs in the platform that will be used for hosting PNFs. It is mandatory to add a PDU if the slice includes the deployment of PNFs

Supported Components

Current version of the Slice Manager supports the following components:

VIM NFVO WIM EMS PDU
OpenStack (Queens, Rocky & Stein) OSM (5 - 8) Athens Platform ODL WIM Athens Platform Amarisoft EMS Any
OpenNebula

Katana Slice Manager communicates with these components using REST APIs

Component Configuration Files

Clone this wiki locally