Mobile Number Portability in India
Mobile Number Portability in India
AN OVERVIEW
Prepared by
Learntelecom.com
Contents
1. 2. 3. 4. INTRODUCTION PROJECT BACKGROUND MNP PRINCIPLE IN INDIA HIGH LEVEL NETWORK ARCHITECTURE FOR MNP SOLUTION
4.1. Central Side- MNPO (Mobile Number Portability Operator) 4.2. Operator Side (Service Providers)
5. 6. 7. 8. 9.
MNP TERMINOLOGY PORTING PROCESS FLOW POST MNP VOICE CALL FLOW POST MNP SMS FLOW PROCEDURE TO SWITCH SERVICE PROVIDER IN INDIA
10. Reference
www.le arntelecom.com
List of Figures Figure 1 HIGH LEVEL MNP ARCHITECTURE Figure 2 END TO END PORTING PROCESS Figure 3 End to End Call Flow for ported Number Figure 4 POST MNP SMS FLOW FOR PORTED NUMBER
www.le arntelecom.com
1. INTRODUCTIO N
The Jan much awaited in MNP (Mobile Number Portability) finally 2011 launched on 20th India, empowering mobile Number
submitted to DoT for initiating the process for MNPO (Mobile Number Portability Operator). Subsequently, the DoT issued guidelines for MNP service license on 1st August envisaged 2008. The DoT guidelines
geographical division of the country into the two Number Portability Zones (Zone 1 North West & Zone 2 South East), each consisting of 11 licensed service area. DoT issued the tender Document on 25th November 2008 for MNPO. in Based the on the selection for MNP parameters set service each license, zone was guidelines M/s
phone consumers to change service provider conveniently.Mobile Portability (MNP) allows the mobile subscribers to retain the existing mobile phone number when the subscriber switches from one access service provider (Operator) anotherirrespective of to mobile
technology or from one technology to another of the same or any other access service provider, in a licensed service area.
Technologies(I) Pvt. Ltd was granted license for operating in Zone-1 (North-West India) and M/s MNP Interconnection Telecom Solutions (I) Pvt. Ltd (Telcordia) was granted license for MNP Service Zone-2 (North-East India). Further, on 6th May 2009, DoT issued detailed instructions to all Access Provider/NLD/ILD licensees regarding provisioning of MNP. On 25th Nov 2010, MNP has been implemented in Haryana as a pilot LSA to observe implication of MNP on voice as well as non voice calls. Finally, 20th January 2011, MNP implemented across the India. has been
2. PROJECT BACKGROUND
The projected was started long back in India. The first mile stone came when The Telecom Regulatory Authority of India (TRAI) issued draft Regulations to facilitate Number Portability implementation in India Mobile (MNP) and
submitted recommendations to DoT on 8th March 2006. The draft regulations lay down the business process for implementing mobile number portability. The Department of Telecom (DoT) had accepted TRAIs recommendations on 10th December 2007. DoT had also accepted the suggestion of TRAI that a Steering under the aegis of TRAI, to deliberate upon various issues involved in the Committee be formed
INDIA
3. MNP PRINCIPLE IN
the TRAI constituted a Steering Committee consisting Applicable only for Mobile Numbers of representatives from TEC, Service Providers and their Associations. Based on the report of the Steering Committee and deccision of the Authority, a draft Request for Proposal (RFP) was prepared and Number Portability is Mobile only applicable to
www.le arntelecom.com
Applicable only in intra licensed area A mobile subscriber can switch from one service provide to another within the same license area. Portability is applicable only in intra-circle; it is not applicable in inter-circle. Applicable Technology Portability is irrespective of
ported in and ported out numbers. Originating network originating performs calls MNPDB and query for all to directly routes
ILDOs/IGPs are responsible for MNP dip for the International calls and SMS terminating to Indian subscribers. to ILDOs/IGPs be an the Indian supposed originating
Possible irrespective of
Mobile
Technology used by Service Provider. A mobile subscriber can change its operator from CDMA to GSM/UMTS and vice-versa. LRN routing DoT has based
network for
terminating international calls/SMS. ILDOs/IGPs perform MNP dip and route calls/SMS directly to the subscription network. MNP Zones (Circle) and LSA
number called LRN (Location Routing Number) to all Mobile Operators for each circle to identify individual network. Post MNP calls (Voice/Non Voice) will be routed on the basis of LRN. Ported numbers are prefixed with a LRN
1 2 3 4 5 6 7 8 9 10 S. No. MNP ZONES ZONE 1 Licensed Service Area Gujarat Haryana Himachal Pradesh Jammu & Kashmir Maharashtra Punjab Rajasthan Uttar Pradesh (E) Uttar Pradesh (W) Chennai Delhi Mumbai TABLE 1 MNP ZONES AND LSA West Bengal Kolkata ZONE 2 Licensed
Service Area Andhra Pradesh Assam Bihar Karnataka Kerala Madhya Pradesh North East Orissa Tamil Nadu including
identifying the new service provider for the number. So when MNP database receives a query for a given MSISDN, the data base will return the MSISDN prefixed with the LRN of the MNO to database which always it (MSISDN) belongs. MNP responds to a query with
LRN+B Number. In case of Ported Number LRN belongs to new service provider and in case of Non Ported Number LRN belongs to same service provider. MNPDB Method query & Routing
11
All call query and direct routing method has been chosen for the MNP in India. MNPDB contains all
Fig 1 show high level network architecture and network components for MNP solution. On high level, complete network can be visualized into two parts:
www.learntelecom.com
Central Side MNPO (Centralized Clearing House) Operator Side Service Providers
(MOBILE
NUMBER
The central side is a MNPO, supposed to provide MNP Service in a particular zone. It is also called MNP Clearing House (MCH). MCH shall receive mobile number portability requests from the recipient operator; forward it to the donor operator for verification. On getting clearance from donor operator MNP service provider shall control and coordinate the mobile number portability process. At a predetermined date and time the MNP service provider will instruct the donor operator to disconnect the mobile number of the subscriber and upon receiving confirmation of such effect shall instruct the recipient operator to activate the mobile number of the subscriber. Once the mobile number is activated at the recipient operators end, the MCH will send the details of the porting to the centralised Number Portability Database (NPDB) which in turn will update its own database by an appropriate routing number called Location Routing Number (LRN), a unique routing number assigned to each operator in a service area by the DoT. This updation will be communicated by the NPDB to all the service providers for updating their respective local Number Portability database. MNP Service provider has to deploy its system (network) in redundant way as shown in figure in two different geographical areas, one as a production site and another as a disaster recovery site to avoid interruption in service due to failure of one site. Both side must be in sync and work in active redundant mod e
www.le arntelecom.com
SIDE
(SERVICE
Operator side consists service providers like MNO, ILDO, IGP, Fixed Line service Provider, content provider etc. Service providers should connect their Local Number Portability database to the both sites of MNPO. Whenever any call is made to the ported mobile number, the originating network shall first query the number portability database to obtain LRN and then the call is routed directly to the destination mobile network. As shown in figure, depending upon requirement and network topology, service provider can choose any of below mention option to connect MNP service provider. Option 1: Service provider can directly connect its gateway to Central MNPDB of MNP service provider and perform MNP query to Central MNPDB to get appropriate LRN to route originating calls to subscription network. In this option service provider not required to deploy its Local MNPDB separately. Option 2: Service Provider can deploy its separate Local MNPDB and connect it to Central MNPDB through its number portability gateway (NPG). Local MNPDB is synchronized with Central MNPDB of the MNP service provider. In this option service provider performs MNP query to its Local MNPDB to get appropriate
www.le arntelecom.com
LRN to route originating calls to subscription network. Option 3: This option is similar to the Option 2 but in this, Local MNPDB is the Part of service providers STP (Signaling Transfer Point), whereas in option 2 Local MNPDB is independent node. In this option, service provider performs MNP query to its STP (which consist Local MNPDB) to get appropriate LRN to route originating calls to subscription network.
5. MNP TERMINOLOGY
CCH: Centralized Clearing House. Negotiating between Donor & Recipient Operator during porting process and responsible for Central NP Database Administration. CNPDB: Centralized Number Portability Database. Repository for Ported Subscribers information. Donor Network: The initial network where the number was located before being ported. LRN: Location Routing Number. A unique routing number assigned to each operator in a service area by the DoT. LNPDB: Local Number Portability Database, deployed by service provider for the repository of Ported Subscribers information. MNPDB: Mobile Number Portability Database. NPG: Number Portability gateway. The network component which connects service providers LNPDB to the MNP Service Providers gateway. Originating Network: The Network where the calling party is currently connected. Recipient Network: The network where a number is located after being ported. Routing Prefix: Routable number to identify the Service provider, Technology and the Service area for the called party.
www.le arntelecom.com
www.le arntelecom.com
5. The GMSCB requests routing information by submitting a MAP SRI to the HLRB, including the MSISDN in the request.
The HLRB requests an MSRN from the MSC/VLRB where the mobile subscriber currently is registered.
7 8 9
The MSC/VLRB returns an MSRN back to the HLRB. The HLRB responds to the GMSCB by sending an SRI ack with an MSRN. GMSCB uses the MSRN to route the call to VMSCB.
Once IAM terminates to appropriate MSC/VLR, subsequent messages like ACM, ANM, REL and RLC (other ISUP messages for Call completion) will flows between Originating and Subscription network as it is.
www.le arntelecom.com
1.
2. The SMS-GMSC generates a routing enquiry for SM delivery. The MAP SRI_for_SM message is routed to the networks MNP-SRF. 3. When MNP-SRFA receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN in the CdPA and identifies the MSISDN as being ported using information which may be retrieved from an LNPDB. As the message is non-call related, the MNP- SRF function then populates the CdPA with a location routing number and MSISDN. The format of CdPA = CC+LRN+NDC+SN. After modifying the CdPA, the message is routed to MNP-SRFB in the subscription network. 4. When MNP-SRFB receives the message, MNP-SRF operation is triggered. The MNP-SRF functionality analyses the MSISDN (CC+LRN+NDC+SN) in the CdPA and identifies the MSISDN as being ported into the network using information which may be retrieved from a LNPDB. The MNP- SRF function then populates the CdPA with an HLRB address. After modifying the CdPA, the message is routed to HLRB. 5. HLRB responds to the routing enquiry by sending back a SRI_for_SM ack with the address of the VMSC. 6. The SMS-GMSC can now deliver the message to the VMSCB using a Forward_SMS message.
www.le arntelecom.com
7.
10 .
REFERENCE
http://www.trai.go v.in http://www.dot.go v.in
http://www.coai.in
www.le arntelecom.com