The Network Carrier Dilemma

This article in Forbes magazine about network equipment providers enabling network carriers to expose service APIs (Application Programing Interfaces) started an interesting debate with Alcatel-Lucent's Laura Merling (@magicmerl), Mike Maney (@the_spinmd) and others on Twitter.

The crux of the debate is whether exposing developer APIs at the network layer is a good or a bad thing. This is the latest round in the 'dumb pipes vs. smart network' debate which lies at the heart of an economic dilemma facing the network carrier business model.

Value in the internet economic model is being extracted by the likes of Google, Microsoft, Facebook, EBay, Amazon et. al. — not by the network providers.

Network carriers increasingly provide only one service that consumers value — moving bits from point A to point B. Competition — at least outside the US — makes 'bit delivery' a commodity business with pricing models to match. Downward pricing pressure on the commoditized 'bit delivery' business model stands in stark contrast to the ever greater capital investment required to keep up with growing bandwidth demands. Bluntly the equation does not compute and something will have to give.

What does all of this have to do with APIs? In short network carriers see the provision of APIs as an opportunity to extract value from further up the internet food chain. APIs are the mechanism through which developers embed services in the apps they write for consumers. APIs make it more likely that developers will consume new network services that carriers create. Carriers can then generate incremental revenue from consumers that use the service embedded — through the API — in the applications developers create.

Creating unique services — that are differentiated from those offered by other carriers — opens the opportunity to control pricing and therefore how much value can be extracted. The downside is that applications consuming these services through their APIs would be carrier specific. The app on your smartphone would only work with the particular carrier offering that unique service. That would be a major problem.

Network specific applications would fracture the internet’s universal access model by partitioning the internet into carrier controlled 'service gardens.' That’s an alarming possibility and one that most believers in network neutrality and most consumers would find very unappealing.

The alternative would be to ensure that any network service and associated API is universally available across all carriers networks. The YouConnect service enabled by Alcatel-Lucent and referenced in the Forbes article applies just such a model. Unfortunately such 'Universal' services are unlikely to be economically appealing to the carriers.

Services that are 'Universally' available across all carrier networks will significantly limit the ability of one carrier to differentiate their service offerings from anyone other carrier’s. This lack of differentiation eliminates competitive leverage and leads directly to commoditization of the service and a return to the downward pricing spiral witnessed in today’s 'bit moving' business model.

In short — carrier specific services and APIs risk undermining the very thing which gives the internet its utility: universality of access. On the other hand universal services are difficult to differentiate and are likely to become commoditized with a resultant lack of carrier pricing power. Neither of these alternatives solves the fundamental economic problem lying at the heart of the network carrier business model.

Leave a Reply

Your email address will not be published. Required fields are marked *


*