Change Log:

Terms and definitions::

Purpose of Document

This document provides an overview of features introduced in Release 6.0 of the NRDB Number Porting project, as well as providing details of any required configuration.

Introduction to Functionality

The purpose of the NRDB Number Porting project is to facilitate number porting for Norwegian customers, using the NRDB framework. Release 6.0 of the NRDB Number Porting project includes a number of refactoring changes, deprecating some very old functionality and bringing the project more in line with Core 11 implementation principles.

Deprecated Logic

The following components should be considered deprecated, and should be avoided if at all possible. While not all the logic in these components has been converted into actions at this time, it is strongly recommended to consider doing so when updating or creating workflows that are meant to use any of the functionality provided by these components.

• WfCNumberExportNorway

• WfCNumberPortabilityNorway

WfCNumberExportNorway

checkAnumber

checkAnumber checks if the number that requested outported is allowed to be outported and if it is not it sets different reject code to the RSP depending on the reason. The logic of this method should be handled using workflow actions instead. The logic for cancelling existing export flows has been moved to a new action, com.CDRator.billing.np.no.action.CancelNpExport (see details below.) The customer validation logic has been moved to a new action, com.CDRator.billing.np.no.action.ValidateNpExport (see details below.)

anbesHasBeenReceived

This method checks if an NRDBMessageType of code 122 (ANBES) has been received for the current np export flow. It has been replaced by a new action, com.CDRator.billing.np.no.action.HasReceivedNRDBMessageOfType (see details below.)

sendGodk

Creates a NRDBMessageType of the type NP_GODK unless an NP_ANBES has been received in which we then redirects the flow to send a NP_KABES.