Skip to main content

JSR 281: IMS Services API

5 replies [Last post]
ivelin
Offline
Joined: 2003-07-13

Bob Bickel at JBoss pointed me to this new JSR proposal. It looks like a Java ME device API that will standardize the client side of mutimedia services.
http://www.jcp.org/en/jsr/detail?id=281

Interestingly it does not cite relationship to JAIN.

Does anyone have thoughts on its significance and the relevance it has to Mobicents?

Ivelin

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mranga
Offline
Joined: 2003-06-06

I am in the process of updating NIST-SIP to be the RI for JAIN-SIP 1.2. We dont have conveniant support for some of the IMS functionality (in particular Registgrations) at present. It is possible to do this with what we have but there should be more by way of helper functions. We will be taking a look at that in the next generation of JAIN-SIP. For now, we have converged on some base functionality for JAIN-SIP 1.2 which will be much better for server applications like the JAIN-SIP resource adaptor.

Ranga

ivelin
Offline
Joined: 2003-07-13

Then it looks like jsr281 does not affect Mobicents in the near future, but we may want to keep our ears open and support an initiative to developer an interoperability test suite to ensure that 281 compliant devices can be served by Mobicents.

Ivelin

copprhead
Offline
Joined: 2007-11-29

JSR 281 really just defines an API towards the application, but doesn't mandate how SIP or HTML messages are actually sent (headers etc). So we can just hope that the applicable 3GPP and IETF standards are well-enough defined so that all implementations are interoperable.

By the way there is now an implementation of JSR 281 available as a library which can be used for own applications on MIDP 2.0 phones from the NSN IMS Developer Program: http://www.nokiasiemensnetworks.com/idp

maretzke
Offline
Joined: 2004-10-04

Hello Ivelin, hello all,

the IMS Services API looks very device centric and its intention is to offer a SIP API - or better said an IMS API on the mobile device.

From my point of view, if the SIP stack included in Mobicents (which is the NIST stack) is capable of dealing with 3GPP messages (especially the very initial security negotiation dialoge), then Mobicents will be ready to talk to JSR-281 enabled devices.

Just my 2 pence,
-- Michael.

deruelle_jean
Offline
Joined: 2003-06-24

it looks like the sip-for-me java.net project might evolve towards this direction or that a new project can be done on this new JSR when it will be finalized...