How does NSP enable service management?

Service management for NSP

NSP's service management function allows for service provisioning and activation across networks accessible to the NSP. Through the GUI, or through the northbound interface (RESTConf), NSP enables users to make service requests that deploy services to the network using the NSP’s mediation framework.

A library exists with a predefined set of service models (such as L3 VPN, EVPN, C-Line, E-LAN, E-TREE, E-Line and IES services) for both classic and model-mode SROS networks. These service models can be installed and utilized by the built-in, intent-based engine (NSP’s Network Intents views) to provide assurance that service configuration is as planned/requested, and also easy adaptability for custom service model requests. New service models to support custom needs can also be developed with aid of the NSP’s automation practice team — or, if your deployment includes the NSP’s programmability suite, self-development.

Note: This library of predefined service models (intent types) is obtained from the artifacts section of the Nokia Support Portal, however, customers should consult with Nokia prior to deploying these in live networks, in order to ensure that they will suit their needs. The models are contained in the NSP_Product_Service_Artifacts_<Rr>.zip file and must be installed using NSP's network intents function before being imported into the service management views. An important readme file is also bundled with the models.

Note: NSP's service models are composed of yang modules. Users can create additional yang modules with the intention of augmenting the existing service models, which may result in custom parameters being configurable from NSP. Visit the Nokia Network Developer Portal for more information about extending the operational service models.

Network abstraction is used to simplify how the network appears to the IT/OSS layer and users of NSP's service management function. This allows services to be defined and enhanced more quickly by presenting only the network service attributes and endpoints that are relevant to a specific customer's needs, thereby streamlining service fulfilment operations.

Service management provides real-time, service-related inventory, including available Ports, LAGs, and Service Tunnels (SDPs). This allows users to view the availability of resources in the network before beginning the fulfilment process. Service offerings with customer-centric naming can be created by the user, thereby enabling dynamic creation of the service catalogue based on installed service models. NSP supports the configuration and deployment of services on third-party devices.

Users have granular control over a service's entire life cycle. This allows them to define services without deploying them into the network, to plan services so that resources are reserved within NSP, to deploy services in the network that are fully synchronized with the intended configuration, or even to remove services from the network without deleting them entirely. users can also view all services that are in the various life cycle states, as well as view the real-time operational state of deployed services.

Service topology views are available within the service management network map, but users are also provided with the ability to easily navigate to the NSP’s Network Map and Health views in order to see multi-layer topology maps and accomplish additional assurance tasks.

To ensure that intended service configurations are maintained in the network, users can audit individual services in order to view and correct any deviations, thereby ensuring configuration assurance in addition to operational assurance.

Automation is achieved using NSP's workflows function. During a service's life cycle, a workflow can be invoked to carry our specific tasks. For example, when planning a service a workflow could be invoked prior to deployment that would pre-configure policies into the network. Alternatively, when removing a service from the network, a workflow could be invoked to ensure that OAM tests and/or telemetry subscriptions are paused. Automation of user-focused workflows can also be invoked through those views, or via API on an ad-hoc basis against the services.

Use subject to agreed restrictions on disclosure and use.