MPN Nokia Solutiona

One-MNP Product Overview Subscriber Data Management 29-09-2015 1 29-09-2015 © Nokia Solutions and Networks 2015 Confidential

Version 3.5 / D507206773

Content

• One-MNP product • Overview • HW architecture • SW architecture • Flexibility and scalability • Redundancy and overload • O&M • One-NDS • Value-adding features • Virtualisation/Telco Cloud • Summary 2 29-09-2015 © Nokia Solutions and Networks 2015 Confidential

Version 3.5 / D507206773

One-MNP product

3 29-09-2015 © Nokia Solutions and Networks 2015 Confidential

Version 3.5 / D507206773

One-MNP Value Proposition Innovation

Scalability

Flexibility

• Software based Mobile Number Portability product implementation • Security robustness as standard • Always available architecture • Plug-in approach to the OneNDS multi-application ecosystem • Monitoring and recovery via NetAct & NEBR

• Unparalleled market leading dynamic and static scalability • From small start-up configurations to large scale deployments with multiple applications • Small scale HW footprint with a single O&M interface needed for One-MNP and One-EIR

• One-MNP runs on Telco grade high performance IT blade platform for superior performance and compact footprint • Deployed as a system in it’s own right or as part of a multi-application system with other One-NDS applications • On-site commissioning is simple by local configuration


Version 3.5 / D507206773

Subscriber Data Management Evolution Strategic Data Consolidation

Applications Strategy • Complete, dataless

application portfolio with real-time access to unified subscriber data • Integrate broad range of Nokia applications • Common industry, information model & application development tools

Network Simplification

1 Lead Application (E.g. NT HLR or One-MNP)

One-NDS

Provisioning

Service Innovation

2 One-EIR

One-MNP

One-AAA

Data Strategy • Single, simplified telco-grade open enterprise architecture for provisioning, data, & identify • Multi-vendor & multiapplication environment • Open Partner Program & Telco User Group

Data Consolidation

3

NT HLR

One-EIR

CMS-8200 HSS

One-AAA

One-NDS

Provisioning

Custom apps.

One-MNP

NT HLR CMS-8200 HSS

One-NDS

Policy (PCRF)

3rd party apps. Insights

Provisioning

Simplify complexity across one application


Version 3.5 / D507206773

Eliminate multiplicity of costs across legacy applications

Innovate around a single subscriber-centric network

Overview


Version 3.5 / D507206773

Mobile Number Portability Nokia One-MNP • Mobile Number Portability (MNP) enables mobile subscribers to keep their existing phone number when changing their service provider. • When subscribers change their service provider they are issued a new SIM and IMSI, however their original MSISDN can be retained • MNP keeps track of which MSISDNs have been ported in, out or between networks. • MNP is accessed for • • •

Call setup Call charging MO SMS

Ported

MSC/SMSC Ported

GMSC


Version 3.5 / D507206773

Not ported

Porting check

One-MNP

Own HLR

Foreign HLR

One-MNP Product Overview • Key Functionality -

3GPP 23.066 compliant Mobile Number Portability functionality Signaling Routing Function (SRF) based routing capability Support for both direct and indirect routing and All Call Query CAMEL Ph1, Ph2, Ph3 IDP/IDP-SMS relay, INAP, SINAP and Nortel INAP support HLR routing (IMSI routing) Enhanced features such as Voicemail routing, SMS Spam and Fraud prevention

• Architecture -

EIR AAA EIR

Custom app. Policy (PCRF)

Subscriber data de-coupled SW application front end Flexible, robust and highly scalable hosting platform layer Number portability data stored on One-NDS with prefixes available via the APP FE APP FE redundancy (n+k) and geographical diversity provided by One-MNP and One-NDS Support for SIGTRAN M3UA signaling. Robust and security conscious OS; Red Hat Enterprise Linux Standard IT server based hardware; HP blades (Oracle Netra X4270 for HW re-use) Installation and Configuration Server


Version 3.5 / D507206773

HLR

One-NDS

MNP HSS

3rd party apps. Insights

Core Network Context Position of One-MNP Access Network

Core Network

Circuit Switched Domain MSC

GMSC

GSM

To other PLMN or PSTN HLR

IN

One-MNP SGSN UMTS

TDM

GGSN

Packet Switched Domain

IMS Core


CSCF

Version 3.5 / D507206773

To Packet Network

MGCF/IN/TAS

To other PLMN or PSTN

One-MNP in VoLTE

• ENUM interworking between operators is typically not in place • Nokia’s CS domain One-MNP can be re-used in VoLTE One-MNP

TAS

One-MNP

One-MNP

ENUM CSCF

Number portability query is done in originating TAS for voice and video call 10 29-09-2015 © Nokia Solutions and Networks 2015 Confidential

TAS

ENUM

CSCF

TAS MGCF

Number portability query is done in originating MGCF for voice and video call Version 3.5 / D507206773

ENUM

CSCF Number portability query is done in originating S-CSCF for voice and video call

HW architecture


Version 3.5 / D507206773

HP Blade System hardware architecture for One-MNP FE HP Rack [front view only, AC, DC] 42

DC fuse panel for c7000 enclosures

L2/L3-Switches

HP P/N AH355A

41 40 39 38 37 36 35 34 33 32

HP P/N AH355A HP 5820AF HP 5820AF

One-EIR FE, One-MNP FE, TIAMS, NT-HLR FE, CMS 8200 HSS FE, ...

HP BLS c7000

HP fuse fuse panel (DC only, in case of a 2nd shelf)* Rack Switch, could be 2U if not Juniper EX4600 (optional)* Rack Switch, could be 2U if not Juniper EX4600 (optional)* Not used Reserved for DC cabling and seismic kit

HP BladeSystem c7000 enclosure

22 21

One-NDS

HP fuse fuse panel (DC only, 1st shelf)*

Reserved for DC cabling and seismic kit

HP BladeSystem c7000 enclosure

HP BLS c7000

11 10

Reserved for DC cabling and seismic kit

08

HSM boxes (optional)

CS10LANv3 AuC (HSM box) CS10LANv3 06

Reserved for add. HSM boxes or used in connection with a 3rd c7000 enclosure * 00

HP 10000 G3

RU

The detailed placement of equipment at the rack is subject of change and follows respective technical needs.


* filled with blank panels if not used

Version 3.5 / D507206773

• Up to 2 shelves can be deployed in one rack • Power distribution units available in the rack • Existing Top of the rack switch HP 5820 replaced by Juniper EX4600

Support for latest HW and platforms

• One-MNP is offered on HP Gen9 blade system based on the latest Intel Haswell processor technology and based on the RHEL 7.x release OS platform

Key characteristics • Compact and energy efficient  - decreased power usage, - decreased need for cooling, - smaller footprint • Carrier Grade reliability at commercial IT prices  - NEBS & ETSI certified 13 29-09-2015 © Nokia Solutions and Networks 2015 Confidential

Version 3.5 / D507206773

HP BLc7000 Enclosure

HP Proliant BL460 blade server

HP blades offer • High performance CPUs • Large memory and storage • Wide ecosystem of IT MW, HW and SW Partners Both AC and DC power options available

SW architecture


Version 3.5 / D507206773

One-MNP SW architecture More or less in our control One-MNP application

One-MNP

Application hosting

ADW

Database

Nokia (Aricent*)

Install Server

SS7 stack

Installation & configuration

Management Server

Operating system

Fault & performance System management Monitor

Configuration GUI

One-MNP

NDS

RHEL + Java

* Nokia wholly own the license to develop 15 29-09-2015 © Nokia Solutions and Networks 2015 Confidential

Version 3.5 / D507206773

Flexibility and scalability


Version 3.5 / D507206773

One-MNP flexibility

2 Site Deployment Architecture Site 1 One-NDS1

One-MNP2

Site 2 One-NDS1

One-MNP2

Management Server Installation Server System Monitor

3 Site Deployment Architecture Site 1 One-NDS


One-MNP3

Site 2 One-NDS

One-MNP3

Site 3


Version 3.5 / D507206773


Installation Server

One-NDS

1) One-NDS in 2 site: 2+2 2) In 2 site a single site is dimensioned to assume the full load of both sites


One-MNP3

3) In 3 site, 2 sites are dimensioned to assume the full load of three sites

Redundancy and overload


Version 3.5 / D507206773

Robustness - by design Devised to handle a wide range of possible failure scenarios Traffic spikes

Node failure

Comms issues

Signalling storms

Site failure

Human error

Optimized database and Telco core operations during overload

Automatic recovery procedures and transparent failover

Network design, provisioning gateway and configuration GUI


Version 3.5 / D507206773

Redundancy Concepts

• In any configuration One-MNP nodes can fall back to other One-MNP nodes • Adequate capacity must be engineered during the design phase • Routing of messages are directed via MSCs, GMSCs and/or STPs to MNP Fes • When a node fails - GSM/UMTS: SS7 mechanisms redirect number portability SS7 messages to the other nodes


Version 3.5 / D507206773

Redundancy Normal Operation One-NDS

10 00 0

Device Management Server Via query or update

Device Conf Device Conf All One-MNP FE servers access the same database Device E.g. GPRS settings E.g. GPRS settings Management MNP 1-1 MNP 1-2 MNP 1-3 Server Device Conf Via query or SMSCPC Device SMSC PC = x =y PC = z E.g. GPRS settings update Management SMS with SMS with Server configuration information configuration information Via query or SMSC SMSC update SOAP Trigger SOAP Trigger SMS with configuration information 4. Ported Number + HLR GT

Device Management Server Device Conf or Via query E.g. GPRS settings update

Check IMEI

MSC SAI/OC MSC One-EIR

Site 1

MSC

MSC


Version 3.5 / D507206773

SAI/OC

SIM Card

SOAP Trigger Check IMEISS7

Check IMEI One-EIR

One-EIR

SMS with configuration informa

SIM Card

SOAP Trigger

One-EIR

One-NDS assures Data Redundancy

SAI/OC

Check IMEI

MSC Site 2 MSC

SAI/OC

MSC

MSC

Redundancy One-MNP FE Node failure One-NDS

10 00 0

Device Management Server Via query or update

Device Management Server Device Conf or Via query E.g. GPRS settings update

Device Conf

Device Conf

Device Any can pick up the MNP traffic, offers Network redundancy E.g.Server GPRS settings E.g. GPRS settings Management Server Via query or PC = x update

MNP 1-1

MNP 1-2

MNP 1-3

Device Conf SMSCPC Device SMSC =y PC = z E.g. GPRS settings Management SMS with SMS with Server configuration information configuration information Via query or SMSC update

Check IMEI

MSC SAI/OC MSC One-EIR

Site 1

MSC

MSC


Version 3.5 / D507206773

SAI/OC

SIM Card

SOAP Trigger Check IMEISS7

Check IMEI One-EIR

One-EIR

SMS with configuration informa

SIM Card

SMSC SOAP Trigger SMS with configuration information 4. Ported Number + HLR GT

SOAP Trigger

SOAP Trigger

One-EIR

One-NDS assures Data Redundancy

SAI/OC

Check IMEI

MSC Site 2 MSC

SAI/OC

MSC

MSC

Redundancy concepts Same site routing • Same site routing provides an efficient way of routing LDAP traffic within the same site - All APP FE nodes are connected with two connections to all other R-DS nodes both locally and remotely - The R-DS nodes within the same physical site as the One-MNP can be configured to make best use of local connections - If the same site connection fails the remaining active connections to remote sites take over - The connection error thresholds are monitored every minute to check for possible recovery back to the same site


Version 3.5 / D507206773

O&M


Version 3.5 / D507206773

Management Server Functionality Management Server Web based GUI used for application/subscriber administration and basic OA&M for the application Front Ends. Connected via a TCP/IP interface which uses the LDAP protocol for communications


Version 3.5 / D507206773

Installation Server Functionality Installation Server

The use of HP blade hardware limits the available installation options for both the operating system and applications due to the limited interfaces i.e. no optical drive or USB. Therefore One-MNP provides a network based installation functionality (Also usable for upgraded x4270 deployments)

• Support for SW installation - Non-interactive installation of RHEL OS, defining

Installation Server

One-MNP FE

required packages, services and configuration - Installation of Non-OS packages such as One-MNP application, System Monitor, Management Server - Basic configurations and security hardening for starting up of protected system System Monitor Management Server


• Support for SW update installation - Patch management push to all configured blades Version 3.5 / D507206773

One-NDS


Version 3.5 / D507206773

One-NDS X.500 – A standards-based architecture X.500 is a hierarchical directory structure for categories of information • ISO and ITU defined Directories can: • Be geographically dispersed • Cater for potentially billions of entries of information • Be accessible from any recognised point of access and yet appear as a single logical global entity (directory)


Version 3.5 / D507206773

Extending X.500 provides unparalleled scalability, resilience and carrier grade performance Directories are the logical choice for international industry, telecommunications, internet, commerce, banking, government

Nokia Subscriber Data Management System architecture

NetAct1 or other NMS NE3S WebServices One-NDS Administrator, Status Service

NetAct1 or other NMS

CRM SPML

NE3S/WebServices

Notification Manager

Provisioning Gateway

Management/Install/ System Monitor Server (One-MNP FE)

SOAP

LDAP

LDAP

Install Server

Routing DSA

One-MNP FE

One-EIR FE NT HLR FE

One-NDS

BE DSA n

BE DSA 1

1) Dual or single NetAct 29 29-09-2015 © Nokia Solutions and Networks 2015 Confidential

Version 3.5 / D507206773

Custom application

One-NDS Multi Application Integration Flexible & Extensible approach – Adding a new application CRM

ADM (SWAM)* NT HLR counters

SPML

Provisioning Gateway

NT HLR FE SOAP

NT HLR plugin

Notification Manager

LDAP LDAP

NT HLR triggers

Directory Nodes SOAP

Extension package (ExP) is the generic mechanism to deliver application specific logic and configuration for One-NDS to provide the provisioning and notification functionality required by One-MNP. Benefits of Extension Package concept

Open and standardized interfaces which allows decoupling of One-NDS from application FEs

Modular and easily extensible mechanism to integrate the application data on One-NDS

Schema

Extension Package Components * Counters active but not linked to NetAct


Version 3.5 / D507206773

Enables a common provisioning interface across applications

One-MNP data model root

o=DEFAULT dc=msisdn

dc=imsi tennantConfiguration

ds=subscriber dcObject

dcObject cntdbDsElement

msisdn=XXXXX

imsi=XXXXX Uid=xxxxxxxxxx

msisdnAlias

imsiAlias

subscriber alias

alias subData=services

subData=relation

subscriberSubData

subscriberSubData

ds=mnp

ds=mnp

cntdbDsElement

cntdbDsElement

Adaptive name map

Adaptive name map msisdn=XXXXX mnpMsisdn=xxxxxx

mnpPortedMsisdn

msisdnAlias

alias

[mnpPortStatus] [mnpRoutingLocation]

Subscriber Data Store 31 29-09-2015 © Nokia Solutions and Networks 2015 Confidential

Version 3.5 / D507206773

imsi=XXXXX

imsiAlias

Value adding features


Version 3.5 / D507206773

One-MNP Value Added Features SMS Fraud Prevention (SMS Screening)


Version 3.5 / D507206773

Operator A One-MNP

X

7798

7989

• The SMS Screening feature prevents the fraudulent use of an operator's SMSC by the subscribers of other networks. • One-MNP ensures for MAP MOForwardSM operations that a subscriber belongs to the operator (e.g. own network or ported-in) before they are allowed to use the operator’s SMSC to send an SMS otherwise the operation is rejected.

SMSC (7989)

One-MNP Value Added Features SMS Firewall (SMS Home Routing) • This feature facilitates routing of SMS-related messages to different network elements, for example, to a Firewall node to protect subscribers from SMS spam. • One-MNP achieves this by setting the Translation Type SCCP parameter of the Called Party Address digits to a specific value such that onward routing is directed to the firewall node. 34 29-09-2015 © Nokia Solutions and Networks 2015 Confidential

Version 3.5 / D507206773

One-MNP

One-MNP Value Added Features Intelligent Networks • Non-Geographic Number Portability

- Provides a mechanism for resolving the Cell Location Number which can be used for special routing purposes • Routing Emergency calls based on current location of called party • Routing calls to special services based on current location of called party (ex. Taxis, Pizza delivery…)

• IDP Relay customisations

• Numerous flexibility is built into One-MNP to accommodate a variety of charging and routing platforms, including but not limited to: • Routing to SCP based on service key • Mapping of NOA + short code to Subscription Network ID for IDP Relay + many more….

• Flexible numbering

• In order to accommodate numerous charging and routing functions One-MNP has a wide variety of routing number substitution options: • RN+CC+NDC+SN, RN+NDC+SN, CC+RN+NDC+SN


Version 3.5 / D507206773

One-MNP Value Added Features Core • Voicemail Prefix Substitution

- In some GSM networks voicemail numbers are prefixed differently from the subscribers MSISDN number. - One-MNP provides a mechanism whereby a unique voicemail prefix can be modified to a ‘standard’ MSISDN prefix prior to database lookup thereby eliminating the need to store a separate MNP entry for every subscribers voicemail number

• Flexible routing

- Numerous flexible routing options are available with One-MNP in order to accommodate differing operator or regulatory network strategies for the implementation of One-MNP including but not limited to: - Support for over-decadic digits for both inbound HPLMN checks and outbound RN - NoA and Translation Type modification - Disabling of MNP-SRF for specific SCPs - Providing multiple RNs for HPLMN subscribers


Version 3.5 / D507206773

One-MNP Value Added Features SMS • SMSC loadsharing

- One-MNP facilitates the ability to monitor the availability of SMSC remote point code in order to provide a loadsharing function for the delivery of MO-FSM operations. - Concatenated SMS - In the event an SMS is detected as concatenated, One-MNP ensures that all concatenated messages are delivered to the same SMSC to ensure the subscriber is delivered the message in the sequence it was sent.

• LongSMS

- Owing to the lack of dialogue portion in a MAPv1 MO-FSM it is possible that the contained text message is close to or at the 160 character limit. When sending this onto the SMSC via MAPv2 or MAPv3, the dialogue portion means the MO-FSM cannot be completed in a single message. OneMNP handles this by initiating a dialogue with the SMSC in order to deliver the dialogue portion first before completing the sequence with the MO-FSM components i.e. the text message etc.

• SMS calling party routing


Version 3.5 / D507206773

Summary


Version 3.5 / D507206773

One-MNP at a glance

Control

Roadmap

Robustness

Customers

Wholly Nokia owned SW development

Strong, definitive, dynamic and innovative

Nokia SDM as a proven differentiator

24

Quality

Value

Subscriber scale

0.1M to >200M

Virtual zero targets and metrics for every release


Unlocking the mandated investment with value adding features and insights Version 3.5 / D507206773

Subscribers

200M

MPN Nokia Solutiona

Recommend Documents