Showing posts with label TRAI. Show all posts
Showing posts with label TRAI. Show all posts

TRAI TELECOMMUNICATION TARIFF (FIFTY SIXTH AMENDMENT) ORDER, 2013

1
TO BE PUBLISHED IN THE GAZETTE OF INDIA
EXTRAORDINARY PART III SECTION 4
TELECOM REGULATORY AUTHORITY OF INDIA
THE TELECOMMUNICATION TARIFF (FIFTY SIXTH AMENDMENT) ORDER, 2013
No. 5 of 2013
NOTIFICATION
New Delhi, the 26th November, 2013
No. 301-26/2012-ER — In exercise of the powers conferred upon it under subsection
(2) of section 11, read with sub-clause (i) of clause (b) of sub-section (1) of
the said section, of the Telecom Regulatory Authority of India Act, 1997 (24 of
1997), the Telecom Regulatory Authority of India hereby makes the following Order
further to amend the Telecommunication Tariff Order, 1999, namely:
1. (1) This Order may be called the Telecommunication Tariff (Fifty Sixth
Amendment) Order, 2013.
(2) This Order shall come into force on the 1st day of January, 2014.
2. In clause 2 of the Telecommunication Tariff Order, 1999 (hereinafter referred to
as the principal tariff order), after sub-clause (r), the following sub-clauses shall be
inserted, namely: ---
“ra. “USSD” or “Unstructured Supplementary Service Data” means a
real-time or instant session-based messaging service;
rb. “USSD-based mobile banking services” means delivery of
banking services through mobile phones over USSD;
rc. “USSD session for USSD-based mobile banking services” means
a session over USSD between the mobile subscriber and the bank or its
agent;”
2
3. In the Schedule II to the principal tariff order, the item (8) shall be numbered
as item (9);
4. In the Schedule II to the principal tariff order, after item (7A), the following
items and entries relating thereto shall be inserted, namely:
ITEM TARIFF
“(8) Use of USSD for USSD-based mobile banking
services
(8.a) Charge for outgoing USSD session for USSDbased
mobile banking services
Ceiling of Rs. 1.50 per
USSD Session
(8.b) Other matters related to USSD-based mobile
banking services
Forbearance.”
(Manish Sinha)
Advisor (F&EA)
N
Explanatory Memorandum
A- Introduction and Background
1. The purpose of the present amendment to the TTO is to design a mechanism
and determine the terms and conditions under which mobile banking for
financial inclusion can be facilitated. The amendment prescribes a ceiling tariff
for conducting a banking transaction through a mobile phone over USSD. This
explanatory memorandum aims to provide the rationale for this regulatory
action.
2. Availability of banking services to the entire population of the country without
any discrimination is a major objective of public policy. Banking services are in
the nature of a public good. Financial inclusion based on the principle of
equity and inclusive growth has been engaging the attention of policy makers
around the world. The United Na tions broadly describes the main goals of
financial inclusion as access to services such as savings, credit, insurance,
remittance and other banking/ payment services to all ‘bankable’ persons at a
reasonable cost.
3. However, a large section of the population in India has no access to banking
services today. The barriers to financial inclusion in India include (a) the poor
accessibility of banking services, mainly due to the reluctance on the part of
the banks to invest in infrastructure and human resources in remote areas;
and, (b) when accessible, the high costs incurred by households to access
such services. There is an increasing realization that a sustainable solution to
the problem could lie in technology-driven service delivery models. The
mobile phone is evolving into another transaction mode for customers with
bank accounts. The ease of use of a mobile phone could potentially draw the
unbanked into opening bank accounts and undertaking banking transactions.
On 30.09.2013, there were about 87 crore mobile subscribers in the country
of which about 35 crore were in the rural areas. The fact that a large number
of mobile subscribers in rural areas do not have access to banking facilities
6
presents an opportunity for leveraging the mobile telephone to achieve the
goal of financial inclusion.
4. Technology adoption in India is proceeding apace. A large scale digitization of
India is becoming visible. While there are about 87 crore mobile subscribers in
the country, the number of subscribers who access Internet by wireless
phones has grown to about 14.3 crore. With crores of people transacting
faster, quicker and better, there is likely to be productivity improvement and
GDP growth. With growth in household incomes, the demand for monetary
and banking transactions is also likely to rise. The Government-to-citizen cash
payments such as direct benefits transfers are also bringing in the unbanked
population into the banking system. With bank accounts becoming universal
and planned 80 crore Aadhar cards easing the Know Your Customer (KYC)
norms, there is going to be an increase in the demand for banking services in
the next few years. Even if the banks were prepared to invest heavily into
building physical branches, it may be difficult to serve the requirements of the
large and widely dispersed rural population. With a significant penetration of
mobile telephony in rural India, the mobile phone has the potential to help
provide basic banking and payment services to citizens on a model that
supplements the conventional banking system.
5. With a view to leverage the strengths of mobile telephony for financial
inclusion, the Government of India constituted an Inter-Ministerial Group
(IMG) to submit a report on the framework for delivery of basic financial
services using mobile phones. The framework proposed in the IMG report has
been accepted as the basis for delivery of basic financial services using mobile
technology by a Committee of Secretaries under the chairmanship of Cabinet
Secretary in April 2010. The IMG framework envisages the opening of mobile
linked ‘no-frills’ accounts, which would be operated using mobile phones. The
customer would be able to perform five basic transactions - cash deposit,
cash withdrawal, balance enquiry, transfer of money from one mobile-linked
account to another, and transfer of money to a mobile-linked account from a
regular bank account.
7
6. The IMG framework also proposes compensation to the key players after
taking into account the actual costs incurred by them. One of the
recommendations of the IMG is that the telecom service providers (TSPs)
should provide prioritized secure communication for mobile banking and they
should charge not more than Re. 1 per transaction from their subscribers viz.
mobile linked ‘no-frills’ account holders/ Business Correspondents. TRAI has,
however, been requested to devise a mechanism to support the operation of
market forces for ensuring that telecom services of adequate quality are
provided for mobile banking services at reasonable charges.
7. In countries where the financial services infrastructure is not sufficient to
provide access to a large population, the mobile system can be an effective
replacement mechanism to access the bank. The ecosystem in mobile banking
thus comprises two distinct sectors i.e. the financial services sector and the
telecom sector. The two sectors are governed by two separate sets of
regulations.
8. To make financial services available for the unbanked population, USSD-based
mobile channels can be effectively deployed. USSD based mobile banking
services have already been launched by some banks in the country viz. State
Bank of India, Canara Bank and ICICI Bank in partnership with some TSPs.
However, the extent and scope of the USSD-based mobile banking services
offered by these banks are limited on the following counts:
(i) These services are, at present, not available to the subscribers of all
TSPs.
(ii) These services are limited to the provision of value added banking
services to the banks’ existing customers and are not designed to meet
the objective of providing banking services to the unbanked/ underbanked
population i.e. financial inclusion.
9. On the other hand, the IMG framework envisages mobile banking services to
cater to the banking needs of the masses in general and the unbanked/
8
under-banked population, in particular. This would require creation of an
enabling environment where subscribers of all TSPs and customers of all
banks would be able to avail of mobile banking services as per their
requirement and at affordable prices. The business framework required for
this purpose would have to transcend the simple model of one-on-one
partnerships between banks and TSPs in areas of mutually perceived
pecuniary advantage.
10. As a follow-up to the IMG report, the Department of Telecom (DOT) , through
their letter no. 20-1/2011-AS-III/43/7/6 dated 09.12.2011, allocated the
USSD code *99# to the Department of Financial Services for mobile banking
services through the gateway of the National Payments Corporation of India
(NPCI). TSPs were directed to connect to the gateway of the NPCI as per
requirement of service and in consultation with NPCI. A copy of the letter is
placed as Annexure. Perceiving that a certain extent of hand-holding would
be required for the project to take-off, TRAI made concerted efforts to bring
the banks and TSPs into a technical and commercial partnership model by
evolving a mutually acceptable consensus regarding the terms and conditions
of such a partnership. TRAI’s efforts in this direction stretched over a period
of 10 months. However, this attempt did not lead to the desired result, for
two reasons. Firstly, the banks were not able to clearly articulate the business
case embodied in the proposed venture. Secondly, it is also true that the TSPs
view the IMG model as being in competition with their own efforts to diversify
into the mobile money space. The lack of cash-out facility in the mobile
money solutions has remained a sore point with the TSPs. Since the
collaborative effort, focused as it was on business-to-business relationships,
did not take off, the Authority decided to go in for a fresh round of
consultations for enabling mobile subscribers to have an option to access
financial services through the technology of their choice at an affordable
price.
9
11. With a view to devising a framework for use of USSD for delivery of basic
financial services through the mobile phone, a Consultation Paper (CP) on
‘USSD-based Mobile Banking for Financial Inclusion’ was issued on
20.09.2013. Stakeholders were invited to submit written comments by
04.10.2013 and counter-comments by 11.10.2013. The comments and the
counter-comments received from the stakeholders were placed on TRAI’s
website– www.trai.gov.in. The issues raised in the CP and the views of the
stakeholders thereupon are being examined in the succeeding paragraphs.
B- Analysis of the Key Issues Raised in the Consultation Paper
12. A summary description for each issue together with the comments of
stakeholders and further analysis thereon is presented below:
(1) Suitability of USSD for mobile banking for financial inclusion
13. A majority of TSPs and their industry associations have not favoured USSD as
the most appropriate mode for mobile banking service for financial inclusion.
The primary concerns of these stakeholders are based on the following
premises:
(i) USSD is not a main-stream commercial service.
(ii) USSD menus are currently available only in English.
(iii) USSD is not supported by CDMA.
14. These stakeholders have argued that USSD has primarily been deployed in a
limited way in telecom networks for delivering various value added services
(VAS) which do not need to follow the stringent and rigorous specifications for
a financial transaction such as audit trail of transaction, storage of transaction
data, interface with multiple third-party applications, and stringent quality-ofservice
(QoS) parameters; in order to make USSD as a main-stream
technology for mobile banking services, significant investment in billing
systems, transaction data storage, retrieval systems, dedicated USSD platform
and the radio access network (RAN) would be required. Further, they have
10
contended that the fact that USSD menus are currently available only in the
English language would act as an adoption barrier for financially excluded
customers. They have also pointed out that a significant portion of mobile
users would not be able to use USSD-based mobile banking services since
CDMA does not currently support USSD. Owing to these issues, such
stakeholders have favoured Interactive Voice Response (IVR) and SMS in
place of USSD for mobile banking services for financial inclusion.
15. On the other hand, some TSPs and a majority of consumer advocacy groups,
organizations and individual stakeholders have favored USSD as the most
appropriate mode for mobile banking service for financial inclusion. These
stakeholders have cited the following features of USSD in support of their
view:
(i) Ubiquitous (Available across mobile handsets): A significant proportion
of mobile phone users are still using ultra-low-cost-handsets (ULCH).
USSD is available on nearly all GSM mobile handsets.
(ii) Inexpensive: USSD uses an inexpensive resource (signaling channel) of
the TSPs.
(iii) Secure: USSD is the most reliable channel for making financial
transactions because there is no potential risk of misuse of mPIN.
(iv) Convenient: USSD offers better user experience as it is menu-based
and provides a continuous session for the transaction(s).
(v) It also supports vernacular/ regional languages.
16. In view of the fact that USSD has all the essential features required in a
communication channel for mobile banking services for financial inclusion viz.
it is ubiquitous, inexpensive, secure and convenient, the Authority is of the
view that USSD is an appropriate channel for mobile banking service for
financial inclusion.
17. The successful use of USSD for mobile banking transactions is likely to open a
significant revenue stream for TSPs. They are already deploying USSD-based
11
services in their networks. Some of them are also using it to provide mobile
banking services in partnership with banks. In existing USSD-based mobile
banking models, one or more entities interface between the banks and the
TSPs in channeling and processing transactions. On the TSPs’ side, the
requirement is for compiling the USSD messages and interfacing with the
banks. On the banks’ side, the requirement is for compiling transactions and
interfacing with the TSPs. The entities which perform these functions for the
TSPs and banks are generally referred to as aggregators. The TSPs and banks
can have a common, single aggregator, or separate aggregators. For the sake
of clarity, in this explanatory memorandum, the TSPs’ aggregator is referred
to as the gateway operator. The gateway provider provides equipment and
services to TSPs who do not own the necessary infrastructure i.e. the USSD
gateway and the capability to generate Call Data Records (CDRs) for USSD
transactions. (The banks’ aggregator has already been termed as the USSD
aggregation platform provider in the CP dated 20.09.2013).
18. Some TSPs have contended that the use of USSD for mobile banking
transactions would necessitate huge investments. However, the Authority
observes that a large amount of capital expenditure can be avoided by
employing the services of gateway operators who, inter-alia, can provide
capability for billing USSD messages to the TSPs. The records that are created
for billing will also help to satisfy the information needs of the customers.
Besides, some TSPs are already making use of SMS-MT (Short Message
service-Mobile Terminating) upon completion of USSD session for billing their
subscribers.
19. To sum up, no excessively large capital expenditure is involved in extending
the use of USSD-based channels for mobile banking services. It can be done
economically, as has been demonstrated. Further, in most models where
gateway operators are working for TSPs, the same gateway operator provides
the required CAPEX for enhancing capabilities.
12
20. As regards the contention that a significant proportion of mobile users would
not be able to use USSD based mobile banking service because USSD is not
supported by CDMA systems, it is pertinent to point out that of the total
wireless subscriber base of about 87 crore as on 30.09.2013, about 80.7 crore
(92.77%) of the subscribers are GSM subscribers, and only about 6.3 crore
(7.23%) are CDMA subscribers. The objective of financial inclusion is to cover
a wide base of telephone users with mobile banking services. The Authority is
of the view that this objective will be largely achieved if such a large
percentage of wireless subscribers are enabled to use the USSD-based mobile
banking service. Additionally, the possibility of work-around methods to cover
CDMA subscribers can also be explored by banks and TSPs.
21. It is clarified that while considering USSD as an appropriate channel for
mobile banking service for financial inclusion, the Authority, by no means,
intends to exclude IVR and SMS-based mobile banking services. The use of
USSD is only to supplement the already present IVR, SMS and mobile Appsbased
offerings with a specific focus to cater to the needs of financially
excluded citizens of the country.
(2) Should the access service providers collect charges from their
subscribers for the use of USSD for mobile banking services?
22. A core issue is whether the customers should pay for the use of USSD for
mobile banking services - the business-to-customer (B2C) pricing model orshould
banks/ banks’ agents pay for the use of USSD for mobile banking
services- the business-to-business (B2B) pricing model.
23. A majority of TSPs, their industry associations, a few organizations, and a
consumer advocacy group have not favored the B2C pricing model for the use
of the USSD channel for mobile banking services. The primary concerns of
these stakeholders are based on the following premises:
13
(i) Implementation of B2C pricing model for USSD-based mobile banking
service would require a new billing system for which a huge investment
would be needed. Without an assured USSD transaction volume, there
can be no business case for investing in additional capacity.
(ii) In case charges are recovered by TSPs from their customers (B2C
pricing model), they would be more inclined to contact the call centers
of the TSPs instead of calling to banks. This would put an unnecessary
burden on the call centre infrastructure of the TSPs.
(iii) Since the users are customers of the banks, the banks should recover
charges from them directly or absorb the cost. However, the banks
must compensate the TSPs for their cost in both the scenarios.
24. On the other hand, a few TSPs and a majority of consumer advocacy groups,
organizations and individuals have favoured the B2C pricing model for the use
of the USSD channel for mobile banking services. These stakeholders have
cited the following reasons in support of their view:
(i) It is natural to expect the user of a service to pay to the providers of
the service. In the present case, the TSPs are providing the service of
‘air-time’ through the USSD channel to their customers.
(ii) The USSD channel is just like any other channel of communication viz.
voice, SMS and data. For USSD transactions, the TSPs should collect
charges from subscribers as they do in the case of SMS-based, Mobile
App-based and Internet banking.
(iii) As the customer is benefited both in terms of cost and convenience by
using the USSD-based mobile banking service, he would be willing to
pay a reasonable amount for the use of USSD. The customer reduces
the risk of carrying cash and the service is available everywhere
irrespective of the location of the Bank/ATM. A charge on the customer
would encourage proper use and avoid misuse of the service.
25. From the stakeholders’ comments, it is evident that a majority of the TSPs
prefer a B2B pricing model. One of their apprehensions about the B2C pricing
14
model is that it may require a significant investment on a new billing system
to support USSD transactions, which will not yield sufficient returns on
investment (ROI). However, the present ecosystem provides a ready
alternative solution. Many TSPs have already outsourced the USSD gateway
service to gateway operators. The gateway operators can, in addition, help to
build a billing and audit trail system to satisfy the customers and fulfill the
regulatory requirement. The model of business that is currently in use
incorporates a revenue share to the gateway operator that replaces the
requirement of making fresh investments. The payment in exchange for the
services provided by the gateway operator for the USSD channel ranges
between 5-15% of the charges levied by the TSPs on their subscribers. The
spread of the cost per transaction is very small and can easily be built into the
end-user tariff.
26. In addition, the mobile banking service would add value to existing services
and providing a new revenue stream, thereby increasing the average revenue
per user.
27. The concern of TSPs that, in the event of adopting the B2C pricing model,
they would be unnecessarily inundated with customer complaints of failed
banking transactions at their call centers appears to be a misapprehension.
The TSP is providing a communication channel to the mobile customer, not
the banking service per se, which is provided by the bank. This situation
applies equally to mobile banking through SMS, IVR or the Internet, which are
also used as modes for mobile banking. As such, customers are fully aware
that they are making transactions out of their own accounts in the bank, for
which the TSP cannot be held responsible.
28. The argument of TSPs that the banks should recover charges from citizens for
the use of USSD because the citizens are customers of banks, does not
appear to be reasonable. The mobile banking sector involves players from the
financial services sector on the one hand and the telecom sector on the other.
15
Their respective roles in the process of delivering USSD-based mobile banking
services are as follows:
(i) Banks facilitate their customers with banking over mobile. Thus mobile
banking acts as another outlet of the banks.
(ii) TSPs provide their subscribers with a delivery channel (USSD) to
execute banking transactions. Thus the USSD channel acts as a vehicle
to help the customer reach the mobile banking outlet of the banks.
29. The Authority is of the view that the B2C model is logical. It is only
appropriate that the TSPs receive adequate recompense from the customer
for the facility of the USSD communication channel that they provide to help
the customer (subscriber) access mobile banking services.
30. It is further observed that the B2C model has been successfully implemented
in some of the existing mobile banking projects such as the partnerships
between ICICI Bank and six TSPs, and that between SBI and five TSPs. A
significantly strong argument in support of this model is that it is already
working in the functioning systems.
31. Although the TSPs have argued strongly for a B2B model, it is a fact that the
banks and TSPs have failed to reach agreement on terms and conditions of
partnership, in spite of intensive parleys over the past year. In the
meanwhile, the project of mobile banking for financial inclusion has been the
casualty. The Authority is of the view that this situation cannot be allowed to
continue indefinitely. As stated earlier, the present TTO is meant to fix the
terms and conditions under which mobile banking for financial inclusion can
be facilitated.
16
(3) Appropriateness of Rs. 1.50 per USSD session for mobile
banking as a ceiling tariff
32. On the subject of the appropriate ceiling tariff for mobile banking service,
significantly divergent views have been expressed by the stakeholders viz.
(i) Tariff per USSD session for mobile banking should remain under
forbearance.
(ii) A ceiling tariff of Rs. 1.50 per USSD session for mobile banking would
be appropriate.
(iii) A tariff significantly higher than Rs. 1.50 per USSD session for mobile
banking should be allowed.
(iv) The ceiling tariff should be much lower than Rs. 1.50 per USSD
session.
(v) Subscription based pricing model instead of pay-per-use pricing model
should be adopted.
33. Some TSPs and the industry associations have favoured the policy of
forbearance in the tariff for the USSD session for mobile banking services.
They have stated that mobile banking is at a very nascent stage of growth as
the eco-system is still developing and, therefore, it would be premature to fix
a ceiling tariff per USSD session at this stage.
34. On the other hand, many stakeholders have supported prescription of a
ceiling tariff for the use of USSD for mobile banking services in view of the
following:
(i) A ceiling tariff is necessary for customer protection and to encourage
innovation to enable scale and volume of transactions on the USSD
channel.
(ii) From the experience of usage of short codes in SMS-based banking, it
seems necessary to prescribe a ceiling tariff for USSD-based mobile
banking service. Since the TSPs charge Rs. 3 per SMS, the usage has
not picked up in the lower end of the customer segment.
17
35. A few stakeholders have considered Rs. 1.50 per USSD session for mobile
banking as an appropriate ceiling tariff in order to ensure that the TSPs do
not charge an exorbitant or unreasonably high tariff per USSD session. They
have also stated that voice and SMS services also operate near this price
point.
36. A few access service providers have argued that they should be allowed to
charge higher than Rs. 1.50 per USSD session (e.g. Rs. 3 or Rs. 5.50) in view
of the following:
(i) Huge investment in the billing system and to meet the strict guidelines
for quality of service for mobile banking;
(ii) USSD session for mobile banking service involves multiple hits which
would engage the signaling channel and core network for a long time.
37. On the other hand, a majority of consumer advocacy groups, organizations
and individuals have contended that the TSP should charge much lower tariff
per USSD session. Some of the comments offered by these stakeholders are
as below:
(i) The price per USSD session should be at par with GPRS service i.e. Re.
0.20 to Re. 0.30 per USSD session.
(ii) The customers should be able to pay as low as Re. 0.50 per USSD
session with no additional charges.
(iii) The ceiling should begin with Re. 1 per USSD session.
These stakeholders have opined that the real growth of the service will come
out of ‘large volume of transactions and small value charges’ rather than from
‘high value charges and small volumes of transactions’.
38. One TSP has stated that a subscription-based pricing model instead of payper-
use pricing model should be adopted for pricing the use of USSD for
mobile banking services so that the TSPs do not require any investment in
their network.
18
39. Though there are divergent views on the issue, most of the stakeholders
consider tariff of USSD session for mobile banking service an important
determinant of the success of USSD-based mobile banking service. Besides, it
is clear, from the comments of the stakeholders, that the principle that the
person seeking the service must pay for the service, is widely acceptable.
40. As the use of USSD for mobile banking service is not a main offering of the
TSPs, the pricing of these services is not likely to be subjected to the same
competitive pressure which the main offerings of the TSPs (viz. voice call and
SMS) have to face in the marketplace. Besides, the use of USSD for mobile
banking for financial inclusion carries definite socio-economic benefits to the
target group i.e. unbanked/ under-banked population and, therefore, the
price for the use of USSD for mobile banking needs to be reasonable and
affordable. In the USSD-based mobile banking solutions already deployed in
the country, subscribers are charged a pay-per-use charge in the range of Rs.
1 to 1.50 per USSD session regardless of the duration of the session.
41. It is noteworthy that while voice calls travel over traffic channels, USSD
messages and SMS messages travels over inexpensive signaling channels.
The prevalent tariff of outgoing SMS in the tariff plans offered by the TSPs is
generally Re. 1 per local SMS and Rs. 1.50 per national SMS.
42. In the light of the above, the Authority is of the view that a ceiling tariff of Rs.
1.50 per USSD session would be reasonable to compensate the TSPs to meet
the expenses incurred in the use of USSD for mobile banking service and also
it would be affordable to the subscribers. Ordinarily, a USSD session shall
comprise one banking transaction e.g. balance enquiry, transfer of money
(Fund transfer) etc. However, the TSPs and banks/ banks’ agents may agree
to accommodate more transactions in a USSD session. A pay-per-use charge
within the ceiling tariff of Rs. 1.50 per USSD session would be payable by the
subscriber upon establishment of an outgoing USSD session, regardless of
whether the session results in a successful or a failed banking transaction.
19
Annexure
20
List of Acronyms
Sl. No. Acronym Expansion
1 ATM Automated Teller Machine
2 B2B Business-to-Business
3 B2C Business-to-Customer
7 CAPEX Capital Expenditure
4 CDMA Code Division Multiple Access
5 CDR Call Data Record
6 CP Consultation Paper
8 DoT Department of Telecommunications
9 GDP Gross Domestic Product
10 GPRS General Packet Radio Service
11 IMG Inter Ministerial Group
12 IVR Interactive Voice Response
13 KYC Know Your Customers
14 m-PIN Mobile Personal Identification Number
15 NPCI National Payment Corporation of India
16 QoS Quality of Service
17 RAN Radio Access Network
18 ROI Return on Investment
19 SMS Short Message Service
20 SMS-MT Short Message Service - Mobile Terminating
22 TRAI Telecom Regulatory Authority of India
23 TSP Telecom Service Provider
21 TTO Telecommunications Tariff Order
24 ULCH Ultra-Low-Cost-Handsets
25 USSD Unstructured Supplementary Service Data
26 VAS Value Added Services

Full Mobile Number Portability TRAI

Chapter II: Full Mobile Number Portability
2.1 Presently mobile subscribers are availing the facility of MNP for
porting their mobile number within the same LSA. For example, if a
subscriber belongs to Andhra Pradesh LSA, he can port his mobile
number to any TSP of his choice within Andhra Pradesh LSA only.
Accordingly, in the present framework, MNP porting request is
processed amongst Recipient Operator, Donor Operator and the
MNPSP of the same LSA. Whenever a subscriber changes his LSA,
he needs to acquire a new mobile number of that LSA, otherwise he
will be under roaming, inviting higher call charges than a normal
subscriber.
2.2 The facility of pan-India portability will allow a subscriber to change
his LSA without change of mobile number. This means that a
subscriber of Andhra Pradesh LSA can port his number to any LSA
say Karnataka, Maharashtra, Haryana etc. Implementation of Full
Mobile Number Portability would therefore mean acceptance of a
porting request by the Recipient Operator from a mobile number
belonging to any of the LSAs of the country, irrespective of the fact
that the LSA from where the subscriber is porting his mobile
number and the LSA to which he wants to port his number belong
to the same or different MNP zones.
2.3 There will be regulatory and technical challenges in facilitating such
porting across LSAs. Some of the major challenges which need to
be deliberated are –
(i) how the request of the subscriber for porting will be
processed by the Donor Operator, Recipient Operator and
MNPSPs,
(ii) what changes are required in Number Portability Gateway
(NPG) of the operator and operator’s IT systems etc.; and 5
(iii) how much time will be required to complete the
modifications in the existing systems of the operators.
These challenges are discussed in the succeeding paras.
2.4 In the present framework on receipt of porting request, the
Recipient Operator forwards the same to the MNPSP of its MNP
zone. However, in full MNP scenario, the recipient operator will have
the following options which were described in the pre-consultation
paper dated 20th February, 2013.
Approach-1 : Recipient Operator forwards the porting request
to the MNPSP of its zone.
Approach-2 : Recipient Operator forwards the porting request
to the MNPSP of the other zone to which the Donor Operator
belongs.
Approach-3 : Recipient Operator forwards the porting request
to the MNPSP of the zone to which original number range holder
(the TSP to which the number originally belonged before its first
porting) belongs.
2.5 Stakeholders’ comments were sought on the most suitable approach
for implementation of Full MNP. The stakeholders were divided in
their opinion. While the TSPs supported Approach-1, the MNPSPs
supported Approach-3. None of the stakeholders supported
Approach-2. As there were differences in opinion between TSPs and
MNPSPs, meetings were held with the industry representatives viz.
COAI, AUSPI and MNPSPs. During the discussions, it emerged that
another approach, hereinafter called ‘modified Approach-1’, which
is a combination of Approach-1 and Approach-3, should also be
considered. These three possible approaches are discussed below:6
A. Approach 1: Recipient Operator forwards the porting request
to the MNPSP of its zone
2.6 In this approach, the Recipient Operator submits the porting
request to the MNPSP of its MNP zone. For example, if a subscriber
of Karnataka LSA wants to port his number from Karnataka to
Delhi LSA, he will submit his porting request to the Recipient
Operator of Delhi LSA, who in turn will forward the porting request
to MNPSP of MNP Zone-1. (which serves Delhi LSA) for porting.
2.7 On receipt of the porting request, the MNPSP of MNP Zone-1 will
verify the porting history of the mobile number by querying with the
MNPSP of MNP Zone-II(which serves Karnataka LSA). The query is
primarily to check whether the porting request meets the following
conditions:
(a) Completion of 90 days in its current operator’s network;
(b) No simultaneous porting is under process for the said
mobile number, in the other MNP zone.
If the porting request meets the above two conditions, the MNPSP of
MNP Zone-I will seek clearance from the Donor Operator of Karnataka
LSA. Further processing of porting request will take place as per the
existing porting process.
2.8 From the TSP’s perspective, this approach requires minimal
changes in the TSP’s Number Portability Gateway (NPG) as the
Recipient Operator continues to forward the porting requests from
the subscribers desirous of porting out their numbers to the MNPSP
of its zone. However, this approach has the following implications:
i. It will add complexity to the MNPSPs’ system as it requires
connectivity between the two MNPSPs.
ii. It will require synchronization of the database of the two
MNPSPs for ported numbers, porting history, database tables
etc. During discussions, MNPSPs stated that since they used
proprietary software, synchronization between the two MNP
systems has never been done earlier and would require 7
extensive development efforts and such a design will be
susceptible to errors in a live scenario.
iii. The MNPSPs also stated that new software development work
would be required for:
(a) developing mutually agreed interface specification by both
MNPSPs for requesting and obtaining the required data;
(b) modification to the current process, including new
messages, timers, error codes and reports;
(c) changes in the database design to maintain the data
received from other MNPSP;
iv. Real time port-in-progress validation and sharing of broadcast
information between the MNPSPs will increases dependency
between the two MNP Clearing House (MCH) systems. This will
increase system complexity, storage needs and will affect the
system performance (in terms of time and processing).
v. Testing in the above approach would be time and resource
consuming and also very costly.
B. Modified Approach 1: Recipient Operator forwards the porting
request to the MNPSP of its zone and the Donor Operator is
responsible to check the condition of 90 days and simultaneous
port requests
2.9 In the modified version of Approach-1, the need for connectivity
between the two MNPSPs has been eliminated. In this approach, the
Donor Operator will be responsible for verifying whether the
subscriber fulfils the eligibility condition of 90 days in the existing
network and also if the subscriber has made any simultaneous
porting request for the same mobile number. As such the
responsibility to check the above mentioned two conditions by
querying with the MNPSP of the other zone (Approach 1) will move
to the Donor Operator. The Donor Operator will be required to build
this check in their Number Portability Gateway (NPG). This will
require software changes in all the TSP’s NPG. However, the
advantage of this method is that there will be comparatively fewer8
changes requirement in the MNPSP’s systems due to the elimination
of connectivity between the two MCHs.
C. Approach 3: Recipient Operator forwards the porting request to
the MNPSP of the zone to which number range holder of the
number belongs.
2.10 In this approach, the Recipient Operator submits the porting
request to the MNPSP in whose zone the Number Range network
belongs. As all TSPs already have connectivity with both the
MNPSPs they will not have to make any changes in communicating
with the MNPSP of the other zone. This approach also does not
require interaction between the two MNPSPs. Therefore, this
method eliminates the need for connectivity /synchronization
between the two MNPSPs. However, in this approach, intelligence
needs to be built-into the operator’s NPG so as to forward the
porting request to the concerned MNPSP based on the identity of
the number range holder network.
2.11 In this approach the control on porting the mobile number will
continue to be with one of the MCHs. Even after a subscriber moves
to other MNP zone, all his subsequent porting requests (whether for
intra-Circle porting or Inter-Circle porting) will continue to be
processed by the MNPSP where his number originally belong. For
example, if a subscriber port his number from Delhi (which is in
MNP Zone-I) to Bengaluru (which is in MNP Zone-II), he will
approach the Recipient Operator of Karnataka LSA for processing
his porting request. The Recipient Operator will process the porting
request through MNPSP of Zone-I. Subsequently, if the subscriber
ports his number within the Karnataka LSA then also, the Recipient
Operator to whom the subscriber approaches in Karnataka LSA will
process the porting request through MNPSP of Zone-I only.9
2.12 All three approaches described above have their pros and cons.
Therefore, before deciding the approach to be implemented for full
MNP, the Authority decided to form a Focus Group consisting of
representatives from MNPSPs and TSPs to give their views on :
a. the preferred approach for implementation of full MNP;
b. changes required in the existing MNP system;
c. cost and time involved in various methods;
d. any other optimal feasible solution for implementation of
full MNP.
2.13 The deliberations of the Focus Group was coordinated and
facilitated by TRAI. After deliberating on all the possible
approaches, the Focus Group has unanimously recommended
Approach-3 for implementation of Full MNP in the country. (Report
at Annexure-II)
2.14 According to the Focus Group, cost requirement in Approach-3 will
be the least for both the MNPSPs. For TSPs, there will not be a
significant difference in the cost to be incurred in any of the three
approaches.
2.15 The Focus Group was also of the view that, irrespective of the
method adopted, TSPs will be required to upgrade their existing
backend systems such as CRM, mediation platforms, provisioning
systems / activation systems, billing systems, number
managements systems, recharging platforms, VAS management
systems etc, to support complete numbering plan and enable interLSA porting. Similarly, MNPSPs will also need to upgrade their MCH
to support complete numbering plan and enable inter-LSA porting
apart from enhancing billing system, Graphical User Interface (GUI)
etc.
2.16 The pros and cons deliberated by the Focus Group have been
examined by the Authority. The Authority agrees with the Focus
Group’s observation that the variation in the costs to be incurred in the three approaches will not be significant for the TSPs, whereas a
significant expenditure will be required for MNPSPs if Approach-1 is
adopted for implementation of full MNP. Further, the
implementation time for Approach-3 will be much less as compared
to Approach-1 or modified Approach-1. In addition,
2.17 Therefore, in the opinion of the Authority, Approach-3 will be the
most suitable approach for implementation of full MNP. Though the
Focus Group has not clearly mentioned the time frame for
implementation of the solution, the Authority is of the opinion that
6 months will be sufficient for operators to carry out the required
changes in their existing systems, complete inter-operator testing
and implement the solution.
2.18 Accordingly, the Authority recommends that Approach-3, as
described in para 2.10, should be adopted for implementation
of Full Mobile Number Portability. The TSPs may be given 6
months time to implement full MNP in the country.
Changes required in the MNP licence conditions:
2.19 For implementation of full Mobile Number Portability, following
licence conditions of MNP licence will require
modification/amendment:
(a). Scope of Licence:
In the scope of MNP license, the following condition will require
modification:
“12.5 The MCH and NPDB established by the licensee shall be
used by all telecommunication service providers (both existing &
new) (i.e. Basic, CMTS, UAS, NLD and ILD Licensee(s)) of the
licensed MNP zone for the purpose of supporting porting of mobile
numbers between mobile operators.”11
If full MNP is implemented with Approach-3, TSPs will have to
use the services of both the MNPSPs for processing the porting
request. Therefore, the restriction ‘the licensed MNP zone” in
clause 12.5 needs to be removed.
(b). Delivery of service:
The ‘Delivery of Service’ condition in clause 18.1 of the MNPSP
licence would require amendment -
“18.1 MNP is to be implemented in each intra Licensed Service
Area (LSA)……….”
In order to provide inter service area MNP service, the word
‘each intra’ may be modified to read as ‘inter and intra’
(c). Changes required in the DoT instructions dated 06th May
2009
DoT instructions dated 6th May 2009 regarding provisioning of
MNP will also require modification. Para 3(i) of the said
instructions is given below:
“ ….MNP is to be implemented in each intra license Service Area
(LSA) as per the schedule notified by the Licensor from time to
time…….”
The word ‘each intra’ in the para may be modified to read as
‘inter and intra’.
2.20 In view of the above, the Authority recommends that the DoT
should carry out the necessary changes as mentioned in the
above paras in the:
(i) existing MNP license; and
(ii) instructions of the DoT dated 6th May 2009, for
implementation of Full MNP.12
Upon acceptance of these recommendations, the Authority will carry
out necessary changes in the MNP regulations
Identification of inter-service area (STD) calls after implementation
of Full MNP
2.21 Presently, a calling subscriber can store the mobile number of the
called subscriber in one of the following possible ways in the
contact list of his mobile phone handset:
(a) Storing directly the mobile number of the called subscriber ;
(b) Storing the mobile number with prefix ’0’ ;
(c) Storing the mobile number with prefix ‘+91’ ,
2.22 In the Full MNP scenario, if a called number happens to be a ported
number that has been ported to a different LSA, a subscriber calling
that mobile number in the case of (a) above, will not be successful
as the called number has been ported out of the LSA and the caller
has to prefix ‘0’ to this called number – being an inter-service area
call. Therefore, by default, the calling subscriber will get ‘number
does not exist’ announcement. In the case of (b) and (c) above,
when a subscriber makes a call, though the call will be successful,
it will attract applicable STD charges instead of local charges (before
porting). There is a possibility that the calling subscriber may not
be aware that the number has been ported out to another LSA.
This may result in a subscriber complaining of higher charges.
2.23 This issue was raised in the pre-consultation paper and inputs
were sought from stakeholders on the need to inform the calling
subscriber through announcement prior to connecting the call. In
response, some TSPs suggested that identification of inter-service
area ported numbers and playing an announcement thereof, will
burden their network resources and will increase call set up time.
It was suggested that the subscribers may be made aware
of/educated to dial numbers in the +91 format which is the
standard dialing format, after Full MNP is implemented.



2.24 On the issue of higher call charges and possible subscriber
complaints, most TSPs were of the view that STD rates have
plummeted to almost the same level as local call rates; hence, it is
not a major issue. Further, in most cases, the calling party may
already be aware that the called party has moved to another LSA.
Therefore, the onus should lie on the calling party to bear the STD
charges, if applicable. One of the suggestions was to have a website
so that a query for a given telephone number can be given which
will provide information about the current serving operator/LSA for
the called number. This facility can be developed by the MNPSPs.
The Authority agrees with the above comments of the TSP and is of
the opinion that no action is required on this issue
UPC generation in J & K LSA in Full MNP Scenario:
2.25 As per the existing MNP process, a subscriber is required to
generate a UPC before submitting a porting request to the Recipient
Operator. In the Full MNP scenario, the location of the Recipient
Operator being in a different LSA, the Donor Operator will have to
ensure generation of UPC for subscribers under roaming. During
the pre-consultation, TSPs informed that UPC can be
requested/generated from any LSA (except in Jammu & Kashmir
LSA where roaming of pre-paid subscribers is not permitted).
2.26 In the J&K LSA, post-paid subscribers can generate a UPC as in
any other part of the country. However, pre-paid subscribers of
J&K can generate a UPC only by making a call to ‘1900’ instead of
sending an SMS. Therefore, in a full MNP scenario, the issue of
generation of a UPC while in another LSA may arise for pre-paid
subscribers of J&K as such subscribers are not permitted roaming.
2.27 The solution to this problem is that the subscriber of J&K LSA who
wants to port his number to any other LSA can generate the UPC in
J&K LSA and then apply for porting to any desired LSA.
Alternatively, he can convert his subscription from pre-paid to 14
post-paid which will enable him to generate a UPC under roaming,
and then request porting in any LSA.
Testing Fees for Acceptance Testing
2.28 During the consultation process, the TSPs and MNPSPs have stated
that apart from network implementation costs, significant testing
costs would be incurred by them.
2.29 The TSPs have requested to waive the testing fee by the DoT for
acceptance tests to be conducted for implementation of Full MNP.
2.30 On 24th November 2011, the DoT specified the Acceptance Testing
fee to be charged for various types of networks as follows:-
S.
No.
Fee to be charged from
TSP/ ILDOs/ MNPOs
Unit Price (per network/ per LSA.
Per gate way, per site)
1 UASL /CMTS Service
Provider
Rs. 307228 (per network per LSA)
2 Basic/ WLL Service
Provider
Rs.189360 (per network per LSA)
3 International Long Distance
Operator (ILDO)
Rs.189360 (per Gateway)
4 MNPO Rs.279800 per site (Production/
Disaster)
Rs.60360 per network per LSA
(GSM/ CDMA)
2.31 Before the launch of MNP, DoT had already conducted acceptance
test through respective TERM cells of DoT for which testing fee had
already been charged as per the above said circular. Now, Full MNP
is being mandated pursuant to NTP-2012 and testing is to be
carried out for various scenarios due to a change in the process.
Therefore, the Authority recommends that the DOT may
consider the request of the operators and reduce the
Acceptance Testing Fee to 25% of the Current Fee.15



Chapter III: Summary of recommendations
3.1 The Authority recommends that Approach-3, described in the
relevant para (2.10), should be adopted for implementation of
Full Mobile Number Portability. The TSPs may be given 6
months time to implement full MNP in the country. ( ¶2.18)
3.2 The DoT may carry out the necessary changes in the:
(i) existing MNP license; and
(ii)instructions of the DoT dated 6th May 2009, for
implementation of Full MNP. (¶2.20)
3.3 The DoT may consider the request of the operators and reduce
Acceptance Testing Fee to 25% of the Current Fee. (¶2.31)
Related Posts Plugin for WordPress, Blogger...

Related Posts