Our centralized provisioning server for dynamic onboarding of Southbound Network Elements and Northbound Tenants
A global IoT network, Nokia WING, required a provisioning interface that could automatically handle the subscriber provisioning across all the southbound network elements in sequence or parallel.
During the first phase of Centralized Provisioning Server development, the aim was to cover 3 provisioning interfaces over SOAP (Simple Object Access Protocol) and REST (Representational State Transfer adapters). Notably, Southbound Network Elements and Northbound Tenants were onboarded dynamically
The objective was to centralize the provisioning activities across multiple Tenants and multiple Network Elements in WING architecture.
This activity was mission-critical since the overall WING architecture required a complex and scalable solution to bring all the provisioning integrations to a single system for centralized and automatic tracking and monitoring.
Key business benefits delivered by Teliolabs
In terms of business benefits, the CPS venture produced:
- An end-to-end solution with seamless dataflow
- The ability to be deployed across cloud platforms
- A solution that can support one-to-one API mapping
- The option to onboard any 2 pairs of systems (different formats based) and facilitate their communication
The ability to support synchronous or asynchronous REST or SOAP API calls on both Northbound and Southbound
High-level solution framework used to resolve the issue
CPS acts as an interface and an interpreter between the NB onboarded tenant and the SB onboarded network elements. CPS works on REST/SOAP and accepts requests in either SOAP or REST from the tenant and converts it to the language the network element understands (REST or SOAP) to communicate with the tenant and uses call type onboarding.
For instance, if we have one calling system in SOAP and one in REST, CPS converts it accordingly in the language (SOAP/REST) used by the network element. CPS has the combination of SOAP/REST and converts into SOAP or REST. The onboarding system chooses communication language.
CPS also provides an interface to communication channels like Email and SMS to alert and notify the faults. Other integrations are done with third-party applications using HTTP calls or Database calls to prepare the Request parameters to be sent downstream.
For the project’s deployment, a dockerized cluster in Kubernetes was used. Meanwhile, Java and Spring were employed for microservices. The workflow engine of choice was Apache Camel, and Hazel cast was the In-Memory DB
The IoT and Telecom sectors will benefit the most from the project.
Notably, Nokia’s end customers, including ATT, CMP, and many more, will benefit from the collaboration.
Teliolabs has put in place a system that ensures top-notch project quality and delivery in record time. Owing to these qualities, the team was able to:
- Launch the beta version in just 3 months
- Deliver a multi-cloud supportive application
- Ensure scalability through microservices-based architecture
Produce reusable components for facilitating future releases