Mnp Main Report

39
A REPORT on SEMINAR on MOBILE NUMBER PORTABILITY Submitted by HEMANT SINGH RATHORE in the partial fulfilment for the award of the degree of BACHELOR OF TECHNOLOGY in COMPUTER SCIENCE & ENGINEERING DEPARTMENT 1

Transcript of Mnp Main Report

Page 1: Mnp Main Report

A REPORT on SEMINAR on

MOBILE NUMBER PORTABILITY

Submitted by

HEMANT SINGH RATHORE in the partial fulfilment for the award of the degree

ofBACHELOR OF TECHNOLOGY

in

COMPUTER SCIENCE & ENGINEERING DEPARTMENT

SWAMI KESHVANAND INSTITUTE OF TECHNOLOGY MANAGEMENT & GRAMOTHAN, JAIPUR

RAJASTHAN TECHNICAL UNIVERSITY, KOTA

1

Page 2: Mnp Main Report

Candidate’s Declaration

I hereby declare that the work, which is being presented in

the seminar, entitled “MOBILE NUMBER PORTABILITY” in

partial fulfilment for the award of Degree of “Bachelor of

Technology” in Department of Computer Science and Engineering

in Swami Keshvanand Institute of Technology Management &

Gramothan is a record of my own investigations which is carried

under the Guidance of Mrs. Neha Agarwal (Sr. lecturer), Mrs.

Rimjhim Jain (Lecturer) and Ms. Neha Kapur (Sr. lecturer)

Department of Computer Science and Engineering.

Hemant Singh Rathore

Roll No- 08ESKCS047

2

Page 3: Mnp Main Report

ACKNOWLEDGEMENT

It would be insufficient just to say a “word of thanks” for all those people who have been so instrumental in the success of this seminar. However, as a small token of my appreciation I have named here of all those wonderful people, without whom all this would not have been possible.I am deeply indebted to Prof.(Dr.) C.M. Choudhary (HOD) and mentors Mrs. Neha agarwal (Sr. Lecturer), Mrs. Rimjhim Jain (Lecturer) and Ms. Neha Kapur (Sr. Lecturer) for allowing me to gain the benefits of this seminar.

Hemant Singh Rathore BRANCH – C.S. VIII SEMESTER

INDEX3

Page 4: Mnp Main Report

CHAPTER

SERIAL NUMBER

SUB SERIAL NUMBERS

TABLE OF CONTENTS PAGE

NOS.

CHAPTER-1

MOBILE NUMBER PORTABILITY(MNP) 6

1. INTRODUCTION 6

2. BACKGROUND 6

3. TYPES OF NUMBER PORTABILITY 8

3.1 OPERATOR PORTABILITY 8

3.2 LOCATION PORTABILITY 9

3.3 SERVICE PORTABILITY 9

4.WHAT NUMBER PORTABILITY WOULD MEAN TO SUBSCRIBERS & SERVICE PROVIDERS?

9

5. THE CHALLENGES 10

6. IMPLEMENTING NUMBER PORTABILITY

11

7. ELEMENTS OF MNP 12

8. DATABASE MANAGEMENT FOR MNP 13

8.1 SYNCHRONISATION OF DATABSE UPDATION OF DIFFERENT OPERATORS

13

9. NETWORK ELEMENTS 13

10. WORKING OF MNP 17

10.1 PORTING PROCESS 18

11. NUMBER POOLING 19

CHAPTER-2

12. MOBILE NUMBER PORTABILITY IN INDIA

20

13. A FLOW CHART DEPICTION OF STEPS INVOLVED FOR PORTING A NUMBER.

23

14. WHAT ACCESS PROVIDERS THINK OF 24

4

Page 5: Mnp Main Report

MNP

15. WHO IS LIKELY TO SWITCH 24

16. HOW CALLS WILL BE HANDLED AFTER MNP

25

17. DIFFERENT COSTS AND CHARGES INVOLVED

26

18. ISSUES NOT COVERED BY TRAI 27

19. WILL MNP BE A SUCCESS 27.

20. MNP PROS. AND CONS. 29

20.1 MNP PROS. 29

20.2 MNP CONS. 29

21. MOBILE OPERATORS IN INDIA 31

22. REFERNCES 32

CHAPTER-1

MNP

1. Introduction

5

Page 6: Mnp Main Report

In the context of traditional circuit-switched telecommunications networks, number portability is the ability of end-users to retain their telephone numbers when changing service providers, service types or locations. It is believed that when fully and nationally implemented by both wireline and wireless service providers, number portability will remove one of the most significant switching costs for consumers and will encourage competition in the telecommunications industry. With the Telecommunications Act of 1996, Congress addressed the issue of number portability by formally defining it, setting deadlines for implementation, and requiring all carriers to deploy it. To ensure standardization across platforms for all participants, the Federal Communication Commission (FCC) instructed the North American Numbering Council (NANC) to determine which number portability method to employ. The location routing number (LRN) method proved to be the most efficient among alternatives and is the method now widely implemented in wireline environment. The sections below discuss in detail number portability and LRN architectures.

2. Background

The Telecommunications Act of 1996 (TA 96) tore down most of the significant barriers to unfettered competition in telecommunications. However, the inability of end users to retain their telephone numbers when changing service providers or types could potentially dissuade consumers from making such a change, threatening to hinder industry competition and growth. Congress’ addition of Section 251 (b)(2) to TA 96 addressed this obstacle by defining number portability, requiring that all carriers deploy it, and setting deadlines for implementation. FCC Docket No. 95-116 (In the Matter of Telephone Number Portability) and subsequent FCC orders and reconsiderations reinforced Congress’ mandate and set the machinery in motion to implement number portability. The actions of both Congress and the FCC enabled consumers and businesses to choose new providers, services, and locales while retaining their phone numbers, thereby fostering competition in the telecommunications industry. To ensure standardization across platforms for all participants, the FCC instructed the North American Numbering Council (NANC) to determine which number portability method to employ. Several options were investigated. The location routing number (LRN) method was chosen because it appeared to be the most efficient and is now successfully implemented in the wireline environment. The NANC then created the Local Number Portability Working Group (LNPA-WG) and empowered it to select the appropriate technology, create standards, determine operational processes, and develop and implement a deployment strategy. To fulfil its responsibilities, the LNPA-WG was granted the authority to convene appropriate subcommittees as needed. Subcommittees created include the National Number Pooling and Slow Horse groups, as well as the Wireless Number Portability subcommittee, which defines integration issues between the wireless and the wireline industries. NeuStar was named the Number Portability Administrator and operates the Number Portability Administration Centre (NPAC).

Regulators have mandated that number portability be implemented before the regional Bell operating companies (RBOCs) are allowed to offer long distance service within their regions. Conversely, interexchange carriers (IXCs) and competitive local exchange carriers (CLECs) require local number portability (LNP), also called service provider portability, to gain a competitive foothold in the local loop. This ability to enter local markets on a competitive

6

Page 7: Mnp Main Report

basis is considered key to fair and open competition and is directly addressed in FCC Docket No. 95-116.

CLECs are taking advantage of opportunities created by LNP to compete with incumbent local exchange carriers (ILECs). In 1999, the local service market—the primary market identified by CLECs—represented over $109 billion in total revenue, and CLECs garnered 5.8 percent of that revenue, according to the FCC. This penetration is largely predicated on the ability of current ILEC customers to change service providers without changing their phone numbers. Some CLECs have reported that over 90 percent of their subscriber growth was directly enabled by number portability. Wireline LNP has been implemented within the top 100 MSAs in the United States, as mandated, and is gradually being adopted outside of these areas.

The FCC order also set an aggressive implementation schedule for the wireless industry. However, the Cellular Telecommunications Industry Association (CTIA), acting on behalf of the wireless community, asked for and received deadline extensions. The FCC’s current mandate requires that wireless carriers, including cellular and personal communications service (PCS) carriers, implement service providerPortability by November 24, 2003.

3. Types of Number Portability

The government has defined and mandated three basic types of number portability:

service provider portability (commonly referred to as Local Number Portability), location portability, and service portability. The three types may be combined to form variations on number portability services.

3.1 Operator (Service Provider) Portability

Service provider portability or Local Number Portability (the term Local Number Portability will continued to be used in referencing service provider portability), as defined in the Telecommunications Act of 1996, is the ability of end users to retain existing directory numbers at the same location as they change from one service provider to another. Historically, all directory numbers in one NPA-NXX were assigned to a single telephone switch. The incumbent had a significant advantage in retaining customers by controlling or, in effect, owning the customer’s telephone number. A customer who wanted to change local service providers faced the potential costs and inconveniences of changing to a new phone number, including distributing it to family, friends, and business contacts. To facilitate competition at the local exchange, the FCC mandated that phone numbers be portable among local exchange competitors (ILECs, CLECs, cellular providers, and so on). With the introduction of local number portability, individual directory numbers in one NPA-NXX may be moved to a different telephone switch. Therefore, the first six digits of a directory number (NPA-NXX) no longer uniquely identify the switch that serves that customer. To identify the correct switch, the concept of a location routing number (LRN) was introduced by industry experts and approved by the FCC. Each switch that hosts portable numbers will be assigned a

7

Page 8: Mnp Main Report

10-digit LRN that will be used in routing a call to that switch. The order calls for porting only within a rate centre. A rate centre, or the portability domain, is an area (usually under the jurisdiction of the state Public Utilities Commission) in which directory numbers can be ported. All LNP-capable network elements, including service switching points (SSPs), signal transfer points (STPs), and signal control points (SCPs), must maintain a list of NPA-NXXs that are considered portable.

3.2 Location Portability

Location portability, as defined in the FCC’s First Report and Order, Docket No.N95-116, released July 2, 1996, is the ability of users of telecommunications services to retain existing directory numbers without impairment of quality, reliability, or convenience when moving from one physical location to another. In this case, a given telephone number could Be associated with any network termination device, independent of location. Location portability would allow customers to take their directory number when they move to a geographic location outside of the original rate centre. In the Second Memorandum Opinion and Order on Reconsideration regarding FCC Docket 95-116, the FCC concluded that nothing in the Act would preclude it from mandating location portability in the future; however, no requirements have yet been designated or mandated.

3.3 Service Portability

Service portability, as defined in the FCC’s First Report and Order, Docket No. 95-116, is the ability of users of telecommunications services to retain existing directory numbers without impairment of quality, reliability, or convenience when switching from one service to another service provided by the same carrier. The FCC has not addressed service portability at this time, and requirements for service portability are still undefined.

4. What number portability would mean to subscribers & service providers?

When fully implemented nationwide by both wireline and wireless providers, portability will remove one of the most significant deterrents to changing service, providing unprecedented convenience for consumers and encouraging unrestrained competition in the telecommunications industry. In short, this is the best method to increase the efficiency of the service provider by increasing the competition, thereby ensuring better services in all respects. From the subscribers’ perspective, this is a deceptively simple and very welcome change, because they can change wireless service providers without worrying about notifying friends, family and business contacts that their wireless number is changing. In addition, being able to ‘port’ a number from one provider to another eliminates the Hassle and expenses of changing business cards, stationery, invoices and other materials for businesses.

8

Page 9: Mnp Main Report

From the wireless carrier’s perspective the change is anything, but simple. Virtually all of wireless carriers’ systems are affected. Especially any system that relies on mobile identity numbers (MINs) or mobile directory numbers (MDNs) will be affected. Examples of critical systems and processes that would be affected are: billing, customer service, order activation, call delivery, roamer registration and support, short messages service centre, directory assistance, caller ID, calling name presentation, switches, maintenance and CSC systems, home location registers (HLRs), and visiting location registers (VLRs).

5. The Challenges

Huge Costs: Telecom services sector in India requires an investment of Rs 50,000 crore over the next three years to meet the growing demand. A substantial share would be required for the mobile services market. The GSM service providers are yet to justify the huge investments made in this field and are not keen on MNP

.

Customer Retention/Increased Competition- The service providers are also on guard against the risk of losing customers and revenues in the post-MNP era.

Infrastructure Upgrade: To support MNP, a company has to upgrade both its hardware and software capabilities, which will amount to some cost.

Cost Recovery and Bill Reconciliation/Query Processing: When a customer plans to shift, the old service provider (OSP) has to perform a query to identify if there are any billing amounts pending, which they need to recover before the subscriber moves to the new service provider (NSP).

Several issues need to be cleared by the regulator before implementing the MNP. Primary among these are the limited mobility versus mobile services, carrier access code (CAS), finalisation of the Interconnect Usage Charges (IUC), etc.

The regulator must ensure that there is absolute transparency in the charges for the person calling a ported number and another receiving the call on a ported number. Only such clarity will ensure widespread usage among the Indian mobile users and make MNP a widely used feature.

6. Implementing Number Portability

Let us look at some of the basic terminologies used in any porting process:

Donor network: The initial network where the number was located before ever being ported.

9

Page 10: Mnp Main Report

Originating network: The network where the calling party is connected.

Recipient network: The network where a number is located after being ported.

Database: The store of ported numbers with their relevant routing numbers.

Routing number: A specific number that is derived and used by the network to route the call towards a ported number.

New service provider (NSP): It is the recipient carrier i.e., the new service provider to which the subscriber wishes to subscribe to.

Old service provider (OSP): The donor carrier is the old service provider, which the subscriber wishes to leave.

Number Portability Administration Centre (NPAC): The authority responsible for maintaining NP solutions in different regions. Both the OSP and NSP carriers will have access to their own wireless network, order entry and point of sale terminals. Further, the two competing carriers’ WNP architectures will be connected at two points:

Intercarrier communications process (ICP) Number portability administration centre (NPAC).

In number portability the “donor network” provides the number and the “recipient network” accepts the number. The operation of donating a number requires that a number is “snapped out” from a network and “snapped into” the receiving network. If the subscriber ceases to need the number then it is normal that the original donor receives the number back and “snaps back” the number to its network. The situation is slightly more complex if the user leaves the first operator for a second and then subsequently elects to use a third operator. In this case the second operator will return the number to the first and then it is assigned to the third Calls to ported numbers are completed when a customer who calls a ported number sends the dialled number to a provider's SSP (Service Switch Point), where it is identified either as a local call or not. If the call is local, the switch has the NPA-NXX in its routing table as portable, so it sends a routing request to the STP (Signalling 1 Transfer Point) which accesses a local database that is updated by an LSMS (Local Service Management System) which holds all routing for all ported numbers to which the carrier is responsible for completing calls. If routing information is found, a response is sent to the "query" containing the information necessary to properly route the call. If it is not a local number, the call is passed on to the STP and routed until it gets to a local carrier who will perform the "query" mentioned earlier and route the call accordingly.

7. Elements of MNP

MNP Clearing house(MCHA) & its Disaster recovery site

NP Database (NPDB) & its Disaster recovery site with security provisions

10

Page 11: Mnp Main Report

NP gateways at operator’s end

NPDB at operator’s end

8. Database Management for MNP

All implementations of mobile number portability involve the use of databases which contain information of the networks and associated ported numbers. This information is used for a call to determine the correct terminating network of a ported number. Databases relating to Number Portability are typically managed either in a centralised or in a distributed manner. Logically Centralised Database with regionally located databases is setup and managed by neural third party setup by operators. Logically Centralised approach may serve as a common platform for ordering, provisioning, and notification process of number portability

8.1 Synchronisation of Database Updation of different operators

Port information is kept in a centralized master of Reference Database. Any update to theReference Database is broadcasted more or less in real time to all operators. (Push method). Alternatively Reference Database can be downloaded by operators (pull method).

9. Network ElementsArchitecturally, seven basic components are required to deploy local numberPortability (LNP):

• Service order administration (SOA)• Number portability administration centre (NPAC)• Local service management system (LSMS)• Service control point management system (SCP MS)• Number portability database (NPDB)• Signal transfer point (STP)• Service switching point/mobile switch centre (SSP/MSC)

11

Page 12: Mnp Main Report

Service Order Administration (SOA)Service order administration provides the functionality to interface to carriers’ order and provisioning systems in order to update the NPAC for access by all other carriers. The SOA’s primary functions include subscription audit request/management; data administration; data transfer to the NPAC; report generation; bulk-file parse and upload; subscription tracking; legacy order entry interface; and logging. Depending on an individual service provider’s requirements, the SOA may interface with multiple NPACs to allow for nationwide number portability. The carrier-to-SOA connection may be custom-designed to interface with existing carrier order entry systems. However, the SOA interface to the NPAC is a common management information service element (CMISE), providing subscription management functions as well as logging, error reporting, and alarm functions. Specific industry-approved interface requirements are contained in the NANC Functional Requirements Specifications (FRS) and Interoperable Interface Specification (IIS).Orders

Number Portability Administration Centre (NPAC)

12

Page 13: Mnp Main Report

The FCC’s First Report and Order, Docket No. 95-116 describes the third-party, neutral database administration function in support of number portability. Called the number portability administration centre (NPAC), this database is designed to receive information from both the incumbent and new service providers, validate the information received, and download the new routing information when an activate message is received indicating that the customer has been physically connected to the new service provider’s network. Each ported number is a subscription version within NPAC that contains the new service provider’s ID, the location routing number (LRN) associated with the new switch, and routing data associated with additional services the customer may request (for example, line information database (LIDB), calling name delivery (CNAM), and so on). The NPAC also maintains a record of all ported numbers and a history file of all transactions relating to the porting of a number. The NPAC provides audit functionality and the capability to retransmit subscription version information to local service management systems under certain conditions. The NPAC is not involved in real-time call processing. The NPAC provides management, administration, oversight, and integration of NPAC operations, hardware and software development, and all maintenance related functions. It is responsible for meeting performance standards established by the industry and providing user and technical support services and training for industry participants on an ongoing basis.

Local Service Management System (LSMS)The local service management system is a fault-tolerant hardware and software platform that contains the database of information required to enable routing and call completion to ported telephone numbers. The primary functions of the LSMS are subscription management, network data management, service provider data management, error processing and notification, transaction event logging and reporting, transmission of activation/deactivation events to the network elements, and audits. The LSMS interface with the NPAC provides real-time activation/deactivation information upon download from the NPAC and can send responses to the NPAC once a message or subscription version is processed. Similar to the SOA, the interface between the LSMS and the NPAC is CMISE and contains capabilities for event logging, security, and alarming. The LSMS is expected to mirror NPAC ported routing information and can request updates from the NPAC in a variety of ways if database synchronization is in question. Specific industry approvedinterface requirements are contained in the NANC FRS and IIS.

Service Control Point Management System (SCP MS)

The service control point management system provides interface services between the LSMS and the SCP. The SCP MS may or may not be physically integrated with the SCP.

Number Portability Database (NPDB)

13

Page 14: Mnp Main Report

The number portability database contains the routing information necessary to support number portability. The NPDB provides the LNP association between the called party and the carrier LRN, identifying the switch to which the call should be routed. The NPDB stores all ported numbers within the ported domain. Carriers can choose between two different LNP database architectures for accessing the LRN associated with a particular directory number: an integrated STP/SCP configuration or an STP with an adjunct SCP. An LNP SCP provides the LRN for a particular directory number. The correct routing information for SCP-based services, including line information database (LIDB), calling name delivery (CNAM), custom local area signalling services (CLASS), and inter-switch voice messaging (ISVM) for a ported directory number, is determined by 10-digit global title translation (GTT), also provided in the NPDB. The SCP is a high-transaction-oriented server that receives intelligent network (IN) and advanced intelligent network (AIN) 0.1 LNP Transactional Capabilities Application Part (TCAP) messages or Number Portability Request (NPREQ) messages from the SSPs/MSCs using the SS7 network. As an alternative, some providers deploy an integrated STP/SCP platform, which enables high transaction rates but requires fewer infrastructures (links and ports).

Signal Transfer Point (STP)The signal transfer point receives the LRN query from the SSP/MSC and routes he query to the appropriate LNP SCP. The STP returns the SCP response to the SSP/MSC

Service Switching Point/Mobile Switch Centre (SSP/MSC)

The exchange carrier owns and operates the service switching point/mobile switch centre. Service switching points must be able to generate an LNP query to the SCP (via the STP network) when a call is placed to a telephone number in a ported domain. A ported domain is an MSA that has implemented number portability. A query is generated on any call to an NPA-NXX that has been marked as portable in the local exchange routing guide (LERG) and NPAC with at least one ported number.

10. Working of MNP

14

Page 15: Mnp Main Report

All Cell phones have special codes. These codes identify the phone, the phone’s owner, & the service provider. Cell phones use high frequency radio signals to communicate with cell towers located throughout the calling area. These phones operate in the frequency range of 806-890 MHz.

10.1 PORTING PROCESS

15

Page 16: Mnp Main Report

16

Page 17: Mnp Main Report

11. NUMBER POOLING

It is widely recognized that the current method of allocating NPA-NXXs in blocks of 10,000 is inefficient and contributing to shortages of numbering resources. In an effort to find a more efficient method of allocation, FCC had approved a National Number Pooling plan for network resource optimization. Number pooling is defined as the ability to share an NPA-NXX among several facilities-based carriers within the same rate centre. The concept of pooling is based on the fact that whole blocks of telephone numbers, held by some service providers, are not assigned or in service. Pooling allows these currently unassigned blocks of numbers to be reassigned to other service providers in need of numbers, as they request and show need. With pooling, service providers can maintain a small supply of numbers for expected subscriber assignment. As that supply depletes, service providers will request additional numbering resources from the industry inventory maintained by the Pooling Administrator.

When a "pooled" block of numbers is transferred from one service provider to another, there is some critical information that needs to be broadcast across the region to ensure effective data provisioning for call routing. To facilitate the broadcasting of "pooled" blocks and associated routing data, the Location Routing Method, the same platform used for LNP could be used for implementation of national number pooling. This method of resource allocation allows NXXs within a given NPA to be shared among entities that offer service to subscribers within a defined geographic area (rate centre). Specifically, it allows the assignment of numbers to competitive service providers in blocks of 1000.

While wireless carriers are not currently required to participate in number pooling, the September 1999 ruling by the FCC did dictate that the Number Administrator will ensure that 10,000 number blocks are available for assignment to wireless carriers. This safeguard will guarantee that wireless carriers are not prevented or disabled from operating in a pooled environment in which they are not currently participating. However, as the wireless industry implements full number portability, it will inevitably also become subject to pooling standards.

CHAPTER-2

12. Mobile Number Portability in India

World’s lowest call rate and fastest growing subscriber rate is what differentiates Indian

Telecom market from the other country’s market, yet a mobile penetration rate of as low as

37.94% (as in April 09). The reason for this can be considered the rural areas where the

majority of population resides and the access providers find it hard to provide services at

these remote places. Another major reason is the economic status of the people. Still this is a

growing market with around 12-13 access providers spread across the nation while a few

others only providing services in selected few areas.

17

Page 18: Mnp Main Report

The regulatory Authority, TRAI (Telecom Authority of India), in the year 2006 among other

plans and reforms came up with the plan of implementation of Mobile Number Portability

(MNP). It was suggested that by April 2007, MNP will be implemented. But it has been

delayed due to several reasons, the major ones among them being,

Opposition from the mobile service providers asking TRAI to implement fixed

number portability before MNP.

Regulatory authority taking a lot of time in the analysis and planning.

Delay due to bidding for the MNP service providers.

Opposition from the Department of Telecommunication stating the technical

difficulties in MNP implementation.

And now after a series of consultations and surveys, the ground is all set with the MNP to be

launched and according to TRAI, MNP will be launched on 31st Dec 2009 in metros and

category ‘A’ service areas (which include Delhi, Mumbai, Kolkata, Tamil Nadu, Karnataka,

Maharashtra, Gujarat and Andhra Pradesh) and by 20th March 2010 in other B and C class

service areas. Telecordia’s joint venture company MNP Interconnection Telecom Solutions

India Pvt Ltd (MITS) will manage India’s Mobile Number Portability solutions in South and

East of India, while Syniverse Technologies in the North and the West1.

Absence of number portability is a major reason for customers not being able to switch from

their existing access providers even if they are not satisfied with the services of the operator

specially to the business person, for whom a change in number means communicating the

new number to the clients and other business associates and also requires modification in

stationary and other media through which the number is displayed. This can be taken as one

of the reason for decrease in the level of competition as the service providers know that the

customers will not move to other access providers.

On the contrary the access providers opine that MNP is unnecessary as the cost structure of

the Indian Telecom sector was the highest with lowest tariffs and this would only increase

network costs, forcing them to divert resources from their current plans. They also suggested

for the implementation of fixed number portability before MNP was implemented as fixed

line services are the one which need competition with only two companies BSNL and MTNL

having over 94% market share. TRAI’s answer to this argument was that in the current

scenario where mobile usage is much higher compared to the usage of fixed line services,

18

Page 19: Mnp Main Report

MNP was more beneficial for the customers. It also gave the reason that the incumbents’

legacy system would not be efficient enough for the implementation of FNP.

Amidst all this on September 23, 2009 TRAI released what it called the “Telecommunication

Mobile Number Portability Regulations, 2009”. This regulation clearly defined the roles of

each of the involved operator, criteria for a customer to be able to use MNP, technology to be

used for implementing MNP and other details based on the inquiries and comments the

authority had received from the different parties involved in this project. Here is a brief

summary of the regulation based on the original document.

It has been made mandatory that all the service providers or operators provide MNP to their

customers. By Nov 26, 2009 all the mobile service providers should be up with the facilities

to automate the porting process automatic and SMS based. A set of criteria for customer’s

eligibility to apply for porting are specified which state that a customer could only submit a

porting request if it’s been ninety or more days since the activation of the number if the

number has not been ported earlier or the same duration since the previous porting request.

Some other legal clauses and bill clearance conditions have also been included.

13. A Flow Chart depiction of steps involved for porting a number.

Starts from a subscriber raising a porting request to Recipient Operator and ends with number activated in Recipient’s network.

19

DO sends an automated SMS reply along with a unique porting code

Customer making a written request to the recipient operator (RO) for porting along with other documents required.

Customer asked by RO to send an SMS to the Donor Operator (DO)

RO verifies the documents

Customer submits the code to the RO

Within 24 hours, RO forwards the unique porting code to the MNP service provider (MNPSP).

On receiving the porting request MNPSP verifies the 90 day condition and no pending porting request on that number from its database

If condition is satisfied, MNPSP forwards the details to the DO for clearance.

Page 20: Mnp Main Report

A subscriber may within twenty four hours withdraw the porting request by informing the

Recipient Operator.

14. What Access Providers think of MNP

Initially not in favour of MNP, as it would reduce the profits for them, Access Providers tried

hard for MNP not to be implemented. Implementation of MNP will not be a simple change

for the Access Providers. Any of the providers’ system working on Mobile Identity number

or Mobile Directory Numbers will be affected. Processes and systems that would be

influenced: Billing, customer service, order activation, call delivery, roamer registration &

support, SMS centre, directory assistance, caller ID, calling name presentation, switches,

Home Location registers and visiting location registers.

15. Who is likely to switch

20

DO checks if the criteria for porting are satisfied and inform MNPSP of the same

MNPSP fixes a date and time of porting which should be 36 hours from the time of receipt of the clearance from the DO & informs the same to DO & RO

RO informs the same date & time to the subscriber through SMS or telephonically or an automated voice message

On the specified date, MNPSP communicates the instructions for disconnecting the number to the DO

On receiving the report of the completion of number activation from the RO, MNPSP allocates the ported number a corresponding Location Routing Number and broadcasts the same to all the Access Providers and International Long Distance operators.

RO will do the required within 1 hour of receiving information from the MNPSP and inform MNPSP of completion

On receipt of the release from DO or completion of 1 hour MNPSP will inform the RO to activate the mobile number

DO within 1 hour of receipt of instructions release the number and report it to MNPSP

Page 21: Mnp Main Report

According to a recently conducted study by the Nielson company in which 12500 mobile

users across 50 centres were surveyed, close to one in five (18%) mobile subscribers would

change their mobile operator if MNP is introduced in the market. Based on the access

providers, one in four Reliance & Tata Indicom subscribers would like to change operators.

These access providers would have the highest porting rate based on the survey. The study

also says that subscribers with higher spending, post paid customers and business subscribers

show greater tendency to switch on introduction of MNP3.

“According to Shankari Panchapakesan, Executive director, Telecom Practice, The Nielsen

company, “Mobile number Portability represents a powerful opportunity for the operators to

drive in-bound porting of high-value subscribers provided they have a good understanding of

who is more likely to switch and why. MNP can be leveraged by operators through smart

targeted marketing and promotion to coincide with the introduction of this facility.

16. How Calls will be handled after MNP

All Call Query would be the method that would be used to handle calls after MNP is

implemented.

All ported mobile numbers will be maintained in a “Local Number Portability Database”.

Every Access Provider will be assigned a code called “Location Routing Number”. The

MNP service provider will maintain a centralized database which would contain all the

mobile numbers of the nation and their corresponding current Access Provider’s location

routing number. When a call is made, the dialler’s network which has access to the MNP

service provider’s database will query the database to find the dialled number’s Access

provider. Based on the information the call is progressed further. This solution is an

expensive one but the authority feels that in long Term it would be a stable one. The setup

time of each call, whether the dialled number is ported or not is increased and would be

inefficient in case the porting volume turns out to be too low.

21

International Long Distance

Page 22: Mnp Main Report

1. Query

17. Different Costs and Charges Involved

Implementation of Number Portability would incur costs to different stakeholders as the

regulatory authority is would not be paying any of the costs involved. The different costs and

who would be paying are:

Setting up of Location Number Portability Database which will be two in number,

one main and the other disaster recovery. These will be maintained by the Mobile

Number Portability Service Providers.

22

Location Number Portability Database

Donor Operator Network

Originating Network

Receiver Network

Long Distance Operators

Location Routing Number

2. New Routing Information

3. Call Routing

International Long Distance

Page 23: Mnp Main Report

A fail proof Mobile Number Portability gateway from the Access Provider’s system

to the main and disaster recovery sites of the database. The cost for this will be born

by the Access Provider.

A “Per Port Transaction Charge” to be paid by the Recipient Operator to the

Mobile Number Service Provider.

The Donor operator has to maintain a record of all ported out numbers and rejected

porting requests for at least a year.

The Recipient Operator has to keep record for a minimum of one year the record of

all rejected porting requests.

The subscriber willing to avail Mobile Number Portability, has to pay to the Recipient

Operator a nominal fees (not finalized yet) as the “Porting Charges”.

A “Dipping Charge” to be paid by the Access Provider to query response system to

Mobile Number Portability Service Provider to obtain the correct Location Routing

Number. The access provider has to query the database for calls, missed calls and

even sms.

18. Issues not covered by TRAI

The tariffs for calling vary if a person calls in the same Access Provider’s network as his own

or any other access provider. Also in India the calling party is charged for the call. When the

Mobile Number Portability is implemented, the called party might not be aware if the dialled

number has been ported to some other access provider. So the tariffs that will be applicable to

him would not be clear. This is termed as “Consumer ignorance Problem”4 in some of the

case studies as the consumer is not aware of the billing that is being done on his mobile

usage. This can lead to distortion of the tariff structure of calls progressed across networks.

23

Page 24: Mnp Main Report

This issue has not been covered in the regulation and needs to be looked into as it is a very

important consumer concern.

Some of the possible solutions as applied in some other countries are using an acoustic signal

to alert the called subscriber that the call is terminating into different network due to porting

out of the called subscriber, or the verbal announcement of the tariff structure of such calls or

having a toll free number or toll free SMS facility for customer to check if a number is ported

out or not. Whatever method is applied, will only incur extra costs in the implementation of

the number portability.

19. Will MNP be a success

The success of MNP can be viewed in terms of the porting rate. Porting rate depends on a

number of factors. Considering that today a person can get a new connection at lesser than

$1, if a high portability charge is applied, porting rate cannot be expected to be high. And it

has been decided that the porting charge will be somewhere between INR 20 to INR 200

($0.40 to $4). Another important factor will be how convenient it is for an individual to port a

number. As of now seeing the regulation, MNP doesn’t seem to involve much hassle for the

customer to apply for porting. The time taken for porting is also an important factor as a

customer will definitely compare the porting time with the time taken to get a new number

activated as it just takes a few hours to activate a new number. As per the regulation, the

porting process should not take more than 4 working days in all licensed service areas except

in the case of Jammu & Kashmir, Assam and North East where the maximum time allowed is

12 days. Exit barriers also an important consideration but since exit barriers do not exist in

Indian market, porting rate can be expected to be high. Churn rate will also affect the porting

rate. The Churn rate in India is very high and even if a part of the churning subscribers opt

for porting, MNP can be expected to be high. The number of access providers in a particular

area will also be a major market dynamic as higher the access providers, more the offers to

lure customers.

Taking all this in consideration it can be said that it is very likely that MNP will be a success

as the porting charges seem to be affordable compared to the costs that would be incurred in

switching access provider.

24

Page 25: Mnp Main Report

Over the past decade, number portability of various types has been implemented in a range of countries The detailed history of number portability implementation in each country is unique, but later implementations had the advantage of being able to take into account the experiences of earlier implementations

Recently IDC had conducted a study, which revealed that 30 per cent of mobile users are ready to change their operator if given a better option. TRAI said that the introduction of number portability will also benefit operators as they will strive to offer better service to prevent churn. However, mobile operators are not keen to implement it fearing huge churn. International experience proves that there is substantial improvement in the QoS after introduction of NP. The roadmap to MNP requires cooperation of all the stakeholders.

20. MNP PROS AND CONS

20.1 MNP PROS:-

1) The Mobile Number Portability (MNP) allows you to retain your existing or old mobile phone number despite switching over to yet another service operator. You enjoy the advantage of retaining your old mobile phone number without unduly worrying about the burden of using or memorizing a new number.

2) Despite switching over to yet another service operator, there is no any additional burden of informing it to your relatives and friends. If you are a business man or a professional like a

25

Page 26: Mnp Main Report

doctor or lawyer, your customers or clients can contact you with the same old mobile phone number. Hence, despite switching over to a new service provider, you retain your customers or clients intact.

3) You enjoy the benefits of better service from the new operator by retaining the same old mobile phone number wherever you go or reside. Again, each service provider offer some special services that cater to the needs of its bulk customers. You have the added advantage of availing such special services from a new operator by retaining your old mobile phone number using MNP facility.

4) The facility of Mobile Number Portability is a boon to the countries like India and China, where the mobile phone users are in millions and their density is very high.

20.2 MNP CONS:-

1) By switching over to a new service provider, a mobile phone subscriber loses the special services and facilities offered by the previous or old service provider once and for all.

2) Despite retaining the same old mobile phone number through MNP facility, it takes time to acclimatize to the operating system and features of the new service provider.

3) In order to avail the MNP facility, you have to keep in touch with two service providers, the old and the new. It involves a number of technical feasibilities as well clerical formalities.

4) By availing the MNP facility, your mobile phone number loses it specific identity associated with a particular operator. Now it is not possible to predict exactly from where a subscriber avails his mobile phone service.

21. MOBILE OPERATORS IN INDIA

Names of some of the mobile operators are listed below:

26

Page 27: Mnp Main Report

REFERENCES

Aoki, R. and J. Small (1999), The economics of number portability: Switching costs and two-part tariffs, working paper, University of Auckland.

Telecom regulatory Authority of India, www.trai.gov.in

27

Page 28: Mnp Main Report

INTUG (2003), Mobile Number Portability ,International Telecommunications User Group (INTUG)

Consultation Paper on Mobile Number Portability, Consultation Paper No. 7/2005, Telecom Regulatory Authority of India, New Delhi: July 22, 2005.

28