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.
Number
Portability
Operator Portability
Location Portability
Service Portability
FNP
MNP
Number Portability for India
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.
MNP Terminologies related to network
Donor Network
Originatin g
Recipien t Network
NPDB
Network
Originating Network Donor Network Recipient Network NPDB
: Network of the calling party : Previous subscription of Called party : Present subscription of Called party : 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 Recipient ORIG NW NPDB will acknowledge the Network NPDB query by adding a prefix (LRN) to the B MSISDN if the B LRN + B-MSISDN MSISDN is ported out. Based on the prefix Originating Donor (LRN) the Network Network Originating n/w will route the call to the recipient n/w without involving the Donor network. ACQ is called as direct routing as donor network will not be included during entire call flow.
LRN + B-MSISDN B-MSISDN
LRN codes circulated by TRAI
MNP architecture
National NPDB Layer
MCH-Zone1 Telecordia MCH-Zone2 Syniverse
MNP Provisioning Layer (IT Domain)
SOAP/XML BOSS/BSCS NPGW IP
MNP Provisioning & Routing Process Layer (Network Domain)
MML STP-NEM STP NPDB
MML STP NPDB
Service Process Layer MSC HLR SCP SMSC
MMSC
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 3rd 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.
Signaling flow of SRF-ACQ (Call Related Functions)
HLR
3. SRI (MSISDN) CdPA = HLR CgPA - VMSC
Call-Related Service: Post-paid subs calls Regular own subscriber
4. SRI_ACK(MSRN) CdPA = VMSC CgPA - HLR
STP(SRF-NPDB)
2. SRI (MSISDN) CdPA = MSISDN CgPA - VMSC
5. SRI_ACK(MSRN) CdPA = VMSC CgPA - HLR
VMSC
1. Originates a call
6. IAM (MSRN)
VMSC
Signaling flow of SRF-ACQ (Call Related Functions)
HLR
3. SRI (MSISDN) CdPA = HLR CgPA - VMSC
Call-Related Service: Post-paid subs calls Ported in subscriber
4. SRI_ACK(MSRN) CdPA = VMSC CgPA - HLR
STP(SRF-NPDB)
2. SRI (MSISDN) CdPA = MSISDN CgPA - VMSC
5. SRI_ACK(MSRN) CdPA = VMSC CgPA - HLR
VMSC
1. Originates a call
6. IAM (MSRN)
VMSC
Signaling flow of SRF-ACQ (Call Related Functions)
Call-Related Service: Post-paid subs calls Ported out or cross ported subscriber
HLR HLR
ORIGINAL NETWORK STP(SRF-NPDB)
7. SRI (MSISDN) CdPA = HLR CgPA = VMSC
8. SRI_ACK(MSRN) OTHER CdPA = VMSC NETWORK CgPA = HLR
STP(SRF-NPDB)
2. SRI (MSISDN) CdPA = MSISDN CgPA - VMSC
3. SRI_ACK(RN+MSISDN) CdPA = VMSC CgPA = STP-NPDB
6. SRI (MSISDN) CdPA = MSISDN CgPA = GMSC
9. SRI_ACK(MSRN) CdPA = VMSC CgPA = HLR
VMSC
1. Originates a call
4. IAM (RN+MSISDN)
GMSC
5. IAM (RN+MSISDN)
GMSC
10. IAM (MSRN)
VMSC
Signaling flow of SRF-ACQ (Call Related Functions)
Call-Related Service: Post-paid subs calls regular foreign subscriber
HLR HLR
ORIGINAL NETWORK STP(SRF-NPDB)
7. SRI (MSISDN) CdPA = MSISDN CgPA = VMSC
8. SRI_ACK(MSRN) OTHER CdPA = VMSC NETWORK CgPA = HLR
STP(SRF-NPDB)
2. SRI (MSISDN) CdPA = MSISDN CgPA - VMSC
3. SRI_ACK(RN+MSISDN) CdPA = VMSC CgPA = STP-NPDB 4. IAM (MSISDN)
6. SRI (MSISDN) CdPA = MSISDN CgPA = GMSC
9. SRI_ACK(MSRN) CdPA = VMSC CgPA = HLR 10. IAM (MSRN)
VMSC
1. Originates a call
GMSC
5. IAM (MSISDN)
GMSC
VMSC
Signaling flow of SRF-ACQ (Call Related Functions)
SCP
Call-Related Service: Pre-paid subs calls Regular own subscriber HLR
STP(SRF-NPDB)
2. IDP (MSISDN)
6. SRI (MSISDN) CdPA = MSISDN CgPA - VMSC
5. Continue
VMSC
1. Originates a call
9. SRI_ACK(MSRN) CdPA = VMSC CgPA - HLR
VMSC
10. IAM (MSRN)
Signaling flow of SRF-ACQ (Call Related Functions)
SCP
Call-Related Service: Pre-paid subs calls Ported in subscriber
HLR
STP(SRF-NPDB)
VMSC
10. IAM (MSRN) 1. Originates a call
9. SRI_ACK(MSRN) CdPA = VMSC CgPA - HLR
2. IDP (MSISDN)
5. Continue
6. SRI (MSISDN) CdPA = MSISDN CgPA - VMSC
VMSC
Signaling flow of SRF-ACQ (Call Related Functions)
ORIGINAL NETWORK SCP
11. SRI (MSISDN) CdPA = HLR CgPA = VMSC
HLR HLR
12. SRI_ACK(MSRN) CdPA = VMSC CgPA = HLR
OTHER NETWORK
7. SRI_ACK(RN+MSISDN) CdPA = VMSC CgPA = HLRB
STP(SRF-NPDB)
STP(SRF-NPDB)
13. SRI_ACK(MSRN) CdPA = VMSC CgPA = HLR
VMSC
8. IAM (RN+MSISDN)
GMSC
10. SRI (MSISDN) CdPA = MSISDN CgPA = GMSC
6. SRI (MSISDN) CdPA = MSISDN CgPA - VMSC
5. Continue
2. IDP (MSISDN)
9. IAM (RN+MSISDN)
GMSC
14. IAM (MSRN)
VMSC
1. Originates a call
Call-Related Service: Pre-paid subs calls Ported out or cross ported subscriber
ORIGINAL NETWORK
1. Originates a call
2. IDP (MSISDN)
SCP
5. Continue
STP(SRF-NPDB)
Signaling flow of SRF-ACQ (Call Related Functions)
VMSC
6. SRI (MSISDN) CdPA = MSISDN CgPA - VMSC 7. SRI_ACK(RN+MSISDN) CdPA = VMSC CgPA = STP-NPDB 8. IAM (MSISDN)
HLR
GMSC
9. IAM (MSISDN) 10. SRI (MSISDN) CdPA = MSISDN CgPA = GMSC 11. SRI (MSISDN) CdPA = MSISDN CgPA = VMSC
STP(SRF-NPDB)
GMSC
14. IAM (MSRN)
HLR
12. SRI_ACK(MSRN) CdPA = VMSC CgPA = HLR 13. SRI_ACK(MSRN) CdPA = VMSC CgPA = HLR
OTHER NETWORK
VMSC
Call-Related Service: Pre-paid subs calls regular foreign subscriber
SMS MT Relay
Subs sends SMS, B number is regular-own or ported-in
5.SRI_FSM (MSISDN) HLR 7.SRI_FSM_ACK (IMSI, VMSC)
CdPA=MSISDN CgPA=SMSC
SMSC
6.SRI_FSM (MSISDN)
CdPA=HLR CgPA=SMSC
4. MO_FSM (MSISDN)
CdPA=SMSC CgPA=VMSC
3.MO_FSM (MSISDN)
CdPA=SMSC CgPA=VMSC
STP 8. MT_FSM 1.IDPSMS (MSISDN) VMSC 2.IDPSMS_ACK
VMSC
SCP
SMS MT Relay
Subs sends SMS, B number is ported-out or cross-ported
Other Network
SMSC 4. MO_FSM (RN+MSISDN) HLR
CdPA=SMSC CgPA=VMSC
5.SRI_FSM (MSISDN)
CdPA=MSISDN CgPA=SMSC
GMSC
HLR
8. MT_FSM 7.SRI_FSM_ACK (IMSI, VMSC) 3.MO_FSM (MSISDN)
CdPA=SMSC CgPA=VMSC
STP 1.IDPSMS (RN+MSISDN) 6.SRI_FSM (MSISDN)
Other Network
GMSC
2.IDPSMS_ACK VMSC
SCP
CdPA=RN+MSISDN CgPA=SMSC
HLR
SMS MT Relay
Subs sends SMS, B number is Regular-foreign subscriber
SMSC 4. MO_FSM (MSISDN) HLR
CdPA=SMSC CgPA=VMSC
5.SRI_FSM (MSISDN)
CdPA=MSISDN CgPA=SMSC
8. MT_FSM 7.SRI_FSM_ACK (IMSI, VMSC) 3.MO_FSM (MSISDN) STP
CdPA=SMSC CgPA=VMSC 1.IDPSMS (MSISDN)
6.SRI_FSM (MSISDN)
Other Network
GMSC
2.IDPSMS_ACK
VMSC
CdPA= MSISDN
SCP
CgPA=SMSC
HLR
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
Subs sends MMS, B number is regular-own or ported-in
MMS MT
Subs sends MMS, B number is ported-out or cross-ported
MMS MT
Subs sends MMS, B number is Regular foreign subscriber
Impact on Network due to MNP
Mandatory STP inclusion. MNP related features and HW in all core nodes, IN, SMSC etc.
MSC has to populate LRN information in CDRs. Entire B number table would be modified. IN has to understand the modified IDP msg coming from STP where called party would be LRN+B MSISDN. IN has to charge based on LRN along with called party MSISDN. SMSC CDRs to be referred for SMS. FDA (First Delivery Attempt) will not be used as MSC CDRs will not be referred for SMS.
Additional 25% signaling load will increase from the day1 of MNP launch. Migration of all core elements on STP to be MNP ready with in given dead line would be the critical task. Changes in tariffs (RN based tariffs instead if MSISDN) Ericsson IN nodes are working on CS1+ (Ericsson proprietary) protocol which is not supported by many STPs for IDP message modification for MNP lookup. Software development required by IN Vendors, to send CONNECT message in response to IDP query from STP. Connect message saves additional signaling whereas Continue message does not. Monitoring and interception related issues.
Thanks & Happy learning
