Bridging the Connectivity Gap: Unraveling the Challenges and Solutions for PM-WANI

The Pradhan Mantri Wifi Access Network Interface (PM WANI) was launched in December 2020. It received a great initial reception, but the enthusiasm died over time. Several reasons have been cited, including a lack of a vibrant ecosystem, lack of profitability, limited business models, etc. In addition, a belief also crept up over time that India did not need PM-WANI as existing telcos would step in and provide universal connectivity in the country. At the same time, several stand-alone solutions have been provided from various quarters to jumpstart the ecosystem. 

iSPIRT has taken a long hard look at PM-WANI. It has identified the causes for the multiple issues plaguing the system and attempted to solve the problem holistically. This Open House Session presents our analysis of the issues in PM-WANI and a path forward. It argues for an integrative approach, considering all stakeholders’ concerns. We believe that PM-WANI can fulfil its mission of providing universal connectivity to a large unconnected part of our population.

Latest Open House

The blog post is co-authored by iSPIRT Volunteers, Prof. Nilesh Gupta, Saurabh Chakrabarti, Bhuvan Beejawat, Prof. Himanshu Tyagi, and Sharad Sharma.

P.S: Prof. Nilesh Gupta and Prof. Himanshu Tyagi are faculty members at the Indian Institute of Management Nagpur and Indian Institute of Science, respectively, and they also represent their views as independent researchers on the topic.

PM-WANI: Business models

India, a large country with a lot of geographical and economic diversity, faces interesting challenges with last-mile connectivity for internet users. PM-WANI programme provides a powerful technical and policy framework towards the goal of broadband proliferation across the country.

iSPIRT Foundation has been involved with the PM-WANI programme right from its inception. Dr Pramod Varma, Siddharth Shetty and other volunteers, were involved with the technical framework for unbundling the internet access and ensuring interoperability among all participants

As of date, the Centre for Development of Telematics (CDoT) and Telecom Regulatory Authority of India (TRAI) has been ably managing the mantle with all aspects related to the PM-WANI framework.

The PM-WANI has a unique, distributed and unbundled architecture. It has the following participants:

PDO – Set up and maintain the access point (AP). Users connect to this AP to access the internet.

PDOA – Provides the technical backend for the PDO for Authentication, Authorization and Accounting (AAA). PDOA provides a facility for the PDO operator to define broadband sachet for their users (e.g. 1GB data for Rs 5). PDOA also stores the users’ usage data as per the government security compliance.

App-Provider – Operates a mobile application for PM-WANI. A user will use this mobile application to discover a PM-WANI-compatible network. The App-Provider maintains the user KYC.

Central-Registry – It maintains the details of every registered PDO, PDOA and App-Provider. It is generally used to validate requests made between the participants. 

PM-WANI facilitates the delivery of broadband access to users using PDO-operated WiFi access points (AP). A telecom/internet service provider provides the backhaul internet to this AP.

Instead of needing multiple licences and compliances to commercially distribute internet, in PM-WANI’s case, the PDO requires absolutely no compliance or licence to distribute internet locally! 

That does not mean the security is compromised in any way. The user KYC is handled by the App-Provider and the usage logs are maintained by the PDOA

User Flow

PM-WANI as an earning opportunity for small entrepreneurs

This programme offers great monetary opportunities for entrepreneurs. Multiple companies are coming up with varied plans for becoming a PDO / PDOA. Let us discuss some of them 

Case 1: Become a PDOA with a C-DoT software stack and onboard PDOs

This is for entrepreneurs to start their own PDOA business and create a network of PDOs (on their own or onboarding other small-business owners) 

The Centre for Development of Telematics (C-DoT) provides a complete PDOA software stack as Platform as a Service(PaaS). Here, it takes care of all the technical requirements (including software, server and regulatory requirements). This enables entrepreneurs to start their PDOA operations without getting into the technical nitty-gritty. They charge a very low fee of Rs. 15000 for 3 months.

Costs

Here is the cost breakdown for a PDO for Year 1:

Annual Internet pricing – 50 Mbps connectionRs.600/month = Rs 7200/-
Annual Electricity & Router MaintenanceRs.150/month = Rs 1800/-
Indoor AP which is CDoT PM-WANI compliant (WAYU)Rs. 5300/-
Total Investment for year 1 for a PDORs. 14300/-

Cost breakdown for a PDO Year 2 onwards:

Annual Internet pricing – 50 Mbps connectionRs.600/month = Rs 7200/-
Annual Electricity & Router MaintenanceRs.150/month = Rs 1800/-
Indoor AP which is CDoT PM-WANI compliant (WAYU)Already Purchased
Total Investment from year 2 onwards for a PDORs. 9000/-

In this business case, we consider that 95% of the voucher collection goes to the PDO and 5% goes to the PDOA

The annual investment for the PDOA is Rs. 60000

Value Proposition for PDO

A PDOA can create an excellent value proposition for a PDO using this model.

We have considered the average voucher cost for a user to be Rs 2, Rs 5, Rs 10 and Rs 15., eg. a user will buy an internet sachet/voucher of Rs. 2 for 1GB data a day.

The below table shows the cost-benefit analysis for Year 1 wherein a PDO charges Rs 2 per voucher. Annually, PDO breaks even with just 20 daily users and achieves 100% return-on-investment (ROI) with just 40 daily users in the first year itself! Year 2 onwards it’s just 13 users to break even and 25 users for 100% ROI.

PDO Year 1

Daily Cost Per User(in Rs)No of daily users for breakevenNo of daily users for 100% ROI
22040
5816
1048
1536

PDO Year 2 onward

From year 2 onwards, the ROI starts getting even sweeter as the operating cost further reduces to Rs. 9000 for a year 

Daily Cost Per User(in Rs)No of daily users for breakevenNo of daily users for 100% ROI
21325
5510
1035
1524

Value Proposition for PDOA

The below graph shows the number of PDOs needed to be deployed for a PDOA to break even for different voucher costs and daily users

Case 2 – Become a PDO with other private players

There are quite a few companies that allow people to deploy their own PDO directly. They provide a PDO infrastructure (AP and allied software) for Rs 12000 a year

Costs

Here is the cost breakdown for a PDO:

Annual Internet pricing – 50 Mbps connectionRs.600/month = Rs 7200/-
Annual Electricity & Router MaintenanceRs.150/month = Rs 1800/-
AP which is PM-WANI compliantRs. 12000/-
Total Investment for year 1 for a PDORs. 21000/-

Value Proposition for PDO

Daily Cost Per User(in Rs)No of daily users for breakevenNo of daily users for 100% ROI
22958
51224
10612
1548

PM-WANI Challenges

Interoperability 

One of the major challenges that PM-WANI is facing right now is protocol compliance. Because of this, some of the PM-WANI Apps do not work interoperably with the PDO. 

Example: A PM-WANI app developed by company A is not compatible with a PDO of company B. A’s app only works with A’s PDO

Data Sharing 

The protocol, as of now, does not have a standard way to share usage data between the participants. Hence, the app provider does not get any incentive when a user buys a PDO/PDOA coupon due to this lack of data sharing. Also, for implementing roaming between PDOs, it is essential that there is some data-sharing standard available between multiple PDOAs.

Grievance Redressal

This is another area that is not regulated at the moment

What iSPIRT is up to

We are working on multiple fronts to solve the PM-WANI challenges. 

For the interoperability issue, we are developing a certification mechanism for PM-WANI that cthe PDOA or App-Providers can easily usewith minimal complexity.

We are developing a reference implementation for PM-WANI. The community can further build on it and come up with more interesting business models for PM-WANI.

We are also working on proposals for improving the protocol to address the challenges mentioned in the previous section.

Please feel free to write to Saurabh Chakrabarti at [email protected] for any questions.

Building Innovative Products Out of India: Lessons from Bell Labs India, CDOT, Cisco, Concept2Silicon and Ittiam

What will it take to build an Apple or Google out of India? This is a question we often ask, and you might recall that I gave one perspective on this in my Outlook Business column some months ago.

Sanjay Nayak of Tejas Networks has devoted the last decade to building high tech telecom products out of India. He is passionate about building a supportive product ecosystem in Bangalore/India. So, when he invited me to moderate a panel discussion on “Fostering an Innovation Economy in India: Issues, Challenges & Recommendations” at the IEEE ANTS 2012 conference at Bangalore last week, I jumped at the opportunity.

We had great participants – Vishy Poosala of Bell Labs, VVR Sastry of CDOT (former CMD of Bharat Electronics), Srini Rajam of Ittiam, Satya Gupta of concept2silicon (and present chair of the Indian Semiconductor Association), and Ishwar Parulkar of Cisco, I had requested each participant to start with a short account of a successful innovation project they had been associated with in India, and what made it work. Since we hear so much about the obstacles to innovation in India, I thought some bright spots may offer ways around these.

And, a real treat followed as we got some insightful examples from all the speakers.

Vishy Poosala – Alcatel Lucent (Bell Labs)

Vishy started by describing an interesting phenomenon his team noticed. Rather than download songs legally available through mobile service providers, mobile owners preferred to buy songs from a corner store. The obvious reason was cost – it’s much more expensive to buy songs “legally.” Why do downloaded songs cost more? His team found out that the reason for this was that the service providers had congested networks, and therefore did not want to promote downloads that would congest their networks further. Bell Labs India proposed a solution to this problem – a “Mango Box” which could push content to users at off peak times when there was no congestion, and hence songs (or other content) could be sold cheaper. While they managed to commercialise this product in India, revenues were never big enough to excite AT&T. Ultimately, “Mango” got traction when it was deployed in the US for use on AT&T’s iphone network. The lessons? Address local problems, but look out for global problems where the same solution can be applied.Vishy mentioned that AL ventures, an internal venturing arm of Alcatel Lucent played a key role in making this cross-fertilization happen.

Srini Rajam – Ittiam

Srini went next. Ittiam has completed a successful decade of a focused IP play. It earns all its revenues from licensing IP it has created. In 2009, Ittiam identified that the then smartphones did not have the capability to play HD video. Creating that capability was non-trivial because it involved change in the software architecture and working with both handset and silicon players. There was a window of opportunityopen, and Ittiam sought to address this by quickly creating the IP, filing a patent and then working with the players to implement it. Not only were 10 million phones incorporating this IP sold in the first year, one of Ittiam’s major clients highlighted the HD video playback in its product marketing collateral. Based on this experience, Srini stressed the importance of innovation as a process – the spark (idea), followed by implementation, and then business impact. Clearly, as in the Alcatel Lucent case, choice of the product is key as well.

VVR Sastry – CDOT

After CDOT’s pioneering efforts on switching for rural exchanges in the 1980s, CDOT disappeared from public imagination. While it has continued to be involved in strategic projects, it’s no longer “visible.” Sastry of CDOT gave one example of how CDOT is trying to change that. Mobile base stations are power guzzlers and are already being targeted by environmentalists for their high carbon footprint. At the same time, rural call rates are not always high, and rural cellular infrastructure is under-utilized. CDOT is trying to solve this problem through shared GSM radio. With the regulators possibly allowing spectrum sharing, this could be a way for better utilization of rural cellular infrastructure. While admittedly a late life cycle product with an emerging market focus, this has the potential to lower costs yet provide multi-operator service in rural locations. Sastry stressed “right product at the right time”, providing a “total product concept” and keeping up the motivation of engineers.

Satya Gupta – Concept2Silicon

Satya Gupta’s company Concept2Silicon is just 3 years old. He encourages innovation through Friday brainstorming sessions. He stressed the importance of aligning new product ideas with needs and timing. In particular, he underlined the importance of aligning products to local conditions and price points. He outlined one important opportunity. Education is rapidly shifting from the traditional classroom to electronic media. But the electronic media used in the classroom are not interactive and don’t allow the teacher to adapt/change content or modify / add comments easily. Interactive whiteboards are available, but they are imported and too expensive. This is an area where Concept2Silicon sees product innovation opportunities.

Ishwar Parulkar – Cisco

Ishwar is the CTO of Cisco’s Provider Access Business Unit in Bangalore. He shared the highlights of the ASR 901 router, the first product developed end-to-end by Cisco in India (see my earlier post on this project for more details). Defining what product to build in India was critical – they chose a router for access providers (= mobile service providers) not only because this was a relevant market in India but also because this was not a core segment addressed by Cisco’s existing products. Scale, reliability and monetization were 3 key criteria for Cisco. To build the product in Bangalore, Ishwar’s team had to persuade vendors to enhance their local capabilities. They also had to transfer knowledge in certain areas like certification. Thus product development efforts involved building a local ecosystem. The third element was creating an appropriate organizational and operational model – there were 3 stages: an incubation stage (under the radar) till a concept could be proved, a stage of scale up with “borrowed resources,” and a third stage of mainstreaming with more funding.Today, ASR 901 has a market not only in India, but across the world.

Fostering an Innovation Economy

In the discussion that followed, several interesting questions came up which addressed the larger theme that Sanjay had identified for the session:

1. Will India be restricted to “late in the life cycle” or niche products, or will we be able to come out with genuinely new products?

2. What needs to be done to improve the innovation ecosystem?

3. How does India compare to China on the innovation front?

4. How can we improve collaboration between academia and industry?

5. How can we enhance the economic dividend to India of innovation activities here?

Most of the comments in response to the first question identified the usual obstacles to creating really innovative products from India: hierarchy in Indian society (vs. the questioning attitude required to do genuine innovation); fear of failure; the education system; and inadequate private sector investment in R&D. There was agreement that many of these things are changing, and the future looks optimistic. But the slow growth of private sector R&D investment continues to be an issue of concern.

Satya Gupta had some very specific and relevant suggestions on improving product innovation. His own experience in his company has been that even the components required for product innovation are not easily available, and often need to be imported with delays of upto 3-4 weeks. This slows down the innovation process, and also demotivates the innovator. He called for the setting up of resource centres – he called them ESDM innovation centres – that are fully equipped and ready-to-use for experimentation. This will help start-up entrepreneurs quickly try out new ideas.

There was broad agreement that China has been able to do several things on a scale that India is unable to even dream of – these include development of infrastructure, education in science and technology, funding for start-ups etc. China has a strong desire to dominate telecom and has therefore supported the creation of large corporations like Huawei and ZTE. In contrast, India lacks a strategic orientation, is unable to spend the R&D money committed because of cumbersome bureaucratic processes, and is no longer even the source of the largest number of graduate students abroad.

Regarding academia-industry collaboration, speakers pointed to the incentive systems in Indian academia that appear to favour academic research resulting in papers and do not give importance to industrial R&D. A specific example was given of a person with considerable international corporate R&D experience who was denied a job in one of the IITs because she did not have adequate research output (=papers in journals).

The fifth question – economic dividend for india – prompted an interesting discussion around value capture in the innovation process. Sanjay Nayak wondered aloud whether Indian companies need to invest more in marketing and branding if India is to capture more value. There was a broad agreement that collaboration was key to improving the economic returns to India – and that even multinational subsidiaries in India may gain from collaborating with each other rather than trying to “sell” their innovations to reluctant managements in the developed world.

Does innovation have to be a struggle? Or can it be the mainstream of a company’s activities? Many speakers pointed out that innovation involves change, and most human beings don’t like change. Hence innovation will always involve overcoming obstacles. Ishwar pointed out that even in Apple, ideas are hard fought. But I felt that companies like 3M, Google, and our own Titan have shown that innovation can become a more routine activity of the company.

Conclusion
I see confidence in our abilities to innovate from India growing, and that’s a good thing. There is a new generation of innovation evangelists returning to India (people like Vishy and Ishwar) who are determined to make things happen here. At the same time, we have people like Srini and Sanjay who have shown that good innovation can come out of India and that it’s possible to run innovative companies here. Of course, it’s not easy, but I see the formation of a critical mass of people who know how to make innovation work. Let’s hope a lot more people get inspired by their examples in the days to come.