Anda di halaman 1dari 24

MNP Solution

FSUE ZNIIS
June 2015

Fixed
Operators

The general circuit of mobile number portability service


PBX

The donor
operator
Mobile
Operators

MSC

SRF

The recipient operator


MSC

DB

HLR

Operator
NPDB

MSC

NPCDB

Federal State
of
Communicatio
ns

HLR

DB

The
operator
SRF

Numbering
Resource
Register

SRF

HLR

Synchronization of the data with the register of a numbering resource


Replication of the data on a mobile communication network
Logic of request of the data and connection establishment in mode OR
Logic of request of the data and connection establishment in mode ACQ
2

DB

Interaction NPDB (Number Portability DataBase) with the


numbering resource register
Regulator State

NPDB Operator

The numbering register contains the


NPDB contains the information to what
information to what operator and the
operator the numbering resource is
resource of numbering is selected for what
transferred
territory
Database of the
The numbering
NPDB
numbering register
register
The information on a numbering
resource
The information on resource change
The legal status
Conducts the numbering register
Carries out the quarterly publication of
the register
Supports a database of the numbering
register

Statistics, analytics

The question of transferred numbers


database interaction with a numbering
register database is worked

Interaction of NPDB operator with operators of mobile telephone communication is


carried out in the course of number transfer, participants of process are both technology
professionals of the companies, and workers of sales offices and cellular communication
salons

Interaction
To avoid handling of
requests about number
transfer manually,
management NPDB
system should interact at
least with two types of
information systems of the
mobile communication
operator:
Management system of
mutual relations with
clients (CRM)
And the automated
system of calculations
(Billing)

Complexity

FSUE ZNIIS solution interact with


following

128 operators

It is necessary to organize interactions


with 62 mobile communication operators
and with 66 MVNO operators, each of
which can have some systems CRM and
Billing
Bulkiness

More than 200 systems


Each such system can have the unique
format of the data, to be constructed on
various program platforms or not to be
subject to upgrade

Scale

More than 50000 offices


It is necessary to connect more than
50000 sales offices and salons of cellular
communication, system of subscribers
registration in separate regions can differ

System engineering and development of protocols and


interfaces specifications
The purpose
and results of
operation

Experts

The system project defining the functional and


technical architecture of NPDB, and also
mechanisms of reliability support and safety of
functioning NPDB
Protocols and interfaces specifications of
interaction NPDB with technical and software
of mobile operators
The rules interactions (project)
The project custom lists on the server
equipment and the software
RFP on design engineering
RFP on software development

Operation should be carried out


together with the supplier of the
software

From ZNIIS: system designers, experts


concerning designing of business
processes, safety, reliabilities; management,
architects of a software, technology
professionals

Interaction with operators of mobile


communication is necessary for
beginning at once with the first
development cycle (a format Working
group)

5
5

The coordination of decisions with operators


The purpose
and results of
operation

The coordinated order and the rules of


interaction of NPDB operator with
telecommunications operators at all stages
of number porting
The coordinated technical decisions
regarding the organization of interaction of
hardware-software complex NPDB with the
equipment of telecommunications
operators (communications mediums,
systems OSS/BSS)
The coordinated specifications of
interaction protocols
The coordinated plan of hardware upgrade
and software of telecommunications
operators

Operation should be
carried out within the limits
of Working group with
involvement of experts
ZNIIS and operators of
mobile communication

6
6

Design engineering, civil work and equipment purchase


The purpose
and results of
operation

Binding lines

Competition

As the head executor the


company - the integrator is
preferable

The design and working documentation for carrying out


building and installation works
Custom technical specifications of the equipment and
the software, and also purchasing lists
The budget documentation
The equipped locations on two objects:
In Moscow and St.-Petersburg
The mounted equipment
The equipped lines of a binding to communication
networks and electrical supplies
Creation of bindings lines can be broken into two stages:
on the first there are base lines, on the second reserve.
The termination date of the first stage should be anchored
to the beginning of equipment installation. Period of the
second stage to a trial operation expiry date
For the purpose of operations acceleration it is offered to
produce the competition declaration at once upon
termination of the first stage - system engineering
It is expedient to unite design operations with operations
on building and mounting, and also delivery of the
equipment within the limits of one competition

7
7

Software development
The purpose
and results of
operation

Software developed and adapted:


According to order of number porting in
territory of the Russian Federation
According to the developed protocols
specifications of interaction with
information systems and a data model
According to the developed business
processes
According to requirements to GUI staff
workplaces
The program of operations and road map on
software development
The program and user documentation
System of support of development and control
of versions

Development and adaptation is


carried out by FSUE ZNIIS with
engaging of regular staff

8
8

Allowing documents and licenses


The purpose
and results of
operation

Necessary licenses for activity realization on


rendering of a telecommunication service
Certificates and declarations on the equipment
The registered passports on objects of building
The state expert appraisal inferences
Licenses for the software
Other licenses
The necessary documentation for object
delivery in maintenance

The list is specified at a system


engineering stage

9
9

Preparation and staff training


The purpose
and results of
operation

Training

The prepared staff according to the list of staff


and the installed qualification requirements
The program of training and staff preparation

The staff dial-up is carried out


stage by stage, since the first
stage of performance of
operations on creation of NPDB
operator

The equipment provider should provide following


types of training:
Training of operational staff
Training of a support service staff
Training of programmers
Training of two teachers at basic courses

10
10

Testing and experimental zones


The purpose
and results of
operation

Testing

The connected networks of


telecommunications operators
Waste procedures of interaction with the
equipment of telecommunications operators
Waste operational business processes

Tasks of experimental zones


are specified at a system
engineering stage

Begins with large operators


It is led it is subject
Includes the load and functional tests
By results of testing finishing of a software and
adjustment of business processes is carried out

11
11

Hardware architecture of FSUE ZNIIS MNP solution

12
12

Numbering
The
The
register
register

Access
Access
of
of the
the
third
third
parties
parties

Web
Web a
a
portal
portal

Access
Access of
of
operators
operators

ns
es
pe
ra
to
rs
fo

Li
ce

to

lis

g
ns
io
rin
c is
be
ns
m
De
io
nu
at
of of nic , n
s
u rs o
an
m to e
Pl
m ra nc nt
co e e e
le op erg em
te
nv olv
Co inv

Creation of the
numbering
database providing
the analysis of
efficiency of
resource usage
the first step of
formation of
practical expertize
of FSUE ZNIIS in
the field of crucial
resources usage

Roskomnadzor
Roskomnadzor

Th
e

Register
Register
guiding
guiding

DB
DB

NPDB
NPDB

Operators and other clients

Services
Online access to the master data
.164
CONSTRUCTION DEPARTMENT 7
MNC
The plan of transferred numbers
Online access to the bound data
.164 And URI
.164 And routing numbers
Web-accessto system and the bound data

Registration of changes in the register


(For NPDB operator)
Register guiding
Guiding of the plan of numbering of a
communication network
Provision GUI for guiding of the plan and
depositing of convergence on involvement of
number capacity
Guiding of the plan (outsourcing)

Access to basis of Federal Agency of


Communications resolutions
The Online

Web

Elimination of intersections
Extracts
13

Project Tasks (step-by-step diagram)


#

Task

Preliminary
Requirement
Definition

On-site survey
Functional
Specifications
Modeling
Technical
specification
validation with
customer

Task end
Task
(weeks
Locatio duratio
from
n
n
contract
(weeks) signature
)
Off-site

Input conditions for


task start

Deliverables

Documents submitted
to customer
acceptance at the end
of the task

Signed contract

Full list of business processes to be


implemented in the MNP System,
specifications and instructions

On-site survey plan


containing the list of
interviews and
interviewed persons

On-site

Availability of
stakeholder
for interviews

Off-site

12

20

Signed contract

On-site

22

Signed description of
acceptance criteria of
technical specifications

Development &
Testing

Off-site

28

50

Deployment and
Provisional
Acceptance

On-site

54

Training

On-site

60

Pilot production

On-site

64

Defect fixing

Off-site

56

10

Three-year
technical
support

Off-site

156
(3
years)

Signed Technical
specifications,
Signed System Design,
Architecture
specification
Signed test scripts,
Signed user guide,
Signed admin guide,
Availability of HW
equipment on site
Signed training
program, rooms,
trainees
Signed Act of
Provisional Acceptance,
Signed Protocol of users
training
Signed methods of
solving defects
Approved mechanism
(protocol) receiving
requests and bug fixes

Detailed work plan, user cases,


Description of acceptance
architecture specifications, training plan,
criteria of technical
description of acceptance criteria of
specifications
technical specifications
Deployed test platform,
modeled/customized UserForms, the
N/A
system is ready for demonstration / testing
Validated technical specification for
development

Technical specifications,
System Design,
Architecture specification

Source code

Test scripts, User Guide,


Admin Guide,
Training program

Deployed solution
Data migration

Protocol of data
migration, Act of
Provisional Acceptance

Trained users

Protocol of users training

List of defects

Protocol of defects,
Methods of solving
defects

Solutions free from identified defects

Protocol of solved defects,


Act of final acceptance

14

Working system, bugs fixed

Yearly maintenance
service acceptance14act

MNP Solution scheme

15

Main functionalities of NPDB


NPDB is a solution where order processing is centralized for all operators and routing information for ported
numbers is stored. NPDB covers two main functionalities required for efficient number portability service
implementation and later administration:

NP Clearinghouse functionality for Centralised order processing;

NP Central Reference Database (CRDB) functionality to synchronize NP local DBs.


The routing data in the NPDB are available for all ported numbers in the country (Mobile, Fixed, Premium and
Freephone).
The following functionality makes NPDB an extremely powerful and flexible product:

Support for Mobile (MNO) and Fixed (FNO) Network Operators;

Support for Virtual Network Operators (VNO);

A complete set of processes for Number portability (MNO-MNO, FNO-FNO, MNO-FNO,


MNO-MVNO, FNO-FVNO, MVNO-MVNO, Number Return, NP Reversion, Number
Suspend/Resume, etc.);

A completely flexible system for any new porting process implementation without additional developmental
efforts;

Timer control and parameters validation. More than 100 different validation rules are defined and available
for use as a result of best practice;

Powerful testing tools for easy integration and user-friendly testing during the implementation, which allows
saving time and keeping the time schedule of the project unchanged.

High availability solution with full reservation of all parts, fail over to secondary remote location and
synchronization between locations;

High performance and scalable solution evaluating the specific needs of the country;

Support for most the advanced and flexible SOAP based M2M interface;

Support for the synchronization over FTP;

Reporting tools for business and operation control;

Multilingual user interface;


16

Operation and maintenance manuals.

Benefits of NPDB
Centralized NP solution allows service providers and operators to provide high-quality and user
attractive NP services in a timely manner in accordance with the joint agreement of the institutions
regulating the telecommunication market and operators. NPDB is a new generation number
portability solution with unique benefits which were created considering practical needs of the
operators and National Regulation Authorities (NRA).
In addition to the qualities of the other providers of centralized NP solutions, NPDB is:

Reliable 99,9 % service up time;

Secure secure communication lines, protocols and data room for equipment;

Scalable easy adaptable to different needs;

Providing data safety and consistency guarantee;

Designed using module-based architecture and open standards for the interfaces;

Easy to integrate and maintain;

Easy to configure new services can be easy added to the existing platform.

17

Solution architecture
The main role in NPDB belongs to the data layer, which is presented by NP database. NP database stores all
porting data including National numbering plan, history of porting, and online porting data for data synchronization
with operator DBs and statuses for ongoing porting processes. The technical solution selected for the database
allows having high available system using standard SQL features. NPDB can have several databases synchronized
for quick recovery. The data can be synchronized with the database even on a separate physical location.
For an additional security and availability, the data can be backed up to a tape device.
The second functional level is NP business logic layer which serves business logics:

NP engine core;

NP SOAP WEB service core;

NP user interface core;

NP stored procedures API.


NP stored procedures API provides an additional level for the harmonized connectivity to NP database. This level is
responsible for the database access. It facilitates the database access, simplifies the developing of new
functionality and is responsible for the performance of such access.
NP Engine core is a core for the Number portability functionality. The rules and the logic for processing request
messages from the operators reside in here. This engine controls all timers, validates the data with data and rules
in the NP database, and controls the logic defined for the selected processes.
NP SOAP WEB service core is responsible for M2M interfaces. This module covers the functionality necessary for
secure SOAP connection including basic synchronous validation of the messages and their formats.
NP user interface core is a set of functionality required for representing and managing the data over user GUI. A set
of modules provide management tools and reports for GUI.
The third functional level is represented by NP services layer which serves main functional logics of the solution:

SOAP dispatcher service (handles distribution of SOAP messages);

Email notifier (is extremely useful for sending alarms);

Timer validation service (control timer values).


18

Management of porting process - Powerful flow control


NPDB is a process-based system for developing and operating very complex processes of Number Portability. The
engine has been developed using the experience gained while implementing similar systems. The specific needs of
operators and regulation authorities were evaluated during the design process of the system.
Today the solution is a unique tool combining flexibility and performance. Thanks to new technologies, these two
targets have been successfully achieved. Flexibility means possibility to define almost any NP process using simple
customization of the system as opposed to programming which is widely used by many suppliers. It will reduce the
time spent on NP implementation in the country and will allow reduce the costs. The skills developed during the
previous implementations and the knowledge gained from the comprehensive analysis of existing worldwide NP
implementation examples allowed to collect huge information on best implementations, success factors and
lessons learned. This information was used to create a set of processes for several different porting scenarios.
Each scenario is carefully tested for different external factors like specific requirements from the regulation
authorities or from the operators.
Several totally different NP scenarios can run on the same system without any interference and can be easily
combined later to get one common solution. For example, it can be used for MNP implementation from the very
beginning and for FNP implementation in later phases. Both processes can be combined later for the portability
between Mobile and Fixed networks. The operators can decide to use a different commonly agreed scenario at any
time.
This example shows the simple scenario for the flow of messages between Mobile Virtual Network Operators and
Mobile Network Operator. The most complete scenario for this case also includes the possibility for cancelling the
porting. There are also separate processes for number return to number/range holder, for number/range suspend
after porting is completed and for porting reversion in faulty case. The complexity of the processes is a matter of
operators decision rather than the system.

19

Basic validation
The purpose of basic validation is to verify the main values and parameters of any single message
to be sent to CDB. In case of WEB GUI interface, each mandatory field shall be filled with a value
and each value shall have a correct format. Web GUI is responsible for the first validation but this
is not the case for SOAP interfaces. Therefore, synchronous validation is performed by SOAP
interface and is applicable to WEB GUI, too. In a NPDB system, WEB GUI is a layer over SOAP
implementation.

Advanced validation
The scope of advanced validation is to verify the business logics of the message flow to be
controlled by the CDB on automatic basis (correct message sequence, control of the timer values,
etc). Opposite to basic validation, advanced validation doesnt check the format of the messages.
Advanced validation is responsible for data lookup in the database, for timers and process steps
validations.
The verification option might be easily customized in order to meet the needs of the operators/
SP having both the basic and the advanced validation sets enabled, the operator/ SP may
choose the way of performing the verification from synchronous or asynchronous methods. The
synchronous one will launch both the basic and the advanced validation sets simultaneously after
a message is received at CDB. This might be the problem in case of limited IT resources due to
the increased load. This risk can be mitigated by another method, i.e. the asynchronous method,
based on which only the basic validation will be launched simultaneously on message receive, the
message will be placed into the processing queue, and then advanced validation will be launched
on the background.
20

Business process or porting number scheme fragment

21

Providing MNP method All Call Query scheme

22

Providing MNP method Onward routing

23

SMS and MMS delivery

24