Mobile Number Portability

in India
Need of Number Portability

Subscribers benefit:
Convenience of customer to personalize the same number across the Operators,
Locations and Services. (No age for your number.)
Better QOS, more features and services, better tariff plans for customers.
No cost incurred to notify the new contact details to the others( friends, family,
business..)

Operator s benefit:
Healthy competition and an opportunity to explore more services/features.
Operator with best QOS will gain the subscribers.
Introduction of innovative service.

Regulatorys benefit:
A better means to facilitate the subscribers the best of services from different
operators.
Use this infrastructure to resolve Directory Number resource problems.
Number portability definition
Number portability enables a subscriber to switch
between services, locations, or operators while retaining
the original mobile number, without compromising on
quality, reliability, services and operational convenience.
Operator
Portability
Location
Portability
Service
Portability
FNP MNP
Number
Portability
Out of several types of number portability DoT has
recommended Mobile Number Portability (MNP) for all
mobile service operators.
Ph-1 (Sep09)- All metro and class A circles MNP enabled.
Ph-2 (Mar10)- Rest all circles MNP enabled.
Two central clearing houses for MNP database covering
North-West zone (Syniverse) and South-East zone
(Telecordia).
These CCH will download the MNP database in operators
NPDB on daily basis.
MNP will be restricted only for intra circle operators.
MNP will be allowed between CDMA and GSM operators.
ACQ (All Call Query) direct routing method to implement
MNP.
Break before make porting process with negotiation period of
max 2 days and service interruption of max 30 minutes.

Number Portability for India
MNP Terminologies related to
network
Originatin
g
Network
Donor
Network
Recipien
t
Network
NPDB
Originating Network : Network of the calling party
Donor Network : Previous subscription of Called party
Recipient Network : Present subscription of Called party
NPDB : Number Portability Data Base (maintains
portability database and provides routing
instructions)
(ACQ) All call query- Direct routing method
Whenever the call is
originated, the
Originating n/w will
query its NPDB
NPDB will
acknowledge the
query by adding a
prefix (LRN) to the
B MSISDN if the B
MSISDN is ported
out.
Based on the prefix
(LRN) the
Originating n/w will
route the call to the
recipient n/w without
involving the Donor
network.
Originating
Network
Donor
Network
Recipient
Network
ORIG NW
NPDB
L
R
N

+

B
-
M
S
I
S
D
N

B
-
M
S
I
S
D
N

ACQ is called as direct routing as donor network will not be included
during entire call flow.
LRN + B-MSISDN
LRN codes circulated by TRAI
SCP
SMSC HLR MSC
BOSS/BSCS
NPGW
MCH-Zone2
Syniverse
MMSC
SOAP/XML
IP
National NPDB
Layer
Service Process
Layer
MNP Provisioning
& Routing Process
Layer (Network Domain)
MNP Provisioning
Layer (IT Domain)
MNP architecture
MCH-Zone1
Telecordia
MML
MML
STP NPDB STP NPDB
STP-NEM
Will be residing in MCH vendor premises
Will be residing in operators premises
MNP terminologies related to porting process.
MCH (Central Clearing House): To be managed by 3
rd
Party finalized by
DoT. Zone-1(North,West) MCH would be of Syniverse and Zone-2
(South,East) MCH would be of Telecordia. Both MCH, in downward
direction will be talking to NPGW of all operators to download the porting
data on daily basis. Connectivity: IP, Protocol: SOAP/XML.

NPGW(NP Gateway): To be managed by IT team. On one side it would be
talking to BOSS/BSCS for provisioning port in subscribers in to HLRs and
on other side it would be talking to STP NEM (Network Element Manager) to
download porting data. Connectivity : IP, Protocol: NPGW vendor specific.

STP NEM (Network Element Manager): To be managed by network team.
NEM would be STP vendor specific. NEM would be centralized node which
will be talking to all STPs to dump porting data in to STP NPDB.
Connectivity: IP, Protocol: MML.

STP NPDB (Number Portability Database): To be managed by network
team. All core network elements like MSC/MSS, IN, HLR, SMSC, MMSC,
SGSN etc will be connected to STPs and STP will refer its own NPDB to
know the porting status of called party for all scenarios which require NP
check like Calls, SMS, MMS etc. Connectivity: IP/TDM, Protocol: All GSM
protocols (MAP, CAP, CS1+, CS1, CS2, INAP, SIGTRAN etc.
Will be residing in MCH vendors premises
Will be residing in operators premises
CNPMS: CNPMS is nothing but MCH (Central Clearing House)
DNO OSSGW & RNO OSS GW: Donor OSS GW & Recipient OSS GW. OSS GW is nothing but IT piece
of NPGW.
LSMS/QNPDB: LSMS/QNPDB is nothing but network piece of NPGW.
Impact of MNP on Call Flow.
STP(SRF-NPDB)
HLR
VMSC VMSC
1. Originates a call
2. SRI (MSISDN)
CdPA = MSISDN
CgPA - VMSC
3. SRI (MSISDN)
CdPA = HLR
CgPA - VMSC
4. SRI_ACK(MSRN)
CdPA = VMSC
CgPA - HLR
6. IAM (MSRN)
Call-Related Service: Post-paid subs calls
Regular own subscriber
Signaling flow of SRF-ACQ (Call Related
Functions)
5. SRI_ACK(MSRN)
CdPA = VMSC
CgPA - HLR
STP(SRF-NPDB)
HLR
VMSC VMSC
1. Originates a call
2. SRI (MSISDN)
CdPA = MSISDN
CgPA - VMSC
3. SRI (MSISDN)
CdPA = HLR
CgPA - VMSC
4. SRI_ACK(MSRN)
CdPA = VMSC
CgPA - HLR
6. IAM (MSRN)
Call-Related Service: Post-paid subs calls
Ported in subscriber
Signaling flow of SRF-ACQ (Call Related
Functions)
5. SRI_ACK(MSRN)
CdPA = VMSC
CgPA - HLR
STP(SRF-NPDB)
HLR
VMSC
1. Originates a call
2. SRI (MSISDN)
CdPA = MSISDN
CgPA - VMSC
3. SRI_ACK(RN+MSISDN)
CdPA = VMSC
CgPA = STP-NPDB
4. IAM
(RN+MSISDN)
Call-Related Service: Post-paid subs calls
Ported out or cross ported subscriber
GMSC GMSC
VMSC
STP(SRF-NPDB)
HLR
5. IAM
(RN+MSISDN)
10. IAM
(MSRN)
6. SRI (MSISDN)
CdPA = MSISDN
CgPA = GMSC
7. SRI (MSISDN)
CdPA = HLR
CgPA = VMSC
8. SRI_ACK(MSRN)
CdPA = VMSC
CgPA = HLR
ORIGINAL
NETWORK
OTHER
NETWORK
Signaling flow of SRF-ACQ (Call Related
Functions)
9. SRI_ACK(MSRN)
CdPA = VMSC
CgPA = HLR
STP(SRF-NPDB)
HLR
VMSC
1. Originates a call
2. SRI (MSISDN)
CdPA = MSISDN
CgPA - VMSC
3. SRI_ACK(RN+MSISDN)
CdPA = VMSC
CgPA = STP-NPDB
4. IAM
(MSISDN)
Call-Related Service: Post-paid subs calls
regular foreign subscriber
GMSC GMSC
VMSC
STP(SRF-NPDB)
HLR
5. IAM
(MSISDN)
10. IAM
(MSRN)
6. SRI (MSISDN)
CdPA = MSISDN
CgPA = GMSC
7. SRI (MSISDN)
CdPA = MSISDN
CgPA = VMSC
8. SRI_ACK(MSRN)
CdPA = VMSC
CgPA = HLR
ORIGINAL
NETWORK
OTHER
NETWORK
Signaling flow of SRF-ACQ (Call Related
Functions)
9. SRI_ACK(MSRN)
CdPA = VMSC
CgPA = HLR
STP(SRF-NPDB)
HLR
VMSC VMSC
1. Originates a call
6
.

S
R
I

(
M
S
I
S
D
N
)

C
d
P
A

=

M
S
I
S
D
N

C
g
P
A

-

V
M
S
C

10. IAM (MSRN)
Call-Related Service: Pre-paid subs calls
Regular own subscriber
SCP
2
.

I
D
P

(
M
S
I
S
D
N
)

Signaling flow of SRF-ACQ (Call Related
Functions)
5
.

C
o
n
t
i
n
u
e

9
.

S
R
I
_
A
C
K
(
M
S
R
N
)

C
d
P
A

=

V
M
S
C

C
g
P
A

-

H
L
R

STP(SRF-NPDB)
HLR
VMSC VMSC
1. Originates a call
6
.

S
R
I

(
M
S
I
S
D
N
)

C
d
P
A

=

M
S
I
S
D
N

C
g
P
A

-

V
M
S
C

10. IAM (MSRN)
Call-Related Service: Pre-paid subs calls
Ported in subscriber
SCP
2
.

I
D
P

(
M
S
I
S
D
N
)

Signaling flow of SRF-ACQ (Call Related
Functions)
5
.

C
o
n
t
i
n
u
e

9
.

S
R
I
_
A
C
K
(
M
S
R
N
)

C
d
P
A

=

V
M
S
C

C
g
P
A

-

H
L
R

STP(SRF-NPDB)
HLR
VMSC
1. Originates
a call
6
.

S
R
I

(
M
S
I
S
D
N
)

C
d
P
A

=

M
S
I
S
D
N

C
g
P
A

-

V
M
S
C

7
.

S
R
I
_
A
C
K
(
R
N
+
M
S
I
S
D
N
)

C
d
P
A

=

V
M
S
C

C
g
P
A

=

H
L
R
B

8. IAM
(RN+MSISDN)
Call-Related Service: Pre-paid subs calls
Ported out or cross ported subscriber
GMSC GMSC
VMSC
STP(SRF-NPDB)
HLR
9. IAM
(RN+MSISDN)
14. IAM
(MSRN)
1
0
.

S
R
I

(
M
S
I
S
D
N
)

C
d
P
A

=

M
S
I
S
D
N

C
g
P
A

=

G
M
S
C

1
1
.

S
R
I

(
M
S
I
S
D
N
)

C
d
P
A

=

H
L
R

C
g
P
A

=

V
M
S
C

1
2
.

S
R
I
_
A
C
K
(
M
S
R
N
)

C
d
P
A

=

V
M
S
C

C
g
P
A

=

H
L
R

ORIGINAL
NETWORK
OTHER
NETWORK
SCP
2
.

I
D
P


(
M
S
I
S
D
N
)

Signaling flow of SRF-ACQ (Call Related
Functions)
5
.

C
o
n
t
i
n
u
e

1
3
.

S
R
I
_
A
C
K
(
M
S
R
N
)

C
d
P
A

=

V
M
S
C

C
g
P
A

=

H
L
R

STP(SRF-NPDB)
HLR
VMSC
1. Originates a call
6
.

S
R
I

(
M
S
I
S
D
N
)

C
d
P
A

=

M
S
I
S
D
N

C
g
P
A

-

V
M
S
C

7
.

S
R
I
_
A
C
K
(
R
N
+
M
S
I
S
D
N
)

C
d
P
A

=

V
M
S
C

C
g
P
A

=

S
T
P
-
N
P
D
B

8. IAM
(MSISDN)
Call-Related Service: Pre-paid subs calls
regular foreign subscriber
GMSC GMSC
VMSC
STP(SRF-NPDB)
HLR
9. IAM
(MSISDN)
14. IAM
(MSRN)
1
0
.

S
R
I

(
M
S
I
S
D
N
)

C
d
P
A

=

M
S
I
S
D
N

C
g
P
A

=

G
M
S
C

1
1
.

S
R
I

(
M
S
I
S
D
N
)

C
d
P
A

=

M
S
I
S
D
N

C
g
P
A

=

V
M
S
C

1
2
.

S
R
I
_
A
C
K
(
M
S
R
N
)

C
d
P
A

=

V
M
S
C

C
g
P
A

=

H
L
R

ORIGINAL
NETWORK
OTHER
NETWORK
SCP
2
.

I
D
P

(
M
S
I
S
D
N
)

Signaling flow of SRF-ACQ (Call Related
Functions)
5
.

C
o
n
t
i
n
u
e

1
3
.

S
R
I
_
A
C
K
(
M
S
R
N
)

C
d
P
A

=

V
M
S
C

C
g
P
A

=

H
L
R

SMS MT Relay
IDEA subs sends SMS, B number is regular-own or ported-in
VMSC
HLR
STP
VMSC
6.SRI_FSM
(MSISDN)
CdPA=HLR
CgPA=SMSC
3.MO_FSM
(MSISDN)
CdPA=SMSC
CgPA=VMSC
SMSC
4. MO_FSM
(MSISDN)
CdPA=SMSC
CgPA=VMSC
7.SRI_FSM_ACK
(IMSI, VMSC)
5.SRI_FSM
(MSISDN)
CdPA=MSISDN
CgPA=SMSC
8. MT_FSM
SCP
1.IDPSMS (MSISDN)

2.IDPSMS_ACK

SMS MT Relay
IDEA subs sends SMS, B number is ported-out or cross-ported
HLR
STP
VMSC
3.MO_FSM
(MSISDN)
CdPA=SMSC
CgPA=VMSC
SMSC
4. MO_FSM
(RN+MSISDN)
CdPA=SMSC
CgPA=VMSC
5.SRI_FSM (MSISDN)
CdPA=MSISDN
CgPA=SMSC
GMSC
Other
Network
6.SRI_FSM (MSISDN)
CdPA=RN+MSISDN
CgPA=SMSC
HLR
7.SRI_FSM_ACK
(IMSI, VMSC)
GMSC
Other
Network
HLR
8. MT_FSM
SCP
1.IDPSMS (RN+MSISDN)

2.IDPSMS_ACK

SMS MT Relay
IDEA subs sends SMS, B number is Regular-foreign subscriber
HLR
STP
VMSC
3.MO_FSM (MSISDN)
CdPA=SMSC CgPA=VMSC
SMSC
4. MO_FSM
(MSISDN)
CdPA=SMSC
CgPA=VMSC
5.SRI_FSM (MSISDN)
CdPA=MSISDN
CgPA=SMSC
GMSC
Other
Network
6.SRI_FSM (MSISDN)
CdPA= MSISDN
CgPA=SMSC
HLR
7.SRI_FSM_ACK
(IMSI, VMSC)
8. MT_FSM
SCP
1.IDPSMS (MSISDN)

2.IDPSMS_ACK

MMS solution
MMS platform can apply charging based on called
subscribers domain name.
MMSC can know the called subscribers domain name based
on IMSI returned from HLR in Sri_for_SM solution (relation
data between domain name and IMSI number range is
configured in MMSC).
The relation data between domain name and IMSI number
ranges is configured in MMSC. When MMSC receives a
MMS, MMSC can send Sri_for_SM, STP will intercept the
message and route it to correct HLR. HLR will returned the
called IMSI to MMSC, MMSC can know the domain name
which the called subscriber belongs to, so MMSC can route
the MMSC correctly based on returned IMSI from HLR .
MMS MT
IDEA subs sends MMS, B number is regular-own or ported-in
MMS MT
IDEA subs sends MMS, B number is ported-out or cross-ported
MMS MT
IDEA subs sends MMS, B number is Regular foreign subscriber
Thanks & Happy learning