Skip to content

Introduction

NSPS Connector Implementation Guide provides implementation and configuration guidance for partners who want to integrate their external network systems with NSPS using Docker microservices. Topics such as monitoring, high availability, disaster recovery, or other operational and infrastructure-related aspects are out of scope of this guide — consult the solution architect responsible for your deployment.

Provisioning System Overview

The system consists of:

  • PortaBilling: Generates events (e.g., customer creation, service activation) and sends them via webhooks.
  • Cloud Provider: Represents the infrastructure environment (such as GCP, OCI, AWS, etc.) where NSPS is deployed. It provides cloud services for monitoring, logging, and hosting all system components.
  • External Network Systems (e.g., HSS, PCRF, etc.): Receive updates via proprietary API based on the incoming events.
  • NSPS (New Service Provisioning System): Processes events, enriches data, and provisions the necessary external network systems.

NSPS automates provisioning and service updates in external network systems when changes occur in PortaBilling — including service activation, deactivation, and configuration updates. NSPS is a lightweight tool for cloud provisioning, designed to handle basic provisioning flows. For complex workflow logic, consider PortaOne Workflows instead.

The connector is a microservice that receives enriched events from NSPS (which has already added the necessary data from PortaBilling), selects the necessary parameters, and sends them to the external system in the required format.

The interaction of the components is shown in the diagram below:

flowchart LR
    A[PortaBilling] -->|Event| B
    B <-->|Enrich event with SIM, Account, etc.| A
    B -->|Send enriched event| C
    C -->|Provision| D[External Systems]
    subgraph Cloud1[Google Cloud]
        B[NSPS]
    end
    subgraph Cloud2[Google Cloud, Azure, Amazon, etc.]
        C{Connector}
    end