Instead, within the lifecycle of a single large operator IMS RFI, lab trial and RFP, Youtube was founded (Feb 2005), reached 100 million videos being watched daily (July 2006) and was sold to Google for $1.65B (November 2006). Video sharing. Wasn't that one of the main exciting, change the world, IMS applications? Youtube is available on many 3G mobile phones now.
So how does an operator participate in the external speed of innovation and adoption without becoming a dumb bit pipe in the process? Web 2.0 applications are in perpetual beta, with releases every few weeks. The learning from actual usage is quickly captured and used to improve the service on a fast feedback loop. This is a far cry from the five nines methodical testing pursued by an operator, the 3 month lab trial and 6 month market trial and multi-million dollar systems integration project with Cap Gemini or IBM. Entire Web 2.0 startups can get to breakeven cashflow on less than the integration budget for a typical telecom operator internal application.
The technological answer is fairly well understood - exposing the key operator golden assets of call control, location, presence, messaging and billing securely to external applications using telecom web services, often using 3GPP standards like ParlayX. Vendors like Aepona, Nokia Siemens and BEA Systems provide Service Delivery Platforms that do this in a carrier class manner, and even help bridge the external applications to gradual use of IMS underpinnings inside the network, without requiring the Web 2.0 developer to understand IMS, let alone IN. There are deployments of note at leading operators, a good example being Sprint's Business Mobility Framework for exposing location which has 50 or more enterprise applications accessing location and messaging from the Sprint Network.
So that's the answer then, case closed?
No. The bigger problem is how do an operator and an application partner on the web do business together? One is used to free trials for months, slow testing and full control over every aspect of service pricing and branding. The other cycles every few weeks, gets users quickly, and revenue as much through advertising as subscriptions. Imagine both sides in the same room trying to work out a deal. They don't even talk the same language! The cultural distance is huge.
What's needed is a roadmap or guide to selecting a business model and a set of rules for how to pick the right model for the right situation that creates aligned timelines, financial incentives and risk tolerance for each. Whilst this seem like business development 101, its hard to do for an operator and a web 2.0 startup. Below is a framework for such an approach, that looks at application types based on their position on the demand curve or so called "long tail curve".


