Beruflich Dokumente
Kultur Dokumente
FSUE ZNIIS
June 2015
Fixed
Operators
The donor
operator
Mobile
Operators
MSC
SRF
DB
HLR
Operator
NPDB
MSC
NPCDB
Federal State
of
Communicatio
ns
HLR
DB
The
operator
SRF
Numbering
Resource
Register
SRF
HLR
DB
NPDB Operator
Statistics, analytics
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
128 operators
Scale
Experts
5
5
Operation should be
carried out within the limits
of Working group with
involvement of experts
ZNIIS and operators of
mobile communication
6
6
Binding lines
Competition
7
7
Software development
The purpose
and results of
operation
8
8
9
9
Training
10
10
Testing
11
11
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
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
Web
Elimination of intersections
Extracts
13
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
Deliverables
Documents submitted
to customer
acceptance at the end
of the task
Signed contract
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
Technical specifications,
System Design,
Architecture specification
Source code
Deployed solution
Data migration
Protocol of data
migration, Act of
Provisional Acceptance
Trained users
List of defects
Protocol of defects,
Methods of solving
defects
14
Yearly maintenance
service acceptance14act
15
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;
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:
Secure secure communication lines, protocols and data room for equipment;
Designed using module-based architecture and open standards for the interfaces;
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;
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
21
22
23
24