Engaging MNP Management Solutions That Work For Your Network

This document is offered compliments of BSP Media Group. www.bspmediagroup.com

All rights reserved.

http://www.bspmediagroup.com

http://www.bspmediagroup.com

Slide title

minimum 48 pt

Slide subtitle

minimum 30 pt

Engaging MNP Management Solutions that work for your network

Dar es salaam

November 2012

Harald Hauser Market Management

Interconnect Solutions

Ericsson Telcordia

+1 732.822.8958

[email protected]

International MNP Forum

Slide title

minimum 32 pt

(32 pt makes 2 rows

Text and bullet level 1

minimum 24 pt

Bullets level 2-5

minimum 20 pt

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–—‘’‚“”„†‡•…‰‹›⁄€™−≤≥fifl

ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș

ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏ

ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ№

Do not add objects or

text in the footer area 2

Overcoming MNP implementation challenges & resolving

possible impacts on networks and services

Challenging old implementation approaches to improve the

customer experience

About us

Approaches to managing service issues that will occur as

a result of MNP implementation

Understanding port-corrected data for ensuring seamless

and efficient delivery of content and other services

agenda

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







1984

Our History & Track Record

Break-up of Bell

System – becomes

the Central Services

Organization

providing R&D & OSS

support for the Bell

Operating

Companies

25-year+ history

Acquired

by SAIC

1994-98 1999-

2002 2003-04

Equity

investors acquire

Telcordia – 3/15/05

Renamed

Telcordia

Technologies

Acquires

Granite

Systems

2005-

2011

Formerly

Bellcore

1960s

Creating

Telecom OSS

with goal of

maximizing

flow though

operations

Busi

ness

T

echnolo

gy

Develops call

waiting, call

forwarding, and

caller ID

Handles all toll

free (800)

number calls in

the US

Provides Y2K

testing for

customers

Enables DSL

rollout

Delivers managed

IP solution

Introduces

Elementive®

product

portfolio

Part of Bell Labs

within AT&T

Enables WNP Enables FTTx

rollouts

Develops

Intelligent

Network

Acquires Mesa

Systems (power

utility & force

management

support)

Rolls out

Maestro ® IMS

suite of

products Develops Traffic

Routing Admin

center for World

Zone 1

Manager for WZ1 Numbers

Rolls out VoIP Routing

Registry & Global

Dialing Plan Solutions

Today

Ericsson

acquires

Telcordia

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Our Number portability Footprint

Malaysia

Mexico

USA

Canada Lithuania

Greece

Pakistan

Turkey

Saudi Arabia

Egypt

South Africa

India

Number Portability Gateway

Number Portability Clearinghouse

MessageHub

Thailand UAE

Chile

Argentina

Nigeria

Brazil

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Fundamentals

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







MNP Implementation - Key Aspects

Number Portability has two key aspects:

Business

o Ordering:

Negotiation / Validation

o Provisioning:

Processing / Activation

o Notification:

Broadcast, Batch, Download

Network

How does an Operator process a

subscriber request to port their number?

o Storage:

Ported & associated routing

numbers

o Querying:

Address resolution

o Call Signaling and Routing

How does an Operator deliver a call or

text message to a ported mobile number?

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







NP Architecture - Options

Bilateral Model Indirect Routing

Hybrid Model Direct Routing

Centralized Model Direct Routing

Port Order Handling

Central National Reference DB for Ported Numbers

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Network and Non-Network Related Aspects

Direct Routing (AcQ/SRF)

Centralized

Port Order

Processing

Indirect Routing (Onward Routing /

Call Forwarding)

Peer-to-Peer / Direct

B2B / Bilateral type

Implementation

Donor

Originating

Recipient

X X

Originating Recipient

Donor

Networks and other internal systems need to know some of this information!!

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Standards Bodies: ETSI Recommendation

Replicated Real-Time DBs on Operator level.

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Value of Centralizing NPDB & Order Handling

Centralizing the NPDB to

standardize and mechanize:

o Saves OPEX

o Reduces risk

o Improves industry process

quality

o Reduces time to port

o Improves customer

experience

Why not apply the same key-

learning & concepts with the

aim of achieving the same

goals for Inter-Operator

communications with an

Intelligent NP process Hub?

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Best Practice Today Centralized, Direct Routing

Number Portability Clearinghouse Administration

Data

Distribution

Reference

Database

Provisioning

Business

Logic

Recipient : Operator A

BSS/OSS

Network

Elements

Donor : Operator B

BSS/OSS

Network

Elements

Other Operators

Number

Portability

Provisioning

Notifications

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Number Portability Methods

Query Mechanics versus Routing Methods

Onward Routing

All Call Query

Query on Release

Signaling Relay Function (SRF) Intelligent Network (IN)

Direct Routing Originating Query on Digit

Analysis

Indirect Routing (with reference

to subscription network)

Terminating Query on Digit

Analysis

N.A. Query on HLR Release

Definitions according to ETSI /3GPP 123/023.066

Standard

Call and Non-Call related Standard

Call related only

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Routing Challenges

› Before (M)NP routing based on number block assignments

› (M)NP breaks association between block & serving provider

› Porting record re-established this association – Prefix + NSN/MSISDN

– Prefix identifies serving / recipient network

› Problem for incoming international traffic to ported numbers – Default solution in most markets is call/message forwarding

› International GW provider receives traffic and…

- …forwards traffic to donor network

› Intercepting and port correcting on the donor’s STP, and...

- Delivers traffic to recipient, usually for a “conveyance fee”

› Messy and expensive in the long term

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







MNP Implementation Challenges

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Management of NP Data – Standards

e.g. X.25

M-NPMP

e.g. X.25

Data Base

Service

Switching (& control)Point(-s)

Service

Control (& Data)

Point(-s)

Master Administrative

Directory Number

Data Base

Service

Management

Point

Operator 1 Operator 2 Operator n

SSCP

SSCP

SSP

SSP

SSP

SSP

SCP

e.g. X.25

SCP

SMP SMP SMP

e.g. No. 7

SDP

Master NP

Management

Point

Centralized Order

Processing

National Reference DB

Op

era

tor

EG 201 367 V1.1.1 (1999-02)

Porting Data replicated in each Operator’s Network

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







NP Integration Challenges

Number Portability

Clearinghouse Administration

Reference

Database

Registration

› Operators are faced with the challenges of: – Interfacing with the centralized NPC

– Integrating NP with various internal systems and processes,

including BSS/OSSs and network

Operator’s Environment

? ? ?

Notification

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Number Porting Request, Response & Service Fulfillment Process

› User requesting porting as part of ordering process – Service fulfillment process now includes sending and receiving

porting requests to and from NPC

› NP transactions can be managed: – Manually, or

– Integrated with BSS/OSSs via a specialized system that

interfaces with the NPC

Service Provider Environment

Call

Center CRM Billing

Other

BSSs

Order

Mgmt

Inven-

tory

Other

OSSs

Cust-

omer

Care

Porting Messages

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Number Porting Update & Networks

› NPC broadcasts the latest update on successfully

ported numbers and their new serving provider

› Each operator needs to capture this new routing data

and update its network elements (e.g., switches,

signaling, etc.) for use to route each service session

Operator Environment

Network

Routing Update

NEM STP

NPDB

MSC

Query with

Called number

Respond with

Routing number NPDB

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Implementation Option 1

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Implementation Option 2

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Number Portability

Clearinghouse Administration

Data

Distribution

Reference

Database

Provisioning

Business

Logic

Best Practice – Fully Integrated Number Portability Gateway

Routing Updates

Operations

NPDB

STP NEM

CRM Billing Other

BSSs

Order

Mgmt

Inven-

tory Other

BSSs

Network

Telcordia

Number Portability

Gateway

Port Order

Provisioning

Routing Data

Provisioning

Porting Requests

NEM specific interface (NEM = Network Element Manager)

SOAP / JMS / XML

Provider Environment

Automate number portability data provisioning by

integrating NPC and Operator’s internal systems

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Number Portability Gateway

Requirements

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Number Portability Gateway Requirements

› Goal: MNP Flow Through Automation

- Updates relevant BSSs & OSSs and NE components

› Implementation of specified processes for porting a

number(s)

- Same external process for all service providers

- Internal processes specific to service provider

› Replicated copy of the centralized reference database

- Routing for all ported numbers in a particular country

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Logical Architecture, Interfaces & Integration

Tekelec PDBI

Nokia Siemens Ntwk Sw Cmdr

Ericsson EMA

Huawei LSMS

Other

SOAP (XML/https)

EAI /Messaging Backbone

(e.g. Tibco, WebMethods, MQ)

JMS /XML/SOAP or

direct BSS/OSS Interfaces

Pro

vid

er

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Sample MNO Architecture beforE MNP

Provisioning

Mediation

Network

SMS-C

Other

VAS Nodes

HLR/

FNR

Service Network

CHARGING SYSTEM

CDR

CDR

MSC/MSS

GGSN

Packet Network

DR

CRM

BILLING

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Sample Architecture with MNP

Provisioning

Mediation

Network

SMS-C

Other

VAS Nodes

HLR/

FNR

Service Network

Charging System

CDR

CDR

MSC/MSS

GGSN

Packet Network

DR

CRM

BILLING

NPC NPG

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







The Number Porting Process

Process for implementing Number Portability

is very similar globally

o Recipient initiates request

o Donor validates request

o Depending on validation

result • Port is executed or

• Port request is terminated

o Upon execution:

NPDB is updated to

contain new routing

Entities which update

routing databases

are notified

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Sample MNP Process Flow - Port In

NPC

Request for NP Port Request

Update Case

Activate Ack Port Activated

Port

Initiation

Port

Activation

Port Deactivated

Port Request

Port Request Ack Port Request Ack

Port Response

Port Request

Port Response

Port Deactivated Activate Number

Port Activated

Broadcast

OTHER

OPERATORS

Port Activated

Broadcast Close Case

Welcome SMS

Activated SMS

BSS/OSS NEM

RECIPIENT

NPG DONOR

OPERATORS

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Message and Timer Processing Requirements

› Message Processing Engine

– Control and organization of flow of messages between NPG

components, internal & external interfaces

– Control of adherence to the internal & external business rules

– Maintenance of routing and status of all ported numbers

– Specific Functions:

› Message validation, including state, content, timer

constraints

– Message forwarding

› Timer Processor

– Detection of timer expirations

– Logging of timer violations

– Performance of any required actions associated with expiration

of specific timers

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Flexibility, Extensibility & Scalability Requirements

› Core framework design

– Flexibility to accommodate changes to a process after initial

implementation

– Ability to add new functions

› Support of multiple sets of processes and messages – Different process for pre-paid and post-paid MNP

– FNP, etc.

› Configurable – Processes can be changed

– New messages can be defined

› Scalability – Horizontal

– Vertical

– (Process Distribution)

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Reliability & Availability Requirements

› High Availability

– No single point of failure

› Redundancy

- Hardware & connectivity

- Sites

› Application server cluster

› Multiple instances of processes

› Database cluster

› Reliable Message Delivery

– Messages received/sent

– Acknowledgement for each message sent

› Re-send until successful

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







User Interfaces Requirements

› HTML GUI accessed through browser

– Display of list of master records with selection criteria

– Work List - for viewing and acting upon all pending messages

– Dedicated Porting Screens - for sending/responding to a single

message at a time

› Number Portability Request

› Number Portability Response

› System Administration Screens

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Reporting Requirements

› Published NPG database schema

– can be used to extract data or build reports

› At a minimum reports should cover:

– Completed Ports In:

› For Completed Ports In, reports should include:

- Ports In/Ports Out Completed total counts of ports and numbers,

Number Range(s), Port ID, Port Type, Recipient ID, Donor ID,

Completion Date

– Completed Ports Out:

› Same as previous.

– Timer Violations:

› For each Violation, report should include:

› Date /Time, Number Range(s), Port ID, Port Type, Timer ID

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Systems Management & Security Requirements

› User access control and profile management

› Event Management

› Auditing Logs

› Failures/Monitoring Management

› Digital Certificates

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







Some Services Requirements

Installation

o Deployment planning support

o Solution installation

Test Plans & Testing Support

o Test plan development

o Acceptance and industry testing

Interface Integration Support

o Consultation for integration with the

EAI/JMS/XML/NEM interface

o Problem analysis and resolution

Project Management

o Project plan development

o Implementation coordination and monitoring

Training

o System admin training

o End user training

o Materials preparation

o Ongoing Operations & Support

Slide title

minimum 32 pt

(32 pt makes 2 rows


minimum 24 pt

Bullets level 2-5

minimum 20 pt







In a Nutshell, What you need to look for is…

Rapid Time to Launch

• Short deployment time

• Low Total Cost of Ownership

• No cost overruns

• No surprises

Proven Platform

• Proven, off-the-shelf

• Open, configurable, scalable

• High quality & reliability

• Multiple deployments of

similar systems

• Already pre-integrated

Track Record

• Number of deployments

• Delivery on Time without any

delays

End-to-End Expertise

• From consultation planning to

solution implementation to

operations

Documents

Engaging MNP Management Solutions That Work For Your Network