Java 4 IMS

The IP Multimedia Subsystem (IMS) represents the evolution of the traditional telecom architectures which will provide to service providers the possibility to create attractive multimedia services based on IP. IMS, as almost every technology in the telecom industry, is being standardized, mainly by 3GPP, OMA and IETF, which will ensure interoperability between different operators. A big disadvantage of this standardization activities is its slow process and the amount of specifications being defined. For service providers, it is a complex task to start developing or creating an architecture for their applications, and it get even worse for new players in the market willing to make some profit from IMS capabilities. The telecom industry is now aware of that, at least from the mobile platform perspective; with the already approved jsr-281 API and the upcoming jsr-325, the developers can effortless access a set of essential IMS Services and Communication Enablers. In the same way, there is also a need of the developer community to have an abstraction, in a similar fashion as JSR-281 and JSR-325 do, to facilitate the development of IMS Applications on the server and desktop side, and in benefit of the developer community, an alignment (see picture bellow) between the different APIs in the different Java platforms will facilitate the creation of one-to-one and one-to-many services.


Currently, On the server side, Java SIP Servlets is the starting point for creating server-side (JavaEE) applications, just as JAIN SIP (jsr-32) and jsr-180 do for the JavaSE and JavaME platform. However, this API are quite different to each other, and many times, developers get confused trying to identify what transaction, dialogs or session means in each API. In addition, those API are SIP protocol related and payload unaware. Well, IMS is a lot more than SIP: media handling, signaling flow, standardized XML schemas in the payload, XCAP protocol, security, authentication and so on, are just some examples of the many different technical issues a programmer has to deal with when creating a application that interacts with the IMS network and its Enablers (presence, messaging, multimedia telephony).

jsr-281 and jsr-325 are already trying to cover many of the already mentioned IMS technical issues, but nothing is already being done on the server and desktop environments. By defining similar (because a 100% mapping is not reachable due the nature of the platforms) IMS APIs both on JavaSE and JavaEE the programmer can smoothly move between different development environments when creating one-to-one/many applications where server and client side coding is needed.

Comments

Post a Comment

Popular posts from this blog

A review of Partitioning Attacks

Partitioning Attacks is one form of side channel attacks which deals with cryptographic algorithm implementation, and more specifically, with those implementations where sensitive data reveals some statistical dependency of the logical states and hence, several well known techniques such us power or electromagnetic analysis can be used to find out the value of such relevant data. Partitioning is related to the property of certain implementations where relevant data can be distinguished as belonging to certain clusters - partitions - of signals or side channel information, which the attacker may use to createa statistical dependency of the flow. Such leakiness can be caused by algorithms using, for instance, lookup tables to store values needed during computation. In this paper , an overview of partitioning attacks is presented by exploring a particular example, the characteristics under which it operates and certain countermeasures which has been also suggested to thwart such attack.
Read more

Asynchronous Features for IMS Applications

One of main advantages of using the SIP protocol for developing IMS applications is its asynchronous nature. Interactive applications are those ones providing asynchronous notifications of events, and nowadays the current trend is on this direction (just take a look around to the asynchronous Web where you have the ability for the application to deliver state changes to the client, without the user necessarily having to initiate those updates). SIP is inherently an asynchronous protocol, where your User Agent or IMS entity is both client and server, and therefore, interactivity is a default feature. One of the main extensions offered by the SIP protocols is the SUBSCRIBE / NOTIFY mechanism RFC 3265. SUBSCRIBE/NOTIFY is a kind of observer pattern, where clients subscribe (listen) to a server for specific events, and once the server decides that a certain event must be communicated to the client, it notifies them about it (using the contact information provided by the client during su...
Read more

Homeopathic Ontology

Homeopathy is an alternative medical approachbased on the principle that a disease with a given set of symptoms can be cured by a medicine (remedy) which is known to produce a similar set of symptoms. Homeopathic remedies are based on "proving" techniques, which is a process used to test certain substances on healthy volunteers and to observe their reactions (symptoms). In order to analyze specific symptoms, this process may take months or years and results or provings are registered in a repertory, which represents a collection of homeopathic provings, well known as the Homeophatic Materia Medica. The repertory is an extensive collection of many years of investigation. Software technologies allow us to index all this information, in order to be able to look for any related symptom or remedie based on different criteria, proximity or combination of words. Due to the complexity and broadness of homeopathy, there is not a defined vocabulary or schema on those repertories where...
Read more