mobile number portability_workshop

Mobile Number Port

August, 2014

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.2

THIS PRESENTATION IS INTENDED TO OUTLINE OUR GENERAL

PRODUCT DIRECTION. IT IS INTENDED FOR INFORMATION

PURPOSES ONLY, AND MAY NOT BE INCORPORATED INTO ANY

CONTRACT. IT IS NOT A COMMITMENT TO DELIVER ANY

MATERIAL, CODE, OR FUNCTIONALITY, AND SHOULD NOT BE

RELIED UPON IN MAKING PURCHASING DECISIONS. THE

DEVELOPMENT, RELEASE, AND TIMING OF ANY FEATURES OR

FUNCTIONALITY DESCRIBED FOR ORACLE'S PRODUCTS

REMAINS AT THE SOLE DISCRETION OF ORACLE.

Safe Harbor


Agenda

MNP Concepts and Terminologies

MNP Global Status

MNP Overal Architecture

EAGLE 5 MNP

MNP Routing Option


MNP Concepts and Terminology

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.55 |

Wireless

Operator

A

Wireless

Operator

B

What is Number Portability?

PSTN

HLR HLR55 1010-7325 55 1010-7325

Subscriber changes Mobile Service Provider

while keeping its mobile number

Wireline

Operator

A

Wireline

Operator

BSSP SSP

55 5323-8970 55 5323-8970

Subscriber changes Wireline Service Provider

while keeping its telephone number


Number Portability Common Terminologies

The Directory Number (DN) is the telephone number entered when making a voice call or sending an SMS to a customer.

– In mobile networks DN=MSISDN

The Network that the customer is leaving is called the Donor network.

The Network that the customer is moving to is called the Recipient orSubscription network.

The Network that originating the call is called Originating Network

The Network that own the number is called Number Range Holder Network.

A Routing Number (RN) is a number assigned by a regulator to an operator to distinguish between different operators networks in the Portability environment.


Key Participants in a NP Domain

How to route calls to the right subscription network?

Originating

Network

Transit

Network

Donor

Network

Recipient

Network Called

Subscriber

No longer

Serve the

Called Sub

Calling

Subscriber

• Donor Network: Previously owns the number

• Number Range Holder: Donor of the first porting, has been

assigned the number range (NDC) the number belongs to.

• Originating Network: Where call is originated

• Recipient Network: Where the subscriber is presently served

• Transit Network: Where signaling (possibly also the bearer

channel) is transported prior to arriving at recipient Network

Number

Range Holder

No longer

Serve the

Called Sub


Other important aspects

IMSI addresses (SIM cards) are not portable.

– Each ported subscriber gets a new SIM card from the

new subscription network

MNP allows porting of the number but not the service!

– Credits with the donor operator will be lost

– Some services may work different from one operator to

another, e.g. access to voice mail

– Some services may no longer work


Operator 1NP Database

De-Centralized Solution




Centralized Solution

NCH

NP Database

Operator 1 NP Database

N Operator 3 NP Database



Administrative Layer:De-Centralized Vs. Centralized

No central reference database

Synchronization dependent on each operator

Requires many connections between all operators

OK for indirect routing

Centralized reference database – Most countries

Third party manages database and distributes to all operators

Minimizes interconnections between operators


Number Porting Process – General Flow

Centralized

Number

Portability

Management

System

(CNPMS)

NP Order

RecipientOSSGW

1) Number PortOrder containing Authorization Info and Proposed Order Transfer Time

NP Order

Ne

goti

atio

nP

has

e

All LSMS in theCountry

5) Service Connect Notice to ALL

operators

Po

rtin

gP

has

e

2) NPO transferred to DNO

Activation Time commences

The subscriber applies for

Number Porting

DonorOSSGW

5) Service Connect Notification

5) Service Disconnect Request

Act

ivat

ion

P

has

e

Disconnect ConnectDonorOSSGW

RecipientOSSGW

The subscriber can switch the SIM Card

or Phone

ConfirmConfirm3) NP OrderConfirmation or Rejection

4) Number Port Order Approved and Order Transfer Time Confirmed

Informs the customer that the

Porting Time is confirmed

RecipientDonor


Number Porting Process – Scenarios

Various Scenarios

– Pre-validation (Optional)

– Submission

– Confirmation

– Rejection

– Cancellation

– Activation

– De-activation

– Routing Info Distribution


LSMS

Porting Activation Flow Control

Operators may worry that

their IT System and

Network will be

overloaded during the

Port Activation Window

Our strategies

– Port Activation Window(s)

configurable at the NPCH

– Subscribers select the Port

Activation Window

– NPCH allocates the orders

to the windows

12NPCH

OSSGW

LSMS

OSSGW

LSMS

CNPDB

Service ConnectService Disconnect

RN Broadcast

RN Broadcast

time

Activation Timeslot

1

Activation Timeslot

2

Activation Timeslot

3

Po

rt O

rder

s


13

Subscription Termination Process – General Flow

NRHN

OSSGW

Centralized

Number

Portability

Management

System

(CNPMS)

SN

OSSGW

3) Service

Disconnect

Notice to ALL

operators

Po

rtin

g

Ph

as

e

All LSMS in the

Country

Activation Time

Window

• A Ported Subscriber terminates his

service from the Subscription Network

• Subscription Network disconnects the

Number and retains the Number for X

days

1) Number Port

Order Termination

containing the

Subscriber

Number and

Termination Time

Number Return

Ne

go

tia

tio

n

Ph

as

e

2) Number

Returned to

the NRHN

Number Return

Subscription (Recipient)

Network

Number Range Holder

Network


Subscription Termination Process – Scenarios

Various Scenarios

– Submission

– Confirmation

– Rejection

– Routing Info Distribution


Other Number Portability Processes

Routing Information Distribution

– Real-time, Full DB, Partial DB

– The process to ensure everybody are in synchronous of the

Ported Number and RN Mapping

Subscription Suspension Process

– Optional process to terminate a subscriber if he does not pay after

ported out

– The subscriber can be a prepaid or postpaid

Optional Advanced Processes

– RN Audit, Active Reconciliation, Status Query, Down-time

Notification, Reversal, etc


MNP Global Status


Worldwide Number Portability Deployment Status

Fixed-Line NP Deployments

Mobile NP Deployments

1996 1997 1998 1999 2000 2001 2002 2003

France

Germany

US

Canada TaiwanSweden

Australia DenmarkUK

Hong Kong

UK

Holland

Iceland

Spain

Italy

Switzerland

Sweden

Australia

Denmark

Norway

Germany

Belgium

Portugal

France

US

Finland

Ireland

Greece


Worldwide Number Portability Timeline 2005 - 2012

Azerbaijan

Bahrain

Dominican

Rep.

Ecuador

Fixed-Line NP Deployments

Mobile NP Deployments

Bahrain

Columbia

Dominican

Rep.

Ecuador

South Africa

TurkeyChile

2005 2006 2007 2008 2009

Slovenia SingaporeBrazil

Mexico

Croatia

Estonia

Latvia

Luxembourg

Malta

South Korea

Taiwan

Czech Rep.

Israel

Japan

Oman

Poland

Saudi Arabia

South Africa

Canada

Egypt

New Zealand

Pakistan

Romania

Brazil

Bulgaria

Macedonia

Malaysia

Mexico

Singapore

Turkey

Argentina

Belarus

Cayman Is.

Chile

Honduras

Jordan

Peru

Thailand

(China)

South Africa

ThailandHong Kong

2010 2011 2012

India

Albania

Bahrain

Colombia

Ghana

Georgia

India

Kenya

Panama

Serbia


In the process Implementing

– Azerbaijan

– Moldova

– Nigeria

Vendor selection

– Bahamas

– Costa Rica

– Jamaica

– Tunisia

Activities of some kind

– Bangladesh

– Guatemala

– Indonesia

– Kazakhstan

– Philippines

– Russia

– Venezuela

– Vietnam

– Ukraine


MNP Architecture


NPCH

CNPDB

OSSGW

LSMS

QNPDB

IP C

on

nec

tivi

ty

Intr

anet

Central SideCNPMS

Operator SideNPGW

QNPDB SS7 / IP

Number Portability Administrative Architecture

Coordinate Number Portability Workflows

Centrally

Master Reference

Database of Routing Info.

Coordinate Number Portability Workflow within an operator

Receive Routing Info from the CNPDB and

provision the QNPDBs

Query Number Portability DB

e.g. HTTP, SOAP, ENUM, SIP, ITDB, …STP from partners

Optional Centralized Query Box

CNPMS – Centralized Number Portability Management System• NPCH – Number Portability Clearing House• CNPDB – Centralized Number Portability Database

NPGW – Number Portability Gateway• OSSGW – OSS Gateway• LSMS – Local Service Management SystemQNPDB – Query Number Portability Database


Administrative Infrastructure Overview

(Optional)Content

Providers

Operator Gateway(s)

Centralized NP Mgmt Sys

Operation

Centre (s)

Core Network

A. Mobile Operators

OSSGW

BSS/OSS

LSMS Live

NPDB

Vendor Specific Protocol(s)

Live

NPDBQueryNPDB

Console(s)

ACQ

Core Network

B. International GatewaysC. Fixed-line Operators

Vendor Specific Protocol(s)

Console(s)

LSMS Live

NPDBLive

NPDBQueryNPDB

API & Web

ACQ

QueryNPDB

QueryNPDB

Data

Data

Primary System

Disaster Recovery System

NPCH

NPCH

CNPDB

CNPDB

Sync


Signaling

Network

Signaling

Network

NPDB

MSC SMSC

NPDB

Network

Routing

Layer

Typical Signaling Architecture Components

Administrative

Layer

Management

System (LSMS)

Management

System (LSMS)

Inter-Network

SignalingNPDB

SMSCMSC

NPDB

Network

Routing

Layer

Centralized NP

Management

System

Operator N

Administrative

LayerManagement

Network

Operator 1

CNPDB

ISUP

SCCP

SIP

ENUM…

Provisioning &

Port process


EAGLE 5 MNP


EAGLE 5 - Database Features

MSC/

SSP

HLR NHLR 1…

DB

Eagle 5

– GSM Mobile Number portability (Voice, SMS and MMS)

G-Port – (GSM SRF based MNP)

– G-Port Circular Route Prevention

– Portability Check for MO SMS

– SMS MO NP

– SMS MT NP

– GSM Fixed Number portability

INP – (INAP Based Number Portability)

– Prepaid

IDP Relay – (MNP for Prepaid - GSM)

ATI Query

– ISUP NP

Triggerless Number Portability

– ATI Query

– ANSI Number Portability

A-Port (IS-41 SRF based MNP)

– NP Req (WIN Based Number Portability)

– ANSI NP Prepaid

Analyzed Info Relay – (MNP for Prepaid – IS-41)

– G-Flex – (IMSI or MSISDN Router)

– EIR – (Equipment Identity Register)


STP with integrated database functions

Other

Networks

Data

Provisioning

System

MSC

SSP

MSC

Signalling &

Network Intelligence

Layer

Base Station

SubscriberBSC

Subscriber

Eagle 5

DB

Eagle 5

DB

Eagle 5

DB

Eagle 5

DB

HLR SCP VMSC

Intelligent

Network

Layer

NP Portability

Status Exchange

with OLOs

e.g. via central

database


A database provisioning system that maintains a subscriber database for

support of query processing of the subscriber management and number

portability applications

EPAP interfaces with:

• A customer NP provisioning system if NPDB is to be administered directly by

the customer; or

• An LSMS if NPDB is to be administered by a centralized NP Administration

Centre

EAGLE 5 Provisioning Application Processor: EPAP


Database Replications


Database Capacity

• Up to 120M individual DN entries

• Up to 50,000 range DN entries

Throughput

• Supports 25+ Provisioning System Updates/sec

• Supports 250+ Provisioning System reads/sec

Support Multiple EAGLE 5s

• Automatic provisioning synchronization up to 12 EAGLE 5 nodes

EPAP Processing Capacity


Routing Options


Routing Options Indirect Routing (Onward Routing)

– Routing via number range holder

– Sometimes referred to as “Onward Routing”

– Operator database only holds imported and exported numbers

– Does not require All Call Query (ACQ)

Direct Routing

– Calls and MSUs are transferred directly from origination to subscription network without involvement of the Number Range Holder network

– Operator database need to hold all ported numbers

– Requires All Call Query


Indirect Routing

Originating network

ISUP IAM

Subscription network

NPDBNPDB

NPDB

Number Range

Holder network


4

3

2

SRI (MSISDN)

CdPA=MSISDN,

CgPA=GMSCA

SRI (MSISDN)

CdPA=HLRB or

MSISDN

CgPA=GMSCA

HLRA

GMSCA

Eagle

5

G-Port

SRI ack (MSRN)

CdPA=GMSCA

CgPA=HLRA

5

IAM (MSRN)

If the subscriber number is part of the own number range and the number has not been ported, the call is handled inside the originating network

Direct, Indirect, Partially Direct Routing, Call to Own Number

Originating Network A =

Subscription Network

IAM (MSISDN)

1


If the subscriber number is not from the own number range, the originating network routes the call to the number range holder network

The range holder network performs a MNP check and routes the call back to the origination network

This effect is known as tromboning

Indirect Routing, Call to Ported-in Number

4

3

SRI (MSISDN)

HLRA

GMSCA

Eagle

5

G-Port

Number Range Holder

Network

5 IAM (RN+MSISDN)

SRI ack

(MSRN=RN+MSISDN)

CdPA=GMSCB

CgPA=HLRB



IAM (MSISDN)

1

8

7

6

SRI

((RN+)MSISDN)

SRI

(MSISDN)

HLRB

GMSCB

Eagle

5

G-Port

SRI ack

(MSRN=MSISDN)

IAM (MSRN)

2IAM (MSISDN)

9



The Number Range Holder Network determines that it is the current subscription network and handles the call inside the network

Indirect Routing, Call to Non Ported Number

GMSCA

Number Range Holder Network =


2

IAM (MSISDN)

Originating

Network A

IAM (MSISDN)

1

5

4

3SRI (MSISDN)

SRI (MSISDN)HLRB

GMSCB

Eagle

5

G-Port

SRI ack

(MSRN)

IAM

(MSRN)

6


5

8

7

6SRI

((RN+)MSISDN)

SRI (MSISDN)

HLRC

GMSCC

Eagle

5

G-Port

SRI ack

(MSRN)

IAM

(MSRN)

9GMSCA

4

3SRI (MSISDN)

HLRB

GMSCB

Eagle

5

G-Port

Number Range

Holder Network B

2

Subscription

Network C

IAM (MSISDN) IAM

(RN+MSISDN)

Indirect Routing, Call to Cross-Ported Number

Originatin

g

Network A

IAM

(MSISDN)

1

SRI ack

(MSRN=

RN+MSISDN)


The Number Range Holder Network determines the current subscription network and forwards the call to the network

VMSCC


Direct Routing

Originating network Number Range

Holder network

ISUP IAM

Subscription network

NPDBNPDB

NPDB


4

3

2SRI (MSISDN)

SRI (MSISDN)

HLRA

GMSCA

Eagle

5

G-Port

SRI ack

(MSRN)

5

IAM (MSRN)

The originating network performs a MNP check

If the subscriber number is an own customer, the call is handled inside the network

Direct Routing, Call to Ported-in Number



IAM (MSISDN)

1VMSCA


The originating network performs a MNP check and determines the current subscription network

If the subscriber number is not an own customer, the call is routed to the subscription network

Direct Routing, Call to Non Ported Number

3

2SRI (MSISDN)

HLRA

GMSCA

Eagle

5

G-Port

4

IAM (MSISDN)

SRI ack

(MSRN=MSISDN)

Originating

Network A

IAM (MSISDN)

1

7

6

5SRI (MSISDN)

SRI (MSISDN)HLRB

GMSCB

Eagle

5

G-Port

IAM

(MSRN)

8

Number Range Holder Network =


SRI ack (MSRN)

VMSCB


The originating network performs a MNP check and determines the current subscription network

If the subscriber number is not an own customer, the call is routed to the subscription network

Direct Routing, Call to Cross-Ported Number

3

2SRI (MSISDN)

HLRA

GMSCA

Eagle

5

G-Port

4

IAM (RN+MSISDN)

SRI ack

(MSRN=MSISDN)

Originating

Network A

IAM (MSISDN)

1

7

6

5SRI

((RN+)MSISDN)

SRI (MSISDN)

HLRB

GMSCB

Eagle

5

G-Port

SRI ack

(MSRN)

IAM

(MSRN)

8

Subscription Network B ≠

Number Range Holder Network

VMSCB


EAGLE5 signaling approach


NP Product Family

ITU Based NP solutions

– Inter-Carrier NP Solutions (Service Provider Portability)

GSM G-Port Mobile Number Portability (G-Port): applicable to the GSM networks.

ANSI-41 A-Port MNP (A-Port): applicable to TDMA/CDMA networks

INAP-based Number Portability (INP): applicable to GSM/IS41 network and/or ITU based fixed-line networks.

– Intra-Carrier NP Solution

IS41->GSM Migration: Support number portability

– when an operator migrate its TDMA/CDMA networks to GSM or vice-versa

– Triggerless NP Solution using ISUP

ISUP Triggerless NP (based on intercept of ISUP IAM)

North America NP solution

– Local Number Portability (LNP): applicable to North America fixed-line and wireless GSM, TDMA

and CDMA networks


Service Provider Portability deployed in GSM networks

Subscribers change operators while retaining their MSISDN numbers

Based on Signaling Relay Function (a triggerless solution) defined in 3GPP TS 23.066

Intercepts MAP messages already flowing in network, thus creating minimum disruption to existing deployed network elements

Requires GTT

–If a number is ported out and the message is call-related, G-Port acts as an “NP HLR,” by responding to the switch with a MAP SRI ACK message.

–If a number is non-ported or ported-in, G-Port performs an HLR translation and forwards the translated message to the destination HLR.

GSM Portability : G-Port


MT to Non-ported or Imported Number

32

1

4

Recipient

Network

Originating

Network

SRI (MSISDN)

CdPA=MSISDN,

TT=SRI

CgPA=GMSCB

SRI (MSISDN)

CdPA=HLRB or

MSISDN

CgPA=GMSCBSRI ack (MSRN)

CdPA=GMSCB

CgPA=HLRB

IAM (MSRN) VMSCB

HLRB

G-Port

GMSCA

32

1

4

Recipient

Network

Originating

Network

SRI (MSISDN)

CdPA=MSISDN,

TT=SRI

CgPA=GMSCB

SRI (MSISDN)

CdPA=HLRB or

MSISDN

CgPA=GMSCBSRI ack (MSRN)

CdPA=GMSCB

CgPA=HLRB

IAM (MSRN) VMSCB

HLRB

G-Port

GMSCA


MT to Ported Out Number

21

3

Recipient

Network

Originating

Network

SRI (MSISDN)

CdPA=MSISDN,

CgPA=GMSCASRI ack (RN + MSISDN)

CdPA=GMSCA

CgPA=G-Port_MNP

IAM

(RN+MSISDN)

GMSCB

G-Port

GMSCA

21

3

Recipient

Network

Originating

Network

SRI (MSISDN)

CdPA=MSISDN,

CgPA=GMSCASRI ack (RN + MSISDN)

CdPA=GMSCA

CgPA=G-Port_MNP

IAM

(RN+MSISDN)

GMSCB

G-Port

GMSCA


A Trigger Based Solution

EO/MSC needs to be IN-equipped to detect IN triggering so that IN queries can be sent to external

network nodes for NPDB lookup

Trigger detection can be initiated from an Originating, Transit, Donor, or Subscription network

NP Server performs NPDB lookup based on the Called Party Number populated in INAP IDP to

determine if the number is a ported number

– If exported subscriber, NP Server returns a routing number

– If non-ported or imported, NP server instructs the EO/MSC to handle the call as it is

Handling of non-call related messages is based on the SRF function as defined in 3GPP TS23.066

Supports “triggered” solution based on Intelligent Network Application Protocol (INAP) InitialDP

message (IDP), defined by ITU Series Q and Supplement 2

INAP-based Portability: INP


Supports “triggered” INAP (Intelligent Network Application Protocol), defined by ITU Q. Series of specifications on TCAP/IN as well as supplement 2

Handling of non-call related messages

EO/MSC needs to be IN-equipped to set IN trigger points to detect messages that require NPDB lookup

Trigger detection can be initiated from an Originating, Transit, Donor, or Subscription network

INP may be used for several purposes

– NP in Fixed Networks (Operator and Geographical NP)

– MNP database query in fixed networks for direct routing

– FNP database query in mobile networks for direct routing

– Call related scenario in MNP (ACQ, QoD, QoHR)

INAP – Feature highlight


Call Flow for IN Based Solution

EO/MSC

2. INAP IDP Query

3a. INAP Connect

3b. INAP Continue

For call related messages only

1. incoming call

EO/MSC receives an incoming call and detects an IN trigger

EO/MSC sends NP Server an INAP IDP to query routing instructions

NP Server performs NPDB lookup to determine if the called party is a ported

number:

3a. If ported, NP Servers returns an INAP Connect Message with Routing

Number

3b. If not ported, NP Server returns an INAP Continue (or a CONNECT) Message

to route the call as is

NP

ServerNPD

B


Triggerless ITU ISUP NP

Intercept ISUP IAM message and perform NPDB lookup to determine portability status of the Called

Party Number encoded in the IAM

Include portability information (RN or SubNet ID) in the IAM message prior to forwarding the message to

its intended destination

Sample Applications:

– Upon receipt the modified IAM message from the EAGLE 5, the recipient switch (e.g., MSC)

populate the portability information in an INAP IDP message when querying a prepaid node

– A recipient switch can redirect the modified IAM based on the portability information encoded in the

IAM message


Signaling approach in detail

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.51Tekelec Confidential51 I Tekelec. For What’s Next.

GSM Solution

Affected Services: Mobile Terminating Calls


INP Call to Non-ported (or Ported-in Number)

Return INAP Continue Message

3

IAM

Continue

Originating

Network

Terminating

Network

InitialDP 1 2

Switch Switch

NPDB

SSP could be

in a different

network


INP Call to Ported(-out) Number

3

IAM (RN+DN)

Connect

DRA = RN+DN

Originating

Network

Terminating

Network

1 2

Switch Switch

Return INAP Connect Message

Destination Routing Address (DRA) = RN+DN, Operator can

provision to send the RN only

NPDB

InitialDP


INP Call related scenario in MNP (ACQ)Call to Non-Ported Number

Eagle

5

INP

MSC

B

SRI (CdPA=B)

CONTINUE

IDP (CdPN=B)

A

SRI (MSRN).

HLR

• INP imposes an additional dialog, which increases

The call setup delay

the CPU usage at MSC

The required number of links, …


G-Port MNP (call related) –Signalling Relay Function (SRF)

Eagle

5

G-Port

MSC

B

A

IAM (MSRN)

HLR

› The SRF based MNP solution uses existing SRI dialog

› The SRI message is relayed to the respective HLR for imported and own

subscribers

› Same principles may be applied to regular own subscribers

→ MSISDN based Flexible Routing is an integral part of G-Port

SRI (CdPA=B)

SRI (MSRN).

SRI (B)


G-Port MNP (call related)Signalling Relay Function (SRF)

Eagle

5

G-Port

MSC

B

A

IAM (RN+B)

HLR

› The SRI message is answered (MAP termination function) if exported or non

ported

→ MSC should add MSRN to the CDRs to allow for differentiated billing

SRI (CdPa=B)

SRI (MSRN=RN+B)


Call to a ported number –Query on ISUP Release

Eagle

5

G-Port1. IAM (CdPN=MSISDN)

Call is Released,

Number is

Ported to OLO

Call is routed

As if there is

No MNP

GMSCMSC

INP finds an entry,

which points to a OLO

and sends back a

CONNECT

2. IAM (CdPN=MSISDN)

GMSC

@OLO

3. REL (Cause=14)

MSC triggers

an IDP

4. IDP (CdPN=MSISDN)

5. CONNECT (DRA=NRN+MSISDN

MSC routes the call

To the respective OLO

HLR

6. IAM

(CdPN=NRN+MSISDN)


INP – QoHR (Query on HLR Release)

Eagle

5

G-Port

MSC

B

A

IAM (RN+B)

HLR

SRI (CdPA=B)

Unknown Subscriber

CONNECT (DRA=RN+B)

IDP (CdPN=B)


Summary Mobile Terminated Calls SRF is the preferred solution

– Least Intrusive

– Limited Overhead

– Implemented in numerous operators

Query on Release

– Very efficient and low overhead as long the number of ported subscribers is

low

– Issues:

Release with specific Release Cause Value may be a problem

Delay

– Has been implemented in Poland


All digital networks

Triggerless ISUP based solutions


Triggerless Number Portability How does it work?

– Eagle 5 intercepts ISUP IAM messages

– Extracts the CdPN

– Does a database search

– Prefixes the CdPN if the number is ported

Eagle

5

SAS

Switch

A

Transit

Switch

IAM (602123456)

IAM (RN 602123456)

IAM (RN 602123456)

Switch

@SN

602 123456


Triggerless Number Portability Advantages

Does not require an additional dialog to resolve

number portability

– Low delay

– No additional CPU requirements at the switch

– No additional protocol requirements at the switch, e.g.

INAP

– Does not use up triggerpoints that may be required for

other applications


Triggerless Number Portability Limitations

Eagle 5 cannot change the first leg of the bearer channel– I.e., calls may be routed via the number range holder (NRH) network

NRH does not have to perform NP database check

Possibly not allowed by regulation

Eagle

5

Switch

602 123456

A

Switch

@NRH

IAM (602123456)

IAM (RN 602123456)

IAM (RN 602123456)

Switch

@SN


Triggerless Number Portability Possible Workaround: ISUP Loop

Route calls on a loop via the Eagle 5

– If the number is ported, a RN is inserted

– If the number is not ported, the IAM is routed back unchanged

Drawback: Increases the workload at the switch

Eagle

5

Switch

602 123456

A

Switch

@SN

IAM (602123456)

IAM (RN 602123456)

IAM (RN 602123456)


Possible Workaround: Reroute on RELEASE

Route calls to the Eagle 5 ISS– If the number is ported, the Eagle 5 ISS returns a REL containing

the routing number and subscriber number in the redirection number parameter

– If the number is not ported, route the ISUP message to the next switch

Drawback: Some switches do not support this part of the ISUP specifications

In service in Mexico

Eagle

5

ISS

Switch

602 123456

A

Switch

@SN

IAM (602123456)

REL (RN 602123456)

IAM (RN 602123456)


Possible Workaround: Combined Solution

Combined Triggered and Triggerless Solution

– Triggerless where you can

– Triggered where you have to


Circular Route Prevention


Circular Route Prevention Problem

– Circular routing can occur due to incorrect information in one or more of the number portability databases.

– For example, network A has the correct routing information, indicating that the subscriber now belongs to network B. But network B may have the incorrect (old) information, indicating that the subscriber belongs to network A.

Effects

– Calls are looped around between the donor and subscription networks

Solution

– G-Port Circular Route Prevention (SRF solution)

– TIF Circular Route Prevention (Triggerless ISUP solution)

– INP Circular Route Prevention (Triggered INAP solution)


Network A determines Network B as the subscription network for a given MSISDN and forwards the call to it

Network B determines that the MSISDN is not an own subscriber and returns an error

On receipt of an SRI message. If a home RN is appended to the message; then the Eagle examines the DN before performing NPDB lookup as following:

– If DN is of a Ported-out number -> Circular Route conditions identified

– If DN is of a Ported-in number -> The Eagle relay the message to HLR

G-Port MNPPrevention of Circular Routing

3

2SRI (MSISDN)

HLRA

GMSCA

Eagle

5

G-Port

4 IAM (RN+MSISDN)

SRI ack

(MSRN=MSISDN)

Originating

Network A

IAM (MSISDN)

1

HLRB

GMSCB

Network B

6

5

SRI ((RN+)MSISDN)

CdPA=RN+MSISDN,

CgPA=GMSCB

UDTS

Eagle

5

G-Port



Network B determines that the MSISDN is not an own subscriber releases the call

On receipt of an INAP IDP message. If a home RN is appended to the CdPN; then the Eagle examines the DN before performing NPDB lookup as following:


– If DN is of a Ported-in number -> The Eagle replies with CONNECT operation

INP Prevention of Circular Routing(In Network B)

3

2SRI (MSISDN)

HLRA

GMSCA

Eagle

5

G-Port

4 IAM (RN+MSISDN)

SRI ack

(MSRN=MSISDN)

Originating

Network A

IAM (MSISDN)

1

HLRB

GMSCB

Network B

6

5

INAP IDP

CdPN=RN+MSISDN,

CgPA=GMSCB

INAP RELEASE CALL

Provisionable RCV

Eagle

5

INP



Network B determines that the MSISDN is not an own subscriber releases the call

On receipt of an ISUP IAM message. If a home RN is appended to the CdPN; then the Eagle examines the DN before performing NPDB lookup as following:


– If DN is of a Ported-in number -> The Eagle forwards the call to the GMSC

TIF NP Prevention of Circular Routing(In Network B)

3

2SRI (MSISDN)

HLRA

GMSCA

Eagle

5

G-Port

4 IAM (RN+MSISDN)

SRI ack

(MSRN=MSISDN)

Originating

Network A

IAM (MSISDN)

1

HLRB

GMSCB

Network B

Eagle

5

TIF

5 RELEASE


GSM Solution

Affected Services: Prepaid


MNP Effect on Prepaid

Main Problem: Differentiated On-Net/Off-Net Charging

Prepaid IN needs subscription network information in

real time


Prepaid Considerations Signalling in a Portability environment is further complicated when

we consider Pre-paid subscribers

Before any call is originated for a Prepaid subscriber the IN SCP is checked to ensure that the caller has enough credit to make the call

This credit check is normally performed using an INAP or CAMEL query (IDP) to an SCP (IN Node)

It is common for network operators to charge different rates if a subscriber is calling another network subscriber.

In this instance the SCP must be able to determine the subscription network of B-number to apply the corresponding rate. This requires the NP status of the B-number be known by the SCP.


Prepaid Number Portability Solution

There are 3 basic methods defined to provide the NP status to the

SCP: IDP Relay, SRI Query & ATI Query

IDP Relay involves sending the existing IDP dialogue via the NPDB

so that the B-number can be modified to include the NP status

ATI or SRI Query involve the Pre-paid SCP interrogating the NPDB to

determine the NP status after an IDP has been received

IDP Relay is the most efficient since it does not require additional

triggers on the SCP (i.e. no costly upgrade)


Prepaid Credit Check

IDP Relay

ISUP IAM

NPDB

1

2

3

SRI or ATI Query

ISUP IAM

NPDB

2

1

4

3


Mobile Originated call to a non-ported number or Imported OLO number

MSC Eagle

5

G-PortMSISDN

Eagle 5 ISS intercepts

the IDP and prefixes the

CdPNA 1. IDP (CdPN=MSISDN)

2. IDP (HLR-ID+MSISDN)

PP-

SCP

3. CONNECT (DRA=HLR-ID+MSISDN)

4. SRI (MSISDN=MSISDN)

HLR


Mobile Originated call to a exported, foreign ported or non-ported OLO number

Eagle 5 ISS intercepts

the IDP and prefixes the

CdPN

1. IDP (CdPN=MSISDN)

2. IDP (CdPN=RN+MSISDN)

3. CONNECT (DRA=RN+MSISDN)

4. IAM (CdPN=RN+MSISDN)

The call is

setup to the

respective

network

operator

Eagle

5

G-Port

PP-

SCP

MSC

MSISDN

A


ATI Interface at Eagle

Eagle can also provide an ATI interface for MNP Query

Depending on IN vendor and implementation the easier solution

– Standards based

– No dependencies on INAP or CAMEL interface

Could be used in addition to or instead of IDP Relay


Ported-out or Cross-Ported subscriber

Eagle

5

G-Port

2. SRI_Ack

(MSRN=RN+MSISDN)

1. SRI

(CdPA=MSISDN, TT=9)

SCP

Originating

Network A

1. ATI

(MSISDN)

2. ATI_Rsp

(RN+MSISDN)


Ported-in subscriber

Eagle

5

G-Port

2. SRI_Ack

(MSRN=HLR-Id+MSISDN)

1. SRI

(CdPA=MSISDN, TT=9)

SCP

Originating

Network A

1. ATI

(MSISDN)

2. ATI_Rsp

(HLR-Id+MSISDN)


Non-ported own subscriber

Eagle

5

G-Port

2. SRI_Ack

(MSRN=MSISDN)

1. SRI

(CdPA=MSISDN, TT=9)

SCP

Originating

Network A

1. ATI

(MSISDN)

2. ATI_Rsp

(MSISDN)


Non-ported foreign subscriber

Eagle

5

G-Port

2. SRI_Ack

(MSRN=Prefix+MSISDN)

1. SRI

(CdPA=MSISDN, TT=9)

SCP

Originating

Network A

1. ATI

(MSISDN)

2. ATI_Rsp

(Prefix+MSISDN)


SMS & MMS


Eagle

5

G-PortSMS to B

A

HLR

SRI_for SM (CdPA=B)

G-Port MNP (non-call related)

› Non-call related messages are relayed, e.g. HLR query for SMS delivery,

to the respective network element for imported and own subscribers

to the SCCP gateway at the respective operator if exported or non ported

SRI_for SM (CdPA=B)

SRI_for SM (CdPA=RN+B)

SCCP

GW

OLO

1. CdPN is own

Subscriber

2. CdPN is not own

subscriber

SMSC


MNP Check for Mobile Originated SMS

Problem

– Ported out subscribers reprogram their handsets to continue using

previous operator Short Message Service Center

– Number range check does not work any more

Effects

– Revenue lost for the operator by providing the service without being able

to charge it

Solution

– Tekelec’s “MNP Check for Mobile Originated SMS” Solution


Portability Check for Mobile Originated SMS

Protects own SMSCs from misuse

Avoids MNP database at the SMSCs

Eagle

5

G-Port

MSC

MO_FSM

A MO_FSM

MO_FSM

MAP Error

IF A is an own customer

Forward SMS to SMSC

IF A is not an own customer

Filter SMS and return error

SMSC


ITU NP support for MO-SMS

› Protects own SMSC from misuse

› Allows for On-net/Off-net charging

› Avoids MNP database at the SMSCs

› Avoids additional dialog to dip NPDB

Eagle

5SMS

NP

MSC

MO_FSM

A

MO_FSM

MAP SM UI=RN+B

MO_FSM

MAP Error

IF A is an own customer

•Forward SMS to SMSC

•Prefix B-Number

IF A is not an

own customer

Filter SMS and

return error

SMSC

CR (RN+B)

SCP/

RI

Ack

SRI_for_SM (SCCP CdPA=RN+B,

MAP MSISDN=B)

SCCP

GW

OLO

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.89 89

Portability Check for Mobile Originated SMS (HLR based)

MSC

MO_FSM

A MO_FSM

SRI_for_SM/ATI (A)

SMSC

CR (RN+B)

SCP/

RIHLR

Ack (A)

SRI_for_SM/ATI (B)

Ack (RN+B)

Ack

Two additional

database queries

If SRI_for_SM

Query is used, the

MSU may also have

to be relayed to the

respective

subscription network


Q&A

Thank you

Contact me: [email protected]

mobile number portability_workshop

Documents

originating network

number range holder

number number range

oracle andor

transit network

mobile number port

number range ndc

originated recipient