Ajax (facebook application) and IMS mashup using a JSON-RPC bridge

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.

IMS%20-%20facebook%201.jpg

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

IMS%20-%20facebook%202.jpg

The result is a mashup between the Web and IMS – one of the first instances of such a service I have seen as below

IMS%20-%20facebook%203.jpg

If you have any comments or are implementing similar services, please comment here

You can see a YouTube video HERE

Comments

  1. Paul Golding says:

    Very interesting mix of Web 2.0 with IMS. We should, in this case, think of Facebook as the primary platform, which is clearly is (i.e. with Facebook Applications) enabling links to IMS, another “platform”. However, in the IMS view of the world, applications (i.e. Facebook) “hang off” the IMS architecture (in order to add the IMS control plane to the application space).
    However, the big question is that in order for such Web2.0/IMS mash-ups to flourish, are operators going to give the degree of openness to allow such things to happen? This seems the crux of the matter.
    In this case, I would argue that 99% of the value in this mash-up is in the Facebook platform, not IMS. Operators have a hard time thinking of APIs as mechanisms to add and access value, instead of mechanisms to control services. Until they get round this issue, the potential for IMS as a driver for Mobile 2.0 in the same way we’ve seen the tipping point of Web 2.0, will never transpire.

  2. Ajit Jaokar says:

    spot on paul! agree .. this is an experimental service and not a commercial service .. yet I think its interesting and one to watch kind rgds Ajit

  3. Niklas Blum says:

    I can only partly agree with Paul. From a technical perspective Facebook offers only the framework for the application. The application that we created (sure as an experimental service) resides at a different server that could even be hosted at an operator or service provider.
    In regard of the openness of networks, we will see some more operators this year to offer an open API for 3rd parties as BT pioneered with Web21CSDK.
    I fully agree to your point about operators having a hard time to adapt the thinking of APIs and openness of networks.
    IMHO, either the operators will change their thinking (and network architecture) or other players will take over the application space for mobile networks and telecommunications.

  4. The OPUCE project is an European FP6 research project which is truly filling the gap between the IT and the telco worlds. Through a user-centric platform it allows end-users to compose and run their own telecom oriented services using services exposed both by Internet service providers and telcos (supported by an IMS). The services can be composed using a Web editor or a small application from a PDA.
    Besides, 3rd parties service providers can also develop their functions in an easy way and commit them to the OPUCE platform. The requirements are basically to have some simple Java and/or WS knowledge.
    This project has finished its first iteration with a successful working product which will be available soon through the Web site. During the second iteration of the project specific aspects of the project will be refined, in order to improve usability and other user-oriented aspects.
    Regarding operators support for this kind of platforms, it is worth noting that OPUCE is supported by three major European telcos; Telefónica, Telecom Italia and Portugal Telecom.
    A workshop of the project with a live demonstration will be held next June in Madrid. For more information, please refer at http://www.opuce.eu