5G Network Slicing is a new concept to allow differentiated treatment to network traffic depending on each customer's or use case’s requirements. With slicing, it’s now possible for Mobile Network Operators (MNO) to consider customers or use cases as different context types with each having different service requirements. These requirements are governed in terms of what slice types each context is eligible to use based on Service Level Agreements and subscriptions. In order to orchestrate and manage 5G network slicing, the Linux Foundation Open Network Automation Platform (ONAP) project has come with E2E slice management architecture with different choices based upon various 3GPP defined components with specific roles (e.g CSMF, NSMF, NSSMF). In this blog, we shall uncover the architecture of NSSMF and its interaction with other components.
3GPP 3rd Generation Partnership Project
BSS Business Support System
E2E End to End
CSMF Communication Service Management Function
NSMF Network Slice Management Function
NSSMF Network Slice Subnet Management Function
NSI Network Slice Instance
NSSI Network Slice Subnet Instance
ONAP Open Network Automation Platform
OSS Operations Support System
SO Service Orchestrator
5G ONAP Network Slicing
In ONAP, options 1 & 4 from the various slice management architecture choices are supported — see Figure-1.
Figure-1: Slice Management Architecture Choice
Essentially, the choices have evolved from the requirements of service providers and open source community contributors. In Architecture Choice#1, CSMF, NSMF, and NSSMF are internal components of ONAP in reference design and implementation. In this option, OSS/BSS can integrate with the runtime component CSMF hosted in SO for business and operational needs. In Choice#4, CSMF and NSMF are internal components of ONAP and hosted in a runtime component called SO. In Figure-1, CSMF takes the business requirements from OSS/BSS and transforms communication service requirements to network slice requirements and is consumed by NSMF. Moreover, NSMF is responsible for the management and orchestration of NSI and derive network slice subnet requirements. In choice#4, NSSMF is an external component and is responsible for the management and orchestration of NSSI. ONAP has implemented standard APIs defined by 3GPP towards NSSMF and the same is  listed below in Table-1.
Table-1: NBI Interface exposed from NSSMF towards NSMF
As we uncover architecture choice#4, NSSMF performs communication with the ONAP NSMF component and that integration is done using the standard RestAPI interface as per Table-1 shown above. In our NSSMF architecture as shown below in Figure-2, consists of various elements and is defined as:
● NBI Interface: This is the reception point for all the incoming requests from NSMF using the RestAPIs as detailed in Table-1.
● Model Validator: This component validates the incoming NSMF requests with predefined models for various lifecycle events of a slice.
● NSS Manager: Network Slice Subnet manager decides the role of processing the incoming request in Asynchronous or Synchronous flow mode.
● Egress Manager/Ingress Manager: NSSMF is defined with two internal roles. First being a forwarder and second as a receiver. This helps in a distributed model for processing slice events.
● CnCfgManager: The core network configuration manager is responsible for processing the slice events received from the Ingress manager for event types as AllocateNSSI, ActivateNSSI, DeactivateNSSI, and DeAllocateNSSI. Core network configuration manager was built with the support of NETCONF client and RESTCONF interface to cater deployment of network functions (NF) as PNF and CNF respectively.
Figure-2: NSSMF as external to ONAP (Choice#4)
We have done a webinar on deep dive on NSSMF architecture wherein we talked about insights and how the slice event lifecycle is processed by NSSMF and provisioning a commercial 5GC Network functions with a demo. You can refer to the video link: https://lnkd.in/gHvyFhx for details. Also, if you want to try out this NSSMF in your setup, reach out to us at firstname.lastname@example.org
● 3GPP TS 28.541
● 3GPP TS 28.531