NSSF Architecture

NSSF comprises of various microservices deployed in Kubernetes based Cloud Native Environment (CNE, example: OC-CNE) . Some common services like logs or metrics data collection, analysis and graphs or charts visualization, etc. is provided by the environment. The microservices integrates with them and provide them necessary data. The following diagram describes the overall architecture of the NSSF:

Figure 2-1 Network Slice Selection Function Architecture Diagram

The solution has the following components:

• NS-Gateway (NSG):This microservice distributes among the NSSelection and NSConfig microservices. NSG is also responsible to pegging traffic related measurements. It also provides support for API life cycle.

  Note:

  API Gateway Ambassador is used to implement NS-Gateway.

• NS-Selection MicroService (NSS): This micro-service receives all traffic for NS Selection Service. The micro-service validates and pre-processes NS Selection query requests before forwarding it to NSPolicy service. NSS parses and validates Get request parameters for initial registration and PDU session establishment messages. It also forwards response back to NS-Gateway.

• NS-Policy MicroService (NSP):

  This microservice performs the policy decision based on operator configured policy rules.

• NS-Config MicroService (NSC):

  This microservice is responsible for configuring NSSF managed objects. NSC also implements a REST messaging server that receives configuration HTTP messages, validates and stores the configuration in the database.

• NS-Registration MicroService (NSR):

  This microservice registers with the NRF and sends periodic heartbeats.

• Data Service

  The data service is deployed by the CNE provider. It is a common CNE service with persistent data storage and highly available clustered MySql. The OCNSSF microservices create their data store using the Data Service upon initialization.