I have been discussing the interplay between IMS and Web 2.0 in a number of recent blogs.
To get our terminology right:
a) By IMS applications – I mean any application that is uniquely possible by using the IMS network. The operative word being uniquely – because many applications enabled by IMS are also possible through the Web 2.0 services for free.
b) For the purposes of this blog, I am using facebook as the Web 2.0 application.
On first impressions, Web 2.0 and IMS don’t mix. However, there are two obvious points of contact.
Firstly, many IMS applications can be done by Mobile Web 2.0 services (for free!). That means, the two are competitors.
Secondly, IMS can be used to enable many Web 2.0 applications if IMS functionalities can be abstracted as a service and can be accessed at the Web 2.0 level.
We are discussing the second point in this blog
As I have mentioned before, my company – futuretext – is a partner of Fraunhofer FOKUS.
The FOKUS team has been doing some pioneering work in this space.
Essentially, they have abstracted IMS services into a facebook application.
To understand this, we have to take a Web and a mobile view.
Taking a Web view, we have a facebook application – like any other facebook application.
On the IMS side, we need a JSON-RPC bridge.
The significance is: this technique allows us to access IMS services in a browser.
This is significant since browser support for IMS is practically non existent (In contrast, Java has JSR 307 JSR 281 , Symbian has Symbian freeway which support IMS integration into their respective environments)
So, the IMS side looks like this
The result is a mashup between the Web and IMS – one of the first instances of such a service I have seen as below
If you have any comments or are implementing similar services, please comment here
You can see a YouTube video HERE