36924069-MNP-Call-Flow
Transcript of 36924069-MNP-Call-Flow
-
5/26/2018 36924069-MNP-Call-Flow
1/27
Mobi le Number Portab i li ty
in Ind ia
-
5/26/2018 36924069-MNP-Call-Flow
2/27
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.
-
5/26/2018 36924069-MNP-Call-Flow
3/27
Number portability definition
Number portability enables a subscriber to switch
between services, locations, or operators while retainingthe original mobile number, without compromising onquality, reliability, services and operational convenience.
Operator
Portability
Location
Portability
Service
Portability
FNP MNP
Number
Portability
-
5/26/2018 36924069-MNP-Call-Flow
4/27
Out of several types of number portability DoT has
recommended Mobile Number Portability (MNP) for allmobile 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 operatorsNPDB 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 ofmax 2 days and service interruption of max 30 minutes.
Number Portability for India
-
5/26/2018 36924069-MNP-Call-Flow
5/27
MNP Terminologies related to
network
Originatin
gNetwork
DonorNetwork
Recipien
t
NetworkNPDB
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)
-
5/26/2018 36924069-MNP-Call-Flow
6/27
(ACQ) All call query- Direct routing method
Whenever the call isoriginated, theOriginating n/w willquery its NPDB
NPDB willacknowledge thequery by adding aprefix (LRN) to theB MSISDN if the BMSISDN is portedout.
Based on the prefix(LRN) theOriginating n/w will
route the call to therecipient n/w withoutinvolving the Donornetwork.
Originating
Network
Donor
Network
Recipient
Network
ORIG NW
NPDB
LRN
+B-MSISDN
B-MSISDN
ACQ is called as direct routing as donor network will not be included
during entire call flow.
LRN + B-MSISDN
-
5/26/2018 36924069-MNP-Call-Flow
7/27
LRN codes circulated by TRAI
-
5/26/2018 36924069-MNP-Call-Flow
8/27
SCP SMSCHLRMSC
BOSS/BSCSNPGW
MCH-Zone2
Syniverse
MMSC
SOAP/XML
IP
National NPDBLayer
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
-
5/26/2018 36924069-MNP-Call-Flow
9/27
MNP terminologies related to porting process. MCH (Central Clearing House):To be managed by 3rdParty 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 portingdata on daily basis. Connectivity: IP, Protocol: SOAP/XML.
NPGW(NP Gateway):To be managed by IT team. On one side it would betalking to BOSS/BSCS for provisioning port in subscribers in to HLRs andon other side it would be talking to STP NEM (Network Element Manager) todownload 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 whichwill 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 networkteam. 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 toknow the porting status of called party for all scenarios which require NPcheck like Calls, SMS, MMS etc. Connectivity: IP/TDM, Protocol: All GSMprotocols (MAP, CAP, CS1+, CS1, CS2, INAP, SIGTRAN etc.
Will be residing in MCH vendors premises
Will be residing in operators premises
-
5/26/2018 36924069-MNP-Call-Flow
10/27
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.
-
5/26/2018 36924069-MNP-Call-Flow
11/27
Impac t o f MNP on Call Flow.
-
5/26/2018 36924069-MNP-Call-Flow
12/27
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 callsRegular own subscriber
Signaling flow of SRF-ACQ (Call Related
Functions)
5. SRI_ACK(MSRN)
CdPA = VMSC
CgPA - HLR
-
5/26/2018 36924069-MNP-Call-Flow
13/27
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 callsPorted in subscriber
Signaling flow of SRF-ACQ (Call Related
Functions)
5. SRI_ACK(MSRN)
CdPA = VMSC
CgPA - HLR
-
5/26/2018 36924069-MNP-Call-Flow
14/27
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
NETWORKOTHER
NETWORK
Signaling flow of SRF-ACQ (Call Related
Functions)
9. SRI_ACK(MSRN)
CdPA = VMSC
CgPA = HLR
-
5/26/2018 36924069-MNP-Call-Flow
15/27
STP(SRF-NPDB)
HLR
VMSC1. 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
NETWORKOTHER
NETWORK
Signaling flow of SRF-ACQ (Call Related
Functions)
9. SRI_ACK(MSRN)
CdPA = VMSC
CgPA = HLR
-
5/26/2018 36924069-MNP-Call-Flow
16/27
STP(SRF-NPDB)
HLR
VMSC VMSC
1. Originates a call
6.
SR
I(MSISDN)
CdPA
=MSISDN
CgPA
-VMSC
10. IAM (MSRN)
Call-Related Service: Pre-paid subs calls
Regular own subscriberSCP
2.
ID
P(MSISDN)
Signaling flow of SRF-ACQ (Call Related
Functions)
5.C
ontinue
9.SRI_AC
K(MSRN)
CdPA=V
MSC
CgPA-HLR
-
5/26/2018 36924069-MNP-Call-Flow
17/27
STP(SRF-NPDB)
HLR
VMSC VMSC
1. Originates a call
6.SRI(M
SISDN)
CdPA=M
SISDN
CgPA-VMSC
10. IAM (MSRN)
Call-Related Service: Pre-paid subs calls
Ported in subscriberSCP
2.IDP(M
SISDN)
Signaling flow of SRF-ACQ (Call Related
Functions)
5.Co
ntinue
9.
SRI_ACK
(MSRN)
CdPA=VM
SC
CgPA-HLR
Signaling flow of SRF ACQ (Call Related
-
5/26/2018 36924069-MNP-Call-Flow
18/27
STP(SRF-NPDB)
HLR
VMSC
1. Originates
a call
6.SRI(MSISDN)
CdPA=MSISDN
CgPA-VMSC
7.SRI_ACK(RN+MSISDN)
CdPA=VMSC
CgPA=HLRB
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)
10.
SRI(MSISDN)
CdPA=MSISDN
CgPA=GMSC
11.SRI(MSISDN)
CdPA=HLR
CgPA=VMSC
12.
SRI_ACK(MSRN)
CdPA=VMSC
CgPA=HLR
ORIGINAL
NETWORK
OTHER
NETWORK
SCP
2.IDP
(MSISDN)
Signaling flow of SRF-ACQ (Call Related
Functions)
5.
Continue
13.SRI_ACK(MSRN)
Cd
PA=VMSC
Cg
PA=HLR
-
5/26/2018 36924069-MNP-Call-Flow
19/27
STP(SRF-NPDB)
HLR
VMSC
1. Originatesa call
6.SRI(MSISDN)
Cd
PA=MSISDN
Cg
PA-VMSC
7.S
RI_ACK(RN+MSISDN)
CdPA=VMSC
CgPA=STP-NPDB
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)
10.SRI(MSISDN)
Cd
PA=MSISDN
Cg
PA=GMSC
11.SRI(MSISDN)
CdPA=MSISDN
CgPA=VMSC
12.SRI_ACK(MSRN)
CdPA=VMSC
CgPA=HLR
ORIGINALNETWORK
OTHER
NETWORK
SCP
2.ID
P(MSISDN)
Signaling flow of SRF-ACQ (Call Related
Functions)
5.Continue
1
3.
SRI_ACK(MSRN)
C
dPA=VMSC
C
gPA=HLR
-
5/26/2018 36924069-MNP-Call-Flow
20/27
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=SMSCCgPA=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
-
5/26/2018 36924069-MNP-Call-Flow
21/27
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
Network6.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
-
5/26/2018 36924069-MNP-Call-Flow
22/27
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
Network6.SRI_FSM (MSISDN)CdPA= MSISDN
CgPA=SMSC
HLR
7.SRI_FSM_ACK
(IMSI, VMSC)
8. MT_FSM
SCP
1.IDPSMS (MSISDN)
2.IDPSMS_ACK
-
5/26/2018 36924069-MNP-Call-Flow
23/27
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.
-
5/26/2018 36924069-MNP-Call-Flow
24/27
MMS MT
IDEA subs sends MMS, B number is regular-own or ported-in
MMS MT
-
5/26/2018 36924069-MNP-Call-Flow
25/27
MMS MT
IDEA subs sends MMS, B number is ported-out or cross-ported
-
5/26/2018 36924069-MNP-Call-Flow
26/27
MMS MT
IDEA subs sends MMS, B number is Regular foreign subscriber
-
5/26/2018 36924069-MNP-Call-Flow
27/27
Thanks & Happy learning