MOBILE PORTABILIT

ABSTRACT

Mobile number portability allows a mobile subscriber to switch operators without changing

his/her telephone number. This paper describes and analyzes mobile number portability routing

mechanisms and their implementation costs. Cost recovery issues for number portability are

discussed in this paper from a technical perspective. We note that rules for cost recovery also

depend on business and regulatory factors that vary from country to country.

This paper examines the consequences of introducing mobile number portability (MNP). If the

sole effect of introducing MNP is the abolishment of switching costs, MNP unambiguously

benefits mobile customers. However, if MNP also causes consumer ignorance, as telephone

numbers no longer identify networks; mobile operators will increase termination charges, with

ambiguous net effect on the surplus of mobile customers.

Mobile number portability (MNP) requires that mobile telephone customers can keep their

telephone number–including the prefix–when switching from one provider of mobile Tele

communications services to another. In the absence of MNP, customers have to give up their

number and must adopt a new one when they switch operators. As a result, customers face

switching costs associated with informing people about changing their number, printing new

business cards, missing valuable calls from people that do not have the new number, etc. Based

on these considerations, many regulatory authorities have imposed mandatory MNP–or are about

to require its introduction–so as to reduce customers’ switching costs, attempting to make mobile

telecommunications more competitive The world’s first country to introduce MNP was

Singapore in 1997.

This paper introduces the concept of number portability, explains its different types and benefits,

and the technical, operational, and economic issues that might arise out of its implementation in

India. The specific issues such as ensuring tariff transparency, the National Numbering Plan, and

regulating porting charges, etc. have been raised and will need careful consideration.

MOBILE PORTABILITY

TABLE OF CONTENTS

1. Introduction

1.1 What Is Portability

1.2 Definition

1.3 Types

1.4 Concept

1.5 Basic terms

1.6 Salient Features of MNP

2.Detailed Description Of The Technology

2.1Number portability technical aspect

2.2 Basic Implementation Of MNP

2.2.1 Indirect Routing or Decentralized or Bilateral architecture

2.2.2 Direct Routing or Centralized architecture

2.3 Call Routing Schemes

2.3.1 All Call Query (ACQ)

2.3.2 Query On Release (QOR)

2.3.3 Call Dropback

2.3.4 Onward Routing ( OR)

2.4 Working Of MNP

2.4.1 MNP SMS Flow

2.4.2 MNP Prepaid Call Flow

2.4.3 MNP Call Flow To Ported Out or Other Operator

2.4.4 MNP Call Flow Normal Mobile To Mobile Calls

2.5 Overview Of Technical Choices In Other Countries

3. Implementation

3.1 Porting Process

3.1.1 How To Change Your Operator

3.1.2 How To Transfer a Mobile Number To a New Mobile Phone

3.2 Factors Influencing The Success Of Number Portability

3.3 Challenges Of Implementing Number Portability

3.3.1 Number Portability Set Up Cost

3.3.2 NP Maintenance Cost

3.3.3 Call Routing Costs

3.4 Solution

4. Advantages And Disadvantages

4.1 Benefits Of Mobile Number Portability In India To Users

4.2 Problems Of Mobile Number Portability In India To Users

5. Conclusion And Future Scope

5.1 Conclusion

5.2 Future Of Mobile Number Portability

6. References

6.1 Websites

1. Introduction

1.1 What is portability?

Portability is a characteristic attributed to a computer program if it can be used in an operating

systems other than the one in which it was created without requiring major rework.

Porting is the task of doing any work necessary to make the computer program run in the new

environment. In general, programs that adhere to standard program interfaces such as the

X/Open Unix 95 standard C language interface are portable. Ideally, such a program needs only

to be compiled for the operating system to which it is being ported. However, programmers

using standard interfaces also sometimes use operating system extensions or special capabilities

that may not be present in the new operating system. Uses of such extensions have to be removed

or replaced with comparable functions in the new operating system. In addition to language

differences, porting may also require data conversion and adaptation to new system procedures

for running an application.

Portability has usually meant some work when moving an application program to another

operating system.

Portability can be applied in any programming languages but highly preferable portable

languages are given below

Examples of portable languages: Java, C#(C sharp).

Java programming language and runtime environment has made it possible to have programs that

run on any operating system that supports the Java standard (from Sun Microsystems) without

any porting work. Java applets in the form of precompiled bytecode can be sent from a server

program in one operating system to a client program (your Web browser) in another operating

system without change.

1.2 Mobile Number Portability: Definition

Mobile Number portability is a telecommunications network feature that enables end users to

retain their telephone numbers when changing service providers, service types, and/or locations

Mobile Number portability (MNP) enables mobile subscribers to change their service providers

or their location without having to change their existing phone numbers. If the subscribers are

not satisfied with the services of their service provider, they can change their service provider

while retaining the existing phone number. This infuses competition among service providers

and forces them to improve their service standards to check subscriber churn. Many countries

have made number portability mandatory to liberalize competition. Many others are in the

process of implementing it. A significant technical aspect of implementing number portability

is related to the routing of calls or mobile messages (SMS, MMS) to a number once it is ported

to some other network.

1.3 Types

There are three basic types of number portability-

- Operator portability: It is the ability of an end user to retain the same telephone number as he/she changes from one operator to another. It is also referred to as ‘service provider number portability’ and is equally applicable to fixed telephony, mobile telephony and non-geographic number service providers. These forms of number portability are known as, respectively:

local number portability or LNP (for geographic numbers in fixed telephony networks);

mobile number portability (for GSM and other mobile system numbers);

non-geographic number (NGN) portability (for services such as freephone and special rate services).

- Geographic portability : It is the ability of a fixed telephony end user to retain the same telephone number as he/she moves from one physical location to another.

- Service portability: It is the ability of an end user to retain the same telephone number as he/she changes from one type of service to another (eg from POTS to ISDN).

1.4 Concept              MNP functionality is used only in MT (Mobile Terminating) transactions of voice and messaging. For MO (Mobile Originating) transactions, the current flow scenario remains unchanged.             Only for the MT functionality, the mobile number has to be identified and the corresponding service provider has to be interrogated for optimal routing of the service.

1.5 Basic Terms Ported out – If a subscriber moves to new service provider, for the old service

provider, he is a “ported out” subscriber. Ported in - If a subscriber moves to new service provider, for the new service

provider, he is a “ported in” subscriber.

Donor – The service provider left by the subscriber. OR  It is the network that first assigns a telephone number to a subscriber

Recipient – The service provider joined by the subscriber. OR  It is the network that currently serves the ported number. A recipient network is a network that a subscriber’s number is ported to when the subscriber switches the service provider.

Participant – A Participant is a service provider who is not related to the porting process in any way and still needs the routing information for call routing and various other activities.

CDB / NPDB – Central Database or Number Portability Database.

ACQ – All Call Query

1.6 Salient features of the MNP

• MNP facility shall be available only within a given licensed service area.

• A subscriber holding a mobile number is eligible to make a porting request only after 90 days of the date of activation of his mobile connection. If a number is already ported once, the number can again be ported only after 90 days from the date of the previous porting.

• The subscriber who wishes to port his mobile number should approach the Recipient operator (the operator to whom the subscriber wants to port his number). The Subscriber may be required to pay porting charges, if any, to the Recipient Operator.

• The subscriber making the porting request is required to have cleared all the bills issued prior

to the date of porting request. He shall give an undertaking that he has already paid all billed dues to the Donor Operator as on the date of the request for porting and that he shall pay dues to the Donor Operator pertaining to the mobile number till its eventual porting and that he understands and agrees that in event of non-payment of any such dues to the Donor Operator, the ported mobile number shall be liable to be disconnected by the Recipient Operator.

• A subscriber may withdraw his porting request within 24 hours of its submission to the Recipient Operator. However, the porting charges shall not be refundable.

• The regulation envisage a maximum time period of 4 days for the completion of porting process in all licensed service areas except in the case of J&K, Assam and North East licensed service areas where the maximum time allowed is 12 days. However, efforts will be made to further reduce the porting period.

• Access Providers are required to implement All Call Query method.

• The Originating operator shall be responsible to route the call to correct terminating network.

Chapter II

2. DETAILED DESCRIPTION OF THE TECHNOLOGY

2.1 Number Portability Technical Aspect

Number Portability has to ensure that call routing for all mobile sessions Voice, SMS, MMS should be enabled with routing to the ported network for the same called subscriber number. IETF defines three types of number portability (NP): Service provider number portability (SPNP), location portability and service portability.The current paper focuses on the SPNP, which is the agenda set by TRAI to the service provider bodies in India. SPNP allows subscribers to switch service providers while retaining the same phone number. The technology challenges towards implementation come through complexities in number administration, network signalling functions, call routing, billing and service management.A translation element is necessitated in the network as the mobile number addressing scheme becomes a virtual address. Central to the address translation scheme is the NP translation database hereafter to be termed as NPDB (Number Portability Database).The network classification is done as follows:

Donor Network: The network that first assigns a telephone number to a subscriber from one of its administered ranges

New Serving Network: The network of the current service provider serving the ported number.

Old Serving Network: The network prior to porting in of the number to the current network. It is not necessarily the Donor network as multiple provider switches is feasible.

2.2 There are two basic implementation of MNP

2.2.1 Indirect Routing or decentralized or bilateral architecture 

This model works bilaterally between the donor and recipient service providers who are

responsible for informing all others of the change. It would suit to markets with less number of

service providers. Each provider will have a dedicated setup and comprehensive database of

ported out and ported in subscribers. As the number of service providers increases, the bilateral

approach becomes a great burden to all service providers involved in terms of time, cost and

resources. FNR (Flexible Number Register) will help the service providers have the ported

database in addition to the original HLR database.

Fig 2.2.1. Peer-to-peer approach

2.2.2 Direct Routing or centralized architecture

In direct routing, the concept of CDB comes into picture. This central database or Central

clearing house will handle all activities related to porting of subscribers between service

providers. This model is suited for markets with several service providers and this model

is currently used almost in all MNP implementations. Two options are available with this

model with all the service providers updating the ported number database in

synchronization with the CDB and the other is to query the CDB for all call interrogation

to get proper routing procedure. After obtaining the rules, rest of the call is handled

normally.

Fig 2.2.2. Centralized Approach

2.3 Call Routing Schemes

The implementation of the routing is through four different schemes:

2.3.1All Call query (ACQ)

Fig 2.3.1. ACQ

The Originating Network receives a call from the caller and sends a query to a centrally administered Number Portability Database (NPDB), a copy of which is usually residing on a network element within its network (like SCP).

The NPDB returns the routing number associated with the dialed directory number. A LRN prefix is usually added to the B‐MSISDN for the ported out number.

The Originating Network uses the routing number to route the call to the new serving network. Based on the LRN prefix (Location Routing Number) the originating network will route the call to the recipient network.

As donor network doesn’t get involved in the entire call flow ACQ scheme is called direct routing

2.3.2Query on Release (QoR)

Fig 2.3.2.QOR

The Originating Network receives a call from the caller and routes the call to the donor network.

The donor network releases the call and indicates that the dialed directory number has been ported out of that switch.

The Originating Network sends a query to its copy of the centrally administered NPDB. The NPDB returns the routing number associated with the dialed directory number. The Originating Network uses the routing number to route the call to the new serving

network.The QOR mechanism can hold out to be a smart implementation when the MNP porting figures are low. There are no unnecessary SCP queries for B party subscribers that are not ported yet, which is likely to save ample processing capacity on the network as well as associated call setup delay. However as the porting figures rise (which is close to 25% in most mature MNP markets), the cost of call setup and subsequent release in case of ported out numbers is likely to take an adverse hit on the network utilization as well as setup cost. Thus for a future proof implementation ACQ is the recommended scheme.

2.3.3 Call Dropback

Fig 2.3.3. Call dropback

The Originating Network receives a call from the caller and routes the call to the donor network.

The donor network detects that the dialed directory number has been ported out of the donor switch and checks with an internal network‐specific NPDB.

The internal NPDB returns the routing number associated with the dialed directory number.

The donor network releases the call by providing the routing number. The Originating Network uses the routing number to route the call to the new serving

network

2.3.4 Onward routing (OR)

The Originating Network receives a call from the caller and routes the call to the donor network.

The donor network detects that the dialed directory number has been ported out of the donor switch and checks with an internal network‐specific NPDB.

The internal NPDB returns the routing number associated with the dialed directory number.

The donor network uses the routing number to route the call to the new serving network

Fig 2.3.4 Onward rounting

2.4 Working Of MNP

2.4.1 MNP SMS FLOW

Fig 2.4.1 mnp sms flow

Assumptions: A and B both are Vodafone Delhi Subscribers (Ported In or normal).

A is postpaid number.

Let us now go through signalling flow.

1) A sends an SMS to B. Mobile Originated Forward Short Message (MO-FSM) is send to STP/MNP with destination as SMSC address(SMSC GT). SMSC address is already stored in SIM. MO-FSM also contains B number to which SMS is sent.

2) MNP check its database attaches RN/LRN to B number and forward MO-FSM to SMSC.

3) SMSC acknowledges the MO-FSM by FSM Response to MSC. This threesteps complete the MO leg of SMS Flow and handset receives an indication "SMS sent" at this point of flow

4) Step4 marks the beginning of SMS terminating flow. SMSC checks this is our own RN/LRN removes RN from B number and sends Send Routing Info- Short Message (SRI-SM) to STP/MNP. This message can be directly send to HLR also that depends on network topology.

5) SRI-SM is forwarded to HLR with B number.

6) HLR responds SRI-SM Response with the VLR address where subscribers is currently registered and IMSI of B number.

7) On receiving VLR address now SMSC knows where to send MT-FSM. SMSC send MT-FSM to that particular VLR with B number IMSI and SMS data.

Here after MSC tries to deliver this message to B Subscriber using standard MT SMS flow.

8) MSC/VLR acknowledge SMSC by MT-FSM response which contains status of MT SMS.

i.e delivered or failed cause if SMS is not delivered to B number.

2.4.2 MNP PREPAID CALL FLOW

Fig 2.4.2 mnp prepaid call flow

Assumptions: A and B both are Vodafone Delhi Subscriber in different MSC/MSS coverage area.

Let us discuss call flow step by step.

1) Subscriber A (prepaid) call B.

2) Since A is prepaid first query(IDP) has to go IN/SCP with "calling party number" Subscriber A MSISDN and "called party Subscriber" Subscriber B MSISDN. Here is change from normal prepaid call flow, in normal case IDP would have gone straight to serving SCP but in case of MNP IDP will sent to MNP server.

3) MNP server will check its database for B MSISDN and add LRN/RN according to operator to which B subscriber is registered, in above case it is Vodafone Delhi.After addition of LRN/RN IDP is forwarded to SCP.

4) IDP received by SCP contains LRN/RN + B MSISDN in "called party number" field and "calling party field" contains A MSISDN. Charging is done on the basis of LRN/RN. Here LRN is of Vodafone Delhi so local call rates apply to this call. In normal scenario charging would have be done on the basis on B party MSISDN.In response to IDP SCP revert with Connect/Continue message to MSC which contains "called party number" as LRN+B MSISDN.

5) MSC check called party number and removes LRN (as its own LRN) and forward SRI to MNP server.

Hereafter normal MNP call flow is followed which is already discussed in detail in earlier

post.

6) MNP server checks B MSISDN and forward SRI to HLR.

7) HLR queries with MSC B and provide MSRN to MSC A

8) IAM is send out to MSC B with called number at B party MSRN.

Thereafter normal terminating call flow taken place.

2.4.3 MNP Call Flow to Ported Out or Other Operator

1) Ported In/Out--> Ported In/Out subscriber are those which havechanged there Service providerExp: A was originally Airtel Subscriber and availed MNP and changed toVodafone so A will be Ported in number for Vodafone and Ported out Number for Airtel.

2) RN/LRN--> Called as Routing Number(RN) for NLD calls or Local Routing number(LRN) in case of Local call. Is four digit Unique Number allocated by TRAI to each operator.

Now let us go through call flow.

Fig 2.4.3 MNP Call Flow to Ported Out or Other Operator

Assumptions: Take an example of Vodafone Delhi, call is originated by A which is Vodafone Delhi subscriber to B number which is either other operator number or Ported out number.

Let us go through call flow in steps:

1) A dials B number

2) After receiving B number MSC send SRI to MNPDB. This is major difference between normal/MNP call flow. In normal call flow there would have been IAM to other operators MSC.

3) MNP check its database and returns with RN/LRN+ B number in SRI response as its not Vodafone Delhi subscriber.

4) After receiving RN/LRN+ B Number MSC agin checks its B number routing table and sends IAM to that operator.

Call flow remains same in case NLD also, IAM (LRN + B number) is sent to NLD in that case.

After this calls flow remains same as in case of normal call 

2.4.4 MNP Call Flow Normal Mobile to Mobile Call

Before coming to the point i would like to elaborate some terms which will used later in explaination.

1) MNPDB--> Mobile Number Portability Database, where in all details of subscriber is stored.

2) Ported In/Out--> Ported In/Out subscriber are those which have changed there Service providerExp: A was originally Airtel Subscriber and availed MNP and changed toVodafone so A will be Ported in number for Vodafone and Ported out Number for Airtel.

Fig 2.4.4 MNP Call Flow Normal Mobile to Mobile Call

Here i have taken example to Vodafone Delhi where Subscriber A in MSC1 and Subscriber B in Coverage of MSC2.

Let us now go through signaling flow in steps:

1) Subscriber A dials Subscriber B

2) MSC1 receives B number and SRI is sent to MNP server instead of HLR as in case of traditional call flow.

3) MNP checks its database and founds that this is own subscriber and relays that SRI to HLR.

4) HLR on receiving SRI check the VLR address of subscriber and send PRN to MSC2.

5) In response to PRN MSC2 returns with MSRN.

6) HLR forward that MSRN number to MSC1 in SRI Response Message

7) MSRN is now dialled out from MSC1 to MSC2 to establish the voicepath between two MSCs

After this call flow remains same as in case of traditional call flow which is already posted in this blog.

**There may be some changes in call flow as Implementing MNP is operator specific, they implement the way which is best feasible for them.

2.5 Overview of Technical Choices in Other Countries

Call routing to ported mobile numbers planned or adopted in European countries vary

considerably in technique. Table below illustrates this variation across various countries and for

which information is available:

Table 2.5: Technical solutions for MNP used in various countries

Routing from a fixed network to a mobile network

Routing from a mobile network to another mobile network

Belgium all call query all call query & query on release

Denmark all call query & query on release

all call query & query on release

Finland onward routing onward routing

France Phase 1: onward routing, phase 2: all call query

phase 1: onward routing, phase 2: all call query

Germany onward routing & all call query

all call query

Hungary all call query & query on release

phase 1: onward routing & all call query, phase 2: all call query

Ireland onward routing all call query

Italy onward routing & all call query

all call query

CHAPTER III

3. Implementation

3.1 Porting Process

3.1 .1 How To Change Your Operator

The procedure for MNP is as follows:

1. Send a message as  PORT <space> to 1900 [Toll Free].  Eg: PORT   9999999999    and send this message to 1900. 

2. You will receive a UPC Code in message. Note it down.

3. Now goto the nearest Customer service center (or Retailers) of Network you want to shift. (for ex, if you are shifting from X toY network, Goto Y's Customer Center).

4. Fill the Form and pay Rs. 19. In the form You have to mention UPC Code ( From Step 2). Submit your Photo & Address Proof.

5. The customer center will give a new Empty sim.

6. With in 24 Hrs you will receive an Acceptance Message to Confirm the Porting (for your old sim). Then You have to Agree with that by replying to the Message.

7. In the next 24 hrs you will get a another mssg (for your old sim) to select a 2hrs time slot.In this time your number will not work because the porting process will be done at this time. So give a 2hrs time which is convinient for you.

8. After this 2hrs the new sim (From Step 5) will work.

9. Insert the new sim in your phone, Now You are in the new network with old number.

3.1.2 How to Transfer a Mobile Number to a New Mobile Phone

Fig 3.1.2 How to Transfer a Mobile Number to a New Mobile Phone

When changing cell phone carriers, consumers now have the option of keeping their original mobile telephone number. Keeping the same number, regardless of cell phone carrier, is generally more convenient than changing. The responsibility of retaining a cell phone number lies on the new carrier. During the process of changing service providers, the customer service representative can enter a request to transfer a mobile number to a new mobile phone. The process of transferring a mobile number from an old phone to a new one is sometimes referred to as local number portability.

Instructions

1. Inform the customer service representative who is handling the purchase of your new mobile phone that you would like to retain your original mobile number. In some cases, the customer service representative will ask if you already have a telephone number. If

you are not asked, you should mention transferring your mobile number before the representative begins the activation process on your new phone.

2. Give the customer service representative your original mobile number. The customer service representative will look up your information and determine what company last held your number.

3. Provide the customer service representative with your account number with your previous carrier if asked. In some cases, customer service representatives need this information to determine whether you have the right to that mobile number.

4. Tell the customer service representative your account's personal identification number (PIN) if asked. You may also be required to provide the customer service representative with your billing address.

5. Ask the customer service representative if they have all the information they need to switch your telephone number to their carrier. Generally, this information is sufficient. However, if they require more information, provide it as necessary.

3.2 Factors Influencing the success of number portability

Subscriber Awareness: Subscribers needs to be aware of Number Portability (NP), its advantages, and how to go about it

Simplicity: NP success mainly depends on the simplicity of the process. There could be many rules that the regulator may impose. For example, a number can’t be ported in the first 6 months of the subscription. Such forced conditions hamper the success of NP

Speed: Speed is one of the major factors that affect the success of NP. Service level agreements should be stringent enough to minimize the time taken to port the number to other network. Thisincreases the level of customer satisfaction

Cost factor: NP success also depends on the cost of porting the number. The lower the cost, the higher will be the rate of porting.The cost here refers to the amount that the subscribers need topay to port their number to some other service provider’s network.This all depends on the regulatory authority that decides who bears the cost of porting. For better success and market competition, it is recommended that the new service provider, who is getting the subscriber, bear the cost of porting.

3.3 Challenges of implementing number portability

The major challenges of implementing number portability are:

Cost involved in upgrading the network infrastructure to support number portability

Cost involved in maintaining the upgraded infrastructure

Cost involved in the usage of network resources to route the calls to the ported number

3.3.1 Number portability setup costs

This is one of the major deterring factors for NP implementation in any country. There are many expenses involved in NP system setup. The setup costs include the cost of setting up the central NPDB, which maintains the complete information on the porting details, providing a well-defined interface for the service providers to interact with apart from adhering to the policies setup by the telecom regulatory. Apart from these all the service providers need to have NP gateway server capable of interacting with the central NPDB using the defined application programminginterface (API). The NP gateway should, apart from maintaining an internal NPDB, provision the routing information to the respective network elements. Apart from these, upgrading the network adds to the cost. The service providers are supposed to bear these costs.The setup costs includes:

Central NPDB setup cost

Software development or upgrade

Network upgrade

Customer Relationship Management (CRM) upgrade

Cost involved in upgrading the billing system

3.3 2 NP Maintenance costs

Once the NP system is deployed, there are many other costs involved in maintenance of the system. The maintenance cost includes the following:

Cost for the agreed procedure involved in the porting process

Activating the ported number

Provisioning the routing information

Informing all the service providers of the ported number

3.3.3 Call Routing costs

Routing the call to a ported number is one of the major issues in NP. In case of ACQ, the originating network needs to make a query to the NP database irrespective of whether the called number is ported or not. Even the other schemes of NP implementation has their own impacts on the network signaling, database queries, and other network resources, which directly influence the network traffic adding on to the cost.

3.4 SOLUTION Many countries have their own guidelines on how to share the costs incurred in NP implementation. Regulatory bodies can consider the following points in arriving at a better

model for cost sharing to implement number portability.

o Number of subscribers per service provider should be the base at the time of setting up the NP System

o The service providers can incur the annual maintenance costs for using the service of the central NPDB. This can be for the services used such as NPDB system and customer help desk usage. These costs should be based on the usage of the central NPDB or based on the quality of service such as the bandwidth for accessing the central NPDB

Recipient service provider can pay for the costs incurred by the centralized NPDB for any subscriber that ports to its network

Recipient service provider can pay for the costs incurred by the donor for each ported number

The central NPDB should be a non-profitable or at most a reasonable profit making organization and there should be a policy to share the profits with the service providers to lower their burden.

Service providers can be made stakeholders in the central NPDB, though the regulatory body shall have the sole discretionary powers to control the NPDB.

CHAPTER-IV

4. Advantages and Disadvantages

4.1 Benefits of Mobile Number Portability in India to users

Following are the benefits that Indian people will get after Mobile Number Portability is implemented in India:

People will not have to change the number for changing the operator : This is the core theme of this service and I hope I do not need to say much here.

One will not have to inform all the people in their phonebook about the operator change because this will not change the number anymore: When you change the operator, it is your personal matter from now and you need not tell anyone or let anyone know which telecom operator you are taking service from!

You can save money by having the best plan you like : while some people hardly leave the city they live in and want more features, others might travel a lot and need better signal reception. Mobile Number Portability allows both type of users to have the same number without having the additional headache.

Due to operators offering free talktime and data usage, there will also be monetary benefits to the users for short time: While there has been news that BSNL is offering talktime for free to those customers, people are waiting for the same or similar goodies from other operators.

4.2 Problems of Mobile Number Portability in India to users

While Mobile Number Portability is a great technology, it may cause a few problems to the users. They might be as follows:

The switching from one operator to another requires you to pay Rs. 19 : Just like some say it, "Nothing comes for free". So you have to pay some charge to the new operator for using their service. It is expected that operators would ask you the maximum amount, Rs. 19 for changing to their service. While this is not certain, even the possibility of the same is a disadvantage.

You still have to follow the same old procedure of going to a shop, getting a new SIM and so on: If you thought that you would just send a SMS and you will change your operator which you are in the train, you are wrong. You still have to go to the shop and get a new SIM. So you cannot retain your old SIM (and all the phone numbers and messages stored in it). So we suggest, you get a habit of storing your contacts in your mobile phone memory instead, if you are going to use Mobile Number Portability service soon and again.

It takes time for the switch to take place : So if you want it to happen immediately, you cannot do it. Nothing is in your hands after you have started the process of changing the operator. One would have to wait for about 4 days for the switch to happen in the worst case. In the best case, it would still take about an hour.

Since it has not been made clear that when can a person use his new SIM card after applying to the new operator, it may cause problems to the users in some scenarios: Today you get a new SIM and start using the moment you buy it. This will not be possible since the new SIM you buy will not be active unless the number is transferred to the new operator, which may take time of the old operator is snail paced.

We cannot use this service to change the operators across telecom circles : Say you are a student who is going outside the state (and possibly the telecom circle as well), then you

cannot keep the same number in the new state. In simpler words, assume that if a person living in Karnataka is shifting to Madhya Pradesh wants to retain his number, he will not be able to.

CHAPTER – V

Conclusion and Future scope

5.1 CONCLUSION

To implement number portability, the best solution is to implement the centralized system, maintain a common number porting database, and use the All Call Query (ACQ) call routing scheme to route the calls to a ported number. A trusted 3rd party, which typically reports to the telecom regulatory authority, can maintain the centralized number porting database.

5.2 Future of Mobile Number Portability

The future seems to be bright for this technology in India. The reason for being so is that currently, according to the government statistics, about 68% of all mobile customers change their mobile phone number at least once in a year. When Mobile Number Portability in India is complete, the number will drop significantly and only those people will change the numbers who really want to disconnect the mobile service or want to become anonymous again. There are many people who have been waiting for Mobile Number Portability in India to become existent. Now, they will be able to choose the best plan and the operator without having to change the number. Since the number of such people is quite large, Indian government is expecting that Mobile Number Portability in India will receive a warm welcome from the users, when it arrives.

CHAPTER-VI

REFERENCES

6.1 Websites

http://en.wikipedia.org/wiki/Mobile_number_portability

http://www.enotes.com/topic/Mobile_number_portability