1. Overview of Mobile Number Portability Presented by P. K
Overview of Mobile Number Portability Presented by P.K.Kamalasanan SDE NSS Ernakulam

2. Introduction

3. MNP Definition
"Mobile Number Portability" means the facility which allows a subscriber of a mobile telephone service to retain his mobile telephone number when he moves –
from one mobile telephone service provider to another, irrespective of the mobile technology or
from one mobile technology to another of the same mobile telephone service provider, within such limits as may be permitted by the licensor

4. MNP Definition While retaining his mobile number
Presently, Number portability is permitted only within LSA and not across LSAs, in India.
That means subscriber can change
Operator say Airtel to BSNL, or
Technology – GSM to CDMA or vice versa, or
both say Reliance CDMA to BSNL GSM
While retaining his mobile number

5. Call Routing post MNP scenario
In the post MNP scenario, level based routing is not possible, because service provider cannot be identified levels
A customer with 9447XXXXXX, may or may not belong to BSNL.
The switching philosophy is based on Location Routing Number (LRN)
Unique LRN is defined in the trunk groups of the operators
If the B belong ,say to Idea, the call is routed to the trunk group of Idea, using LRN

6. TERMINOLOGIES USED

7. TERMINOLOGY "Donor Operator" “-
means a operator from whose network the subscriber is porting out.
“Recipient Operator" –
means an Operator who will be providing mobile service to the subscriber after porting

8. TERMINOLOGY from BSNL point of view
Not Ported – Mobile Numbers belonging to BSNL.
( say subscribers of 94 Series belonging to BSNL )
Port IN or Imported – Number ported into BSNL
from another network. (say a 98 series BSNL subs.)

9. TERMINOLOGY from BSNL point of view
Ported Out – Number Ported out to another N/w
from BSNL.
( say a 94 series subscriber of Airtel )
Foreign Number – Other Operator subscriber not known to be ported.
( say subscriber of Idea who may or may not have
ported to say Airtel)

10. TERMINOLOGY MCHA :- Mobile Clearing House Administrator
NPDB :- national Number Portability database
LPDB :- Local portability database
LRN :-Location routing number
B&CCS :- Billing and Customer Care System

11. TERMINOLOGY
"Location Routing Number” means the code assigned to every Access Provider for the purpose of implementing Mobile Number Portability
These are 4 digit codes and have been assigned by DOT.
They have been assigned LSA wise, Operator wise and technology wise
BSNL has been allocated 42 codes in total – 21 for GSM and 21 for CDMA.

12. LRNs allotted to Service providers in Kerala
Technology
LRN
BSNL
GSM
2491
CDMA
2702
Bharti
3003
Datacom
3036
Dishnet
3053
Idea
3072
Loop
3094
RCL
3118
3136
Shyam
3169
Swam
3273
TTSL
3446
Unitech
3574
Vodafone
3579

13. Functional Elements in MNP

14. MNP Elements
Several new elements are introduced in the network for the implementation of MNP
MCHA
LSOA
LSMS
NPDB

15. Functions of Elements- MCHA
MNP Clearing House Administrator (MCHA) is managed by a third-party company with no interest in the telephone business.
DOT Floated Tender on and awarded the license to
M/s Syniverse Technologies (India) Delhi for Zone I
M/s MNP Interconnection Telecom Solution (India) Ltd @Bangalore for Zone II
The MCHA network includes a service order administration (SOA) system as well as a service management system (SMS).
It has a database NPDB

16. Functions of Elements- SOA
All order information regarding a number being ported is sent to the SOA system. The SOA is used to process a subscriber’s order
the subscriber data includes the LRN of the serving (donor) carrier,
The SOA communicates this information to the SOA in the MCHA, which in turn passes the information to the SOA in the donor network.
It is important to understand that the only purpose of the SOA is to track the activities of an order to provide the specifics about when a number is to be ported and who the donor network is.

17. FUNCTIONAL ELEMENTS- LSMS
Each carrier has a Local Service Management System (LSMS), which serves as the interface between the carrier networks and the NPAC.
The LSMS is responsible for collecting porting data and downloading it to the LNP databases.
The LSMS is a computer system with database storage and must be able to verify the data within the database with the data stored at the NPAC. This is accomplished through periodic audits between the LSMS and the NPAC.
Likewise, the LSMS also audits the LNP databases within its own network. It is crucial that the data is accurate

18. FUNCTIONAL ELEMENTS- LPDB
The actual database used to maintain Porting data can be one of two types:
an SCP or
an integrated Stand alone Signal transfer Point (SSTP).
The integrated SSTP solution is more favorable because of the throughput that modern SSTPs can provide in comparison to SCPs

19. SS7 Network Elements and MNP Network Elements
The database function itself can reside in SSTP. The only connection to the SS7 network provided is the database itself.
The LSMS does not connect to the SS7 network, and neither does the MCHA.
All communications between these entities are through communications link using Ethernet and TCP/IP protocols. We use MPLS cloud
The SS7 network uses the information provided by the LNP database to route calls through the network.

20. SS7 Network Elements and MNP Network Elements
MCHA
NPDB
LSMS
SOA
SOA SP SP
LSMS
SSTP
LPDB
MNP N/W
SS7 N/W

21. PORTING PROCESS

22. Porting Process Eligibility Criteria for making a port request.–
Every subscriber shall be eligible to make a request for porting his mobile number. provided that
a period of 90 days has expired from the date of activation of his new mobile connection / 90 days from last porting
there are no outstanding payments due to the Donor Operator by way of pending bills issued as per the normal billing cycle but before the date of application for porting

23. Porting Process
there is no pending request for change of ownership of the mobile number
porting of the concerned mobile number has not been prohibited by a Court of Law.
Note :- In case of Pre – paid :- the balance amount of talk time, if any, at the time of porting shall lapse

24. Porting Process
Subscriber desirous of porting his mobile number shall make a request in writing to the concerned Recipient Operator in specified format
The subscriber shall pay the porting charge, if any
The Recipient Operator, shall treat the customer in the same way as that for a new subscriber
The Recipient Operator shall thereupon ask the subscriber to send a SMS to Donor Operator using short code 1900 from the mobile number which is sought to be ported.

25. Porting Process
Upon receipt of the SMS, the Donor operator shall forthwith send back a reply SMS containing a unique porting code through an automated system.
Subscriber shall intimate the same to the Recipient Operator
Recipient Operator shall, within a period of twenty four hours, forward the mobile number, the corresponding unique porting code and the date on which porting request is made by the subscriber, to the concerned MCHA.

26. Porting Process
A subscriber may, withdraw porting request by informing the Recipient Operator in writing within twenty four hours of making a request for porting, but he shall not be entitled to any refund of the porting charge paid by him
The Recipient Operator shall be liable to pay Per Port Transaction charge in respect of each porting request forwarded by it to MCHA
SIM card is required to be changed

27. Porting Process
On receipt of the porting request MCHA shall verify whether a period of ninety days has elapsed from the date of its last porting and if any porting request in respect of the same mobile number is already pending
In case the porting request is found eligible MCHA shall forthwith forward the details of such request to the Donor Operator for seeking his clearance for such porting

28. Porting Process
Donor Operator will verify if the porting is permissible as per the rules defined in the TRAI regulation like UPC is same, Outstanding dues are paid etc.
Donor Operator will verify the above and communicate to MCHA accordingly within 24 Hrs (excl. Sundays and public holidays)

29. Porting Process
MCHA will fix the date and time of porting such that the porting happens within 36 hrs of the clearance from the Donor Operator or on non receipt of any communication from the Donor Opr.
MCHA will intimate porting date and time to both the operators.
In J&K, Assam and North East the date and time for porting shall be within ten days from the date of receipt of the clearance from the Donor Operator.

30. Porting Process
Recipient Operator shall communicate the same, to the concerned subscriber via SMS.
The porting will be break before make.
Donor Opr. will disconnect the subs at the time specified by MCHA and intimate MCHA. (1 Hr. window)
MCHA will then ask Recipient Opr. to connect.
Recipient Opr. will connect and intimate MCHA (1 Hr. window)

31. Porting Process
MCHA will broadcast MSISDN and LRN to all Oprs. for call routing. (MSISDN-LRN update to NPDB & to LPDB of all Oprs)
Donor Operator will issue Bill to the ported out Post paid Subscriber for his unbilled usage till the time of porting. Subs. Will have to pay within stipulated period.
In case not paid, Donor Opr. Will take necessary steps for recovery. Further, Donor Opr. Will request MCHA to get the subs disconnected. MCHA will ask the Recipient Opr who is bound to do so.

32. Porting Process In case, subscriber surrenders his connection
or the number gets disconnected, the Mobile
number will be returned by the Recipient Opr.
to the Operator owning the number series.

33. Number Portability Business Process
4. Forward Request to MCHA
2. Request to port
5. Approve or Reject, if approved forward request to Donor Operator
1. Request to switch to Telco B (Porting Number)
Telco A
( Donor)
Telco B (Recipient)
3. Verify the request
Voice
7. MCHA fix the porting window and convey it to Donor and Recipient Operator
Customer
Mobile
Clearing
House(MCHA)
8. Number is disconnected from Donor operator and provisioned in Recipient Operators Network
6. Approve or Reject, if approved forward approval to MCHA
Telco C
Telco D
9. LRN of Recipient Operator is defined against the Mobile Number
10. New LRN is updated by all Operators

34. IMPLEMENTATION

35. Implementataion DOT has issued licences to two sevice providers
M/s Syniverse Technologies (India) Ltd @ Delhi for Zone I
M/s MNP Interconnection Telecom Solution (India) for Zone II

36. MNP Zones & MCHAs Zone 1 - STIPL Zone – II - MITS Delhi Kolkata Mumbai
T.N including Chennai
Maharashtra
Andhra Pradesh
Gujarat
Karnataka
Haryana
Kerala
Punjab
Madhya Pradesh
Rajasthan
West Bengal
Uttar Pradesh (E)
Assam
Uttar Pradesh(W)
Bihar
Himachal Pradesh
North East
Jammu & Kashmir
Orissa

37. Implementation
All operators are hooked up to the MCHA through their own MNP gateways
BSNL is having its MNP Chandigarh and Kolkatta

38. Technical Implementation
DONOR G A T E W Y G A T E W Y R E C I P N T
MCHA

39. Technical Implementation
SSTP M C H A DB L S M
SSTP
LSMS : Localized Service Management System
Local Service Management System The LSP owned network database which holds downloaded ported number information.

40. MNP Functional DIAGRAM
MCHA
Gateway
Opr. B
Gateway
Opr. A
NPDB
MNP Licensee
LPDB Opr A
LPDB Opr B
B&CCS
Opr A
B&CCS
Opr B
N/ W Elements
Opr A.

41. MNP BLOCK DIAGRAM B&CCS PSTN M C H MNP G A - I A PLMN GSM T M P E L W
SDCC
TANDEM
PSTN
TAX M C H
A - I
MNP G A T E W Y
PLMN
GSM M P L S
SSTP
MSC
SMSC
HLR M C H
A - II
SSTP
HLR
MSC
B&CCS
SMSC
BSNL - CDMA

42. Network Structure for MNP Implementation in South Zone
Page 42

43. Call Routing All call query to be done for routing mobile
terminated calls originated from any network.
Every Access Provider on whose network a call
originates shall be responsible for the correct
routing of such call in accordance with the
Location Routing Number (LRN).

44. Call Set Up Pre MNP and Post MNP Scenario

45. for all ported/non-ported scenarios
VOICE CALL
for all ported/non-ported scenarios
Page 45

46. Call flow prior MNP for own subscriber
SRF-NPDB
HLR
VMSC
1. Originates a call
2. SRI (MSISDN)
CdPA = HLR
CgPA =VMSC
3. SRI_ACK
CdPA = VMSC
4. IAM (MSRN)
STP
Page 46

47. Call flow post MNP for own subscriber
SRF-NPDB
VMSC
1. Originates a call
2. SRI
CdPA = MSISDN
6. SRI_ACK(MSRN)
CdPA = VMSC
7. IAM (MSRN)
3. SRI
4. SRI ACK
Routing digits=RN+B
STP
5. SRI REQ
CdPA = B
HLR
Page 47

48. Page 48

49. Page 49

50. SMSC
Page 50
Tekelec Confidential

51. Page 51

52. Page 52

53. Page 53

54. Page 54

55. Page 55

56. Page 56

57. Page 57

58. for all ported/non-ported scenarios
SMS
for all ported/non-ported scenarios
Page 58

59. Page 59

60. Page 60

61. Page 61

62. Page 62

63. Page 63

64. THANK YOU
Message Cal Flow