Tuesday, May 09, 2006

Dean Bubley: What's an IMS handset? And who cares? I've already got one with "Naked SIP"

Dean Bubley writes at Disruptive Wireless about some upcoming research of his on IMS- and SIP-capable phones. He writes that "we're not even at the stage of operators standing up and saying "Er..... you know these IMS networks we're deploying? Well, we've got a small problem.....""

Bubley comments on the standards that have been developed for these IMS phoneswhich have SIP and some 3GPP extensions. He then states:

Now try & find anywhere that says how these phones should actually work in the hands of the user. How does the "IMS client framework" work with all the other applications on the phone? What are the standards for the user interface - telling the other presence user that your videocamera is switched off, or that the phone's in your pocket & you're using a Bluetooth headset? Does the phone need to be multi-tasking capable if you want several IM sessions, video-sharing and a buddy list working simultaneously? While listening to the MP3 player too? How should it behave differently if it's got WiFi in it? Should the applications be "bearer aware"?
Bubley believes that when properly IMS-capable handsets are avaialble (probably late 2007-early 2008), "we should expect another 2 years of fiddling around trying to get them to be decently useable. Especially as the earliest ones will have operator-proprietary software stacks and applications. Reliable interoperability between handset brands (or operators) for anything other than the most basic push-to-talk or video-sharing applications is a LONG way off. And I haven't even factored in any unexpected problems with battery consumption or end-to-end service latency."

He then remarks that "well before we get IMS handsets, we have SIP-enabled ones. They're already shipping - the latest versions of Windows Mobile and Symbian OS both include SIP. Future versions of handset Java will as well. Not only that, but 3rd party developers can access the SIP stack, and write their own applications that exploit it. VoIP, or IM, for example. IP-PBX clients. Conferencing tools. Open-Source SMS replacement applications. Cool Web 2.0 stuff. "

Bubley estimates that
between now and the end of 2011, there will be, cumulatively, 980m more "Naked SIP" cellphones sold than "Closed IMS" handsets which restrict the user to the operator's billable IMS services. That's a billion extra mobile devices capable of supporting disruptive non-operator SIP applications, developed by 3rd parties, over the next 5 years. I've said before that IMS is less a "walled garden" than an "open prison". Well, the inmates have already started jumping over the fence, even before they've been shown to their cells.