Of OpenGardens, Walled Gardens, Tim Wu, Net Neutrality, Carterfone and IMS

netneutrality.JPG

Probably my longest article on this blog. I am preparing a pdf version as well!

Introduction

As many of you know Columbia University Professor Tim Wu has written a fascinating article called: Wireless Net Neutrality: Cellular Carterfone on Mobile Networks . If you have not read it already, I very much recommend that you do!

With a blog called ‘OpenGardens’, this topic is clearly of deep interest to me.

However, after reading the article, I have mixed views. The paper does a great job of highlighting the issues we face today, but I also believe that it mistaken on many other issues – and I find my selves taking a stance which is much more neutral.

This article outlines my thoughts on this document.

All comments welcome to ajit.jaokar at futuretext.com.

Particularly, I welcome feedback from Operators – since many in Europe I know are thinking of Opening up the network in some way.

Synopsis of my thinking• Tim Wu’s document does a great job of highlighting the issues. It does an excellent job about raising consumer awareness and I truly hope it drives some thinking at Government and at Operator levels.

• The USA is clearly losing out due to the practises highlighted in the document. However, these practises are not a global trend. Even within the USA, there is a range of behaviour exhibited by Operators. Legislation may not be the only option here – and indeed may not be the best option.

• The whole document is primarily based on the application of Carterfone principle to the Mobile Operators. I believe that the Carterphone principle can be applied to voice but not to data unless certain other conditions are fulfilled first – which I explain below. Thus, it is not a simple case of applying the Carterphone principle to the Mobile Network Operator as is implied

• Oddly enough, the document does not talk of IMS . IMS is a huge buzzword in the industry and addresses the very same issues that are outlined here. I discuss some implications of IMS below.

• In fact, if IMS were to be considered, Skype would be one of the ‘walled gardens’ (since it does not use the SIP protocol – which means it is not Open).

• It is ironic that the Carterphone principle (opening up the Mobile network as envisaged in the document), would benefit the two closest walled gardens – Skype and iPhone. (My previous caveats about applying the Carterphone principle to voice apply in this case)

• The issues highlighted are not ONLY due to the Operator in all cases. For instance, for Mobile Video, the government is an important player(and cause) of the delay in deployment.

• The document does not address net neutrality as I understand it. Thus, net neutrality seems to be a keyword designed to gain some emotional currency

• I totally agree on the discussions about Disclosure. There may be a case for legislation in this sector only i.e. enforcing greater disclosure

• Cooperation and not competition is the key!! In that sense, unless America does some fundamental rethink, it may well lose out in the end because of it’s culture of competing vs. collaborating

My core belief (and potential solution to the issues outlined by Tim) is :

In a consumption driven world, competition is the driving force. In a creation driven world(User generated content, Web 2.0, Mobile Web 2.0 etc), cooperation is the driving force. For reasons I explain below, we have no choice but to accept a diverse ecosystem in the West and legislation is not a good option. Instead, we should look at cooperation and try to identify the dimensions of the stack where we can get critical mass.

Analysis

Verizon: Firstly, let us acknowledge that Verizon is an exception. Much of what they do will be severely limiting in a Web 2.0/Social networking world – simply because Version customers will want to interact with other people (and not just other Verizon customers). Like AOL, Verizon will find out that it can’t maintain a walled garden for ever. Now, having got the issue of Verizon out of the way, let us look at a wider picture

Skype and iPhone: The irony here is – Opening up the network in this way, would benefit two of the closest gardens : i.e. Skype and iPhone

No IMS?: Surprisingly, Tim Wu’s document does not mention IMS at all. This is strange, since IMS is such a huge buzzword in the industry today. IMS also plays directly on the net neutrality issue in the sense either you can view it as a walled garden (at the packet level) or you can consider the disruptive potential of naked SIP (SIP sans IMS). Or, like I do, think that IMS has some unique and powerful features and depending on how IMS is implemented – this can be truly beneficial to the industry.

In any case, what you can’t do is – ignore IMS!

SIP and Skype : If IMS were to be included, Skype does not look that good – because it does not follow an open protocol(SIP).

The Carterfone principle: The whole document is primarily based on the application of Carterfone principle to the Mobile Operators. In my view, The Carterphone principle can be applied to voice but not to data unless the Operator creates APIs (Application Programming Interfaces) first. Carterfone without APIs is practically useless.

We can illustrate this by considering the example of Visual voicemail in iPhones. As a consumer, I love the idea of Visual voicemail. That’s EXACTLY what I want .. I hate trawling through old voicemail(and worse still – remembering keys to go next voicemail etc etc!). So, it’s fantastic to have visual voicemail .. BUT guess what? Supporting visual voicemail implies that the two (device and Carrier) are intimately in bed! Else, it is not possible to provide such a service(because the voicemail is stored on the network and not the device) .

Thus, in a Voice scenario, Carterfone may work – but in a data scenario it will not because to make a useful service(like Visual voicemail), the device needs the network to be abstracted(i.e. API enabled).

Tim Wu’s document misses this critical point.

An API enabled Mobile Operator actually is a very powerful proposition – something which I have been speaking of for some time as in Mobile web 20: Re-engineering the digital ecosystem with converged digital processes in a Post IMS/Quad play world and in The Long tail and Mobile Web 2.0

Thus, it’s certainly not a case of directly applying the Carterfone principle (i.e. Plug and Play) to Mobile Data scenarios.

Carterfone, APIs and Pipes: Note that in the above API enabled scenario, the Operator is still the hub(and not the dumb pipe). The Operator still retains leverage in this situation by managing the APIs

The iPhone : Tim says: >>> Most importantly, to the surprise of many, the iPhone only works on the network of a single carrier, AT&T Wireless. The hundreds of millions of consumers who are not AT&T Wireless customers cannot make use of the iPhone unless they become AT&T customers. The question is, why? Why can’t you just buy a cell phone and use it on any network, like a normal phone? <<<

No No No .. I was not surprised. See my longish post saying ..

The iPhone is extraordinary not because of it’s UI but because it’s the tail wagging the dog ..( But the real question is: How many dogs can it wag?)

In fact, as I said before, the iPhone CANNOT work with multiple Operators with ease because it needs to be in bed with the Operator to give that unique user experience. The client alone cannot deliver that user experience and I use the case of Visual voicemail to indicate why

Locked phones? In light of the above, locked phones are not such a big issue.

Qualcomm/ BREW : One must also not ignore the role of Qualcomm/BREW in this – i.e. Qualcomm by definition leads to a certain ecosystem biased towards a walled garden at all levels(network, apps and so on). Outside that scenario, the Mobile world is a lot more open place.

Mobile TV and Video: Mobile TV and Video is hobbled not by the Operators – but due to a range of other factors(including broadcast spectrum allocations in Europe). Thus, it’s a much more complex issue – with standards wars at technology/broadcast level – not a pure Operator scenario

Developers: When the article talks of developers, the implicit assumption in the document is : you need to be on the carrier portal/deck. However, Operators were never good at marketing mobile applications. In other words, even if you did end up on the deck, it may not translate to sales(excluding simple content such as games etc).

The Operator Portal also degrades the brand of the content/application owner. They are not the destination site. If they were strong or innovative enough, they would not want to be eclipsed by the Operator’s brand and instead would want to promote their own brand. Clearly, the off portal market in the USA is not mature (and this is the real problem i.e. short codes need to be viable and interoperable). In the UK, companies like Yell Mobile , which have good content, are primarily taking the off portal route rather than the Operator route.

Thus, if the service is compelling enough, I would not recommend the Portal route. As a corollary, I think the off portal market in the US needs to improve. That’s a real issue

WAP vs. Full browsers : Yes, WAP was a crippled version of the Web. That’s true. But, in the early days (low bandwidth, low CPU etc), was there an option? i.e. could we have really been able to run full web browsers on mobile devices? Today, as we increasingly see the uptake of full web browsers on Mobile devices from companies such as Nokia and Opera, these vendors are redefining the landscape(and I include Widgets amongst browser technology). This will lead to applications that span the Web and the Mobile Web using technologies like Mobile Ajax, Mobile Widgets and WICD () – making long tail applications possible.

Openmoko : Openmoko has been on my radar. It is interesting. Time will tell. It still needs a network though and I am not sure how that works.

Net neutrality: Defining net neutrality primarily in terms of terms of the Carterphone principle sounds limiting to me?

The mobile network is different and the Mobile network operator is not anonymous : Mobile network operator is not anonymous. In fact they are a (longish!) phone call away. But accessible none the less. Which means – they can be sued. I don’t think this fact can be ignored. For instance, if you get Spam on the Web, there is not a lot you can do. However, if you get Spam on the Mobile web – who do you call? Your Operator. In practise, this fact cant be ignored.

The security risks are also higher due to the personal nature of the device. For example, a child may be using a PC(which may be also be used by an adult). But in case of the child’s phone, it is always being used by the child – hence more risk.

The point of these arguments is: there are genuine reasons to be cautious.

Why change and why now?

In the last few years since I have been tracking this space, why is the idea of opening up Telecoms networks suddenly of interest?

Here is the reason in my view.

Telecoms is a mature industry. Voice revenues still drive a lot of the business. Data revenues are small, indeed non existent. However, Voice revenues are under threat from VOIP – and that’s a universal phenomenon – on both fixed and mobile networks. (albeit on mobile networks today, it is still mainly voice over WiFi).

Also, in most places in the West, the markets are saturated. Thus, growth prospects for voice alone are limited. In contrast to the Web companies, especially with the uptake of Web 2.0, Telecoms is not an attractive investment proposition in light of the (lack of) future growth.

Hence, witness the interest in Fixed to Mobile convergence (fixed operators trying to poach customers from mobile operators and vice versa) and acquisitions in fast growing markets like India. And also an interest in Mobile data for the same reason.

Hence, market forces will drive the change in many part of the world. Other factors also help. Better devices, mature networks, better browser technology etc.

Case for Government intervention?

Tim Wu’s article concludes: “At some point, I think Americans are going to put their foot down and say, ‘We won’t tolerate this anymore.’”

That’s true

The real question is: What could be done and should the government intervene?

In fact, a government mandated environment leading to fantastic rates of growth and innovation does exist today. It’s in South Korea where the Ministry of Information and Communication (South Korea) or MIC Korea plays the overseer role.

But is that the best way? Is that the optimal path in the West?

Think about this, Korea and Japan have made great strides internally but have struggled (and will continue to struggle in my view) to export their Mobile/communications services globally. That’s the dark side of government mandated standards – high internal growth – low global growth.

Thus, excessive government intervention is the wrong thing in my view.

See my blog Should you be thinking of Vegas on your next flight to Tokyo or Seoul? .

Speaking of Governments, ours(UK) did intervene in the dot com boom and reaped a windfall through the 3G spectrum auctions . By saddling the Operators with debt, I believe the British government squashed a golden opportunity for British companies to take a lead in the Wireless space. We definitely don’t want more of that – Thank You!

The Web itself is not exactly free of monopolies. Take the case of Microsoft. However, with my Randian / free market view, I would oppose any regulation on a company like Microsoft. After all, if customers truly hated it, they could change(nothing prevents them from making that choice – much as the same with leaving a specific Operator). With Google applications , that may well happen – but the changes will be market driven and not regulatory.

The search for disruptive elements

The problem with the Mobile industry is: It’s still very arrogant. We talk of concepts like Mobile Youth – but the IPTV industry does not talk of ‘IPTV Youth’ or the fixed line industry of ‘Fixed line youth’.

Once we accept that there are only ‘people’ and they want to communicate irrespective of transport mechanisms – then we have to ask ourselves the question : Where can we get critical mass?

In my view, no single Operator can gain critical mass because the Operator’s subscriber base is fragmented along many dimensions, for instance devices, Pre pay-Post Pay etc.

So, disruptive elements can arise if we unify the stack across Operators along some dimension

At the application level, I believe that Web technologies will do this (especially full web browsers, widgets etc). At a network level, the combination of devices and WiFi/WiMax is the key.

These will happen organically – and we will always have to get used to working in a diverse ecosystem.

Co-operation as a solution

To recap, I believe that :

In a consumption driven world, competition is the driving force. In a creation driven world(User generated content, Web 2.0, Mobile Web 2.0 ), cooperation is the driving force. For reasons I explain previously, we have no choice but to accept a diverse ecosystem in the West and sweeping legislation is not a good option.

In that sense, unless America does some fundamental rethink, it may well lose out in the end because of it’s culture of competing vs. collaborating. In contrast, the European / GSM approach is more collaborative and suited for future growth

To conclude

1) We will continue to live in a diverse ecosystem and that is good

2) Operators will end up with Open APIs and that’s not a Pipe.

3) As we go from a consumption driven ecosystem to a creation driven ecosystem, cooperation will be a driving force and not competition. The need to communicate will overcome outdated business models.

4) Market forces are the main drivers to opening up in Europe(the need to show growth to the investment community for example)

5) In my view, government regulation is the wrong step(except in cases like Disclosure). A combination of Web enabled devices, devices supporting WiFi etc will drive disruptive applications.

PS: In an ironic twist, the March 26 issue of Business week’s best performers – has Google in the top spot. But guess who is on No 7? Yes, Verizon communications!. It indicates to me, that if customers want to leave a service, they will – but they don’t at the moment because they are primarily consuming content.

However, I believe that the future will belong to those Operators who open up because the creation driven ecosystem will demand that (in contrast to the current consumption driven ecosystem)

Image source: Image shack

http://img145.imageshack.us/img145/5388/internet3yc.gif

A note on comments:

I have been having a lot of problems with Spam. Hence, comments are disabled. Please email me at ajit.jaokar at futuretext.com and I shall be happy to post your comments

What is the relationship between Mobile Ajax and Mobile Widgets?

widget1.JPG

This is a part of the Mobile Ajax FAQ which I, Rocco and Bryan are working on .. Due to my travel last week at MIT and Ajaxworld, that’s been a bit delayed but we hope to release it this week.

Meanwhile, I am putting out a few questions from the FAQ so we get ongoing feedback

Here is one ..

What is the relationship between Mobile Ajax and Mobile Widgets?

In its entirety, Ajax comprises of XMLHTTPReq + DOM Scripting + XHTML/CSS. Functionally, two things are happening here: Data is being fetched asynchronously and the information thus fetched is being rendered on the client through Javascript.

Most widget engines are using the asynchronous part uniformly but are making their own changes to the rendering(display) part. While this leads to fragmentation of Widget technology, the fact still remains that Ajax i.e. Asynchronous I/O and visual rendering are the core technologies underpinning widgets

From simple beginnings, Widgets(powered by Ajax), are taking a life of their own(for example Widgets calling other widgets).

When it comes to the mobile environment, we are seeing the same phenomenon i.e. we see Mobile Widgets powered by Mobile Ajax and also some fragmentation

Also, we are seeing the first attempts of standardization from the W3C

The significance of Mobile Widgets lies in two factors

a) As full web browsers become the norm on mobile devices(by that we mean a browser supporting Web technologies like Javascipt, CSS etc), Widgets can span the Web and the Mobile Web. This is very significant because Long Tail applications are now possible and we will now have the Web as a mechanism to distribute mobile applications(widgets). With Widgets calling other widgets, we could soon see an entire Widget framework leading to Long Tail applications powered by Widgets

Opera is already doing this with their Widget platform and we expect Apple dashboard widgets may also appear in the iPhone

b) Offline widgets are an interesting variant. For offline widgets to work, we need an API which allows the widget to work offline and then resync/transfer data when the connection is available again

Thus, Mobile Ajax powers Mobile Widgets and Mobile Widgets are significant because they span the Web and the Mobile Web(for instance Apple dashboard widgets). By doing so, they enable Long Tail mobile applications(because the Web now acts as a distribution platform for Mobile Widgets)

My talk at Ajaxworld: A brief summary of main ideas covered..

threemusketeers.jpg

Yesterday, I spoke at Ajaxworld in New York on Deploying Web-Based Applications to Mobile Devices Using AJAX Techniques.

This is my third Ajax world(after New York and Santa Clara last year) and I am pleasantly surprised as to how many people turned up this year for my talk!

Ajax on Mobile devices is a subsidiary topic from the main conference (i.e. Rich Internet Applications on the Web) – and hence to see so many people attending what was in effect, the last session for the day, is great. In fact the room was full – and there were some people outside the Hudson Suite – where I spoke.

I can think of three reasons for this uptake:

a) RIA (Rich Internet Applications) is becoming mainstream – be they Ajax or Flex. For instance, for the first time, Oracle was an attendee and also a sponsor

b) Mobile Ajax is unexpectedly in the news thanks to iPhone and Mobile Widgets(The Mobile Widgets I predicted more than a year ago, iPhone was unexpected to all and will be significant for Mobile Ajax as I spoke yesterday – especially if Dashboard widgets make it to the iPhone)

c) And finally, there is widespread support from almost all browser vendors. Here in Europe, we focus on Nokia and Opera – but there were a number of questions about Windows Mobile – something I need to clearly brush up on a bit more!

Here is a slide summarising the top five things to take away from the talk

Some notes

a) By three musketeers, I mean the trio of technologies : Mobile Ajax, Mobile Widgets and WICD

b) The quickest benefits for Mobile Ajax are based on accessing the Web / enterprise data(because these applications don’t need access to device APIs). The best example of this type of service is Soonr

c) Mobile Ajax is more than a pretty face! See an article which I wrote a while ago elaborating this i.e. look beyond the UI to the broader architecture

d) Long tail applications and Widgets!! .. Mobile Ajax is the foundation of Mobile Widgets and Widgets span the Web and the Mobile Web(thereby enabling Long Tail applications)

Thanks to team at sys-con . Someone at sys-con said I am almost part of the family :) and they always help me out since I am one of the few regular European speakers. Thanks to Jeremy, Faut, Dion, Laurie and Megan for all your help.

Look out for our Mobile Ajax FAQ (I , Rocco and Bryan are writing)

fivethings1.jpg

Three musketeers image source: http://www.dead-fish.com/Pictures/PC%20Build%20042%20thumb.jpg

Feedback from MIT Sloan re my talk ..

mitsloan.JPG

Furthur to my talk at MIT Sloan on Web 2.0, Mobile Web 2.0, Convergence and changing business processes , Aaron and Maya sent me this nice note

We created MoMIT (the Mobile, Media, and Internet Club) to keep MIT/Sloan at the forefront of the converging Mobile/Media/Internet space. Our club members really benefited from Ajit’s company-neutral position, and we look forward to an ongoing dialogue with Futuretext.”

Thanks Aaron and Maya. Like I said in my talk, the goal of futuretext and my talk at MIT was to share ideas i.e. to talk about our vision and ideas(OpenGardens, Convergence, Communities etc). So, I am glad I could contribute to the knowledge base

Project View: Mobile penpals – Stanford RDVP program

stanford.JPG

Last year, I spoke at Stanford University’s Digital Visions program. Since then, I have been keeping in touch with Karen Coppock (Director, Industry Collaboration – Stanford RDVP program) and her team at Stanford.

The Reuters Digital Vision Program (RDVP) is a Stanford centre for social entrepreneurship that applies the principles of high-tech innovation to create product and service concepts that empower communities worldwide. This resonates with my personal vision of the power of Mobile technology to make a wider, global impact on society and affect the lives of people (The mobile Internet will do more for Africa than live 8!)

So, I am always happy to blog about the interesting work Karen and her team are doing – since it has the potential to make a difference in the lives of so many people worldwide.

Here are two programs I think are interesting

John Kuner is working on Project VIEW. When I was young, I had a ‘pen friend’. Today, the same idea can be enriched by mobile technology. Project View explores the use of camera phones and digital storytelling for cross-cultural connections between students in the United States and students in the developing world. Although lack of access to computer technology is a common problem in the developing world, mobile phones are ubiquitous. Camera phones combined with non-verbal communications like movement and digital storytelling allow young people to establish meaningful connections with each other across geographic and cultural boundaries. The video exchanges are a cross between websites like MySpace and Facebook, traditional penpal programs and distance learning.

The components of Project View include:

Classes (teaching students how to use their own voice with basic technology to create a short video piece)

Technology (websites, social networking, video uploading, mobile browsing)

Cultural Exchange (by exploring and refining their own viewpoint, then experiencing perspectives from other cultures, students get an early exposure to a broader, global perspective breaking down barriers and assumptions, and fostering tolerance and understanding)

John did the field work in Sri Lanka in Jan 2007. Sri Lanka is a relatively poor country for the average citizen. According to the CIA world factbook, the per capita GDP (Gross Domestic Product) is $4,600, compared to the $43,500 for the United States. (CIA Factbook, 2006). However, it is an excellent place for internet and particularly mobile phone-based projects. Over 4 of the 20 million citizens have cell phones, with a higher concentration in urban areas.

People are tech savvy. A young woman John spoke with was very familiar with cell phones, including prices of phones and services. She had plans with two operators and switched her SIM card (effectively changing her number but keeping the same phone) to take advantage of text messaging promotions for both operators, first using all of her ’50 free weekend text messages’ on one, then using ‘free messaging within the network’ on the other.

The young in Sri Lanka absorb the technology quickly and are hard working and eager to learn – and project View helps them to form relationships with friends worldwide – just like traditional pen pals did.

The second project I found very interesting was by Saori Fotenos which is based on the idea of citizen’s journalism. There is a talk about : Citizen Journalism: A Look at How Blogging is Changing the Media Landscape from the Congo to Korea”, hosted by Democracy Now! with Amy Goodman.

And of course, I follow my friend Adam Tolnay’s project on Y-Fi (Youth Financial Literacy)

Do you want to write an FAQ on the OpenGardens blog?

Hello

Alongwith Rocco Georgi and Bryan Rieger , I am working on a Mobile Ajax Faq in line with my presentation at Ajaxworld in New York. I am now thinking of extending this idea more to other topics. Would you be interesting in writing an FAQ which we would publish on this blog?

It will be a living document and hopefully would be great for your personal profile as well.

If so, please contact me at ajit.jaokar at futuretext.com

futuretxt (not futuretext)

futuretxt1.JPG

In the spirit of helping the industry .. I got a note from Christopher Rhodes, Creative Director

of Msgme, who wants to launch a service called futuretxt(and not futuretext i.e. my company!).

Chris wanted to know if I thought there was a conflict of interest – and I think not – and I even promised to blog about futuretxt because it’s simple but useful

So, here we are!

Presenting futuretxt (and not futuretext :)

It is based on their flagship product which is a text messaging call/response platform called Msgme. The futuretxt service is based on Msgme and provides a scheduled text messaging alert system. I know many calendar based systems would also do this – but I like simple, monolithic applications i.e. an application that does one thing very well – so I think this service may be useful

Podcast: Håkon Wium Lie CTO of Opera software – Significance of Widgets – Web and Mobile

hakon.JPG

Yesterday, we launched our second video podcast – an interview with Håkon Wium Lie CTO of Opera software on the significance of Widgets (Web and Mobile). I have been a great fan of Widgets and Opera is a world leader in this space having a footprint on both the Web and Mobile Web. This is a first of a series of three podcasts.

You can see Håkon at the Horizon Channel

We welcome feedback on ajit.jaokar at futuretext.com.

Carnival of the mobilists – at Rudy’s blog ..

One of the best carnivals – and they all have such great quality. I think Rudy is right in saying that everyone is a winner!

Carnival of the mobilists no 64